Brocade Communications Systems Brocate Ethernet Access Switch 6910 - Manual (Page 1161)

Brocade 6910 Ethernet Access Switch Configuration Guide 1111
53-1002581-01
Appendix
A
Troubleshooting
In this chapter
• Problems Accessing the Management Interface. . . . . . . . . . . . . . . . . . . 1111
• Using System Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
Problems Accessing the Management Interface
TABLE 185 Troubleshooting Chart
Symptom Action
Cannot connect using
Telnet, web browser, or
SNMP software
•
Be sure the switch is powered on.
•
Check network cabling between the management station and the switch. Make
sure the ends are properly connected and there is no damage to the cable. Test
the cable if necessary.
•
Check that you have a valid network connection to the switch and that the port
you are using has not been disabled.
•
Be sure you have configured the VLAN interface through which the management
station is connected with a valid IP address, subnet mask and default gateway.
•
Be sure the management station has an IP address in the same subnet as the
switch’s IP interface to which it is connected.
•
If you are trying to connect to the switch via the IP address for a tagged VLAN
group, your management station, and the ports connecting intermediate switches
in the network, must be configured with the appropriate tag.
•
If you cannot connect using Telnet, you may have exceeded the maximum number
of concurrent Telnet/SSH sessions permitted. Try connecting again at a later
time.
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 both an RSA and DSA public key on the switch,
exported this key to the SSH client, and enabled SSH service. Try using another
SSH client or check for updates to your SSH client application.
•
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).