PRVT-MPLS-LDP-MIB :: mplsLdpEntityFrameRelayVcDirectionality

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › PRVT-MPLS-LDP-MIB › mplsLdpEntityFrameRelayVcDirectionality

mplsLdpEntityFrameRelayVcDirectionality

Module: PRVT-MPLS-LDP-MIB

OID (symbolic): PRVT-MPLS-LDP-MIB::mplsLdpEntityFrameRelayVcDirectionality

OID (numeric): 1.3.6.1.4.1.738.1.6.5.1.6.1.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

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 in both link directions (bidirectional) or only one (unidirectional) for this entity's Frame Relay label space; in the unidirectional case, odd- and even-numbered DLCIs are split between the two LSRs by comparing their LDP identifiers, exactly as for ATM VCIs. This must be compatible with the peer's own setting for Frame Relay label sessions to work.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.738.1.6.5.1.6.1.1.1.4
snmpwalk -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityFrameRelayVcDirectionality

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.738.1.6.5.1.6.1.1.1.4.1
snmpget -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityFrameRelayVcDirectionality.1

Start monitoring BATM Advanced Communications MPLS router/switch (LDP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PRVT-MPLS-LDP-MIB::mplsLdpEntityFrameRelayVcDirectionality OID value, configure state conditions and alerts, and monitor any BATM Advanced Communications MPLS router/switch (LDP) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.738privateVendorOIDPRIV-VENDORDEF-MIB
1.3.6.1.4.1.738.1prvt_productsPRVT-SWITCH-MIB
1.3.6.1.4.1.738.1.6ipSwitchPRVT-SWITCH-MIB
1.3.6.1.4.1.738.1.6.5mplsPRVT-CR-LDP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.738.1.6.5.1mplsLdpStdMIBPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.6mplsLdpFrameRelayObjectsPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.6.1mplsLdpEntityFrameRelayObjectsPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.6.1.1mplsLdpEntityFrameRelayTablePRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.6.1.1.1mplsLdpEntityFrameRelayEntryPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.6.1.1.1.4mplsLdpEntityFrameRelayVcDirectionalityPRVT-MPLS-LDP-MIB