MPLS-TE: It doesn't switch to the protected tunnel automatically?!
Hello all
I am having a problem figuring out the cause for the router not to choose the protected tunnel when the primary tunnel is down because the physical interface is down/down, the configuration is as follows:
mpls traffic-eng tunnels
mpls traffic-eng signalling advertise implicit-null
mpls traffic-eng signalling restart neighbors
mpls label protocol ldp
!
interface Vlan856
description VLAN MPLS_ T-01_S-01
mtu 9216
ip address 172.16.35.1 255.255.255.252
no ip redirects
no ip proxy-arp
no ipv6 mld snooping
mpls traffic-eng tunnels
mpls label protocol ldp
mpls ip
ip rsvp bandwidth
!
interface Tunnel501
description T-01_A-01
ip unnumbered Loopback0
tunnel destination 10.254.254.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 100
tunnel mpls traffic-eng path-option 10 explicit name path501
tunnel mpls traffic-eng path-option protect 10 explicit name path501B
end
!
ip explicit-path name path501B enable
next-address 172.16.34.1
next-address 172.16.33.1
next-address 172.16.32.1
next-address 172.16.31.1
ip explicit-path name path501 enable
next-address 172.16.35.2
next-address 172.16.36.2
next-address 172.16.37.2
Only this address "172.16.35.2 " is not pingable, the interface vlan associated to it has down/down status, because the physical interface is down. It should choose the
next path (501B), but it doesn't!
T-01#sh mpls traffic-eng tunnels tunnel 501
Name: T-01_A-01 (Tunnel501) Destination: 10.254.254.1
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 10, type explicit path501
path protect option 10, type explicit path501B
Config Parameters:
Bandwidth: 100 kbps (Global) Priority: 1 1 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: enabled LockDown: disabled Loadshare: 100 bw-based
auto-bw: disabled
Shortest Unconstrained Path Info:
Path Weight: 4 (TE)
Explicit Route: 172.16.34.2 172.16.34.1 172.16.33.2 172.16.33.1
172.16.32.2 172.16.32.1 172.16.31.2 172.16.31.1
10.254.254.1
History:
Prior LSP:
ID: path option 10 [5120]
Removal Trigger: configuration changed
Last Error: PCALC:: Explicit path has unknown address, 172.16.35.2
************************************************************
The other side where this tunnel ends also has the same issue, it can't reach the network 172.16.35.2 but it also doesn't switch to the protected tunnel
interface Tunnel105
description A-01_T-01
ip unnumbered Loopback0
tunnel destination 10.254.254.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 100
tunnel mpls traffic-eng path-option 10 explicit name path105
tunnel mpls traffic-eng path-option protect 10 explicit name path105B
!
ip explicit-path name path105B enable
next-address 172.16.31.2
next-address 172.16.32.2
next-address 172.16.33.2
next-address 172.16.34.2
ip explicit-path name path105 enable
next-address 172.16.37.1
next-address 172.16.36.1
next-address 172.16.35.1
A-01#sh mpls tr tun tun 105
Name: A-01_T-01 (Tunnel105) Destination: 10.254.254.5
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 10, type explicit path105
path protect option 10, type explicit path105B
Config Parameters:
Bandwidth: 100 kbps (Global) Priority: 1 1 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: enabled LockDown: disabled Loadshare: 100 bw-based
auto-bw: disabled
Shortest Unconstrained Path Info:
Path Weight: 4 (TE)
Explicit Route: 172.16.31.1 172.16.31.2 172.16.32.1 172.16.32.2
172.16.33.1 172.16.33.2 172.16.34.1 172.16.34.2
10.254.254.5
History:
Prior LSP:
ID: path option 10 [8339]
Removal Trigger: configuration changed
Last Error: PCALC:: Explicit path has unknown address, 172.16.35.1
************************************************************
when i change the configuration under both interfaces tunnel 501 and tunnel 105 to use path501B and path105B respectively as the primary path, the tunnel comes up as normal, but why the router doesn't do that automatically? Is there any missing command!?
T-01(config)#interface Tunnel501
tunnel mpls traffic-eng path-option 10 explicit name path501B
A-01(config)#interface Tunnel105
tunnel mpls traffic-eng path-option 10 explicit name path501B
Comments
hey can you ping this ip ? next-address 172.16.35.1
http://ieoc.com/forums/t/6650.aspx
hi soud
No, i can't ping that address because the Vlan assoiated to it is down.
T-01#sh int vlan 856
Vlan856 is down, line protocol is down
Hardware is EtherSVI, address is 0023.0417.d000 (bia 0023.0417.d000)
Description: VLAN MPLS_ TR01_SE01
Internet address is 172.16.35.1/30
The router should do the math and switch to the protected path automatically if it can't reach one of the addresses in the explicit-path, but it doesn't
remember this the next-address in explicit path must be directlly connected neighbor otherwise it wont work
yes soud, this address 172.16.35.1/30 is for directly connected neighbor
Yes, the first address in the explicit path is a directlly connected neighbor.
Any answers!
hey dude post your topology u r using, i will give it a short, issue you are having is that it doesnt switch on automatically? thenn you need fast reroute enabled on the interface, and those path-options if im not mistaken they both start at 10, try to givr thr 11 or any number, lets cross out one at a time, but pls post ur topology !!!