MPLS-LC-ATM-STD-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: MPLS-LC-ATM-STD-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, MPLS-TC-STD-MIB, ATM-TC-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
 mplsLcAtmStdMIB 1.3.6.1.2.1.10.166.9
This MIB module contains managed object definitions for MPLS Label-Controlled ATM interfaces as defined in [RFC3035]. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4368; see the RFC itself for full legal notices.
     mplsLcAtmStdNotifications 1.3.6.1.2.1.10.166.9.0
     mplsLcAtmStdObjects 1.3.6.1.2.1.10.166.9.1
         mplsLcAtmStdInterfaceConfTable 1.3.6.1.2.1.10.166.9.1.1 no-access
This table specifies per-interface MPLS LC-ATM capability and associated information. In particular, this table sparsely extends the MPLS-LSR-STD-MIB's mplsInterfaceConfTable.
             mplsLcAtmStdInterfaceConfEntry 1.3.6.1.2.1.10.166.9.1.1.1 no-access
An entry in this table is created by an LSR for every interface capable of supporting MPLS LC-ATM. Each entry in this table will exist only if a corresponding entry in ifTable and mplsInterfaceConfTable exists. If the associated entries in ifTable and mplsInterfaceConfTable are deleted, the corresponding entry in this table must also be deleted shortly thereafter.
                 mplsLcAtmStdCtrlVpi 1.3.6.1.2.1.10.166.9.1.1.1.1 atmvpidentifier read-only
This is the VPI value over which this LSR is willing to accept control traffic on this interface.
                 mplsLcAtmStdCtrlVci 1.3.6.1.2.1.10.166.9.1.1.1.2 mplsatmvcidentifier read-only
This is the VCI value over which this LSR is willing to accept control traffic on this interface.
                 mplsLcAtmStdUnlabTrafVpi 1.3.6.1.2.1.10.166.9.1.1.1.3 atmvpidentifier read-only
This is the VPI value over which this LSR is willing to accept unlabeled traffic on this interface.
                 mplsLcAtmStdUnlabTrafVci 1.3.6.1.2.1.10.166.9.1.1.1.4 mplsatmvcidentifier read-only
This is the VCI value over which this LSR is willing to accept unlabeled traffic on this interface.
                 mplsLcAtmStdVcMerge 1.3.6.1.2.1.10.166.9.1.1.1.5 truthvalue read-only
If set to true(1), indicates that this interface is capable of ATM VC merge; otherwise, it MUST be set to false(2).
                 mplsLcAtmVcDirectlyConnected 1.3.6.1.2.1.10.166.9.1.1.1.6 truthvalue read-only
This value indicates whether an LC-ATM is directly or indirectly (by means of a VP) connected. If set to true(1), indicates that this interface is directly connected LC-ATM; otherwise, it MUST be set to false(2). Note that although it can be intimated from RFC 3057 that multiple VPs may be used, in practice only a single one is used, and therefore the authors of this MIB module have chosen to model it as such.
                 mplsLcAtmLcAtmVPI 1.3.6.1.2.1.10.166.9.1.1.1.7 atmvpidentifier read-only
This is the VPI value used for indirectly connected LC-ATM interfaces. For these interfaces, the VPI field is not available to MPLS, and the label MUST be encoded entirely within the VCI field (see [RFC3035]). If the interface is directly connected, this value MUST be set to zero.
                 mplsLcAtmStdIfConfRowStatus 1.3.6.1.2.1.10.166.9.1.1.1.8 rowstatus read-only
This object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry and mplsInterfaceConfEntry MUST exist beforehand. If a manager attempts to create an entry for a corresponding mplsInterfaceConfEntry that does not support LC-ATM, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1), except to mplsLcAtmStdIfConfRowStatus and mplsLcAtmStdIfConfStorageType.
                 mplsLcAtmStdIfConfStorageType 1.3.6.1.2.1.10.166.9.1.1.1.9 storagetype read-only
The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
     mplsLcAtmStdConformance 1.3.6.1.2.1.10.166.9.2
         mplsLcAtmStdCompliances 1.3.6.1.2.1.10.166.9.2.1
             mplsLcAtmStdModuleFullCompliance 1.3.6.1.2.1.10.166.9.2.1.1
Compliance statement for agents that provide full support for MPLS-LC-ATM-STD-MIB. Such devices can be monitored and also be configured using this MIB module.
             mplsLcAtmStdModuleReadOnlyCompliance 1.3.6.1.2.1.10.166.9.2.1.2
Compliance requirement for implementations that only provide read-only support for MPLS-LC-ATM-STD-MIB. Such devices can be monitored but cannot be configured using this MIB module.
         mplsLcAtmStdGroups 1.3.6.1.2.1.10.166.9.2.2
             mplsLcAtmStdIfGroup 1.3.6.1.2.1.10.166.9.2.2.1
Collection of objects needed for MPLS LC-ATM interface configuration.