[rbak-nsp] SEOS 6.4.1.1 and iBGP problem

[Marcin Kuczera]

Blake Willis wrote:
> Hi Marcin,
> 
> Have a look at 'show bgp neighbor' for the IP of the bouncing neighbor 
> on both boxes.  If the address families (& some capabilies) don't match 
> or aren't supported by one of the neighbors, the session might not come 
> up.  You should see something like this on both sides (this is from one 
> of my boxes):
> 
>   CapSent: refresh, 4byteAS, unicast, vpn, restart
>   CapRcvd: refresh, 4byteAS, unicast, vpn, restart (time 120, flags 0x0)
> 
>   Address family: ipv4 unicast
>   Address family: ipv4 vpn
> 
> As a first guess, you might try explicitly disabling the IPv6 AFI for 
> the IPv4 neighbor on the new box running 6.4:
> 
> neighbor 195.66.73.253 internal
>  no address-family ipv6 unicast
> 
> You can also use 'show bgp neighbor' to see malformed messages, resets, 
> etc.
> 
> Once you figure out which capability the old SEOS doesn't like, you may 
> be able to disable it on the new box with the "send" or "address-family" 
> config statements. Perhaps the new SEOS has a "capability" knob as well?

this looks like some other problem..

[bgp1]se100-test#show bgp neighbor 195.66.73.253
BGP neighbor: 195.66.73.253, remote AS: 13000, internal link
   Version: 4, router identifier: 91.195.159.133
   State: Idle for 00:00:08
   Description: iBGP RedBack1 <=> RedBack2
   Last read 00:00:08, last send 00:00:08
   Hold time: configured 180, negotiated 0
   Keepalive time: configured 60, negotiated 0
   Local restart timer 120 sec, stale route retain timer 180 sec
   Received restart timer 0 sec, flag 0x0
   Minimum time between advertisement runs: 5 secs
   Source (local) IP address: 0.0.0.0
   Received messages: 0 (0 bytes), notifications: 0, in queue: 0
   Sent messages: 0 (0 bytes), notifications: 4222, out queue: 0
   Last active open: 23:22:06, reason: down/prefix_limst/dampen/deleted
   Last passive open: 00:03:06, reason: down/prefix_limst/dampen/deleted
   Reset count: 4222, last reset time: 00:00:08, reset reason: 
Notification sent (update: optional attribute error)

   Address family: ipv4 unicast
     BGP table version: 88696138, neighbor version: 0
     Routes: rcvd 0, imported 0, active 0, history 0, dampend 0, sent 0
[bgp1]se100-test#show bgp neighbor 195.66.73.253 malform update
Dump logged malformed UPDATE messages for ??? (1 total entries):
Sep 27 14:09:48 Malformed UPDATE msg (nbr 195.66.73.253, context 
0x40080002, 120 bytes, repeated 4221 times, reason: Invalid msg) -
  ffff ffff ffff ffff ffff ffff ffff ffff 0078 0200 0000 4540 0101 02c0 
0708 0000 611f 0000 0000 5002 000e 0203 0000 6094 0000 3c34 0000 611f 4
003 04c1 6f26 6180 0404 0000 0000 4005 0400 0000 c8c0 080c 0000 3b41 
0000 51cc 220a 220a 1829 b200 1629 c404 1629 c408 1629 c40c 1629 c410 162
9 c418 1729 c424
[bgp1]se100-test#





Is there any possibility to ignore malformed updates instead of dropping 
down whole session ?

Regards,
Marcin