User manual

Mediant 2000 SIP User’s Manual L. SNMP Traps
Version 4.4 271 July 2005
Appendix L SNMP Traps
This section provides information on proprietary SNMP traps currently supported by the gateway.
There is a separation between traps that are alarms and traps that are not (logs). Currently all
have the same structure made up of the same 10 varbinds (Variable Binding)
(1.3.6.1.4.1.5003.9.10.1.21.1).
L.1 Alarm Traps
The following tables provide information on alarms that are raised as a result of a generated
SNMP trap. The component name (described in each of the following headings) refers to the
string that is provided in the ‘acBoardTrapGlobalsSource’ trap varbind. To clear a generated
alarm the same notification type is sent but with the severity set to ‘cleared’.
L.1.1 Component: System#0
Table L-1: acBoardFatalError Alarm Trap
Alarm:
acBoardFatalError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.1
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Board Fatal Error: <text>
Status Changes:
Condition: Any fatal error
Alarm status: Critical
<text> value: A run-time specific string describing the fatal error
Condition: After fatal error
Alarm status: Status stays critical until reboot. A clear trap is not sent.
Corrective Action: Capture the alarm information and the Syslog clause, if active. Contact your first-level
support group. The support group will likely want to collect additional data from the
device and perform a reset.
Table L-2: acBoardConfigurationError Alarm Trap
Alarm:
acBoardConfigurationError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.2
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Board Config Error: <text>
Status Changes:
Condition: A configuration error was detected
Alarm status: critical
<text> value: A run-time specific string describing the configuration error.
Condition: After configuration error
Alarm status: Status stays critical until reboot. A clear trap is not sent.