MPLS-LDP-ATM-MIB
AI MIB Summary
The MPLS-LDP-ATM-MIB enables the configuration and monitoring of Multiprotocol Label Switching Label Distribution Protocol sessions specifically over Asynchronous Transfer Mode (ATM) interfaces, tracking LDP peer adjacencies, label bindings, and ATM-specific transport parameters. This module provides granular visibility into the state of LDP-controlled pseudowires and the underlying ATM Layer 2 media used to carry MPLS traffic.
Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFCXXX; see the RFC itself for full legal notices.
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.
Main OID:
mplsLdpAtmMIB.1.3.6.1.4.1.1991.1.2.15.15.1
35
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
35 total| Object Name |
|---|
mplsLdpAtmMIBCopyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices.
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. MODULE-IDENTITY .1.3.6.1.4.1.1991.1.2.15.15.1 |
IMPORTSCopyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices.
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. Unknown .1.3.6.1.4.1.1991.1.2.15.15.1 |
mplsLdpAtmObjects OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.1 |
mplsLdpEntityAtmObjects OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.1.1 |
mplsLdpEntityAtmTableThis table contains information about the
ATM specific information which could be used
in the 'Optional Parameters' and other ATM specific
information.
This table 'extends' the mplsLdpEntityTable when
ATM as the Layer 2 media. SEQUENCE OF MplsLdpEntityAtmEntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1 |
mplsLdpEntityAtmEntryAn entry in this table represents the ATM parameters
and ATM information for this LDP entity. MplsLdpEntityAtmEntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1 |
mplsLdpEntityAtmIfIndexOrZeroThis value represents either the InterfaceIndex of
the 'ifLayer' where the ATM Labels 'owned' by this
entry were created, or 0 (zero). The value of zero
means that the InterfaceIndex is not known. For example,
if the InterfaceIndex is created subsequent to the
ATM Label's creation, then it would not be 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.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.1 |
mplsLdpEntityAtmMergeCapDenotes 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.rw Enumeration .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.2 |
mplsLdpEntityAtmLRComponentsNumber 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.rw Unsigned32 .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.3 |
mplsLdpEntityAtmVcDirectionalityIf 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.rw Enumeration .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.4 |
mplsLdpEntityAtmLsrConnectivityThe 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.rw Enumeration .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.5 |
mplsLdpEntityAtmDefaultControlVpiThe 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.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.6 |
mplsLdpEntityAtmDefaultControlVciThe 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.rw MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.7 |
mplsLdpEntityAtmUnlabTrafVpiVPI 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.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.8 |
mplsLdpEntityAtmUnlabTrafVciVCI 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.rw MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.9 |
mplsLdpEntityAtmStorageTypeThe storage type for this conceptual row. Conceptual rows
having the value 'permanent(4)' MAY allow write-access to any
columnar objects in the row, except for setting the
mplsLdpEntityAtmRowStatus to 'destroy(6)'.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.10 |
mplsLdpEntityAtmRowStatusThe 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 explicitely 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.
NOTE: This RowStatus object should
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.1.1.11 |
mplsLdpEntityAtmLRTableThe 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. SEQUENCE OF MplsLdpEntityAtmLREntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2 |
mplsLdpEntityAtmLREntryA 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 be created unless a unique and
non-overlapping range is specified. Thus, row
creation implies a one-shot row creation of
LDP EntityID and LowerBound vpi/vci and
UpperBound vpi/vci. At least one label
range entry for a specific LDP Entity MUST
include the default VPI/VCI values denoted
in the LDP Entity Table. MplsLdpEntityAtmLREntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1 |
mplsLdpEntityAtmLRMinVpiThe minimum VPI number configured for this range.
The value of zero is a valid value for the VPI portion
of the label. AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1.1 |
mplsLdpEntityAtmLRMinVciThe minimum VCI number configured for this range. MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1.2 |
mplsLdpEntityAtmLRMaxVpiThe maximum VPI number configured for this range.rw AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1.3 |
mplsLdpEntityAtmLRMaxVciThe maximum VCI number configured for this range.rw MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1.4 |
mplsLdpEntityAtmLRStorageTypeThe 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.4.1.1991.1.2.15.15.1.1.1.2.1.5 |
mplsLdpEntityAtmLRRowStatusThe 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 explicitely 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.
There must exist at least one entry in this
table for every LDP Entity that has
'mplsLdpEntityOptionalParameters' object with
a value of 'atmSessionParameters'.
NOTE: This RowStatus object should
have the same value of the 'mplsLdpEntityRowStatus'
related to this entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.1991.1.2.15.15.1.1.1.2.1.6 |
mplsLdpAtmSesObjects OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.1.2 |
mplsLdpAtmSesTableA 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.
NOTE: this table cannot use the 'AUGMENTS'
clause because there is not necessarily a one-to-one
mapping between this table and the mplsLdpSessionTable. SEQUENCE OF MplsLdpAtmSesEntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1 |
mplsLdpAtmSesEntryAn 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. MplsLdpAtmSesEntry .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1.1 |
mplsLdpSesAtmLRLowerBoundVpiThe minimum VPI number for this range. AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1.1.1 |
mplsLdpSesAtmLRLowerBoundVciThe minimum VCI number for this range. MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1.1.2 |
mplsLdpSesAtmLRUpperBoundVpiThe maximum VPI number for this range.ro AtmVpIdentifier (ATM-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1.1.3 |
mplsLdpSesAtmLRUpperBoundVciThe maximum VCI number for this range.ro MplsAtmVcIdentifier (MPLS-TC-MIB) .1.3.6.1.4.1.1991.1.2.15.15.1.1.2.1.1.4 |
mplsLdpAtmConformance OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.2 |
mplsLdpAtmGroups OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.2.1 |
mplsLdpAtmCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.1991.1.2.15.15.1.2.2 |