Troubleshooting Checklist
4.2TROUBLESHOOTING CHECKLIST
If the module is not working properly, refer to Table
Table 4-2 Troubleshooting Checklist
Problem | Possible Cause | Recommended Action | |
|
|
| |
All LEDs are | Loss of power. | Ensure that the module was installed | |
OFF. |
| properly according to the installation | |
|
| instructions in Chapter 3, and that the host | |
|
| chassis is powered properly. | |
|
|
| |
No Local | Autobaud is enabled, but | Press ENTER (RETURN) (may take up to | |
Management | the baud rate has not yet | four times). | |
Password | been detected. |
| |
screen. |
|
| |
Incorrect terminal setup. | Refer to the appropriate Local Management | ||
| |||
|
| User’s Guide for proper setup procedures. | |
|
|
| |
| Improper console cable | Refer to Appendix A for proper COM port | |
| pinouts. | pinouts. | |
|
|
| |
| Corrupt firmware image, or | If possible, attempt to download the image to | |
| hardware fault. | the module again. Refer to Section B.2 for | |
|
| instructions to clear NVRAM. | |
|
|
| |
Cannot navigate | Improper Community | 1. Refer to the appropriate Local | |
beyond Password | Names Table. | Management User’s Guide for the | |
screen. |
| Community Names Table setup. | |
|
| 2. If the Community Names have been | |
|
| forgotten, refer to Section B.2 for | |
|
| instructions on how to set the mode switch | |
|
| to reset the Community Names to their | |
|
| default values. | |
|
|
|
Troubleshooting
