|
|
This chapter describes how the Cisco 6100 Series system events are transmitted through the ViewRunner for Windows and ViewRunner for HP OpenView software. The following sections are included:
In the ViewRunner for Windows software, you can view events generated by the Cisco 6100 Series system in one of the following ways:
This section provides information on viewing events in ViewRunner for Windows, chassis alarms, examples of module alarms, and the use of color in the ViewRunner for Windows software.
In ViewRunner, use the Event History View dialog box to show all of the events that were asserted and cleared for a particular Cisco 6100 Series system.
During each session, default interval poll settings in the ViewRunner software cause it to poll the node for new events at 15-second intervals. You can change this poll interval by selecting Options > ViewRunner Preferences. Doing so, opens the ViewRunner Preferences: Interval Poll Settings dialog box (see Figure 1-1) where the interval can be increased or decreased.
The Cisco 6100 Series system node saves no more than 200 events at one time, beginning with number 1 and incrementing indefinitely. When the node event log has more than 200 events, the oldest event in the queue, event 1, is removed, and the newest event is added to the bottom of the queue as event 201. Therefore, depending on the number of generated events, the node queue could begin with event 101 and end with event 300.
The ViewRunner for Windows software can save more than 200 events at a time. If, for example, the Cisco 6100 Series node event queue shows events 101 through 300, the ViewRunner could be displaying events 50 through 300. (The number of events in the ViewRunner display depends on how long the ViewRunner session has been active and on what the node was showing at the time the session began.)
The event numbers for the Cisco 6100 Series system display and the ViewRunner display correspond. For example, event 50, in the Cisco 6100 Series system display, corresponds to event 50 in the ViewRunner display. Events must be removed at the node or between ViewRunner sessions or polls. After events are removed from the top of the queue, they do not appear in the ViewRunner display. For example, if more than 200 events occur between consecutive ViewRunner sessions, you do not see those that were already removed from the node queue when you begin the new ViewRunner session. ViewRunner generates an alarm indicating that events have been missed during the current poll.
If the ViewRunner detects a system controller (SC) module reset during an active session, all displayed events are removed from the Event History View dialog box, and only events occurring after the reset are displayed. The Cisco 6100 Series system node loses event history and begins numbering again at 1 after an SC module reset.
Figure 1-2 is an example of the ViewRunner for Windows Event History View dialog box.
The fields in the Event History View dialog box are described in Table 1-1.
| Field | Field Description |
|---|---|
Sequence number of the event in the ViewRunner Event History View dialog box for this session. The field also contains an alarm icon in which the color indicates the severity of the event:
| |
Cisco determines the severity of the event. Event severities are defined as follows:
| |
The date and time when the event occurred. | |
The module that the event is asserted against. The information in this field can be used to help locate the event in the Cisco 6100 Series Alarm Summary Guide. The entity can be any one of the following: CAP ATU-C, SC, NI1, LIM2 controller, LIM, Slot, ViewRunner, or Unknown. An Unknown entity appears only if the format of the data from the node is faulty. | |
Corresponds to the chassis and slot number associated with the event. You can use the information in this field to pinpoint the source of the event and thus isolate the problem. ViewRunner displays Unknown in the AID field if an event was asserted by an entity that was later deleted, or by an entity that was added but not yet discovered by ViewRunner at the time the event was generated. To go directly to the entity and slot location in which the event was received, click the underlined text in this field. | |
The current status of the event. Possibilities include
| |
Description | A short description of the event. Corresponds to one of the descriptions found in the system event definitions tables in the Cisco 6100 Series Alarm Summary Guide. This description is a predefined string based on the entity and event code from the node. |
| 1NI = network interface 2LIM = line interface module 3AID = access identifier |
To sort the contents of the ViewRunner Event History View dialog box according to any one of the fields in the preceding table, click the field header (such as AID, Log Time, Severity). If you click more than one column heading, you can nest the results of sort operations. The order in which you select headings determines the order in which results are nested. If there are more entries than can fit in the dialog box, a scroll bar appears, allowing you to scroll through the entries.
To remove events from the display, select the events and delete them. Select events in the Event History View dialog box.
To select an event, click the Sequence Id number of each row. Use the Shift or Ctrl key to select multiple events.
To delete the selected events, click the Alarm toolbar deletion button. (This button is the x next to the discovery icon on the ViewRunner toolbar; see Figure 1-3.) Removing an event does not delete it permanently from the Cisco 6100 Series system. It is removed only from the ViewRunner display.
The Current Alarms View dialog box lists all currently asserted alarm events in the system, including module, slot, and image alarm events. The dialog box format is similar to that for the Event History View dialog box.
You can use the Current Alarms View dialog box to retrieve and display current alarm events. You can do this when the dialog box is first opened or after you manually request a refresh. To retrieve current alarm events, you can also go to Options > ViewRunner Preferences to set a smaller polling interval in the ViewRunner Preferences dialog box (see Figure 1-1).
In the Current Alarms View dialog box, click the blue underlined text to have ViewRunner take you to the Properties dialog box of the chassis, slot, and port where the alarm event was asserted.
Figure 1-4 is an example of the Current Alarms View dialog box.
Logical service-oriented dialog box navigation is available in the Event History View dialog box. Just click the blue, underlined text, and ViewRunner takes you to the Properties dialog box of the chassis, slot, and port where the alarm was asserted.
To view alarms for the Cisco 6100 Series system, use the command line interface (CLI). For information on the command syntax and use of the CLI, refer to the ViewRunner for Windows Installation and Administration Guide.
The following are some examples of CLI commands used to show alarms on various Cisco 6100 Series system components.
show alarms show alarms sys
show alarms curtained sys
show alarms chassis L.3
show alarms min chassis L
show alarms atuc M.1.12
show alarms crit lp L.2.12.2
In the ViewRunner for Windows software, Release 2.0, the valid command is show alarms with all of its options.
ViewRunner for Windows Release 2.4.0 supports two chassis alarm events. Both of these alarms are critical and they both report fan tray status. You can view chassis alarms in the Event History View dialog box or in the Current Alarms View dialog box. Only the Cisco 6130 system supports a fan tray at the time of this Release.
The first alarm, MC Fan Failure, occurs when you have checked the Fan Tray Present toggle on the 6100 Properties dialog box (see Figure 1-5), but a fan tray is not present.
The second alarm, MC Fan Required, occurs when you have configured a module requiring a fan tray, such as the DMT-2 ATU-C module and no fan tray can be detected. In this instance, the DMT-2 module will detrain and issue a corresponding critical module alarm.
You can arrive at the appropriate Module Properties dialog box for the alarm in one of three ways:
1. Click the hyperlink in the Event History View dialog box.
2. Click the Current Alarms View dialog box.
3. Navigate to the AID of the alarm.
Figure 1-6 is a Subtend Host Module Port Properties dialog box showing the port of a Subtend Host module in alarm.
Figure 1-7 is a Network Interface Module Properties dialog box showing an NI module in alarm.
The Chassis View displays colored module ejector tabs to indicate the status and state of each module and its ports. Table 1-2 lists the colors according to the highest priority color (displays first) and the lowest priority color (displays last), in cases where more than one of the conditions described below is met. Refer to the ViewRunner for Windows Provisioning and Operation Guide for more information on states.
| Ejector Tab Color (in order of priority) | State or Alarm Type | Description |
|---|---|---|
Red | A critical alarm is the most severe alarm present on the module or any of its ports. | |
Orange | A major alarm is the most severe alarm present on the module or any of its ports. | |
Yellow | A minor alarm is the most severe alarm present on the module or any of its ports. | |
Blue | Indicates the Equipage state of the module is Unfilled-Provisioned. This state is used when a module has been configured in the slot; however, the SC1 module has not communicated with it since power up. | |
Brown | Either the module is configured with the Administrative state of Locked, or all of the module's ports are configured with the Administrative state of Locked. | |
Green | The module and all of its ports are in a Normal state. |
| 1SC = system controller |
The ejector tab colors are updated when you
ViewRunner for Windows displays colors on module and port tabs, providing a quick indication of their Administrative and Operational state. The displayed color changes any time you:
A priority scheme defines which color is displayed on the module or port tab.
ViewRunner for Windows uses tabs with different colors to show various levels of state functionality. The varying tab colors are defined in Table 1-3.
| Icon Color | State and Alarm Types | Description |
|---|---|---|
Blue | State---Unknown | For module tabs only. Indicates that the Equipage state of the module is Unfilled-Provisioned. This state is used to indicate that a module has been configured in the slot, but the SC has not communicated with it since power-up. |
Brown | State---Locked | For module or port tabs. Node reports Administrative state of Locked. |
Red | Alarm Type---Critical | For module or port tabs. A critical alarm is the most severe alarm present. |
Orange | Alarm Type---Major | For module or port tabs. A major alarm is the most severe alarm present. |
Yellow | Alarm Type---Minor | For module or port tabs. A minor alarm is the most severe alarm present. |
Cyan | Alarm Type---Warning | For module or port tabs. A warning alarm is the most severe alarm present. Not supported in this release. |
Green | State---Normal/Up | For module or port tabs. Indicates a Normal state. |
In the ViewRunner for HP OpenView software, you can view events generated by the Cisco 6100 Series system in one of the following ways:
This section provides information on viewing events in ViewRunner for HP OpenView, chassis alarms, examples of module alarms, and the use of color in the ViewRunner for HP OpenView software.
The Error Events Browser shows all the alarms that have been asserted and cleared for a particular Cisco 6100 Series system.
The columns in the Error Events Browser are described in Table 1-4.
| Column | Column Description |
|---|---|
Ack | Acknowledgment of the alarm. |
Severity | The severity of the alarm or event as determined by Cisco. The alarm or event severities are Information, Undefined, Critical, Major, Minor, Warning, and Normal. |
Date and Time | The date and time on which the alarm or event occurred. |
Source | The node against which the alarm or event is asserted. The information in this column can be used to help track down the alarm or event. An "Unknown" entity is returned only when the format of the data from the node is faulty. |
Message | A short description of the alarm or event. This description is a predefined string based on the entity and event code from the node. The first part of the message identifies the chassis and slot number associated with the alarm or event. In some cases, such as a system controller reset, the chassis and slot number information are missing because all the alarms on all modules are cleared. In other cases, such as when an alarm comes from a subtended node, the port number is also included. Some events or alarms are discovered by ViewRunner. In this case, the notation "(Discovered by ViewRunner)" appears at the end of the alarm description. |
The contents of the ViewRunner Error Events Browser can be sorted by any one of the columns in Table 1-4 by clicking on the column header. Clicking on more than one column header allows you to nest sorts in the order of column selection. If there are more entries than can fit in the browser window, a scroll bar appears to allow scrolling through the entries.
The Current Alarms dialog box displays a concise list of all currently asserted alarms in the system, including module, slot, port, and image alarms. The dialog box format is similar to the Error Events Browser.
In the Current Alarms dialog box, current alarms are retrieved and displayed when the dialog box is first opened, and when you manually request an alarm synchronization. The Current Alarms dialog box is opened by clicking Current Alarms in the 6100 Chassis View or by using the View menu option.
Figure 1-9 is an example of the Current Alarms dialog box.
The columns in the Current Alarms dialog box are described in Table 1-5.
| Column | Column Description |
|---|---|
AID | The access identifier for the resource (the chassis and slot) in alarm. Click the hyperlink to use logical service-oriented navigation to go to the status dialog box for the entity in alarm. |
Entity | The module against which the alarm or event is asserted. The entity can be either the ATU-C (CAP or DMT), STU-C, system controller, NI, LIM, or STM. |
Severity | The severity of the alarm or event as determined by Cisco. The alarm or event severities are Information, Undefined, Critical, Major, Minor, Warning, and Normal. |
Description | A short description of the alarm or event. This description is a predefined string based on the entity and event code from the node. |
Click Alarm Sync in the lower left corner of the Current Alarms dialog box to synchronize alarms to ensure that no traps have been missed by ViewRunner.
The command line interface (CLI) can be used to view alarms on the Cisco 6100 Series system. Complete information on the command syntax and use of the CLI is found in the ViewRunner for HP OpenView Provisioning and Operation Guide.
Following are some examples of CLI commands used to show alarms on various Cisco 6100 Series system entities.
> show alarms > show alarms sys
> show alarms crit.maj sys
> show alarms chassis L.3
> show alarms min chassis L
> show alarms atuc M.1.12
> show alarms crit lp L.2.12.2
Currently, the only valid command is show alarms with all its options.
When you click on a module in the 6100 Chassis View and choose Module > Status, you arrive at the appropriate Module Properties dialog box for the alarm.
Figure 1-10 is an ATU-C Module Properties dialog box showing an ATU-C module alarm bell icon.
The 6100 Chassis View displays colored module ejector tabs and icons that feature a lock and key to indicate the status and state of each module and its ports. The color of each ejector tabs that displays is based on a set of rules defined in the ViewRunner for HP OpenView Provisioning and Operation Guide, which describes the highest priority color that displays first and the lowest priority color that displays last, in cases where more than one of the conditions described is met. Refer to the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on states.
| Tab Color | Description |
|---|---|
White | This state indicates that the resource should not be monitored and that the operational status is being ignored. Traps are still received and displayed in the Event Categories window. ViewRunner uses this state for displaying modules in Cisco 6100 Series systems that are in loss of communication, but for which there is configuration information in the database. |
Blue | This state indicates that the Cisco 6100 Series Slot State is Empty---Provisioned. This state occurs when the system controller has not communicated with the module, but a module configuration exists for the slot. This could occur when
|
Red | This state indicates that a critical alarm is the most severe alarm present on the module or any of its ports. |
Orange | This state indicates a major outstanding alarm on the module or any of its ports. |
Yellow | This state indicates that a minor alarm is the least severe alarm present on the module or any of its ports. |
Green | This state indicates that the module and all of its ports are in a Normal state. |
Client dialog boxes are updated dynamically in real time while they are open. Changes detected by ViewRunner server applications are propagated to all ViewRunner clients when
Lock and key icons that display on the modules in the Chassis View dialog box indicate the administrative state of the module and its ports as shown in Table 1-7.
.
| Icon | Module State | Port State |
|---|---|---|
Lock (shown locked) | Locked or all ports locked | All ports locked |
Lock (shown unlocked) | Unlocked | All ports unlocked |
Lock (shown locked) with key | Unlocked | At least one port locked |
Administrative states are set by an application or a user. Consult OpenView Help on both Administrative and Operational status colors via the OpenView Help > Display Legend.
Table 1-8 shows the administrative condition of an entity, its color, and the meaning of that color in HP OpenView.
| Administrative Condition | Default Color | HP OpenView Meaning |
|---|---|---|
Unmanaged | Off-white | Indicates that the resource (entity) should not be monitored and that the operational status is being ignored. Traps are still received and displayed in the HP OpenView Event Categories window. |
Testing | Salmon | An application sets the status to "testing" when an object is undergoing temporary diagnostic or maintenance procedures. |
Restricted | Tan | An application sets the status to "restricted" when an object is functioning normally, but it might not be available to all users. |
Disabled | Dark Brown | An application sets the status to "disabled" when an object is inactive (although the object might be functioning correctly). |
The operational status of a particular symbol represents the status of certain object attributes, as defined by the managing application. Unknown and Normal or Up states are considered normal. The last four states listed in Table 1-9 are considered abnormal.
| Operational Condition | Default Color | HP OpenView Meaning |
|---|---|---|
Unknown | Blue | Indicates that the status of the resource cannot be determined. |
Normal | Green | Resource is in a normal operational state. |
Warning | Cyan | An alarm level that indicates a condition exists that could potentially cause a problem with the resource. |
Minor | Yellow | An alarm level that indicates a problem of relatively low severity that should not impede use of the resource. |
Major | Orange | An alarm level that indicates some kind of possibly service-affecting problem with the resource. The severity of the problem is relatively high and normal use of the resource is likely to be impaired. |
Critical | Red | An alarm level that indicates a severe problem exists with the resource and normal use is disrupted or severely impeded. This is the most severe alarm level. |
The colors listed in Table 1-10 are used by ViewMap icons.
| Operational Condition | Default Color | HP OpenView Meaning |
|---|---|---|
Test | Salmon | Node reports a Maintenance state of Under Test. |
Critical | Red | Indicates the most severe alarm at this level in the map hierarchy and below. |
Major | Orange | Indicates the most severe alarm at this level in the map hierarchy and below. |
Minor | Yellow | Indicates the most severe alarm at this level in the map hierarchy and below. |
Normal | Green | No alarms are present at this level in the map hierarchy and below. |
ViewRunner follows the basic HP OpenView paradigm. For example, the unmanaged Administrative state overrides a critical Operational alarm. Table 1-11 lists the state colors for the Cisco 6100 Series as they appear on the ejection tabs in the Chassis View window.
The operational state of the fan tray, if one is installed, is represented by a rectangular, colored box which is displayed in the upper right corner of the chassis in the Chassis View. The box changes colors to reflect the status of the fan tray. The fan status and alarm colors are the same as those used to indicate status and alarms of the Cisco 6100 Series Chassis.
| Order of State Display | Color | State Type | Cisco 6100 Series Chassis View Description |
|---|---|---|---|
Unmanaged | Off-white | Administrative | Indicates that the resource should not be monitored and that the operational status is being ignored. Traps are still received and displayed in the HP OpenView Event Categories window. ViewRunner uses this state to display modules in Cisco 6100 Series systems that are in Loss of Communication if their configuration information is in the database. |
Unknown | Blue | Operational | Indicates that the equipage state of the module is Empty-Provisioned. This state is used to depict when a module has been configured in the slot, however the system controller has not communicated with it since power up. This could occur when
|
Test | Salmon | Administrative | Node reports the maintenance state of Under Test for the module or for all of its ports. |
Critical | Red | Operational | A critical alarm is the most severe alarm present. |
Major | Orange | Operational | A major alarm is the most severe alarm present. |
Minor | Yellow | Operational | A minor alarm is the most severe alarm present. |
Normal | Green | Operational | Indicates a normal state. |
Posted: Tue Nov 16 15:31:14 PST 1999
Copyright 1989-1999©Cisco Systems Inc.