| mplsLdpEntityAtmIfIndexOrZero |
.1.3.6.1.2.1.10.166.5.1.1.1.1.1 |
|
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.
|
| mplsLdpEntityAtmMergeCap |
.1.3.6.1.2.1.10.166.5.1.1.1.1.2 |
|
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.
|
| mplsLdpEntityAtmLRComponents |
.1.3.6.1.2.1.10.166.5.1.1.1.1.3 |
|
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.
|
| mplsLdpEntityAtmVcDirectionality |
.1.3.6.1.2.1.10.166.5.1.1.1.1.4 |
|
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.
|
| mplsLdpEntityAtmLsrConnectivity |
.1.3.6.1.2.1.10.166.5.1.1.1.1.5 |
|
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.
|
| mplsLdpEntityAtmDefaultControlVpi |
.1.3.6.1.2.1.10.166.5.1.1.1.1.6 |
|
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.
|
| mplsLdpEntityAtmDefaultControlVci |
.1.3.6.1.2.1.10.166.5.1.1.1.1.7 |
|
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.
|
| mplsLdpEntityAtmUnlabTrafVpi |
.1.3.6.1.2.1.10.166.5.1.1.1.1.8 |
|
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.
|
| mplsLdpEntityAtmUnlabTrafVci |
.1.3.6.1.2.1.10.166.5.1.1.1.1.9 |
|
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.
|
| mplsLdpEntityAtmStorageType |
.1.3.6.1.2.1.10.166.5.1.1.1.1.10 |
|
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.
|
| mplsLdpEntityAtmRowStatus |
.1.3.6.1.2.1.10.166.5.1.1.1.1.11 |
|
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.
|
| mplsLdpEntityAtmLRMinVpi |
.1.3.6.1.2.1.10.166.5.1.1.2.1.1 |
|
The minimum VPI number configured for this range.
The value of zero is a valid value for the VPI portion
of the label.
|
| mplsLdpEntityAtmLRMinVci |
.1.3.6.1.2.1.10.166.5.1.1.2.1.2 |
|
The minimum VCI number configured for this range.
|
| mplsLdpEntityAtmLRMaxVpi |
.1.3.6.1.2.1.10.166.5.1.1.2.1.3 |
|
The maximum VPI number configured for this range.
|
| mplsLdpEntityAtmLRMaxVci |
.1.3.6.1.2.1.10.166.5.1.1.2.1.4 |
|
The maximum VCI number configured for this range.
|
| mplsLdpEntityAtmLRStorageType |
.1.3.6.1.2.1.10.166.5.1.1.2.1.5 |
|
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.
|
| mplsLdpEntityAtmLRRowStatus |
.1.3.6.1.2.1.10.166.5.1.1.2.1.6 |
|
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.
|
| mplsLdpSessionAtmLRLowerBoundVpi |
.1.3.6.1.2.1.10.166.5.1.2.1.1.1 |
|
The minimum VPI number for this range.
|
| mplsLdpSessionAtmLRLowerBoundVci |
.1.3.6.1.2.1.10.166.5.1.2.1.1.2 |
|
The minimum VCI number for this range.
|
| mplsLdpSessionAtmLRUpperBoundVpi |
.1.3.6.1.2.1.10.166.5.1.2.1.1.3 |
|
The maximum VPI number for this range.
|
| mplsLdpSessionAtmLRUpperBoundVci |
.1.3.6.1.2.1.10.166.5.1.2.1.1.4 |
|
The maximum VCI number for this range.
|
