User's Manual

146 APCD-LM043-4.0
12 Troubleshooting
.
Table 34 Remote Troubleshooting — CCU
What should I do? What is a good result?
What does a good
result mean?
What if I do not get a good result?
A
Confirm the network link
to the CCU
Telnet to the CCU. Access to the CCU is
available.
Verifies network access
connectivity down to the
CCU level.
Either the network connection to the CCU is
down, or the CCU Ethernet port is not
responding. Confirm the network connection
to the CCU site. If OK, go to the local CCU
tests outlined in Table 35 on page 147.
B
Confirm EUM status at
the CCU
Enter the CLI, type
<air>.
All EUMs for the sector
should be listed.
All EUMs listed have
successfully
communicated with the
CCU during the last 12-
hour period. The time
since their last
transmission is listed in
the table. Go to Test C.
If only some EUMs are missing, they may be
turned off, or may be unable to communicate
with the CCU. Verify that all EUMs are
assigned a usable GOS in the Authorization
Table (enter
<auth> in the CLI). If no EUMs
are present, all EUMs have been unable to
communicate with the CCU. Reset the CCU.
If no EUMs register, suspect CCU system
failure, or high level of interference. Go to the
local CCU tests outlined in Table 35 on page
147.
C
Check for system
congestion
In the CLI, type
<ra
meter>
.
No indication of
violations indicating
system congestion. Note
aveIPS readings for all
GOS levels.
No violations means all
users are receiving
subscribed levels of
service. AveIPS values
that are significantly
longer than minimum for
the specific GOS may
indicate users are seeing
“degraded” service with
respect to their maximum
burst rate. This can
happen during busy
hour, depending on
system traffic load and
engineering.
Violations indicate system congestion - too
many users at too high a service level. You
need to analyze your user traffic levels.
AveIPS canbeusedtomonitorfluctuationin
user-perceived throughput. Slowdowns, even
within the bounds of subscribed service, may
result in customer complaints.