RIVERSTONE-MPLS-MIB

File: RIVERSTONE-MPLS-MIB.mib (12755 bytes)

Imported modules

SNMPv2-SMI RIVERSTONE-SMI-MIB SNMPv2-TC
MPLS-LSR-MIB SNMPv2-CONF

Imported symbols

OBJECT-TYPE MODULE-IDENTITY NOTIFICATION-TYPE
riverstoneMibs TruthValue RowPointer
mplsXCOperStatus mplsXCEntry MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP

Defined Types

RsMPLSXCExtEntry  
SEQUENCE    
  rsMPLSXCType INTEGER
  rsMPLSXCExtendedOperStatus INTEGER
  rsMPLSXCDetourXC RowPointer
  rsMPLSXCSecondaryXC RowPointer

Defined Values

rsMPLSMIB 1.3.6.1.4.1.5567.2.39
This mib module defines an SNMP API to manage Riverstone's MPLS module
MODULE-IDENTITY    

rsMPLSObjects 1.3.6.1.4.1.5567.2.39.1
OBJECT IDENTIFIER    

rsMPLSNotification 1.3.6.1.4.1.5567.2.39.2
OBJECT IDENTIFIER    

rsMPLSNotificationControl 1.3.6.1.4.1.5567.2.39.2.1
OBJECT IDENTIFIER    

rsMPLSNotifications 1.3.6.1.4.1.5567.2.39.2.2
OBJECT IDENTIFIER    

rsMPLSNotifyPrefix 1.3.6.1.4.1.5567.2.39.2.2.0
OBJECT IDENTIFIER    

rsMPLSXCExtTable 1.3.6.1.4.1.5567.2.39.1.1
This table specifies extra parameters which might be of interest to a SNMP manager, which are not present in the mplsXCTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    RsMPLSXCExtEntry

rsMPLSXCExtEntry 1.3.6.1.4.1.5567.2.39.1.1.1
An entry in this table supplies additional necessary parameters like whether rerouted or not, detour LSP, secondary LSP.
Status: current Access: not-accessible
OBJECT-TYPE    
  RsMPLSXCExtEntry  

rsMPLSXCType 1.3.6.1.4.1.5567.2.39.1.1.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), other(2), nonIngress(3), primaryNoSecondary(4), primary(5), secondary(6), detour(7)  

rsMPLSXCExtendedOperStatus 1.3.6.1.4.1.5567.2.39.1.1.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2), testing(3), unknown(4), dormant(5), notPresent(6), lowerLayerDown(7), rerouted(8)  

rsMPLSXCDetourXC 1.3.6.1.4.1.5567.2.39.1.1.1.3
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).
Status: current Access: read-only
OBJECT-TYPE    
  RowPointer  

rsMPLSXCSecondaryXC 1.3.6.1.4.1.5567.2.39.1.1.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  RowPointer  

rsMPLSEnableNotifications 1.3.6.1.4.1.5567.2.39.2.1.1
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

rsMPLSConformance 1.3.6.1.4.1.5567.2.39.3
OBJECT IDENTIFIER    

rsMPLSCompliances 1.3.6.1.4.1.5567.2.39.3.1
OBJECT IDENTIFIER    

rsMPLSGroups 1.3.6.1.4.1.5567.2.39.3.2
OBJECT IDENTIFIER    

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.
Status: current Access: read-write
MODULE-COMPLIANCE    

rsMPLSLSRExtensionGroup 1.3.6.1.4.1.5567.2.39.3.2.1
The collection of objects which are extended from MPLS-LSR-MIB.
Status: current Access: read-write
OBJECT-GROUP    

rsMPLSNotificationGroup 1.3.6.1.4.1.5567.2.39.3.2.2
Set of notifications implemented in this module.
Status: current Access: read-write
NOTIFICATION-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP