Troubleshooting, Introduction, Hardware problems – Perle Systems Perle IOLAN DS1 User Manual
Page 217: Communication issues, Appendix g troubleshooting
IOLAN DS1/TS2 User’s Guide, Version 3.4
217
Troubleshooting
Appendix G
G
Introduction
This chapter provides information that can help resolve problems with the IOLAN.
Hardware Problems
If the IOLAN 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 IOLAN is not in Console mode, do the following:
a.
Set up a direct connection to the IOLAN; see
Through the Serial Port on page 38
information on this type of connection.
b.
Power the IOLAN off.
c.
Switch the Console dip switch to On.
d.
Power the IOLAN on.
If there is a problem with the IOLAN firmware, you will need to reload the firmware, which can
be found either on the CD-ROM that came with the IOLAN or on the Perle website,
z
If the IOLAN is already in Console mode and the Power LED stays red, you need to make
arrangements to return the IOLAN.
If you purchased the IOLAN less than 30 days before this problem appears, contact your distributor;
otherwise, see the Perle web site (
www.Perle.com
) for factory service information. Note: no factory
service can be performed on IOLANs that have 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
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 IOLAN, reboot the IOLAN (does not apply
when using BOOTP or DHCP). Once the IOLAN 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?