|
|
This chapter explains how to diagnose and handle slot 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 16-1 lists slot 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 |
|---|---|---|---|
1 | SLOT_MISMATCH_EVENT | Minor | A module was inserted in the slot that did not match the type that was pre-provisioned for that slot |
2 | SLOT_INVALID_EVENT | Minor | A module that was not valid for the slot was inserted in the slot |
3 | SLOT_NO_IMAGE_EVENT | Minor | No image exists for the type module present in the slot |
4 | SLOT_IMAGE_NOT_READY | Minor | Image for download is not ready |
5 | SLOT_DOWNLOAD_START | Info | Download for module in slot is underway |
6 | SLOT_DOWNLOAD_COMP | Info | Download for module in slot is complete |
7 | SLOT_DOWNLOAD_FAIL | Info | Image download failed for module in slot |
8 | SLOT_CURR_IMG_FAIL | Minor | Image could not be obtained for module in slot |
9 | SLOT_INVALID_XTUC_TYPE | Minor | The line encoding for the physical pool does not match the modem card |
|
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 |
|---|---|---|
1 | SLOT_MISMATCH_EVENT | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
A module was inserted in the slot that did not match the type that was pre-provisioned for the slotEvents 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.
Preprovisioning may have been performed on this slot during system configuration (after the system controller module was installed). Preprovisioning implies that a slot was configured for a given module type, and the system controller module has detected that a module of a different type is physically inserted in this slot.
Check ViewRunner information on the slot. Either replace the module of the incorrect type with a module of the preprovisioned type, or delete the module configuration for the slot.
| ID | Event Name | Severity |
|---|---|---|
2 | SLOT_INVALID_EVENT | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
A module that was not valid for the slot was inserted in the slotEvents 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.
Complete the following steps to clear the alarm event:
Step 2 Remove the inappropriate module and use the ViewRunner software to delete the configuration.
| ID | Event Name | Severity |
|---|---|---|
3 | SLOT_NO_IMAGE_EVENT | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
No image exists for the type module present in the slotEvents 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.
Preprovisioning may have been performed on this slot during system configuration (after the system controller module was installed). Preprovisioning implies that a slot was configured for a given module type, and the system controller module has detected that a module of a different type is physically inserted in this slot.
Check ViewRunner information on the slot. Either replace the module of the incorrect type with a module of the preprovisioned type, or delete the module configuration for the slot.
If the system controller module NVRAM is cleared from the command line interface, all of the modules, except for the system controller module, will report this event. Proceed with the software upgrade using the same Cisco 6100 Series software revision to clear the message.
| ID | Event Name | Severity |
|---|---|---|
4 | SLOT_IMAGE_NOT_READY | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Image for download is not readyEvents 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.
Preprovisioning may have been performed on this slot during system configuration (after the system controller module was installed). Preprovisioning implies that a slot was configured for a given module type, and the system controller module has detected that a module of a different type is physically inserted in this slot.
Check ViewRunner information on the slot. Either replace the module of the incorrect type with a module of the preprovisioned type, or delete the module configuration for the slot.
| ID | Event Name | Severity |
|---|---|---|
5 | SLOT_DOWNLOAD_START | 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 for module in slot is underwayEvents 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).
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.
The system controller module has detected that a module does not have the correct software revision. The updated image that is stored in the system controller module will be downloaded to the module. No action is required.
| ID | Event Name | Severity |
|---|---|---|
6 | SLOT_DOWNLOAD_COMP | 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 for module in slot is completeEvents 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).
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.
The system controller module has completed the image download to the module. With a successful image download, the module can be put into service. No action is required.
| ID | Event Name | Severity |
|---|---|---|
7 | SLOT_DOWNLOAD_FAIL | Info |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Image download failed for module in slotEvents 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).
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.
Complete the following steps to clear the alarm event:
Step 2 Reseat the module.
Step 3 If the problem persists, replace the module or delete the module configuration for the slot.
| ID | Event Name | Severity |
|---|---|---|
8 | SLOT_CURR_IMG_FAIL | Minor |
The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:
Image could not be obtained for module in slotEvents 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).
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.
Preprovisioning may have been performed on this slot during system configuration (after the system controller module was installed). Preprovisioning implies that a slot was configured for a given module type, and the system controller module has detected that a module of a different type is physically inserted in this slot.
Check ViewRunner information on the slot. Either replace the module of the incorrect type with a module of the preprovisioned type, or delete the module configuration for the slot.
You may be running an older Cisco 6100 Series code release that does not support the new module. If you are using DMT-2 ATU-C or STU-C modules with a Cisco 6100 Release 2.2.x code and earlier, upgrade the Cisco 6100 Series system code to the current release.
| ID | Event Name | Severity |
|---|---|---|
9 | SLOT_INVALID_XTUC_TYPE | 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 line encoding for the physical pool does not match the modem cardThe modem inserted in the slot is invalid for the physical pool because of invalid modem encoding.
Insert the modem in the physical pool that is set for that type of modem encoding.
Posted: Wed May 10 13:46:50 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.