Troubleshooting Checklist
Troubleshooting Checklist
If the device is not working properly, refer to Table 4‐2 for a checklist of problems, possible causes, and recommended actions to resolve the problem.
Table
Problem | Possible Cause | Recommended Action |
|
|
|
All LEDs are OFF. | Loss of power. | Ensure that the SecureStack A2 was |
|
| installed properly according to the |
|
| installation instructions in Chapter 3. |
|
| Ensure that the power cords are |
|
| connected properly to an active power |
|
| source that meets the AC input |
|
| specifications for this switch. |
|
| Ensure that the AC power cord is not |
|
| damaged. Replace the power cord with a |
|
| known good one. |
|
|
|
All LEDs are OFF | Possible mismatch in code | Connect to the console port and type |
| between the master and the | “show switch”. If a code mismatch is the |
| device. If the switch does not | cause, the output of the above command |
| have the same code as the | will show “code version mismatch”. |
| stack master the switch will not | Disconnect the switch from the stack and |
| join the stack and all LEDs will | |
| load the necessary code to match the | |
| remain off. | |
| stack master. | |
|
| |
|
|
|
No local | Incorrect terminal setup. | Refer to the SecureStack A2 |
management |
| Configuration Guide for proper setup |
startup screen. |
| procedures. |
|
|
|
| Improper Console cable | Refer to Appendix A for proper Console |
| pinouts. | port pinouts. |
|
|
|
| Corrupt firmware image, or | If possible, attempt to download the image |
| hardware fault. | to the device again. Refer to the |
|
| SecureStack A2 Configuration Guide for |
|
| details. |
|
|
|
Cannot navigate | Improper Community Names | Refer to the SecureStack A2 |
beyond startup | Table. | Configuration Guide for the Community |
screen. |
| Names Table setup. |
