Table of Contents
Advertisement
Troubleshooting Checklist
Troubleshooting Checklist
If the device is not working properly, refer to Table
possible causes, and recommended actions to resolve the problem.
Table 4-2 Troubleshooting Checklist
Problem
All LEDs are OFF.
All LEDs are OFF
No local
management
startup screen.
Cannot navigate
beyond startup
screen.
4-6 Troubleshooting
Possible Cause
Loss of power.
Possible mismatch in code
between the master and the
device. If the switch does not
have the same code as the
stack master the switch will not
join the stack and all LEDs will
remain off.
Incorrect terminal setup.
Improper Console cable
pinouts.
Corrupt firmware image, or
hardware fault.
Improper Community Names
Table.
4‐2 for a checklist of problems,
Recommended Action
Ensure that the SecureStack A2 was
installed properly according to the
installation instructions in
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.
Connect to the console port and type
"show switch". If a code mismatch is the
cause, the output of the above command
will show "code version mismatch".
Disconnect the switch from the stack and
load the necessary code to match the
stack master.
Refer to the SecureStack A2
Configuration Guide for proper setup
procedures.
Refer to
Appendix A
for proper Console
port pinouts.
If possible, attempt to download the image
to the device again. Refer to the
SecureStack A2 Configuration Guide for
details.
Refer to the SecureStack A2
Configuration Guide for the Community
Names Table setup.
Chapter
3.
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
