Looks like the want to be *_very_* sure there traffic flows through as174 :-)
M
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
Mark Tinka
Sent: 27 November 2013 04:26
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] %BGP-6-MSGDUMP_LIMIT
On 26/11/13 21:11, Saku Ytti wrote:
Interestingly, I don't believe this behaviour could be seen in IOS-XR or JunOS
or such, since it's quite untypical for userland process to start processing
packet before it's received. But IOS specifically has dedicated TCP/IP
implementation for BGP and
Hi!
well, I tested on different IOS versions: actually it doesn't show on
151-4.M1 and 124-24.T8 and 123-21 for instance.
just on 152-4.S4
15M, 12.4, etc are ISR branches, while 15S or 12.2SR are 7600 branches.
On the 7200 you have the choice between the two, but they are fundamentally
Il 27/11/13 19:01, Lukas Tribus ha scritto:
15M, 12.4, etc are ISR branches, while 15S or 12.2SR are 7600
branches. On the 7200 you have the choice between the two, but they
are fundamentally different
thank you, exactly what I meant by saying different versions
--
antonio
Hello,
if I set the maxas-limit, whenever the router receives a longer path, it
complains:
020250: Nov 26 12:09:52: %BGP-6-MSGDUMP_LIMIT: unsupported or
mal-formatted message received from xx.xx.xxx.243:
007A 0200 1C18 67F5 0C16 C773
C412 2966
4011 2966
On (2013-11-26 12:16 +0100), Antonio Prado wrote:
if I set the maxas-limit, whenever the router receives a longer path, it
complains:
020250: Nov 26 12:09:52: %BGP-6-MSGDUMP_LIMIT: unsupported or
mal-formatted message received from xx.xx.xxx.243:
I'm guessing this might happen because
On Tuesday, November 26, 2013 10:11:20 PM Saku Ytti wrote:
Interestingly, I don't believe this behaviour could be
seen in IOS-XR or JunOS or such, since it's quite
untypical for userland process to start processing
packet before it's received. But IOS specifically has
dedicated TCP/IP
