Mitel Sx 200 El/ml Technicians Handbook

							Troubleshooting and Repair
51
Troubleshooting
Flowchart 4: Correcting Set / Dataset Problems
Swap the set/dataset with a known working 
set/dataset (note the revision & model).
Return faulty set / dataset for 
repair.
To clear all dynamic user features 
for a set use
DIAGNOSTIC-CLR-FEATURE
Is the fault 
corrected?Ye s
No
Ensure that valid features, such as 
Do Not Disturb, are not causing 
the set to appear faulty. 
Verify the firmware revision.
Try swapping the specific line card.
Hint: Remember to advise the users of the 
temporary loss of service.Is the problem 
related to feature 
functions or is the 
problem hardware 
based ? 
=> Try swapping COS, COR, 
Tenant with a known working set to 
isolate programming area.
=> Determine what has recently 
been changed to cause this type of 
failure.
=> Determine COS, COR, Tenant 
commonality with other sets to rule 
out specific set hardware problems.
=>Verify set errors.
D
Flowchart 4:
Correcting set / dataset 
problems
Features
Hardware 
						

							Technician’s Handbook
52
Flowchart 4: continued
D
See the troubleshooting procedure given for the 
set/dataset in Troubleshoot Sets of the SX-200 EL/ML 
Technical Documentation for other possible 
corrective actions.
Is the fault corrected ?
Check the cable and cable connections between the set 
and the line card.
=> Try connecting the device directly to the 
cross-connect field to verify against house wiring 
problems.
=> Try another port on the card to verify against 
backplane problems.
Ye s
NoReturn faulty card 
for repair. 
						

							Troubleshooting and Repair
53
Troubleshooting
Flowchart 5: Maintenance Terminal Problems
Refer to the Maintenance Terminal Troubleshooting 
Procedures in the SX-200 EL/ML Technical 
Documentation for further possible corrective actions.
Ensure that the terminal parameters are set 
correctly. They are:
VT100 / 8 Bits / No Parity / One Stop Bit
ASCII character set
Xon/Xoff flow control
300-38, 400 baud
Pin 4 & Pin 7 high
Try a selection of baud rates from 300-38,400 and 
press Esc-6 after each change.
Hint: If communication was lost during a session, the 
system considers the terminal logged-in and will only 
respond at the current logged-in speed. Try setting to 
the same speed and press Esc-6 (quit) (or Esc-5 from 
Maintenance application).
If communication was never established, the system 
should respond at any speed.
Flowchart 5:
Maintenance Terminal 
troubleshooting
Try a screen reset by toggling the power off 
then on again.
Verify terminal and cabling to the maintenance 
port.
If available, try connecting to a Peripheral Bay.
Check the switch settings on the CRC. 
If a modem is connected, disconnect it.
Try Resetting the system - Hint: Remember to 
advise users of loss of service. 
						

							Technician’s Handbook
54
Interpreting the Main Control Card 
Power-Up Error Codes
The error codes listed in Table 3 may appear on the Main Control Card 
numeric display during startup. 
NOTE: 1.A normal running system may show other codes (card diagnostics or errors). 
However, during start-up, only the codes in this table are possible. Any other 
code shown during start-up indicates a faulty Main Control Card. 
2.Codes possible AFTER start-up include card diagnostics codes (last card lo-
cation tested - top number indicates bay number, bottom number indicates 
card slot number).  Maintenance logs give results of test, pass or fail with 
cause. 
Table 3:  Main Control Card Error Code Summary 
Error 
CodeLikely Cause(s)
(blank) • Faulty power system.
• Faulty Main Control Card.
0 • Faulty Main Control Card.
E.
8• MOSS password was not purchased, a purchased option is
not enabled, an enabled option is not purchased, the system
password does not match, or the system id does not match. 
• Faulty System ID module.
C • Faulty Flash memory or Main Control Card - This code shows
for approximately 15 seconds during a proper power-up
sequence. If the code remains, then a problem exists.
-
-• Nothing - indicates successful software download. This
display may be immediately changed to display post-boot-up
codes (see note 1). 
						

							Troubleshooting and Repair
55
Troubleshooting
Restoring the Database 
Restoring the SX-200 EL/ML Database 
To restore a customer database, your communication package 
must support the Kermit protocol. We recommend Terminal or 
Hyper Terminal.
1. Select the following maintenance commands:
SYSTEM
DATABASE
RESTORE
ENTER
2. Exit to a local Kermit session.
3. Specify the name and location of the software file that you want to 
transfer to the system and send it to the system.
4. After the file transfer has completed, the message 
Download/Upload Successful  appears on the screen.
After the database file is restored, the system automatically resets 
the system and the following entry is added to the log file : Main 
Control was reset due to Database Restore.
The system will reboot automatically when it detects the presence 
of a new database. 
Restoring the SX-200 LIGHT/DIGITAL Database 
1. Reset the system.
2. Remove the disks.
3. Insert the disks with the backed-up database.
4. Reset the system.
5. After the system restabilizes, copy the database to the previous 
disks. 
						

							Technician’s Handbook
56
Backing Up Log Entries
To back up log entries, your communication package must support the 
Kermit protocol.This log back-up procedure allows you to copy all 
maintenance log entries into a text file on either a directory on your PC’s 
hard disk, or on a diskette in the PC’s disk drive. 
To back up log entries:
1. Select the following commands: 
SYSTEM
DATABASE
LOGS_BACKUP
ENTER
The system prompts you for the file name. 
2. Enter the file name.
3. Press ENTER.
The system then prompts you to exit to a local Kermit session.
4. In the Kermit session, issue the Receive command.
While the backup is in progress, the top seven-segment LED on the 
MCC shows “A”, and the lower seven-segment LED shows a dash 
that is circling in a clockwise direction.
Ensure that the file name is meaningful to you. It can include 
abbreviations for the name of a remote site, the purpose or function of 
the database, the version of the software, or the number of the 
database.
Ensure that the Kermit session is set to text mode, because the 
maintenance log entries must copy into a text file. 
						

							Troubleshooting and Repair
57
Troubleshooting
Correcting System ID Errors
If the System Reports a System ID Mismatch
If the system reports a System ID mismatch, the problem may be one 
of the following:

The System ID module is faulty

The wrong System ID module is installed 

The Password is incorrect. 
Verify that the options selected on Form 04, System Options, and the 
password entered match the data provided on the MOSS sheet.
Contact MITEL Product Support for assistance. Have your tech ID 
number available.
If the System Reports a Decryption Module Error
If the system reports a decryption module error, your decryption module 
is faulty or wrong for the software that is in your system. 
Contact MITEL Product Support for assistance.
Powering Down the Nodes 
Powering Down the SX-200 EL/ML Control Node
1. End any customer data entry sessions. 
2. If you don’t have an up-to-date database backup, perform a 
database backup.
3. Switch-off power at the Bay Power Supply. Disconnect the power 
cords from the AC power source.
Refer to Backing Up a Customer Database (page 27).  
						

							Technician’s Handbook
58
Powering Down the SX-200 LIGHT Control Node
1. End any customer data entry sessions. 
2. If you don’t have an up-to-date database backup, perform a 
database backup. 
3. Push the System Reset Button.
4. Remove the disks.
5. Turn off the AC power by pushing the 0 (off) button at the rear of the 
cabinet. Disconnect the power cords from the AC power source.
Powering Down the Peripheral Nodes
1. Set the Bay Power Supply switch to O (OFF).
2. Unplug the AC power cord from the rear of the node.
Powering Down the IP Node
Unplug the AC power cord from the rear of the node.
Refer to Backing Up a Customer Database (page 27).  
						

							Troubleshooting and Repair
59
Troubleshooting
Powering Up the Nodes
Powering Up the SX-200 EL/ML Control Node
1. Connect the external AC power cord(s) at the rear of the node.
2. Switch on the Bay Power Supply switch to ON. Set the power 
switch(es) on the rear of the node to I (ON) or set the Bay Power 
Supply switch to I (ON).
Powering Up the SX-200 LIGHT Control Node
1. Connect the external AC power cord(s) at the rear of the cabinet. 
2. Set the power switch(es) on the rear of the node to I (ON). 
3. Insert the disks into the MCC.
Powering Up the Peripheral Nodes
1. Connect the external AC power cord at the rear of the node.
2. Set the Bay Power Supply switch to I (ON).
Powering Up the IP Node
1. Ensure the SX-200 IP Node is NOT connected to a power source.
2. Using a serial cable, connect a PC to the Maintenance Port on the 
IP Node.
3. Launch a data communication application, such as Hyperterminal 
on the PC. 
4. Set the parameters: 9600, 8, N, 1, None.
5. Plug the IP Node into a power source. 
						

							Technician’s Handbook
60
Replacing Circuit Cards
Wear an anti-static wrist strap whenever you handle
circuit cards.
Replacing Peripheral Interface Cards
You may replace the peripheral interface cards with the power on.
1. From the maintenance terminal select:
DIAGNOSTICS
MORE_KEYS
BUSY-OUT
 (plid of faulty card).
2. Wait until all the circuits are busied out.
3. Replace the faulty card with a new card of the same type.
WARNING: Hazardous voltages can exist on installed peripheral 
cards even when power is removed from the 
system. Grasp cards by the lock latches only. Do not touch the 
sides of cards.
Power must be off when inserting the Main Control card,
Bay Control Card, Control FIM Carrier Card, or Bay Power Supply. 
Cards that must not be inserted while system power is on carry a 
caution notice.
Set switches or jumpers on the new card to match switches or 
jumpers on the existing card.