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.
Parsed from file USR-VHA-MIB.mib.txt
Company: None
Module: USR-VHA-MIB
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.
Parsed from file USR-VHA-MIB.mib
Module: USR-VHA-MIB
Vendor: UTStarcom Incorporated
Module: USR-VHA-MIB
[Automatically extracted from oidview.com]
usrVHAActiveSessionsAlarmState OBJECT-TYPE SYNTAX INTEGER { clear(0), major(1), critical(2) } MAX-ACCESS read-write STATUS current 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. " ::= { usrVHAActiveSessionsPM 8 }
usrVHAActiveSessionsAlarmState OBJECT-TYPE SYNTAX INTEGER { clear(0), major(1), critical(2) } MAX-ACCESS read-write STATUS current 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. " ::= { usrVHAActiveSessionsPM 8 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.429.4.84.10.2.8.0 | usrVHAActiveSessionsAlarmState | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.429.4.84.10.2.1 | usrVHAActiveSessionsCriticalAlarmThresh | 1 | 1 | The critical alarm threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. If… |
| 1.3.6.1.4.1.429.4.84.10.2.2 | usrVHAActiveSessionsMajorAlarmThresh | 1 | 1 | The major alarm threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. The o… |
| 1.3.6.1.4.1.429.4.84.10.2.3 | usrVHAActiveSessionsClearAlarmThresh | 1 | 1 | The alarm clear threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. This … |
| 1.3.6.1.4.1.429.4.84.10.2.4 | usrVHAActiveSessionsCriticalAlarmThreshPct | 1 | 1 | The major alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range… |
| 1.3.6.1.4.1.429.4.84.10.2.5 | usrVHAActiveSessionsMajorAlarmThreshPct | 1 | 1 | The major alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range… |
| 1.3.6.1.4.1.429.4.84.10.2.6 | usrVHAActiveSessionsClearAlarmThreshPct | 1 | 1 | The clear alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range… |
| 1.3.6.1.4.1.429.4.84.10.2.7 | usrVHAActiveSessionsTrapsEnabled | 1 | 1 | This object controls trap generation when usrVHASActiveSessionsAlarmState changes. See usrVHAActiveSessionsAlarmState for alarm d… |
| 1.3.6.1.4.1.429.4.84.10.2.9 | usrVHAActiveSessionsAlarmTime | 1 | 1 | Time last usrVHAActiveSessionsAlarmState state change. If the state has never changed, this value will be zero. |
| 1.3.6.1.4.1.429.4.84.10.2.10 | usrVHAActiveSessionsAlarmChanges | 1 | 1 | Count of usrVHAActiveSessionsAlarmState changes. |