|
|
This chapter explains how to diagnose and handle system controller module events that are generated by the Cisco 6100 Series system. The following information is presented for each of the events:
If none of the actions presented for the event are successful, contact the Cisco Technical Assistance Center (TAC) for additional support.
 |
Note Refer to the ViewRunner for Windows User Guide or the ViewRunner for HP OpenView User Guide for detailed information on viewing events in the ViewRunner management software. Refer to "Event Guidelines and Definitions" for detailed information on event severity guidelines and alarm event status changes. |
Table 5-1 lists system controller module events and their IDs, definition, severity, and description. A detailed explanation of these events and the corrective actions that are required (if any) is located in this chapter.
| ID | Definition | Severity | Description |
|---|---|---|---|
2 | SC_IP_MISMATCH | Minor | The IP number assigned to the Cisco 6100 Series system is unusable |
3 | SC_SUBNET_ERROR | Minor | The subnet mask is incorrect |
4 | SC_DOWNLOAD_DONE | Info | Download to the system controller module is complete |
127 | --- | Critical | Loss of communication with system controller module |
|
Note Events with an ID less than 128 are specific to the module in alarm. Events with an ID value greater than or equal to 128 are system-wide events. |
| ID | Event Name | Severity |
|---|---|---|
2 | SC_IP_MISMATCH | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
The IP number assigned to the Cisco 6100 Series is unusableEvents of this type are not run-time events. They occur only during node installation or configuration and affect only the node's ability to communicate properly over Ethernet.
Complete the following steps to clear the alarm event:
Step 2 Verify that the ViewRunner can access the node correctly.
| ID | Event Name | Severity |
|---|---|---|
3 | SC_SUBNET_ERROR | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
The subnet mask is incorrectEvents of this type are not run-time events. They occur only during node installation or configuration and affect only the node's ability to communicate properly over Ethernet.
Complete the following steps to clear the alarm event:
Step 2 Verify that the ViewRunner can access the node correctly.
| ID | Event Name | Severity |
|---|---|---|
4 | SC_DOWNLOAD_DONE | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Download to the system controller module is completeEvents of this type are not run-time events. They occur only during node installation or configuration and affect only the node's ability to communicate properly over Ethernet.
This is an information event, not an alarm event. Information events do not represent a state change and therefore are not followed by a Cleared event.
Information events are typically one-time occurrences that are corrected by the module without a reset. They do not cause service degradation.
No craft action is required.
| ID | Event Name | Severity |
|---|---|---|
127 | --- | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Loss of communication with system controller moduleAn alarm event of this type will likely result in the loss of a single cell. Loss of a single cell is a transient event, affecting only one subscriber. Recovery is possible at higher layers in the protocol stack. Multiple occurrences of the alarm event are more serious and typically indicate the failure of a hardware component on the network interface module.
The term multiple occurrences is applied if several occurrences take place within a few seconds. If a problem with cell loss, and ultimately subscriber traffic throughout is suspected, service personnel should review the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser for multiple occurrences. In a future software release, multiple occurrences of events in this category will generate a higher severity alarm.
Alarm events of this type are typically caused by short-term (milliseconds in duration) incidents that clear as part of the normal course of traffic management. Examples of traffic management events include the freeing of buffer space, recovery from parity errors at a higher level, and recover after a brief loss of signal.
Each of these alarm events is followed by an additional event showing a Cleared event status, meaning the alarm event has been corrected.
Step 2 If a problem persists, replace the module.
Posted: Wed May 10 13:35:14 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.