cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
978
Views
0
Helpful
5
Replies

Interworking on Static Routing as IGP

attrgautam
Level 5
Level 5

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 ?

1 Accepted Solution

Accepted Solutions

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,

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

View solution in original post

5 Replies 5

Harold Ritter
Cisco Employee
Cisco Employee

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,

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

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

Can you elaborate on what you recursive routes were?

Thanks,

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

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

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,

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