VITALINK-MIB :: vIfWhyRxBroken

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › VITALINK-MIB › vIfWhyRxBroken

vIfWhyRxBroken

Module: VITALINK-MIB

OID (symbolic): VITALINK-MIB::vIfWhyRxBroken

OID (numeric): 1.3.6.1.4.1.29.1.2.1.1.1.12

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: If the 'Receive state' = 'broken,' this read- only variable displays the reason.

What is vIfWhyRxBroken?

Read-only reason code explaining why vIfReceiveState reports 'broken' for this port, such as dcdloss (Data Carrier Detect lost). An admin reads this to pinpoint why a port's receive function has failed.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.29.1.2.1.1.1.12
snmpwalk -v2c -c public <target> VITALINK-MIB::vIfWhyRxBroken

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.29.1.2.1.1.1.12.1
snmpget -v2c -c public <target> VITALINK-MIB::vIfWhyRxBroken.1

Start monitoring Vitalink network bridge / communication server (bridge-group/interface media-type status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VITALINK-MIB::vIfWhyRxBroken OID value, configure state conditions and alerts, and monitor any Vitalink network bridge / communication server (bridge-group/interface media-type status) 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.29vitalinkVITALINK-MIB
1.3.6.1.4.1.29.1vitamanagementVITALINK-MIB
1.3.6.1.4.1.29.1.2vitainterfacesVITALINK-MIB
1.3.6.1.4.1.29.1.2.1vIfbaseVITALINK-MIB
1.3.6.1.4.1.29.1.2.1.1vifTableVITALINK-MIB
1.3.6.1.4.1.29.1.2.1.1.1vifEntryVITALINK-MIB
1.3.6.1.4.1.29.1.2.1.1.1.12vIfWhyRxBrokenVITALINK-MIB