460 V7122 GatewayUser GuideAPPENDIX I: SNMP T RAPSThis section provides information on proprietary SNMP traps currently supported by thegateway. 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 isbeing sent (forwarded by the hierarchy in which it resides). For example, an alarm from anSS7 link has the following string in its source varbind:acBoard#1/SS7#0/SS7Link#6In this example, the SS7 link number is specified as 6 and is part of the only SS7 module inthe device that is placed in slot number 1 (in a chassis) and is the module to which this traprelates. For devices where there are no chassis options the slot number of the gateway isalways 1.Alarm TrapsThe following tables provide information on alarms that are raised as a result of a generatedSNMP trap. The component name (described in each of the following headings) refers to thestring that is provided in the ‘acBoardTrapGlobalsSource’ trap varbind. To clear a generatedalarm the same notification type is sent but with the severity set to ‘cleared’.Component: Board#The source varbind text for all the alarms under this component is Board# where n is theslot number when the board resides in a chassis (for TP-260 and TP-1610 = 1).Table 99 acBoardFatalError Alarm TrapAlarm: acBoardFatalErrorOID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.1Default Severity CriticalEvent Type: equipmentAlarmProbable Cause: underlyingResourceUnavailable (56)Alarm Text: Board Fatal Error: Status Changes:Condition: Any fatal error
