Troubleshooting; Alarms - Extron electronics NAVigator User Manual

Troubleshooting

Alarms

The following table lists common NAV alarms shown on the Monitoring page (see
and suggested remedies:
Alarm
Assignment Conflict
Assignment Failure
Audio Loss
Auth Failures
Backup Restore Failure
Channel Conflict
Communication Failure
Controller Disconnect
CPU Usage
Device Offline
Disk Space
Firmware Failure
Cause
The NAVigator and endpoint report
conflicting assignment statuses.
The NAVigator failed to assign a
discovered endpoint.
The input audio signal level is below
-60dB for a period of five 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 NAVigator CPU is overloaded.
An assigned endpoint has gone offline,
either due to power or a network
connectivity loss.
Internal storage on the NAV device is
low.
A critical process has failed, crashing
either the NAVigator or an endpoint.
Factory reset
Perform a
endpoint that is causing the issue and then
reassign it to the NAVigator.
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
Factory 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 controller-to-NAVigator
communications.
Check the offline endpoint for a power failure.
Check the network connectivity of the endpoint.
Reboot the NAV device. If the issue persists,
perform a software reset that delete files (see
Resetting the NAVigator
Reboot the NAVigator. If the failure persists,
perform a Factory reset
NAVigator System Manager • Troubleshooting
Alarms pane on page 113
Remedy
(see page 8) on the
on page 95).
(see page 8).
140