MPLS-LDP-ATM-STD-MIB
- Registered at
- 1.3.6.1.2.1.10.166.5
- Last updated
- 2004-06-03 00:00
- Organization
- Multiprotocol Label Switching (mpls) Working Group
- Revisions
- 2004-06-03 00:00
- Namespace
- standard
- Source file
MPLS-LDP-ATM-STD-MIB- Digest
sha256:60df458cb5498f33703b4b9f804ef58ca82e942174cd7af49d8062a3a7096ea2
Description
Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 media.
Contact
Joan Cucchiara (jcucchiara@mindspring.com) Marconi Communications, Inc. Hans Sjostrand (hans@ipunplugged.com) ipUnplugged James V. Luciani (james_luciani@mindspring.com) Marconi Communications, Inc. Working Group Chairs: George Swallow, email: swallow@cisco.com Loa Andersson, email: loa@pi.se MPLS Working Group, email: mpls@uu.net
Imports
| From | Symbols |
|---|---|
| ATM-TC-MIB | AtmVpIdentifier |
| IF-MIB | InterfaceIndexOrZero |
| MPLS-LDP-STD-MIB | mplsLdpEntityIndex, mplsLdpEntityLdpId, mplsLdpPeerLdpId |
| MPLS-TC-STD-MIB | MplsAtmVcIdentifier, mplsStdMIB |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso |
| SNMPv2-TC | DisplayString, RowStatus, StorageType, TEXTUAL-CONVENTION |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
ATM-TC-MIB DIFFSERV-DSCP-TC DIFFSERV-MIB IANA-ADDRESS-FAMILY-NUMBERS-MIB IANAifType-MIB IF-MIB INET-ADDRESS-MIB INTEGRATED-SERVICES-MIB MPLS-LDP-ATM-STD-MIB MPLS-LDP-STD-MIB MPLS-LSR-STD-MIB MPLS-TC-STD-MIB SNMPv2-CONF SNMPv2-MIB SNMPv2-SMI SNMPv2-TC
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| mplsLdpAtmObjects OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.1 | |||
| mplsLdpEntityAtmObjects OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.1.1 | |||
| mplsLdpEntityAtmTable OBJECT-TYPE This table contains ATM specific information which could be used in the 'Optional Parameters' and other ATM specific information. This table 'sparse augments' the mplsLdpEntityTable when ATM is the Layer 2 medium. | 1.3.6.1.2.1.10.166.5.1.1.1 | not-accessible | current | |
| mplsLdpEntityAtmEntry OBJECT-TYPE An entry in this table represents the ATM parameters and ATM information for this LDP entity. | 1.3.6.1.2.1.10.166.5.1.1.1.1 | not-accessible | current | |
| mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE This value represents either the InterfaceIndex or 0 (zero). The value of zero means that the InterfaceIndex is not known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex. If an ATM Label is being used in forwarding data, then the value of this object MUST be the InterfaceIndex. | 1.3.6.1.2.1.10.166.5.1.1.1.1.1 | InterfaceIndexOrZero | read-create | current |
| mplsLdpEntityAtmMergeCap OBJECT-TYPE Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate. - The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.' Please refer to the following reference for a complete description of this feature. | 1.3.6.1.2.1.10.166.5.1.1.1.1.2 | INTEGER {notSupported(0), vpMerge(1), vcMerge(2), vpAndVcMerge(3)} | read-create | current |
| mplsLdpEntityAtmLRComponents OBJECT-TYPE Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityAtmLRTable which correspond to this entry. This is the EXACT value for the ATM Session Parameter, field N (for Number of label range components). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'N, Number of label range components Specifies the number of ATM Label Range Components included in the TLV.' Please refer to the following reference for a complete description of this feature. | 1.3.6.1.2.1.10.166.5.1.1.1.1.3 | Unsigned32 (1..65535) | read-only | current |
| mplsLdpEntityAtmVcDirectionality OBJECT-TYPE If the value of this object is 'bidirectional(0)', a given VCI, within a given VPI, is used as a label for both directions independently. If the value of this object is 'unidirectional(1)', a given VCI within a VPI designates one direction. This is the EXACT value for the ATM Session Parameter, field D (for VC Directionality). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can (within a given VPI) support the use of a given VCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning (within a given VPI) a given VCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered VCIs in the VPI/VCI range as labels. The system with the smaller LDP Identifier may assign only even-numbered VCIs in the VPI/VCI range as labels.' Please refer to the following reference for a complete description of this feature. | 1.3.6.1.2.1.10.166.5.1.1.1.1.4 | INTEGER {bidirectional(0), unidirectional(1)} | read-create | current |
| mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE The peer LSR may be connected indirectly by means of an ATM VP so that the VPI values may be different on either endpoint so the label MUST be encoded entirely within the VCI field. | 1.3.6.1.2.1.10.166.5.1.1.1.1.5 | INTEGER {direct(1), indirect(2)} | read-create | current |
| mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE The default VPI value for the non-MPLS connection. The default value of this is 0 (zero) but other values may be configured. This object allows a different value to be configured. | 1.3.6.1.2.1.10.166.5.1.1.1.1.6 | AtmVpIdentifier | read-create | current |
| mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE The Default VCI value for a non-MPLS connection. The default value of this is 32 but other values may be configured. This object allows a different value to be configured. | 1.3.6.1.2.1.10.166.5.1.1.1.1.7 | MplsAtmVcIdentifier | read-create | current |
| mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE VPI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVpi', however another value may be configured. | 1.3.6.1.2.1.10.166.5.1.1.1.1.8 | AtmVpIdentifier | read-create | current |
| mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE VCI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVci', however another value may be configured. | 1.3.6.1.2.1.10.166.5.1.1.1.1.9 | MplsAtmVcIdentifier | read-create | current |
| mplsLdpEntityAtmStorageType OBJECT-TYPE 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. | 1.3.6.1.2.1.10.166.5.1.1.1.1.10 | StorageType | read-create | current |
| mplsLdpEntityAtmRowStatus OBJECT-TYPE The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated. | 1.3.6.1.2.1.10.166.5.1.1.1.1.11 | RowStatus | read-create | current |
| mplsLdpEntityAtmLRTable OBJECT-TYPE The MPLS LDP Entity ATM Label Range (LR) Table. The purpose of this table is to provide a mechanism for configuring a contiguous range of vpi's with a contiguous range of vci's, or a 'label range' for LDP Entities. LDP Entities which use ATM must have at least one entry in this table. There must exist at least one entry in this table for every LDP Entity that has 'mplsLdpEntityOptionalParameters' object with a value of 'atmSessionParameters'. | 1.3.6.1.2.1.10.166.5.1.1.2 | not-accessible | current | |
| mplsLdpEntityAtmLREntry OBJECT-TYPE A row in the LDP Entity ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having LowerBound vpi/vci == 0/32, and UpperBound vpi/vci == 0/100, and a second entry for this same interface with LowerBound vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. However, there could not be a third entry with LowerBound vpi/vci == 0/200 and UpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e., both entries now have 0/200). A row will not become active unless a unique and non-overlapping range is specified. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table. A request to create a row with an overlapping range should result in an inconsistentValue error. | 1.3.6.1.2.1.10.166.5.1.1.2.1 | not-accessible | current | |
| mplsLdpEntityAtmLRMinVpi OBJECT-TYPE The minimum VPI number configured for this range. The value of zero is a valid value for the VPI portion of the label. | 1.3.6.1.2.1.10.166.5.1.1.2.1.1 | AtmVpIdentifier | not-accessible | current |
| mplsLdpEntityAtmLRMinVci OBJECT-TYPE The minimum VCI number configured for this range. | 1.3.6.1.2.1.10.166.5.1.1.2.1.2 | MplsAtmVcIdentifier | not-accessible | current |
| mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE The maximum VPI number configured for this range. | 1.3.6.1.2.1.10.166.5.1.1.2.1.3 | AtmVpIdentifier | read-create | current |
| mplsLdpEntityAtmLRMaxVci OBJECT-TYPE The maximum VCI number configured for this range. | 1.3.6.1.2.1.10.166.5.1.1.2.1.4 | MplsAtmVcIdentifier | read-create | current |
| mplsLdpEntityAtmLRStorageType OBJECT-TYPE 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. | 1.3.6.1.2.1.10.166.5.1.1.2.1.5 | StorageType | read-create | current |
| mplsLdpEntityAtmLRRowStatus OBJECT-TYPE The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated. | 1.3.6.1.2.1.10.166.5.1.1.2.1.6 | RowStatus | read-create | current |
| mplsLdpAtmSessionObjects OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.1.2 | |||
| mplsLdpAtmSessionTable OBJECT-TYPE A table which relates sessions in the 'mplsLdpSessionTable' and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection. This table cannot use the 'AUGMENTS' clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable. | 1.3.6.1.2.1.10.166.5.1.2.1 | not-accessible | current | |
| mplsLdpAtmSessionEntry OBJECT-TYPE An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer. The information contained in a row is read-only. | 1.3.6.1.2.1.10.166.5.1.2.1.1 | not-accessible | current | |
| mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE The minimum VPI number for this range. | 1.3.6.1.2.1.10.166.5.1.2.1.1.1 | AtmVpIdentifier | not-accessible | current |
| mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE The minimum VCI number for this range. | 1.3.6.1.2.1.10.166.5.1.2.1.1.2 | MplsAtmVcIdentifier | not-accessible | current |
| mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE The maximum VPI number for this range. | 1.3.6.1.2.1.10.166.5.1.2.1.1.3 | AtmVpIdentifier | read-only | current |
| mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE The maximum VCI number for this range. | 1.3.6.1.2.1.10.166.5.1.2.1.1.4 | MplsAtmVcIdentifier | read-only | current |
| mplsLdpAtmConformance OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.2 | |||
| mplsLdpAtmGroups OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.2.1 | |||
| mplsLdpAtmCompliances OBJECT-IDENTITY | 1.3.6.1.2.1.10.166.5.2.2 |
Conformance
| Name | OID | Status |
|---|---|---|
| mplsLdpAtmGroup OBJECT-GROUP Objects that apply to all MPLS LDP implementations using ATM as the Layer 2. | 1.3.6.1.2.1.10.166.5.2.1.1 | current |
| mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE. | 1.3.6.1.2.1.10.166.5.2.2.1 | current |
| mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE. | 1.3.6.1.2.1.10.166.5.2.2.2 | current |