|
|
This chapter explains how to diagnose and handle ATU-C 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 2-1 lists ATU-C 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 | SAC_SOFTWARE_FAILED_CRC | Major | Software failed CRC check during download |
3 | SAC_OUT_OF_MEMORY | Critical | Application was unable to allocate memory |
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module did not respond to system monitor |
|
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 | SAC_SOFTWARE_FAILED_CRC | Major |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Software failed CRC check during downloadEvents of this type are not run-time events. They occur only during module power up and self-test, and they do not affect service (because subscriber service is typically not active yet). The module fails self-test as a result of this event, and immediately retries the self-test, but no self-test will end in success. A failure message is generated with each failure. Without a successful self-test, the module cannot be put into service, so the node does not complete its installation cycle.
Software update events fall into this description, because it is assumed that the updates are always monitored by an operator. Consequently, the events need not be coded as critical. In any case, the goal is to monitor the node status until the node becomes fully operational.
Alarm events of this type are generated only during module initialization and automatically force a module reset.
Step 2 If a problem persists, replace the module.
| ID | Event Name | Severity |
|---|---|---|
3 | SAC_OUT_OF_MEMORY | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Application was unable to allocate memoryEvents of this type are normally coded as minor, but are currently are maintained as critical. This is done to preserve the node software's requirement to decouple event severity from service state impact.
In some cases, a module forces itself into a self-test based on the alarm condition. In other cases, the system controller module forces the alarmed module to reset. A module reset forces the module to be power cycled, self-tested, and reconfigured into the slot by the system controller module.
Several alarm event conditions are cleared by a module reset. Look for the alarm event to clear within 1 minute. An alarm event is cleared when the system controller module faceplate ALARM LED changes from red to off.
In the ViewRunner management software, two actions show that an alarm event is cleared:
If the alarm event does not clear, complete the following steps:
Step 2 Observe the system controller module ALARM LED or the ViewRunner ejector tabs to see if the alarm condition returns. If the previous problem persists, the condition will probably reoccur within 1 minute.
Step 3 If the alarm condition persists, replace the module.
| ID | Event Name | Severity |
|---|---|---|
128 | LR_CREATE_OBJ | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Module was detectedEvents of this type do not indicate service impairment or loss.
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 |
|---|---|---|
129 | LR_PING_FAIL | Critical |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Module did not respond to system monitorEvents of this type are normally coded as minor, but are currently are maintained as critical. This is done to preserve the node software's requirement to decouple event severity from service state impact.
In some cases, a module forces itself into a self-test based on the alarm condition. In other cases, the system controller module forces the alarmed module to reset. A module reset forces the module to be power cycled, self-tested, and reconfigured into the slot by the system controller module.
Several alarm event conditions are cleared by a module reset. Look for the alarm event to clear within 1 minute. An alarm event is cleared when the system controller module faceplate ALARM LED changes from red to off.
In the ViewRunner management software, two actions show that an alarm event is cleared:
If the alarm event does not clear, complete the following steps:
Step 2 Observe the system controller module ALARM LED or the ViewRunner ejector tabs to see if the alarm condition returns. If the previous problem persists, the condition will probably reoccur within 1 minute.
Step 3 If the alarm condition persists, replace the module.
Posted: Wed May 10 13:28:19 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.