USR-VHA-MIB :: usrVHAActiveSessionsAlarmState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-VHA-MIB › usrVHAActiveSessionsAlarmState

usrVHAActiveSessionsAlarmState

Module: USR-VHA-MIB

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

OID (numeric): 1.3.6.1.4.1.429.4.84.10.2.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Alarm state is maintained by PDSN by comparing usrVHAActiveSessionsCurrent with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHAActiveSessionsAlarmTime is updated with the current time regardless of usrVHAActiveSessionsTrapsEnabled and usrVHAActiveSessionsAlarmChanges is incremented. This allows alarm state and time information to be retrieved by SNMP management stations that don't support SNMP traps or when traps are intentionally disabled to reduce trap processing load on the SNMP management station. Writing a 'clear' value will force the alarm state to go to 'clear'. This will count as a state change and cause a trap if the state was 'major' or 'critical'. This step conceptually occurs before comparing the alarm thresholds. If major or critical thresholds are exceeded, the appropriate state change and trap occur. This means that writing 'clear' may cause 0, 1, or 2 alarm state changes and traps.

What is usrVHAActiveSessionsAlarmState?

It reports the current alarm state (clear, major, or critical) for the active-session count, maintained by comparing usrVHAActiveSessionsCurrent against the configured thresholds, mirroring usrVHASessionsAlarmState but scoped to active-only sessions. State transitions update usrVHAActiveSessionsAlarmTime and increment usrVHAActiveSessionsAlarmChanges, and fire a trap if enabled; an admin can write 'clear' to force the state down manually.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.2.8
snmpwalk -v2c -c public <target> USR-VHA-MIB::usrVHAActiveSessionsAlarmState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.2.8.1
snmpget -v2c -c public <target> USR-VHA-MIB::usrVHAActiveSessionsAlarmState.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.429.4.84.10.2.8.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::usrVHAActiveSessionsAlarmState 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.8usrVHAActiveSessionsAlarmStateUSR-VHA-MIB