[rbak-nsp] SE600 BGP Session drops

[Jim Tyrrell]

No issues with various 6.4.1.x versions.

I seem to recall a previous thread discussing SEOS and how it handles 
malformed BGP packets, ie they reset the BGP session rather than 
ignoring the packet.  Could it be that your ASR recieved a malformed 
packet from an upstream provider which was then sent to the SmartEdges?

Jim.

On 19/04/2012 08:32, Florian Lohoff wrote:
> Hi,
>
> has anyone else Full Routing on their Smartedges and saw BGP Session
> drop yesterday? We had BGP drops simultanous on all Smartedges.
> All of them are SE600 with 6.5.1.3p3, configured as a RR client:
>
>
> Apr 18 15:22:36.242: [0001]: %BGP-6-INFO: 172.30.0.4 DOWN - Notification sent
> Apr 18 15:22:36.242: [0001]: %BGP-6-INFO: 172.30.0.4 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=60001
> Apr 18 15:22:36.242: [0001]: %BGP-6-INFO: 172.30.0.3 DOWN - Notification sent
> Apr 18 15:22:36.242: [0001]: %BGP-6-INFO: 172.30.0.3 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=60002
> Apr 18 15:23:06.534: [0001]: %BGP-6-INFO: 172.30.0.4 UP
> Apr 18 15:23:07.019: [0001]: %BGP-6-INFO: 172.30.0.3 UP
> Apr 18 15:23:27.385: [0001]: %BGP-6-INFO: 172.30.0.3 DOWN - Notification sent
> Apr 18 15:23:27.386: [0001]: %BGP-6-INFO: 172.30.0.3 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=7760
> Apr 18 15:23:30.583: [0001]: %BGP-6-INFO: 172.30.0.4 DOWN - Notification sent
> Apr 18 15:23:30.583: [0001]: %BGP-6-INFO: 172.30.0.4 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=7985
> Apr 18 15:23:49.575: [0001]: %BGP-6-INFO: 172.30.0.3 UP
> Apr 18 15:24:01.185: [0001]: %BGP-6-INFO: 172.30.0.4 UP
> Apr 18 15:24:04.581: [0001]: %BGP-6-INFO: 172.30.0.3 DOWN - Notification sent
> Apr 18 15:24:04.581: [0001]: %BGP-6-INFO: 172.30.0.3 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=7761
> Apr 18 15:24:18.310: [0001]: %BGP-6-INFO: 172.30.0.4 DOWN - Notification sent
> Apr 18 15:24:18.310: [0001]: %BGP-6-INFO: 172.30.0.4 send NOTIFICATION: 3/9 (update: optional attribute error) with 11 byte data. mxReadMs=7957
> Apr 18 15:24:37.570: [0001]: %BGP-6-INFO: 172.30.0.3 UP
> Apr 18 15:24:46.318: [0001]: %BGP-6-INFO: 172.30.0.4 UP
>
> All times are UTC.
>
> The Route Reflector (Cisco ASR9k) shows:
>
> RP/0/RSP0/CPU0:Apr 18 15:22:36.381 : bgp[1047]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.30.0.8 Down - BGP Notification received, unsupported option specified (VRF: default)
>
> On the Smartedge the "sh bgp malform update" shows the packets:
>
> Apr 18 15:24:18 Malformed UPDATE msg (nbr 172.30.0.4, context 0x40080001, 98 bytes, repeated 0 times, reason: Invalid msg) -
>   ffff ffff ffff ffff ffff ffff ffff ffff 0062 0200 0000 4740 0101 0040 0212 0204 0000 1b1b 0000 1a6a 0000 0cc5 0000 510a 4003 04ac 1e00 0140 0504 0000 0064 c007 0800 0
> 000 0000 0000 00c0 0804 e009 00c8 800a 0459 bbd0 0480 0904 ac1e 0001 1859 1f30
>
> although i havent had a try to decode it.
>
> Flo
>
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20120419/b294b7ca/attachment-0001.html>