Mediant 2000 SIP User's Manual
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
Alarm:
OID:
Default Severity
Event Type:
Probable Cause:
Alarm Text:
Status Changes:
Condition:
Alarm status:
<text> value:
Condition:
Alarm status:
Corrective Action:
Alarm:
OID:
Default Severity
Event Type:
Probable Cause:
Alarm Text:
Status Changes:
Condition:
Alarm status:
<text> value:
Condition:
Alarm status:
Version 4.4
Table L-1: acBoardFatalError Alarm Trap
acBoardFatalError
1.3.6.1.4.1.5003.9.10.1.21.2.0.1
Critical
equipmentAlarm
underlyingResourceUnavailable (56)
Board Fatal Error: <text>
Any fatal error
Critical
A run-time specific string describing the fatal error
After fatal error
Status stays critical until reboot. A clear trap is not sent.
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
acBoardConfigurationError
1.3.6.1.4.1.5003.9.10.1.21.2.0.2
Critical
equipmentAlarm
underlyingResourceUnavailable (56)
Board Config Error: <text>
A configuration error was detected
critical
A run-time specific string describing the configuration error.
After configuration error
Status stays critical until reboot. A clear trap is not sent.
271
L. SNMP Traps
July 2005