Table of Contents
Advertisement
Troubleshooting
Alarms
The following table lists common NAV alarms shown on the
pane
Alarm
Assignment Conflict
Assignment Failure
Audio Loss
Auth Failures
Backup Restore Failure
Channel Conflict
Communication Failure
Controller Disconnect
CPU Usage
Device Offline
on page 46) and suggested remedies:
Cause
The endpoint is reporting a conflicting
assignment status.
The endpoint failed to be assigned to a
NAVigator.
The input audio signal level is below
-60 dB for a period of 5 minutes or more.
A user has attempted to login
unsuccessfully 10 or more times.
A problem occurred while trying to
perform a backup or a restore.
Two or more NAV devices on the
network have been given the same input
or output number.
An online assigned endpoint cannot
establish a connection with the
NAVigator.
The NAV device is unable to connect to
a paired control processor.
The NAV device CPU is overloaded.
An assigned NAVigator is not discovered
on the network.
NAV SD 501 and NAV SD 101 Scaling Decoders • Troubleshooting
page (see
Monitoring
Remedy
Verify that the endpoint is not assigned
to another NAVigator. If it is, it must be
unassigned from the previous NAVigator.
If the previous NAVigator is unavailable,
perform a
mode 5 reset
(see page 15)
on the conflicted endpoint.
Confirm that the NAVigator has not
reached its endpoint assignment limit.
If a device has been decomissioned
from the NAV system, unassign the
endpoint from the "Offline endpoints"
list. If endpoint still cannot be assigned,
perform a
mode 5 reset
on the
endpoint.
Increase the output level of audio source.
Check whether login attempts were from
internal personnel. If not, take action to
strengthen security measures.
Debug network connectivity between the
NAVigator and endpoints.
For devices affected, change the input
number or output number so that each
is unique in the system.
Check the network settings to ensure
unicast routing is possible between the
NAVigator and endpoints.
Verify the control processor is online.
Review network settings to ensure
unicast communication is possible from
the NAV device to the control processor.
Check for excessive network data being
delivered to the endpoint.
Check the offline NAVigator for a power
failure. Check the network connectivity of
the endpoint.
Alarms
69
Advertisement
Table of Contents
