Re: LDP goes down every 3mins

Is this from GNS3 ? If so, I run into this a lot and I haven't figured out how to stop it, just something I deal with while I'm testing something.

Regards,
 Joe Sanchez

( please excuse the brevity of this email as it was sent via a mobile device. Please excuse misspelled words or sentence structure.)

> On Mar 10, 2014, at 10:31 AM, Darlington Ngaiso <ngaissod_at_gmail.com> wrote:
>
> Hi Guys
>
> I have an Issue below and would be glad if you could assist.
>
> nam-wdk-tel-ppe02#
> 299740: *Mar 10 17:04:49: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 1):
> interrupted--recovery pending
> 299741: *Mar 10 17:04:49: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (0)
> is DOWN (Session KeepAlive Timer expired)
>
> 299742: *Mar 10 17:04:53: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 2):
> starting graceful recovery
> 299743: *Mar 10 17:04:53: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (2)
> is UP
>
> 299744: *Mar 10 17:06:30: %BGP-3-NOTIFICATION: sent to neighbor
> 41.218.71.73 passive 6/0 (cease) 0 bytes
>
> 299745: *Mar 10 17:07:53: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 2):
> completed graceful recovery
> 299746: *Mar 10 17:07:53: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 2):
> interrupted--recovery pending
> 299747: *Mar 10 17:07:53: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (0)
> is DOWN (Session KeepAlive Timer expired)
> 299748: *Mar 10 17:07:56: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 1):
> starting graceful recovery
> 299749: *Mar 10 17:07:56: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (1)
> is UP
> 299750: *Mar 10 17:09:02: %BGP-3-NOTIFICATION: sent to neighbor
> 41.218.71.73 passive 6/0 (cease) 0 bytes
> 299751: *Mar 10 17:10:56: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 1):
> completed graceful recovery
> 299752: *Mar 10 17:10:56: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 1):
> interrupted--recovery pending
> 299753: *Mar 10 17:10:56: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (0)
> is DOWN (Session KeepAlive Timer expired)
>
> 299754: *Mar 10 17:11:01: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 4):
> starting graceful recovery
> 299755: *Mar 10 17:11:01: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (4)
> is UP
> 299756: *Mar 10 17:11:35: %BGP-3-NOTIFICATION: sent to neighbor
> 41.218.71.73 passive 6/0 (cease) 0 bytes
> 299757: *Mar 10 17:14:01: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 4):
> completed graceful recovery
> 299758: *Mar 10 17:14:01: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 4):
> interrupted--recovery pending
> 299759: *Mar 10 17:14:01: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (0)
> is DOWN (Session KeepAlive Timer expired)
>
> 299760: *Mar 10 17:14:04: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 2):
> starting graceful recovery
> 299761: *Mar 10 17:14:04: %LDP-5-NBRCHG: LDP Neighbor 10.117.246.141:0 (2)
> is UP
> 299762: *Mar 10 17:14:04: %LDP-5-GR: GR session 10.117.246.141:0 (inst. 2):
> completed graceful recovery
>
>
> When I ping from Side A
>
> I get the pattern below
>
> ping 10.214.0.76 re 100 size 1496 df
> Type escape sequence to abort.
> Sending 100, 1496-byte ICMP Echos to 10.214.0.76, timeout is 2 seconds:
> Packet sent with the DF bit set
> !!!!.!!!!!!.!!!!!!.!!!!!!!.!!!!!!.!!!!!!.!!!!!!.!!!!!!.!!!!!!.!!!!!!.!
> !!!!!.!!!!!!.!!!!!!.!!!!!.!!!!
> Success rate is 86 percent (86/100), round-trip min/avg/max = 168/170/180 ms
>
> But the ping from Side B is going through fine
>
> ping 10.214.0.77 re 100 size 1496 df
>
> Type escape sequence to abort.
> Sending 100, 1496-byte ICMP Echos to 10.214.0.77, timeout is 2 seconds:
> Packet sent with the DF bit set
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> Success rate is 100 percent (100/100), round-trip min/avg/max = 168/170/184
> ms
>
> A#sh mpls ldp neighbor 10.117.246.141 detail
> Peer LDP Ident: 10.117.246.141:0; Local LDP Ident 10.214.57.142:0
> TCP connection: 10.117.246.141.646 - 10.214.57.142.36408
> Password: not required, none, in use
> State: Oper; *Msgs sent/rcvd: 1424/2;* Downstream; Last TIB rev
> sent 77971
> Up time: 00:00:50; UID: 19327; Peer Id 0;
> LDP discovery sources:
> GigabitEthernet0/1.304; Src IP addr: 10.214.0.76
> holdtime: 15000 ms, hello interval: 5000 ms
> Targeted Hello 10.214.57.142 -> 10.117.246.141, active, passive;
> holdtime: infinite, hello interval: 10000 ms
> Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estab
> Clients: Graceful Restart
> LDP Session Protection enabled, state: Ready
> duration: 86400 seconds
> Capabilities Sent:
> [ICCP (type 0x0405) MajVer 1 MinVer 0]
> [Dynamic Announcement (0x0506)]
> [Typed Wildcard (0x050B)]
> Capabilities Received:
> [ICCP (type 0x0405) MajVer 1 MinVer 0]
> [Dynamic Announcement (0x0506)]
> A#
>
>
>
> A#sh tcp brie | in 10.117.246.141
> 71310EA4 10.214.57.142.11539 10.117.246.141.646 FINWAIT2
> 712AF614 10.214.57.142.15104 10.117.246.141.646 FINWAIT2
> 69F87444 10.214.57.142.25966 10.117.246.141.646 FINWAIT2
> 69B3C8C0 10.214.57.142.36408 10.117.246.141.646 ESTAB
> A#
>
>
> Below is the config on the interface
>
>
> interface GigabitEthernet0/1.304
> encapsulation dot1Q 304
> ip address 10.214.0.77 255.255.255.254
> ip ospf network point-to-point
> ip ospf cost 10000
> ip ospf mtu-ignore
> mpls label protocol ldp
> mpls ip
>
>
> 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
Received on Mon Mar 10 2014 - 11:49:59 ART