05-24-2019 08:56 AM
when setting the maxas-limit I seem to be running into a bug?, not sure, %BGP-6-MSGDUMP_LIMIT: unsupported or mal-formatted message received. Has anyone else obverse this on ASR1001-x IOS 16(everest) ? It looks cosmetic but I cant seem to stop it. I tried neighbor x.x.x.x dont-capability-negotiate but that didnt seem to work. The error is triggered when you receive a prefix with AS path longer the maxas-limit configured.
TIA
paul
05-24-2019 09:05 AM
Hello Paul,
other people have reported a lot of log messages after enabling the feature
see the following thread
So it might not be a bug, even cosmetic but a wanted behaviour.
Hope to help
Giuseppe
05-24-2019 09:42 AM
I agree its probably a bug, I should see be able to see that a prefix was rejected like on other platforms but not the complaint
May 24 11:51:04: %BGP-6-MSGDUMP_LIMIT: unsupported or mal-formatted message received from x.x.x.x:
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00BE 0200 0000 A340 0101 0040 028A 0222
0000 7D91 0000 00AE 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9
0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9
0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9 0000 21F9
0000 21F9 0000 21F9 0000 234E 0000 234E 0000 234E 0000 234E 0000 234E 0000 234E
0000 234E 0000 234E 4003 0483 6D87 01C0 0808 00AE 526D 00AE 55FC 136D 6BE0
May 24 11:48:03: %BGP-6-ASPATH: Long AS path .... 8697 8697 8697 8697 8697 8697 8697 8697............
Paul
05-24-2019 10:05 AM - edited 05-24-2019 10:09 AM
Hello Paul,
yes I agree you should see only the log message
>> May 24 11:48:03: %BGP-6-ASPATH: Long AS path .... 8697 8697 8697 8697 8697 8697 8697 8697.....
The previous lines are misleading and confusing as they make you think of a true issue with the neighbor.
By the way, when receiving a true malformed message a BGP speaker could send a NOTIFICATION message to close the session and the session would flap.
Hope to help
Giuseppe
05-24-2019 10:44 AM
I thought so, good to be assured thought. Maybe cisco will patch that up.
thanks again,
Paul
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide