The MPLS-OPS Archive

["Shane Sexton" <wsexton@nextlec.net>]

Not sure why its not working on yours, I have a lot of explicit path tunnels
defined and they are using the next-address of the next hop. I tried to use
the "desired" local interface address and it seemed to ignore it.

Something I did note, do you have the remote address of 21.21.21.1 in your
explicit-path?

Below is a config I tested in the lab:

===================================
show mpls traffic-eng tunnels destination 10.10.10.9
===================================
Name: c12012-1_t9                 (Tunnel9) Destination: 10.10.10.9
  Status:
    Admin: up         Oper: up     Path: valid       Signalling: connected

    path option 9, type explicit 9 (Basis for Setup, path weight 2)

  Config Paramters:
    Bandwidth:  750       Priority: 1  1   Affinity: 0x0/0xFFFF
    AutoRoute:  enabled   LockDown: disabled  Loadshare: 750      bw-based

  InLabel  :  -
  OutLabel : Serial2/6, implicit-null
  RSVP Signalling Info:
       Src 10.10.10.1, Dst 10.10.10.9 Tun_Id 9, Tun_Instance 3622
    RSVP Path Info:
      My Address: 10.10.10.1
      Explicit Route: 10.10.9.186 10.10.10.9
      Record   Route:  NONE
      Tspec: ave rate=750 kbits, burst=1000 bytes, peak rate=750 kbits
    RSVP Resv Info:
      Record   Route:  NONE
      Fspec: ave rate=750 kbits, burst=1000 bytes, peak rate=Inf

=========
Explicit Path
=========
c12012-1#sh ip explicit-paths identifier 9
PATH 9 (strict source route, path complete, generation 10)
    1: next-address 10.10.9.185
    2: next-address 10.10.9.186

========
Tunnel conf:
========
!
interface Tunnel9
 ip unnumbered Loopback0 # loopback 10.10.10.1
 no ip directed-broadcast
 tunnel destination 10.10.10.9 # loopback address end of tunnel
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng autoroute announce
 tunnel mpls traffic-eng priority 1 1
 tunnel mpls traffic-eng bandwidth 750
 tunnel mpls traffic-eng path-option 9 explicit identifier 9
!

=============
Outbound Interface
=============
interface Serial2/6
 ip address 10.10.9.185 255.255.255.252
 no ip directed-broadcast
 no ip mroute-cache
 load-interval 30
 mpls traffic-eng tunnels
 tag-switching ip
 ip rsvp bandwidth 1000 1000

Hope this helps...

--
Shane Sexton
Director of Network Operations
Nextlec, A Division of Talon Communications
phone: (423) 664-8000
url: <http://www.nextlec.net>

----- Original Message -----
From: "Rajeev Manur" <rmanur@force10networks.com>
To: "'Shane Sexton'" <wsexton@nextlec.net>
Cc: <mpls-ops@mplsrc.com>
Sent: Saturday, April 21, 2001 8:25 PM
Subject: RE: Question on enabling RSVP-TE signalling on GSR


It's a one hop LSP. Explicit path is giving the outgoing interface and the
tunnel destination is given the connected peer's IP addr. Even in Cisco's
doc example cfg, the path definition starts with the outgoing interface. The
nexthop is actually the tunnel destination. Are you sure even in this
scenario we have to give the same nexthop both as the tunnel destination and
also in the explicit-path definition..

with ragards,
Rajeev


-----Original Message-----
From: Shane Sexton [mailto:wsexton@nextlec.net]
Sent: Saturday, April 21, 2001 5:14 PM
To: Rajeev Manur
Subject: Re: Question on enabling RSVP-TE signalling on GSR


You have to specify the next hop as the next-address not the local
interface...

Try this:

!
ip explicit-path identifier 1 enable
 next-address 21.21.21.1
!
--
Shane Sexton
Director of Network Operations
Nextlec, A Division of Talon Communications
phone: (423) 664-8000
url: <http://www.nextlec.net>

----- Original Message -----
From: "Rajeev Manur" <rmanur@force10networks.com>
To: <mpls-ops@mplsrc.com>
Sent: Saturday, April 21, 2001 5:21 PM
Subject: Question on enabling RSVP-TE signalling on GSR


Here is the test setup :

GSR is the head-end of an explicit LSP. One of the interfaces of GSR is
configured with 21.21.21.3/24 as the ip addr. I am seeding the cfg below. I
have also truned all the debug messages. I don't see GSR initiating RSVP
signalling ? I would appreciate if any one can help me figure out the
problem in my cfg..

with regards,
Rajeev

global config dump :
==============
!
ip subnet-zero
ip ftp username anvltest
ip ftp password 7 03025419050A701C
no ip domain-lookup
ip host linuxx 172.16.1.239
ip host linux 25 172.16.1.51
ip name-server 198.6.1.1
clns routing
mpls traffic-eng tunnels
!

Tunnel configuration :
===============

!
interface Tunnel1
 description First tunnel to pass through the F10-box
 ip unnumbered Loopback11
 no ip directed-broadcast
 tunnel destination 21.21.21.1   # this is the ip addr of connected peer.
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng priority 1 1
 tunnel mpls traffic-eng bandwidth 100
 tunnel mpls traffic-eng path-option 1 explicit identifier 1
!


physical interface configuration dump :
===========================
!
interface FastEthernet0/4
 ip address 21.21.21.3 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 mpls traffic-eng tunnels
 ip rsvp bandwidth 1000 1000
!

path configuration :
show ip explicit-paths identifier 1
PATH 1 (strict source route, path complete, generation 14)
    1: next-address 21.21.21.3


120008-1#show mpls traffic-eng tunnels Tunnel 1

Name: First tunnel to pass through the... (Tunnel1) Destination: 21.21.21.1
  Status:
    Admin: up         Oper: down   Path: not valid   Signalling: Down
    path option 1, type explicit 1

  Config Paramters:
    Bandwidth:  100       Priority: 1  1   Affinity: 0x0/0xFFFF
    AutoRoute:  disabled  LockDown: disabled





-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml




-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml