EasyManua.ls Logo

MDS iNET 900 - Troubleshooting Using the Embedded Management System; Starting Information Screen

MDS iNET 900
130 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
MDS 05-2806A01, Rev. A MDS iNET 900 Users Guide 89
4.1.2 Troubleshooting Using the Embedded
Management System
If you have looked over and tried the things mentioned in Table 4-1and
still have not resolved the problem, there are some additional tools and
techniques that can be used. The embedded Management System is a
good source of information that may be used remotely to provide pre-
liminary diagnostic information, or may even provide a path to cor-
recting the problem.
The following is a summary of how several screens in the iNET Man-
agement System can be used as diagnostic tools. For information on
how to connect to the iNET Management System See STEP 3CON-
NECT PC TO THE iNET on Page 80.
Starting Information Screen
(See Starting Information Screen on Page 24)
The iNET MS’s “home page” provides some valuable bits of data. Prob-
ably the most important is the “Device Status” field. This one item will
tell you if the unit is showing signs of life.
If the Device Status field says “associated,” then look in the network
areas beginning with network data statistics. If it displays some other
message, such as Scanning, Sync Hop or Alarmed, you will need to
determine why it is in this state.
The Scanning state indicates a Remote unit is looking for an Access
Point beacon signal to lock onto. It should move to the Sync Hop and
finally to the Associated state within less than a minute. If this Remote
unit is not providing reliable service, look at the Event Logs for signs of
lost association with the Access Point or low signal alarms. Table 4-3
provides a description of the Device Status messages.
Table 4-2. Basic troubleshooting using the Management System
Symptom Problem/Recommended System Checks
Cannot pass IP
data to WAN.
a. Verify your IP settings.
b. Use the PING command to test communication with iNET
units in the local radio system.
c. If successful with local PING, attempt to PING an IP unit
attached to an iNET radio.
d. If successful with the LAN PINGs, try connecting to a
known unit in the WAN.
Wireless Retries
too high.
Possible Radio Frequency Interference
a. If omnidirectional antennas are used, consider changing to
directional antennas. This will often limit interference to
and from other stations.
b. Try skipping some zones where persistent interference is
known or suspected.
c. The installation of a filter in the antenna feedline may be
necessary. Consult the factory for further assistance.

Table of Contents

Related product manuals