Last Error: PCALC:: No addresses to connect 10.127.1.70 to 10.127.1.26 ?

[ปลาวาฬทราย RMUTT CPE IX]

What should I do

b2#sho mpl tra tun tun 3500 | inc Err
      Last Error: PCALC:: No addresses to connect 10.127.1.70 to 10.127.1.26

b2#10.127.1.70                      
Trying 10.127.1.70 ... Open

RP/0/RP1/CPU0:k1#sho ip int bri | inc 70
POS0/2/0/0                     10.127.1.70     Up                    Up     

RP/0/RP1/CPU0:k1#sho ip int bri | inc 25
TenGigE0/0/0/5                 10.127.1.25     Up                    Up     

RP/0/RP1/CPU0:k1#sho rsv int
Interface   MaxBW (bps) MaxFlow (bps) Allocated (bps)      MaxSub (bps)
----------- ----------- ------------- -------------------- ------------
Te0/0/0/5           10G           10G             0 (  0%)            0
PO0/2/0/0           40G           40G             0 (  0%)            0

RP/0/RP1/CPU0:k1#sho run rsv
rsvp
interface POS0/2/0/0
  bandwidth 40000000
!
interface TenGigE0/0/0/5
  bandwidth 10000000

!

!

RP/0/RP1/CPU0:k1#sho run mpl tra
mpls traffic-eng
interface POS0/2/0/0
  bfd fast-detect
!
interface TenGigE0/0/0/5
  bfd fast-detect
!

!

RP/0/RP1/CPU0:k1#exi

[Connection to 10.127.1.70 closed by foreign host]

b2#10.127.1.26
Trying 10.127.1.26 ... Open

k9#sho ip int bri | inc 7.1.26
TenGigabitEthernet4/4  10.127.1.26     YES manual up                    up     

k9#sho ip rsv int
interface    rsvp       allocated  i/f max  flow max sub max
Te4/4        ena        1G         10G      10G      0  

k9#sho run int te4/4
Building configuration...

Current configuration : 350 bytes
!
interface TenGigabitEthernet4/4
mtu 9000
ip address 10.127.1.26 255.255.255.252
ip router isis
ip pim sparse-mode
load-interval 30
mpls traffic-eng tunnels
mpls ip
isis circuit-type level-2-only
isis network point-to-point
isis metric 1000
ip rsvp bandwidth 10000000
end

Thank you very much.

[Muhammad Thanveer]

Hello, You must have a global command mpls label protocol ldp, You must have a mpls ldp neighbor relation ship between the routers which come in to picture when you are trying to do MPLS Traffic Engineering.

Your IGP Protocol ISIS or OSPF must be ready for MPLS Traffic engineering.

then after as per your configuration there must be Explicit or Dynamic Path.

There must be a tunnel in which you call your path-option.

Later there should be a static route for the intended destination via the tunnel which you have your path option set.

Please rate the helpful answers/discussions.

Regards
Thanveer
"Everybody is genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is a stupid."

[Andre Gustavo Albuquerque]

Make sure you share more information about the configuration of the involved parties in order to get a faster and precise response.

Some general recommendations:

- ISIS TE extension requires wide metrics;

- If ISIS is being used for IPv4 and IPv6, and you have a mix of IOS and IOS-XR in your environment, change the ISIS configuration on IOS to operate in multi-topology mode.

- Check if mpls-te and rsvp-te is enabled at all interfaces in the path between head end and tail end.

HTH

[Yasir nawaz]

I have configured MPLS tunnel in GNS3 but tunnels is unable to come up.

Both head and tail routers are pingable through OSPF with loopback interfaces.

Can anyone tell me where I am committing mistake?

R2#show mpls traf tu tu26

Name: R2_t26                              (Tunnel26) Destination: 9.9.0.6
  Status:
    Admin: up         Oper: down   Path: not valid   Signalling: Down
    path option 1, type explicit 26

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

  Shortest Unconstrained Path Info:
    Path Weight: UNKNOWN
    Explicit Route:  UNKNOWN
  History:
    Tunnel:
      Time since created: 5 minutes, 32 seconds
      Number of LSP IDs (Tun_Instances) used: 12
    Path Option 1:
      Last Error: PCALC:: Destination IP address, 9.9.0.6, not found

R2#ping 9.9.0.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 9.9.0.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/107/120 ms

__________________________________________________

R6#show mpls traf tu tu62

Name: R6_t62                              (Tunnel62) Destination: 9.9.0.2
  Status:
    Admin: up         Oper: down   Path: not valid   Signalling: Down
    path option 1, type explicit 62

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

  Shortest Unconstrained Path Info:
    Path Weight: UNKNOWN
    Explicit Route:  UNKNOWN
  History:
    Tunnel:
      Time since created: 6 minutes, 59 seconds
      Number of LSP IDs (Tun_Instances) used: 15
    Path Option 1:
      Last Error: PCALC:: Destination IP address, 9.9.0.2, not found

R6#ping 9.9.0.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 9.9.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 72/96/120 ms

[Muhammad Thanveer]

can u please share the tunnel config along with protocol config for TE, note that your LSP should be continuos.

[Giuseppe Larosa]

Hello PlaWAnSai,

you haven't provided enough information to be helped effectively.

The most important configuration object to see is tunnel 3500 that should be defined on node named b2.

If you have used an explicit path for the MPLS TE tunnel tu3500 you may need to list both the endpoints of a TE link instead of simply listing

10.127.1.70 10.127.1.26 in the path definition you may need something like the following:

10.127.1.69 10.127.1.70 10.127.1.25 10.127.1.26

At least so it was with explicit paths some years ago if I remember correctly at least on LAN broadcast interfaces

You don't need to enable LDP.

Hope to help

Giuseppe

[jpudasaini]

hi,

this is a very old thread but I would like to add something.

'Last Error: PCALC:: Destination IP address, xx.xx.xx.xx, not found ' this means there is missing configuration in the TE tunnel. Please verify every router to configure tunnel into IGP protocol. Somewhere TE tunnel was not configure into the IGP protocol.

e.g (in-case of OSPF)

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