User Manual

Table Of Contents

20 APCD-LM047-1.1

3: Installation

on the CCU sector and the loading over the rest of the Internet. So this test is not the

best test for ensuring that the modem to CCU link is operating at its correct speed. But

it should indicate that the PC is able to communicate with a site on the Internet.

If any of these tests fail, then the installer may need to check the modem, its alignment, the

cabling, the PC’s configuration and the RF link. If all of these appear good, then the installer

should contact the Network Operator for further troubleshooting advice.

Even if all the above tests indicate a good link, WaveRider recommends that the Network

Operator remotely test the EUM-to-CCU data link more thoroughly soon after it is installed.

The test facilities available to the Network Operator are outlined in the LMS4000 Managing the

Network manual and other manuals on the WaveRider web-site.

The following sections provide more detail for some of the steps for Testing the Data Link.

Ping the EUM

Note that the EUM3005 may be on a different sub-net than the end-user’s PC, so pinging the

IP address assigned to the EUM3005 will go through the CCU. Therefore, we ping the

EUM3005 using the local link IP address as the 1st test.

1. Ensure the end-user’s PC is configured with an IP address of 169.254.10.251,

netmask = 16 (or 255.255.0.0). See Setup Menu on page 9 for more information.

2. Ping the EUM’s local-link IP address 169.254.10.250, from the end-user’s PC, as

follows:

• Open a DOS window in the end-user’s PC.

• At the command prompt, type ping 169.254.10.250 and press Enter.

3. If there is no response, check the following:

• The end-user’s computer IP address settings.

• The Ethernet link light on the PC.

• The Ethernet crossover cable between the EUM3005 and the end-user’s PC,

to ensure that the pins have not been damaged.

• The POWER LED should be on or flashing.

4. If there is a response, but with errors, check the Ethernet crossover cable.

This is what a successful ping from the end-user’s PC to the EUM looks like:

C:\>ping 169.254.10.250

Pinging 169.254.10.250 with 32 bytes of data:

Reply from 169.254.10.250: bytes=32 time<10ms TTL=64

Ping statistics for 169.254.10.250:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms