|
|
This chapter describes the various ways that you can view events in ViewRunner, presents the event severity guidelines and alarm and event status changes, and includes examples of module alarm events that are associated with Cisco 6100 Series systems.
This chapter includes the following sections:
On the ViewRunner graphical user interface (GUI), you can view events that the Cisco 6100 Series system generates by using the methods described in the following sections:
In ViewRunner, use the Event History dialog box to show all of the events that were asserted and cleared for a particular Cisco 6100 Series system.
During each session ViewRunner software polls the node for new events at 15-second intervals. This interval is the default setting. You can change this polling interval by following these steps:
The ViewRunner Preferences dialog box opens, shown in Figure 9-1.
Step 2 Increase or decrease the polling interval on the ViewRunner Preferences dialog box by using the up and down arrows in the Alarms and Events group box polling field.
The range is 15 to 120 seconds.
 |
Note ViewRunner displays in the Event History only the events that are asserted by the Cisco 6100 Series system or that ViewRunner generates. It does not report events from other network elements in the end-to-end ATM connection. |
ViewRunner can save more than 200 events at a time. If, for example, the Cisco 6100 Series node event queue shows events 101 through 300, 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.)
If ViewRunner detects a system controller module reset during an active session, ViewRunner removes all displayed events from the Event History dialog box and displays only those events that occur after the reset. After a system controller reset, the Cisco 6100 Series system node loses event history and begins numbering again at 1.
Figure 9-2 shows an example of the ViewRunner Event History dialog box.
|
Note After you open the Event History dialog box, you cannot close it. (Notice that the x in the upper right corner of the dialog box is dimmed). You can, however, minimize the dialog box by clicking the - icon in the upper right corner. |
Logical service-oriented navigation is available in the Event History dialog box. Click the blue, underlined text, and ViewRunner takes you to the Module Properties dialog box of the chassis, slot, and port from which the event was asserted.
The columns in the Event History dialog box are described in Table 9-1.
| Column | Description | ||
|---|---|---|---|
Sequence Id | Displays the sequence number of the event in the ViewRunner Event History dialog box for this session. This column also contains an alarm icon in which the color indicates the severity of the event as follows:
| ||
Severity | Displays the severity level of the event. Event severities are classified as follows:
Normally, an alarm event causes a service impairment or a service outage. However, some alarm events cause no effect to 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. | ||
Log Time | Identifies the date and time when the event occurred. | ||
Entity | The module against which the event is asserted. You can use the information in this field to help locate the event in the Cisco 6100 Series with NI-1 Alarm Summary Guide. The entity can be any one of the following items:
| ||
AID2 | Corresponds to the chassis and slot number that are 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 entity that you later delete asserts an event. ViewRunner also displays Unknown in the AID field if you add an entity that ViewRunner has not yet discovered at the time the event was generated. To go directly to the entity and slot location in which the event is received, click the underlined text in this field. | ||
Status | Displays the current status of the event, which can be one of the following types:
| ||
Description | Briefly describes the event. This field corresponds to one of the descriptions that are listed in the system event definitions tables in the Cisco 6100 Series with NI-1 Alarm Summary Guide. This description is a predefined string based on the entity and event code from the node. |
| 1LIM = line interface module 2AID = access identifier |
To sort the contents of the ViewRunner Event History dialog box according to any one of the fields in Table 9-1, go through the following steps:
Step 2 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 more entries can fit in the dialog box, a scroll bar appears, allowing you to scroll through the entries.
To remove events from the display, go though the following steps:
To choose an event, click the Sequence Id number of each row (see Figure 9-3). Use the Shift or Ctrl key to choose multiple events.
Step 2 To remove an event, highlight it, and then click the X icon (Remove events from view icon) on the toolbar.
If you remove an event from the Event History dialog box, it still remains in the Cisco 6100 Series system. The event that you remove is removed only from the Event History dialog box display.
The Current Alarms dialog box lists all of the currently asserted alarm events in the system, including module, slot, and image alarm events. The dialog box format is similar to that of the Event History dialog box. Figure 9-4 shows an example of the Current Alarms dialog box.
You can retrieve and display current alarm events either when you first open the dialog box or after you refresh the screen. To retrieve the most current alarm events, you can set a smaller polling interval in the ViewRunner Preferences dialog box. Go through these steps:
|
Note You can update the Current Alarms dialog box yourself by clicking the red, circular Discover icon in the far left corner of the Current Alarms dialog box toolbar. |
Step 2 In the Current Alarms dialog box, click the blue underlined text to navigate to the Module Properties dialog box of the chassis, slot, and port from which the alarm event was asserted.
|
Note After you open the Current Alarms dialog box, you cannot close it. (Notice that the x in the upper right corner of the dialog box is dimmed.) You can, however, minimize the dialog box by clicking the - icon in the upper right corner. |
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, see the "Using the Command Line Interface" section, and also refer to the ViewRunner for Windows Installation and Administration Guide.
The following examples of CLI commands display 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
|
Note If you are running ViewRunner for Windows Release 2.0, the valid command is show alarms with all of its options. |
|
Note For more information on events and alarm events, including descriptions of all Cisco 6100 Series system alarm events and corrective actions, refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide. |
The Cisco 6100 Series system generates the following types of events, which you can view on the ViewRunner GUI:
The following sections describe the criteria for each of these event types.
The following criteria apply to information events:
Alarm severity is based on criteria set forth in TR-NWT-000057, Functional Criteria for DLC Systems. These criteria are as follows:
Normally, an alarm event causes a service impairment or a service outage. However, some alarm events cause no effect to 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 Event History dialog box, alarm events are followed by an additional event showing a Cleared event status, which means the alarm event is corrected.
Table 9-1 describes the criteria for the three types of alarm events.
| Alarm Type | Criteria |
|---|---|
Critical | Service outage severities are coded as either a major alarm event or a critical alarm event, depending on the number of subscribers that are affected. If more than four subscribers are out of service, the event is a critical alarm event. |
Major | Service outage severities are coded as either a major alarm event or a critical alarm event, depending on the number of subscribers that are affected. If four or fewer subscribers are out of service, the event is a major alarm event. |
Minor | The following guidelines distinguish minor alarm events:
|
Alarm events that the Cisco 6100 Series system asserts result in the following actions:
1. A cleared event
2. An information event---In effect, clears all alarm events associated with a particular entity at a particular slot
You can clear some alarm events if congestion or a single parity error caused the problem. At other times, you must reset or reinsert the module that generated the alarm event. In this case, the only event returned is Event 128, "Module was detected," which clears whatever outstanding alarm events were asserted against that module.
ViewRunner for Windows Release 3.0.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 dialog box or in the Current Alarms dialog box. The Cisco 6100 Series system supports a fan tray if you use flexi ATU-C (CAP or DMT) or DMT-2 ATU-C modules.
|
Note References here to modules or to CAP ATU-C modules include all modules supported by the Cisco 6100 Series system (CAP ATU-C, STU-C, and DMT-2 ATU-C modules). |
The first alarm, Fan Failure, occurs when you have clicked the Fan Tray Present checkbox on the 6100 Properties dialog box, shown in Figure 9-6, but a fan tray is not present.
The second alarm, Fan Required, occurs when you have configured a module that requires a fan tray, such as the DMT-2 ATU-C module, and the software cannot detect a fan tray. In this case, the DMT-2 ATU-C module detrains and issues a corresponding critical module alarm.
You can open the appropriate Module Properties dialog box for the alarm in one of three ways:
Figure 9-7 shows the Subtend Host Module Properties dialog box Port Status tab showing an alarm.
Figure 9-8 shows the Network Interface Module Properties dialog box Status tab with an alarm.
|
Note For more information on events and alarm events, including descriptions of all Cisco 6100 Series system alarm events and corrective actions, refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide. |
Posted: Mon Feb 14 16:36:30 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.