Filter
Top Products
Troubleshooting Checklist
4-6 Troubleshooting
Troubleshooting Checklist
Ifthedeviceisnotworkingproperly,refertoTable4‐2forachecklistofproblems,
possiblecauses,andrecommendedactionstoresolvetheproblem.
Table 4-2 Troubleshooting Checklist
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
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.
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.
No local
management
startup screen.
Incorrect terminal setup. Refer to the SecureStack A2
Configuration Guide for proper setup
procedures.
Improper Console cable
pinouts.
Refer to Appendix A for proper Console
port pinouts.
Corrupt firmware image, or
hardware fault.
If possible, attempt to download the image
to the device again. Refer to the
SecureStack A2 Configuration Guide for
details.
Cannot navigate
beyond startup
screen.
Improper Community Names
Tabl e.
Refer to the SecureStack A2
Configuration Guide for the Community
Names Table setup.