hit counter script

Troubleshooting With Leds; Troubleshooting With The Menu System - GE MDS iNET Series Reference Manual

Wireless ip/ethernet transceiver
Hide thumbs Also See for MDS iNET Series:
Table of Contents

Advertisement

3.2 Troubleshooting with LEDs

An important set of troubleshooting tools are the LED status indicators on the front panel of case. You
should check them first whenever a problem is suspected. Table 3-1 on Page 95 provides suggestions for
resolving common system difficulties using the LEDs, and Table 3-2 on Page 96 provides other simple tech-
niques.
Table 3-1. Troubleshooting Using LEDs—Symptom-Based
Symptom
PWR LED does not
turn on
LINK LED does not
turn on
PWR LED is
blinking
LAN LED does not
turn on
LAN LED lights, but
turns off after some
time

3.3 Troubleshooting with the Menu System

If you have reviewed and tried the things mentioned in Table 3-1 and still have not resolved the problem,
there are some additional tools and techniques that can be used. The radio's embedded Management System
is a good source of information that may be used remotely to provide preliminary diagnostic information,
or may even provide a path to correcting the problem.
05-2806A01, Rev. L
Problem/Recommended System Checks
a. Voltage too low—Check for the proper supply voltage at
the power connector. (10–30 Vdc)
b. Indefinite Problem—Cycle the power and wait
( 30 seconds) for the unit to reboot. Then, recheck for
normal operation.
a. Network Name of Remote not identical to desired Access
Point. Verify that the system has a unique Network Name.
b. Not yet associated with an Access Point with the same
Network Name.
Check the "Status" of the unit's process of associating with
the Access Point. Use the Management System.
c. Poor Antenna System. Check the antenna, feedline and
connectors. Reflected power should be less than 10% of
the forward power reading (SWR 2:1 or lower).
d. Security Parameters do not match, preventing Remotes to
join. Disable or correct these parameters.
a. Blinking indicates an alarm condition exists.
b. View Current Alarms and Event Log and correct the
problem if possible.
(See "Using Logged Operation Events" on Page 99)
c. Blinking will continue until the source of the alarm is
corrected, for example, a valid IP address is entered, etc.
a. Verify the Ethernet cable is connected at both ends.
b. Verify that the appropriate type of Ethernet cable is used:
straight-through, or crossover.
Verify traffic in LAN. Typically, the radio should not be placed
in high traffic enterprise LANs, as it will not be able to pass this
level of traffic. If needed, use routers to filter traffic.
MDS iNET Series Reference Manual
95

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mds inet-ii 900Mds inet 900

Table of Contents