deploying and managing ip over wdm networks - Index of

Management of the IP Network Layer 41
• The in-segment (mplsInSegmentTable) and out-segment (mplsOut-
SegmentTable) tables, which are used for configuring LSP segments at
an LSR;
• The cross-connect table (mplsXCTable), which is used to associate
input and output segments together, in order to form a cross connect;
• The label stack table (mplsLabelStackTable), which is used for specifying
label stack operations;
• The traffic parameter table (mplsTrafficParamTable), which is used for
specifying LSP-related traffic parameters;
• Moreover, the MPLS in-segment and out-segment performance tables,
mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the
objects necessary to measure the performance of LSPs, and the mplsInterfacePerfTable
has objects to measure MPLS performance on a perinterface
basis.
The MPLS-TE-MIB is based around a table that represents TE tunnels
that either originate at a given LSR or traverse or terminate on the LSR. The following
MPLS-TE-MIB tables can be used:
• Tunnel table (mplsTunnelTable) for setting up MPLS tunnels;
• Resource table (mplsTunnelResourceTable) for setting up the tunnel
resources;
• Tunnel specified, actual, and computed hop tables (mplsTunnel-
HopTable, mplsTunnelARHopTable, and mplsTunnelCHopTable)
for strict and loose source routed MPLS tunnel hops;
• Constraint-based LDP (CR-LDP) resource table (mplsTunnel-
CRLDPResTable) for specifying resource objects applicable to tunnels
signaled using CR-LDP.
3.3.3.2 Fault Management
The four MPLS-TE-MIB notifications, namely, mplsTunnelUp, mplsTunnel-
Down, mplsTunnelRerouted, and mplsTunnelReoptimized, give asynchronous
information about the status of the MPLS tunnels.
In case of a lack of the previously mentioned MPLS native MIBS, the
MIB-II objects linked to the mplsTunnel (150) at the interfaces group can be
used for MPLS monitoring. Also the conventional linkDown and linkUp traps
can be used for monitoring LSPs.