The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: TE MIB - LSR MIB integration
Thomas D. Nadeau wrote: > At 12:20 PM 11/25/2002 +0100, Roberto.Guglielmi@alcatel.it wrote: > >> Hello everybody, >> I have a doubt about interactions between LSR MIB and TE MIB for what >> concerning LSPs nested in TE tunnels. >> Consider the following scenario: >> >> R1 -------- R2 -------- R3 >> >> and suppose, for example, I have three incoming flows. I want to >> insert each flow in one LSP and tunnel the three LSPs in one TE tunnel. >> My questions are: >> >> 1) How are the three LSPs mapped on the same TE tunnel? > > > Do you really want to map LSPs to the tunnel, or to the > outgoing LSP used for the tunnel? It sounds like what you are > describing is 3 LSPs entering an LSR and a tunnel beginning > at that LSR. If that is so, then you will have 3 LSPs that merge > onto the tunnel's LSP that begins at the same LSR. > >> 2) Is there only one entry in the mplsTunnelTable pointing to one >> entry in the mplsXCTable? >> >> 3) Does this entry in the mplsXCTable have a not-null >> mplsLabelStackTable? >> >> 4) How many entries are there in the mplsXCTable? And what LSP/TE >> tunnel do they refer to? >> >> 5) Are there four different entries in the mplsXCTable and in the >> mplsOutSegmentTable referring to a TE tunnel interface in the ifTable >> (by mplsOutSegmentIfIndex)? >> If not, how are, in the LSR MIB, the LSP entries correlated to the >> TE tunnel entry? > > > Assuming that the tunnel begins at the LSR in question, you > will should have 3 > incoming labels (one for each LSP) that go to the same XCentry, that > is also used > by the TE tunnel, so that everyone uses the same outgoing label (LSP). > > --Tom Tom, suppose I have three incoming Ethernet TLS flows on R1. Following Martini's draft, I should encapsulate Ethernet frames with a stack of two labels: the bottom label being the VC label, while the top label being the tunnel label. In other words, R1 has to push two labels on every incoming frame where the one at the top is always the same. I suppose each entry in mplsXCTable should point to a not null mplsLabelStackTable containing the corresponding VC label. If the tunnel label is set up by means of RSVP-TE and the VC label by means of LDP, how does R1 decides that the VC label has to be put in the mplsLabelStackTable and not in a new separate entry in mplsXCTable? What information of the RSVP messages are used to accomplish this? Will the entries in mplsTunnelTable be 3, each entry with a different mplsTuunnelInstance set to the LSPID? The mplsTunnelInstance "Uniquely identifies an instance of a tunnel. It is useful to identify multiple instances of tunnels for the purposes of backup and parallel tunnels." Thanks Roberto > > > >> Thanks in advance for your help. >> Regards Roberto. >> >> ------- >> The MPLS-OPS Mailing List >> Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > Success is relative; the more success, the more relatives. -Anonymous > > > ------- > 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
|
|