Mitel 3300 Technician's Handbook page 180

Technician's Handbook
Table 42. Troubleshoot the NSU
Symptoms
The LEDs are
marching (red/amber
for 15 minutes, then
amber for a few
minutes), and cycle
persistently through
the same pattern.
NSU fails to boot, with
an error message.
Boot line timeout.
NSU fails to boot, with
an error message.
Boot line timeout.
NSU keeps resetting
with no IMAT db error
message.
162
Probable Cause
Corrupted NSU
software.
No fiber connection
between Controller
and NSU.
Universal NSU
programming is not
complete.
No IMAT database is
saved to the NSU
(PRI).
Corrective Action
Refer to TSB
#58004932 for
information on
reflashing the NSU.
Fix the fiber
connection, and
ensure that the LEDs
of both FIMs are solid
green.
1.
Ensure that the NSU
is programmed as a
Universal NSU T1 or E1
(not T1 or CEPT).
2.
Program the proper
link descriptor with the
proper integrated
access, and assign to the
corresponding NSU unit
(for example: ISDN node
for PRI protocol, T1D4
for T1D4, DPNSS for
MSDN).
3.
Program at least one
trunk.
Use IMAT and save
the corresponding
database to NSU
(PRI).