Dear all,
When I do some ISIS lab, I found a interesting question. The topo in
attachment. when i did ISIS Leak on R2 and R3,interesting thing occur. I
check the route on R2,I found the R3's loopback is suboptimum,not go R2-R3
link directly.It go through R4. I found Juniper document,It said Junipe
Ok so, I'm currently beating my head against the inpenetrable wall of
anti-clue that is JTAC (yes I know what you're asking, when am I not?
:P), and I've apparently reached a point of impasse where I need to
solicit some external assistance to help get the point across.
The other day we discover
My understanding is that new Trio card for the MX will allow you to do
Netflow processing on the line card itself, without the need for a
separate Multiservices DPC card.
What I don't know is if there is some flavor of 10.x available where this
is currently supported on these new cards. In ot
On Tue, Mar 09, 2010 at 05:01:19PM +0100, Sean Clarke wrote:
> I'm telling you what it's doing.. I'm not saying it's impossible in
> theory on the RE.
>
> It's just Juniper don't do it, probably to stop people breaking stuff,
> i.e. protocol handling.
> If you want that to change why not talk to
Nonsense. The CPU usage might be ever so slightly higher in v9, but
neither is a major contributor to overall load even at the maximum
supported RE sampling rate. The only time you *need* a services card is
when you want to do a much higher rate than the RE can support (i.e. you
want to do some 1
On 3/9/10 4:40 PM, Richard A Steenbergen wrote:
Nonsense. The CPU usage might be ever so slightly higher in v9, but
neither is a major contributor to overall load even at the maximum
supported RE sampling rate. The only time you*need* a services card is
when you want to do a much higher rate tha
On Tue, Mar 09, 2010 at 03:29:05PM +0100, Sean Clarke wrote:
> This is correct. To do v9 is far more processor intensive, hence you
> really don't want to be doing this on the Routing Engine, as is the case
> with v5. All this functionality is off loaded onto the MS-DPC instead.
Nonsense. The CP
On 3/9/10 2:38 PM, Matjaž Straus wrote:
We are using 9.6R3.8 on our Juniper MX routers and we wish to enable netflow v9
for IPv6 traffic flow sampling. Our local Juniper partner claims that a special
Multiservices DPC card is needed for netflow v9. DPCE 4x 10GE R can run tunnels
like GRE, IP-i
On Tue, Mar 09, 2010 at 02:44:06PM +, Humair Ali wrote:
> you could use a routing instance , with layer 2 virtual switch, and use
> multiple bridge domain as part of that virtual switch routing instance ,
> with the L3 interface
How many such instances would you expect to work? With all the c
Hey everyone,
I'm working on replacing some datacenter Cat 6500s with Juniper MX and
the more I read about bridge domains and L2 virtual switches, the more
I'm completely mystified. Our current deployment is VLAN-based (one
per customer installation). L3 services are provided on SVIs.
If I crea
On Mar 8, 2010, at 1:54 PM, Chuck Anderson wrote:
I wonder if that is because the IS-IS Hello PDUs are being sent
as Ethernet Multicast frames
This had been my suspicion as well. Is it possible to disable igmp-
snooping on the EX2500's?
-Shane
Hi there!
We are using 9.6R3.8 on our Juniper MX routers and we wish to enable netflow v9
for IPv6 traffic flow sampling. Our local Juniper partner claims that a special
Multiservices DPC card is needed for netflow v9. DPCE 4x 10GE R can run tunnels
like GRE, IP-in-IP but not netflow services :
On Saturday 06 March 2010 05:14:42 pm David Monosov wrote:
> Does anyone have any experiences (or ideas) to share on
> the subject of elegantly integrating JUNOSe devices into
> multi-topology IPv4 and IPv6 IS-IS domains without this
> feature?
Have no experience with JUNOSe, but if the code i
Hi Matjaž,
You are correct that the MS-DPC cards are needed for NetFlow v9 functionality.
I believe that you also need a software license to activate this feature once
you obtain the MS-DPC. My understanding is that an MS-PIC (and s/w license) is
needed for NFv9 on M- and T-series routers. O
14 matches
Mail list logo