04-13-2004 11:49 AM
I am trying to configure a tunnel interface with a specific destination. Even though that destination is reachable (I can ping it) I get the output below. "Path not valid... destination IP address not found."
Can anybody shed some light on why this is?
-------------
cisco7206#show mpls tr tun
Name: cisco7206_t0 (Tunnel0) Destination: 1.0.0.1
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: 2 hours, 7 minutes
Path Option 1:
Last Error: PCALC:: Destination IP address, 1.0.0.1, not found
cisco7206#
04-13-2004 12:11 PM
Hi,
This may be due to a number of things, chief among them config problems. How does your tunnel config look like? Do you have RSVP configured along the path? How does
show mpls traffic-eng topology look like? I cannot tell from only this show command output what the problem could be, hopefully others can...
Thanks,
--tamrat
04-13-2004 12:24 PM
Hi. My tunnel config is (the tunnel dest is 1.0.0.2, not 1.0.0.1 as shown in my original post):
------------
!
interface Tunnel0
ip unnumbered Loopback0
tag-switching ip
tunnel destination 1.0.0.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng path-option 1 dynamic
end
-----------
I have rsvp configured all along the path.
The show mpls tr top looks like:
-------------------------
cisco7206#show mpls tr top
My_System_id: 99.99.99.99, Globl Link Generation 2
Signalling error holddown: 10 sec
IGP Id: 99.99.99.99, MPLS TE Id:99.99.99.99 Router Node
link[0 ]:DR Intf Address: 1.0.0.1, gen:2
frag_id 0, Intf Address:1.0.0.1
TE metric:1, IGP metric:1, attribute_flags:0x0
physical_bw: 100000 (kbps), max_reservable_bw_global: 10000000 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 10000000 0
bw[1]: 0 10000000 0
bw[2]: 0 10000000 0
bw[3]: 0 10000000 0
bw[4]: 0 10000000 0
bw[5]: 0 10000000 0
bw[6]: 0 10000000 0
bw[7]: 0 10000000 0
link[1 ]:DR Intf Address: 2.0.0.1, gen:2
frag_id 1, Intf Address:2.0.0.1
TE metric:1, IGP metric:1, attribute_flags:0x0
physical_bw: 100000 (kbps), max_reservable_bw_global: 10000000 (kbps)
max_reservable_bw_sub: 0 (kbps)
Global Pool Sub Pool
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
bw[0]: 0 10000000 0
bw[1]: 0 10000000 0
bw[2]: 0 10000000 0
bw[3]: 0 10000000 0
bw[4]: 0 10000000 0
bw[5]: 0 10000000 0
bw[6]: 0 10000000 0
bw[7]: 0 10000000 0
cisco7206#
-------------------
04-13-2004 04:21 PM
Hi,
Ok, so you have RSVP configured and have enough BW on the tunnels. Could you check if you are propagating TE info into OSPF/ISIS? Is 1.0.0.2 one or more hops away? Could you do a traceroute to 1.0.0.2? And also do a show mpls interfaces?
I do not see anything wrong thus far, but perhaps one of the things I am asking you for here will uncover the problem.
Thanks,
--tamrat
04-14-2004 11:52 AM
I have made some progress. The original problem seems to have been a bandwidth problem. Now, when I give the command "debug ip rsvp all" I get:
---------------
sco7206#
cisco7206#
cisco7206#
*Mar 24 01:00:43.734: RSVP-API 99.99.99.99_443->1.0.0.2_1[0.0.0.0]: Failed to cr
eate proxy Path state, reason: Invalid route specification
cisco7206#
------------
repeatedly. Does anybody know what this means? If I do the command "show mpls tr top path tunnel 1"
I get:
---------------------
cisco7206#show mpls tr top path tunnel 1
Query Parameters:
Destination: 1.0.0.2
Bandwidth: 10
Priorities: 5 (setup), 5 (hold)
Affinity: 0x0 (value), 0xFFFF (mask)
Query Results:
Min Bandwidth Along Path: 80 (kbps)
Max Bandwidth Along Path: 100000 (kbps)
Hop 0: 1.0.0.1 : affinity 00000000, bandwidth 100000 (kbps)
Hop 1: 1.0.0.2 : affinity 00000000, bandwidth 80 (kbps)
Hop 2: 1.0.0.2
cisco7206#
----------------
which shows a valid path.
Any help would be appreciated.
04-14-2004 01:33 PM
Make sure that you the loopback interface address of the the egress router as the destination address. Also make sure you use the loopback interface for the "mpls traffic-eng router-id" command.
Hope this helps,
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: