The MPLS-OPS Archive

["Carlos Patriawan" <carlos@carlos.net>]

----- Original Message ----- 
From: "Sriram" <send4sri@yahoo.com>
To: "Carlos Patriawan" <carlos@carlos.net>; <mpls-ops@mplsrc.com>
Sent: Thursday, February 12, 2004 9:10 PM
Subject: Re: [MPLS-OPS]: Multiple LSP between source and destination


> 
> RFC says Tunnel-id uniquely defines a traffic
> engineered tunnel. If 2 LSP are part of same traffic
> engineered tunnel then tunnel-id is same.So its LSP
> ID which varies when 2 paths are set up between
> same source and destination.
> 

Actually even if you have such configuration that has
primary and secondary/standby lsp travel from the
same head-end to the same tail-end node,it still has 
different tunnel-id as it is separate reservation.

What you mention above is only possible when user
force make-before-break(for example,by increasing
LSP bandwidtj) with SE style only.

Thanks,


Carlos


> But isn't this similar to tunnel bandwidth increase
> procedure defined in RFC ?.My question is what object
> is used to differentiate tunnel bandwidth procedure
> and setting up of 2 LSP ? Tunnel bandwidth increase
> requires resv with STYLE shared explicit but 2 LSP
> set up requires resv with STYLE Fixed Format.
> 
> Thanks
> Sriram
> 
> 
> 
> 
> --- Carlos Patriawan <carlos@carlos.net> wrote:
> > There're 5 tuples in rsvp object that should be used
> > to differentiate lsp:
> >  Tunnel endpoint (egress) address (in SESSION
> > object)
> >  Tunnel ID (in SESSION object)
> >  Extended Tunnel ID (in SESSION object)
> >  Sender (ingress) address (in
> > SENDER_TEMPLATE/FILTER_SPEC object)
> >  LSP ID (in SENDER_TEMPLATE/FILTER_SPEC object
> > 
> > In one platform,even when ingress and egress
> > destination is the same,
> > tunnel-id/lsp-id pairs is unique. Tunnel-id (and/or
> > lsp-id) may also 
> > increasing if lsp is flapping.
> > 
> > Thanks,
> > 
> > Carlos
> > 
> > 
> > ----- Original Message ----- 
> > From: "Sriram" <send4sri@yahoo.com>
> > To: <mpls-ops@mplsrc.com>
> > Sent: Thursday, February 12, 2004 1:33 AM
> > Subject: [MPLS-OPS]: Multiple LSP between source and
> > destination
> > 
> > 
> > > Hi all,
> > > 
> > > How is multiple LSP's  having "seperate resource
> > > reservation"  established between source and
> > > destination when LSPs share same route ?
> > > 
> > > Let say we want 2 LSP between A and B which take
> > > same path in MPLS cloud. When 2nd LSP is setup
> > > what field in path message is used by A to prevent
> > > B from replying with Resv msg with STYLE shared
> > > explicit ?
> > > 
> > > 
> > > Thanks
> > > Sriram
> > > 
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Finance: Get your refund fast by filing
> > online.
> > > http://taxes.yahoo.com/filing.html
> > > 
> > > -------
> > > 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
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> http://taxes.yahoo.com/filing.html
> 
> -------
> 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