USR-VHA-MIB :: usrVHAActiveSessionsCriticalAlarmThresh

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-VHA-MIB › usrVHAActiveSessionsCriticalAlarmThresh

usrVHAActiveSessionsCriticalAlarmThresh

Module: USR-VHA-MIB

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

OID (numeric): 1.3.6.1.4.1.429.4.84.10.2.1

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: The critical alarm threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. If usrVHAMaxSessions is reduced below the value of this object, this object will automatically reduced so that this constraint holds. 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 usrVHAActiveSessionsMajorAlarmThresh, THEN usrVHAActiveSessionsMajorAlarmThresh 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 usrVHAActiveSessionsClearAlarmThresh, THEN usrVHAActiveSessionsClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHAActiveSessionsCriticalAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAActiveSessionsAlarmState is not 'critical' and the current gauge value is equal or greater than this critical threshold, and this critical threshold is non-zero, THEN usrVHAActiveSessionsAlarmState will change to 'critical'. See usrVHAActiveSessionsAlarmState for TRAP generation details.

What is usrVHAActiveSessionsCriticalAlarmThresh?

It is the critical alarm threshold for the usrVHAActiveSessionsCurrent gauge (active, non-dormant sessions), automatically capped at usrVHAMaxSessions and reducing the major/clear thresholds if needed to stay consistent. A value of 0 disables this alarm; otherwise, when active sessions reach or exceed it, usrVHAActiveSessionsAlarmState moves to 'critical', giving an admin a capacity warning specifically about actively transmitting sessions rather than the broader total.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.2.1
snmpwalk -v2c -c public <target> USR-VHA-MIB::usrVHAActiveSessionsCriticalAlarmThresh

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.2.1.1
snmpget -v2c -c public <target> USR-VHA-MIB::usrVHAActiveSessionsCriticalAlarmThresh.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> usrVHAActiveSessionsCriticalAlarmThresh.1

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::usrVHAActiveSessionsCriticalAlarmThresh 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.2usrVHAActiveSessionsPMUSR-VHA-MIB
1.3.6.1.4.1.429.4.84.10.2.1usrVHAActiveSessionsCriticalAlarmThreshUSR-VHA-MIB