Mitel Sx 200 Ml Pabx Lightware 16 Instructions Guide

							1 General 
1.1 This practice describes the maintenance philosophy, features, and facilities of the 
SX-200@ ML Private Automatic Branch Exchange (PABX). Diagnostic tests, 
maintenance aids, local and remote terminals, and other available tools assist 
maintenance users to ensure a continued high standard of efficiency and 
performance. Further details concerning maintenance may be found in the practices 
listed in Table l-i. 
Table l-l SX-200 ML PABX Practices 
9109-098-l 
00-NA General Description 
9109-098-l 05NA Features Description 
19109-098-l 80-NA Engineering Information 
9109-098-350-NA 
9109-098-351 -NA Troubleshooting 
RS-232 Maintenance Terminal 
Reason for Issue 
1.2 This practice forms part of the MlTEL@ Standard Practices issued to provide technical 
information for the SX-200 ML PABX. 
Disclaimer 
1.3 The following products have been manufacture-discontinued by Mitel. These 
products are supported but not described in SX-200 ML Practices: 
l SUPERSET 3TM and SUPERSET 4TM telephone sets 
l SUPERSET 3DNTM and SUPERSET 4DNTM telephone sets 
l DATASET 1101 data cartridge 
l SUPERSETTM DSS module. 
I .4 The following products and peripheral devices are not supported on the SX-200 ML 
PABX and are not described in SX-200 ML Practices: 
Modem Interconnect Panel 
DATASET I 102 Rack-mounted Dataset 
DATASET 2102 Rack-mounted Dataset 
DATACABINET 9000 data cabinet 
DATASHELF 9100 datashelf 
ISDN Node. 
Fiber Interface Module (and associated products) 
Peripheral Node 
LCD Console (and Console module for Universal Card). 
March 1997 Issue 1 Revision 0 l-l  
						

							General Maintenance Information 
l-2 Issue 1 Revision 0 March 1997  
						

							, 2 Maintenance Tools 
The Maintenance Terminal 
2.1 The RS-232 ASCII Maintenance Terminal is the primary maintenance tool for the 
SX-200 ML PABX. There can be only one maintenance session active at any time. 
The maintenance terminal connects by means of a standard g-pin RS-232 cable. 
One end of the cable is plugged into the main RS-232 communication port of the 
terminal; the other end is plugged into the Maintenance Connector port on the cabinet 
backplane. Refer to Figure 2-l. 
A wide range of commands is available at the maintenance terminal to help the user 
locate and replace faulty equipment. For further information, refer to the 
RS-232 Maintenance Termina/ Practice. 
Note: The maintenance terminal user must “LOGOUT’ after every session. 
The attendant console can be used as an alternate maintenance workstation. All com- 
mands available at the maintenance terminal are available at the attendant console. 
A PC can be used as a maintenance terminal to back up a customer database to the 
PC storage medium by using the Database Restore function. 
Maintenance Port 
The maintenance port provides a connection to the system for an RS-232 ASCII ter- 
minal for maintenance or programming purposes. The terminal is connected to the 
system through the Maintenance Connector port either directly, or indirectly through a 
modem and a null modem adapter. The Maintenance Connector port is located on the 
rear panel of the SX-200ML cabinet (see Figure 2-l); refer to the RS-232 Maintenance 
Termina/ Practice for further information. 
System Maintenance Log 
2.2 The system maintenance log is a text file-based record of all maintenance-related 
information. Any event which potentially affects the functioning of the system is 
entered into this log. Typical maintenance log entries include circuits that fail 
diagnostics, cards that have been unplugged, and alarm levels that change. The user 
may read, delete, and print log entries, as well as set a variety of printing options. For 
additional information on maintenance log functions see Section 6. 
Three types of log reports are generated: 
l Fault report - Call Processing or the maintenance system has detected an error 
or an abnormal condition. 
l Reset report - A bay or the Main Control Card II has reset. 
l Alarm Level Change report - The overall system alarm level has changed. 
March 1997 Issue 1 Revision 0 2-l  
						

							General Maintenance Information 
-ylll I Tl AIIAPTER ASSEMBLY .- . .-. .--- ..--. P/N 9400-I 00-302-NA 
(OPTIONAL - SHOWN INSTALLED) 
BAY PSU AC PLUG 
ACCESS PANEL 
PFT CONNECTOR 
SYSTEM GROUND LUG 
cc0179 
Figure 2-l Rear Panel of the SX-ZOO ML Cabinet 
2-2 Issue 1 Revision 0 March 1997  
						

							3 Alarms 
General 
3.1 Alarms allow the SX-200 ML PABX to determine its own functional state. The Alarm 
Manager software program monitors the performance of all peripheral devices in the 
system, and compiles up-to-date statistics on anomalies. The alarm level is 
determined by the actual or potential effect on service that the anomalies cause. 
Alarm Levels 
3.2 There are four distinct levels of alarm defined for the maintenance system. These 
levels provide maintenance personnel with up-to-date information on the severity of 
existing anomalies. The four alarm levels are: 
l NO ALARM - indicates that the system is functioning properly. 
l MINOR - indicates that there are problems affecting the system in small 
proportion. 
9 MAJOR - indicates that there are problems causing a serious degradation of 
service. 
l CRITICAL - indicates that there has been a very serious loss of call processing 
capability. It invoks an automatic system fail transfer (SFT) and resets the system. 
Alarm Categories 
3.3 Four basic alarm categories relate to peripheral equipment. All problems affecting 
system performance will fall into one or more of these categories. Failure of other 
system components will indirectly cause failure of peripheral equipment. The 
categories are: 
l Lines 
l Trunks 
l DTMF Receivers 
l PCM Channels. 
March 1997 Issue 1 Revision 0 3-l  
						

							General Maintenance Information 
Alarm Types 
3.4 Because the SX-200 ML PABX is modular in design, the Alarm Manager keeps alarm 
statistics in three categories: 
l Bay Alarms - alarm levels of the categories specific to the one bay in the system. 
l System Alarms - alarm levels of the categories on a system-wide basis. 
l Overall Alarm - overall system alarm level, derived from all bay alarms and sys- 
tem alarms in all categories. This is the alarm that is displayed on the upper right 
corner of the console. 
Alarm Thresholds 
3.5 For each alarm category, the thresholds represent the alarm level trip points; that is, 
the precise divisions between the alarm levels. The thresholds are simple 
percentages, indicating availability: the number of working devices is compared to the 
number of programmed devices. The Critical Alarm threshold is not a percentage, but 
is a precise numerical value. When the number of available devices falls below this 
number, a critical alarm is raised. The thresholds are programmable (refer to the 
K-232 A&irrtenafxe Termi& Practice). 
Alarm Totals 
3.6 The Alarm Manager keeps a record of the total numbers of the various devices that 
should be available to Call Processing, as well as the actual number that are 
available. Alarm totals are maintained for each of the alarm categories in each bay, as 
well as for the entire system. These totals are compared to the alarm thresholds, to 
determine the level of alarm that is raised. 
3-2 
Issue 1 Revision 0 March 1997  
						

							4 The Maintenance 
Manager 
General 
4.1 The Maintenance Manager is the central maintenance soft :ware program in the 
SX-ZUO ML PABX system software. Its responsibility inck Jdes receiving requests to 
run diagnostic tests, managing test schedules (queues), and initializing diagnostic 
tests. 
Diagnostic Test Queues 
4.2 Diagnostic tests are grouped into three different categories: power-up, background, 
and directed. The test schedules (queues) are prioritized along the same categories. 
Table 4-l describes the queues in ascending order of priority. When the Maintenance 
Manager schedules a device for a particular type of diagnostic test, it places the 
device in the appropriate diagnostic test queue. When the maintenance person 
disables a diagnostic test type through the maintenance interface, the corresponding 
test requests are removed from the associated test queue. The priority scheme is 
designed to ensure that testing requested by the maintenance person through the 
maintenance terminal is handled immediately. 
2 
Table 4-l Diagnostic Test Queues 
Diagnostic Test 
Queue Priority Description 
Background Queue 6 This queue has the lowest priority; any device with background 
diagnostics enabled will normally be tested once during each pass 
through the system. 
Power-up Queue 5 
Power-up RetryQueue 4 
Fault Isolation Queue 3 Note: Background Diagnostics can be manually disabled. 
If a device has power-up diagnostics enabled, and is both 
programmed and installed, it will be put on this queue. 
Note: Power-up Diagnostics must be manually enabled. 
If a device could not be tested when on the Power-up Queue, it is 
placed on this higher priority queue to be tested as soon as 
possible. 
If a previously healthy device fails a test, it will be flagged 
“SUSPECT” and tested again from this queue. If it fails here, it is 
removed from service. 
Fault Isolation Retry 
Queue 2 If a device could not be tested when on the Fault Isolation queue, 
it is placed on this higher priority queue to be tested as soon as 
possible. 
Directed Test (User) 
Queue 1 This is the highest priority test queue. Devices in this queue are 
tested immediately; results are reported to initiating user port. 
March 1997 Issue 1 Revision 0 4-l  
						

							General Maintenance Information 
Testing 
4.3 The Maintenance Manager controls the entire test sequence on any device under 
test. The general test sequence for any peripheral device is: 
1. The Maintenance Manager locates a device with pending diagnostic test requests 
on the highest priority test queue. 
2. The device is requested from call processing for testing. If the device is idle, the 
request is granted. 
3. Any resources required to perform tests on the device are allocated. 
4. The series of tests for the particular device is invoked. 
5. When testing has been completed, the status of the device is updated. 
6. Changes to device status are logged into the maintenance log and the alarm levels 
are updated. 
7. Resources required for testing are released. 
8. The device is then returned to call processing providing it has passed all tests. If 
any tests failed, the device will be re-tested. Failure of retest removes the device 
from service. 
When the Maintenance Manager has control of a device for testing purposes, it must 
follow a set of guidelines designed to make diagnostic testing both transparent to 
system users and efficient. These guidelines include: 
(a) If call processing requires a device while it is being tested, the Maintenance Man- 
ager immediately aborts the test and releases the device. 
(b) When a device fails a diagnostic test, it is tested a second time to verify the fault. 
If it fails again, it is removed from service. 
(c) When a device fails diagnostic tests, and is subsequently removed from service, 
it remains out of service until it passes seven successive diagnostic tests. 
(d) If a device scheduled for power-up or fault-isolation diagnostic testing cannot be 
tested, it is rescheduled for testing on a higher priority test queue, and retried at 
Sminute intervals. 
(e) Each device may have background and/or power-up diagnostics selectively dis- 
abled by the maintenance person through the maintenance interface. 
Fault Recovery 
4.4 Once a device fails diagnostic testing, it is removed from active service; it can no 
longer be used by call processing. The three different circumstances through which 
the device can be returned to active service are: 
1. The most common method should be through the troubleshooting procedures 
outlined in the TrouHes/?ooGng Practice, which entails repair or replacement of 
the affected device. When re-installed, the device is automatically tested, and if it 
passes, it is returned to service. 
4-2 
Issue 1 Revision 0 March 1997  
						

							The Maintenance Manager 
2. The maintenance person has the option of returning a faulty device to service, if 
desired, through the maintenance interface (terminal, console, or test line); see 
the 
I%-232 Maintenance Termha/ Practice. 
3. When a device fails diagnostic testing and is subsequently removed from service, 
the Maintenance Manager continues testing it. If a device passes seven consec- 
utive tests after being removed from service, it is returned to service. 
The Maintenance Database 
4.5 All cards that are programmed through Customer Data Entry (CDE) have associated 
with them an up-to-date status record located in system DRAM memory. These areas 
are the Maintenance Device Work Areas (DWA) and help the system todetermine the 
state of every device in the system at any point in time. Table 4-2 describes the 
information stored in the device work areas. 
Table 4-2 The Maintenance Device Work Area 
DWA Entry Description 
1 Physical Location 1 The physical location (bay, slot, circuit, subcircuit) of the device. 
Card Type 
Card Status The type of card programmed in the specified location; i.e., ONS Line 
Card, DTMF Receiver Module, etc. 
The status of the card; one of: 
I 1 instld - the correct card type is installed 
unplug -the card is programmed, but is either unplugged or not installed 
wrong - an incorrect card type is installed. 
Test Request Pending On each of the six test queues, the number of outstanding requests for 
Counter diagnostics 
tests for the card. 
Test Request Pending 
Flag 
Circuit Status For each circuit on the card, and for each test queue, this flag indicates 
outstanding test requests. 
The status of the circuit, one of: 
avail - available to CP and maintenance 
v-w - programmed in CDE but not installed 
unprog - installed but not programmed in CDE 
suspt - suspect - failed diagnostic test once 
flty0 - faulty 
fltyl -faulty with one pass 
flty2 - faulty with two passes 
flty3 - faulty with three passes 
flty4 - faulty with four passes 
flty5 - faulty with five passes 
flty6 - faulty with six passes 
bsout - forced busy, busied-out 
Page 1 of 2 
March 1997 Issue 1 Revision 0 
4-3  
						

							General Maintenance Information 
Table 4-2 The Maintenance Device Work Area (continued) 
DWA Entry 
Power-up Enable 
Background Enable Description 
For each circuit on the card, indicates whether power-up diagnostics are 
enabled. 
Foreach circuit on the card, indicates whether background diagnostics 
are enabled. 
Page2 of2 
Maintenance Device Work Area 
4.6 When a card is first programmed, a maintenance device work area is assigned for it. 
This work area can be accessed by two softkeys: MT-DWA and MT-DWA-MEM. 
MT-DWA - gives an English format of the status of the diagnostics of the main- 
tenance work area 
MT-DWA-MEM - is a hexadecimal memory dump of the contents of the mainte- 
nance device work area 
Figure 4-i shows a typical display of a Maintenance Device Work Area. Definitions of 
the terms used in the screen display follow Figure 4-l. 
lo:04 AM 23-APR-90 
alarm status = NO ALARM 
CARD DATA DEV STATUS BGR PWR BGR SYS PUP FIS PRT FRT 
USR 
DEVPLID: 11 50 1 
CARD TYPE: ONS 2 
CARDSTAT INSTLD 3 
NUM CCTS: 12 4 
5 
DEVSWlD:MTCARDl9 6 
DWA ADD: 1336CO 7 
CMOS ADD: OE49 OlA6 
8 AVAIL 
ON OFF 1 0 0 0 
0 0 0 
AVAIL ON OFF 1 0 0 0 0 0 0 
AVAIL 
ON OFF I 0 0 0 
0 0 0 
AVAIL 
ON OFF 1 0 0 0 
0 0 0 
AVAIL ON OFF 10 0 0 0 0 0 
AVAIL ON OFF 1 0 0 0 0 0 0 
AVAIL ON OFF 10 0 0 
0 0 0 
AVAIL ON OFF 10 0 0 0 0 0 
CARD RED 12 0 0 0 0 0 0 
l- 
6- MTCE WORK AREA 
2- 
3- 4- 5- CANCEL 
7- 
8- 9- MORE-DEVICES 0- RETURN 
Figure 4-l Maintenance 
Device Work Area 
4-4 Issue 1 Revision 0 March 1997