Mitel Sx-2000 Llightware 32, Release 1.0 Technicians Handbook

							Troubleshooting and Repair
121
Troubleshooting
Flowchart 4: Correcting Set/Dataset Problems
Swap the set/dataset with a known working 
set/dataset (of the same model).
Return faulty set/dataset 
for repair.
Enter:
LOC FEAT EXT .
The system displays the active 
features for that extension.
Is the fault 
corrected?Ye s
No
Ensure that valid features, 
such as do not disturb or call 
forwarding, are not causing the 
set or dataset to appear faulty.
Enter:
BUSY  of the card for the 
set/dataset. Select COURTESY DOWN.Is the fault 
corrected?
Ye s
No
Troubleshooting complete.
D
Flowchart 4:
Correcting set/dataset 
problems 
						

							Technician’s Handbook
122
Flowchart 4: Continued
D
See the SX-2000 Peripheral Troubleshooting 
Procedures section of the Technical 
Documentation CD-ROM for further possible 
corrective action.
Enter:
STATE  of the card.
Are all circuits 
busy?Wait until all 
circuits are in the 
busy state.No
Ye s
Swap the card with a known working 
card. Enter RTS  to return the 
circuits to service.
Is the fault 
corrected?
Check the cable and cable connections 
between the set and the line card.
Ye s
NoReturn faulty 
card for repair. 
						

							Troubleshooting and Repair
123
Troubleshooting
Flowchart 5: The Bootstrap Sequence
Flowchart 5:
The system bootstrap 
sequence
See The Bootstrap Sequence on page 115 
to identify whether the system is in the 
process of a normal bootstrap sequence. 
After determining the status of the bootstrap 
sequence, proceed from this point in the 
flowchart.
No
Is the system 
booting properly?
Wait for the system to 
finish booting.
Ye s
Flowchart 2:
System is not booting up
E 
						

							Technician’s Handbook
124
Flowchart 5: Continued
Interpret the system 
response using Table 25 on 
page 125.
Enter:
FILE STATUS REDUN
first from the active plane, 
then from the inactive plane.
F
Do you have a 
redundant 
system?
Ye sNo
Is a system 
alarm present?
Ye s
No
Troubleshooting 
complete.
Flowchart 3:
An alarm is present
E 
						

							Troubleshooting and Repair
125
Troubleshooting
Flowchart 5: Continued
F
Table 25:   Status of Redundant File System
 FILE STAT 
REDUN on 
the active 
Plane  F I LE  S T A T 
REDUN on 
the inactive 
Plane
InterpretationAction to Take
  ISOLATED    ISOLATED  The system is likely partitioned. 
You can check this status by 
entering the WHERE command 
on each plane. An asterisk at the 
end of the first line in the display 
indicates that the controller is 
partitioned. Systems are usually 
only partitioned during software 
upgrades when it is necessary to 
isolate the different software 
streams on the two main 
controllers.
   
The redundant file system could 
be disabled because someone 
has previously entered the FILE 
DISABLE REDUN command, or 
because it is a new system and 
the redundant file system has 
never been enabled.Enter the JOIN command first 
on the inactive side, then on 
the active side. Only enter this 
command if you are sure that 
the operating system software 
is identical on both planes. Use 
the WHERE command on both 
planes to verify that the 
software is identical.
   
   
Enter the FILE ENABLE 
REDUN command on the 
active plane. (You can verify 
communication between the 
active controller and the 
inactive plane’s HDM by 
entering the LOGS R OTHER 
 MATCH xxxx 
command).
IN SYNCH OUT OF 
SYNCHThe active controller is in the 
process of copying the database 
from its RAM to both hard disks. 
The inactive controller will not 
report “IN SYNCH” until the 
copying is complete.
   
If the inactive controller remains 
OUT OF SYNCH for more than 
20 minutes, the redundant file 
may be corrupted.Wait for the active controller to 
finish the copying, and then 
check for an “IN SYNCH” on 
the inactive side. 
   
   
   
If you suspect redundant file 
corruption, see page 133
IN SYNCH IN SYNCH The databases on both the active 
and inactive planes are identical.No action to take. This is how 
the system should be.
G 
						

							Technician’s Handbook
126
Flowchart 5: Continued
Is an alarm
present?Troubleshooting 
complete. No
Ye s
G
Flowchart 3:
An alarm is present 
						

							Troubleshooting and Repair
127
Troubleshooting
Flowchart 6: Maintenance Terminal Troubleshooting
Were you able to 
correct the fault?
See the SX-2000 Maintenance Terminal 
troubleshooting procedure on theTechnical 
Documentation CD-ROM for further possible 
corrective actions.
Refresh the terminal screen by typing 
[Ctrl] W. 
Ensure that the terminal baud rate is 
set correctly. Default rate is
8N1
ASCII character set
Xon/Xoff flow control
9600 baud
Pin 4 & Pin 20 high
Troubleshooting 
complete. Ye s
Try using other baud rates
(for example, 1200).
No
Flowchart 6:
Maintenance terminal 
troubleshooting
Res
et the terminal by pressing [Ctrl] Q on 
the keyboard or by resetting the power. Enter 
[Ctrl] C to cancel any active commands. 
						

							Technician’s Handbook
128
Fixing Database Errors
If the DBMS CHECK command finds errors in the database, 
fix it by restoring an uncorrupted version from a DATA SAVE 
backup on RSD.
Note:If a Guest Service function is performed during a DBMS Check, a major alarm is 
raised because the database is not fully accessible. A subsequent DBMS 
Check command will clear the error.
Restoring the Database from a DATA SAVE Backup
If your latest DATA SAVE backup is on the hard drive, you 
can restore the database faster by using it. Use the DATA 
QUERY command to display details about the database on 
the hard drive.
Always ensure you have an up-to-date DATA SAVE backup 
on RSD in case of hard disk failure.
Non-redundant Systems
1. If you don’t have an up-to-date DATA SAVE on RSD, 
perform a DATA SAVE to RSD (see page 164). 
2. Enter:
DBMS FLAG OFF
3. Hold down PANEL ENABLE and press A RESET. 
Service is lost until you complete this procedure.
4. Insert the datasave RSD into the RSD drive.
5. Enter:
VOL MOUNT RSD
Read the volume name of the RSD from the system 
response on the maintenance terminal.
6. Enter:
DATA RESTORE ∗.
RSD 15 min
Tape 60 min 
						

							Troubleshooting and Repair
129
Troubleshooting
This message appears:
Delete old log file? (Yes/No)
Enter YES.
This message appears:
Existing Data Save will be deleted from Harddisk. Continue? 
(Y/N)
Enter YES.
This message appears:
Restore system dimensions from saved data?
Enter NO.
7. If you have the Flexible Dimensioning option, this 
message may appear, if not skip to step 8:
Custom Dimensions have been detected:
Overwrite the current dimensions? (y/n)
- Enter YES.
- Remove the datasave RSD.
- Hold down PANEL ENABLE and press A RESET.
- Return to step 3 of this procedure and carry on from 
there.
8. Enter:
VOL DISMOUNT 
9. Remove the RSD.
10. Enter:
DBMS SAVE
When the save is complete, this message appears:
DBMS info: Save Completed
11. Perform the procedure Checking a Non-redundant 
System on page 157.
10 min 
						

							Technician’s Handbook
130
Redundant Systems
1. Hold down PANEL ENABLE and press ACTIVITY 
FREEZE ON.
2. Enter PARTITION first from the active plane and then 
from the inactive plane.
3. From the inactive plane, enter:
DBMS FLAG OFF.
4. Hold down PANEL ENABLE and press the inactive 
plane’s RESET button.
5 Log on to the inactive plane and select maintenance 
mode.
6. Insert the datasave RSD into the RSD drive.
7. Enter:
VOL MOUNT RSD
Read the volume name of the RSD from the system 
response on the maintenance terminal.
8. Enter:
DATA RESTORE ∗.
If this message appears:
Delete old log file? (Yes/No)
Enter YES.
This message appears:
Existing Data Save will be deleted from Harddisk. Continue? 
(Y/N)
Enter YES.
This message appears:
Restore system dimensions from saved data?
Enter NO.
9. If you have the Flexible Dimensioning option, this 
message may appear, if not skip to step 10:
Custom Dimensions have been detected:
Overwrite the current dimensions? (y/n)
15 min