|
|
This chapter discusses ViewRunner fault management and the dialog boxes associated with the Cisco 6100 Series system or ViewRunner for HP OpenView events and alarms.
Faulty resources are taken out of service by the Cisco 6100 Series system. The Cisco 6100 Series system changes the ISO state of the chassis, module, slot, or port to indicate that operations are not normal for that entity. In any resource that is faulty, the Cisco 6100 Series system changes its Operational State to Disabled and its Service State to Out of Service. The Service State of all resources dependent on the faulty entity are also set to Out of Service. That is, all ports on a module that has been set to Out of Service are also set to Out of Service.
Alarms showing that a fault of some sort has occurred in a Cisco 6100 Series system entity are reported by the Cisco 6100 Series system.
ViewRunner for HP OpenView receives traps from the Cisco 6100 Series system and reports them in various Event Categories windows. ViewRunner checks the trap sequence number to ensure that traps aren't missed, duplicated, or received out of order. It can synchronize with the current alarm tables on the Cisco 6100 Series system if a trap is missed. Therefore, ViewRunner can always display the correct view of a Cisco 6100 Series system alarm state.
Event or alarm displays are kept current through the following methods:
ViewRunner for HP OpenView does not currently use the Cisco 6100 Series system event log to capture information like the ViewRunner for Windows does. The event or alarm information is cached in the Oracle database.
Alarm synchronization is the process of synchronizing ViewRunner client GUIs and the Oracle alarm database with the Cisco 6100 Series system slot, module, port, and image alarm states. A full alarm synchronization updates all Cisco 6100 Series system alarm states, and a module alarm synchronization updates Cisco 6100 Series system alarm states for a specific module and its ports.
Alarm synchronization is needed to guarantee that all ViewRunner client dialog boxes display
the correct alarm state information. The following client dialog boxes are updated with an
alarm synchronization:
ViewRunner gets out of synchronization with a Cisco 6100 Series system alarm state whenever traps are not received. This can happen when
A full alarm synchronization is invoked automatically whenever the following conditions exist:
A module alarm synchronization is invoked automatically whenever the following conditions exist:
A full alarm synchronization can be manually invoked through menu options, a toolbar icon, or command line invocation.
If View Alarm Formatter discovers that it has missed a trap, it invokes a configuration synchronization. This might result in a lockout of user actions, as discussed in "Configuration Synchronization."
There is minimal impact on you because alarm synchronizations are brief and do not lock out user actions. Alarm synchronizations take place in just a matter of seconds.
When an alarm out-of-sync message is detected, ViewRunner regenerates the missed trap and forwards it to the Error Event Browser dialog box. The event message then is appended with "(Discovered by ViewRunner)" to indicate that a trap was missed. ViewRunner displays the correct node status on all client GUIs.
ViewRunner for HP OpenView uses color in ViewMap to indicate the alarm status of a location or a wire center. The Location or Wire Center symbol displays the color of the most critical alarm on any of the entities (module, slot, port, or image) in that location or on that node. Figure 12-1 shows an example of these icons.
ViewRunner also uses color in the Chassis View to indicate the most critical alarm for a particular module. The ejector tab on the module in any chassis is the color of the most critical alarm on that module. In addition, the toolbar of the Chassis View, provides a count of all current alarms of critical, major, or minor severity, as shown in Figure 12-2. The color next to the alarm count indicates the severity (red = critical, orange = major, and yellow = minor).
ViewRunner also reports alarms in various event category dialog boxes, the Current Alarm
dialog box, and in the module or port properties dialog boxes. This is discussed in detail in the following sections.
ViewRunner maps utilize the default states and colors defined by HP OpenView. The status color displayed is dependent on the symbol prioritization order of evaluating states. In the HP OpenView paradigm, the display of Administrative State colors overrides the display of Operational State colors. That is, an unmanaged administrative state overrides a critical operational alarm. See "Use of Color in ViewRunner," for more information.
A window that appears when you open ViewRunner is the Event Categories window. It contains a list of the types of events that can be viewed. Each type of event has a box in front of it that displays the color of the highest level alarm asserted for that list of events or alarms.
The recovery from lost traps does not require automatic polling. It is performed when either an alarm or a configuration synchronization is invoked or when a trap is received. The alarm and configuration synchronizations can be configured to occur automatically.
The status colors for the icons on ViewMap are updated as new traps are received and when ViewRunner for HP OpenView periodically polls the Cisco 6100 Series systems to examine the highest outstanding alarm against the equipment. The default polling interval is 20 minutes.
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 12-1.
| 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. See the Cisco 6100 Series Alarm Summary Guide for more information and for exceptions to this definition. |
The contents of the ViewRunner Error Events Browser can be sorted by any one of the columns in Table 12-1 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 12-5 is an example of the Current Alarms dialog box.
The columns in the Current Alarms dialog box are described in Table 12-2.
| 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. See the Cisco 6100 Series Alarm Summary Guide for more information and for exceptions to this definition. |
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 "Command Line Interface" section.
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.
There are four types of events generated by the Cisco 6100 Series system and viewed in ViewRunner for HP OpenView.
The following sections describe the guidelines for each type of event.
The following are guidelines used to distinguish information events from other events:
An exception to the above guidelines is as follows.
Alarm event severity is based on guidelines set forth in TR-NWT-000057, Functional Criteria for DLC Systems. The guidelines are as follows:
Normally, an alarm event causes a service impairment or a service outage. However, some alarm events do not affect service. A service impairment typically results in a loss of end-to-end traffic for some number of subscriber connections (one to several) for a brief period of time (milliseconds to seconds, but normally less than one minute unless repeat occurrences are encountered). A service outage is the absolute loss of the ability to connect one or more subscribers.
In the ViewRunner Error Event Browser dialog box, alarm events are followed by an additional event showing a Cleared event status, which means the alarm event is corrected.
The following are guidelines used to distinguish minor alarm events from other events:
This guideline is used to distinguish major alarm events from other events. Service outage severities are coded as either a major alarm event or a critical alarm event, depending on the number of subscribers affected. If 24 to 127 subscribers are out of service, the event is a major alarm event.
This guideline is used to distinguish critical alarm events from other events. Service outage severities are coded as either a major alarm event or a critical alarm event, depending on the number of subscribers affected. If more than 128 or more subscribers are out of service, the event is a critical alarm event.
Alarm events that have been asserted by the Cisco 6100 Series system are followed by:
For example, you can clear some alarm events if the problem is caused by congestion or a single parity error. At other times, you must reset or reinsert the module generating the alarm event. In this case, the only event returned is the Event 128, "Module was detected," which clears whatever outstanding alarm events were asserted against that module.
ViewRunner for HP OpenView 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 using the Command Line Interface, in the Error Events Browser, or in the Current Alarms dialog box. Only the Cisco 6130 system supports a fan tray at the time of this Release.
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 for the Cisco 6100 Series Chassis. (See "Cisco 6100 Series Chassis View Colors" section for more information.)
The first alarm, MC Fan Failure, occurs when you have checked the Fan Tray Present toggle on the 6100 Properties dialog box (see Figure 12-6), 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.
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 12-7 is an ATU-C Module Properties dialog box showing an ATU-C module alarm
bell icon.
Posted: Fri Oct 8 16:06:16 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.