On Wed, Aug 23, 2006 at 06:48:52AM -0700, bablam wrote:
> Good morning,
> Being that I cannot find a list specifically for openbgp I am
> going to send it here (to the mics@ list), if anyone knows of a list
> more suited to openbgp troubleshooting please let me know.
misc@ is the right place.
> The issues is dropped neighborships between IBGP peers every 1-2
> minutes. One host is a PFsense (FC1) firewall running openbgp version
> 3.72 and the other a Fedora Core 5 box running Quagga 0.98.6. The
> configs and debugs are below, anyone seen wierdness like this before?
> This is not a complex config, looks like an undocumented feature.
> Thanks all.
>
> Wade B
>
> openbgp config
> --------------------------------------------------------------------------------------
> #macros
> peer2="192.168.12.130"
> myip="192.168.12.129"
>
> neighbor $peer2 {
> remote-as 65001
> announce all
> holdtime 6
Why do you set holdtime to 6?
> }
>
....
> openbgp debug
> bgpd -dv
> peer2 = "192.168.12.130"
> myip = "192.168.12.129"
> startup
> route decision engine ready
> listening on 192.168.12.129
> session engine ready
> neighbor 192.168.12.130: state change None -> Idle, reason: None
> neighbor 192.168.12.130: state change Idle -> Connect, reason: Start
> neighbor 192.168.12.130: state change Connect -> OpenSent, reason:
> Connection opened
> neighbor 192.168.12.130: state change OpenSent -> Active, reason:
> Connection closed
> neighbor 192.168.12.130: state change Active -> OpenSent, reason:
> Connection opened
> neighbor 192.168.12.130: state change OpenSent -> OpenConfirm, reason:
> OPEN message received
> neighbor 192.168.12.130: state change OpenConfirm -> Established,
> reason: KEEPALIVE message received
> neighbor 192.168.12.130 (AS65001) update 192.168.11.0/25/134726144
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.12.128/25/134726272
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.12.0/25/134726272
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.11.128/25/134726272
> 192.168.12.130
> nexthop 192.168.12.130 now valid: directly connected
> neighbor 192.168.12.130: state change Established -> Idle, reason:
> HoldTimer expired
This is the cause why the connection goes down. For some reason the hold
timer triggered. Check with bgpctl show nei 192.168.12.130 timer if the
holdtime and keepalive timer are correct.
> Connection attempt from neighbor 192.168.12.130 while session is in state
> Idle
> neighbor 192.168.12.130: state change Idle -> Connect, reason: Start
> neighbor 192.168.12.130: state change Connect -> OpenSent, reason:
> Connection opened
> neighbor 192.168.12.130: state change OpenSent -> OpenConfirm, reason:
> OPEN message received
> neighbor 192.168.12.130: state change OpenConfirm -> Established,
> reason: KEEPALIVE message received
> neighbor 192.168.12.130 (AS65001) update 192.168.11.0/25/134726144
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.12.128/25/134726272
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.12.0/25/134726272
> 192.168.12.130
> neighbor 192.168.12.130 (AS65001) update 192.168.11.128/25/134726272
> 192.168.12.130
> nexthop 192.168.12.130 now valid: directly connected
> neighbor 192.168.12.130: state change Established -> Idle, reason:
> ConnectRetryTimer expired
This one here is a bit strange. Why is the ConnectRetryTimer still running
when the connection is established.
Please send the output of "bgpctl show nei 192.168.12.130 timer"
and what version of OpenBGPD are you running (there is no such thing as
3.72). Check if it is not possible to install a more current version.
--
:wq Claudio
