No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

LDP Neighbor Relation is not Established because the Realization of BAS of J Company and NE80E is Different

Publication Date:  2012-07-27 Views:  32 Downloads:  0
Issue Description
NE80E and BAS of J company cannot establish LDP neighbor relation, and the neighbor is always in open sent state.
<NE80E>display mpls ldp session
               LDP Session(s) in Public Network
 ------------------------------------------------------------------------------
 Peer-ID            Status      LAM  SsnRole  SsnAge      KA-Sent/Rcv
 ------------------------------------------------------------------------------
 2.2.2.1:0          Open Sent        Active               0/0
 ------------------------------------------------------------------------------
 LAM : Label Advertisement Mode      SsnAge Unit : DDD:HH:MM
The case is applicable to VRP5.10 of NE80E.
Alarm Information
Null
Handling Process
1. Configure mpls ldp transport-address interface on the interface connecting NE80E and J company, and then LDP neighbor recovers.
For example, GigabitEthernet2/0/0 interface of NE80E and BAS of J company connect and establish LDP neighbor.
NE80E (GigabitEthernet2/0/0)------J company
[NE80E]interface GigabitEthernet2/0/0
[NE80E-GigabitEthernet2/0/0]mpls ldp transport-address interface
Root Cause
BAS of J company requires that LDP neighbor relation should be established through direct physical interface address. NE80E is to use LoopBack interface to establish LDP neighbor.
Suggestions
NE80E and router of J company connect LDP and there is no such problem. So does NE80E and router of A company. If it occurs, configure mpls ldp transport-address interface on interconnected interface.

END