The MPLS-OPS Archive

[Robert Raszuk <raszuk@cisco.com>]

Hi Rajeev,

> Do we need IGP-TE cfg for "explicit"
> path LSP setup too. 

I believe you do. We don't have a direct analogy command to juniper's
"no-cspf". The closest one is path option with the "verbatim" keyword
which you could use. In that case the database check is disabled. Pls
open a case with TAC for their assistance if you need one. 

The (I believe still hidden and not officially supported) would be: 

"tunnel mpls traffic-eng path-option 1 explicit name vpn-123 verbatim"

R.

> Rajeev Manur wrote:
> 
> I am trying to setup the explicit path. Do we need IGP-TE cfg for "explicit"
> path LSP setup too. I do not want to use cspf/dynamic path  computation..
> 
> with regards,
> Rajeev
> 
> -----Original Message-----
> From: Martin, Christian [mailto:cmartin@gnilink.net]
> Sent: Saturday, April 21, 2001 5:32 PM
> To: 'Rajeev Manur'; mpls-ops@mplsrc.com
> Subject: RE: Question on enabling RSVP-TE signalling on GSR
> 
> Have you enabled your link-state IGP to advertise TE extensions?
> 
> router isis
>  metric-style wide
>  mpls traffic-eng level-2 (and/or level-1)
> 
> ./chris
> 
> > -----Original Message-----
> > From: Rajeev Manur [mailto:rmanur@force10networks.com]
> > Sent: Saturday, April 21, 2001 5:22 PM
> > To: mpls-ops@mplsrc.com
> > 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

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