The MPLS-OPS Archive

["Rajeev Manur" <rmanur@force10networks.com>]

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