USR-VHA-MIB :: usrVHAFailedSessionsAlarmState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-VHA-MIB › usrVHAFailedSessionsAlarmState

usrVHAFailedSessionsAlarmState

Module: USR-VHA-MIB

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

OID (numeric): 1.3.6.1.4.1.429.4.84.10.3.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Alarm state is maintained by PDSN by comparing usrVHAFailedSessionsValue with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHAFailedSessionsAlarmTime is updated with the current time regardless of usrVHAFailedSessionsTrapsEnabled and usrVHAFailedSessionsAlarmChanges 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 usrVHAFailedSessionsAlarmState?

It reports the current alarm state (clear, major, or critical) for failed-session rate, maintained by comparing usrVHAFailedSessionsValue against the configured thresholds. State transitions update usrVHAFailedSessionsAlarmTime and increment usrVHAFailedSessionsAlarmChanges, 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.3.8
snmpwalk -v2c -c public <target> USR-VHA-MIB::usrVHAFailedSessionsAlarmState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.3.8.1
snmpget -v2c -c public <target> USR-VHA-MIB::usrVHAFailedSessionsAlarmState.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.429.4.84.10.3.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::usrVHAFailedSessionsAlarmState 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.8usrVHAFailedSessionsAlarmStateUSR-VHA-MIB