[j-nsp] iBGP problems after upgrading to 8.5

[Campbell, Alex]

Hi guys,

Has anyone else run into issues with iBGP sessions not coming up after
upgrading to 8.5?

We upgraded one of our J4350s from 8.4R3.3 to 8.5R2.1.  After rebooting,
the box's iBGP session wouldn't come back up.  I tried rebooting again,
taking out MD5 auth, and re-entering the config for the group protocols
bgp.

I've got JTAC looking into the problem but I was wondering if anyone
here has seen similar issues.  The iBGP session runs across a directly
connected copper ethernet interface to lo0 on another J4350 running
8.3R2.8.

This is what we see from "show bgp summ":

x at border2> show bgp summary
Groups: 3 Peers: 3 Down peers: 1
Table          Tot Paths  Act Paths Suppressed    History Damp State
Pending
inet.0            253485     250875          0          0          0
0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn
State|#Active/Received/Damped...
x.x.x.1    XXXXX          0          0       0       0          40
Connect
y.y.y.y    YYYYY      44476         89       0       0       38:06
248631/251190/0      0/0/0
z.z.z.z    ZZZZZ        462         89       0       0       38:35
2244/2295/0          0/0/0

The config is very simple:

(on the 8.3 side)

x at border1# show protocols bgp
traceoptions {
    file log-bgp size 1m files 5;
    flag open;
}
log-updown;
remove-private;
group ibgp-XXXXX {
    type internal;
    local-address x.x.x.1;
    advertise-inactive;
    export announce-to-XXXXX;
    peer-as XXXXX;
    multipath multiple-as;
    neighbor x.x.x.2;
}

(on the 8.5 side)

x at border2# show protocols bgp
traceoptions {
    file log-bgp size 1m files 5;
    flag open;
}
log-updown;
remove-private;
group ibgp-XXXXX {
    local-address x.x.x.2;
    advertise-inactive;
    export announce-to-XXXXX;
    peer-as XXXXX;
    multipath multiple-as;
    neighbor x.x.x.1;
}

When I clear the session on each side and watch log-bgp, this is what I
see:

(from the 8.3 side)

Apr 21 07:56:18.777883 bgp_send: sending 21 bytes to x.x.x.2 (Internal
AS XXXXX) 
Apr 21 07:56:18.777896 
Apr 21 07:56:18.777896 BGP SEND x.x.x.1 -> x.x.x.2+179 
Apr 21 07:56:18.777911 BGP SEND message type 3 (Notification) length 21 
Apr 21 07:56:18.777949 bgp_send: sending 21 bytes to x.x.x.2 (Internal
AS XXXXX) failed: Socket is not connected

(from the 8.5 side)

Apr 21 07:36:53.953869 bgp_send: sending 21 bytes to x.x.x.1 (Internal
AS XXXXX) 
Apr 21 07:36:53.953881 
Apr 21 07:36:53.953881 BGP SEND (null) -> x.x.x.1 
Apr 21 07:36:53.953894 BGP SEND message type 3 (Notification) length 21 
Apr 21 07:36:53.953925 bgp_send: sending 21 bytes to x.x.x.1 (Internal
AS XXXXX) failed: Bad file descriptor


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________