Snmp Traps; Alarm Traps; Component: Board#<N - AudioCodes Mediant 1000 User Manual

Sip media gateways
Hide thumbs Also See for Mediant 1000:
Table of Contents

Advertisement

SIP User's Manual
I

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 11 varbinds (Variable Binding)
(1.3.6.1.4.1.5003.9.10.1.21.1).
The source varbind is composed of a string that details the component from which the trap
is being sent (forwarded by the hierarchy in which it resides). For example, an alarm from
an SS7 link has the following string in its source varbind:
acBoard#1/SS7#0/SS7Link#6
In this example, the SS7 link number is specified as 6 and is part of the only SS7 module in
the device that is placed in slot number 1 (in a chassis) and is the module to which this trap
relates. For devices where there are no chassis options the slot number of the gateway is
always 1.
I.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'.
I.1.1
Component: Board#<n>
The source varbind text for all the alarms under this component is Board#<n> where n is
the slot number (i.e., <n> = 1).
Alarm:
OID:
Default Severity:
Event Type:
Probable Cause:
Alarm Text:
Status Changes:
Condition:
Alarm status:
<text> value:
Condition:
Alarm status:
Corrective Action:
Version 5.0
Table I-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.
451
I. SNMP Traps
December 2006

Advertisement

Table of Contents
loading

Table of Contents