GTE Omni Si Database Technical Practices Manual
Have a look at the manual GTE Omni Si Database Technical Practices Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
TL-130200-1001 CARD NO. FB-17312-AFB-17314-1ATable 1.1 OMNI Sl Cards (Continued) MNEMONICDESCRIPTION RPTRRepeater Card (Note 3) MlMBMemory 1 Megabyte (Note 1) FB-20718-1ATlSSupervisory Alarm Circuit for Tl . . .FB-20771-l AINCKIntermediate Network Clock (Note 1) - FB-20922-AINCKSFB-20974-A FB-20992-A FB-20996-A FB-51051 -AFB-51267-A FB-51279-APCMTS NSDC RABR PFT PFWTA PCONFSynchronized Intermediate Network Clock (Note 1)PCM Tone Source Card (Note 1) Narrow Serial Device Controller (Notes 1, 3) Recorder Announcer Buildout Resistor Power Fail Transfer PCM Four-Wire E&M Trunk (Note 2) PCM Conference Card 1 FB-51280-A IPILT1 PCM Incoming Loop Trunk DID (Note 2) PCM Incoming Loop Trunk DID (Note 2) FB-51280-BOAPILT5210FB-100119-lPMIProperty Management System Interface (Note 1) NOTES: 1. Power to cabinet must be turned OFF before card can be removed or replaced 2. Card position must be placed in MAINTENANCE BUSY state before card can be removed 3. Cables must be disconnected from the front of the card before removing from the cabinet. 8187M-19
TL-130200-1001Power Restrictions1.4.3 There are three power restriction categories for the removal and replacement of OMNI SI printed circuit boards. PABX service may be affected as follows: l AC power ON -No interruption to PABX service l AC power OFF - Warm start required (about a 15 second system outage) lAC power off and battery pack fuse removed - Cold start required (about a ten minute system outage) Cards with peripheral service circuits (lines and trunks) may be removed and replaced while the PABX is operating. The removal and replacement of common control cards may require AC power down or AC power down with the battery pack fuse removed. Table 1.2 provides a reference between cards and the power restrictions for removal and replacement. Handling Cards1.4.4 (PCBs) Printed circuit boards require special handling during removal and storage because of their sensitivity to static electrical charges. A static discharge as low as 40 volts can damage the PCB metal-oxide semiconductor integrated and hybrid circuitry. The following procedures are used when handling a PCB: 1. A wrist strap must be worn, and it must be connected to a bare metal or plated part of the frame (screw, card guide support, etc.) when performing the following procedures: l Removing the static-sensitive PCB from the SI frame and placing it in an anti-static plastic bag. l Removing a static sensitive PCB from an anti-static plastic bag and inserting it into the frame. l Repairing static sensitive cards or handling static sensitive components. Because the human body can hold static electricity, cards should never come in contact with skin or clothing. 2. Remove static sensitive cards from anti-static packaging immediately before placing into the OMNI SI frame. 3. Static sensitive cards are stored in anti-static packaging. Card Removal and1.4.5 OMNI SI PCBs fall into the three power restrictions Replacementshown in paragraph 1.9. When removal or replacement are required, refer to Table 1.2. M-208l875210
TL-130200-1001 Table 1.2Power Restriction Status Card No.MnemonicAC ONAC OFFRemoveBattery Fuse . .FB-15277-l A FB-15278-A FB-15280-A FB-17187-A FB-17188-A SILFDC LCM PCMI TPl2 X X X XX 52101 FB-17220-BOA1 FMSD FB-17224-A FB-17225-A IFCC CIP X X X 8187M-21
TL-130200-1001Table 1.2Power Restriction Status (Continued) Card No.1 Mnemonic / AC ON 1 AC OFF / BgyT&e 1 FB-17226-A FB-17227-A FB-17228~BOA VPLC PBEiTPREX X X -FB-17229-AADMP-AX FB-17230-BOAADMP-C -X FB-17231 iA-FB-17235-A FB-17236-AUCB VCIP DVCIPX X X FB-17242-A FB-17246-A FB-17250-A FB-17251 -AFB-17254-ANIC VPLC 2 POPS PRLT PLCCX - /X X X X FB-17265-AOCAX FB-17276-A OAIODX FB-17288-A CP85EX FB-17314-l A MlMBXX FB-20718-l A TlSX FB-20771-1 AFB-20922-A FB-20974-AINCK INCKSPCMTSX X X FB-20992-A FB-51051 -AFB-51267-A FB-51279-A FB-51280-ANSDCPFTPFWTA PCONF PILTX X X X X 81875210
MAINTENANCE2.0 The OMNI SI system provides software support and COMMANDSstatus display programs that aid in system maintenance AND DISPLAYSand fault isolation. The system provides maintenance displays, maintenance commands and maintenance request commands . Maintenance displays provide records of system operations andrecords of automatic fault detection. Maintenance commands, memory access commands, and maintenance requests permit testing of devices and/or circuits and the removal of defective devices and/or circuits from operation without affecting the operation of the system. Maintenhce Displays2.1 Maintenance displays provide both general and specific--information on system operations. The displays are: . l System Status l Fault Log l Response Codes l ACA (Automatic Circuit Assurance Requests Log) l Traffic Study 0 Display Condition System Status2.1.1 System status can be displayed on the system maintenance terminal by entering the status command. The STATUS (or “ST.“) command is used. The system will respond by causing the maintenance terminal to print out the following: --------------------------------------------------------------, [STATUSI ! 07104 1236I I ) CECO i INS PECOPECl PEC2PEC3PEC4PEC5PECGPEC7MDR ESPADMP i ;OKINS UNE UNE UNE UNE UNE UNE UNE INS INS INS ;OK OK OK OK OK OK OK OK OKI I I I iN0 ALARMS PRESENTI ----_--__-_-________------------------------------------------: With an ADMP out of service: r--------------------------------------------------------------,1 STATUS.II ; 09/19 16:18 ;CECO PECOPEClPEC2PEC3PEClPEC5PECGPEC7MDRESPADMP ; ; INSINS UNE UNE UNE UNE UNE UNE UNE INS UNE 00s ; ;OKOK OK OK OK OK OK OK OK OKI I II i ALARMS PRESENTI I IL--------------------------------------------------------------, 52108187M-23
Tb-130200-1001Fault Log2.1.2 The status printout wilt show NO ALARMS PRESENT when Request Commandsthere are no faults in the system. If the printout shows that alarms are present, a printout of the fault log should be requested by executing the appropriate fault log command. The fault log is a record of the last 32 faults that were detected by the CEC.A printout of these faults is arranged in the same order that the faults occurred (earliest is first entry on the list; most recent is the last entry on the list). The commands for ,executing a fault log report are as follows: (a)To dump a fault iog, enter the following: r---m---------------------------------------------~ IFLOG INS DUMP. orI I I IFL INS. or I I II IFL INS DU. IL-------------------------------------------------~ (b)To clear a fault log, enter the following: r-------------------------------------------------~IIIFLOG INS CLEAR. orI II IFL INS CLEAR.orI iFL INS CL. orI I L-------------------------------------------------~ (c)To dump and clear a fault log, enter the following: r-------------------------------------------------~II I IFL INS DUMP CLEAR. orI I II III FL INS DU CL.I I III_---____________---_------------------------------~ Fault Log DisplayWhen a system fault occurs, a message is printed on the maintenance terminal connected to the CEC. The fault is also logged in memory so that maintenance personnel can later retrieve a recent, operational history of the system. This fault log may be displayed and/or cleared at any time via maintenance commands. The format of a fault message as printed on the terminal is shown in Figure 2.1. A key item in the fault message is the two-digit fault code. Table 2.1 lists the fault codes and their functions. M-24 a/a75210
5210Fault codes and their associated fault message printouts form the basis for system troubleshooting as described in section 5.0of this practice. A fault code quick reference chart is given in Figure 2.3. For each code, the fault title and the meaning of data stored in the CEC CPU registers are given.MONTH/DAY .~_HOUR/MINUTE . ON-LINE CEC (0) (CONTROLS ON-LINE l-l-Y) CEC REPORTING FAULT (0) (REPORTS FAULT) FAULT CODE di-d? CECX &i--6b B C D E H L xx xx xx xxxx xx IcXX = TWO HEXAIDECIMAL DIGITSREGISTER STORED--INN = TWO-DIGIT FAULT CODEDATA VALUE AT TIME OF FAULT Figure 2.1Fault Reporting Format on TTY 8f87M-25
I L-l 3uzuu- I vu I Table 2.1Fault Codes and Functions CODE FUNCTION 00BLOCK PARITY FAILURE 01DYNAMIC RAM MEMORY FAILURE 02CONTROL MEMORY READ-AFTER-WRITE FAILURE 06=- SYSTEM NETWORK TEST FAILURE. . . - 08NETWORK TEST MALFUNCTION 09DIRECTIVE TEST MALFUNCTION M-2610 .DlRECTlVE HOPPER FULL MALFUNCTION 11ILLEGAL EVENT ERROR MALFUNCTION 12READ-AFTER-WRITE FAILURE IN CHANNEL MEMORY 15Tl ALARM 1610 MS STOPPED 17ALARM FAULT 19PRE-LOADING MEMORY TEST FAILURE 20EVENTHOPPERERROR 21DIRECTIVE HOPPER ERROR 22MDR SDC FAULT 25REAL TIME CLOCK FAILURE I 271 HOTEL /HEALTH CARE DISK BACKUP FAILURE I 281 CAS MAIN/ACD AGENT DATA LINK ERROR 29CAS MAIN/ACD MESSAGE QUEUE ERROR 30ATTENDANT CONSOLE DATA CHECK ERROR 32CIP/VCIP/DVCIP CARD FAILURE 33CIP/VCIP/DVCIP PORT FAILURE 36CHANGE MDR SYSTEM CLOCK FAILURE 37SYSTEM WARM START 39ADMP INITIALIZATION AND ASSOCIATED ERRORS 40DISK FILES GV TX009/GVTXOlO (TCM/FRL) AND I/O ERRORS 41FMS DISK ERROR 42TIME SLOT LOCKUP 81875210
.- .-..--- .--. II I IREGISTER STORED DATA VALUEI I I I II I IIIII FAULT CODEI IIIBIC’ID2IE3IHILI I I I ! 00-CEC I IIf 02 = TestI Pageonwhich IAddress of Faulty ByteII Block ParityII IFailureI FailureI III failureoccurred II II IIIII 00 IO 08 I4II III=II I1 IIII III; o,:,, 09=15 ;I I .;. ;IIII II1 02=DOOA=D4 ;IIII 03=DlOB=D5 II I . . .I III II II I; 04=12 OC=l6 ;I I II II II II II; 05=13 OD=17 ;II II II 06 DZOE D6I==II tI III; 07=D3OF=D7 ;II II,I I Ol-CECI- II IIIII II I DynamicI II1 02 = Test, Pageonwhich;I failureoccurred ,Address of Faulty Byte I IIIFailure; I I MemoryI III Failure I IIIIII I III 00=1008=14 ;III III1 01 I1 09 I5,I II I II tII; &l)OA==D4 ;IIII II III, 03=DlOB=D5 ;IIIIIIIi=I6 ’III IIII II IIII 05=I3 OD:l7 I1 06=DZOE=D6III III I IIIII, 07=D3OF=D7 :III II I : 02- CECI II I III DataI Data Read IAddress of Faulty Bytei t Control MemoryIfI II II( WrittenI I; Read-After-IIIII, Write FailureI IIIIIII I,III ; 03 -CEUPECI I PEC No.IIIIII; CommonMemory I I .II DataI WrittenI Data ReadIAddress of Faulty ByteI I Read-After-I IIIIII II III I1 Write Failure : II III I I f OCCECI I Channel No.i 00 = CannotIIII IIII TotalIII Communication I lthat failedi AllocateII:I II; MessageIIII; Failure! f, BufferIIIIIIIIII IIIIII IIIIIII1 01 =TestII IIAnd I III II MessageIIIIIIII II III I ; TimeoutIIIIIIII; OS-CECII 02=MPB85 ;III SingleI IIII I ChannelI I! TimeoutII I ,II I Communication i II (WhileII:I ; Un-Loading) 1II I; FailureI IIIII III III IIIIIII II 03=CheckIIII I I IIII I II II AllocateIIIIII I 1 MessageIII III II BufferIIIIII 1IIII I fIIIII IIII II I II 04=MPB85 ;II I II IIII II II TimeoutIIIII II I; (Single Byte) ;IIII1 I I I IIIII1 Figure 2.2Fault Code Quick Reference Guide5210 a/a7M-27
.- .----- .W”. IIIII IREGISTER STORED DATA VALUEI I III II IFAULT CODEI8C’IIIID2I IEsHILI II III I II I’ 05=Readi’ Data After Writef Written] Data Read;I IAddress of Faulty ByteII Ii ErrorinCEC III1III iI II II I ; MemoryIIII I IIII II III’=-. I III1III I:II I ‘I-I I; 06= MPB85;r TimeoutIIII II I II II II III! (WhileI I IIIi Loading)II I III II IIII -I II II 07 = CannotIII I IIIII IIIIIIII II Ii Bring UpIIIII II Channel onI II Ii StartupIII1 II III,I I fI ;II 08= FirstI III I II III Ii Faulty Byte;IIIII II in MessageIIIIII II IfiIII II II f 06-CECIi 1 PEC XI ISystem Network I Ii Timeslot in1 OO=PEC(s)did iI I Test FailureI I ; PEC X; not respond ;; PEC Yr Timeslot i IIinI II II III 01 = Only one! PEC No. notI; PEC YI II IIi PECresponded ) respondingIII I I II I IIII I I II02 =TestfII II II FailureIII I II IIIIII I ObPECI1 Networki i PEC No. I I I I ) Channel No.; OO=PEC(s) ;II Ir did notIIII Test Failure I II III II IIi respondII1 I II II II II IIi 02=TestI III I I IIII II III FailureI I I I I I I II I IIi 03=Network III I i III If Detected Off- iIII: ;ti lineIII III I ; 09-PEC1 I, , PEC No.I Channel No.IfIIr DirectiveI I:I OO=PEC(s)did II not respond iII tTest FailureIII III II IIII I II II IIIIIIII02 = TestI IiI FailureIIII iI fI II I II r IO-PEC; ; PEC No.II I III II IIII DirectiveI IIIIII II Hopper Full I iI II I I III I I II IIIII 11 PECI I ,I iI I PEC No.Illegal EventI Ii Parameter 1I Parameter 2f Parameter 3i Event No. iIII I Error t IIIIIIIII III Figure 2.2 Fault Code Quick Reference Guide (Continued) M-2881875210