ACMIB :: vbrVbrPvcConnFailureCauseB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsACMIBvbrVbrPvcConnFailureCauseB

vbrVbrPvcConnFailureCauseB

Module: ACMIB

OID (symbolic): ACMIB::vbrVbrPvcConnFailureCauseB

OID (numeric): 1.3.6.1.4.1.1751.2.18.6.11.1.14

Node type: OBJECT-TYPE

Type: ConnFailureCause

Access: read-only

Description: connection status reason code

What is vbrVbrPvcConnFailureCauseB?

This read-only OID displays the reason code explaining why side B of a VBR PVC connection failed to establish or has dropped. Engineers use this to identify whether the B-side termination point has a physical, logical, or configuration problem causing the connection to fail. For example, code 3 could indicate the local management interface on the B-side is down.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.11.1.14
snmpwalk -v2c -c public <target> ACMIB::vbrVbrPvcConnFailureCauseB

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.6.11.1.14.1
snmpget -v2c -c public <target> ACMIB::vbrVbrPvcConnFailureCauseB.1

Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::vbrVbrPvcConnFailureCauseB 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.11vbrVbrPvcTableACMIB
1.3.6.1.4.1.1751.2.18.6.11.1vbrVbrPvcEntryACMIB
1.3.6.1.4.1.1751.2.18.6.11.1.14vbrVbrPvcConnFailureCauseBACMIB