[j-nsp] BGP error messages
Kevin Oberman
oberman at es.net
Mon Sep 1 17:09:57 EDT 2008
> Date: Mon, 1 Sep 2008 14:48:45 -0600
> From: lbarrios at NAVEGA.com
> Sender: juniper-nsp-bounces at puck.nether.net
>
> Hello,
> Im running iBGP between two routers m7i. the session was working ok but
> since one week ago the sessios is resetting pretty frequently. im running
> the 7.3 Rel 1.5 version. Today the session is up during 3 minutes and the
> session gets down, ang 30 sec after the session gets up again.
>
>
> Sep 1 14:15:36 BGP SEND Notification code 4 (Hold Timer Expired Error)
> subcode 0 (unused)
> Sep 1 14:15:36 bgp_peer_close: closing peer 192.168.1.250 (Internal AS
> 65510), state is 6 (Established)
> Sep 1 14:15:36 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Established event HoldTime new state Idle
> Sep 1 14:15:36 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Idle event Start new state Active
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Active event ConnectRetry new state Connect
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Connect event Open new state OpenSent
> Sep 1 14:16:08 bgp_send: sending 55 bytes to 192.168.1.250 (Internal AS
> 65510)
> Sep 1 14:16:08
> Sep 1 14:16:08 BGP SEND 192.168.1.249+2329 -> 192.168.1.250+179
> Sep 1 14:16:08 BGP SEND message type 1 (Open) length 55
> Sep 1 14:16:08 BGP SEND version 4 as 65510 holdtime 180 id 192.168.1.249
> parmlen 26
> Sep 1 14:16:08 BGP SEND MP capability AFI=1, SAFI=128
> Sep 1 14:16:08 BGP SEND Refresh capability, code=128
> Sep 1 14:16:08 BGP SEND Refresh capability, code=2
> Sep 1 14:16:08 BGP SEND Restart capability, code=64, time=120, flags=
> Sep 1 14:16:08 BGP SEND Restart capability AFI=1, SAF=128,
> Flags=ForwardingSaved
> Sep 1 14:16:08
> Sep 1 14:16:08 BGP RECV 192.168.1.250+2424 -> 192.168.1.249+179
> Sep 1 14:16:08 BGP RECV message type 1 (Open) length 55
> Sep 1 14:16:08 BGP RECV version 4 as 65510 holdtime 180 id 192.168.1.250
> parmlen 26
> Sep 1 14:16:08 BGP RECV MP capability AFI=1, SAFI=128
> Sep 1 14:16:08 BGP RECV Refresh capability, code=128
> Sep 1 14:16:08 BGP RECV Refresh capability, code=2
> Sep 1 14:16:08 BGP RECV Restart capability, code=64, time=120, flags=
> Sep 1 14:16:08 BGP RECV Restart capability AFI=1, SAF=128,
> Flags=ForwardingSaved
> Sep 1 14:16:08 bgp_pp_recv: NOTIFICATION sent to 192.168.1.250 (Internal
> AS 65510): code 6 (Cease) subcode 7 (Connection collision resolution),
> Reason: dropping 192.168.1.250 (Internal AS 65510), connection collision
> prefers 192.168.1.250+2424 (proto)
> Sep 1 14:16:08 bgp_send: sending 21 bytes to 192.168.1.250 (Internal AS
> 65510)
> Sep 1 14:16:08
> Sep 1 14:16:08 BGP SEND 192.168.1.249+2329 -> 192.168.1.250+179
> Sep 1 14:16:08 BGP SEND message type 3 (Notification) length 21
> Sep 1 14:16:08 BGP SEND Notification code 6 (Cease) subcode 7 (Connection
> collision resolution)
> Sep 1 14:16:08 bgp_pp_recv: dropping 192.168.1.250 (Internal AS 65510),
> connection collision prefers 192.168.1.250+2424 (proto)
> Sep 1 14:16:08 bgp_peer_close: closing peer 192.168.1.250 (Internal AS
> 65510), state is 4 (OpenSent)
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state OpenSent event Stop new state Idle
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Idle event Start new state Active
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state Active event Open new state OpenSent
> Sep 1 14:16:08 bgp_send: sending 55 bytes to 192.168.1.250 (Internal AS
> 65510)
> Sep 1 14:16:08
> Sep 1 14:16:08 BGP SEND 192.168.1.249+179 -> 192.168.1.250+2424
> Sep 1 14:16:08 BGP SEND message type 1 (Open) length 55
> Sep 1 14:16:08 BGP SEND version 4 as 65510 holdtime 180 id 192.168.1.249
> parmlen 26
> Sep 1 14:16:08 BGP SEND MP capability AFI=1, SAFI=128
> Sep 1 14:16:08 BGP SEND Refresh capability, code=128
> Sep 1 14:16:08 BGP SEND Refresh capability, code=2
> Sep 1 14:16:08 BGP SEND Restart capability, code=64, time=120, flags=
> Sep 1 14:16:08 BGP SEND Restart capability AFI=1, SAF=128,
> Flags=ForwardingSaved
> Sep 1 14:16:08 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state OpenSent event RecvOpen new state OpenConfirm
> Sep 1 14:16:09 bgp_event: peer 192.168.1.250 (Internal AS 65510) old
> state OpenConfirm event RecvKeepAlive new state Established
>
>
>
> This are the logs in one of the routers. i was checking the links between
> the routers and its not look as congestion problem . have you any idea
> about the problem . The configuration en both router is very simple .
>
>
> lbarrios at JuniperNetworkPE_012_PA# show protocols bgp group INTERNAL
> type internal;
> local-address 192.168.1.249;
> family inet-vpn {
> unicast;
> }
> authentication-key "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"; ## SECRET-DATA
> neighbor 192.168.1.250 {
> description XXXXXX;
> hold-time 180;
> }
>
> i changed the hold-time just for troubleshooting . It had configuered as
> default 90 seg. im runnig LDP between the routers , but is a bgp issue.
>
> thanks
>
> luis
Looks like an MTU mis-match. Other things can cause this, but MTU is the
most common. The symptoms are BGP starts and may even roun for a while,
but when a packet that exceeds the path MTU comes along, it just hangs
in the output queue and keep-alives are then blocked which leads to the
session timeout you see.
Try a ping of full MTU size to check. (Don't forget to allow for 20
bytes TCP and 8 bytes ICMP header, so if you are not running jumbos it
would be:
ping addr size 1472 count 1
Something is likely being affected by the bytes in the MPLS header bytes
and lowering the MTU on family inet or raising it for the interface will
likely fix it. When things like MPLS and VLANS are used, especially in
combination or stacked (or when tunnels are used), this is fairly common.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20080901/9923ffb6/attachment.bin>
More information about the juniper-nsp
mailing list