Owner's manual

System Troubleshooting
1-3
Table 1.2 provides suggestions to troubleshoot this issue.
1.1.4 Switch is Stuck in a Booting Loop
The WS5000 Series Switch continuously boots and does not change context to a user name prompt. Table 1.3
provides suggestions to troubleshoot this issue.
1.1.5 Unable to Telnet into the Switch
The WS5000 Series Switch is physically connected to the network, but telneting into the switch does not work.
Table 1.4 provides suggestions to troubleshoot this issue.
Table 1.2 Switch Does Not Obtain an IP Address through DHCP Troubleshooting Notes
Possible Issue Suggestions to Correct
DHCP is not configured, or
not available on same
network as the WS5000
Series Switch
• Verify that the configuration for the switch has DHCP enabled. By default, Ethernet
NIC 2 is DHCP enabled. Otherwise, use set dhcp enable command at the Ethernet
NIC 2 Instance prompt (
WS5000.(Cfg).Ethernet.[2]> set dhcp enable).
• Ensure that the WS5000 is on the same network as the DHCP server and verify the
server is providing DHCP services.
• Connect another host configured for DHCP and verify it is getting a DHCP address
DHCP is not enabled on
NIC 2 (that is, the Ethernet
port that is not managing
the RF network)
• Enable DHCP, use the CLI command or the GUI to enable DHCP on the Ethernet port
not managing the RF network (NIC 2)
• Verify that DHCP packets are being sent to NIC 2 using a sniffer tool
• If DHCP packets are seen, check to ensure that the switch is not configured for a
static IP on NIC 2.
All else.. Contact Symbol Support.
Table 1.3 Switch is Stuck in a Booting Loop Troubleshooting Notes
Possible Issue Suggestions to Correct
Bad DOM (disk on memory)
module
Remove the DOM (disk on memory) and install it in a different switch.
DOM/switch not getting
enough ventilation
Verify that the CPU fan is operating properly.
All else... Contact the Symbol Support.
Table 1.4 Unable to Telnet into the Switch Troubleshooting Notes
Possible Issue Suggestions to Correct
Console is not on network • Check all cabling and terminal emulation program settings to be sure they are
correctly set. See Console Port is Not Responding issue, or the WS5000 Series
Wireless Switch System Reference Guide for more details.
• From a another system on the same network. attempt to ping the switch.
Telnet is not enabled
and/or SSH is disabled
Verify that Telnet is enabled and SSH is disabled by using the CLI or GUI (By default,
telnet is disabled.).
Use the show telnet command at the WS5000> prompt.