%MPLS_TE-5-LSP: LSP 2.2.2.2 5_167: DOWN: path error

[michael1999ac]

Hi There, 

I can't bring up a MPLS TE tunnel with fast-reroute Node Protection, here is the error I get.

*Dec 18 21:24:32.537: %MPLS_TE-5-LSP: LSP 2.2.2.2 5_192: DOWN: path error

I attach the headend's config

interface Tunnel5
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 6.6.6.6
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 500
tunnel mpls traffic-eng affinity 0x0 mask 0x0
tunnel mpls traffic-eng path-option 1 explicit name PATH_P5_IN
tunnel mpls traffic-eng fast-reroute node-protect
end

The PLR's config

interface Tunnel4
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 5.5.5.5
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 4000
tunnel mpls traffic-eng affinity 0x0 mask 0x0
tunnel mpls traffic-eng path-option 1 explicit name INCLUDE_P4
end

interface GigabitEthernet4
ip address 192.168.57.4 255.255.255.0
ip router isis
shutdown
negotiation auto
mpls ip
mpls traffic-eng tunnels
mpls traffic-eng backup-path Tunnel4
no mop enabled
no mop sysid
ip rsvp bandwidth 1000000
en

-----------------------------------

I tried everything but it doesn't work, pls help me :'( !!!!!!!!

[Harold Ritter]

Hi @michael1999ac ,

Can you provide the "show mpls traffic-eng tunnels tu5"

Regards,

[michael1999ac]

Sure, 

Here is the ouput when the interface of the primary tunnel is down,

PE1#show mpls traffic-eng tunnels tunnel 5

Name: PE1_t5 (Tunnel5) Destination: 6.6.6.6
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 1, type explicit PATH_P5_IN

Config Parameters:
Bandwidth: 500 kbps (Global) Priority: 7 7 Affinity: 0x0/0x0
Metric Type: TE (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: enabled LockDown: disabled Loadshare: 500 [0] bw-based
auto-bw: disabled
Fast Reroute: enabled, Node Protection: Yes, Bandwidth Protection: No
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Shortest Unconstrained Path Info:
Path Weight: 20 (TE)
Explicit Route: 192.168.23.2 192.168.23.3 192.168.36.3 192.168.36.6
6.6.6.6

History:
Tunnel:
Time since created: 2 minutes, 1 seconds
Time since path change: 1 minutes, 13 seconds
Number of LSP IDs (Tun_Instances) used: 40
Prior LSP: [ID: 37]
ID: path option 1 [40]
Removal Trigger: path error
Last Error: CTRL:: Can't use link 192.168.24.2 on node 2.2.2.2

------------------------------------------------

And here , the ouput of the tunnel when gi4 is UP,

PE1#show mpls traffic-eng tunnels tunnel 5

Name: PE1_t5 (Tunnel5) Destination: 6.6.6.6
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit PATH_P5_IN (Basis for Setup, path weight 5)

Config Parameters:
Bandwidth: 500 kbps (Global) Priority: 7 7 Affinity: 0x0/0x0
Metric Type: TE (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: enabled LockDown: disabled Loadshare: 500 [4000000] bw-based
auto-bw: disabled
Fast Reroute: enabled, Node Protection: Yes, Bandwidth Protection: No
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled

InLabel : -
OutLabel : GigabitEthernet3, 34
Next Hop : 192.168.24.4
RSVP Signalling Info:
Src 2.2.2.2, Dst 6.6.6.6, Tun_Id 5, Tun_Instance 75
RSVP Path Info:
My Address: 192.168.24.2
Explicit Route: 192.168.24.4 192.168.57.8*
Record Route:
Tspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits
RSVP Resv Info:
Record Route: 4.4.4.4(34) 192.168.57.4(34)
8.8.8.8(36) 192.168.58.8(36)
5.5.5.5(36) 192.168.56.5(36)
6.6.6.6(3) 192.168.56.6(3)
Fspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits
Shortest Unconstrained Path Info:
Path Weight: 20 (TE)
Explicit Route: 192.168.23.2 192.168.23.3 192.168.36.3 192.168.36.6
6.6.6.6

History:
Tunnel:
Time since created: 12 minutes, 35 seconds
Time since path change: 6 seconds
Number of LSP IDs (Tun_Instances) used: 75
Current LSP: [ID: 75]
Uptime: 6 seconds
Prior LSP: [ID: 62]
ID: path option unknown
Removal Trigger: path error

The curios thing is that it is even observed as backp route but it is no activated (I mean is activated like for a couple of seconds and then it is eliminated).

P2#show mpls traffic-eng fast-reroute database
P2P Headend FRR information:
Protected tunnel In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------

P2P LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
2.2.2.2 5 [75] 34 Gi4:36 Tu4:36 ready

P2MP Sub-LSP FRR information:
*Sub-LSP identifier
src_lspid[subid]->dst_tunid In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------

* Sub-LSP identifier format: <TunSrc>_<LSP_ID>[SubgroupID]-><TunDst>_<Tun_ID>
Note: Sub-LSP identifier may be truncated.
Use 'detail' display for the complete key.

And after that I get this error, and is eliminated from the FRR database.

P2#
*Dec 19 02:19:37.999: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed, handle:2 neigh proc:FRR, handle:2 active

[Harold Ritter]

Hi @michael1999ac ,

Can you please attach a topology.

Regards,

[MHM Cisco World]

MPLS TE link protect

R1 is head tunnel router' this config with fastreroute 

R2 is route in path of tunnel R1 use 

R2 is config with interface and it  backup tunnel x 

R2 have tunnel x (this tunnel must config without autoroute' it only other link of original tunnel of R1)

Do these steps and check again 

MHM

[michael1999ac · Accepted solution]

Hi everyone,

I found the solution, but actually I clearly don't understand, how explicit path with next-address works.

If you see in the output, of PE1#show mpls traffic-eng tunnels tunnel 5, tha explicit route was, " Explicit Route: 192.168.24.4 192.168.57.4 192.168.57.8 8.8.8.8 " because I use this config, 

!

 PATH PATH_P5_IN (loose source route, path complete, generation 12)
1: next-address 192.168.24.4
2: next-address loose 192.168.57.8

!

I gues with next-address we have to put all the path, so Instead I use exclude address.

!

PATH PATH_P5_IN (strict source route, path complete, generation 30)
1: exclude-address 3.3.3.3
2: exclude-address 10.10.10.10
3: exclude-address 192.168.45.4

!

After using this explicit path and shutdown the interface the backup tunnel works fine

!

CE1#traceroute 7.7.7.7 source loopback 0
Type escape sequence to abort.
Tracing the route to 7.7.7.7
VRF info: (vrf in name/id, vrf out name/id)
1 192.168.12.2 3 msec 2 msec 1 msec
2 192.168.24.4 [MPLS: Label 41 Exp 0] 5 msec 6 msec 4 msec
3 192.168.26.5 [MPLS: Labels 29/39 Exp 0] 7 msec 7 msec 6 msec
4 192.168.27.7 [MPLS: Label 39 Exp 0] 7 msec 6 msec 5 msec
5 192.168.56.6 3 msec 4 msec 2 msec
6 192.168.67.7 83 msec * 18 msec

!

But thanks anyway for yours answers.

Here I attach my topology work on EVE-NG with GCP

[Harold Ritter]

Hi @michael1999ac ,

I am glad to see you fixed the issue and thanks for providing the additional information. It will certainly help others.

Regards,