07-22-2005 06:24 AM
Was testing interworking between Vlan over ethernet and FR. As long as my LDP was on static routing, I couldnt reach end-to-end. The moment i configured OSPF as my routing protocol it came up. Can anyone let me know what the reason could be ?
Solved! Go to Solution.
07-26-2005 06:50 AM
Gautam,
This is actually normal behavior.
Before the label learnt via an LDP peer is coupled to a route in the FIB, the next-hop IP address of the route needs to match one of the interface IP addresses bound to the LDP peer (see below). So basically it will not work without a next IP address.
r2#sh mpls ldp nei
Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 2.2.2.2:0
TCP connection: 3.3.3.3.11004 - 2.2.2.2.646
State: Oper; Msgs sent/rcvd: 27/27; Downstream
Up time: 00:15:07
LDP discovery sources:
Serial3/0, Src IP addr: 192.168.23.3
Addresses bound to peer LDP Ident:
3.3.3.3 192.168.34.3 192.168.23.3 <++++++ the route next hop has to match one of these addresses.
Hope this helps,
07-22-2005 05:16 PM
It should work with static routes as well as with dynamic routing protocols.
Make sure that you have connectivity between the loopback addresses of the two PEs and between loopback addresses of each LDP (or TDP) neighbors.
Let me know if I answered your question,
07-24-2005 10:45 PM
The issue was with non recursive routing in my P router. I added non recursive routes and it was fine. Suprised this issue isnt solved even in 12.0(28)s
07-25-2005 04:28 AM
Can you elaborate on what you recursive routes were?
Thanks,
07-25-2005 09:05 PM
for my remote loopback, there were static routes in my P router
For eg
Initial Config
ip route x.x.x.x 255.255.255.255 S0/0
Working config
ip route x.x.x.x 255.255.255.255 S0/0 192.168.1.2
07-26-2005 06:50 AM
Gautam,
This is actually normal behavior.
Before the label learnt via an LDP peer is coupled to a route in the FIB, the next-hop IP address of the route needs to match one of the interface IP addresses bound to the LDP peer (see below). So basically it will not work without a next IP address.
r2#sh mpls ldp nei
Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 2.2.2.2:0
TCP connection: 3.3.3.3.11004 - 2.2.2.2.646
State: Oper; Msgs sent/rcvd: 27/27; Downstream
Up time: 00:15:07
LDP discovery sources:
Serial3/0, Src IP addr: 192.168.23.3
Addresses bound to peer LDP Ident:
3.3.3.3 192.168.34.3 192.168.23.3 <++++++ the route next hop has to match one of these addresses.
Hope this helps,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide