User's Manual

APCD-LM043-4.0 143
12 Troubleshooting
B
Verify the logical data
connection between the
PC and EUM.
Through the DOS
command line,
<ping>
the EUM with short and
long packets.
No failures or time-outs. Confirms physical and
logical connection to the
EUM, and basic IP
addressing. Go to C.
• Verify the IP address in the PC, by
entering
<ipconfig> in the DOS
command line. If the IP is bad, enter the
appropriate IP set (PC’s IP, gateway IP,
and DNS IP).
• If using DHCP, renew through
<ipconfig>.
• If DHCP fails, enter valid IP set for
remaining tests
• Change to different PC, using shorter
cable.
• If none of the above, suspect defective
EUM.
C
Through the DOS
command line,
<ping>
the CCU with short and
long packets.
No failures or time-outs. Confirms data
transmission over the
radio link, and completes
the 900 MHz network-
specific troubleshooting.
Go to E.
If no pings are successful:
• Verify the EUM ID in the CCU
Authorization Table.
• Reboot the EUM.
• Reboot the PC.
• Refer to procedure <In the Case of
Interference>.
If pings are successful but have errors:
• Refer to procedure <In the Case of
Interference>.
D
Verify data transfer
across the radio link.
Through the DOS
command line, FTP to
the CCU, and follow the
instructions set out in
Transfer a File to or from
a CCU Using FTP
on
page 78 (bin, hash, get
<file>).
The FTP transfer rate
varies depending on
system loading;
however, you should see
a resultant transfer rate
corresponding to the
assigned GOS for the
EUM.
Confirms data
transmission over the
radio link, and completes
the 900 MHz network-
specific troubleshooting.
Go to E.
If the data transfer rate is poor, or if you
observed severe stalling of the transfer
progression (minor stalls can be expected
and are a normal part of the polling process).
Table 33 Local Troubleshooting — EUM (Service Degraded)
What should I do? What is a good result?
What does a good
result mean?
What if I do not get a good result?