SMC Networks SMC TigerStack III SMC6824MPE - Manual (Page 554)

T
ROUBLESHOOTING
B-2
Using System Logs
If a fault does occur, refer to the Installation Guide to ensure that the
problem you encountered is actually caused by the switch. If the problem
appears to be caused by the switch, follow these steps:
1. Enable logging.
2. Set the error messages reported to include all categories.
3. Designate the SNMP host that is to receive the error messages.
4. Repeat the sequence of commands or other actions that lead up to the
error.
5. Make a list of the commands or circumstances that led to the fault.
Also make a list of any error messages displayed.
Cannot connect using
Secure Shell
• If you cannot connect using SSH, you may have exceeded the
maximum number of concurrent Telnet/SSH sessions permitted.
Try connecting again at a later time.
• Be sure the control parameters for the SSH server are properly
configured on the switch, and that the SSH client software is
properly configured on the management station.
• Be sure you have generated a public key on the switch, and
exported this key to the SSH client.
• Be sure you have set up an account on the switch for each SSH
user, including user name, authentication level, and password.
• Be sure you have imported the client’s public key to the switch (if
public key authentication is used).
Cannot access the
on-board
configuration
program via a serial
port connection
• Be sure you have set the terminal emulator program to VT100
compatible, 8 data bits, 1 stop bit, no parity, and the baud rate set
to any of the following (9600, 19200, 38400, 57600, 115200 bps).
• Check that the null-modem serial cable conforms to the pin-out
connections provided in the Installation Guide.
Forgot or lost the
password
• Contact SMC Technical Support for help.
Table B-1 Troubleshooting Chart
Symptom Action