|
|
This chapter explains how to diagnose and handle slot 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 18-1 lists slot 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 |
|---|---|---|---|
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 |
| 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 [SC] module was installed). Preprovisioning implies that a slot was configured for a given module type, and the SC 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.
Step 1 The configuration style being used in this node (DOH or Direct Connect) does not require that a module of this type be inserted in this slot. Refer to the Cisco 6100 Series User Guide for more information on configuration styles.
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 [SC] module was installed). Preprovisioning implies that a slot was configured for a given module type, and the SC 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 SC module NVRAM is cleared from the command line interface, all of the modules, except for the SC 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 [SC] module was installed). Preprovisioning implies that a slot was configured for a given module type, and the SC 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 (SC) module has detected that a module does not have the correct software revision. The updated image that is stored in the SC 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 (SC) 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.
Step 1 Check ViewRunner information on the slot.
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 [SC] module was installed). Preprovisioning implies that a slot was configured for a given module type, and the SC 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.
Posted: Tue Nov 16 15:46:50 PST 1999
Copyright 1989-1999©Cisco Systems Inc.