cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2894
Views
0
Helpful
1
Replies

BGP stuck in opensent state

C P
Level 1
Level 1

HELP! Been looking at this problem all day. Have a simple BGP config on my end (below). I have no control on the other end. Recently upgraded from 2811 to 2911.  IOS: c2900-universalk9-mz.SPA.151-4.M7.bin  Configs on old and new routers exactly the same.

Called our ISP. They see the same debug logs, but have no clue to fix. I can ping across fine. No MTU issues. Move connections back to old 2811 BGP comes up no problem.

 

!
interface Serial0/0/0
 ip address X.X.X.86 255.255.255.252
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 service-module t1 fdl ansi
 no cdp enable
!
router bgp 65000
 bgp log-neighbor-changes
 network Y.Y.Y.0
 network Y.Y.Y.16 mask 255.255.255.240
 neighbor X.X.X.85 remote-as 2
 neighbor X.X.X.85 password 7 06252C1268715E3C5139

 

debug

Nov  5 11:07:05.493: BGP: Selected new router ID Y.Y.Y.17 for scope global
Nov  5 11:07:05.537: BGP: Applying map to find origin for Y.Y.Y.16/28
Nov  5 11:07:05.541: BGP: Applying map to find origin for Y.Y.Y.16/28
Nov  5 11:07:05.541: BGP: Applying map to find origin for Y.Y.Y.16/28
Nov  5 11:07:05.549: BGP: nbr global X.X.X.85 Active open failed - can't get active topologies
Nov  5 11:07:05.549: BGP: nbr global X.X.X.85 Open active delayed 11264ms (35000ms max, 60% jitter)
Nov  5 11:07:06.457: BGP: X.X.X.85 passive open to X.X.X.86
Nov  5 11:07:06.461: BGP: X.X.X.85 passive went from Idle to Connect
Nov  5 11:07:06.461: BGP: ses global X.X.X.85 (0x307CA074:0) pas Setting open delay timer to 60 seconds.
Nov  5 11:07:06.461: BGP: ses global X.X.X.85 (0x307CA074:0) pas read request no-op
Nov  5 11:07:06.521: BGP: Sched timer-wheel running slow by 8 ticks
Nov  5 11:07:16.761: BGP: X.X.X.85 active went from Idle to Active
Nov  5 11:07:16.761: BGP: X.X.X.85 open active, local address X.X.X.86
Nov  5 11:07:16.773: BGP: ses global X.X.X.85 (0x30B937F4:0) act Adding topology IPv4 Unicast:base
Nov  5 11:07:16.773: BGP: ses global X.X.X.85 (0x30B937F4:0) act Send OPEN
Nov  5 11:07:16.773: BGP: X.X.X.85 active went from Active to OpenSent
Nov  5 11:07:16.773: BGP: X.X.X.85 active sending OPEN, version 4, my as: 65000, holdtime 180 seconds, ID CD464511
Nov  5 11:07:16.785: BGP: X.X.X.85 active rcv message type 3, length (excl. header) 5
Nov  5 11:07:16.785: %BGP-3-NOTIFICATION: received from neighbor X.X.X.85 active 2/8 (no supported AFI/SAFI) 3 bytes 000000
Nov  5 11:07:16.785: BGP: ses global X.X.X.85 (0x30B937F4:0) act Receive NOTIFICATION 2/8 (no supported AFI/SAFI) 3 bytes 000000
Nov  5 11:07:16.785: BGP: ses global X.X.X.85 (0x30B937F4:0) act Reset (BGP Notification received).
Nov  5 11:07:16.785: BGP: X.X.X.85 active went from OpenSent to Closing
Nov  5 11:07:16.785: BGP: nbr_topo global X.X.X.85 IPv4 Unicast:base (0x30B937F4:0) NSF delete stale NSF not active
Nov  5 11:07:16.785: BGP: nbr_topo global X.X.X.85 IPv4 Unicast:base (0x30B937F4:0) NSF no stale paths state is NSF not active
Nov  5 11:07:16.785: BGP: nbr_topo global X.X.X.85 IPv4 Unicast:base (0x30B937F4:0) Resetting ALL counters.
Nov  5 11:07:16.785: BGP: X.X.X.85 active closing
Nov  5 11:07:16.785: BGP: ses global X.X.X.85 (0x30B937F4:0) act Session close and reset neighbor X.X.X.85 topostate
Nov  5 11:07:16.785: BGP: nbr_topo global X.X.X.85 IPv4 Unicast:base (0x30B937F4:0) Resetting ALL counters.
Nov  5 11:07:16.785: BGP: X.X.X.85 active went from Closing to Idle
Nov  5 11:07:16.785: %BGP_SESSION-5-ADJCHANGE: neighbor X.X.X.85 IPv4 Unicast topology base removed from session  BGP Notification received
Nov  5 11:07:16.785: BGP: ses global X.X.X.85 (0x30B937F4:0) act Removed topology IPv4 Unicast:base
Nov  5 11:07:16.785: BGP: ses global X.X.X.85 (0x30B937F4:0) act Removed last topology
Nov  5 11:07:16.785: BGP: nbr global X.X.X.85 Active open failed - existing passive session
Nov  5 11:07:16.785: BGP: nbr global X.X.X.85 Active open failed - existing passive session
 

1 Reply 1

John Blakley
VIP Alumni
VIP Alumni

From what I'm finding, AFI 2 is IPv6. This seems like it's expecting IPv6:


Nov  5 11:07:16.785: %BGP-3-NOTIFICATION: received from neighbor X.X.X.85 active 2/8 (no supported AFI/SAFI) 3 bytes 000000

I'm also seeing that SAFI 8 is multicast:

http://www.iana.org/assignments/safi-namespace/safi-namespace.xhtml

If this is the case, the settings that you have above simply wouldn't work. I would contact the ISP to see what your peer is running.

http://routing-bits.com/2009/11/26/output-101-bgp-afisafi/

 

HTH,

John

HTH, John *** Please rate all useful posts ***