[j-nsp] BGP error messages
Luis Ximenez Gomez
lxg at luis.geezas.net
Mon Sep 1 17:14:32 EDT 2008
Hi Luis,
Your problem seems to be derived from connection collisions:
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)
Long story, but basically your router is trying to take the active & passive
roles. For some reason (maybe a keepalive missing?) one peer sends a
notification message and the session is closed immediately, trigering the
finite state machine to start all over again negotiating a new session
-which is what your logs show
I wonder if both peers are running the same JUNOS version. Nevertheless I'm
almost certain that if you set the offender peer session as "passive" your
problem will not reappear
Hope it helps,
Luis
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> lbarrios at NAVEGA.com
> Sent: lunes, 01 de septiembre de 2008 22:49
> To: juniper-nsp at puck.nether.net
> Cc: lbarrios at NAVEGA.com
> Subject: [j-nsp] BGP error messages
>
> 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
>
>
> thanks for your help.
>
>
> Este correo electrsnico puede contener informacisn
> confidencial y protegida legalmente bajo secreto profesional.
> La informacisn esta dirigida solamente a la persona o entidad
> indicada como destinatario y su acceso por cualquier otra
> persona no esta autorizado. Si usted recibis este mensaje
> electrsnico por error, infsrmeselo al remitente y bsrrelo.
> Aclaramos que los conceptos y opiniones comprendidos en este
> correo electrsnico, deben atribuirse exclusivamente a su
> autor y no deben entenderse como necesariamente coincidentes
> con las de NAVEGA.COM, S.A. y en consecuencia, absolutamente
> ajenos a la responsabilidad de sus directores y ejecutivos,
> en tanto no hayan participado de su confesisn y/o emisisn y
> quede esta participacisn expresamente consignada en el
> mensaje. La divulgacisn pzblica de este correo electrsnico,
> como asm su copia, reproduccisn total o parcial queda
> prohibida, dando lugar en caso de inobservancia de esta todas
> las acciones legales que pudiesen corresponder. Muchas Gracias. =
>
More information about the juniper-nsp
mailing list