Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

LDP - URGENT

Hi ALL,

Please help me for following issues. i hv mpls network and my P router that is GSR LDP was getting up and down. can any):

body tell me the why LDP was down.

following is the log file for P router.

Jan 19 15:06:23: %GRPGE-6-LINE_STATE: Interface GigabitEthernet2/0: Line state OK

Jan 19 15:06:25: %LINK-3-UPDOWN: Interface GigabitEthernet2/0, changed state to up

Jan 19 15:06:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0, changed state to up

Jan 19 15:06:34: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Jan 19 15:07:10: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Feb 5 17:38:03: %GRPGE-6-SYNC_LOSS: Interface GigabitEthernet2/0: Loss of Sync

Feb 5 17:38:03: %GRPGE-6-RX_LOS: Interface GigabitEthernet2/0: Detected RX Loss of Signal

Feb 5 17:38:04: %GRPGE-6-GBIC_TX_FAULT: Interface GigabitEthernet2/0: GBIC TX Fault OK

Feb 5 17:38:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/0, changed state to down

Feb 5 17:38:05: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from 2WAY to DOWN, Neighbor Down: Interface down or detached

Feb 5 17:38:05: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Feb 5 17:38:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0, changed state to down

Feb 5 18:38:07: %GRPGE-6-SYNC_LOSS: Interface GigabitEthernet2/0: Sync OK

Feb 5 18:38:07: %GRPGE-6-LINE_STATE: Interface GigabitEthernet2/0: Line state OK

Feb

Mar 19 19:27:23: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:30:43: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:30:50: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:32:28: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:32:35: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:33:33: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:35:13: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:35:15: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:36:35: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:36:37: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:38:14: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:38:21: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:40:04: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:40:08: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:40:25: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:41:32: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:41:51: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:42:06: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:42:18: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:43:18: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:43:21: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:46:13: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:48:28: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:50:29: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:50:39: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:51:42: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is DOWN

Mar 19 19:51:46: %LDP-5-NBRCHG: LDP Neighbor 202.183.64.5:0 is UP

Mar 19 19:52:43: %OSPF-5-ADJCHG: Process 10, Nbr 202.183.64.5 on GigabitEthernet2/0 from LOADING to FULL, Loading Done

Mar 19 19:

pls go threw the attachment. i am sending u the logs of P router

rgds

ciscobuddy

5 REPLIES
Bronze

Re: LDP - URGENT

G2/0 link is flapping due to which ur Ospf/Ldp Adj with nbr 202.183.64.5 is flapping.

Pls check the Link.

Mar 19 21:42:48: %GRPGE-6-SYNC_LOSS: Interface GigabitEthernet2/0: Loss of Sync

Mar 19 21:42:48: %GRPGE-6-RX_LOS: Interface GigabitEthernet2/0: Detected RX Loss of Signal

New Member

Re: LDP - URGENT

hi aditya,

i think u hv forgot to send the link

pls send it

rgds,

Bronze

Re: LDP - URGENT

See the reason ur failing to have LDP Nbr Adj with 202.183.64.5 is bcoz ur gig2/0 link is flapping.

1. Is the ldp neighbour 202.183.64.5 connected thro intf g2/0.

2. Check the intf g2/0.

3. sh mpls ldp dis .

4. Check if ur able to reach this ip 202.183.64.5

http://www.cisco.com/en/US/partner/tech/tk436/tk428/technologies_tech_note09186a0080094b4e.shtml#subfirstfive

New Member

Re: LDP - URGENT

Maybe you should also check for bidirectional faults on link. I guess that you have fiber connections...try using the command "udld aggressive" on both sides on ports. This way you could se if RX or TX is bad. udld would put your interface on bad side, to down and make a trap to logg.

Another thing you could check is the MPLS MTU size on GE links. If your running MPLS/LDP, the MTU size may have to be changed, due to additional headers (BGP/IP/MPLS/LDP.....).

Cheers;

Cisco Employee

Re: LDP - URGENT

Try reseating the GBIC. I have seen issues with the same error messages being solved by doing so.

Hope this help,

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México 
Paseo de la Reforma 222 Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
421
Views
4
Helpful
5
Replies