Monitoring Your Network
-
Resetting Alarms -
Some alarms are designed to return to the Ground state when the condition they detect goes away. For example, the predefined alarm ifLoad tracks the level of traffic on an interface. As traffic increases, instances of this alarm may move from the Ground state to the medium state to the high state. Then, as traffic subsides, they may transition from the high state to the medium state to the Ground state. When these instances return to Ground state, they are automatically deleted from the Alarm Summary window.
Other alarms, however, are designed to remain in a terminal state until they are manually reset. For example, an instance of the predefined alarm Authentication transitions to the Intrusion state if a node receives four or more authentication-failure traps in a ten-minute period. The instance then remains in this state until it is manually reset.
Both the NerveCenter Web Client and the NerveCenter Client give you the ability to reset alarm instances, though in somewhat different ways. For information on the reset capabilities afforded by each client, see the following sections:
Whether resetting alarms from the Client or Web Client, if you reset an alarm to ground, any pending triggers fired by that alarm are cleared if the Clear Triggers for Reset To Ground or Off checkbox is checked in the Client's alarms definition window for the alarm.
| How to Interpret Logged Data | Using the NerveCenter Web Client |
| 29 July 2003 |