Lantronix SCS100/200/400 SCS100 / SCS200 / SCS400 - User Guide - Page 51

Power-up Troubleshooting, Problem/Message, Error, Remedy

Page 51 highlights

SCS100/200/400 User Guide 7: Troubleshooting When you report a problem, please provide the following information: Your name, and your company name, address, and phone number Lantronix SCS model number Lantronix SCS serial number Software version (use the Show Server command to display) Network configuration, including the information from a Netstat command Description of the problem Debug report (stack dump), if applicable Status of the unit when the problem occurred (please try to include information on user and network activity at the time of the problem) Power-up Troubleshooting Problem situations and error messages are listed in the table below. If you cannot find an explanation for your problem, try to match it to one of the other errors. If you cannot remedy the problem, contact your dealer or Lantronix Technical Support. Problems and Error Messages Problem/Message Error Remedy The SCS is connected to a power source, but there is no LED activity. The unit or its power supply is damaged. Contact your dealer or Lantronix Technical Support for a replacement. The SCS is unable to complete power-up diagnostics. This generally indicates a hardware fault. One of the LEDs will be solid red for three seconds, followed by one second of another color. Note the blinking LED and its color, and then contact your dealer or Lantronix Technical Support. The SCS will not be operational until the fault is fixed. The SCS completes its power-up and boot procedures, but there's no noticeable serial activity. There is a problem with the serial connection or the set- up of the serial device. A rapidly blinking OK LED may signal boot failure. Check the terminal setup and the physical connections, including the cable pinouts. Try another serial device or cable, or cycle power on the SCS. Reboot the unit. When the SCS is running normally, the OK LED blinks every two seconds. The terminal shows a Boot> prompt rather than a Local> prompt. The SCS is not connected properly to Ensure that the SCS is firmly connected to a the Ethernet. functional and properly terminated network node. The SCS Ethernet address is on the bottom of the The terminal shows a Boot> prompt rather than a Local> prompt. The SCS Ethernet address is invalid. unit. Use the Set Server Hardware command to set the correct address (enter the last three hex pairs of the address), and then reboot. Init Noboot command was entered. See Boot Prompt Commands. The SCS passes power- If the OK LED blinks rapidly, the Reboot the unit. If you get the same message, you up diagnostics, but Flash ROM code may be corrupt. will need to reload Flash ROM. attempts to download If you did not request a TFTP boot, new Flash ROM code the flash ROM code is corrupt. The See Updating Software. from a network host. unit will remain in boot mode. 7-2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61

SCS100/200/400 User Guide
7: Troubleshooting
When you report a problem, please provide the following information:
±
Your name, and your company name, address, and phone number
±
Lantronix SCS model number
±
Lantronix SCS serial number
±
Software version (use the Show Server command to display)
±
Network configuration, including the information from a
Netstat
command
±
Description of the problem
±
Debug report (stack dump), if applicable
±
Status of the unit when the problem occurred (please try to include information
on user and network activity at the time of the problem)
Power-up Troubleshooting
Problem situations and error messages are listed in the table below. If you cannot find an
explanation for your problem, try to match it to one of the other errors. If you cannot
remedy the problem, contact your dealer or Lantronix Technical Support.
Problems and Error Messages
Problem/Message
Error
Remedy
The SCS is connected to
a power source, but there
is no LED activity.
The unit or its power supply is
damaged.
Contact your dealer or Lantronix Technical
Support for a replacement.
The SCS is unable to
complete power-up
diagnostics.
This generally indicates a hardware
fault. One of the LEDs will be solid
red for three seconds, followed by
one second of another color.
Note the blinking LED and its color, and then
contact your dealer or Lantronix Technical
Support. The SCS will not be operational until the
fault is fixed.
There is a problem with the serial
connection or the set- up of the serial
device.
Check the terminal setup and the physical
connections, including the cable pinouts. Try
another serial device or cable, or cycle power on
the SCS.
The SCS completes its
power-up and boot
procedures, but there's
no noticeable serial
activity.
A rapidly blinking OK LED may signal
boot failure.
Reboot the unit. When the SCS is running
normally, the OK LED blinks every two seconds.
The terminal shows a
Boot>
prompt rather
than a
Local>
prompt.
The SCS is not connected properly to
the Ethernet.
Ensure that the SCS is firmly connected to a
functional and properly terminated network node.
The SCS Ethernet address is invalid.
The SCS Ethernet address is on the bottom of the
unit. Use the
Set Server Hardware
command to
set the correct address (enter the last three hex
pairs of the address), and then reboot.
The terminal shows a
Boot>
prompt rather
than a
Local>
prompt.
Init Noboot
command was entered.
See
Boot Prompt Commands.
If the OK LED blinks rapidly, the
Flash ROM code may be corrupt.
Reboot the unit. If you get the same message, you
will need to reload Flash ROM.
The SCS 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.
See
Updating Software
.
7-2