The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Jan> msg00159



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

mpls lsr mib

  • From: francis.arts@alcatel.be
  • Date: Thu, 24 Jan 2002 17:05:03 +0100
  • Cc: Alia Atlas <aatlas@avici.com>, mpls@UU.NET
  • X-MIMETrack: Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.8 |June 18, 2001) at01/24/2002 17:05:15,Serialize complete at 01/24/2002 17:05:15


Tom,

Thanks for your response. It already answers part of my question. Can you indicate which value the xaMplsIfConfLabelMinIn should have for a row with ifIndex /= 0:
* The min label value of the **per interface** label space.
OR
* The min label value of all the labels in the per interface **and** per platform label spaces.

Best regards,

        Francis.

----------------------------



"Thomas D. Nadeau" <tnadeau@cisco.com>

24/01/2002 16:43

       
        To:        Alia Atlas <aatlas@avici.com>
        cc:        Francis ARTS/BE/ALCATEL@ALCATEL, mpls@UU.NET
        Subject:        Re: mpls lsr mib





> >>Hello Tom et all,
> >>
> >>I have a question on the mplsInterfaceConfTable in the mpls lsr mib.
> >>IAssume that we consider the following:
> >>* Per interface label space used for RSVP signalled LSPs and static LSPs.
> >>* Global label space used for LDP signalled LSPs.
> >
> >         First, how can you use two different label spaces to advertise over
> >the same interface?  I have never heard of this behavior before. One
> >assigns a per-interface label range that is unique for that interface
> >only, no?
>
>Having LDP use global labels while RSVP-TE LSPs use per interface labels is
>reasonable; certainly, I've heard of it before.  One can partition the
>label range given out, so that one range is for the global labels, while
>the other is for per-interface.

        Yes, it is within the realm of possibility to configure your label
ranges that way. However, what you are talking about is per-application
label space configuration, which is not what the MIB variable is getting at.
It is used to represent per-interface label range configuration or per-platform
label range configuration. These values are configured on interfaces, not on
applications. If you want to divide up the range further (i.e.: per
application),
that is something the MIB was not intended to do.

        --Tom



>Alia
>
> >>Which value should we then give to the mplsInterfaceLabelMinIn:
> >>* The min label value of the per interface label space (that is, the min
> >>label value from the RSVP signalled LSPs and the static LSPs)?
> >>* The min label value of the RSVP signalled LSPs.
> >>* The min label value of all LSPs on the interface (=min of all LDP
> >>signalled, RSVP signalled and static LSPs).
> >>
> >>I would appreciate any help you can give me.
> >>
> >>Kind regards,
> >>
> >>         Francis.
> >>
> >>--------------------------------
> >>
> >>OBJECT-TYPE
> >>    SYNTAX        MplsLabel
> >>    MAX-ACCESS    read-only
> >>    STATUS        current
> >>    DESCRIPTION
> >>        "This is the minimum value of an MPLS label that this
> >>         LSR is willing to receive on this interface."
> >>    ::= { mplsInterfaceConfEntry 2 }
> >
> >
> >
> >------------------------------------------------------------------------
> >Mathematics is the supreme nostalgia of our time.
> >



------------------------------------------------------------------------
Mathematics is the supreme nostalgia of our time.