RIVERSTONE-MPLS-MIB: View SNMP OID List / Download MIB

VENDOR: RIVERSTONE NETWORKS


 Home MIB: RIVERSTONE-MPLS-MIB
Download as:   
SNMPv2-CONF, RIVERSTONE-SMI-MIB, SNMPv2-SMI, MPLS-LSR-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 rsMPLSMIB 1.3.6.1.4.1.5567.2.39
This mib module defines an SNMP API to manage Riverstone's MPLS module
       rsMPLSObjects 1.3.6.1.4.1.5567.2.39.1
           rsMPLSXCExtTable 1.3.6.1.4.1.5567.2.39.1.1 no-access
This table specifies extra parameters which might be of interest to a SNMP manager, which are not present in the mplsXCTable.
               rsMPLSXCExtEntry 1.3.6.1.4.1.5567.2.39.1.1.1 no-access
An entry in this table supplies additional necessary parameters like whether rerouted or not, detour LSP, secondary LSP.
                   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. Enumeration: 'nonIngress': 3, 'primaryNoSecondary': 4, 'unknown': 1, 'primary': 5, 'detour': 7, 'other': 2, 'secondary': 6.
                   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. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'rerouted': 8, 'notPresent': 6.
                   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).
                   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.
       rsMPLSNotification 1.3.6.1.4.1.5567.2.39.2
           rsMPLSNotificationControl 1.3.6.1.4.1.5567.2.39.2.1
               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.
           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
                   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.
                   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.
                   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.
                   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.
                   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.
       rsMPLSConformance 1.3.6.1.4.1.5567.2.39.3
           rsMPLSCompliances 1.3.6.1.4.1.5567.2.39.3.1
               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.
           rsMPLSGroups 1.3.6.1.4.1.5567.2.39.3.2
               rsMPLSLSRExtensionGroup 1.3.6.1.4.1.5567.2.39.3.2.1
The collection of objects which are extended from MPLS-LSR-MIB.
               rsMPLSNotificationGroup 1.3.6.1.4.1.5567.2.39.3.2.2
Set of notifications implemented in this module.
               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.