Greetings list,
I'm dealing with the following issue:
Using an ASR9K (XR 4.3.4) I am modifying a prefix-set that is called in a
route-policy for outbound filtering on a peer to an upstream provider.
These modifications will increase my announcements by about 60 prefixes (based
on testing to lab peer) which the provider states should fall within their
allowed max-prefix range for our session, problem is everytime I commit the
change they drop the session and I recieve the lovely max-prefix message:
38.x.x.x Down - BGP Notification received, maximum number of prefixes reached
When I perform a "show bgp ipv4 unicast neighbor 38.x.x.x" I see the following
HEX data under the error code session:
Error Code: maximum number of prefixes reached
Notification data received:
01010000 0190
I "think" the last 16 bits is the value on the far end but I would like to
confirm that with somebody before I get on my high horse (as that value would
be incorrect from what was told to our team) and I can't seem to find a
definitive answer.
And if the last portion of the data is the max-prefix value on the receiver,
then what does the 01010000 represent? Do I have any options to decode this
data?
Or would a debug on the session during the tear-down give me more data that I
could use to determine the far end value?
Thanks in advance for any guidance !
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
