The MPLS WG Archive

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

         Hi Ron,

>I am an operator with MPLS deployed in my network. For fault management
>purposes, I need to know the following:
>
>         -> which LSPs are broken
>         -> which LSPs are sub-optimally routed
>         -> which LSPs have reset
>
>Using Kireeti's MIB, I can answer these questions by polling the following
>items:
>
>         -> mplsLspState
>         -> mplsPathType
>         -> mplsLspLastPathChange
>
>This is pretty simple.
>
>Couldn't this level of abstraction be applied to any MPLS implementation?

         Yes. These were precisely some of the salient features
from Kireeti's MIB which we were trying to incorporate into
the MPLS-TE-MIB. However, we need Kireeti's and the TE WG's
help to make sure that these are really the things that people
need added. FYI, these attributes can be easily added to the
mplsTunnelTable in the MPLS-TE-MIB. It may also be favorable to
add traps for these state changes rather than polling.

>Please re-orient me if I am missing some very fundamental issue.

         Nope. Makes perfect sense to me.

         --Tom