Terminal Server User Guide, Version 3.3
132
Troubleshooting
Appendix E
E
Introduction
This chapter provides information that can help resolve problems with the Terminal Server.
Hardware Problems
If the Terminal Server Power/Ready LED is red and stays red for over 10 seconds, you have a
hardware problem that might to require factory service. First, try the following:
z
If the Terminal Server is not in Console mode, do the following:
a.
Set up a direct connection to the Terminal Server; see
Through the Serial Port
on page 31
for information on this type of connection.
b.
Power the Terminal Server off.
c.
Switch the Console dip switch to On.
d.
Power the Terminal Server on.
If there is a problem with the Terminal Server firmware, you will need to reload the firmware,
which can be found either on the CD-ROM that came with the Terminal Server.
z
If the Terminal Server is already in Console mode and the Power LED stays red, you need to
make arrangements to return the Terminal Server.
If you purchased the Terminal Server less than 30 days before this problem appears, contact your
distributor; otherwise, see the Black Box web site (
www.blackbox.com
) for factory service
information. Note: no factory service can be done on a Terminal Server that has not been registered.
Power/Ready LED continues to flash green in Desktop models
This is not an error, the Power/Ready LED will flahs green when serial port 1 is in Console Mode.
Communication Issues
General communication checks and practices are as follows:
z
Are your cables connected and correctly configured? If you are using EIA-232, see
EIA-232
Cabling Diagrams on page 125
to verify that your cables are correctly configured.
z
Ping your host? If you can ping but packet loss is reported, ping another host/device on the same
network. This will tell you whether the problem is specific to the host/device or general to the
network.
z
After entering or changing IP information for your Terminal Server,
reboot
the Terminal Server
(does not apply when using BOOTP or DHCP). Once the Terminal Server has rebooted, other
network devices should be able to communicate with it (ping, telnet, etc.). Also, protocols such
as ARP and proxy-ARP will work properly.
z
Use the
show routes
command (command line only) or view the
Routes
statistics. Is there a
route to the host?
