Diagnostics & Troubleshooting; Interface Connection Issues; Testing Configuration Changes; Table 20: Diag. - Web Interface Diagnostics - Redline RDL-3000 Series User Manual

RDL-3000 FAMILY
5 Diagnostics & Troubleshooting
This section provides basic diagnostic and troubleshooting procedures. If the system can
not be restored to normal operation using the procedures in this section, contact the
local Redline representative for assistance. Include the model name and serial number
of the system in all communications.
5.1

Interface Connection Issues

Attempt to login to the RDL-3000 using a Web browser. The following table lists common
troubleshooting tips for the web interface.
Symptom
General
Information
screen is not
displayed
5.2

Testing Configuration Changes

Use the test function to evaluate changes to the remote unit configuration that may result
in loss of the wireless link.
1. Make all necessary editing changes to the configuration.
2. Click Apply (bottom of screen) to activate all edited changes.
3. Click Utilities ->
in five minutes (5 x 60 seconds).
4. If the new configuration is operating as expected, click Save All in the main menu at
any time to save the running configuration permanently.
If connectivity to the RDL-3000 is lost, wait 5 minutes for the unit to automatically
restore the previous settings.
70-00158-03-00
USER MANUAL

Table 20: Diag. - Web Interface Diagnostics

Possible Problem
Incorrect IP
address and/or
subnet mask.
Problems with host
computer, or RDL-
3000.
Host PC ARP table
is not correctly
configured
Test in the main menu. This will set a timer to reboot the RDL-3000
Proprietary Redline Communications © 2015
Solution
Perform a ping test from the host computer command
line. If the ping test is unsuccessful (timeout), then the
problem may be the IP address is not correct.
Perform a long reset to apply the default IP address
(192.168.25.2) and subnet mask (255.255.255.0).
If the ping is successful, reset the RDL-3000 and/or
reset the host computer.
Run 'arp -d' whenever the RDL-3000 is replaced. Check
that the subnet mask for the host PC matches the
subnet mask of the RDL-3000. Verify that the host and
the RDL-3000 are set for the same subnet and are not
using a duplicate or reserved IP address.
Page
Chapter 5
145 of 254 April 17, 2015