Programming instructions

195
Troubleshooting
Changing NSU
from T1 to E1, NSU
remains
unassigned
NSU does not
reflash
• Flash the NSU (refer to Technical
Bulletin 58004932)
OR
• Delete datetag.txt via ftp
OR
• From the debug terminal, issue
force dl for the NSU.
The LEDs are
marching 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 boot,
with an error
message.
Boot line timeout
No fiber connection
between the
controller and NSU.
Fix the fiber connection, and ensure
that the LEDs of both FIMs are solid
green.
Universal NSU
programming is not
complete.
1. Ensure that the NSU is
programmed as a Universal 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.
PRI/QSIG NSU
fails to boot
Database not
compatible with
new load.
1. Connect IMAT to the PRI NSU and
start IMAT.
2. Download the database from the
NSU to IMAT.
3. Save the database from IMAT to
the NSU.
4. A message appears asking if you
want to convert the database.
Select Yes.
5. When the database has finished
saving, reset the NSU.
Table 18: NSU Troubleshooting (continued)
Symptoms Probable Cause Corrective Action
(Page 2 of 3)