|
|
This chapter explains how to diagnose and handle subtend host module (STM) events 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.
Table 13-1 lists STM events and their IDs, definition, severity, and description. A detailed explanation of these events and corrective actions required (if any) is located in subsections in this chapter.
| ID | Definition | Severity | Description |
|---|---|---|---|
128 | LR_CREATE_OBJ | Info | Module was detected |
129 | LR_PING_FAIL | Critical | Module did not respond to the system monitor |
42 | FC_SUBTEND_PORT_BUFFER_OVERFLOW | Info | Buffer overflow in the cell buffer on the subtend module |
43 | FC_SUBTEND_PORT_UTOPIA_ERROR | Info | Error in UTOPIA chip |
44 | FC_SUBTEND_PORT_INGRESS_HEC | Info | Subtend port ingress HEC error |
| 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 the 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 (SC) 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 SC 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 SC 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:
Step 1 Remove and reinsert the module. This forces a module to reset if neither the module nor the SC module could force a reset. A module reset usually clears all alarm conditions.
Step 2 Observe the SC 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 |
|---|---|---|
42 | FC_SUBTEND_PORT_BUFFER_OVERFLOW | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Buffer overflow in the cell buffer on the subtend moduleAn alarm event of this type is likely the result in 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 ATM switch module (ASM).
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 1 If a Cleared event status is not received within 1 minute, reinsert the module.
Step 2 If a problem persists, replace the module.
| ID | Event Name | Severity |
|---|---|---|
43 | FC_SUBTEND_PORT_UTOPIA_ERROR | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Error in UTOPIA chipAn alarm event of this type is likely the result in 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 ATM switch module (ASM).
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.
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 |
|---|---|---|
44 | FC_SUBTEND_PORT_INGRESS_HEC | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Subtend port ingress HEC errorAn alarm event of this type is likely the result in 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 ATM switch module (ASM).
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.
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.
Posted: Tue Nov 16 15:42:22 PST 1999
Copyright 1989-1999©Cisco Systems Inc.