Page 1 Maintenance for the Avaya™ S8700 Media Server for IP Connect Configurations Volume 3 555-233-142 Issue 1 May 2002...
Page 2 How to Get Help These compromises may become more acute if you fail to follow For additional support telephone numbers, go to the Avaya Web site: Avaya's recommendations for configuration, operation and use of the http://www.avaya.com/ equipment.
Page 3 Technical Service Center at 1-800-242- sion signaling is in violation of Part 68 rules. This equipment returns 2121 or contact your local Avaya representative. If the equipment is answer-supervision signals to the public switched network when: causing harm to the telephone network, the telephone company may •...
Page 4 Haverhill, MA 01835 USA but many have been registered with the FCC before the SDoC process Attention: Avaya Account Management was available. A list of all Avaya registered products may be found at: E-mail: totalware@gwsmail.com http://www.part68.org/ by conducting a search using “Avaya” as manufacturer.
Page 5: Table Of Contents
Contents Volume 1 About this Book xvii Intended Use xviii How to Use this Document xviii Organization xviii Conventions Used in This Document Trademarks and Service Marks Where to Call for Technical Support xxii Maintenance Architecture Maintenance Objects Alarm and Error Reporting Basic Server and IPSI Connectivity Power Interruptions Protocols...
Page 6 Contents Initialization and Recovery Initialization Recovery Reset Level 1 (Warm Restart) Reset Level 2 (Cold-2 Restart) 3-10 Reset Level 4 (MultiVantage Application Reload) 3-11 Alarms, Errors, and Troubleshooting Safety Precautions Suppress Alarm Origination [y] Reseating and Replacing Circuit Packs Replacing a BIU or Rectifier Troubleshooting a Duplicated Server Executing a Server Interchange 4-14...
Page 7 Contents LED Interpretation Alarm Levels Terminal Alarm Notification Attendant Console LEDs Circuit Pack LEDs Server LEDs IPSI LEDs 6-13 Duplication Memory Card LEDs 6-16 Maintenance Commands New Commands Modified Commands Command-Line Syntax Common Input Parameters Common Output Fields Contention Between Simultaneous Commands 7-12 Busyout and Release Commands 7-13...
Page 8 Contents change system-parameters ipserver-interface 7-66 change system-parameters maintenance 7-68 clear errors 7-74 clear firmware-counters 7-75 clear link n 7-76 disable filesystem board ppcss 7-77 disable firmware download 7-78 display alarms 7-79 display capacity 7-86 display communication-interface links 7-99 display communication-interface processor-channel 7-101 display errors 7-103...
Page 9 Contents list isdn-testcall 7-169 list marked-ports 7-170 list measurements clan ethernet 7-171 list measurements clan ppp 7-174 list measurements clan sockets 7-176 list measurements ds1 7-179 list measurements ip codec 7-184 list measurements ip dsp-resource 7-188 list measurements ip-signaling-group 7-192 list pms-down 7-195 list registered-ip-stations...
Page 10 Contents save translation 7-256 set boot-image 7-257 set ethernet-options 7-258 set ipserver-interface (a-all | b-all) 7-259 set options 7-260 set pnc 7-268 set signaling-group 7-269 set synchronization 7-270 set tdm 7-271 set time 7-272 set tone-clock 7-274 status access-endpoint 7-275 status administered-connection 7-276 status attendant...
Page 11 Contents status sys-link 7-380 status trunk 7-383 status tsc-administered 7-388 status tti 7-390 status val-ip 7-392 test alarms 7-393 test analog-testcall 7-402 test board 7-403 test cdr-link 7-404 test data-module 7-405 test ds1-loop 7-406 test eda-external-device-alrm 7-410 test environment 7-413 test failed ip-network-region 7-415 test firmware download...
Page 12 Contents Volume 2 Maintenance-Object Repair Procedures Escalation Procedures ABRI-PORT (ASAI ISDN-BRI Port) AC-POWER ADM-CONN (Administered Connection) 8-11 ADX8D-BD (AUDIX Circuit Pack) 8-14 ADX8D-PT (AUDIX Digital Port) 8-15 ADX16D-B (16-Port AUDIX Circuit Pack) 8-23 ADX16A-BD (AUDIX Circuit Pack) 8-24 ADX16D-P (16-Port AUDIX Digital Port) 8-25 ADX16A-PT (AUDIX Analog Line/Control Link) 8-33...
Page 13 Contents BRI-SET, ASAI-ADJ, BRI-DAT 8-249 CABINET (Cabinet Sensors) 8-278 CDR-LNK (Call Detail Recording Link) 8-288 CLAN-BD (Control LAN Circuit Pack) 8-289 CLSFY-BD (Call Classifier Circuit Pack) 8-305 CLSFY-PT (Call Classifier Port) 8-306 CO-BD (Central Office Trunk Circuit Pack) 8-311 CO-DS1 (DS1 CO Trunk) 8-312 CO-TRK (Analog CO Trunk) 8-328...
Page 14 Contents HYB-LINE (Hybrid Line) 8-601 INADS (INADS Link) 8-622 IPMEDPRO (IP Media Processor Circuit Pack) 8-626 IP-SVR (IP Server Interface) 8-647 ISDN-PLK (ISDN-PRI Signaling Link Port) 8-653 ISDN-LNK (ISDN-PRI Signaling Link Port) 8-658 ISDN-SGR (ISDN-PRI Signaling Group) 8-664 ISDN-TRK (DS1 ISDN Trunk) 8-677 JNL-PRNT (Journal Printer Link) 8-700...
Page 15 Contents PKT-BUS (Packet Bus) 8-918 PKT-INT (Packet Interface) 8-926 PLAT-ALM (Platform Alarms) 8-949 PMS-LINK (Property Management System Link) 8-950 PMS-PRNT/JNL-PRNT (PMS Printer Link) 8-958 PPP-PT (Control LAN Packet/Port) 8-964 PRI-CDR/SEC-CDR (Call Detail Recording Link) 8-976 PROC-SAN (Process Sanity Audits) 8-982 RALM-SVC (Remote Alarm Service) 8-983 RANL-STA (Remote Analog Line (Station) Port...
Page 16 Contents UPS (Server UPS) 8-1312 VAL-BD (Voice Announcements over LAN Circuit Pack) 8-1319 VAL-PT (Voice Announcements over LAN Packet/Port) 8-1341 VC-BD 8-1347 VC-DSPPT 8-1351 VC-LEV (Voice Conditioner DSP Port Level) 8-1359 VC-SUMPT 8-1362 WAE-PORT (Wideband Access Endpoint Port) 8-1367 XXX-BD (Common Port Circuit Pack) 8-1374 Index IN-1...
Page 17 The TN802 Multiple Application Platform for DEFINITY (MAP-D) circuit pack allows sending voice and fax from S8700 IP Connect through the Internet to another S8700 IP Connect also having this feature or to other PBXs that are equipped with the Internet Telephony server (ITS-E).
Page 18: Maintenance Objects
Maintenance Object Repair Procedure Feature Limitations The Internet trunking application relies on the single call scenario, or a direct, point-to-point call that does not terminate at multiple S8700 IP Connect nodes through call processing. Table 8-293 describes the feature limitations for S8700 IP Connect.
Page 19 MAPD-BD (MAPD Interface Circuit Pack TN802) Table 8-293. S8700 IP Connect IP trunk feature/performance limitations — Continued Feature/ Performance Description Recommendation Conferencing Voice quality and delay Avoid conference calls where at problems if the party least two other parties are on the controlling the conference is other side of the IP trunk.
Page 20 Table 8-294. Backing up TN802 administration data Step Description Comments Busyout circuit pack At the S8700 IP Connect terminal, type busyout board UUCSS (the address of the TN802 circuit pack) and press Enter Backup administration At the Windows NT desktop, double-click on the IP TN802 to disk Trunk Backup Restore icon.
Page 21 When the far end returns a poor response time to the ping, S8700 IP Connect’s ARS or AAR network routing patterns bypass those ports and direct the call to another port, typically on a PSTN trunk.
Page 22 MAPD circuit pack. UPS Protection Since the robustness of S8700 IP Connect’s Linux operating system (OS) is less certain than DEFINITY’s Oryx/Pecos OS, uninterruptible power supply (UPS) protection is strongly recommended for an EPN containing a TN802 circuit pack.
Page 23 MAPD-BD (MAPD Interface Circuit Pack TN802) Table 8-296 lists the TN802 LCD messages that you might see if installing or servicing an IP Trunk. Table 8-296. TN802 LCD messages for IP trunks Display Explanation PC BOOT The TN802 MAPD PC is booting up. IP TRK # IP Trunk application is running (# character blinks).
Page 24 Maintenance Object Repair Procedure Table 8-297. Remote connection settings Field Value 38,400 Speed None (default) Parity RTS/CTS Flow Control Carrier detect (DCD) Started by Carrier detect (DCD) Ended by Continued on next page 6. Click on the new item icon, and the laptop connects to the host ®...
Page 25 MAPD-BD (MAPD Interface Circuit Pack TN802) Directly-Connected Keyboard, Monitor, Mouse NOTE: You need 2 power sources for the monitor and the modem in order to complete this procedure. NOTE: The TN802 circuit pack must be booted with a local mouse and keyboard connected to it for these devices to work.
Page 26 Maintenance Object Repair Procedure 3. At the command prompt, type ping nnn.nn.nn.nn (the external IP trunk server’s address), and press Enter If configured correctly, the system displays: Reply from nnn.nn.nn.nn: bytes=32 time<##ms TTL=### If there is no reply, verify the IP address and check the physical connections to and from the TN802 circuit pack.
Page 27 MAPD-BD (MAPD Interface Circuit Pack TN802) 3. At the command prompt, type ping 10.32.64.97 (the internal IP trunk server’s address), and press Enter If configured correctly, the system displays: Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=### If there is no reply: a.
Page 28 Maintenance Object Repair Procedure Board Assembly and Cables Figure 8-17 shows the circuit pack with the two additional boards connected through the side plane. indfmap2 KLC 031699 Figure Notes: 1. Main TN802 board 4. Side plane 2. Texas Microsystems Inc. (TMI) board 5.
Page 29 MAPD-BD (MAPD Interface Circuit Pack TN802) Figure 8-18 shows a side view of the thee boards and interconnecting cables that make up the TN802. cddfmap2 KLC 040699 Figure Notes: 1. Main TN802 board 4. SCSA (Signal Computing System Architecture) ribbon cable 2.
Page 30 Maintenance Object Repair Procedure Figure 8-19 shows the end view of the thee boards and interconnecting cables on the TN802. ckdfmap3 KLC 040699 Figure Notes: 1. Analogic board 3. SIMMs (memory) 2. TMI (Texas Microsystems Inc.) board 4. SCSA (Signal Computing System Architecture) ribbon cable If the board is seated and you hear fast beeping, it means that one of the small boards containing the memory chips is dislodged.
Page 31: Initialization
MAPD-BD (MAPD Interface Circuit Pack TN802) Replacing the Hard Disk The TN802 hard drive (Note 5 in Figure 8-18) is field-replaceable. Table 8-298. Replacing the TN802 hard drive Step Description Comments Shut down NT. Shut down Windows NT by either method described in the ‘‘Shutting Down NT on the TN802’’...
Page 32 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-299. MAPD (TN802) Error Log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test board UUCSS 1 (a) Circuit pack removed or MIN/ SAKI test (#53) 2 (b)
Page 33 MAPD-BD (MAPD Interface Circuit Pack TN802) Table 8-299. MAPD (TN802) Error Log entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 3073 to Slip Alarm Inquiry test MIN/ test board UUCSS r 6 3160 (#144) 3330 (n)
Page 34 Maintenance Object Repair Procedure Completely remove the MAPD-BD from the system: a. Shut down NT (see ‘‘Shutting Down NT on the TN802’’) b. Remove any administered DS1 trunks, access endpoints, or PRI endpoints associated with the circuit pack from their respective trunk groups.
Page 35 MAPD-BD (MAPD Interface Circuit Pack TN802) g. Error Type 513: transient hardware problem. Aux Data: 4352 External RAM failure 4353 Internal RAM failure 4355 Internal ROM failure 1. If the same Error Type/Aux Data value occurs more than once in a 24-hour period, the circuit pack should be replaced.
Page 36 Maintenance Object Repair Procedure k. Error Type 1537—LAN Bus Timeout; the circuit pack transmitted too many bytes on the LAN bus for a single frame. This condition may be caused by: an on-board fault faulty data received on one of the circuit pack’s external ports. If any of the ports on this circuit pack are alarmed, refer to the repair procedures for those MOs.
Page 37 MAPD-BD (MAPD Interface Circuit Pack TN802) n. Error Type 3330—LAN Critical error; critical failure in the packet-bus interface to the circuit pack. This failure may be due to an on-board or a packet-bus fault. 1. If the packet bus is alarmed, see ‘‘PKT-BUS (Packet Bus)’’...
Page 38 Maintenance Object Repair Procedure t. Error Type 3999—The circuit pack sent a large number of control-channel messages to the switch within a short period of time. Error Type 1538 (hyperactivity) also present? Then the switch: Takes the circuit pack out-of-service due to hyperactivity Does not take the circuit pack out-of-service, but the circuit pack has generated 50% of the messages necessary to be considered hyperactive.
Page 39 MAPD-BD (MAPD Interface Circuit Pack TN802) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented in Table 8-301. For example, by clearing error codes associated with the NPE Connection Audit test (#50), you may also clear errors generated from other tests in the testing sequence. Table 8-301.
Page 40 Maintenance Object Repair Procedure NPE Connection Audit Test (#50) The system sends the circuit pack’s on-board microprocessor a message to update the network-connectivity translation for its SCOTCH-NPE chip. Table 8-302. Test #50 NPE Connection Audit Test Error Test Code Result Description / Recommendation None ABORT...
Page 41 MAPD-BD (MAPD Interface Circuit Pack TN802) Control Channel Loop-Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 8-303. Test #52 Control Channel Loop-Around Test Error Test Code Result Description / Recommendation None ABORT...
Page 42 Maintenance Object Repair Procedure SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack. The test is highly destructive and can only be initiated by a system technician-demanded reset board UUCSS command. Table 8-304. Test #53 SAKI Sanity Test Error Test Code...
Page 43 MAPD-BD (MAPD Interface Circuit Pack TN802) Loss of Signal Alarm Inquiry Test (#138) This test is meaningless for the TN802 MAPD circuit pack. Table 8-305 details the test results. Table 8-305. Loss of Signal Inquiry Test (#138) results Windows NT up on the TN802? Then...
Page 44 Maintenance Object Repair Procedure Yellow Alarm Inquiry Test (#141) This test is meaningless for the TN802 MAPD circuit pack. Table 8-308 details the test results. Table 8-308. Yellow Alarm Inquiry Test (#141) results If Windows NT is up on the TN802 When the switch confirms Yellow alarm: Test passes Test aborts with ABORT 2000 Error Code.
Page 45 MAPD-BD (MAPD Interface Circuit Pack TN802) Slip Alarm Inquiry Test (#144) This test is meaningless for the TN802 MAPD circuit pack. Table 8-311 details the test results. NOTE: The query for slips always returns a 0 count. Table 8-311. Slip Alarm Inquiry Test (#144) results If Windows NT is up on the TN802 When the switch confirms Slip alarm:...
Page 46 Maintenance Object Repair Procedure Table 8-313. Test #146 Translation Update Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. FAIL Internal system software error. 1. Verify the MAPD Interface circuit pack translation (display ds1 UUCSS). PASS Translation data has been downloaded to the MAPD Interface circuit pack successfully.
Page 47 NT interface and the ITS software diagnostics. The Media Processor application is built upon the existing ITS software, and as such is not administered in S8700 IP Connect as a DS1 trunk, and does not emulate a DS1 for maintenance purposes. Use the following Maintenance procedures for this application.
Page 48 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-314. DS1 Interface Circuit Pack Maintenance Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test board UUCSS 1(a) Circuit pack removed or MINOR SAKI test (#53) WARNING...
Page 49 MEDPRO (Media Processor MAPD Circuit Pack) Notes: a. Error Type 1 - indicates that the circuit pack has totally stopped functioning or is not fully administered. The alarm is logged about 15 minutes after the circuit pack has been removed or 11-minutes after the test (#53) fails.
Page 50 Maintenance Object Repair Procedure d. Error Type 125 - no Aux Data: The wrong circuit pack is inserted in the slot where this circuit pack is logically administered. 1. Remove the wrong circuit pack and insert the logically administered circuit pack Re-administer this slot to match the circuit pack inserted (change circuit-pack).
Page 51 MEDPRO (Media Processor MAPD Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented inTable 8-315. For example, by clearing error codes associated with the Control Channel Loop test (#52), you may also clear errors generated from other tests in the testing sequence. Table 8-315.
Page 52 Maintenance Object Repair Procedure Control Channel Loop-Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 8-316. Test #52 Control Channel Loop-Around Test Error Test Code Result Description / Recommendation None ABORT System resources required for this test are not available.
Page 53 MEDPRO (Media Processor MAPD Circuit Pack) SAKI Sanity Test (#53) This is a destructive test. This test is only run as a part of a reset board procedure. For the Media Processor, it is necessary to use the change ip-interfaces form to disable the Media Processor IP interface before performing this reset board procedure.
Page 54 It is possible that changes can be made via the NT PC interface that cause the Media Processor board to be inconsistent with S8700 IP Connect translations. The area of concern is the IP address, subnet mask, and gateway translation.
Page 55 MEDPRO (Media Processor MAPD Circuit Pack) Ping Test (#1379) This test is nondestructive This test verifies that the MedPro circuit pack can communicate to other nodes on the LAN. This test pings the gateway IP address as defined on the IP Interface form. If the PING is successful, this test looks at the PING round trip delay.
Page 56 Maintenance Object Repair Procedure Table 8-319. Test #1379 Ping Test — Continued Error Test Code Result Description / Recommendation 2801 ABORT No IP address defined. Verify IP Interfaces translations and retest. 2802 ABORT Different IP address pinged than software had allocated for the test. 1.
Page 57 MEDPRO (Media Processor MAPD Circuit Pack) Table 8-320. Test #1381 NT Reset Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT System resources required for this test are not available. 1. Retry the reset board UUCSS command at 1-minute intervals up to 5 times.
Page 58 Maintenance Object Repair Procedure NIC Query Test (#1383) This test is nondestructive. This test passes if the Ethernet port is connected, and you can talk on the network. Otherwise, it fails with no fail code or AUX data. Table 8-321. Test #1383 NIC Query Test Error Test Code...
Page 59 MEDPROPT (TN802/TN2302 MED PRO DSP PORT) MEDPROPT (TN802/TN2302 MED PRO DSP PORT) MO’s Name Alarm (in Alarm Log) Level Initial Command to Run Full Name of MO MEDPROPT MINOR test port UUCSS or PCSS TN802/TN2302 WARNING [short/long] [repeat#] | [clear] MEDPRO DSP PORT The MEDPROPT MO monitors the health of the MEDPRO digital signal processors (DSPs).
Page 60 Maintenance Object Repair Procedure Table 8-322. MEDPROPT Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 515 (e) DSP Capacity Query test MINOR test board UUCCSS l r5 (##1382) TDM NIC Loop-Around MINOR test port UUCCSS l r10 test (#1380)
Page 61 MEDPROPT (TN802/TN2302 MED PRO DSP PORT) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented in Table 8-323. For example, by clearing error codes associated with the DSP Capacity Query test (#1382), you may also clear errors generated from the other tests in the testing sequence. Table 8-323.
Page 62 Maintenance Object Repair Procedure Table 8-324. DSP Capacity Query Test (#1382) Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 3 times. 2100 ABORT Could not allocate the necessary system resources to run this test.
Page 63 MEDPROPT (TN802/TN2302 MED PRO DSP PORT) TDM NIC Loop-Around Test (#1380) This test is nondestructive This test sets up a loop-back path from the TDM bus out to the NIC edge of the Media Processor and back to the TDM bus. The loop back is established by setting up the outbound IP connection to send IP packets to the MedPro’s own IP address.
Page 64 Maintenance Object Repair Procedure Table 8-325. TDM NIC Loop-Around Test (#1380) — Continued Error Test Code Result Description / Recommendation 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2500 ABORT Internal system error.
Page 65 MEDPROPT (TN802/TN2302 MED PRO DSP PORT) Port Status Query Test (#1407) This test is nondestructive This test queries the Port status. Table 8-326. port Status Query Test (#1407) Error Test Code Result Description / Recommendation ABORT This port is Out of service (OOS) due to: A board-level problem, for example no IP address has been translated for this location.
Page 66: Met-Bd (Met Line Circuit Pack)
Maintenance Object Repair Procedure MET-BD (MET Line Circuit Pack) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO MET-BD MINOR test board UUCSS sh MET Line circuit pack MET-BD WARNING test board UUCSS sh MET Line circuit pack UU is the universal cabinet number (1–64).
Page 67: Met-Line (Met Line)
MET-LINE (MET Line) MET-LINE (MET Line) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO MET-LINE MINOR test port UUCSSpp l MET Line MET-LINE WARNING test port UUCSSpp sh MET Line UU is the universal cabinet number (1–64). C is the carrier designation (A, B, C, or D). SS is the number of the slot where the circuit pack resides (01–10).
Page 68 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-327. MET Line Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 40987 None 18 (b)
Page 69 MET-LINE (MET Line) b. Error type 18 is logged when maintenance personnel busyout the port. The port is released from busyout via the release port UUCSSpp command. c. The circuit pack has been removed or has been insane for more than 11 minutes.
Page 70 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the Port Diagnostic test (#35), you may also clear errors generated from other tests in the testing sequence.
Page 71 MET-LINE (MET Line) NPE Crosstalk Test (#6) The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, one-way and noisy connections may be observed.
Page 72 Maintenance Object Repair Procedure Table 8-329. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1018 ABORT Test disabled via administration. This only applies to analog stations. The default for this field is y, so you may want to determine why it has been turned off on this station.
Page 73 MET-LINE (MET Line) Table 8-329. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation PASS The port uses its allocated time slots correctly. Investigate user-reported troubles on this port using other port tests and by examining station, trunk, or external wiring.
Page 74 Maintenance Object Repair Procedure Port Diagnostic Test (#35) This test checks a port’s battery feed circuitry. The battery feed circuitry is tested for proper battery voltage by testing the switchhook state. In response to the test message, the on-board firmware terminates the line and checks for switch-hook presence.
Page 75 MET-LINE (MET Line) Table 8-330. Test #35 Port Diagnostic Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT Could not allocate the necessary system resources to run this test. This could be due to a failure to seize the port. 1.
Page 76 Maintenance Object Repair Procedure MFAT Electronic Power Feed (#56) The software requests that the EPF be turned on for a given port. The hardware then attempts to turn on that port’s station power unit. If no current is drawn, the station is probably not connected.
Page 77 MET-LINE (MET Line) Table 8-331. Test #56 MFAT Electronic Power Feed Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 78 Maintenance Object Repair Procedure MET Circuit and Conference Circuit Test (#57) This test checks two different port circuit functions. The Hybrid Circuit test performs an analog reflective loop-around measurement on the port’s hybrid circuitry. The Conference Circuit test performs a conference test on the port’s NPE.
Page 79 MET-LINE (MET Line) Table 8-332. Test #57 Hybrid Circuit and Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1002 ABORT The system could not allocate time slots for the test. The system may be under heavy traffic conditions or it may have time slots out-of-service due to TDM-BUS errors.
Page 80 Maintenance Object Repair Procedure Table 8-332. Test #57 Hybrid Circuit and Conference Circuit Test — Continued Error Test Code Result Description / Recommendation FAIL The conference circuit test failed. The conference circuit test is performed only if the hybrid test passes. The conference circuit test verifies that the network processing element (NPE) can correctly conference several test tones together.
Page 81 MET-LINE (MET Line) Table 8-332. Test #57 Hybrid Circuit and Conference Circuit Test — Continued Error Test Code Result Description / Recommendation PASS Hybrid Circuit and Conference Circuit test passed. The hybrid circuitry is transmitting properly. 1. If complaints persist, investigate by using other port tests, and by examining the station, wiring, and connections.
Page 82 Maintenance Object Repair Procedure MET Line Station Lamp Updates Test (#60) For this test, the software lights the lamps on the terminal based on the status record contained in the processor. The lamp updates run only if the station is in-service.
Page 83 MET-LINE (MET Line) Table 8-333. Test #60 MET Line Station Lamp Updates Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 84 Maintenance Object Repair Procedure Table 8-334. Test #61 MET Line Station Audits Test Error Test Code Result Description / Recommendation ABORT Internal system error ABORT The test was aborted due to an internal system error during the switchhook audit. The test was aborted due to an internal system error during the bad scan inquiry.
Page 85 MET-LINE (MET Line) Table 8-334. Test #61 MET Line Station Audits Test — Continued Error Test Code Result Description / Recommendation PASS Hybrid Line Station audits passed. 1. Although this test will never actually return a FAIL result except for the Internal system error described above, it is possible that it will enter Error Type 257 or 513 into the Error Log.
Page 86 Maintenance Object Repair Procedure MET Line Ringer Update Test (#62) In this update, a “ringer on” or a “ringer off” message is sent to the firmware to start and stop the ringer on the set. Table 8-335. Test #62 MET Line Ringer Update Test Error Test Code...
Page 87 MIS (Management Information System) MIS (Management Information System) MO’s Name Alarm (in Alarm Log) Level Initial Command to Run Full Name of MO WARNING release mis Management Information System The Management Information System (MIS)/Call Management System (CMS) MO is used only to monitor MIS busyouts during administration of MIS translations. There are no hardware failures associated with this MO.
Page 88 Maintenance Object Repair Procedure MMI-BD MO’s Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO MMI-BD MAJOR test board UUCSS l r# Multimedia Interface circuit pack MMI-BD MINOR test board UUCSS l r# Multimedia Interface circuit pack MMI-BD WARNING test board UUCSS s r#...
Page 89 Provides T.120 data-sharing capability on a MMCH multipoint H.320 video conference Each conference participant must have endpoints administered and a personal computer with the H.320 video application installed. The S8700 IP Connect must have the expansion service module installed. 555-233-142 Issue 1 May 2002 8-785...
Page 90 3. 25-pair Y-cable rate interface) card 4. 356A adapter Figure 8-21. Typical ESM connections CAUTION: The TN2207 circuit pack is the only pack allowing connection of an ESM to the S8700 IP Connect ECS switch. 8-786 Issue 1 May 2002 555-233-142...
Page 91 MMI-BD Error Log Entries and Test to Clear Values Table 8-337. MMI-BD Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test board UUCSS sh r 1 1 (a) None MINOR 18 (b) Busyout board UUCSS WARNING release board UUCSS...
Page 92 Maintenance Object Repair Procedure d. Indicates transient communication problems between the switch and this circuit pack. Execute the test board UUCSS command and see the repair procedures for the Control Channel Loop-around test (#52) in ‘‘XXX-BD (Common Port Circuit Pack)’’ on page 8-1374.
Page 93 MMI-BD System Technician-Demanded Tests: Descriptions and Error Code Always investigate tests in the order presented in Table 8-338 below when inspecting errors in the system. For example, by clearing error codes associated with the TSI Crosstalk test (#6), you may also clear errors generated from other tests in the testing sequence.
Page 94 Maintenance Object Repair Procedure Table 8-339. Test #6 TSI Crosstalk Test Error Test Code Result Description / Recommendation ABORT Internal system error. This is an abnormal abort. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABORT The system could not allocate time slots for the test, the traffic load on the system is very high, or the time slots are out-of-service due to TDM-BUS errors.
Page 95 MMI-BD TSI Loop-Around Test (#1108) This test is nondestructive. During this test, the MMI’s Time Slot Interchanger (TSI) is listens to a TDM timeslot. A digital count tone loops back in the TSI and onto another TDM timeslot without passing through any resource hardware. A tone detector port verifies the looped data.
Page 96: Recovery
Maintenance Object Repair Procedure MMI Synchronization Status Test (#1122 and 1123) This test is nondestructive. To support applications involving multiple MMI circuit packs, the appropriate MMI circuit packs must be synchronized with one another. One such circuit pack is designated as the master sync source, which provides the synchronization signal onto the TDM bus.
Page 97 MMI-BD Table 8-341. Test #1122/1123 MMI Synchronization Status Test — Continued Error Test Code Result Description / Recommendation FAIL The MMI circuit pack is out of MMI synchronization. Run the long option of the test board command. 1. Wait up to 5 minutes, and then reset the circuit pack with these commands: busyout board UUCSS, then reset board UUCSS, followed by release board UUCSS.
Page 98 Maintenance Object Repair Procedure MMI-LEV (Multimedia Interface Resource Level) MO’s Name Alarm (in Alarm Log) Level Initial Command to Run Full Name of MO MMI-LEV MAJOR ‘‘Resolving MMI-LEV Errors/Alarms’’ MMI-LEV The Multimedia Interface Resource Level MO monitors MMI efficiency by tracking the number of MMI ports that are in-service, and then comparing that number with the value entered in the MMIs field on the System-Parameters Maintenance form.
Page 99: Maintenance Commands
MMI-LEV (Multimedia Interface Resource Level) The MMI circuit pack is maintained by the software like the Tone Detector circuit pack, which can be removed and reinserted in any port board slot without administration. Similarly, if a MMI circuit pack is removed from service logically by failing the Archangel sanity scan test or is removed from service physically by removing the circuit pack from the carrier, no error/alarm is raised against either the MMI-BD or the MMI-PT MOs.
Page 100 Maintenance Object Repair Procedure To resolve this alarm, correct the out-of-service problem by following these procedures: 1. See “MMI-PT” and “MMI-BD” and resolve any associated alarms. 2. If a MMI-LEV error/alarm exist and none has been raised against MMI-BD or MMI-PT MOs, an MMI circuit pack may have been removed from service causing the MMI-LEV error/alarm.
Page 101: Alarms, Errors, And Troubleshooting
MMI-PT MMI-PT MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO MMI-PT MAJOR test port UUCSSpp l r# Multimedia Interface Port MMI-PT MINOR test port UUCSSpp l r# Multimedia Interface Port MMI-PT WARNING test port UUCSSpp l r# Multimedia Interface Port Where UU is the universal cabinet number (1–64);...
Page 102 Maintenance Object Repair Procedure Figure 8-22. TN787 MMI (MULTIMEDIA INTERFACE) CIRCUIT PACK 8-798 Issue 1 May 2002 555-233-142...
Page 103 MMI-PT Error Log Entries and Test to Clear Values Table 8-343. MMI-PT Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) Uplink error from pack 18 (b) Busyout port PCSSpp WARNING...
Page 104 Maintenance Object Repair Procedure f. This error occurs if either the MMI or Voice Conditioner (VC) circuit packs reports a loss of framing on the service channel between these two circuit packs. When a customer endpoint establishes a call to the VSP-MCU, a channel is established between the MMI resource and the VC port.
Page 105 MMI-PT Table 8-344. Test #1111 Resource Loop-Around Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call. 1. Retry the command at 1-minute intervals up to 5 times. 2.
Page 106 Maintenance Object Repair Procedure Table 8-344. Test #1111 Resource Loop-Around Test — Continued Error Test Code Result Description / Recommendation 0, 1, 2 FAIL This resource cannot guarantee data integrity and is out-of-service. The following error codes indicate failure of a particular media loop: 0 = video 1 = audio 2 = low-speed data...
Page 107 MMI-SYNC MMI-SYNC MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO MMI-SYNC MINOR test board UUCSS l r# Multimedia Interface circuit pack Where UU is the universal cabinet number (1–64); C is the carrier designation (A, B, C, or D); SS is the address of the slot in the carrier where the circuit pack resides (01–10);...
Page 108 Maintenance Object Repair Procedure A synchronization switch takes place if half or more of the MMI circuit packs in a PN report a loss of synchronization. For example, a PN with two MMIs reporting a loss of sync source switches immediately, three and four MMIs switch if two report the loss, and so forth.
Page 109: Modem-Bd (Modem Pool Circuit Pack)
MODEM-BD (Modem Pool Circuit Pack) MODEM-BD (Modem Pool Circuit Pack) MO’s Name Alarm (in Alarm Log) Level Initial Command to Run Full Name of MO MODEM-BD test board UUCSS sh Modem Pool circuit pack MODEM-BD test board UUCSS sh Modem Pool circuit pack UU is the universal cabinet number (1–64).
Page 110 Maintenance Object Repair Procedure MODEM-PT (Modem Pool Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO MODEM-PT MINOR test port UUCSSpp s Modem Pool Port UU is the universal cabinet number (1–64). C is the carrier designation (A, B, C, or D). SS is the number of the slot where the circuit pack resides (01–10).
Page 111 MODEM-PT (Modem Pool Port) Integrated Modem Pools There are two primary types of Modem Pool conversion resources available: an Integrated Pooled Modem and a Combined Modem Pool. The integrated TN758 Pooled Modem circuit pack contains two independent 300- or 1200-bps conversion resources.
Page 112 Maintenance Object Repair Procedure Combined Modem Pools The Combined Modem Pool conversion resource is the second type available. The function served by the Combined Modem Pool is similar to that of the integrated Pooled Modem circuit pack, but the physical implementation is much different.
Page 113 MODEM-PT (Modem Pool Port) TERMINAL DATA MODULE DIGITAL LINE (TN754) DATA DIGITAL MODULE LINE (TN754) DIGITAL RS-232 COMBINED MODEM POOL NETWORK ANALOG MODEM LINE CENTRAL OFFICE Tip/Ring TRUNK TELEPHONE ANALOG NETWORK (TN747B) ANALOG MODEM HOST COMPUTER Figure 8-24. Typical Modem Pool Switched Connection with Combined Modem Pool 555-233-142 Issue 1 May 2002...
Page 114 Maintenance Object Repair Procedure Troubleshooting Modem-Pool Symptoms Certain customer-reported troubles may provide important information for troubleshooting Modem Pool problems. For example, if the customer tries to make a data call requiring a Modem Pool conversion resource, and the Modem Pool and Data Module speeds or other options do not match, they may receive a “CHECK OPTIONS”...
Page 115 MODEM-PT (Modem Pool Port) Error Log Entries and Test to Clear Values Table 8-346. Modem Pool Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 busyout UUCSS WARNING release port UUCSS None...
Page 116 Maintenance Object Repair Procedure Modem Pool NPE Crosstalk Test (#96) This test is destructive. The Modem Pool Crosstalk test verifies that the NPE is connected only to the desired time slot and is not crosstalking on other time slots. This test operates exactly like Test #6 for other types of port circuits but is performed twice in order to test both NPEs in the Modem Pool Port.
Page 117 MODEM-PT (Modem Pool Port) Table 8-347. Test #96 Modem Pool NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 6000 ABORT System resources needed to complete the test could not be allocated for the...
Page 118 Maintenance Object Repair Procedure Modem Pool Conference Test (#97) This test is destructive. The Modem Pool Conference test checks most of the switching and gain control functions provided by the NPE circuit in the analog section of the conversion resource. This test conferences a 1004-Hz tone through the NPE, looping it back so that it can be verified with a Tone Detector circuit Table 8-348.
Page 119 MODEM-PT (Modem Pool Port) Table 8-348. Test #97 Modem Pool Conference Test — Continued Error Test Code Result Description / Recommendation 4000 ABORT System resources needed to complete the test could not be allocated. Ordinarily, this means the conversion resource or other hardware used during the test was in use.
Page 120 Maintenance Object Repair Procedure Modem Pool Conversion Resource Loop-Around Test (#98) The Modem Pool Conversion Resource Loop-around test is set up as follows: TN758 POOLED MODEM CIRCUIT PACK TS-A DIGITAL ANALOG DIGITAL TS-C PORTION PORTION PORT TS-B MAINTENANCE/ MODEM POOL CONVERSION RESOURCE TEST BOARD (TN771B) Figure 8-25.
Page 121 MODEM-PT (Modem Pool Port) Test data patterns are transmitted from a Maintenance/Test board’s digital port over network time slot A through the digital port on the conversion resource, looped around through the analog port via time slot C back to the Maintenance/Test board’s digital port circuit via time slot B where the patterns are checked for accuracy.
Page 122 Maintenance Object Repair Procedure Table 8-349. Test #98 Modem Pool Conversion Resource Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1182 ABORT Internal system error. Failed to connect the digital ports with time-slots. 1. Retry the command at 1-minute intervals up to 5 times. 1340 ABORT No Maintenance/Test digital port is currently available to perform this test.
Page 123 MODEM-PT (Modem Pool Port) Table 8-349. Test #98 Modem Pool Conversion Resource Loop-Around Test — Continued Error Test Code Result Description / Recommendation 2323 ABORT The Maintenance Test circuit pack digital port allocated for this test did not disconnect properly. This error is more closely related to the Maintenance Test circuit pack digital port used for this test than the TN758 Pooled Modem circuit pack itself.
Page 124 Maintenance Object Repair Procedure Modem Pool Audit Test (#99) This audit updates the Modem Pool conversion resource status contained in the TN758 Pooled Modem circuit pack’s microprocessor. It does not actually test the Pooled Modem circuit pack; therefore, there are no FAIL codes. The audit can only be performed on idle conversion resources.
Page 125: M/T-Anl (Maintenance/Test Analog Port)
M/T-ANL (Maintenance/Test Analog Port) M/T-ANL (Maintenance/Test Analog Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO M/T-ANL Minor test port UUCSSpp l Maintenance/Test analog port M/T-ANL Warning release port UUCSSpp Maintenance/Test analog port UU is the universal cabinet number (1–64).
Page 126 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-351. M/T-ANL Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp 1 (b) 41018 none MINOR test port UUCSSpp l r 3 busyout port UUCSSpp WARNING release port UUCSSpp...
Page 127 M/T-ANL (Maintenance/Test Analog Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following table when inspecting errors in the system. For example, by clearing error codes associated with the Analog Port Sanity test (#963), you may also clear errors generated from other tests in the testing sequence.
Page 128 Maintenance Object Repair Procedure Table 8-352. Test #9 NPE Cross Talk Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use on a valid ATMS trunk test call. 1.
Page 129 M/T-ANL (Maintenance/Test Analog Port) Table 8-352. Test #9 NPE Cross Talk Test — Continued Error Test Code Result Description / Recommendation FAIL The NPE of the tested port was found to be transmitting in error. This will cause noisy and unreliable connections. 1.
Page 130 Maintenance Object Repair Procedure Table 8-353. Test #13 Analog Port Digital Loop-Around Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 3 times. 1000 ABORT The port is in use on a valid ATMS test call. 1.
Page 131 M/T-ANL (Maintenance/Test Analog Port) Table 8-353. Test #13 Analog Port Digital Loop-Around Test — Continued Error Test Code Result Description / Recommendation FAIL Conference test failed on the primary information channel. 1. Run the circuit pack tests to check the Tone-Clock (TONE-BD) circuit pack and the Tone Detector circuit pack via the test board UUCSS command.
Page 132 Maintenance Object Repair Procedure Table 8-354. Test #270 Clear Error Counters Error Test Code Result Description / Recommendation PASS The message to clear the Maintenance/Test circuit pack’s counter for Background Maintenance Failures has been sent. Continued on next page Hook State Inquiry (#566) This test ensures that the Maintenance/Test analog port maintenance software and call processing agree on the on-/off-hook status of the Maintenance/Test analog port.
Page 133 M/T-ANL (Maintenance/Test Analog Port) Analog Port Sanity Test (#963) This test verifies that the port circuitry involved in the analog trunk testing on the Maintenance/Test analog port is functioning properly. This test will abort if an ATMS test call is in progress on the Maintenance/Test analog port when the test is requested.
Page 134: M/T-Bd (Maintenance/Test Circuit Pack)
Maintenance Object Repair Procedure M/T-BD (Maintenance/Test Circuit Pack) MO’s Name As It Appears in Alarm Initial System Technician Alarm Log Level Command to Run Full Name of MO M/T-BD MINOR test board UUCSS l Maintenance/Test circuit pack M/T-BD WARNING release board UUCSS Maintenance/Test circuit pack UU is the universal cabinet number (1–64).
Page 135 M/T-BD (Maintenance/Test Circuit Pack) Hardware Error Log Entries and Test to Clear Values Maintenance/Test Board Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1(a) SAKI Sanity test (#53) MINOR See footnote a 18(b)
Page 136 Maintenance Object Repair Procedure d. A Control Channel Protocol error has occurred. This may be due to the circuit pack detecting an on-board hardware failure. Execute busyout board UUCSS and reset board UUCSS commands to reset the circuit pack. Any such problem will be detected during initialization, as the circuit pack locks up and appears insane to the system.
Page 137 M/T-BD (Maintenance/Test Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the Control Channel Loop-Around test (#52), you may also clear errors generated from other tests in the testing sequence.
Page 138 Maintenance Object Repair Procedure M/T-DIG (Maintenance/Test Digital Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO M/T-DIG MINOR test port UUCSSpp l Maintenance/Test digital port M/T-DIG WARNING release port UUCSSpp Maintenance/Test digital port UU is the universal cabinet number (1–64).
Page 139: M/T-Dig (Maintenance/Test Digital Port)
M/T-DIG (Maintenance/Test Digital Port) PBX Equipment UN332 TN1655 MSSNET PKT-INT Packet Looped-back data stream pattern is generated by digital port 1 and checked by digital port 2 on ......... . . the TN771 Digital Digital...
Page 140 Maintenance Object Repair Procedure Hardware Error Log Entries and Test to Clear Values M/T-DIG Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp 1 (a) 41018 none MINOR test port UUCSSpp l r 3 18 (b) busyout port UUCSSpp WARNING...
Page 141 M/T-DIG (Maintenance/Test Digital Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following table when inspecting errors in the system. For example, by clearing error codes associated with the Digital Port Sanity test (#565), you may also clear errors generated from other tests in the testing sequence.
Page 142 Maintenance Object Repair Procedure Table 8-357. Test #9 NPE Cross Talk Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use on a valid ISDN-PRI test call. Use the list isdn-testcall command to determine whether the port is in use (listed in the M/T Port column).
Page 143 M/T-DIG (Maintenance/Test Digital Port) Table 8-357. Test #9 NPE Cross Talk Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT System resources required to run this test are not available. 1.
Page 144 Maintenance Object Repair Procedure Digital Port Loop-Around Test (#13) This test is a modification of the Voice and Control Channel Local Loop test used by Digital Station (DIG-LINE) maintenance. This test does not perform the control channel and secondary information channel loop around tests as described for DIG-LINE, as these data paths do not exist for the Maintenance/Test digital port.
Page 145 M/T-DIG (Maintenance/Test Digital Port) Table 8-358. Test #13 Digital Port Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of tone detectors present, or some tone detectors may be out-of-service.
Page 146 Maintenance Object Repair Procedure Table 8-358. Test #13 Digital Port Loop-Around Test — Continued Error Test Code Result Description / Recommendation FAIL The primary information channel is not transmitting properly. User impact may range from nothing to not being able to use this port. 1.
Page 147 M/T-DIG (Maintenance/Test Digital Port) Clear Error Counters (#270) This test is not an actual test in the strict sense of the word. Many circuit packs have counters in the Angel firmware. These counters are used so that Control Channel Message Set (CCMS) messages are not continuously sent uplink. Using this method, the message will be sent once, when the counter reaches some preset threshold, and then not sent again until the counter is cleared.
Page 148 Maintenance Object Repair Procedure Digital Port Sanity Test (#565) This test verifies that the port circuitry involved in the digital trunk testing on the Maintenance/Test digital port is functioning properly. This circuitry is common to both Maintenance/Test digital ports on the Maintenance/Test circuit pack. Therefore, this test is only run for port 2.
Page 149 M/T-DIG (Maintenance/Test Digital Port) Table 8-360. Test #565 Digital Port Sanity Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a valid ISDN-PRI test call. Use the list isdn-testcall command to determine which call is using the port (from the M/T Port column). Either wait for the test call to complete (as indicated in the Start Time Duration...
Page 150 Maintenance Object Repair Procedure Table 8-360. Test #565 Digital Port Sanity Test — Continued Error Test Code Result Description / Recommendation FAIL The switch was unable to communicate with the port circuitry used for digital trunk testing. FAIL Data was not sent from port 2 to port 3 successfully in asynchronous mode. FAIL Data was not sent from port 3 to port 2 successfully in asynchronous mode.
Page 151 M/T-DIG (Maintenance/Test Digital Port) Hook State Inquiry (#566) This test ensures that the Maintenance/Test digital port maintenance software and call processing agree on the on-/off-hook status of the Maintenance/Test digital port. Table 8-361. Test #566 Hook State Inquiry Error Test Code Result Description / Recommendation...
Page 152 Maintenance Object Repair Procedure M/T-PKT (Maintenance/Test Packet Bus Port) MO’s Name As Initial System It Appears in Alarm Technician Command Alarm Log Level to Run Full Name of MO M/T-PKT Minor test port UUCSSpp l Maintenance/Test Packet Bus port M/T-PKT Warning release port UUCSSpp Maintenance/Test Packet...
Page 153 M/T-PKT (Maintenance/Test Packet Bus Port) Hardware Error Log Entries and Test to Clear Values M/T-PKT Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp 1 (a) 41018 none MINOR test port UUCSSpp l r 3 18 (b) busyout port UUCSSpp WARNING...
Page 154 Maintenance Object Repair Procedure When this alarm is active, the amber LED will be in one of three states: An unlit amber LED indicates no activity on the Maintenance/Test circuit pack. You can replace the Maintenance/Test circuit pack. If there is an indication of an uncorrectable fault on the packet bus, the amber LED will be blinking at a rate of 1 Hz.
Page 155 M/T-PKT (Maintenance/Test Packet Bus Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following table when inspecting errors in the system. Short Test Long Test Order of Investigation Sequence Sequence D/ND Packet Bus Port Health Inquiry test (#567) Clear Error Counters (#270) D = Destructive, ND = Nondestructive Clear Error Counters (#270)
Page 156 Maintenance Object Repair Procedure Packet Bus Port Health Inquiry Test (#567) This test verifies that the packet-bus fault-detection and maintenance function of the M/T-PKT is functioning properly. This is done by having the M/T-PKT perform a self-test. If the self-test passes, then the Packet Bus Port Health Inquiry test passes.
Page 157: No-Lic (No License)
S8700 IP Connect software along with a new feature mask. The feature mask controls revenue associated options.
Page 158 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 1 (a) MAJOR See Footnote 513 (b) None MAJOR See Footnote 769 (c) None MAJOR See Footnote 1281 (d) None...
Page 159 NO-LIC (No License) e. Error Type 1537 This error indicates the License File is missing or corrupted. Maintenance software notifies call-processing software to stop every new call origination, except outgoing calls to an emergency number and incoming calls to an administration number. f.
Page 160 Maintenance Object Repair Procedure OPS-LINE (DS1 Off-Premises Station Line) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO OPS-LINE MINOR test station extension l DS1 OPS Line OPS-LINE WARNING test station extension DS1 OPS Line An analog Off-Premises Station (OPS) can be connected to the system through a DS1 link.
Page 161 OPS-LINE (DS1 Off-Premises Station Line) Error Log Entries and Test to Clear Values Table 8-364. DS1 OPS Maintenance Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test station <ext> 15(a) Audit and Update test (#36) 18(b) busyout station <ext>...
Page 162 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the NPE Crosstalk test (#6), you may also clear errors generated from other tests in the testing sequence.
Page 163 OPS-LINE (DS1 Off-Premises Station Line) Table 8-365. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1002 ABORT The system could not allocate time slots for the test. The system may be under heavy traffic conditions or it may have time slots out-of-service due to TDM-BUS errors.
Page 164 Maintenance Object Repair Procedure Table 8-365. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation FAIL The test failed. This can be due to on-board or off-board problems. Off-board problems of concern include RMC-ENV faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators.
Page 165 OPS-LINE (DS1 Off-Premises Station Line) Conference Circuit Test (#7) One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM-bus interface. (The TN464 UDS1 circuit pack has one SCOTCH-NPE chip instead of several NPE chips). The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis.
Page 166 Maintenance Object Repair Procedure Table 8-366. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1020 ABORT The test did not run due to an already existing error on the specific port or due to a more general error on the circuit pack. 1.
Page 167 OPS-LINE (DS1 Off-Premises Station Line) Table 8-366. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1.
Page 168 Maintenance Object Repair Procedure Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface circuit pack to assure that the trunk’s translation is correct. Translation updates include the following data: line type, dial type, timing parameters, and signaling bits enabled.
Page 169 OPS-LINE (DS1 Off-Premises Station Line) Table 8-367. Test #36 Audit and Update Test — Continued Error Test Code Result Description / Recommendation PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack and switch software are consistent. If the trunk is busied out, the test will not run but will return PASS.
Page 170: Ds1 Ops Switchhook Inquiry Test
Maintenance Object Repair Procedure DS1 OPS Switchhook Inquiry Test (#312) This test initiates the Switchhook Audit test. The test queries the switchhook state of the Off-Premises-Station in switch software. If the state in switch software disagrees with the state on the DS1 Interface circuit pack, then the state in the switch software is updated to match the state on the DS1 Interface circuit pack.
Page 171 OPS-LINE (DS1 Off-Premises Station Line) Table 8-368. Test #312 DS1 OPS Switchhook Inquiry Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT The test was aborted because response to the test was not received within the allowable time period. 1.
Page 172: Pdata-Pt (Packet Data Line Port)
Maintenance Object Repair Procedure PDATA-PT (Packet Data Line Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO PDATA-PT MINOR test port UUCSSpp PDATA Port Maintenance PDATA-PT WARNING release port UUCSSpp PDATA Port Maintenance UU is the universal cabinet number (1–64).
Page 173 PDATA-PT (Packet Data Line Port) Data Applications and System Port Connectivity As part of each data application, the SPE connects itself to the application device through a system port. The application device may be an external terminal, printer, or data-module, or it may be circuitry internal to the switch, as is the case for the Announcement Circuit pack data-module used to save and restore recorded announcements.
Page 174 Maintenance Object Repair Procedure Testing the System Port Pool This section describes a method for isolating a bad system port when its location is not known. A pool of system ports is used to service the set of application features listed above. The system supports up to 10 system ports. Since each Data Line Circuit pack provides 8 ports and each PDATA provides 12 ports, 2 Data Line Circuit packs and one PDATA Circuit pack are required if all 10 system ports are to be administered.
Page 175 PDATA-PT (Packet Data Line Port) Locating MOs when Data Application Link Fails This sequence of steps should be used if the application is experiencing problems and the health of the ports is unknown. 1. Using column three of the commands table below, find the command to display the status of the application link.
Page 176 Maintenance Object Repair Procedure 2. If the port is a system port, enter status data-module ext. Record the Data Line or PDATA port. If there is a connected port do the following: a. Record the location of the connected port. b.
Page 177 PDATA-PT (Packet Data Line Port) Table 8-369. Data Application Commands Application Command to Display Command to Locate the Application Name MO’s Name Link Status Extension Announcement circuit Not applicable Not Applicable display announcements pack CDR-LNK status cdr-link display sys-param cdr Wakeup Log printer for JRNL-LNK status journal-link...
Page 178 Maintenance Object Repair Procedure Table 8-370. Wiring Table for the System Ports Feature (eight ports) Data Line Port PDATA Port Amphenol Carrier Lead Carrier Lead Amphenol Port Connector Pin # Appearance Appearance Connector Pin # TXT1 PXT1 TXR1 PXR1 PXT1 TXT1 PXR1 TXR1...
Page 179 PDATA-PT (Packet Data Line Port) Table 8-370. Wiring Table for the System Ports Feature (eight ports) — Continued Data Line Port PDATA Port Amphenol Carrier Lead Carrier Lead Amphenol Port Connector Pin # Appearance Appearance Connector Pin # TXT5 PXT5 TXR5 PXR5 PXT5...
Page 180 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-371. PDATA Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) LAP-D Connectivity test MINOR test port UUCSSpp r 3...
Page 181 PDATA-PT (Packet Data Line Port) c. These three counters are incremented for errors which may or may not be caused by the PDATA port itself. For example, the Invalid LAP-D Frame counter (error type 513) could exceed threshold due to a large number of “bad CRC”...
Page 182 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the PDATA Port Local Loop-Around test (#602), you may also clear errors generated from other tests in the testing sequence.
Page 183 PDATA-PT (Packet Data Line Port) Table 8-372. Test #558 LAP-D Connectivity Test Error Test Code Result Description / Recommendation 1000 ABORT The port is in use for a call. Use status data-module extension command to determine when the port is available for testing. 1.
Page 184 Maintenance Object Repair Procedure Table 8-372. Test #558 LAP-D Connectivity Test — Continued Error Test Code Result Description / Recommendation FAIL Response to the test was not received for the PDATA circuit pack within the allowable time period. 1. Retry the command at 1-minute intervals up to 3 times. 2.
Page 185 PDATA-PT (Packet Data Line Port) Table 8-373. Test #602 PDATA Port Local Loop-Around Test Error Test Code Result Description / Recommendation 1000 ABORT The port is in use for a call. Use status data-module extension command to determine when the port is available for testing. 1.
Page 186 Maintenance Object Repair Procedure System Port Connectivity Test (#603) This test is destructive. This test verifies the capability to communicate between the PDATA and the Data Line (TN 726B) ports of a System Port member. A System Port requires the PDATA port and the Data Line port to be wired together.
Page 187 PDATA-PT (Packet Data Line Port) Table 8-374. Test #603 System Port Connectivity Test — Continued Error Test Code Result Description / Recommendation 1115 ABORT The PDATA port resources could not be allocated. 1. Run the busyout port UUCSSpp 2. Run the test again 3.
Page 188: Pdmodule (Processor Data Module)
Maintenance Object Repair Procedure PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO PDMODULE MINOR test port UUCSSpp l Processor Data Module PDMODULE WARNING test port UUCSSpp s Processor Data Module TDMODULE MINOR...
Page 189 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) Stand-Alone DCP Data Modules There are two types of stand-alone DCP data modules: Table 8-375. Stand-Alone DCP Data Modules Type Name Interfaces to: MPDM Modular Processor DTE (data terminals, host computers, printers, etc.) Data Module MTDM Modular Trunk Data...
Page 190 Maintenance Object Repair Procedure Configurations and Maintenance In the following discussion, the general term data module refers to MPDMs, MTDMs, and DAs. The PBX loop or digital link between a data module and the Digital Line port supports two logical information channels and one signaling channel.
Page 191 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) G3 PBX MPDM or DA Physical Connection stand-alone Digital mode Line Primary Information Channel Circuit Terminal Pack Signaling ..........(Secondary Information Channel unused) Physical Connection...
Page 192 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-377. PDMODULE, TDMODULE Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) None 1 (b,n) 40987 None WARNING 1 (c,n) 1 –...
Page 193 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) Notes: a. Error type 0 appears in the Error Log only if a Digital Line circuit pack that has ports administered has been removed since the Error Log was last cleared. Make sure that the circuit pack has been re-inserted. b.
Page 194 Maintenance Object Repair Procedure l. Error type 3841 indicates that the downlink buffer on the circuit pack has overflowed. No action is necessary. m. A DCP endpoint may have been disconnected. n. Make sure the data module is connected and operating properly. Check for faulty wiring.
Page 195 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) NPE Crosstalk Test (#9) The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, one-way and noisy connections may be observed.
Page 196: Information And Control Channel Local Loop Test
Maintenance Object Repair Procedure Table 8-378. Test #9 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1020 ABORT Test disabled via background testing. Use status data-module command to determine when the data module is available for testing. 2000 ABORT Response to the test request was not received within the allowable time period.
Page 197 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) With the port still in loop-around mode, the S Channel Loop-around test is performed next. This test consists of sending four different transparent patterns to the on-board microprocessor, receiving them back, and comparing them. The third test is a loop around test for the secondary information channel.
Page 198 Maintenance Object Repair Procedure Table 8-379. Test #13 Information and Control Channel Local Loop Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. 1.
Page 199: Data Module Audits Test
PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) Data Module Audits Test (#17) This is a series of six tests that are classified as hardware audits. The processor sends messages to the on-board microprocessor to perform the following tests: Switchhook Inquiry — This is an update of the processor’s software records based on the on-hook/off-hook status of the data module.
Page 200 Maintenance Object Repair Procedure Table 8-380. Test #17 Data Module Audits Test — Continued Error Test Code Result Description / Recommendation ABORT Ringer update aborted (data module not in the in-service state) 1. Verify that the data module is powered (power LED on). 2.
Page 201 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) For this test to run, the Remote Loop-Around Test field on the Data Module administration form must be set to y, indicating that the data module endpoint supports the test. Switch TN771 Maintenance/ Test circuit Data module...
Page 202 Maintenance Object Repair Procedure Table 8-381. Test #175 Data Module Internal Loop-Around Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use on a valid call. Use status data-module to determine when the port is available for testing.
Page 203 PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module) Table 8-381. Test #175 Data Module Internal Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1392 ABORT This port is currently a TTI port and the test will not execute on it. 1.
Page 204 Maintenance Object Repair Procedure Table 8-381. Test #175 Data Module Internal Loop-Around Test — Continued Error Test Code Result Description / Recommendation 2500 ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. FAIL Data received from remote loop back does not match data sent. 1.
Page 205: Pe-Bchl (Pri Endpoint Port)
PRI terminal adapters. In the same sense that a S8700 IP Connect data module acts as a DCP or BRI terminal adapter between endpoint data such as V.35 and...
Page 206 (ISDN-LNK). The signaling protocol used on the ISDN-PRI signaling-link port’s D channel is defined by one of the four selectable ISDN-PRI Specifications: Avaya, CCITT, ECMA, and ANSI. The ISDN-PRI Specification defines the possible service states for a B channel. The service state is negotiated with the far-end terminal adapter, changes over time, and can have far- and near-end components.
Page 207 PE-BCHL (PRI Endpoint Port) A PRI endpoint port is a port on a UDS1 interface circuit pack and thus depends on the health of the circuit pack for proper operation (see the following figure). A problem on the associated ISDN-LNK’s (ISDN-PRI signaling-link port’s) D channel can also affect the PRI endpoint.
Page 208 Maintenance Object Repair Procedure Out-of-Service/Far-End (OOS/FE) A B channel is initialized to this state when first administered. The switch then sends messages to the far-end terminal adapter to negotiate the B channel into service. If the far-end terminal adapter does not respond to the messages within a certain time period, the port remains out of service, and maintenance will periodically resend the messages.
Page 209 PE-BCHL (PRI Endpoint Port) Table 8-382. PRI Endpoint Port Service States Service State Alarm Possible Cause Possible Solution OOS/NE Warning Port has been busied out by Enter release pri-endpoint extension. command. Minor NPE Crosstalk test (#6) Replace UDS1 circuit pack. failed.
Page 210 Maintenance Object Repair Procedure Table 8-382. PRI Endpoint Port Service States — Continued Service State Alarm Possible Cause Possible Solution Normal operating state. ISDN wideband calls being completed. Continued on next page Out-of-Service Maintenance Far-end Near-end PINS Pending in-service OUT-OF- MAINTENANCE SERVICE NEAR END...
Page 211 PE-BCHL (PRI Endpoint Port) Error Log Entries and Test to Clear Values Table 8-383. PRI endpoint port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) None test port UUCSSpp sh r 1 15 (b)
Page 212 Maintenance Object Repair Procedure d. The far-end terminal adapter changed its ISDN service state to either out-of-service or maintenance. This may be a temporary condition due to testing of this port by the far-end terminal adapter or a hardware problem with the port.
Page 213 PE-BCHL (PRI Endpoint Port) PE-BCHL Error 3585 Aux Data Data Meaning A call in a stable, talking state (the active state) was cleared unexpectedly by the far-end terminal adapter with an ISDN RESTART message. A call that has not reached the active state, but has at least reached a ringing state, was cleared unexpectedly by the far-end terminal adapter with an ISDN RESTART message.
Page 214 Maintenance Object Repair Procedure NPE Crosstalk Test (#6) The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, one-way and noisy connections may be observed.
Page 215 PE-BCHL (PRI Endpoint Port) Table 8-384. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 2020 ABORT The test did not run due to an existing error on the specific port or a more general circuit pack error. 1.
Page 216 Maintenance Object Repair Procedure Table 8-385. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1020 ABORT The test did not run due to an already existing error on the specific port or a more general circuit pack error. 1.
Page 217 PE-BCHL (PRI Endpoint Port) Audit and Update Test (#36) This test sends port level translation data from switch processor to the UDS1 interface circuit pack to assure that the port’s translation is correct. The port audit operation verifies the consistency of the current state of port kept in the UDS1 interface circuit pack and in the switch software.
Page 218: Signaling Link State Check Test
Maintenance Object Repair Procedure Signaling Link State Check Test (#255) As noted in the preceding general description, operation of the PRI endpoint port depends on the health of the UDS1 interface circuit pack and System Link for proper operation. This test checks the status of those critical elements. Table 8-387.
Page 219 PE-BCHL (PRI Endpoint Port) Service State Audit (#256) As noted in the general description for PRI endpoint port, these ports may be in one of several service states as defined by the ISDN-PRI Specification. This test performs a service state audit with the far-end terminal adapter to ensure both sides agree on the service state.
Page 220 Maintenance Object Repair Procedure Table 8-388. Test #256 Service State Audit Test — Continued Error Test Code Result Description / Recommendation PASS Wait 4 minutes and then check the Error Log for any new errors of type 3073. If there are none, then both sides of the ISDN connection agree on the service state;...
Page 221 PE-BCHL (PRI Endpoint Port) Table 8-389. Test #257 Call State Audit Test — Continued Error Test Code Result Description / Recommendation 1116 ABORT The port is in an out-of-service ISDN service state. 1. A call cannot be present if the port is in an ISDN out-of-service state, so a call state audit would be inappropriate.
Page 222: Pkt-Bus (Packet Bus)
Maintenance Object Repair Procedure PKT-BUS (Packet Bus) MO’s Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO PKT-BUS MAJOR test pkt P l r 2 Packet Bus PKT-BUS MINOR test pkt P l Packet Bus PKT-BUS WARNING test pkt P l Packet Bus...
Page 223 PKT-BUS (Packet Bus) This section on the PKT-BUS MO is limited to a description of the Error and Alarm Log entries and the test sequence for the packet bus. The following list summarizes some of the important points to consider when working with the packet bus.
Page 224 Maintenance Object Repair Procedure Hardware Error Log Entries and Test to Clear Value Table 8-390. PKT-BUS Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test pkt port-network 1 (a) 1–2 Packet circuit pack MAJOR test pkt port-network P l r 2 Audit test (#570)
Page 225 PKT-BUS (Packet Bus) e. Packet circuit pack, port, and endpoint maintenance has been disabled due to a packet bus failure. The Aux Data value indicates the cause: Data Cause In-line errors from packet circuit packs Uncorrectable packet bus fault reported by the Maintenance/Test packet bus port (M/T-PKT) Both of the above 100x...
Page 226 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following tables. For example, by clearing error codes associated with the Packet Circuit Pack Audit test (#573), you may also clear errors generated from other tests in the testing sequence.
Page 227 PKT-BUS (Packet Bus) Table 8-391. Test #572 Maintenance/Test Circuit Pack Query Test — Continued Error Test Code Result Description / Recommendation 1142 ABORT No Maintenance/Test circuit pack packet bus port is in service in this EPN. 1. If this EPN is required by configuration guidelines to have a Maintenance/Test circuit pack (i.e., it is either a PPN or else an EPN in a system having both SPE and PNC duplication) either: a.
Page 228 Maintenance Object Repair Procedure Table 8-391. Test #572 Maintenance/Test Circuit Pack Query Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT Maintenance could not allocate every necessary system resource to perform this test. 2500 ABORT An internal operation failed; the test could not be completed. 1.
Page 229 PKT-BUS (Packet Bus) Packet Circuit Pack Audit Test (#573) This test determines whether Packet circuit packs have reported Packet Bus-related in-line errors within the last minute. If so, the failure code indicates whether one or more than one circuit pack has reported such failures. If the test has failed within the last 5 minutes, there is a 15 second delay before the result is returned.
Page 230: Pkt-Int (Packet Interface)
Maintenance Object Repair Procedure PKT-INT (Packet Interface) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO PKT-INT MAJOR reset packet-interface UC Packet Interface PKT-INT MINOR test packet-interface UC Packet Interface PKT-INT WARNING test packet-interface UC Packet Interface UU is the universal cabinet number (1–64).
Page 231 PKT-INTs within IPSIs that are distributed out to every EPN. Whereas, G3r allowed up to three active and three standby PKT-INTs in the PPN, S8700 IP Connect allows one PKT-INT in each EPN (that is, up to 64 PKT-INTs in the system).
Page 232 Description of Components and Connections in Figure 8-37 S8700 Media Server 1 – Two are always present, one in a active mode and the other on standby. S8700 Media Server 2 – Two are always present, one in a active mode and the other on standby.
Page 233: Add Ipserver-Interface
VLAN and 10/100 mbps. Port Network – optional configuration of Media Gateways that provides increased switch capacity. IPSI – provides transport of CCMS messages over IP allowing the S8700 Media Server to communicate with the port networks. Customer LAN...
Page 234 Maintenance Object Repair Procedure A demand reset of a standby Packet Interface circuit is not disruptive and is allowed regardless of the service state of the associated maintenance software. Service States Packet Interface maintenance software maintains a state variable to monitor the in-service/out-of-service state of each Packet Interface circuit.
Page 235 PKT-INT (Packet Interface) Issue the status packet-interface command to determine the: — Service state of the Packet Interface circuit (for example, in service/out of service) — Total number of Packet Interface links assigned to a Packet Interface circuit. For a standby IPSI’s Packet Interface circuit in a high-reliability system (duplicated IPSIs), the circuit (if not out of service due to a failure condition) is shown in “standby”...
Page 236 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-393. Packet Interface Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test packet-interface Uc l r 2 1 (a) None MAJOR reset packet-interface Uc...
Page 237: Escalation Procedures
PKT-INT (Packet Interface) Notes: a. Error 1 occurs when background maintenance software has reset the Packet Interface circuit as a fault recovery action. It is used to keep track of the number of times that the Packet Interface circuit is reset, independent of whether or not the Reset test passed.
Page 238 Maintenance Object Repair Procedure e. Error 513 is called Message Handshake failure. It indicates that a failure with the message protocol between the server’s software and the Packet Interface circuit was detected. 1. If the Packet Interface has a MAJOR alarm: a.
Page 239 PKT-INT (Packet Interface) j. Error 1793 indicates a FLASH Memory test failure. The Packet Interface circuit may still be operational if no other errors are reported. However the circuit may report a fatal fault during board initialization. This may occur during a system recovery level more severe than a WARM restart.
Page 240 Maintenance Object Repair Procedure o. Errors 3074, 3073, and 3072 indicate PKT-INT Transmit Buffer Overflow, which means that the number of transmit buffers required by software exceeded the number available. A 3074 error is generated when the PKINT sends an in-line hardware error to maintenance software indicating transmit buffer overflow.
Page 241 PKT-INT (Packet Interface) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. By clearing error codes associated with the Packet Interface Private Loop-Around test for example, you may also clear errors generated from other tests in the testing sequence.
Page 242 Maintenance Object Repair Procedure Table 8-394. Test #884 Memory Checksum Test Error Test Code Result Description / Recommendation 1006, ABORT Since the IPSI’s Packet Interface circuit is out of service, normal maintenance 1137 tests do not run on the IPSI circuit pack. 1.
Page 243 PKT-INT (Packet Interface) Table 8-394. Test #884 Memory Checksum Test — Continued Error Test Code Result Description / Recommendation FAIL The Flash memory checksum test failed. The circuit pack may still be operational, but will fail if a reset is executed. 1.
Page 244 Maintenance Object Repair Procedure Table 8-395. Test #885 Private Loop-Around Tests Error Test Code Result Description / Recommendation 1006, ABORT Packet Interface circuit is out of service, so normal maintenance tests do not 1137 run on that circuit. 1. Enter reset packet-interface Uc to reset the Packet Interface circuit. For further action, see the procedures in Table 8-394 on page 8-938 for the...
Page 245 PKT-INT (Packet Interface) Table 8-395. Test #885 Private Loop-Around Tests — Continued Error Test Code Result Description / Recommendation FAIL The Private Link Broadcast Loop-Around test failed. The circuit pack will enter a fatal fault state when this occurs and the Packet Interface maintenance software should put the circuit in a out-of-service state.
Page 246 Maintenance Object Repair Procedure Maintenance Loop-Around Test (#886) This test checks whether an IPSI circuit pack’s Packet Interface circuit can send and receive data correctly. It establishes a LAP-D link from the IPSI’s Packet Interface circuit back to the same Packet Interface circuit, and transmits and receives test data over that testing link.
Page 247 PKT-INT (Packet Interface) Table 8-396. Test #886 Maintenance Loop-Around Test — Continued Error Test Code Result Description / Recommendation 2060 ABORT Packet link’s bus went down during maintenance loop-around test. 1. Retry the command at 1-minute intervals up to 5 times. 2.
Page 248 Maintenance Object Repair Procedure Table 8-396. Test #886 Maintenance Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1–3 FAIL The test failed. Either maintenance could not establish a loop-around link from the IPSI’s Packet Interface circuit back to itself or could not receive data that was sent on one side of the loop-around link.
Page 249 PKT-INT (Packet Interface) Read and Clear Board Counters (#887) This test involves sending commands to read circuit pack error counters located on the IPSI circuit pack’s Packet Interface circuit. It also verifies the message interface between the server and the Packet Interface circuit. This test checks different circuit pack counters.
Page 250: Hardware Configurations
Maintenance Object Repair Procedure Table 8-397. Test #887 Read and Clear Board Counters — Continued Error Test Code Result Description / Recommendation 256, FAIL The active IPSI circuit pack’s Packet Interface circuit has an error counter set. 512, The following error codes are possible: 256 (parity error), 512 (FIFO overflow), 768 (parity error and FIFO overflow error).
Page 251 PKT-INT (Packet Interface) Table 8-397. Test #887 Read and Clear Board Counters — Continued Error Test Code Result Description / Recommendation 1024– FAIL The standby IPSI’s Packet Interface circuit has bad Translation RAM 1096 locations. A MINOR alarm is generated when the number of bad locations is from 1 and 4.
Page 252 Maintenance Object Repair Procedure Table 8-398. Test #889 Reset Test Error Test Code Result Description / Recommendation 1334 ABORT The Packet Interface circuit’s command queue is full. This should be a temporary condition caused by a high rate of commands being sent to a Packet Interface circuit.
Page 253: Plat-Alm (Platform Alarms)
PLAT-ALM (Platform Alarms) PLAT-ALM (Platform Alarms) The PLAT-ALM is a virtual MO used by the S8700 IP Connect’s MultiVantage software to keep track of its server alarms. A MAJOR, MINOR, or WARNING alarm can be logged against this MO to indicate the presence of one or multiple S8700 server alarms.
Page 254: Pms-Link (Property Management System Link)
Maintenance Object Repair Procedure PMS-LINK (Property Management System Link) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO PMS-LINK MINOR test pms l PMS Link PMS-LINK WARNING test pms PMS Link Property Management System (PMS) is a stand-alone computer system that environments such as hotels or hospitals use for services such as reservations, registration, messaging, housekeeping, night audit, billing, and inventory.
Page 255 PMS-LINK (Property Management System Link) PMS Link Maintenance does not cover the maintenance of the elements composing the PMS physical link (the external PMS device, Data Module (PDM/MPDM/DTDM), Digital Line Port of a TN754 Digital Line circuit pack, ADU, or Data Line Port of TN726B Data Line circuit pack). If PMS Link Maintenance cannot restore the PMS Link, then the maintenance tests of these individual components of the PMS Link must be executed to diagnose faults.
Page 256 Maintenance Object Repair Procedure Hardware Error Log Entries and Test to Clear Values Table 8-399. PMS Link Maintenance Error Log Entries Error Alarm On/Off Type Aux Data Associated Test Level Board Test to Clear Value test pms sh r 1 18 (a) busyout pms-link WARNING...
Page 257 PMS-LINK (Property Management System Link) c. The PMS physical link is down for one of the following reasons: Cable to the PMS device is disconnected. The PMS device is powered off. The data extension to which the PMS device connects has been busied out.
Page 258 Maintenance Object Repair Procedure i. The attempt to swap the database between PBX and PMS failed three times consecutively due to excessive PMS/PBX protocol violations, buffer overflows, or PMS Link outages. The PMS Link is NOT torn down. If this error type occurs frequently (more than once a month), advise the customer to call the vendor of the PMS to check out the PMS device.
Page 259 PMS-LINK (Property Management System Link) The PMS should be assessed for adherence to the PMS/PBX protocol specifications. m. The link was taken down by the switch because the threshold for application protocol violations has been exceeded by the PMS. The protocol never started and messages were received and/or messages were received in a state in which they were not expected.
Page 260 Maintenance Object Repair Procedure Link Tear Down Test (#213) This test is destructive. This test disconnects the existing link between the system and the external PMS device. If the link has been disconnected already, then this test just returns “PASS.” Every resource allocated for a PMS Link is released after this test. Table 8-400.
Page 261 PMS-LINK (Property Management System Link) Link Retry Test (#215) This test sends a message to the PMS software process to make a data call to the extension where the PMS device connects. If the PMS Link is already up, then this test passes without making any data call.
Page 262: Pms-Prnt/Jnl-Prnt (Pms Printer Link)
Maintenance Object Repair Procedure PMS-PRNT/JNL-PRNT (PMS Printer Link) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO PMS-PRNT/JNL-PRNT MINOR test journal [pms-log | PMS Printer/ Journal wakeup-log] l Printer PMS-PRNT/JNL-PRNT WARNING test journal [pms-log | PMS Printer/ Journal wakeup-log] Printer...
Page 263 PMS-PRNT/JNL-PRNT (PMS Printer Link) PMS/JOURNAL Printer Link Maintenance provides a strategy for maintaining the link between the system and a PMS device (an external Journal Printer device). The strategy includes a set of tests for periodic diagnosis, detection of errors during normal operation, actions for troubleshooting, and raising alarms for serious problems.
Page 264 Maintenance Object Repair Procedure It should be noted that when restoring the PMS printer link, it is necessary to execute tests on different MOs that comprise the link; it is recommended that you busyout the PMS printer link before trying to restore the link. If the PMS printer Link is busied out, then every PMS printer Link maintenance action is deactivated, and interference with tests of other MOs is prevented.
Page 265 PMS-PRNT/JNL-PRNT (PMS Printer Link) d. Link idle timer; link comes down. This indicates that the printer device is in an off-line state, for example, paper jam or paper out. Check the printer device and act promptly to put it back to on-line state. Enter test journal wakeup-log|pms-log command to set up the printer link.
Page 266 Maintenance Object Repair Procedure Link Tear Down Test (#213) This test is destructive. This test disconnects the existing link between the system and the external printer device. If the link has been disconnected already, this test just returns PASS. Every resource allocated for a PMS Printer Link is released after this test. Table 8-403.
Page 267 PMS-PRNT/JNL-PRNT (PMS Printer Link) Link Retry Test (#215) This test sends a message to the journal printer management software process to make a data call to the extension where the printer device connects to. If the journal printer link is already up, this test passes without making any data call. Table 8-404.
Page 268: Ppp-Pt (Control Lan Packet/Port)
Maintenance Object Repair Procedure PPP-PT (Control LAN Packet/Port) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO PPP-PT MAJOR test port UUCSSpp long PPP Port Maintenance PPP-PT MINOR test port UUCSSpp long PPP Port Maintenance PPP-PT WARNING test port UUCSSpp...
Page 269 PPP-PT (Control LAN Packet/Port) Error Log Entries and Test to Clear Value Table 8-405. PPP-PT Error Log Entries Alarm On/Off Error Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp s 1 (a) SCOTCH Sync MINOR test port UUCSSpp l r 3 Looparound test (#1275) 257 (b)
Page 270 Maintenance Object Repair Procedure c. Error Type 513: PPP link lost end-to-end connectivity. 1. Test for hardware problem (test port UUCSSpp long). 2. Run TDM Loop-around test (#1285), and refer to repair procedures if there is a hardware problem. If there is no hardware problem, the switch tries to re-establish PPP link.
Page 271 PPP-PT (Control LAN Packet/Port) h. Error Type 2305-2816: System software detected a session is down. Aux Data indicates the session number. These are log only errors. Error types 2305–2560 are for session numbers 1–256. Error types 2561–2816 are for session numbers 257–512. i.
Page 272 Maintenance Object Repair Procedure TDM Loop-Around Test (#1285) NOTE: This test is destructive. This test verifies whether the C-LAN PPP port can send and receive data on the TDM bus. This test has a tone generator send tones on a timeslot, and it has a tone receiver receive tones on another timeslot.
Page 273: Busyout Data-Module
PPP-PT (Control LAN Packet/Port) Table 8-407. Test #1285 TDM Loop-Around Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Did not receive circuit pack test response within the allowable time period. 1. If this problem persists, reset the circuit pack (busyout board UUCSS, reset board UUCSS, and release board UUCSS).
Page 274 Maintenance Object Repair Procedure Table 8-408. Test #1275 SCOTCH Synchronous Loop-Around Test Error Test Code Result Description / Recommendation 1000 ABORT The port is in use or PPP link is connected. 1. Determine when the port is available for testing (status clan-port UUCSSpp).
Page 275 PPP-PT (Control LAN Packet/Port) TCP/IP Ping Test (#1281) This nondestructive test fails if the endpoint fails to respond. Use this test to check the circuitry in the data path for a peer-to-peer IP layer connection. Table 8-409. Test #1281 TCP/IP Ping Test Error Test Code...
Page 276 Maintenance Object Repair Procedure Table 8-409. Test #1281 TCP/IP Ping Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT Could not allocate the necessary system resources to run test. 1. Retry the command at 1-minute intervals up to 5 times. 2.
Page 277 PPP-PT (Control LAN Packet/Port) Table 8-410. Test #1286 Session Status Test Error Test Code Result Description / Recommendation 1124 ABORT PPP link is not enabled. 1. Verify that the ppp link is enabled (status port UUCSSpp, status link n, or display data-module).
Page 278 Maintenance Object Repair Procedure PPP Link Status Inquiry Test (#1279) This nondestructive test determines the state of the PPP link. The test passes only if the link is up. Table 8-411. Test #1279 PPP Link Status Inquiry Test Error Test Code Result Description / Recommendation...
Page 279 PPP-PT (Control LAN Packet/Port) Table 8-411. Test #1279 PPP Link Status Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL PPP link is down. 1. Test the port (test port UUCSSpp long) to verify the SCOTCH Synchronous Local Loop Around test (#1275) result. 2.
Page 280 Maintenance Object Repair Procedure PRI-CDR/SEC-CDR (Call Detail Recording Link) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO PRI-CDR/SEC-CDR MINOR test cdr primary/secondary l CDR Link PRI-CDR/SEC-CDR WARNING test cdr primary/secondary CDR Link The CDR feature records detailed call information about every incoming and outgoing call on specified trunk groups and sends this information to a CDR output device.
Page 281 PRI-CDR/SEC-CDR (Call Detail Recording Link) CDR Link Maintenance does not cover the maintenance of the elements composing the CDR physical link: External CDR output device Data Module (PDM/MPDM/DTDM) and Digital Line Port of TN754 Digital Line circuit pack ADU and Data Line Port of TN726B Data Line circuit pack If CDR Link Maintenance cannot restore the CDR link, the maintenance tests of these individual components of the CDR link must be executed to diagnose faults.
Page 282 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-412. CDR Link Maintenance Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test cdr primary|secondary sh 18 (a) busyout cdr WARNING release cdr primary|secondary...
Page 283 PRI-CDR/SEC-CDR (Call Detail Recording Link) e. Software detects an overflow of CDR records generated in the switch due to the heavy trunk traffic and low speed CDR output device. If both primary and secondary links are ON, the secondary link is torn down temporarily for two minutes to speed up the output process to the primary link.
Page 284 Maintenance Object Repair Procedure Link Tear Down Test (#213) This test is destructive. This test disconnects the existing link between the system and the external CDR output device. If the link has been disconnected already, this test just returns PASS. Every resource allocated for a CDR link is released after this test. Table 8-413.
Page 285 PRI-CDR/SEC-CDR (Call Detail Recording Link) Link Retry Test (#215) This test sends a message to the CDR software process to make a data call to the extension where the CDR output device connects to. If the CDR link is already up, then this test will be passed without making any data call.
Page 286: Proc-San (Process Sanity Audits)
Maintenance Object Repair Procedure PROC-SAN (Process Sanity Audits) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO PROC-SAN none none Process Sanity Audits The Process Sanity Audits MO is responsible for monitoring the sanity of software processes in the system.
Page 287: Ralm-Svc (Remote Alarm Service)
RALM-SVC (Remote Alarm Service) RALM-SVC (Remote Alarm Service) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO RALM-SVC SUPER None Remote Alarm Service RALM-SVC MAJOR None Remote Alarm Service For the RALM-SVC MO, maintenance software does special periodic testing every 60 seconds.
Page 288 Maintenance Object Repair Procedure RANL-STA (Remote Analog Line (Station) Port MO’s Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO RANL-STA MINOR test port UUCSSpp l Remote Analog Line Port RANL-STA WARNING test port UUCSSpp sh Remote Analog Line Port UU is the universal cabinet number (1–64).
Page 289 RANL-STA (Remote Analog Line (Station) Port Error Log Entries and Test to Clear Values Table 8-417. Analog Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 40960, none...
Page 290 Maintenance Object Repair Procedure c. Error type 257—An in-line error and can only be resolved over time. This error indicates that ringing voltage is absent. If only one analog circuit pack in the system has this problem, then replace the circuit pack. If only analog circuit packs on a particular carrier have this error, then the ringing generator may not be connected to this carrier.
Page 291 RANL-STA (Remote Analog Line (Station) Port Battery Feed Test (or Port Diagnostic test) (#35) The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing, transmission, and balance. This test checks the signaling and switchhook capabilities of the battery feed chip by terminating the port, applying battery and detecting the resulting current.
Page 292 Maintenance Object Repair Procedure Table 8-418. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABORT Could not allocate the necessary system resources to run this test.
Page 293 RANL-STA (Remote Analog Line (Station) Port Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 8-419. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 294 Maintenance Object Repair Procedure Station Present Test (or Ringing Application Test) (#48) This test applies momentary ringing voltage to the terminal equipment and monitors resulting current flow to determine whether the terminal equipment is connected to the port. The test may cause some terminal equipment to ring briefly during daily maintenance.
Page 295 RANL-STA (Remote Analog Line (Station) Port Table 8-420. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABORT Could not allocate necessary system resources to run this test.
Page 296: Rdig-Sta (Remote Digital Station)
Maintenance Object Repair Procedure RDIG-STA (Remote Digital Station) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO RDIG-STA MINOR test station UUCSSpp l Remote Digital Station RDIG-STA WARNING test station UUCSSpp sh Remote Digital Station UU is the universal cabinet number (1–64).
Page 297 RDIG-STA (Remote Digital Station) Downloading of Terminal Parameters Programmable Terminals The following information describes how maintenance software interacts with terminal parameter downloading. Terminal Types a. 84xx multibutton digital voice terminals (8403D01A, 8410B, 8410D02A, 8434D01A) with optional expansion module. b. 603A1 and 603D1 Callmaster terminals for telemarketing applications. c.
Page 298 Maintenance Object Repair Procedure Download Actions There are several different scenarios which causes a terminal to be downloaded. These can occur as part of background maintenance activity or on demand from the SAT (System Access Terminal) or from a station. For the background actions described below, the terminal downloads automatically if a download retry flag for the terminal is set in software.
Page 299 RDIG-STA (Remote Digital Station) 4. Port Insertion Whenever maintenance software initiates a request to place a port into service, a terminal download action is begun on that terminal, if that terminal is programmable. This port insertion action occurs under the following circumstances: A digital line circuit pack that is physically inserted into the system and has ports currently administered for programmable terminals.
Page 300 Maintenance Object Repair Procedure A confirmation is returned if the download request is accepted. A busy tone is returned if the request is made from a different station when the target station is off-hook. As a result of an entry of a Refresh Terminal Parameters Facility Access Code, the first three green call appearance LEDs on the 84xx 603x terminal are turned on for three seconds, if the station was successfully downloaded.
Page 301 RDIG-STA (Remote Digital Station) Table 8-423. Digital Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 1 – 20, None WARNING 40987 18 (b) busyout port UUCSSpp WARNING re port UUCSSpp...
Page 302 Maintenance Object Repair Procedure Notes: a. Error type - 1; with Aux Data of 40987—Could be caused by a noisy port or link. This is an off-board problem detected by the port circuit. Check for defective wiring, a defective voice terminal, or move the voice terminal closer to the switch (in terms of feet of wire from the jack to the switch).
Page 303 RDIG-STA (Remote Digital Station) h. Error Type - 1537—An in-line maintenance error has generated an off-board warning due to a problem with the link to the voice terminal. This can be ignored if no user complaints are received. Otherwise, make sure the voice terminal is connected, check for defective wiring, check for a defective voice terminal, and move the voice terminal to a jack that is closer to the switch (in terms of feet of wiring between the jack and the...
Page 304 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the Digital Line Electronic Power Feed test (#11), you may also clear errors generated from other tests in the testing sequence.
Page 305 RDIG-STA (Remote Digital Station) Table 8-424. Test #11 Digital Line Electronic Power Feed Test Error Test Code Result Description / Recommendation ABORT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call.
Page 306 Maintenance Object Repair Procedure DIG-LINE Station Lamp Updates Test (#16) This test lights every lamp on the terminal as specified. The lamp updates will run only if the station is in-service. The status of the station is checked and the lamp updates are blocked from taking place, if the station is not in the in-service state.
Page 307 RDIG-STA (Remote Digital Station) Table 8-425. Test #16 DIG-LINE Station Lamp Updates Test — Continued Error Test Code Result Description / Recommendation PASS The message to light every station lamp was sent successfully to the port. 1. Observe the station lamps being lit when running the test. If every lamps does not light, the other Digital Line test results may indicate related problems that do not allow the lamps to light.
Page 308 Maintenance Object Repair Procedure Table 8-426. Test #17 Station (Digital) Audits Test Error Test Code Result Description / Recommendation ABORT Switchhook audit timed out. 1. Make sure voice terminal is connected and repeat test. 2. If test fails, replace voice terminal and repeat test. ABORT ID request fails, health bit returned from voice terminal is bad.
Page 309 RDIG-STA (Remote Digital Station) Table 8-426. Test #17 Station (Digital) Audits Test — Continued Error Test Code Result Description / Recommendation 1392 ABORT This port is currently a TTI port and the test will not execute on it. 1. Verify that the port is a TTI port using either the display port command (the display shows that the port is a TTI port) or the list config command (the display shows a for the port).
Page 310: Rem-Off (Remote Office)
Maintenance Object Repair Procedure REM-OFF (Remote Office) The physical location of the circuit pack in CCcss format C-LAN Board (cabinet, carrier, slot) Location The number of routes that were deleted from the TN799 Number of (C-LAN) route tables Routes Removed The number of routes that were added from the TN799 Number of (C-LAN) route tables...
Page 311 REM-OFF (Remote Office) Notes: a. Error Type - 1 — indicates that a PING test to the Remote Office has failed, and a MINOR alarm has been raised. The PING test verifies that a path to a registered Remote Office is good. When this error is logged, as many as 26 endpoints (associated with that Remote Office) and several H.323 signaling groups could be out of service.
Page 312: Multicarrier Cabinets
Maintenance Object Repair Procedure RING-GEN Analog Ring Generator MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO RING-GEN MAJOR test environment P Analog Ring Generator P is the port network’s number indicated in the PORT field from the Alarm or Error Log. Analog phones must be provided with a voltage that allows them to ring.
Page 313 RING-GEN Error Log Entries and Test to Clear Values Table 8-428. Analog Ring Generator Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test environment UU Analog Ring Generator Query MAJOR test environment UU r 3 (#118) Run the short test sequence first.
Page 314: Circuit Packs
Maintenance Object Repair Procedure Analog Ring Generator Initialization Test (#117) The Analog Ring Generator Initialization test sends a request to the active TN2312 IPSI circuit pack’s Tone-Clock circuit to monitor the voltage. The Tone-Clock responds with an error if the ringing voltage falls too low. Table 8-430.
Page 315: Analog Ring Generator Query Test
RING-GEN Analog Ring Generator Query Test (#118) The Analog Ring Generator Query test requests the active Tone-Clock circuit pack to check the ringing voltage. The Tone-Clock circuit pack replies with PASS if the ringing voltage is adequate to ring the analog phones. If not, the active Tone-Clock circuit pack replies with a FAIL.
Page 316 Maintenance Object Repair Procedure Table 8-431. Test #118 Analog Ring Generator Query Test — Continued Error Test Code Result Description / Recommendation FAIL 6. Since the test still fails, the ring generator is defective. (cont’d) a. If the reset button on the ring generator is out, press it in. b.
Page 317: Rmc-Env (Power/Fan Sensors)
Power/Fan Sensors The AC Power Supply (650A) for a S8700 IP Connect rack-mounted cabinet supports one alarm lead that indicates the state of both the power and fan. The cabinets use variable-speed fans to reduce noise. The power unit contains thermal speed control.
Page 318 Maintenance Object Repair Procedure fndpremv LJK 102600 Figure 8-38. Fan Removal Hardware Error Log Entries and Test to Clear Values Table 8-433. Cabinet sensors error log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test environment 1(a) Cabinet Temperature or...
Page 319 RMC-ENV (Power/Fan Sensors) (The fan and power lead is an O-ring of every cabinet’s status lead.) Since an error condition on a fan’s or power supply’s output could be the result of a temporary overload (e.g., during board insertion) or caused by the equipment’s location (e.g., fan blockage), a single event may be an anomaly that eventually clears.
Page 320 This test queries the Processor circuit pack for the status of the cabinet sensors in the Avaya IP600 cabinet. Only one alarm lead is supported by this cabinet type to indicate a power, temperature, or a fan problem. This means that a failure of this test can also mean a power problem, not necessarily just a temperature/fan problem.
Page 321 RMC-ENV (Power/Fan Sensors) Table 8-435. TEST #122 Cabinet Temperature Query Test Error Test Code Result Description / Recommendation 5. If the fans are running at high speed, check the items on following list. Any one of these could be restricting or redirecting the cabinet’s air flow. a.
Page 322 Put cross-ref to {ChapterTitle} here S-SYN-BD (Speech Synthesis Circuit Pack) MO’s Name Alarm Initial Command to (in Alarm Log) Level Full Name of MO S-SYN-BD MINOR test board UUCSS sh Speech Synthesis circuit pack S-SYN-BD WARNING test board UUCSS sh Speech Synthesis circuit pack UU is the universal cabinet number (1–64).
Page 323: S-Syn-Pt (Speech Synthesis Port)
S-SYN-PT (Speech Synthesis Port) S-SYN-PT (Speech Synthesis Port) MO’s Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO S-SYN-PT MAJOR test port UUCSSpp sh Speech Synthesis port S-SYN-PT MINOR test port UUCSSpp l Speech Synthesis port S-SYN-PT WARNING test port UUCSSpp sh...
Page 324 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-436. Speech Synthesis Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 17672 None busyout port UUCSSpp...
Page 325 S-SYN-PT (Speech Synthesis Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the NPE Crosstalk test (#6), you may also clear errors generated from other tests in the testing sequence.
Page 326 Maintenance Object Repair Procedure NPE Crosstalk Test (#6) The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, one-way and noisy connections may occur. This test is usually only part of a port’s long test sequence and takes about 20 to 30 seconds to complete.
Page 327 S-SYN-PT (Speech Synthesis Port) Table 8-437. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation FAIL The NPE of the tested port was found to be transmitting in error. This will cause noisy and unreliable connections. 1.
Page 328 Maintenance Object Repair Procedure Conference Circuit Test (#7) One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM-bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis. The Conference Circuit test verifies that the NPE channel for the port being tested can correctly perform the conferencing function.
Page 329 S-SYN-PT (Speech Synthesis Port) Speech Synthesis DTMF Receiver Test (#163) A series of dual-tone multifrequency (DTMF) tones are conferenced from the TDM bus into the port’s DTMF receiver and checked to see if the correct tones have been detected during the correct intervals. If every DTMF tone was detected correctly, the test passes.
Page 330: Speech Synthesis Dtmf Receiver Inquiry Test
Maintenance Object Repair Procedure Speech Synthesis DTMF Receiver Inquiry Test (#164) This test determines the sanity of the port’s dual-tone multifrequency (DTMF) receiver. The on-board microprocessor tests the port’s DTMF receiver and determines if it is in a sane (test passes) or insane (test fails) condition. Table 8-440.
Page 331 S-SYN-PT (Speech Synthesis Port) Table 8-441. TEST #165 Speech Synthesis DSP Tone Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABORT System resources required to run this test are not available.
Page 332: Speech Synthesis Memory Test
Maintenance Object Repair Procedure Speech Synthesis Memory Test (#166) The encoded speech for the Speech Synthesis circuit pack is stored in on-board read-only memory (ROM). A checksum is computed for each 32K speech memory block and compared against a known checksum value. If every computed checksum value is successfully compared against the stored checksum values, the test passes.
Page 333: Speech Synthesis Ssd Inquiry Test
S-SYN-PT (Speech Synthesis Port) Speech Synthesis SSD Inquiry Test (#167) This test determines the sanity of the specified port’s speech synthesis device (SSD). The on-board microprocessor tests the port’s SSD and determines if it is in a sane (test passes) or insane (test fails) condition. Other ports on the Speech Synthesis circuit pack will continue to function correctly during this type of failure.
Page 334 Maintenance Object Repair Procedure Speech Synthesis PSS Handshake Test (#168) This test verifies control functionality between the on-board microprocessor and programmable speech synthesizer (PSS) controller. A failure occurs if either of the following events occur: The on-board microprocessor times out while waiting for the PSS controller to respond.
Page 335: Speech Synthesis Parameter Update Test
S-SYN-PT (Speech Synthesis Port) Speech Synthesis Parameter Update Test (#169) This test updates the dual-tone multifrequency (DTMF) interdigit time-out parameter used by the Speech Synthesis circuit pack so that it is consistent with that specified by the server. Table 8-445. TEST #169 Speech Synthesis Parameter Update Test Error Test Code...
Page 336: Svc-Slot (Service Slot)
Maintenance Object Repair Procedure SVC-SLOT (Service Slot) MO’s Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO SVC-SLOT MINOR none Service Slot The Service Slot MO detects the insertion of an invalid circuit pack into a dedicated SERVICE slot.
Page 337 SVC-SLOT (Service Slot) Error Log Entries and Test to Clear Values Table 8-446. Service Slot Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 600 (a) None MINOR Note: a. Error type 600 indicates that an invalid circuit pack was inserted in slot 00, the SERVICE slot, of a J58890BB port carrier.
Page 338: Sync (Port-Network Synchronization)
Sync Operation IP-Connected S8700 Media Server For an S8700 IP Connect system, its port networks (PNs) are connected via the customer’s IP network. This network cannot be used to transmit timing information between the PNs. The complete set of PNs need not be synchronized with each other.
Page 339 IPSI’s Tone-Clock circuit provides the EPN’s timing source. If the system (PN for S8700 Media Server systems) is using the local oscillator as the timing source (both the primary and secondary references are providing invalid timing signals), should either the primary or secondary reference becomes valid again, the system (PN for S8700 Media Server systems) switches back to the primary or secondary source.
Page 340 Maintenance Object Repair Procedure When both the primary and secondary source become valid, the system (PN for S8700 Media Server systems) switches to the primary source, since the primary source is always preferred over the secondary source when both sources are equally healthy.
Page 341 SYNC (Port-Network Synchronization) When troubleshooting synchronization problems when slips are the primary error log entry indications of a synchronization problem, requires that the problem be isolated to: A problem outside of the switch (That is, the switch is not properly synchronized to the rest of the network.) A problem internal to the switch DS1 and UDS1 circuit packs can be administered with slip detection enabled via...
Page 342 Maintenance Object Repair Procedure Troubleshooting Synchronization Problems The following flow chart presents a logical approach to troubleshooting synchronization problems in conjunction with the previous background information. Explanatory notes follow the charts. of 6 Slips Enable Is synchronization synchronization. enabled? Is reference a Synchronization is enabled free-running IPSI for this port network.
Page 343 SYNC (Port-Network Synchronization) Retranslate to From have DS1 operate Fig 1 acccording to the network’s plan. Is this DS1 Examine cabinet’s Slips on DS1 supposed to be PN’s role in network’s facilities? timing reference? synchronization plan. Refer problem for investigation at other end of facility.
Page 344 Maintenance Object Repair Procedure Is there a Slips on Fix DS1-BD and DS1 reference loss-of-signal or UDS1-BD alarms. facilities? network alarm? Replace circuit packs: – IPSI/Tone-Clock in Escalate, if the the PN problem is not fixed. – DS1 in PN Problem is in PN, Are there Many...
Page 345 SYNC (Port-Network Synchronization) Figure 8-43. From Fig 1 Is reference on line? Is the reference administered and To Fig 3 SYNC enabled? Administer the To Fig 3 reference, and enable synchronization. Problem is in PN, Slips on IPSI’s IPSI’s Tone-Clock Escalate Tone-Clock circuit? or DS1s.
Page 346 Maintenance Object Repair Procedure Notes for Sheet 1 through Sheet 6 flowcharts. (When checking for slip errors, use the previous Table 8-447 on page 8-1037 Figure 8-40 on page 8-1038.): 1. Use the status synchronization cab # command to determine whether synchronization is enabled and to determine the on-line reference.
Page 347 SYNC (Port-Network Synchronization) Facility Fault Sectionalization DS1 facility fault sectionalization involves looping around the DS1 signal at on-site access points to localize the source of the problem to equipment and wiring on either the near side or far side of the loop-around point. WARNING: The facility fault sectionalization technique disrupts service.
Page 348 Maintenance Object Repair Procedure START (DS1 Interface refers to the TN722, TN767 or TN464 circuit pack.) Since this technique is time-consuming, ﬁrst ﬁx any DS1-BD, UDS1-BD, STRAT-3 or SYNC errors that are not slip errors. Enter busyout board for the DS1 Interface. This circuit pack should not be the on-line synchronization reference.
Page 349 SYNC (Port-Network Synchronization) Notes to Facility Fault Sectionalization Flowchart 1. Loop transmit to receive on the system side. Remove the transmit signal from the TN722, TN767, or TN464 circuit pack inputs and outputs and loop it around to the receive signal going toward the TN722, TN767, or TN464 circuit pack at the first unit wired to the TN722, TN767, or TN464 circuit pack.
Page 350 Maintenance Object Repair Procedure A correctly designed network has no loops, and each piece of equipment in the network is supplied by a clock with an equal or lower stratum number. (For example, the inputs to a Stratum-3 clock should never be from a Stratum-4 device.) CAUTION: Synchronization administration changes should never be done without...
Page 351 SYNC (Port-Network Synchronization) LEDs on Tone-Clock Circuit Packs The specific flashing pattern of a TN768, TN780, or TN2182 Tone-Clock circuit pack’s amber and green LEDs indicates the circuit pack’s status. For example, these flashing LED patterns are used to indicate whether the Tone-Clock circuit pack is: Deriving timing from an external source Providing the timing signal for its PN...
Page 352 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-449. Synchronization Maintenance Error Log Entries Associated On/Off Error Type Data Test Alarm Level Board Test to Clear Value test synchronization 1 (a)* None WARNING/MINOR (f) None 18 (b) disable sync WARNING...
Page 353 SYNC (Port-Network Synchronization) 5. Execute the disable synchronization-switch and then the enable synchronization-switch commands. These two commands (when executed together) will switch the system synchronization reference to the primary DS1 Interface circuit pack. 6. Check the Error Log and execute the status synchronization cab # command to verify that the primary DS1 Interface circuit pack is still the system synchronization reference.
Page 354 Maintenance Object Repair Procedure 3. For duplicated Tone-Clock circuit packs in the master port network, enter set tone-clock UUC command to switch the Tone-Clocks. For unduplicated Tone-Clock circuit packs in the master port network of a system, replace the primary and secondary (if assigned) DS1 Interface circuit packs.
Page 355 SYNC (Port-Network Synchronization) Table 8-450. Test #n (Name of) Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 3 times. 1115 ABORT Could not allocate the necessary system resources to run this test.
Page 356: Sys-Link (System Links)
Maintenance Object Repair Procedure SYS-LINK (System Links) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO SYS-LINK MINOR test sys-link UUCSSpp SYSTEM LINKS SYS-LINK WARNING test sys-link UUCSSpp SYSTEM LINKS System links are packet links that originate at the Packet Interface board and traverse various hardware components to specific endpoints.
Page 357 SYS-LINK (System Links) Identifying a System Link In order to trace problems associated with a system link, it is necessary to find its location. The following methods can be used to find the location of the system link: Display Errors/Alarms The output of the display errors or display alarm commands shows the location of the system link for entries with a Maintenance Name of SYS-LINK.
Page 358 Maintenance Object Repair Procedure The status sys-link location command shows the state of both the hardware paths (current and faulted) along with the state of each of the components in the hardware path. When analyzing any system link problem: 1. Look for alarms on the components listed under desired hardware path. 2.
Page 359 SYS-LINK (System Links) Notes: a. This error indicates that the link went down. The link may have gone down or never come up. Enter command status sys-link location and check the value of the Faulted Path field. If the value is default, then the link never came up.
Page 360 Maintenance Object Repair Procedure f. This error indicates that the link has experienced slow transmit rate because the remote endpoint is busy. The effect of this error is that the endpoint location may experience slower throughput rate and/or noisy transmission. The system link is alarmed if 4 or more errors of this type are detected within 10 minutes.
Page 361 SYS-LINK (System Links) Test command for the system links, test sys-link UUCSSpp can be specified with current or faulted as an optional argument if the user wishes to test every component in the specified path. The tests executed will be the same if the user were to test each component manually.
Page 362: Sys-Prnt (System Printer)
Maintenance Object Repair Procedure SYS-PRNT (System Printer) MO’s Name As It Initial System Appears in Alarm Alarm Technician Level Command to Run Full Name of MO SYS-PRNT MINOR test sp-link l System Printer SYS-PRNT WARNING release sp-link System Printer The Report Scheduler feature provides the capability to schedule printing of output form selected administration commands on an asynchronous System Printer (SYS-PRNT) or a Personal Computer (PC).
Page 363 SYS-PRNT (System Printer) Procedures for Restoring the System Printer Link 1. Determine the status of the System Printer Link via the status sp-link command. Verify that the System Printer Link is not busied out for maintenance. This is indicated by a no in the Maintenance Busy? field. If the System Printer Link has been busied out, issue the release sp-link command.
Page 364: Busyout Sp-Link
Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-453. SYS-PRNT Maintenance Error Log Entries Error Alarm On/Off Test to Clear Type Aux Data Associated Test Level Board Value test sp-link 18 (a) busyout sp-link WARNING release sp-link 257(b) 1, 3 4, 5, 6...
Page 365 Link Tear Down Test (#213) This test is destructive. The Link Tear Down test disconnects the existing link between S8700 IP Connect and the external SYS-PRNT output device. If the link has been disconnected already, this test just returns PASS. Every resource allocated for a System Printer Link is released after this test.
Page 366 Maintenance Object Repair Procedure Link Retry Test (#215) This test sends a message to the System Printer management software process instructing it to make a data call to the extension connected to the printer. If the System Printer link is already up, this test passes without making any data call. Table 8-455.
Page 367: Troubleshooting A Duplicated Server
SYSTEM (System) SYSTEM (System) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO SYSTEM None None System SYSTEM has no associated alarms and thus appears only in the Error Log. There are no tests that run on SYSTEM.
Page 368 Maintenance Object Repair Procedure Notes: a. Software requested a System Restart Level 3. b. Software requested a System Restart Level 2. c. Software requested a System Restart Level 1. d. An error occurred during initialization. e. Translation data was corrupted, so the system requested a Restart Level 3 to reload translation data from the Mass Storage System (MSS).
Page 369 SYSTEM (System) n. For error types 6002, 6003, 6102, and 6103, the aux-data value points to the MO that the error or alarm is logged against. The following table lists possible aux-data values and their associated MOs. Locate the Error Log entry for the indicated MO and follow the instructions for that error.
Page 370 Maintenance Object Repair Procedure Table 8-457. SYSTEM Error 605 AUX Data, Failure of Planned Interchange Data See Note Explanation 1352 Standby SOH "non-functional" 1353 Standby SOH not "functional" server 1355 Handshake Communication with standby is down 1356 Memory Shadowing not enabled 1357 Standby memory not refreshed 1358...
Page 371 SYSTEM (System) Notes for SYSTEM Error 605 AUX Data: 1. Follow repair instructions in “STBY-SPE” for the particular standby server problem. After fixing that problem, try the interchange again. 2. Mass Storage System is in use. Check Disk and Removable Media LEDs for activity.
Page 372: Tbri-Bd (Tn)
Put cross-ref to {ChapterTitle} here TBRI-BD (TN2185 ISDN Trunk-Side BRI) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO TBRI-BD MINOR test board UUCSS l r# TBRI-BD Where UU is the universal cabinet number (1–64), C is the carrier designation (A, B, C, or D), SS is the carrier slot address where the circuit pack resides (01–10), and pp is the 2-digit port number (1, 2, 3, and so forth).
Page 373 TBRI-BD (TN2185 ISDN Trunk-Side BRI) 4-Wire 4-Wire Terminal Adapter 2-Wire 4-Wire 2-Wire 4-Wire 2-Wire 2-Wire ISDN Interface Reference Points cydfisdn RPY 072397 Figure 8-47. Integrated Trunk-Side BRI, ISDN Interface Reference Points ISDN Interface Reference Point definitions: Logical Terminal Primary Rate user/network (asymmetrical) trunk interface. The ECS is capable of acting as the user or as the network side of this 1.544- or 2.048-Mbps interface.
Page 374 Maintenance Object Repair Procedure Basic Rate network-side 2-wire line interface. TN556B ISDN-BRI 4-Wire S/T-NT Line (A-law) TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) TN2198 ISDN-BRI 2-Wire U Interface TN2198 ISDN-BRI 2-Wire U Interface TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) Network Termination 2 (NT2), that terminates Layer 1 and higher layers.
Page 375 TBRI-BD (TN2185 ISDN Trunk-Side BRI) Table 8-458. TBRI-BD Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 3330 (j) 46083 MINOR 3586 (k) MINOR 3840 (l) 4096 4101 3842 (m) 46095 3843 (n) 46097 Continued on next page...
Page 376 Maintenance Object Repair Procedure d. The circuit pack detects a program logic error. While no action is required, this error can lead to other errors against this circuit pack. e. The circuit pack cannot update and read back NPE/NCE memory. This error can be ignored, but may lead to other errors against this circuit pack.
Page 377 TBRI-BD (TN2185 ISDN Trunk-Side BRI) j. Error Type (2305, 3330): A critical failure in the Circuit Pack’s Packet bus interface. Possible causes include either a Packet bus fault or an on-board fault, for example, the board received a bad CRC or invalid DLCI. If the Packet bus is alarmed, see ‘‘Isolating and Repairing Packet-Bus Faults’’...
Page 378 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes When inspecting errors in the system, always investigate tests in the order listed below. For example, by clearing error codes associated with the Control Channel Loop-around test (#52), you may also clear errors generated from other tests in the testing sequence.
Page 379 TBRI-BD (TN2185 ISDN Trunk-Side BRI) Table 8-459. Test #595 LAN Receive Parity Error Counter Test Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received from the circuit pack within the allowable time period. 1.
Page 380: Tbri-Pt (Isdn Trunk-Side Bri Port)
(01–10), and pp is the 2-digit port number (1, 2, 3, and so forth). This document describes the port maintenance features of the S8700 IP Connect TN2185 Trunk-Side ISDN-BRI board. The circuit pack provides 8 S/T ISDN 2B+D ports that interface to either the central office or another PBX.
Page 381 TBRI-PT (ISDN Trunk-Side BRI Port) 4-Wire 4-Wire Terminal Adapter 2-Wire 4-Wire 2-Wire 4-Wire 2-Wire 2-Wire ISDN Interface Reference Points cydfisdn RPY 072397 Figure 8-48. Integrated Trunk-Side BRI, ISDN Interface Reference points ISDN Interface Reference Point definitions: Logical Terminal Primary Rate user/network (asymmetrical) trunk interface. The ECS is capable of acting as the user or as the network side of this 1.544- or 2.048-Mbps interface.
Page 382 Maintenance Object Repair Procedure Basic Rate network-side 2-wire line interface. TN556B ISDN-BRI 4-Wire S/T-NT Line (A-law) TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) TN2198 ISDN-BRI 2-Wire U Interface TN2198 ISDN-BRI 2-Wire U Interface TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) Network Termination 2 (NT2), that terminates Layer 1 and higher layers.
Page 383 TBRI-PT (ISDN Trunk-Side BRI Port) Table 8-460. TBRI-PT Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 3073 (m) Slip Query test MINOR (#1244) 3585 (n) Receive FIFO Log Only Overflow (TDM D-channel) 3586 (o) 3587 (p)
Page 384 Maintenance Object Repair Procedure e. Error Type (769) — The port is generating too many uplinks. The link is being suspended. f. Error Type (1025) — An expired timer has created an unexpected event. The timer could be any of the following: Timer Event T3031...
Page 385 TBRI-PT (ISDN Trunk-Side BRI Port) l. Error Type (2305) — The Remote Layer 3 Query failed. The test is repeated every 15 minutes until it passes. m. Error Type (3073) — A frame of information had to be repeated or deleted. Slips usually occur when the received bit rate is not synchronized with the TDM bus clock.
Page 386 Maintenance Object Repair Procedure Table 8-461. Cause Values for Error 3841–3942 Value Type of Problem Meaning admin No route to specific transit network admin No route to destination (or Germany bcap not imp) admin Channel unacceptable switch problems No user responding switch problems Network failure subscription...
Page 387 TBRI-PT (ISDN Trunk-Side BRI Port) System Technician-Demanded Tests: Descriptions and Error Codes When inspecting errors in the system, always investigate tests in the order listed below. For example, by clearing error codes associated with the BRI Local LAN Port Loop Around test (#618), you may also clear errors generated from other tests in the testing sequence.
Page 388 This test is not valid for this type of translation. Ports administered as “ASAI” or “ADJK” cannot run this test, because the B channels associated with the port are not used by ASAI or Avaya Adjunct Links. This is a normal condition. 2012...
Page 389 TBRI-PT (ISDN Trunk-Side BRI Port) Table 8-463. Test #617 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation PASS The port is correctly using its allocated time slots. 1. To be sure that this is not an intermittent problem, repeat this test up to 10 times to ensure it continues to pass.
Page 390 Maintenance Object Repair Procedure Table 8-464. Test #618 BRI Port Local LAN Loop Around Error Test Code Result Description / Recommendation 1015 ABORT The port is not out-of-service. 1. Use the status bri-port UUCSSpp command to determine the status of the port.
Page 391 TBRI-PT (ISDN Trunk-Side BRI Port) BRI Port Local TDM Loop-Around Test (#619) This test is conditionally destructive. This test verifies the connectivity of a BRI port across the TDM bus. It aborts if calls associated with the port are in progress. Failure of this test indicates an on-board fault associated with the port hardware on the circuit pack.
Page 392 This test is not valid for this type of translation. Ports administered as ASAI or ADJK cannot run this test because the B channels associated with the port are not used by ASAI or Avaya Adjunct Links. This is a normal condition. 2000...
Page 393 TBRI-PT (ISDN Trunk-Side BRI Port) CRC Error Counter Test (#623) This test is nondestructive. This test reads the BRI port’s CRC error counters that are maintained on the BRI circuit pack. The Cyclic Redundancy Check (CRC) is a means of error detection used to determine the integrity of data frame contents.
Page 394 Maintenance Object Repair Procedure Table 8-467. Test #625 Receive FIFO Overflow Error Counter Test Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received from the circuit pack within the allowable time period. 1. If the test aborts repeatedly up to 5 times, reset the circuit pack with the busyout board UUCSS and reset board UUCSS commands.
Page 395 TBRI-PT (ISDN Trunk-Side BRI Port) The Deactivated state indicates a problem with the TBRI-BD circuit pack. When in this state, the Level 1 interface is not active, and an idle signal is transmitted to the channels or that Layer 1 was deactivated by the switch. When an TBRI-PT port is placed in the out-of-service state, Level 1 is also put into the Deactivated state.
Page 396 Maintenance Object Repair Procedure Table 8-468. Test #1242 Level 1 Status Inquiry — Continued Error Test Code Result Description / Recommendation FAIL Received a status of Level 1 Pending Activation. U interface down indicating a problem with a connection between the switch and the NT1, a 2- to 4-wire converter that is used to connect 4-wire terminals to a 2-wire TN2198 or TN2185 circuit pack.
Page 397 TBRI-PT (ISDN Trunk-Side BRI Port) Table 8-468. Test #1242 Level 1 Status Inquiry — Continued Error Test Code Result Description / Recommendation FAIL Received a status of Level 1 Pending Activation, the NT1 has a loss of power indicating a problem with the NT1. 1.
Page 398 Maintenance Object Repair Procedure Table 8-469. Test #1243 Layer 3 Query — Continued Error Test Code Result Description / Recommendation 1139 ABORT The Packet bus in the port network is out-of-service. 1. Follow the repair procedures for the Packet bus. 2.
Page 399 TBRI-PT (ISDN Trunk-Side BRI Port) Slip Query Test (#1244) This test is nondestructive. Slips occur when the transmitter and receiver are not running at precisely the same clock rate. The Slip Alarm Inquiry test polls the total number of slips that have occurred on a link.
Page 400 Maintenance Object Repair Procedure Table 8-470. Test #1244 Slip Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation PASS No Slip alarm is detected on the DS1 Interface circuit pack. The DS1 Interface circuit pack is not administered. BOARD 1.
Page 401: Tbri-Trk (Trunk-Side Isdn Bri)
TBRI-TRK (Trunk-Side ISDN BRI) TBRI-TRK (Trunk-Side ISDN BRI) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO TBRI-TRK MAJOR test trunk UUCSSpp l MO_TBRI_TRK TBRI-TRK MINOR test trunk UUCSSpp l MO_TBRI_TRK TBRI-TRK WARNING test trunk UUCSSpp sh MO_TBRI_TRK Where UU is the universal cabinet number (1–64), C is the carrier designation (A, B, C, or D), SS is the carrier slot address where the circuit pack resides (01–10), and pp is the 2-digit port number (1, 2, 3, and so forth).
Page 402 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the Service State Audit test (#256), you may also clear errors generated from other tests in the testing sequence.
Page 403 TBRI-TRK (Trunk-Side ISDN BRI) Table 8-471. Test #1251 Signaling Link State Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 1018 ABORT The test is disabled.
Page 404 Maintenance Object Repair Procedure Table 8-472. Test #256 Service State Audit Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be on a valid call. Use status trunk to determine when trunk is available for testing.
Page 405 TBRI-TRK (Trunk-Side ISDN BRI) Call State Audit Test (#257) This test is nondestructive. This test performs a call state audit on an ISDN B channel, and upon successful completion, guarantees that both sides of the interface are in a consistent call state for connections using the B channel.
Page 406 Maintenance Object Repair Procedure ISDN Test Call Test (#258) This test performs a far-end loop around to a far-end switch over an ISDN trunk. The trunk’s service state must be in-service, maint-NE, or out-of-service/NE, and no call can be active on the trunk. A test call connection is established to a far-end switch over the ISDN trunk to be tested.
Page 407 TBRI-TRK (Trunk-Side ISDN BRI) If no Maintenance/Test circuit pack exists, an outgoing test call over a trunk-side ISDN-BRI facility is established over a high-speed data channel on the Network Control (NETCON) circuit pack (DATA-BD). Asynchronous Commands NOTE: Only one trunk can be tested in a given port network, until the test call is canceled or completes.
Page 408 Maintenance Object Repair Procedure Table 8-474. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 1117 ABORT ISDN B-channel maintenance message is already outstanding. 1. Wait two minutes, then try again. 1118 ABORT Far end of ISDN trunk is not administered. 1.
Page 409 TBRI-TRK (Trunk-Side ISDN BRI) Table 8-474. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 2041 ABORT The call has timed out, perhaps because of a lack of system resources. 1. Retry the command at 1-minute intervals up to 5 times. 2.
Page 410 Maintenance Object Repair Procedure Table 8-474. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 2208 ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 2209, ABORT Could not allocate the necessary system resources to run this test.
Page 411 TBRI-TRK (Trunk-Side ISDN BRI) Table 8-474. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 2042 FAIL This is the main purpose of the test. The comparison of the data sent with the data received indicates a loss of integrity on the communications path. 1.
Page 412: Tdm-Bus (Tdm Bus)
Maintenance Object Repair Procedure TDM-BUS (TDM Bus) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO TDM-BUS MAJOR test tdm P TDM bus TDM-BUS MINOR test tdm P TDM bus TDM-BUS WARNING test tdm P TDM bus P is the port network’s number.
Page 413 TDM-BUS (TDM Bus) TDM-Bus Fault Detection and Isolation TDM-bus faults are usually caused by one of the following: A defective circuit pack connected to the backplane Bent pins on the backplane Defective bus cables or terminators It is possible that a circuit pack can cause a TDM-bus fault and still exhibit trouble-free operation.
Page 414 Maintenance Object Repair Procedure Procedure 1: Isolating TDM-Bus Faults This procedure is an attempt to isolate the TDM-bus fault to circuit packs that are essential to the system’s operation. For each of the following circuit packs in the port network where the TDM-bus fault appears, perform Procedure 1. Circuit Pack Error Log Names Tone-Clock...
Page 415 TDM-BUS (TDM Bus) In Procedure 2, an option of working either with one circuit pack at a time or with multiple circuit packs simultaneously is available. In view of this capability, determine the level of service interruption that will be acceptable during the procedure.
Page 416 Maintenance Object Repair Procedure Procedure 3: Removing and Reinserting EPN Control Circuit Packs This procedure removes and reinserts an EPN’s control circuit packs, as listed in the table at the beginning of this section. The following circuit packs should be tested with this procedure: The Tone-Clock circuit pack should be the next-to-last one checked.
Page 417 TDM-BUS (TDM Bus) 5. If the TDM-bus fault is still present, the suspected circuit pack was not the cause of the TDM-bus failure. Do the following: a. Remove the replacement circuit pack that was just inserted and replace it with the previously suspected circuit pack. b.
Page 418 Maintenance Object Repair Procedure TDM/LAN Bus Terminator TDM/LAN Bus Cable ....Carrier C Carrier B ....
Page 419 TDM-BUS (TDM Bus) Part 1 1. If spare TDM/LAN cable assemblies and TDM/LAN bus terminators are not available, go to Part 2 of this procedure. 2. Power down the EPN. 3. Replace every TDM/LAN cable assembly and both TDM/LAN bus terminators.
Page 420 Maintenance Object Repair Procedure Restarting Non-Functioning Port Circuit Packs A defective TDM-bus control channel or system-timing reference on one of the EPNs can cause port circuit packs residing outside the EPN’s control carrier to enter the reset state. When this situation occurs, the circuit pack will stop functioning, and its red LED will light.
Page 421 TDM-BUS (TDM Bus) Error Log Entries and Test to Clear Values Table 8-475. TDM Bus Error Log Entries Error On/Off Test to Clear Type Data Associated Test Alarm Level Board Value test tdm P Control Channel test (#296) MINOR test tdm P r 3 18(a) busyout tdm PC WARNING...
Page 422 Maintenance Object Repair Procedure If this error is logged on both TDM buses (A and B) on the PPN within two or three minutes, the red LED of several circuit packs may or may not be lit and there could be Switch Control (SW-CTL) errors. Under these circumstances do the following: Display the Hardware Error Log via the display errors command and look for SW-CTL (Switch Control) errors.
Page 423 TDM-BUS (TDM Bus) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the Control Channel test (#296), you may also clear errors generated from other tests in the testing sequence. Short Test Long Test Order of Investigation...
Page 424 Maintenance Object Repair Procedure Table 8-476. Test #294 Idle Time Slot Test on TDM bus A or TDM bus B Error Test Code Result Description / Recommendation None ABORT Could not allocate the necessary system resources to run this test. For example, maintenance could be running on the Tone Detector circuit pack and it is using the CPTRs.
Page 425: Control Channel Test
TDM-BUS (TDM Bus) Control Channel Test (#296) This tests the integrity of the Control Channel bus by ensuring that communication through the TDM bus is operational. The test attempts to query a circuit pack whose presence is required in each port network for proper operation (Tone-Clock or Tone Detector).
Page 426: Digit Detection Test
Maintenance Object Repair Procedure Digit Detection Test (#297) This test is executed on the Non-Control Channel bus. The Tone-Clock circuit pack is told to put a tone on the Non-Control Channel bus and the Tone Detector circuit pack is told to listen to it. The test passes if the tone is successfully transmitted on the Non-Control Channel bus.
Page 427: Tdm-Clk (Tdm Bus Clock)
TDM-CLK (TDM Bus Clock) TDM-CLK (TDM Bus Clock) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO TDM-CLK MAJOR test tone-clock UUC short TDM bus Clock TDM-CLK MINOR test tone-clock UUC short TDM bus Clock TDM-CLK WARNING release tone-clock UUC...
Page 428 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-479. TDM Bus Clock Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test tone-clock UUC sh r 1 1 (a) None MINOR 130 (b)
Page 429 TDM-CLK (TDM Bus Clock) d. The IPSI’s Tone-Clock circuit may be defective, however it may be a software failure that can be corrected by testing. 1. Check to see if the board is duplicated (list cabinet and status port-network) on the affected port network. 2.
Page 430 Maintenance Object Repair Procedure 2. Otherwise, enter the display errors command, and follow corrective procedures for any other TDM-CLK, TONE-BD, SYNC, and DS1C-BD, errors logged, except for those in Table 8-480. Table 8-480. Error Log Entries for Slip Errors Error Log Error Log Entry Circuit Pack Name Name...
Page 431 TDM-CLK (TDM Bus Clock) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the SAKI Reset test (#53), you may also clear errors generated from other tests in the testing sequence.
Page 432: Tdm Bus Clock Circuit Status Inquiry Test
Maintenance Object Repair Procedure TDM bus Clock Circuit Status Inquiry Test (#148) The TDM bus Clock circuitry is checked for sanity. Any problems that are found are reported via error codes Table 8-481. Test #148 TDM bus Clock Circuit Status Inquiry Test Error Test Code...
Page 433 TDM-CLK (TDM Bus Clock) Table 8-481. Test #148 TDM bus Clock Circuit Status Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The tone-clock is currently not able to lock on to the current synchronization reference. If this tone-clock is in the master port networK: 1.
Page 434: Tdm Bus Clock Slip Inquiry Test
Maintenance Object Repair Procedure TDM Bus Clock Slip Inquiry Test (#149) This test evaluates the quality of the synchronization source for the IPSI circuit pack’s Tone-Clock circuit. NOTE: This test does not apply to the TN2182. Table 8-482. Test #149 TDM bus Clock Slip Inquiry Test Error Test Code...
Page 435: Tdm Bus Clock Ppm Inquiry Test
TDM-CLK (TDM Bus Clock) TDM bus Clock PPM Inquiry Test (#150) This test evaluates the quality of the synchronization source for the Tone-Clock circuit pack. Table 8-483. Test #150 TDM bus Clock PPM Inquiry Test Error Test Code Result Description / Recommendation ABORT The system could not allocate the necessary resources for the test.
Page 436: Tdm Bus Clock Parameter Update Test
Maintenance Object Repair Procedure TDM Bus Clock Parameter Update Test (#151) This test updates the following internal parameters on the IPSI circuit pack: Disable in-line duplication status messages. Set the PPM threshold at 85 PPM for TN2312. Enable PPM threshold switching Set the number of slips to trigger loss of signal - currently 30 per 5-millisecond period Enable the on-board synchronization switching algorithm (see above)
Page 437 TDMODULE (Trunk Data Module) TDMODULE (Trunk Data Module) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO TDMODULE MINOR test port UUCSSpp | Trunk Data Module TDMODULE WARNING test port UUCSSpp | Trunk Data Module UU is the universal cabinet number (1–64).
Page 438: Tie-Bd (Tie Trunk Circuit Pack)
Maintenance Object Repair Procedure TIE-BD (Tie Trunk Circuit Pack) MO’s Name (in Alarm Alarm Log) Level Initial Command To Run Full Name of MO TIE-BD MINOR test board UUCSS sh Tie Trunk Circuit Pack TIE-BD WARNNG test board UUCSS sh Tie Trunk Circuit Pack UU is the universal cabinet number (1–64).
Page 439: Tie-Ds1 (Ds1 Tie Trunk)
TIE-DS1 (DS1 Tie Trunk) TIE-DS1 (DS1 Tie Trunk) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO TIE-DS1 MAJOR test trunk grp/mbr l DS1 Tie Trunk TIE-DS1 MINOR test trunk grp/mbr l DS1 Tie Trunk TIE-DS1 WARNING test trunk grp/mbr...
Page 440 Maintenance Object Repair Procedure The DS1 tie trunk maintenance strategy covers logging DS1 tie trunk hardware errors, running tests for trunk initialization, periodic and scheduled maintenance, system technician-demanded tests, and alarm escalation and resolution. Three different trunk service states are specified in DS1 tie trunk maintenance: Out-of-service The trunk is deactivated and cannot be used for incoming or outgoing calls.
Page 441 TIE-DS1 (DS1 Tie Trunk) Table 8-485. DS1 Tie Trunk Maintenance Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1281 Conference Circuit test MINOR test trunk grp/mbr l r 4 (#7) WARNING 1537 NPE Crosstalk test (#6)
Page 442 Maintenance Object Repair Procedure If every administration parameter between the switch and the far end match and these errors continue to recur, follow normal escalation procedures. b. Error Type 15 — This is a software audit error that does not indicate any hardware malfunction.
Page 443 TIE-DS1 (DS1 Tie Trunk) k. Error Type 2562 — Retry Failure error. This error is logged only. It is not a hardware failure and hence does not start any testing or generate any alarms. This error comes from call processing and is generated when a second attempt (retry) to seize an outgoing trunk fails.
Page 444 Maintenance Object Repair Procedure NPE Crosstalk Test (#6) The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, 1-way and noisy connections may be observed. This test is usually only part of a port’s long test sequence and takes on the order of 20 to 30 seconds to complete.
Page 445 TIE-DS1 (DS1 Tie Trunk) Table 8-486. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a user for a valid call. 1. Use the display port UUCSSpp command to determine the trunk group/member number of the port.
Page 446 Maintenance Object Repair Procedure Table 8-486. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation PASS The port is correctly using its allocated time slots. User-reported troubles on this port should be investigated using other port tests and by examining station, trunk, or external wiring.
Page 447 TIE-DS1 (DS1 Tie Trunk) Conference Circuit Test (#7) One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM-bus interface. (The TN464C/D UDS1 circuit pack has one SCOTCH-NPE chip instead of several NPE chips). The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis.
Page 448: Change Station
Maintenance Object Repair Procedure Table 8-487. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a user for a valid call. 1. Use the display port UUCSSpp command to determine the trunk group/member number of the port.
Page 449 TIE-DS1 (DS1 Tie Trunk) Table 8-487. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1.
Page 450 Maintenance Object Repair Procedure Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface circuit pack to ensure that the trunk’s translation is correct. Translation updates include the following data: trunk type (in/out), dial type, timing parameters, and signaling bits enabled.
Page 451 TIE-DS1 (DS1 Tie Trunk) Table 8-488. Test #36 Audit and Update Test — Continued Error Test Code Result Description / Recommendation PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack and switch software are consistent. If the trunk is busied out, the test does not run but returns a PASS.
Page 452 Maintenance Object Repair Procedure This second part of this test cannot be run on a trunk if one of the following cases is true: 1. The trunk direction is administered as an incoming only trunk. 2. The trunk is the 24 port on a DS1 Interface circuit pack which is administered using 24 common-channel signaling.
Page 453 TIE-DS1 (DS1 Tie Trunk) Table 8-489. Test #136 DS1 Tie Trunk Seizure Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABORT System resources required to run this test were not available. The port may be busy with a valid call.
Page 454 Maintenance Object Repair Procedure Table 8-489. Test #136 DS1 Tie Trunk Seizure Test — Continued Error Test Code Result Description / Recommendation 1020 ABORT The test did not run due to an already existing error on the specific port or due to a more general circuit pack error.
Page 455 TIE-DS1 (DS1 Tie Trunk) Table 8-489. Test #136 DS1 Tie Trunk Seizure Test — Continued Error Test Code Result Description / Recommendation 2000 FAIL Response to the seizure message was not received within the allowable time period. 1. Enter the list configuration board UUCSS command. If the circuit pack is a TN767B vintage 8 or 9, a failure of test 136 causes a subsequent failure of test 7 due to a firmware bug.
Page 456: Tie-Trk (Analog Tie Trunk)
Maintenance Object Repair Procedure TIE-TRK (Analog Tie Trunk) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO TIE-TRK MAJOR test port UUCSSpp l Tie Trunk TIE-TRK MINOR test port UUCSSpp l Tie Trunk TIE-TRK WARNING test port UUCSSpp sh Tie Trunk...
Page 457 TIE-TRK (Analog Tie Trunk) A tie trunk port can also be administered as an access endpoint which is a non-signaling channel with a voice-grade data bandwidth. Tie trunk maintenance employs up to 6 tests, depending on the hardware involved, to monitor the operating condition of the trunk and its connections.
Page 458 Maintenance Object Repair Procedure Table 8-491. TIE Trunk Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 769(l) 57481 EPF M and E Lead MAJOR test port UUCSSpp sh r 3 (#74) MINOR WARNING...
Page 459 TIE-TRK (Analog Tie Trunk) Notes: a. Digit time-out. This occurs when the far-end PBX began transmitting digits too late (10 seconds) after receiving the signal indicating ready to receive digits (if any). This can occur on an incoming immediate, wink, or delay dial line.
Page 460 Maintenance Object Repair Procedure n. Reorder message. The trunk could not be seized. This error causes the Tie Trunk Seizure test (#73) to run and is considered a problem only if that test fails, logging error 1793. In this case, the trunk may be placed in the ready-for-service state, allowing only incoming calls.
Page 461 TIE-TRK (Analog Tie Trunk) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in Table 8-492 when inspecting errors in the system. For example, by clearing error codes associated with the NPE Crosstalk test (#6), you may also clear errors generated from other tests in the testing sequence.
Page 462 Maintenance Object Repair Procedure NPE Crosstalk Test (#6) The NPE Crosstalk test verifies that a port’s NPE channel talks on the time slot assigned to it and does not cross over to time slots reserved for other connections. If the NPE is not working correctly, 1-way and noisy connections may be observed.
Page 463 TIE-TRK (Analog Tie Trunk) Table 8-493. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate the necessary system resources to run this test. This could be due to a failure to seize the port.
Page 464 Maintenance Object Repair Procedure Table 8-494. Test #33 Looparound and Conference Circuit Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. This could be due to a failure to seize the port. 1.
Page 465 TIE-TRK (Analog Tie Trunk) Table 8-494. Test #33 Looparound and Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. Use the display trunk xx command to determine the trunk group/member number of the port.
Page 466 Maintenance Object Repair Procedure Table 8-494. Test #33 Looparound and Conference Circuit Test — Continued Error Test Code Result Description / Recommendation FAIL NOTE: 129, (cont’d) If the loop-around and conference circuit test fails for every port on a 131, or circuit pack, a -5 Volt power problem is indicated.
Page 467 TIE-TRK (Analog Tie Trunk) Table 8-495. Test #36 Audit Update Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABORT Could not allocate the necessary system resources to run the test.
Page 468 Maintenance Object Repair Procedure For TN439, Test #747 is run instead of #73. This test seizes a trunk and outpulses a pause digit. This test aborts on ports administered as access endpoints. Table 8-496. Test #73,#747 Tie Trunk Seizure Test Error Test Code...
Page 469 TIE-TRK (Analog Tie Trunk) Table 8-496. Test #73,#747 Tie Trunk Seizure Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT Could not allocate the necessary system resources to run the test. This could be due to a failure to seize the port. 1.
Page 470 Maintenance Object Repair Procedure Tie Trunk EPF Test (#74) The first part of this test checks for proper activation and deactivation of the port’s E lead. The second part checks the M lead electronic power feed current flow. Table 8-497. Test #74 Tie Trunk EPF Test Error Test Code...
Page 471 TIE-TRK (Analog Tie Trunk) Table 8-497. Test #74 Tie Trunk EPF Test — Continued Error Test Code Result Description / Recommendation 1040 ABORT This test is not performed for trunk ports administered as access endpoints. 1. Verify this port is an access endpoint by using the display port command. 2.
Page 472 Maintenance Object Repair Procedure Transmission Test (#844-848) This test is nondestructive. NOTE: Tests #844–848 are not supported on an International switch. These tests are run by the Automatic Transmission Measurement System (ATMS). They are not part of the long or short trunk test sequences. Instead, they are run on demand with the test analog-testcall command or as part of ATMS scheduled testing.
Page 473 TIE-TRK (Analog Tie Trunk) Table 8-498. Test #844-848 Transmission Test — Continued Error Test Code Result Description / Recommendation 1005 ABORT Trunk has been administered as incoming-only; transmission tests can only be run on outgoing trunks. 1115 ABORT The near end test line on the TN771 circuit pack could not be allocated. 1.
Page 474 Maintenance Object Repair Procedure Table 8-498. Test #844-848 Transmission Test — Continued Error Test Code Result Description / Recommendation 1920 ABORT No response from far end. 1. The problem is with the far-end system; a technician at the far end should test the test line (TN771 or ADFTC).
Page 475 TIE-TRK (Analog Tie Trunk) Table 8-498. Test #844-848 Transmission Test — Continued Error Test Code Result Description / Recommendation 1947 ABORT Noise with tone self check failed. 1. Test the TN771 circuit packs. 2000 ABORT The test timed out while waiting for a response from the TN771 circuit pack. 1.
Page 476: Time-Day (Time Of Day)
Maintenance Object Repair Procedure TIME-DAY (Time of Day) MO’s Name (in Alarm Initial Command To Alarm Log) Level Full Name of MO TIME-DAY MINOR set time Time of Day The time of day contains the current year, month, day of the week, day of the month, hour, minute, and second.
Page 477: Tone-Bd (Tone-Clock Circuit Pack)
Tone-Clock circuit pack UU is the universal cabinet number (1–64). C is the carrier designation (A, B, C, or D). The TONE-BD MO supports EPNs in an S8700 Media Server system using a TN2312 IP Server Interface (IPSI) circuit pack...
Page 478 Figure 8-50 S8700 Media Server 1 - two are always present, one in a active mode and the other on standby. S8700 Media Server 2 - two are always present, one in a active mode and the other on standby.
Page 479: Change System-Parameters Maintenance
10/100 mbps. Port Network - optional configuration of Media Gateways that provides increased switch capacity. IPSI - provides transport of CCMS messages over IP allowing the S8700 Media Server to communicate with the Port Networks. Customer LAN Tone-Clock Interchange Strategy...
Page 480 After detecting a loss of clock/clock errors, and rather than waiting for S8700 IP Connect software to request a switch, the IPSI firmware will automatically switch the clock (when auto clock switching is enabled). The auto clock switching option is disabled during system restarts.
Page 481 EPN enters emergency transfer within one minute, and no calls can be set up from or to that EPN. When replacing a Tone-Clock circuit in an S8700 IP Connect system, always be sure to replace it with the appropriate Tone-Clock circuit for the system. One...
Page 482 Maintenance Object Repair Procedure Port Networks with a Single Tone-Clock Circuit Pack This procedure is destructive. 1. Pull out the defective IPSI circuit pack. This will remove the clocks and cause the system to activate emergency measures. Use the busyout ipserver-interface command: All calls to and from the EPN will drop, and the EPN will activate Emergency Transfer within about one minute.
Page 483 TONE-BD (Tone-Clock Circuit Pack) Table 8-500. LED Condition/Tone-Clock Circuit States Tone-Clock Condition Circuit State Explanation flashing yellow active An external timing source is being used as a 2.7 seconds on synchronization reference 0.3 seconds off flashing yellow active The local oscillator on the IPSI circuit pack is being used 0.3 seconds on as a synchronization reference.
Page 484 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-501. Tone-Clock Circuit Pack Error Log Entries Error On/Off Type Aux Data Associated Test Alarm Level Board Test to Clear Value test tone-clock PC sh 1 (a) Circuit pack removed or MINOR SAKI Sanity test (#53)
Page 485 TONE-BD (Tone-Clock Circuit Pack) Notes: a. Error Type 1 This error indicates the circuit pack totally stopped functioning or it was physically removed from the system. NOTE: The alarm is logged approximately 11 minutes after the circuit pack is removed/SAKI Sanity test (#53) fails. If the circuit pack is not present in the system, insert a circuit pack in the slot indicated by the error to resolve the error.
Page 486 Maintenance Object Repair Procedure g. Error Type 76 — This error can be ignored, but look for other errors on this circuit pack. h. Error Type 1025 — This error is not service-affecting and no action is required. i. Error Type 1538 — The circuit pack was taken out of service because of an excessive rate of uplink messages.
Page 487 TONE-BD (Tone-Clock Circuit Pack) k. Error Type 2561 This error indicates that a Tone-Clock circuit, with a different circuit-pack code as required for this system, has been inserted in the port slot as shown in the Hardware Error Log. To resolve this error, see ‘‘Replacing the IPSI Circuit Pack’’...
Page 488: Clear Errors
Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. By clearing error codes associated with the SAKI Reset test for example, you may also clear errors generated from other tests in the testing sequence.
Page 489 TONE-BD (Tone-Clock Circuit Pack) Clock Health Inquiry Test (#46) This inquiry reads special data stored in memory to determine if this IPSI circuit pack had a loss of any of three clock types: SYSCLK SYSFM SYSDCLK If this data indicates this IPSI circuit pack had a loss of any of these clocks, the inquiry reports FAIL.
Page 490 Maintenance Object Repair Procedure Table 8-504. Test #46 Clock Health Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error. Retry the command at 11-minute intervals up to 5 times. none FAIL This IPSI circuit pack had an apparent loss of clock. One or more of error types 2049, 2305, 3834, 3857, 3858, and 3872 will appear in the error log.
Page 491: Tone-Pt (Tone Generator)
TONE-PT (Tone Generator) TONE-PT (Tone Generator) MO’s Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO TONE-PT MAJOR test tone-clock UUC short Tone Generator TONE-PT MINOR test tone-clock UUC short Tone Generator TONE-PT WARNING release tone-clock UUC Tone Generator UU is the universal cabinet number (1 for PPN, 2 -64 for EPNs).
Page 492 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-505. Tone Generator Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test tone-clock UUC r 1 1 (a) 17664 Tone Generator Audit/ MAJOR test tone-clock UUC r 2...
Page 493 TONE-PT (Tone Generator) f. The system-parameters country-options administration requires a TN2312 IPSI circuit pack, but the existing Tone-Clock circuit does not provide the needed functionality. The Base Tone Generation Set on page 1 or the custom tones beginning on page 2 of the system-parameters country options form may have values not supported by the existing Tone-Clock.
Page 494 Maintenance Object Repair Procedure Short Test Long Test Reset Board Order of Investigation Sequence Sequence Sequence D/ND Tone Generator Audit/Update test (#41) TDM bus Clock Circuit Status Inquiry test (#148) (c) TDM Bus Clock Slip Inquiry test (#149) (c)(e) TDM bus Clock PPM Inquiry test (#150) (c) TDM bus Clock Parameter Update test (#151) (c)
Page 495 TONE-PT (Tone Generator) The tone generator is then told to generate a sequence of test tones whose output levels are measured by a tone detector. These tones are: 404 Hz at 0 dB 1004 Hz at -16 dB 1004 Hz at 0 dB 2804 Hz at 0 dB A Tone Detector’s general-purpose tone detector listens for tones and measures their quality.
Page 496 Maintenance Object Repair Procedure Table 8-506. Test #40 Tone Generator Transmission Test Error Test Code Result Description / Recommendation None ABORT The system was not able to allocate all the resources needed for this test or there was an Internal system error. ABORT The system could not allocate all the resources needed to test the DTMF tones.
Page 497 TONE-PT (Tone Generator) Table 8-506. Test #40 Tone Generator Transmission Test — Continued Error Test Code Result Description / Recommendation 111 (b) FAIL Generation of 1004-Hz low level invalid. 112 (b) FAIL Generation of 1004-Hz high level invalid. 113 (b) FAIL Generation of 2804-Hz level invalid.
Page 498 Maintenance Object Repair Procedure c. Error code 115 may also be caused by TDM bus corruption. This normally means a physical problem with bent backplane pins, TDM/LAN bus cabling, or TDM/LAN bus terminators. Such physical problems should especially be suspected if board replacement or other physical activity has occurred just before this error is observed.
Page 499 TONE-PT (Tone Generator) Tone Generator Crosstalk Test (#90) This test checks the ability of the Tone Generator to talk on a specific time slot. The tone generator is told to talk on a specific time slot. The other idle time slots are checked to make sure the Tone Generator put the tone on only the specified time slot.
Page 500: Tr-Ln-Bd (Trunk Line Board)
1-way only – either incoming or outgoing – not only at the S8700 IP Connect switch, but also at the CO switch. This is necessary to avoid collisions (i.e., “glare”) and other highly undesirable conditions.
Page 501: Tsc-Adm (Administered Temporary)
TSC-ADM (Administered Temporary Signaling Connections) TSC-ADM (Administered Temporary Signaling Connections) MO’s Name Alarm Initial Command (in Alarm Log) Level to Run Full Name of MO TSC-ADM none none Administered Temporary Signaling Connections No alarms are generated for Administered Temporary Signaling Connections (TSC-ADM, also called ADM TSCs).
Page 502 Maintenance Object Repair Procedure Since ADM TSCs are administered on a per signaling-group basis, the health of an ADM TSC also depends on the state of the D channel or D-channel pair administered per signaling group. See ‘‘ISDN-SGR (ISDN-PRI Signaling Group)’’ on page 8-664 documentation for details on ISDN-PRI NFAS and D-channel backup maintenance.
Page 503 TSC-ADM (Administered Temporary Signaling Connections) System Technician-Demanded Tests: Descriptions and Error Codes Short Test Long Test Order of Investigation Sequence Sequence D/ND TSC Heartbeat Inquiry test (#604) D = Destructive; ND = Nondestructive TSC Heartbeat Inquiry Test (#604) This test can be invoked by system technician personnel for any ADM TSC administered in the switch.
Page 504 Maintenance Object Repair Procedure Table 8-511. Test #604 TSC Heartbeat Inquiry Test — Continued Error Test Code Result Description / Recommendation 1145 ABORT There is congestion in the network. 1. Issue the status tsc-administered command at 1-minute intervals up to 5 times.
Page 505 TSC-ADM (Administered Temporary Signaling Connections) Table 8-511. Test #604 TSC Heartbeat Inquiry Test — Continued Error Test Code Result Description / Recommendation 1148 ABORT The ADM TSC is enabled, but inactive (near end). 1. Disable and enable the ADM TSC. 2.
Page 506 Maintenance Object Repair Procedure Table 8-511. Test #604 TSC Heartbeat Inquiry Test — Continued Error Test Code Result Description / Recommendation 2012 ABORT Internal system error. 1. Reissue the test tsc-administered command at 1-minute intervals up to 5 times. FAIL The Administered TSC is not active (far end).
Page 507: Ttr-Lev (Ttr Level)
TTR-LEV (TTR Level) TTR-LEV (TTR Level) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO TTR-LEV WARNING TTR Level TTR-LEV MINOR TTR Level TTR-LEV MAJOR TTR Level See Repair Procedure for the TTR-LEV below. TN748 and TN420 Tone Detector circuit packs and TN744 Call Classifier circuit packs provide tone receivers for detecting various types of signaling tones.
Page 508 Maintenance Object Repair Procedure When a user goes off-hook to place a call, dial tone is returned to the user, indicating that a tone detector is connected and ready to receive and interpret tones. The tone detector is in use until the total number of digits needed is collected or until a time-out occurs.
Page 509: Display Alarms
TTR-LEV (TTR Level) Repair Procedure for TTR-LEV To resolve a TTR-LEV alarm: 1. Display errors and use the TTR-LEV Error Log Table to determine which type of tone receiver has fallen below its threshold. 2. Enter change system-parameters maintenance, and check the administered value.
Page 510 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-512. TTR Level Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 1 (a) None 2 (b) WARNING (See WARNING message below) 3 (c) None...
Page 511 TTR-LEV (TTR Level) e. Error code 5 does not indicate a current error condition. It indicates that the number of Call Classifier ports (CLSFY-PT) service was below the administered threshold, but is now equal to or greater than the threshold. These errors are typically generated during boot time or other transitional states when the ports are being brought into service.
Page 512: Usb1 (Modem Testing)
Maintenance Object Repair Procedure USB1 (Modem Testing) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO USB1 MAJOR testmodem USB Port Modem Testing USB1 MINOR testmodem USB Port Modem Testing USB1 WARNING testmodem USB Port Modem Testing 1.
Page 513 USB1 (Modem Testing) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following table. For example, by clearing error codes associated with the Handshake test, you may also clear errors generated by other tests in the testing sequence. Short Test Long Test Order of Investigation...
Page 514 Maintenance Object Repair Procedure Offhook Test This test is destructive. This test runs an offhook test for the modem attached to the USB port on the server. The test sends an ATH1 string to check that a line is connected to the modem.
Page 515 CSU. The 120A1 CSU module connects to the TN464F circuit pack on the I/O connector panel behind the port carrier. The CSU module, thus becomes an integrated part of the S8700 IP Connect system. Throughout the document, the term 120A1 will mean a 120A1 or later suffix CSU module.
Page 516 Maintenance Object Repair Procedure The Enhanced Integrated CSU is for use in the United States of America with 1.544-Mbps DS1 service. For further details on the 120A1 CSU module refer to DEFINITY Communications System Generic 1, Generic 2, and Generic 3 V1 and V2 - Integrated CSU Module Installation and Operation.
Page 517 UDS1-BD (UDS1 Interface Circuit Pack) cydfjap1 LJK 012899 Figure Notes: 1. S8700 IP Connect system 3. JRC (Japan Radio Corporation) external converter 2. UDS1-BD DS1-CONV circuit pack (24-trunk digital tie trunk) 4. TDM facilities Figure 8-51. Japanese TTC public network connections...
Page 518 Maintenance Object Repair Procedure cydfjap2 LJK 012999 Figure Notes: 1. S8700 IP Connect system 3. H600-513 cable assembly cable. (See ‘‘H600-513 Cable Pinout’’). 2. TN2242 2-Mbit Japan trunk circuit pack 4. TDM facilities Figure 8-52. TN2242 Japan trunk TTC private network connections To upgrade a system to the TN2242 circuit pack: 1.
Page 519 Answer Supervision Timeout Receive Answer Supervision Disconnect Supervision - In? Disconnect Supervision - Out? Incoming Dial Type tone, rotary, mf (to other Avaya systems only) Wink Timer for wink type Continued on next page 555-233-142 Issue 1 May 2002 8-1215...
Page 520: Led Interpretation
Maintenance Object Repair Procedure Table 8-518. TN2242 administration — Continued Field Value Wink Timer for delay type 4500 Trunk Group form, Page 3 (Administrable Timers) Incoming Disconnect Incoming Glare Guard 800ms or higher Incoming Dial Guard Incoming Incomplete Dial Alarm 25 or higher Incoming Partial Dial 10 or 20...
Page 521 Hardware Connections This circuit pack can be: Mated to another circuit pack of the same type when interconnecting two S8700 IP Connect systems Directly connected to the TDM network device Directly connected to another vendor PBX using ISDN-PRI signaling 555-233-142...
Page 522 Maintenance Object Repair Procedure Loopbacks There is no automatic process to signal the remote end to provide loopbacks for testing purposes. Every loop back to be tested with a single circuit pack must be a local loop back on the circuit pack. Remote loopbacks may be possible with the TDM network equipment with appropriate coordination between BCS Services Technicians and the service technicians of the TDM equipment (considered a CPE device).
Page 523 UDS1-BD (UDS1 Interface Circuit Pack) Echo cancellation is turned on or off on a per trunk-group basis using the change trunk-group command. If the TRUNK GROUP field, DS1 Echo Cancellation? is set to y, echo cancellation will be applied to every TN464GP/TN2464BP trunk member in that trunk group.
Page 524 CSU. The 120A1 CSU module connects to the UDS1 circuit pack on the I/O connector panel behind the port carrier. The CSU module thus becomes an integrated part of the S8700 IP Connect system. Throughout this MO, the term 120A1 will mean a 120A1 or later suffix CSU module.
Page 525 UDS1-BD (UDS1 Interface Circuit Pack) The UDS1-BD and 120A1 CSU module support on-demand loop-back tests that assist in the detection of faults between the UDS1-BD circuit pack and the CSU module, between the Integrated CSU and the optional Customer Premises Loop-Back Jack, or between the Integrated CSU and remote CSU.
Page 526 Maintenance Object Repair Procedure RLB = Repeater Loopback CLJ = Loop-Back Jack Loopback R-LLB = Remote Line Loopback SMRT = Smart Jack LPBK = Loopback Circuit Pack Administration and Options The DS1 configuration for each circuit pack is administered on the DS1 Circuit Pack form.
Page 527 UDS1-BD (UDS1 Interface Circuit Pack) TN464C/D 24/32 Channel Selector 75/120 Ohm Selector Bottom Backplane Connectors Faceplate Figure 8-54. TN464C/D DS1 Option Jumpers 24 CHNL 32 CHNL Insert the jumpers into the blocks so as to join the center row of pins and the row designating the desired options.
Page 528 TDM bus. The transfer of the download image from the source board to a target board is done under switch software’s control. This process is initiated using the S8700 IP Connect SAT interface.
Page 529: Alarm Levels
UDS1-BD (UDS1 Interface Circuit Pack) Error Log Entries and Test to Clear Values Table 8-520. DS1 Interface Circuit Pack Maintenance Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test board UUCSS 1(a) Circuit pack removed WARNING or SAKI test (#53)
Page 530 Maintenance Object Repair Procedure Table 8-520. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 1312(p) Repeater Loopback WARNING test ds1-loop UUCSS test (#1211) MINOR ds1/csu-loopback-tests 1313(q) CPE Loop-Back Jack WARNING...
Page 531 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-520. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 2305 Yellow Alarm Inquiry WARNING test board UUCSS test (#141) MINOR 2306 Yellow Alarm Inquiry...
Page 532 Maintenance Object Repair Procedure Notes: a. Error Type 1 — Indicates that the circuit pack has totally stopped functioning or is not fully administered. The alarm is logged about 15 minutes after the circuit pack has been removed or 11 minutes after the SAKI test (#53) fails.
Page 533 UDS1-BD (UDS1 Interface Circuit Pack) d. Error Type 125: No Aux Data — An incorrect circuit pack is inserted in the slot where the USD1 circuit pack is logically administered. To resolve this problem, do one of the following: Remove the incorrect circuit pack, and insert the logically administered circuit pack.
Page 534 Maintenance Object Repair Procedure j. Error Type 1300 — CSU module missing. CSU module: The Near-End CSU Type field on the add ds1 form has been administered as integrated but the 120A1 CSU module is not physically connected (or is improperly connected) to the UDS1 board behind the port carrier.
Page 535 UDS1-BD (UDS1 Interface Circuit Pack) o. Error Type 1311 — ELB failure. This error occurs when the Equipment Loopback (ELB) test fails for the Integrated CSU (I-CSU) module. This test is executed by the I-CSU during I-CSU power-up/reset (i.e.- UDS1 board physically inserted and 120A1 CSU module) or when the 120A1 CSU module is plugged on to an already initialized UDS1 DS1 board.
Page 536 Maintenance Object Repair Procedure s. Error Types 1400, 1401 — Echo Cancellation errors are logged when: Error 1400 - Echo canceller function failed. The Echo Canceller Function test, which is executed by firmware, failed. Error 1401 - Echo canceller memory failed. The Echo Canceller Memory test, which is executed by firmware, failed.
Page 537 UDS1-BD (UDS1 Interface Circuit Pack) w. Error Type 3330 — LAN Critical Error. A critical failure has been detected in the Packet bus interface of the circuit pack. This failure may be due to an on-board fault or a Packet bus fault. If the Packet bus is alarmed, see ‘‘PKT-BUS (Packet Bus)’’...
Page 538 Maintenance Object Repair Procedure ac. Error Type 3900 — Provides status information about a CPE Loop-Back Jack test. The value in the Aux Data field indicates the status of the loop-back test. Aux Data Test Status Currently running Failed because loop back could not be activated Failed because test pattern could not be detected Terminated ad.
Page 539 UDS1-BD (UDS1 Interface Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented in Table 8-521. For example, by clearing error codes associated with the Echo Cancellation test (#1420), you may also clear errors generated from other tests in the testing sequence. Table 8-521.
Page 540: Npe Connection Audit Test (#50)
Maintenance Object Repair Procedure NPE Connection Audit Test (#50) The system sends the circuit pack’s on-board microprocessor a message to update the network-connectivity translation for its SCOTCH-NPE chip. Table 8-522. Test #50 NPE Connection Audit Test Error Test Code Result Description / Recommendation None, ABORT...
Page 541 UDS1-BD (UDS1 Interface Circuit Pack) Control Channel Loop-Around Test (#52) This test queries the circuit pack for its code and vintage and verifies its records. Table 8-523. Test #52 Control Channel Loop-Around Test Error Test Code Result Description / Recommendation None, ABORT System resources required for this test are not available.
Page 542 Maintenance Object Repair Procedure SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack. The test is highly destructive and can only be initiated by a system technician-demanded reset board UUCSS command. Table 8-524. Test #53 SAKI Sanity Test Error Test Code...
Page 543 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-524. Test #53 SAKI Sanity Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 544 Maintenance Object Repair Procedure Internal Loop-Around Test (#135) This test is destructive. The Internal Loop-Around test is run by looping the transmitted DS1 bit stream back into the UDS1 board’s receiver. The loop occurs just before the DS1 facility interface. The test is highly destructive and can only be initiated by a technician-demanded reset board UUCSS command.
Page 545 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-525. Test #135 Internal Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1015 ABORT Ports on the UDS1 Interface circuit pack have not been busied out to out-of-service. 1. Enter the busyout board UUCSS command to put every trunk or port of the UDS1 Interface circuit pack into the out-of-service state.
Page 546 Maintenance Object Repair Procedure Table 8-525. Test #135 Internal Loop-Around Test — Continued Error Test Code Result Description / Recommendation FAIL If the UDS1 connects to a line-side terminating device such as a PRI terminal (cont’d) adapter: 1. Retry the reset board command at 1-minute intervals up to 5 times. 2.
Page 547: Loss Of Signal Alarm Inquiry Test (#138)
UDS1-BD (UDS1 Interface Circuit Pack) Table 8-525. Test #135 Internal Loop-Around Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 548 Maintenance Object Repair Procedure If a UDS1 circuit pack detects certain I-CSU hardware errors, it notifies maintenance. When the maintenance subsystem receives notification of the I-CSU error, it executes this Loss of Signal Alarm Inquiry test (#138). The test, in addition to querying for a Loss of Signal alarm condition, also queries the UDS1 board to confirm the I-CSU error.
Page 549 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 550 Maintenance Object Repair Procedure Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL UDS1 Interface circuit pack detects a Loss of Signal alarm. The physical link is broken or the remote DS1 endpoint is down. Every trunk or port of this UDS1 interface circuit pack is out-of-service.
Page 551 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1301 FAIL The 120A1 CSU module is not expected. The 120A1 CSU module: The 120A1 CSU module is physically connected to the UDS1 board behind the port carrier, but the field Near-End CSU Type...
Page 552 Maintenance Object Repair Procedure Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1311 FAIL The Integrated CSU (I-CSU) Module Equipment Loopback (ELB) test (#1210) failed. This test is executed by the I-CSU during I-CSU power-up/reset (i.e., the UDS1 board is physically inserted and a CSU module is already installed) or when the CSU module is plugged on to an already initialized DS1 board.
Page 553 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1320 FAIL Either a CSU module hardware failure or an ICSU serial-interface audit failure was detected by the UDS1 circuit pack. 1.
Page 554 Maintenance Object Repair Procedure Table 8-526. Test #138 Loss of Signal Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1324 FAIL A non-service-affecting CSU module audit failure was detected by the UDS1 circuit pack. No ports should be affected. No immediate action is required. These errors indicate that the CSU module hardware may have a problem, and that it should be replaced when practical to avoid further deterioration.
Page 555: Blue Alarm Inquiry Test (#139)
UDS1-BD (UDS1 Interface Circuit Pack) Blue Alarm Inquiry Test (#139) The Blue Alarm is a signal sent by the remote DS1 endpoint when it is out-of-service. The Blue Alarm Inquiry test checks the blue alarm status of the remote DS1 endpoint. When the UDS1 Interface circuit pack detects a Blue Alarm signal from the remote DS1 endpoint, the circuit pack transmits a Yellow alarm to the remote DS1 endpoint and sends a BLUE ALARM message to the maintenance software.
Page 556 Maintenance Object Repair Procedure Table 8-527. Test #139 Blue Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 557 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-527. Test #139 Blue Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1795 FAIL The UDS1 Interface circuit pack detects a Payload Loopback Alarm (PLB). If the UDS1 Interface circuit pack connects to a leased T1 facility, call the vendor of the T1 carrier to diagnose the remote DS1 endpoint.
Page 558: Red Alarm Inquiry Test (#140)
Maintenance Object Repair Procedure Red Alarm Inquiry Test (#140) A UDS1 Interface circuit pack raises a Red alarm when the framing pattern of the incoming DS1 bit stream has been lost. The Red Alarm Inquiry test checks the framing status of a UDS1 Interface circuit pack. A UDS1 Interface circuit pack takes 3 seconds to recognize and report a Red alarm and 10 seconds to recognize and report the resolution of a Red alarm.
Page 559 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-528. Test #140 Red Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 560 Maintenance Object Repair Procedure Table 8-528. Test #140 Red Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The UDS1 interface circuit pack detected a Red alarm. An out-of-frame condition occurred on the UDS1 interface circuit pack. The UDS1 interface circuit pack will transmit a Yellow alarm to the remote UDS1 endpoint until the Red alarm is retired.
Page 561 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-528. Test #140 Red Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The test failed. The UDS1 interface circuit pack detected a loss of multiframe alarm (LMA). An out-of-frame condition occurred on the UDS1 interface circuit pack.
Page 562 Maintenance Object Repair Procedure Table 8-528. Test #140 Red Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation PASS No Red alarm is detected on the UDS1 Interface circuit pack. The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 563: Yellow Alarm Inquiry Test (#141)
UDS1-BD (UDS1 Interface Circuit Pack) Yellow Alarm Inquiry Test (#141) Receiving a Yellow alarm from a remote DS1 endpoint indicates that the remote DS1 endpoint has an out-of-frame condition. The Yellow Alarm Inquiry test is used to determine whether the remote DS1 endpoint is transmitting a Yellow alarm.
Page 564 Maintenance Object Repair Procedure Table 8-529. Test #141 Yellow Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 565 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-529. Test #141 Yellow Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The UDS1 interface circuit pack detected a Yellow alarm sent by the remote DS1 endpoint. An out-of-frame condition occurred at the DS1 endpoint. If the UDS1 connects to a T1 network facility or to another switch, do the following: 1.
Page 566 Maintenance Object Repair Procedure Table 8-529. Test #141 Yellow Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The UDS1 interface circuit pack detected a remote multiframe alarm (RMA) sent by the remote DS1 endpoint. An out-of-frame condition occurred at the DS1 endpoint.
Page 567 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-529. Test #141 Yellow Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL The UDS1 interface circuit pack is reporting a Yellow F5 fault alarm. There is a fault in the User-Network interface from the user (PBX) to the network. An out-of-frame condition occurs on the remote DS1 endpoint.
Page 568: Major Alarm Inquiry Test (#142)
Maintenance Object Repair Procedure Table 8-529. Test #141 Yellow Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation PASS Neither a Yellow alarm nor a Remote Multiframe Alarm nor a F5 state alarm is being received from the remote DS1 endpoint. The test could not relate the internal ID to the port (no board).
Page 569 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-530. Test #142 Major Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 570 Maintenance Object Repair Procedure Table 8-530. Test #142 Major Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL If the UDS1 connects to a line-side terminating device (for example, a PRI (cont’d) terminal adapter), do the following: 1.
Page 571: Minor Alarm Inquiry Test (#143)
UDS1-BD (UDS1 Interface Circuit Pack) Minor Alarm Inquiry Test (#143) The Minor alarm raised by a UDS1 Interface circuit pack indicates that the average bit error rate on the DS1 facility is greater than 1/1,000,000, but less than 1/1000. The Minor Alarm Inquiry test is used to determine that the received DS1 bit error rate is greater than 1/1,000,000 and less than 1/1000.
Page 572 Maintenance Object Repair Procedure Table 8-531. Test #143 Minor Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 573 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-531. Test #143 Minor Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation FAIL Minor alarms are often accompanied by slip and misframe alarms against the board. Trunk alarms and hardware error logs may occur on the associated trunks.
Page 574: Slip Alarm Inquiry Test (#144)
Maintenance Object Repair Procedure Table 8-531. Test #143 Minor Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation PASS No Minor alarm is detected in the UDS1 Interface circuit pack. The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 575 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-532. Test #144 Slip Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 576 Maintenance Object Repair Procedure Table 8-532. Test #144 Slip Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1 to 88 FAIL The test failed because the UDS1 interface circuit pack and the remote DS1 endpoint are not synchronized to the same clock rate. The UDS1 interface circuit pack detected a slip alarm.
Page 577: Misframe Alarm Inquiry Test (#145)
UDS1-BD (UDS1 Interface Circuit Pack) Table 8-532. Test #144 Slip Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation PASS No Slip alarm is detected on the UDS1 Interface circuit pack. The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 578 Maintenance Object Repair Procedure Table 8-533. Test #145 Misframe Alarm Inquiry Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
Page 579 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-533. Test #145 Misframe Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1 to 17 FAIL The test failed because the UDS1 interface circuit pack detected errors in the received framing bits pattern. The error code equals the number of misframes detected by the UDS1 interface circuit pack since the last misframe alarm inquiry test.
Page 580 Maintenance Object Repair Procedure Table 8-533. Test #145 Misframe Alarm Inquiry Test — Continued Error Test Code Result Description / Recommendation 1 to 17 FAIL If the UDS1 connects to a line-side terminating device such as a PRI terminal (cont’d) (cont’d) adapter: 1.
Page 581: Translation Update Test (#146)
UDS1-BD (UDS1 Interface Circuit Pack) Translation Update Test (#146) The Translation Update test sends the circuit-pack-level information specified by System Administration to the UDS1 Interface circuit pack. Translation includes the following data administered for a UDS1 Interface circuit pack (see output of display ds1 UUCSS command): DS1 Link Length between two DS1 endpoints, Synchronization Source Control, All Zero Suppression, Framing Mode, Signaling Mode, Time Slot Number of 697-Hz Tone, Time Slot Number of 700-Hz Tone, etc.
Page 582 Maintenance Object Repair Procedure DS1 Board Loop-back Test (#1209) This test is destructive. The DS1 BLB (Board Loopback) test causes a loop back at the DS1 board edge and tests DS1 board internal circuitry. The test is destructive and can only be initiated by a system technician demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.
Page 583 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-535. Test #1209 DS1 Board Loop-Back Test — Continued Error Test Code Result Description / Recommendation 1039 ABORT The UDS1 Interface circuit pack is providing timing for the system. Executing this test could cause major system disruption. If the UDS1 Interface circuit pack needs to be tested, set the synchronization reference to another DS1 Interface circuit pack or to the IPSI circuit pack via the following command sequence:...
Page 584 Maintenance Object Repair Procedure Table 8-535. Test #1209 DS1 Board Loop-Back Test — Continued Error Test Code Result Description / Recommendation 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. FAIL UDS1 Interface circuit pack failed the DS1 Board Loopback test.
Page 585: Csu Equipment Loopback Test
UDS1-BD (UDS1 Interface Circuit Pack) CSU Equipment Loop-Back Test (#1210) This test is destructive. The CSU Equipment Loopback (ELB) test causes a loopback at the near-edge of the local 120A1 CSU module and tests the connection from the DS1 board to the CSU module (DS1 board edge interconnecting cable, and CSU module edge).
Page 586 Maintenance Object Repair Procedure Table 8-536. Test #1210 CSU Equipment Loop-Back Test — Continued Error Test Code Result Description / Recommendation 1015 ABORT Ports on the UDS1 Interface circuit pack have not been busied out to out-of-service. 1. Enter the busyout board UUCSS command to put every trunk or port of the UDS1 Interface circuit pack into the out-of-service state.
Page 587 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-536. Test #1210 CSU Equipment Loop-Back Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 588 Maintenance Object Repair Procedure Table 8-536. Test #1210 CSU Equipment Loop-Back Test — Continued Error Test Code Result Description / Recommendation PASS The ELB test executed successfully. The test pattern was transmitted and received successfully over the connection from the DS1 board to the near-edge of the 120A1 CSU module.
Page 589: Csu Repeater Loopback Test
UDS1-BD (UDS1 Interface Circuit Pack) CSU Repeater Loop-Back Test (#1211) This test is destructive. The CSU Repeater Loopback (RLB) test causes a loopback at the far-edge of the local 120A1 CSU module and tests the connection from the DS1 board to and including the CSU module circuitry.
Page 590 Maintenance Object Repair Procedure Table 8-537. Test #1211 CSU Repeater Loop-Back Test — Continued Error Test Code Result Description / Recommendation 1015 ABORT Ports on the UDS1 Interface circuit pack have not been busied out to out-of-service. 1. Enter the busyout board UUCSS command to put every trunk or port of the UDS1 Interface circuit pack into the out-of-service state.
Page 591 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-537. Test #1211 CSU Repeater Loop-Back Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 592 Maintenance Object Repair Procedure Table 8-537. Test #1211 CSU Repeater Loop-Back Test — Continued Error Test Code Result Description / Recommendation PASS The RLB test executed successfully. The test pattern was transmitted and received successfully over the connection from the UDS1 board to the far-edge of the 120A1 CSU module.
Page 593 UDS1-BD (UDS1 Interface Circuit Pack) CPE Loop-Back Jack Test (#1212) This test is destructive. The CPE Loop-Back Jack (CLJ-LB) test causes a loopback at the CPE Loop-Back Jack and tests the building wiring connection between the UDS1-BD DS1 board and the CPE Loop-Back Jack. The test is highly destructive and can only be initiated by a system technician demanded test ds1-loop UUCSS cpe-loopback-jack-test-begin [number-of-bits bit-pattern] command.
Page 594 Maintenance Object Repair Procedure Table 8-538. Test #1212 CPE Loop-Back Jack Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the test ds1-loop UUCSS cpe-loopback-jack-test-begin command at 1-minute intervals up to 5 times. 1005 ABORT CPE Loop-Back Jack test cannot be executed in the current configuration.
Page 595 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-538. Test #1212 CPE Loop-Back Jack Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 596 Maintenance Object Repair Procedure Table 8-538. Test #1212 CPE Loop-Back Jack Test — Continued Error Test Code Result Description / Recommendation FAIL The CLJ-LB test failed because it was not set up properly. The UDS1 interface pack could not successfully put the CPE loopback jack into loop-back mode. 1.
Page 597 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-538. Test #1212 CPE Loop-Back Jack Test — Continued Error Test Code Result Description / Recommendation PASS The CPE Loop-Back Jack test has successfully began executing. The test will continue to run until the system technician enters the test ds1-loop UUCSS end-loopback/span-test command or the release board UUCSS command.
Page 598 Maintenance Object Repair Procedure Far CSU Loop-Back Test (#1213) This test is destructive. The Far CSU Loopback (R-LLB) test causes a loopback at the far-end CSU and tests all circuitry and facilities from the local DS1 board to the far-end CSU. The test is destructive and can only be initiated by a technician-demanded test ds1-loop UUCSS far-csu-loopback-test-begin command.
Page 599 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-539. Test #1213 Far CSU Loop-Back Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the test ds1-loop UUCSS far-csu-loopback-test-begin command at 1-minute intervals up to 5 times. 1005 ABORT Far CSU Loopback test cannot be executed in the current configuration.
Page 600 Maintenance Object Repair Procedure Table 8-539. Test #1213 Far CSU Loop-Back Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 601 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-539. Test #1213 Far CSU Loop-Back Test — Continued Error Test Code Result Description / Recommendation FAIL The Far CSU Loopback test was not set up properly. The framed 3-in-24 test pattern, generated by the UDS1 Interface circuit pack and looped back through the far-end CSU, could not be detected properly by the UDS1 circuit pack.
Page 602 The One-Way Span test allows 1-way span testing to and from remote test equipment or another Avaya communications system. This tests all circuitry and facilities from the local DS1 board to the remote test equipment or other Avaya communications system.
Page 603 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-540. Test #1214 One-Way Span Test Error Test Code Result Description / Recommendation ABORT Internal system error 1. Retry the test ds1-loop UUCSS one-way-span-test-begin command at 1-minute intervals up to 5 times. 1005 ABORT One-Way Span test cannot be executed in the current configuration.
Page 604 Maintenance Object Repair Procedure Table 8-540. Test #1214 One-Way Span Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 605 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-540. Test #1214 One-Way Span Test — Continued Error Test Code Result Description / Recommendation PASS The One-Way Span test has successfully began transmitting a framed 3-in-24 test pattern. The test will continue to run until the system technician enters the test ds1-loop UUCSS end-loopback/span-test command or the release board UUCSS command.
Page 606 Maintenance Object Repair Procedure Inject Single Bit Error Test (#1215) This test is destructive. The Inject Single Bit Error test causes a single bit error to be sent within an active framed 3-in-24 test pattern. The test is highly destructive and can only be initiated by a system technician demanded test ds1-loop UUCSS inject-single-bit-error command.
Page 607 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-541. Test #1215 Inject Single Bit Error Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 608 Maintenance Object Repair Procedure Table 8-541. Test #1215 Inject Single Bit Error Test — Continued Error Test Code Result Description / Recommendation PASS A single bit error has been successfully injected into an active framed 3-in-24 test pattern. The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 609 UDS1-BD (UDS1 Interface Circuit Pack) End Loopback/Span Test (#1216) This test is destructive. The End Loopback/Span test terminates an active loopback or span test on a UDS1 circuit pack. Bit error counting against the received test pattern stream is terminated and sending of the framed 3-in-24 test pattern is halted. If either the CPE Loop-Back Jack or the far-end CSU is looped, the appropriate loopback deactivate code is sent.
Page 610 Maintenance Object Repair Procedure Table 8-542. Test #1216 End Loopback/Span Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity.
Page 611 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-542. Test #1216 End Loopback/Span Test — Continued Error Test Code Result Description / Recommendation PASS The active long-duration loopback or span test on the UDS1-BD circuit pack was successfully terminated. The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 612 Maintenance Object Repair Procedure ICSU Status LEDs Test (#1227) The UDS1 circuit pack has four status LEDs on the faceplate in addition to the three standard faceplate LEDs. These four status LEDs are associated with the 120A1 Channel Service Unit (CSU) Module that can be connected to the UDS1-BD board through the I/O connector panel behind the port carrier.
Page 613 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-543. Test #1227 ICSU Status LEDs Test — Continued Error Test Code Result Description / Recommendation PASS The ICSU Status LEDs test executed successfully. A PASS result, however, does not necessarily mean that the status LEDs behaved properly. It only means that the software successfully attempted to light the status LEDs.
Page 614 Maintenance Object Repair Procedure Echo Canceller Test (#1420) This test is destructive. NOTE: This test is executed only for TN464GP/TN2464BP circuit packs that have been administered on the DS1 circuit pack form to provide echo cancellation. The TN464GP/TN2464BP must be busied out before this demand test is run.
Page 615 UDS1-BD (UDS1 Interface Circuit Pack) Table 8-544. Test #1420 Echo Canceller Test — Continued Error Test Code Result Description / Recommendation 2012 ABORT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABORT Could not allocate the necessary system resources to run this test. 1.
Page 616: Ups (Server Ups)
Maintenance Object Repair Procedure UPS (Server UPS) The UPS MO supports the UPS device for each S8700 Media Server. This MO’s maintenance software reacts to UPS-generated inline errors via SNMP traps. NOTE: This MO provides no periodic or on-demand tests.
Page 617: Ups (Server Ups)
UPS (Server UPS) Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap #3, Event ID #10 Alarm string = #1, ACT, UPS, A, 10, WRN, Miscellaneous trap, e.g., bad battery. upsAlarmShutdownPending This UPS trap [Event #10] is a miscellaneous environmental alarm sent from the UPS that supports server A.
Page 618 Maintenance Object Repair Procedure Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap (3), Event ID #18 Alarm string = #1,ACT,UPS,A,18,MIN,Miscellaneous trap, e.g., bad battery upsAlarmInputBad This UPS trap [Event #18] is a miscellaneous environmental alarm. This alarm is sent from the UPS that in this case supports server A.
Page 619 UPS (Server UPS) Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap (4), Event #23 Alarm string = #1,ACT,UPS,A,23,WRN,Miscellaneous trap, e.g., bad battery upsAlarmCommunicationsLost This UPS trap [Event #23] is a miscellaneous environmental alarm. This alarm is sent from the UPS that in this case supports server A.
Page 620 Maintenance Object Repair Procedure Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap (3), Event ID #28 Alarm string = #1,ACT,UPS,A,28,WRN,Miscellaneous trap, e.g., bad battery upsAlarmUpsOutputOff This UPS trap [Event #28] is a miscellaneous environmental alarm. This alarm is sent from the UPS that in this case supports server A.
Page 621 UPS (Server UPS) Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap (4), Event ID #33 Alarm string = #1,ACT,UPS,A,33,WRN,Miscellaneous trap, e.g., bad battery upsAlarmOutputOverload This UPS trap [Event #33] is a miscellaneous environmental alarm. This alarm is sent from the UPS that in this case supports server A.
Page 622 Maintenance Object Repair Procedure Table 8-545. Server’s SNMP Traps Enterprise Specific Trap and Event Numbers Definition of Traps Trap (3) - upsAlarmFuseFailure Alarm string = #1,ACT,UPS,A,38,WRN,Miscellaneous trap, e.g., bad battery This UPS trap [Event #38] is a miscellaneous environmental alarm. This alarm is sent from the UPS that in this case supports server A.
Page 623 VAL-BD (Voice Announcements over LAN Circuit Pack) VAL-BD (Voice Announcements over LAN Circuit Pack) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO VAL-BD MINOR test board UUCSS long Voice Announcements over the LAN Circuit Pack VAL-BD WARNING...
Page 624 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1 (a) Sanity MINOR 18 (b) WARNING release board UUCSS 217 (c) None WARNING 65535 Control Channel MINOR test board UUCSS l r 20...
Page 625 VAL-BD (Voice Announcements over LAN Circuit Pack) Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 3845 (v) 3846 (w) 3848 (x) 3851 (y) 3852 (z) 3853 (aa) 3854 (ab) 3855 (ac) 3856 (ad) Continued on next page Notes: a.
Page 626 Maintenance Object Repair Procedure e. Error Type 513 — Circuit pack detected and reported hardware failure. 1. Reset the circuit pack (reset board UUCSS). Aux Data: 4352 External RAM error 4353 Internal RAM error 4355 ROM Checksum error 4356 Angel Message Corruption error 4357 Instruction set error f.
Page 627 VAL-BD (Voice Announcements over LAN Circuit Pack) j. Error Type 1798 — Unable to write translation RAM. 1. Attempt to clear alarm (reset board UUCSS). 2. If alarm recurs within 15 minutes, replace the circuit pack. k. Error Type 2049 — Packet Interface test (#598) failed. 1.
Page 628 Maintenance Object Repair Procedure m. Error Type 2561–2668 — System software received an indication that the socket was closed due to an error. Errors are reported as log only. Errors logged here are for the sockets that had no processor channels associated with them, for example, sockets to read SNMP data.
Page 629 VAL-BD (Voice Announcements over LAN Circuit Pack) q. Error Type 3586 and 3999 — Switch removed hyperactive circuit pack that reported threshold number of errors. One or more of the following symptoms can be present: Circuit pack port tests return NO BOARD. List configuration command shows circuit pack and ports are installed properly.
Page 630 Maintenance Object Repair Procedure Below, Error Types correspond to descriptions. 3841 Internal firmware error. 3843 Bad translation RAM. Call uses another translation location. These errors do not affect service, however, they can cause reports of other errors that do affect service. If Error Type 3843 begins to affect service, it escalates to Error Type 1294 (See Note g).
Page 631 VAL-BD (Voice Announcements over LAN Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate errors in the order they appear in the table below. Short Test Long Test Order of Investigation Sequence Sequence D/ND Control Channel Loop-around test (#52) Circuit Pack Restart test (#594) Invalid LAPD Frame Error Counter test (#597) PPE/LANBIC Receive Parity Error Counter test (#595)
Page 632: Circuit Pack Restart Test
Maintenance Object Repair Procedure Circuit Pack Restart Test (#594) NOTE: This test is destructive. Execute this test (not part of either short or long demand test sequence) to reset the circuit pack only if there are PPCPU errors. This test fails if the circuit pack does not return to a sane state after being reset.
Page 633 VAL-BD (Voice Announcements over LAN Circuit Pack) PPE/LANBIC Receive Parity Error Counter Test (#595) This test is non-destructive. When the VAL circuit pack detects a parity error with a received frame, it increments the PPE/LANBIC Receive Parity error counter. This test reads and clears the counter, and can verify repair of the problem. Errors can indicate a problem with: This circuit pack A packet bus...
Page 634 Maintenance Object Repair Procedure Receive FIFO Overflow Error Counter Test (#596) This test is non-destructive. When the VAL circuit pack detects packet bus buffer overflow, it increments the error on the FIFO Overflow error counter. This test reads and clears the counter. If errors are: Then they can be due to: Occasional...
Page 635 VAL-BD (Voice Announcements over LAN Circuit Pack) Invalid LAPD Frame Error Counter Test (#597) This test is non-destructive. The VAL circuit pack detects invalid frames when it receives a frame with a CRC error an unrecognizable frame a recognizable frame in an unexpected state When the VAL circuit pack detects an invalid LAPD frame, it increments the Invalid LAPD Frame error counter.
Page 636 Maintenance Object Repair Procedure Packet Interface Test (#598) This non-destructive test checks the packet bus interface circuitry on the VAL circuit pack. Test failure indicates faulty circuit pack. Table 8-551. Test #598 Packet Interface Test Error Test Code Result Description / Recommendation 2000 ABORT Did not receive circuit pack test response within the allowable time period.
Page 637 VAL-BD (Voice Announcements over LAN Circuit Pack) Table 8-552. Test #600 Congestion Query Test Error Test Code Result Description / Recommendation 2000 ABORT Did not receive circuit pack test response within the allowable time period. 1. Retry command at 1-minute intervals up to 5 times. 2.
Page 638 Maintenance Object Repair Procedure Link Status Test (#601) This non-destructive test determines the state of the call-control signaling link for VALs. If the signaling link is physically connected, the test sends a test frame over the link and checks for a response. The test passes only if both the signaling link is connected and the test frame is successfully transmitted.
Page 639 VAL-BD (Voice Announcements over LAN Circuit Pack) Configurations The following figure shows the configuration options for the TN2501AP (VAL) circuit pack within a system. cydfval LJK 032001 Figure Notes 1. TN2501AP VAL announcement 6. Your LAN (See cable) circuit pack 7.
Page 640 Maintenance Object Repair Procedure Faceplate LEDs The following figure shows the 9 LEDs on the TN2051AP faceplate. Descriptions of each LED are in Table 8-554. LINK TRMT 100M Figure 8-58. TN2501AP faceplate LEDs The following table lists the TN2501AP faceplate LEDs, the type of behavior (on, off, flashing, or intermittent), and a description of the condition.
Page 641 VAL-BD (Voice Announcements over LAN Circuit Pack) Table 8-554. TN2501AP LEDs Behavior Description On solid Circuit pack failure or a major or minor on-board alarm Green On solid Firmware is self-downloading to the circuit pack or testing in progress. Amber On solid Firmware is self-downloading to the circuit pack.
Page 642 Maintenance Object Repair Procedure Other hardware To establish LAN connections the TN2501AP circuit pack requires a Backplane Adapter that attaches to the Amphenol connector behind the cabinet, corresponding to the TN2501AP integrated announcement circuit pack slot. LAN cable that attaches to the Backplane Adapter. Backplane Adapter The following figure shows the Backplane Adapter (label reads IP Media Processor).
Page 643: Lan Cable
VAL-BD (Voice Announcements over LAN Circuit Pack) LAN cable The TN2501AP circuit pack does not include cables to connect the circuit pack to your LAN. The following table lists the cable category and connection port. Ethernet connection speed Cable Connection description 10 Mbps Category 3 Connects through the RJ45 jack (note #2...
Page 644 Maintenance Object Repair Procedure Table 8-555. VAL maintenance commands — Continued Command Use this command to status link Generate a status report about a specific administered Ethernet link. (For VAL this means the administered Ethernet link.) status val-ip Generate an IP-related, MIB data status report. netstat ip-route Generate a report showing the status of the VAL IP routes on the VAL circuit pack.
Page 645 VAL-PT (Voice Announcements over LAN Packet/Port) VAL-PT (Voice Announcements over LAN Packet/Port) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO VAL-PT MAJOR test port UUCSSpp long VAL Port Maintenance VAL-PT MINOR test port UUCSSpp long VAL Port Maintenance VAL-PT WARNING...
Page 646 Maintenance Object Repair Procedure Notes: a. Error Type 001: SCOTCH Synchronous Loop-Around test (#1275) failed. 1. Test the port (test port UUCSSpp long). 2. See ‘‘SCOTCH Synchronous Loop-Around Test (#1275)’’ on page 8-1345 repair procedures. b. Error Type 257: VAL port detected overrun or underrun condition that can indicate a hardware problem.
Page 647 VAL-PT (Voice Announcements over LAN Packet/Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate errors in the order they appear in the table below. Table 8-556. System Technician-Demanded Tests: VAL-PT Short Test Long Test Order of Investigation Sequence Sequence D/ND TDM Loop-Around test (#1285) SCOTCH Synchronous Loop-Around test (#1275) D = Destructive, ND = Non-destructive...
Page 648 Maintenance Object Repair Procedure Table 8-557. Test #1285 TDM Loop-Around Test Error Test Code Result Description / Recommendation 1000 ABORT The port is in use. 1. Retry the command when the port is idle. You can force the port to the idle state with the busyout port UUCSS command.
Page 649 VAL-PT (Voice Announcements over LAN Packet/Port) SCOTCH Synchronous Loop-Around Test (#1275) This test is destructive. This test verifies the circuit in the data path of a VAL announcement port call. This test fails if the data transmitted on the port does not match the data received in the loop-around mode.
Page 650 Maintenance Object Repair Procedure Table 8-558. Test #1275 SCOTCH Synchronous Loop-Around Test — Continued Error Test Code Result Description / Recommendation FAIL VAL circuit pack detected test failure. If the problem persists, reset the circuit pack (busyout board UUCSS, reset board UUCSS, and release board UUCSS). If the problem persists, replace the circuit pack.
Page 651 VC-BD VC-BD MO’s Name (in Alarm Alarm Initial Command to Log) Level Full Name of MO VC-BD MAJOR test board UUCSS l r# Voice Conditioner circuit pack VC-BD MINOR test board UUCSS l r# Voice Conditioner circuit pack VC-BD WARNING test board UUCSS s r# Voice Conditioner circuit pack Where UU is the universal cabinet number (1–64);...
Page 652 Maintenance Object Repair Procedure Table 8-559. VC-BD Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1025 (f) 4363 NPE Audit test (#50) 1281 (g) SAKI Sanity test (#53) MAJOR 1293 to 46088 SAKI Sanity test (#53) MINOR...
Page 653 VC-BD Reset the circuit pack by executing the busyout board UUCSS, reset board UUCSS, and release board UUCSS commands. When it is reset, the circuit pack executes a set of tests to detect the presence of any of the above faults. The detection of one these errors during initialization causes the circuit pack to lock-up and appear insane to the system.
Page 654 Maintenance Object Repair Procedure System Technician-Demanded Tests: Descriptions and Error Code Short Test Long Test Order of Investigation Sequence Sequence D/ND Control Channel Loop-around test (#52) D = Destructive; ND = Nondestructive See repair procedures described in ‘‘XXX-BD (Common Port Circuit Pack)’’.
Page 655 VC-DSPPT VC-DSPPT MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO VC-DSPPT MAJOR test port UUCSSpp Voice Conditioner DSP Port VC-DSPPT MINOR test port UUCSSpp Voice Conditioner DSP Port VC-DSPPT WARNING test port UUCSSpp Voice Conditioner DSP Port Where UU is the universal cabinet number (1–64);...
Page 656 Maintenance Object Repair Procedure Notes: a. This port has been busied out by the busyout port UUCSSpp command. b. The VC DSP Port NPE Crosstalk test (#1103) failed. c. The VC DSP Port Local TDM Loopback test (#1104) failed. Run the long test sequence.
Page 657 VC-DSPPT Table 8-561. Test #1103 NPE Crosstalk Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call. 1. Retry the command at 1-minute intervals up to 5 times. 2012 ABORT Internal system error...
Page 658 Maintenance Object Repair Procedure Figure 8-60. VC Circuit Pack DSP Port Local TDM Loop-Back Test 8-1354 Issue 1 May 2002 555-233-142...
Page 659 VC-DSPPT Table 8-562. Test #1104 VC DSPPT Local TDM Loop-Back Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available, or the port is busy 1001 with a valid call. 1.
Page 660 Maintenance Object Repair Procedure VC-DSP Port DSP Loop-Back Test (#1105) This test is destructive. This test verifies the connectivity of a VC-DSPPT across the TDM bus. It aborts if calls associated with the port are in progress. Failure of this test indicates an on-board fault associated with the port hardware on the circuit pack.
Page 661 VC-DSPPT Table 8-563. Test #1105 VC-DSP Port DSP Loop-Back Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available, or the port is busy with a valid call. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABORT The system could not allocate time slots for the test, the traffic load on the...
Page 662 Maintenance Object Repair Procedure VC Port Reset DSP Test (#1106) This test is destructive. This test resets the VC-DSPPT and the DSP associated with it. As part of the reset procedure, the VC-DSPPT will execute a series of self-tests on the hardware.
Page 663: Multimedia Call Handling (Mmch)
VC-LEV (Voice Conditioner DSP Port Level) VC-LEV (Voice Conditioner DSP Port Level) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ‘‘Resolving VC-LEV VC-LEV MAJOR VC-LEV Errors/Alarms’’ The MMCH feature must be enabled on the system-parameters customer-options form before you can change these fields.
Page 664: Display System-Parameters Maintenance
Maintenance Object Repair Procedure Resolving VC-LEV Errors/Alarms VC ports are a key part of the MMCH feature, any loss in the number of ports available for use degrades the MMCH customer defined service level. If a VC circuit pack or port is busied out using the busyout board or busyout port command, these out-of-service ports are not included in the VC level calculation, thus allowing a technician to busyout a VC circuit pack for maintenance reasons without causing a MAJOR alarm to be raised.
Page 665 VC-LEV (Voice Conditioner DSP Port Level) Error Log Entries and Test to Clear Values Table 8-565. VC-LEV Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1 (a) None MAJOR Notes: a. The number of VC resources in the system that are in service has fallen below the calculated minimum value.
Page 666 Maintenance Object Repair Procedure VC-SUMPT MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO VC-SUMPT MAJOR test port UUCSSpp Voice Conditioner Summer Port VC-SUMPT MINOR test port UUCSSpp Voice Conditioner Summer Port VC-SUMPT WARNING test port UUCSSpp Voice Conditioner Summer Port Where UU is the universal cabinet number (1–64);...
Page 667 VC-SUMPT Notes: a. This port has been busied out with the busyout port UUCSSpp command. b. The circuit pack has been removed or has been insane for more than 11 minutes. To clear the error, replace or reinsert the circuit pack. c.
Page 668 Maintenance Object Repair Procedure VC-SUMPT Port NPE Crosstalk Test (#6) This test is destructive. The NPE controls port connectivity and gain and provides conferencing functions. The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, 1-way and noisy connections may be observed.
Page 669 VC-SUMPT The tests are run in the above order. If the first test fails, the switch returns an error code, and the second test is not executed. Figure 8-62. VC Circuit Pack Summer Port Loop-Back Test 555-233-142 Issue 1 May 2002 8-1365...
Page 670 Maintenance Object Repair Procedure Table 8-568. Test #1100 VC Summer Port Local TDM Loop-Back Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available, or the port may be busy with a valid call. 1.
Page 671 Wideband Switching supports end-to-end connectivity between customer endpoints at data rates from 128 to 1536 kbps over T1 facilities and to 1984 kbps over E1 facilities. S8700 IP Connect switching capabilities support wideband calls comprised of multiple DS0s that are switched end-to-end as a single entity.
Page 672 Although Wideband Access Endpoints are used primarily for line-side facilities, these endpoints can also be administered on network DS1 facilities to connect S8700 IP Connect to non-switched network services, such as the Avaya fractional T-1 service. An example of this is the Avaya Static Integrated Network Access, where a trunk group to AT&T 4ESS Switched Services shares an access T-1...
Page 673 WAE-PORT (Wideband Access Endpoint Port) Error Log Entries and Test to Clear Values Table 8-569. Wideband Access Endpoint Maintenance Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test access-endpoint extension sh r 1 18 (a) busyout access-endpoint WARNING...
Page 674 Maintenance Object Repair Procedure Technician-Demand Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the NPE Crosstalk test (#6), you may also clear errors generated from other tests in the testing sequence.
Page 675 WAE-PORT (Wideband Access Endpoint Port) Table 8-570. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1002 ABORT The system could not allocate time slots for the test. The system may be under heavy traffic conditions or it may have time slots out-of-service due to TDM-BUS errors.
Page 676 Maintenance Object Repair Procedure Conference Circuit Test (#7) The Conference Circuit test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. The NPE is instructed to listen to several different tones and conference the tones together. The resulting signal is then measured by a Tone Detector port.
Page 677 WAE-PORT (Wideband Access Endpoint Port) Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the UDS1 Interface circuit pack to ensure that the wideband access endpoint port’s translation is correct. Table 8-572. Test #36 Audit and Update Test Error Test Code...
Page 678 Maintenance Object Repair Procedure XXX-BD (Common Port Circuit Pack) MO’s Name (in Alarm Initial Command Alarm Log) Level to Run Full Name of MO XXX-BD MAJOR test board UUCSS Common Port Circuit Pack maintenance XXX-BD MINOR test board UUCSS Common Port Circuit Pack maintenance XXX-BD WARNING test board UUCSS...
Page 679 XXX-BD (Common Port Circuit Pack) The following list of circuit packs are listed by apparatus code. Table 8-573. XXX-BD Common Circuit Packs Apparatus Code Name Type CPP1 Memory Expansion Control ED-1E546 EMBEDDED AUDIX R3 System Port Assembly (TN2169) (TN2170) (TN566) (TN567) ED-1E546 Call Visor ASAI over the DEFINITY (LAN) Gateway R1 Port Assembly...
Page 680 Maintenance Object Repair Procedure Table 8-573. XXX-BD Common Circuit Packs — Continued Apparatus Code Name Type TN742 Analog Line Port TN744/B Call Classifier Service TN744/C/D Call Classifier - Detector Service TN746/B Analog Line Port TN747B Central Office Trunk Port TN748/B/C/D Tone Detector Service TN750/B/C...
Page 681 XXX-BD (Common Port Circuit Pack) Table 8-573. XXX-BD Common Circuit Packs — Continued Apparatus Code Name Type TN2146 Direct Inward Dialing Trunk Port TN2147/C Central Office Trunk Port TN2149 Analog Line Port TN2180 Analog Line Port TN2181 Digital Line 2-Wire DCP Port TN2183 Analog Line...
Page 682 Maintenance Object Repair Procedure Error Log Entries and Test to Clear Values Table 8-574. Common Port Circuit Pack Maintenance Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test board UUCSS sh r 1 1 (a) Circuit pack removed or MINOR...
Page 683 XXX-BD (Common Port Circuit Pack) Notes: a. Error type 1 indicates the circuit pack has stopped functioning or has been physically removed from the system. This error type does not apply to ANN-BD, DETR-BD, S-SYN-BD, M/T-BD, or CLSFY-BD. The alarm is logged approximately 11 minutes after removal of the circuit pack or failure of the SAKI Sanity test (#53).
Page 684: List Configuration
Maintenance Object Repair Procedure h. This error, when reported with Aux data in the range of 4352 to 4358, indicates that the circuit pack has reported an on-board hardware failure. The circuit pack will continuously test the hardware and report the results approximately every 10 minutes.
Page 685 XXX-BD (Common Port Circuit Pack) Technician-Demand Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the NPE Audit test (#50), you may also clear errors generated from other tests in the testing sequence.
Page 686 Maintenance Object Repair Procedure NPE Audit Test (#50) The system sends a message to the on-board microprocessor to update the network connectivity translation for every NPE (Network Processing Element) on the circuit pack. Table 8-575. Test #50 NPE Audit Test Error Test Code...
Page 687 XXX-BD (Common Port Circuit Pack) Ringing Application Test (#51) This test checks the ringing application circuitry common to every port on an Analog Line circuit pack. Table 8-576. Test #51 Ringing Application Circuit Test Error Test Code Result Description / Recommendation 1000 ABORT Could not allocate the necessary system resources to run test.
Page 688 Maintenance Object Repair Procedure Table 8-576. Test #51 Ringing Application Circuit Test — Continued Error Test Code Result Description / Recommendation 1008 ABORT Could not allocate a ringing circuit for one of the following reasons: all the ringing circuits are in use; the ringing generator is defective; ringing generator is not wired correctly.
Page 689 XXX-BD (Common Port Circuit Pack) Control Channel Loop-Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 8-577. Test #52 Control Channel Loop-Around Test Error Test Code Result Description / Recommendation None ABORT System resources required for this test are not available.
Page 690 Maintenance Object Repair Procedure SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack. It is executed as part of the long test sequence only for the Tone-Clock circuit pack and DS1 interface circuit packs. Other common circuit packs can be reset with the reset board UUCSS command which also executes this test.
Page 691: Neon Test
XXX-BD (Common Port Circuit Pack) Neon Test (#220) This test checks the voltage required to light the neon lamp on an analog terminal. A relay connects a 150V DC source from the backplane of the circuit pack onto the voltage bus, and another relay connects a 2K shunt from the bus to ground. Current in the line is then monitored to determine if the voltage is present.
Page 692 Maintenance Object Repair Procedure Table 8-579. Test #220 Neon Test — Continued Error Test Code Result Description / Recommendation FAIL The test failed because no neon current was detected. 1. Determine if there is a TN755 or TN752 power unit circuit pack installed in the same carrier as the TN746 or TN769 analog line circuit pack that failed the test.
Page 693: Terminal Alarm Notification
Index ATMS, see Automatic Transmission Measurement System attendant console, LEDs audits (tests), see tests and audits 8-14 AUDIX circuit pack (ADXDP-BD) 8-15 AUDIX digital port (ADXDP-PT) Automatic Transmission Measurement System (ATMS) Numerics 5-34, 8-821 4-12 auxiliary error codes 120A ICSU 8-80 8-port analog line (ANL-LINE, ANL-NE-L) 5-24...
Page 694: Release Commands
Index circuit packs, (continued) digital port 8-702, 8-853, 8-1173 1-19 tone-clock insertion loss 1-12 tone-clock LEDs Digital Signal Level 1 (DS1) 8-456, 8-626, 8-713, universal DS1 (UDS1) interface digital-to-analog 8-743, 8-1211 1-21 peak noise level 4-42 1-20 using the packet bus quantization distortion loss yellow LEDs digital-to-digital...
Page 695: Troubleshooting Isdn-Pri
Index ESD, See electrostatic discharge Initialization and Administration System (INADS) European conference of postal/ telecom rate 1, see CEPT1 alarm notification 8-622 expansion port networks (EPNs) maintenance objects (MOs) 4-66 1-19 troubleshooting packet bus insertion loss install a BIU or Rectifier 8-1175 interchanges, tone-clocks interface...
Page 696: Power Interruptions
Index 1-21 loop input impedances loss 1-21 echo return 1-19 insertion 1-20 quantization distortion 8-856 Off-Premises Station (OPS) Line 1-21 single-frequency Open System Interconnect model data-link layer physical layer option jumpers 8-1222 TN464 8-1222 universal DS1 (UDS1) interface circuit packs 8-821 maintenance Originating Test Line (OTL)
Page 697: Protocols
Index 1-11 1-17 RS-464A 8-901 1-14 PRI endpoint port (PE-BCHL) rules, connectivity 1-22 private line service codes procedures 4-18 fiber fault isolation 8-982 process sanity audits (PROC-SAN) 8-950, 8-958 property management system (PMS) 8-950 property management system link (PMS-LINK) 4-2, safety precautions 8-594 Proshare...
Page 698: Signaling
Index 8-1123 TDM bus clock (TDM-CLK) tests and audits, (continued) 5-18 8-500, 8-742, 8-750, TDM Bus Time Slot Test Call #146 Translation Update Test 1-21 8-1277 technical specifications terminal #148 TDM Bus Clock Circuit Status Inquiry Test 1-22 8-1128 equipment port wiring 8-1130 Terminal Alarm Notification #149 TDM Bus Clock Slip Inquiry Test...
Page 699 Index tests and audits, (continued) tests and audits, (continued) 8-396, 8-770 8-304, 8-974 #35 Port Diagnostic Test #601Link Status Test 8-689, 8-864, 8-1146, 8-881 #36 Audit and Update Test #602 PDATA Port Local Loop-Around Test 8-1373 8-882 #603 System Port Connectivity Test 8-214, 8-368, 8-1163 8-1199...
Page 700: Traceroute
Index TN2182 circuit packs troubleshooting 8-562 description duplicated switch processing element (SPE) 8-1175 4-30 interchanges ISDN-BRI/ASAI problems 8-1177 4-28 international settings ISDN-PRI endpoints (wideband) 8-1177 4-26 replacing ISDN-PRI problems 8-1123 4-34 time division multiplex (TDM) bus clocks ISDN-PRI test call problems 8-702, 8-853, 8-1173 4-37...

Avaya S8700 Maintenance Manual

Table of Contents

Table of Contents

Initialization

Maintenance Commands

Alarms, Errors, and Troubleshooting

Hardware Configurations

LED Interpretation

Table of Contents

Quick Links

Chapters

Troubleshooting

Related Manuals for Avaya S8700

Summary of Contents for Avaya S8700

Table of Contents