MPLS-LC-ATM-STD-MIB
AI MIB Summary
The MPLS-LC-ATM-STD-MIB provides managed object definitions for monitoring and configuring MPLS Label-Controlled ATM interfaces, specifically tracking label binding states, virtual circuit (VCC) parameters, and interface operational status as defined in RFC 3035. This module enables network administrators to manage the integration of ATM transport layers with MPLS label-switched paths, including the supervision of PVC/SVC signaling and associated performance counters.
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.
Main OID:
mplsLcAtmStdMIB.1.3.6.1.2.1.10.166.9
20
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
mplsLcAtmStdMIBThis 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. MODULE-IDENTITY .1.3.6.1.2.1.10.166.9 |
mplsLcAtmStdNotifications OBJECT IDENTIFIER .1.3.6.1.2.1.10.166.9.0 |
mplsLcAtmStdObjects OBJECT IDENTIFIER .1.3.6.1.2.1.10.166.9.1 |
mplsLcAtmStdInterfaceConfTableThis table specifies per-interface MPLS LC-ATM capability and associated information. In particular, this table sparsely extends the MPLS-LSR-STD-MIB's mplsInterfaceConfTable. SEQUENCE OF MplsLcAtmStdInterfaceConfEntry .1.3.6.1.2.1.10.166.9.1.1 |
mplsLcAtmStdInterfaceConfEntryAn 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. MplsLcAtmStdInterfaceConfEntry .1.3.6.1.2.1.10.166.9.1.1.1 |
mplsLcAtmStdCtrlVpiThis is the VPI value over which this LSR is willing to accept control traffic on this interface.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.2.1.10.166.9.1.1.1.1 |
mplsLcAtmStdCtrlVciThis is the VCI value over which this LSR is willing to accept control traffic on this interface.rw MplsAtmVcIdentifier (MPLS-TC-STD-MIB) .1.3.6.1.2.1.10.166.9.1.1.1.2 |
mplsLcAtmStdUnlabTrafVpiThis is the VPI value over which this LSR is willing to accept unlabeled traffic on this interface.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.2.1.10.166.9.1.1.1.3 |
mplsLcAtmStdUnlabTrafVciThis is the VCI value over which this LSR is willing to accept unlabeled traffic on this interface.rw MplsAtmVcIdentifier (MPLS-TC-STD-MIB) .1.3.6.1.2.1.10.166.9.1.1.1.4 |
mplsLcAtmStdVcMergeIf set to true(1), indicates that this interface is capable of ATM VC merge; otherwise, it MUST be set to false(2).rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.10.166.9.1.1.1.5 |
mplsLcAtmVcDirectlyConnectedThis 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.10.166.9.1.1.1.6 |
mplsLcAtmLcAtmVPIThis 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.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.2.1.10.166.9.1.1.1.7 |
mplsLcAtmStdIfConfRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.10.166.9.1.1.1.8 |
mplsLcAtmStdIfConfStorageTypeThe 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.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.10.166.9.1.1.1.9 |
mplsLcAtmStdConformance OBJECT IDENTIFIER .1.3.6.1.2.1.10.166.9.2 |
mplsLcAtmStdCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.10.166.9.2.1 |
mplsLcAtmStdModuleFullComplianceCompliance 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. Unknown .1.3.6.1.2.1.10.166.9.2.1.1 |
mplsLcAtmStdModuleReadOnlyComplianceCompliance 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. Unknown .1.3.6.1.2.1.10.166.9.2.1.2 |
mplsLcAtmStdGroups OBJECT IDENTIFIER .1.3.6.1.2.1.10.166.9.2.2 |
mplsLcAtmStdIfGroupCollection of objects needed for MPLS LC-ATM interface configuration. Unknown .1.3.6.1.2.1.10.166.9.2.2.1 |