WaveRider LMS4000, User Manual

Page: 136 / 282

9 Installing the EUM
118 APCD-LM043-4.0
Ping statistics for 10.5.4.116:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
If you are not able to
<ping>
the EUM from the PC, go to Troubleshooting on page 121.
Testing the Data Link from the End-user’s PC to the Network
Once the connection from the PC to the EUM is confirmed, ping the EUM gateway address
from a PC DOS window. Ping with short packets first to confirm function, and then with long
packets (1472 byte packets) to confirm performance. Errors observed on pings with long
packets indicate a high error rate on the channel, caused by low signal levels or interference.
To Ping a CCU with the maximum packet size
1. Open a DOS window.
2. At the command prompt, type ping <aaa.bbb.ccc.ddd> -t -L 1472, where
<aaa.bbb.ccc.ddd> is the CCU radio IP address and press Enter.
3. Press Ctrl+c to end the test.
NOTE: If this test fails, but pinging the CCU with the default packet size
succeeds, then the connection is working but is not operating at
maximum capacity, possibly due to poor antenna placement or
orientation.
This following example uses the sample configuration shown in Figure 47 :
Pinging the CCU from the end-user’s PC (with maximum packet size):
C:\>ping 10.5.0.1 -t -l 1472
Pinging 10.5.0.1 with 1472 bytes of data:
Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=81ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=80ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=60ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=80ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64
Reply from 10.5.0.1: bytes=1472 time=110ms TTL=64
Ping statistics for 10.5.0.1:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 110ms, Average = 66ms
Control-C
^C
C:\>
More advanced tests and troubleshooting procedures are included in Troubleshooting on page
135.