The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: Multiple LSP between source and destination
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
|
|