User Manual

Table Of Contents
4: Installation
APCD-LM048-1.1 33
Ping the EUM
Note that the EUM3006 may be on a different sub-net than the end-user’s PC, so pinging the
IP address assigned to the EUM3006 will go through the CCU. Therefore, we ping the
EUM3006 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 15 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 PoE Injector and the end-user’s
PC, to ensure that the pins have not been damaged.
The PoE Injector’s POWER LED should be on.
The Ethernet cables are plugged into the correct ports of the PoE Injector.
If you have an MDB1000, cycle the power at the PoE Injector to reboot the
EUM3006 and verify that the EUM3006 is communicating with the MDB1000.
Note that the MDB1000 needs to be near the EUM3006. Also, if the EUM3006
has been on for more than 1 hour, it will have stopped sending the magnetic
signal to the MDB1000, hence the reason for cycling the power on the
modem.
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
Reply from 169.254.10.250: bytes=32 time<10ms TTL=64
Reply from 169.254.10.250: bytes=32 time<10ms TTL=64
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