[j-nsp] BGP error messages
lbarrios at NAVEGA.com
lbarrios at NAVEGA.com
Tue Sep 2 11:49:33 EDT 2008
Thanks for your answers .
I had a simlar problem too in other Routers m10i but that routers are
running the version 8.2 ( and i used this command to resolve it) . I
don´t know if the 7.3 version doesnt support the tcp-mss command, because
it doesnt appear in the CLI of my m7i in which i had the problem ( they
are running 7.3) .
Yesterday i disabled 6 bgp sessions ( that sessions was working OK, but
for troubleshooting i can disable it for one day ). i dont kwon why but
the session in which i had problem, now it has almost 16 hours in
ESTABLISHED state =0) . is there any limit for routes, memory , amount of
sessions o anything could be affected ? .
I was checking the routing engine and cfeb when the bgp sessions was
flaping
lbarrios at Juniper-Networks-XXXX# run show chassis routing-engine
Routing Engine status:
Temperature 26 degrees C / 78 degrees F
CPU temperature 24 degrees C / 75 degrees F
DRAM 256 MB
Memory utilization 37 percent
CPU utilization:
User 1 percent
Background 0 percent
Kernel 4 percent
Interrupt 0 percent
Idle 95 percent
Model RE-5.0
Serial ID 1000583967
Start time 2008-06-11 08:23:06 GMT
Uptime 82 days, 9 hours, 7 minutes, 13 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
[edit]
lbarrios at Juniper-Networks-NI# run show chassis cfeb
CFEB status:
State Online
Intake temperature 23 degrees C / 73 degrees F
Exhaust temperature 29 degrees C / 84 degrees F
CPU utilization 6 percent
Interrupt utilization 1 percent
Heap utilization 9 percent
Buffer utilization 25 percent
Total CPU DRAM 128 MB
Internet Processor II Version 2, Foundry IBM, Part
number 164
Start time: 2008-06-11 08:24:46 GMT
Uptime: 82 days, 9 hours, 5 minutes, 43
seconds
Now i have few bgp sessions aprox 10 session, And maybe 5000 routes .
Thanks a lot everyone for your help ...
luis
"Drechsel, Thiago (NSN - BR/Curitiba)" <thiago.drechsel at nsn.com>
09/02/08 07:31 AM
To
<lxg at luis.geezas.net>, <lbarrios at NAVEGA.com>,
<juniper-nsp at puck.nether.net>
cc
Subject
RE: [j-nsp] BGP error messages
Hi Luis.
If you want to be sure that MTU isn't your problem, try to configure
"tcp-mss". This will limit the TCP packet size. I had some similar
problems on the past.
neighbor 200.164.100.200 {
description GVS-MG;
tcp-mss 500;
}
Best Regards
Thiago Drechsel
-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of ext Luis
Ximenez Gomez
Sent: Monday, September 01, 2008 6:15 PM
To: lbarrios at NAVEGA.com; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP error messages
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. =
>
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Este correo electrónico puede contener información confidencial y protegida legalmente bajo secreto profesional. La información está dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no está autorizado. Si usted recibió este mensaje electrónico por error, infórmeselo al remitente y bórrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electrónico, 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 confesión y/o emisión y quede esta participación expresamente consignada en el mensaje. La divulgación pública de este correo electrónico, como así su copia, reproducción 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