GMPLS-LSR-STD-MIB

All MIBs › GMPLS-LSR-STD-MIB

Organization: IETF Common Control And Measurement Plane (CCAMP) Working Group

Last Updated: 2007-02-27

Category: MPLS and Traffic Engineering

Description: Defines managed objects for configuring and monitoring Generalized MPLS (GMPLS) Label Switching Routers.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring GMPLS-LSR-STD-MIB with a free 30-day trial of IPNetwork Monitor.

What Is GMPLS-LSR-STD-MIB?

GMPLS-LSR-STD-MIB is a vendor-neutral IETF standards-track MIB (RFC 4803) defining managed objects for Generalized MPLS (GMPLS) Label Switching Routers, extending the MPLS-LSR-MIB model to cover non-packet switching types such as TDM, lambda, and fiber cross-connects as defined in the GMPLS architecture (RFC 3945). It exposes configuration and status data for GMPLS-capable interfaces and for in-segments and out-segments, which together represent the pieces of a label switched path as it passes through a router. Its monitoring value lies in confirming the software/control-plane health of GMPLS signaling and cross-connection: interface signaling capabilities and RSVP hello timers reveal whether the control-plane session with a neighbor is correctly configured, while in-segment/out-segment direction and TTL handling reveal whether a provisioned label switched path is cross-connected as expected end to end. It explicitly depends on the base MPLS-LSR-MIB and GMPLS architecture concepts from RFC 3945, and is typically used alongside RSVP-TE signaling MIBs. It is deployed on carrier-grade optical, TDM, and packet transport routers in GMPLS-enabled backbone and metro networks. Engineers implementing or auditing this functionality typically reference the GMPLS-LSR-STD-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in GMPLS-LSR-STD-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
GMPLS-capable label switching routers (optical, TDM, and packet transport routers)

Monitoring Examples

An operator polls gmplsInterfaceTable/gmplsInterfaceEntry to check gmplsInterfaceSignalingCaps and gmplsInterfaceRsvpHelloPeriod, confirming GMPLS signaling is enabled and hello timers match the neighboring node, which catches control-plane misconfiguration before it causes session flaps. Walking gmplsInSegmentTable and gmplsOutSegmentTable and comparing gmplsInSegmentDirection/gmplsOutSegmentDirection with gmplsOutSegmentTTLDecrement shows how each label switched path segment is cross-connected and whether TTL is being handled correctly, useful when verifying that a provisioned LSP is wired up end-to-end as intended.

What Can Be Monitored

GMPLS interface signaling capabilities
RSVP hello timer configuration
in-segment direction and parameters
out-segment direction and TTL handling
label switched path cross-connect status

Imported Objects

From GMPLS-TC-STD-MIB

GmplsSegmentDirectionTC

From IF-MIB

ifCounterDiscontinuityGroup	OBJECT-GROUP
ifGeneralInformationGroup	OBJECT-GROUP

From MPLS-LSR-STD-MIB

mplsInSegmentGroup	OBJECT-GROUP
mplsInSegmentIndex	OBJECT-TYPE
mplsInterfaceGroup	OBJECT-GROUP
mplsInterfaceIndex	OBJECT-TYPE
mplsLsrNotificationGroup	NOTIF-GROUP
mplsOutSegmentGroup	OBJECT-GROUP
mplsOutSegmentIndex	OBJECT-TYPE
mplsPerfGroup	OBJECT-GROUP
mplsXCGroup	OBJECT-GROUP

From MPLS-TC-STD-MIB

mplsStdMIB

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
zeroDotZero

From SNMPv2-TC

RowPointer

OIDs

OID symbolic	OID numeric	Type	Access	Description
gmplsLsrStdMIB	1.3.6.1.2.1.10.166.15			Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4803; see the RFC itself for full legal notices. This MIB module contains managed object definitions for the Generalized Multiprotocol (GMPLS) Label Switching Router as defined in Generalized Multi-Protocol Label Switching (GMPLS) Architecture, Mannie et al., RFC 3945, October 2004.
gmplsLsrObjects	1.3.6.1.2.1.10.166.15.1
gmplsInterfaceTable	1.3.6.1.2.1.10.166.15.1.1		not-accessible	This table specifies per-interface GMPLS capability and associated information. It extends the information in the mplsInterfaceTable of MPLS-LSR-STD-MIB through a sparse augmentation relationship.
gmplsInterfaceEntry	1.3.6.1.2.1.10.166.15.1.1.1		not-accessible	A conceptual row in this table is created automatically by an LSR for each interface that is both capable of supporting GMPLS and configured to support GMPLS. Note that support of GMPLS is not limited to control plane signaling, but may include data-plane-only function configured through SNMP SET commands performed on this MIB module. A conceptual row in this table may also be created via SNMP SET commands or automatically by the LSR to supplement a conceptual row in the mplsInterfaceTable where the interface is not capable of GMPLS but where the other objects carried in this row provide useful additional information for an MPLS interface. A conceptual row in this table will exist if and only if a corresponding entry in the mplsInterfaceTable exists, and a corresponding entry in the ifTable exists with ifType = mpls(166). If the associated entry in the ifTable is operationally disabled (thus removing the GMPLS capabilities on the interface) or the entry in the mplsInterfaceTable is deleted, the corresponding entry in this table MUST be deleted shortly thereafter. The indexes are the same as for the mplsInterfaceTable. Thus, the entry with index 0 represents the per-platform label space and contains parameters that apply to all interfaces that participate in the per-platform label space.
BIT gmplsInterfaceSignalingCaps	1.3.6.1.2.1.10.166.15.1.1.1.1	Bits	read-create	Defines the signaling capabilities on this interface. Multiple bits may legitimately be set at once, but if 'unknown' is set then no other bit may be set. Setting no bits implies that GMPLS signaling cannot be performed on this interface and all LSPs must be manually provisioned or that this table entry is only present to supplement an entry in the mplsInterfaceTable by providing the information carried in other objects in this row.
U32 gmplsInterfaceRsvpHelloPeriod	1.3.6.1.2.1.10.166.15.1.1.1.2	Unsigned32	read-create	Period, in milliseconds, between sending Resource Reservation Protocol (RSVP) Hello messages on this interface. A value of 0 indicates that no Hello messages should be sent on this interface. This object is only valid if gmplsInterfaceSignalingCaps has no bits set or includes the rsvpGmpls bit.
gmplsInSegmentTable	1.3.6.1.2.1.10.166.15.1.2		not-accessible	This table sparse augments the mplsInSegmentTable of MPLS-LSR-STD-MIB to provide GMPLS-specific information about incoming segments to an LSR.
gmplsInSegmentEntry	1.3.6.1.2.1.10.166.15.1.2.1		not-accessible	An entry in this table extends the representation of an incoming segment represented by an entry in the mplsInSegmentTable in MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events. Note that the storage type for this entry is given by the value of mplsInSegmentStorageType in the corresponding entry of the mplsInSegmentTable.
GMP gmplsInSegmentDirection	1.3.6.1.2.1.10.166.15.1.2.1.1	GmplsSegmentDirectionTC	read-create	This object indicates the direction of data flow on this segment. This object cannot be modified if mplsInSegmentRowStatus for the corresponding entry in the mplsInSegmentTable is active(1).
NUM gmplsInSegmentExtraParamsPtr	1.3.6.1.2.1.10.166.15.1.2.1.2	RowPointer	read-create	Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, Synchronous Optical Network (SONET) resource usage). Such can be supplied from an external table and referenced from here. A value of zeroDotZero in this attribute indicates that there is no such additional information.
gmplsOutSegmentTable	1.3.6.1.2.1.10.166.15.1.3		not-accessible	This table sparse augments the mplsOutSegmentTable of MPLS-LSR-STD-MIB to provide GMPLS-specific information about outgoing segments from an LSR.
gmplsOutSegmentEntry	1.3.6.1.2.1.10.166.15.1.3.1		not-accessible	An entry in this table extends the representation of an outgoing segment represented by an entry in the mplsOutSegmentTable of MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events. Note that the storage type for this entry is given by the value of mplsOutSegmentStorageType in the corresponding entry of the mplsOutSegmentTable.
GMP gmplsOutSegmentDirection	1.3.6.1.2.1.10.166.15.1.3.1.1	GmplsSegmentDirectionTC	read-create	This object indicates the direction of data flow on this segment. This object cannot be modified if mplsOutSegmentRowStatus for the corresponding entry in the mplsOutSegmentTable is active(1).
U32 gmplsOutSegmentTTLDecrement	1.3.6.1.2.1.10.166.15.1.3.1.2	Unsigned32	read-create	This object indicates the amount by which to decrement the Time to Live (TTL) of any payload packets forwarded on this segment if per-hop decrementing is being done. A value of zero indicates that no decrement should be made or that per-hop decrementing is not in use. See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable of GMPLS-TE-STD-MIB for a value by which to decrement the TTL for the whole of a tunnel. This object cannot be modified if mplsOutSegmentRowStatus for the associated entry in the mplsOutSegmentTable is active(1).
NUM gmplsOutSegmentExtraParamsPtr	1.3.6.1.2.1.10.166.15.1.3.1.3	RowPointer	read-create	Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, SONET resource usage). Such can be supplied from an external table and referenced from here. A value of zeroDotZero in this attribute indicates that there is no such additional information.
gmplsLsrConformance	1.3.6.1.2.1.10.166.15.2
gmplsLsrGroups	1.3.6.1.2.1.10.166.15.2.1
gmplsInterfaceGroup	1.3.6.1.2.1.10.166.15.2.1.1			Collection of objects that provide additional information for an MPLS interface and are needed for GMPLS interface configuration and performance information.
gmplsInSegmentGroup	1.3.6.1.2.1.10.166.15.2.1.2			Collection of objects that provide additional information for an MPLS in-segment and are needed for GMPLS in-segment configuration and performance information.
gmplsOutSegmentGroup	1.3.6.1.2.1.10.166.15.2.1.3			Collection of objects that provide additional information for an MPLS out-segment and are needed for GMPLS out-segment configuration and performance information.
gmplsLsrCompliances	1.3.6.1.2.1.10.166.15.2.2
gmplsLsrModuleFullCompliance	1.3.6.1.2.1.10.166.15.2.2.1			Compliance statement for agents that provide full support for GMPLS-LSR-STD-MIB. The mandatory group has to be implemented by all LSRs that originate, terminate, or act as transit for TE-LSPs/tunnels. In addition, depending on the type of tunnels supported, other groups become mandatory as explained below.
gmplsLsrModuleReadOnlyCompliance	1.3.6.1.2.1.10.166.15.2.2.2			Compliance requirement for implementations that only provide read-only support for GMPLS-LSR-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.

RFC description

Manages Generalized Multiprotocol Label Switching label switching router interfaces and operations.

Start monitoring Vendor-neutral GMPLS-capable optical/packet transport router or switch, any manufacturer (Label Switching Router, RFC 4803) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download GMPLS-LSR-STD-MIB

What Is GMPLS-LSR-STD-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description