| OID symbolic | OID numeric | Type | Access | Description |
|---|
| mplsLdpFrameRelayStdMIB | 1.3.6.1.2.1.10.166.6 | | | Copyright (C) The Internet Society (year). 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 Frame Relay as the Layer 2 media. |
| mplsLdpFrameRelayObjects | 1.3.6.1.2.1.10.166.6.1 | | | |
| mplsLdpEntityFrameRelayObjects | 1.3.6.1.2.1.10.166.6.1.1 | | | |
| mplsLdpEntityFrameRelayTable | 1.3.6.1.2.1.10.166.6.1.1.1 | | not-accessible | This table contains Frame Relay specific
information which could be used in the
'Optional Parameters' and other Frame Relay
specific information.
This table 'sparse augments' the mplsLdpEntityTable
when Frame Relay is the Layer 2 medium. |
| mplsLdpEntityFrameRelayEntry | 1.3.6.1.2.1.10.166.6.1.1.1.1 | | not-accessible | An entry in this table represents the Frame Relay
optional parameters associated with the LDP entity. |
| NUM mplsLdpEntityFrameRelayIfIndexOrZero | 1.3.6.1.2.1.10.166.6.1.1.1.1.1 | InterfaceIndexOrZero | read-create | This value represents either the InterfaceIndex of
the 'ifLayer' where the Frame Relay 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
Frame Relay 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 Frame Relay Label is
being used in forwarding data, then the value of this
object MUST be the InterfaceIndex. |
| INT mplsLdpEntityFrameRelayMergeCap | 1.3.6.1.2.1.10.166.6.1.1.1.1.2 | INTEGER | read-create | This represents whether or not the Frame Relay merge
capability is supported. This is the EXACT value for the
Frame Relay Session Parameter, field M (for Frame Relay
Merge Capabilities). The Frame Relay Session Parameter
is an optional parameter in the Initialization Message.
The description from rfc3036.txt is:
'M, Frame Relay Merge Capabilities
Specifies the merge capabilities of a Frame
Relay switch. The following values are
supported in this version of the
specification:
Value Meaning
0 Merge not supported
1 Merge supported
Non-merge and merge Frame Relay LSRs may
freely interoperate.'
Please refer to the following reference for a
complete description of this feature. |
| U32 mplsLdpEntityFrameRelayLRComponents | 1.3.6.1.2.1.10.166.6.1.1.1.1.3 | Unsigned32 | read-only | Number of Label Range Components in the Initialization
message. This also represents the number of entries
in the mplsLdpEntityFrameRelayLRTable which correspond
to this entry.
This is the EXACT value for the Frame Relay Session
Parameter, field N (for Number of label range
components). The Frame Relay 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 Frame Relay Label
Range Components included in the TLV.'
Please refer to the following reference for a
complete description of this feature. |
| INT mplsLdpEntityFrameRelayVcDirectionality | 1.3.6.1.2.1.10.166.6.1.1.1.1.4 | INTEGER | read-create | If the value of this object is 'bidirectional(0)', then
the LSR supports the use of a given DLCI as a label for
both directions independently. If the value of
this object is 'unidirectional(1)', then the LSR
uses the given DLCI as a label in only one direction.
This is the EXACT value for the Frame Relay Session
Parameter, field D (for VC Directionality). The
Frame Relay 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 support the use of a given
DLCI as a label for both link directions
independently. A value of 1 specifies
unidirectional VC capability, meaning a given
DLCI 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 DLCIs
in the range as labels. The system with the
smaller LDP Identifier may assign only
even-numbered DLCIs in the range as labels.'
Please refer to the following reference for a
complete description of this feature. |
| STO mplsLdpEntityFrameRelayStorageType | 1.3.6.1.2.1.10.166.6.1.1.1.1.5 | StorageType | read-create | 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. |
| ROW mplsLdpEntityFrameRelayRowStatus | 1.3.6.1.2.1.10.166.6.1.1.1.1.6 | RowStatus | read-create | 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. |
| mplsLdpEntityFrameRelayLRTable | 1.3.6.1.2.1.10.166.6.1.1.2 | | not-accessible | This table contains information about the
Optional Parameters for the Frame Relay Session
in the LDP Initialization Message, specifically
it contains information about the Frame Relay
Label Range Components.
If the value of the object
'mplsLdpEntityOptionalParameters' contains the
value of 'frameRelaySessionParameters(3)' then
there must be at least one corresponding entry
in this table. |
| mplsLdpEntityFrameRelayLREntry | 1.3.6.1.2.1.10.166.6.1.1.2.1 | | not-accessible | An entry in this table represents the Frame Relay
Label Range Component associated with the LDP entity. |
| DLC mplsLdpEntityFrameRelayLRMinDlci | 1.3.6.1.2.1.10.166.6.1.1.2.1.1 | DLCI | not-accessible | The lower bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Minimum DLCI field. The value
of zero is valid for the minimum DLCI field of
the label. |
| DLC mplsLdpEntityFrameRelayLRMaxDlci | 1.3.6.1.2.1.10.166.6.1.1.2.1.2 | DLCI | read-create | The upper bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Maximum DLCI field. |
| INT mplsLdpEntityFrameRelayLRLen | 1.3.6.1.2.1.10.166.6.1.1.2.1.3 | INTEGER | read-create | This object specifies the length of the DLCI bits.
This is the EXACT value for the Len field of the
Frame Relay Label Range Component.
The description from rfc3036.txt is:
'Len
This field specifies the number of bits of the DLCI.
The following values are supported:
Len DLCI bits
0 10
2 23
Len values 1 and 3 are reserved.'
Please refer to the following reference for a complete
description of this feature. |
| STO mplsLdpEntityFrameRelayLRStorageType | 1.3.6.1.2.1.10.166.6.1.1.2.1.4 | StorageType | read-create | 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. |
| ROW mplsLdpEntityFrameRelayLRRowStatus | 1.3.6.1.2.1.10.166.6.1.1.2.1.5 | RowStatus | read-create | 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. |
| mplsLdpFrameRelaySessionObjects | 1.3.6.1.2.1.10.166.6.1.2 | | | |
| mplsLdpFrameRelaySessionTable | 1.3.6.1.2.1.10.166.6.1.2.1 | | not-accessible | A table of Frame Relay label range intersections
between the LDP Entities and LDP Peers.
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. |
| mplsLdpFrameRelaySessionEntry | 1.3.6.1.2.1.10.166.6.1.2.1.1 | | not-accessible | 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. |
| DLC mplsLdpFrameRelaySessionMinDlci | 1.3.6.1.2.1.10.166.6.1.2.1.1.1 | DLCI | not-accessible | The lower bound of DLCIs which are supported.
The value of zero is a valid value for the
minimum DLCI field of the label. |
| DLC mplsLdpFrameRelaySessionMaxDlci | 1.3.6.1.2.1.10.166.6.1.2.1.1.2 | DLCI | read-only | The upper bound of DLCIs which are supported. |
| INT mplsLdpFrameRelaySessionLen | 1.3.6.1.2.1.10.166.6.1.2.1.1.3 | INTEGER | read-only | This object specifies the DLCI bits. |
| mplsLdpFrameRelayConformance | 1.3.6.1.2.1.10.166.6.2 | | | |
| mplsLdpFrameRelayGroups | 1.3.6.1.2.1.10.166.6.2.1 | | | |
| mplsLdpFrameRelayGroup | 1.3.6.1.2.1.10.166.6.2.1.1 | | | Objects that apply to all MPLS LDP implementations
using Frame Relay as the Layer 2. |
| mplsLdpFrameRelayCompliances | 1.3.6.1.2.1.10.166.6.2.2 | | | |
| mplsLdpFrameRelayModuleFullCompliance | 1.3.6.1.2.1.10.166.6.2.2.1 | | | 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. |
| mplsLdpFrameRelayModuleReadOnlyCompliance | 1.3.6.1.2.1.10.166.6.2.2.2 | | | The Module is implemented with support for
read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE. |
