USR-VHA-MIB :: usrVHAFailedSessionsCriticalAlarmThresh

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-VHA-MIB › usrVHAFailedSessionsCriticalAlarmThresh

usrVHAFailedSessionsCriticalAlarmThresh

Module: USR-VHA-MIB

OID (symbolic): USR-VHA-MIB::usrVHAFailedSessionsCriticalAlarmThresh

OID (numeric): 1.3.6.1.4.1.429.4.84.10.3.1

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-write

Description: The critical alarm threshold for usrVHAFailedSessionsValue gauge. Object value of 0 disables this alarm and threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAFailedSessionsMajorAlarmThresh, THEN usrVHAFailedSessionsMajorAlarmThresh will be automatically reduced to a valid value. IF this object is set to a non-zero value equal or less than the current value of usrVHAFailedSessionsClearAlarmThresh, THEN usrVHAFailedSessionsClearAlarmThresh will be automatically reduced to a valid value. Agent is allowed to either reject a SET which violates these constraints, or adjust the object value such that the constraints hold. Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAFailedSessionsAlarmState is not 'critical' and the current gauge value is equal or greater than this critical threshold, and this critical threshold is non-zero, THEN usrVHAFailedSessionsAlarmState will change to 'critical'. See usrVHAFailedSessionsAlarmState for TRAP generation details.

What is usrVHAFailedSessionsCriticalAlarmThresh?

It is the critical alarm threshold for the usrVHAFailedSessionsValue gauge, defaulting to 1000, and setting it automatically reduces the major/clear thresholds if they'd otherwise be inconsistent. A value of 0 disables this alarm; otherwise, when the failed-session count for an interval reaches or exceeds it, usrVHAFailedSessionsAlarmState moves to 'critical', flagging a burst of sessions that failed to establish.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.3.1
snmpwalk -v2c -c public <target> USR-VHA-MIB::usrVHAFailedSessionsCriticalAlarmThresh

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.3.1.1
snmpget -v2c -c public <target> USR-VHA-MIB::usrVHAFailedSessionsCriticalAlarmThresh.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.429.4.84.10.3.1.1 i <value>

Start monitoring CommWorks/3Com mobility gateway, carrier broadband access equipment supporting Mobile IP (VHA binding/tunnel status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the USR-VHA-MIB::usrVHAFailedSessionsCriticalAlarmThresh OID value, configure state conditions and alerts, and monitor any CommWorks/3Com mobility gateway, carrier broadband access equipment supporting Mobile IP (VHA binding/tunnel status) from a single console.

OID Breakdown

Upper-level ancestors (9 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.429usrANIC-MIB
1.3.6.1.4.1.429.4commonHDR2-MIB
1.3.6.1.4.1.429.4.84usrVHAUSR-DEFINITIONS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.429.4.84.10usrVHAPMUSR-VHA-MIB
1.3.6.1.4.1.429.4.84.10.3usrVHAFailedSessionsPMUSR-VHA-MIB
1.3.6.1.4.1.429.4.84.10.3.1usrVHAFailedSessionsCriticalAlarmThreshUSR-VHA-MIB