Mitel SX-200 DIGITAL Pabx Engineering Information Manual

							General Maintenance information 
LOCAL , .._.,, .,n,. 
RS-232 CABLE 
TERMINAL 
REMOTE - DEDICATED, PUBLIC NETWORK 
RX 
TX TERMINAL 
REMOTE - DIAL-UP 
FOR AUTO-ANSWER TO DPABX VIA 
=?7-JLzJ 
_ . 
REMOTELY LOCATED 
NOTE: The Auto-Answer MODEM is 
permanently connected to ona 
local station circuit bxtension). 
7707ROE’ 
Figure 3-2 Maintenance Terminal Connection (Standard SX-200” DIGITAL Control Cabinet) 
Page 3-3  
						

							POWER FAIL TRANSFER 
,-TEST LINE JICK , ,consor.MAINTENANCE PORTS -, 
CONTROL SWITCH 
DRD”HO TIP RlNO MAINTENANCE PORT 
@ TERHIHAL SELECTION SWITCH 
NORHlL 
TEAM’HnL ‘oTE’ OH REAR OF CI\BINET  6 MOOEM ILICE, c  
						

							TOP SHELF POWER 
MAINTENANCE FORT  
						

							General Maintenance Information 
located in bay 2, slot 3, circuit 1. Refer to Section MITL9108-093- 
315-NA, Attendant Console information for information on console 
operation. 
3.07 Test Line Connectors. These connectors allow the mainte- 
nance person to access individual lines, trunks and receivers for 
testing purposes. The test line also has the capability of removing 
circuits from service, and accessing speech paths and the system 
printer. To facilitate operation of the test line, there must be an ONS 
line card installed in bay 2, slot 1. Refer to Part 7 of this Section for 
further information on the test line. 
Peripheral Cabinet Maintenance Panel 
3.08 Located at the top of the peripheral equipment cabinet is the 
peripheral maintenance panel (see Figure 3-5). This provides 
maintenance personnel with access to the power fail transfer switches 
for the peripheral equipment cabinet. These switches allow the main- 
tenance person to determine the type of failure that will cause a power 
fail transfer in the peripheral equipment cabinet. There are three op- 
tions: transfer on power supply failure, transfer on common control 
failure, or transfer on either power supply or common control failure. 
These options are s.elected by switching the POWER SUPPLY and 
COMMON CONTROL switches to the ENABLE and DISABLE positions as 
required. The MASTER SWITCH allows the maintenance person to 
manually force a power fail transfer, by switching to the TRANSFER 
position. For normal system operation, this switch should always be in 
the NORMAL position 
Important: Note that the switches labelled MAINTENANCE CONSOLE, 
CONSOLE NO. 1 and CONSOLE NO. 2 must always be in the 
DISABLE position 
System Maintenance Log 
3.09 The system maintenance log is a floppy-disk-based record of 
maintenance-related information. Any event which has the po- 
tential of affecting the functioning or the capacity of the system is 
entered into this log. There are three types of log reports possible: 
1. Fault report - A report is generated whenever Call 
Processing or the maintenance sys- 
tem detects an error or an abnormal 
condition. 
2. Reset report - A report is generated whenever a bay 
or the Main Controller is reset. 
3. Alarm level change - A report is generated whenever a 
report change in the overall system alarm 
level occurs. 
Page 3-6  
						

							General Maintenance information 
7984ROEt 
Figure 3-5 Peripheral Cabinet Maintenance Panel 
Page 3-7/T  
						

							General Maintenance Information 
4. ALARMS 
General 
4.01 Alarms are the means through which the SX-200@ DIGITAL 
PABX is able 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 anoma- 
lies-The. level of alarm is determined by the actual or potential effect 
on service that the anomalies cause. 
Alarm Levels 
4.02 There are four distinct levels of alarm defined for the SX-200@ 
maintenance system. These levels are intended to give the 
maintenance person up-to-date information on the severity of existing 
anomalies. The four alarm levels are: 
1. NO ALARM - This indicates that the system is functioning 
properly. 
2. MINOR - This indicates that there are problems af- 
fecting the system in small proportion. 
3. MAJOR - This indicates that there are problems caus- 
ing a serious systemwide degradation of 
service. 
4. CRITICAL - This indicates that there has been a total 
loss of call processing capability; an auto- 
matic power-fail transfer (PFT) is invoked. 
Alarm Categories 
4.03 There are four basic alarm categories, all relating to peripheral 
equipment. All problems affecting system performance will fall 
into one or more of these categories. Failure of other system compo- 
nents will indirectly cause failure of peripheral equipment. The cate- 
gories are: 
a Lines 
9 
Trunks 
8 
DTMF Receivers 
l PCM Channels (junctors). 
Alarm Types 
4.04 Since the SX-200@ DIGITAL PABX is modular in design, the 
Alarm Manager keeps alarm statistics in a modular fashion. For 
this reason, the alarms are divided into three types: 
1. Bay Alarms - These are the alarm levels of the 
categories specific to each separate 
bay in the system. 
Page 4-l  
						

							Gen,eral Maintenance Information 
2. Systemd Alarms - These are the alarm levels of the 
categories on a systemwide basis. 
3. Overall Alarm. - This is the overall system alarm level, 
taking into account all of the bay 
alarms and system alarms in all cate- 
gories. 
Alarm Thresholds 
4.05 For each alarm category, the thresholds represent the alarm 
level trip points; 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, however, is not a percentage, but 
rather a precise numerical valve. When the number of available devices 
falls below this number, a Critical Alarm is raised. The thresholds are 
programmable (refer to Section MlTL9108-093-351-NA); the default 
values are specified in Table 4-l. 
Note: Alarm thresholds are NOT programmable in software Generic 
1000. 
Alarm Totals 
4.66 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 main- 
tained 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. 
TABLE 4-I 
ALARM THRESHOLDS 
Page 4-X2  
						

							General Maintenance Information 
5. THE MAINTENANCE MANAGER 
General 
5.01 The Maintenance Manager is the central maintenance software 
program in the SX-200@ DIGITAL PABX system software. Its 
responsibility includes the receiving of requests to run diagnostic 
tests, managing the test schedules (queues) and initiating testing. 
Diagnostic Test Queues 
5.02 Diagnostic tests are grouped into three different categories: 
Power-up, Background and Directed. To reflect this, the test 
schedules (queues) are prioritized along the same categories. Table 
5-1 describes the queues in ascending order of priority. When the 
 Maintenance Manager schedules a device for a particular type of di- 
agnostic test, it places the device in the appropriate diagnostic test 
queue. When the maintenance person disables a diagnostic test type 
via the maintenance interface, the corresponding test requests are 
removed from the associated test queue. The priority scheme is de- 
signed to ensure that testing requested by the maintenance person via 
the maintenance terminal is handled immediately. 
TABLE 5-l 
DIAGNOSTIC TEST QUEUES 
Diagnostic Test Queue Priority 
Background Queue 
Power-up Queue 
Power-up Retry Queue 
Fault Isolation Queue 
Fault Isolation Retry Queue 
Directed Test (User) Queue Description 
This queue has the lowest priority; any device with 
background diagnostics enabled will normally be 
tested once during each pass through the system. 
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 will be 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. 
If a device could not be tested when on the Fault 
Isolation queue, it will be placed on this higher 
priority queue to be tested as soon as possible. 
This is the highest priority test queue. Devices in 
this queue will be tested immediately; results will be 
reported to initiating user port. 
Page 5-l  
						

							General Maintenance Information 
Testing 
5.03 The Maintenance Manager controls the entire test sequence on 
any device under test. The general test sequence for any pe- 
ripheral device is as follows: 
1. The Maintenance Manager locates a device with diagnostic test 
requests pending on one of the test queues. 
2. The device is requested from Call Processing for testing. If the 
device is idle, the request will be 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. 
8. If the device status has changed, this will be logged into the 
Maintenance log, and the alarm levels will be updated. 
7. Resources required for testing are released. 
8. The device is then returned to Call Processing, providing all 
tests passed. If any of the tests failed, the device will be re- 
tested; failure in this case will result in the device being re- 
moved from service. 
5.04 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 include: 
(4 
(b) 
(cl 
(d) 
(e) If Call Processing requires a device while it is being tested, the 
Maintenance Manager immediately aborts the test and releases 
the device. 
When a device fails a diagnostic test, it will be tested a second 
time to verify the fault. If it fails again, it will be removed from 
service. 
When a device fails diagnostic tests, and is subsequently re- 
moved from service, it shall remain out of service until it 
passes seven successive diagnostic tests. 
If a device scheduled for power-up or fault-isolation diagnostic 
testing cannot be tested, it will be rescheduled for testing on a 
higher priority test queue, and retried on 5 minute intervals. 
Each device may have background and/or power-up diagnos- 
tics selectively disabled by the maintenance person via the 
maintenance interface. 
Page 5-2  
						

							General Maintenance Information 
Fault Recovery 
5.05 Once a device fails diagnostic testing, it is removed from active 
service; it can no longer be used by Call Processing. There are 
three different circumstances through which the device can be re- 
turned to active service. They are: 
1. The most common method should be through the trouble- 
shooting procedures outlined in Section MITL9108-093-350-NA, 
Troubleshooting. Thisentails repairing or replacing the affected 
card. When re-installed, the device is automatically tested, and 
if it passes, is returned to service. 
2. The maintenance person has the option of returning a faulty 
device to service, should that be desirable. This is done via the 
maintenance interface (terminal, console, or testline) - see Sec- 
tion MITL9108-093-351-NA, RS-232 Maintenance Terminal. 
3. When a device fails diagnostic testing and is subsequently re- 
moved from service, the Maintenance Manager continues test- 
ing it. If a device passes seven consecutive tests after being 
removed from service, it will be returned to service. 
The Maintenance Database 
5.06 All cards that are programmed via Customer Data Entry (CDE) 
have associated with them an up-to-date status record located 
in system DRAM memory. These are known as the Maintenance Device 
Work Areas (DWA), and aid the system in determining the state of 
every device in the system at any point in time. Table 5-2 describes all 
of the information stored in the device work areas. 
Page 5-3