PRVT-MPLS-LDP-MIB :: mplsLdpEntityAtmMergeCap

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

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

mplsLdpEntityAtmMergeCap

Module: PRVT-MPLS-LDP-MIB

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

OID (numeric): 1.3.6.1.4.1.738.1.6.5.1.4.1.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message.

The description from rfc3036.txt is:

'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification:

Value Meaning

0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported

If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate.

- The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.'

Please refer to the following reference for a complete description of this feature.

What is mplsLdpEntityAtmMergeCap?

Reports this entity's ATM cell-merging capability as advertised in the optional ATM Session Parameter of the LDP Initialization message: none, VP merge, VC merge, or both. Merge capability affects how gracefully this LSR interoperates with peers of differing merge support, since RFC 3036 notes VP-merge interoperability between mismatched peers is only loosely defined.

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.2
snmpwalk -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityAtmMergeCap

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.2.1
snmpget -v2c -c public <target> PRVT-MPLS-LDP-MIB::mplsLdpEntityAtmMergeCap.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> mplsLdpEntityAtmMergeCap.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::mplsLdpEntityAtmMergeCap 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.2mplsLdpEntityAtmMergeCapPRVT-MPLS-LDP-MIB