Switch Takes A Long Time To Start Up; Switch Does Not Obtain An Ip Address Through Dhcp; Switch Is Stuck In A Booting Loop - Motorola WS5100 Series Troubleshooting Manual

1-2 WS5100 Series Switch Troubleshooting Guide
Table 1.1 Switch Does Not Boot Up Troubleshooting Notes
Possible Problem
Switch has no power
Chassis fans and/or CPU
fan not rotating
All else...

1.1.2 Switch Takes a Long Time to Start Up

Until DHCP is enabled (and if static IP addresses are not being used), startup can be extremely slow. This is
normal.

1.1.3 Switch Does Not Obtain an IP Address through DHCP

The switch requires a routable IP address for the administrator to manage it via Telnet, SSH or a Web
browser. By default, the switch boots up with a non-routable static IP address.
Table 1.2 provides suggestions to troubleshoot this issue.
Table 1.2 Switch Does Not Obtain an IP Address through DHCP Troubleshooting Notes
Possible Issue
DHCP is not configured, or
not available on same
network as the switch
DHCP is not enabled on
NIC 2 (that is, the Ethernet
port that is not managing
the RF network)
All else..

1.1.4 Switch is Stuck in a Booting Loop

The switch continuously boots and does not change context to a user name prompt.
Table 1.3 provides suggestions to troubleshoot this issue.
Suggestions to Correct
• Verify power cables, fuses, UPS power. The front panel LED lights up when
power is applied to the switch.
• Verify the power switch on the back of the switch is in the I (on) position.
• Have a qualified electrician check the power source to which the switch is
connected.
• Visually inspect the fans located inside the switch chassis.
• If one or more of the CPU fans are not running, contact the Motorola Support
center for further instructions.
Contact Motorola Support.
Suggestions to Correct
• Verify the configuration for the switch has DHCP enabled. By default, Ethernet NIC 2
is DHCP enabled. Otherwise, refer to the CLI reference for instructions on enabling
the Ethernet interfaces.
• Ensure the WS5100 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
• Enable DHCP, use the CLI command or the GUI to enable DHCP on the Ethernet port
connected to your network.
• Verify 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.
Contact Motorola Support.