Filter
Top Products
Troubleshooting
ETS Installation Guide 49
Problem/Message Error Remedy
A rapidly-blinking OK LED
may signal boot failure.
Reboot the unit. When the ETS is
running normally, the OK LED
blinks every two seconds.
The ETS is not connected
properly to the Ethernet.
Ensure that the ETS is firmly
connected to a functional and
properly-terminated network node.
The ETS Ethernet address
is invalid.
The ETS Ethernet address is
located on the bottom of the unit.
Use the Set Hardware command to
set the correct address, then
reboot. See Entering Commands at
the Boot Prompt on page 50.
The terminal shows a
Boot> prompt rather than
a Local> prompt.
Init Noboot command was
entered.
See Entering Commands at the
Boot Prompt on page 50.
If the OK LED blinks
rapidly, the Flash ROM
code may be corrupt.
The ETS passes power-
up diagnostics, but
attempts to download
new Flash ROM code
from a network host.
If you did not request a
TFTP boot, the flash ROM
code is corrupt. The unit
will remain in boot mode.
Reboot the unit. If you get the same
message, you will need to reload
Flash ROM. Refer to D:Updating
Software.
DHCP Troubleshooting
Table B-3. DHCP Troubleshooting
Area to Check Diagnosis/Remedy
DHCP is enabled on the
ETS
Use the Set Server DHCP Enabled
command. If you manually enter an IP
address, DHCP is automatically disabled.
Make sure the DHCP
server is operational.
Check to see that the DHCP server is on
and is functioning correctly.
The ETS gets its IP
address from the DHCP
server
Refer to the DHCP Manager on your DHCP
server for information about addresses in
use. If the DHCP server doesn’t list your
ETS IP address, there may be a problem.
BOOTP Troubleshooting
If the BOOTP request is failing and you have configured your host to respond to the
request, check these areas:
Table B-4. BOOTP Troubleshooting
Area to Check Explanation
BOOTP is in your system’s
/etc/services file
BOOTP must be an uncommented line in
/etc/services.