M10i already has many peers that support *2 byte asn only* and is running
without any issues, but *why it is not able to negotiate with Maipu to make
the peer up without disabling the 4byte asn capability*.
ASFAIK, 4 byte ASN or AS4_PATH is an optional transitive attribute unlike
AS_PATH
Yes, per-packet really means per-flow. The default is per-prefix. Have to use
mlpp to get per-packet.
Regards
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Paul Stewart
Sent: Thursday, May 20, 2010 5:52 PM
As there is quite a bit of voice traffic involved I asked if this was really
per packet or if it was per flow as he had mentioned. I was told that
even though the configuration uses the wording per-packet that it's really
per flow occurring. It does appear to actually be some kind of
On Fri, May 21, 2010 at 08:18:57AM +0200, sth...@nethelp.no wrote:
Confirmed. It is per flow. All modern JunOS equipment can only do per
flow. The wording of the command is unfortunate, and results in such
questions showing up on this list on a regular basis.
Funny, they had no problem
Hi Paul,
l also have two cases open with similar questions.
First it is nowhere written which fields are taken on EX to calculate the
hash for per flow. JTAC seems to not know though sent me very detailed
explanation of how per-flow balancing is done for LAGs. Seems like ECMP uses
the same
Hello,
I have a switch EX3200-48T with quite simple L2 config. Once in a
while I can see some MAC addresses learned on the correct interface
and VLAN, but then (less than a second later) the MAC is deleted.
I can also see the Immediate aging counter increasing.
Example:
u...@switch show
Please disregard this message. It is just a test.
I apologize for the inconvenience.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
7 matches
Mail list logo
