MPLS TE PCALC error: destination IP addr not found

From: John Neiberger <jneiberger_at_gmail.com>
Date: Sun, 4 Aug 2013 16:27:27 -0600

I'm working on labbing up a very simple TE tunnel, but it won't come up and
I can't figure out why. I seem to have all the necessary configuration in
place, but I'm getting an error that I don't understand.

My topology is a simple line at the moment:

A -- B -- C -- D -- E

I have multi-area ISIS configured such that A and B are in area 1, C is are
2, while D and E are in area 3. Routers A and E are L1 only; B and D are
L1L2; router C is L2 only.

I have the following configured on all routers in the path:

mpls traffic-eng tunnels

interface <relevant interfaces>
 mpls traffic-end tunnels
 ip rsvp bandwidth 1000 1000

router isis
 mpls traffic-eng router-id lo0

On the headend (Router A), I configured a tunnel thusly:

interface Tunnel0
 ip unnumbered Loopback0
 mpls traffic-eng tunnels
 tunnel destination 5.5.5.5
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng priority 1 1
 tunnel mpls traffic-eng bandwidth 64
 tunnel mpls traffic-eng path-option 1 explicit name PATH
 no routing dynamic

The destination, 5.5.5.5, is in the ISIS database and in the routing table.
It is the loopback0 address on Router E.

With that config, I got the following error:

TE-PCALC: Tunnel0 Path Setup to 5.5.5.5: FULL_PATH
*Aug 4 10:30:00.768: TE-PCALC: bw 64, min_bw 0, metric: 0
*Aug 4 10:30:00.768: TE-PCALC: setup_pri 1, hold_pri 1
*Aug 4 10:30:00.768: TE-PCALC: affinity_bits 0x0, affinity_mask 0xFFFF
*Aug 4 10:30:00.772: TE-PCALC_PATH: get_path: system_id not initialized!

So, the system ID isn't initialized. WTH? Not sure what that means. But I
tried adding the following to the isis config:

mpls traffic-eng level-1

That seemed to get over that particular hurdle, although I'm not sure why.
It seems that I had to specify level 1 or 2 on each router in the path to
make it work, but I'm not really sure what I'm selecting, nor do I know
what the correct setting is on L1L2 routers.

Here's the error I'm getting now:

TE-PCALC: Tunnel0 Path Setup to 5.5.5.5: FULL_PATH
*Aug 4 10:31:47.228: TE-PCALC: bw 64, min_bw 0, metric: 0
*Aug 4 10:31:47.228: TE-PCALC: setup_pri 1, hold_pri 1
*Aug 4 10:31:47.228: TE-PCALC: affinity_bits 0x0, affinity_mask 0xFFFF
*Aug 4 10:31:47.232: TE-PCALC_PATH: get_path:Dst ip addr 5.5.5.5 not found!

Clearly, this does not mean that 5.5.5.5 is not in the routing table,
because it is:

R1#show ip route isis
     2.0.0.0/32 is subnetted, 1 subnets
i L1 2.2.2.2 [115/110] via 10.1.2.2, FastEthernet1/0
     5.0.0.0/32 is subnetted, 1 subnets
i ia 5.5.5.5 [115/140] via 10.1.2.2, FastEthernet1/0
     10.0.0.0/24 is subnetted, 2 subnets
i L1 10.2.3.0 [115/110] via 10.1.2.2, FastEthernet1/0
i*L1 0.0.0.0/0 [115/100] via 10.1.2.2, FastEthernet1/0

As you can see, 5.5.5.5 is an inter-area route that I'm leaking to router A
from router B. I have no idea if that is causing this problem or not.

So, what is that error actually telling me? The path calculation is
failing, but I have no clue why. Is it possibly because of the way I have
routing configured and router A is not receiving the necessary TLVs related
to MPLS-TE or something like that?

Thanks,
John

Blogs and organic groups at http://www.ccie.net
Received on Sun Aug 04 2013 - 16:27:27 ART

This archive was generated by hypermail 2.2.0 : Sun Sep 01 2013 - 08:35:50 ART