User Manual Part 2

Link CX-24 User’s Manual
Version 1.0 Page 79 February 2004
trapSentCounter }
DESCRIPTION
"A trap that indicates the beginning or end of a test procedure.
An alarmTrap trap might result from this procedure."
::= 3
END
E-2 Enterprise Traps
Link CX-24 supports three enterpriseSpecific traps - alarmTrap, configurationChangeTrap, and unitTest-
Trap. Each of these traps contains all the relevant variables for that particular trap, in order to minimize
polling. One variable that is in each of the traps is a counter, so that the network management application
can detect loss of traps.
E-2.1 alarmTrap
Link CX-24 sends this trap when any of the alarm variables changes, either going into or out of an alarm
condition. All of the relevant alarm conditions and performance data are contained in the trap PDU, along
with a counter of enterprise traps sent. The variables include:
• trap counter
DS3 LOS status (DS3 input absent/present)
Tx Power status (under/over minimum power)
Tx Synthesizer lock status (unlocked/locked)
Rx Synthesizer lock status (unlocked/locked)
RSSI level status (under minimum level)
Rx overload status (over maximum level)
BER status (over threshold)
demodulator lock status (unlocked/locked)
• BER
• RSSI
• Tx Power
E-2.2 configurationChangeTrap
Link CX-24 sends this trap when the persistent state of the Link CX-24 changes. This trap alerts the
network management application that it must refresh its database. If all management is through SNMP
exclusively, this trap is redundant. If on the other hand, management is a mixture of HTTP and SNMP this
will keep the SNMP side completely consistent. All the relevant persistent state variables are contained in
the trap PDU, along with the trap counter. The variables include:
• trap counter
• Tx control (attenuated/unattenuated)
ATPC control (ATPC enabled/disabled)
Tx power setting
ATPC peer IP address (IP address of the CX at the other end of the radio link)
• channel number
RSSI alarm threshold
DS3 LOS control (enable/disable alarm for LOS)