USR-VHA-MIB :: usrVHASessionsAlarmState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-VHA-MIB › usrVHASessionsAlarmState

usrVHASessionsAlarmState

Module: USR-VHA-MIB

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

OID (numeric): 1.3.6.1.4.1.429.4.84.10.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Alarm state is maintained by PDSN by comparing usrVHASessionsCurrent with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHASessionsAlarmTime is updated with the current time regardless of usrVHASessionsTrapsEnabled and usrVHASessionsAlarmChanges 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 usrVHASessionsAlarmState?

It reports the current alarm state (clear, major, or critical) for the total RP session count, maintained by comparing usrVHASessionsCurrent against the configured critical/major/clear thresholds. State transitions update usrVHASessionsAlarmTime and increment usrVHASessionsAlarmChanges, and (if usrVHASessionsTrapsEnabled) fire the matching trap; an admin can also write 'clear' to this object to force the alarm back down manually. This lets a management station retrieve current alarm state even if it doesn't process SNMP traps.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.1.7
snmpwalk -v2c -c public <target> USR-VHA-MIB::usrVHASessionsAlarmState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.84.10.1.7.1
snmpget -v2c -c public <target> USR-VHA-MIB::usrVHASessionsAlarmState.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.429.4.84.10.1.7.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::usrVHASessionsAlarmState 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.1usrVHASessionsPMUSR-VHA-MIB
1.3.6.1.4.1.429.4.84.10.1.7usrVHASessionsAlarmStateUSR-VHA-MIB