Mitel Sx 200 Ml Pabx Lightware 16 Instructions Guide

							2 Troubleshooting - 
General 
Emergency Procedures 
2.1 When any switching machine is totally inoperative, the prime requirement is the 
restoration of service to the system or the part that has been affected. Table 2-i 
shows how to achieve this in the shortest possible time. Once service has been 
restored, the other procedures (see Table of Contents) may be used to determine the 
cause of the failure. 
Step 
1. 
2. 
3. 
4. 
5 
6. 
7. Table 2-l Emergency Troubleshooting Procedures 
Action 
At the 
control cabinet, check if the green 
ACTIVEindicator on the Main Control Card II 
front panel is flashing. 
Press the RESET pushbutton on the front 
panel of the Main Control Card Il. 
Check if the POWER O/Vindicator on the Bay 
Power Supply is on. 
Turn the Cabinet power supply off, reseat the 
Main Control Card II and Bay Control Card, 
and turn the power on again. Any indication 
on numeric display? 
Check power rails and continuity on the 
backplane. 
Power down the cabinet, remove the Main 
Control Card II, and check if System ID 
module is securely installed. 
Ensure Bay PowerSupply isfirmlyseated into 
the backplane. ispowercordfirmlyconnected 
to the rear of the BPS? 
Check for loose power cable connections in 
the Cabinet. Description / Follow-Up 
Yes: l Go to step 7. 
No: 
l Go to step 2. 
l If the Main Control Card II numeric 
displays are blank, go to step 3; otherwise 
go to step 9. 
Yes: 
l Go to step 4. 
No: 
l Go to step 7. 
Yes: . Go to step 9. 
No: 0 Go to step 5. 
l Verify that the required voltage signals 
actually are present at the Main Control 
Card II connector. 
l Once verified, go to step 6. 
Yes: 
l Possible System ID problem - 
replace MainControl Card Il. 
No: 
l Install System ID module properly 
and go back to step 2. 
No: 
l Plug in securely; go back to step 2. 
Yes: 
l If no wiring problems are found, 
refer to the Bay Power Supply 
procedures. 
Page 1 of 2 
March 1997 Issue 1 Revision 0 2-l  
						

							Troubleshooting 
Table 2-l Emergency Troubleshooting Procedures (continued) 
Step Action Description / Follow-Up 
8. Attempt a station-to-station call - is Call Yes: 
l Stop. Continue to monitor system. 
Processing functioning? No: 
l Press the RESET push- 
button on the Main Control Card II 
front panel, and go to step 9. 
9. Check for error codes on the Main Control 
l Refer to Table 2-2. 
Card II numeric display. 
Page 2 of 2 
Main Control Card II Power-Up Error Codes 
Table 2-2 shows the Main Control Card II numeric display error codes which may 
appear during start-up. Also shown are the most likely causes of the error condition. 
Table 2-2 Main Control Card II Error Code Summary 
Error Code 
(blank) 
0 
E. 
8 
Likely Cause(s) 
l Faulty power system - refer to that procedure. 
l Faulty Main Control Card Il. 
l Faulty Main Control Card Il. 
l Faulty System ID module. 
l Nothing - indicates successful software 
download. This display may be immediately 
changed to display post-boot-up codes (see 
note 1). 
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 Il. 
2. Codes possible AFTER start-up include card diagnostics codes (last card location tested - 
top number indicates bay number, bottom number indicates card slot number). Maintenance 
logs give results of test, i.e., pass or fail with cause). 
Troubleshooting Methodology 
General 
2.2 Troubleshooting a malfunction in any complex electronic system is accomplished in a 
series of logical steps. This Section assumes the following basic steps in the 
troubleshooting of a malfunction: 
2-2 
Issue 1 Revision 0 March 1997  
						

							Troubleshooting - General 
l GATHERING of information 
l CLARIFICATION of the problem 
l CONFIRMATION of the problem 
l ISOLATION of the problem 
l CORRECTION and DOCUMENTATION 
When investigating a problem, the troubleshooter should continually verify each step 
in the isolation process so as to ensure that the system and the symptoms of the 
malfunction are clearly understood. This will ensure that the malfunction is accurately 
categorized so that appropriate diagnostics, where applicable, may be invoked. 
Information Gathering and Problem Clarification 
Chart 2-l provides a list of the information which may be necessary in order to 
adequately categorize a fault. All relevant information should be gathered and entered 
into a site fault record. If the fault has resulted in total or partial shutdown of the system, 
much of this data will be unobtainable or irrelevant. In such cases, reference should 
be made to the EMERGENCY TROUBLESHOOTING PROCEDURES. 
Chart 2-l Information Gathering and Clarification 
Step Action Description Follow-up 
1. Talk to station users. Obtain the following information: 
- frequency of occurrence 
- intermittent or continuous nature 
- time period during which the fault occurs 
- circumstances common to all occurrences. 
2. Check Maintenance 
Alarm indications. - Check maintenance log for fault/ alarm reports (see Note 1). 
- Check system LED and numeric display indicators for error 
codes. 
3. Collectdataconcerning 
environmental 
conditions. - Check if the system is located close to a heat source or a 
source of power radiation (see Note 2). 
- Note the temperature and humidity conditions and 
compare with specified operating parameters. 
- Check the susceptibility of the area with respect to static 
electricity generation. 
- The following can seriously affect the performance of 
the system: 
- power fluctuations 
- lightning storms 
- excessively high humidity 
- excessively high temperature 
- dust 
- rf interference. 
4. Verify system 
programming. - Check the existing programming to ensure that the correct 
options and features have been enabled (see Note 3). 
- Verify the Class Of Service assignments, trunk descriptors, 
and feature access codes. 
Page 1 of 2 
March 1997 Issue 1 Revision 0 2-3  
						

							Troubleshooting 
Chart 2-l Information Gathering and Clarification (continued) 
1 
Step 
5. 
6. 
7. 
Action Description Follow-up 
Make special checks 
for new installations, 
additions or 
modifications. - Check that the procedures specified in the /n.sWa~~o~~ 
/nformafion Practice have been properly implemented. 
- Verify that any changes have been made in accordance 
with the appropriate practices, and to the prescribed 
standards. 
Make random 
miscellaneous checks. 
Check for minor alarm 
indications - these 
assist in isolating and 
categorizing faults. - Check for possible conflicts if features have been added or 
deleted, or if other programming changes have been made. 
- Ensure all circuit cards are properly seated. 
- Verify that the system fans are running. 
- Check the main distribution field for loose or damaged 
wiring, improperly seated connectors, orothersigns of trouble. 
- Record relevant data and note the affected area of the system. 
Page 2 of 2 
Note: 1. Refer to the W-232 Maintenance Terminal Practice, for details on procedures. 
2. Refer to the 
Engineering hformation Practice, for the specified operating parameters. 
3. Refer to the Features Description Practice, and the Customer Data Entty Practice. 
Problem Confirmation 
Many faults, particularly intermittent faults, “disappear” before the troubleshooter is 
able to make a positive trace. Wherever possible, attempts should be made to force 
the problem to recur, such that the effects may be observed and hence the cause 
determined. The information gathered up to this point may be used to set up conditions 
relating as closely as possible to those under which the fault originally manifested itself. 
Problem Isolation 
The aids listed in Table 2-3 are useful in isolating fault conditions. 
Table 2-3 Troubleshooting Aids 
Troubleshooting Aid 
Maintenance Log 
Maintenance Terminal Description and Use 
- Provides a record of maintenance activities and causes of alarms 
(the primary source of troubleshooting information). 
- Primary access to the maintenance log. 
- Provides ability to query alarm status, along with a variety of status 
reports. 
- Allows testing of individual functional units, using directed 
diagnostics. 
Page 1 of 2 
2-4 Issue 1 Revision 0 March 1997  
						

							Troubleshooting - General 
Table 2-3 Troubleshooting Aids (continued) 
Troubleshooting Aid Description and Use 
Circuit Card Numeric 
Displays - Allow system power-up testing and operation to be monitored. 
Status LEDs (on peripher- - Used to determine if circuit is in use, idle, or not functioning. 
al cards) 
Page 2 of 2 
Correction and Documentation 
Once a problem is isolated, the table of contents of this document should be consulted, 
and the appropriate procedure referenced. Many procedures contain instructions 
requiring control circuit cards to be reset, removed, powered down or replaced; in these 
circumstances it should be noted that these actions will cause a partial or total loss of 
service. If possible, these procedures should be performed during periods of little or 
no traffic. 
All repairs or adjustments to the system should be recorded into a log book which is 
kept permanently at the site. Faulty equipment should be returned in the same 
packaging as the replacement part (FRU). For further information on FRU items, refer 
to the Fie/d-Rep/aceab/e Units Practice. 
March 1997 Issue 1 Revision 0 2-5  
						

							Troubleshooting 
2-6 Issue 1 
Revision 0 March 1997  
						

							3 Peripheral Equipment 
Troubleshooting 
Procedures 
Peripheral Interface Circuit Cards 
ONS / OPS / Station Line Cards 
3.1 This section covers the ONS Line Card (PN 9109-010) and the OPS Line Card 
(PN 9109-040). Table 3-l outlines the most likely items to cause malfunction. For 
ONS Line Card problems involving Voice Mail, see Voice Mail - ONS Port. 
Table 3-l ONS Line Card Troubleshooting Summary 
Step Possible Malfunction Source 
1. Faulty connections between the telephone and the cross-connect field. 
2. Faulty connections between the cross-connect field and the system. 
3. Faulty CDE programming; likely forms: 
l COS Define 
l Stations / SUPERSETTM Telephones 
l Device Interconnection Table 
l System Configuration 
4. Faulty telephone set. 
5. Faulty line card. 
6. Faulty backplane cable connections. 
7. Problem with DSP receivers or DTMF Receiver modules (not enough for peak traffic load). 
Note: Useful maintenance commands: SHOW STATUS, TEST, SHOW ALARMS - see the US-232 
Maintenance Terminal Practice. 
March 1997 Issue I Revision 0 3-l  
						

							Troubleshooting 
COV Line Cards 
This section covers the COV Line Card (PN 9109-020). Table 3-2 outlines the most 
likely items to cause malfunction. For COV Line Card problems involving Voice Mail, 
see COV Port - Voice Mail in Chapter 5. 
Table 3-2 COV Line Card Troubleshooting Summary 
Step Possible Malfunction Source 
Faulty connections between the SWH?SE~telephone and the cross-connect field. 
1. 
2. 
3. Faulty connections between the cross-connect field and the SX-200 ML system. 
Faulty CDE programming; likely forms: 
l COS Define 
4. 
5. 
6. 
7. 
l Stations / SUPE/%flTelephones 
l Device Interconnection Table 
l System Configuration. 
Faulty SUPH?SE~ telephone set. 
Faulty line card. 
Faulty backplane cable connections. 
Problem with DTMF Receivers (not enough for peak traffic load). 
Note: Useful maintenance commands: SHOW STATUS, TEST, SHOW ALARMS, SHOW ERRORS 
SS3-SS4 - see the RS-232 Maintenance Commands Practice. 
Digital Line Card 
General 
Intermittent problems can be caused by improper bridge taps, or incorrect loop lengths. 
The following table lists the maximum loop lengths in meters with 24 or 26 AWG twisted 
pair wiring. 
Table 3-3 Digital Line Card Loop Lengths 
Peripheral Maximum Loop Length 
Device Without Bridge Tap With Bridge Tap * 
SUPERSET 401 +TM 1 OOOm not permitted 
SUPERSET 41 OTM 1 OOOm not permitted 
SUPERSET 420TM 1 OOOm 1 OOOm 
SUPERSET 430TM 1 OOOm 1 OOOm 
Dataset 1103 2000m 1 OOOm 
Page 1 of 2 
3-2 Issue 1 Revision 0 March 1997  
						

							Peripheral Equipment Troubleshooting Procedures 
Table 3-3 Digital Line Card Loop Lengths (continued) 
Peripheral Maximum Loop Length 
Device Without Bridge Tap 
With Bridge Tap * 
Dataset 2103 2000m 1 OOOm 
MILINKTM Data Module 2000m 1 OOOm 
SUPERCONSOLE 1 OOOTM console 1 OOOm 1 OOOm 
SUPERSET 7000TM console 1 OOOm not permitted 
Page 2 of 2 
Note: 
Peripheral devices can not use bridge taps if they are connected to Digital Line Cards with PN 
9109-012-001 -NA or PN 9109-012-001 -NA. Digital Line Cards with PN 9109-012-000-SA may 
have bridge taps. 
SHOW ERRORS DATASET Command 
The SHOW ERRORS DATASET command can be a useful tool in the troubleshooting 
of both the Digital Line Card and the Dataset. The following table lists the possible 
causes of the error types. 
Error 
Type 
CFICERR 
RESETS 
LINK FAIL Table 3-4 SHOW ERRORS Command 
L 
Call Possible Cause 
State Dataset Cabling DX Chip Line Card DTE/DCE 
any w ws 
w yes no 
w yes w yes 9s yes 
Call setup/ Talk 
yes vs yes w no 
Additional Troubleshooting 
Digital Line Cards are used for many applications. For additional troubleshooting 
information, refer to procedures for the specific application; i.e.: 
l SUPERSET 401+ Telephones 
l SUPERSET 4 IO Telephones 
March 1997 Issue 1 Revision 0 3-3  
						

							Troubleshooting 
. SWERSE~ 4ZU Telephones 
l SW ERSET 430 Telephones 
l SUPERSET 7000 console 
l DATASET 1103 
l DATASET 2103 
l A&WWData Module 
l Programmable Key Module 
Trunk Cards - General 
The procedures detailed below cover the isolation and correction of faults with the 
various trunk cards. Supplementary procedures are provided for specific trunk types 
where required. Table 3-5 summarizes troubleshooting for trunk cards. 
Table 3-5 Trunk Card Troubleshooting Summary 
Step Possible Malfunction Source 
1. Faulty connections between the external trunk equipment and the cross-connect field. 
See Note 3. 
2. Faulty connections between the cross-connect field and the system. 
3. Faulty CDE programming; likely forms: 
l COS Define 
l Trunk Circuit Descriptors 
l Non-Dial In Trunks 
l Dial In Trunks 
* Trunk Groups 
l Device Interconnection Table 
l System Configuration. 
4. 
Faulty external trunk equipment (see Note 4). 
5. 
Incorrect jumper settings (LWGS Trunk card only) - see Figure 3-l. 
6. Incorrect switch settings (E&M Trunk Module). 
7. Faulty Universal Card (E&M Trunk Module only). 
8. 
Faulty LS/GS or DID Trunk Card (see Note 3). 
9. Faulty backplane cable connections. 
10. 
Problem with DTMF Receivers (not enough for peak traffic load, see Note 2). 
Note: 1. Useful maintenance commands: SHOW STATUS, TEST, SHOW ALARMS - see the f!S-232 
Maintenance Terminal Practice. 
2* Refer to the Engineering hformation Practice, for details on CO Busy Hour and receiver 
provisioning. 
3-4 Issue 1 Revision 0 March 1997