All MIBs › MPLS-LDP-FRAME-RELAY-MIB › mplsLdpEntityFrameRelayVcDirectionality
mplsLdpEntityFrameRelayVcDirectionality
Module: MPLS-LDP-FRAME-RELAY-MIB
OID (symbolic): MPLS-LDP-FRAME-RELAY-MIB::mplsLdpEntityFrameRelayVcDirectionality
OID (numeric): 1.3.6.1.4.1.99999.42.1.1.1.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-create
Description: 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.
What is mplsLdpEntityFrameRelayVcDirectionality?
Indicates whether a given DLCI can be used as a label independently in both directions, bidirectional, or only in one direction, unidirectional, matching the exact D field from RFC 3036's Frame Relay Session Parameter. When either LDP peer specifies unidirectional capability, both sides use unidirectional label assignment, comparing LDP identifiers to split odd and even DLCIs between the peers. An admin troubleshooting an asymmetric Frame Relay LSP would check this setting to understand whether the negotiated DLCI usage follows the bidirectional or split odd/even unidirectional scheme.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.99999 | iec624392 | IEC-62439-2-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.99999.42 | mplsLdpFrameRelayMIB | MPLS-LDP-FRAME-RELAY-MIB |
| 1.3.6.1.4.1.99999.42.1 | mplsLdpFrameRelayObjects | MPLS-LDP-FRAME-RELAY-MIB |
| 1.3.6.1.4.1.99999.42.1.1 | mplsLdpEntityFrameRelayObjects | MPLS-LDP-FRAME-RELAY-MIB |
| 1.3.6.1.4.1.99999.42.1.1.1 | mplsLdpEntityFrameRelayTable | MPLS-LDP-FRAME-RELAY-MIB |
| 1.3.6.1.4.1.99999.42.1.1.1.1 | mplsLdpEntityFrameRelayEntry | MPLS-LDP-FRAME-RELAY-MIB |
| 1.3.6.1.4.1.99999.42.1.1.1.1.4 | mplsLdpEntityFrameRelayVcDirectionality | MPLS-LDP-FRAME-RELAY-MIB |