Mitel Sx-2000 Llightware 32, Release 1.0 Technicians Handbook

							Troubleshooting and Repair
131
Troubleshooting
- Enter YES.
- Remove the datasave RSD.
- Hold down PANEL ENABLE and press the inactive 
plane’s RESET button.
- Return to step 5 of this procedure and continue.
10. Enter:
VOL DISMOUNT 
11. Remove the RSD.
12. Enter:
DBMS SAVE.
When the save is complete, the system delivers the 
following message:
DBMS info: Save Completed
13. Switch activity. Service is lost for 5 to 15 minutes.
14. Enter JOIN first from the newly inactive plane, and then 
from the newly active plane.
When the JOIN command is entered, the system 
delivers the following messages and prompts:
ENTER:  if both planes have the same S/W
version,  to cancel JOIN.
Enter YES. 
After the operation is complete, this message appears:
System JOIN completed.
15. Ensure the databases on both drives are in synch by 
entering FIL ST RED.
16. Hold down PANEL ENABLE and press ACTIVITY 
FREEZE OFF.
17. Perform the procedure Checking a Redundant System 
on page 158.
10 min
15 min 
						

							Technician’s Handbook
132
If the System Reports a Blank Database
If you set the DBMS FLAG off by issuing the DBMS FLAG 
OFF command, the database is blanked during the next 
system reload. If you entered the command on the active 
plane of a redundant system, both planes are loaded with 
the blank database after a reload.
If both planes have a blank database, restore the database 
from a DATA SAVE backup (see page 128).
If only the inactive plane is blank, the redundant file may be 
corrupted (see page 133).
If the System Reports that the System Dimensions 
Don’t Match
If you change your system dimensions and reload the 
software, the system will not download the database. The 
system will report that the system dimensions don’t match 
the saved database.
To recover, change the system dimensions back to the 
original settings (using your old SX-2000 Feature Options 
Record sheet and MITEL OPTIONS password) and reload 
the system to recover your original database. Then, follow 
the procedure in Performing an Option Upgrade on page 
194 to change your system dimensions.
If the System Reports a SYSID Mismatch
If the system reports a SYSID mismatch, your SYSID 
module is faulty or the wrong SYSID module has been 
installed in your system. Contact MITEL Technical Support 
for assistance. 
						

							Troubleshooting and Repair
133
Troubleshooting
Fixing Redundant File Corruption
Both of the following symptoms indicate redundant file 
corruption
!if you enter DBMS SAVE and the system responds 
with DBMS SAVE COMPLETE without displaying 
the following messages:
DBMS SAVE info: 10% complete.
DBMS SAVE info: 20% complete.
*
*
DBMS SAVE info: 90% complete.
DBMS SAVE info: Save completed.
!if the active plane is IN SYNCH, but the inactive 
plane remains OUT OF SYNCH for longer than 20 
minutes.
Note:Redundant File Corruption can ocurr on non-redundant systems. Recovery is 
the same, but eliminate partitioning and joining steps and perform all steps that 
refer to the inactive plane on the active plane of your non-redundant system.
To correct redundant file corruption
1. If you don’t have an up-to-date DATA SAVE on RSD, 
make a DATA SAVE backup (see page 164).
2. Hold down PANEL ENABLE and press ACTIVITY 
FREEZE ON.
3. Log on to the active plane and select maintenance 
mode.
4. Enter:
FILE DISABLE REDUNDANCY
This message appears:
FS error: File system redundancy could not be disabled. 
Reason: No such volume.
FS warning: Local disable can be attempted (Note: can 
lead to FS corruption). 
						

							Technician’s Handbook
134
FS info: Continue? (yes/no)
Enter YES
OR
This message appears:
FS info: File system redundancy disabled.
DBMS warning: Unable to read/write state file. Reason: 
Node does not exist.
DBMS error: Download failed. Reason: Node does not 
exist.
5. Enter:
PARTITION
This message appears:
Partition complete.
6. Log on to the inactive plane and select maintenance 
mode.
7. Enter
FILE DISABLE REDUNDANCY
This message appears:
FS error: File system redundancy could not be disabled. 
Reason: No such volume.
FS warning: Local disable can be attempted (Note: can 
lead to FS corruption).
FS info: Continue? (yes/no)
Enter YES
OR
This message appears:
FS info: File system redundancy disabled.
DBMS warning: Unable to read/write state file. Reason: 
Node does not exist.
DBMS error: Download failed. Reason: Node does not 
exist.
8. Enter:
PARTITION
This message appears:
Partition complete. 
						

							Troubleshooting and Repair
135
Troubleshooting
9. Enter
VOL DISMOUNT SYSUSER
10. Enter:
VOL FORMAT DISK SYSUSER REDUND ONLY
11. Hold down PANEL ENABLE and press the inactive 
plane’s RESET button.
12. Restore the database to the inactive plane (see 
page 183).
Before doing a DBMS SAVE, enter the following 
command: TYPE ∗.DR.LOGFILE_1 to display the log 
files. Check the logs. If there are no errors, the data 
restore was completed successfully.
13. Hold down PANEL ENABLE and press ACTIVITY 
SWITCH. Service is lost for 5 to 15 minutes.
14. Enter:
DATE
Verify that the date is set correctly.
15. Enter:
TIME
Verify that the time is set correctly.
16. Log on to the newly inactive plane and select 
maintenance mode.
17. Enter
VOL DISMOUNT SYSUSER
18. Enter:
VOL FORMAT DISK SYSUSER REDUND ONLY
19. Hold down PANEL ENABLE and press the inactive 
plane’s RESET button.
20. Enter the JOIN command, first from the inactive plane 
and then from the active plane.
21. Perform the procedure Checking a Redundant System 
on page 158. 
						

							Technician’s Handbook
136
Power-down Procedures
Powering Down the Control Node
1. End any customer data entry sessions.
2. If you don’t have an up-to-date DATA SAVE on RSD, 
perform a DATA SAVE to RSD (see page 164).
3. Hold down PANEL ENABLE and press ACTIVITY 
FREEZE ON.
4. (Redundant systems only) Enter the PARTITION 
command from the active plane and then from the 
inactive plane.
5. (Redundant systems only) Enter the FILE STAT REDUN 
command from the active plane and then from the 
inactive plane. Both planes should be ISOLATED (see 
Table 25 on page 125 if they are not).
6. Enter the DBMS STAT command. The DBMS initialized 
flag should be ON.
7. Enter the VOL DISMOUNT SYSUSER command (if your 
system is redundant, enter the command first from the 
inactive plane and then from the active plane).
8. When the system confirms that SYSUSER is 
dismounted, set the power switch on the power 
distribution units at the rear of the main control cabinet to 
“0” (OFF).
9. Disconnect the power cords from the power source. 
						

							Troubleshooting and Repair
137
Troubleshooting
Powering Down the Peripheral Nodes
1. Remove the front panels.
2. If your system is redundant, set ACTIVITY FREEZE (at 
the control node) to ON.
3. Switch off the power converter.
4. Set the power switch on the rear of the node to “0” (OFF).
5. Unplug the external power cord at the rear of the node.
Powering Down the DSU Nodes
1. If your system is redundant, set ACTIVITY FREEZE (at 
the control node) to ON.
2. Set the power switch on the rear of the node to “0” (OFF).
3. Unplug the external power cord at the rear of the node. 
						

							Technician’s Handbook
138
Power-up Procedures
Powering Up the Control Node
1. Ensure the control cards are installed before powering 
up. Control cards cannot be installed when the system is 
under power.
2. Connect the external power cord(s) at the rear of the 
node.
3. Set the power switch(es) on the rear of the node to “I” 
(ON).
4. (Redundant systems only) If your system is partitioned, 
enter the JOIN command from the inactive plane and 
then from the active plane
Powering Up the Peripheral Nodes
1. Ensure the voltage selector switch is set to the required 
setting for your country.
2. Connect the external power cord at the rear of the node.
3. Set the power switch on the rear of the node to “I” (ON).
4. Switch on the power converter.
5. Complete the procedure Checking a Non-redundant 
System on page 157 or Checking a Redundant System 
on page 158.
6. If your system is redundant, set ACTIVITY FREEZE (at 
the control node) to OFF. 
						

							Troubleshooting and Repair
139
Troubleshooting
Powering Up the DSU Nodes
1. Connect the external power cord at the rear of the node.
2. Set the power switch on the rear of the node to”I” (ON).
3. Complete the procedure Checking a Non-redundant 
System on page 157 or Checking a Redundant System 
on page 158.
4. If your system is redundant, set ACTIVITY FREEZE (at 
the control node) to OFF. 
						

							Technician’s Handbook
140
Recovering from a Corrupted Hard Disk
To determine whether your hard disk is corrupted, enter 
the following command from the maintenance terminal:
MSS
This command displays the number of soft and hard errors 
on the hard disk. If hard errors are reported your hard disk is 
probably corrupted. Often you can remove hard disk 
corruption by formatting the disk. If not, the hard disk is 
faulty, and you must replace it.
Formatting the Hard Disk
Non-redundant Systems
If you have an RSD copy of the hard disk (a VOL 
BACKUP)
1 Insert the RDS copy of the VOL BACKUP in the RSD 
drive.
2. Enter:
VOL DISMOUNT SYSUSER
3. Enter:
VOL FORMAT DISK SYSUSER LOAD $8000 REDUN 
$10000 SCRATCH.
4. Insert the RSD labelled “MAIN Backup ” in the RSD drive. This RSD contains a 
copy of the hard disk. It was made during routine 
maintenance.
5. Enter:
VOL RESTORE SYSUSER FROM RSD
6. Remove the RSD from the RSD drive.