Other Event Types - NETGEAR NMS100 Reference Manual

Reference Manual for the ProSafe Network Management System NMS100

Other Event Types

The pollDeviceDown event is an example used in this section. The mechanism is the same for
other types of events, including those generated for Status Variable and Manual Threshold Alarms.
The following table shows common events and when they occur.
Table 4-2. ProSafe NMS Events
Event Subtree
Snmpc-Status-Polling
Snmpc-System-Info
Snmpc-Threshold-Alarm
snmp-Traps
4-10
Trap Name
pollDeviceDown
pollNoResponse
pollRequestRejected
pollResponse
pollServiceDown
pollServiceNoResponse
pollServiceResponding
pollStatusTestFail
pollStatusTestPass
pollAgentConnect
pollAgentDisconnect
alarmAutoThresholdExpand
alarmAutoThresholdReduce
alarmAutoThresholdSet
alarmAutoThresholdTrigger
alarmManualThresholdTrigger Trend manual alarm passed threshold.
alarmManualThresholdReset
authenticationFailure
coldStart
linkDown
linkUp
September 2004 202-10058-01
Description
Device has not responded for three consecutive
poll sequences.
Device failed to respond to one poll sequence.
Device rejected the sysObjectId.0 or the user-set
status polling variable.
Device responded to a poll sequence.
Could not connect to the TCP port after three
consecutive attempts.
Could not connect to the TCP port after one
attempt.
Connection to TCP port OK.
Status variable test failed.
Status variable test passed.
SNMPc polling agent connection to server
established.
SNMPc polling agent connection to server lost.
Trend auto-baseline moved higher.
Trend auto-baseline moved lower.
Trend auto-baseline initially set.
Trend auto-baseline exceeded.
After being triggered, a trend manual alarm no
longer passes the threshold test.
Trap generated by a device on an illegal access
(bad community name).
Trap generated by a device after it restarts.
Trap generated by a device when a link fails.
Trap generated by a device when a link that was
down recovers.
Polling and Emailing