Troubleshooting guide

Troubleshooting Guide
44
Service Units
Table 11: Service Unit Troubleshooting
Symptom Probable Cause Corrective Action
Network Service Units
NSU not functioning correctly. Issue with external equipment. Check external equipment.
Faulty fiber connection between
NSU and controller.
Fix the fiber connection, and ensure that
the LEDs of both FIMs are solid green.
Programming error. Check the programming in the following
forms:
MSDN/DPNSS/DASS2 Trunk Circuit
Descriptor Assignment
Miscellaneous Assignment (for
NSU-BRI only)
Link Descriptor Assignment.
NSU fails to come up after
upgrade or new installation
(Both the red and amber
LEDs, or just the amber LED,
are alternating between
L0/L1).
Automatic NSU upgrade is in
progress.
Wait 15–20 minutes for the NSU upgrade
to complete.
CAUTION: Do not power
down when the amber LED
is alternating between
L0/L1. Powering down the NSU may
corrupt the NSU software.
The LEDs are flashing green
and amber for more than 30
minutes during an NSU
upgrade.
Corrupted NSU software. Refer to Technical Bulletin 58004932 for
information on flashing the NSU.
NSU fails to come up after
upgrade or new installation.
NSU continues to reset on a
regular interval and/or the
LEDs on L0 and L1 continue in
alternating flash cycle longer
than 30 minutes.
NSU flash is corrupted. Refer to Mitel Knowledge Base article
04-1000-00026_2 for instructions.
NSU fails to load after upgrade
or install with “Unexpected
database error”
Database version is unsupported
(incompatible).
Refer to Mitel Knowledge Base article
04-5115-00002 for instructions.
NSU or PRI card fail to load
after upgrade or database
restore.
NSU and PRI cards fail to load
because the database version
does not match the current
software load on the card.
Refer to Mitel Knowledge Base article
05-5134-00023.
NSU keeps resetting with no
IMAT db error message.
No IMAT database is saved to the
NSU (PRI/QSIG).
Use IMAT to save the corresponding
database to NSU (PRI/QSIG).
Page 1 of 3