RIVERSTONE-MPLS-MIB

All MIBs › RIVERSTONE-MPLS-MIB

Organization: Riverstone Networks, Inc.

Last Updated: 2002-05-24

Category: MPLS, Riverstone Networks

Description: Manages MPLS label switching configuration, LSP status, and traffic engineering on Riverstone routers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is RIVERSTONE-MPLS-MIB?

RIVERSTONE-MPLS-MIB is a Riverstone Networks enterprise MIB for managing MPLS (Multiprotocol Label Switching) on Riverstone routers, covering cross-connect entries, label-switched path state, and protection/detour mechanisms, plus a notification framework for MPLS events. It exposes configuration objects (cross-connect type, detour and secondary cross-connect associations) and operational status (extended operational status per cross-connect) alongside trap enable/prefix controls. For software/hardware status monitoring, it's used to confirm that label-switched paths and their protection/detour paths are in the expected operational state, and to receive traps when an LSP transitions state, such as a primary path failing over to its detour. It is implemented as a Riverstone-specific private enterprise MIB rather than direct reuse of the IETF MPLS-LSR-MIB/MPLS-TE-MIB, though it parallels similar concepts. It's deployed on Riverstone routers providing MPLS transport/traffic engineering in carrier or enterprise backbone networks. Engineers can download the RIVERSTONE-MPLS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in RIVERSTONE-MPLS-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

Riverstone Networks router

Monitoring Examples

Polling rsMPLSXCExtTable/rsMPLSXCExtEntry for rsMPLSXCExtendedOperStatus on a given cross-connect reveals whether an LSP is actively forwarding traffic or has failed. rsMPLSXCDetourXC and rsMPLSXCSecondaryXC let an operator confirm a detour or secondary path is correctly associated with its primary, and enabling rsMPLSEnableNotifications means the router emits an rsMPLSNotification trap the moment a monitored cross-connect's status changes, such as during a protection switchover.

What Can Be Monitored

cross-connect type
cross-connect operational status
detour/secondary path association
MPLS notification/trap configuration

Imported Objects

From MPLS-LSR-MIB

mplsXCEntry	OBJECT-TYPE
mplsXCOperStatus	OBJECT-TYPE

From RIVERSTONE-SMI-MIB

riverstoneMibs

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

RowPointer
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
rsMPLSCompliance	1.3.6.1.4.1.5567.2.39.3.1.1			The compliance statement for SNMP entities which implement the Riverstone Router Config Management MIB.
rsMPLSCompliances	1.3.6.1.4.1.5567.2.39.3.1
rsMPLSConformance	1.3.6.1.4.1.5567.2.39.3
T/F rsMPLSEnableNotifications	1.3.6.1.4.1.5567.2.39.2.1.1	TruthValue	read-write	When this object is set to True(1), the notifications will be sent out depending upon the events. If set to False(2), the notifications will not go out. By default, the notifications are disabled.
NTF rsMPLSEndedDetourUse	1.3.6.1.4.1.5567.2.39.2.2.0.4			This notification is generated when the original next hop is reachable, and the regular path is used. At this point the the data will go through the regular next hop. The object included is the OperationalStatus of the cross-connect of the original LSP. This notificiation is generated by the ingress-router of the detour LSP.
rsMPLSGroups	1.3.6.1.4.1.5567.2.39.3.2
NTF rsMPLSLSPPreempted	1.3.6.1.4.1.5567.2.39.2.2.0.5			This notification is generated when a higher priority LSP pre-empts and tears down a lower priority LSP. The lower priority LSP then can use a detour or go down. The objects included are the OperationalStatus of the cross-connect of the higher priority LSP and that of the lower priority LSP. This notificiation is generated by the hop of the LSP where the pre-emption takes place.
rsMPLSLSRExtensionGroup	1.3.6.1.4.1.5567.2.39.3.2.1			The collection of objects which are extended from MPLS-LSR-MIB.
rsMPLSMIB	1.3.6.1.4.1.5567.2.39			This mib module defines an SNMP API to manage Riverstone's MPLS module
rsMPLSNotification	1.3.6.1.4.1.5567.2.39.2
rsMPLSNotificationControl	1.3.6.1.4.1.5567.2.39.2.1
rsMPLSNotificationControlGroup	1.3.6.1.4.1.5567.2.39.3.2.3			This object is mandatory to control emission of notifications, when the SNMP-NOTIFICATION-MIB is not available in a given agent.
rsMPLSNotificationGroup	1.3.6.1.4.1.5567.2.39.3.2.2			Set of notifications implemented in this module.
rsMPLSNotifications	1.3.6.1.4.1.5567.2.39.2.2
rsMPLSNotifyPrefix	1.3.6.1.4.1.5567.2.39.2.2.0
rsMPLSObjects	1.3.6.1.4.1.5567.2.39.1
NTF rsMPLSPrimaryPathFailOver	1.3.6.1.4.1.5567.2.39.2.2.0.1			This notification is generated when the primary LSP goes down and the secondary path (if any) takes over. First the Fast Reroute mecahnism will try to use the primary path. For this event, fast reroute notification will be generated. If this does not exist or if this also fails, then only will this notification will be generated and the seconday path will take over. The variables included are the operational status of the primary path that failed and the secondary path that took over. This notificiation is generated by the ingress-router of the LSP.
NTF rsMPLSPrimaryPathTakeOver	1.3.6.1.4.1.5567.2.39.2.2.0.2			This notification is generated when the primary LSP comes back up and takes over from the secondary path. This notificiation is generated by the ingress-router of the LSP.
NTF rsMPLSStartedDetourUse	1.3.6.1.4.1.5567.2.39.2.2.0.3			This notification is generated when the Detour LSP is used to circumvent the next hop in the LSP. The objects included are the OperationalStatus of the cross-connect of the original LSP and the operational status of the detour LSP being used. This notificiation is generated by the ingress-router of the detour LSP.
NUM rsMPLSXCDetourXC	1.3.6.1.4.1.5567.2.39.1.1.1.3	RowPointer	read-only	A pointer to a conceptual row in the mplsXCTable. This object is set to the ZeroDotZero OID by default. Whenever the LSP identified by this cross-connect uses a detour, this object is set to point to the cross-connect which acts as a detour for this LSP. At this time, the rsMPLSExtOperStatus will set to the value of rerouted (8).
INT rsMPLSXCExtendedOperStatus	1.3.6.1.4.1.5567.2.39.1.1.1.2	INTEGER	read-only	This object is the same as the mplsXCOperStatus during the normal operation. If the LSP has a Detour (Fast Reroute LSP), this value is set to rerouted (8), when the detour is used for transmitting the data path. At this time, the rsMPLSXCDetourXC will point to the cross-connect of the detour LSP. The mplsOutSegmentTopLabel value of the outsegment of this LSP will be set to 0 (invalid label). When this LSP comes back up, again the value will change as mplsXCOperStatus and the rsMPLSXCDetourXC will be set to the ZeroDotZero OID. Also the mplsOutSegmentTopLabel will be set to the proper value.
rsMPLSXCExtEntry	1.3.6.1.4.1.5567.2.39.1.1.1		not-accessible	An entry in this table supplies additional necessary parameters like whether rerouted or not, detour LSP, secondary LSP.
rsMPLSXCExtTable	1.3.6.1.4.1.5567.2.39.1.1		not-accessible	This table specifies extra parameters which might be of interest to a SNMP manager, which are not present in the mplsXCTable.
NUM rsMPLSXCSecondaryXC	1.3.6.1.4.1.5567.2.39.1.1.1.4	RowPointer	read-only	A pointer to a conceptual row in the mplsXCTable. This object is set to the ZeroDotZero OID by default. This object is valid only in case of Ingress LSRs. If the LSP identified by this cross-connect is a primary, and when this LSP goes down, and if there is a secondary LSP, this cross-connect is not torn down. In stead, the mplsXCOperStatus will be set to down, the mplsOutSegmentTopLabel identified by the out segment of the cross-connect is set to 0 (invalid label). At this time, this object is set to point to the cross-connect which acts as the secondary LSP. Note that, this is the last resort. First the mpls engine will try to use a detour. If no detours are configured or up, then only will it use the secondary LSP.
INT rsMPLSXCType	1.3.6.1.4.1.5567.2.39.1.1.1.1	INTEGER	read-only	This object reflects the type of the LSP. In case of ingress, this reports whether it is a primary or secondary or detour for some other LSPs.

RFC description

MPLS label switching module management with cross-connect extensions for traffic engineering.

Start monitoring Riverstone Networks router (MPLS cross-connect/LSP protection/detour status) 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 RIVERSTONE-MPLS-MIB

What Is RIVERSTONE-MPLS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description