To open the Alarm Summary window:
Monitoring Your Network
-
Monitoring Alarms - Viewing Alarm Information - Using the NerveCenter Client -
The NerveCenter Client provides two windows that you can use to view information about current alarm instances:
If you're only connected to one server or are only interested in viewing alarm instances from one server at a time, you should use the Alarm Summary window. On the other hand, if you are connected to multiple servers and want to be able to view alarm instances from all servers at once, you should use the Aggregate Alarm Summary window.
To open the Alarm Summary window:
To open the Aggregate Alarm Summary window:
From the client's
Admin menu, choose Aggregate Alarm Summary.
The Aggregate Alarm Summary window is displayed.
These windows are very similar. Both contain a tree view of the current alarm instances in the left pane, and details about the current alarm instances in the right pane. For information about how to interpret the information in these two panes, see the following sections:
The left pane in both the Alarm Summary window and the Aggregate Alarm Summary window contains a tree of severities.
The only difference between the two trees is that the top folder in the Alarm Summary window represents the active server, while the top folder in the Aggregate Alarm Summary window represents all of the servers to which you are connected.
This tree view has two purposes:
The right pane in both the Alarm Summary and Aggregate Alarm Summary windows contains an alarm detail view that presents quite a bit of information about each current alarm instance, as shown in Alarm Detail Pane.
This is the pane you'll use for most of your monitoring.
Fields in Alarm Detail Pane explains what information is available for each alarm instance.
| Column | Description |
|---|---|
The name of the server that is managing the alarm instance. This column is present only in the Aggregate Alarm Summary window. | |
The date and time at which the alarm instance's most recent transition occurred. | |
The name of the alarm from which the alarm instance was created. If you have any question about what condition a particular alarm is monitoring, you can use the NerveCenter Client to view a definition of the alarm. For information about viewing such a definition, see the section Getting Information about an Alarm. | |
The hostname of IP address of the node the alarm instance is monitoring. | |
The subobject associated with the alarm instance. This subobject consists of a MIB base object plus an instance number, for example, ifEntry.1. The instance usually tells you which interface on a device is being monitored. | |
The current state of the alarm instance. The name of the state should indicate the condition NerveCenter is reporting. For example, if an instance of the alarm IfUpDownStatus is monitoring an interface and the current state of the alarm instance is "down," the operational status of the interface is down. | |
The name of the trigger that caused the most recent alarm transition. | |
The type of trigger that caused the most recent alarm transition. The possible types are poll, mask, fire (alarm), and built-in. | |
The name of the poll, mask, or alarm that generated the trigger. Or, in the case of a built-in trigger, the name of the trigger. Given the name of the trigger that caused the transition and the name of the object that generated the trigger, you can pinpoint the exact cause of a transition. See the section Getting Information about a Trigger for details on this subject. |
The alarm detail pane is designed primarily for reading. However, there are a couple of actions you can take from this pane.
This feature is useful for tasks such as ordering alarm instances by node.
| Using the NerveCenter Web Client | Interpreting Alarm-Instance Information |
| 29 July 2003 |