MPLS-LSR-EXT-STD-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: MPLS-LSR-EXT-STD-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, MPLS-TC-STD-MIB, MPLS-LSR-STD-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
 mplsLsrExtStdMIB 1.3.6.1.2.1.10.166.19
This MIB module contains generic object definitions for MPLS LSRs in transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
       mplsLsrExtNotifications 1.3.6.1.2.1.10.166.19.0
       mplsLsrExtObjects 1.3.6.1.2.1.10.166.19.1
           mplsXCExtTable 1.3.6.1.2.1.10.166.19.1.1 no-access
This table sparse augments the mplsXCTable of MPLS-LSR-STD-MIB (RFC 3813) to provide MPLS-TP-specific information about associated tunnel information
               mplsXCExtEntry 1.3.6.1.2.1.10.166.19.1.1.1 no-access
An entry in this table sparsely extends the cross-connect information represented by an entry in the mplsXCTable in MPLS-LSR-STD-MIB (RFC 3813) through a sparse augmentation. An entry can be created by a network operator via SNMP SET commands or in response to signaling protocol events.
                   mplsXCExtTunnelPointer 1.3.6.1.2.1.10.166.19.1.1.1.1 rowpointer read-only
This read-only object indicates the back pointer to the tunnel entry segment. The only valid value for Tunnel Pointer is mplsTunnelTable entry.
                   mplsXCExtOppositeDirXCPtr 1.3.6.1.2.1.10.166.19.1.1.1.2 rowpointer read-only
This object indicates the pointer to the opposite- direction XC entry. This object cannot be modified if mplsXCRowStatus for the corresponding entry in the mplsXCTable is active(1). If this pointer is not set or removed, mplsXCOperStatus should be set to down(2).
       mplsLsrExtConformance 1.3.6.1.2.1.10.166.19.2
           mplsLsrExtCompliances 1.3.6.1.2.1.10.166.19.2.1
               mplsLsrExtModuleFullCompliance 1.3.6.1.2.1.10.166.19.2.1.1
Compliance statement for agents that provide full support for MPLS-LSR-EXT-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.
               mplsLsrExtModuleReadOnlyCompliance 1.3.6.1.2.1.10.166.19.2.1.2
Compliance requirement for implementations that only provide read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
           mplsLsrExtGroups 1.3.6.1.2.1.10.166.19.2.2
               mplsXCExtGroup 1.3.6.1.2.1.10.166.19.2.2.1
This object should be supported in order to access the tunnel entry from the XC entry.
               mplsXCExtReadOnlyObjectsGroup 1.3.6.1.2.1.10.166.19.2.2.2
This Object is needed to associate the opposite-direction (forward/reverse) XC entry.