ACMIB :: vbrAtmPvcVccConnFailureCauseB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsACMIBvbrAtmPvcVccConnFailureCauseB

vbrAtmPvcVccConnFailureCauseB

Module: ACMIB

OID (symbolic): ACMIB::vbrAtmPvcVccConnFailureCauseB

OID (numeric): 1.3.6.1.4.1.1751.2.18.6.9.1.24

Node type: OBJECT-TYPE

Type: AtmConnFailureCause

Access: read-only

Description: connection status reason code

What is vbrAtmPvcVccConnFailureCauseB?

This read-only field contains the reason code for why the side-B endpoint failed to establish or maintain the connection. Like the side-A equivalent, it helps troubleshoot connection problems systematically. A code of 'invalid-vpi-vci' indicates that the virtual path and channel identifiers configured for side B don't exist or conflict.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.9.1.24
snmpwalk -v2c -c public <target> ACMIB::vbrAtmPvcVccConnFailureCauseB

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.9.1.24.1
snmpget -v2c -c public <target> ACMIB::vbrAtmPvcVccConnFailureCauseB.1

Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::vbrAtmPvcVccConnFailureCauseB OID value, configure state conditions and alerts, and monitor any Lucent/Nortel Access Concentrator (legacy) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.1751lucentACMIB
1.3.6.1.4.1.1751.2mibsACMIB
1.3.6.1.4.1.1751.2.18acMIBACMIB
1.3.6.1.4.1.1751.2.18.6connectionConfigACMIB
1.3.6.1.4.1.1751.2.18.6.9vbrAtmPvcVccTableACMIB
1.3.6.1.4.1.1751.2.18.6.9.1vbrAtmPvcVccEntryACMIB
1.3.6.1.4.1.1751.2.18.6.9.1.24vbrAtmPvcVccConnFailureCauseBACMIB