PRVT-MPLS-LDP-MIB :: mplsLdpEntityAtmVcDirectionality

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

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

mplsLdpEntityAtmVcDirectionality

Module: PRVT-MPLS-LDP-MIB

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

OID (numeric): 1.3.6.1.4.1.738.1.6.5.1.4.1.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: 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.

What is mplsLdpEntityAtmVcDirectionality?

Indicates whether this entity treats a given VCI within a VPI as usable as a label in both link directions (bidirectional) or only one direction (unidirectional); in the unidirectional case, RFC 3036 has the two LSRs split odd/even VCI assignment based on comparing their LDP identifiers. This setting must be compatible with the peer's own VC directionality capability for ATM label sessions to work correctly.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.738.1.6.5.1.4.1.1.1.4
snmpwalk -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityAtmVcDirectionality

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.738.1.6.5.1.4.1.1.1.4.1
snmpget -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityAtmVcDirectionality.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::mplsLdpEntityAtmVcDirectionality 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.4mplsLdpAtmObjectsPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.4.1mplsLdpEntityAtmObjectsPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.4.1.1mplsLdpEntityAtmTablePRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.4.1.1.1mplsLdpEntityAtmEntryPRVT-MPLS-LDP-MIB
1.3.6.1.4.1.738.1.6.5.1.4.1.1.1.4mplsLdpEntityAtmVcDirectionalityPRVT-MPLS-LDP-MIB