[rbak-nsp] Today I have 40 min down bgp peer AS31133 (magistral megafon)

[Marcin Kuczera]

Соловьёв Роман wrote:
> in bgp routes I see all destinations with 0.0.0.0 NEXTHOP
> 
> Has anybody have some problems with SE100?

I suppose that you have to go up to SEOS 11.x
That is well known issue (not a bug) with implementation of strict RFC 
specification. In 11.x some security recommendations (idiot proof rules) 
are already added.

Regards,
Marcin

> 
> as it was half year ago?
> SE100 wrote
>>> 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
> 
> 
> 
> 
>