Nortel Meridian 1 General Maintenance

8/4/2019 Nortel Meridian 1 General Maintenance

1/68

SL-1Meridian 1Gene ra l ma in tenance in fo rma tion

Publication number: 553-3001-500Document release: 8.0Document status: StandardDate: April 1, 1994

1990 Northern TelecomAll rights reserved.

General maintenance information 553-3001-500


2/68

ii

Revision historyJanuary 29,1990 Standard, release 1.0.February 28, 1990 Standard, release 2.0.July 31,1990 Standard. release 3.0.December 1, 1991 Standard, release 4.0. This document is reissued to include technical content

updates. Due to the extent of the changes, revision bars are not used.December 31, 1992 Standard, release 5.0. This document is reissued to include information on

system option 81 and equipment required for compatibility with X II release18. Only new information and changes to technical content are noted byrevision bars in the margins.

April 1, 1993Standard, release 6.0. Changes to technical content are noted by revision barsin the margins.

August 1, 1993Standard, release 7.0. Changes to technical content are noted by revision barsin the margins.

April 1, 1994Standard. release 8.0. This document is reissued to include the information onMeridian I option 61C. Changes to technical content are noted by revisionbars in the margins.



3/68

iii

ContentsAbout this document 1References .Precautions 3General precautions 3Circuit cards . . . . . . . . . . 4Data disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Communicating with the system. . . . . . . . . . . . . . 9System terminal 9

Message format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Local and remote access I IOptions 61C and 81 terminal and modem guidelines 12

Maintenance telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Routine maintenance 17Pedestal air filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Option 21E battery pack assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17DC-power battery systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Hardware maintenance tools . . . . . .. 19Circuit card features .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Battery backup for CPU memory 19Card test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Enable/disable switch 20LED................................................. 20Maintenance display code .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22



4/68

iv ContentsCPU controls 26

Initialize button :. . . . . . 26Normal/maintenance switch 26Reload button 28

System alarms 28Major alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Remote alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

System monitor indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32NT7D15 System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 32NT8D22 System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 33Line transfer 35Main power loss 37Module power supply failure 37Temperature alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Software maintenance tools 41Diagnostic programs 41

Error Monitor 42Initialize Program 42Midnight and Background Routines . . . . . . . . . . . . . . . . . . . . . . . . 43Overlay Loader . . . . . . 45Overload Monitor 45Resident Trunk Diagnostic . . . . . . . . . . . . . . . . . . 45System Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Options 61C and 81 features 47The History File feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Interactive diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

The Enhanced Maintenance feature 49Manual continuity tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

User reports 53Technical assistance service 55



5/68

v

List of figuresFigure IStatic discharge pointsFigure 2Disk position

4

7Figure 3Local and remote access to a system terminal 12Figure 4Modem to a switch box and SOl and CPIO ports 13Figure 5Sample enable/disable switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 6Sample LED indicator 23Figure 7Sample maintenance display 25Figure 8Manual initialize button and normal/maintenance switch on the CPUinterface card 27Figure 9Reload button on the changeover and memory arbitrator cardFigure 10NT8D22 System Monitor message flow

29

34Figure IIPFTU configurations 36



6/68

vi List of figuresFigure 12Power equipment designations from the master NT8D22 System Monitor 39Figure 13Manual continuity tests: point-to-point configurations . 51Figure 14Manual continuity tests: loop back configurations . . . . . . . . . . . . . . . . 52



7/68

vii

List of tablesTable ISystem message format 10Table 2Translation from keyboard to dial pad 16Table 3Sample LED indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Table 4Circuit cards with maintenance displays 24Table 5Faults monitored by the NT8D22 System MonitorTable 6Programs used in Midnight and Background Routines

33

44Table 7User report indications 54Table 8Technical service emergency classifications 56Table 9Technical service non-emergency classifications 57Table 10Checklist for service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58



8/68

viii List of tables



9/68

1About this document

This document describes maintenance features for Meridian 1 system options21A, 21, 21E, 51, 61, 61C, 71, and 81. The chapters in this document describethe following:

Precautions: guidelines to avoid personal injury and equipment damageCommunicating with the system: methods for exchanging informationwith the systemRoutine maintenance: requirements for servicing batteries and air filtersHardware maintenance tools: descriptions of circuit card hardware, CPUcontrols, system alarms, and system monitor indicatorsSoftware maintenance tools: descriptions of diagnostic programs, theHistory File, and interactive diagnosticsUser reports: problems typically reported by usersCustomer technical assistance service: information on Northern TelecomTechnical Assistance Centers and services

This document does not provide procedures for locating faults, clearingfaults, or replacing equipment. See Fault clearing (553-3001-510) to locateand clear faults. See Hardware replacement (553-3001-520) to replace faultyequipment.

ReferencesSee the Meridian I planning and engineering guide for

Master index of publications (553-3001-000)System overview (553-3001-100)Equipment identification (553-3001-154)



10/68

2 About this document

See the Meridian I installation and maintenance guide forSystem installation procedures (553-3001-210)Circuit card installation and testing (553-3001-211)Telephone and attendant console installation (553-3001-215)Fault clearing (553-3001-510)Hardware replacement (553-3001-520)

See the XII software guide for an overview of software architecture,procedures for software installation and management, and a detaileddescription of all XII features and services. This information is contained intwo documents:

XII software management (553-3001-300)XII features and services (553-3001-305)

See the XII input/output guide (553-3001-400) for a description of alladministration programs, maintenance programs, and system messages.



11/68

Precautions3

General precautionsMeridian 1 equipment is sensitive to static electricity and environmentalconditions. Follow the precautions in this chapter to avoid personal injury orequipment damage.

WARNINGModule covers are not hinged; do not let go of the covers. Lift coversaway from the module and set them out of your work area.

WARNINGTo avoid the danger of electric shock, be very careful when you workwith power equipment and connections. Warning notices are displayedand must be heeded.There are no user repairable components or assemblies in the powersystem. If a power unit fails, the complete unit must be replaced. Donot disassemble a power unit under any circumstances because of therisk of electric shock.



12/68

4 Precautions

Circuit cardsWARNING

Circuit cards may contain a lithium battery. There is a danger ofexplosion if the battery is incorrectly replaced. Do not replacecomponents on any circuit card; you must replace the entire card.

Dispose of circuit cards according to the manufacturer's instructions.

To avoid damage to circuit cards from static discharge, wear a properlyconnected antistatic wrist strap when you work on Meridian 1 equipment. Ifa wrist strap is not available, regularly touch one of the bare metal strips in amodule to discharge static. Figure 1 shows the recommended connectionpoints for the wrist strap and the bare metal strips you should touch.Figure 1Static discharge points

- - - - - - - >

Modulerear

Wrist strapconneltion point Bare mral strip;/f Power supply slot \, ", , :"::'.',1 II Module IWrist strap front Bare metal str ipconnection point

553-5000



13/68

Precautions 5

Handle cards as follows:Handle cards by the edges only. Do not touch the contacts orcomponents.Set cards on a protective antistatic bag. If an antistatic bag is notavailable, hand-hold the cards, or set them in card cages unseated fromthe connectors.Unpack or handle cards away from electric motors, transformers, orsimilar machinery.Store cards in protective packing. Do not stack cards on top of each otherunless they are packaged.Store cards in a dry, dust-free area.

During repair and maintenance procedures do the following:Insert cards into compatible slots only.Turn off the circuit breaker or switch for a module power supply beforethe power supply is removed or inserted.Note: In AC-powered systems, capacitors in the power supply mustdischarge. Wait five full minutes between turning off the circuit breakerand removing the power supply from the module.Software disable cards, if applicable, before they are removed orinserted.Hardware disable cards, whenever there is an enable/disable switch,before they are removed or inserted.Return defective or heavily contaminated cards to a repair center; do nottry to repair or clean them.



14/68

6 Precautions

Data disksMake sure disks are labeled with the software generic and issue number if youremove them from the system.Follow the precautions below to avoid damaging disks:

Handle only the hard surface of the disk; never touch the recordingsurface.Keep disks away from strong magnetic fields.Avoid exposing disks to extreme heat, rapid changes in temperature, orhigh humidity.Store disks in a suitable container.

Before installing a new disk do the following:Check the disk identification to make sure it is the correct disk. Comparesoftware options with the data cartridge.Look for any damage to the disk.Make sure the arrow on the label is pointing up and the rounded corneron the disk is on the bottom (see Figure 2).

CAUTIONThe disk drive can be damaged if an upside-down disk is forced intothe slot. If there is significant resistance when you try to insert a disk,remove the disk and check the position.

For more detailed information on data disks, see X II software management(553-3001-300).

Note: No maintenance or cleaning is required on the disk drives.



15/68

Precautions 7Figure 2Disk position

Top - arrow pointing up

Bottom - rounded corner553-5001

Insert inthis direction~



16/68

8 Precautions



17/68

9

Communicating with the systemYou can exchange information with the system through system terminals andmaintenance telephones. This chapter discusses these tools forcommunicating with the system.

Note: Before XI I release 19, only one device at a time cancommunicate with the system. Accessing a device while another islogged in will log out the device that was already connected. The MultiUser Login feature, available with XI I release 19 and later, allows morethan one device to interact with the Meridian I. Refer to X II systemmanagement application (553-300 I-30 I) for details on using thisfeature.

System terminalYou can send maintenance commands and receive system messages (statusand error messages) by accessing the central processing unit (CPU) throughan RS-232 device, such as a video display terminal (VOT) or teletypewriter(TTY).For most system options, only the code is displayed or printed when the CPUsends system messages. For the interpretation of the code and any requiredaction, refer to the X II input/output guide (553-300 I-400). Option 61C andoption 81 provide the code, a plain text explanation, and required actions.Before X I I release 18, if the same data is printed on more than one port. thethroughput of each port is equal to the speed of the slowest device. If. forexample, a traffic report is printed on two ports, one configured for 9600 baudand the other for 300 baud, the effective throughput of both ports is 300 baud.



18/68

10 Cammunicating with the systemXII release 18 and later provide enhanced I/O huffering (independentthroughout). With this capahility, devices with higher baud rates run fasterthan devices that are limited to slower speeds.

Message formatThrough the system terminal, you can enter commands that tell the system to.perform specific tasks; the system performs the tasks and sends messageshack to.the system terminal, indicating status or errors. System messages,along with indicators such as maintenance display codes and light emittingdiode (LED) indicators, identify faults in the system.System messages are codes with a mnemonic and number, such as PWR0014.The mnemonic identifies an overlay program or a type of message. Thenumber identifies the specific message. Table 1 gives an example of theformat for a system message.Table 1System message format

System message: InterpretationPWROO14PWR This message (generated by the systemmonitor) indicates power and temperature

status or failures.0014 This message means the system monitor faileda self-test.

With option 61C and option 81, system messages generated from the CoreCommon Equipment Diagnostic (LD 135) and the Core Input/OutputDiagnostic (LD 137) include the interpretation and any action required. Forexample, if a CPU test from LD 135 fails, the message displayed is"CCED200 CPU test failed Check the CP card."See the XII input/output guide (553-3001-400) for a description of allmaintenance commands and the interpretation of all system messages.



19/68

Communicating with the system 11

Local and remote accessA terminal or a modem must remain permanently connected to an SDI port ina network slot to provide a constant I/O interface to the system. Althoughonly one device can communicate with the system at a time, many devicescan be installed at local and remote locations.When a system terminal is installed locally, it is connected directly to a serialdata interface (SDI) card, located within a module. When a system terminalis installed at a remote location, modems (or data sets) and a telephone lineare required between the terminal and the SDI card.For a modem connection to the Meridian 1, Bell 103/212 compatible dumbmodems are recommended for all systems, except options 61C and 81.

CAUTIONIf a Hayes command-set compatible (smart) modem is used at theMeridian 1 end, you must select the dumb mode of operation,Command Recognition OFF and Command Echo OFF, beforeconnecting the modem to the SDI port. Refer to the modeminstructions to set the mode of operation.

If a printer is connected to an SDI port (locally or remotely), you must disableXON/XOFF flow control so that no characters or signals are sent to the port,to avoid a "ping-pong" effect.Figure 3 shows typical system terminal configurations. See "Access throughthe system terminal" in Fault clearing (553-3001-510) or Hardwarereplacement (553-3001-520) for the access procedure.For information specific to option 61C and option 81, see "Options 61C and81 terminal and modem guidelines" on page 12.



20/68

12 Communicating with the system

Figure 3Local and remote access to a system terminal

Meridian 1

Loca l accesss y st em t er m in a l

Options 61C and 81 terminal and modem guidelinesEach NT6D66 Call Processor (CP) Card provides a data terminal equipment(DTE) port at J21 and a data communication equipment (DCE) port at J25 onthe Core and Core/Network Module I/O panel. The designations DTE andDCE refer to the function of the port, not the type of device that connects tothe port. Therefore, a modem (which is DCE) connects to the DTE port at J21,and a terminal (which is DTE) connects to the DCE port at J25.

Remote accesssystem terminal

modem

telephone l ine

5533000

The input/output ports on the CP card (CPIO ports) are used for access to theCore or Core/Network Module, which houses the card. The CPIO ports areactive only when the Core associated with the CP card is active. Therefore,the CPIO ports should not be used as the only I/O connection for the system.

Note: For correct operation, terminals used with options 61C and 81must be set to 9600 baud, 7 data, space parity, one stop bit, full duplex,XON.



21/68

Communicating with the system 13Figure 4 shows the recommended configuration for remote maintenancemonitoring on option 81, which also applies to option 61C. In thisconfiguration, a switch box is normally set to the SDI port to remotelymonitor general system operation. The CPIO ports can be accessed fordebugging and patch downloading (through your Northern Telecomrepresentative).

Figure 4Modem to a switch box and SOl and ePlo ports

Dumb mode modem553-5809

Note, ThA AO::l77!'l!'l::> swltnh hnl


22/68

14 Communicating with the systemSee "Options 61C and 81 terminal and modem connections" in Systeminstallation procedures (553-3001-210) for detailed information onconfiguring and connecting terminals and modems with options 61C and 81.

Note: The A0377992 Black Box ABCDE-Switch, A0381391 UDSFastTalk modem, and cables required for the configuration are availablethrough Northern Telecom.

Modems must meet the following required specifications to be compatiblewith option 61C and option 81. Modems that meet the followingrecommended specifications must also meet the required specifications.

Required: true, not buffered, 9600 baud support (required for remoteNorthern Telecom technical support)Required: CCITT V.32 or V.32bis complianceRecommended: the ability to adjust to lower and higher speeds,depending on line quality, while maintaining 9600 baud at local DTERecommended: VA2 error correctionRecommended: VA2bis data compression

The following models have been tested and verified as compatible withoption 61C and option 81:

Hayes V-series ULTRA Smartmodem 9600UDS FastTalk V.32/42b (available through Northern Telecom)US Robotics Courier HST Dual Standard V.32bis

A dispatch or call back modem, normally connected to the SDI port, can beused if it meets the requirements listed above. If you want to use a modem ofthis type that does not meet the requirements, the modem can only be used inaddition to a modem that does meet specifications.



23/68

Communicating with the system 15

Maintenance telephoneA telephone functions as a maintenance telephone when you define theclass of service as maintenance set allowed (MTA) in the Multi-lineTelephone Administration program (LD11). A maintenance telephone allowsyou to send commands to the system through the following maintenanceoverlays: LD 30, LD 32, LD 33, LD 34, LD 35, LD 36, LD 37, LD 38, LD41, LD 42, LD 43, LD 45, LD 46, LD 60, LD 61, and LD 62.

Note: The Core Common Equipment Diagnostic (LD 135) and Core I/ODiagnostic (LD 137) are among the overlays that cannot be accessedthrough a maintenance telephone.

You can test tones and outpulsing through the maintenance telephone.Specific commands for tone testing are given in the Tone and Digit Switchand Digitone Receiver Diagnostic (LD 34).To enter commands on a maintenance telephone, you press the keys thatcorrespond to the letters and numbers of the command (for example, to enterLD 42 return, key in 53#42##). Table 2 shows the translation from a terminalkeyboard to a telephone dial pad.See "Access through the maintenance telephone" in Fault clearing(553-3001-510) or Hardware replacement (553-3001-520) for the accessprocedure.



24/68

16 Communicating with the systemTable 2Translation from keyboard to dial pad

Keyboard Dial pad1 1

A B C 2 20 E F 3 3G H I 4 4J K L 5 5M N 0 6 6P R S 7 7T U V 8 8W X Y 9 9

0 0Space or # #

Return ##* *

Note: There is no equivalent for Q or Z on a dial pad.



25/68

17Routine maintenance

You must service batteries and air filters regularly. Follow the guidelines inthis chapter to maintain batteries and air filters.

Pedestal air filterThere is an air filter in the pedestal of each column (in all options except21A). Service the air filters once a month. For instructions on replacing theair filter, see Hardware replacement (553-3001-520).If an air filter is damaged in any way, discard it and install a new one. Ifa dirtyair filter is not damaged, you can clean it with warm water and mild detergent.(Do not use compressed air because it may damage the filter.) When the filteris completely dry, you can reinsert it in the pedestal or store it as a spare.

Option 21E battery pack assemblyAn A0378252 Battery Pack Assembly on the NTND02 Misc/SOI/PeripheralSignaling (MSPS) Card is used in option 21E. The battery is constantlyrecharged through a trickle charging circuit on the NTNDO 1 IntegratedCPU/Memory (ICM) Card.You can run a battery checking routine manually using the command BATTin the Common Equipment Diagnostic (LD35), or as part of the midnightroutines. A battery failure generates system message CED503.Replace the battery pack every three years, even if no battery failures haveoccurred. For instructions on replacing the battery pack assembly, seeHardware replacement (553-3001-520).



26/68

18 Routine maintenance

DC-power battery systemsExternal batteries, often used with DC-powered systems, gener-ally requireregular visual inspections. They may also require charger or rectifier tests andpilot cell tests. Perform all inspections and tests according to the supplier'sinstructions.To comply with safety requirements, consult the following articles beforeworking with any battery systems:

Read the "Material Safety Data Sheet" that must be posted to meetOccupational Safety and Health Administration (OSHA) requirements.This article outlines appropriate reserve battery handling procedures.Refer to National Electric Code 645-10. This article outlinesrequirements that call for the installation of AC- and DC-power killswitches to battery systems in certain environments.



27/68

19

Hardware maintenance toolsThere are fault indicators and hardware features that help you performmaintenance tasks (particularly identifying and clearing faults). Thesemaintenance tools include the following:

circuit card features that include card level tests and status indicatorsCPU controls that allow you to control common equipment functionssystem alarms that categorize the severity of a system failuresystem monitor indicators that identify power and temperature faults

Circuit card featuresBattery backup for CPU memory

The NTND02 MSPS Card, used in option 21E, is equipped with theA0378252 Battery Pack Assembly. If power to the system is lost, the batteryretains CPU memory for up to 60 minutes.

Card testA card test checks to see that a card is working correctly. Many cards performa self-test on power-up. You can also force card-level tests through softwarecommands.



28/68

20 Hardware maintenance tools

Enable/disable switchSome cards have a switch on the faceplate that enables or disables thehardware for that card.When you remove a card, whenever possible disable the software, thendisable the hardware by setting the switch to Dis.Hardware disable a card (set the switch to Dis) before you install it. After thecard is locked into position, set the switch to Enb then enable the software.Software disable and enable cards as described in the XII input/output guide(553-3001-400).Figure 5 shows the typical location of an enable/disable (Enb/Dis) switch.

LED Many cards have one or more light emitting diodes (LEDs) on the faceplate.The LED gives a visual indication of the status of the card or of a unit on acard.When a green LED is steadily lit, it indicates the card is operating normally.When a green LED is off, it indicates the card is disabled or faulty.When a red LED is steadily lit, it indicates the card, or a unit on it, is disabledor faulty. When a red LED is off and power is available to the card, it indicatesthe card is operating normally.

Note 1: The shape of the LED (some are round and some arerectangular) does not indicate a different function.Note 2: In option 61C and option 81, the red LEDs on the NT6D65 Coreto Network Interface (CNI) Cards are lit when the associated Core isinactive. This is normal operation.

When intelligent peripheral cards are installed, the red LED on the faceplateremains lit for two to five seconds while a self-test runs. (The time requiredfor the self-test depends on the type of card.) If the test is successful, the LEDflashes three times and remains lit until the card's software is configured andenabled, and then the LED goes out. If the LED does not follow the patterndescribed or operates in any other manner (such as continually flashing orremaining weakly lit), the card should be replaced.



29/68

Hardware maintenance tools 21Figure 5Sample enable/disable switch

Enable/disableswitch

II 553-3003



30/68

22 Hardware maintenance toolsIn option 61C and option 81, when Core common control cards are installed,a self-test runs. If the self-test is successful, the LED flashes three time, thengoes out.Table 3 gives two examples of LED indications.Table 3Sample LED indications

Type of card LED color StatusCommon equipment green LED lit = operation normalpower supplyDigital line card red LED lit = disabled

Figure 6 shows the location of the LED on the faceplate of an intelligentperipheral line card.

Maintenance display codeMaintenance displays are located on the faceplate of some circuit cards. A

Ihexadecimal code is displayed. Interpretations of the maintenance displaycodes are listed under "HEX" in the XII input/output guide (553-3001-400).You should examine previous codes, system messages, and visual indicatorswith any current maintenance display codes to properly analyze faults.In option 61C and option 81, the maintenance display on the NT6D66 CallProcessor (CP) Card shows two lines of information with up to 16 charactersper line. The hexadecimal code and its definition are shown on the display.Each new code shown on a maintenance display overwrites the one before it.However, note the following:

All codes received on common equipment displays are recorded. Youcan review them by printing the History File.



31/68

Hardware maintenance tools 23Figure 6Sample LED indicator

LED

553-3004



32/68

24 Hardware maintenance toolsThe most recent 16 codes displayed on a controller card stay in memory.You can review them and reset the counter through the Network andSignaling Diagnostic (LD30).In option 61C and option 81, the most recent 64 displays on a CP cardstay in memory. You can review the displays on the active CP cardthrough the Core Common Equipment Diagnostic (LD135).

Table 4 lists the cards with maintenance displays and the type of informationthe codes indicate on each card. Figure 7 shows the location of themaintenance display on the faceplate of a floppy disk interface card.

Table 4Circuit cards with maintenance displays

System options Circuit card Display indication(for ali related cards)- 21A,21 - NT8D19 Sysload (system reload) statusMemorylPeripheral Interrupt faultsSignaling Card Memory faults- 21E - NTND01 ICM Card Common equipment hardware faults- 51, 61, 71 - QPC580 CPU InterfaceCard- 61C,81 - NT6D66 Call ProcessorCard- 21A,21, - QPC742 Floppy Disk Faults on the disk drive unit21E,51,61 Interface Card Faults on the disk drive interface card- 51,61,71 - QPC584 Mass StorageInterface Card- 61C, 81 - NT6D63 1/0 ProcessorCard- 21,21 E, - NT8D01 Controller Card During normal operation, display shows

51,61, self-test codes and port number on61C, 71,81 which controller clock is tracking



33/68

Hardware maintenance tools 25Figure 7Sample maintenance display

Two-digitmaintenancedisplay

553-3001

General maintenance information 553-3001 -500


34/68


CPU controlsSwitches and buttons on common equipment cards allow you to-control CPUactivity and clear common equipment faults.

Initialize buttonPressing the manual initialize (Man Int) button associated with the activeCPU starts the Initialize Program. The Initialize Program clears commonequipment faults and then rebuilds call-dependent data and generates systemmessages indicating the status of the system. This process is called aninitialization. Call processing is briefly interrupted during an initialization.Manual initialize buttons are located on the following cards:

In options 21A and 21, the initialize button is on the NT8D19Memory/Peripheral Signaling Card.In option 21E, the initialize button is on the NTNDOI ICM Card.In options 51,61, and 71, the initialize button is on the QPC580 CPUInterface Card.In option 61C and option 81, the initialize button is on the NT6D66 CallProcessor (CP) Card.

Normal/maintenance switchThere is a normal/maintenance (Norm/Maint) switch on the QPC580 CPUInterface Card and the NT6D66 CP Card. In dual CPU systems (options 61,61C, 71, and 81), you use this switch as follows to keep the dual CPUs fromswitching, or trying to switch, when you are testing or replacing commonequipment hardware on the inactive CPU:

On the CPU you are not testing or replacing, set the switch to Maint. ThisCPU will be active.On the CPU you are testing or replacing, set the switch to Norm. ThisCPU will remain inactive as long as the other CPU is set to Maint.

For regular operation in dual CPU systems, set both normal/maintenanceswitches to Norm. For option 51 (a single CPU system), set the switch toMaint.Figure 8 shows the location of both the manual initialize button and thenormal/maintenance switch on the QPC580 CPU Interface Card.



35/68

Hardwaremaintenance tools 27Figure 8Manual initialize button and normal/maintenance switch on the CPUinterface card

Normal/maintenanceswitch

Manual initializebutton

~-I

I 553-3005General maintenance information 553-3001 ~500


36/68


Reload buttonReload (RId or Man Rst) buttons allow you to manually activate the SystemLoader program. The System Loader initiates call processing and startsmemory-checking diagnostics. This process is called a sysload or systemreload. Here are the locations of the reload button for the various options:

In options 21A and 21, the reload button is on the QPC687 CPU Card.In option 21E, the reload button is on the NTNDOI ICM Card.In option 51, the reload button is on the NTNDlO Changeover andMemory Arbitrator (CMA) Card (or QPC581 before XU release 18).In options 61 and 71, the reload button is on the NTNDlO (or QPC581)CMA Card. To start a sysload, you must simultaneously press the reloadbutton on both CMA cards.In option 61C and option 81, the reload button (Man Rst) is on theNT6D66 CP Cards. To start a sysload, you must simultaneously press thereload buttons on both CP cards.

Figure 9 shows the location of the reload button on a QPC581 CMA Card.

CAUTIONActive calls are disconnected and the system goes into an emergencyline transfer state during a sysload. Use the reload button only if youare specifically instructed to do so in Northern Telecom Publications.

System alarmsSystem alarms are based on various fault monitors and indicators. Thecategory of the alarm - major, minor, or remote - indicates the severity of thesystem failure:

A major alarm requires immediate action by the technician.A minor alarm requires attention, but not necessarily immediateattention, by the technician.A remote alarm may require attention by the technician.



37/68

Hardware maintenance tools 29

Figure 9Reload button on the changeover and memory arbitrator card

II5533006



38/68


Major alarmsA major alarm indicates a fault that seriously interferes with call processing.The following faults cause a major alarm:

CPU or control bus failuredisk system failure when attempting to load the systemsystem power failure (without reserve power)temperature fault (excessive heat)

When there is a major alarm, the red LED at the top of the affected columnlights. A major alarm also activates a display on all attendant consoles.When a Meridian 1 is equipped with a power failure transfer unit, a majoralarm causes designated 500/2500 telephones to connect directly to CentralOffice trunks; this is called a line transfer. Minor alarmsA minor alarm indicates the system hardware or software has detected a faultrequiring attention. The following faults cause a minor alarm: Automaticidentification of outward dial (AIOD) trunk failure

conference failuredigitone receiver failurememory failuremore than one fault on different line and trunk cards in one shelf(indicated on affected customer's console only)network failure (indicated on affected customer's console only)peripheral signaling failureserial data interface failuretone and digit switch failure



39/68


A minor alarm displays an alarm on attendant consoles in customer groupsaffected by the fault. (A minor alarm indication on the console is an optionalfeature, enabled and disabled on a customer basis through data administrationprocedures.)

Remote alarmsA remote alarm is an optional extension of a major alarm to another location,such as a monitoring or test center, or to an indicator, such as a light or bell.When a major alarm occurs, the Meridian 1 provides relay contact closureacross two remote alarm lines, REMALMA and REMALMB. These lines areextended to the main distribution frame (MDF) through the system monitorto MDF cable for customer use. The relay contacts are rated at 30 V de and 2amps. The REMALMB line is the return or ground for the REMALMA line.Northern Telecom does not extend remote alarm lines beyond the MDF.



40/68


System monitor indicatorsThe system monitor checks the column temperature, cooling system status,and system voltage status and controls line transfer states accordingly.

NT7D15 System MonitorSystem option 21A is equipped with the NT7D15 System Monitor, which isa paddle board installed on the rear of the backplane. This system monitorperforms the following:

If the main circuit breaker in the system trips (for example, if there is apower surge or short circuit), the system monitor starts a line transfer andsends a remote alarm signal.If the temperature of the column reaches 70 degrees C (158 degrees F),the system monitor trips the main circuit breaker, starts a line transfer,and sends a remote alarm signal.If the power supply loses +5 volts, the system monitor starts a linetransfer and sends a remote alarm signal.If the power supply loses any voltage other than +5 volts, the systemmonitor lights the column LED, sends a major alarm indication to theCPU, and sends a remote alarm signal.If call processing stops, the system monitor lights the column LED andstarts a line transfer.Note: The NT7D15 System Monitor does not generate systemmessages.

When major system failures occur, the system monitor sends a remote alarmsignal. As an option, an indicator, such as a bell or light, can be connected tothe system monitor to receive the remote alarm signal.



41/68


NT8D22 System MonitorSystem options 21, 21E, 51, 61, 61C, 71, and 81 are equipped with theNT8D22 System Monitor, which is installed in the rear of the pedestal in eachcolumn. Table 5 lists faults monitored by this system monitor.

Note: The NT8D15 System Monitor must be used in option 21A. Inmultiple-column systems, there is one master system monitor, located inthe column with CPU 0, and multiple slave system monitors. A switchsetting on each system monitor defines the master or the address of eachslave.

Table 5Faults monitored by the NTBD22 System Monitor

Power faults SourceCPU condition CPU failure

Sysload (system reload)Main power loss System input power, AC or DCPower supply failure Common equipment power supply

Common/peripheral equipment powersupplyPeripheral equipment power supplyRinging generator

Temperature alarm Blower unitColumn temperature sensors

The master system monitor checks the CPU column and periodically polls theslaves to check their status. When polled, the slaves report their status to themaster. If a slave does not respond when it is polled, the master reports theaddress as a faulty slave.If a slave is removed, the master cannot communicate with higher addresses.Therefore, the master considers the removed slave and all slaves with a higheraddress as disabled. For example, if slave 2 is disabled, the master also reportsslaves 3, 4, and up as disabled.



42/68

34 Hardware maintenance toolsThe system monitor reports power equipment status and faults to the CPU.(Only the master system monitor communicates with the CPU.) Systemmessages generated by the system monitor are identified by the-mnemonicPWR. Figure 10 shows the flow of messages from NT8D22 System Monitorsto the system terminal.If there is a fault, the system monitor lights the LED on the affected column.

Figure 10NT8D22 System Monitor message flow

Serial datainterface ~(SDI)

Systemterminal Fault sources to mastersystem monitor

CPU faultMain power lossPower supply failureTemperature alarms

Mastersystem ~monitor

System Serial dataCPU 4- interface"'_(SDI)

-I"I 1st slave Fault sources to slaveI system ~ system monitormonitor CPU faultI Main power lossPower supply failure

L Last slave Temperature alarms- systemmonitor553-3007



43/68


Line transferAs an option, you can connect one or more power failure transfer units(PFTUs) to the Meridian 1.Each PFTU connects up to eight designated500/2500 telephones to Central Office trunks. If call processing stops, those500/2500 telephones are transferred through the PFTU to the Central Officeso that you still have outside connections. A line transfer occurs during thefollowing situations:

during a sysload (system reload)if there is a major power failure in a DC-powered system (as detected bythe TRIP signal)if call processing stops because of a CPU failureif there is a loss of power to the columnif there is a loss of power to the PFTUif the temperature in a column is too highif a line transfer button on the attendant console is pressed (this applieson a customer basis)if a line transfer switch on the PFTU is turned onNote: Ifposition 4 on switch 1 (SW1) is set to OFF on a system monitor,that system monitor's column will not activate a line transfer if thetemperature is too high.

Figure 11 shows four ways multiple-column systems and PFTUs can beconfigured. You can configure in the following ways:

connect all the columns in a system to a single PFTUconnect each column to an individual PFTUcombine connecting individual columns to individual PFTUs andmultiple columns to a single PFTUattach additional PFTUs to a PFTU that is connected to one or multiplecolumns



44/68

36 Hardware maintenance toolsFigure 11PFTU configurations

r - P F ~ U J[ / = ' r - ~t : I ~I I ~I I ~I ~ I ).All columns to one PFTU

One column to one PFTUand multiple columns to one PFTU

One column to one PFTU

i)I i

j

i:

: i ;1

I . ;,: I Ij ' Y , " ' . ,) :/PFTU with additional PFTUs attached

553-3035


" ' ) . : ; _ : - ~ -e


45/68


Main power lossThe system monitor receives status and control signals from the externalpower system. The system monitor then generates system messages thatindicate the status of main and reserve power supplies.You can connect a reserve (back-up) power supply to the Meridian 1: eitheran uninterruptible power supply (UPS) for AC-powered systems or reservebatteries for DC-powered systems. If the main source of external power islost, power to the system is maintained by the UPS or reserve batteries.If the main power supply is lost, the system monitor generates a major alarm.The NT8D22 System Monitor also generates system messages to indicate thesystem is running on reserve power.

Module power supply failureThere are four types of module power supplies:common equipment (CE) power supplycommon/peripheral equipment (CE/PE) power supplyperipheral equipment (PE) power supplyringing generator

The NT8D22 System Monitor handles complete or partial failures in amodule power supply as follows:

If the output voltage is higher than the threshold for +5 volts, the affectedpower supply shuts down, the column LED lights, and a system messageis sent.If the output voltage is higher than the threshold for other than +5 volts,power for only that voltage shuts down in the affected power supply, thecolumn LED lights, and a system message is sent.If the output voltage is lower than the threshold for any voltage, powerfor only that voltage shuts down in the affected power supply, the columnLED lights, and a system message is sent.If the input voltage is lower than the threshold, the affected power supplyshuts down and then recovers when the input level recovers.



46/68


To help you pinpoint a power supply problem, the master NT8D22 SystemMonitor identifies the following:

the column with the fault (system monitor 0-63)the module (0-3) in that columnthe power supply unit (1-2) in the module

Figure 12 shows the power equipment designations in a column.Temperature alarms

System option 21A has two fans in the top cap. If the temperature of thesystem exceeds 70 degrees C (158 degrees F), the NT7D15 System Monitortrips the main circuit breaker to prevent further overheating.

Each column in options 21, 21E, 51, 61, 61C, 71, and 81 is cooled by a blowerunit (NT8D52AB with AC power or NT8D52DD with DC power) in thepedestal. All of these systems are equipped with the NT8D22 SystemMonitor, which performs the following functions:

If there is a partial or complete failure in a blower unit, the systemmonitor lights the column LED and generates a system message.Ifthe thermostats in a column report a temperature exceeding 70 degreesC (158 degrees F), the system monitor lights the column LED, generatesa system message, then, providing this condition exists for 30 seconds,shuts down power to the column in 30 seconds.

The NT8D22 System Monitor generates a system message if the air leavingthe column exceeds 55 degrees C (131 degrees F). This thermal alarm mayindicate a loss of air-conditioning in the room, loss of ventilation in thecolumn, a problem with the blower unit, or a blocked air filter.



47/68

Hardware maintenance tools 39Figure 12Power equipment designations from the master NT8D22 System Monitor

Module 3Power unit 1

Module 2Power unit 1Power unit 2



Column 0System monitor 0

Front of the column, covers removed 553-3014



48/68




49/68

41Software maintenance toolsDiagnostic programs

Note: See "Options 61C and 81 features" on page 47 for informationspecific to option 61C and option 81.

Diagnostic software programs monitor system operations, detect faults, andclear faults. Some programs run continuously; some are scheduled.Diagnostic programs are resident or non-resident. Resident programs, such asthe Error Monitor and Resident Trunk Diagnostic, are always present insystem memory. Non-resident programs, such as the Input/Output Diagnosticand Common Equipment Diagnostic, are used as Midnight and BackgroundRoutines or for interactive diagnostics. Non-resident programs are loadedfrom the system disk and are run as scheduled or upon request.Non-resident programs are called overlay programs or loads. They areidentified by a title and a number preceded by the mnemonic for load (forexample, Trunk Diagnostic-LD 36).See the X II input/output guide (553-3001-400) for detailed information onall diagnostic programs.



50/68

42 Software maintenance tools

Error MonitorThe Error Monitor is a resident program that continuously tracks callprocessing. The Error Monitor generates system messages if it detects invalidor incorrectly formatted call- processing information.System messages generated by the Error Monitor are preceded by themnemonic ERR, which usually indicates hardware faults, or the mnemonicBUG, which usually indicates software problems. With prompt ERRM in theConfiguration Record (LD 17), you can instruct the system to print or notprint ERR or BUG messages.

Initialize ProgramThe Initialize Program momentarily interrupts call processing as it clearscommon equipment faults. It then rebuilds call-dependent data and generatessystem messages, with the mnemonic INI, that indicate the status of thesystem. This process is called an initialization.Through an initialization, you can download firmware from the CPU tosuperloop network cards and controller cards. Call processing is interruptedfor an additional amount of time during this process.You can activate an initialization by pressing the manual initialize (Man Int)button on the following:

NT8D19 Memory/Peripheral Signaling Card in options 21A and 21NTND01 ICM Card in option 21EQPC580 CPU Interface Card in options 51,61, and 71NT6D66 CP Card in option 61C and option 81

An initialization always occurs automatically after the System Loaderprogram runs. An initialization often occurs when a software or firmwarefault is detected and when a common equipment hardware fault is detected.



51/68

Software maintenance tools 43

Midnight and Background RoutinesIn the Configuration Record (LD 17), you can select the overlay programsthat will run in the Midnight Routine and Background Routine. These routinesautomatically perform maintenance checks. Programs included in theMidnight Routine are defined with the prompt DROL (derived from "dailyroutine overlay"). Programs included in the Background Routine are definedwith the prompt BKGD.

Note: A memory test must be run once a day on options 21 and 21E.Therefore, the Common Equipment Diagnostic (LD 35) runs as part ofthe Midnight Routine even if it is not programmed.

The Midnight Routine runs once everyZd hours. This routine is preset to runat midnight when a system is shipped, but you may assign a different time inthe Configuration Record. When it is time for the Midnight Routine to start,the system cancels any other program.The Background Routine runs when no other program is loaded in the overlayarea. The programs included in the Background Routine run in sequencerepeatedly until the Midnight Routine runs or there is another request to usethe overlay area (for example, if you log on to check the status of a circuitcard).You may include the programs listed in Table 6 in Midnight and BackgroundRoutines. Your maintenance requirements and the configuration of yoursystem determine the programs you include in Midnight and BackgroundRoutines.

Note: Software Audit (LD 44) should always be used in the BackgroundRoutine.



52/68

44 Software maintenance toolsTable 6Programs used in Midnight and Background Routines

Program number Program functionLD 30 Network and Signaling DiagnosticLD 32 (Midnight only) Network and Peripheral Equipment ReplacementLD 33 1.5 Mbyte Remote Peripheral EquipmentDiagnosticLD 34 Tone and Digit Switch and Digitone ReceiverLD 35 (see Not 1) Common Equipment DiagnosticLD 36 Trunk Diagnostic 1LD 37 (see Note 1) Input/Output DiagnosticLD 38 Conference Circuit DiagnosticLD 40 Call Detail Recording DiagnosticLD 41 Trunk Diagnostic 2LD 43 (Midnight only) Data Dump (see Note 2)LD 44 Software AuditLD45 Background Signal and Switching DiagnosticLD 46 Multifrequency Sender Diagnostic for ANILD 60 (Midnight only) Digital Trunk Interface DiagnosticLD 61 (Midnight only) Message Waiting Lamps ResetNote 1: For option 61C and option 81, use LD 135 instead of LD 35. Use LD 137andLD 37.Note 2: LD43 will automatically beactivated during midnight routines if changeshave beenmadewithin the past 24 hour.



53/68


Overlay LoaderThis resident program locates, loads, and checks all overlay programs. Itautomatically activates the Midnight and Background Routines. You can loadprograms manually by entering commands through the system terminal ormaintenance telephone. Once the program is loaded, you see the programmnemonic (such as TRK for Trunk Diagnostic) on the system terminal.You can also use the Overlay Loader to enable, disable, and display the statusof the disk drive unit.

Overload MonitorThe system continuously monitors the volume of system messages. If itdetects too many error messages are detected from a line or trunk card, thesystem activates the Overload Monitor program. The Overload Monitordisables the faulty card and generates system messages with the mnemonicOVD.

Resident Trunk DiagnosticThis program automatically monitors all trunk calls and records apparentfaults on each trunk. If the number of faults on a trunk exceeds the thresholdfor that trunk, the program generates a system message identifying the trunkand the type of fault.A failure on a trunk may keep the trunk from detecting incoming calls. Thethreshold mechanism cannot detect such a failure, so this program alsorecords how many days it has been since each trunk received an incomingcall. If you suspect some incoming calls are not being processed, you can usethe command LMAX in Trunk Diagnostic 1 (LD 36) to identify the trunk withthe maximum idle days.

System LoaderThe System Loader program loads all call-processing programs and data, andstarts memory-checking diagnostics. After all required programs and datahave been loaded and all checks performed, the System Loader is erased fromsystem memory, the Initialize Program runs, and normal call processingbegins. This process is called a sysload or system reload.

General maintenance information 553-3001 -500


54/68

46 Software maintenance toolsThe System Loader operates automatically on system power up or if acommon equipment or power fault destroys information in the systemmemory. For maintenance purposes, you generally activate this program onlyif call processing has stopped.You can start a sysload manually by pressing the reload (RId) button on thefollowing:

QPC687 CPU Card in options 21A and 21NTNDOI ICM Card in option 21ENTNDlO (or QPC581) CMA Card in options 51,61, and 71(simultaneously press both buttons in options 61 and 71)NT6D66 CP Card in option 61C and option 81 (simultaneously pressboth buttons)Note: The system loses the time and date during a sysload (except onoption 61C and option 81). You should reset the time and date usingLD02.

CAUTIONActive calls are disconnected and the system goes into an emergencyline transfer state during a sysload. Activate the System Loader only ifyou are specifically instructed to do so in Northern TelecomPublications.

To minimize sysload time, you can enable the Short Memory Test capabilityin LD 17 (prompt SMEM). If you enable the test, only one pass of memorytesting is performed on a normal reload. If any subsequent system failurecauses an automatic reload, the full six-pass Memory Test is performed on allsystem memory.

Note: A sysload completes so quickly on option 61C and option 81 thatthe Short Memory Test is not useful. Therefore, the package was notdesigned to be compatible with options 61C and 81.



55/68


Options 61C and 81 featuresWhen option 61C and option 81 receive a system reload signal, the sysloadoccurs in two to five minutes, depending on the size of the customer database.During the sysload, option 61C and option 81 perform a core shelf test, whichincludes self-tests on the CP and lOP cards. The results of the self-tests aredisplayed on the liquid crystal display (LCD) on the CP card, the hex displayon the lOP card, and the system terminal. On the other Core cards, the LEDblinks three times after a successful test.Options 61C and 81 typically performs an initialization in under 90 seconds.You can manually initialize only the active core side.In option 61C and option 81, the overlays reside in dynamic random accessmemory (DRAM) after they are loaded from the hard disk during an initialsoftware load (software is shipped on redundant hard disks). Since they arealways in resident memory, the overlays can be loaded quickly.Option 61C and option 81 can diagnose faults in field replaceable units for allCore hardware, including cables. In case of a failure, a message in a naturallanguage (such as English) appears on the system terminal and on the liquidcrystal display (LCD) on the CP card.If there is a hardware fault, the system attempts a recovery. In the case of aredundant hardware failure, under certain conditions option 6lC and option81 will attempt a graceful switch over to the core side without the failure.Option 61C and option 81 remote operation capabilities include remoteaccess to both Core Modules, the ability to sysload, initialize, or put thesystem in a split mode, and the ability to upload and download the customerdatabase. You can access the core complex in each Core Module through theI/O ports on the CP cards.



56/68


The History File featureIf you have a printer connected to the system, each system message is printedas it is received. Ifyou do not have a printer connected, you can use theHistory File to store a limited number of system messages in protectedmemory. The contents of the file may then be printed on demand using PrintRoutine 3 (LD 22).The messages stored are specified on a system basis and can be one or moreof the following types:

customer service changes (CSC)maintenance messages (MTC)service changes (SCH)software errors (BUG)initialization and sysload messages (INI and SYS)traffic messages (TRF)

For information on selecting the messages to be stored, see Xll features andservices (553-3001-305).The contents of the History File are erased during a sysload or if you changethe History File's length. However, because the History File is located inprotected data store, the contents survive an initialization.You can change the length of the History File with the prompt HIST in theConfiguration Record (LD 17). The maximum length of the file depends onthe amount of protected data store available, which in turn depends on thenumber of system features that require protected data store.If the History File is full, the first messages stored are replaced by incomingmessages. If this happens, the system gives a "file overflow" message at thestart of a printout so you know some information has been replaced by newermessages.



57/68


Interactive diagnosticsYou can load overlay programs, including programs called maintenanceroutines, into memory through the system terminal or maintenance telephone.This function is performed by the Overload Loader program.

Note: The programs used in Midnight and Background Routines arealso used manually as interactive diagnostic programs (see Table 6).

Maintenance routines are used interactively with a command/responseformat. In this format, you enter a command that tells the system to performa specific task. The system performs the task and sends system messagesindicating the status or errors back to you.With interactive diagnostics you can do the following:

disable, test, and enable specific equipmentverify that a reported fault still needs to be clearedverify that a repair procedure has cleared a fault

All maintenance programs, commands, and system messages are described indetail in the XII input/output guide (553-3001-400).

The Enhanced Maintenance featureSystem software sometimes requires modifications, called patches, providedby Northern Telecom Technical Assistance Centers. The command ISS inPrint Routine 3 (LD 22) prints the software generic and issue. A plus sign (+)by the issue number means a patch is in service.The Enhanced Maintenance feature does the following:

allows patches to automatically survive a sysloadpermits patches on non-resident programsrecords all patches in the systemallows data disks to be shipped with pre-loaded patches

If there is a problem with a patch, the CPU sends system messages with themnemonic EHM to the system terminal or the History File.



58/68


Manual continuity testsYou can perform manual continuity tests on superloop network cards,intelligent peripheral equipment, and Basic Rate Interface (BRI) equipment.A continuity test generates a signaling pattern at one point, monitors itsprogress, and checks for its detection at an end point. For example, when asuperloop network card sends a signal to a controller card, the continuity testverifies the following:

the superloop network card sent the signalthe loop carried the signal to the controller cardthe controller card received the signal

In a point-to-point continuity test, a superloop network card or a controllercard can generate or detect the test pattern. In loopback tests, one card, asuperloop network card, a controller card, or a multi-purpose ISDN signalingprocessor (MISP) card, is both the generator and the detector. Only idletimeslots are tested in any of the continuity tests.There are two types of loopback tests for BRI equipment. In one type of test,the pattern generated by the MISP card loops back through the digitalsubscriber loop (DSL) interface. In the other type of test, the patterngenerated by the MISP card loops back through an Sff-interface line card(SILC) or a U-interface line card (VlLC), depending on which is specified.Both types of test are accessed as Test 9, but responses to the series ofprompts for Test 9 determine the loopback point.Fifteen continuity tests can run simultaneously. When a test is completed, itstops, the status is reported, and the other tests continue running. You cancheck the status of any test at any time. When all the tests end, the number oftests run and any failed tests are reported to the CPU. You can display theresults at any time during the procedure.There are nine continuity test configurations. You can run each test byentering a set of prompts outlined in the Background Signaling and SwitchingDiagnostic (LD 45). Figure 13 shows point-to-point configurations.Figure 14 shows loopback configurations.



59/68

Softwaremaintenancetools 51Figure 13Manual continuity tests: polnt-to-polnt configurations

Pattern generator Pattern detector'--N_e_tw_o_r_k_;-------------1.~1 Controller I

TEST 1Superloopnetworkcard to controller card

TEST 2Controller card to 1 1 1superloop network card Controller 1--------------1.~ Network

TEST 3Superloop network card 1NetworkA 1 " ' 1 Network B 1to superloop network. 1-.------------1-~. .card

TEST 4Controller card tocontroller card I Con~oller 1-1-----1 ..~1 Network

ORt--- .... Iongoller I

I con~ollerH Net~ork H Ne~ork

Generalmaintenance information 553-3001-500

5533006


60/68

52 Software maintenance toolsFigure 14Manual continuity tests: loopback configurations

TEST 5Superloop network cardthrough backplane

TESTESuperloop network cardthrough controller card

TEST 7Controller card throughspecial channelTEST 8Superloop network cardthrough special channel

TEST 9BRI continuity tests:- MISP card throughDSL interface- MISP card throughSILC or UILC businterface

Pattern generatorand pattern detector Loopback point

I ~IetworkLN_e_tw_o_rk_r... ------------. backplaneNetwork I . . . ~ I Controller 1

I Controller I I I t. . . ~ _ 1 Special. r- loopbackchannel *I - - I I SpecialNetwork ""'... ----------- loopbackchannel *

MISP I - - I DSLl_~M:IS~P_ r l . .- - - - - - - - - - - - - - - - - - - ~ _ L 1 _s~~~~~~~r~

* Specialloopback channels are used to verify the integrity of the continuitygenerators and detectors. Run these tests first.

5533009



61/68

53

User reportsReports from system users often tell you about problems that the system maynot indicate. Many faults reported by users, such as a damaged telephone ordata set, are obvious and can be fixed by replacing the damaged equipment.Some faults are less obvious and may be caused by other equipment. such asa defective peripheral equipment line or trunk card. To classify the fault inthese cases, check for system messages and visual fault indications. You mayalso need to have the user reproduce the problem so you can determine thesequence of events that led to the fault.Table 7 lists problems users typically report.



62/68

54 User reportsTable 7User report indications

User report Type of fault

Major alarm reported by attendant PowerNo ring on 500/2500 telephonesMajor alarm reported by attendant Common equipmentMinor alarm reported by attendant Network equipmentUsers cannot transfer or conferenceUsers cannot dial out on 500/2500 telephonesTrouble with calls on attendant console Peripheral equipmentTrouble with calls on 500/2500 telephonesTrouble with calls on SL-1 , M1000, or digitaltelephonesUsers have trouble with a specific trunk TrunkCallers report continuous ringingTrouble with calls on console or telephones,or bothTrouble with calls Attendant consoleTrouble with equipment (such as handset,headset, or display)Trouble with calls TelephoneTrouble with equipment (such as handset oradd-on module)



63/68

55

Technical assistance serviceNorthern Telecom provides technical assistance in resolving systemproblems. To access a Technical Assistance Center. contact your NorthernTelecom representative. Services available include the following:

diagnosing and resolving software problems not covered by supportdocumentationdiagnosing and resolving hardware problems not covered by supportdocumentationassisting in diagnosing and resolving problems caused by localconditions

Several types of class-of-service are available. Emergency requests (Class EIand E2) receive an immediate response. Service for emergency requests iscontinuous until normal system operation is restored. Non-emergency requests(Class SI,S2, and NS) are serviced during normal working hours. Serviceclassifications are described further in Tables 8 and 9.Except as excluded by the provisions of warranty or other agreements withNorthern Telecom. a fee for technical assistance may be charged, at ratesestablished by Northern Telecom. Information on rates and conditions forservices are available through Northern Telecom representatives.Collect the information listed in Table 10 before you call for service.



64/68

56 Technical assistance serviceTable 8Technical service emergency classifications

Class Degree of failure SymptomsE1 Major failure causing system System out of service with complete loss ofdegradation or outage call-processing capability

Loss of total attendant console capabilityLoss of incoming or outgoing call capabilityLoss of auxiliary Call Detail Recording (CDR) inresale applicationCall processing degraded for reasons such as:- trunk group out of service- 10% or more lines out of service- frequent initializations (seven per day ormore)- inability to recover from initialization or

sysload- consistently slow dial tone (eight seconds or

more delay)E2 Major failure causing potential Standby CPU out of servicesystem degradation or outage Frequent initializations (one per day or more)

Disk drive failureTwo sets of disks inoperative



65/68

Technical assistance service 57Table 9Technical service non-emergency classifications

Class Degree of failure SymptomsS1 Failure that affects service Software or hardware trouble directly andcontinuously affecting user's service or

customer's ability to collect revenueProblem that will seriously affect service at in-service or cut-over date

S2 Intermittent failure that affects Software or hardware faults that onlyservice intermittently affect serviceSystem-related documentation errors that directlyresult in or lead to impaired service

NS Failure that does not affect Documentation errorsservice Software inconsistencies that do not affectserviceHardware diagnostic failures (not defined above)that cannot be corrected by resident skillsTest equipment failures for which a back-up ormanual alternative can be usedAny questions concerning products



66/68

58 Technical assistance serviceTable 10Checklist for service requests

Name of person requesting serviceCompany representedTelephone numberSystem option number/identificationSystem serial numberInstalled software generic and issue (located on data disk)Modem telephone number and password (if applicable)Request classification (see Tables 8 and 9)Description of assistance required



67/68


68/68

SL-1Meridian 1G en eral m ain ten an ce info rm atio nCopyright 1990 Northern TelecomA ll rights reserved.Information subject to change without notice.Release 8.0StandardApril 1, 1994Printed in the U.S.A.

Documents

Nortel Meridian 1 General Maintenance