MPLS Traffic Engineering - Tunnels not coming up.

[mac_mac_net83]

So I have a network setup and everything seems to work fine. 

I have 3 OSPF areas and running MPLS VPN (MP - BGP all configured)

Area 65 ---- Area 0 ----- Area 78

I am trying to create a tunnel from one router in Area 65 to another router in router 78.

Take note that all routers partcipating on reach respective areas are configured with:

   mpls traffic-eng area <area-id>  as well as mpls traffic-eng roouter-id <interface>

All interfaces on the core are configured with mpls traffic-eng tunnels as well as the ip rsvp bandwidht command. 

Below are the results I get when I configure just a simple tunnel fom a router in Area 65 to a router going to Area 78. 

R5#show running-config interface tunnel 57
Building configuration...

Current configuration : 156 bytes
!
interface Tunnel57
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 7.7.7.7
tunnel mpls traffic-eng path-option 1 dynamic
end

R5#

interface Loopback0
ip address 5.5.5.5 255.255.255.255
end

R5#ping 7.7.7.7 source lo0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 7.7.7.7, timeout is 2 seconds:
Packet sent with a source address of 5.5.5.5
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
R5#

R5#show mpls traffic-eng tunnels

Name: R5_t57 (Tunnel57) Destination: 7.7.7.7
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 1, type dynamic

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
auto-bw: disabled

History:
Tunnel:
Time since created: 14 hours, 16 minutes
Time since path change: 13 hours, 57 minutes
Number of LSP IDs (Tun_Instances) used: 1732
Prior LSP:
ID: path option 1 [40]
Removal Trigger: configuration changed
Last Error: PCALC:: Destination IP address, 7.7.7.7, not found

I can't figure it out why the output is saying 7.7.7.7 cannot be found but, that /32 route is in the routing table and is reachable from this router. 

Any comments are appreciated. 

Thanks. 

Mark

[Reza Sharifi]

Does every router in the path have these commands in the OSPF config?

mpls traffic-eng router-id Loopback0

mpls traffic-eng area x

HTH

[mac_mac_net83]

yes, there is, also for the ABRs, is like below:

router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
mpls traffic-eng area 65

[Harold Ritter]

Hi Mark,

You can't use the dynamic path-option between area. The issue is that the head end router does not have all the information to calculate the entire path to the tail end, as they are not in the same area. You need to use an explicit path-option, as explained in this document.

https://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/fs_areat.html#wp1034833

Regards,

[mac_mac_net83]

HI harold, thanks for the reply.
I have tried that option (using explicit paths with strict and loose) and it fails as well, Let me try again later and see if to reset the tunnel as well.
Also, my "show mpls traffic-eng topology " output for each routers shows that it is learning all the nodes within the areas, so I think there should be no problem of having the tunnels up . let me try again later. Thanks for the inputs.

[Harold Ritter]

Hi Mark,

The following error message "Last Error: PCALC:: Destination IP address, 7.7.7.7, not found" is basically telling you that the information for the tail-end router is not present in the head end router topology database.

The MPLS traffic engineering topology information is advertised via opaque LSAs and these LSAs have a scope of area, which means they will not propagate outside of the local area. So I do not know how MPLS traffic engineering information could be present on all routers given your multi area topology.

Regards,

[mac_mac_net83]

HI Harold,

I am pretty sure, it should work still is using multiple areas that is why it is the reason why you need to specify the areas for the mpls traffic engineering under the routing protocol you are using in the network, not sure if this is an issue with the simulator, so I am still trying and running debugs of what could be the cause....

mark

[Julio E. Moisa]

Hi

Have you verified if RSVP is configured under the interfaces over the path?

[mac_mac_net83]

Hi Harold, 

Ye. The RSVP bw are already configured. It is configured with 2M . I have 10M core links across the network and rarely used, does it pose any issue?

Mark

[Harold Ritter]

Hi Mark,

It will not work. The reason you specify the area is to tell OSPF what area should be using the MPLS TE extensions. OSPF still won't propagate TE information from one area to the other. You should be able to verify that even in your simulated lab.

Regards,

[mac_mac_net83]

Hi Harold,

In our production network, we are using OSPF multi area and was able to setup MPLS traffic engineering tunnels all over the place...

Mark

[Harold Ritter]

You must be using the Inter Area MPLS TE feature then. Check your production config to see whether you use a dynamic or explicit path.

Regards,

[mailatgk]

Hi ,

I am seeing same kind of issue. Tunnel is not coming up . 

I am using XRV node running version 7.11.2.  Could anyone please comment on this issue ?

XRV-A Config:                                                                       

RP/0/RP0/CPU0: XRv-A#show running-config interface tunnel-te 7

Wed May  8 07:34:55.889 UTC

interface tunnel-te7

 description RSVPtunnel

 ipv4 unnumbered Loopback0

 signalled-name XRV-A

 autoroute announce

 !

 destination 92.168.96.24

 path-option 1 dynamic

!

RP/0/RP0/CPU0:XRv-A#show running-config router ospf 1

Wed May  8 06:19:12.705 UTC

router ospf 1

 router-id 92.168.96.26

 redistribute connected

 area 0.0.0.0

  mpls traffic-eng

  interface GigabitEthernet0/0/0/2.10

   network point-to-point

  !

 mpls traffic-eng router-id Loopback0

!

RP/0/RP0/CPU0:XRv-A#show running-config rsvp

Wed May  8 06:19:36.765 UTC

rsvp

 interface GigabitEthernet0/0/0/2.10

 !

!

RP/0/RP0/CPU0:XRv-A#show running-config mpls traffic-eng

Wed May  8 06:19:42.471 UTC

mpls traffic-eng

interface GigabitEthernet0/0/0/2.10

 !

RP/0/RP0/CPU0: :XRv-A#show running-config interface loopback 0

Wed May  8 06:32:08.518 UTC

interface Loopback0

 ipv4 address 92.168.96.26 255.255.255.255

!!

RP/0/RP0/CPU0:XRv-A#show running-config interface GigabitEthernet0/0/0/2.10

Wed May  8 07:43:16.876 UTC

interface GigabitEthernet0/0/0/2.10

 ipv4 address 10.10.15.1 255.255.255.252

 encapsulation dot1q 10

!

RP/0/RP0/CPU0: XRv-A#show ospf neighbor

Wed May  8 06:53:28.103 UTC

* Indicates MADJ interface

# Indicates Neighbor awaiting BFD session up

Neighbors for OSPF 1

Neighbor ID     Pri   State           Dead Time   Address         Interface

92.168.96.24    1     FULL/  -        00:00:37    10.10.15.2      GigabitEthernet0/0/0/2.10

    Neighbor is up for 00:26:29

RP/0/RP0/CPU0:XRv-A#show mpls traffic-eng tunnels 7

Wed May  8 07:44:29.749 UTC

Name: tunnel-te7  Destination: 92.168.96.24  Ifhandle:0x1c

  Signalled-Name: XRV-A

  Status:

    Admin:    up Oper: down   Path:  valid   Signalling: RSVP signaling proceeding

    path option 1,  type dynamic

    G-PID: 0x0800 (derived from egress interface properties)

    Bandwidth Requested: 0 kbps  CT0

    Creation Time: Tue May  7 06:28:17 2024 (1d01h ago)

  Config Parameters:

    Bandwidth:        0 kbps (CT0) Priority:  7  7 Affinity: 0x0/0xffff

    Metric Type: TE (global)

    Path Selection:

      Tiebreaker: Min-fill (default)

    Hop-limit: disabled

    Cost-limit: disabled

    Delay-limit: disabled

    Delay-measurement: disabled

    Path-invalidation timeout: 10000 msec (default), Action: Tear (default)

    AutoRoute:  enabled  LockDown: disabled   Policy class: not set

    Forward class: 0 (not enabled)

    Forwarding-Adjacency: disabled

    Autoroute Destinations: 0

    Loadshare:          0 equal loadshares

    Load-interval: 300 seconds

    Auto-bw: disabled

    Auto-Capacity: Disabled:

    Self-ping: Disabled

    Fast Reroute: Disabled, Protection Desired: None

    Path Protection: Not Enabled

    BFD Fast Detection: Disabled

    Reoptimization after affinity failure: Enabled

    Soft Preemption: Disabled

  History:

    Current LSP:

      Setup Time: 57 seconds

    Reopt. LSP:

      Last Failure:

        Re-opt LSP signalling time-out

        Date/Time: Tue May 07 10:54:59 UTC 2024 [20:49:30 ago]

        First Destination Failed: 92.168.96.24

    Prior LSP:

      ID: 298 Path Option: 1

      Removal Trigger: setup timed out

  Path info (OSPF 1 area 0.0.0.0):

  Node hop count: 1

  Hop0: 10.10.15.2

  Hop1: 92.168.96.24

LSP Tunnel 92.168.96.24 7 [301] is signalled, Signaling State: up

  Tunnel Name: XRV-B Tunnel Role: Tail

  InLabel: GigabitEthernet0/0/0/2.10, implicit-null

  Signalling Info:

    Src 92.168.96.24 Dst 92.168.96.26, Tun ID 7, Tun Inst 301, Ext ID 92.168.96.24

    Router-IDs: upstream   92.168.96.24

                local      92.168.96.26

    Bandwidth: 0 kbps (CT0) Priority:  7  7 DSTE-class: 0

    Soft Preemption: None

    SRLGs: not collected

    Path Info:

      Incoming Address: 10.10.15.1

      Incoming:

      Explicit Route:

        Strict, 10.10.15.1

        Strict, 92.168.96.26

      Record Route: Disabled

      Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

      Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set

                          Soft Preemption Desired: Not Set

    Resv Info: None

      Record Route: Disabled

      Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 0 up, 1 down, 0 recovering, 0 recovered heads

RP/0/RP0/CPU0:XRv-A#show interfaces tunnel-te 7

Wed May  8 08:05:36.859 UTC

tunnel-te7 is down, line protocol is down

  Interface state transitions: 4

  Hardware is Tunnel-TE

  Description: RSVPtunnel

XRV-B config:

RP/0/RP0/CPU0:XRv-B#show running-config interface gigabitEthernet 0/0/0/2.10

Wed May  8 07:58:54.490 UTC

interface GigabitEthernet0/0/0/2.10

 ipv4 address 10.10.15.2 255.255.255.252

 encapsulation dot1q 10

!

RP/0/RP0/CPU0:XRv-B#show running-config interface loopback 0

Wed May  8 07:59:33.424 UTC

interface Loopback0

 ipv4 address 92.168.96.24 255.255.255.255

!

RP/0/RP0/CPU0:XRv-B#show ospf neighbor

Wed May  8 07:59:52.277 UTC

* Indicates MADJ interface

# Indicates Neighbor awaiting BFD session up

Neighbors for OSPF 1

Neighbor ID     Pri   State           Dead Time   Address         Interface

92.168.96.26    1     FULL/  -        00:00:37    10.10.15.1      GigabitEthernet0/0/0/2.10

    Neighbor is up for 2w0d

Total neighbor count: 1

RP/0/RP0/CPU0:XRv-B#show running-config router ospf 1

Wed May  8 08:00:16.799 UTC

router ospf 1

 router-id 92.168.96.24

 redistribute connected

 address-family ipv4 unicast

 area 0.0.0.0

  mpls traffic-eng

  interface Loopback0

  !

  interface GigabitEthernet0/0/0/2.10

   network point-to-point

  !

 !

 mpls traffic-eng router-id Loopback0

!

RP/0/RP0/CPU0:XRv-B#show running-config rsvp

Wed May  8 08:00:49.427 UTC

\rsvp

 interface GigabitEthernet0/0/0/2.10

 !

!

RP/0/RP0/CPU0:XRv-B#show running-config mpls traffic-eng

Wed May  8 08:00:54.751 UTC

mpls traffic-eng

interface GigabitEthernet0/0/0/2.10

 !

!

RP/0/RP0/CPU0:XRv-B#show mpls traffic-eng tunnels 7

Wed May  8 08:02:52.520 UTC

Name: tunnel-te7  Destination: 92.168.96.26  Ifhandle:0x1c

  Signalled-Name: XRV-B

  Status:

    Admin:    up Oper: down   Path:  valid   Signalling: RSVP signaling proceeding

    path option 1,  type dynamic

    G-PID: 0x0800 (derived from egress interface properties)

    Bandwidth Requested: 0 kbps  CT0

    Creation Time: Tue May  7 09:37:58 2024 (22:24:54 ago)

  Config Parameters:

    Bandwidth:        0 kbps (CT0) Priority:  7  7 Affinity: 0x0/0xffff

    Metric Type: TE (global)

    Path Selection:

      Tiebreaker: Min-fill (default)

    Hop-limit: disabled

    Cost-limit: disabled

    Delay-limit: disabled

    Delay-measurement: disabled

    Path-invalidation timeout: 10000 msec (default), Action: Tear (default)

    AutoRoute:  enabled  LockDown: disabled   Policy class: not set

    Forward class: 0 (not enabled)

    Forwarding-Adjacency: disabled

    Autoroute Destinations: 0

    Loadshare:          0 equal loadshares

    Load-interval: 300 seconds

    Auto-bw: disabled

    Auto-Capacity: Disabled:

    Self-ping: Disabled

    Fast Reroute: Disabled, Protection Desired: None

    Path Protection: Not Enabled

    BFD Fast Detection: Disabled

    Reoptimization after affinity failure: Enabled

    Soft Preemption: Disabled

  History:

    Current LSP:

      Setup Time: 49 seconds

    Prior LSP:

      ID: 304 Path Option: 1

      Removal Trigger: setup timed out

  Path info (OSPF 1 area 0.0.0.0):

  Node hop count: 1

  Hop0: 10.10.15.1

  Hop1: 92.168.96.26

LSP Tunnel 92.168.96.26 7 [303] is signalled, Signaling State: up

  Tunnel Name: XRV-A Tunnel Role: Tail

  InLabel: GigabitEthernet0/0/0/2.10, implicit-null

  Signalling Info:

    Src 92.168.96.26 Dst 92.168.96.24, Tun ID 7, Tun Inst 303, Ext ID 92.168.96.26

    Router-IDs: upstream   92.168.96.26

                local      92.168.96.24

    Bandwidth: 0 kbps (CT0) Priority:  7  7 DSTE-class: 0

    Soft Preemption: None

    SRLGs: not collected

    Path Info:

      Incoming Address: 10.10.15.2

      Incoming:

      Explicit Route:

        Strict, 10.10.15.2

        Strict, 92.168.96.24

      Record Route: Disabled

      Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

      Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set

                          Soft Preemption Desired: Not Set

    Resv Info: None

      Record Route: Disabled

      Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 0 up, 1 down, 0 recovering, 0 recovered heads

RP/0/RP0/CPU0:XRv-B#show running-config interface tunnel-te 7

Wed May  8 08:02:59.789 UTC

interface tunnel-te7

 description RSVPtunneltoA

 ipv4 unnumbered Loopback0

 signalled-name XRV-B

 autoroute announce

 !

 destination 92.168.96.26

 path-option 1 dynamic

!

RP/0/RP0/CPU0:XRv-B#show interfaces tunnel-te 7

Wed May  8 08:06:11.917 UTC

tunnel-te7 is down, line protocol is down

  Interface state transitions: 0

  Hardware is Tunnel-TE

[MHM Cisco World]

Make new post is better 

MHM