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.
Parsed from file USR-VHA-MIB.mib.txt
Company: None
Module: USR-VHA-MIB
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.
Parsed from file USR-VHA-MIB.mib
Module: USR-VHA-MIB
Vendor: UTStarcom Incorporated
Module: USR-VHA-MIB
[Automatically extracted from oidview.com]
usrVHASessionsAlarmState 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 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. " ::= { usrVHASessionsPM 7 }
usrVHASessionsAlarmState 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 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. " ::= { usrVHASessionsPM 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.429.4.84.10.1.7.0 | usrVHASessionsAlarmState | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.429.4.84.10.1.1 | usrVHASessionsCriticalAlarmThresh | 1 | 1 | The critical alarm threshold for usrVHASessionsCurrent gauge. The value of this object will be automatically set to the lesser of… |
| 1.3.6.1.4.1.429.4.84.10.1.2 | usrVHASessionsMajorAlarmThresh | 1 | 1 | The major alarm threshold for usrVHASessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. The object… |
| 1.3.6.1.4.1.429.4.84.10.1.3 | usrVHASessionsClearAlarmThresh | 1 | 1 | The alarm clear threshold for usrVHASessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. This objec… |
| 1.3.6.1.4.1.429.4.84.10.1.4 | usrVHASessionsMajorAlarmThreshPct | 1 | 1 | The major alarm threshold for usrVHASessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of th… |
| 1.3.6.1.4.1.429.4.84.10.1.5 | usrVHASessionsClearAlarmThreshPct | 1 | 1 | The clear alarm threshold for usrVHASessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of th… |
| 1.3.6.1.4.1.429.4.84.10.1.6 | usrVHASessionsTrapsEnabled | 1 | 1 | This object controls trap generation when usrVHASessionAlarmState changes. See usrVHASessionsAlarmState for alarm details. |
| 1.3.6.1.4.1.429.4.84.10.1.8 | usrVHASessionsAlarmTime | 1 | 1 | The time of the last usrVHASessionsAlarmState state change. If the state has never changed, this value will be zero. |
| 1.3.6.1.4.1.429.4.84.10.1.9 | usrVHASessionsAlarmChanges | 1 | 1 | Count of usrVHASessionsAlarmState changes. |