cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2516
Views
9
Helpful
38
Replies

RSVP-TE tunnel does not establish

quad99
Level 1
Level 1

Hi
I am doing a simple lab and at the very beginning I have a problem .Well it does not set up the tunnel ,I have checked the configuration many times with the official cisco materials and the configuration seems correct. Anyone can help ?

Below i am uploading my topology along with the configuration.

quad99_0-1736079250611.png

 

PE1 Configuration:

!
ip cef
mpls traffic-eng tunnels
mpls traffic-eng logging lsp setups
mpls traffic-eng logging lsp teardowns
mpls traffic-eng reoptimize events link-up
!
interface Loopback0
ip address 1.1.1.1 255.255.255.255
!
interface GigabitEthernet1/0
no shutdown
ip address 192.168.12.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet2/0
no shutdown
ip address 192.168.23.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
router-id 1.1.1.1
network 1.1.1.1 0.0.0.0 area 0
network 192.168.12.1 0.0.0.3 area 0
network 192.168.23.1 0.0.0.3 area 0
!
ip explicit-path name PE1-PE2 enable
next-address 192.168.12.2
next-address 192.168.34.2
next-address 4.4.4.4
!
interface Tunnel12
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 2 2
tunnel mpls traffic-eng bandwidth 100
tunnel mpls traffic-eng path-option 1 explicit name PE1-PE2
!
...................................................................
PE2 Configuration:

!
ip cef
mpls traffic-eng tunnels
mpls traffic-eng logging lsp setups
mpls traffic-eng logging lsp teardowns
mpls traffic-eng reoptimize events link-up
!
interface Loopback0
ip address 4.4.4.4 255.255.255.255
!
interface GigabitEthernet1/0
no shutdown
ip address 192.168.34.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet2/0
no shutdown
ip address 192.168.45.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
router-id 4.4.4.4
network 4.4.4.4 0.0.0.0 area 0
network 192.168.34.0 0.0.0.3 area 0
network 192.168.45.0 0.0.0.3 area 0
!
ip explicit-path name PE2-PE1 enable
next-address 192.168.34.1
next-address 192.168.12.1
next-address 1.1.1.1
!
interface Tunnel21
ip unnumbered Loopback0
tunnel destination 1.1.1.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 2 2
tunnel mpls traffic-eng bandwidth 100
tunnel mpls traffic-eng path-option 1 explicit name PE2-PE1
!

...................................................................
P1 Configuration:

ip cef
mpls traffic-eng tunnels
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
router-id 2.2.2.2
network 2.2.2.2 0.0.0.0 area 0
network 192.168.12.0 0.0.0.3 area 0
network 192.168.34.0 0.0.0.3 area 0
network 192.168.56.0 0.0.0.3 area 0
!
interface GigabitEthernet0/0
no shutdown
ip address 192.168.12.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet1/0
no shutdown
ip address 192.168.34.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet2/0
no shutdown
ip address 192.168.56.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface Loopback0
ip address 2.2.2.2 255.255.255.255
!

...................................................................
P2 Configuration:

ip cef
mpls traffic-eng tunnels
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
router-id 3.3.3.3
network 3.3.3.3 0.0.0.0 area 0
network 192.168.23.0 0.0.0.3 area 0
network 192.168.45.0 0.0.0.3 area 0
network 192.168.56.0 0.0.0.3 area 0
!
interface GigabitEthernet0/0
no shutdown
ip address 192.168.23.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet1/0
no shutdown
ip address 192.168.45.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface GigabitEthernet2/0
no shutdown
ip address 192.168.56.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 1000
!
interface Loopback0
ip address 3.3.3.3 255.255.255.255
!

quad99_2-1736079032268.png

 

 

38 Replies 38

Hi

"mpls traffic-eng tunnels" was added globally at the very beginning and still is.. Very strange riddle

Hi @quad99 ,

The issue is with the "mpls traffic-eng router-id Loopback0" that was initially configured out of sequence (before loopback 0 was configured) on P1 and P2. Please configured it again and the problems will be solved.

Regards, 

Regards,
Harold Ritter, CCIE #4168 (EI, SP)

...Right ! For Router P1 & P2 I did the configurations in the wrong order . I don't know how I could not notice that ...what a shame . Well nothing , as they say we learn from our mistakes , thank you very much for your help Harold .This is my first thread on this “forum” . I did not expect such advanced and quick help.

Best regards

I ask you twice did you close and reopen lab and you confirm ?

it sure ID issue and when close and reopen the issue will solve 

anyway 

glad issue solved

MHM

I did as you say .It was not a virtualization environment problem just a configuration problem (mpls-te was missing on the P1 router).

Regards

Friend I am happy participate in this issue, 
each time I participate give more ack now I know what I will looking for in feature for mpls te.

have a nice day 

MHM

Great! Cool that the community is working so well. If I gain experience then I will also try to help others

Join try solve any issue other face, write comment do lab. 

For mpls te, your issue give me hint how I looking for correct config.

And when I finish my note I will share with you. 

In real network try and guess is not preferr. 

Anyway let me finish my note and later we talk 

Dont stop studying 

MHM

Hi @MHM Cisco World ,

First thing that should be done when troubleshooting why a MPLS TE tunnel doesn't come up is to check the error message part of the "show mpls traffic-eng tunnels". The next step is often to check the MPLS TE database to see if the information is present for all the nodes. If the information is not there for a specific node, the issue is most likely related to the MPLS TE configuration on that node.

Regards,

Regards,
Harold Ritter, CCIE #4168 (EI, SP)

You are very welcome @quad99 and thanks for the feedback

Regards,
Harold Ritter, CCIE #4168 (EI, SP)

Hi @quad99 ,

According to the configuration you provided, you tried to configured "mpls traffic-eng router-id Loopback0" before the interface lo0 was configured. You probably got an error message. Please configure "mpls traffic-eng router-id Loopback0" again under router ospf and you should see the information for 2.2.2.2 and 3.3.3.3 in the mpls traffic engineering database.

Regards,

Regards,
Harold Ritter, CCIE #4168 (EI, SP)

Unfortunately not , first I configured the interfaces , then ospf.

under all LO add 
ip ospf network point-to-point<<- 

use LO as I mention before in explicit path
then wr config close lab and reopen again 

check the tunnel state 

MHM

Router# show mpls traffic-eng forwarding path-set brief
Router# show mpls traffic-eng forwarding path-set detail

if above not work share about of these command 

NOTE:- last command with detail only work in IOS XR I check it

MHM 

Still without any changes ...

My routers don't support both commands...

I'm running on 7200 Software (C7200-ADVENTERPRISEK9-M), Version 12.4(24)T5, RELEASE SOFTWARE (fc3)

I'm attaching the project from gns as if anyone would like >> file.i o/H24F yCi4ViA8