MPLS-LDP-ATM-STD-MIB :: mplsLdpEntityAtmLsrConnectivity

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MPLS-LDP-ATM-STD-MIB › mplsLdpEntityAtmLsrConnectivity

mplsLdpEntityAtmLsrConnectivity

Module: MPLS-LDP-ATM-STD-MIB

OID (symbolic): MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLsrConnectivity

OID (numeric): 1.3.6.1.2.1.10.166.5.1.1.1.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-create

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

What is mplsLdpEntityAtmLsrConnectivity?

This object states whether the peer LSR is connected directly, direct(1), or indirectly through an intervening ATM VP, indirect(2), and defaults to direct. Admins need this because indirect connectivity means the VPI values seen at each endpoint can differ, forcing the LDP label to be encoded entirely within the VCI field instead of the VPI/VCI pair. For example, an admin troubleshooting a label mismatch across an ATM cross-connect would check whether this entity is set to indirect(2) to confirm VCI-only encoding is expected.

OID Breakdown

Upper-level ancestors (8 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
1.3.6.1.2.1.10.166mplsStdMIBMPLS-TC-PRIV-STDEXT-MIB
Numeric OIDNameModule
1.3.6.1.2.1.10.166.5mplsLdpAtmStdMIBMPLS-LDP-ATM-STD-MIB
1.3.6.1.2.1.10.166.5.1mplsLdpAtmObjectsMPLS-LDP-ATM-STD-MIB
1.3.6.1.2.1.10.166.5.1.1mplsLdpEntityAtmObjectsMPLS-LDP-ATM-STD-MIB
1.3.6.1.2.1.10.166.5.1.1.1mplsLdpEntityAtmTableMPLS-LDP-ATM-STD-MIB
1.3.6.1.2.1.10.166.5.1.1.1.1mplsLdpEntityAtmEntryMPLS-LDP-ATM-STD-MIB
1.3.6.1.2.1.10.166.5.1.1.1.1.5mplsLdpEntityAtmLsrConnectivityMPLS-LDP-ATM-STD-MIB