Re: OT: BGP failing to establish a peer. Any ideas?

Dave,

The other side is a BNT switch - what is the OS version it runs? Blade OS is
probably the most buggy piece of networking software that you may have seen
in your life (nothing against Bay Network and Nortel, but still ;) They are
getting better, though. Make sure the OS version is at least 6.6.100.16, say
your prayers otherwise. Unfortunately, the debugging capabilities on Blade
OS are less than limited, so your only hope for information Cisco side. The
TCP session is established (transport is OK) and your side is advertising
NSF capability - the BNT side may not support caps and simply terminate the
session upon reception of the OPEN message (per the original BGP standard).
Try reducing the amount of parameters on your side to a minimum and see if
the OPEN exchange finishes successfully .

PS
Marko, for the keepalive, the BGP speakers normally negotiate the minimum
value advertised as the common denominator. I haven't seen that causing any
problems to BNT switches.. yet ;)

-- 
Petr Lapukhov, petr_at_INE.com
CCIE #16379 (R&S/Security/SP/Voice)
CCDE #20100007
Internetwork Expert, Inc.
http://www.INE.com
Toll Free: 877-224-8987
Outside US: 775-826-4344
2011/8/5 Dave Serra <maybeedave_at_yahoo.com>
> Hey Guys,
>
> I am running into an issue with bringing up a partner who is using
> a "blade networks" switch and I am using a Cisco 4900M.  Debugs show that
> the
> session is moving from idle to active and then to Open and finally to
> OpenConfirm before closing.  So I don't think this is a layer 3 check ttl
> (update source, TTL, etc...) though I could be wrong.  From looking at the
> debug below, can anyone tell what is happening?  I've looked at RFC 1105
> but
> it says nothing about the "cease 0" message I am getting in the debug.
>
> I
> tried setting the timers to defaul (60 keepalive - 180 hold down) and
> removing
> soft-reconfiguration inbound but no luck.  And I did clear the bgp neighbor
> with the "clear ip bgp 10.255.0.10" command after each change
>
> Below is the
> config and debug.  Any help is MUCH appreciated!
>
> router bgp 1
>  neighbor
> 10.255.0.10 remote-as 2
>  neighbor 10.255.0.10 timers 3 9
>  neighbor
> 10.255.0.10 soft-reconfiguration inbound
>
> Aug  5 21:48:09.873: BGP:
> 10.255.0.10 went from Idle to Active
> Aug  5 21:48:09.873: BGP: 10.255.0.10
> open active, local address 10.255.0.9
> Aug  5 21:48:09.873: BGP: 10.255.0.10
> read request no-op
> Aug  5 21:48:09.873: BGPNSF: Building graceful restart
> capability for 10.255.0.10
> Aug  5 21:48:09.873: BGP: 10.255.0.10 went from
> Active to OpenSent
> Aug  5 21:48:09.873: BGP: 10.255.0.10 sending OPEN,
> version 4, my as: 1, holdtime 9 seconds
> Aug  5 21:48:09.873: BGP: 10.255.0.10
> send message type 1, length (incl. header) 55
> Aug  5 21:48:09.873: BGP:
> 10.255.0.10 rcv message type 1, length (excl. header) 10
> Aug  5 21:48:09.873:
> BGP: 10.255.0.10 rcv OPEN, version 4, holdtime 180 seconds
> Aug  5
> 21:48:09.873: BGP: 10.255.0.10 rcv OPEN w/ OPTION parameter len: 0
> BGP:
> 10.255.0.10 rcvd OPEN w/ remote AS 2
> Aug  5 21:48:09.873: BGP: 10.255.0.10
> went from OpenSent to OpenConfirm
> Aug  5 21:48:09.873: BGP: 10.255.0.10 rcv
> message type 3, length (excl. header) 2
> Aug  5 21:48:09.873:
> %BGP-3-NOTIFICATION: received from neighbor 10.255.0.10 6/0 (cease) 0 bytes
> Aug  5 21:48:09.873: BGP: 10.255.0.10 went from OpenConfirm to Closing
> Aug  5
> 21:48:09.873: BGPNSF state: 10.255.0.10 went from nsf_not_active to
> nsf_not_active
> Aug  5 21:48:09.873: BGP: 10.255.0.10 went from Closing to
> Idle
> Aug  5 21:48:09.873: BGP: 10.255.0.10 closing
>
> Make a small loan, Make a
> big difference - Kiva.org
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net