Alarm Traps; Component: Board#<N - 3Com V7122 User Manual

A
PPENDIX
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.

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'.
Component: Board#<n>
The source varbind text for all the alarms under this component is Board#<n> where n is the
slot number when the board resides in a chassis (for TP-260 and TP-1610 <n> = 1).
acBoardFatalError Alarm Trap
Table 99
Alarm:
OID:
Default Severity
Event Type:
Probable Cause:
Alarm Text:
Status Changes:
Condition:
460
I: SNMP T
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
RAPS
V7122 GatewayUser Guide