Monitoring Your Network - Monitoring Alarms - Viewing Alarm Information - Using the NerveCenter Web Client -
Viewing Alarm Information      Using the NerveCenter Client

Using the NerveCenter Web Client

To view information about current alarm instances using the NerveCenter Web Client, you use the Web client's alarm-summary window. By default, you are taken to this window when you log in.

 
  To get to the alarm-summary window via the Login page:

  1. Enter your user name and password in the Username and Password fields.
  2. Make sure that the Auto-Connect Previously Selected Servers radio button is selected.

    Before you can connect to one or more NerveCenter servers and view information about the alarm instances created by those servers, you must have created a list of servers as described in Modifying the Server Connection List on page 29 and set your alarm viewing preferences as described in Setting Preferences on page 31.

  3. Select the OK button.

The alarm-summary window displays.

alarmSummary221

The left frame in the window contains a tree view of the current alarm instances that meet the criteria you specified when you set your preferences. You can expand the tree by clicking on the plus sign associated with a branch that contains other branches or leaves, and you can display information about a set of alarm instances in the right frame by selecting one of the hypertext links in the tree view.

For information about how to interpret the information in tree and alarm-detail frames, see the following sections:

The Tree View

The left frame in the alarm-summary window contains a tree view of the alarm instances you've requested to see. The figure below shows an expanded tree of alarm instances organized first by server, then by severity.

alarmTree23

This tree view serves several purposes:

The Alarm-Detail View

The right frame in the alarm-summary window contains an alarm-detail view that presents quite a bit of information about selected alarm instances, as shown in Alarm-Detail Frame.

Alarm-Detail Frame

alarmDetail222

This is the frame you'll use for most of your monitoring.

Fields in Alarm-Detail Pane explains what information is available for each alarm instance.

Fields in Alarm-Detail Pane

Column Description

Name

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.

Node

The hostname or IP address of the node the alarm instance is monitoring.

Time

The date and time at which the alarm instance's most recent transition occurred.

SubObject

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.

State

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.

Trigger

The name of the trigger that caused the most recent alarm transition.

Type

The type of trigger that caused the most recent alarm transition. The possible types are poll, mask, fire (alarm), and built-in.

Source

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 frame is designed primarily for reading. However, there are a couple of actions you can take from this frame.


Viewing Alarm Information Using the NerveCenter Client
29 July 2003