5-2
Cisco H.323 Signaling Interface User Guide
OL-4806-01 Rev. A14
Chapter 5 Troubleshooting Cisco HSI Alarms
Alarms Overview
Retrieving and Reporting Alarms
Events with a severity level of critical, major, or minor are classified as alarms and can be retrieved
through the Man-Machine Language (MML) interface and a Simple Network Management Protocol
(SNMP) manager.
An alarm must be reported when an alarm state changes (assuming the alarm does not have an unreported
severity).
Informational Event Requirements
Informational events do not require state changes. An informational event is a warning that an abnormal
condition that does not require corrective action has occurred. An invalid protocol call state transition is
an example of an informational event. The informational event needs to be reported, but it is transient.
No corrective action is required by the management center to fix the problem.
An informational event is reported once, upon occurrence, through the MML and SNMP interfaces. The
MML interface must be in the
rtrv-alms:cont
mode for the event to be displayed. The event is not
displayed in subsequent
rtrv-alms
commands.
SNMP Trap Types
Alarms have SNMP trap types associated with them. Table 6-2 identifies the trap types.
Table 5-1
Alarm Severity Levels
Severity Level
Description
Critical
A serious problem exists in the network. Clear critical alarms immediately.
A critical alarm should force an automatic restart of the application.
Major
A disruption of service has occurred. Clear this alarm immediately.
Minor
No disruption of service has occurred, but clear this alarm as soon as
possible.
Informational
An abnormal condition has occurred. It is transient and does not require
corrective action. (An invalid protocol call state transition is an example of
an event that prompts such an alarm.) No corrective action is required by
the management center to fix the problem.
Table 5-2
SNMP Trap Types
Trap Type
Trap Description
0
No error
1
Communication alarm
2
Quality of service
3
Processing error
4
Equipment error
5
Environment error