GMPLS-LSR-STD-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: GMPLS-LSR-STD-MIB
Download as:   

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
 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 no-access
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 no-access
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.
                   gmplsInterfaceSignalingCaps 1.3.6.1.2.1.10.166.15.1.1.1.1 bits read-only
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. Bits: 'unknown': 0, 'otherGmpls': 3, 'rsvpGmpls': 1, 'crldpGmpls': 2.
                   gmplsInterfaceRsvpHelloPeriod 1.3.6.1.2.1.10.166.15.1.1.1.2 unsigned32 read-only
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 no-access
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 no-access
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.
                   gmplsInSegmentDirection 1.3.6.1.2.1.10.166.15.1.2.1.1 gmplssegmentdirectiontc read-only
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).
                   gmplsInSegmentExtraParamsPtr 1.3.6.1.2.1.10.166.15.1.2.1.2 rowpointer read-only
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 no-access
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 no-access
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.
                   gmplsOutSegmentDirection 1.3.6.1.2.1.10.166.15.1.3.1.1 gmplssegmentdirectiontc read-only
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).
                   gmplsOutSegmentTTLDecrement 1.3.6.1.2.1.10.166.15.1.3.1.2 unsigned32 read-only
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).
                   gmplsOutSegmentExtraParamsPtr 1.3.6.1.2.1.10.166.15.1.3.1.3 rowpointer read-only
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.