Specifications

Installation and Operation Manual Chapter 6 Troubleshooting and Diagnostics
IPmux-8/16 Ver. 6.00 Handling Alarms and Traps 6-25
Table 6-8. IPmux-8/16 Traps (Cont.)
Alarm ID Alarm Description, Severity Trap Sent to NMS
IPmux-8/16 SNMP agent received SNMP request with a
wrong community name
rfc1215.authenticationFailure
1.3.6.1.6.3.1.1.5.5
Used by TFTP application during file download TftpStatusChangeTrap
1.3.6.1.4.1.164.6.1.0.1
Used by RADview application for node status indication AgnStatusChangeTrap
1.3.6.1.4.1.164.6.1.0.2
Used by RADview application for path status indication AgnCounterChange
1.3.6.1.4.1.164.6.1.0.6
Generated for:
Power supply failure
ps1NotActive(3), major
ps1Active(4), minor
ps2NotActive(5), major
ps2Active(6), minor
Fan failure
fan1Ok(17), minor
fan1Fail(18), major
fan2Ok(19), minor
fan2Fail(20), major
Heat alarm
heatAlarmOff(7), minor
heatAlarmOn(8), major
General alarms.
General alarms generated by an external circuit connected to
the ALARMS connector.
SystemTrap
1.3.6.1.4.1.164.6.1.3.0.6
Working with Alarm Relay
IPmux-8/16 includes an alarm relay port which has two functions:
Dry contact – a trigger for an external monitoring equipment when one of the
alarms become active
General purpose input port – it generates a system trap to the NMS when
triggered from an external device.
Alarms are classified to 3 categories:
Major alarm – all physical alarms, power supply and fan failures
Minor alarm – alarms related to IP bundle status: ID 26, 27
General alarm – a circuit between one of the four general-purpose discrete
input pins and GND is closed.
All alarms are reported in the system Event Log.