User manual

ManualsBrandsAvaya ManualsOtherHome Security System 03-300430

Maintenance Alarms for

Avaya Communication Manager 3.0,

Media Gateways and Servers

03-300430

Issue 1

June 2005

Summary of content (2574 pages)

PAGE 1
Maintenance Alarms for Avaya Communication Manager 3.
PAGE 2
Copyright 2005, Avaya Inc. All Rights Reserved Notice Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty.
PAGE 3
Electromagnetic Compatibility (EMC) Standards This product complies with and conforms to the following international EMC standards and all relevant national deviations: Limits and Methods of Measurement of Radio Interference of Information Technology Equipment, CISPR 22:1997 and EN55022:1998.
PAGE 4
A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord and modular plug is provided with this product. It is designed to be connected to a compatible modular jack that is also compliant. It is recommended that repairs be performed by Avaya certified technicians. The equipment cannot be used on public coin phone service provided by the telephone company.
PAGE 5
Contents About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Structure of book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Downloading this book and updates from the Web . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Contents UPS LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 IPSI LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 650A Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 655A Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Duplication memory card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Contents ANL-LINE (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 ANL-NE-L (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 AN-LN-PT (Analog Line Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 ANN-BD (Announcement circuit pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 ANN-PT (announcement port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
Contents BRI-PORT (ISDN-BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 BRI-SET, Various Adjuncts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708 BRI-DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736 CAB-CALM (Customer alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737 CAB-EXFR (emergency transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Contents DTMR-PT (Dual-Tone Multifrequency Receiver Port) . . . . . . . . . . . . . . . . . . . . . . . 1115 E-DIG-BD (Multi Application Platform Board) . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 E-DIG-RES (TN800 reserve slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123 E-DIG-STA (Emulated Digital Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124 EMG-XFER (Emergency Transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
Contents LIC-ERR (License-Error Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479 LOG-SVN (Login Security Violation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487 MAINT (PN’s Maintenance Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490 MAPD-BD (MAPD Interface Circuit Pack TN802) . . . . . . . . . . . . . . . . . . . . . . . . . 1508 MEDPRO (Media Processor MAPD Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Contents PLAT-ALM (Platform Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838 PMS-LINK (Property Management System Link) . . . . . . . . . . . . . . . . . . . . . . . . . 1839 PMS-PRNT/JNL-PRNT (PMS Printer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846 PNC-DUP (PNC Duplication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851 POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Contents SYSTEM (System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186 TBRI-BD (TN2185 ISDN Trunk-Side BRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2192 TBRI-PT (ISDN Trunk-Side BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2200 TBRI-TRK (Trunk-Side ISDN BRI Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224 TDM-BUS (TDM Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 13
About this book Overview This document provides procedures to monitor, test, and maintain an Avaya Media Server or Gateway system. It covers many of the faults and troubles that can occur and provides simple procedures to correct them. Simple, traditional troubleshooting methods are sometimes sufficient to locate and clear faults. The traditional methods include substitution, visual inspections, continuity checks, and clarification of operating procedures with end users.
PAGE 14
About this book It does not contain information about ● DEFINITY G3R (see 555-233-117: Maintenance for DEFINITY R Servers or 555-233-142: Maintenance for Avaya S8700 Media Servers with G600 Media Gateway) ● DEFINITY SI (see 555-233-119: Maintenance for DEFINITY SI Servers or 555-233-143: Avaya S8700 Media Servers with MCC1/SCC1) ● Avaya S8100 Media Server (see 555-233-123: Maintenance for DEFINITY CSI Servers) ● IBM eServer BladeCenter HS20 Type 8832 ● G150/G250/G350 Media Gateways Structure of b
PAGE 15
Structure of book Chapters or Maintenance Objects (MOs) At the Chapter or MO level, bold names of the server(s) or gateway(s) that are represented within the sections to follow are inserted immediately after the Chapter title or MO title. For example, the heading for the SER-BUS (Serial communication bus) MO looks like: SER-BUS (Serial communication bus) G650 The G650 after the title indicates that the material in this MO relates to the G650 media gateway.
PAGE 16
About this book Paragraphs or in-line comments At the paragraph level and for comments in-line, the specific media server or gateway is indicated by its bold name, and the parenthetical information follows immediately afterward. For example, a paragraph insert for the S8700 and S8500 media servers might looks like: 1. If the Tone-Clock circuit is a slave clock, then the EI to which it is listening is providing a bad timing source. Follow the diagnostic procedures specified for TDM-CLK Error Code 2305. 2.
PAGE 17
Downloading this book and updates from the Web This book is not intended to solve all levels of troubles. It is limited to troubles that can be solved using: ● The Alarm Log ● The Error Log ● Trouble-clearing procedures ● Maintenance tests ● Traditional troubleshooting methods If the trouble still has not been resolved, it is the maintenance technician’s responsibility to escalate the problem to a higher level of technical support.
PAGE 18
About this book Safety labels and security alert labels Observe all caution, warning, and danger statements to help prevent loss of service, equipment damage, personal injury, and security problems. This book uses the following safety labels and security alert labels: ! CAUTION: A caution statement calls attention to a situation that can result in harm to software, loss of data, or an interruption in service.
PAGE 19
Related resources Related resources Table 1: Additional document resources on page 19 lists additional documentation that is available for you, and which has been referenced within this document.
PAGE 20
About this book Table 1: Additional document resources (continued) Document Number Site Preparation, Installation, and Operator’s Manual, 167-405-035 167-405-035 Maintenance for the Avaya S8700 Media Server with an Avaya SCC1 Media Gateway or an Avaya MCC1 Media Gateway, 555-233-143 555-233-143 Avaya MultiVantage Solutions Installation and Maintenance for Survivable Remote EPN, 555-233-121 555-233-121 Installing the Avaya S8700 Media Server with the Avaya G600 Media Gateway, the Avaya MCC1 Media Ga
PAGE 21
Technical assistance Table 1: Additional document resources (continued) Document Number Job Aid: Repacking the S8500 Dual Network Interface, 555-245-760 555-245-760 Job Aid: Replacing the G700 Media Gateway, 555-245-752 555-245-752 3 of 3 Technical assistance Avaya provides the following resources for technical assistance.
PAGE 22
About this book Sending us comments Avaya welcomes your comments about this book. To reach us by: ● Mail, send your comments to: Avaya Inc. Product Documentation Group Room B3-H13 1300 W. 120th Avenue Westminster, CO 80234 USA ● E-mail, send your comments to: document@avaya.com ● Fax, send your comments to: 1-303-538-1741 Ensure that you mention the name and number of this book.
PAGE 23
Organization Organization Chapter 1: Server Alarms, contains information on alarms generated on various platforms, including the S8300, S8500, and S8700 media server. These alarms cover such categories as process watchdog, environmental, login, translation monitoring, and power supply alarms. Alarm identifications, levels, and resolutions are given. Chapter 2: Denial Events, contains information about denial events that are generated by Avaya Communication Manager.
PAGE 24
About this book Conventions used in this document Table 2: Typography used in this book on page 24 lists the typographic conventions in this document. Table 2: Typography used in this book To represent . . . This typeface and syntax are shown as . . .
PAGE 25
Conventions used in this document Table 2: Typography used in this book (continued) To represent . . . Web interface Keys This typeface and syntax are shown as . . . ● Bold for menu selections, tabs, buttons, and field names ● Right arrow > to separate a sequence of menu selections Special font for keyboard keys and SAT screen clickable buttons For example, . . . Select Alarms and Notification, the appropriate alarm, and then click Clear.
PAGE 26
About this book Useful terms Table 3: Terminology summary on page 26 summarizes some of the terms used in this book and relates them to former terminology.
PAGE 27
Chapter 1: Server Alarms S8700 | 8710 / S8500 / S8300 This chapter provides background information on server alarming. For detailed information on G700 Media Gateway Traps, refer to Chapter 4: G700 Media Gateway Traps. Introduction During normal operations, software or firmware may detect error conditions pertaining to specific Maintenance Objects (MOs) or other subsystems. The system automatically attempts either to fix or circumvent these problems.
PAGE 28
Server Alarms Note: For non-Communication Manager alarms, use the Web Page header "Alarms and Notification" and "Diagnostics: View System Log". Choose the appropriate heading and, if necessary, call Avaya support. Note: ● Media Server bash shell Provides alarms information related to Communication Manager, the media server, and messaging. ● Media Server SAT CLI Provides alarms information related to Communication Manager.
PAGE 29
Background Terms Background Terms Table 4: Alarming Background Terms on page 29 gives a useful explanation of terms. Table 4: Alarming Background Terms Term Explanation TRAP A trap is an event notification that is sent to the SNMP trap manager and received from the Media Gateway Processor, Layer 2 Switching Processor, or RTCP Monitor (Avaya VisAbility). ALARM Some traps are determined to be an alarm. If determined to be an alarm they are sent to an appropriate alarm management site, such as INADS.
PAGE 30
Server Alarms Alarm-Related LEDs Table 5: Alarm-Related LEDs on page 30 shows alarm-related LEDs on the faceplate of the G700 or on an attendant console, and shows how certain LEDs reflect specific alarm situations. Table 5: Alarm-Related LEDs LED Location Alarm-Related Cause ALARM LED Attendant Console The system alarm causes the attendant console ALARM LED to light. ACK LED Attendant Console The ACK LED on the attendant console reflects the state of acknowledgement of the alarm report from INADS.
PAGE 31
QOS Alarms QOS Alarms An RTCP monitor using the local SNMP agent generates traps to a pre-administered trap collector. The following QoS alarms are generated: ● The voip-callqos alarm is generated if a single session exceeds configured QOS levels. It can generate a warning or an SNMP trap. Warnings are used for less severe problems. They can be accumulated internally within Avaya VoIP Monitoring Manager for use by the alarms defined below.
PAGE 32
Server Alarms 2. Enable the modem from the media server Web Interface. In addition, use the Setup Modem Interface under the Configure Server pages. 3. With this modem, a client PC uses the Point-to-Point Protocol (PPP) to access the media server and connect via telnet to a Linux shell. 4. Once logged into the media server, you can telnet out to media gateways, such as the G700, and other devices on the network.
PAGE 33
Alarms in Linux Media Servers Media server alarms perform a similar role to Communication Manager alarms in a traditional telephony context.
PAGE 34
Server Alarms S8300 Alarming on the S8300 Functioning as a Local Survivable Processor The S8300 functioning as a Local Survivable Processor (LSP) logs an alarm when it becomes active. It also logs an alarm for every G700 Media Gateway that registers with it. It does NOT log alarms when IP phones register with it; rather, it logs a warning. Communication Manager Hardware Traps Table 6: Communication Manager Hardware Traps on page 34 illustrates hardware traps that apply to Communication Manager.
PAGE 35
Alarms in Linux Media Servers Backup and Restore Traps The S8300 uses the LAN to backup a copy of its translation data. Table 7: Backup and Restore Traps on page 35 illustrates the backup and restore traps. Table 7: Backup and Restore Traps Trap Description Successfully stored backup A trap of informational severity is sent when backup is successful. (REPLY_ACK) The trap reads “Successful backup of S8300 translation data,” and names the backup location stored in the string “BACKUP_LOCATION.
PAGE 36
Server Alarms Server-related alarms Server-related alarms and their troubleshooting procedures are described in the following tables: ● ARB (Arbiter) on page 37 ● DAJ1/DAL1 Alarms in S8700 Media Server on page 54 ● DUP (Duplication Manager) on page 56 ● ENV (Environment) on page 60 ● FSY (File Synchronization) on page 67 ● HDD (Hard Disk Drive) on page 69 ● KRN (Kernel) on page 73 ● Login Alarms on page 74 ● NIC (Network Interface Card) on page 75 ● RALM-SVC (Remote Alarm Service) on pag
PAGE 37
Alarms in Linux Media Servers ARB (Arbiter) S8700 | 8710 only The Arbiter process runs on S8700 Media Servers to: ● Decide which server is healthier and more able to be active ● Coordinate data shadowing between servers, under the Duplication Manager’s control At the physical and data-link layers, an Ethernet-based duplication link provides an inter-arbiter UDP communication path to: ● Enable this arbitration between the active and standby servers ● Provide the necessary status signaling for memory
PAGE 38
Server Alarms Table 8: ARB Alarms in Media Server on page 38 describes the Arbiter’s alarms and their troubleshooting procedures. See DUP (Duplication Manager) on page 56 for more information. Table 8: ARB Alarms in Media Server Event ID 3 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Interchange hand off failed” — Standby server could not process active server’s interchange request. The interchange does not occur, and the active side remains active. 1.
PAGE 39
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID 7 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Arbiter in invalid/unknown state” — Memory corruption or bad code/build 1. Verify that the server’s state is “Corrupt!”, either from the: - Web interface’s Server section, by selecting View Summary Status - Linux command line, by entering server 2.
PAGE 40
Server Alarms Table 8: ARB Alarms in Media Server (continued) Event ID 8 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Both servers thought they were active” 1. To verify this condition, either from the: - Web interface’s Server section, select View Summary Status - Linux command line, enter server 2. To distinguish the cause, examine the trace logs for Interarbiter messages with timestamps shortly before to shortly after the loss of heartbeat, either from the: - Web interface, by: a.
PAGE 41
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID 8 Alarm Level MIN (cont’d) Alarm Text, Cause/Description, Recommendation 3. A high-priority process caused the active Arbiter to hang for at least 4.5 seconds (causing an interchange). Then, the hang lifted, and each Arbiter realized that the other had assumed the active role. An automatic resolution process should leave the newly active server active, while the other server backs down to the standby role. a.
PAGE 42
Server Alarms Table 8: ARB Alarms in Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 9 WRN The following is a sample string pair generated by ARB Event #9. Within this sample, four pairs of digits in each string have special meaning, and are labeled “aa” through “dd.
PAGE 43
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 9 WRN Troubleshooting ARB Event #9 (cont’d) 1. compare the health of both servers, either from the: - Web interface’s Server section, by selecting View Summary Status - Linux command line, by entering server 2. Using the output from Step 1, check the health of each server’s individual processes. 3.
PAGE 44
Server Alarms Table 8: ARB Alarms in Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation After the interchange, the newly active server’s health should be significantly better (lower SOH value) than the standby server’s. If so, troubleshoot the standby server: If not: 1. Manually clear the alarm, either from the: - Web interface, by selecting Alarms and Notification, the appropriate alarm, and Clear - Linux command line, by entering almclear -n #id 2.
PAGE 45
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID Alarm Level 11 WRN (cont’d) Alarm Text, Cause/Description, Recommendation 2. Check for both the completeness and consistency of the servers’ hosts and servers.conf files (containing IP addresses of the system’s configured components), either from the: - Web interface, by selecting Configure Server - Linux command line, by entering: more /etc/hosts more /etc/opt/ecs/servers.conf 3.
PAGE 46
Server Alarms Table 8: ARB Alarms in Media Server (continued) Event ID 12 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Interchange without doing prep” — Since the Arbiter could not create a thread to request a file synchronization, some files did not get shadowed. 1. Examine the trace logs for the entry, Can't create interchange-prep thread, either from the: - Web interface by: a. Selecting the View System Logs diagnostic and Logmanager Debug trace b.
PAGE 47
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID 13 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Heartbeat timeout from ACTIVE” — When the timeout occurs, this alarm is only logged on the standby side.
PAGE 48
Server Alarms Table 8: ARB Alarms in Media Server (continued) Event ID 13 (cont’d) Alarm Level MIN Alarm Text, Cause/Description, Recommendation 2. From the Linux command line, enter start -a to restart the standby server. 3. Prevent any future misuse of the stop command. 4.
PAGE 49
Alarms in Linux Media Servers Table 8: ARB Alarms in Media Server (continued) Event ID 13 (cont’d) Alarm Level Alarm Text, Cause/Description, Recommendation MIN If the servers did not interchange, use the following procedure: 8. See if the standby server is busied-out, either from the: - Web interface, by selecting View Summary Status - Linux command line, by entering server 9.
PAGE 50
Server Alarms (Table 13: DAJ1/DAL1 Alarms in Media Server on page 54 describes the Duplication Memory board’s alarms and their troubleshooting procedures.) [See also, ARB (Arbiter) on page 37, DUP (Duplication Manager) on page 56, and NIC (Network Interface Card) on page 75.] Both periodic and on-demand testing is provided for this MO. The periodic test runs the Read Error Register test at 15-minute intervals. On-demand testing includes the Read Error Register and Local Loop tests.
PAGE 51
Alarms in Linux Media Servers Alarm Log Entries Table 10: DAJ1/DAL1 Alarm Log Entries EVENT ID# Associated Test Alarm Level On/Off Board Linux Test to Clear Value 2 (a) Read Error Register test (EDC single-bit errors) WRN ON testdupboard 3 (b) Read Error Register test (SDRAM multibit errors) MAJ ON testdupboard 4 (c) DAJ1/DAL1 Local Looparound test MIN ON testdupboard 5 (d) Read Error Register test (Link Receiver CRC errors) MIN ON testdupboard 6 (e) Read Error Register test (Link
PAGE 52
Server Alarms System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order shown in. By clearing error codes associated with the first test, you may clear errors generated from other tests in the sequence. Order of Investigation Short Test Sequence Long Test Sequence D/ND1 Read Error Register test X X D [DAJ1|DAL1] Board Local Loop test X X D 1.
PAGE 53
Alarms in Linux Media Servers Table 11: TEST Read Error Register Test Error Code Test Result Description / Recommendation Open failed to MDD ABRT The Memory Duplication Driver (MDD) is the system driver that communicates with the [DAJ1|DAL1] board. If this driver cannot be opened, then the [DAJ1|DAL1] board’s registers cannot be read. 1. This is a system type error, try again.
PAGE 54
Server Alarms Table 12: TEST DAJ1/DAL1 Local Loop Test Error Code Test Result Description / Recommendation Open failed to MDD ABRT The MDD is the system driver that communicates with the Duplication Memory board. If this driver cannot be opened, the board’s registers cannot be read. This is a system type error, try again. System Error MDD failed to return data ABRT The test ran, but for some reason the MDD could not return data. This is a system type error, try again.
PAGE 55
Alarms in Linux Media Servers Table 13: DAJ1/DAL1 Alarms in Media Server (continued) Event ID 3 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Multibit EDC Test (bad err register)” — Catastrophic multibit SDRAM error occurred. (Usually due to a hardware problem.) 1. Enter testdupboard on the Linux command line. 2. If the test fails, escalate this problem for explicit guidance with Steps 3 through 5. 3. Power-cycle the server. 4. Enter testdupboard again. 5.
PAGE 56
Server Alarms DUP (Duplication Manager) S8700 | 8710 only The Duplication Manager process, via coordination of the Arbiter process, runs on each S8700 Media Server to control data shadowing between them. At the physical and data-link layers, an Ethernet-based duplication link provides a TCP communication path between each server’s Duplication Manager to enable their control of data shadowing.
PAGE 57
Alarms in Linux Media Servers Table 14: DUP Alarms in Media Server Event ID 1 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Duplication card error” — Duplication Manager determined that the duplication card is not functioning, but it cannot distinguish between a bad card, an unplugged card, or a bad fiber link. 1. Check the physical fiber connectivity at each server. 2. Verify the alarm, by accessing the trace log, either from the: ● Web interface, by: a.
PAGE 58
Server Alarms Table 14: DUP Alarms in Media Server (continued) Event ID 1 Alarm Level MAJ (cont’d) Alarm Text, Cause/Description, Recommendation If not and at the customer’s convenience: Since the following commands cause a brief service outage, they should only be executed at the customer’s convenience. a. Force a server interchange to make the suspected server standby, either from the Linux command line, by entering server -if. b.
PAGE 59
Alarms in Linux Media Servers Table 14: DUP Alarms in Media Server (continued) Event ID 2 (cont’d) Alarm Level MAJ Alarm Text, Cause/Description, Recommendation 3. See if the dup link is “up”, either from the: - Web interface’s Server section, by selecting View Summary Status - Linux command line, by entering the server command 4.
PAGE 60
Server Alarms ENV (Environment) S8700 | 8710 / S8300 / S8500B The ENV MO monitors environmental variables within the server, including temperature, voltages, and fans. Table 15: ENV Alarms in Media Server on page 60 describes the ENV MO’s alarms and their troubleshooting procedures. Table 15: ENV Alarms in Media Server Event ID 1 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Temperature reached critical low” — Motherboard's temperature reached a critically low level. 1.
PAGE 61
Alarms in Linux Media Servers Table 15: ENV Alarms in Media Server (continued) Event ID 3 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Temperature reached warning high” — Motherboard's temperature reached a warning high. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 62
Server Alarms Table 15: ENV Alarms in Media Server (continued) Event ID 6 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “+3.3 voltage reached critical low” — Motherboard's nominal +3.3 voltage reached a critically low level. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 63
Alarms in Linux Media Servers Table 15: ENV Alarms in Media Server (continued) Event ID 12 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “+5 voltage reached critical high” — Motherboard's nominal +5 voltage reached a critically high level. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 64
Server Alarms Table 15: ENV Alarms in Media Server (continued) Event ID 18 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “-12 voltage reached critical low” — Motherboard's nominal -12 voltage reached a critically low level. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 65
Alarms in Linux Media Servers Table 15: ENV Alarms in Media Server (continued) Event ID 24 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “CPU core voltage reached critical high” — Motherboard's CPU core voltage reached a critically high level. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 66
Server Alarms Table 15: ENV Alarms in Media Server (continued) Event ID 29 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “All fan failure” — Every fan is running at a critically low speed. 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 67
Alarms in Linux Media Servers Table 15: ENV Alarms in Media Server (continued) Event ID 35 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ +2.5V under voltage. S8500B media server environment. S8500B 1. See if the alarmed condition is still present, either from the: - Web interface, by selecting the View Temperature/Voltage diagnostic - Linux command line, by entering environment 2.
PAGE 68
Server Alarms Table 16: FSY Alarm in Media Server on page 68 describes the FSY MO’s alarms and their troubleshooting procedures. Table 16: FSY Alarm in Media Server Event ID 1 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “File sync failed” — File synchronization operation failed. 1. See if the filesyncd (file sync daemon) process is up, either from the: - Web interface, by selecting View Process Status - Linux command line, by entering statapp 2.
PAGE 69
Alarms in Linux Media Servers HDD (Hard Disk Drive) The HDD MO monitors the hard drive via the Self Monitoring, Analysis, and Reporting Technology (S.M.A.R.T) capability that is built into the hard disk drive unit. The integrated controller for the hard disk drive works with sensors incorporated in the hard drive to monitor the drive’s performance. The SMART technology makes status information concerning the disk drive available to monitoring software.
PAGE 70
Server Alarms Table 17: HDD Alarm in Media Server (continued) Event ID 21 (cont’d) Alarm Level Alarm Text, Cause/Description, Recommendation Num Name Description 1 Raw Read Error Indicates the rate of hardware read errors that occur when reading data from the disk surface. This error is critical. An increasing error rate may indicate a failing disk drive. (Samsung, Seagate, IBM (Hitachi), Fujitsu, Maxtor, Western Digital) 2 Throughput Performance Overall throughput performance of the hard disk.
PAGE 71
Alarms in Linux Media Servers Table 17: HDD Alarm in Media Server (continued) Event ID 21 Alarm Level Alarm Text, Cause/Description, Recommendation 11 Recalibration Retries Number of times recalibration was requested after initial request. (Samsung, Seagate, IBM (Hitachi), Fujitsu, Maxtor, Western Digital) 12 Device Power Cycle Count Count of full hard disk power on/off cycles.
PAGE 72
Server Alarms Table 17: HDD Alarm in Media Server (continued) Event ID Alarm Level 21 Alarm Text, Cause/Description, Recommendation 199 UltraDMA CRC Error Count Count of Cyclic Redundancy Check (CRC) errors during UltraDMA mode (Samsung, Seagate, IBM (Hitachi), Fujitsu - select models, Maxtor, Western Digital - select models) 200 Write Error Rate (Multi Zone Error Rate Total number of errors found when writing a sector.
PAGE 73
Alarms in Linux Media Servers KRN (Kernel) S8700 | 8710 The KRN MO monitors the operating system Kernel. Table 18: KRN Alarm in Media Server on page 73 describes the MO’s alarms and their troubleshooting procedures. Table 18: KRN Alarm in Media Server Event ID 10 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ Failure in a Synchronous Dynamic Random Access Memory (SDRAM) Dual Inline Memory Module (DIMM).
PAGE 74
Server Alarms Login Alarms The Login MO monitors access to the server and alarms suspicious activity. Table 19: Login Alarms in Media Server on page 74 describes the Login MO’s alarms and their troubleshooting procedures. Table 19: Login Alarms in Media Server Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 2 WRN “sat_Auth:Login for [inads] invalid password” — An SAT login to Communication Manager failed. 1.
PAGE 75
Alarms in Linux Media Servers NIC (Network Interface Card) S8700 | 8710 / S8500 This MO supports the NICs in each S8700 media server providing the physical and data-link interfaces for Ethernet-based links. Table 20: NIC Alarms in Media Server on page 75 describes NIC’s alarms and their troubleshooting procedures. See DAJ1/DAL1 (Duplication Memory Board) on page 49 for more information.
PAGE 76
Server Alarms Table 20: NIC Alarms in Media Server (continued) Event ID 2 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “eth1 NIC Link is Down” — Ethernet link on native NIC 1 is down. 1. Verify Ethernet connectivity, either from the: - Web interface, by selecting the Execute Pingall diagnostic - Linux command line, by entering pingall -a Check both sides of each failed link, and make any necessary repairs. 2.
PAGE 77
Alarms in Linux Media Servers Alarm Log Entries These tests verify that the standby media server’s components are operating correctly. Table 21: RALM-SVC Alarm Log Entries EVENT ID# Aux Data Associated Test Alarm Level On/Off Board Linux Test to Clear Value 1 (1) SME_ARB test MAJOR ON testdupboard 2 (2) Standby_PN Check test MAJOR ON testdupboard Notes: 1.
PAGE 78
Server Alarms SME Alarm in S8700 Media Server Table 22: SME Alarm in Media Server on page 78 describes the SME alarm (for RALM-SVC (Remote Alarm Service) and its troubleshooting procedures.
PAGE 79
Alarms in Linux Media Servers SVC_MON (Service Monitor) S8700 | 8710 / S8500 SVC_MON is a media server process, started by Watchdog, to monitor Linux services and daemons. It also starts up threads to communicate with a hardware-sanity device. Table 23: SVC_MON Alarms in Media Server on page 80 describes the SVC_MON MO’s alarms and their troubleshooting procedures. For information about Watchdog, see _WD (Watchdog) Alarms on page 99.
PAGE 80
Server Alarms Table 23: SVC_MON Alarms in Media Server Event Alarm ID Level 1 MIN Alarm Text, Cause/Description, Recommendation “service atd could not be restarted” — The Linux at daemon is down. Scheduled services such as session cleanup or daily filesync will not work. 1. From the /sbin directory type service atd restart to restart the at daemon. 2.
PAGE 81
Alarms in Linux Media Servers Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 2 MIN Alarm Text, Cause/Description, Recommendation “service crond could not be restarted” — The Linux cron daemon is down. Periodic services such as session cleanup or daily filesync will not work. 1. Enter /sbin/service cron restart to restart the cron daemon. 2.
PAGE 82
Server Alarms Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 3 MIN Alarm Text, Cause/Description, Recommendation “service inet could not be restarted” — The Linux internet server daemon is down. Networking services will not work. 1. Enter /sbin/service inet restart to restart the inet daemon. 2.
PAGE 83
Alarms in Linux Media Servers Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 4 MIN Alarm Text, Cause/Description, Recommendation “service syslog could not be restarted” — Linux “syslog” service is down. Event logging to syslog and alarm generation will fail. 1. Enter /sbin/service syslog restart to restart the syslog service. 2.
PAGE 84
Server Alarms Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 5 MIN Alarm Text, Cause/Description, Recommendation “service xntpd could not be restarted” — The Linux network time protocol daemon is down. The server’s clock and recently logged time stamps may be inaccurate. 1. Enter /sbin/service xntpd restart to restart the xntpd daemon. 2.
PAGE 85
Alarms in Linux Media Servers Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 6 MIN Alarm Text, Cause/Description, Recommendation “service dbgserv could not be restarted” — Debug server is down, and Gemini debugger may not work. Although losing this service does not affect operations, the debugging of a running system is prevented. 1. Enter /sbin/service dbgserv restart to restart the dbgserv service. 2.
PAGE 86
Server Alarms Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 7 MIN Alarm Text, Cause/Description, Recommendation “service prune could not be restarted” — The prune service is not running. The hard disk’s partition usage is not being monitored or cleaned. 1. Enter /sbin/service prune restart to restart the prune service. 2.
PAGE 87
Alarms in Linux Media Servers Table 23: SVC_MON Alarms in Media Server (continued) Event Alarm ID Level 8 MIN Alarm Text, Cause/Description, Recommendation “service httpd could not be restarted” — The hypertext transfer protocol daemon is down. The Web interface will not work. 1. Enter /sbin/service httpd restart to restart the http daemon. 2.
PAGE 88
Server Alarms _TM (Translation Manager) S8700 | 8710 / S8500 / S8300 The _TM MO is an S8700 Media Server that monitors the server’s ability to read Communication Manager translations. Table 24: TM Alarm in Media Server on page 88 describes the _TM MO’s alarm and its troubleshooting procedures. Table 24: TM Alarm in Media Server Event ID 1 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Cannot read translations” — Server could not read translations.
PAGE 89
Alarms in Linux Media Servers UPS (Uninterruptible Power Supply) S8700 | 8710 / S8500 / S8300 The UPS MO supports the UPS device for each media server. This MO’s maintenance software reacts to UPS-generated in-line errors via SNMP traps. Note: Note: This MO provides no periodic or on-demand tests. UPS Traps to Media Server Table 25: Enterprise-Specific UPS Traps to Server on page 89 contains the various UPS-generated SNMP traps to the media server.
PAGE 90
Server Alarms Table 25: Enterprise-Specific UPS Traps to Server (continued) SNMP Trap from UPS Event ID Definition of Trap Trap (1) #8 (1–8) Alarm string = #1, ACT, UPS, A, 8, MAJ, power failure: Shutting down in 8 minutes. The UPS battery’s power is in a critically low condition, with an estimated 8 minutes of remaining holdover. ● A warning is written to every logged-in user of the server. ● When 8 minutes elapse, the server begins shutting down.
PAGE 91
Alarms in Linux Media Servers Table 25: Enterprise-Specific UPS Traps to Server (continued) SNMP Trap from UPS Event ID Definition of Trap Trap (3) upsAlarmCommunicatio nsLost #18 Alarm string = #1,ACT,UPS,A,18,WRN,Miscellaneous trap, e.g., bad battery (For troubleshooting procedures, see Event #18 on page 93) Trap (3) upsAlarmBypassBad #19 Alarm string = #1,ACT,UPS,A,19,WRN,Miscellaneous trap, e.g.
PAGE 92
Server Alarms Table 25: Enterprise-Specific UPS Traps to Server (continued) SNMP Trap from UPS Event ID Definition of Trap Trap (3) – upsAlarmGeneralFault #27 #1,ACT,UPS,A,27,WRN,Miscellaneous trap, e.g., bad battery (For troubleshooting procedures, see Event #27 on page 95) 4 of 4 1. These events will degrade the server’s state of health. System Technician-Demanded Tests: Descriptions and Error Codes This MO provides no on-demand tests for system technicians.
PAGE 93
Alarms in Linux Media Servers Table 26: UPS Alarms to the Media Server (continued) Event ID 14 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “upsAlarmDepletedBattery” — If primary power is lost, the UPS could not sustain the current load. 1. Charge or replace the batteries in the UPS, according to procedures in its Site Preparation, Installation, and Operator’s Manual, 167-405-035. 15 MAJ “upsAlarmBatteryBad” — One or more batteries needs to be replaced. 1.
PAGE 94
Server Alarms Table 26: UPS Alarms to the Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 19 WRN “upsAlarmBypassBad” — The “source” power to the UPS, which (during a UPS overload or failure) also serves as “bypass” power to the load, is out of tolerance — incorrect voltage by > ±12% or frequency > ±3%. This on-line UPS normally regenerates its source power into clean AC power for the load.
PAGE 95
Alarms in Linux Media Servers Table 26: UPS Alarms to the Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 26 WRN “upsAlarmFuseFailure” — One or more UPS fuses have failed. 1. Replace the UPS, and diagnose it later. 27 WRN “upsAlarmGeneralFault” — A general fault occurred in the UPS. (A UPS diagnosis is required.) 1. Replace the UPS, and diagnose it later. 4 of 4 This MO provides periodic and on-demand testing.
PAGE 96
Server Alarms -t arg Specific test to perform. Possible values for arg are: reset_usb | handshake | off-hook | -? Usage (this). Alarm Log Entries Table 27: USB1 Alarm Log Entries EVENT ID# Aux Data Associated Test Alarm Level On/ Off Board Linux Test to Clear Value 1 (1) Handshake test MIN ON testdupboard 2 (2) Modem Off-Hook test MAJ ON testdupboard Notes: 1.
PAGE 97
Alarms in Linux Media Servers Handshake Test This test is destructive. This test verifies that modem’s hardware is attached and that the modem can “handshake” with the USB port. The test: 1. Tries to open the device 2. Sends a handshake string (ATZ) to the modem The modem should return an “OK” string.
PAGE 98
Server Alarms This test runs an off-hook 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. The following errors can be detected: Table 29: TEST Off-Hook Test Error Code Test Result Description / Recommendation Modem in use, try again later ABRT Some other application is currently using the modem. Try again later. Could not open USB port ABRT System error: An attempt to open the USB device failed.
PAGE 99
Alarms in Linux Media Servers _WD (Watchdog) Alarms S8700 | 8710 / S8500 / S8300 The Watchdog MO is a media server process that: ● Creates other Communication Manager processes ● Monitors their sanity ● Can recover their failures These applications come up and start heartbeats to the Watchdog. For more information about Watchdog, see Table 31: _WD Alarms in Media Server on page 100 that describes the _WD MO’s alarms and their troubleshooting procedures.
PAGE 100
Server Alarms Table 31: _WD Alarms in Media Server Event ID 4 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Application (pid) TOTALLY FAILED” — An application is present, but not launching. The application could not start the maximum allowed number of times. (This alarm usually occurs with Event ID #20.) 1.
PAGE 101
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID Alarm Level 4 (cont’d) MAJ Alarm Text, Cause/Description, Recommendation 5. If so (less common): a. Enter ls -l on the symbolic link’s address. b. Verify that the executable has “execution” permissions. c. If not, enter chmod +x to enable execution of the application. If not — Linux has returned a “null link” (more common): - Acquire the executable from the CD. 6. Enter start -s application to start the application.
PAGE 102
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID 5 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “WARNING: timeout waiting for reqsvr to initialize” — During each server’s boot process, the server’s Watchd process waits up to 2 minutes for its “reqsvr” (request server) thread to initialize. If the 2-minute waiting interval elapses, this server logs this alarm, and its boot process hangs.
PAGE 103
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID Alarm Level 5 (cont’d) MIN 6 MAJ S8300 Alarm Text, Cause/Description, Recommendation 6. If rebooting the server does not help or if the problem recurs, escalate the problem to the next higher tier. “Application (pid) not started, config parm errors” — Watchdog cannot read its configuration file, /etc/opt/ecs/watchd.conf. 1.
PAGE 104
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID 7 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Application not started, parm file errors” — Since an application’s specified location in watchd.conf is incorrect, Watchdog cannot start the application. 1.
PAGE 105
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID 13 (Except S8500) Alarm Level Alarm Text, Cause/Description, Recommendation MIN “ERROR: could not dup socket fd in reqsvr.c, heartbeat thread not created, errno=” — As either a: ● Booting application initiates ● Restarting application re-initiates heart beating with Watchdog (see Event ID #5), the “reqsvr” (request server) thread tries to create a duplicate socket for the hearbeating thread.
PAGE 106
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID 13 (Except S8500) (cont’d) Alarm Level MIN Alarm Text, Cause/Description, Recommendation 4. Reboot the standby server, either from the: - Web interface, by selecting Shutdown This Server - Linux command line, by entering /sbin/shutdown -r now 5. If rebooting the server does not help or if the problem recurs, escalate the problem to the next higher tier. 14 (Except S8500) MIN “ERROR in req2svr.
PAGE 107
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID 15 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Detected a rolling reboot” — Watchdog has detected “x” number of Linux reboots within “y” minutes (where x and y are configurable in /etc/opt/ ecs/watchd.conf). Rolling reboots have a wide variety of possible causes. 1.
PAGE 108
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 18 WRN “Application restarted. Retry , New Pid: ” — An application has failed, and Watchdog successfully restarted it. S8300 1.
PAGE 109
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID 19 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MIN “Application failed unintentionally” — Watchdog is bringing the system down because an application failed to start correctly. The application may have failed to start either because: ● The file did not exist (coincident with Event ID #7). ● Required application parameters were missing or invalid in watchd.conf. 1.
PAGE 110
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID 20 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Application (pid) TOTALLY FAILED” — Application failed the maximum allowed number of times. (This alarm usually occurs with Event ID #4.) 1.
PAGE 111
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID 20 (cont’d) Alarm Level MAJ Alarm Text, Cause/Description, Recommendation 5. If so (less common): a. Enter ls -l on the symbolic link’s address. b. Verify that the executable has “execution” permissions. c. If not, enter chmod +x to enable execution of the application. If not — Linux has returned a “null link” (more common): - Acquire the executable from the CD 6. Enter start -s application to start the application.
PAGE 112
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID Alarm Level Alarm Text, Cause/Description, Recommendation 22 WRN “Application () terminated” — Watchdog successfully shut down the named application, and (if appropriate) watchdog will try to restart it. S8300 1.
PAGE 113
Alarms in Linux Media Servers Table 31: _WD Alarms in Media Server (continued) Event ID Alarm Level 22 WRN S8300 Alarm Text, Cause/Description, Recommendation 5. Manually clear the alarm, either from the: - Web interface, by selecting Alarms and Notification, the appropriate alarm, and Clear (cont’d) - Linux command line, by entering almclear -n #id 6. Watch to see if the alarm recurs. If so, escalate the problem. 23 S8300 MAJ “Watchd high-monitor thread is rebooting the system” — The: 1.
PAGE 114
Server Alarms Table 31: _WD Alarms in Media Server (continued) Event ID 24 S8300 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ “Watchd’s high-monitor thread is stopping tickling of hw” — Event ID #23’s call to reboot the server was unsuccessfully invoked. (A Linux kernel’s semaphore is possibly stuck.) After this happens, Watchd stops tickling the HW sanity timer so that the HW sanity watchdog executes a hard reboot of the processor. 1.
PAGE 115
Alarms in Linux Media Servers Login Alarms - S8300 S8300 Table 32: Login Alarms in Media Server on page 115 describes media server login alarms and their troubleshooting procedures. Table 32: Login Alarms in Media Server Event ID Alarm Level 1 WRN Alarm Text, Cause/Description, Recommendation 1. On the Web Interface, choose View Current Alarms. 2. Notify Customer. 2 WRN 1. On the Web Interface, choose View Current Alarms. 2. Notify Customer. 3 MIN Security violation. 1.
PAGE 116
Server Alarms Virtual Alarms S8300 only The Virtual Announcement Media Module faults are managed as server alarms. In the S8300 Media Server, the Virtual Analog Angel (VAA) represents a messaging board. The VAA is a virtual board on the G700. When the G700 reboots, the VAA senses that it has lost connectivity with the G700, and triggers its "removal and re-insertion". The removal of the VAA causes the AUDIX ports to go out-of-service and to return back in service when the re-insertion is complete.
PAGE 117
Alarms in Linux Media Servers Note: The S8500 has a set of alarms for the RSA card, which is also called the Remote Maintenance Board (RMB). The MO name is RMB. Alarms reported, by the S8500 media server, via the MO name RMB will include a Product ID beginning with one (1) followed by nine digits. The A+SAMP board in a S8500B media server may also report alarms via the MO name RMB. See S8500B Augmentix Server Availability Management Processor™ (A+SAMP) Alarms on page 120.
PAGE 118
Server Alarms Table 34: RMB Alarms in the S8500 Media Server (continued) Event ID 3 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ "RMB reset command failed" - The RSA card did not respond to a reset command.
PAGE 119
Alarms in Linux Media Servers Table 34: RMB Alarms in the S8500 Media Server (continued) Event ID 4 Alarm Level Alarm Text, Cause/Description, Recommendation MAJ "RMB failed handshake test" - The RSA card did not respond to commands from the server.
PAGE 120
Server Alarms S8500B Augmentix Server Availability Management Processor™ (A+SAMP) Alarms S8500B Only The Augmentix Server Availability Management Processor (A+SAMP) board is installed in the S8500B media server. It monitors and reports alarms on S8500B components and software and provides control to power on and power off the server. The A+SAMP will report alarms when it detects certain failure conditions. See A+SAMP Alarms in the S8500B Media Server on page 120.
PAGE 121
S8710 Alarms S8710 Alarms S8710 environmental alarms The Environmental maintenance object (ENV-MO) monitors environmental variables within the server, including temperature and fans. However, you can check these variables from the Maintenance Web Pages also. To check the S8710 server temperature and voltage readings: 1. At the Maintenance Web Pages, select Diagnostics > Temperature/Voltage. 2. The Temperature/Voltage page displays.
PAGE 122
Server Alarms 3. Use the descriptions in Table 36 to interpret the report. Table 36: S8710 Temperature and voltage report Field Description ID An identification number automatically generated by the system. Type Power supply: ● Intelligent—power regulating ● Standard—other Fan: speeds include ● Var Speed—variable speed ● Basic Fan—fixed speed ● Auto.
PAGE 123
S8710 Alarms Table 36: S8710 Temperature and voltage report (continued) Field Description Threshold Temperature: above for which an alarm is generated, in degrees Fahrenheit and Celsius. 2 of 2 S8710 server BIOS error messages The S8710 server BIOS error messages are listed and interpreted in Table 37.
PAGE 124
Server Alarms 124 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 125
Chapter 2: Denial Events The tables in this chapter define and explain the information listed on the Events Report (display events screen). The Event Type tables are grouped by denial event category, denial event number, and Communication Manager release number. The Event Tables list: ● The number that identifies the Event Type. See Table 38: Denial Event types and ranges on page 126.
PAGE 126
Denial Events Event Type number ranges Event Type number ranges help define the type and source of the denial event, as listed in Table 38: Denial Event types and ranges. Some numbers are placeholders and have no assigned denial event. Table 38: Denial Event types and ranges Number range Type/source of denial event Reference 0 - 999 Vector process Avaya Communication Manager Call Center Software Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300186.
PAGE 127
Event Data Table 38: Denial Event types and ranges (continued) Number range Type/source of denial event Reference 3400 - 3499 Data Error (corruption) process Table 60: Data Error denial events (3400 - 3499) on page 252. 3500 - 3599 Contact Closure process Table 61: Contact Closure denial events (3500 - 3503) on page 253. 3600 - 3604 ESS process Table 62: ESS denial events (3600 - 3604) on page 254.
PAGE 128
Denial Events Cause Values and their meanings/interpretations See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic Code) in Event Data 2 fields. Event Data 2 sometimes contains data that represents the Cause Value (CV) (required), Cause Value Diagnostic (DIAG) (optional), Location Code (LC) (optional) from the denial event.
PAGE 129
Event Data 2. Convert the hexadecimal number provided in Event Data 2 to three binary numbers: put a one in the appropriate binary number positions that add up to the value of the number. Each binary number consists of eight bits. See Table 40: Event Data 2 conversion example on page 129 for an example of the hexadecimal number 0x429, and Table 41: Hexadecimal, decimal, and binary equivalents on page 130 for the binary equivalents for individual digits. 3.
PAGE 130
Denial Events .
PAGE 131
Event Data Table 42: Location Code definitions (continued) Location Code Definition 5 Private Network Serving Remote User (the remote PBX or phone system on the Called Party premises). 7 International. A Network beyond inter-networking point. 2 of 2 Transmission Protocols See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic Code) in Event Data 2 fields.
PAGE 132
Denial Events Table 43: Country Codes and Transmission Protocols (continued) Country Protocol Supported B-channel Maint.
PAGE 133
Event Data Table 43: Country Codes and Transmission Protocols (continued) Country Protocol Supported B-channel Maint. Message Inter-working Message 21 Macedonia ETS 300 102 RESTART PROGRESS 22 Poland ETS 300 102 RESTART PROGRESS 23 Brazil ETS 300 102 RESTART PROGRESS ETSI-a Europe, etc.
PAGE 134
Denial Events Table 44: Cause Value Classes and Ranges (continued) Number range Cause Value Class 65 to 79 Service or Option not Implemented Class Cause Values on page 158 ● 67, 68, 71-78, 80 81 to 95 ● 92-94 96 to127 ● 104-109, 116-126 unassigned Invalid Message Class Cause Values on page 161 unassigned Protocol Error Class Cause Values on page 165 unassigned 2 of 2 Cause Values Normal Class Cause Values Cause Value (empty) []Normal call clearing (1TR6: AT&T ISDN Protocol) The call was disconne
PAGE 135
Event Data See also Cause Value 22 on page 143 and Cause Value 56 on page 154. Troubleshooting ● Check the numbers sent to see if any prefixes or service values that were needed to access the network were not sent. ● Check the Cause Value Information Element (LOC). See Location Codes on page 130. ● Check Communication Manager administration. - Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code conversion.
PAGE 136
Denial Events Troubleshooting ● Check the diagnostic information (DIAG) for the transit network identity of the unreachable network. See Cause Values and their meanings/interpretations on page 128. ● Check the numbers sent for any missing prefixes or service values that were needed to access the network. ● Check that the call type (data, voice, fax) can be routed between the ISDN networks serving both ends of the call.
PAGE 137
Event Data - IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan, causing incorrect IXC manipulation. - AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is being routed into the wrong network and over the wrong route pattern. Further conversion is needed but the dial string is restricted from further conversion.
PAGE 138
Denial Events - AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the wrong type of number and/or number plan information, or it is preventing code conversion from taking place. Call is being routed to the incorrect route pattern where the incorrect digit manipulation and/or code conversion is taking place. An incorrect service or feature is specified for the call being made on a CBC trunk group preference. Changing the Number format to a format incorrect for the call type.
PAGE 139
Event Data - AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the wrong type of number and/or number plan information, or it is preventing code conversion from taking place. An incorrect service or feature is specified for the call being made on a CBC trunk group preference. Changing the Number format to a format incorrect for the call type.
PAGE 140
Denial Events Troubleshooting Wait and try the call again later. Cause Value 09 [0x9/0x89] Preemption, circuit reserved for reuse/ Prefix 1 dialed in error (NI-2: National ISDN 2) Cause Value 09 For Autovon switching networks, the call attempt was blocked by a call with a higher priority reserving the requested channel for reuse. Cause Value 09 (NI-2) indicates that the network does not want to receive the prefix digit 1 as part of the digit string in the CALLED PARTY NUMBER.
PAGE 141
Event Data Cause Value 16 [0x10/0x90] Normal call clearing/ Requested facility not implemented (1TR6: AT&T ISDN Protocol) Cause Value 16 indicates that the call was disconnected normally by either end hanging up. Cause Value 16 (1TR6) indicates that the call could not be completed because the equipment sending this Cause Value does not support the requested service, feature, or supplementary service in the SETUP message.
PAGE 142
Denial Events ● Check the Cause Value Information Element (LOC). - If the location information of the Cause Value is 4, “public network serving the remote user”, the trunk group to the remote endpoint location might be experiencing an “all trunks busy” condition or not enough channels allocated into a virtual group for the particular NSF of the call. - If the location information of the Cause Value is 0, “user”, the endpoint might be busy.
PAGE 143
Event Data Cause Value 19 [0x13/0x93] User alerting no answer The remote device returned an alerting [ringing] indication but did not provide a connect indication within the period of time prescribed by timer T301. Communication Manager never originates this Cause Value. Troubleshooting Wait and retry the call later. Cause Value 20 [0x14/0x94] Subscriber absent [wireless networks] The mobile remote device/endpoint is not available. Troubleshooting Wait and try the call again later.
PAGE 144
Denial Events Cause Value 23 [0x17/0x97] Redirection to new destination The call has been redirected to a different endpoint. Communication Manager does not originate Cause Value 23. Cause Value 25 [0x19/0x99] Exchange routing error The call cannot be routed to the remote party. Cause Value 26 [0x1A/0x9A] Non-selected user clearing The call was cleared before the called endpoint was awarded the incoming call.
PAGE 145
Event Data Troubleshooting ● Check the Cause Value Information Element (LOC). See Location Codes on page 130. ● Check Communication Manager administration (network generated the Cause Value). - Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code conversion. - IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan, causing incorrect IXC manipulation. - AAR/ARS digit conversion: The wrong digit string substitution is being made.
PAGE 146
Denial Events Troubleshooting ● Check the diagnostic information (DIAG) for the facility identifier of the service that was rejected. See Cause Values and their meanings/interpretations on page 128. ● Check Communication Manager administration (network generated the Cause Value). - Route pattern: The service or feature field contains an incorrect value for this route preference. The ITC/BCIE fields might not indicate the correct information for a data call.
PAGE 147
Event Data Cause Value 32 [0x20/0xA0] Outgoing calls barred (1TR6: AT&T ISDN Protocol) The call could not be completed because the calling user does not have permission to make an outgoing call. This Cause Value has local significance only.
PAGE 148
Denial Events Troubleshooting ● Check Communication Manager administration (network generated the Cause Value). - B-channels might be assigned off a T1/E1 into a trunk group that are not available for service from the remote end. Contact the ISDN service provider to find out which B-channels can be used. ● Check administration that might cause Communication Manager to generate this Cause Value.
PAGE 149
Event Data Cause Value 40 [0x28/0xA8] Permanent frame mode connection is operational This appears to be a Q.933 frame relay Cause Value. A frame relay PVC that was terminated has been restored to service. Not applicable to a Communication Manager system. Cause Value 41 [0x29/0xA9] Temporary Failure The call was not completed because the ISDN network is not functioning correctly. The condition is not likely to last a long period of time. If the user attempts the call again it will probably complete.
PAGE 150
Denial Events This Cause Value is usually delivered in a STATUS message. Communication Manager generates this Cause Value when: ● A tandem call inter-works from ISDN to non-ISDN trunking. ● Calling number and/or calling name information is sent in the SETUP message when it is not needed. ● Connected number information is sent when the network does not support it. This Cause Value has end-to-end significance and should always be passed back through the network to the user.
PAGE 151
Event Data Cause Value 45 [0x2D/0xAD] Pre-empted The call could not be completed because the equipment sending this Cause Value does not have the requested B-channel in a maintenance state that allows for call requests to be processed. Communication Manager does not support this Cause Value. Cause Value 46 [0x2E/0xAE] Precedence call Blocked For Autovon switching networks, the call could not complete because the remote endpoint is busy with a call that has a higher priority.
PAGE 152
Denial Events Cause Value 50 [0x32/0xB2] Requested facility not subscribed The call could not be completed because the user has not subscribed to the service, feature, or supplementary service requested in the SETUP message. If the user is supposed to have access to this service, feature, or supplementary service, then complete the required ordering process with the ISDN service provider. This Cause Value has end-to-end significance and should always be passed back through the network to the user.
PAGE 153
Event Data Cause Value 52 [0x34/0xB4] Outgoing calls barred The call could not be completed because the network screened the call, and the calling user is not permitted to make an outgoing call. This Cause Value has local significance only.
PAGE 154
Denial Events Cause Value 56 [0x38/0xB8] Number changed (1TR6: AT&T ISDN Protocol) The called party number indicated has been changed to a new number that might be sent in the diagnostic information (DIAG) for this Cause Value. See Cause Values and their meanings/ interpretations on page 128. If this Cause Value is not supported by the ISDN network, Cause Value 01 is used instead. This Cause Value has end-to-end significance and should always be passed back through the network to the user.
PAGE 155
Event Data - A call tandeming through Communication Manager on a non-ISDN trunk group inter-working to an ISDN trunk group might have an incorrect bearer capability assigned on the incoming trunk group. The BC and ITC fields on the incoming trunk group might be set wrong. Cause Value 58 [0x3A/0xBA] Bearer capability not presently available/ No user responding (1TR6: AT&T ISDN Protocol) This Cause Value has end-to-end significance and should always be passed back through the network to the user.
PAGE 156
Denial Events Cause Value 59 [0x3B/0xBB] User busy (1TR6: AT&T ISDN Protocol) The endpoint called has indicated an inability to accept another call. This Cause Value has end-to-end significance and should always be passed back through the network to the user. Troubleshooting ● Wait and try the call again later. ● Check the Cause Value Information Element (LOC) - If the Location Information of the Cause Value is 0 (User), the endpoint is probably busy.
PAGE 157
Event Data This Cause Value has end-to-end significance and should always be passed back through the network to the user. Troubleshooting ● Check Communication Manager administration (network generated the Cause Value).
PAGE 158
Denial Events Service or Option not Implemented Class Cause Values Cause Value 65 [0x41/0xC1] Bearer capability not implemented The call could not be completed because the equipment sending this Cause Value does not support the bearer capability requested in the SETUP message. This Cause Value has end-to-end significance and should always be passed back through the network to the user.
PAGE 159
Event Data Cause Value 69 [0x45/0xC5] Requested facility not implemented The call could not be completed because the equipment sending this Cause Value does not support the requested service, feature, or supplementary service in the SETUP message. This Cause Value has end-to-end significance and should always be passed back through the network to the user. Communication Manager does not originate this Cause Value for PRI.
PAGE 160
Denial Events Cause Value 70 [0x46/0xC6] Only restricted digital information bearer capability is available The call could not be completed because the equipment sending this Cause Value only supports the restricted version of the requested bearer capability, and in the SETUP message bearer capability was unrestricted. Communication Manager does not originate Cause Value 70. Troubleshooting ● Check Communication Manager administration (network generated the Cause Value).
PAGE 161
Event Data Invalid Message Class Cause Values Cause Value 81 [0x51/0xD1] Invalid call reference value The equipment sending this Cause Value received a message with a call reference value that is not currently in use on this user-network (D-channel) interface. This could indicate a call state mismatch for the attempted connection between the two sides of the interface.
PAGE 162
Denial Events ● Communication Manager administration that can affect sending this Cause Value: - Communication Manager might have missed assigning some B-channels into a trunk group that the remote believes can be used for service and is attempting to request a call on one. Check which channel is being requested and if possible assign it into the appropriate trunk group.
PAGE 163
Event Data Cause Value 87 [0x57/0xD7] User not a member of the Closed User Group [CUG] The packet mode call was rejected because the user is not a member of the remote end’s Closed User Group (CUG), which is a feature associated with packet mode calls similar to X.25 connection made over the ISDN D-channel. Communication Manager does not support packet mode sessions on D-channels, therefore this is not applicable to Communication Manager.
PAGE 164
Denial Events - A data call attempt tandeming through Communication Manager ISDN trunk group to ISDN trunk group the outgoing route pattern has the Bearer Capability Class (BCC) required for making this call set to “NO” and/or the ITC and BCIE are not compatible with the incoming bearer capability. - A TSC setup attempt that is tandeming through Communication Manager, the outgoing route pattern does not have the TSC bearer capability activated.
PAGE 165
Event Data Troubleshooting ● Check Communication Manager administration (network generated the Cause Value). - Communication Manager sent the transit network identification in the NSF IE when the network expected it to be in the TNS IE. The protocol version on the DS1 form does not match the near-end ISDN network that is terminating the D-channel. Contact the ISDN network service provider and try to line up the protocols being used.
PAGE 166
Denial Events Troubleshooting ● Check that the protocols at each end of the interface match (for example, both sides are AT&T Custom or both sides are NI-2). If the ends of the interface are running different protocols, they might be running with different Information Element encoding. ● Check the diagnostic information (DIAG) for the IE identifier of the missing information. See Cause Values and their meanings/interpretations on page 128. Communication Manager generates diagnostic information.
PAGE 167
Event Data Table 45: Cause Value 96 & 100 Diagnostic Information (continued) Missing IE Identifier Information Element 20 NETWORK SPECIFIC FACILITIES 27 NOTIFICATION INDICATOR 28 DISPLAY 34 SIGNAL 70 CALLED PARTY NUMBER 71 CALLED PARTY SUB-ADDRESS 74 REDIRECTING NUMBER 79 RESTART INDICATOR 78 TRANSIT NETWORK SELECTION Code-set 6 7B LOOK AHEAD INTERFLOW 08 TRAVELING CLASS MARK 28 DISPLAY 55 Distributed Communication System (DCS) 56 Distributed Communication System (DCS) AUDIX 5
PAGE 168
Denial Events This Cause Value has local significance only. The ISDN network between the user and the equipment generating the Cause Value might: ● Send no cause indication through the network ● Send a more generic Cause Value through the network Troubleshooting ● Check that the protocols at each end of the interface match (for example, both sides are AT&T Custom or both sides are NI-2).
PAGE 169
Event Data Table 46: Cause Value 97, 98, 101 Diagnostic Information (continued) Message Type Identifier Message 72 FACILITY REJECT 75 STATUS ENQUIRY 79 CONGESTION CONTROL Maintenance Message 0F SERVICE 07 SERVICE ACKNOWLEDGE 2 of 2 Cause Value 98 [0x62/0xE2] Message type, not compatible with call state, or non-existent, or not implemented The equipment that sent this Cause Value received a message, and the procedures in the protocol specification indicate that this is not a permissible message
PAGE 170
Denial Events Problems have been revealed with the state machine implementations of some of the CO switches for different protocols, and the state machine problems in the CO switches are most likely not going to be corrected. Communication Manager has not shown any problems with its state machine implementations for the different protocols. Change Communication Manager administration to change the message sequence of the call scenario causing the error, and help solve state machine implementation problems.
PAGE 171
Event Data This Cause Value has local significance only. The ISDN network between the user and the equipment generating the Cause Value might: ● Send no cause indication through the network ● Send a more generic Cause Value through the network Troubleshooting ● Check that the protocols at each end of the interface match (for example, both sides are AT&T Custom or both sides are NI-2).
PAGE 172
Denial Events ● Call state problems are reported with STATUS messages. The equipment sending the Cause Value uses the CALL STATE IE of the STATUS message to indicate the call state. To determine the call state of the other end of the interface, run the message sequence of the call through the SDL flow charts of the appropriate side (user or network) and the appropriate protocol (TR41449/41459, TR1268, A211 etc.).
PAGE 173
Event Data Table 47: Cause Value 102, Signaling Group Error Type 1, Aux Data information Aux Data Value Timer Name Timer Value Description 1 T302 4s SETUP_ACK messages (overlap receiving mode) 2 T303_1 4s SETUP message 1st timer expiration 3 T303_2 4s SETUP message 2nd timer expiration 4 T305 4/30s DISCONNECT message 5 T308_1 4s RELEASE message 1st expiration 6 T308_2 4s RELEASE message 2nd expiration 7 T310 10s CALL_PROCEEDING message 8 T313 4s CONNECT message 9 T313_2
PAGE 174
Denial Events ● ● the far end never saw the message because the message was corrupted in transmission by noise on the D-channel. Check for any type of T1/E1 facility errors. ● the far end is experiencing a high traffic condition and did not have the processing time to parse the sent message before the timer expired. ● even though the message was seen to be generated in an internal Communication Manager trace, the message was never transmitted out onto the D-channel.
PAGE 175
Event Data Cause Value 103 [0x67/0xE7] Parameter not implemented The equipment sending this Cause Value received a message that includes an Information Element that it does recognize and implements, however one or more of the fields contained in the Information Element are coded in such a way that it has not been implemented by the equipment sending this Cause Value.
PAGE 176
Denial Events Cause Value 111 (NI-2) is used in packet mode to be able to map the X.25 Cause Value 17 “remote procedure error”. Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch Application Interface (ASAI) application might generate this Cause Value. Cause Value 112 [0x70/0xF0] Local procedure error (1TR6: AT&T ISDN Protocol) This is a packet mode Cause Value.
PAGE 177
Denial Event Tables Communication Manager generates this Cause Value for events on tandem calls that have inter-worked from ISDN trunk groups to non-ISDN trunk groups. Troubleshooting ● Check the Cause Value Information Element (LOC). See Location Codes on page 130.
PAGE 178
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1007 CAS_remhold The Centralized Attendant Service (CAS) Remote Hold feature was accessed. No CAS attendant exists. 1008 CAS_remhold Centralized Attendant Service (CAS) Remote Hold was accessed by a non-CAS attendant. 1009 CAS_remhold Centralized Attendant Service (CAS) Remote Hold was accessed by non-CAS attendant.
PAGE 179
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1022 CDR_resource Call Detail Recording (CDR) resource exhaustion. Caller from tie trunk can receive reorder tone. 1023 CDR_resource Call Detail Recording (CDR) resource exhaustion. Give Trunk/Personal Central Office Line (TK/ PCOL) caller termination to announcement. User ID not found for announcement.
PAGE 180
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1040 Acd_login GM/UM set up of the Automatic Call Distribution (ACD) Logical Agent login info failed after password matching succeeded. 1041 DS0 loop around failed Incoming ds0 test call failed to set up non-inverting digital loop-around capability. 1042 TTR_unavail Facility Access Test.
PAGE 181
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1058 Auto Callback User ID User activating automatic callback has software partyblock member misrepresented. 1059 Auto Callback double qued User is activating automatic callback, but the call has already been queued or has no principal terminating User ID.
PAGE 182
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1072 TTR_TDM_VC Time Division Multiplexed (TDM) Voice Condition (VC) creation for Touch Tone Receiver (TTR) failed while in Audio add-on password supervision.
PAGE 183
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1083 Add/Rmv skill denied Add/Remove Agent Skills.
PAGE 184
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1098 TTI merge/unmerge failed Station server could not perform Terminal Translation Initiation (TTI) merge/unmerge. Certain resources are unavailable. The user can try again and the resources might be available. 1099 LWC access code rejected Voice synthesis Leave Word Calling access code rejected by msg_sv.
PAGE 185
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1115 LWC timeout Leave Word Calling timeout occurred in the dap for a non-call associated attempt. 1116 DCS confirm msg timeout Remote busy verification. A Distributed Communication System (DCS) confirmation message was not back in 4 seconds.
PAGE 186
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1127 Bsy Vfy warn tone conn Busy verification warning tone connection (callr) failed. 1128 Bsy Vfy warn tone conn Busy verify warning tone connection to verified call (callr2) failed. 1129 Bsy Vfy call went away Bridging a busy-verification call with a busy-verification call that no longer exists.
PAGE 187
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1139 Whisp Pg Attd call Whisper page - bridging to call with an attendant on it. 1140 Whisp Pg Man Exclsn call Whisper page - bridging to call with manual exclusion activated. 1141 Whisp Pg merge denied Bridging a busy whisper paging party to a call cannot be merged.
PAGE 188
Denial Events Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation 1153 ARS man activation queing Manual activation of queueing seen while in ARS supervision - ARS DAC has been dialed. 1154 Outgoing trk seizure fail Seize failed.
PAGE 189
Denial Event Tables Table 48: Call Process denial events (1001 - 1172) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1167 Can’t term emergency call No Attendants or redirection extension assigned for termination of emergency call. 1168 Second call failed Russia MultiFrequency (MF) Packet Signaling Second call attempt failed. 1169 Retry option not enabled Russia MultiFrequency (MF) Packet Signaling.
PAGE 190
Denial Events Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1175 ISDN channel unacceptable Channel unacceptable. See Cause Value 06 on page 139. UID DIAG/LOC/CV 1176 ISDN MLPP circ not resrvd MLPP preemption, circuit not reserved. See Cause Value 08 on page 139. UID DIAG/LOC/CV 1177 ISDN MLPP circ resv reuse MLPP preemption, circuit reserved for reuse.
PAGE 191
Denial Event Tables Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1195 Circ/channel unavail Requested circuit / channel not available. See Cause Value 44 on page 150. UID DIAG/LOC/CV 1196 ISDN blocked precedence Locked precedence level. See Cause Value 46 on page 151. UID DIAG/LOC/CV 1197 Resources unavail/unspec Resources unavailable, unspecified.
PAGE 192
Denial Events Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1215 ISDN msg typ nonexist/imp Message type nonexistent or not implemented. See Cause Value 97 on page 167. UID DIAG/LOC/CV 1216 Msg not compat state Message not compatible with call state. See Cause Value 98 on page 169. UID DIAG/LOC/CV 1217 ISDN nonexistant IE Nonexistent IE.
PAGE 193
Denial Event Tables Call processing Denial Events Event Types 1000 - 1899 show denial events generated during call processing, as listed in Call Process denial events (1001 - 1172) on page 177 and Call Process denial events (1225 1899) on page 193.
PAGE 194
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1300 Digits prevent call route MultiFrequency Compelled call not routed due to invalid digit, not enough digits, etc. 1301 Need MFC or TT dial type Outgoing dial type is not MultiFrequency Compelled or Touch Tone (TT).
PAGE 195
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1316 No unrstrictd term point No principal to terminate to, or it is termination restricted, and there is no termination coverage point. 1317 Coverage software failure Software error call_p termination to coverage point received invalid gm_term return code.
PAGE 196
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1332 Data mod options qry fail Reserving a pooled modem. Query data module for its options failed. 1333 Term to modem failure Seizing (terminating on) a pooled modem failed. 1334 Term to modem failure Analog endpoint termination to pooled modem (after administrable time delay expires) failed. 1335 LWC blocked by msg_sv Leave Word Calling.
PAGE 197
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1352 Port ntwk numbr too large Facility access test specified a port network number greater than the maximum allowed (MAX_PPNS). 1353 Cabinet number too large Malicious call trace specified a cabinet number greater than the maximum allowed (MAX_PPNS). 1354 SSC dialed ext's uid fail Station Security Code (SSC) digit processing.
PAGE 198
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1368 MFC out dialing timeout outgoing MultiFrequency Compelled call under outpulse supervision. Interdigit or end-of-dialing timeout without any expectation of user completing dialing. 1369 Dgt tmout PCOL merge fail Unexpected digit timeout. Drop of principal finds that it is a Personal Central Office Line (PCOL) group User ID.
PAGE 199
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1383 Agent login failure/error Logical Agent (LAGT) failure getting agent login-id. Possible causes: ● error initializing agent-stat table ● login for a skill failed ● TRAD logging into split already logged into ● already logged into maximum number of splits.
PAGE 200
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1399 EAS not enabled Activating Add/Remove Skill feature but Expert Agent Selection (EAS) is not enabled. 1400 EAS not enabled Activating Add/Remove Skill feature but Expert Agent Selection (EAS) is not enabled. 1401 COR_AR_SKL query failure Activating Add/Remove Skill feature COR_AR_SKL dpm_query failed. User ID structure not found.
PAGE 201
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1415 DAC msg err/agent login Adjunct Switch Application Interface (ASAI) third party direct agent call. process CP_DIR_AGENT message from ISG.
PAGE 202
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1429 Rmte cfwd not allowed Disallow remote call-forwarding of an Expert Agent Selection (EAS) loginID extension in all cases (for example, whether the loginID is logged into a terminal or not). 1430 COS deny cfwd activate User’s Class of Service does not allow this call forwarding activation.
PAGE 203
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1447 TTR port type query fail Facilities Access Test call - Touch Tone Receiver (TTR) test. CM query for TTR port type fails. 1448 Tested not trunk or TTR Facilities Access Test call - user type being tested is neither a trunk or Touch Tone Receiver (TTR), but logic that got us here thought it was.
PAGE 204
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1462 Split group digits wrong User activating/deactivating Position Busy. Wrong number of digits used to specify split group. 1463 Agent denied in split group Agent deactivating Position Busy, not allowed in split group. 1464 Agent not in aux work Agent not in AUX_WORK activating Position Busy.
PAGE 205
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1478 Block iteratve Lst Nbr Dl Last Number Dialed was accessed through an Abbreviated Dialing list. Do not allow it again. 1479 LND digits - DPM fail User’s Last Number Dialed (LND) digits were not returned successfully by dial plan manager.
PAGE 206
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1495 Local only/annc dest/uid Announcement record/playback session. Only local calls to the announcement are allowed. Call destination must be an announcement group. Must have a User ID slot for the announcement board. 1496 Annc ID needed/conn fail Begin integrated announcement session. Integrated announcement not identified (ann_sess()).
PAGE 207
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1508 Unparking vec ctrld call Answer parked call, give confirmation tone to parked party, merge 2 calls. Deny the unpark (answer back) attempt if the parked call is under vector control. 1509 Answr back station dialed Answer parked call, give confirmation tone to parked party, merge 2 calls.
PAGE 208
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1525 Call pickup from adjnct Pickup for Call Pickup or Trunk Answer Any Station (TAAS). Pickup of call originated by an adjunct is not allowed. 1526 Pickup of call wait call Pickup for Call Pickup. Pickup of a call waiting call is not allowed. 1527 Pickup of converse call Pickup for Call Pickup or Trunk Answer Any Station (TAAS).
PAGE 209
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1540 Callback type qry failed Invalid callback type returned by gm_query(). 1541 Invalid call ID/conn fail Switch has answered remote access call. Set up end-to-end signaling digit collection. Invalid Caller ID or Touch Tone Receiver (TTR) connection failure. (tu_ecoll_dg(), bch_ecoll_dg() -).
PAGE 210
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1556 Annc/music connect fail Wakeup announcement verification. Failure of the CM to connect a wakeup announcement or music to the call. 1557 Wakeup annc vfy COS deny Call originator does not have Class of Service permission to verify wakeup announcements. 1558 Maid status PMS msg fail Sending the PMA_MDSTATUS message to the PMS failed.
PAGE 211
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1572 Call hndlng/usg alloc err Processing incoming digits for ISDN call.Eerror during Incoming Call Handling Treatment or Usage allocation Check (GM_ISDNDIG). 1573 (also in Table 49) Principal is not ISDN Get called digits, calling number and name, etc., and send ISDN SETUP message to the far end. The principal is not ISDN.
PAGE 212
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1583 Spvsr state/feat_id wrong Generating intercept via CP_CONFTONE with sup = ACT_TTI_SUP (for Terminal Translation Initiation digit collection) and feat_id != CHG_SEC (Change station security code). Possible causes: ● wrong supervisory state ● wrong feat_id in callr 1584 Software invalid stim Software error.
PAGE 213
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1596 Attd must enter station Attendant-activation of call forwarding, and extended administration of call forwarding. The extension being administered is not a simple station user. 1597 Attd cant fwd attd calls Attendant-activation of call forwarding, and extended administration of call forwarding.
PAGE 214
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1611 Not MM station/chnl busy Sending down the MultiMedia Call Handling Basic mode activation message to the User Manager fails. Possible causes: ● station not part of Multi-media ● data user busy on at least one channel.
PAGE 215
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1624 Backward tone absent tmo Trunk outpulsing supervision. Outgoing backward tone absent timeout on MultiFrequency Compelled digit sending. 1625 7 min tmo - no tone rcvd Trunk outpulsing supervision.
PAGE 216
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1636 Not a downloadable set Refresh Terminal Parameters supervision. Port type is not a valid downloadable station port type. Only 8400/6400/4600/603 type stations and the 302 type attendant consoles are allowed. 1637 Wrt prot/maxd/annc bd Supervision for announcement record/playback session processing.
PAGE 217
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1646 No act call_ap/sftw err One-button transfer to data feature activation failed. Possible causes: ● No active call appearance ● Call id passed from call_p to su_obt() is not on the active call appearance 1647 Telcomtr diald illegl FAC Supervisor for telecommuting access.
PAGE 218
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1658 TTI - BRI not allowed Cannot Personal Station Access (PSA) disassociate a BRI station. 1659 TTI - COS restricted Class of Service does not allow Personal Station Access (PSA) disassociate operation. 1660 TTI - BRI not allowed Cannot Personal Station Access (PSA) associate a BRI station.
PAGE 219
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1675 Svc obsrvr vecstep/extdgt Activate service observing feature. Initiated from a vector step and only the Feature Access Code of service observing is in the vector step. End-to-end signaling digit collection of extension to be observed failed. 1676 Svc obsrv not on ext/VDN Validation of service observed extension.
PAGE 220
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1690 Software invalid stim Supervision after confirmation tone to a service observer. Invalid Call Processing (CP) stimulus received by this supervisor. 1691 Term restriction chk fail Processing incoming Call Forwarding. All Distributed Communication System (DCS) message. Other switch had problem processing CF_ACT message.
PAGE 221
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1703 Whisp pg query fail Whisper paging - shouldn’t see this - sim_quer/ su_query don’t develop GQRY_AE response to qtype QWHISP_PG 1704 Whisp pg usr not allowed Whisper paging. User is not allowed to make whisper pages. 1705 Whisp pg query fail Whisper paging. QWHISP_PG type gm_query failed.
PAGE 222
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 1721 QSIG VM-no remote user id Received a Voicemail Number MSI but did not receive an original diverting number. 1722 QSIG VM-prin not smpl uid The local principal User ID is not a simple user User ID. 1723 QSIG VM-no voicemail nbr Do not know the number of the voicemail adjunct, the call cannot transfer to the adjunct.
PAGE 223
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1744 Conf/xfer a tone Cannot conference or transfer tone. 1745 Conf/xfer Announcements Cannot conference or transfer with multiple announcements. 1746 Conf/xfer a Vector call Cannot conference or transfer vector call. 1747 Cnf/xfr Service Observers Cannot conference or transfer two service observers.
PAGE 224
Denial Events Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1767 Rmt Logout COR restricted no info available 1768 Rmt Logout COS restricted no info available 1769 Rmt Logout invalid input no info available 1770 Rmt Logout tenant number no info available 1771 Rmt Logout cant do self no info available 1772 PSA on Virt EXT disallow Personal Station Access (PSA) associate/ d
PAGE 225
Denial Event Tables Table 50: Call Process denial events (1225 - 1899) (continued) Event Type Event Description, as it appears on the event log Explanation 17861 CC: MG not administered Contact-closure related operation had unadministered media gateway number. 17871 CC: MG not registered An unregistered media gateway was selected for a contact-relay related operation on a G350 Media Gateway.
PAGE 226
Denial Events User Manager Events Event Types 1900 - 1906 show User Manager-generated denial events, as listed in User Manager denial events (1900 - 1906) on page 226. Table 51: User Manager denial events (1900 - 1906) Event Type Event Description, as it appears on the event log Explanation Event Data 1 1900 Invalid CFWD destination CF_DEST digits do not map to station User ID. 1901 Control Restrn Check fail Control Restriction.
PAGE 227
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1909 IP RRJ-RemoteOfc misadmin Registration rejected because: 0 IP address of the endpoint ● Remote Office is enabled on the Signaling Group screen, but the registration request (RRQ) is not from a supported Remote Office product (the Remote MAX Product/Vendor ID is invalid).
PAGE 228
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1916 IP RRJ-No H323 NonStdData Registration rejected because Non-standard Data (NSD) is missing in the registration request (RRQ) from the endpoint. 0 IP address of the endpoint 1917 IP RRJ-Invld H323 ObjID Registration rejected because the H323 Object ID in the registration request (RRQ) is invalid.
PAGE 229
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1923 IP RRJ-No E164 number Registration rejected because there is no valid E.164 number in the RRQ or the extension is not administered.
PAGE 230
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1928 IP RRJ-StnTyp/Protocl err Registration rejected because station type and call-signaling protocol are inconsistent. An IP Softphone should be assigned as one of the following: UID Endpoint type (3rd and 2nd nyble); call signaling protocol (low nyble) ● DCP extension, with call control set to IP Softphone ● H.
PAGE 231
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1936 IP RRJ-RO stn mismatch Registration rejected because of invalid analog station type. UID IP address of the endpoint IP RRJ-RO stn mismatch Registration of Remote Office endpoint rejected because set type on Remote Office differs from set type on station screen.
PAGE 232
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1948 IP RRJ-Complete pend reg Registration rejected because of failure to obtain a station user record (internal software error – corrupt translation).
PAGE 233
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1957 IP GRJ-GK will not host Gatekeeper request rejected because the gatekeeper is unwilling to host endpoint because no alias address has been provided. Endpoint type sent in GRQ IP address of the endpoint 1958 IP GRJ-Invalid extension Gatekeeper request rejected because the extension is not administered.
PAGE 234
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1971 IP BRJ-Build BCF msg Bandwidth Request rejected because of failure to build a Bandwidth Request Confirm (BCF) message for a non-Gateway or MCU user (internal software error). UID IP address 1972 IP BRJ-No H323 user Bandwidth Request rejected because the H.323 user object does not exist (internal software error).
PAGE 235
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 1987 IP ARJ-Admissn rqst fail Admission Request rejected: unexpected return code from Admission Request (internal software error). UID IP address 1988 IP URJ-Null UserID Unregistration Request rejected: received invalid endpoint ID.
PAGE 236
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2002 IP URJ-Build UCF msg Unregistration Request rejected because of failure to build an unregistration request confirm (UCF) message (internal software error).
PAGE 237
Denial Event Tables Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2013 IP FURQ-SigGrp removed Force Unregistration Request. An H.323 Gateway (administered as a signaling group) is registered. Unregister the Gateway before removing the administered signaling group. Gateway UID IP address of the far-end 2014 IP FURQ-Siggrp changed Force Unregistration Request.
PAGE 238
Denial Events Table 52: IP Denial Events (1907 - 2020) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2020 IP FURQ-Mtc:RemOfc TTI Forced Unregistration Request. Terminal Translation Initiation (TTI) background maintenance task has requested the removal of Remote Office LAN TTI ports. UID 0 IP FURQ-Mtc:RemOfc TTI Forced Unregistration Request. Terminal Translation Initiation (TTI) was turned off.
PAGE 239
Denial Event Tables Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2027 Annc not found on board User attempted to play MO_VAL_BD announcement and file was not found on board. 2028 Annc file has bad format User attempted to play MO_VAL_BD announcement and file had bad format.
PAGE 240
Denial Events Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2036 Incoming QSIG LWC failed Leave Word Calling on the incoming side of a QSIG_LWC MSI CS0FAC message failed. 2037 QSIG LWC fail find voice Getting the voice callr on the outgoing side of a QSIG_LWC MSI SETUP message failed.
PAGE 241
Denial Event Tables Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2056 No null caps SBS orig end IncomingMsg. Null caps not received on originating end of Separation of Bearer and Signaling (SBS) trunk. 2057 No null caps SBS term end IncomingMsg. Null caps not received on terminating end of Separation of Bearer and Signaling (SBS) trunk. 2058 Null caps on H323 trunk IncomingMsg.
PAGE 242
Denial Events Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2072 Conf/Transfer 2 Meet-me Conference or transfer 2 Meet-me conference call. 2073 Permission denied (or) Download permission deny User attempted to download firmware to a station. User does not have console permission.
PAGE 243
Denial Event Tables Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation 2084 TLS: Handshake Failure Handshake failed, for example due to no common cipher suite. 2085 TLS: Certificate expired An expired certificate was returned and rejected. 2086 SBS bearer Auth not supp If authorization code is required on outgoing Separation of Bearer and Signaling (SBS) bearer call, this is not supported.
PAGE 244
Denial Events Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2100 Rmt Div-QSIG VALU disable QSIG Remote Diversion is not allowed over a QSIG trunk with QSIG VALU disabled. 2101 Feat. requires only dgts A feature was activated via a request URI. The part of the request URI string that should contain all digits contained characters other than digits.
PAGE 245
Denial Event Tables Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2106 SCCAN announcement denied Seamless Converged Communications Across Networks (SCCAN) attempt to handover failed.
PAGE 246
Denial Events Table 53: Call Process denial events (2021 - 2299) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 2113 IP RRJ-TTI incapable Deny Terminal Translation Initiation (TTI) registration, IP endpoint not TTI capable. IP address TTI state 2114 IP RRJ-TTI reg eConsole Deny Terminal Translation Initiation (TTI) registration, request from IP eConsole. NULL IP address.
PAGE 247
Denial Event Tables Connection Manager Denial Events Event Types 2300 - 2399 show Connection Manager denial events, as listed in Connection Manager denial events (2300 - 2399) on page 247. Table 54: Connection Manager denial events (2300 - 2399) Event Type Event Description, as it appears on the event log Explanation Event Data 1 2300 Ept capabilities mismatch Endpoint connects to Time Division Multiplexed (TDM) bus or it hairpinned capabilities mismatch.
PAGE 248
Denial Events Table 54: Connection Manager denial events (2300 - 2399) (continued) Event Type Event Description, as it appears on the event log Explanation 2334 No channel resources No channel resources. 2335 RejReqMode-no common mode Deny inbound RM, not compatible with modes received in request. 2336 RejReqMode-no common mode Deny inbound RM, cannot arrive at common profile. 2337 RejReqMode-no modes rcvd Deny inbound RM, no data modes were received in request.
PAGE 249
Denial Event Tables Dial Plan Manager Denial Events Event Types 2400 - 2406 show Dial Plan Manager denial events, as listed in Dial Plan Manager denial events (2400 - 2406) on page 249. Table 55: Dial Plan Manager denial events (2400 - 2406) Event Type Event Description, as it appears on the event log Explanation Event Data 1 2400 UDP: too many conversions Digit conversion counter exceeded. 2401 UDP: node-rte pat blank Node number route pattern is blank.
PAGE 250
Denial Events Dial Access Plan Denial Events Event Types 3101 - 3200 show Dial Access Plan denial events, as listed in Dial Access Plan denial events (3101 - 3200) on page 250. Table 57: Dial Access Plan denial events (3101 - 3200) Event Type Event Description, as it appears on the event log Explanation 3101 DCS invalid PBX/Mach/Node Distributed Communication System (DCS) requires Trunk Group pbx-id, Signal Group Mach-id, or AAR Analysis node number.
PAGE 251
Denial Event Tables Table 58: Meet Me Conference denial events (3201 - 3299) (continued) Event Type Event Description, as it appears on the event log Explanation 3206 MM Access Obj/SAT Busy SAT window with Meet-me security/access code or obj is busy and cannot make changes via AC. 3207 Merge Meet-me Conf call User tried to merge to a existing Meet-me conference call and mmcon _val failed to validate the merge.
PAGE 252
Denial Events LSP Denial Events Event Types 3300 - 3399 show LSP-generated denial events, as listed in LSP denial events (3300 - 3399) on page 252. Table 59: LSP denial events (3300 - 3399) Event Type Event Description Explanation Event Data 1 Event Data 2 3300 IP RRJ-LSP not active Local Survivable Processor (LSP) is not yet active. NULL sending LSP’s IP address 3301 IP RRJ-LSP not admin Local Survivable Processor (LSP) has not been administered.
PAGE 253
Denial Event Tables Table 60: Data Error denial events (3400 - 3499) (continued) Event Type Event Description, as it appears on the event log Explanation Event Data 1 3407 Unicode ava file not read Unicode translation read error. Entire Avaya file not read. 3408 Error in Unicode ava file Unicode translation read error. Error found in Avaya file.
PAGE 254
Denial Events ESS Denial Events Event Types 3600 - 3604 are ESS-generated denial events, and listed in ESS denial events (3600 - 3604) on page 254. Table 62: ESS denial events (3600 - 3604) Event Type Event Description, as it appears on the event log Explanation Event Data 1 Event Data 2 3600 IP RRJ-ESS not admin ESS has not been administered. NULL sending ESS’s IP address 3601 IP RRJ-ESS obj not init EssMgr_ptr has not been initialized.
PAGE 255
Chapter 3: LEDs This chapter describes the meanings of the LEDs on system components and the alarm levels they indicate.
PAGE 256
LEDs Alarms are communicated to the system users and technicians by entries in the alarm log and the lighting of LEDs located on the attendant console, on all circuit packs, on the server, on the Cajun Ethernet switch if there is one, and, optionally, on customer-designated voice terminals. Warning alarms are not reported to the attendant console.
PAGE 257
Attendant console LEDs Attendant console LEDs The console has two red LEDs, labeled “ALM” and “ACK.” The ALM LED lights steadily when there is a major or minor alarm at the switch cabinet. The ACK LED lights steadily if the alarm has been successfully reported. If the system is unable to report the alarm, the LED flashes; this signals the attendant to call the Avaya alarm receiving system and report the alarm.
PAGE 258
LEDs LED alarms without Alarm Log entry or with Error Type 1 Whenever the system or a part of the system is reset, every affected circuit pack will briefly light their red and green LEDs as they are initialized. Upon power up of a newly installed system, several alarm indicators may remain lit until the circuit packs are administered. These alarms should be ignored until administration is completed. Boards with a “P” suffix have downloadable firmware.
PAGE 259
Circuit pack LEDs 3. Reseat the suspect circuit pack. ! CAUTION: This procedure can cause a partial or total service outage. Consult thoroughly the documentation for the associated maintenance object before proceeding. Observe the precautions and procedures described above. CAUTION: 4. Inspect the backplane connectors for bent pins. 5. If the system seems to be functioning correctly, but the circuit pack in question will not communicate with the system, replace the circuit pack.
PAGE 260
LEDs Maintenance circuit pack LEDs TN775D PN maintenance circuit packs have seven LEDs on their front panels. The top three LEDs are the standard group of red, green and yellow, and indicate the status of the circuit pack. The green LED on TN775Ds blinks faintly once per second, indicating continual self-testing.
PAGE 261
Circuit pack LEDs Figure 1: TN775 circuit pack LEDs on faceplate Figure notes: 1. Alarm LED (Red) 4. Latch pin 2. Test LED (Green) 5. Locking lever 3. Busy LED (Yellow) DS1C (TN574/TN1654) circuit pack LEDs The TN574 and the TN1654 LEDs provide an indication of the state of the DS1 converter and facilities. Note: Note: DS1 converters are used exclusively with a CSS.
PAGE 262
LEDs The yellow LED is used to indicate the state of the fiber interface, the fiber channel, and the DS1 channel as listed in Table 66: DS1C yellow LED flashing states on page 262 in order of priority. Table 66: DS1C yellow LED flashing states LED on LED off Condition 0.1 sec 0.1 sec Fiber Out-of-Frame or Fiber Loss of Signal 0.5 sec 0.5 sec In Frame, fiber channel down. The fiber channel communicating between the DS1C and the other fiber endpoint (EI or SNI) is down.
PAGE 263
Circuit pack LEDs Figure 2: TN574 DS1 Converter circuit pack LEDs Figure notes: 1. Alarm LED (Red) 4. STATUS LEDs 2. Test LED (Green) 5. SPAN LEDs 3. Busy LED (Yellow) TN1654 circuit pack LEDs The TN1654 DS1C-BD board has 11 LEDs on its faceplate. The top three system standard LEDs indicate the state of the DS1C-BD board. These LEDs are under firmware control until the board has established a link to the S8700 Media Server via the EI or SNI.
PAGE 264
LEDs The yellow LED under firmware control is used to indicate the state of the physical fiber interface, the Fiber Channel (link to EI or SNI), the DS1 Control Channel (link to opposite DS1CONV board), and the S8700 Media Server communications link in the following manner and order of priority. (The yellow LED remains on for longer periods of time as the DS1CONV complex becomes closer to being fully operational.) 1.
PAGE 265
Circuit pack LEDs Figure 3: TN1654 DS1CONV circuit pack . INSET 0015_0 RBP 052396 Switch Node Interface LEDs The Switch Node Interface (SNI) TN573 circuit pack has the standard red, green, and yellow LEDs. The red and green LEDs have the traditional meaning, where red indicates an alarm condition, and green indicates testing in progress.
PAGE 266
LEDs Table 67: Switch Node Interface (SNI) yellow LED flashing states on page 266 illustrates the SNI yellow LED states. Table 67: Switch Node Interface (SNI) yellow LED flashing states LED on LED off 0.1 sec 0.1 sec Fiber Out-of-Frame. This state indicates a failure of test #238, which may be caused by absence of the opposite end EI or Switch Node Interface, a broken or missing fiber, or a missing lightwave transceiver on either endpoint. 0.5 sec 0.5 sec In Frame — No Neighbor.
PAGE 267
Circuit pack LEDs Table 68: TN771D Maintenance/Test Yellow LED States LED State1 TN771D Mode Condition Solid off Normal The Maintenance/Test circuit pack detects no packet-bus faults. Solid on2 Normal The Maintenance/Test packet-bus port has successfully reconfigured the packet bus around a fault. Flashing (1 Hz) Normal The Maintenance/Test packet-bus port is unable to reconfigure the packet bus around a fault. Solid off Standalone3 The Maintenance/Test detects no packet-bus faults.
PAGE 268
LEDs Avaya Ethernet Switch LEDs The Avaya Ethernet switch’s LEDs are shown in Figure 4: Avaya Ethernet switch LEDs on page 268.
PAGE 269
UPS LEDs UPS LEDs All Ethernet hubs and UPSs have LEDs to indicate that they are powered on or off. LEDs “on” imply the device is powered on. LED “off” implies the device is powered down. The Powerware front panel has the LEDs shown in Figure 5: UPS LEDs on page 269. Figure 5: UPS LEDs ledlups KLC 030102 1 2 8 7 3 4 5 6 Figure notes: 1. Normal mode indicator 5. Off button 2. Battery mode indicator 6. On button 3. Bypass mode indicator 7. Bar graph indicators 4.
PAGE 270
LEDs IPSI LEDs There are four LEDs on the TN2312AP IPSI faceplate, and five LEDs on the TN2312BP IPSI faceplate. The top three LEDs are the standard ones found on most TN circuit packs. The fourth LED imitates the TN2182B Tone-Clock’s amber LED. The archangel flashes the yellow LED when active, 2 seconds on and 200 msec off. In addition, the TN2312BP has a fifth LED that shows the emergency transfer control status.
PAGE 271
IPSI LEDs Figure 7: S8700 IP-Connect IPSI display 1 2 CLK S E R V I C E ledlip1 KLC 030502 N E T W O R K Figure notes: 1. IPSI using DHCP 2.
PAGE 272
LEDs Figure 8: S8700 Multi-Connect IPSI Board Display 1 CLK 2 3 S E R V I C E ledsa01 KLC 030502 N E T W O R K Figure notes: 1. Switch identifier 2. Cabinet 3. IPSI has connectivity and an IP address 272 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 273
650A Power supply LEDs 650A Power supply LEDs Table 70: LED and alarm conditions on page 273 shows the LED and alarm conditions for the 650A Power Supply. Ring voltage and neon bus output do not activate alarm status.
PAGE 274
LEDs LED indicators of serial bus commands to the power supply Operation of the 655A power supply LED indicators for visual indication of serial bus commands to the power supply for power supply shutdown and ringing shutdown are described below. Power supply shutdown The 655A power supply can be commanded off for a period selectable from 1 to 255 seconds. The intent is to allow a hard reset to the G650 chassis remotely.
PAGE 275
Duplication memory card LEDs On the active server the Trans Mode LED will be green and the Receive Mode LED will be dark. On the standby server the Receive Mode will be green and the Trans Mode LED will be dark. Also see System shutdown LEDs on page 280.
PAGE 276
LEDs S8710 Media Server LEDs The S8710 Media Server has LEDs on both the front and back panels. Use the links in Table 73 for LED information and interpretation.
PAGE 277
S8710 Media Server LEDs Table 74: S8710 front panel LED interpretation Number Description Status 1 Internal health GREEN: normal AMBER: system degraded. See system board LEDs to identify component in degraded state. RED: system critical. See system board LEDs to identify component in critical state.
PAGE 278
LEDs Figure 10: LEDs on back panel of S8710 Media Server 1 3 2 3 2 4 3 3 2 DAL1 DUP MEMORY LINC ACTIVE LINC SYNC TRANS MODE RECEIVE MODE 100 MGz 2 100 MGz iLO 2 1 1 133 MGz VDCI UID 5 6 8 7 msds871c KLC 040604 Figure notes:S8710 rear panel LED interpretation Number Description Status 1 Not used ON: expansion board failed. OFF: normal 2 Not used STEADY ON: slot has power FLASHING: power is cycling OFF: no power 3 Quad-NIC fault (slot 2) (AMBER) ON: expansion board failed.
PAGE 279
S8700 Media Server LEDs Figure notes:S8710 rear panel LED interpretation (continued) Number Description Status 8 Power supply (GREEN) ON: power is on and power supply is functioning properly OFF: indicates one or more of the following conditions: ● AC power is unavailable ● Power supply failed ● Power supply in standby mode ● Power supply exceeded current limit 2 of 2 S8700 Media Server LEDs The S8700 Media Server has an LED called Active/Standby that indicates whether the server is the active
PAGE 280
LEDs Figure 11: S8700 Media Server LEDs—Front and Back 1 2 ACTIVE SERVICE 1 3 4 STANDBY 5 6 U2 7 8 5 4 3 2 9 RECEIVE LINE AVAYA LINK STAT TRANS DAI - 1 DUP MEMORY 2 10 11 1 scdlled KLC 030502 Figure notes: 1. Power 7. U2 (not used) 2. Configuration fault 8. 4 NIC ports (the numbers indicate their assigned Ethernet ports) 3. Disk activity 9. LEDs for the NIC ports 4. Network activity (not used) 1 0 . LEDs for fiber optic duplication connectivity 5.
PAGE 281
S8700 Media Server LEDs To test the server LEDs: 1. On the main menu, under Diagnostics, click Test Server LEDs. 2. On the Test Server LEDs screen, click Test LEDs. 3. Observe the Active/Standby LED on your server and the transmit LED on your duplication card to ensure they are blinking. Interpreting the test results An abnormal condition is indicated if an LED shows any of the following flashing patterns.
PAGE 282
LEDs S8500 Media Server LEDs The S8500 Media Server has: ● Five (5) LEDs on the front panel (Figure 12: S8500 front panel on page 282) ● Four (4) LEDs on the back (Figure 13: S8500 rear panel on page 283) Figure 12: S8500 front panel 1 2 3 4 5 disc 6 h3msfrnt LAO 070103 7 8 9 Figure notes: 1. CD-ROM drive activity LED (green) 6. System-error LED (amber) 2. CD eject button 7. Hard disk drive activity LED (green) 3. Power-control button 8. Reset button 4. USB connector 1 9.
PAGE 283
S8300 Media Server LEDs Figure 13: S8500 rear panel PCI 1 100-127 -, 3,0A, 50/60 Hz 200-240 -, 1,5A, 50/60 Hz PCI 2 LINK TX/RX 133 MHz/64 Bit, 100 MHz/64 Bit LINK TX/RX 2 1 h3msble2 KLC 082503 100-127 -, 3,0A, 200-240 -, 1,5A, 5 2 1 Figure notes: 1. Activity 2. Connection speed ● LED is off: there is a 10 BASE-T active link. ● LED is green: there is a 100 BASE-T active link. ● LED is orange: there is a 1000 BASE-T active link.
PAGE 284
LEDs GREEN “OK-to-Remove” LED The S8300 has a hard drive that must be shut down prior to removal of the S8300. Initiate a shutdown process by first depressing the shutdown button located next to the fourth GREEN “Ok-to-Remove” LED for 2-4 seconds (specific to the S8300). The GREEN LED will first blink; then go steady. Once steady, the GREEN LED indicates that the disk drive has been shut down properly and the S8300 is ready to be removed.
PAGE 285
S8300 Media Server LEDs Note: Note: For an S8300 configured as an LSP, the converse is true. If a G700 Media Gateway registers with an LSP, a major alarm is generated, and the RED LED turns on. When the Media Gateway unregisters, the RED LED turns off. The RED LED can be turned on by software to report an application or other error. The RED LED can also be turned on by a hardware watchdog that has not been cleared for at least 10ms, when the processing complex has ceased to function.
PAGE 286
LEDs Table 76: Test – Avaya Communication Manager status (green LED) Test – To Be Defined Power On Reset Off BIOS Boot Off OS and SW Boot On-SW System Up Off - SW Avaya Communication Manager Running On H.248 Registered Off - SW Shutdown in Progress Off - SW Shutdown Complete Off Table 77: Active – In Use (yellow LED) Active – In Use Power On Reset Off BIOS Boot Off OS and SW Boot Off System Up SW H.
PAGE 287
S8300 Media Server LEDs Table 78: OK to Remove (green LED) (continued) OK to Remove H.248 Registered Off Shutdown in Progress 1 Hz flash Shutdown Complete On 2 of 2 Table 79: ENET Link/Activity (green LED) ENET Link/Activity Power On Reset Off BIOS Boot N/A OS and SW Boot N/A System Up Link Status H.
PAGE 288
LEDs G700 and Media Module LEDs LEDs are important status indicators for technicians during on-site installation, maintenance, troubleshooting, and repair. They encompass three major areas: Alarms, Testing, and Usage Activity. Some LEDs are specialized to support specific procedures (such as removing the S8300 Media Server). When alarms or problems occur, LEDs are present to indicate that attention by a technician is needed. LEDs appear on the G700 LED panel, and each Media Module.
PAGE 289
G700 and Media Module LEDs LED panel location on the G700 As shown in Figure 15: G700 LED Panel Location on page 289, the LED panel is located on the top left corner of the G700. Directly below the LED panel is Media Module slot V1, which can be occupied by any type of Media Module. However, the S8300 Media Server can reside only in this particular slot because of height restrictions (for a specific discussion of the S8300 LEDs, see S8300 Media Server LEDs on page 283.
PAGE 290
LEDs Figure 16: G700 LED Panel 51 ALM PWR CPU MSTR LNK COL Tx Rx FDX 52 V1 ALM TST ACT OK TO REMOVE LNK COL Tx Rx FDX 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 FC Hspd LAG V2 EXT 1 EXT 2 V3 USB 1 55 SO ALM TST ACT SIG 60 EI 61 SM EM 62 V4 EXT 2 57 58 SI 64 65 66 EO EIA 530A DCE ALM TST ACT USB 2 EXT 1 56 63 E1/T1 SHUT DOWN SERVICES 54 EXT 1 EXT 2 59 ALM PWR CPU MSTR 53 FC Hspd LAG 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 ALM TST ACT
PAGE 291
G700 and Media Module LEDs Front panel LEDs The front panel includes the following LEDs (Figure 17: G700 Front Panel LEDs on page 291): ● 4 LEDs in Voice/Data Module zone (ALM, PWR, CPU, MSTR) Note: The LEDs labeled OPR and SYS on the P330 are labeled CPU and MSTR, respectively, on the G700.
PAGE 292
LEDs Navigating using the front panel LEDs Navigation using the front panel LEDs on the G700 is that same as with the Avaya Cajun P330 series. “Table 2-2: Avaya P330 <--> Select buttons, in the "Avaya P333T User’s Guide". For example, a technician can use the arrows to move left and right between the LEDs, and check the following: ● LNK (link) ● Col (collision) ● Tx (send) ● Rx (receive) In addition, a technician can query the status of the ports using 51-66 in the LED panel.
PAGE 293
G700 and Media Module LEDs RED ALM or Alarm LED The RED ALM or Alarm LED is on the top-left most corner of the LED Panel next to other important system LEDs (PWR, CPU, MSTR), as specified in Figure 17: G700 Front Panel LEDs on page 291. The presence of this RED ALM LED is primarily for on-site service technicians or dispatches. It alerts technicians of major failures that require a physical replacement or removal of equipment.
PAGE 294
LEDs EXT 1 LED EXT 1 LED appears on the LED Panel (Figure 17: G700 Front Panel LEDs on page 291), which reports the status of the first 10/100 MB/sec port (these LEDs report the 8 different functional statuses dictated by the left and right arrow buttons). EXT 2 LED EXT 2 LED appears on the LED Panel (Figure 17: G700 Front Panel LEDs on page 291), which reports the status of the second 10/100 MB/sec port (these LEDs report the 8 different functional statuses dictated by the left and right arrow buttons).
PAGE 295
G700 and Media Module LEDs Table 81: LED Definitions (continued) No.
PAGE 296
LEDs Media Module LEDs Media Gateway physical LEDs provide the technician with information regarding the ability to troubleshoot the Media Module as a whole. Note: Note: The physical LEDs provide board level status information, while the SAT provides port level status information. LED Locations on the Media Modules All Media Modules have three standard LEDs on the faceplate (Figure 18: Faceplate of Media Modules with Standard LEDs on page 296).
PAGE 297
G700 and Media Module LEDs MM710 T1/E1 Media Module LEDs The T1/E1 Media Module has four LEDs on its faceplate (see Figure 20: T1/E1 Media Module LEDs on page 297). Table 82: T1/E1 LEDs on page 297 shows their color and functions. The first three are the standard LEDs, which are under software control. Table 82: T1/E1 LEDs Name Color Location Description ALM RED Top Upon power-up, this LED is turned on. Upon passing diagnostics this LED is turned off.
PAGE 298
LEDs The supported portion of the LED control message allows software to change the status of the three standard LEDs on the T1/E1 Media Module faceplate. Power-up and alarm states are the only conditions where hardware sets the state of the LEDs independent of ANGEL firmware control.
PAGE 299
G700 and Media Module LEDs Operational control After successful initialization, the T1/E1 Media Module’s LEDs are controlled as follows: ● The Angel lights the YELLOW ACT LED when there is at least one non-idle trunk. If Communication Manager sends a message to drive the clock sync signals, the YELLOW ACT LED indicates this instead of the port busy/idle status.
PAGE 300
LEDs 300 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 301
Chapter 4: G700 Media Gateway Traps This chapter applies to the G700 Media Gateway only. SNMP Alarming on the G700 Setting up SNMP alarm reporting involves two main tasks: ● Configure the primary server to report alarms ● Configure the G700 to Send its Traps to the Primary Server Configure the primary server to report alarms The primary server may be either an S8300 Media Server or an S8700 Media Server. The Media Server supports two methods for reporting alarms.
PAGE 302
G700 Media Gateway Traps Add INADS Phone Numbers and Enable Alarms to INADS The following procedure using the primary server’s Linux shell commands administers the dial-out modem to send alarms in the OSS method. In this example, the primary server is an S8300, and the services support agency is Avaya’s Initialization and Administration System (INADS). Perform this task after all Communication Manager administration is complete. To add INADS phone numbers and enable alarms to INADS 1.
PAGE 303
SNMP Alarming on the G700 To configure an SNMP community string for traps 1. Open the Run dialog box. 2. Type telnet and press Enter. 3. Log in as root. 4. At the L2 Processor CLI prompt, type set snmp community trap [community string] and press Enter. 5. Type exit Configure the destination for G700 SNMP traps Events occurring on the G700 cause SNMP traps to be generated.
PAGE 304
G700 Media Gateway Traps G700 Alarm Format G700 Media Gateways (serving either as standalone port networks, or as port networks within an IP or a Multi-Connect system) report alarms to the primary server (either an S8300 or S8700 Media Server) using SNMP traps.
PAGE 305
G700 Traps and Resolutions G700 Traps and Resolutions Although these alarms can be viewed from the primary server, they are normally resolved from within the G700 Media Gateway. The G700 generates the following traps. Follow the error resolution procedures in Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server on page 305 to resolve errors indicated by these traps.
PAGE 306
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 2 4 MIN cmgPsuBriefFanFault — A G700’s PSU fan has been operating at less than 90% of its nominal speed for between 5 and 15 minutes. (This may be an early warning of overheating.) 1. Verify there are faults in the system.
PAGE 307
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 4 10 MIN cmgCpuTempWarningFault — A G700’s CPU temperature sensor has exceeded its warning threshold. 1. Verify there are faults in the system. Use the Avaya G700 Media Gateway Processor (MGP) Command Line Interface (CLI) command show faults to display any faults on the G700. 2.
PAGE 308
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 5 12 MIN cmgDspTempWarningFault — The temperature sensor in a G700’s DSP complex has exceeded its warning threshold. 1. Verify there are faults in the system. Use the Avaya G700 Media Gateway Processor (MGP) Command Line Interface (CLI) command show faults to display any faults on the G700. 2.
PAGE 309
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 6 14 MAJ cmgTempShutdownFault — The temperature sensor in a G700’s CPU has exceeded its shutdown threshold. The system is about to begin controlled shutdown. 1. Verify there are faults in the system. Use the Avaya G700 Media Gateway Processor (MGP) Command Line Interface (CLI) command show faults to display any faults on the G700. 2.
PAGE 310
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 7 16 MAJ cmgMgpPowerFault — The voltage reading at the server’s +5.1V power source is out of tolerance. 1. Check voltages. Enter the MGP CLI command show voltages to determine voltages for Media Modules and other components of the G700. Voltage may be reduced by a short in one of the Media Modules or a bad power supply. 2.
PAGE 311
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 9 20 MAJ cmgVoipPowerFault — The voltage reading at the VoIP complexes’ +3.4V power source is out of tolerance. 1. Check voltages. Enter the MGP CLI command show voltages to determine voltages for Media Modules and other components of the G700. Voltage may be reduced by a short in one of the Media Modules or a bad power supply. 2.
PAGE 312
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 11 24 MAJ cmg8620PowerFault — The voltage reading at the VoIP Processor’s +2.5V power source is out of tolerance. 1. Check voltages. Enter the MGP CLI command show voltages to determine voltages for Media Modules and other components of the G700. Voltage may be reduced by a short in one of the Media Modules or a bad power supply. 2.
PAGE 313
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 14 30 MAJ cmgSyncSignalFault — Synchronization signal lost. 1. Check that provisioned clock-sync source has a good signal by issuing a Media Gateway Processor (MGP) Command Line Interface (CLI) command show sync timing Procedure for setting synchronization timing sources on T1/E1 MM or MM710: 1.
PAGE 314
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level 14 30 MAJ (cont’d) Description / Recommendation 5. Verify whether or not these commands were executed by issuing a show sync timing command to ensure that the source is provisioned and active, or visually inspect the Yellow LED on the MM710 Media Module. Note: When the Yellow LED is on 2.7 seconds and off 0.
PAGE 315
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 74 cmgFirmwareDownloadBegun — A Media Gateway began downloading a software module. 75 cmgModuleManualReset — A Media Module is beginning a user-requested reset operation. 76 cmgVoipManualReset — A VoIP engine is beginning a user-requested reset operation.
PAGE 316
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 17 90 MAJ cmgMemoryFault — The Media Gateway Processor has detected a low processor memory condition. If an attempt by a software module to allocate memory fails, or if available memory falls below four million bytes, this trap is generated. If available memory later rises above five million bytes, this trap is cleared.
PAGE 317
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 19 94 MAJ cmgFirmwareDownloadFault — An attempt to download a software module has failed. 1. Check the event log to find the specific error. 2. Troubleshoot the specific error according to the information found. For example, if the string “File not found” appears in the log, then verify that the image file: a. Exists b. Has the correct name c.
PAGE 318
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 21 98 MAJ cmgIccMissingFault — An internal communications controller, expected in Slot 1, is missing. 1. Check for presence of S8300. 2. If present, check the G700 administration. 3. If the administration is correct, suspect the S8300. 22 100 MAJ cmgIccAutoReset — The Media Gateway automatically reset the internal communications controller.
PAGE 319
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 25 106 MAJ cmgRegistrationFault — The Media Gateway cannot register with any controllers in its controller list. 1. Verify that the controller list is correct. From the MGP CLI, enter the command show mgc list. The IP address should match the S8700 Media Server CLAN or the S8300 Media Server IP addresses. 2.
PAGE 320
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 29 114 WRN cmgMgAutoReset — The Media Gateway Processor automatically reset (rebooted). The processor automatically resets when a critical error occurs from which it cannot recover. The error may be software or hardware related. It may also automatically reset in response to a maintenance test running on the call controller.
PAGE 321
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 30 116 WRN cmgModuleAutoReset — A Media Module in the Media Gateway automatically reset (rebooted). A Media Module automatically resets when it fails a sanity test performed by the Media Gateway Processor. It may also automatically reset in response to a maintenance test running on the call controller.
PAGE 322
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 32 118 MIN cmgModulePostFault — A Media Module failed its power-on start-up test. 1. Reset or replace the Media Module. 34 122 MAJ cmgConfigUploadFault — An attempt to upload a configuration file failed. 1. Check the event log for an error message during the backup/ restore process. 2.
PAGE 323
G700 Traps and Resolutions Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level Description / Recommendation 37 128 WRN cmgVoipAutoReset — A VoIP (Voice Over IP) module in the Media Gateway automatically reset (rebooted). A VoIP module automatically resets when it fails a sanity test performed by the Media Gateway Processor. It may also automatically reset in response to a maintenance test running on the call controller.
PAGE 324
G700 Media Gateway Traps Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued) Event ID Trap # Alarm Level 37 128 WRN (cont’d) Description / Recommendation 8. If manually resetting the VoIP module does not return it to service, and if a spare VoIP module of the same type is available, replace the failing VoIP module with the spare and see if the spare VoIP module goes into service. If so, follow procedures for dealing with the original, bad, VoIP module. 9.
PAGE 325
Chapter 5: Communication Manager Maintenance-Object Repair Procedures Note: This chapter does not contain MOs for the DEFINITY Wireless Business System (DWBS), nor MOs for messaging systems. Refer to the maintenance documentation that accompanies these products for this information Note: The Communication Manager maintenance subsystem is partitioned into separate entities called Maintenance Objects (MOs).
PAGE 326
Communication Manager Maintenance-Object Repair Procedures Figure 21: Display of test board Subsystems Maintained by Communication Manager Communication Manager subsystems are listable using list config and, in most cases, have some maintenance activities involved. Note: Note: list config all on the Communication Manager SAT gives you information that includes whether or not stations have been administered on a port.
PAGE 327
Subsystems Maintained by Communication Manager G700 Subsystems Maintained by Communication Manager The G700 subsystems that are applicable to Communication Manager maintenance considerations are identifiable by the presence of ‘angels’. Angels may be either physical or virtual, and both types use the CCMS message. Table 84: G700 Subsystems Maintained by Communication Manager on page 327 lists the applicable subsystems and how they are maintained.
PAGE 328
Communication Manager Maintenance-Object Repair Procedures MO Groupings by MM Type Table 85: Media Module Tests on page 328 shows MO groupings by Avaya Media Module type.
PAGE 329
Viewing Communication Manager Alarms Table 85: Media Module Tests (continued) Media Module Maintenance Object VOIP Media Module (MM760) Board (MG-VOIP) Voice Announcements (Communication Manager) Board (MG-ANN) Announcement Ports (VAL-PT) Ethernet Port (ETH-PT) 2 of 2 Viewing Communication Manager Alarms The technician views Communication Manager alarms and events through commands that are available via the Web Interface or the SAT command-line interface.
PAGE 330
Communication Manager Maintenance-Object Repair Procedures The command syntax for circuit packs is test port location. Variable Definition Platform Range UU Universal cabinet number ATM PNC 1-64 CSS PNC 1-44 G600 1-64 ATM PNC A, B, C, D, or E CSS PNC A, B, C, D, or E G600 A, B, C, or D ATM PNC 01-21 CSS PNC 01-21 G600 01-10 All 01, 02,... C SS pp Carrier designation Circuit pack slot 2-digit port number The command syntax for media modules is test port GGGVSpp.
PAGE 331
Abort Code 1412 Abort Code 1412 Tests that do not run on the G700 abort with Abort Code 1412. Tests that abort are listed under each MO, but are not described. Escalation Procedure This document is not intended to solve all levels of trouble. When the limits of these procedures have been reached but a problem is not resolved, a technician should escalate the problem to a higher level of technical support. This escalation should conform to the procedures in the Technical and Administration Plan.
PAGE 332
Communication Manager Maintenance-Object Repair Procedures ABRI-PORT (ASAI ISDN-BRI Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full MO Name ABRI-POR 1 MAJ MIN WRN test port location l ASAI ISDN-BRI port 1. Use set options to set the alarm level for ABRI ports. The alarm level can be set independently for onand off-board alarms to WARNING, MINOR, or MAJOR for every ABRI port in the system. For repair procedures, see BRI-PORT (ISDN-BRI Port) on page 685.
PAGE 333
AC-POWER AC-POWER S8700 | 8710 / S8500 AC Power for AC-Powered Systems MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AC-POWER WRN test environment UU1 AC Power 1. UU is the universal cabinet number indicated in the PORT field of the alarm log. S8700 MC S8700 Multi-Connect systems support three different cabinet types as PNs: multicarrier cabinets, single-carrier cabinets and the G650 rack mounted cabinets. All types may be powered by either an AC or DC power source.
PAGE 334
Communication Manager Maintenance-Object Repair Procedures The AC power supply produces the following DC outputs: +5 VDC, -5 VDC, -48 VDC, +12 VDC, and a battery-charging voltage. The DC outputs distribute power on the cabinet backplane to the circuit pack slots. The AC power supply also produces AC ringing voltage. The AC ringing voltage output value and frequency depend on the country of use. The power supply has a circuit breaker and EMI filtering.
PAGE 335
AC-POWER System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order shown. By clearing error codes associated with the Battery and Battery Charger Query test (#5), you may clear errors from other tests in the testing sequence. Note: Note: The following tests apply to J58890CE, J58890CF, and J58890CH.
PAGE 336
Communication Manager Maintenance-Object Repair Procedures Table 88: Test #78 Power Query Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 100 2000 ABRT 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. 2.
PAGE 337
AC-POWER Table 88: Test #78 Power Query Test (continued) Error Code Test Result Description / Recommendation 1 (cont’d) FAIL Procedures for a J58890CE 1. Check for AC power at the wall outlet (99–127 or 200–250 VAC). 2. If AC power is absent, then the problem is not with the system itself. Power must be restored to the wall outlet. If present, there could be a problem with the battery or battery chargers. Resolve every alarm logged against POWER (battery & battery charger), and rerun the test. 3.
PAGE 338
Communication Manager Maintenance-Object Repair Procedures AC-POWER for DC-Powered Systems MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AC-POWER WRN test environment location AC Power Note: In a DC-powered multicarrier cabinet, the AC-POWER MO exists but serves no functional purpose. Because the system cannot determine the type of power used, the AC-POWER test should always pass or abort.
PAGE 339
AC-POWER System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing error codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 340
Communication Manager Maintenance-Object Repair Procedures AC Power Query Test (#78) AC Power Query Test (#78) is not valid for DC-powered cabinets and should always abort or pass. S8700 IP will always abort. Table 91: Test #78 Power Query Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run test are not available. 100 2000 ABRT Response to the test request was not received within the allowable time period. 1.
PAGE 341
ADM-CONN (Administered Connection) ADM-CONN (Administered Connection) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADM-CONN MAJ MIN WRN status administered-connection n 1 Administered Connection 1. n is an administered connection number indicated in the PORT field of the Alarm or Error Log.
PAGE 342
Communication Manager Maintenance-Object Repair Procedures Table 92: Administered Connection Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 6, 21, 31, 127 (d) Any None Any OFF None 16 (a) Any None Any OFF None 17 (e) Any None Any OFF None 18, 102 (f) Any None Any OFF None 22 (a, g) Any None Any OFF None 34, 42, 44, 58 (h) Any None Any OFF None 38, 41 (i) Any None Any OFF None 43, 81 Any None A
PAGE 343
ADM-CONN (Administered Connection) b. Error Types 1, 28: the address of the destination endpoint is: an unassigned number (1), has an invalid number format (28), or is restricted from terminating calls due to Class of Restriction (“Access Denied”). Verify that the destination address is correct and that the destination endpoint is administered. The destination endpoint is not administered on the switch where this error is logged. c.
PAGE 344
Communication Manager Maintenance-Object Repair Procedures ADX8D-BD (AUDIX Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADX8D-BD MIN WRN test board location sh AUDIX circuit pack The ADX8D-BD MO defines a TN566/TN2169 EMBEDDED AUDIX circuit pack (also called DEFINITY AUDIX) operating in DP (digital-port) mode. For port-level problems, see ADX8D-PT (AUDIX Digital Port) on page 345.
PAGE 345
ADX8D-PT (AUDIX Digital Port) ADX8D-PT (AUDIX Digital Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADX8D-PT MIN test port location l AUDIX digital port ADX8D-PT WRN test port location sh AUDIX digital port The ADX8D-PT MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack (also called DEFINITY AUDIX) operating in DP (digital-port) mode.
PAGE 346
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 93: EMBEDDED AUDIX Digital Port Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 40987 None WRN OFF 1 (c) 1 to 20 None WRN OFF 15 (d) Any None 18 (e) 0 busyout port location WRN OFF 23 (f) 0 None WRN OFF None WRN ON 130 (g) release port location test port locat
PAGE 347
ADX8D-PT (AUDIX Digital Port) b. Error Type 1, Aux Data 40987: the user may experience a noisy port or link, due to an off-board problem that is detected by the port circuit. If so, replace the circuit pack (see caution at the beginning of this section). Once the problem is resolved, the alarm is retired after a predetermined time. c. Error Type 1, Aux Data 1 to 20: At least 15 off-board problems have been detected with the link to the voice port.
PAGE 348
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented when you are inspecting errors in the system. Order of Investigation Short Test Sequence Long Test Sequence D/ND1 Voice and Control Channel Local Looparound test (#13) X ND NPE Crosstalk test (#9) X ND 1. D = Destructive; ND = Nondestructive NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE.
PAGE 349
ADX8D-PT (AUDIX Digital Port) Crosstalk testing is performed on both the primary (for voice) and the secondary (for data) information channel associated with each EMBEDDED AUDIX port. If NPE Crosstalk Test (#9) fails on either channel, the voice port is taken out of service. Table 94: Test #9 NPE Crosstalk Test Error Code Test Result Description / Recommendation 1 ABRT During testing of the primary information channel, system resources may not have been available.
PAGE 350
Communication Manager Maintenance-Object Repair Procedures Table 94: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors. 2. Resolve any TONE-PT errors. 3. Retry the command at 1-minute intervals up to 5 times.
PAGE 351
ADX8D-PT (AUDIX Digital Port) While the primary information channel is still looped around, the Control Channel Looparound test is performed. The Looparound test for the secondary information (data) channel is then performed. This is the same test as the primary information channel’s loop-around test. Next, a Conference test is implemented for the primary information channel. This is the same test as Conference test (#6). Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run.
PAGE 352
Communication Manager Maintenance-Object Repair Procedures Table 95: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was put in use during the test. 1. Use display port location to determine the voice port extension of the port. Use status station to determine the service state of the port. If the service state indicates that the port is active, wait until it is idle before retesting. 2.
PAGE 353
ADX16D-B (16-Port AUDIX Circuit Pack) ADX16D-B (16-Port AUDIX Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADX16D-B MIN test board location sh AUDIX circuit pack ADX16D-B WRN test board location sh AUDIX circuit pack The ADX16D-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack combination operating in 16-port mode digital (DP).
PAGE 354
Communication Manager Maintenance-Object Repair Procedures ADX16A-BD (AUDIX Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADXCL-BD ADX16A-B MIN WRN test board location sh AUDIX circuit pack The ADX16A-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack combination operating in control-link (CL) mode. For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 355
ADX16D-P (16-Port AUDIX Digital Port) ADX16D-P (16-Port AUDIX Digital Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADX16D-P MIN WRN test port location l AUDIX Digital port ! CAUTION: Never do any of the following without first shutting down AUDIX.
PAGE 356
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 96: EMBEDDED AUDIX Digital Port Error Log Entries Error Type Aux Data Associated Test Alarm Level On/ Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 40987 None WRN OFF 1 (c) 1 to 20 None WRN OFF 15 (d) Any None 18 (e) 0 busyout port location WRN OFF 23 (f) 0 None WRN OFF None WRN ON 130 (g) release port location test port loca
PAGE 357
ADX16D-P (16-Port AUDIX Digital Port) b. Error Type 1 with Aux Data 40987: The user may experience a noisy port or link, due to an off-board problem that is detected by the port circuit. If so, replace the circuit pack (see caution at the beginning of this section). Once the problem is resolved, the alarm is retired after a predetermined time. c. Error Type 1: At least 15 off-board problems have been detected with the link to the voice port.
PAGE 358
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. Long Test Sequence D/ND1 Voice and Control Channel Local Looparound test (#13) X ND NPE Crosstalk test (#9) X ND Order of Investigation Short Test Sequence 1. D = Destructive; ND = Nondestructive NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE.
PAGE 359
ADX16D-P (16-Port AUDIX Digital Port) Table 97: Test #9 NPE Crosstalk Test Error Code Test Result Description / Recommendation 1 ABRT During testing of the primary information channel, system resources may not have been available. Also, the port may have been busy during the test. 1. Check the port status. 2. Use display port location to determine the voice port extension of the port. Use status station to determine the service state of the port. If the port is active, it is unavailable for this test.
PAGE 360
Communication Manager Maintenance-Object Repair Procedures Table 97: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors. 2. Resolve any TONE-PT errors. 1004 ABRT The port was put in use during the test. The test has been aborted. 1.
PAGE 361
ADX16D-P (16-Port AUDIX Digital Port) Voice and Control Channel Local Loop Test (#13) This test checks the information and control channels between the server the EMBEDDED AUDIX port circuit. The server sends a message to loop around both the information and control channels for the port. First, the primary information (voice) channel loop back test is run. While the primary information channel is still looped around, the Control Channel Looparound test is performed.
PAGE 362
Communication Manager Maintenance-Object Repair Procedures Table 98: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was put in use during the test. The test has been aborted. 1. Use display port location to determine the voice port extension of the port. Use status station to determine the service state of the port. If the port is active, wait until it is idle before retesting.
PAGE 363
ADX16A-PT (AUDIX Analog Line/Control Link) ADX16A-PT (AUDIX Analog Line/Control Link) S8700 | 8710 S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ADXCL-PT or ADX16A-P MIN test port location l AUDIX Analog Line/ Control Link ADXCL-PT or ADX16A-P WRN test port location sh AUDIX Analog Line/ Control Link ! CAUTION: Never do any of the following without first shutting down AUDIX.
PAGE 364
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 99: EMBEDDED AUDIX Analog Line/Control Link Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test port location sh r 1 1 (a) 40977 None 18 0 busyout station ext WRN ON release station extension 23 (b) 0 None WRN OFF None WRN ON test port location sh 130 (c) 257 (d) 40973 None 513 (e) Any None 1025 (
PAGE 365
ADX16A-PT (AUDIX Analog Line/Control Link) d. Error Type 257 is an in-line error and can only be resolved over time. Ringing voltage is absent. If only one analog circuit pack in the system has this problem, replace the circuit pack. If only analog circuit packs on a particular carrier have this error, the ringing generator may not be connected to this carrier. If analog circuit packs on many carriers have this error, check the ringing generator. e. Error Type 513: AUDIX is not available to the switch.
PAGE 366
Communication Manager Maintenance-Object Repair Procedures NPE Crosstalk Test (#6) This 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. This test is part of the long test sequence and executes in about 25 seconds.
PAGE 367
ADX16A-PT (AUDIX Analog Line/Control Link) Table 100: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid call during the test. The test has been aborted. 1. Use display port location to determine the station extension. Use status station to determine the service state of the port. If the port is active, it is unavailable for certain tests. Wait until the port is idle before testing. 2.
PAGE 368
Communication Manager Maintenance-Object Repair Procedures Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. Table 101: Test #7 Conference Circuit Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run test are not available.
PAGE 369
ADX16A-PT (AUDIX Analog Line/Control Link) Loop-Around Test (#161) This test is designed to check the on-board transmission capabilities of the NPE on the analog port. Table 102: Test #161 Loop-Around Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources for this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1.
PAGE 370
Communication Manager Maintenance-Object Repair Procedures Table 102: Test #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test disabled by administration. 1. To enable the test for the particular analog station, enter change station extension. 2. Enter y in the Test field. 2000 ABRT Response to the test was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 371
AESV-LNK (AE Services Link) AESV-LNK (AE Services Link) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AESV-LNK MAJ WRN test aesvcs-server Application Enablement Services (AESVCS) Link AESVCS Links provide a connection between Communication Manager and an AESVCS Server in which data is exchanged. Communication Manager dynamically creates and deletes AESVCS Links as socket connections to AESVCS Server are established and torn down.
PAGE 372
Communication Manager Maintenance-Object Repair Procedures b. Error type 769 is a log only error and is displayed when Communication Manager does not receive a response from the AESVCS Server to a heartbeat message that was sent over the AESVCS Link. Failure to receive a response to a heartbeat message results in the deletion of the AESVCS Link by Communication Manager. Both an AESVCS Session Level and Link level error is generated against this condition. Escalate if the error persists. c.
PAGE 373
AESV-LNK (AE Services Link) Aux Data Description 208 Communication Manager detected processing the data from the AESVCS Server and closed the socket connection. Escalate if the problem persists. 209 Communication Manager could not read data from the socket and closed the connection. Escalate if the problem persists. 2 of 2 d. Error Type 2561 is a log only error and is displayed when an AESVCS message is discarded due to a link buffer overflow.
PAGE 374
Communication Manager Maintenance-Object Repair Procedures Table 104: AESVCS Link Heartbeat Test (#1324) (continued) Error Code Test Result Description / Recommendation PASS The heartbeat test passed. 2 of 2 AESVCS Session Level Link Status Test (#1323) The AESVCS Session Level Link Status Test determines if any AESVCS Links are associated with a given AESVCS Session.
PAGE 375
AESV-SESS (AE Services Session) AESV-SESS (AE Services Session) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AESV-SESS MAJ WRN test aesvcs-server Application Enablement Services (AESVCS Session) An AESVCS Session is a logical connection between Communication Manager and a single AESVCS Server and encompasses all the AESVCS Links that are connected between them.
PAGE 376
Communication Manager Maintenance-Object Repair Procedures b. Error type 769 is a log only error and is displayed when Communication Manager detects a heartbeat failure on one or more AESVCS Links within the AESVCS Session. The Aux Data filed contains the link ID of the last AESVCS Link to report a heartbeat failure. An AESVCS Link level error is also generated against this condition. Refer to AESV-LNK section for more information. c.
PAGE 377
AESV-SESS (AE Services Session) AESVCS Link Heartbeat Test (#1324) The AESVCS Link Heartbeat test sends a TCP tunnel connection heartbeat message to the far end AESVCS Server. If the AESVCS Server fails to return a response to the heartbeat message, the test fails. An AESVCS Link that fails a Heartbeat test is subsequently deleted from the AESVCS Session. Table 107: AESVCS Link Heartbeat Test (#1324) Error Code Test Result Description / Recommendation FAIL The heartbeat test failed. 1.
PAGE 378
Communication Manager Maintenance-Object Repair Procedures ALARM-PT (Alarm Port) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ALARM-PT MIN test port location l Alarm-Port ALARM-PT WRN test port location sh Alarm-Port The Alarm Port MO provides on-board maintenance for an analog line port that is administered as an external device alarm port. Tests are provided to verify the analog line ports ability to detect an external device alarm.
PAGE 379
ALARM-PT (Alarm Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented in the table below. For example, by clearing error codes associated with the Battery Feed test (#35), you may also clear errors generated from other tests in the testing sequence. Order of Investigation Short Test Sequence Long Test Sequence D/ ND1 Battery Feed test (#35) X X ND Station Status and Translation Audits and Updates test (#36) X X ND 1.
PAGE 380
Communication Manager Maintenance-Object Repair Procedures Table 110: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. Use display port location to determine the station extension, attendant number, or trunk group/member number of the port. Use status station, status attendant, or status trunk to determine the service state of the port.
PAGE 381
ALARM-PT (Alarm Port) Table 110: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. enter list config, and resolve any problems that are found. 2.
PAGE 382
Communication Manager Maintenance-Object Repair Procedures Table 111: Test #36 Station Status and Translation Audits and Updates (continued) Error Code Test Result Description / Recommendation 1000 ABRT The test was aborted because system resources required to run this test were not available. The port may be busy with a valid call. Use display port PCSSpp to determine the station extension of the port. Use status station to determine the service state of the port.
PAGE 383
ALARM-PT (Alarm Port) Table 111: Test #36 Station Status and Translation Audits and Updates (continued) Error Code 0 Test Result Description / Recommendation PASS The software and the port processor have the same status. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct.
PAGE 384
Communication Manager Maintenance-Object Repair Procedures ANL-16-L (16-Port Analog Line) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ANL-16-L MIN test port location l 16-Port Analog Line ANL-16-L WRN test port location sh 16-Port Analog Line The circuit packs listed below provide 16 analog line ports for single-line voice terminals.
PAGE 385
ANL-16-L (16-Port Analog Line) Ringing Caused by Maintenance Testing Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this ringing is disturbing the customer or the terminal equipment, it should be disabled in the Tests field of the change station extension screen. Be aware that this action will also disable Tests #6, 7, 161, and 35.
PAGE 386
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures. b. Error Type 1: These are in-line errors and can only be resolved over time. c. Aux Data 40960 indicates that too many simultaneous incoming ringing attempts were made on this board. Only 4 ports on a board may ring simultaneously.
PAGE 387
ANL-16-L (16-Port Analog Line) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Battery Feed test (#35), you may also clear errors generated from other tests in the testing sequence.
PAGE 388
Communication Manager Maintenance-Object Repair Procedures Table 113: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run test are not available. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is. 1. Enter display port location to determine the station’s extension.
PAGE 389
ANL-16-L (16-Port Analog Line) Table 113: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT The test has been disabled by administration. The default for the Test field on the station screen is y. Determine why this field has been set to “no” on this station (this may be due to the ringing application Test #48, that can be customer or terminal disturbing. 1.
PAGE 390
Communication Manager Maintenance-Object Repair Procedures Table 113: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Enter list config, and resolve any problems. 2.
PAGE 391
ANL-16-L (16-Port Analog Line) Table 114: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid call during the test. The test has been aborted. 1. Use display port location to determine the station extension. Use status station to determine the service state of the port. If the port is active, wait until it is idle. 2. Retry the command at 1-minute intervals up to 5 times.
PAGE 392
Communication Manager Maintenance-Object Repair Procedures Table 114: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Enter list config, and resolve any problems. 2.
PAGE 393
ANL-16-L (16-Port Analog Line) Table 115: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is. 1. Enter display port location to determine the station’s extension. Enter status station extension to determine the service state of the port.
PAGE 394
Communication Manager Maintenance-Object Repair Procedures Table 115: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 395
ANL-16-L (16-Port Analog Line) 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 116: Test #36 Station Status and Translation Audits and Updates Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 396
Communication Manager Maintenance-Object Repair Procedures Table 116: Test #36 Station Status and Translation Audits and Updates (continued) Error Code Test Result Description / Recommendation 1 FAIL This does not indicate a hardware problem. The switchhook audit failed. The other updates were not performed because of this failure. This may occur when the audit is performed at the same time the terminal equipment goes off-hook. 1. Use status station to determine when the port is available. 2.
PAGE 397
ANL-16-L (16-Port Analog Line) 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 terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance. If this ringing disturbs the customer or the terminal equipment, you can disable it via the Tests field on the change station screen.
PAGE 398
Communication Manager Maintenance-Object Repair Procedures Table 117: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT The test has been disabled by administration. The default for the Test field on the station screen is y. Determine why this field was set to n on this station. It may be due to the brief ringing disturbance that this test may cause. 1.
PAGE 399
ANL-16-L (16-Port Analog Line) Table 117: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Enter list config, and resolve any problems. 2.
PAGE 400
Communication Manager Maintenance-Object Repair Procedures Table 118: Test #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command at 1-minute intervals up to 5 times.
PAGE 401
ANL-16-L (16-Port Analog Line) Table 118: Test #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT Could not allocate the necessary system resources to run this test. This could be due to a failure to seize the port. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 402
Communication Manager Maintenance-Object Repair Procedures Table 118: Test #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Enter list config, and resolve any problems. 2.
PAGE 403
ANL-BD (Analog Line Circuit Pack) ANL-BD (Analog Line Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name Of MO ANL-BD MIN WRN test board location sh 8-Port Analog Line circuit pack ANL-BD MIN WRN test board location sh 8-Port Neon Analog Line circuit pack ANL-BD MIN WRN test board location sh 16-Port Neon Analog Line circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors.
PAGE 404
Communication Manager Maintenance-Object Repair Procedures ANL-LINE (8-Port Analog Line) Error log entries and tests also apply to ANL-NE-L (8-Port Analog Line).
PAGE 405
ANL-LINE (8-Port Analog Line) Hardware Error Log Entries and Test to Clear Values Table 119: 8-Port Analog Line Error Log Entries Error Type Aux Data Associated Test Alarm Level On/ Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 40960 40975 40977 None 15 (c) Any Audits and Updates (#36) 18 0 busyout station extension WRN OFF release station extension 130 (d) None WRN ON test port location sh 257 (e) Station Present test (#48) WRN OFF test
PAGE 406
Communication Manager Maintenance-Object Repair Procedures b. Error Type 1: These are in-line errors that can only be resolved over time. Aux Data 40960: too many simultaneous incoming ringing attempts were made on this board. Only 4 ports on a board may ring simultaneously. A 5th incoming call will cause an inline error from the board. Aux Data 40975: the terminal equipment was on-hook when ring-tip was detected during ringing.
PAGE 407
ANL-LINE (8-Port Analog Line) Order of Investigation Short Test Sequence Long Test Sequence Loop Around and Conference test (#47) Station Status and Translation Audits and Updates test (#36) X D/ND1 X ND X ND 1. D = Destructive; ND = Nondestructive NPE Crosstalk Test (#6) One or more NPEs (Network Processing Elements) 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.
PAGE 408
Communication Manager Maintenance-Object Repair Procedures Table 120: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve TTR-LEV errors. 2. Resolve TONE-PT errors. 3. Retry the test at 1-minute intervals up to 5 times.
PAGE 409
ANL-LINE (8-Port Analog Line) Table 120: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT System resources required to run this test are not available.
PAGE 410
Communication Manager Maintenance-Object Repair Procedures Table 120: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL This test can fail due to either on- or off-board problems. Off-board problems of concern include EXP-PN, EXP-INTF, and RMC-ENV faults, TDM-BUS faults, and faults associated with the Tone Detectors/Tone Generators. Clear every off-board problem before replacing the board.
PAGE 411
ANL-LINE (8-Port Analog Line) 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 trying to detect a current.
PAGE 412
Communication Manager Maintenance-Object Repair Procedures Table 121: Test #35 Battery Feed Test Results (continued) Error Code Test Result Description / Recommendation 1005 ABRT The test was aborted due to a configuration problem. This error code occurs under either of the following conditions: 1. This test may not be applicable, or it may be disruptive to terminal equipment other than a voice terminal (for example, the modem pool member or music on hold). 2.
PAGE 413
ANL-LINE (8-Port Analog Line) Table 121: Test #35 Battery Feed Test Results (continued) Error Code Test Result Description / Recommendation FAIL The port’s battery feed chip is unable to supply sufficient power to the terminal equipment. This may occur when the test is performed at the same time that the terminal equipment goes off-hook. 1. Use status station to determine when the port is available for testing.
PAGE 414
Communication Manager Maintenance-Object Repair Procedures 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 (such as station type, dial type, network connection) with information kept in the software. The software is updated with the switchhook state reported by the port processor.
PAGE 415
ANL-LINE (8-Port Analog Line) Table 122: Test #36 Station Status and Translation Audits and Updates Test (continued) Error Code Test Result Description / Recommendation 1006 ABRT This port has been busied out by command or taken out-of-service by the failure of the NPE Crosstalk test. 1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this error is present, then release the port with release station extension and run the test again. 2.
PAGE 416
Communication Manager Maintenance-Object Repair Procedures Table 122: Test #36 Station Status and Translation Audits and Updates Test (continued) Error Code 0 Test Result Description / Recommendation PASS The software and the port processor have the same status. User-reported troubles on this port should be investigated by using other port tests, by examining station wiring, by examining the station, and by ensuring that the terminal is correctly translated as off-premises or on-premises.
PAGE 417
ANL-LINE (8-Port Analog Line) The Conference Circuit test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. Test #47 also tests the operation of the port conference circuits in the NPE for three and four parties. In addition, a test is run to measure noise. 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 418
Communication Manager Maintenance-Object Repair Procedures Table 123: Test #47 Loop Around and Conference Test (continued) Error Code Test Result Description / Recommendation 7 ABRT The port was seized by a user for a valid call. 1. Enter display port location to determine the station’s extension. Enter status station extension to determine the service state of the port. If the port is active, it will be unavailable for certain tests. Wait until the port is idle before retesting. 2.
PAGE 419
ANL-LINE (8-Port Analog Line) Table 123: Test #47 Loop Around and Conference Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT The test was aborted due to a configuration problem. This error code occurs under either of the following conditions: ● This test may not be applicable, or it may be disruptive to terminal equipment other than a voice terminal (for example, a modem pool member or music on hold).
PAGE 420
Communication Manager Maintenance-Object Repair Procedures Table 123: Test #47 Loop Around and Conference Test (continued) Error Code Test Result Description / Recommendation 7 FAIL The conference test or the noise test failed. This could cause noisy or unreliable connections, or users calling this port may hear an echo. The problem can also be off-board, as described below. 13 The reflective loop around with gain set to low and the 600-ohm balance failed.
PAGE 421
ANL-LINE (8-Port Analog Line) Table 123: Test #47 Loop Around and Conference Test (continued) Error Code Test Result Description / Recommendation PASS The port is able to provide an analog transmission path to the station equipment. User-reported troubles on this port should be investigated by using other port tests, by examining station wiring, by examining the station, and by ensuring that the terminal is correctly translated as off-premises or on-premises.
PAGE 422
Communication Manager Maintenance-Object Repair Procedures Table 124: Test #48 Station Present Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the station’s extension.
PAGE 423
ANL-LINE (8-Port Analog Line) Table 124: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation 1008 ABRT Could not allocate a ringing circuit for one of the following reasons: ● Every ringing circuit is active. ● The ringing generator is defective. ● It is incorrectly wired. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, look for RING-GEN errors in the Error Log.
PAGE 424
Communication Manager Maintenance-Object Repair Procedures Table 124: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation FAIL The terminal equipment is not connected to the circuit pack or the ringing generator may have failed. 1. Remotely test the equipment. 2. If the test fails again, look for RING-GEN errors in the error log. If present, see RING-GEN (Analog Ring Generator) on page 1942 (analog ring generator) maintenance. 3.
PAGE 425
ANL-NE-L (8-Port Analog Line) ANL-NE-L (8-Port Analog Line) See ANL-LINE (8-Port Analog Line) on page 404. S8700 | 8710 / S8500 This maintenance object covers the neon message waiting lamp power on the 8-port analog line board.
PAGE 426
Communication Manager Maintenance-Object Repair Procedures AN-LN-PT (Analog Line Port) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AN-LN-PT MIN test port location l Analog Line port AN-LN-PT WRN test port location sh Analog Line port The TN793B/TN2793B Analog Line (w/ Caller ID) and the TN797 Analog Trunk and Line circuit packs both support AN-LN-PT.
PAGE 427
AN-LN-PT (Analog Line Port) Error log entries and test to clear values Table 125: Analog line port error log entries Error Type Aux Data Associated Test Alarm Level On/ Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 40960 40975 40977 none 15 (c) Any Audits and Updates test (#36) 18 0 busy station extension WRN ON release station extension None WRN ON test port location sh 130 (d) 257 (e) 40973 None 513 (f) Station Present test (#48) WRN O
PAGE 428
Communication Manager Maintenance-Object Repair Procedures ● Aux Data 40975 indicates that the terminal equipment was on-hook when ring-tip was detected during ringing. This usually indicates a failure in the terminal equipment or the type of terminal has a low ringer impedance. 1. Call the terminal equipment and verify that the terminal rings. 2. If the terminal does not ring, replace it. 3. Otherwise, run test port location, and follow the procedure for Test #48.
PAGE 429
AN-LN-PT (Analog Line Port) System technician-demanded tests: descriptions and error codes Investigate tests in the order presented. By clearing error codes associated with the Battery Feed test (#35), you may clear errors generated from other tests in the sequence. Order of Investigation Short Test Sequence Long Test Sequence D/ ND1 Battery Feed test (#35) X X ND Station Present test (#48) X X ND Analog Looparound test (#161) S8300 / G700: This test aborts with Error Code 1412.
PAGE 430
Communication Manager Maintenance-Object Repair Procedures Table 126: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources are unavailable. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is. 1. Enter display port location to determine the station’s extension. 2. Enter status station extension to determine the service state of the port. 3.
PAGE 431
AN-LN-PT (Analog Line Port) Table 126: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT A valid call seized the port during the test and aborted the test. 1. Use display port location to determine the station extension. 2. Use status station extension to determine the service state of the port. 3. If the port is active, wait until it is idle before testing. Retry the command at 1-minute intervals up to 5 times. 4.
PAGE 432
Communication Manager Maintenance-Object Repair Procedures Table 126: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL This test can fail due to either on- or off-board problems. Off-board problems include TDM-BUS faults, EXP-PN, EXP-INTF, and RMC-ENV faults, and faults associated with the Tone Detectors/Tone Generators. Clear every off-board problem before replacing the board. 1.
PAGE 433
AN-LN-PT (Analog Line Port) Table 127: Test #7 Conference Circuit Test Error Code Test Result Description / Recommendation ABRT Necessary system resources could not be allocated to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 1000 ABRT System resources are unavailable. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is. 1.
PAGE 434
Communication Manager Maintenance-Object Repair Procedures Table 127: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT System resources required to run this test are not available. 1. Resolve any TONE-PT errors in the error log. 2.
PAGE 435
AN-LN-PT (Analog Line 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 power, and detecting the resulting current.
PAGE 436
Communication Manager Maintenance-Object Repair Procedures Table 128: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Administration has disabled the test. The default for the Test field on the station form is y. Determine why this field has been set to n on this station (this may be due to the ringing application Test #48, which can be disturbing to customer or terminal equipment). 1.
PAGE 437
AN-LN-PT (Analog Line Port) Table 128: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation PASS The port’s battery feed chip is able to provide sufficient power to the station equipment to detect on-/off-hook, but may not be able to supply power for touch-tones. 1. If touch-tones are inoperative on this station, replace the circuit pack or media module, because this port is inoperative. 2.
PAGE 438
Communication Manager Maintenance-Object Repair Procedures Table 129: Test #36 Station Status and Translation Audit and Update (continued) Error Code Test Result Description / Recommendation 1004 ABRT A valid call seized the port during the test and aborted the test. 1. Use display port location to determine the station extension. 2. Use status station extension to determine the service state of the port. 3. If the port is active, wait until it is idle before testing.
PAGE 439
AN-LN-PT (Analog Line Port) Table 129: Test #36 Station Status and Translation Audit and Update (continued) Error Code Test Result Description / Recommendation 1 FAIL The switchhook audit failed. This result does not indicate a hardware problem. The other updates were not performed because of this failure. This may occur if the audit is performed at the same time the terminal equipment goes off-hook. 1. Use status station extension to determine when the port is available. 2.
PAGE 440
Communication Manager Maintenance-Object Repair Procedures 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 terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
PAGE 441
AN-LN-PT (Analog Line Port) Table 130: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation 1008 ABRT A ringing circuit could not be allocated. Either every ringing circuit is active, the ringing generator is defective, or it is incorrectly wired. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, look for RING-GEN errors in the Error Log. 3.
PAGE 442
Communication Manager Maintenance-Object Repair Procedures Table 130: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation FAIL The terminal equipment is not connected to the circuit pack. Some terminal equipment, such as modems, may fail even when connected properly. 1. Remotely test the terminal equipment. 2. If the test fails again, resolve any RING-GEN errors in the error log, if present. 3.
PAGE 443
AN-LN-PT (Analog Line Port) Analog Looparound Test (#161) S8300 / G700: This test aborts with Error Code 1412. This test checks the on-board transmission capabilities of the NPE, the codec, and the battery feed chip of the analog port. The test passes if the signal measured by the Tone Detector is within acceptable limits. Table 131: Test #161 Analog Looparound Test Error Code Test Result Description / Recommendation ABRT Necessary system resources could not be allocated to run this test. 1.
PAGE 444
Communication Manager Maintenance-Object Repair Procedures Table 131: Test #161 Analog Looparound Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors in the Error Log. 2. Resolve any TONE-PT errors in the Error Log. 3.
PAGE 445
AN-LN-PT (Analog Line Port) Table 131: Test #161 Analog Looparound Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem.
PAGE 446
Communication Manager Maintenance-Object Repair Procedures Table 131: Test #161 Analog Looparound Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This result could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to make sure that the board translations are correct. Enter list configuration, and resolve any problems. 2.
PAGE 447
ANN-BD (Announcement circuit pack) ANN-BD (Announcement circuit pack) Note: MO Name in Alarm Log Alarm level Initial command to run Full name of MO ANN-BD MIN test board location l Announcement Circuit Pack ANN-BD WRN test board location l Announcement Circuit Pack Note: The information contained in ANN-BD refers only to the TN750-series of circuit packs. Expressions such as "announcement circuit pack" and "announcement board" are to be interpreted to mean the TN750-series only.
PAGE 448
Communication Manager Maintenance-Object Repair Procedures General notes Here are a few important general notes that apply to any problem on the Announcement circuit pack. The user should read this before attempting to work on the TN750 Announcement circuit pack or Announcement Ports, especially if the circuit pack needs to be replaced. 1. The TN750 Announcement circuit pack retains all integrated announcements as long as the circuit pack has power.
PAGE 449
ANN-BD (Announcement circuit pack) If the announcement file becomes corrupted, the only solution is to re-record all announcements. To do this, follow these steps: d. Remove the announcement board. e. Remove the tape cartridge from the tape drive. Do this so that announcements are not automatically restored from tape. f. Re-insert the announcement board. g. Re-record all announcements. h. Insert the tape cartridge in the tape drive. i. Enter save announcements to save all the announcements on the tape.
PAGE 450
Communication Manager Maintenance-Object Repair Procedures Uploading/Downloading announcements Integrated announcements on the TN750 Announcement circuit pack can be uploaded to the memory card with save announcements. Likewise, integrated announcements can be downloaded to the Announcement circuit pack with restore announcements.
PAGE 451
ANN-BD (Announcement circuit pack) Table 132: Announcement circuit pack error log entries (continued) Error type Aux data 125 (f) Associated test Alarm level (See WRN message) On/ Off board None MIN ON Test to clear value 170 0 None MIN ON 217 (g) 0 None WRN OFF 257 65535 Control Channel Test (#52) MIN ON 257 (h) Any None 267 (g) 0 None WRN OFF 513 (i) Any None 1025 (j) 4363 NPE Audit Test (#50) 1281 (k) 17699 None 1538 (l) Any None MIN ON Angel-SP Handshake (
PAGE 452
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. b. Error Type 1: the circuit pack totally stopped functioning or it was physically removed from the system. Note: Note: The alarm is logged about 11 minutes after the circuit pack has been removed and/or SAKI Test (#53) fails.
PAGE 453
ANN-BD (Announcement circuit pack) i. Error Type 513: when reported with Aux Data in the range of 4352 to 4358, the circuit pack has reported a hardware failure on the circuit pack. The circuit pack should be replaced. Replacing the circuit pack results in loss of integrated announcements (TN750/B only). See General notes on page 465 near the beginning of this Maintenance procedure. j. Error Types 1025 and 3840: not service-affecting, no action is required. k.
PAGE 454
Communication Manager Maintenance-Object Repair Procedures System technician-demanded tests: descriptions and error codes Investigate tests in the order presented in Table 133: System Technician-demanded tests: ANN-BD on page 454. By clearing error codes associated with the first test, you may clear other errors in the sequence. For a complete description of these tests, refer to the XXX-BD (Common Port Circuit Pack/ Media Module) on page 2539.
PAGE 455
ANN-BD (Announcement circuit pack) Table 134: TEST #208 angel-speech processor (SP) handshake test Error code Test result Description/ Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. If Error Type 1538 is present in the Error Log, follow the maintenance strategy recommended for this Error Type. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT Could not allocate the necessary system resources to run this test. 1.
PAGE 456
Communication Manager Maintenance-Object Repair Procedures If the test fails, then it returns the total number of defective announcements found. In addition, associated with each failure is an error in the Error Log (Error Type 14). The Aux Data indicates the number of the first defective announcement found. This number corresponds to the announcement numbers on the announcement form. The extension relating to the announcement can be determined by display announcement.
PAGE 457
ANN-BD (Announcement circuit pack) Table 135: TEST #209 announcement checksum test (continued) Error code Test result Description/ Recommendation ABRT Internal system error. 1. Retry the command at 1-minute intervals a maximum of 5 times. 0-256 FAIL Test failed. The error code indicates the total number of defective announcements that were found. When TEST #209 fails with error code 0, the Global Checksum failed on the board, but no individual Checksum failed.
PAGE 458
Communication Manager Maintenance-Object Repair Procedures Table 135: TEST #209 announcement checksum test (continued) Error code Test result Description/ Recommendation PASS All recorded announcements checksum correctly, indicating that the speech main memory is functioning properly. User-reported troubles on this circuit pack should be investigated using other circuit pack and port tests. Refer to ANN-PT (announcement port) on page 465 Maintenance documentation for a description of the port tests.
PAGE 459
ANN-BD (Announcement circuit pack) 140AY loop around test (#210) This test checks the integrity of the record channel on the Announcement circuit pack (Announcement Port 1). The main function of the 140AY device is to accept Pulse Code Modulation (PCM)/Adaptive Differential Pulse Code Modulation (ADPCM) samples and compress/expand the samples using ADPCM. This test connects a Tone Generator to one port (Announcement Port 1, the recording port), and a Tone Detector to another port (Announcement Port 9).
PAGE 460
Communication Manager Maintenance-Object Repair Procedures Table 136: TEST #210 140AY loop around test (continued) Error code Test result Description/ Recommendation 1002 ABRT 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. Refer to TDM-BUS (TDM Bus) on page 2237 Maintenance documentation to diagnose any active TDM-BUS errors. 1.
PAGE 461
ANN-BD (Announcement circuit pack) Table 136: TEST #210 140AY loop around test (continued) Error code Test result Description/ Recommendation 2007 ABRT The Announcement circuit pack thinks that Port 1 or Port 9 is busy. 1. Retry the command at 1-minute intervals a maximum of 5 times. 2. If the test continues to abort, follow the Announcement Port maintenance procedures for Ports 1 and 9. 2100 ABRT Could not allocate the necessary system resources to run this test. 1.
PAGE 462
Communication Manager Maintenance-Object Repair Procedures 1. When attempting to record an announcement, users hear the proper record tone, but the announcement does not record (they do not know it until the announcement is played back). 2. Performing a test board long when the circuit pack is in this state yields the following abort codes: ● Ports 1 AND 9 abort Test #206 with code 1024 ● Ports 1 AND 9 abort Test #205 with code 2000 ● Board level Tests #209 and #210 abort with code 1024 3.
PAGE 463
ANN-BD (Announcement circuit pack) Table 137: TEST #211 super frame match inquiry (continued) Error code Test result Description/ Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. ABRT Internal system error. 1. Retry the command at 1-minute intervals a maximum of 5 times. FAIL Test failed. Announcement playbacks should sound corrupted. 1.
PAGE 464
Communication Manager Maintenance-Object Repair Procedures Table 138: TEST #212 clock match inquiry test (continued) Error code Test result Description/ Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. ABRT Internal system error. 1. Retry the command at 1-minute intervals a maximum of 5 times. FAIL Test failed. Announcements recorded or played back while the clock circuitry is not functioning properly sound distorted.
PAGE 465
ANN-PT (announcement port) ANN-PT (announcement port) MO Name in Alarm Log Alarm level Initial command to run Full name of MO ANN-PT MIN test port location l Announcement Port ANN-PT WRN test port location l Announcement Port The TN750 Announcement circuit pack is a service circuit pack that provides an integrated means for recording announcements that can be played back on demand by call processing as part of a calling feature (that is, announcements on hunt group calls).
PAGE 466
Communication Manager Maintenance-Object Repair Procedures 3. Save announcements replaces the announcement file on the card with the Announcement circuit pack speech memory. Care must be taken not to mistakenly enter this command, thereby destroying a valid file on tape. 4. Restore announcements replaces the Announcement circuit pack speech memory with the announcement file on the card.
PAGE 467
ANN-PT (announcement port) Announcement session Announcements can be recorded, played back, and deleted from an announcement session. A station’s COS needs to include console permissions in order for that station to be able to enter an announcement session. To enter an announcement session, go off-hook on a station that has console permissions and enter the appropriate FAC (administered as Announcement access code on the FACs form). Dial tone should be returned at this point.
PAGE 468
Communication Manager Maintenance-Object Repair Procedures Announcement Board Locked Condition The Announcement circuit pack can exhibit a condition that does not allow recording. If the circuit pack gets locked into this state (this is an extremely rare condition), two of the announcement ports on the circuit pack (one of which is the record port) will be unusable by software. Also, save/restore announcements will not work since the record port looks busy to the circuit pack.
PAGE 469
ANN-PT (announcement port) Hardware error log entries and test to clear values Table 139: Announcement port error log entries Error Type Aux data Associated test Alarm level On/ Off board Test to clear value 0 (a) 0 Any Any Any test port PCSSpp sh r 1 Playback Speech Memory Array (PSMA) Test (#206) MIN ON test port PCSSpp sh r 3 The port was busied out WRN OFF release port PCSSpp 130 (b) None WRN ON test port PCSSpp sh 257 Channel Administration Memory Array (CAMA) Test (#205) MI
PAGE 470
Communication Manager Maintenance-Object Repair Procedures System technician-demanded tests: descriptions and error codes Investigate tests in the order presented. By clearing error codes associated with the Channel Administration Memory Array (CAMA) Test, you may also clear other errors.
PAGE 471
ANN-PT (announcement port) Table 141: TEST #205 channel administration memory array (CAMA) test (continued) Error code Test result Description/ Recommendation FAIL Test failed. Announcements played back on this port may sound corrupted. 1. Reset the circuit pack via reset board PCSS and then run this test again. If the test continues to fail, replace the circuit pack (see Warning). 2.
PAGE 472
Communication Manager Maintenance-Object Repair Procedures Clear the Announcement circuit pack lock-up remotely by performing a soft reset to the circuit pack: 1. busyout board location (this command drops all calls in progress on the Announcement circuit pack) 2. Reset circuit pack using reset board location 3.
PAGE 473
ANN-PT (announcement port) Table 142: TEST #206 playback speech memory array (PSMA) test (continued) Error code Test result Description/ Recommendation 1003 ABRT 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. 1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV (TTR Level) on page 2370. 2. Look for TONE-PT errors in the Error Log.
PAGE 474
Communication Manager Maintenance-Object Repair Procedures Table 142: TEST #206 playback speech memory array (PSMA) test (continued) Error code Test result Description/ Recommendation 1 to 254 FAIL Test failed. The error code indicates the number of byte count errors found by the Tone Detector. 1. Reset the circuit pack via reset board PCSS and then run this test again. If the test continues to fail, replace the circuit pack (see Warning). 2.
PAGE 475
ANN-PT (announcement port) If the circuit pack is locked into this state, the following symptoms are observed: ● When attempting to record an announcement, users hear the proper record tone, but the announcement does not record (they do not know it until the announcement is played back).
PAGE 476
Communication Manager Maintenance-Object Repair Procedures Table 143: TEST #222 140AY channel sanity inquiry test (continued) Error code Test result Description/ Recommendation FAIL Test failed. Announcements cannot be played back over this port. 1. Reset the circuit pack via reset board PCSS and then run this test again. If the test continues to fail, replace the circuit pack (see Warning). 2.
PAGE 477
ANNOUNCE (announce) ANNOUNCE (announce) ● MO Name in Alarm Log Alarm level Initial command to run Full name of MO ANNOUNCE none none ANNOUNCEMENT The ANNOUNCE MO logs an error in the hardware error log if save announcements or restore announcements does not complete successfully, or the system fails to restore announcements from the memory card at boot time.
PAGE 478
Communication Manager Maintenance-Object Repair Procedures Hardware error log entries Table 144: ANNOUNCE error log entries Error type Aux data Associated test 1 (a) (d) any None 257 (d) any None 513 (b) (d) 0 None 769 (d) 0 None 1025 (c) (d) any None Alarm level On/Off board Test to clear value Notes: a. Error Type 1: occurred while saving announcements. See Table 145: Aux data error codes and recommended repair procedures on page 478. b.
PAGE 479
ANNOUNCE (announce) Table 145: Aux data error codes and recommended repair procedures (continued) Aux data Description/ Recommendation 32001 Internal system error. 1. Check other ANNOUNCE errors and take corrective action. If there are no other ANNOUNCE errors, do the following: 2. Retry the command at 2-minute intervals a maximum of 3 times. 3. If restore announcements fails, escalate the problem. 32002 Announcement circuit pack is in use. 1.
PAGE 480
Communication Manager Maintenance-Object Repair Procedures Table 145: Aux data error codes and recommended repair procedures (continued) Aux data Description/ Recommendation 32009 Required DATA-CHL is not administered or out of service. (A DATA-CHL is required to save or restore announcements.) 1. Add a DATA-CHL if none is administered. 2. If a DATA-CHL is administered, use status to check the status of all DATA-CHLs. At least one DATA-CHL should be in the in-service/idle state.
PAGE 481
ASAI-ADJ (ASAI Adjunct) ASAI-ADJ (ASAI Adjunct) S8700 | 8710 / S8500 Refer to BRI-SET, Various Adjuncts on page 708.
PAGE 482
Communication Manager Maintenance-Object Repair Procedures ASAI-BD (Multi-Application Platform Board) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ASAI-BD MIN test board location ASAI-BD ASAI-BD WRN test board location ASAI-BD Maintenance testing of the common circuit pack is handled by on-board firmware and server-controlled tests. Maintenance software queries the firmware for error and alarm information, status, and test results.
PAGE 483
ASAI-BD (Multi-Application Platform Board) ● LED use: The LED Control message 038x requests the Angel to drive the red, amber, and green LEDs on the face plate of a typical port board on or off. Only the MAPD’s red LED is controlled by this message. Yellow and green change requests the MAPD receives from the switch drive LCD behavior rather than LED behavior. The system continues to send the same LED control messages to the MAPD that the system currently sends to every other port board.
PAGE 484
Communication Manager Maintenance-Object Repair Procedures ASAI-EPT S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ASAI-EPT MAJ1 test station extension ASAI-Adjunct 1. The alarm level for ASAI adjuncts is adminisered using set options. The alarm level can be set independently for on- and off-board alarms toWARNING, MINOR, or MAJOR for every ASAI adjunct in the system.
PAGE 485
ASAI-EPT Table 146: ASAI-EPT Error Log Entries (continued) Error Type Aux Data Associated Test 25622566 (h) 0 None 2567 (i) 0 None 2568 (j) 0 None 3329 (k) Any Signaling Link status (#626) 35843839 (l) Any None 3841 (m) 4095 Any None Alarm Level ASAI-EPT On/ Off Board MAJ WRN† OFF Test to Clear Value 2 of 2 1. Major alarms on this MO may be downgraded to Warning alarms based on the value used in set options. Notes: a. Error Type 0: Run the short test sequence first.
PAGE 486
Communication Manager Maintenance-Object Repair Procedures b. Error Type 2: ISDN-BRI signaling protocol violation. Timers associated with layer-3 messages expired before a required response was received. In the following table, the aux data column indicates which timer has just expired.
PAGE 487
ASAI-EPT Aux Data ASAI Link State Error 102 13-restarting No response to RESTART message 104 13-restarting Invalid response to RESTART message 152 13-restarted No response to layer-3 query 154 13-restarted Invalid response to layer-3 query 202 13-established No response to layer-3 query 204 13-established Invalid response to layer-3 query See Maintenance SAT Commands in Maintenance Commands Reference (03-300191) for an explanation of the ASAI link states.
PAGE 488
Communication Manager Maintenance-Object Repair Procedures h. Error Type 2562 - 2566: the ASAI message is not transmitted because the transmit buffer for the ASAI link is full, causing the link to be flow-controlled. Frequent or persistent occurrence of these events may indicate a hardware problem or traffic overload on the PKT-CTRL, the signaling link, or the ASAI adjunct. Follow the repair procedures issued by the manufacturer of the adjunct.
PAGE 489
ASAI-EPT Table 147: ASAI cause values Code Explanation Recommendation 0 Unrecognized ASAI Protocol Operation. Requested ASAI protocol is not implemented by switch or adjunct. Aux Data field of error log entry contains protocol identifier for unrecognized operation. 1. Consult switch and adjunct documentation to determine which set of operations is supported by switch and the adjunct. Turning off adjunct operations not implemented by the switch may resolve the problem.
PAGE 490
Communication Manager Maintenance-Object Repair Procedures Table 147: ASAI cause values (continued) Code Explanation Recommendation 50 Requested facility not subscribed Requested facility is implemented, but not administered. Potential administration problem with endpoint or adjunct. For BRI endpoints: 1. Verify the switch administration of endpoint using display station or display data-module. 2.
PAGE 491
ASAI-EPT Table 147: ASAI cause values (continued) Code Explanation Recommendation 69 Requested facility not implemented Requested service not supported in switch or endpoint. Service or option not implemented Requested service or option (or combination of selected options) is not supported (implemented) in switch or the adjunct. Invalid CRV An invalid CRV was sent by the adjunct. 79 81 1. Consult switch and endpoint documentation to determine service support. 1.
PAGE 492
Communication Manager Maintenance-Object Repair Procedures Signaling Link Status Test (#626) This test determines the current status of the signaling link. This test passes if the link is “bound” to an endpoint and fails if the link is “not bound.” The definition of the term “bound” for a link depends upon the type of endpoint and may depend on the successful completion of procedures at both Layers 2 and 3 of the protocol.
PAGE 493
ASAI-EPT Table 148: Test #626 Signaling Link Status Test (continued) Error Code Test Result Description / Recommendation 1113 FAIL The signaling link is not “bound” to the adjunct. For ASAI adjuncts this error indicates that the link is disconnected at Layer 2. Since the signaling link associated with the endpoint has been identified by administration, the link is only “unbound” from the endpoint when it is disconnected. 1. Execute status bri-port location and see BRI-PORT (ISDN-BRI Port) on page 685.
PAGE 494
Communication Manager Maintenance-Object Repair Procedures ASAI-PT S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ASAI-PT MAJ1,2 test port location l ASAI ISDN BRI port ASAI-PT WRN test port location l ASAI ISDN BRI port 1. The alarm level for ASAI adjunct ports may be administered using set options. The alarm level can be set independently for on- and off-board alarms toWARNING, MINOR, or MAJOR for every ASAI adjunct port in the system. 2.
PAGE 495
ASAI-PT Error Log Entries and Test to Clear Values Table 149: ASAI-PT Error Log Entries Error Type Aux Data Associated Test Alarm Level ASAIPORT On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) (a) Level 1 Status inquiry (#621) MAJ1 OFF test port location sh r 2 513 (c) 0 none (b) ON 1537 (d) 46210 CRC Error counter (#623) MAJ1 OFF 3841 (e) 46208 None 3844 (f) 46223 None 3845 (g) 46211 None 3846 (h) TEI None 1.
PAGE 496
Communication Manager Maintenance-Object Repair Procedures c. Error Type 513: The circuit pack is having problems transmitting data to the packet bus, thus affecting the conveyance of signaling information over the D channel. This error occurs when the packet bus transmit FIFO buffer overflows. This condition probably indicates a hardware problem as well. The ASAI-PORT alarm level is MAJOR with aux data 0.
PAGE 497
ASAI-PT System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the ASAI Port Local LAN Looparound test (#618), you may also clear errors generated from other tests in the testing sequence.
PAGE 498
Communication Manager Maintenance-Object Repair Procedures Figure 24: BRI Port Local LAN Loop-Around Path PACKET INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PACKET BUS BRI LINE CIRCUIT PACK Table 151: Test #618 BRI Port Local LAN Looparound Error Code Test Result Description / Recommendation 1015 ABRT The port is not in the out-of-service state. 1.
PAGE 499
ASAI-PT Table 151: Test #618 BRI Port Local LAN Looparound (continued) Error Code Test Result Description / Recommendation 1139 ABRT The PN’s packet bus is out-of-service. 1. Follow the repair procedures for the packet bus. 2. After completing step 1, execute test port long location and review the results of the BRI Port Local LAN Looparound test to verify the repair. 1141 ABRT The PKT-CTRL is out-of-service. 1. Follow the repair procedures for the PKT-CTRL. 2.
PAGE 500
Communication Manager Maintenance-Object Repair Procedures The Deactivated state indicates a problem with the ASAI circuit pack. When in this state, the Level 1 interface is idle and is not trying to communicate with the BRI endpoints or adjunct. When an ASAI port is placed in the out-of-service state, Level 1 is also put into the deactivated state. This could be due either to the system detecting a fault with the port or in response to a busyout port location request.
PAGE 501
ASAI-PT Table 152: Test #621 Level 1 Status Inquiry (continued) Error Code Test Result Description / Recommendation 3 FAIL Received a status of Level 1 Deactivated; the port is out of service. 1. Enter status bri-port location to verify that the service state of the port is out-of-service. If the port is not out of service, escalate the problem, or else proceed to step 2. 2. If the port has been placed out-of-service using busyout port location, use release port location.
PAGE 502
Communication Manager Maintenance-Object Repair Procedures Table 153: Test #623 CRC Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT Response 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 using busyout board location and reset board location. 2. If the test aborts again, replace the circuit pack. ! CAUTION: CAUTION: 2012 ABRT Do not leave the circuit pack busied out.
PAGE 503
ASAI-PT Table 154: Test #624 Layer 1 Transmission Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT Response 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 using busyout board location and reset board location. 2. If the test aborts again, replace the circuit pack. 2012 ABRT Internal system error 2100 ABRT Could not allocate necessary system resources to run test. 1.
PAGE 504
Communication Manager Maintenance-Object Repair Procedures Table 155: Test #625 Receive FIFO Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT Response 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 using busyout board location and reset board location. 2. If the test aborts again, replace the circuit pack.
PAGE 505
ASAI-PT Clear Error Counters Test (#270) There are various error counters associated with each ASAI-PT. This test clears those counters and triggers the auditing of layer-3 reinitialization. This test is used only to send messages to the ASAI-PT and should not abort nor fail. ASAI uses a fixed TEI value of 1. Table 156: Test #270 Clear Error Counters Error Code Test Result Description / Recommendation Any ABRT This test should never abort. Any FAIL This test should never fail. 1.
PAGE 506
Communication Manager Maintenance-Object Repair Procedures ASAI-RES (TN800 reserve slot) Error log entries and tests also apply to E-DIG-RES. S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ASAI-RES NONE NONE TN800 ASAI reserve slot E-DIG-RE NONE NONE TN800 DIG reserve slot There are no tests associated with these MOs. Both the test board and busyout board commands abort when either is attempted on a reserved slot.
PAGE 507
ATM-BCH (ATM B-Channel Trunk) ATM-BCH (ATM B-Channel Trunk) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-BCH MAJ1 test port location l ATM B-Channel Trunk ATM-BCH MIN test port location l ATM B-Channel Trunk ATM-BCH WRN test port location sh ATM B-Channel Trunk 1. A MAJOR alarm on a trunk means that alarms on these trunks are not downgraded by set options, and at least 75% of the trunks in this trunk group are alarmed.
PAGE 508
Communication Manager Maintenance-Object Repair Procedures B-Channel Service States The ISDN specification defines two service state categories for B channels as listed in Table 157: ATM ISDN service states on page 508. Table 157: ATM ISDN service states Category Description Service states In-Service (INS) B channel is in normal operating state Active A call is connected over the B channel. Idle There is no call on the B channel.
PAGE 509
ATM-BCH (ATM B-Channel Trunk) B-Channel Alarms The Maintenance/Far-End and Out-Of-Service/Far-End states generate warning alarms displayed with status trunk grp#/mem#. Table 158: ATM-BCH alarms by service state Service state Alarm1 Possible cause Possible solution Out-of-Service/NE WRN Trunk busied out Release the port (release trunk grp#/mem#). MIN NPE Crosstalk test (#6) failed Replace ATM circuit pack. None ATM circuit pack lost signal or there is a circuit pack problem.
PAGE 510
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 159: ATM-BCH Error Log entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location 1(b) Any None test port location 18 0 busyout trunk grp/ mbr release trunk grp/mbr None 129 (c) WRN OFF 130 (d) test port location test port location 257(e) Any Service State Audit test (#256) 513(f) Any None 769(g) Any
PAGE 511
ATM-BCH (ATM B-Channel Trunk) ● Outgoing call renegotiated by the far end to another B channel in the absence of SETUP message glare ● Near end attempted a call on a B channel that the far end has marked OOS When running the short test sequence, pay close attention to the results of the Call State Audit test (#257). c. Error Type 129: the far-end switch changed its ISDN service state to either out-of-service or maintenance.
PAGE 512
Communication Manager Maintenance-Object Repair Procedures i. Error Type 3073: Service State Audit attempt failed. See Service State Audit Test (#256) on page 514. Calls can be received but not placed until the test passes and the trunk state returns to In-Service. 1. Check the trunk’s status (status trunk grp#/mem#). j. Error Type 3585: ISDN RESTART message received. Active calls have been dropped.
PAGE 513
ATM-BCH (ATM B-Channel Trunk) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. When you clear one of the error codes associated with a given test, you clear errors generated by other tests in the testing sequence.
PAGE 514
Communication Manager Maintenance-Object Repair Procedures Table 161: Test #255 Signaling Link State Audit Test (continued) Error Code Test Result Description / Recommendation 4 FAIL Signaling channel problem 1. Look for errors or alarms against ATM-SGRP (ATM Signaling Group) on page 598 and ATM-DCH (ATM D-Channel Port) on page 522. 8 FAIL TN230x circuit pack failed 1. See ATM-INTF (TN2305/6) on page 573. PASS Signaling link OK.
PAGE 515
ATM-BCH (ATM B-Channel Trunk) Table 162: Test #256 Service State Audit Test Error Code Test Result Description / Recommendation 1000 ABRT Needed resources not available, port on a call or initializing 1. Run status trunk grp#/mem#. 2. Check the results of Test #255. 1018 ABRT Maintenance disabled 1. Enable maintenance by entering y in the Maintenance Tests field on the change trunk-group screen. 1113 ABRT Signaling link failed 1. Run status trunk grp#/mem#. 2. Check the results of Test #255. 3.
PAGE 516
Communication Manager Maintenance-Object Repair Procedures Call State Audit Test (#257) This test audits the internal call state by asking the far-end switch for the ISDN call state. The test is particularly useful when you are trying to clear a hung call. If the internal call state on the near end differs from that on the far end, the call is torn down. The ISDN specification allows up to 2 minutes for a reply.
PAGE 517
ATM-BCH (ATM B-Channel Trunk) ISDN Test Call Test (#258) This nondestructive test performs a far-end loop-around test over an ATM-BCH trunk if: ● The trunk is IN-SERVICE, MAINTENANCE/NEAR-END, or OUT-OF-SERVICE/ NEAR-END. ● No calls are active on the trunk. ● The system uses country protocol 1 (including US), or the far end has loop-around capability. The test sets up a call to a far-end switch over the ATM-BCH trunk.
PAGE 518
Communication Manager Maintenance-Object Repair Procedures Table 164: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test call disabled 1. Set the Maintenance field on the Trunk Group screen to y. 1020 ABRT TN230x circuit-pack problem 1. See ATM-INTF (TN2305/6) on page 573. 1024 ABRT Maintenance/Test digital port active 1. Wait until amber and green LEDs on the Maintenance/Test circuit pack are OFF. 2. Rerun the test. 3.
PAGE 519
ATM-BCH (ATM B-Channel Trunk) Table 164: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1120 ABRT Trunk OUT-OF-SERVICE/FAR-END 3. Try to change the service state via Test #256 (Service State Audit test). 4. Try the test again. 1122 ABRT No test-line number for the far-end switch 1. Check the Trunk Group screen. 1123 ABRT No Feature Access Code administration for this Facility test 1. Check the Dial Plan and Feature Administration forms.
PAGE 520
Communication Manager Maintenance-Object Repair Procedures Table 164: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2074 ABRT Bit and Block Error query failed 1. Retry the command up to 5 times at 1-minute intervals. 2. If the test continues to abort, there may be a serious internal problem in the Maintenance/Test Digital port. See M/T-DIG (Maintenance/Test Digital Port) on page 1709. 2075 ABRT Internal system error 1.
PAGE 521
ATM-BCH (ATM B-Channel Trunk) Table 164: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2220 ABRT Call terminated prematurely 1. Wait 1 minute, and try again. 2221 – 2226 ABRT 2227 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. Could not allocate needed resources 1. Retry the command at 1-minute intervals up to 5 times. 2042 FAIL Test data corrupt PASS Test pattern intact.
PAGE 522
Communication Manager Maintenance-Object Repair Procedures ATM-DCH (ATM D-Channel Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-DCH MIN test port location l ATM D-Channel ATM-DCH WRN test port location sh ATM D-Channel Note: TN230x circuit packs are not interchangeable. Always replace an ATM circuit pack with the same type. Note: ATM-DCH uses the existing ISDN-PLK or D-channel maintenance strategy with modifications.
PAGE 523
ATM-DCH (ATM D-Channel Port) Hardware Error Log Entries and Test to Clear Values Table 165: ATM D-channel Error Log entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location 18 (b) 0 busyout port location WRN OFF release port location 130 (c) None WRN ON test port location 1793 (d) Signaling Link Board check (#643) test board location l Notes: a. Error Type 0: Run the short test sequence first.
PAGE 524
Communication Manager Maintenance-Object Repair Procedures Signaling Link Board Check (#643) This nondestructive test checks the health of the ATM TN230X trunk circuit pack’s hardware. The test runs on a periodic or scheduled basis, during initialization testing, and upon demand. Note: The board-level maintenance is handled independently of the ATM-CES signaling link maintenance, raising the possibility of inconsistent states.
PAGE 525
ATM-EI (Expansion Interface Circuit Pack) ATM-EI (Expansion Interface Circuit Pack) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-EI MAJ test board location ATM Expansion Interface circuit pack ATM-EI MIN test board location ATM Expansion Interface circuit pack ATM-EI WRN test board location ATM Expansion Interface circuit pack ATM-EI covers the ATM circuit pack administered as an Expansion Interface (ATM-EI) for ATM Port-Network Connectivity (ATM PNC
PAGE 526
Communication Manager Maintenance-Object Repair Procedures LEDs The ATM Interface circuit pack has three LEDs: ● Red indicates some alarm condition. ● Green indicates maintenance testing in progress. ● Amber provides useful visual information regarding the operating mode of the ATM-EI and possible error conditions. The possible LED states are in Table 168.
PAGE 527
ATM-EI (Expansion Interface Circuit Pack) ATM-EI-Related Commands The following commands can be helpful in resolving ATM-EI problems: add atm pnc list measurements atm busyout/release atm pnc remove atm pnc busyout/release board reset board change atm pnc (pnc duplication) status atm pnc display atm pnc status cabinet list atm oam-statistics status port-network list atm pnc test board Replacing an ATM-EI Circuit Pack Standard Reliability 1.
PAGE 528
Communication Manager Maintenance-Object Repair Procedures Critical Reliability There are 2 ATM-EI circuit packs in each PN. 1. Enter status pnc at the SAT. If the board is on the active side, enter reset pnc interchange to switch the active ATM-EI board to the standby side. 2. Enter busyout pnc-standby. 3. Enter busyout atm pnc # a-pnc or b-pnc. 4. Replace the circuit pack. 5. Enter release atm pnc #. 6. Enter release pnc-standby. 7. Wait 2½ minutes for board insertion. 8.
PAGE 529
ATM-EI (Expansion Interface Circuit Pack) 3. Enter add atm pnc n (connection number), and administer the circuit pack location and ATM address. 4. Enter change system-parameters duplication, and change the Enable Operation of PNC Duplication field to y. Removing ATM PNC Connections Standard, Duplex or High Reliability Note: Note: These systems are not equipped with PNC duplication. 1. Enter busyout atm pnc n (connection number). 2. Enter remove atm pnc n (connection number). Critical Reliability 1.
PAGE 530
Communication Manager Maintenance-Object Repair Procedures B-side ATM-EI—Critical Reliability 1. Enter status pnc, and ensure that the A-PNC is active. If not, request a pnc interchange using reset pnc interchange. 2. Enter busyout pnc-standby. 3. Enter list config carrier, and verify that an ATM circuit pack is assigned for the new location. If not, add the ATM circuit pack’s translations. 4. Enter busyout atm pnc n (connection number) b-pnc. 5.
PAGE 531
ATM-EI (Expansion Interface Circuit Pack) Table 169: ATM-EI Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 513 (h) Any ATM Crosstalk test (#1298) MIN ON test board long location 769 (i) 34 35 ATM Board Error Query (1259) WRN OFF test board location 770 (i) 31 ATM Board Error Query (#1259) WRN OFF test board location 771 (i) 26 ATM Board Error Query (#1259) WRN OFF test board location 1024– 1151 (j) Any None WRN
PAGE 532
Communication Manager Maintenance-Object Repair Procedures Table 169: ATM-EI Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 3585 (u) ATM Framer Looparound (#1260) MAJ ON test board location l 3586 (u) ATM Framer Looparound (#1260) MAJ ON test board location l 3841 (v) 3842 (w) None 3843 (x) 3999 (y) Any None Any (z) 32767 None 3 of 3 Notes: a. Error Type 0: Run the short test sequence first.
PAGE 533
ATM-EI (Expansion Interface Circuit Pack) f. Error Type 131: An ATM-EI circuit pack has been removed from the slot for 5 minutes. 1. Insert the ATM-EI circuit pack into its administered slot. 2. Another way to resolve or prevent this alarm is to remove the ATM-EI administration (see Basic ATM PNC Administration on page 528), then remove the ATM-INTF administration (change circuit-pack). It is possible that the ATM-EI could be held in reset by the PN’s Maintenance board and is not inserted in the system. 3.
PAGE 534
Communication Manager Maintenance-Object Repair Procedures ● Some other ATM-EI board is not receiving the cells properly. ● The intervening ATM switch is dropping the ATM cells due to a shortage of bandwidth, or S8700 MC is using more than the subscribed bandwidth. Error Type 771: The ATM switch is sending cells with unknown VPI and VCI address (wrong connection). 1. Ensure that the ATM-EI board address on the ATM switch matches the ATM-EI (ATM) address on the S8700 Multi-Connect side. j.
PAGE 535
ATM-EI (Expansion Interface Circuit Pack) Table 170: ATM Error Types 1024 - 1151 (continued) Error Type Description General problem 1088 1104 ATM-EI circuit pack received a request with an invalid connection identifier. 1089 1105 ATM-EI circuit pack received a request with a reference to an unknown VC token. 1090 1106 ATM-EI circuit pack did not have enough resources (memory) for the requested operation. 1091 1107 Internal failure in the local protocol stack.
PAGE 536
Communication Manager Maintenance-Object Repair Procedures Table 170: ATM Error Types 1024 - 1151 (continued) Error Type Description General problem 1113 Problems detected by the board terminating the connection 3 of 3 1. Test the ATM-EI circuit pack (test board location) and investigate further based on each test’s results. If every test passes, the error was a transient problem.
PAGE 537
ATM-EI (Expansion Interface Circuit Pack) Table 171: Error Type 1024-1151 Aux Data values (XXYYY) converted to slot number Slot Carrier A B C D E Failure type Failure type Failure type Failure type Failure type Slot # Set up Add Party WSP Set up Set up Add Party WSP Set up Set up Add Party WSP Set up Set up Add Party WSP Set up Set up Add Party WSP Set up 8 59 559 859 73 573 873 105 605 905 41 541 841 09 509 809 9 60 560 860 74 574 874 106 606 906 42 54
PAGE 538
Communication Manager Maintenance-Object Repair Procedures l. Error Type 1281: The loss of high-level signal indicating operational problems of equipment located outside of the circuit pack and the fiber connected to the board. Aux Data values are listed in Table 172: Error type 1281 Aux Data and repair procedures on page 538.
PAGE 539
ATM-EI (Expansion Interface Circuit Pack) Table 172: Error type 1281 Aux Data and repair procedures (continued) Aux Data Alarm Description Repair procedure 19 Multiplexer Section Remote Defect Indicator: MS_RDI The far end is detecting a major problem with the signal that this board is transmitting. 1. Make sure the ATM switch port (or a MUX port, if present between ATM switch and the ATM-EI board) is the same as the ATM-EI circuit pack’s cable interface. 2. Run test board location. 3.
PAGE 540
Communication Manager Maintenance-Object Repair Procedures Table 172: Error type 1281 Aux Data and repair procedures (continued) Aux Data Alarm Description Repair procedure 23 High-level path Remote defect Indicator: HP_RDI The far end is detecting a major problem with the signal that this board is transmitting. The transmitted payload is invalid. 1.
PAGE 541
ATM-EI (Expansion Interface Circuit Pack) o. Error Type 1793: LANHO transmit FIFO overflow error (the transmit FIFO RAM buffers on the circuit pack overflowed). This most likely indicates a hardware problem on the circuit pack, because the speed of the LAN/packet bus is much higher than the speed of the link connected to the port. 1. Test this ATM-EI circuit pack (test board location). 2. If Test #598 fails again, replace the ATM-EI circuit pack. p.
PAGE 542
Communication Manager Maintenance-Object Repair Procedures t. Error Type 3329: The on-board LANHO chip is insane, possibly due to a problem in packet-bus arbitration, the transmission line frame, or the circuit pack itself. The circuit pack cannot talk to the packet bus. If the packet bus is alarmed: 1. Resolve any PKT-BUS errors. The probability of this error being related to a packet-bus problem increases with the number of other circuit packs using the bus that are also showing this error.
PAGE 543
ATM-EI (Expansion Interface Circuit Pack) 1. If the system has duplicated PNC: a. Test the ATM-EI (test board location l). b. If Error 3585 is detected again, or if the board is not recognized anymore, replace the ATM-EI circuit pack. 2. If the system does not have duplicated PNC and the circuit pack is in a PN: a. Replace the ATM-EI circuit pack. Error Type 3586: Framer Looparound test (#1260) failed.
PAGE 544
Communication Manager Maintenance-Object Repair Procedures z. Aux Data 32767 for any error log entry indicates that an alarmed ATM-EI was busied out and then released. When this occurs, existing service-affecting alarms must be preserved. Typically, every alarm is resolved when the ATM-EI is released. Therefore, the Alarm and Error Logs must be repopulated with the alarms present at time of busyout.
PAGE 545
ATM-EI (Expansion Interface Circuit Pack) Expansion Interface 2-Way Transmission Test (#241) This test is nondestructive and applies to every ATM-EI, both active and standby. It is run as part of craft short and long testing, periodic, scheduled, initialization, and error analysis testing. The test sets up a connection between a Tone-Clock in one cabinet and a Tone Detector in a separate cabinet and transmits a digital test count between the PNs.
PAGE 546
Communication Manager Maintenance-Object Repair Procedures Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors. 2. Verify that at least one Tone Detector resides in this PN.
PAGE 547
ATM-EI (Expansion Interface Circuit Pack) Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 1033 ABRT The test cannot run because either the ATM-EI board is not administered, or there were no other PNs administered that had its ATM-EI board in-service. 1. Ensure that the board is administered as ATM PNC Expansion Interface circuit pack. 2.
PAGE 548
Communication Manager Maintenance-Object Repair Procedures Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 1395 ABRT This test cannot run on an ATM-EI circuit pack if it is part of the B-side PNC and Duplicated PNC is not enabled. 1. If this test needs to run on this ATM-EI circuit pack, enable PNC with the change system-parameters duplication command. 2.
PAGE 549
ATM-EI (Expansion Interface Circuit Pack) Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 10MM FAIL The failure codes only apply to a system equipped with an ATM Switch. The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end ATM-EI under test.
PAGE 550
Communication Manager Maintenance-Object Repair Procedures Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 20MM FAIL The failure codes only apply to a system equipped with an ATM Switch. The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end ATM-EI under test. 6.
PAGE 551
ATM-EI (Expansion Interface Circuit Pack) Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 30MM FAIL The failure codes only apply to a system equipped with an ATM Switch. The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end ATM-EI under test.
PAGE 552
Communication Manager Maintenance-Object Repair Procedures Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued) Error Code Test Result Description / Recommendation 40MM FAIL Failure code only applies to a system equipped with an ATM Switch. The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end ATM-EI under test.
PAGE 553
ATM-EI (Expansion Interface Circuit Pack) Expansion Interface Lock Query Test (#304) This test is nondestructive and is used to query the ATM and EI circuit packs (both active and standby) for its status concerning lock to the backplane system clock. It is run as part of periodic, scheduled, initialization, and error analysis testing. When an in-line, “out-of-lock” report comes in, this test is run to check the circuit pack’s status. The ATM-EI responds with “in lock” or “out of lock.
PAGE 554
Communication Manager Maintenance-Object Repair Procedures Table 175: Test #304 Expansion Interface Lock Query Test (#304) (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check the error log for wrong board (error 125) or no board (error 131). Resolve either of these issues. 2. Check that the board is properly translated and inserted. If so, check for hyperactivity (error 1538). If hyperactive, use reset board location. 3.
PAGE 555
ATM-EI (Expansion Interface Circuit Pack) Table 176: Expansion Interface Control Channel Test #316 (continued) Error Code Test Result Description / Recommendation FAIL A PN’s unduplicated ATM-EI circuit pack responded incorrectly, or a PN’s active ATM-EI circuit pack could not communicate with the PN’s circuit packs. 1. If the PN’s active ATM-EI circuit pack is failing and duplicated PNC is enabled: a. Enter reset PNC interchange to switch to the standby PNC. b. Repeat the short test sequence. c.
PAGE 556
Communication Manager Maintenance-Object Repair Procedures The Packet Interface Looparound test checks the packet-bus interface circuitry on this board. The on-board LANHO chip sends a data stream to the bus, retrieves it back, and checks for its consistency. If the data is consistent, the test passes; otherwise, it fails. The test aborts if the specified PN’s packet bus has an active minor alarm or is out of service.
PAGE 557
ATM-EI (Expansion Interface Circuit Pack) ATM Board Error Query Test (#1259) This test is nondestructive. The ATM circuit pack firmware maintains counters for some of the on- and off-board errors. The maintenance software queries the board for its health information to do error analysis. These alarms have assigned priority: if a higher priority alarm occurs, the remaining alarms are not reported to the software (through the inline errors), avoiding unnecessary up-link, in-line error message traffic.
PAGE 558
Communication Manager Maintenance-Object Repair Procedures Table 179: XX Error Codes, Test #1259 (ATM Board Error Query Test) XX Aux Data Description 1 ATM framer chip failed 2 NCE chip failed 3 LANHO critical error 4 TDM Prog.
PAGE 559
ATM-EI (Expansion Interface Circuit Pack) Table 180: YY Error Codes, Test #1259 (ATM Board Error Query Test) YY Aux Data Description 15 Backplane clock failed 16 Loss of signal 17 Loss of frame 18 Multiplexer Section Alarm indication signal error 19 Multiplexer Section remote defect indicator error 20 Loss of pointer 21 Path signal level mismatch 22 High level path alarm indication signal 23 High level path remote defect indicator 24 Loss of cell delineation 25 Uncorrectable headers
PAGE 560
Communication Manager Maintenance-Object Repair Procedures ATM Board Framer Loop-Around Test (#1260) This test is destructive. Note: This test can be run on the standby PNC only if the board is busied out. Note: This test places the ATM circuit pack in ATM framer loop-around mode. Once the board receives this message, it creates a dummy virtual circuit that originates and ends on the same board, without leaving the board. This test verifies both the TDM path and the Packet Path.
PAGE 561
ATM-EI (Expansion Interface Circuit Pack) Figure 28: ATM Board Framer Loop-Around Test (#1260) (non-EAA, Packet Path) ATM circuit pack TDM bus (EPN X) Tone clock Tone detector ATM framer looped PNC mode Packet bus (PPN) ATM circuit pack ATM circuit pack Packet interface ATM switch PNC mode ATM expansion archangel PNC mode Packet bus (EPN X) iodfpak AWF 040699 Table 181: ATM Board Framer Loop-Around Test (#1260) Error Code Test Result Description / Recommendation 1002 ABRT The system could no
PAGE 562
Communication Manager Maintenance-Object Repair Procedures Table 181: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 1015 ABRT The ATM-EI circuit pack has not been busied out. 1. Busyout the ATM-Expansion Interface circuit pack, then repeat test board location long . 1031 ABRT If the ATM Expansion Interface circuit pack is in a PN and is on the active PNC, this test cannot be executed. 1.
PAGE 563
ATM-EI (Expansion Interface Circuit Pack) Table 181: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 1407 ABRT This test cannot be run on an ATM-EI board that is on the active PNC because it cannot be busied out. This error code indicates that PNC duplication is enabled. 1. Attempt to perform a PNC interchange with the reset pnc interchange command. 2.
PAGE 564
Communication Manager Maintenance-Object Repair Procedures Table 181: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 2 FAIL The test tone was transmitted and detected correctly, but the correct data packet was not detected by the Packet Interface circuit pack. 1. Test the Packet Interface circuit pack to verify that it is functioning properly. If any tests fail, investigate those tests and repair the Packet Interface circuit pack. 2.
PAGE 565
ATM-EI (Expansion Interface Circuit Pack) Table 181: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code 0 Test Result Description / Recommendation PASS The ATM-EI board is functioning properly, however this test does not verify that the optical portion of the lightwave transceiver is functioning. NO BOARD No board was detected by the test. 1. Resolve either wrong board (Error 125) or no board (Error 131) issues, if applicable. 2.
PAGE 566
Communication Manager Maintenance-Object Repair Procedures Table 182: ATM Board Time Of Day Update (#1261) (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board detected. 1. Resolve either wrong board (Error 125) or no board (Error 131) issues, if applicable. 2. Check that the board is properly translated and inserted. If so, check for hyperactivity (Error 1538). If hyperactive, use reset board location. 3. Run the test again.
PAGE 567
ATM-EI (Expansion Interface Circuit Pack) Table 183: ATM Board Reset (#1256) (continued) Error Code Test Result Description / Recommendation None ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort escalate the problem. 2000 ABRT Did not receive the SANITY response in the given time. 1. Wait for 5 minutes and see if board is visible to the system by using list config all. 2.
PAGE 568
Communication Manager Maintenance-Object Repair Procedures ATM Cross Talk Test (#1298) This test is nondestructive. The ATM board Cross Talk test verifies that the selected TDM bus time slot never crosses over to time slots reserved for other connections. The test also checks for cross connections, where the board talks to time slots other than those specified. Since this test uses many system resources (TDM time slots, Tone Generator, Tone Detector, and others), it runs as a part of demand test only.
PAGE 569
ATM-EI (Expansion Interface Circuit Pack) Table 184: ATM Crosstalk Test (#1298) (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors in the Error Log. 2. Resolve any TONE-PT errors in the Error Log. 3.
PAGE 570
Communication Manager Maintenance-Object Repair Procedures ATM Board DSP Test (#1293) This test is nondestructive and is designed to test the board’s interface to the TDM bus and the functions of all 24 on-board DSPs (Digital Signal Processors). There are three functional types of DSPs: ● talkers – put data on the TDM bus ● listeners – take data off the TDM bus ● echo cancelers – as implied Listener and echo cancelers are tightly coupled because firmware allocates sets of DSPs.
PAGE 571
ATM-EI (Expansion Interface Circuit Pack) Table 185: ATM Board DSP Test (#1293) (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Verify that at least one Tone Detector resides in this PN. (Even without a TTR-LEV error, the tested circuit pack’s PN could be missing a Tone Detector.
PAGE 572
Communication Manager Maintenance-Object Repair Procedures Table 185: ATM Board DSP Test (#1293) (continued) Error Code Test Result Description / Recommendation XYZ FAIL A device on the circuit pack is failing. There is at least one bad DSP on the board. Values are as follows: ● The X value indicates the number of talker DSPs ● Y indicates the number of listener DSPs ● Z indicates the number of Echo Canceler DSPs that have failed the test. 1.
PAGE 573
ATM-INTF (TN2305/6) ATM-INTF (TN2305/6) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-INTF WRN test board location ATM interface board The system recognizes a TN2305/6 as an ATM interface board (ATM-INTF) unless it has an assigned personality (add atm pnc or add atm trunk).
PAGE 574
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 23: The ATM expansion interface circuit pack is administered through a change circuit-pack command, but has not been inserted into the system. Insert the circuit pack. b. Error Type 125: A wrong circuit pack is located in the slot where this circuit pack is logically administered. To resolve this problem either remove the wrong circuit pack or insert the logically-administered circuit pack. c.
PAGE 575
ATM-INTF (TN2305/6) Table 188: Test #52: Control Channel Loop-Around (continued) Error Code Test Result Description / Recommendation FAIL The circuit pack failed to return the circuit pack code or vintage. 1. Retry the command up to 5 times. 2. If the problem continues, reset the circuit pack. 3. Retry the command up to 5 times. Any PASS Communication with this circuit pack is successful. NO BOARD This is normal if the test is being executed when: 1. The board is not physically in the system. 2.
PAGE 576
Communication Manager Maintenance-Object Repair Procedures ATM-NTWK (ATM Network Error) S8700 MC MO Name in Alarm Log Physical Name in Error Log1 Alarm Level Full Name of MO ATM-NTWK ATUUP WRN ATM Network Error ATM-NTWK location WRN ATM Network Error 1. AT indicates it is an ATM switch-related address, UU is the connection number. The connection number can be converted into a board location with display atm pnc UU, which shows the translations for the board that reported the ATM network error.
PAGE 577
ATM-NTWK (ATM Network Error) If the ATM-NTWK MO receives more than 6 errors, the most recent are discarded. Table 189: Error codes and Aux Data values ATM-NTWK Cause Code/ Error Type Aux Data Cause Codes Description NORMAL EVENTS 0 (a) Network unreachable 1 (a) Unallocated (unassigned) number. This cause indicates that the called party cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated). 2 (a) No route to specified transit network.
PAGE 578
Communication Manager Maintenance-Object Repair Procedures Table 189: Error codes and Aux Data values ATM-NTWK (continued) Cause Code/ Error Type Aux Data Cause Codes Description 21 (a) Call rejected. This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.
PAGE 579
ATM-NTWK (ATM Network Error) Table 189: Error codes and Aux Data values ATM-NTWK (continued) Cause Code/ Error Type Aux Data Cause Codes Description 37 (a) User Cell Rate not available 38 (a) Network out of order. This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long time. (Immediately retrying the call is unlikely to succeed.) 41 (a) Temporary failure.
PAGE 580
Communication Manager Maintenance-Object Repair Procedures Table 189: Error codes and Aux Data values ATM-NTWK (continued) Cause Code/ Error Type Aux Data Cause Codes Description 78 (a) AAL parameters cannot be supported. INVALID MESSAGES 81 (a) Invalid call reference value. This cause indicates that its sending equipment received a message with a call reference that is currently inactive on the user-network interface. 82 (a) Identified channel does not exist.
PAGE 581
ATM-NTWK (ATM Network Error) Table 189: Error codes and Aux Data values ATM-NTWK (continued) Cause Code/ Error Type Aux Data Cause Codes Description 99 (a) Information element (IE) either non-existent or not implemented. This cause indicates that its sending equipment received a message with an unrecognized IE, either because the IE’s identifier(s) are undefined, or defined but not implemented by the cause-sending equipment. This cause indicates that its sending equipment discarded the IE.
PAGE 582
Communication Manager Maintenance-Object Repair Procedures Table 189: Error codes and Aux Data values ATM-NTWK (continued) Cause Code/ Error Type Aux Data Cause Codes Description 257 to 300 (b) (b) ATM Impaired Paths 1. Examine the error log (display errors), atm setup-events log (list measurements atm svc-setup), and atm pnc-latency (list measurements atm latency) screens to help diagnose the problem, although the switch could be operating normally.
PAGE 583
ATM-NTWK (ATM Network Error) Notes: a. Aux Data values for Setup and Add Party (XX = port network, YYY = location code). Aux Data values for WSP Setup (XX = WSP number, YYY = location code). Table 190: Location codes from Aux Data values on page 583 is a list of UNI 3.
PAGE 584
Communication Manager Maintenance-Object Repair Procedures d. Error Type 769: ATM CLP (Cell Loss Priority) Bit Errors The ATM cell header has a bit called the cell loss priority (CLP) bit. The bit indicates one of two states: the cell is eligible for discarding, or it is not. In an ATM configuration, every cell is transmitted into the ATM network with the CLP bit set to 0 indicating that these cells are NOT eligible for discarding.
PAGE 585
ATM-NTWK (ATM Network Error) Possible symptoms include audible artifacts in talk paths and failure of modems over voice lines. If cell loss is happening generically in the ATM network, other symptoms like “excessive AAL-5 CRC errors” or “excessive LAP-D retransmissions” are possible on SVCs with Variable Bit Rate (VBRnt) traffic contracts. The VBR SVCs transport system links such as EAL, PACL, and PRI links.
PAGE 586
Communication Manager Maintenance-Object Repair Procedures The “lost cells” error can help you diagnose cell underrun problems. When cell underruns are accompanied by lost cells errors, the lost cells could have caused the underruns. But if you have cell under runs without lost cells, it could indicate that the underruns were due to network jitter instead.
PAGE 587
ATM PNC-DUP (ATM PNC Duplication) ATM PNC-DUP (ATM PNC Duplication) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO PNC-DUP NA status pnc PNC duplication The PNC-DUP MO tracks the health of the active and standby PNCs, controls planned and spontaneous interchanges, and manages related functions such as double call refresh and unrefresh, antithrashing, and so on. The main responsibility of PNC-DUP is to recover the system to full service in the event of a fault.
PAGE 588
Communication Manager Maintenance-Object Repair Procedures PNC-DUP Related Commands Table 191: PNC-DUP Commands on page 588 lists the PNC-DUP related commands and their output forms are fully described in Maintenance SAT Commands in Maintenance Commands Reference (03-300191). Table 191: PNC-DUP Commands Command Description status pnc Shows information about both PNCs’ operational status, including state of health, alarms, busyouts and locks. reset pnc interchange Initiates a demand PNC interchange.
PAGE 589
ATM PNC-DUP (ATM PNC Duplication) Enabling and Removing PNC Duplication To Enable PNC Duplication To enable PNC duplication, perform the following sequence of steps: 1. Enable administration of PNC-DUP on the change system-parameters customer-options screen. 2. Fully administer duplicate ATM PNC connectivity. Verify by list atm pnc. Or for IP duplication, go to step three. 3. Fully administer IPSI duplication (ipserver-interface duplication). Verify by using list ipserver-interface. 4.
PAGE 590
Communication Manager Maintenance-Object Repair Procedures Steady State LEDs The LEDs of PNC components in a stable duplicated system should appear as follows: ● For an active ATM EI (functioning as Archangel) in a PN without IPSIs, its amber LED’s flash pattern is 2 seconds on/200 ms off. ● For a standby ATM EI in a PN without IPSIs, it’s amber LED is off. ● For an active ATM EI in a PN with IPSIs, its amber LED is on steady. ● For an standby ATM EI in a PN with IPSIs, its amber LED is off.
PAGE 591
ATM PNC-DUP (ATM PNC Duplication) PNC State-of-Health Indexes The Inter-PN Index screen the state-of-health vector is used to track and compare the states of health of both PNCs. The fields making up the indexes are 2-digit numbers separated by periods (.), with each field representing a different class of faults. The fault class fields are arranged in order of decreasing importance from left to right.
PAGE 592
Communication Manager Maintenance-Object Repair Procedures Resolving Poor State of Health When both PNCs do not have an all-zero SOH (perfect health), use the following steps to identify and repair the problem. 1. Look for PNC component alarms (major or minor) for the PNC side without an all-zero SOH. The standby PNC should be repaired first. 2. Busy-out the standby PNC. 3. Follow the appropriate diagnostic and repair procedures for the alarmed PNC components just as with a simplex PNC.
PAGE 593
ATM PNC-DUP (ATM PNC Duplication) PNC Interchanges PNC spontaneous interchanges occur when PNC duplication software determines that the standby PNC’s state of health (SOH) surpasses the active PNC’s. ● PNC-DUP executes a spontaneous interchange in response to a message from a PNC component MO indicating that either a fault has occurred on the active PNC or a fault has been resolved on the standby PNC.
PAGE 594
Communication Manager Maintenance-Object Repair Procedures Antithrashing and PNC Interchanges Following a spontaneous PNC interchange, subsequent PNC interchanges are prevented for 5 minutes. This condition is indicated by y in the Interchange Disabled? field of the status pnc screen. After 5 minutes, the antithrashing timer expires, interchange decisions are re-enabled, and the field displays n.
PAGE 595
ATM PNC-DUP (ATM PNC Duplication) ● The global refresh from releasing the standby PNC has completed. ● The standby PNC’s state of health surpasses the active PNC’s. At this point, the faulty component is on the standby PNC, and the PNCs are locked in their current active/standby state. 3. Busyout the PNC with busyout pnc. 4. Use fault isolation and component testing procedures for the individual PNC components, just as for a simplex PNC.
PAGE 596
Communication Manager Maintenance-Object Repair Procedures TDM bus itself. If TDM bus maintenance tests find no problems with the bus, then it is either the port board or the EAA. It may be simpler to replace the port board than to request a PNC interchange. However, if it is not clear which port board may be at fault or maintenance is being performed remotely, verify that the EAA is not at fault by executing a PNC interchange. If the interchange solves the problem, then the EAA is faulty.
PAGE 597
ATM PNC-DUP (ATM PNC Duplication) Table 194: Error Log Encode Field Decoding Field Variable Name Values Description c Alarm Type 0 1 Alarm retired MAJOR or MINOR alarm on any PNC component x Fault class; see description for contributing MOs 0 EAL (Expansion Archangel Link - EXP-PN) carries CCMS messages 1 PACL (ATM-EI) carries ATM signaling commands from Call Processing to the remote ATM-EI circuit packs 2 PNC hardware (providing connectivity of PN-to-PN or -ATM-EI) 5 BFDL (bearer fault de
PAGE 598
Communication Manager Maintenance-Object Repair Procedures ATM-SGRP (ATM Signaling Group) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run1 Full Name of MO ATM-SGRP MIN test sig-group grp# ATM-CES Signaling Group ATM-SGRP WRN test sig-group grp# ATM-CES Signaling Group 1. grp# is the signaling group number (1–166); the test sequence can be either short or long. ATM-SGRP applies when ATM signaling groups have been administered on an ATM circuit pack as ATM trunks.
PAGE 599
ATM-SGRP (ATM Signaling Group) Error Log Entries and Test to Clear Values Table 196: ATM-SGRP Signaling Group Error Log Entries Error Type Aux Data Associated Test Alarm Level 0 0 Any Any 1 (a) Any None On/Off Board Test to Clear Value test sig-group grp# MO busied out 18 (c) 257 (d) Any None test sig-group grp# 769 (e) Any Primary Signaling Link Hardware check (#636) test sig-group grp# 1281 (f) Any Secondary Signaling Link Hardware check (#639) test sig-group grp# 1793 (g) Any
PAGE 600
Communication Manager Maintenance-Object Repair Procedures c. Error Type 18: the ATM circuit pack has been busied out (either busyout atm sig-grp or busyout board location). 1. Release the ATM signaling group (release atm sig-grp) or the circuit pack (release board location). d. Error Type 257: the primary signaling channel connection has been lost for more than 90 seconds. ● The associated B channels are placed in the ISDN Maintenance/Far-End state.
PAGE 601
ATM-SGRP (ATM Signaling Group) h. Error Type 2305: The Remote Layer 3 Query test (#637) failed. A specific message was sent to the far-end switch, and it did not respond within the allotted time. 1. Investigate elements of the ATM D channel(s) (ATM-DCH) for both this switch and the far-end switch. If Test #637 fails twice in a row, the B channels are alarmed and made unavailable for outgoing calls (although incoming calls are still accepted).
PAGE 602
Communication Manager Maintenance-Object Repair Procedures Table 197: Descriptions and repair recommendations (Error Types 3840-3928) (continued) Error Code Description Recommendation 3846 The far-end switch has indicated that the B channel (trunk) is not acceptable for use in the call for which it was requested.
PAGE 603
ATM-SGRP (ATM Signaling Group) Table 197: Descriptions and repair recommendations (Error Types 3840-3928) (continued) Error Code Description Recommendation 3890 A request to use a network service (for example, SDN) has been denied. Administration somewhere in the network has indicated that the requested service has not been subscribed to or purchased for this trunk. This could indicate ● a local administration problem ● a mismatch between the local administration and that of the network provider.
PAGE 604
Communication Manager Maintenance-Object Repair Procedures Table 197: Descriptions and repair recommendations (Error Types 3840-3928) (continued) Error Code Description 3894 Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone. Recommendation 1. Eliminate any transitory state mismatch problems (test port location for the trunk port shown in the Aux Data field). Test #256 (Service State Audit) is the important test in the sequence. 2.
PAGE 605
ATM-SGRP (ATM Signaling Group) Table 197: Descriptions and repair recommendations (Error Types 3840-3928) (continued) Error Code Description Recommendation 3928 A call was denied because of a basic incompatibility between the type of call and either the facilities selected by the routing pattern or the called user itself. This error might be helpful as a clue if the customer complains of receiving unexpected intercept tone after accessing ISDN trunks or PRI endpoints. 1.
PAGE 606
Communication Manager Maintenance-Object Repair Procedures Primary Signaling Link Hardware Check (#636) The ATM-SGRP Signaling Group D-channel port depends on the health of the TN230X interface circuit pack on which it resides. This test fails if there are problems with either the ATM-DCH (D-channel port) MO or the TN230X circuit pack. Investigate the ATM TN230X circuit pack (ATM-TRK) anytime there are problems with the ATM D-channel port (ATM-DCH).
PAGE 607
ATM-SGRP (ATM Signaling Group) Table 200: Test #647 Layer 2 Status Query Test Error Code Test Result Description / Recommendation 1132 ABRT Internal system error. The port location for the D channel is not known. This condition should not be possible since an administered ATM circuit pack must be specified when a Signaling Group is administered: 1. Retry the command at 1-minute intervals up to five times. 1134 ABRT Internal system error. The associated ATM circuit pack is not administered.
PAGE 608
Communication Manager Maintenance-Object Repair Procedures Remote Layer 3 Query (#1291) This test queries the far-end switch or terminal adapter to determine whether the signaling connection is functioning properly at Layer 3. It selects a B channel in the in-service or maintenance service state and sends an ISDN layer-3 SERVice message, which requires a response from the far end (similar to performing Test #256 on an ISDN trunk).
PAGE 609
ATM-SGRP (ATM Signaling Group) Table 201: Test #1291 Remote Layer 3 Query (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2500, none ABRT Internal system error or administration problem 1. Determine whether any B channels are administered. 2.
PAGE 610
Communication Manager Maintenance-Object Repair Procedures ATM-SYNC (ATM Synchronization) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-SYNC MIN display errors ATM Synchronization ATM-SYNC WRN test synchronization ATM Synchronization This section discusses intra-switch synchronization maintenance and the hardware and software components that provide a common reference frequency for reliable digital communications among the G3r system, the ATM switch, and
PAGE 611
ATM-SYNC (ATM Synchronization) Stratum 4 Synchronization Systems may have primary and secondary synchronization references (DS1/UDS1 interface circuit packs or ATM-Switch) when using Stratum 4 synchronization. If the primary synchronization reference in Figure 32: Stratum-4 Synchronization with Unduplicated ATM PNC on page 612 is providing a valid timing signal, then the flow of system synchronization would travel from the DS1 interface circuit pack in the PN to the ATM switch.
PAGE 612
Communication Manager Maintenance-Object Repair Procedures Figure 32: Stratum-4 Synchronization with Unduplicated ATM PNC External T1/E1 primary Clock External T1/E1 secondary ATM switch fabric ATM timing distribution Interface module Interface module Interface module ATM PNC OC3 ATM-EI OC3 DEFINITY EPN DEFINITY PPN Tone clock DS1 DS1 ATM-EI Tone clock DS1 T1-splitter DS1 T1-secondary T1-primary iodfst4 LJK 011998 Note: Note: The TN722 DS1 Interface circuit pack does not provide a synchroni
PAGE 613
ATM-SYNC (ATM Synchronization) ATM-SYNC Commands Use the commands in Table 202 to help troubleshoot ATM-SYNC problems: Table 202: ATM-SYNC commands Command Description change synchronization Allows primary and secondary references to be administered for the Stratum 4 option, or ATM-Switch, indicating that the synchronization references are input directly to the ATM switch status synchronization Shows the current inferred synchronization reference status synchronization Shows the administered primary
PAGE 614
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures. b. Error Type 1: problem with the primary DS1 reference. It is cleared when the primary reference is restored. The following steps should give an indication of the source of the problem: 1.
PAGE 615
ATM-SYNC (ATM Synchronization) 2. Test the active Tone-Clock circuit in the master PN with test tone-clock location long. Check the Error Log for TDM-CLK errors, and verify that TDM Bus Clock Circuit Status Inquiry test (#148) passes successfully. If Test #148 fails with an Error Code 2–32, see TDM-CLK (TDM Bus Clock) on page 2252 to resolve the problem. If not, continue with the following steps. 3.
PAGE 616
Communication Manager Maintenance-Object Repair Procedures Test Synchronization Test (#417) This test updates all the Synchronization Maintenance component circuit packs with the correct information regarding their role in providing synchronization for the system. All the Tone-Clock, ATM Expansion Interface, DS1 Interface, and UDS1 Interface circuit packs in the system are updated through this test. This test either passes or aborts.
PAGE 617
ATM-TRK (Circuit Emulation Service Circuit Pack) ATM-TRK (Circuit Emulation Service Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-TRK MAJ test board location ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK MIN test board location ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK WRN test board location ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK explains how you test and repair TN230x ATM Interface circuit packs (TN23
PAGE 618
Communication Manager Maintenance-Object Repair Procedures Note: TN230x circuit packs are not interchangeable. Note: ATM Circuit Emulation Service Under ATM Circuit Emulation Service (CES), simulate ISDN-PRI circuits by assigning ports to signaling groups. Each signaling group represents a PRI circuit, and the ports in the group represent the D channel and B channels of that circuit.
PAGE 619
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 206: ATM-TRK LED interpretation (continued) LEDs Condition LED status Amber One or more CES signaling groups administered On Amber CES signaling group not administered or not reporting to firmware Off 2 of 2 ATM-TRK-related commands Table 207: ATM CES troubleshooting commands on page 619 lists some commands that can be useful in troubleshooting ATM errors and alarms.
PAGE 620
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 208: ATM-TRK Error Log entries Error Type Aux Data Associated Test Alarm Level 0 0 Any Any None MIN ON 1(a) On/Off Board test board location 18(b) 0 busyout board location MIN ON 23(c) 0 None MIN ON None MIN ON 125(d) Test to Clear Value release board location 257(e) Any Control Channel Loop (#52) MIN ON test board location r 2 513(f) Any ATM Cross Talk (#1298)
PAGE 621
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 208: ATM-TRK Error Log entries (continued) Error Type Aux Data 2818(p) 3330(q) Associated Test Alarm Level On/Off Board Test to Clear Value 1-24 WRN / MIN ON test board location 3 MIN OFF WRN / MIN ON ATM Board Error Query (#1259) 3585(r) 3841(s) Any None 3842(t) 11 None None 3843 (u) 3999(v) test board location l Any None 2 of 2 Notes: a. Error Type 1: the ATM-TRK circuit pack does not appear to be in its assigned slot. 1.
PAGE 622
Communication Manager Maintenance-Object Repair Procedures g. Error Type 769, 770: the ATM switch is requesting too many LAPD retransmissions (off-board ATM cell corruption errors). Error Type Aux Data Description 769 35 Excessive LAPD retransmission requests 770 25 Uncorrectable ATM cell headers – threshold 1. Check the connections between the fiber cable, the ATM-TRK circuit pack, and the ATM switch. 2. See PKT-BUS (Packet Bus) on page 1790 for test and corrective procedures. 3.
PAGE 623
ATM-TRK (Circuit Emulation Service Circuit Pack) h. Error Type 771: the ATM switch is sending cells with unknown Virtual Path-Identifier (VPI) and Virtual Channel-Identifier (VCI) addresses. 1. Make sure that the ATM-TRK circuit-pack address is administered identically on the ATM switch and the S8700 Multi-Connect system. i. Error Type 1281: Board major signals error (loss of high-level signal). The far end has detected a major problem in transmissions originating from the ATM-TRK circuit pack.
PAGE 624
Communication Manager Maintenance-Object Repair Procedures Table 209: Error type 1281 Aux Data and repair procedures (continued) Aux Data Alarm Description Repair procedure 18 Multiplexer Section Alarm Indication Signal: MS_AIS There is a major problem on the far end (between multiplexer section [MUX] and the switch) that prohibits the circuit pack from sending a valid signal. 1. See if the ports at the MUX and/or the ATM switch are connected snugly. 2. Run test board location. 3.
PAGE 625
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 209: Error type 1281 Aux Data and repair procedures (continued) Aux Data Alarm Description Repair procedure 22 High-level Path Alarm Indication Signal: HP_AIS The payload is invalid. 1. Make sure the ATM switch port (or a MUX port, if present between ATM switch and the ATM-TRK board) is the same as the ATM-TRK circuit pack’s cable interface. 2. Run test board location. 3.
PAGE 626
Communication Manager Maintenance-Object Repair Procedures j. Error Type 1537: LANHO bus timeout. The circuit pack is transmitting too many bytes on the LAN bus for a single frame. This can be due to: ● an on-board fault. ● a faulty data received on one of the circuit pack’s external ports. If the error occurs three times in 10 minutes, the board is isolated from the packet bus, and the board is alarmed. To clear the alarm: 1. Restore this circuit pack to the packet bus with this command sequence: a.
PAGE 627
ATM-TRK (Circuit Emulation Service Circuit Pack) 2. Run test board location against the ATM-TRK circuit pack. If Then Test 598 fails. Follow the repair procedures suggested for that test. n. Error Type 2306: too many parity errors in data received from the LAN/packet bus. 1. Run test board location If Then Test 598 fails. Follow the repair procedures suggested for that test. Test 598 passes See PKT-BUS (Packet Bus) and perform the specified repair.
PAGE 628
Communication Manager Maintenance-Object Repair Procedures 2. Follow the repair procedures suggested for Test #1293. Error Type Description 2818 One or more DSPs failed. The Aux Data field contains the ID number of DSP that failed 2817 DSP test failure. The Aux Data field contains the following information about the failed DSPs: X is the number of talker DSPs Y is the number of listener DSPs Z is the number of echo-cancelling DSPs q. Error Type 3330: LANHO critical error.
PAGE 629
ATM-TRK (Circuit Emulation Service Circuit Pack) r. Error Type 3585: Major board alarm; failure of critical components involved in the operation of the circuit pack. The circuit pack has failed, and the switch can no longer recognize it. Aux Data Description 1 ATM framer chip failure 2 NCE failed 4 TDM PLD failed 5 Every DSP on the circuit pack has failed. 6 RNP (Receive Network Processor) failed 7 TNP (Transmit Network Processor) failed 8 MEMORY read/write failure 9 DUART failure 1.
PAGE 630
Communication Manager Maintenance-Object Repair Procedures v. Error Type 3999: circuit pack sent a large number of control channel messages to the switch within a short period of time. If Then Error Type 1538 is also present Circuit pack is taken out of service. Error Type 1538 is absent Circuit pack is not taken out of service, but has generated 50% of the messages necessary to be considered hyperactive. ● This can be normal during heavy traffic.
PAGE 631
ATM-TRK (Circuit Emulation Service Circuit Pack) Connection Audit Test (#50) Nondestructive (in a sane switch environment). The Connection Audit test updates TDM time slots. It sends network-update Control Channel Message Set (CCMS) messages that tell the ATM-TRK circuit pack to listen to, talk to, or disconnect particular time slots. The test passes if software successfully sends the downlink network-update messages. It aborts otherwise.
PAGE 632
Communication Manager Maintenance-Object Repair Procedures Table 211: Test #50 Connection Audit Test (continued) Error Code 0 Test Result Description / Recommendation PASS The circuit pack has been updated with its translation. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check the board translations. 2.
PAGE 633
ATM-TRK (Circuit Emulation Service Circuit Pack) The test passes if the port circuit pack responds. The test aborts if the circuit pack does not respond. The test fails otherwise. Table 212: Control Channel Test #52 Error Code Test Result Description / Recommendation 2000 ABRT Test request timed out. 2100 ABRT Could not allocate needed system resources. 1. Retry the command at 1-minute intervals up to 3 times. 2500 ABRT Internal system error 1.
PAGE 634
Communication Manager Maintenance-Object Repair Procedures Packet Interface Loop Around Test (#598) This nondestructive test checks the ATM-TRK circuit pack’s packet-bus interface. The LANHO chip sends data through the bus and back to itself. If the data received is consistent with the data sent, the test passes. The test does not run if the specified PN’s packet bus has a minor alarm or is out of service.
PAGE 635
ATM-TRK (Circuit Emulation Service Circuit Pack) The test aborts if the ATM-TRK circuit pack is supplying synchronization. Table 214: ATM Board Reset (#1256) Error Code Test Result Description / Recommendation 1005 ABRT Wrong circuit pack configuration to run this test. The ATM CES Trunk Interface circuit pack provides timing for the system and cannot be reset without major system disruptions. 1.
PAGE 636
Communication Manager Maintenance-Object Repair Procedures Table 214: ATM Board Reset (#1256) (continued) Error Code Test Result Description / Recommendation 1 FAIL The circuit pack failed to reset 2 FAIL The circuit pack failed to restart. 1. Retry command. 2. If the problem persists, replace the ATM-TRK circuit pack. 0 PASS The ATM-TRK circuit pack is successfully reset. NO BOARD No board detected. 1.
PAGE 637
ATM-TRK (Circuit Emulation Service Circuit Pack) ATM Board Error Query Test (#1259) This nondestructive ATM Error Query test retrieves the most severe, active, on- and off-board problem from the ATM-TRK circuit pack’s firmware and increments error counts in the Error Log. The test passes if there are no errors and fails otherwise. A passing test clears the software counters; a failure increments the counter associated with the problem that caused the failure and clears the others.
PAGE 638
Communication Manager Maintenance-Object Repair Procedures Aux Data XX Table 216: Aux Data XXfor ATM Board Error Query Test (#1259) If XX= Then 1 ATM framer chip failed 2 NCE chip failed 3 LANHO critical error 4 TDM Programmable Logic Device failed 5 Every on-board DSP failed 6 Receive Network Processor failed 7 Transmit Network Processor failed 8 Memory read failed 9 Dual UART chip failed 10 LANHO receive parity error 11 LANHO FIFO overflow error 12 LAN bus time out 13 LANHO Xmi
PAGE 639
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 217: Aux Data YY for ATM Board Error Query Test (#1259) (continued) If YY= Then 19 MS remote defect indicator error 20 Loss of pointer 21 Path signal level mismatch 22 High-level path alarm indication signal 23 High-level path remote defect indicator 24 Loss of cell delineation 25 Uncorrectable headers sent by the ATM switch 26 Too many cells with invalid VPI/VCI combination 27 The signaling link between the board and the ATM switch
PAGE 640
Communication Manager Maintenance-Object Repair Procedures ATM Board Framer Loop-Around Test (#1260) This test is destructive. This test verifies the board's circuit (Time Division Multiplexing) and packet paths using an on-board, dummy virtual circuit. Before running the test, you must: ● busyout the ATM-TRK circuit pack (busyout board location) and ● switch synchronization (change synchronization) from the ATM-TRK circuit pack If the ATM-TRK circuit pack is supplying synchronization, the test aborts.
PAGE 641
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 218: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 1033 ABRT ATM-TRK circuit pack not found 1. See if the switch can see the circuit pack. Run status trunk-group. 2. Retry the command. 1139 ABRT Major alarm on the PN’s packet bus 1. Run display alarms, and perform the repairs associated with PKT-BUS errors. 2. Run display errors, and perform the repairs associated with PKT-BUS errors.
PAGE 642
Communication Manager Maintenance-Object Repair Procedures Table 218: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 1 FAIL Test tone not detected over the loop around; packet-path test aborted. 1. Test the active Tone-Clock in the PN, and verify that a tone is reaching the ATM-TRK circuit pack. If not, correct the condition. 2. Run test board location long. 3. If the test continues to fail, replace the ATM-TRK circuit pack or transceiver. 4.
PAGE 643
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 218: ATM Board Framer Loop-Around Test (#1260) (continued) Error Code Test Result Description / Recommendation 5 FAIL Unable to create packet-path loop. 1. Retry the command up to 3 times at 1-minute intervals. 2. If this test continues to fail, replace the ATM-TRK circuit pack. 3. Rerun test board location long. 6 FAIL A previously established loop around was not released. 1. Run reset board location. 2.
PAGE 644
Communication Manager Maintenance-Object Repair Procedures ATM Board Time Of Day Update (#1261) The nondestructive ATM-TOD-UPD test updates the system time used by the ATM-TRK circuit pack for SDH/SONET performance monitoring and synchronizes the ATM-TRK circuit pack with the S8700 Multi-Connect system’s clock. This test is run during initialization, scheduled maintenance, and craft long test.
PAGE 645
ATM-TRK (Circuit Emulation Service Circuit Pack) ATM Board DSP Test (#1293) This test is nondestructive. There are three kinds of digital signal processors (DSPs): talkers, listeners, and echo cancelers.Talkers put data on the TDM bus, listeners take data off the TDM bus, and echo cancelers filter out echoes of the main transmission. Firmware allocates DSPs in sets of three (one of each type), up to a maximum of 8 sets. This has three parts, one for each type of DSP.
PAGE 646
Communication Manager Maintenance-Object Repair Procedures Table 220: ATM Board DSP Test (#1293) (continued) Error Code Test Result Description / Recommendation 2000 ABRT Test timed out. 1. If the ATM-TRK circuit pack is in standby, reset the board and run the test again after the ATM-TRK circuit pack is inserted. 2. Examine the Error Log for Error 1218 (bad DSP). 3. Run the test again. 2100 ABRT Could not allocate required system resources. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 647
ATM-TRK (Circuit Emulation Service Circuit Pack) Table 220: ATM Board DSP Test (#1293) (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board detected. 1. Check the Error Log for wrong board Error 125 (wrong board) or Error 131 (no board). Replace or insert the circuit pack if necessary. 2. Check that the board is properly translated and inserted. 3. If Error 1538 (hyperactivity) is listed in the Error Log, and run reset board location. 4.
PAGE 648
Communication Manager Maintenance-Object Repair Procedures Table 221: ATM Crosstalk Test (#1298) (continued) Error Code Test Result Description / Recommendation 1003 ABRT Could not allocate a tone receiver. Too few Tone Detectors installed or Tone Detectors out-of-service. 1. Identify and correct any TTR-LEV (TTR Level) errors listed in the Error Log. 2. Resolve any TONE-PT (Tone Generator) errors listed in the Error Log. 3. Retry the test up to 5 times at 1-minute intervals a maximum.
PAGE 649
ATM-WSP (ATM WAN Spare Processor) ATM-WSP (ATM WAN Spare Processor) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ATM-WSP MAJ status atm wsp wsp# ATM WAN Spare Processor ATM-WSP MIN status atm wsp wsp# ATM WAN Spare Processor ATM-WSP WRN display atm wsp wsp# ATM WAN Spare Processor S8700 Multi-Connect systems with multiple PNs connected via ATM PNC have the option of installing up to 15 ATM WAN Spare Processor (WSP) units.
PAGE 650
Communication Manager Maintenance-Object Repair Procedures Operations of the ATM WAN Spare Processors The WSP has the following operational features: Note: ● The WSP feature is activated/deactivated via license file. You can verify that ATM WSP is enabled by checking the value of the ATM WAN Spare Processor field on the system-parameters customer-options screen.
PAGE 651
ATM-WSP (ATM WAN Spare Processor) Error Log Entries and Test to Clear Values Table 222: ATM-WSP Error Log Entries Error Type Aux Data Associated Test Alarm Level 0 0 Any Any On/Off Board 18 (a) MO busied out 257 (b) Active WSP (#1401) MAJ OFF 513 (c) WSP Link Status (#1400) MIN OFF WSP Priority Error MIN OFF WSP Error WRN OFF 769 (d) 1025 (e) WSP # Test to Clear Value release atm wsp reset system 2 Notes: a. Error Type 18: the ATM WSP has been busied out with busyout atm wsp.
PAGE 652
Communication Manager Maintenance-Object Repair Procedures Examples: ● Aux Data 15: the B-PNC link to WSP 5 is down. ● Aux Data 3: the A-PNC link to WSP 3 is down. d. Error Type 769: there are inconsistent translations with regard to WSP’s priority. Each WSP keeps a list of every other WSP’s priority levels. Inconsistent priorities can exist that result in a WSP receiving an unexpected probe. This causes an alarm to be raised.
PAGE 653
ATM-WSP (ATM WAN Spare Processor) System Technician-Demanded Tests: Descriptions and Error Codes There are no system technician-demanded tests associated with ATM-WSP, only tests run by system software.
PAGE 654
Communication Manager Maintenance-Object Repair Procedures ATT-ADJ (AvayaAdjunct) S8700 | 8710 / S8500 See BRI-SET, Various Adjuncts on page 708. 654 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 655
ATTE-AJ (Ethernet Avaya Adjunct) ATTE-AJ (Ethernet Avaya Adjunct) S8700 | 8710 / S8500 See BRI-SET, Various Adjuncts on page 708.
PAGE 656
Communication Manager Maintenance-Object Repair Procedures AUDIX-BD (AUDIX Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AUDIX-BD MIN test board location sh AUDIX circuit pack AUDIX-BD WRN test board location sh AUDIX circuit pack The AUDIX-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack combination. For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 657
AUDIX-PT (AUDIX Port) AUDIX-PT (AUDIX Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AUDIX-PT MIN test port location l AUDIX port AUDIX-PT WRN test port location sh AUDIX port The AUDIX-PT MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack operating in digital-port (DP) mode. For circuit-pack-level problems (AUDIX-BD), see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 658
Communication Manager Maintenance-Object Repair Procedures AUX-BD (Auxiliary Trunk Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AUX-BD MIN test board location sh Auxiliary Trunk circuit pack AUX-BD WRN test board location sh Auxiliary Trunk circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 maintenance information for circuit pack-level errors.
PAGE 659
AUX-TRK (Auxiliary Trunk) AUX-TRK (Auxiliary Trunk) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AUX-TRK MAJ1 test port location l Auxiliary Trunk AUX-TRK MIN test port location l Auxiliary Trunk AUX-TRK WRN test port location sh Auxiliary Trunk 1. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least 75% of the trunks in this trunk group are alarmed.
PAGE 660
Communication Manager Maintenance-Object Repair Procedures The Loudspeaker Paging feature provides voice and/or code calling chime paging. If multiple paging zones are provided at a customer’s premises, the Loudspeaker Paging feature gives a user the option of paging to a particular zone or to every zone. If a zone is active for one page, it cannot be used at the same time for another. An Auxiliary Trunk circuit pack contains four ports and uses DTMF signaling.
PAGE 661
AUX-TRK (Auxiliary Trunk) Table 223: Auxiliary Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 0 busyout port location WRN OFF release port location None WRN ON test trunk grp#/mem# sh MIN WRN ON test port location l r 3 MIN WRN ON test port location l r 3 WRN ON test port location sh r 3 130(e 769(c) 257 57482 None Hybrid/Conference 1 Circuit test (#33) 513 NPE Crosstalk test (#6) 2 1025 Diagnostic: Au
PAGE 662
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Looparound and Conference test (#33), you may also clear errors generated from other tests in the testing sequence.
PAGE 663
AUX-TRK (Auxiliary Trunk) Table 224: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 664
Communication Manager Maintenance-Object Repair Procedures Table 224: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL The Network Processing Element (NPE) of the tested port was found to be transmitting in error. This will cause noisy and unreliable connections. This problem may be caused by defective Tone Detectors. 1.
PAGE 665
AUX-TRK (Auxiliary Trunk) Table 225: Test #33 Looparound and Conference (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid call during the test. The test has been aborted. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the port is active, wait until it is idle. 2. Retry the command at 1-minute intervals up to 5 times.
PAGE 666
Communication Manager Maintenance-Object Repair Procedures Table 225: Test #33 Looparound and Conference (continued) Error Code Test Result Description / Recommendation 131 FAIL The reflective 1004-Hz tone test failed. No transmission was detected to or from the port. The problem may be off-board. 1. To make sure the problem is on-board, disconnect the port from the auxiliary equipment and retry test. 2. If the test fails, replace the circuit pack.
PAGE 667
AUX-TRK (Auxiliary Trunk) Table 225: Test #33 Looparound and Conference (continued) Error Code Test Result Description / Recommendation 133 FAIL The reflective 2804-Hz tone test failed. No transmission was detected to or from the port. The problem may be off-board. 1. To make sure the problem is on-board, disconnect the port from the auxiliary equipment and retry test. 2. If the test fails, replace the circuit pack.
PAGE 668
Communication Manager Maintenance-Object Repair Procedures Audit Update Test (#36) This test sends updates of the auxiliary trunk port translation for every port on the Auxiliary Trunk circuit pack that has been translated. The update is non-disruptive and guards against possible corruption of translation data contained on the circuit pack. No response message is expected from the circuit pack once it receives translation updates.
PAGE 669
AUX-TRK (Auxiliary Trunk) Diagnostic Test—Auxiliary Trunk Test (#114) The system software sends a message to the on-board microprocessor to operate a relay in the port circuit. If ground is detected, the test passes. Table 227: Test #114 Diagnostic Test—Auxiliary Trunk Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 670
Communication Manager Maintenance-Object Repair Procedures AXA12-BD (AUDIX Circuit Packs) Error log entries and tests also apply to ADX8D-BD and AXD12-BD.
PAGE 671
AXA12-BD (AUDIX Circuit Packs) ADX12-BD The ADX12-BD MO represents a TN568 EMBEDDED AUDIX circuit pack operating in 12-port digital (DP) mode. TN568 EMBEDDED AUDIX circuit packs operating in 12-port digital mode appear to the system as TN2181 Digital Line circuit packs with vintage greater than 50. For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539. Port-level problems are covered by ADX12D-PT.
PAGE 672
Communication Manager Maintenance-Object Repair Procedures ADX8D-BD (Audix Circuit Packs) S8700 MC See AXA12-BD (AUDIX Circuit Packs) on page 670. 672 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 673
AXD12-BD (Audix Circuit Packs) AXD12-BD (Audix Circuit Packs) S8700 MC See AXA12-BD (AUDIX Circuit Packs) on page 670.
PAGE 674
Communication Manager Maintenance-Object Repair Procedures AXA12-RS (AUDIX Reserve Slots) Error log entries and tests also apply to ADX8D-RD and AXD12-RS. S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO AXA12-RS NONE NONE TN568 12-port analog reserve slot ADX8D-RS NONE NONE TN568 8-port digital reserve slot AXD12-RS NONE NONE TN568 12-port digital reserve slot There are no tests associated with these MOs.
PAGE 675
ADX8D-RS (AUDIX Reserve Slots) ADX8D-RS (AUDIX Reserve Slots) S8700 MC See AXA12-RS (AUDIX Reserve Slots) on page 674.
PAGE 676
Communication Manager Maintenance-Object Repair Procedures AXD12-RS (AUDIX Reserve Slots) S8700 MC See AXA12-RS (AUDIX Reserve Slots) on page 674. 676 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 677
BRI-BD (ISDN-BRI Line Circuit Pack) BRI-BD (ISDN-BRI Line Circuit Pack) Error log entries and tests also apply to LGATE-BD.
PAGE 678
Communication Manager Maintenance-Object Repair Procedures LEDS The ISDN-BRI Line circuit pack performs extensive initialization tests and lights both the red and green LEDS during the initialization testing. See Chapter 3: LEDs, for more details on circuit pack status LEDs.
PAGE 679
BRI-BD (ISDN-BRI Line Circuit Pack) Table 228: BRI-BD Error Log Entries (continued) Error Type Aux Data 2306 (k) Associated Test Alarm Level On/Off Board MIN OFF Test to Clear Value LANBIC Receive Parity Error Counter test (#595) 3330 (l) 46083 3840 (m) 4096 to 4101 3843 (n) 46097 3999 (o) Any None 2 of 2 Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence.
PAGE 680
Communication Manager Maintenance-Object Repair Procedures g. Error Type 769: reported by the circuit pack when it detects a program logic error. No action is required, but this error may lead to errors of other types being reported against this circuit pack. h. Error Type 1025: reported by the circuit pack when it cannot update NPE memory and read it back. No action is required, but this error may lead to errors of other types being reported against the circuit pack. i.
PAGE 681
BRI-BD (ISDN-BRI Line Circuit Pack) l. Error Type 3330: A critical failure has been detected in the packet-bus interface of the circuit pack. This failure may be due to either a packet-bus or to an on-board fault. If the packet bus is alarmed, see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 and Isolating and repairing packet-bus faults in Maintenance Procedures (03-300192) for recommended repair procedures.
PAGE 682
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with one test, you may also clear errors generated from other tests in the sequence. Short Test Sequence Long Test Sequence D/ND1 X X ND NPE Audit test (#50) X ND LANBIC Receive Parity Error Counter test (#595) X ND Order of Investigation Control Channel Loop-Around test (#52) 1.
PAGE 683
BRI-BD (ISDN-BRI Line Circuit Pack) These errors may indicate a circuit-pack problem, packet-bus problem, or a problem with another circuit pack on the bus. This test is useful for verifying the repair of the problem. Table 229: Test #595 LANBIC Receive Parity Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received from the circuit pack within the allowable time period. 1.
PAGE 684
Communication Manager Maintenance-Object Repair Procedures BRI-DAT (ISDN-BRI Data Module) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO BRI-DAT WRN1 test data-module extension ISDN-BRI Stand-alone Data Module 1. The alarm level for ASAI or Avaya adjuncts may be administered using set options. The alarm level can be set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI adjunct in the system.
PAGE 685
BRI-PORT (ISDN-BRI Port) BRI-PORT (ISDN-BRI Port) Error log entries and tests also apply to ABRI-POR, ATT-PORT, LGATE-PT, and ATTE-PT.
PAGE 686
Communication Manager Maintenance-Object Repair Procedures The TN2208 LGATE MFB provides Communication Manager with the interface to Adjunct-Switch Application Interface (ASAI) and Avaya adjuncts (for example, CONVERSANT® Voice System). The circuit pack contains 12 ports of line circuit interface (although only 8 are usable by the switch), each of which operates with two B channels (referred to as B1 and B2 throughout this section) and one D channel.
PAGE 687
BRI-PORT (ISDN-BRI Port) and for more information about its endpoints, see: ● ASAI-ADJ (ASAI Adjunct) on page 481 ● ATT-ADJ (AvayaAdjunct) on page 654 ● LGATE-AJ on page 1476 Figure 33: ISDN-BRI Port Interactions Switch BRI line circuit pack Port Voice or data terminal D-channel B-channel B-channel Voice or data terminal Logical connection Physical connection bripor1 LJK 072501 Hardware Error Log Entries and Test to Clear Values Table 230: ISDN-BRI Port Error Log Entries Error Type Aux Data As
PAGE 688
Communication Manager Maintenance-Object Repair Procedures Table 230: ISDN-BRI Port Error Log Entries (continued) Error Type Aux Data Associated Test 130(c) Alarm Level BRIPORT Alarm Level ABRI-PORT ATT-PORT LGATE-PT ATTE-PT WRN 257(d On/Off Board Test to Clear Value ON test port PCSS sh test port PCSSpp sh r 1 EPF Inquiry (#622) WRN MAJ MIN WRN2 OFF 513(e) 46222 none (d) (d) ON 769(f) 0 none WRN MAJ OFF NPE Crosstalk (#617) MIN WRN2 CRC Error Counter (#623) WRN BRI Port Loc
PAGE 689
BRI-PORT (ISDN-BRI Port) c. Error Type 130: 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. d. Error Type 257: the EPF Status Inquiry fails due to an overcurrent condition or when the BRI-LINE circuit pack detects that the EPF is in an over current condition. The aux data field contains one of the following values: ● blank – This indicates that the EPF Status Inquiry failed due to an overcurrent condition.
PAGE 690
Communication Manager Maintenance-Object Repair Procedures This error is most likely due to a problem with the wiring to the set or adjunct, interference on the wiring due to a noise source, or no termination (an open circuit). It usually does not indicate a problem with the circuit pack. ● Check the wiring to the endpoints or the adjunct. ● If the problem persists, replace the endpoints or adjuncts, or escalate the problem. i. Error Type 1793: the BRI Port Local TDM Loop Around test (#619) fails.
PAGE 691
BRI-PORT (ISDN-BRI Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the NPE Crosstalk test (#617), you may clear errors generated from other tests in the sequence.
PAGE 692
Communication Manager Maintenance-Object Repair Procedures This test is not executed for ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT because the B channels associated with the port are not used by ASAI or Avaya adjuncts. Table 231: Test #617 NPE Crosstalk Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1.
PAGE 693
BRI-PORT (ISDN-BRI Port) Table 231: Test #617 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation PASS The port is correctly using its allocated time slots. 1. To verify that this is not an intermittent problem, repeat this test up to 10 times to make sure it continues passing. 2. If complaints still exist, examine the station, connections, and wiring. 2 of 2 BRI Port Local LAN Loop Around Test (#618) This test is destructive.
PAGE 694
Communication Manager Maintenance-Object Repair Procedures Table 232: Test #618 BRI Port Local LAN Loop Around Error Code Test Result Description / Recommendation 1015 ABRT The port is not in the out-of-service state. 1. Display the BRI Port Status screen via status bri-port location to determine what stations or adjuncts are on this port. 2. Use the extension shown on this screen in status station to determine whether the station or adjunct is active. 3.
PAGE 695
BRI-PORT (ISDN-BRI Port) Table 232: Test #618 BRI Port Local LAN Loop Around (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. FAIL The Loop Around test has failed. 1.
PAGE 696
Communication Manager Maintenance-Object Repair Procedures The dotted lines in Figure 35: Path of the BRI Port Local TDM Loop Around on page 696 show how a Loop Around test is performed for the B channels. The figure shows a terminal connected to a BRI line board using a TN556. If a TN2198 is used the terminal would be connected to a NT1, and the NT1 to the BRI board.
PAGE 697
BRI-PORT (ISDN-BRI Port) Table 233: Test #619 BRI Port Local TDM Loop Around Error Code Test Result Description / Recommendation 1000 ABRT The system resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension or trunk group/member number of the port. Use status bri-port location to determine the service state of the port.
PAGE 698
Communication Manager Maintenance-Object Repair Procedures Table 233: Test #619 BRI Port Local TDM Loop Around (continued) Error Code Test Result Description / Recommendation 1005 ABRT 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.
PAGE 699
BRI-PORT (ISDN-BRI Port) Electronic Power Feed Restoral Test (#620) This test attempts to restore the Electronic Power Feed (EPF) on an ISDN-BRI port twice. In this test, the processor requests that the EPF be turned on for a given port. An attempt is made to turn on the power unit to the station or adjunct. If no current is being drawn by a station, this probably indicates that the station is not connected. No current being drawn by an adjunct is the normal condition.
PAGE 700
Communication Manager Maintenance-Object Repair Procedures The Activated state is the correct state for an ISDN-BRI port. In this state the Level 1 interface can communicate with the BRI endpoint or ASAI or Avaya adjunct administered on this port. This test passes if the state of Level 1 (L1) is Activated. This test also passes if software has taken this port out of service. See the description of the Level 1 “Deactivated State” below for more details.
PAGE 701
BRI-PORT (ISDN-BRI Port) Table 235: Test #621 Level 1 Status Inquiry (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to fail, escalate the problem.
PAGE 702
Communication Manager Maintenance-Object Repair Procedures Table 235: Test #621 Level 1 Status Inquiry (continued) Error Code Test Result Description / Recommendation 2 FAIL For the TN556 or TN2208, received a status of Level 1 Pending Activation-Endpoint Active which indicates a problem with the BRI endpoint or ASAI or Avaya adjunct, the wiring to the endpoint or adjunct, or the ISDN-BRI port. For the TN2198, received a status of Level 1 Pending Activation.
PAGE 703
BRI-PORT (ISDN-BRI Port) Table 235: Test #621 Level 1 Status Inquiry (continued) Error Code Test Result Description / Recommendation 4 FAIL For the TN2198 only: Received a status of Level 1 Pending Activation, the NT1 has a loss of power indicating a problem with the NT1. 1. For the NT1 follow the manufacturers recommended repair procedures. 2. Execute test port location, and review the results of the Level 1 Status Inquiry test to verify the repair. If the test is still failing proceed to step 3. 3.
PAGE 704
Communication Manager Maintenance-Object Repair Procedures Table 236: Test #622 Electronic Power Feed Inquiry (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem.
PAGE 705
BRI-PORT (ISDN-BRI Port) Table 237: Test #624 Layer 1 Transmission Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received from the circuit pack within the allowable time period. 1. If the test aborts repeatedly up to five times, reset the circuit pack via busyout board location and reset board location. 2. If the test aborts again, replace the circuit pack. 2012 ABRT Internal system error.
PAGE 706
Communication Manager Maintenance-Object Repair Procedures Receive FIFO Overflow Error Counter Test (#625) This test reads and clears the BRI port’s Receive FIFO Overflow error counter maintained on the BRI-LINE circuit pack. This counter is incremented by the circuit pack when it detects an overflow of its receive buffers. The test passes if the value of the counter is 0 (that is, the error is cleared).
PAGE 707
BRI-PORT (ISDN-BRI Port) Clear Error Counters Test (#270) This test is not an actual test in the strict sense of the word. There are various error counters associated with each BRI-PORT/ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT. This test clears those counters and triggers the auditing of Terminal Endpoint Identifier (TEI) values and layer-3 reinitialization. This test is used only to send messages to the BRI-PORT/ABRI-PORT/ ATT-PORT/LGATE-PT/ATTE-PT and, therefore, should neither abort nor fail.
PAGE 708
Communication Manager Maintenance-Object Repair Procedures BRI-SET, Various Adjuncts Error log entries and tests also apply to ATT-ADJ, ATTE-AJ, ASAI-ADJ, BRI-DAT, and LGATE-AJ.
PAGE 709
BRI-SET, Various Adjuncts The TN2208 ESAI MFB provides the system with an Ethernet interface to Adjunct-Switch Application Interface (ASAI) and Avaya adjuncts (for example, CONVERSANT® Voice System). This circuit pack contains 8 ports of line circuit interface, each of which operates with two B channels (referred to as B1 and B2 throughout this section) and one D channel.
PAGE 710
Communication Manager Maintenance-Object Repair Procedures Figure 36: ISDN-BRI Set Interactions VOICE or DATA SET BRI Line Circuit Pack P O PBX R T D-Channel B-Channel B-Channel PHYSICAL CONNECTION VOICE or DATA SET Logical Connection Physical Connection This section contains the ISDN-BRI Set, ASAI Adjunct and Avaya Adjunct Maintenance documentation.
PAGE 711
BRI-SET, Various Adjuncts Table 240: BRI-SET/ASAI-ADJ Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level BRI-SET BRI-DAT Alarm Level ASAI-ADJ ATT-ADJ ATTE-AJ LGATE-AJ On/ Off Board Test to Clear Value 257 (d) Any BRI Layer 3 Query (#629) WRN MAJ WRN2 OFF test station ext r 2 test data-module ext r 2 351 (e) 0 None WRN OFF busyout station and release station 513 (f) 0 None 769 (g) 0 None WRN MAJ OFF 2561 (h) 0 None 2562-2566 (i) 0 None 2567 (p)
PAGE 712
Communication Manager Maintenance-Object Repair Procedures b. Error Type 2: violations of the ISDN-BRI signaling protocol; timers associated with certain layer-3 messages have expired before a required response was received. In the following table, the aux data field indicates what timer has just expired.
PAGE 713
BRI-SET, Various Adjuncts When this error occurs for an ASAI or Avaya adjunct, the Aux Data field indicates the state of the ASAI link or Avaya link and whether an invalid response or no response was received to the query from the switch, as shown in the following table: Aux Data ASAI Link State Error 102 13-restarting No response to RESTART message 104 13-restarting Invalid response to RESTART message 152 13-restarted No response to layer-3 query 154 13-restarted Invalid response to layer-3
PAGE 714
Communication Manager Maintenance-Object Repair Procedures h. Error Type 2561: the ASAI-ADJ or ATT-ADJ or LGATE-AJ or ATTE-AJ message is not transmitted because the PKT-CTRL (Packet Control circuit pack) transmit buffers are exhausted. Frequent or persistent occurrence of these events may indicate a hardware problem or traffic overload on the PKT-CTRL, the signaling link, or the ASAI or Avaya adjunct. Attempt to resolve the problem by following the repair procedures for the PKT-CTRL.
PAGE 715
BRI-SET, Various Adjuncts Table 241: ASAI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes) Error Code Test Result Description / Recommendation 0 Unrecognized ASAI Protocol Operation Requested ASAI protocol operation is not implemented by the switch or adjunct. Aux Data field of Error Log entry contains protocol identifier for unrecognized operation. 1. Consult switch and adjunct documentation to determine which set of operations is supported by the switch and the adjunct.
PAGE 716
Communication Manager Maintenance-Object Repair Procedures Table 241: ASAI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes) Error Code Test Result Description / Recommendation 87 Internal switch audit There is an inconsistency in switch data records. 1. There is no action needed since the switch has corrected the data inconsistency. 2. If a number of these errors continue to occur, then escalate to next tier. 2 of 2 n.
PAGE 717
BRI-SET, Various Adjuncts Table 242: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes) (continued) Error Code Test Result Description / Recommendation 34 No circuit or channel available A resource on the switch is unavailable for a call. For BRI endpoints: This cause value is not logged. For ASAI or Avaya Adjuncts: This condition means that there are no available trunks for an outgoing call request. 1. Verify that the adjunct is administered to support the trunk capabilities of the switch. 2.
PAGE 718
Communication Manager Maintenance-Object Repair Procedures Table 242: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes) (continued) Error Code Test Result Description / Recommendation 58 Bearer Capability Not Currently Available Requested bearer capability is implemented, but not administered. No B channel is administered. See recommendation for Error Code 50 above. 65 Bearer Service Not Implemented Requested service not implemented in switch or endpoint.
PAGE 719
BRI-SET, Various Adjuncts Long Test Sequence D/ND1 X(a) ND X(a) ND BRI Vendor ID test (#631) X(a) ND BRI Model/Vintage ID test (#632) X(a) ND Order of Investigation Short Test Sequence BRI Remote Loop Back (#627) BRI Set Audits (#630) X(a) 2 of 2 1. D = Destructive; ND = Nondestructive Note: (a) Execute test port long location, and review the results of the BRI Port Local LAN Loop Around test (#618) to verify the repair.
PAGE 720
Communication Manager Maintenance-Object Repair Procedures Table 243: Test #626 Signaling Link Status Test Error Code Test Result Description / Recommendation 1139 ABRT The PN’s packet bus is out-of-service. 1. Follow the repair procedures for the packet bus. 2. After completing step 1, use test port long location, and review the results of the BRI Port Local LAN Loop Around test (#618) to verify the repair. 1141 ABRT The PKT-CTRL is out-of-service. 1.
PAGE 721
BRI-SET, Various Adjuncts Table 243: Test #626 Signaling Link Status Test (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 1113 FAIL The signaling link is not “bound” to the adjunct or endpoint.
PAGE 722
Communication Manager Maintenance-Object Repair Procedures This test is not executed for ASAI adjuncts because adjuncts do not support MIMs upon which this test is based. Table 244: Test #627 BRI Remote Loop Back Error Code Test Result Description / Recommendation 1000 ABRT Could not seize the endpoint or B channels for test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem.
PAGE 723
BRI-SET, Various Adjuncts Table 244: Test #627 BRI Remote Loop Back (continued) Error Code Test Result Description / Recommendation 1187 ABRT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET. a. If this error type is present for BRI-SET only, then release the station via the release station b.
PAGE 724
Communication Manager Maintenance-Object Repair Procedures Table 244: Test #627 BRI Remote Loop Back (continued) Error Code Test Result Description / Recommendation 2069 ABRT The endpoint has returned an error response to the application message sent by the switch. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem.
PAGE 725
BRI-SET, Various Adjuncts BRI XID Test (#628) This test checks the D-channel connection between the server and an endpoint or adjunct. In this test, a D-channel XID frame is sent to the endpoint or adjunct over the point-to-point signaling link. The test passes if the endpoint or adjunct responds with a layer-2 XID-RESPONSE frame This test must be administered to not run in the Station Administration screen for ports on a TN2208.
PAGE 726
Communication Manager Maintenance-Object Repair Procedures Table 245: Test #628 BRI XID (continued) Error Code Test Result Description / Recommendation 1141 ABRT The PKT-CTRL is out-of-service. 1. Refer to PKT-CTRL (Packet Control Circuit Pack) Maintenance documentation. 2. If step 1 does not resolve the problem, escalate to the next tier. 1187 ABRT The circuit pack, port or station may have been busied out by a technician. 1.
PAGE 727
BRI-SET, Various Adjuncts Table 245: Test #628 BRI XID (continued) Error Code Test Result Description / Recommendation 2000 FAIL The XID-RESPONSE message was not received from the endpoint. 1. Consult the endpoint’s documentation to determine whether layer-2 XID and XID-RESPONSE messages are supported. If the documentation reflects no support for these messages, use change station extension and change the XID Testing field to n. 2.
PAGE 728
Communication Manager Maintenance-Object Repair Procedures Table 246: Test #629 BRI Layer 3 Query (continued) Error Code Test Result Description / Recommendation 1113 ABRT The signaling link between the switch and the endpoint or adjunct is down. 1. Use test port location long to clear any errors that prevent establishment of the signaling link. 2. Examine the results of Test #626 that are executed with the command.
PAGE 729
BRI-SET, Various Adjuncts Table 246: Test #629 BRI Layer 3 Query (continued) Error Code Test Result Description / Recommendation 1187 ABRT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET. a. If this error type is present for BRI-SET only, then release the station via release station. b.
PAGE 730
Communication Manager Maintenance-Object Repair Procedures Table 246: Test #629 BRI Layer 3 Query (continued) Error Code Test Result Description / Recommendation 2069 ABRT The endpoint has returned an error response to the switch sent application message. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 2000 FAIL No response is received from the endpoint or the adjunct. For BRI endpoints: 1.
PAGE 731
BRI-SET, Various Adjuncts BRI Set Audits Test (#630) This is a series of two tests that are classified as audits. The switch sends messages to the BRI endpoint to perform the following tests: ● Ringer Audit – This audit insures that both the switch and the endpoint agree as to the current state of the endpoint’s ringer. ● Lamps Audit – This audit insures that both the switch and the endpoint agree as to the current state of the endpoint’s lamps.
PAGE 732
Communication Manager Maintenance-Object Repair Procedures Table 247: Test #630 BRI Set Audits (continued) Error Code Test Result Description / Recommendation 1187 ABRT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET. a. If this error type is present for BRI-SET only, then release the station via release station. b.
PAGE 733
BRI-SET, Various Adjuncts SPID Facility Test This test is used to verify the wiring and operation of the signaling link between the switch and a endpoint or adjunct on a BRI interface. This test is not executed from the administration terminal, but rather is executed by using a BRI test set equipped with a display.
PAGE 734
Communication Manager Maintenance-Object Repair Procedures Table 248: SPID Facility Test (continued) Test Result Description / Recommendation PASS Display matches administered port address for the endpoint or adjunct. For BRI endpoints: 1. Verify that the SPID values administered in the switch and the endpoint are consistent. 2. If the SPID values are correct, replace the endpoint. 3. If test continues to fail, escalate the problem. For ASAI adjuncts: 1.
PAGE 735
BRI-SET, Various Adjuncts Table 249: Service SPID Display (continued) Restricted Service starting display column 8 14 25 31 Bound to Second Endpoint Translation starting display column 8 14 25 31 port location - ext1 - SPID111111 * ext2 * SPID222222 2 of 2 Issue 1 June 2005 735
PAGE 736
Communication Manager Maintenance-Object Repair Procedures BRI-DAT S8700 | 8710 / S8500 See BRI-SET, Various Adjuncts on page 708 736 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 737
CAB-CALM (Customer alarm) CAB-CALM (Customer alarm) G650 MO name in alarm log CAB-CALM Alarm level Initial SAT command to run Full name of MO test customer-alarm location Customer Alarm CAB-CALM provides control of a relay contact between a pair of leads from the TN2312BP IPSI that can be wired to an external alarming device that is provided by the customer (CPAD).
PAGE 738
Communication Manager Maintenance-Object Repair Procedures Table 250: Test 115 Customer provided alarming device Error Code Test Result Description / Recommendations 1000 ABRT This is an internal system error. 1. Repeat the command at one-minute intervals 1 to 3 times. 2000 ABRT The response to a query was not received in the time allowed. 1. Repeat the command at one-minute intervals 1 to 3 times.
PAGE 739
CAB-EXFR (emergency transfer) CAB-EXFR (emergency transfer) G650 MOs name in alarm log Alarm level Initial SAT command to run Full name of MO CAB-EXFR MIN test environment location sh Emergnncy Transfer CAB-EXFR MAJ test environment location l Emergency Transfer The emergency transfer feature connects some central office trunks directly through to analog user stations when the system has a serious problem or experiences a total power failure.
PAGE 740
Communication Manager Maintenance-Object Repair Procedures Error log entries and test-to-clear values Table 251: CAB-EXFR Error Log Entries Error type Aux data Associated test Alarm level On/Off board Test-to-clear value 1 (a) — Emergency transfer query test (#1532) MAJ On test environment location 2 (b) — Emergency transfer query test (#1532) MAJ On test environment location 257 (c) — Emergency transfer query tesst (#1532) WRN On test environment location Notes: a.
PAGE 741
CAB-EXFR (emergency transfer) Emergency Transfer Query test (#1532) There is only one test associated with the MO CAB-EXFR. The emergency transfer query test queries the maintenance module on the TN2312BP IPSI to determine if the emergency transfer is set in MANUAL-ON or MANUAL-OFF mode. If emergency transfer is set to MANUAL-ON, a major alarm is generated. If emergency transfer is set to MANUAL-OFF, a warning alarm is generated.
PAGE 742
Communication Manager Maintenance-Object Repair Procedures Table 252: Test 1532 Emergency transfer query (continued) Error code Test result Description and recommendation 2 FAIL The emergency transfer is set to Manual-On. 1. Use the status cabine cab or status health cab command to display the status of the emergency transfer select switch: ● “on” means that emergency transfer was manually activated by the set emergency-transfer on command.
PAGE 743
CAB-EXFR (emergency transfer) Table 252: Test 1532 Emergency transfer query (continued) Error code Test result Description and recommendation PASS System software has control of Emergency Transfer within this cabinet. If Emergency Transfer is currently invoked (the emergency transfer LED is on), the cause could be a major alarm. 1. The following shows the error types that can cause Emergency Transfer.
PAGE 744
Communication Manager Maintenance-Object Repair Procedures CAB-MTCE (Media Gateway Maintenance) G650 MO name in alarm log Alarm level Initial SAT command to run Full name of MO CAB-MTCE MIN test maintenance location sh Media Gateway Maintenance CAB-MTCE MAJ test maintenance location l Media Gateway Maintenance Avaya Communication Manager 2.0 introduces the G650 media gateway.
PAGE 745
CAB-MTCE (Media Gateway Maintenance) When a TN2312BP IPSI is inserted in a G650, Communication Manager sends the following messages to embedded software (firmware) on the board: ● Enable environmental maintenance ● Enable power supply insertion ● Enable power supply audits ● A query to verify that environmental maintenance is enabled ● A query to verify that power supply insertion is enabled ● A query to verify that power supply audits are enabled Error log entries and test-to-clear values Tabl
PAGE 746
Communication Manager Maintenance-Object Repair Procedures d. Error Type 769—This error indicates that a message with a valid op-code was received but some other part of the message was indecipherable. The op-code with the error is recorded under Aux data. e. Error Type 1025—This error indicates that an unsuccessful attempt was made to reset environmental maintenance. f. Error Type 1281—This error indicates that environmental initialization failed.
PAGE 747
CAB-MTCE (Media Gateway Maintenance) Table 254: Test #1545 Reset test (continued) Error code Test result Description and recommendation 1982 ABRT The board being tested is NOT a TN2312BP IPSI or later. 1. Insert a TN2312BP IPSI circuit pack. 1986 ABRT The TN2312BP IPSI failed to set emergency transfer to AUTO at initialization. 1. Enter reset maintenance 2. If the reset maintenance command aborts again enter set emergency command to see if emergency transfer can be activated or deactivated. 3.
PAGE 748
Communication Manager Maintenance-Object Repair Procedures Correct Board test (#1546) The TN2312BP IPSI board is required for the environmental functions to work in the G650 media gateway. This test verifies that the proper IPSI is inserted in the G650. Table 255: Test #1546 Correct board test Error code Test result Description and recommendation 2500 ABRT An internal operation failed. 1. Repeat the command at one-minute intervals 1 to 3 times.
PAGE 749
CAB-PFL (Power Fan Lead) CAB-PFL (Power Fan Lead) G650 MOs name (in alarm log) Alarm level Initial SAT command to run Full name of MO CAB-PFL MIN test environment location Power Fan Lead CAB-PFL MAJ test environment location Power Fan Lead The CAB-PFL represents the state of a combined power/fan lead. This lead is known as the AuxSig lead.
PAGE 750
Communication Manager Maintenance-Object Repair Procedures System technician-demanded tests: Descriptions and error codes S8700 | 8710 Order of Investigation Short test sequence Long test sequence D/ND X X Nondestructive Power/Fan lead query test (1533) Power/Fan lead query test #(1533) The Power/Fan Query test sends a request for the state of the power/fan lead (AuxSig) to the TN2312BP IPSI board in the G650 with an A carrier address. If the lead is on, the test fails.
PAGE 751
CAB-PFL (Power Fan Lead) Table 258: Test 1533 Power/Fan lead query (continued) Error code Test result Description and recommendation 1 FAIL (Cont) G600 / CMC1 In a G600 or CMC1, this error code indicates a failure in either: ● Power supply ● Fan Assembly There is a fan, temperature, power, or voltage problem in one or more of the cabinets. The power supply’s LEDs may indicate the problem’s source. 1. If none of the fans are running, then: a.
PAGE 752
Communication Manager Maintenance-Object Repair Procedures Table 258: Test 1533 Power/Fan lead query (continued) Error code Test result Description and 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. Check filter. If the filter is dirty or clogged it should be cleaned or replaced. The filter can either be washed with soap and water or vacuumed. a.
PAGE 753
CAB-TEMP (Cabinet Temperature) CAB-TEMP (Cabinet Temperature) G650 MO name (in alarm log) Alarm level Initial SAT command to run Full name of MO CAB-TEMP MIN test board location Cabinet Temperature CAB-TEMP MAJ test board location Cabinet Temperature The MO CAB-TEMP monitors the G650 and the 655A for the following: ● The power supply - Inlet temperature - Hot spot temperature status - Fan speed - Fan alarm lead ● The G650 carrier exhaust temperature The serial bus is used by the TN2312BP I
PAGE 754
Communication Manager Maintenance-Object Repair Procedures Table 259: CAB-TEMP Error Log Entries Error Type Aux data Associated test Alarm level On/Off board Test-to-clear value 513 (c) Power supply temperature test (#1537) MIN/ MAJ 1 ON test enviroment location test board location 769 (d) Power supply fan test (#1538) MIN ON test enviroment location test board location 1. This is a minor alarm if there is a redundant power supply, and a major alarm if there is only one power supply.
PAGE 755
CAB-TEMP (Cabinet Temperature) Table 260: Test #1537 Power Supply Temperature Error code Test result Description and recommendation 1000 ABRT There is an internal software error. 1. Repeat the command at one-minute intervals 1 to 3 times. 1035 ABRT The port network is not available. 1. Use status port-network to verify that the network is not up. 2. Look for alarms against EXP-PN, EXP-INT, PK-INT, etc. 3. Use diagnostic procedures for those MOs to clear the problem.
PAGE 756
Communication Manager Maintenance-Object Repair Procedures Table 260: Test #1537 Power Supply Temperature (continued) Error code Test result Description and recommendation 2 FAIL The exhaust temperature is over threshold. 1. Use the test board location command to check the temperature. 2. If redundant power supplies are present, there may be a problem with the backplane.
PAGE 757
CAB-TEMP (Cabinet Temperature) Power supply fan test (#1538) The power supply fan test verifies that the fan alarm lead from the fan assembly is not active. Table 261: Test #1538 power supply fan Error code Test result Description and recommendation 1000 ABRT This is an internal software error. 1035 ABRT The port network is not available. 2028 ABRT There is a problem communicating with the environmental maintenance firmware. 2100 ABRT The system could not allocate resources. 1.
PAGE 758
Communication Manager Maintenance-Object Repair Procedures CABINET (Cabinet Sensors) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CABINET MAJ test environment location Cabinet Sensors CABINET MIN test environment location Cabinet Sensors This maintenance object covers environmental maintenance for S8700, and S8500 media servers equipped with multicarrier cabinets (MCCs), and for media servers equipped with CMC1 or G600 carriers.
PAGE 759
CABINET (Cabinet Sensors) Variable-Speed Fans A variable-speed fan is identified by the following features: ● A fan and air filter assembly with product code ED-67077-30, Group 4 or greater, labeled on the front of the carrier ● A 5-pin white connector mounted next to each fan on the fan assembly cover plate for speed control and alarm circuitry ● A 2-pin black -48 V power connector to each fan ● A power filter (ED-1E554-30, G1 or G2) located in a metal box mounted behind the fans on the right-hand
PAGE 760
Communication Manager Maintenance-Object Repair Procedures CMC1 Table 263: CMC1: Cabinet sensors error log entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test environment 1(b) 257 (c) 513 (d) 769 (e) 1025 (f) 1281 (g) 1537 (h) 1793 (i) Any Cabinet Temperature or Voltage Query Test (#122) MAJ ON test environment Notes: a. Error Type 0: Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence.
PAGE 761
CABINET (Cabinet Sensors) Note: Note: An out-of-tolerance voltage condition may be caused by transient conditions (e.g. board insertion or electrical noise). Voltage problems can cause serious damage to the TN2314 or highly unpredictable failure modes. Therefore, a repeating condition will cause a major alarm. The following Error Types 769 through 1793 represents the various system voltages and are listed below: e. Error Type 769: Out-Of-Tolerance voltage condition for -48 VDC. f.
PAGE 762
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes S8700 | 8710 / S8500 Investigate tests in the order presented. By clearing error codes associated with one test, you may clear errors generated from later tests in the sequence.
PAGE 763
CABINET (Cabinet Sensors) CMC1 Short Test Sequence Long Test Sequence D/ND1 Cabinet Test (#122) X X ND Emergency Transfer Query Test (#124) (a) X X ND External Alarm Lead Query Test (#120) (b) X X ND Analog Ring Generator Initialization Test (#117)(c) X X ND Analog Ring Generator Query Test (#118)(d) X X ND Order of Investigation 1. D = Destructive; ND = Nondestructive Notes: a. Refer to EMG-XFER (Emergency Transfer) on page 1134 for a description of this test. b.
PAGE 764
Communication Manager Maintenance-Object Repair Procedures Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2. S8700 | 8710: If the test continues to abort with error code 2000, check for power problems with the PN’s A carrier.
PAGE 765
CABINET (Cabinet Sensors) Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710 S8500:1 FAIL VARIABLE-SPEED FAN ASSEMBLIES: One or more fans have stopped. If none of the fans are running: 1. Resolve every alarm against CARR-POW (Carrier Power Supply) on page 770. S8700 IP Resolve every alarm against RMC-ENV. 2. Verify that 48 VDC is available to the fan power filter at the J2F local cable connector. The voltage range is -42.
PAGE 766
Communication Manager Maintenance-Object Repair Procedures Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710 S8500:1 FAIL (cont’d) If some of the fans are running and some are not: (cont’d) 1. Replace the defective fans. If every fan can then be started, wait 5 minutes and rerun the test. If the test fails again, proceed to the next step. 2. Remove all six white 5-pin connectors on the front and back of the fan assembly.
PAGE 767
CABINET (Cabinet Sensors) Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710 S8500:1 FAIL (cont’d) NONVARIABLE-SPEEDFAN ASSEMBLIES (older or upgraded cabinets): The AHD1 circuit pack has reported an air-flow problem. The temperature difference between the air intake and the air exhaust is at least 150C (590F)) and the absolute temperature at the top of the cabinet is at least 500C (1220F).
PAGE 768
Communication Manager Maintenance-Object Repair Procedures Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710 S8500:1 FAIL (cont’d) NONVARIABLE-SPEEDFAN ASSEMBLIES (cont’d): If the fans are running at high speed, check the following items, any of which can restrict or redirect airflow within the cabinet. (cont’d) 1. Check both filters. If a filter is dirty or clogged, clean with soapy water or a vacuum. 2.
PAGE 769
CABINET (Cabinet Sensors) Table 264: Test #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710 S8500:2 FAIL A temperature problem due to the S1 sensor detecting a temperature of at least 650 C (1490 F) has been reported. The entire cabinet is in danger of power-down if the temperature reaches 700 C (1580 F). 1. If any of the fans are not running, there should be a FAIL with Error Code 1 present.
PAGE 770
Communication Manager Maintenance-Object Repair Procedures CARR-POW (Carrier Power Supply) S8700 MC MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CARR-POW MAJ recycle carrier location Carrier Port Power Supply S8700 Multi-Connect systems support two different cabinet types for PNs. Both cabinet types may be powered by either AC or DC external power source. Environmental maintenance differs according to cabinet type and external power supply.
PAGE 771
CARR-POW (Carrier Power Supply) Cycling Power Supplies When a port carrier power supply problem is reported by hardware, the system can cycle the power supplies in that carrier. When a carrier is cycled, the power supplies are turned off for 2 seconds and then turned back on.
PAGE 772
Communication Manager Maintenance-Object Repair Procedures AC-Powered Cabinets AC Power-Distribution Unit and Battery Charger (J58890CE-2) Figure 37: AC Power-Distribution Unit (J58890CE-2): Front on page 772 shows an AC power-distribution unit (List 9 or List 10). This unit sits at the bottom of some multicarrier cabinets.
PAGE 773
CARR-POW (Carrier Power Supply) Figure 38: Battery Charger (Optional Part of J58890CE-2): Front Battery Charger Batteries battchar RBP 031996 The charger is used only without an uninterruptible power supply (UPS).
PAGE 774
Communication Manager Maintenance-Object Repair Procedures Figure 39: AC Power Distribution in Multicarrier Cabinets "C" Position Carrier "B" Position Carrier "A" Position Carrier "F" Position 2 Fan Unit "D" Position Carrier "E" Position Carrier Power Distribution 3 Unit Battery Charger (Optional) mcc4_g3 RBP 041696 Power Backup If AC power fails, three 48-V DC batteries power the system for: ● 15 seconds in a PN cabinet ● 10 minutes in the expansion control carrier in the “A” position of a PN c
PAGE 775
CARR-POW (Carrier Power Supply) J58890CH-1 In AC-powered cabinets, the power-distribution unit (J58890CH-1), distributes 170 to 264 VAC from a wall outlet to a set of BU3200A Battery Interface Units (BIU). See Figure 40: AC Power-Distribution Unit (J58890CH-1): Front on page 775 and Figure 41: Power-Distribution Unit (J58890CH-1) on page 776.
PAGE 776
Communication Manager Maintenance-Object Repair Procedures Figure 41: Power-Distribution Unit (J58890CH-1) Power Backup The small battery is at the center rear of the multicarrier cabinet. This 8-AH (Amp Hour) battery is fused for short circuit protection and is charged by the J58890CH-1. The batteries also contain a thermal sensor that changes the charging voltage depending on battery temperature. The small batteries provide short-term battery holdover.
PAGE 777
CARR-POW (Carrier Power Supply) Figure 42: Small Battery Assembly Fuse Battery Connector 0064_0 RBP 071596 Issue 1 June 2005 777
PAGE 778
Communication Manager Maintenance-Object Repair Procedures DC-Powered Cabinets DC Power-Distribution Unit (J58890CF-2) Figure 43: DC Power-Distribution Unit (J58890CF-2): Front on page 778 shows a power-distribution unit in some DC-powered multicarrier cabinets. The unit sits at the bottom of the cabinet and contains the ring generator, 20-Amp circuit breakers, terminal blocks, and system fan power.
PAGE 779
CARR-POW (Carrier Power Supply) Figure 44: Typical Multicarrier Cabinet with 649A Power Units The table below shows what carriers are protected by each circuit breaker on the J58890CF-1. The ring generator is protected by a fuse located next to the main circuit breaker on the front of the unit.
PAGE 780
Communication Manager Maintenance-Object Repair Procedures The table below shows what carriers are protected by each circuit breaker on the J58890CH-1. The ring generator is protected by a fuse located next to the main circuit breaker on the front of the unit.
PAGE 781
CARR-POW (Carrier Power Supply) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Battery & Battery Charger Query test (#5), you may also clear errors generated from other tests in the sequence.
PAGE 782
Communication Manager Maintenance-Object Repair Procedures OLS Recycle Test (#126) This test is destructive. This test removes power from the specified carrier and causes every circuit pack in the recycled carrier to be removed and inserted. These actions cause every call originating from or terminating to circuit packs in this carrier to be dropped. The pair of OLSs in the specified carrier is recycled. Both OLSs in the carrier are turned off for 2 seconds and then back on again.
PAGE 783
CARR-POW (Carrier Power Supply) Table 267: Test #126 OLS Recycle Test (continued) Error Code Test Result Description / Recommendation FAIL There is a problem with one or both OLSs on the cycled carrier. 1. Since the OLS Recycle test failed, both OLSs in the cycled carrier should have been powered off by the system software. Both OLSs should be showing a red status LED, instead of an amber one. Since the OLS Query test is a subset of the OLS Recycle test, the OLS Query test (#127) should also fail.
PAGE 784
Communication Manager Maintenance-Object Repair Procedures Table 268: Test #127 OLS Query Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2. If the test continues to ABORT with error code 2000, check for system powering problems with the PN’s A carrier.
PAGE 785
CARR-POW (Carrier Power Supply) Table 268: Test #127 OLS Query Test (continued) Error Code Test Result FAIL (cont’d) Description / Recommendation 4. If the replaced OLS(s) still do not operate properly, then a circuit pack or a defective telephone connected to a circuit pack in the affected carrier could be causing an electrical load that is preventing the OLS from operating properly. Unseat every circuit pack in the carrier, and enter recycle carrier. a.
PAGE 786
Communication Manager Maintenance-Object Repair Procedures Table 268: Test #127 OLS Query Test (continued) Error Code Test Result Description / Recommendation FAIL DC-POWERED SYSTEMS There is a problem with one or both port carrier power supplies on the tested carrier. 1. For each port carrier power supply that has every status LED OFF, check the DC input to the port carrier power supply at the port carrier power supply outlet.
PAGE 787
CARR-POW (Carrier Power Supply) Table 268: Test #127 OLS Query Test (continued) Error Code Test Result FAIL (cont’d) Description / Recommendation a. If the recycle passes, then the port carrier power supplies are healthy, and the problem is with one of the circuit packs. Reinsert the circuit packs one at a time. If the status LED shows red after reinserting a circuit pack, then replace the defective circuit pack.
PAGE 788
Communication Manager Maintenance-Object Repair Procedures CDR-LNK (Call Detail Recording Link) MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CDR-LINK MIN test cdr [primary | secondary] l CDR Link CDR-LINK WRN test cdr [primary | secondary] CDR Link Refer to PRI-CDR (Call Detail Recording Link) on page 1905 for Call Detail Recording Link problems. 788 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 789
CLAN-BD (Control LAN Circuit Pack) CLAN-BD (Control LAN Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CLAN-BD MIN test board location long Control LAN circuit pack CLAN-BD WRN test board location short Control LAN circuit pack Control LAN circuit pack The TN799 Control LAN (C-LAN) packet port circuit pack provides TCP/IP connection to adjunct applications such as CMS, INTUITY, and DCS Networking.
PAGE 790
Communication Manager Maintenance-Object Repair Procedures Socket counts will include H.245 and H.248 endpoints but the load-balancing algorithm will not be used for registering these endpoints. Sockets used by adjuncts will not be included in the socket count. Note: Note: This allocation is performed for the C-LANs assigned within each network region, independently of the C-LANs assigned to other network regions.
PAGE 791
CLAN-BD (Control LAN Circuit Pack) C-LAN congestion controls The switch activates congestion controls on a C-LAN when it detects a buffer exceeding the threshold. The switch releases the congestion controls when the C-LAN reports that its buffers have returned to normal levels. If congestion: Then the switch: Persists for a 14-minute interval, Raises MINOR alarm. Exhausts buffers, Raises MINOR alarm. Ceases for 12 minutes, Retires MINOR alarm.
PAGE 792
Communication Manager Maintenance-Object Repair Procedures Table 269: CLAN-BD Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value Packet Interface test (#598) MIN ON test board location l r 3 Congestion Query test (#600) MIN ON test board location s r 3 WRN OFF MIN ON test board location s MIN ON reset board location 1797 (k) 1798 (l) 2049 (m) 2305 2306 (n) 2561 to 2668 (o) Any 2817 2819 (p) 2820 (af) 3073 (q) Link Status t
PAGE 793
CLAN-BD (Control LAN Circuit Pack) Table 269: CLAN-BD Error Log Entries (continued) Error Type Aux Data 3862 (ac) Any 3865 (ad) Any 3866 (ae) Any Associated Test Alarm Level On/Off Board Test to Clear Value 3 of 3 Notes: a. Error Type 1: Circuit pack stopped functioning or is not physically present. 1. Verify that the circuit pack is present. If circuit pack is present, reset the circuit pack with reset board location. ● If the error persists, replace the circuit pack. b.
PAGE 794
Communication Manager Maintenance-Object Repair Procedures g. Error Type 1293-1297: Critical hardware or firmware error. If the switch detects: Then the switch: 1 error, Resets circuit pack. 3 errors in 15 minutes, Raises MINOR alarm. Error Type descriptions are as follows: 1293 Insane onboard processor 1294 Onboard translation RAM error 1295 (Aux 3) RSCL link down Software requested a reset of the CLAN because it failed to get a keep-alive response from the CLAN for over a minute.
PAGE 795
CLAN-BD (Control LAN Circuit Pack) 3. Reset circuit pack with the busyout board location, reset board location, and release board location commands. 4. Clear alarms using the test board long clear command. 5. If the error returns within 15 minutes, replace the circuit pack. k. Error Type 1797: Invalid layer 2 frame received. l. Error Type 1798: Unable to write translation RAM. 1. Attempt to clear alarm with reset board location. 2. If alarm recurs within 15 minutes, replace the circuit pack. m.
PAGE 796
Communication Manager Maintenance-Object Repair Procedures Note: 2561 - 2668 is a range of reserved numbers for future applications. 2570 currently represents an SNMP socket failure. Note: p. Error Type 2817-2819: Congestion Query test (#600) failed. The Error Types correspond to the descriptions: 2817 All buffers exhausted. 2819 Utilized buffers exceed threshold. If: Then: Active buffers exceed threshold C-LAN enters congested state. 1.
PAGE 797
CLAN-BD (Control LAN Circuit Pack) s. Error Type 3586 and 3999: Switch removed hyperactive circuit pack that reported threshold number of errors. One or more of the following symptoms may be present: ● Circuit pack port tests return NO BOARD. ● List configuration command shows circuit pack and ports are installed properly If Error Type 3999: And traffic volume is: Then: Does not accompany Error Type 3586, Heavy Circuit pack is in service, but sent at least half hyperactive threshold.
PAGE 798
Communication Manager Maintenance-Object Repair Procedures u. Error Type 3841-3843: errors do not affect service. 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 may cause reports of other errors that do affect service. If Error Type 3843 begins to affect service, it escalates to Error Type 1294. v.
PAGE 799
CLAN-BD (Control LAN Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate errors in the order they appear in the table below.
PAGE 800
Communication Manager Maintenance-Object Repair Procedures Control Channel Loop-Around Test (#52) This nondestructive test fails if the circuit pack does not return to a sane state after being reset. This test queries the circuit pack for its code and vintage, and verifies its records. Table 270: Test #52 Control Channel Loop-Around Test Error Code Test Result Description / Recommendation None, 2100 ABRT Could not allocate the necessary system resources to run test. 1.
PAGE 801
CLAN-BD (Control LAN Circuit Pack) Circuit Pack Restart Test (#252) 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. The circuit pack resets through the SAKI Sanity test (#53).
PAGE 802
Communication Manager Maintenance-Object Repair Procedures PPE/LANBIC Receive Parity Error Counter Test (#595) This test is nondestructive. When the C-LAN 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 may verify repair of problem.
PAGE 803
CLAN-BD (Control LAN Circuit Pack) Receive FIFO Overflow Error Counter Test (#596) This test is nondestructive. When the C-LAN circuit pack detects packet-bus buffer overflow, it increments the error on the FIFO Overflow error counter. This test reads and clears the counter.
PAGE 804
Communication Manager Maintenance-Object Repair Procedures Invalid LAPD Frame Error Counter Test (#597) This test is nondestructive. A C-LAN detects an invalid frame when it receives: ● a frame with a CRC error ● an unrecognizable frame ● a recognizable frame in an unexpected state When the C-LAN circuit pack detects an invalid LAPD frame, it increments the Invalid LAPD Frame error counter. This test reads and clears the counter, and verifies the repair of the problem.
PAGE 805
CLAN-BD (Control LAN Circuit Pack) Table 274: Test #597 Invalid LAPD Frame Error Counter Test (continued) Error Code Test Result Description / Recommendation 1–10 FAIL The circuit pack detects LAPD frame errors. The error code indicates the value of the on-board error counter. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to fail, execute the Packet Interface test (#598) (test board location long). 3.
PAGE 806
Communication Manager Maintenance-Object Repair Procedures Table 275: Test #598 Packet Interface Test (continued) Error Code Test Result Description / Recommendation FAIL Circuit pack has detected a failure of Packet Interface Test #598. 1. Retry command at 1-minute intervals up to 5 times. 2. If the problem persists, reset the circuit pack with reset board location. 3. If the test continues to fail, replace the circuit pack. PASS Packet Interface Test #598 passed.
PAGE 807
CLAN-BD (Control LAN Circuit Pack) Table 276: Test #600 Congestion Query Test (continued) Error Code Test Result Description / Recommendation 2012 ABRT Could not allocate the necessary system resources to run test. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the problem persists, escalate the problem. 1, 2 FAIL FAIL The buffer level is nearly exhausted.
PAGE 808
Communication Manager Maintenance-Object Repair Procedures Link Status Test (#601) This nondestructive test determines the state of the call-control signaling link for Control LANs. 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 809
CLAN-BD (Control LAN Circuit Pack) Table 277: Test #601 Link Status Test (continued) Error Code Test Result Description / Recommendation 3 FAIL Received no response to RSCL control link test frame. 1. Retry command at 1-minute intervals up to 5 times. 2. If the problem persists, reset the circuit pack with reset board location. 3. If test continues to fail, replace the circuit pack. PASS RSCL control link connected.
PAGE 810
Communication Manager Maintenance-Object Repair Procedures CLSFY-BD (Call Classifier Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CLSFY-BD MIN test board location sh Call Classifier circuit pack CLSFY-BD WRN test board location sh Call Classifier circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors.
PAGE 811
CLSFY-PT (Call Classifier Port) CLSFY-PT (Call Classifier Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CLSFY-PT MAJ test port location sh Call Classifier Port CLSFY-PT MIN test port location sh Call Classifier Port CLSFY-PT WRN test port location sh Call Classifier Port The TN744 Call Classifier is a service circuit pack that provides specialized tone detection capabilities to support the Outbound Call Management (OCM) and Inbound Call
PAGE 812
Communication Manager Maintenance-Object Repair Procedures 1. Enter these commands in order: busyout board, reset board, release board. The board reset is required to reload on-board RAM associated with the TN744’s DSPs. This takes all 8 Tone Detector ports out of service for a few seconds. Only 4 of the 8 would be out of service due to the alarm. (There are five Tone Detectors on each of the two DSPs.
PAGE 813
CLSFY-PT (Call Classifier Port) Table 279: Test #42 Tone Detection Verification Test Error Code Test Result Description / Recommendation none ABRT The system was not able to allocate every resource needed for this test, OR there was an internal system error. 1 ABRT The system could not allocate every resource needed to test the tones. 1. Retry the command at 1-minute intervals up to 5 times. 1001 ABRT The system was unable to put the call classifier port in the appropriate mode to test it. 1.
PAGE 814
Communication Manager Maintenance-Object Repair Procedures Table 279: Test #42 Tone Detection Verification Test (continued) Error Code Test Result Description / Recommendation 2006 ABRT Indicates that the active Tone-Clock circuit pack or a Tone Detector circuit pack may not be functioning properly. If there is more than one Tone Detector circuit pack in the system, then the problem can be either with the Tone-Clock circuit pack or the Tone Detector circuit pack.
PAGE 815
CLSFY-PT (Call Classifier Port) Tone Detector Audit/Update Test (#43) This test performs a sanity audit on the CLSFY-PT (Call Classifier Port). Table 280: Test #43 Tone Detector Audit/Update Test Error Code Test Result Description / Recommendation none ABRT The system was not able to allocate the resources for this test. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT Response to the test request was not received within the allowable time period. 1.
PAGE 816
Communication Manager Maintenance-Object Repair Procedures CO-BD (Central Office Trunk Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CO-BD MIN test board location sh Central Office Trunk circuit pack CO-BD WRN test board location sh Central Office Trunk circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors.
PAGE 817
CO-DS1 (DS1 CO Trunk) CO-DS1 (DS1 CO Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CO-DS1 MAJ1 test trunk grp#/mem# l DS1 CO Trunk CO-DS1 MIN test trunk grp#/mem# l DS1 CO Trunk CO-DS1 WRN test trunk grp#/mem# DS1 CO Trunk 1. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least 75 percent of the trunks in this trunk group are alarmed.
PAGE 818
Communication Manager Maintenance-Object Repair Procedures S8300 / G700 The MM710 supports T1/E1, and delivers the same functionality as the TN464 circuit pack. Although CO-DS1 is provided for G700/G350 Media Gateways, CO-DS1 only partially supports the MM710 DS1 Media Module. Three trunk service states are specified by DS1 CO trunk maintenance: out-of-service The trunk is in a deactivated state and cannot be used for either incoming or outgoing calls.
PAGE 819
CO-DS1 (DS1 CO Trunk) Table 281: DS1 CO Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level 1793 (i) Test to Clear Value test board location l 2562 (j) 16665 2817 (k) 52992 3840 (l) On/Off Board Port Audit and Update (#36) 2 of 2 1. Major alarms MO may be downgraded to Warning alarms based on the value used in set options. Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence.
PAGE 820
Communication Manager Maintenance-Object Repair Procedures g. Error Type 513: The DS1 Interface circuit pack detects a hardware fault. Aux Data 57393 indicates belated external release on PBX disconnect. This alarm will only be raised when the System-Parameter Country screen has the Base Tone Generator field set to 4 (Italy). This alarm will be a MINOR alarm unless 75% or more trunks in this trunk group are out of service, then the alarm will be upgraded to a MAJOR alarm.
PAGE 821
CO-DS1 (DS1 CO Trunk) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented. 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 822
Communication Manager Maintenance-Object Repair Procedures Table 282: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the port is active, wait until it is idle before testing. 2.
PAGE 823
CO-DS1 (DS1 CO Trunk) Table 282: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1020 ABRT The test did not run due to a previously existing error on the specific port or a more general circuit pack error. 1. Examine Error Log for existing errors against this port or the circuit pack and attempt to diagnose the already existing error. S8300 G700 ABRT This test does not execute on a G700 Media Gateway.
PAGE 824
Communication Manager Maintenance-Object Repair Procedures Table 282: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, an insane board is inserted, or the board is hyperactive. 1. Verify that the board’s translations are correct.
PAGE 825
CO-DS1 (DS1 CO Trunk) Table 283: Test #7 Conference Circuit Test Error Code Test Result Description / Recommendation ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT The test was aborted. System resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/member number of the port.
PAGE 826
Communication Manager Maintenance-Object Repair Procedures Table 283: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT The test was disabled via translation. You may want to determine why the test has been disabled before you enable it. 1. Verify that the Maintenance Test field on the Trunk Administration form is set to n. To enable the test, change the trunk administration and enter y into the Maintenance Test field. 2. Repeat the test.
PAGE 827
CO-DS1 (DS1 CO Trunk) Table 283: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation Any FAIL The NPE of the tested port did not conference the tones correctly. This will cause noisy and unreliable connections. 1. Enter list configuration board location. If the circuit pack is a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3 or later. The error log may have error type 1281 entries. 2. Test every administered trunk on the board.
PAGE 828
Communication Manager Maintenance-Object Repair Procedures Table 283: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This result could be due to incorrect translations, no board is inserted, an incorrect board is inserted, an insane board is inserted, or the board is hyperactive. 1. Verify that the board’s translations are correct.
PAGE 829
CO-DS1 (DS1 CO Trunk) Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface circuit pack or media module to assure 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. The port audit operation verifies the consistency of the current state of trunk.
PAGE 830
Communication Manager Maintenance-Object Repair Procedures Table 284: Test #36 Port Audit and Update Test (continued) Error Code Test Resul t Description / Recommendation PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack or media module and switch software are consistent. If the trunk is busied out, the test will not run but will return PASS. To verify that the trunk is in-service: 1.
PAGE 831
CO-DS1 (DS1 CO Trunk) DS1 CO Dial Tone Seizure Test (#314) Note: S8300 / G700: This test aborts with Error Code 1412. Note: The DS1 CO Dial Tone Seizure test checks the trunk’s signaling capability provided by the DS1 Interface circuit pack. The maintenance software initiates the test by sending a “seizure” message to the DS1 Interface circuit pack and expects an “active” reply from the DS1 interface circuit pack. If the “active” message is received, then the test passes.
PAGE 832
Communication Manager Maintenance-Object Repair Procedures Table 285: Test #314 DS1 CO Dial Tone Seizure Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The test was aborted because the port was seized by a user for a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is active, wait until it is idle before testing. 2.
PAGE 833
CO-DS1 (DS1 CO Trunk) Table 285: Test #314 DS1 CO Dial Tone Seizure Test (continued) Error Code Test Result Description / Recommendation S8300 / G700 ABRT This test does not execute on a G700 Media Gateway. 2000 ABRT Response to the test request was not received within the allowable time period. 1412 1. Retry the command at 1-minute intervals up to 5 times. 2012 ABRT The test was aborted due to an internal system error. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 834
Communication Manager Maintenance-Object Repair Procedures Table 285: Test #314 DS1 CO Dial Tone Seizure Test (continued) Error Code Test Result Description / Recommendation FAIL The trunk cannot be seized for an outgoing call. This could cause in-line failures to be reported against the trunk (no answer would report error type 257 with auxiliary data 57487 in the error log). 1. Verify the Trunk Type field on the trunk administration screen screen matches the trunk type administered on far-end switch.
PAGE 835
CO-TRK (Analog CO Trunk) CO-TRK (Analog CO Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CO-TRK MAJ1 test port location Analog CO Trunk CO-TRK MIN test port location Analog CO Trunk CO-TRK WRN test port location Analog CO Trunk 1. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least 75% of the trunks in this trunk group are alarmed.
PAGE 836
Communication Manager Maintenance-Object Repair Procedures S8300 / G700 For systems supporting Media Modules: Analog CO trunks are 2-wire analog lines to the CO which support both incoming and outgoing calls. CO trunk MM711 Analog Media Modules have eight ports. Note: Note: Although the CO-TRK MO is provided for G700 and G350 media gateways, this MO only partially supports the MM711 Analog Media Module.
PAGE 837
CO-TRK (Analog CO Trunk) Ground Start Operation Idle state: Tip = open, Ring = CO Battery Outgoing Call: 1. PBX Off-Hook (Seize message): Places ground on Ring CO response: Places ground on Tip PBX response: Close the loop CO response: Provide loop current PBX response: Dial out digits 2. PBX On-Hook first (Drop message): Open the Tip-Ring Loop, no loop current CO response: Open circuit on Tip 3.
PAGE 838
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 286: CO Trunk Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 57347 None 15 (c) any Port Audit Update (#36) 18 0 busyout trunk WRN OFF release trunk grp#/mem# None WRN ON test port location sh r 2 130 (d) 257 (b) 50176 None 513 (b) 57364 None MAJ MIN WRN1 ON 769 (
PAGE 839
CO-TRK (Analog CO Trunk) Table 286: CO Trunk Error Log Entries (continued) Error Type Aux Data Associated Test 3073 (e) 57376 None 3329 (e) 57408 None 3329 (e) 57484 Dial Tone Test (#0) 3585 (e) 57424 None Alarm Level On/Off Board Test to Clear Value MAJ MIN WRN OFF test port location l r 1 The ATMS Transmission Tests are not supported on the G700/G350, and abort with Error Code 1412.
PAGE 840
Communication Manager Maintenance-Object Repair Procedures If error count associated with this error type is very high (i.e., 255) and if Alarm Status on the Hardware Error Report is “n” (not alarmed), then the existence of this error type indicates that, despite the fact that many in-line error messages have been received, every Call Seizure test has passed. Problems at the CO may cause this condition rather than problems with the PBX. f.
PAGE 841
CO-TRK (Analog CO Trunk) Table 287: CO Trunk Errors with No Tests (continued) Error Type Aux Data Error Description and Repair Action 513 57364 Ground detector stuck active. After several occurrences, an on-board minor alarm is generated. Run the short test sequence. If test aborts with Error Code 1000, disconnect Tip and Ring and repeat short test. If test still aborts, replace circuit pack. If test passes, refer problem to CO. If any other error code is received, pursue that problem.
PAGE 842
Communication Manager Maintenance-Object Repair Procedures Table 287: CO Trunk Errors with No Tests (continued) Error Type Aux Data Error Description and Repair Action 3329 57408 Trunk error. No Tip ground detected on outgoing call. This error occurs when an attempt is made to seize a ground-start CO trunk for an outgoing call and Tip ground is not detected or the caller hangs up before Tip ground is detected. 1. Busyout the affected port, and run a long test. Observe the test results.
PAGE 843
CO-TRK (Analog CO Trunk) Order of Investigation Short Test Sequence Long Test Sequence D/ND1 Audit Update test (#36) X X ND ND Transmission test - ATMS (#844-848) S8300 / G700 aborts with Error Code 1412 2 of 2 1. D = Destructive; ND = Nondestructive Note: Note: A Demand Diagnostic test (#3) will always return a PASS indication for CO-TRK/ CO-BD [TN747B] version 8 or greater. However, any errors produced as a result of this test will be logged and produce no alarms.
PAGE 844
Communication Manager Maintenance-Object Repair Procedures Table 288: Test #0 Dial Tone Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port.
PAGE 845
CO-TRK (Analog CO Trunk) Table 288: Test #0 Dial Tone Test (continued) Error Code Test Result Description / Recommendation FAIL Trunk was seized, but dial tone could not be detected. 1. Test every administered outgoing port on the board. Failure of 1 port indicates a problem toward the CO. 2. If every port fails, see note below. 3. Check for errors on the TONE-BD or TONE-PT. Clear any errors found, and repeat the test. 4. If the error has still not cleared, refer the problem to the CO. 5.
PAGE 846
Communication Manager Maintenance-Object Repair Procedures Table 288: Test #0 Dial Tone Test (continued) Error Code 0 Test Result Description / Recommendation PASS Trunk was seized, and dial tone was detected. User-reported troubles on this port should be investigated by using other port tests and by examining trunk or external wiring. NO BOARD The test could not relate the internal ID to the port. 1. Verify that the board’s translations are correct. Translate the board, if necessary. 2.
PAGE 847
CO-TRK (Analog CO Trunk) Table 289: Test #3 CO Demand Diagnostic Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the service state indicates that the port is active, then it is unavailable for certain tests.
PAGE 848
Communication Manager Maintenance-Object Repair Procedures Table 289: Test #3 CO Demand Diagnostic Test (continued) Error Code Test Result Description / Recommendation FAIL Failure to detect ground or faulty ground detected on Ring lead. Display the hardware errors for this trunk, to determine whether the fault was on- or off-board. Look for Error Type 1025 or 1281 (if both appear in the Hardware Error Log, pick the most recent error).
PAGE 849
CO-TRK (Analog CO Trunk) Table 289: Test #3 CO Demand Diagnostic Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). 1. Verify that the board’s translations are correct. Translate the board, if necessary. 2. Enter busyout board location 3. Enter reset board location 4. Enter release board location 5. Enter test board location This should re-establish the linkage between the internal ID and the port.
PAGE 850
Communication Manager Maintenance-Object Repair Procedures Table 290: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT The port was seized by a user for a valid call. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the port is active, wait until it is idle before testing. 2.
PAGE 851
CO-TRK (Analog CO Trunk) Table 290: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation S8300 / G700 ABRT This test does not execute on a G700 media gateway. 2000 ABRT Response to the test request was not received within the allowable time period. 1412 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 852
Communication Manager Maintenance-Object Repair Procedures Looparound and Conference Circuit Test (#33) Note: Note: S8300 / G700: This test aborts with Error Code 1412. This test checks the reflective loop-around and conference capabilities of a CO port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. Each tone is transmitted separately through the loop and checked.
PAGE 853
CO-TRK (Analog CO Trunk) Table 291: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command at 1-minute intervals up to 5 times.
PAGE 854
Communication Manager Maintenance-Object Repair Procedures Table 291: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 7 FAIL The conference capabilities of the port failed (Error Code 7). 129 The reflective 404-Hz Tone test failed. No transmission was detected to or from the port (Error Code 129). FAULT ISOLATION: Proceed as follows unless power or tone problems are suspected (see Description/Recommendation for Error Code 7 below). 2.
PAGE 855
CO-TRK (Analog CO Trunk) Table 291: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 7 129 131 133 FAIL If the Looparound and Conference Circuit test (#33) fails for every port on a circuit pack, a -5 Volt power problem is indicated. To investigate problems with a power unit, see CARR-POW (Carrier Power Supply) on page 770 or RMC-ENV (Power/Fan Sensors) on page 1951. If a red LED is lit on the power unit circuit pack, replace the pack.
PAGE 856
Communication Manager Maintenance-Object Repair Procedures Port Audit Update Test (#36) This test will send updates of the CO port translation for every port on the circuit pack or media module that has been translated. The update is non-disruptive and guards against possible corruption of translation data contained on the circuit pack or media module. No response message is expected from the circuit pack or media module once it receives translation updates.
PAGE 857
CO-TRK (Analog CO Trunk) Table 292: Test #36 Port Audit Update Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). 1. Verify that the board’s translations are correct. Translate the board, if necessary. 2. Enter busyout board location 3. Enter reset board location 4. Enter release board location 5. Enter test board location This should re-establish the linkage between the internal ID and the port.
PAGE 858
Communication Manager Maintenance-Object Repair Procedures Table 293: Test #844-848 Transmission Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the port is active, wait until it is idle before testing. 2.
PAGE 859
CO-TRK (Analog CO Trunk) Table 293: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1905 ABRT Intercept tone detected from far end. 1. Get the test line data from and verify it with the far end. 2. Dial the test number manually to see if the TTL is reached. If not, then either the number is wrong or the far end is administered incorrectly. 1906 ABRT Reorder tone detected from far end. 1. See actions for error code 1905.
PAGE 860
Communication Manager Maintenance-Object Repair Procedures Table 293: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1922 ABRT Steady, unidentifiable tone from far end 1. See actions for error code 1905. 1923 ABRT Broadband energy detected from far end (such as voice or announcement). 1. See actions for error code 1905. 1924 ABRT No test tone from far end 1. See actions for error code 1905. 1938 ABRT Near-end self test failed. 1.
PAGE 861
CO-TRK (Analog CO Trunk) Table 293: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1947 ABRT Noise with tone self check failed. 1. Test the TN771 circuit packs or. 2000 ABRT The test timed out while waiting for a response from the TN771 circuit pack. Retry the command at 1-minute intervals up to 5 times. 2012 ABRT An internal software error occurred. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 862
Communication Manager Maintenance-Object Repair Procedures CONFIG (System Configuration) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO CONFIG none none System Configuration The System Configuration MO oversees logical insertion and removal of circuit packs in the system.
PAGE 863
CONFIG (System Configuration) d. Error Types 1001 - 1119: a port circuit pack in the system did not respond to a vintage inquiry. As a result of any of these errors, a port circuit pack may be physically inserted in a port slot, but the system may not recognize its existence. The Aux Data field specifies the circuit pack’s port-network number as indicated in the following table.
PAGE 864
Communication Manager Maintenance-Object Repair Procedures If the Error Type is greater than 1000, subtract 1000 from the Error Type field before consulting the table. S8700 MC:Before proceeding, if multiple CONFIG errors are simultaneously logged with an Aux Data of 1, investigate any EXP-INTF (Expansion Interface) errors.
PAGE 865
CONFIG (System Configuration) Table 295: Converting Error Types To Carrier Locations (continued) Error Type Carrier Location 22 E00 (d) 23 (a) 24 (a) 25 (a) 26 (a) 27 A00 (e) 28 A01 (b) 29 A02 30 A03 31 A04 32 (a) 33 (a) 34 D01 35 D02 36 D03 37 D04 38 D05 39 D06 40 D07 41 D08 42 D09 43 D10 44 D11 45 D12 46 D13 47 D14 48 D15 2 of 5 Issue 1 June 2005 865
PAGE 866
Communication Manager Maintenance-Object Repair Procedures Table 295: Converting Error Types To Carrier Locations (continued) Error Type Carrier Location 49 D16 50 D17 51 D18 52 D19 53 D20 54 D00 (d) 55 (a) 56 A05 57 A06 58 A07 59 A08 60 A09 61 A10 (c) 62 A11 63 A12 64 (a) 65 (a) 66 B01 67 B02 68 B03 69 B04 70 B05 71 B06 72 B07 73 B08 74 B09 75 B10 3 of 5 866 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 867
CONFIG (System Configuration) Table 295: Converting Error Types To Carrier Locations (continued) Error Type Carrier Location 76 B11 77 B12 78 B13 79 B14 80 B15 81 B16 82 B17 83 B18 84 B19 85 B20 86 B00 (d) 87 (a) 88 A13 89 A14 90 A15 91 A16 92 A17 93 A18 94 A19 95 A20 96 (a) 97 (a) 98 C01 99 C02 100 C03 101 C04 102 C05 4 of 5 Issue 1 June 2005 867
PAGE 868
Communication Manager Maintenance-Object Repair Procedures Table 295: Converting Error Types To Carrier Locations (continued) Error Type Carrier Location 103 C06 104 C07 105 C08 106 C09 107 C10 108 C11 109 C12 110 C13 111 C14 112 C15 113 C16 114 C17 115 C18 116 C19 117 C20 118 C00 (d) 119 (a) 5 of 5 Notes: a. Error Types 1, 23, 25, 25, 26, 32, 33, 55, 64, 65, 87, 96, 97, 119 do not represent physical port circuit pack slots and are not logged against CONFIG.. b.
PAGE 869
CUST-ALM (Customer-Provided Alarming Device) CUST-ALM (Customer-Provided Alarming Device) S8700 | 8710 / S8500 See MAINT (PN’s Maintenance Circuit Pack) on page 1490 for information about this maintenance object.
PAGE 870
Communication Manager Maintenance-Object Repair Procedures DAT-LINE (Data Line Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DAT-LINE MIN test port location l Data Line port DAT-LINE WRN test port location l Data Line port The TN726 Data Line circuit pack has eight ports, each of which supports an RS-232 interface to asynchronous CPE (customer-premises equipment).
PAGE 871
DAT-LINE (Data Line Port) Table 296: Data Line Port Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 15(b) Any Audit Update test (#36) 18 0 busyout port location WRN OFF rel port location 130 (c) None WRN ON test port location sh 257 Conference Circuit test (#7) MIN ON test port location l r 2 513 NPE Crosstalk test (#6) MIN ON test port location l r 2 769(d) 40983 None 2 of 2 Notes: a.
PAGE 872
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Digital Looparound test, you may also clear errors generated from other tests in the testing sequence.
PAGE 873
DAT-LINE (Data Line Port) Table 297: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. Resolve any TDM-BUS errors. 2. If the system is not handling heavy traffic, retry the command at 1-minute intervals up to 5 times.
PAGE 874
Communication Manager Maintenance-Object Repair Procedures 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. If the level of the tone is within a certain range, the test passes.
PAGE 875
DAT-LINE (Data Line Port) Audit Update Test (#36) This audit verifies that the hardware state of the data line is consistent with the system translations. The audit queries the port for the switchhook state, the software state is updated according to the returned value. Also, the audit data line options down to the port. Table 299: Test #36 Audit Update Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. 1.
PAGE 876
Communication Manager Maintenance-Object Repair Procedures Digital Loop-Around Test (#171) The Digital Looparound test checks the data line port’s ability to transmit and receive data on the TDM Bus. Data is sent through an available Maintenance/Test digital port over the TDM Bus, internally looped through the data line port back onto the TDM Bus, and received again by the same Maintenance/Test digital port.
PAGE 877
DAT-LINE (Data Line Port) Table 300: Test #171 Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1042 ABRT Port under test is a TTI port and has only default translations with no assigned extension. The executed test requires an assigned extension associated with the port being tested. Therefore, this test cannot successfully execute. 1.
PAGE 878
Communication Manager Maintenance-Object Repair Procedures Table 300: Test #171 Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1392 ABRT 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 display port (the display shows that the port is a TTI port) or list config (the display shows a “t” for the port). 2.
PAGE 879
DAT-LINE (Data Line Port) Table 300: Test #171 Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2313 ABRT Failed to receive a response from the Maintenance/Test digital port. 1. Resolve any M/T-DIG errors. 2. Retry the command at 1-minute intervals up to 5 times. 3. If the test continues to abort, replace the Maintenance/Test circuit pack. 2314 ABRT Data line port did not respond to downlinked message. 1.
PAGE 880
Communication Manager Maintenance-Object Repair Procedures DC-POWER (Single-Carrier Cabinet Environment) S8700 MC only MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DC-POWER MAJ test environment UU (UU is the universal cabinet number in the PORT field of the alarm log) Single-Carrier Cabinet Environment The S8700 Sever in a Multi-Connect configuration supports two different cabinet types: multicarrier and single-carrier. Single-carrier cabinets are used only for PNs.
PAGE 881
DC-POWER (Single-Carrier Cabinet Environment) If a Carrier Port Power Supply is physically removed from a carrier in a single-carrier cabinet, there will not be a DC-POWER alarm. DC-POWER maintenance cannot distinguish between removal of the power supply and the physical absence of the cabinet. There is a nominal power holdover of.25 second in an PN single-carrier cabinet.
PAGE 882
Communication Manager Maintenance-Object Repair Procedures Notes: a. See EMG-XFER (Emergency Transfer) on page 1134 for a description. b. See EXT-DEV ADMIN? Y (External Device Alarm) on page 1246 for a description. c. See RING-GEN (Analog Ring Generator) on page 1942 for a description. Single-Carrier Cabinet Power Query Test (#79) This test queries an PN’s Maintenance circuit pack about the power’s status in a single-carrier cabinet PN.
PAGE 883
DC-POWER (Single-Carrier Cabinet Environment) Table 302: Test #79 Single-Carrier Cabinet Power Query Test (continued) Error Code Test Result Description / Recommendation 1 FAIL There is currently a problem with the environment of the power system. 1. The power supply to any one of the carriers may have been lost. a. Verify, and if necessary restore, AC power at the wall outlet for each carrier. b. Rerun the test. If the test still fails, proceed to step 2. 2.
PAGE 884
Communication Manager Maintenance-Object Repair Procedures DETR-BD (Tone Detector Circuit) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DETR-BD MIN test board location Tone Detector circuit DETR-BD WRN test board location Tone Detector circuit For proper tone detection, the companding mode administered for the system must match that of the DETR-BD circuit. The companding mode is administered on the location-parameters screen.
PAGE 885
DID-BD (Direct Inward Dial Trunk Circuit Pack) DID-BD (Direct Inward Dial Trunk Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DID-BD MIN test board location sh Direct Inward Dial Trunk circuit pack DID-BD WRN test board location sh Direct Inward Dial Trunk circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors.
PAGE 886
Communication Manager Maintenance-Object Repair Procedures DID-DS1 (Direct Inward Dial Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DID-DS1 MAJ1 test trunk grp#/mem# long Direct Inward Dial Trunk DID-DS1 MIN test trunk grp#/mem# long Direct Inward Dial Trunk DID-DS1 WRN test trunk grp#/mem# Direct Inward Dial Trunk 1.
PAGE 887
DID-DS1 (Direct Inward Dial Trunk) Error Log Entries and Test to Clear Values Table 303: DID-DS1 Trunk Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test trunk grp#/mem# 1 (b) Any 15 (c) Any WRN OFF release trunk grp#/ mem# WRN ON test trunk grp#/mem# Port Audit and Update test (#36) 18 (d) None 130 (e) 257 (f) 57474 57473 513 (g) 57392 MAJ MIN1 769 (h) 57393 MAJ MIN 1 1281 Conference Circuit test (#7)
PAGE 888
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description, and follow its recommended procedures. b. Error Type 1: DS1 Interface circuit pack or media module detects a hardware error on the DS1 DID trunk.
PAGE 889
DID-DS1 (Direct Inward Dial Trunk) j. Error Type 2305 indicates that a signaling change was detected by the PBX trunk circuit pack or media module which is inconsistent with the present state of the trunk. k. Error Type 3840: Port Audit and Update test (#36) failed due to an internal system error. Enter status trunk to verify the status of the trunk. If the trunk is out-of-service, enter release trunk to put it back to in-service. Retry the test command.
PAGE 890
Communication Manager Maintenance-Object Repair Procedures Table 304: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required for this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is in use, wait until it is idle before testing. 2.
PAGE 891
DID-DS1 (Direct Inward Dial Trunk) Table 304: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a user for a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is in use, wait until it is idle before testing. 2. If the port status is idle, retry the command at 1-minute intervals up to 5 times.
PAGE 892
Communication Manager Maintenance-Object Repair Procedures Table 304: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port. This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board translations are correct. Enter list config, and resolve any problems that are found. 2.
PAGE 893
DID-DS1 (Direct Inward Dial Trunk) Table 305: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required for this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is in use, wait until it is idle before testing. 2.
PAGE 894
Communication Manager Maintenance-Object Repair Procedures Table 305: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT The test was disabled via translation. Determine why the test has been disabled before you enable it. 1. Verify that the Maintenance Test field on the Trunk Administration form is n. Enter y to enable the test. 2. Repeat the test.
PAGE 895
DID-DS1 (Direct Inward Dial Trunk) Table 305: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation Any FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1. Enter list configuration board location. The circuit pack must be a TN767C V3 or later. The error log may have Error Type #1281. 2. Test every administered trunk on the board.
PAGE 896
Communication Manager Maintenance-Object Repair Procedures Port Audit and Update Test (#36) This test sends port-level translation data from the switch processor to the DS1 Interface circuit pack or media module to assure that a trunk’s translations are correct. The port audit operation verifies the consistency of the current state of the trunk as kept in the DS1 Interface circuit pack or media module and in switch software.
PAGE 897
DID-DS1 (Direct Inward Dial Trunk) Table 306: Test #36 Port Audit and Update Test (continued) Error Code Test Result Description / Recommendation PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack media module and switch software are consistent. If the trunk is busied out, the test will not run but will return PASS. To verify that the trunk is in-service: 1. Enter status trunk to verify that the trunk is in-service.
PAGE 898
Communication Manager Maintenance-Object Repair Procedures DID-TRK (Direct Inward Dial Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DID-TRK MAJ1 test port location l DID Trunk DID-TRK MIN test port location l DID Trunk DID-TRK WRN None DID Trunk 1. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least 75 percent of the trunks in this trunk group are alarmed.
PAGE 899
DID-TRK (Direct Inward Dial Trunk) DID Trunk Operation The DID port receives three to seven digits from the CO that are used to directly connect an outside caller to the called station without assistance from an attendant. For each call, the CO switch signals the system by opening and closing individual DID loops (one of the eight ports), causing the starting or stopping of loop current. DID Trunk Testing The system uses technician-invoked tests of on-board circuitry to diagnose the health of the trunk.
PAGE 900
Communication Manager Maintenance-Object Repair Procedures Table 307: DID Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 1 (b) Any None WRN OFF 1 (c) 57476 None WRN OFF 1 (d) 57477 None WRN OFF 1 (e) 57483 None WRN OFF 15 (f) Any Port Audit Update (#36) 18 0 busyout trunk grp#/ mem# WRN OFF release trunk grp#/mem# None WRN ON test trunk grp#/mem# 130 (g) Test to Clear Value 257 (h) 57472 None WRN OFF 257 (i) 574
PAGE 901
DID-TRK (Direct Inward Dial Trunk) Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. b. Error Type 1; Aux Data - Any occurs when the tone detector times out waiting for digits. Change wink/immediate-start parameter to wink/immediate-start and rotary/tone-dial parameters. 1. Verify trunk administered wink/immediate-start parameter. 2. Test trunk using BUTT set. 3. Refer problem to CO. c.
PAGE 902
Communication Manager Maintenance-Object Repair Procedures j. Error Type 257; Aux Data - 57474: Rotary dial rate above 12 pulses/sec, less than 75 msec between two successive breaks. 1. Verify trunk administered interdigit-timing parameters. 2. Refer problem to CO. k. Error Type 257; Aux Data - 57475: Digit detection, CO is starting new rotary dial digit within 150 msec of previous digit. 1. Verify trunk administered interdigit timing parameters. 2. Refer problem to CO. l.
PAGE 903
DID-TRK (Direct Inward Dial Trunk) Order of Investigation Short Test Sequence Looparound and Conference Circuit test (#33) S8300 / G700: This test aborts with Error Code 1412. Port Audit Update test (#36) X Long Test Sequence D/ND1 X ND X ND 2 of 2 1. D = Destructive; ND = Nondestructive NPE Crosstalk Test (#6) Note: S8300 / G700: This test aborts with Error Code 1412.
PAGE 904
Communication Manager Maintenance-Object Repair Procedures Table 308: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 905
DID-TRK (Direct Inward Dial Trunk) Table 308: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL This test can fail due to off-board problems, including EXP-PN and EXP-INTF faults RMC-ENV faults (S8700 IP), TDM-BUS faults, and Tone Detectors/Tone Generators. Clear every off-board problem before replacing the board. A TDM-BUS problem is usually a faulty board or bent pins on the backplane. 1.
PAGE 906
Communication Manager Maintenance-Object Repair Procedures Table 309: Test #33 Loop-Around and Conference Circuit Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. This could be due to a failure to seize the port. 1. Retry the command at 1-minute intervals up to 5 times. 3 ABRT System resources required to run this test are not available. The seized tone detector did not respond.
PAGE 907
DID-TRK (Direct Inward Dial Trunk) Table 309: Test #33 Loop-Around and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test disabled by administration. Verify that the Maintenance Tests? field on the Trunk Group form is set to n. To enable the test, enter change trunk-group x (x is the trunk group number). Enter y in the Maintenance Tests field. S8300 / G700 ABRT This test does not execute on a G700 Media Gateway.
PAGE 908
Communication Manager Maintenance-Object Repair Procedures Table 309: Test #33 Loop-Around and Conference Circuit Test (continued) Error Code 7 Test Result Description / Recommendation The conference capabilities of the port failed. Poor-quality transmission was detected to or from the port. The problem may be off-board. See additional information for this error code below. ! CAUTION: CAUTION: 129 The port may still be operational, or the fault may be off-board (connections or CO).
PAGE 909
DID-TRK (Direct Inward Dial Trunk) Table 309: Test #33 Loop-Around and Conference Circuit Test (continued) Error Code 131 Test Result Description / Recommendation The reflective 1004-Hz tone test failed. Poor-quality transmission was detected to or from the port. The problem may be off-board. See additional information for this error code below. ! CAUTION: CAUTION: 133 The port may still be operational, or the fault may be off-board (connections or CO).
PAGE 910
Communication Manager Maintenance-Object Repair Procedures Table 309: Test #33 Loop-Around and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 3 7 129 131 133 FAIL Proceed as follows unless power or tone problems are suspected (see following note). (cont’d) 1. To see if the problem is on-board, disconnect the port from the far end, and retry the test. Coordinate this with the CO, or do it after busy hours. (cont’d) 2.
PAGE 911
DID-TRK (Direct Inward Dial Trunk) Port Diagnostic Test (#35) This test checks a port’s battery feed circuitry for on-/off-hook detection, battery shutdown, and battery reversal (wink) capabilities. Table 310: Test #35 Port Diagnostic Test Error Code Test Result Description / Recommendation ABRT System resources required to run this test were not available. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test were not available.
PAGE 912
Communication Manager Maintenance-Object Repair Procedures Table 310: Test #35 Port Diagnostic Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received within the allowable time period. 1. Rerun the test at 1-minute intervals up to 5 times. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 61446 FAIL Battery feed test failed.
PAGE 913
DID-TRK (Direct Inward Dial Trunk) Table 310: Test #35 Port Diagnostic Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). 1. Verify that the board’s translations are correct. Translate the board if necessary. 2. Enter busyout board location 3. Enter reset board location 4. Enter release board location 5. Enter test board location This should re-establish the linkage between the internal ID and the port.
PAGE 914
Communication Manager Maintenance-Object Repair Procedures Table 311: Test #36 Port Audit Update Test (continued) Error Code Test Result Description / Recommendation 1006 ABRT The port is out of service, perhaps busied out. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the port is out of service, wait until the port is in service and idle before testing. 2.
PAGE 915
DIG-BD (Digital Line Circuit Pack) DIG-BD (Digital Line Circuit Pack) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIG-BD MIN test board location sh Digital Line circuit pack DIG-BD WRN test board location sh Digital Line circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors. See also DIG-LINE (Digital Line) on page 924 in this chapter for related line information.
PAGE 916
Communication Manager Maintenance-Object Repair Procedures DIG-IP-STN (Digital IP Station) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIG-IP-S WRN test station extension Digital IP Station The DIG-IP-STN MO represents Softphone and Avaya 46XX phones. Softphone has some DCP maintenance capability in the form of audits, updates, error log entries, and test to clear values.
PAGE 917
DIG-IP-STN (Digital IP Station) Table 312: DIG-IP-STN Digital IP Station Error Log Entries (continued) Error Type Aux Data (e) Associated Test Alarm Level On/Off Board Digital Terminal Audit Update (#17) WRN OFF Test to Clear Value 513 (f) Any Station Digital AUDIT test (#17) WRN OFF test port | station 1281 (g) Any Station Digital AUDIT test (#17) WRN OFF test port | station 1537 (h) 40968 WRN OFF test port | station WRN OFF None 1793 (i) 2305 (j) 2817 (k) Any None Station
PAGE 918
Communication Manager Maintenance-Object Repair Procedures g. Error Type 1281 indicates that the terminal is reporting a bad state of health (IP terminal only). h. Error Type 1537 indicates that the link has gone down between the terminal and its gateway to the switch. This likely means that the terminal has unregistered (IP terminal only). i. Error Type 1793: indicates the IP station has registered with a Local Survivable Processor (LSP).
PAGE 919
DIG-IP-STN (Digital IP Station) Registration Status Inquiry (#1372) The Registration status inquiry reports the H.323 registration status of the endpoint. An endpoint must be registered and authenticated in order to receive service from the system. Registration is initiated when the endpoint user attempts to login using the Avaya registration software application running on the endpoint PC. The user must provide a valid extension and security code.
PAGE 920
Communication Manager Maintenance-Object Repair Procedures Note: Note: Multiple failures of this test can take the Digital IP Station out of service. This test checks the circuitry involved in the data path of a peer-to-peer IP layer connection. Note: Note: This nondestructive test runs due to in-line errors, during periodic and schedule maintenance, and on demand.
PAGE 921
DIG-IP-STN (Digital IP Station) Digital Terminal Lamp Update (#16) This test updates internal lamp states that can or cannot be shown on the actual PC graphical user interface. The lamp updates 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. This test does not affect the status of the Message Waiting lamp.
PAGE 922
Communication Manager Maintenance-Object Repair Procedures Digital Terminal Audits Test (#17) This is a series of tests that are classified as audits. The media server sends messages to the softphone application or IP phone to perform the following tests. These audits run only if the station is in-service. ● Switchhook Inquiry test updates the media server’s records according to the softphone switch-hook state.
PAGE 923
DIG-IP-STN (Digital IP Station) Table 316: Test #17 Station (Digital) Audits Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received in the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. PASS Station Audits passed. 1. If complaints persist, investigate by using other port tests, and by examining the station, wiring, and connections.
PAGE 924
Communication Manager Maintenance-Object Repair Procedures DIG-LINE (Digital Line) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIG-LINE MIN test port location l Digital Line DIG-LINE WRN test port location sh Digital Line DIG-LINE monitors and tests ports on digital line circuit packs or digital line media modules and on hardware administered as a digital station on those ports.
PAGE 925
DIG-LINE (Digital Line) Each digital line port supports two 64 kbps information channels (primary and secondary) and one 8kbps signaling channel. Digital voice terminals always use the primary information channel, and only one voice terminal can be connected to each port. The secondary information channel can be used to connect a data terminal via a Digital Terminal Data Module (DTDM) or a Data Adaptor (DA).
PAGE 926
Communication Manager Maintenance-Object Repair Procedures Figure 46: Digital Line Connections TN2136 Digital Line Circuit Pack Digital Line Port ............................................................................................................ . . . . . . Physical Connection . . . .. . . .. . Data Italtel . . . Port . . Digital Adaptor . . . . Control Channel (Signaling) . IDCP . Telephone (Linked . . . . . . . . . . . . . . .. . . . Model 1/2 . . Mode) . . . . . .. . . Port .. .
PAGE 927
DIG-LINE (Digital Line) Service States Digital line maintenance interacts with digital line circuit pack (DIG-BD), or with digital line media module (MG-DCP) maintenance. The health of the digital-line circuit pack or media module can affect the results of DIG-LINE testing. Keep this in mind when investigating digital-line problems. It is sometimes important to know the service state of a station.
PAGE 928
Communication Manager Maintenance-Object Repair Procedures Circuit Packs: ● 8400x, 302B1 Terminals ● TN754 (4-wire, mu-law) Note: Minimum usable vintage for 8410D and 8434D terminals - V11 Note: ● ● TN413 (4-wire, A-law) ● TN754B (4-wire, A-law/mu-law selectable) ● TN2177 (2-wire, 16-port, A-law/mu-law selectable) ● TN2181 (2-wire, 16-port, A-law/mu-law selectable) ● TN2224 (2-wire, 24-port, A-law/mu-law selectable) 603A1/D1 Terminals ● TN754 (4-wire, mu-law), ● TN413 (4-wire, A-law) ●
PAGE 929
DIG-LINE (Digital Line) Nonvolatile Memory Nonvolatile memory stores downloadable parameters in programmable terminals. Once the terminal is downloaded, it is not be necessary to download it again, even if power is removed from the terminal. If nonvolatile memory fails with power still present, the terminal reverts to its default factory settings except for its A-law/mu-law companding settings which are stored in RAM.
PAGE 930
Communication Manager Maintenance-Object Repair Procedures Note: Note: It may take more than 1 hour for periodic tests to reach the terminal that needs to be downloaded. Terminal Administration A downloadable terminal is automatically downloaded when translation changes associated with downloadable parameters are made as part of system administration. As shown in Table 318: Parameters Downloadable to Programmable Terminals on page 928, these changes can be for a specified terminal or may be system-wide.
PAGE 931
DIG-LINE (Digital Line) Demand Download Actions Busyout/Release Command A maintenance demand busyout/release request for a station causes the terminal to be downloaded regardless of its previous download status. Feature Access Code A Refresh Terminal Parameters Feature Access Code can be used to request a terminal download action. When this code is followed by a pound sign (#), the programmable parameters for the current terminal are downloaded when the terminal goes on hook.
PAGE 932
Communication Manager Maintenance-Object Repair Procedures Possible reasons for a terminal not being downloaded include: ● Terminal is off-hook. ● Terminal detected a bad checksum. ● Terminal detected a bad or missing EEPROM (refer to hardware error log). ● Terminal is busy programming data from a previous PROGRAM message. ● Terminal is in the Programming Disabled state. ● Terminal is in the Local Program Options mode. ● Terminal is disconnected or out of service (use status station).
PAGE 933
DIG-LINE (Digital Line) Table 319: Digital Line Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1793 Voice and Ctrl. Local Loop test (#13) MIN WRN1 ON test port location l r 3 2049 NPE Crosstalk test (#9) MIN WRN2 ON test port location l r 3 2304 (l) None 2305 (m) (n) 32770 40969 None 2817 (o) Any None 3840 (q) (r) 40965 40989 None 3841 (s) 41029 None OFF 3585 (p) 2 of 2 1.
PAGE 934
Communication Manager Maintenance-Object Repair Procedures e. Error Type 130 indicates that the circuit pack or media module has been removed or has been insane for more than 21 minutes. To clear the error, reinsert or replace the circuit pack or media module. f. Error Type 257 indicates problems transmitting to the voice terminal. This can be caused by defective wiring, which can cause varying degrees of problems on different types of sets.
PAGE 935
DIG-LINE (Digital Line) m. Error Type 2305; Aux Data - 32770: This indicates that the station went off-hook while it was in the ready-for-service state. Use status station to determine the state of the station. The off-hook should have moved the station to ready-for-service. No craft action is necessary. n. Error Type 2305; Aux Data - 40967: An in-line maintenance error has generated an off-board warning due to some problem with the link to the voice terminal.
PAGE 936
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Voice and Control Channel Local Loop-Around test, you may also clear errors generated from other tests in the sequence. Order of Investigation Short Test Sequence Long Test Sequence D/ND1 Digital Terminal Remote Loop-around Test (#1201) S8300 / G700: This test aborts with Error Code 1412.
PAGE 937
DIG-LINE (Digital Line) 2. If the primary information channel test is successful, the loop-around test for the secondary information (data, Information Channel 2 or I2) channel is then performed. This is the same test as the primary information channel’s loop around test and is performed only if a DTDM is administered. This is also the case for a linked DA. Only one value (Pass, Fail, or Abort) is generated as a result of the two tests run. If any test fails aborts, the sequence is stopped.
PAGE 938
Communication Manager Maintenance-Object Repair Procedures Table 320: Test #1201 Digital Terminal Remote Loop-around Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid call during the test. 1. Enter display port location to determine the station extension or attendant number of the port. Use status station or status attendant to determine the service state of the port. If the port is in use, wait until it is idle before resetting.
PAGE 939
DIG-LINE (Digital Line) Table 320: Test #1201 Digital Terminal Remote Loop-around Test (continued) Error Code Test Result Description / Recommendation 16 FAIL The secondary channel is not operating properly. User impact may range from noticing nothing to not being able to use this terminal. 1. Check the results of Voice and Control Channel Local Loop test (#13). 2. If that test fails, suspect the Digital Line circuit pack. If that test passes then replace the terminal. 3.
PAGE 940
Communication Manager Maintenance-Object Repair Procedures Crosstalk testing is performed on both the primary information channel (voice) and the secondary information channel (data) associated with each digital station port. If this test fails on either channel, the station and the DTDM are taken out-of-service.
PAGE 941
DIG-LINE (Digital Line) Table 321: Test #9 Digital Line NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors. 2. Resolve any TONE-PT errors. 3. If neither condition exists, retry the command at 1-minute intervals up to 5 times.
PAGE 942
Communication Manager Maintenance-Object Repair Procedures Digital Line Electronic Power Feed/Positive Temperature Coefficient/PPF Test (#11) S8700 | 8710 / S8500 For TN413, and TN754 vintage 13 or earlier, this is an Electronic Power Feed (EPF) restoral test. In this test, the processor requests that the EPF be turned on for a given port, and an attempt is made to turn on the power supply to the station. If no current is drawn, the station is probably not connected.
PAGE 943
DIG-LINE (Digital Line) Table 322: Test #11 Digital Line Electronic Power Feed Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Enter display port location to determine the station extension or attendant number of the port. Use status station or status attendant to determine the service state of the port. If the port is in use, wait until it is idle before testing.
PAGE 944
Communication Manager Maintenance-Object Repair Procedures Voice and Control Channel Local Loop Test (#13) Note: S8300 / G700: This test aborts with Error Code 1412. Note: These tests check the information and control channels between the media server and the Digital Line port circuit. The media server sends a message to loop around both the port’s information and control channels. 1. First, the primary information (voice) channel’s loop-back test is run.
PAGE 945
DIG-LINE (Digital Line) Table 323: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 946
Communication Manager Maintenance-Object Repair Procedures Table 323: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 14 FAIL The primary voice channel is not transmitting properly. User impact may range from noticing nothing to not being able to use this port. 15 FAIL The control channel between the processor and digital circuit pack is not transmitting properly.
PAGE 947
DIG-LINE (Digital Line) Table 324: Test #16 DIG-LINE Station Lamp Updates Test (continued) Error Code Test Result Description / Recommendation 1 ABRT This port may have been busied out by system technician. 1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this error type is present, then release the port via release station extension and run the test again. 2. Make sure that the terminal is connected. 3. Retry the command at 1-minute intervals up to 5 times.
PAGE 948
Communication Manager Maintenance-Object Repair Procedures Table 324: Test #16 DIG-LINE Station Lamp Updates Test (continued) Error Code Test 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 all lamps do not light, the other Digital Line test results may indicate related problems that do not allow the lamps to light. 2.
PAGE 949
DIG-LINE (Digital Line) S8300 / G700 ● For the MM712 Media Module, the status of the EPF is sent uplink. Possible conditions are EPF-on-ok, EPF-off, and EPF-no-load. Table 325: Test #17 Station (Digital) Audits Test Error Code Test Result Description / Recommendation 1 ABRT Switchhook audit timed out. 2 ABRT ID request fails, health bit returned from voice terminal is bad. 1. Make sure voice terminal is connected, and repeat the test. 2. If test fails, replace voice terminal and repeat test.
PAGE 950
Communication Manager Maintenance-Object Repair Procedures Table 325: Test #17 Station (Digital) Audits Test (continued) Error Code Test Result Description / Recommendation 6 ABRT This port may have been busied out by system technician. 1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this error is present, the release the port via release station extension. 2. Make sure that the terminal is connected. 3. Retry the command at 1-minute intervals up to 5 times.
PAGE 951
DIOD-BD (DIOD Trunk Circuit Pack) DIOD-BD (DIOD Trunk Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIOD-BD MIN test port location s DIOD circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 952
Communication Manager Maintenance-Object Repair Procedures DIOD-DS1 (DS1 DIOD Trunk) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIOD-DS1 MAJ1 test trunk grp#/mem# l DS1 DIOD Trunk DIOD-DS1 MIN test trunk grp#/mem# l DS1 DIOD Trunk DIOD-DS1 WRN test trunk grp#/mem# DS1 DIOD Trunk 1.
PAGE 953
DIOD-DS1 (DS1 DIOD Trunk) Three trunk service states are specified by DS1 DIOD trunk maintenance: out-of-service The trunk is in a deactivated state and cannot be used for either incoming or outgoing calls. in-service The trunk is in an activated state and can be used for both incoming and outgoing calls. disconnect (ready-for-service) The trunk is in an activated state but can only be used for an incoming call.
PAGE 954
Communication Manager Maintenance-Object Repair Procedures Table 326: DS1 DIOD Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1025 DS1 CO Dial Tone Seizure (#314) MIN WRN2 OFF test trunk grp#/mem# r 2 1281 Conference Circuit test (#7) MIN WRN2 ON test trunk grp#/mem# l r 4 1537 NPE Crosstalk test (#6) MIN WRN2 ON test trunk grp#/mem# l r 3 1793 (j) test board location l 2049 (k) 57473 57474 57475 2305 (l) 50944
PAGE 955
DIOD-DS1 (DS1 DIOD Trunk) c. Error Type 15 is a software audit error that does not indicate any hardware malfunction. Run short test sequence, and investigate any errors. d. Error Type 18: System Technician has busied out the trunk to the out-of-service state. No calls can be made on this trunk except Facility Access Test Calls. For details, see Facility test calls in Maintenance Procedures (03-300192). e.
PAGE 956
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented. By clearing error codes associated with the NPE Crosstalk test, for example, you may also clear errors generated from other tests in the sequence.
PAGE 957
DIOD-DS1 (DS1 DIOD Trunk) Table 328: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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 958
Communication Manager Maintenance-Object Repair Procedures Table 328: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2053 ABRT At least one of the following errors is found on the DS1 circuit pack: ● 1281 – Loss of signal ● 1793 – Blue alarm ● 2049 – Red alarm ● 2305 – Yellow alarm ● 1537 – Hyperactivity Look for the previous error types in the Hardware Error Log, and follow the procedures given in the DS1-BD (DS1 Interface Circuit Pack) on page 97
PAGE 959
DIOD-DS1 (DS1 DIOD Trunk) Table 329: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be in use on a valid call. 1. Use status station or status trunk to determine when the port is available for testing. 1004 ABRT The port has been seized by a user for a valid call. 1. Use status station or status trunk to determine when the port is available for testing. 2.
PAGE 960
Communication Manager Maintenance-Object Repair Procedures Table 329: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This will cause noisy and unreliable connections. 1. Replace the circuit pack. PASS The port can correctly conference multiple connections.
PAGE 961
DIOD-DS1 (DS1 DIOD Trunk) Table 330: Test #36 Port Audit and Update Test (continued) Error Code Test 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. To verify that the trunk is in-service: 1. Enter status trunk to verify that the trunk is in-service.
PAGE 962
Communication Manager Maintenance-Object Repair Procedures Table 331: Test #314 DS1 CO Dial Tone Seizure Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port has been seized by a user for a valid call. Use status trunk to determine when the port is available for testing. 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT Test failed due to incompatible configuration administered in trunk group screen. 1.
PAGE 963
DIOD-DS1 (DS1 DIOD Trunk) Table 331: Test #314 DS1 CO Dial Tone Seizure Test (continued) Error Code Test Result Description / Recommendation 2053 ABRT At least one of the following errors is found on the DS1 circuit pack: ● 1281 – Loss of signal ● 1793 – Blue alarm ● 2049 – Red alarm ● 2305 – Yellow alarm ● 1537 – Hyperactivity Look for the previous error types in the Hardware Error Log, and follow the procedures given in the DS1-BD (DS1 Interface Circuit Pack) on page 978 or UDS1-BD (UDS1 I
PAGE 964
Communication Manager Maintenance-Object Repair Procedures DIOD-TRK (DIOD Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIOD-TRK MAJ1 test port location DIOD Trunk DIOD-TRK MIN test port location DIOD Trunk DIOD-TRK WRN test port location DIOD Trunk 1. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least 75 percent of the trunks in this trunk group are alarmed.
PAGE 965
DIOD-TRK (DIOD Trunk) Outgoing Call 1. PBX Off-Hook (Seize Message): Closes the Tip-Ring Loop CO Response: DC loop current + Dial tone 2. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop current CO Response: CO goes to idle state (see Note) Incoming Call 1. CO Applies Ringing Voltage PBX Response: Detect ringing current 2. PBX Off-Hook (Answer Message): Close loop CO Response: Trip ringing, provide loop current 3.
PAGE 966
Communication Manager Maintenance-Object Repair Procedures Table 332: DIOD Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 769 (c) 57392 None MAJ MIN WRN1 ON 1537 Dial Tone test (#0) MAJ MIN WRN1 ON test port long r 2 1793 Looparound and Conference (#33) MAJ MIN WRN1 ON test port long r 3 2049 NPE Cross Talk test (#6) MAJ MIN WRN1 ON test port long r 3 2561 (d) 57345 None 2817 (e) 57393 None 3073 (f) 57376 None 3585 (g) 574
PAGE 967
DIOD-TRK (DIOD Trunk) e. Error Type 2817 Aux Data 57393 is an in-line error that has no specific test associated with it. CO released the trunk at least four minutes after the PBX dropped the call. This error code is log only and causes no other testing to occur. No alarm is generated. Check for other errors. f. Error Type 3073 Aux Data 57376 is an in-line error that has no specific test associated with it. No loop current on incoming call.
PAGE 968
Communication Manager Maintenance-Object Repair Procedures Dial Tone Test (#0) Note: S8300 / G700: This test aborts with Error Code 1412. Note: This test attempts to seize a port and checks for the return of a dial tone. Table 333: Test #0 Dial Tone Test Error Code Test Result Description / Recommendation ABRT Could not allocate system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available.
PAGE 969
DIOD-TRK (DIOD Trunk) Table 333: Test #0 Dial Tone Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT Trunk has been administered as incoming-only; or DID trunk group type; dial tone can only be obtained on outgoing trunks. This is a normal condition. S8300 ABRT This test does not execute on a G700 Media Gateway. ABRT Response to the test was not received within the allowable time period. / G700 1412 2000 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 970
Communication Manager Maintenance-Object Repair Procedures NPE Crosstalk Test (#6) Note: S8300 / G700: This test aborts with Error Code 1412. Note: 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 executes in about 20 to 30 seconds.
PAGE 971
DIOD-TRK (DIOD Trunk) Table 334: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid call during the test. The test has been aborted. 1. Enter display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is in use, wait until it is idle before retesting. S8300 G700 ABRT This test does not execute on a G700 Media Gateway.
PAGE 972
Communication Manager Maintenance-Object Repair Procedures Looparound and Conference Circuit Test (#33) Note: S8300 / G700: This test aborts with Error Code 1412. Note: This test checks the reflective loop and conference abilities of a CO port circuit. The test uses 404-, 1004-, and 2804-Hz tones. Each tone is transmitted separately through the loop and checked.
PAGE 973
DIOD-TRK (DIOD Trunk) Table 335: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 7 FAIL Fail 1. Check for errors on TONE-BD or TONE-PT. 2. If the Reflective Looparound test fails for every port on a circuit pack, a -5V power problem is indicated. S8700 | 8710 / S8500: If a TN736 or TN752 power unit circuit pack is present, check the circuit pack for a red LED. If the red LED is on, then replace the power unit circuit pack.
PAGE 974
Communication Manager Maintenance-Object Repair Procedures Port Audit Update Test (#36) This test sends updates of the CO port translation for every translated port on the circuit pack or media module. The update is non-disruptive and guards against possible corruption of translation data contained on the circuit pack or media module. No response message is expected from the circuit pack or media module once it receives translation updates.
PAGE 975
DLY-MTCE (MO-DAILY) DLY-MTCE (MO-DAILY) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO DLY-MTCE MINOR NONE DLY-MTCE DLY-MTCE MAJOR NONE DLY-MTCE The DLY-MTCE MO monitors daily translation saves. If a translation save times out or fails to run, an error is logged against this MO.
PAGE 976
Communication Manager Maintenance-Object Repair Procedures Other command actions can also interfere with daily maintenance when certain qualifiers are used in the commands, or under certain circumstances. For example, certain test commands, when used with the modifier continuously, could interfere with daily maintenance.
PAGE 977
DLY-MTCE (MO-DAILY) Figure 47: Maintenance-Related System Parameters (change system-parameters maintenance) change system-parameters maintenance MAINTENANCE-RELATED SYSTEM PARAMETERS Page 1 of 3 SCHEDULED MAINTENANCE Start Time: 01 : 00 Stop Time: 06 : 00 Save Translation: daily Figure 48: Command Time-out Entry on list history list history HISTORY Date of Loaded Translation: no translation loaded Date Time Qualifier Port Login Actn 9/18 MGR1 init logn 16:13 Object Issue 1 June 2005 977
PAGE 978
Communication Manager Maintenance-Object Repair Procedures DS1-BD (DS1 Interface Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DS1-BD MAJ test board location sh DS1 Interface circuit pack DS1-BD MIN test board location l DS1 Interface circuit pack DS1-BD WRN test board location sh DS1 Interface circuit pack The DS1 Interface circuit pack provides an interface to an external DS1 facility and supports 24 DS0 channels carried on
PAGE 979
DS1-BD (DS1 Interface Circuit Pack) Combined with a TN767E circuit pack, Avaya’s 120A1 Integrated CSU module becomes an enhanced CSU. The 120A1 CSU, combined with new switch software and the functionality provided by a TN767E’s hardware and firmware, provides functionality equivalent to an external stand-alone Avaya ESF T1 CSU. The 120A1 CSU connects to the TN767E circuit pack on the I/ O connector panel on the back of the port carrier, and thus becomes an integrated part of the system.
PAGE 980
Communication Manager Maintenance-Object Repair Procedures Figure 49: High-Level Overview Of Loop-Back Points NETWORK ENVIRONMENT NET SMRT JACK CPE LPBK JACK CSU MOD DS1 BRD NETWORK NET SMRT JACK CPE LPBK JACK CSU MOD DS1 BRD Remote end Local end CSU module to CSU module PLB BLB CPE LPBK JACK CSU MOD DS1 BOARD ELB LLB RLB NETWORK SMRT JACK CLJ-LB Local end loop backs NETWORK SMRT JACK CPE LPBK JACK CSU* MOD DS1 BOARD R-LLB Remote end loop backs (* CSU or External CSU) Error Lo
PAGE 981
DS1-BD (DS1 Interface Circuit Pack) Table 338: DS1 Interface Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 257 65535 Control Channel Loop test (#52) MIN ON test board location l r 20 257 (f) Any None 513 (g) Any MIN ON 769 (h) 4358 1025 (i) 4363 NPE Audit test (#50) 1281 Any Loss of Signal Alarm Inquiry (#138) MIN WRN † OFF test board location 1300 (i) Any Loss of Signal Alarm Inquiry (
PAGE 982
Communication Manager Maintenance-Object Repair Procedures Table 338: DS1 Interface Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1314 (q) Any Far CSU Loopback test (#1213) MIN WRN † OFF test ds1-loop location end-loopback/span-test 1320 Any Loss of Signal Alarm Inquiry (#138) MIN WRN † OFF test board location 1321 Any Loss of Signal Alarm Inquiry (#138) MIN WRN † OFF test board location 1322
PAGE 983
DS1-BD (DS1 Interface Circuit Pack) Table 338: DS1 Interface Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 2306 Any Yellow Alarm Inquiry test (#141) MIN OFF test board location 2561 Any Major Alarm Inquiry test (#142) MIN WRN † OFF test board location Minor Alarm Inquiry test (#143) MIN WRN † OFF test board location 2817 3073 to 3160 (s) Any Slip Alarm Inquiry test (#144) MIN WRN † OFF test
PAGE 984
Communication Manager Maintenance-Object Repair Procedures If the circuit pack has an entry in the circuit plan and either of the other two conditions are not met, a MINOR alarm is logged. To resolve the error, either: ● Make sure all conditions for administration are met and that a functioning DS1 circuit pack is inserted in the correct slot, or ● Completely remove the DS1-BD from the system: 1.
PAGE 985
DS1-BD (DS1 Interface Circuit Pack) Otherwise, change the Near-End CSU Type field using the change ds1 screen to other. If this error remains after plugging the 120A1 CSU or T1 sync splitter into the board’s connector, there could be a problem with the I/O connector panel. j. Error Type 1301: CSU module/T1 sync splitter not expected.
PAGE 986
Communication Manager Maintenance-Object Repair Procedures Attempt to clear the alarm with busyout board location, test ds1-loop location ds1/csu-loopback-tests, and release board location. If the RLB test continues to fail, then the CSU module/T1 sync splitter needs to be replaced. p. Error Type 1313: CPE loop-back jack deactivation error. This error occurs when the TN767E circuit pack could not deactivate a CPE loop-back jack loop-back.
PAGE 987
DS1-BD (DS1 Interface Circuit Pack) w. Error Type 3901: gives status information about a Far CSU Loopback test. The value in the Aux Data field indicates the status of the loop-back test. Aux Data 1: Test is currently running. Aux Data 2: Test failed because loop back could not be activated. Aux Data 3: Test failed because test pattern could not be detected. Aux Data 4: Test has been deactivated. x. Error 3902: gives status information about a One-Way Span test.
PAGE 988
Communication Manager Maintenance-Object Repair Procedures Table 339: System Technician-Demanded Tests: DS1-BD (continued) Order of Investigation Reset Board Sequence test ds1-loop Command D/ND1 Short Test Sequence Long Test Sequence Yellow Alarm Inquiry test (#141) X X ND Major Alarm Inquiry test (#142) X X ND Minor Alarm Inquiry test (#143) X X ND Slip Alarm Inquiry test (#144) X X ND Misframe Alarm Inquiry test (#145) X X ND Translation Update test (#146) X X ND ICSU Status
PAGE 989
DS1-BD (DS1 Interface Circuit Pack) NPE Connection Audit Test (#50): The system sends a message to the on-board microprocessor to update the network connectivity translation for all the Network Processing Elements (NPEs) on the circuit pack. Table 340: Test #50 NPE Connection Audit Test Error Code Test Result Description / Recommendation None, 2100 ABRT System resources required for this test are not available. 1019 ABRT Test already in progress. FAIL Internal system error 1.
PAGE 990
Communication Manager Maintenance-Object Repair Procedures Control Channel Loop-around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 341: Test #52 Control Channel Loop-around Test Error Code Test Result Description / Recommendation None 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 991
DS1-BD (DS1 Interface Circuit Pack) Table 341: Test #52 Control Channel Loop-around Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 992
Communication Manager Maintenance-Object Repair Procedures SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack. Table 342: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT Wrong circuit pack configuration to run this test. This error applies only to DS1 Interface circuit packs.
PAGE 993
DS1-BD (DS1 Interface Circuit Pack) Table 342: Test #53 SAKI Sanity Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 994
Communication Manager Maintenance-Object Repair Procedures Table 343: Test #135 Internal Loop-Around Test Error Code Test Result Description / Recommendation 2012 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 995
DS1-BD (DS1 Interface Circuit Pack) Table 343: Test #135 Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT The test was aborted. 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 996
Communication Manager Maintenance-Object Repair Procedures Table 343: Test #135 Internal Loop-Around Test (continued) Error Code 0 Test Result Description / Recommendation PASS Every administered trunk of DS1 Interface circuit pack passed the Internal Looparound test. The bit pattern consistency test executed successfully over the path that covers a DS1 port, cable, and the external NCTE device. NO BOARD The test could not relate the internal ID to the port (no board).
PAGE 997
DS1-BD (DS1 Interface Circuit Pack) S8700 MC This test is also used to maintain the 120A CSU module and the 401A T1 sync splitter. The CSU module, when combined with the functionality provided by the TN767E circuit pack, provides functionality equivalent to an external standalone ESF T1 CSU The 401A T1 sync splitter, when combined with the functionality provided by the TN767E circuit pack, allows an ATM switch to derive its timing off a T1 facility connected to the S8700 Multi-Connect’s DS1circuit pack.
PAGE 998
Communication Manager Maintenance-Object Repair Procedures Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 999
DS1-BD (DS1 Interface Circuit Pack) Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1300 FAIL The CSU module or the T1 sync splitter is missing. The Near-End CSU Type field on the add ds1 screen has been administered as integrated, but the 120A1 CSU module/T1 sync splitter is not physically connected to the TN767E board on the back of the port carrier. 1.
PAGE 1000
Communication Manager Maintenance-Object Repair Procedures Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1310 FAIL The DS1 Board Loopback (BLB) demand test (#1209) failed. 1. Repeat the test using test ds1-loop location ds1/ csu-loopback-tests. 2. If the BLB test continues to fail, then replace the TN767E circuit pack. 3. Run this test again.
PAGE 1001
DS1-BD (DS1 Interface Circuit Pack) Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1312 FAIL The Integrated CSU (I-CSU) Module Repeater Loopback (RLB) test (#1211) failed. This test is executed during ICSU/T1 sync splitter power-up/reset (the TN767E board is physically inserted and the CSU module/T1 sync splitter is already installed), or when the 120A1 CSU module/T1 sync splitter is plugged on to an already initialized DS1 board.
PAGE 1002
Communication Manager Maintenance-Object Repair Procedures Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1321 FAIL DTE LOS (loss of signal) was detected between the TN767E DS1 board and the 120A1 CSU module or the T1 sync splitter. Either the TN767E board, the 120A1 CSU module/T1 sync splitter, or the I/O cable between the backplane and the 120A1 CSU module or the 401A T1 sync splitter (or any combination thereof) has failed.
PAGE 1003
DS1-BD (DS1 Interface Circuit Pack) Table 344: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code 0 Test Result Description / Recommendation PASS DS1 signal is present and the physical link is healthy. In addition, no Integrated CSU errors are detected. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1.
PAGE 1004
Communication Manager Maintenance-Object Repair Procedures For blue alarms, a DS1 Interface circuit pack takes much longer to recognize and report its resolution (~ 16 seconds) than its occurrence (~ 2 seconds). So, when a blue alarm is cleared, the local DS1 Interface circuit pack avoids false blue alarms by quickly: ● Restoring the DS1 trunks to service ● Discontinuing yellow alarms to the remote endpoint before the remote endpoint can recognize and report another blue alarm.
PAGE 1005
DS1-BD (DS1 Interface Circuit Pack) Table 345: Test #139 Blue Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 1006
Communication Manager Maintenance-Object Repair Procedures Table 345: Test #139 Blue Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1795 FAIL The DS1 Interface circuit pack detects a Payload Loopback Alarm (PLB). If the DS1 Interface circuit pack connects to a leased T1 facility, call the vendor of the T1 carrier to diagnose the remote DS1 endpoint.
PAGE 1007
DS1-BD (DS1 Interface Circuit Pack) When the Red alarm is cleared, the DS1 Interface circuit pack will stop transmitting the Yellow alarm to the remote DS1 endpoint. The maintenance software restores all trunks of the DS1 Interface circuit pack to the service state before the Red alarm occurs.
PAGE 1008
Communication Manager Maintenance-Object Repair Procedures Table 346: Test #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation FAIL The DS1 Interface circuit pack detects a Red alarm. An out-of-frame condition occurs on the DS1 Interface circuit pack. DS1 Interface circuit pack will transmit a Yellow alarm to the remote DS1 endpoint until the Red alarm is retired. 1.
PAGE 1009
DS1-BD (DS1 Interface Circuit Pack) Table 346: Test #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 1010
Communication Manager Maintenance-Object Repair Procedures This Yellow Alarm corresponds to the yellow F2 state documented in CCITT recommendation I.431. Remote Multiframe Alarm: Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a Loss of Multiframe Alarm condition while the DS1 Interface circuit pack is administered using the DMI-BOS common-channel signaling. The RMA is handled as a Yellow alarm.
PAGE 1011
DS1-BD (DS1 Interface Circuit Pack) Table 347: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation FAIL The DS1 interface circuit pack detected a yellow alarm sent by the remote DS1 endpoint. An out of frame condition occurred at the DS1 endpoint. 1 FAIL The DS1 Interface circuit pack detects a Remote Multiframe Alarm sent by the remote DS1 endpoint. An out-of-frame condition occurs on the remote DS1 endpoint.
PAGE 1012
Communication Manager Maintenance-Object Repair Procedures Table 347: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1013
DS1-BD (DS1 Interface Circuit Pack) When the Major alarm is cleared, the maintenance software restores all trunks on the circuit pack to their previous service state before a Major alarm occurs. Table 348: Test #142 Major Alarm Inquiry Test Error Code 2100 Test Result Description / Recommendation ABRT Internal system error ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1014
Communication Manager Maintenance-Object Repair Procedures Table 348: Test #142 Major Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation FAIL The DS1 Interface circuit pack detects a Major alarm. The DS1 bit error rate is greater than 1/1000. 1. The performance of DS1 link between DS1 Interface circuit pack and remote DS1 endpoint is very poor. If the DS1 Interface circuit pack is TN767, enter list measurement ds1-log location to read the error seconds measurement. 2.
PAGE 1015
DS1-BD (DS1 Interface Circuit Pack) Minor Alarm Inquiry Test (#143) The Minor alarm raised by a DS1 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 1016
Communication Manager Maintenance-Object Repair Procedures Table 349: Test #143 Minor Alarm Inquiry Tests (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 1017
DS1-BD (DS1 Interface Circuit Pack) Table 349: Test #143 Minor Alarm Inquiry Tests (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 1018
Communication Manager Maintenance-Object Repair Procedures Table 350: Test #144 Slip Alarm Inquiry Test Error Code 2100 Test Result Description / Recommendation ABRT Internal system error ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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 1019
DS1-BD (DS1 Interface Circuit Pack) Table 350: Test #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 to 88 FAIL The DS1 interface circuit pack detected a slip alarm. The error code equals the number of slips detected by the DS1 interface circuit pack since the last slip alarm inquiry test. 1. Retry the command at 1-minute intervals up to 5 times. 2.
PAGE 1020
Communication Manager Maintenance-Object Repair Procedures Table 350: Test #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1021
DS1-BD (DS1 Interface Circuit Pack) Table 351: Test #145 Misframe Alarm Inquiry Test Error Code 2100 Test Result Description / Recommendation ABRT Internal system error ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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 1022
Communication Manager Maintenance-Object Repair Procedures Table 351: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation ANY FAIL The test failed because the DS1 interface circuit pack detected errors in the received framing bits pattern. The error code equals the number of misframes detected by the DS1 interface circuit pack since the last misframe alarm inquiry test.
PAGE 1023
DS1-BD (DS1 Interface Circuit Pack) Table 351: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 1024
Communication Manager Maintenance-Object Repair Procedures Table 352: Test #146 Translation Update Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. FAIL Internal system software error. 1. Enter display ds1 location to verify the DS1 Interface circuit pack translation. 0 PASS Translation data has been downloaded to the DS1 Interface circuit pack successfully.
PAGE 1025
DS1-BD (DS1 Interface Circuit Pack) When the BLB test is initiated, maintenance software sends a message to the TN767E DS1 Interface circuit pack to start the test. The board sets up the BLB loop back, transmits a test pattern, and verifies that the pattern is received unaltered through the loop back. If the transmitted and received pattern is different, the test fails.
PAGE 1026
Communication Manager Maintenance-Object Repair Procedures Table 353: Test #1209 DS1 Board Loop-Back Test (continued) Error Code 2100 Test Result Description / Recommendation ABRT Internal system error ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
PAGE 1027
DS1-BD (DS1 Interface Circuit Pack) Table 353: Test #1209 DS1 Board Loop-Back Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 1028
Communication Manager Maintenance-Object Repair Procedures The DS1 circuit pack hardware applies a DC current while the test is running in order to detect any broken wires that may not be detected by the loop-back pattern. When the test is complete, use release board to restore all trunks or ports on the TN767E DS1 Interface circuit pack to the in-service state. Table 354: Test #1210 CSU Equipment Loop-Back Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 1029
DS1-BD (DS1 Interface Circuit Pack) Table 354: Test #1210 CSU Equipment Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1950 ABRT Another loop-back/span test is already executing on the DS1 board or the board is in a network requested loop-back mode (Line loop back or Payload loop back).
PAGE 1030
Communication Manager Maintenance-Object Repair Procedures Table 354: Test #1210 CSU Equipment Loop-Back Test (continued) Error Code Test Result Description / Recommendation FAIL DS1 Interface circuit pack failed the CSU Equipment Loopback test. 1. Retry test ds1-loop location ds1/csu-loopback-tests. 2.
PAGE 1031
DS1-BD (DS1 Interface Circuit Pack) CSU Repeater Loop-Back Test (#1211) This test is destructive. The CSU RLB (Repeater Loopback) test causes a loop back at the far-edge of the local 120A CSU module or T1 sync splitter, and tests the connection from the TN767E DS1 board to and including the CSU module/T1 sync splitter circuitry. The test runs only if the 120A CSU module/ T1 sync splitter is present, administered, and connected to a 1.544-Mbps TN767E DS1 circuit pack on the back of the port carrier.
PAGE 1032
Communication Manager Maintenance-Object Repair Procedures Table 355: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1015 ABRT Ports on the DS1 Interface circuit pack have not been busied out to out-of-service. 1. Enter busyout board location to put all trunks or ports of the DS1 Interface circuit pack into the out-of-service state. 2. Retry the command. 1039 ABRT The DS1 Interface circuit pack is providing timing for the system.
PAGE 1033
DS1-BD (DS1 Interface Circuit Pack) Table 355: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code 2100 Test Result Description / Recommendation ABRT Internal system error ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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 1034
Communication Manager Maintenance-Object Repair Procedures Table 355: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1035
DS1-BD (DS1 Interface Circuit Pack) The status of the CPE Loopback Jack test appears in the hardware error log via Error Type #3900. Several distinct aux values give information on the status of the test. Use list measurements ds1 summary to show the length of time the test has been running (Test Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field). If the test pattern is passed through the loop back cleanly, the number of bit errors should be very low.
PAGE 1036
Communication Manager Maintenance-Object Repair Procedures Table 356: Test #1212 CPE Loopback Jack Test (continued) Error Code Test Result Description / Recommendation 1950 ABRT Another loop-back/span test is already executing on the DS1 board or the board is in a network requested loop-back mode (Line loop back or Payload loop back).
PAGE 1037
DS1-BD (DS1 Interface Circuit Pack) Table 356: Test #1212 CPE Loopback Jack Test (continued) Error Code Test Result Description / Recommendation 2 FAIL The CLJ-LB test failed because it was not set up properly. The DS1 interface pack could not successfully put the CPE loop-back jack into loop-back mode. 1. Rerun test ds1-loop location cpe-loopback-jack-test-begin. 2. If the test continues to fail, the problem could be with the TN767E board, the CPE loop-back jack equipment, or somewhere between.
PAGE 1038
Communication Manager Maintenance-Object Repair Procedures Table 356: Test #1212 CPE Loopback Jack Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1039
DS1-BD (DS1 Interface Circuit Pack) The status of the Far CSU Loopback test appears in the hardware error log via Error Type #3901. Several aux values give information on the status of the test. Use list measurements ds1 summary to show the length of time the test has been running (Test Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field). If the test pattern is passed through the loop back cleanly, the number of bit errors should be very low.
PAGE 1040
Communication Manager Maintenance-Object Repair Procedures Table 357: Test #1213 Far CSU Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1950 ABRT Another loop-back/span test is already executing on the DS1 board or the board is in a network requested loop-back mode (Line loop back or Payload loop back).
PAGE 1041
DS1-BD (DS1 Interface Circuit Pack) Table 357: Test #1213 Far CSU Loop-Back Test (continued) Error Code Test Result Description / Recommendation 3 FAIL The far CSU Loopback test was not set up properly. The framed 3-in-24 test pattern, generated by the DS1 Interface circuit pack and looped back through the far-end CSU, could not be detected by the DS1 circuit pack. 1. Retry test ds1-loop location far-csu-loopback-test-begin. 2.
PAGE 1042
Communication Manager Maintenance-Object Repair Procedures One-Way Span Test (#1214) This test is destructive. The One-Way Span test allows 1-way span testing to and from remote test equipment or another Communication Manager solution. This tests all circuitry and facilities from the local TN767E DS1 board to the remote test equipment or other Communication Manager solution. The test is destructive and can only be initiated by a technician-demanded test ds1-loop location one-way-span-test-begin.
PAGE 1043
DS1-BD (DS1 Interface Circuit Pack) Table 358: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT One-Way Span test cannot be executed in the current configuration. To run this, the TN767E (or higher-suffixed) DS1 must be administered for 24-channel operation. The Bit Rate field on the DS1 circuit pack administration screen must be set to “1.544” for 24-channel operation.
PAGE 1044
Communication Manager Maintenance-Object Repair Procedures Table 358: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 1045
DS1-BD (DS1 Interface Circuit Pack) Table 358: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Use add ds1 location to administer the DS1 interface if it is not already administered. 2.
PAGE 1046
Communication Manager Maintenance-Object Repair Procedures Use release board to restore the trunks or ports on the TN767E DS1 Interface circuit pact to the inservice state. Table 359: Test #1215 Inject Single Bit Error Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry test ds1-loop location inject-single-bit-error at 1-minute intervals up to 5 times. 1015 ABRT Ports on the DS1 Interface circuit pack have not been busied out to out-of-service. 1.
PAGE 1047
DS1-BD (DS1 Interface Circuit Pack) Table 359: Test #1215 Inject Single Bit Error Test (continued) Error Code 0 Test Result Description / Recommendation PASS A single bit error has been successfully injected into an active framed 3-in-24 test pattern. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1.
PAGE 1048
Communication Manager Maintenance-Object Repair Procedures Use list measurements ds1 summary to show the length of time the test ran (Test Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field). Use release board to restore the trunks or ports on the TN767E DS1 Interface circuit pack to the in-service state. Table 360: Test #1216 End Loopback/Span Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 1049
DS1-BD (DS1 Interface Circuit Pack) Table 360: Test #1216 End Loopback/Span Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service and one or more of the following symptoms may be exhibited.
PAGE 1050
Communication Manager Maintenance-Object Repair Procedures Table 360: Test #1216 End Loopback/Span Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1051
DS1-BD (DS1 Interface Circuit Pack) Table 361: Test #1227 ICSU Status LEDs Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT The ICSU Status LEDs test cannot be executed for the current configuration. The test applies only to TN767E or later DS1 circuit packs administered for 24-channel (1.544-Mbps) operation. 2.
PAGE 1052
Communication Manager Maintenance-Object Repair Procedures Table 361: Test #1227 ICSU Status LEDs Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 1053
DS1-FAC (DS1 Facility) DS1-FAC (DS1 Facility) S8700 MC MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DS1-FAC MAJ test board location sh r 1 DS1 Facility DS1-FAC MIN test board location sh r 1 DS1 Facility DS1-FAC WRN test board location sh r 1 DS1 Facility The DS1-FAC is a part of the DS1 Converter (DS1C-BD) complex. The DS1C-BD complex consists of two TN574 DS1C-BD circuit packs or two TN1654 DS1C-BD circuit packs connected by one to four DS1 facilities.
PAGE 1054
Communication Manager Maintenance-Object Repair Procedures Figure 50: DS1 Converter Complex and the DS1 Facilities DS1 Facilities Metallic or Fiber Connection EI DS1CONV Metallic or Fiber Connection Network DS1CONV EI or SNI The DS1 converter complex can replace fiber links between two EIs and fiber links between an PN’s EI and an SNI. Fiber links between two SNIs and fiber links between the and the Center Stage Switch (CSS) cannot be replaced by a DS1 converter complex.
PAGE 1055
DS1-FAC (DS1 Facility) The TN574 DS1 converter has seven LEDs that provide an indication of the state of the DS1 converter circuit pack and the DS1 facilities. There is a yellow, a green, and a red LED under software and/or firmware control. There are four Green LEDs under hardware control that indicate, for each DS1 facility, whether a receive signal is present for the DS1 facility. From top to bottom these green LEDs correspond to DS1 facilities A, B, C, and D respectively.
PAGE 1056
Communication Manager Maintenance-Object Repair Procedures DS1 facility administration is explained in the following sections. These descriptions do not provide complete coverage of fiber link administration. Replacing a DS1 Facility Disconnecting a DS1 facility is service disrupting except on critical-reliability systems since they have PNC duplication. For a standard-, duplex-, or high-reliability system (no PNC duplication): This procedure is destructive. 1.
PAGE 1057
DS1-FAC (DS1 Facility) Removing a DS1 Facility Removing a DS1 facility is service disrupting in any system configuration, because the DS1 facility administration is similar on both sides of the PNC on critical-reliability systems. This procedure is destructive. 1. Use busyout ds1-facility to busyout the DS1 facility. 2. Use list fiber-link to check the fiber link number. 3. Use change fiber-link to administer the DS1 facility. Set the Facility Installed field to n for the facility that is being removed. 4.
PAGE 1058
Communication Manager Maintenance-Object Repair Procedures Table 362: DS1 Interface Options administration (continued) Field Description Bit Rate Select domestic T1 operation or international E1 operation for all facilities in the TN1654 DS1 converter complex: 1.544 Mbps for T1 operation 2.048 Mbps for E1 operation Appears on the fiber-link screen only for TN1654 DS1 converter circuit packs. ● ● The TN1654 DS1 converter circuit pack is also field configurable for T1 or E1 operation.
PAGE 1059
DS1-FAC (DS1 Facility) Table 362: DS1 Interface Options administration (continued) Field Description Line Coding Administer the line coding for the DS1 facility. For the TN574 board and the TN1654 board in T1 mode, the field may be set to ami-zcs or b8zs. If the TN1654 board is set for E1 operation, the line coding may be set to either ami-basic or hdb3. The line coding must be the same at each end of the DS1 converter complex. Framing Mode esf or d4 for the DS1 facility.
PAGE 1060
Communication Manager Maintenance-Object Repair Procedures Table 363: DS1 Facility Line Signal Equalization Values DS1 Converter-1 and DS1 Converter-2 Line Compensation (cont’d) Equalizer Setting Distance to Network Interface (feet) Cable type 22 AWG ABAM & 24 AWG PDS Cable type 26 AWG PDS 1 1 to 133 0 to 90 2 133 to 266 90 to 180 3 266 to 399 180 to 270 4 399 to 533 270 to 360 5 533 to 655 360 to 450 DS1 Converter Performance Measurements Report The DS1 Converter Performance Measurement
PAGE 1061
DS1-FAC (DS1 Facility) Clearing Firmware Errors DS1 converter error reports are generated by firmware autonomously. DS1 converter error reports are not associated with technician-demanded tests. The test board clear command does not affect the error status known by the DS1 converter firmware. To clear every on-board firmware-detected error unconditionally, use clear firmware-counters.
PAGE 1062
Communication Manager Maintenance-Object Repair Procedures Notes: When problems persist, use reset board to reset the DS1 converter circuit pack. This may temporarily resolve the error condition and restore service until further assistance is provided. a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description, and follow its recommended procedures. b.
PAGE 1063
DS1-FAC (DS1 Facility) f. Error Type 856: More than 88 negative and/or positive slip errors occurred. This error clears when there are no slips for 1 hour. 1. Enter display errors and follow the associated repair procedures for any SYNC, TDM-CLK, and SNC-BD errors. 2. Verify that the DS1 facility and the network are using the same Line Coding. For TN574 boards and TN1654 boards in T1 mode, also verify that the Framing Mode used is the same.
PAGE 1064
Communication Manager Maintenance-Object Repair Procedures 4. If Test #799 passes, run the Far-End Internal Loopback test (#797) via test ds1-facility location long. If Test #797 passes, go to step 6. If the test fails, then run the Near-End External Loopback test (#799) via test ds1-facility location external-loopback at the other end of the DS1 converter complex, and repeat steps 2 and 3 for the other endpoint.
PAGE 1065
DS1-FAC (DS1 Facility) Aux Data 2: indicates that the facility is detecting a yellow F5 state alarm. This error only applies to TN1654 DS1 converter boards in 32-channel E1 operation with CRC enabled via the fiber-link screen. The F5 fault state is defined as a fault in the user-network interface, specifically in the direction from the user (PBX) to the network. Refer to CCITT recommendation I.431. The far-end facility will be in LFA state.
PAGE 1066
Communication Manager Maintenance-Object Repair Procedures facility is attached. If the NI does not occur at this point, then any cabling between the CSU terminals and the NI is also considered to be part of the CPE. This cable typically runs between the DS1 facility terminals of the CSU and a cross-connect field where the DS1 facility vendor has terminated the DS1 facility. Maintenance responsibility for this portion of the DS1 facility resides with the customer unless other arrangements are made. 3.
PAGE 1067
DS1-FAC (DS1 Facility) 4. Enter display errors and follow the associated repair procedures for any EXP-INTF, and SNI-BD errors for the Fiber Endpoints. Enter display errors and follow the associated repair procedures for any FIBER-LK errors for this fiber link. 5. If the problem still persists, replace this DS1 converter circuit pack. 6. If the problem still persists, replace the DS1 converter circuit pack at the other end of the DS1 converter complex. l.
PAGE 1068
Communication Manager Maintenance-Object Repair Procedures Figure 51: DS1 Facility Connections Network Interface at CSU T R T R CSU A T1 DS1CONV A T1 R1 R1 CSU B Network/DS1 Facility CPE DS1CONV B CPE Network Interface at Cross Connect Field T R Cross Connect Field CSU DS1CONV T1 R1 Network/DS1 Facility CPE Figure 52: Typical CSU Maintenance Capabilities CSU Signal Out Signal In CPE Side Signal Out DS1 Facility Side DS1 Facility Side LOS LED CPE Side LOS LED Signal In CPE Loopback
PAGE 1069
DS1-FAC (DS1 Facility) System Technician-Demanded Tests: Descriptions And Error Codes Investigate tests in the order presented. By clearing error codes associated with the Failure Audit, you may clear errors generated from other tests in the sequence. Use test board to run Failure Audit. .
PAGE 1070
Communication Manager Maintenance-Object Repair Procedures Figure 53: Far-End Internal Loop-Back Test (#797) Loop at internal interface for the DS1 facility CSU A DS1CONV A CSU B . . .. .. .. DS1CONV .. B . . . .. DS1 Facility Test starts here Table 365: Test #797 Far-End Internal Loop-Back Test Error Code Test Result Description / Recommendation 2000 ABRT Timed out while waiting for a response from the circuit pack. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1071
DS1-FAC (DS1 Facility) Table 365: Test #797 Far-End Internal Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2500 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 3 times. FAIL Far-End Internal loop back failed. A problem exists between DS1 converter A and DS1 converter B’s internal interface for the DS1 facility (see previous diagram). 1. If the test is executed as a part of an error analysis, then return back to the related section. 2.
PAGE 1072
Communication Manager Maintenance-Object Repair Procedures DS1 Interface Options Audit Test (#798) This test is nondestructive. This test sends the administered DS1 Interface options to the DS1 converter circuit pack. Options are sent to both DS1 converter circuit packs at the same time to prevent any transitional mismatch of options. The following DS1 facility options are sent to the TN574 DS1 converter circuit pack: Framing Mode, Line Coding and DS1 converter-1 and DS1 converter-2 Line Compensation.
PAGE 1073
DS1-FAC (DS1 Facility) Near-End External Loop-Back Test (#799) This test is destructive. This test starts at the DS1 converter circuit pack whose equipment location was entered and traverses over the specified facility and loops back at the manually hard-wired external loop-back device. Depending on the type of physical connectivity of the DS1 facility, special tools, cables or connectors may be required to make the hard-wired loop backs.
PAGE 1074
Communication Manager Maintenance-Object Repair Procedures Figure 54: Loopback Points for Test #799 LB 1 LB 2 DS1CONV A CSU B DS1CONV B CSU A DS1 Facility Test starts here Table 367: Test #799 Near-End External Loop-Back Test Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2000 ABRT Timed out while waiting for a response from the circuit pack. 1.
PAGE 1075
DS1-FAC (DS1 Facility) Table 367: Test #799 Near-End External Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2500 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 3 times. FAIL Near-end external loop back failed. A problem exists in the path of the loop back. 1. If the test is executed as a part of an error analysis, then return back to the related section. 2.
PAGE 1076
Communication Manager Maintenance-Object Repair Procedures Failure Audit (#949) This test is nondestructive. This test queries the DS1 converter circuit pack for any existing circuit pack or facility failures and any unacknowledged cleared failure messages. Upon receiving the query request, DS1 converter firmware sends failure reports to the maintenance software for every error in its failure database. This test operates on both MOs DS1C-BD and DS1-FAC.
PAGE 1077
DS1C-BD DS1C-BD S8700 MC only Also called DS1 Converter MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DS1C-BD MAJ test board location sh r 1 DS1 converter circuit pack DS1C-BD MIN test board location sh r 1 DS1 converter circuit pack DS1C-BD WRN test board location sh r 1 DS1 converter circuit pack The DS1 converter complex is part of the port-network connectivity (PNC) consisting of two TN574 DS1 Converter or two TN1654 DS1 Converter circuit packs connected b
PAGE 1078
Communication Manager Maintenance-Object Repair Procedures The DS1 converter circuit pack can be placed in any regular slot in a PN carrier. However, the DS1 converter circuit pack can only be placed in slots 1 and 21 in a Switch Node (SN) carrier. The DS1 converter circuit pack is not connected to the TDM bus or the SN backplane. Communication to the circuit pack is done through the connected EI or the SNI circuit packs.
PAGE 1079
DS1C-BD Figure 56: DS1 converter Complex in Direct Connect PNC Metallic or Fiber Connection E I PPN D S 1 C O N V DS1 Facilities Remote EPN E I D S 1 C O N V Metallic or Fiber Connection Issue 1 June 2005 1079
PAGE 1080
Communication Manager Maintenance-Object Repair Procedures Figure 57: DS1 Converter Complex in Duplicated PNC with 1 SN PPN E I E I Fiber Link Metallic or Fiber Connection Metallic or Fiber Connection Fiber Link D S 1 C O N V S N I S N I ... D S 1 C O N V S N I S N I SN A-PNC ...
PAGE 1081
DS1C-BD To administer a standard-, duplex-, or high-reliability system (no PNC duplication): 1. Administer carriers via add/change cabinet. 2. Administer circuit packs via change circuit-pack. 3. Administer connectivity and the facility options of the DS1 converter complex via add/ change fiber-link. To administer a critical-reliability system (PNC duplication): 1. Enable PNC duplication feature using the change system-parameter customer-option. 2. Administer carriers via add/change cabinet. 3.
PAGE 1082
Communication Manager Maintenance-Object Repair Procedures The red and green LEDs have the traditional use where red means an alarm condition and green indicates that maintenance testing is in progress. The red and green LED is also turned on during circuit pack initialization by firmware. When the control link to the circuit pack is lost, firmware controls the red LED to indicate an alarm condition.
PAGE 1083
DS1C-BD Clear Firmware-Counters Command DS1 converter firmware generates error reports autonomously. This takes place independently of technician-demanded tests. The test board location clear command will not affect the error status reported by firmware. The clear firmware-counters command clears every on-board firmware-detected error unconditionally.
PAGE 1084
Communication Manager Maintenance-Object Repair Procedures Replacing a DS1 Converter Circuit Pack with the Same Type DS1 Converter Circuit Pack — Unduplicated PNC ! WARNING: Do not power down a Switch Node carrier to replace a circuit pack. ! WARNING: Replacing a Switch Node Interface, Switch Node Clock, Expansion Interface or DS1 Converter circuit pack on an unduplicated system disrupts service. The service effect can range from outage of a single PN to outage of the entire system.
PAGE 1085
DS1C-BD Replacing a DS1 Converter Circuit Pack with the Same Type DS1 Converter Circuit Pack—Duplicated PNC ! WARNING: WARNING: On a system with duplicated PNC, synchronization may be provided over a combination of active and standby components. This condition is indicated by an OFF-BOARD WRN alarm against TDM-CLK with Error Type #2305. Repairs to standby PNC in this state may disrupt service. Otherwise, if the active PNC is functional, replacement of a standby component will not disrupt service.
PAGE 1086
Communication Manager Maintenance-Object Repair Procedures ! WARNING: Replacing a Switch Node Interface, Switch Node Clock, Expansion Interface or DS1 Converter circuit pack on an unduplicated system disrupts service. The service effect can range from outage of a single PN to outage of the entire system. ! WARNING: A DS1 Converter complex must consist of two TN574 boards or two TN1654 boards. A TN574 cannot be combined with a TN1654 in the same DS1 converter complex.
PAGE 1087
DS1C-BD Steps Comments Enter change circuit-packs cabinet #. Update the screen to show that TN1654 boards are now being used instead of TN574 boards. Also update the connected SNI, if applicable, to suffix B. Cabinet # represents the cabinet associated with a DS1 converter board. The change circuit-packs screen needs to be updated for both DS1 converter boards. Also, if needed, re-add translations for connected EI boards.
PAGE 1088
Communication Manager Maintenance-Object Repair Procedures Table 369: Upgrading TN574 DS1 Converter Circuit Packs in a fiber-link to TN1654s — Duplicated PNC Steps Comments Enter status pnc. Verify that the A-PNC is active. If the B-PNC is active, enter the reset pnc interchange command to cause the A-PNC to go active. Enter busyout pnc-standby. Fiber link cannot be removed if PNC duplication is operational. Must busyout the standby PNC first. Enter change system-parameters duplication.
PAGE 1089
DS1C-BD Table 369: Upgrading TN574 DS1 Converter Circuit Packs in a fiber-link to TN1654s — Duplicated PNC (continued) Steps Comments Enter change system-parameters duplication. Enter y in Enable Operation of PNC Duplication field. Enable PNC duplication. Enter add fiber-link fiber# to re-add the fiber-link using TN1654 DS1 converter circuit packs. fiber# represents the fiber-link number associated with the TN574 DS1 converter complexes that are being upgraded to TN1654 DS1 converter complexes.
PAGE 1090
Communication Manager Maintenance-Object Repair Procedures Converting DS1-CONV Complex to DirectConnect Fiber (duplicated PNC) Note: The following procedure is generic in its scope. Check the customer’s switch configuration for EI/SNI structures. Note: ! WARNING: Do not power down a Switch Node carrier to replace a circuit pack. ! WARNING: In duplicated PNC configurations, one DS1-CONV complex in the fiber-link serves as the active and the second DS1-CONV complex serves as the standby.
PAGE 1091
DS1C-BD Table 370: Convert from DS1-CONV to direct-connect fiber in a duplicated PNC Step Command/Step Description 8. Remove the DS1- CONV hardware. Remove the 4 TN574 or TN1654 DS1-CONV circuit packs and Y-cables. The TN1654 and TN574 DS1-CONV boards use unique “Y” cables that are incompatible with each other. Reuse these cables only with the proper circuit pack. 9. Install fiber-optic cable. Add the lightwave transceivers (multimode 9823A or single-mode 300A) to match the lightguide fiber.
PAGE 1092
Communication Manager Maintenance-Object Repair Procedures Removing Fiber Connectivity to an PN This procedure covers removing the connectivity to an PN or between SNs. Removing an PN and its associated carrier and circuit packs can be handled on a board-type basis. If this system is duplicated, start with step 1; otherwise, start with step 6. Note: The following procedure is generic in its scope. Check the customer’s switch configuration for EI/SNI structures.
PAGE 1093
DS1C-BD Table 371: Removing Fiber Connectivity from a PN (continued) Step Command/Step Description 8. change system-parameters duplication Enable PNC duplication by changing the Enable Operation of PNC Duplication field to y. 9. Physically remove the a-pnc and b-pnc fiber endpoint circuit packs Physically remove EI, SNI, and DS1C circuit packs associated with the b-pnc. 10. change circuit-pack Un-administer the PNC circuit packs. 11.
PAGE 1094
Communication Manager Maintenance-Object Repair Procedures Table 372: Downgrading from Critical to High Reliability (continued) Step # Command/Step Description 6. change fiber-link n Change fiber removes the b-pnc endpoints (EI, DS1Cs, if equipped). n is the number of the fiber from step 4. Repeat this step for every fiber from step 4. 7. Physically remove the b-pnc endpoint circuit packs Start with the switch carrier most distant from the media server.
PAGE 1095
DS1C-BD Error Log Entries and Test to Clear Values Table 373: DS1 Converter Board Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board SAT Test to Clear Value 0 (a) 0 Any Any Any test board location sh r 1 Failure Audit test (#949) MAJ ON/ OFF test board location sh r 1 release board UCSS 1 (b) 18 (c) 0 busyout board UCSS WRN OFF 125 (d) 3 None MIN ON 218 (e) any None MAJ ON Failure Audit test (#949) MIN ON test board location sh r 1 257 (f) 513
PAGE 1096
Communication Manager Maintenance-Object Repair Procedures Table 373: DS1 Converter Board Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board SAT Test to Clear Value 769 (q) 7 Failure Audit test (#949) MIN ON test board location sh r 1 1281(r) Failure Audit test (#949) MIN OFF test board location sh r 1 1537 (s) Failure Audit test (#949) MAJ OFF test board location sh r 1 1793 (t) Failure Audit test (#949) MAJ OFF test board location sh r 1
PAGE 1097
DS1C-BD d. Error Type 25: The 24/32-channel option switch setting on the TN1654 circuit pack does not match the administered Bit Rate on the fiber-link screen. If the on-board switch setting is wrong, the circuit pack must be physically removed to change the setting of the board option switch. If the administered bit rate is wrong, use change fiber-link to correct it. e. Error Type 218: The DS1 converter board is physically installed in a slot different than its administered slot.
PAGE 1098
Communication Manager Maintenance-Object Repair Procedures m. Error Type 769, Aux Data 2: This error only applies to TN574 DS1 converter circuit packs. If the alarm is on board, then a minor hardware problem has occurred that affects only circuit data being transmitted from the DS1 converter circuit pack. Replace the DS1 converter circuit pack.
PAGE 1099
DS1C-BD q. Error Type 769, Aux Data 7: A minor on-board hardware failure exists on the processor/ control hardware on the DS1 converter circuit pack. Replace the DS1 converter circuit pack. r. Error Type 1281: For TN574 DS1 converter boards, this error indicates that the facility masks or the clock reference masks do not match between the two DS1 converter circuit packs in the DS1 converter complex.
PAGE 1100
Communication Manager Maintenance-Object Repair Procedures 5. If the problem still persists, replace connectors and the cable between the neighbor DS1 converter circuit pack and the Fiber Endpoint at the other end of the DS1 converter complex. The cable may be a fiber or a metallic cable. u. Error Type 2049: Fiber Loss of Signal (LOS) alarm occurred at the other end of the DS1 converter complex.
PAGE 1101
DS1C-BD System Technician-Demanded Tests: Descriptions And Error Codes Investigate tests in the order presented. By clearing error codes associated with the Failure Audit, you may also clear errors generated from other tests in the sequence. Tests 788 and 789 are executed by the TN574 DS1 Converter circuit pack only.
PAGE 1102
Communication Manager Maintenance-Object Repair Procedures The reset sequence will take about one minute to complete. Table 374: Test #787 Reset Board Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1103
DS1C-BD Far-End DS1 Converter Circuit Pack Loopback Test (#788) This test is destructive. This test is executed by the TN574 DS1 Converter circuit pack only. See Test #790 for testing for the TN1654 DS1 Converter. This test starts at the DS1 converter circuit pack whose equipment location was entered, and loops all fiber time slots at the far edge Fiber Optic Interface of the DS1 converter circuit pack at the other end of the DS1 converter complex.
PAGE 1104
Communication Manager Maintenance-Object Repair Procedures Table 375: Test #788 Far-End DS1 Converter Board Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent to the selected DS1C board. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1105
DS1C-BD Table 375: Test #788 Far-End DS1 Converter Board Loop-Back Test (continued) Error Code Test Result Description / Recommendation FAIL Far-end DS1 converter loop back failed. A problem exists between the DS1 converter A and the DS1 converter B (see previous diagram). 1. If there are facilities that are not digital-data compatible, busyout the facilities via busyout ds1-facility. 2. If the test is executed as a part of an error analysis, then return back to the related section. 3.
PAGE 1106
Communication Manager Maintenance-Object Repair Procedures Every part of this test is executed under firmware control and the result is sent back to the maintenance software. The test is executed by sending digital data through every DS1 facility channel. Two different test patterns are used, these are hexadecimal values 55 and AA.
PAGE 1107
DS1C-BD Table 376: Test #789 Far-End FOT (Lightwave Transceiver) Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2300 ABRT The downlink message necessary to run this test could not be sent. 1. Retry the command at 1-minute intervals up to 3 times. 2301 ABRT The timer could not be set before sending the downlink message necessary to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2316 ABRT Fiber link is not administered.
PAGE 1108
Communication Manager Maintenance-Object Repair Procedures Table 376: Test #789 Far-End FOT (Lightwave Transceiver) Loop-Back Test (continued) Error Code Test Result Description / Recommendation FAIL Far-end lightwave transceiver loop back failed. A problem exists between the DS1 converter A and the lightwave transceiver connected to the DS1 converter B (see previous diagram). 1. If there are facilities that are not digital-data compatible, busyout the facilities via busyout ds1-facility. 2.
PAGE 1109
DS1C-BD DS1 Facilities Connectivity Test (#790) This test is destructive. The DS1 facilities connectivity test will check the correct connectivity of the DS1 facilities at opposite ends of the DS1 converter complex. Every part of this test is executed under firmware control and the result is sent back to the maintenance software. For TN574 DS1 Converter circuit packs, this test is executed by sending digital data through each time slot of every DS1 facility channel.
PAGE 1110
Communication Manager Maintenance-Object Repair Procedures Table 377: Test #790 DS1 Facilities Connectivity Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2301 ABRT The timer could not be set before sending the downlink message necessary to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2316 ABRT Fiber link is not administered. Use add fiber-link to administer the DS1 converter fiber link.
PAGE 1111
DS1C-BD Table 377: Test #790 DS1 Facilities Connectivity Loop-Back Test (continued) Error Code Test Result Description / Recommendation 55 FAIL TN1654 DS1 converter packet facility is down and can’t send loop-up message to the far end. 1. Enter display errors and follow the associated repair procedures for any DS1-FAC errors on the DS1 facilities at both ends of the DS1 converter complex. If an alarm exists on a DS1 facility, then this test will fail. 2.
PAGE 1112
Communication Manager Maintenance-Object Repair Procedures Board Options Audit (#795) This test is nondestructive. This test sends the administered circuit pack options to the DS1 converter circuit pack. Options are sent to both DS1 converter circuit packs at the same time to prevent any transitional mismatch of options.
PAGE 1113
DS1C-BD This test operates on both MOs DS1C-BD and DS1-FAC. Error counts of both MOs (DS1C-BD and DS1-FAC) that are displayed in the error log will be incremented when this test is executed. This test is also executed internally by the maintenance software when an alarm is resolved Table 378: Test #949 Failure Audit Error Code Test Result Description / Recommendation 2000 ABRT Timed out while waiting for a response from the circuit pack. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1114
Communication Manager Maintenance-Object Repair Procedures DT-LN-BD (Data Line Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DT-LN-BD MIN test board location sh Data Line circuit pack DT-LN-BD WRN test board location sh Data Line circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors. See also DAT-LINE (Data Line Port) on page 870 for related line information.
PAGE 1115
DTMR-PT (Dual-Tone Multifrequency Receiver Port) DTMR-PT (Dual-Tone Multifrequency Receiver Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DTMR-PT MAJ test port location sh Dual-Tone Multifrequency Receiver port (TTR) DTMR-PT MIN test port location sh Dual-Tone Multifrequency Receiver port (TTR) DTMR-PT WRN release port location Dual-Tone Multifrequency Receiver port (TTR) Dual-Tone Multifrequency Receiver ports (DTMR), also known as
PAGE 1116
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 379: Dual-Tone Multifrequency Receiver Port (TTR) Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (d) 17664 Tone Detector Audit/ Update test (#43) MAJ MIN (b) ON test port location r 2 18 0 busyout port location WRN ON release port location None WRN ON test port location sh r
PAGE 1117
DTMR-PT (Dual-Tone Multifrequency Receiver Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. Short Test Sequence Long Test Sequence D/ND1 Tone Detection Verification test (#42) X X ND Tone Detector Audit/Update test (#43) X X ND Order of Investigation 1. D = Destructive; ND = Nondestructive Tone Detection Verification Test (#42) This test checks the touch-tone digits detection capability of the DTMR port.
PAGE 1118
Communication Manager Maintenance-Object Repair Procedures Table 380: Test #42 Tone Detection Verification Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT The system could not allocate a Tone Generator for the test connection. This may be caused by a heavy load on the system or by a faulted Tone-Clock. 1. Check to see if there are any alarms against the Tone-Clock in the PN where the test aborted.
PAGE 1119
DTMR-PT (Dual-Tone Multifrequency Receiver Port) Tone Detector Audit/Update Test (#43) The DTMR port is refreshed with all time-slot information, and sanity audit is performed on the DTMR port. Table 381: Test #43 Tone Detector Audit/Update Test Error Code Test Result Description / Recommendation None ABRT The system was not able to allocate all the resources needed for this test. 1. Wait 1 minute and try again.
PAGE 1120
Communication Manager Maintenance-Object Repair Procedures 1120 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1121
E-DIG-BD (Multi Application Platform Board) E-DIG-BD (Multi Application Platform Board) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO DIG800-B MIN test board location sh MO800DIG-BD DIG800-B WRN test board location sh MO800DIG-BD The maintenance strategy for DIG800-BD is the same as the one described for MO-XXX-BD [XXX-BD (Common Port Circuit Pack/Media Module) on page 2539].
PAGE 1122
Communication Manager Maintenance-Object Repair Procedures LED Use The LED Control message 038x requests the Angel to drive the red, yellow, and green LEDs on the face plate of typical port board on or off. On the MAPD, only the red LED is controlled by this message. Yellow and green change requests received from the switch by the MAPD drive LCD behavior rather than LED behavior. The switch continues to send the same LED control messages to the MAPD that it currently sends to every other port board.
PAGE 1123
E-DIG-RES (TN800 reserve slot) E-DIG-RES (TN800 reserve slot) S8700 | 8710 / S8500 See ASAI-RES (TN800 reserve slot) on page 506.
PAGE 1124
Communication Manager Maintenance-Object Repair Procedures E-DIG-STA (Emulated Digital Line) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO E-DIG-ST MIN test port location l Emulated Digital Station E-DIG-ST WRN test port location sh Emulated Digital Station There are 4 tests in the Emulated Digital Line station maintenance test sequence and only one test path in the test sequence.
PAGE 1125
E-DIG-STA (Emulated Digital Line) Table 382: Digital Line Error Log Entries – E-DIG-STA (continued) Error Type Aux Data 2049 (g) Associated Test Alarm Level On/Off Board Test to Clear Value NPE Crosstalk test (#9) MIN WRN1 ON test port location l r 3 2305 (h) 32770 None 3840 (i) 40965 None 3841 (j) 41029 None 2304 (k) None 2 of 2 1. Major alarms may be downgraded to Warning alarms based on the value used in set options. Notes: a. Error Type 0: Run the short test sequence first.
PAGE 1126
Communication Manager Maintenance-Object Repair Procedures h. Error Type 2305: The station went off-hook while it was in the ready-for-service state. Use status station to determine the state of the station. The off-hook should have moved the station to ready-for-service. No technician action is necessary. i. Error Type 3840: No terminal is connected to the Digital Line board. No maintenance action is required. j. Error Type 3841: The circuit pack’s message buffer is full.
PAGE 1127
E-DIG-STA (Emulated Digital Line) Table 383: Test #9 Digital Line NPE Crosstalk Test Error Code Test Result Description / Recommendation 1 ABRT During testing of the primary information channel, system resources may not have been available or the port was busy during the test. 1. Check the port status. 2. Use display port location to determine the station extension of the port. Use status station to determine the service state of the port. If the port is in use, wait until it is idle before retesting.
PAGE 1128
Communication Manager Maintenance-Object Repair Procedures Table 383: Test #9 Digital Line NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Resolve any TTR-LEV errors. 2. Resolve any TONE-PT errors. 3.
PAGE 1129
E-DIG-STA (Emulated Digital Line) Voice and Control Channel Local Loop Test (#13) These tests check the information and control channels between the media server and the Digital Line port circuit. The media server sends a message to loop around both the information and control channels for the port.
PAGE 1130
Communication Manager Maintenance-Object Repair Procedures Table 384: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate time slots for the test. The system is under heavy traffic conditions or it has time slots out of service due to TDM-BUS errors. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, repeat test at 1-minute intervals up to 5 times.
PAGE 1131
E-DIG-STA (Emulated Digital Line) Table 384: Test #13 Voice and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 7 FAIL Conference test failed on primary channel. In some cases, users may not notice disruption in service. In extreme cases, conferencing feature may not work at all. 14 FAIL The primary voice channel is not transmitting properly. User impact may range from noticing nothing to not being able to use this port.
PAGE 1132
Communication Manager Maintenance-Object Repair Procedures 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. This test does not affect the status of the Message Waiting lamp.
PAGE 1133
E-DIG-STA (Emulated Digital Line) Table 385: Test #16 DIG-LINE Station Lamp Updates Test (continued) Error Code Test Result Description / Recommendation 1392 ABRT This is currently a TTI port, and the test cannot execute on it. 1. Verify that the port is a TTI port using either display port (the display shows that the port is a TTI port) or list config (the display shows a t for the port). 2. If either list config or display port indicates that the port is not a TTI port, escalate the problem.
PAGE 1134
Communication Manager Maintenance-Object Repair Procedures EMG-XFER (Emergency Transfer) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run1 Full Name of MO EMG-XFER MAJ test environment UU Emergency Transfer EMG-XFER WRN test environment UU Emergency Transfer 1. UU is the universal cabinet number listed in the PORT field of the Alarm or Error Log.
PAGE 1135
EMG-XFER (Emergency Transfer) Notes: a. Error Type 1 indicates that the Emergency Transfer switch located on the Processor circuit pack is set to the manual ON position (up). When the Emergency Transfer switch is in this position it generates a Major alarm. b. Error Type 257 indicates that the Emergency Transfer switch located on the Processor circuit pack is set to the manual OFF position (down). When the Emergency Transfer switch is in this position it generates a Warning alarm.
PAGE 1136
Communication Manager Maintenance-Object Repair Procedures Emergency Transfer Query Test (#124) This test queries the hardware for the state of the Emergency Transfer switch and reports the result. If the switch is in a position where the system software can control Emergency Transfer, then the test passes. If the switch is in a position where the system software cannot control Emergency Transfer, then the test fails. The Processor controls Emergency Transfer.
PAGE 1137
EMG-XFER (Emergency Transfer) Table 389: Test #124 Error Log Entries That Cause Emergency Transfer MO Name Error Type Aux Data SW-CTL 1 SW-CTL 2 TONE-BD 1 0 TONE-BD 2305 0 S8700 | 8710 / S8500 The Emergency Transfer MO monitors the position of the Emergency Transfer switch(es) on the EPNs’ Maintenance circuit packs. It does not monitor whether the system is actually in Emergency Transfer.
PAGE 1138
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 390: EMG-XFER Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test environment UU 1 0 Emergency Transfer query (#124) MAJ ON test environment UU r 3 257 0 Emergency Transfer query (#124) WRN ON test environment UU r 3 1. Run the short test sequence first. If every test passes, run the long test sequence.
PAGE 1139
EMG-XFER (Emergency Transfer) Table 391: System Technician-Demanded Tests: EMG-XFER (Multicarrier Cabinets) Short Test Sequence Long Test Sequence D/ND1 X X ND Analog Ring Generator Initialization test (#117) (f) X X ND Analog Ring Generator Query test (#118) (f) X X ND Order of Investigation External Alarm Lead Query test (#120) (e) Analog Ring Generator Initialization test 2 of 2 1. D = Destructive, ND = Nondestructive Notes: a. See POWER on page 1869 for a description of this test. b.
PAGE 1140
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes (Single-Carrier) Investigate tests in the order presented. By clearing error codes associated with the Power Query test (#79), you may also clear errors generated from other tests in the sequence.
PAGE 1141
EMG-XFER (Emergency Transfer) Emergency Transfer Query Test (#124) The Emergency Transfer Query test queries the hardware for the state of the Emergency Transfer switch and reports the result. If the position of the switch in a PN cabinet is such that the system software can control Emergency Transfer (auto), then the test passes. If the position of the switch or switches is such that the system software cannot control Emergency Transfer (manual “on” or manual “off”), then the test fails.
PAGE 1142
Communication Manager Maintenance-Object Repair Procedures Table 392: Test #124 Emergency Transfer Query Test (continued) Error Code Test Result Description / Recommendation 34, 290 FAIL Emergency Transfer is manually turned ON (Emergency Transfer switch on). 1. Place the switch in the AUTO position. PASS System software has control of Emergency Transfer within this cabinet. If Emergency Transfer is currently invoked (the emergency transfer LED is on), the cause could be a major alarm. 1.
PAGE 1143
EPN-SNTY (PN Sanity Audit) EPN-SNTY (PN Sanity Audit) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO EPN-SNTY None None EPN Sanity Audit The EPN Sanity Audit feature enhances the system’s ability to recover from failure conditions that disable an entire PN. In such situations, not only is the affected PN unable to provide service to the system, but the system itself has not detected the condition.
PAGE 1144
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 393: EPN-SNTY Error Log Entries Error Type Aux Data Associated Test 0 (a) 0 Any 8801 (b) Any None 8803 (c) Any None 9901 (d) Any None 9902 (e) Any None 9903 (f) Any None 9904 (g) Any None 9905 (h) Any None Alarm Level On/Off Board Test to Clear Value None Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence.
PAGE 1145
ERR-LOG (Error Log) ERR-LOG (Error Log) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO ERR-LOG none none Error Log The ERR-LOG MO is responsible for the sanity of the Alarm Log, the Hardware Error Log, and the Software Error Log. If an inconsistency is detected in any one of these logs, every log will be re-initialized and a hardware error will be logged against ERR-LOG indicating the time of inconsistency.
PAGE 1146
Communication Manager Maintenance-Object Repair Procedures ESS (Enterprise Survivable Server) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO ESS MAJ None Enterprise Survivable Server ESS MIN None Enterprise Survivable Server The Enterprise Survivable Server (ESS) maintenance object (MO) monitors the status of the ESS feature. On the Main server the MO will: ● Monitor the registration status for all administered ESS.
PAGE 1147
ESS (Enterprise Survivable Server) Table 394: ESS Error Log Entries Error Type 257 (b) Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value None MIN OFF ESS is not registered. Resolve any server and/or network problems. 513 (c) None MIN OFF Connection not established between ESS server and IPSI. Resolve network command to IPSI any ESS server and/or problems. Use the PING to verify connectivity circuit packs. 2 of 2 Notes: a. Error Type 1: This error only applies to an ESS.
PAGE 1148
Communication Manager Maintenance-Object Repair Procedures ! CAUTION: Issuing the commands below will cause a service interruption. When Port Networks switch to either a Main server or ESS server a level 2 restart is initiated on the Port Network. Service will be interrupted to the entire Port Network. Note that shuffled IP to IP calls will not be dropped but during the restart they will not have any access to features (Hold, Transfer, Conference, etc.). CAUTION: 7.
PAGE 1149
ESS (Enterprise Survivable Server) At the Main: 1. Use display system-parameters ess to verify that the ESS server is properly administered. A ESS server must be administered on the Main before it can register with the Main. Record these values for use when troubleshooting the ESS server. 2. Use the SAT ping ip-address board nnn.nnn.nnn.nnn command to verify connectivity between the Main server and the ESS.
PAGE 1150
Communication Manager Maintenance-Object Repair Procedures 8. On the Maintenance WEB Interface Configure Server pages: Note: ● Verify on the Set Identities page that the correct Server ID (SVID) is entered. This should be a unique value for each server. The SVID must be between 1 and 99. Gaps in the SVIDs for a configuration are allowed (10, 20, 30,...) but the servers may be consecutively numbered if desired. Each server in the system, duplex or simplex, Main or ESS, requires a unique SVID.
PAGE 1151
ESS (Enterprise Survivable Server) 2. From the Maintenance Web Interface pages of the ESS server that is not connecting, initiate a PING to the administered IPSIs to verify connectivity between the ESS server and IPSIs. 3. Firewalls or other security measures may preclude the server and IPSI from communicating.
PAGE 1152
Communication Manager Maintenance-Object Repair Procedures 5. Resolve network fragmentation and outage issues per local practice. 6. Use the SAT command status ess port-network to verify that all Port Networks (IPSIs) are communicating with media servers. System Technician-Demanded Tests: Descriptions and Error Codes There are no system technician demanded tests for the ESS maintenance object. Order of Investigation Short Test Sequence Long Test Sequence Reset Board Sequence D/ND1 None 1.
PAGE 1153
ETH-PT (Control LAN Ethernet) ETH-PT (Control LAN Ethernet) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO ETH-PT MAJ test port location long MO_ETH_PT ETH-PT MIN test port location long MO_ETH_PT ETH-PT WRN test port location short MO_ETH_PT The TN799DP Control LAN (C-LAN) packet port circuit pack provides TCP/IP connection to adjuncts applications such as CMS, INTUITY, and DCS Networking.
PAGE 1154
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Value Table 395: ETH-PT Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location s 1 (b) 0 Ethernet Local Looparound test (#1278) MIN ON test port location l r 3 513 (c) 0 Link Integrity Inquiry (#1282) MIN OFF test port location r 2 769 (d) 0 WRN OFF 1281 (e) 0 Session Status test (#1286) MIN OFF TCP/
PAGE 1155
ETH-PT (Control LAN Ethernet) d. Error Type 769: Port received invalid frame. Invalid Ethernet frame errors occur when the frame: ● Contains a bad cyclic redundancy check (CRC) ● Is misaligned 1. Isolate the problem with the Ethernet Local Looparound test (#1278). 2. Test the port (test port location long). 3. Verify the repair with the Ethernet Local Looparound test (#1278). 4. Clear the alarm (test port location long clear). e.
PAGE 1156
Communication Manager Maintenance-Object Repair Procedures 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. Error Type 3329: TCP/IP Ping test failed. 1. Test port (test port location short). 2. Refer to TCP/IP Ping test (#1281) repair procedures.
PAGE 1157
ETH-PT (Control LAN Ethernet) Table 397: Test #1278 Ethernet Local Loop-Around Test Error Code Test Result Description / Recommendation 1000 ABRT The port is in use. 1. Determine status of port (status clan-port location). 2. Retry the command when the port is idle. You can force the port to the idle state by executing busyout port location. ! CAUTION: CAUTION: 2000 ABRT The busyout port command is destructive, causing every call and link associated with the port to be torn down.
PAGE 1158
Communication Manager Maintenance-Object Repair Procedures TCP/IP Ping Test (#1281) This nondestructive test fails if every endpoint fails to respond. Use this test to check the circuitry in the data path for a peer-to-peer IP layer connection. Table 398: Test #1281 TCP/IP Ping Test Error Code Test Result Description / Recommendation 1 2 11 ABRT Internal error 1. Retry the command at 1-minute intervals up to 3 times. 2. If the problem persists, escalate the problem. 7 ABRT Destination unreachable.
PAGE 1159
ETH-PT (Control LAN Ethernet) Table 398: Test #1281 TCP/IP Ping Test (continued) Error Code Test Result Description / Recommendation 1125 ABRT Ethernet link not in service. 1. Verify Ethernet link is in service (status port location or status link n). 2. If the link is not in service, release the link using (release link n or release port location). 3. Repeat the test. 4. Escalate if the problem persists. 2000 ABRT Did not receive circuit pack test response within the allowable time period. 1.
PAGE 1160
Communication Manager Maintenance-Object Repair Procedures Table 398: Test #1281 TCP/IP Ping Test (continued) Error Code Test Result Description / Recommendation 1007 FAIL Ping to the destination failed due to the destination down. 1. Verify that at least one destination reachable through this port is up. Ping this destination (ping ip-address xxx.xxx.xxx.xxx). 2. If the ping to any destination is successful through this port, the link is up, although some destinations are unreachable.
PAGE 1161
ETH-PT (Control LAN Ethernet) Table 399: Test #1282 Link Integrity Inquiry Test (continued) Error Code Test Result Description / Recommendation 1125 ABRT Ethernet link not in service. 1. Verify whether Ethernet link is in service (status port location or status link n). 2. If the Ethernet link is not in service, release the link (release link n or release port location). 3. Repeat the test. 4. Escalate if the problem persists. 1959 ABRT Downlink message error. 1.
PAGE 1162
Communication Manager Maintenance-Object Repair Procedures Session Status Test (#1286) This nondestructive test determines the status of every Ethernet port session. This test queries the system software on port session status. If the system software indicates that. . . Then the switch . . .
PAGE 1163
ETH-PT (Control LAN Ethernet) Table 400: Test #1286 Session Status Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not locate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals, up to 5 times. 2. Escalate if the problem persists. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals, up to 3 times. 2. Escalate if the problem persists.
PAGE 1164
Communication Manager Maintenance-Object Repair Procedures Verify NIC Options Test (#1511) This test is non-destructive. This test verifies if the NIC interface parameters, speed, and duplex (full/half) match with administration. The test passes if the NIC parameters match administration. The test fails if the NIC parameters do not match administration. Table 401: Verify NIC Options Test (#1511) Error Code Test Result Description / Recommendation 1014 ABRT Board is not inserted.
PAGE 1165
ETH-PT (Control LAN Ethernet) Table 401: Verify NIC Options Test (#1511) (continued) Error Code Test Result Description / Recommendation 3585 FAIL Aux Data = 1. The board is reporting that it is running half duplex with auto-negotiate (y). Communication Manager is trying to negotiate the settings on the circuit pack to match the administered settings and, under the above condition, it is logging a fault.
PAGE 1166
Communication Manager Maintenance-Object Repair Procedures Table 401: Verify NIC Options Test (#1511) (continued) Error Code Test Result Description / Recommendation 3585 FAIL Aux Data = 2. The board is reporting different options than what is administered. Software tried to correct the options but the board did not take the option update. It could be argued that this is a false alarm, especially if the link is operating correctly with no observable degradation of service.
PAGE 1167
ETR-PT (Enhanced Tone Receiver Port) ETR-PT (Enhanced Tone Receiver Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO ETR-PT MAJ test port location sh Enhanced Tone Receiver Port ETR-PT MIN test port location sh Enhanced Tone Receiver Port ETR-PT WRN test port location sh Enhanced Tone Receiver Port Note: Replacing the Tone-Clock circuit pack requires a special procedure which is described in TONE-BD (Tone-Clock Circuit) on page 2327.
PAGE 1168
Communication Manager Maintenance-Object Repair Procedures TN2182 Tone-Clock Circuit Pack (for Non IPSI Connected PNs) A TN2182 is a combined Tone Generator/Tone Detector board. It provides eight Enhanced Tone receiver (ETR) ports. Each of these ports provides the functions previously found individually on DTMR-PTs, GPTD-PTs and CLAS-PTs ports. Each port on the TN2182 may be used for any tone-detection function that was previously done by TN748, TN420, or TN744 Tone Detection boards.
PAGE 1169
ETR-PT (Enhanced Tone Receiver Port) 1. Use list configuration carrier to get the board type and location. If the board is TN744, then do steps 2–4; if it is TN2182 or TN2312, do steps 5–12. 2. Execute three commands: busyout board location, reset board location, and release board location. Reset is required to reload RAM associated with the TN744’s DSPs. This will take all eight tone detector ports out of service for a few seconds. Only four of the eight would be out of service due to the alarm.
PAGE 1170
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. Short Test Sequence Long Test Sequence D/ND1 Tone Detection Verification test (#42) X X ND Tone Detection Audit/Update test (#43) X X ND Order of Investigation 1.
PAGE 1171
ETR-PT (Enhanced Tone Receiver Port) Table 403: Test #42 Tone Detection Verification Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate time slots for the test connection. This situation could occur when the system is heavily loaded. If the system is not heavily loaded, test the TDM-BUS with test tdm. 1. Retry the command at 1-minute intervals up to 5 times. 1003 ABRT The system could not allocate a Tone-Clock for the test connection.
PAGE 1172
Communication Manager Maintenance-Object Repair Procedures Table 403: Test #42 Tone Detection Verification Test (continued) Error Code Test Result Description / Recommendation 102 FAIL 2225-Hz Modem Answer Tone was not detected correctly. This impacts call-classification operation. 1. Run the short test sequence via test port location sh r 1. 2. If the problem persists, the system can still operate properly but capacity is reduced.
PAGE 1173
ETR-PT (Enhanced Tone Receiver Port) Tone Detector Audit/Update Test (#43) A Digital Signal processor sanity audit is performed on the ETR-PT. Table 404: Test #43 Tone Detector Audit/Update Test Error Code Test Result Description / Recommendation none ABRT The system could not allocate every resource needed for this test. 1. Rerun the test at 1-minute intervals up to 5 times. 2000 ABRT Response to the test request was not received within the allowable time period. 1.
PAGE 1174
Communication Manager Maintenance-Object Repair Procedures Table 404: Test #43 Tone Detector Audit/Update Test (continued) Error Code Test Result Description / Recommendation FAIL Hardware audit failed. 1. Use list configuration carrier to get the board type and location. If the board is TN744, then do steps 2–4; if it is TN2182/ TN2312AP, do steps 5–12. 2. Execute three commands: busyout board location, reset board location, and release board location.
PAGE 1175
ETR-PT (Enhanced Tone Receiver Port) Table 404: Test #43 Tone Detector Audit/Update Test (continued) Error Code Test Result FAIL (cont’d) Description / Recommendation 10. Test the alarmed board (test tone location long). This resets the board and is required to reload on-board RAM associated with the TN2182’s/TN2312AP’s DSPs. 11. If every test passes and the alarm does not resolve, retest with test tone location long clear. 12. If the test passes, terminate the repair process.
PAGE 1176
Communication Manager Maintenance-Object Repair Procedures EXP-INTF (Expansion Interface Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO EXP-INTF MAJ test board location s Expansion Interface circuit pack EXP-INTF MIN test board location s Expansion Interface circuit pack EXP-INTF WRN test board location s Expansion Interface circuit pack ! WARNING: WARNING: If the Expansion Interface (EI) circuit pack you are troubleshooting
PAGE 1177
EXP-INTF (Expansion Interface Circuit Pack) In a CSS configuration with duplicated Port Network Connectivity (PNC), EI circuit packs reside in the Switch Node Carrier (see Figure 64: Center Stage Switch Configuration with Duplicated PNC on page 1180). In this case, the EI and SNI circuit packs may be connected via a metallic cable instead of an optical fiber link. Metallic cable should be tested and replaced in the same manner as optical fiber.
PAGE 1178
Communication Manager Maintenance-Object Repair Procedures Each PN in a direct-connect configuration must be connected to the other PNs through a fiber link. Each PN has one EI that functions as an Archangel. This EI must be connected with fiber to an EI. If an EI is functioning as an Archangel (bus master), its amber LED will be flashing at a rate of 2 seconds on and 200 ms off. Figure 62 shows the location of EI circuit packs in a typical duplicated PNC, direct-connect configuration.
PAGE 1179
EXP-INTF (Expansion Interface Circuit Pack) Figure 63 shows the location of EIs in a typical center stage switch configuration with unduplicated PNC.
PAGE 1180
Communication Manager Maintenance-Object Repair Procedures Figure 64: Center Stage Switch Configuration with Duplicated PNC B-PNC FIBER SN #1 CAB 1 CARRIER D E S I N I S N C S N I S N I 1 10 13 20 2 SN #2 CAB 2 CARRIER D 21 1 Slot # S N I S N C S N I 2 10 13 METALLIC CABLE FIBER FIBER EPN E I EPN E I CAB 2 CARRIER B CAB 3 CARRIER B Slot # 2 2 E I METALLIC CABLE E I CAB 2 CARRIER A Slot # 1 CAB 3 CARRIER A 1 FIBER SN #1 CAB 1 CARRIER E E S I N I 1 2 FIBER S N C S N I
PAGE 1181
EXP-INTF (Expansion Interface Circuit Pack) Figure 65: Fiber Link with DS1 Converter Complex METALLIC CABLE or OPTICAL FIBER EI (TN570) or SNI (TN573) METALLIC CABLE or OPTICAL FIBER 1 to 4 DS1 FACILITIES DS1C DS1C EI (TN574) (TN574) (TN570) EI In-Service Mechanism In order for calls to be routed through a given PN, the EI that is part of the connectivity to that PN must be put into service. In order for an EI to be put into service, the following criteria must be met: 1.
PAGE 1182
Communication Manager Maintenance-Object Repair Procedures Survivable Remote EPN The Survivable Remote EPN (SREPN) feature allows a S8700 Multi-Connect EPN (either MCC or SCC) to provide service to the customer when: Note: ● Its fiber (or T1/E1 EI link to the S8700 Multi-Connect processor) fails or is severed ● The S8700 Multi-Connect processor or center stage fails. Note: This feature is viewed as a “disaster recovery operation” capability rather than as an additional reliability option.
PAGE 1183
EXP-INTF (Expansion Interface Circuit Pack) Restoring Normal Service to the SREPN ! WARNING: WARNING: Every call within the SREPN is terminated when the SREPN feature is returned to normal service. To restore normal connections to the SREPN EI circuit pack in the S8700 Multi-Connect PN, you must: 1. Clear every error logged against the S8700 Multi-Connect SREPN EI circuit pack by using the suggested repair procedures outlined in this MO. 2.
PAGE 1184
Communication Manager Maintenance-Object Repair Procedures Another way to determine which PNC (and therefore, which EIs in an EPN) is active and which is standby, use status port-network and status PNC. See Table 405: Expansion Interface Circuit Pack Amber LED Flashing States on page 1184 for the possible EI amber LED states. Table 405: Expansion Interface Circuit Pack Amber LED Flashing States Condition LED On LED Off Fiber Out-of-Frame (a) 0.1 second 0.1 second In Frame-No Neighbor (b) 0.
PAGE 1185
EXP-INTF (Expansion Interface Circuit Pack) The link between two active EI circuit packs or between an active EI circuit pack and an active SNI circuit pack is involved in synchronization. The EI circuit pack reports slip errors if synchronization is not operating properly. When diagnosing synchronization problems, the EI circuit packs should be examined as a possible cause. Expansion Interface LEDs The EI circuit pack has the standard red, green, and amber LEDs.
PAGE 1186
Communication Manager Maintenance-Object Repair Procedures c. This is the normal state for an active PN EI circuit pack that is also the bus master (Expansion Archangel) in the PN. d. This is the normal state for an active EI circuit pack that is not the bus master (Expansion Archangel) for a PN. This applies only in the Direct Connect configuration where the EI circuit pack in a PN is connected via a fiber link to an EI circuit pack in the other PN. e.
PAGE 1187
EXP-INTF (Expansion Interface Circuit Pack) The symptoms of the problem in which an invalid system clock causes an Expansion Link to go down are as follows: ● If the Tone-Clock in the PN provides the current on-line synchronization reference (see status synchronization), is providing an invalid system clock: Any EI or SNI circuit pack has a Fiber Out-of-Frame condition or a No Neighbor condition. An EI circuit pack amber LED blinks quickly when a Fiber Out-of-Frame condition exists (0.1 seconds on, 0.
PAGE 1188
Communication Manager Maintenance-Object Repair Procedures the problem was probably that the synchronization on-line reference became invalid. Since reference switching was disabled, the Tone-Clock did not switch from the invalid reference. Therefore, the Tone-Clock circuit pack put out a system clock that was “out of spec.” Enter enable synchronization-switch. If the PN is down, reseat the Tone-Clock circuit packs on the PN. This action should restore the PN to service.
PAGE 1189
EXP-INTF (Expansion Interface Circuit Pack) ! CAUTION: If, after every link is restored, you suspect the problem might have been due to a defective Tone-Clock circuit pack, switch to this Tone-Clock at an appropriate time. If the Tone-Clock circuit pack was the cause of the problem and the same EI circuit packs are in place, the same link(s) will go down again. CAUTION: a.
PAGE 1190
Communication Manager Maintenance-Object Repair Procedures Step Action Explanation / Caution 1. Enter busyout board location. location = cabinet-carrier-slot location of the circuit pack to be replaced. 2. Replace the circuit pack. 3. Wait for the circuit pack to reset. Red and green LEDs light and then go out. If the red LED remains lit, see the previous note under Expansion Interface LEDs on page 1185. 4. Enter release board location.
PAGE 1191
EXP-INTF (Expansion Interface Circuit Pack) Step Action Explanation / Caution 7. Wait 5 minutes for SNI-BD, SNI-PEER, FIBER-LK, and DS1C-BD alarms to clear, or enter clear firmware-counters a-pnc or b-pnc. Use the letter designation of the PNC that holds the replaced component (the standby PNC). 8. Enter status pnc. If either PNC’s state of health (SOH) is not “functional,” consult PNC-DUP (PNC Duplication) on page 1851. 9. Enter release pnc.
PAGE 1192
Communication Manager Maintenance-Object Repair Procedures 4. Go to the front of the cabinet and inspect the amber LED. ● If the amber LED flashes on at a rate of once per second, the (EI or SNI) circuit pack or transceiver should be replaced. ● If the amber LED flashes on at a rate of five times per second, the circuit pack (EI or SNI) or the lightwave transceiver may need replacement. This condition may also be due to a faulty system clock on the network containing this EI circuit pack.
PAGE 1193
EXP-INTF (Expansion Interface Circuit Pack) Error Log Entries and Test to Clear Values Table 407: EXP-INTF Error Log Entries Error Type Aux Data1 Associated Test Alarm Level On/Off Board Test to Clear Value 02 0 Any Any Any test board location 1 Any EI Local TDM Looparound (#240) MAJ ON test board location r 2 EI Local TDM Looparound (#240) MAJ ON test board location r 2 release board location 2 18 (a) 0 busyout board location WRN OFF 23 (b) 0 None WRN OFF 125 (c) None MIN
PAGE 1194
Communication Manager Maintenance-Object Repair Procedures Table 407: EXP-INTF Error Log Entries (continued) Error Type Aux Data1 Associated Test Alarm Level On/Off Board 2049 (j) 117 None WRN OFF 2305 (k) 118 None WRN OFF 2306 (l) 3 None WRN OFF Test to Clear Value 112 2561 (m) Any None MIN ON 2817 (n) Any None MIN ON 3073 (o) Any EI Packet Interface test (#589) MAJ OFF test board location r 3 3074 (p) 2 EI Packet Interface test (#589) MAJ OFF test board location
PAGE 1195
EXP-INTF (Expansion Interface Circuit Pack) b. Error Type 23: EI circuit pack has been administered on the Circuit Pack screen, but has not been physically inserted into the system. Insert the circuit pack. c. Error Type 125: A different circuit pack occupies the slot where this circuit pack is logically administered. To resolve this problem, either: 1. Replace the incorrect circuit pack with the logically assigned circuit pack. 2.
PAGE 1196
Communication Manager Maintenance-Object Repair Procedures i. Error Type 1538 indicates a hyperactive EI circuit pack that is generating an abnormal amount of control messages to the Processor. When this error was generated, the EI was automatically reset by the system. If this system does not have duplicated Port Network Connectivity, service to the PN will have been disrupted.
PAGE 1197
EXP-INTF (Expansion Interface Circuit Pack) o. Error Type 3073: Perform the following steps for Error Type 3073: 1. Execute display errors and resolve any errors on the following: PKT-BUS, PKT-INT, PDATA-BD, PGATE-BD, BRI-BD, BRI-PT, BRI-SET/ASAI, UDS1-BD. 2. Enter test board location r3 for this circuit pack. If this error continues to appear, replace the EI circuit pack. p. Error Types 3074 and 3075: failures of the EI circuit pack Packet Path test.
PAGE 1198
Communication Manager Maintenance-Object Repair Procedures t. Error Type 3842 indicates that the test that queries the EI for the state of the lock to the system clock has failed. This means that a loss of lock condition is present. u. The counter associated with Error Types 3841 and 3842 is cleared when the query for the state of the clock-to-system-clock passes. Once the alarm is raised, this test is run every five minutes. However, the test is not part of any sequence that can be run on demand.
PAGE 1199
EXP-INTF (Expansion Interface Circuit Pack) When testing of the EI is not possible, (for example, when the PN is down), see the previous EI Manual Loop-Back procedure. Expansion Interface Neighbor Query Test (#237) This test is nondestructive. The Expansion Interface Neighbor Query test is a request to an EI circuit pack to determine whether it has established communication with its neighbor EI or SNI circuit pack.
PAGE 1200
Communication Manager Maintenance-Object Repair Procedures Table 409: Test #237 Expansion Interface Neighbor Query Test (continued) Error Code Test Result Description / Recommendation 1033 FAIL The EI circuit pack under test cannot make contact with its neighbor EI or SNI circuit pack. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192).
PAGE 1201
EXP-INTF (Expansion Interface Circuit Pack) Expansion Interface Fiber Out-of-Frame (FOOF) Query Test (#238) This test is nondestructive. This test is a request to an EI circuit pack to determine whether it is currently detecting the framing sequence on the incoming fiber data stream. If it cannot detect this framing signal, the EI circuit pack will not be able to establish a link with the neighbor EI or SNI circuit pack.
PAGE 1202
Communication Manager Maintenance-Object Repair Procedures Table 410: Test #238 Expansion Interface Fiber Out-of-Frame Query Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check the error log for wrong board (error 125) or no board (error 131). Resolve either of these issues, if applicable. 2. Check that the board is properly translated and inserted. If so, check for hyperactivity (error 1538).
PAGE 1203
EXP-INTF (Expansion Interface Circuit Pack) Table 411: Test #240 Expansion Interface Local Looparound (continued) Error Code Test Result Description / Recommendation 2 ABRT Could not allocate time slot on TDM Bus B. Loop back passed on TDM Bus A. 1. If there is no reason to doubt that the EI circuit pack can transfer data to or from a TDM Bus, then since the test passed on one bus, assume that the test passes on the other bus. 2.
PAGE 1204
Communication Manager Maintenance-Object Repair Procedures Table 411: Test #240 Expansion Interface Local Looparound (continued) Error Code Test Result Description / Recommendation 1032 ABRT The EI cannot detect the framing signal and cannot run the test. 1. Refer to the errors for Test #238 to determine why the EI circuit pack is out of frame. 1033 ABRT The EI circuit pack does not have a fiber link administered to it. There is not sufficient data to run test. 1.
PAGE 1205
EXP-INTF (Expansion Interface Circuit Pack) Table 411: Test #240 Expansion Interface Local Looparound (continued) Error Code Test Result Description / Recommendation 1 FAIL Loop back on TDM Bus A failed. Loop back on TDM Bus B passed. 2 FAIL Loop back on TDM Bus B failed. Loop back on TDM Bus A passed. 3 FAIL Loop back on both TDM Buses failed. 12 FAIL Loop back on TDM Bus B failed. Loop back on TDM Bus A aborted because the system could not allocate time slots.
PAGE 1206
Communication Manager Maintenance-Object Repair Procedures Expansion Interface 2-Way Transmission Test (#241) This test is nondestructive. The EI 2-way transmission test is a basic connectivity test between two PNs. The test first sends dial tone from the cabinet of the EI circuit pack under test through the Center Stage Switch, through the DS1 converter circuit packs, and through another EI circuit pack to a tone detector in the other cabinet.
PAGE 1207
EXP-INTF (Expansion Interface Circuit Pack) Table 412: Test #241 Expansion Interface 2-Way Transmission Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Enter display errors and follow the repair procedures for TTR-LEV errors in the error log.
PAGE 1208
Communication Manager Maintenance-Object Repair Procedures Table 412: Test #241 Expansion Interface 2-Way Transmission Test (continued) Error Code Test Result Description / Recommendation 1394 ABRT The EI circuit pack is out of service and the test cannot be run. This condition is due to a change in the EI circuit pack’s ability to communicate with the EI or SNI circuit pack on the other end of the fiber. 1. Run Test #237, and check the Error Log for EXP-INTF Error Type 1281.
PAGE 1209
EXP-INTF (Expansion Interface Circuit Pack) Table 412: Test #241 Expansion Interface 2-Way Transmission Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 3 times. 2100 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 3 times. 2500 ABRT Internal system error 1.
PAGE 1210
Communication Manager Maintenance-Object Repair Procedures Table 412: Test #241 Expansion Interface 2-Way Transmission Test (continued) Error Code Test Result Description / Recommendation 3 or 4 FAIL The failure codes only apply to a system equipped with a Center Stage Switch.
PAGE 1211
EXP-INTF (Expansion Interface Circuit Pack) This is a 2-part connectivity test. In the first part of the test, a digital count is transmitted from the cabinet of the EI circuit pack under test, through the EI circuit pack under test, out to its lightwave transceiver. The connection then loops back into the lightwave transceiver, through the same EI circuit pack again, and into the originating cabinet. If the test tone is detected by a tone detector, the first part of the test passes.
PAGE 1212
Communication Manager Maintenance-Object Repair Procedures Figure 69: Packet Bus Lightwave Transceiver Looparound—PN only lightwave transceiver TDMBUS (PN X) EXP_INTF Packet Interface To CSS or Neighbor EI Figure 70: Packet Bus Lightwave Transceiver Looparound—CSS and PN EXP_INTF EXP_INTF Packet Interface CSS (Optional) lightwave transceiver EXP_INTF To CSS or Neighbor EI Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound Error Code Test Result Description / Recommendati
PAGE 1213
EXP-INTF (Expansion Interface Circuit Pack) Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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. 1. Enter display errors and follow associated repair procedures for TTR-LEV.
PAGE 1214
Communication Manager Maintenance-Object Repair Procedures Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound (continued) Error Code Test Result Description / Recommendation 1139 ABRT The packet bus in the PN where this EI board resides has a major alarm against it. This test needs to use the alarmed PN’s packet bus. 1. Enter display alarms and display errors and resolve any PKT-BUS alarms. 2. Retry the command. 1141 ABRT The Packet Interface circuit pack is out of service.
PAGE 1215
EXP-INTF (Expansion Interface Circuit Pack) Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound (continued) Error Code Test Result Description / Recommendation 1407 ABRT This test cannot be run on an EI board that is on the active PNC because it cannot be busied out. This error code indicates that PNC duplication is enabled. 1. Attempt to perform a PNC interchange via reset pnc interchange. 2.
PAGE 1216
Communication Manager Maintenance-Object Repair Procedures Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound (continued) Error Code Test Result Description / Recommendation 2 FAIL The test tone was transmitted and detected correctly, but the correct data packet was not detected by the TN1655 Packet Interface circuit pack. 1. Test the TN1655 Packet Interface circuit pack to verify that it is functioning properly.
PAGE 1217
EXP-INTF (Expansion Interface Circuit Pack) Table 413: Test #242 Expansion Interface Lightwave Transceiver Looparound (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check the error log for wrong board (Error 125) or no board (Error 131). Resolve either of these issues, if applicable. 2. Check that the board is properly translated and inserted. If so, check for hyperactivity (Error 1538). If hyperactive, use reset board location. 3.
PAGE 1218
Communication Manager Maintenance-Object Repair Procedures Table 414: Test #316 Expansion Interface Control Channel Test (continued) Error Code Test Result Description / Recommendation Any FAIL The EI circuit pack responded incorrectly or if it is the PN active EI circuit pack, it could not talk to PN circuit packs. 1. If the active EI circuit pack in the PN is failing and duplicated PNC is enabled, attempt to switch to the standby PNC using reset PNC interchange. 2. Repeat the short test sequence. 3.
PAGE 1219
EXP-INTF (Expansion Interface Circuit Pack) Expansion Interface Reset Test (#336) This test is destructive. This test is potentially very destructive and requires the EI circuit pack to be busied out prior to execution of this test. The Expansion Interface Reset test, which is not part of either the Short or the Long test sequences test, is executed via reset board location where location is the location of the EI circuit pack to be reset.
PAGE 1220
Communication Manager Maintenance-Object Repair Procedures Table 415: Test #336 Expansion Interface Reset Test Error Code Test Result Description / Recommendation 4 ABRT Could not reset the PN EI circuit pack over the optical fiber since the neighbor EI circuit pack or SNI circuit pack is not recognized by software (inserted). 1. Insert neighbor EI circuit pack or SNI circuit pack and perform reset again.
PAGE 1221
EXP-INTF (Expansion Interface Circuit Pack) Table 415: Test #336 Expansion Interface Reset Test (continued) Error Code Test Result Description / Recommendation 3 FAIL The reset over the optical fiber failed. 1. Execute test board location on the PN neighbor EI circuit pack located on the opposite end of the fiber from this EI circuit pack. If Test #238 fails, follow the maintenance procedure associated with this test result. Then perform the reset again. 2.
PAGE 1222
Communication Manager Maintenance-Object Repair Procedures Table 415: Test #336 Expansion Interface Reset Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Resolve either wrong board (error 125) or no board (error 131) issues. 2. Check that the board is properly translated and inserted. If so, check for hyperactivity (error 1538). If hyperactive, use reset board location. 3. Run the test again.
PAGE 1223
EXP-INTF (Expansion Interface Circuit Pack) Figure 72: Expansion Interface Packet Interface Test, PN-to-PN loop Packet Bus (PN X) Packet Bus (PPN) EXP-INTF EXP-INTF PKT- CSS INT (optional) In a Center Stage configuration the path shown in Figure 72: Expansion Interface Packet Interface Test, PN-to-PN loop on page 1223 is used when testing a PN EI that is on the standby PNC. In a Direct Connect configuration, this path is used on any PN EI or on a PN EI that is on the standby PNC.
PAGE 1224
Communication Manager Maintenance-Object Repair Procedures Figure 74: Expansion Interface Packet Interface Test, PN-to-PN link Packet Bus ( PPN ) PKT INT EXP-INTF EXP-INTF Packet Bus ( PN X ) EXP-INTF EXP-INTF Packet Bus ( PN Y ) EXP-INTF EXP-INTF The path shown in Figure 74 is used when the EI under test is one that provides connectivity between the two PNs in a Direct Connect configuration. 1224 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1225
EXP-INTF (Expansion Interface Circuit Pack) Table 416: Test #589 Expansion Interface Packet Interface Test Error Code Test Result Description / Recommendation 1033 ABRT The test cannot run because the EI circuit pack does not have a fiber link administered to it and there is not sufficient data to run the test or because EI circuit packs on other port networks needed for this test are out of service. 1.
PAGE 1226
Communication Manager Maintenance-Object Repair Procedures Table 416: Test #589 Expansion Interface Packet Interface Test (continued) Error Code Test Result Description / Recommendation 1033 ABRT (cont’d) (cont’d) Center Stage: If the EI circuit pack under test resides in the PN: None of the EI circuit packs located in the PNs (on the same PNC side) are in service (for PN EIs see the next case). 5.
PAGE 1227
EXP-INTF (Expansion Interface Circuit Pack) Table 416: Test #589 Expansion Interface Packet Interface Test (continued) Error Code Test Result Description / Recommendation 1139 ABRT The packet bus in the PN where this EI circuit pack resides has a major alarm against it. This test needs to use the alarmed port network’s packet bus. 1. Enter display alarms and resolve any PKT-BUS alarms. 2. Retry the command. 1141 ABRT The Packet Interface circuit pack is out of service. 1.
PAGE 1228
Communication Manager Maintenance-Object Repair Procedures Table 416: Test #589 Expansion Interface Packet Interface Test (continued) Error Code Test Result Description / Recommendation 1421 ABRT This abort code appears only when the EI circuit pack addressed in the test command is one that terminates a fiber link between two PNs in a direct connect system.
PAGE 1229
EXP-INTF (Expansion Interface Circuit Pack) Table 416: Test #589 Expansion Interface Packet Interface Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 2500 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 3 times. ANY FAIL The transmitted data packet was not received correctly by the Packet Interface circuit pack.
PAGE 1230
Communication Manager Maintenance-Object Repair Procedures Expansion Interface Test (#244) This test is potentially very destructive and requires the EI circuit pack to be busied out prior to execution of this test. The Expansion Interface test, which is not a part of either the short or long test sequences, is executed via reset board PCSS where PCSS is the location of the EI circuit pack to be reset.
PAGE 1231
EXP-INTF (Expansion Interface Circuit Pack) Table 417: Test #224 Expansion Interface Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. 1. Rerun the test at 1-minute intervals up to 3 times. 2100 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 3 times. 9999 ABRT EI circuit pack reset successfully.
PAGE 1232
Communication Manager Maintenance-Object Repair Procedures Table 417: Test #224 Expansion Interface Test (continued) Error Code Test Result Description / Recommendation 2 FAIL The EI circuit pack was successfully reset, but it did not begin running after the reset. 1. If the EI circuit pack is in the PN, temporarily remove the PN’s Maintenance circuit pack. 2. Repeat reset board PCSS. 3. Re-insert the PN’s Maintenance circuit pack if it was removed. 3 FAIL The reset over the optical fiber failed.
PAGE 1233
EXP-INTF (Expansion Interface Circuit Pack) Table 417: Test #224 Expansion Interface Test (continued) Error Code Test Result Description / Recommendation 5001 FAIL Initialization failure: the EI circuit pack reset successfully and restarted execution, but the EI circuit pack could not synchronize itself during hardware initialization. 1. Enter reset board PCSS. If the circuit pack is in the active link, this procedure can be very destructive.
PAGE 1234
Communication Manager Maintenance-Object Repair Procedures Table 417: Test #224 Expansion Interface Test (continued) Error Code Test Result Description / Recommendation 5016 5017 5018 5019 5032 5033 5048 5064 5080 5096 5112 FAIL Initialization failure: the EI circuit pack reset successfully and restarted execution, but the EI circuit pack detected communication errors during hardware initialization.
PAGE 1235
EXP-PN (Expansion Port Network) EXP-PN (Expansion Port Network) S8700 MC MO Name in Alarm Log Alarm Level Initial SAT Command to Run1 Full Name of MO EXP-PN MAJ display errors1 Expansion Port Network 1. Investigate errors against EXP-PN and EXP-INTF. The EXP-PN MO is responsible for overall maintenance of an Expansion Port Network (EPN) and monitors cross-cabinet administration for compatible companding across the circuit-switched connection.
PAGE 1236
Communication Manager Maintenance-Object Repair Procedures If the Expansion Archangel Link (EAL) is recovered quickly, the PN Warm Restart returns the PN to service with minimal effects on user service. If the EAL cannot be recovered quickly, the PN is taken out of service and a PN Reset Level 2 (PN Cold Restart) is required to return it to service.
PAGE 1237
EXP-PN (Expansion Port Network) Error Log Entries and Test to Clear Values Table 418: Expansion Port Network (EXP-PN) Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board 1 (a) 0 None None 257 (b) 0 None None 513 (c) 0 None MAJ OFF 769 (d) 0 None MAJ OFF 1025 (e) Any None MAJ OFF Test to Clear Value Notes: a. Error Type 1: informational entry only, indicating that a PN Reset Level 1 (PN Warm Restart) has been executed on this PN. b.
PAGE 1238
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions And Error Codes EXP-PN does not support demand testing. A demand reset can be executed to perform a demand reset on a PN by using reset port-network P level 1 or 2 (P is the port network’s number, and 1 or 2 specifies the reset level). PN Cold Restart (#955) PN Cold Restart, or PN Reset Level 2, reset port-network P level 2 is used as a recovery mechanism for a PN that has been taken out of service.
PAGE 1239
EXP-PN (Expansion Port Network) PN Warm Restart (#956) The PN Warm Restart, or PN Reset Level 1, reset port-network P level 1 is used to restart a PN that has not been taken out of service. It is the least severe of the PN restart levels and is used in an attempt to preserve the state of the system as much as possible, thereby reducing user impact. This restart is attempted on a PN if it is still in service, or as a result of a system technician-demanded PN Warm Restart.
PAGE 1240
Communication Manager Maintenance-Object Repair Procedures EXT-DEV (External device alarm) G650 MO name in alarm Log Alarm level Initial SAT command to run Full name of MO EXT-DEV MIN test environment location External Device Alarm EXT-DEV MAJ test environment location External Device Alarm EXT-DEV MIN test eda-external-device-alm location External Device Alarm EXT-DEV MAJ test eda-external-device-alm location External Device Alarm A TN2312BP IPSI, in a G650 with a carrier address set t
PAGE 1241
EXT-DEV (External device alarm) System technician-demanded test: Descriptions and error codes Order of investigation Short test sequence Long test sequence D/ND Alarm query test (#120) X X Nondestructive Alarm query test (#120) The external device alarm test requests the status of the external device alarm from a maintenance circuit pack and reports the results. The test has no affect on the external device itself.
PAGE 1242
Communication Manager Maintenance-Object Repair Procedures Table 423: Test #120 Alarm query (continued) Error code Test result Description and Recommendation ANY FAIL The external device alarm has been activated by the external device. 1. Clear the major alarm on the external device and repeat the test. 2. If the test fails, disconnect the external device alarm leads from the TN2312BP IPSI circuit pack and repeat the test. 3.
PAGE 1243
EXT-DEV ADMIN? N (External Device Alarm) EXT-DEV ADMIN? N (External Device Alarm) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run1 Full Name of MO EXT-DEV MAJ test environment UU External Device Alarm EXT-DEV MIN test environment UU External Device Alarm 1. Where UU is the cabinet number in the PORT field from the Alarm or Error Log.
PAGE 1244
Communication Manager Maintenance-Object Repair Procedures 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 Cabinet Query Test, you may also clear errors generated from other tests in the testing sequence.
PAGE 1245
EXT-DEV ADMIN? N (External Device Alarm) External Device Alarm Test (#120) The External Device Alarm Test requests the state of the External Device Alarm from the Maintenance circuit pack and reports the results. The test has no effect on the external device itself. Table 426: TEST #120 External Device Alarm Test Error Code Test Result Description/ Recommendation 1000 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times.
PAGE 1246
Communication Manager Maintenance-Object Repair Procedures EXT-DEV ADMIN? Y (External Device Alarm) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run 1 Full Name of MO EXT-DEV MAJ test eda-external-device-alrm UU External Device Alarm EXT-DEV MIN test eda-external-device-alrm UU External Device Alarm EXT-DEV WRN test eda-external-device-alrm UU External Device Alarm 1. UU is a cabinet number determined in the Port field of the Alarm or Error Log.
PAGE 1247
EXT-DEV ADMIN? Y (External Device Alarm) Error Log Entries and Test to Clear Values Note: Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 0 Any Any Any test eda-external-device-alrm physical-location r 2 | 6 1 or 5 Any External Device Alarm test (#120) Any OFF test eda-external-device-alrm physical-location r 2 | 6 Note: The loss of -48 volt power prevents detection of an external device alarm.
PAGE 1248
Communication Manager Maintenance-Object Repair Procedures External Device Alarm Test (#120) The External Device Alarm Test requests the state of the External Device Alarm from a Maintenance circuit pack and reports the results. The test has no effect on the external device itself. Table 427: Test #120 External Device Alarm Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. 1.
PAGE 1249
EXT-DEV ADMIN? Y (External Device Alarm) Table 427: Test #120 External Device Alarm Test (continued) Error Code Test Result Description / Recommendation Any FAIL The External Device Alarm has been activated by the external device. 1. Clear the major alarm on the external device, and rerun the test. 2. If the test still fails, then disconnect the External Device Alarm Leads from the Maintenance circuit pack and rerun the test. 3.
PAGE 1250
Communication Manager Maintenance-Object Repair Procedures FIBER-LK (Fiber Link) MO Name in Alarm Log Alarm Level Initial Command to Run1 Full Name of MO FIBER-LK MAJ test fiber-link F pnc s Fiber Link FIBER-LK MIN test fiber-link F pnc s Fiber Link FIBER-LK WRN test fiber-link F pnc s Fiber Link 1. F is the fiber link number; pnc is either “a-pnc” or “b-pnc” (always “a-pnc” for a standard-, high-, or critical-reliability system).
PAGE 1251
FIBER-LK (Fiber Link) The following terms are used in the error descriptions: Control Path The path between the two fiber endpoints that is necessary for the two endpoint circuit packs to communicate. Circuit Path The path between the two fiber endpoints that is necessary for circuit switched phone calls to work. Neighbor The circuit pack on the other end of the fiber. Out of Frame A circuit pack reports fiber out of frame if it cannot detect valid data coming from the fiber.
PAGE 1252
Communication Manager Maintenance-Object Repair Procedures Table 429: Expansion Interface Circuit Pack Amber LED Flashing Codes Condition LED on LED off Fiber Out-of-Frame 0.1 second 0.1 second In frame-No Neighbor (a) 0.5 second 0.5 second Expansion Interface Active (b) 2 second 0.2 second Expansion Interface Active (c) Solid on Never off Expansion Interface Standby (d) Never on Solid off Notes: a. The fiber is in frame, but no communication exists to the neighbor. b.
PAGE 1253
FIBER-LK (Fiber Link) d. The media server is not acknowledging messages from the DS1 converter circuit pack or the DS1 converter circuit pack does not have a processor route. This pattern indicates a probable software problem. In addition to the traditional red, green, and amber LEDs, the DS1 converter circuit pack has four green LEDs that indicate whether a receive signal is present for each DS1 facility.
PAGE 1254
Communication Manager Maintenance-Object Repair Procedures c. Error Type 18: indicates that the fiber link has been busied out via busyout fiber-link F P. To resolve this error, use release fiber-link F P to release the fiber link. d. Error Type 257: indicates problem with the circuit path to the neighbor. See Repair procedures. e. Error Type 513: indicates problem with the packet path to the neighbor. See Repair procedures. f. Error Type 769: indicates problem with the control path from the neighbor.
PAGE 1255
FIBER-LK (Fiber Link) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the following order when inspecting errors in the system. For example, by clearing error codes associated with the EI Out-of-Frame Query test (#238), you may also clear errors generated by other tests later in the sequence.
PAGE 1256
Communication Manager Maintenance-Object Repair Procedures Table 435: Tests Run for an SNI-to-SNI Fiber Link Order of Investigation Long Test Sequence Configuration audit (#759) X X ND Failure audit (#777) X X ND Fiber Out of Frame query (#989) X X ND Destructive Facility test (#757) X D Off-Board Destructive Facility test (#756) X D Fiber Link Reset test (#768) Reset Fiber Sequence D/ND1 Short Test Sequence X D 1.
PAGE 1257
FIBER-LK (Fiber Link) Table 436: Test #237 Expansion Interface Neighbor Query Test (continued) Error Code Test Result Description / Recommendation 2031 ABRT The attempt to send the message to the EI circuit pack, asking it who it’s neighbor is, was not successful. 1. Run test board location separately for each EI endpoint on this fiber link, and follow the procedures for this test in EXP-INTF (Expansion Interface Circuit Pack) on page 1176.
PAGE 1258
Communication Manager Maintenance-Object Repair Procedures Expansion Interface Fiber Out-of-Frame (FOOF) Query Test (#238) This test is nondestructive. This test is a request to an EI circuit pack to determine whether it is currently detecting the framing sequence on the incoming fiber’s data stream. If it cannot detect this framing signal, the EI circuit pack will not be able to establish a link with the opposite EI or SNI circuit pack.
PAGE 1259
FIBER-LK (Fiber Link) Table 437: Test #238 Expansion Interface Fiber Out-of-Frame Query Test (continued) Error Code Test Result Description / Recommendation FAIL EI circuit pack can’t frame up to incoming signal. Several fail codes may be returned depending on which endpoint can’t frame up. Error codes 2326, 2327, and 2328 denote Endpoint 1, Endpoint 2, and both endpoints, respectively. 1. Clear any SYNC and TDM-CLK errors listed in the error log. 2.
PAGE 1260
Communication Manager Maintenance-Object Repair Procedures Table 438: Test #756 SNI Off-Board Destructive Facility Test Error Code Test Result Description / Recommendation 1015 ABRT The system will not allow this test to be run because the fiber link has not been busied out. Busyout the fiber link with busyout fiber-link F P. Run test fiber-link F P long. 1415 ABRT The lightwave transceiver is absent from Endpoint 1 of the fiber link. Use list fiber-link to display fiber link endpoints. 1.
PAGE 1261
FIBER-LK (Fiber Link) Table 438: Test #756 SNI Off-Board Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1262
Communication Manager Maintenance-Object Repair Procedures Table 438: Test #756 SNI Off-Board Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 127 FAIL The data is not correctly looped around on Endpoint 1 of the fiber link. Use list fiber-link to display fiber link endpoints. 1. Check the lightwave transceiver. 2. Replace the lightwave transceiver.
PAGE 1263
FIBER-LK (Fiber Link) Table 439: Test #757 SNI Destructive Facility Test Error Code Test Result Description / Recommendation 1015 ABRT The system will not allow this test to be run because the fiber link has not been busied out. 1. Busyout the fiber link with busyout fiber-link F P. 2. Enter test fiber-link F P long. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1264
Communication Manager Maintenance-Object Repair Procedures Table 439: Test #757 SNI Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 127 FAIL The data is not correctly looped around on Endpoint 1 of the fiber link. Use list fiber-link to display fiber link endpoints. 1. Replace the SNI circuit pack. 227 FAIL The data is not correctly looped around on Endpoint 2 of the fiber link. Use list fiber-link to display fiber link endpoints. 1.
PAGE 1265
FIBER-LK (Fiber Link) 2. Run test led switch-node for each administered switch node carrier (SNC), and verify that the LEDs on the correct SNC are lit. If not, check the connectivity to the SNC that does not light the LEDs as expected. Table 440: Test #759 Configuration Audit Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test for endpoint 1 of the fiber link. 1. Use list fiber-link to display a fiber link’s endpoints. 2.
PAGE 1266
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 2306 ABRT An SNI circuit pack on the fiber link is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node(s) where the SNI(s) reside to verify whether the LEDs on the board(s) light. Follow the steps below for the SNI(s) that had no LEDs light. 2.
PAGE 1267
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 103 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 3. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1268
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 105 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 5. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1269
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 107 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 7. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1270
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 109 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 9. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1271
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 114 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 14. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1272
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 116 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 16. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1273
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 118 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 18. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1274
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 120 FAIL The SNI circuit pack (Endpoint 1) cannot communicate with the equipped SNI in slot 20. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1275
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 137 FAIL The Endpoint 1 SNI’s administered neighbor does not match the physical neighbor connected. Use list fiber-link to see a fiber link’s endpoints. The SNI’s assigned neighbor is an EI, but the SNI is physically connected to another SNI. Enter list fiber-link and verify that the fiber-optic and metallic cables are installed as administered.
PAGE 1276
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 140 FAIL The Endpoint 1 SNI is physically connected to a DS1 converter but is not administered to be connected to a DS1 converter. Use list fiber-link to see a fiber link’s endpoints. Either add the DS1 converter complex to the fiber that this SNI is associated with: 1.
PAGE 1277
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 203 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 3. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1278
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 205 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 5. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1279
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 207 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 7. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1280
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 209 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 9. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1281
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 214 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 14. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1282
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 216 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 16. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1283
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 218 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 18. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1284
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 220 FAIL The SNI circuit pack (Endpoint 2) cannot communicate with the equipped SNI in slot 20. Use list fiber-link to see a fiber link’s endpoints. 1. Perform the Fiber link fault isolation in Chapter 4: General troubleshooting in Maintenance Procedures (03-300192). This should resolve multiple SNI-PEER errors. 2.
PAGE 1285
FIBER-LK (Fiber Link) Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 236 FAIL The Endpoint 2 SNI’s administered neighbor does not match the physical neighbor connected. Use list fiber-link to see a fiber link’s endpoints. The SNI’s assigned neighbor is another SNI, but the SNI is physically connected to an EI. Enter list fiber-link and verify that the fiber-optic and metallic cables are installed as administered.
PAGE 1286
Communication Manager Maintenance-Object Repair Procedures Table 440: Test #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 240 FAIL The SNI Endpoint 2 is physically connected to a DS1 converter, but is not assigned to be connected to one. Use list fiber-link to display a fiber link’s endpoints. Either replace the DS1 converter with fiber: 1. Enter list fiber-link to verify that the fiber-optic and metallic cable connections are installed as assigned 2.
PAGE 1287
FIBER-LK (Fiber Link) When an EI endpoint is reset, the Expansion Interface Reset test (#336) is executed. When an SNI endpoint is reset, the SNI Reset test (#761) is executed. These tests are described in the EXP-INTF and SNI-BD sections. This test starts the other reset test mentioned above and returns PASS without waiting for the results of the other reset test. For a better indication of how the other reset tests are running, use reset board location on each individual fiber link endpoint.
PAGE 1288
Communication Manager Maintenance-Object Repair Procedures For EI-to-EI fiber links, this test is not run. For EI-to-SNI fiber links, this test is run on the SNI circuit pack endpoint of the fiber link. For SNI-to-SNI fiber links, this test is run on both SNI circuit pack endpoints of the fiber link. Table 442: Test #777 Failure Audit Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test.
PAGE 1289
FIBER-LK (Fiber Link) Table 442: Test #777 Failure Audit (continued) Error Code Test Result Description / Recommendation FAIL The SNI circuit pack reported failures or retransmitted a cleared failure message. 1. If this is the first time this test was run, run the test again. If there were any previous failure messages that software did not acknowledge, this test will FAIL even if the failure messages indicate a FAIL to PASS transition, i.e., a problem has gone away.
PAGE 1290
Communication Manager Maintenance-Object Repair Procedures Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 1416 ABRT The lightwave transceiver is absent from Endpoint 2 of the fiber link. Use list fiber-link to display fiber link endpoints. 1. If a lightwave transceiver should not be present (for example, an SNI connected to a DS1 converter circuit pack), do nothing. 2. Otherwise, continue with the following steps. 3.
PAGE 1291
FIBER-LK (Fiber Link) Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 2306 ABRT A fiber link’s SNI circuit pack is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node where the SNI board(s) reside to verify whether their LEDs light. If not, continue with the following steps. 2.
PAGE 1292
Communication Manager Maintenance-Object Repair Procedures Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 142 FAIL The SNI circuit pack (Endpoint 1 of the fiber link) has a fiber out-of-frame condition, but no loss-of-signal condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1293
FIBER-LK (Fiber Link) Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 144 FAIL The SNI circuit pack (Endpoint 1 of the fiber link) has a loss-of-signal condition, but no fiber out-of-frame condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1294
Communication Manager Maintenance-Object Repair Procedures Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 146 FAIL The SNI circuit pack (Endpoint 1 of the fiber link) has a fiber out-of-frame condition, and a loss-of-signal condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1295
FIBER-LK (Fiber Link) Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 242 FAIL The SNI circuit pack (Endpoint 2 of the fiber link) has a fiber out-of-frame condition, but no loss-of-signal condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1296
Communication Manager Maintenance-Object Repair Procedures Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 244 FAIL The SNI circuit pack (Endpoint 2 of the fiber link) has a loss-of-signal condition, but no fiber out-of-frame condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1297
FIBER-LK (Fiber Link) Table 443: Test #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 246 FAIL The SNI circuit pack (Endpoint 2 of the fiber link) has a fiber out-of-frame condition, and a loss-of-signal condition. Also, no lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 1298
Communication Manager Maintenance-Object Repair Procedures FW-DWNLD (Firmware Download) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Full Name of MO FW-DWNLD MINOR1 Firmware Download 1. MINOR alarms can be down-graded to a WARNING level per local instructions by using the set options command. Firmware Download provides the capability to download new firmware to one or more programmable circuit packs of the same type residing within the same system.
PAGE 1299
FW-DWNLD (Firmware Download) Notes: a. Error Type 257 — A log-only error indicating that a certain software resource was not available. Such an error very seldom occurs and usually produces a proc_err. However, in the firmware download feature, the file cannot be downloaded and/or the schedule can also abort/fail. To resolve the error, use the test firmware download command. The Aux Data specifies the unavailable resource that caused the error. See Table 445 for more details.
PAGE 1300
Communication Manager Maintenance-Object Repair Procedures b. Error Type 258 — A log-only error indicating that a source board-related error occurred. The download schedule can also abort/fail. To resolve the error, use the command test firmware download. The Aux Data specifies the error. See Table 446 for more details. Table 446: Aux Data for Error Type 258 Aux Data Description of Failure 1 Download image file specified on the change firmware download screen not present on the source board. 1.
PAGE 1301
FW-DWNLD (Firmware Download) c. Error Type 259 — A log-only error indicating that the target board failed to download. To resolve the error, use the command test firmware download. The Aux Data specifies the error. See Table 447 for more details. Table 447: Aux Data for Error Type 259 Aux Data Description of Failure 1 Target board is not present / responding. 1. Check board’s location and translations, and retry download. 2 Incorrect target board for download schedule. 1.
PAGE 1302
Communication Manager Maintenance-Object Repair Procedures Table 447: Aux Data for Error Type 259 (continued) Aux Data Description of Failure 21 Problem reading the requested file – Internal firmware error on target board. 1. Retry the download, and escalate if it still fails. 22 The download file has a bad CRC – Internal firmware error on target board. 1. Retry the download, and escalate if it still fails. 24 A download is already in progress – Internal firmware error on target board. 1.
PAGE 1303
FW-DWNLD (Firmware Download) Table 448: Error Type 513 Aux Data (continued) Aux Data Description of Failure 2 Source board-related failure; see Error Type 258 (b). 3 A target board failed; see Error Type 259 (c). 1. Check image, translations and retry. 4 Two consecutive target boards failed, download schedule aborted. 1. Verify download image, translations, and retry. 5 Schedule timer expired 1. Schedule unfinished target boards, and retry. 6 disable firmware download command executed.
PAGE 1304
Communication Manager Maintenance-Object Repair Procedures Table 449: Converting an angel number into carrier and slot (continued) Carrier A Slot # B C D E Angel Number 7 58 72 104 40 08 8 59 73 105 41 09 9 60 74 106 42 10 10 61 75 107 43 11 11 62 76 108 44 12 12 63 77 109 45 13 13 88 78 110 46 14 14 89 79 111 47 15 15 90 80 112 48 16 16 91 81 113 49 17 17 92 82 114 50 18 18 93 83 115 51 19 19 94 84 116 52 20 20 95 85 11
PAGE 1305
FW-DWNLD (Firmware Download) Test Firmware Download (#1413) This test is destructive. This test has two functions and can only be executed if there is a download schedule to verify or there are FW-DWNLD errors to resolve and alarms to clear. 1. This test verifies that the information on the FIRMWARE DOWNLOAD screen is correct. It also verifies that the source board is of the correct type, that the file to be downloaded is present on that source board, and that the file is error free.
PAGE 1306
Communication Manager Maintenance-Object Repair Procedures Table 450: TEST #1413 Firmware Download Test (continued) Error Code Test Result Description / Recommendation 2 FAIL The image file header on the source board is invalid. 1. FTP a good firmware image file to the source board. 3 FAIL Firmware image file on the source board has a bad CRC. 1. FTP a good firmware image file to the source board. 4 FAIL Firmware image file name is too long. 1.
PAGE 1307
FW-DWNLD (Firmware Download) Table 450: TEST #1413 Firmware Download Test (continued) Error Code Test Result Description / Recommendation 7 FAIL The source board entered on the screen is not present. 1. Execute the display firmware download command, and verify the source board’s location. 2. Verify the source board’s translations. 3. If the location is incorrect, execute the change firmware download command, and enter the correct location on the screen.
PAGE 1308
Communication Manager Maintenance-Object Repair Procedures GPTD-PT (General-Purpose Tone Detector Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO GPTD-PT MAJ test port location sh General-Purpose Tone Detector Port GPTD-PT MIN test port location sh General-Purpose Tone Detector Port GPTD-PT WRN release port location General-Purpose Tone Detector Port The GPTD (General-Purpose Tone Detector) ports, also known as CPTRs (Call-Progress Ton
PAGE 1309
GPTD-PT (General-Purpose Tone Detector Port) Table 451: General-Purpose Tone Detector Port (CPTR) Error Log Entries (continued) Error Type Aux Data 130 (e) Associated Test Alarm Level On/Off Board Test to Clear Value None WRN ON test port location sh r 2 257 (c) 17666 Tone Detector Audit/ Update (#43) MAJ MIN (a) ON test port location r 3 513 (d) Any Tone Detection Verification (#42) MAJ MIN (a) ON test port location r 3 2 of 2 Notes: a.
PAGE 1310
Communication Manager Maintenance-Object Repair Procedures Tone Detection Verification Test (#42) This test verifies that the call-progress tone-detection and the tone-level measurement capabilities of the GPTD port are functioning properly. Table 452: Test #42 Tone Detection Verification Test Error Code Test Result Description / Recommendation ABRT The system was not able to allocate every resource needed for this test, or there was an Internal system error.
PAGE 1311
GPTD-PT (General-Purpose Tone Detector Port) Table 452: Test #42 Tone Detection Verification Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 101– 122 FAIL FAIL 1. Run the short test sequence: test port location sh r 1. 2. If the problem persists, the system is still operating properly but system capacity will be reduced.
PAGE 1312
Communication Manager Maintenance-Object Repair Procedures Tone Detector Audit/Update Test (#43) The GPTD port is refreshed with all time-slot information, and a sanity audit is performed on the GPTD port. Table 453: Test #43 Tone Detector Audit/Update Test Error Code Test Result Description / Recommendation ABRT The system was not able to allocate the resources needed for this test. 1. Wait 1 minute and try again.
PAGE 1313
H323-BCH (H.323 B Channel) H323-BCH (H.323 B Channel) S8700 | 8710 / S8500 / S8300 No maintenance diagnostic tests exist for this object. H.323 signaling is similar to ISDN Q.931 signaling. In order to take advantage of existing ISDN Avaya™ Communication Manager, H.323 trunk AvayaCommunication Manager software includes H.323 signaling groups, H.323 D channels and H.323 B channels. H.323 signaling groups are similar in concept to ISDN PRI signaling groups. H.
PAGE 1314
Communication Manager Maintenance-Object Repair Procedures System Technician Commands The following commands are available to the system technician: ● busyout port location: on a specific H.323 B channel, drops any active call on that B channel and reduces the trunk group’s capacity by one. No physical piece of hardware is removed from service. ● release port location: on a specific H.323 B channel, increases the trunk group’s capacity by one. No physical piece of hardware is actually added to service.
PAGE 1315
H323-SGRP (H.323 Signaling Group) H323-SGRP (H.323 Signaling Group) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm level Initial SAT Command to Run Full Name of MO H323-SGR MIN test signaling-group grp# H323 Signaling Group H323-SGR WRN test signaling-group grp# H323 Signaling Group The H.323 Signaling Group (H323-SGRP) MO supports a signaling channel (D channel) for H.323 Trunk connections.
PAGE 1316
Communication Manager Maintenance-Object Repair Procedures Table 455: H323-SGRP Signaling Group Error Log Entries (continued) Error Type Aux Data 2305 (l) 2561(m) Any Associated Test Alarm Level On/Off Board Gateway Unregistered Inline Error MIN OFF Registered to LSP Inline Error MIN OFF Test to Clear Value 2 of 2 Notes: a. Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence.
PAGE 1317
H323-SGRP (H.323 Signaling Group) i. Error Type 1537: Indicates that the far end of the signaling group is not ready to handle audio bearer. If the other end of this signaling group is also a Communication Manager server, this error means the server on the other end does not have MEDPRO in-service for its signaling group. This error places the H323 B Channels into an out-of-service far-end state. j.
PAGE 1318
Communication Manager Maintenance-Object Repair Procedures CLAN Ethernet Status Test (#1386) This test is nondestructive. This test checks the status of the C-LAN Ethernet port that is the near end gatekeeper this signaling group. If the C-LAN Ethernet port is in service, the test passes; if it is OOS (out of service), the test fails. Note: Note: Failure of this test will put the SIG-GRP in the OOS state.
PAGE 1319
H323-SGRP (H.323 Signaling Group) Table 456: Test #1386 CLAN Ethernet Status Test (continued) Error Code Test Result Description / Recommendation PASS The C-LAN Ethernet port corresponding to the near-end address of the SIG-GRP that is in service has passed this test. Every session on the Ethernet link is up. 2 of 2 H.323 Signaling Group Ping Test (#1387) This test is nondestructive. This test is only run for those signaling groups that have an administered far-end IP address. If the H.
PAGE 1320
Communication Manager Maintenance-Object Repair Procedures Table 457: Test #1387 H.323 Signaling Group Ping Test (continued) Error Code Test Result Description / Recommendation 7 ABRT Destination unreachable. 1. Verify that the C-LAN has been administered with an IP-Route that enables the C-LAN to reach the far-end IP address. 2. Once verified, use test sig-group grp# to verify that the H.323 Signaling Group Ping test (#1387) passes. 1005 ABRT Configuration for this test is incorrect. 1.
PAGE 1321
H323-SGRP (H.323 Signaling Group) Table 457: Test #1387 H.323 Signaling Group Ping Test (continued) Error Code Test Result Description / Recommendation 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3times. 2800 ABRT No C-LAN in the same region. 1. Verify translations and retest. 2801 ABRT No IP address defined. 1. Verify translations and retest. 2802 ABRT Different IP address pinged than software had allocated for the test. 1.
PAGE 1322
Communication Manager Maintenance-Object Repair Procedures MedPro Status Test (#1392) This test is nondestructive. This test determines if at least one media processor port exists that is in service, and that serves the same region as the C-LAN that the signaling group uses. If at least one exists and is in service, the test passes; otherwise, the test fails.
PAGE 1323
H323-STN (H.323 IP Station) H323-STN (H.323 IP Station) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO H323-STN WRN test station extension H.323 IP Station H323-STN covers implementation of the maintenance for native mode H.323 endpoints. Native mode H.323 applications such as Netmeeting or Proshare provide only what is needed to support the H.323 standard. Communication Manager can invoke very little in the maintenance area.
PAGE 1324
Communication Manager Maintenance-Object Repair Procedures b. Error Type 257 tracks failures of the signaling path PING test. The test attempts to send a PING packet to the endpoint IP address, as reported during registration. The PING packet originates with the C-LAN board through which the endpoint is registered. If the PING response packet is received, the test passes. If the ping response packet times out, the test fails. c. Error Type 513 tracks failures with the media path ping test.
PAGE 1325
H323-STN (H.323 IP Station) A registered extension has a port type SNNNNN, where N is a digit from 0–9. A non-registered extension has an X port. Table 460: Test #1372 Registration Status Inquiry Error Code Test Result Description / Recommendation 1, 2, 3 FAIL The endpoint is not successfully registered. 1. Verify that the user is entering the: ● correct extension and security code ● C-LAN IP address 2. Verify that the extension has been enabled for IP Softphones operation. 3.
PAGE 1326
Communication Manager Maintenance-Object Repair Procedures This nondestructive test runs due to in-line errors, during periodic and schedule maintenance, and on demand. Table 461: Test #1373 Signaling Path PING Test Error Code Test Result Description / Recommendation S8300 G700 ABRT This test does not execute on a G700 media gateway. 2100 ABRT Could not locate the necessary system resources to run this test. 1412 1. Retry the command at 1-minute intervals, up to 5 times. 2.
PAGE 1327
H323-STN (H.323 IP Station) Media Path PING Test (#1374) This test is nondestructive. The test selects a Media Processor board. It then requests the local Media Processor to execute a PING on the endpoint address. If the PING is successful, the test passes. If the PING is not successful, the test fails. Services can execute the standard ping command using the Media Processor board address and endpoint IP address to see the actual round-trip delay.
PAGE 1328
Communication Manager Maintenance-Object Repair Procedures HYB-BD (Hybrid Line Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO HYB-BD MIN test board location sh Hybrid Line circuit pack HYB-BD WRN test board location sh Hybrid Line circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors. See also HYB-LINE (Hybrid Line) on page 1329 for related line information.
PAGE 1329
HYB-LINE (Hybrid Line) HYB-LINE (Hybrid Line) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO HYB-LINE MIN test port location l Hybrid Line HYB-LINE WRN test port location l Hybrid Line Hybrid Line is another term for the MFAT (Multi-Function Analog Telephone). The Hybrid Line set is also known as an SCS (Small Communications System). The TN762B Hybrid Line circuit pack supports eight of these multifunction analog telephone sets.
PAGE 1330
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 463: Hybrid Line Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test port location sh r 1 1 (a) 40987 None WRN OFF 15 (j) Any Hybrid Line Audits test (#161) 18 (b) 0 busyout port location WRN OFF release port location None WRN ON test port location sh 130 (c) 257 (d) 40988 None MIN WRN OFF 513 (e)
PAGE 1331
HYB-LINE (Hybrid Line) Notes: a. Error Type 1: The data link between the port and the terminal is not operational. (An off-board problem was detected by port circuit). Verify that the Hybrid set is connected and that the Electronic Power Feed (EPF) test passes. If data transmission problems are experienced, check for defective wiring or a defective voice terminal, or move terminal closer to the switch (reduce the length of the wiring between the terminal and the switch).
PAGE 1332
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the Local Digital Looparound test (#58), you may also clear errors generated from other tests in the sequence.
PAGE 1333
HYB-LINE (Hybrid Line) Table 465: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension number of the port. Use status station to determine the service state of the port. If the port is in use, wait until it is idle before testing. 2.
PAGE 1334
Communication Manager Maintenance-Object Repair Procedures Table 465: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test disabled by 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 for this station. 1. To enable test, set the Test field on the station administration screen for the particular analog station being tested to y.
PAGE 1335
HYB-LINE (Hybrid Line) Table 465: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config, and resolve any problems that are found. 2.
PAGE 1336
Communication Manager Maintenance-Object Repair Procedures Table 466: Test #56 Hybrid Electronic Power Feed Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension number of the port. Use status station to determine the service state of the port. If the port is in use, wait until it is idle before testing. 2.
PAGE 1337
HYB-LINE (Hybrid Line) Table 466: Test #56 Hybrid Electronic Power Feed Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Enter list config, and resolve any problems that are found. 2.
PAGE 1338
Communication Manager Maintenance-Object Repair Procedures Table 467: Test #57 Hybrid Circuit and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension number of the port. Use status station to determine the service state of the port. If the port is in use, wait until it is idle before testing.
PAGE 1339
HYB-LINE (Hybrid Line) Table 467: Test #57 Hybrid Circuit and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1392 ABRT 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 display port (the port is a TTI port) or list config (the display shows a t for the port). 2. If list config or display port indicate that the port is not a TTI port, escalate the problem.
PAGE 1340
Communication Manager Maintenance-Object Repair Procedures Table 467: Test #57 Hybrid Circuit and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 57 FAIL Hybrid Circuit test failed. This could result in noisy or bad connections. 1. This error can be caused by a disconnected terminal. First, ensure that the terminal is connected and the wiring is OK. 2.
PAGE 1341
HYB-LINE (Hybrid Line) Hybrid Line Local Digital Loop-Around Test (#58) This test checks the control channel between the media server and the port’s digital circuitry. The media server sends transparent data to the on-board microprocessor and compares the data echoed back. This test is repeated three times. Table 468: Test #58 Hybrid Line Local Digital Loop-Around Test Error Code Test Result Description / Recommendation ABRT Internal system error. 1.
PAGE 1342
Communication Manager Maintenance-Object Repair Procedures Table 468: Test #58 Hybrid Line Local Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1, 2, 3 FAIL The control channel between the processor and the port is not transmitting properly. This port is not operable. 1. Retry the test. 2. If the failure still occurs, enter busyout location and release location, and then retest. 3.
PAGE 1343
HYB-LINE (Hybrid Line) Hybrid Line Remote Digital Looparound Test (#59) This test checks the digital control pair from the port circuit to the terminal. The on-board microprocessor sends a message to the terminal and checks for a proper return message. This test is repeated three times, with two out of the three attempts passing being sufficient for this test to pass. This test will run if the station is in service or out of service.
PAGE 1344
Communication Manager Maintenance-Object Repair Procedures Table 469: Test #59 Hybrid Line Remote Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1, 2, 3 FAIL No response was received within the allowable time period on one of the transmissions to the terminal. This indicates a problem with the data link to the voice terminal. This could be a sleeping set problem or it may be due to wiring or an unplugged or defective set. 1.
PAGE 1345
HYB-LINE (Hybrid Line) Hybrid Line 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 will run only if the station is in service. Table 470: Test #60 Hybrid Line Lamp Updates Test Error Code Test Result Description / Recommendation 1 ABRT A request for a remote station lamp update aborted even though every internal resource was correctly allocated. 1.
PAGE 1346
Communication Manager Maintenance-Object Repair Procedures Table 470: Test #60 Hybrid Line Lamp Updates Test (continued) Error Code Test Result Description / Recommendation FAIL Internal system error 1. Retry the command at 1-minute intervals up to 5 times. PASS Hybrid Line Lamp Updates completed successfully 1. If complaints still exist, investigate by using other circuit pack tests, and by examining the station, wiring, and connections.
PAGE 1347
HYB-LINE (Hybrid Line) Table 471: Test #61 Hybrid Line Audits Test Error Code Test Result Description / Recommendation ABRT Internal system error 1 ABRT The test was aborted due to an internal system error during the switchhook audit. 2 ABRT Internal system error occurred during bad scan inquiry audit. 1. Make sure that the station is not in an out of service state. 2. Retry the command at 1-minute intervals up to 5 times. 3 ABRT This port may have been busied out by system technician. 1.
PAGE 1348
Communication Manager Maintenance-Object Repair Procedures Table 471: Test #61 Hybrid Line Audits Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. FAIL Internal system error 1. Retry the command at 1-minute intervals up to 5 times. PASS Hybrid Line Audits test passed. 1.
PAGE 1349
HYB-LINE (Hybrid Line) Hybrid 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 472: Test #62 Hybrid Line Ringer Update Test Error Code Test Result Description / Recommendation 3 ABRT This port may have been busied out by system technician. 1. Look in the Error Log for Error Type 18 (port busied out) for this port.
PAGE 1350
Communication Manager Maintenance-Object Repair Procedures Table 472: Test #62 Hybrid Line Ringer Update Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Enter list config, and resolve any problems that are found. 2.
PAGE 1351
INADS (INADS Link) INADS (INADS Link) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO INADS none test inads-link INADS Link The INADS Link MO represents the software and communications link used by the switch to call an alarm receiver.
PAGE 1352
Communication Manager Maintenance-Object Repair Procedures The “Command successfully completed” message means the switch will attempt to call the alarm receiver in 2 minutes. (This test runs even if Alarm Origination is disabled.) The 2-minute delay provides enough time for a remote technician to hang up the call and thus free up the alarm receiver’s line so that the customer’s switch can call the alarm receiver back.
PAGE 1353
INADS (INADS Link) Table 473: INADS Link Test Error Log Entries (continued) Error Code Test Result Description / Recommendation 4 0 The alarm receiver did not answer the test call. 1. Verify that the alarm receiver is up and running. 2. Verify the accuracy of the alarm receiver’s phone number and the system’s product ID using the Maintenance-Related System Parameters screen. 3. Enable alarm origination using the Maintenance-Related System Parameters screen. 4.
PAGE 1354
Communication Manager Maintenance-Object Repair Procedures Table 473: INADS Link Test Error Log Entries (continued) Error Code Test Result Description / Recommendation 10 0 A test inads-link is already in progress. 1. Wait 10 minutes for the current command to finish. 2. Review the current command’s results by viewing the Error Log and selecting the category inads-link. 11 0 The switch is trying to report alarms to the alarm receiver. The test cannot be run at this time. 1.
PAGE 1355
IPMEDPRO IPMEDPRO The IPMEDPRO Maintenance Object applies to the TN2302 IP Media Processor and the TN2602AP IP Media Resource 320. To identify which type of circuit pack is alarmed use the list configuration command for the location recorded in the error log. Then use the appropriate link below to diagnose the problem.
PAGE 1356
Communication Manager Maintenance-Object Repair Procedures IPMEDPRO (TN2302 IP Media Processor) S8700 | 8710 / S8500 The IPMEDPRO Maintenance Object applies to the TN2302 IP Media Processor and the TN2602AP IP Media Resource 320. To identify which type of circuit pack is alarmed use the list configuration command for the location recorded in the error log. If the circuit pack type displayed from the list configuration command is a TN2302 use this MO.
PAGE 1357
IPMEDPRO (TN2302 IP Media Processor) Table 474: TN2302 IPMEDPRO Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test board location 1 (a) 0 Circuit pack removed or SAKI test (#53) failed MIN ON 18 (b) 0 busyout board location WRN OFF release board location 23 (c) 0 Board administered but not inserted WRN OFF insert the board into the system 125 (d) none Wrong board MIN O
PAGE 1358
Communication Manager Maintenance-Object Repair Procedures Table 474: TN2302 IPMEDPRO Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data 2561 (n) Associated Test Alarm Level On/Off Board Ping error (#1379) MIN OFF 2817 (o) Any Ethernet Hardware Query test (#1405) MIN ON 3073 (p) Any Circuit pack reset test (#53) MIN ON 3329 (q) Any Duplicate network IP Address detected MIN OFF 3585 (r) 1 or 2 Verify NIC option test (#1511) MIN OFF 3841(s) None Inconsis
PAGE 1359
IPMEDPRO (TN2302 IP Media Processor) ● Make sure every condition for administration is met, and that a functioning MedPro circuit pack is inserted in the correct slot. ● Completely remove the IPMEDPRO from the system: a. Remove the administered IP-Interface associated with the circuit pack. b. Physically remove the circuit pack from the slot. b. Error Type 18: The IPMEDPRO interface circuit pack has been busied out by a busyout board location. 1. Release the circuit pack (release board location). c.
PAGE 1360
Communication Manager Maintenance-Object Repair Procedures resources associated with every DSP out of service, and then attempt to reset the TSI. For the repair procedure, see associated Test #1406. j. Error Type 1538: this error indicates hyperactivity on the board. Hyperactivity means the circuit pack is sending too many uplink messages to switch software. The circuit pack will be taken out of service. See Error Type 3999. k.
PAGE 1361
IPMEDPRO (TN2302 IP Media Processor) s. Error Type 3841: Aux Data = None: Inconsistent downlink message. The board was sent a message it did not understand. These errors are not service affecting. No action is required. t. Error Type 3841: Aux Data = 4283: The RTCP monitor server is not connected. There is a network problem between the monitor server and the media server or the RTCP monitor server is mis-administered.
PAGE 1362
Communication Manager Maintenance-Object Repair Procedures Control Channel Loop-around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 476: Test #52 Control Channel Loop-around Test Error Code Test Result Description / Recommendation None, 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1363
IPMEDPRO (TN2302 IP Media Processor) A reset of this circuit pack takes about 3½ minutes. Table 477: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1015 ABRT Port is not out of service. 1. Busy out the circuit pack. 2. Execute command again. 2100 ABRT System resources required for this test are not available. 1.
PAGE 1364
Communication Manager Maintenance-Object Repair Procedures IP Address Update Test #1371 This test is destructive. This test queries the media processor for its IP address, subnet mask, and gateway translation (IP parameters). If the parameters do not match software translation, maintenance software reboots the board. The board goes through a logical board removal and insertion. or: This test sends the IP Media Resource the IP address, subnet mask, and gateway translation (IP parameters).
PAGE 1365
IPMEDPRO (TN2302 IP Media Processor) Network Connectivity Query Test (#1383) This test is nondestructive. This test passes if the Ethernet port is connected. It fails, with no error code or aux data, if no electrical signal is detected. Table 479: Test #1383 Network Connectivity Query Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1366
Communication Manager Maintenance-Object Repair Procedures Ping Test (#1379) This test is nondestructive. This test verifies that the MedPro circuit pack can communicate with other nodes on the LAN. This test pings the gateway IP address as defined on the IP Interface screen. If the PING is successful, this test looks at the PING round-trip delay. If a round-trip delay of greater than 4 seconds is reported, a separate error is logged. Excessive round-trip delays do not take the MedPro out of service.
PAGE 1367
IPMEDPRO (TN2302 IP Media Processor) Table 480: Test #1379 Ping Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT The necessary system resources to execute the test could not be allocated. 1. Retry the command at 1-minute intervals up to 5 times. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times. 2801 ABRT No IP address defined. Verify IP interfaces translations and retest.
PAGE 1368
Communication Manager Maintenance-Object Repair Procedures FPGA Query This test verifies the status of the FPGA device on the TN2302 circuit pack. If the device is bad, software posts an error and alarm, and takes every DSP out of service (every DSP that is controlled by the one FPGA). Software then attempts to reset the FPGA. If the reset passes or the original test passes, the DSPs are placed back into service.
PAGE 1369
IPMEDPRO (TN2302 IP Media Processor) Table 481: Test #1406 MP Diagnostic Test (continued) Error Code Test Result Description / Recommendation 8192– 8328 FAIL The FPGA DSP test failed: 1. Enter busyout board location. 2. Enter reset board location. 3. Enter release board location. 4. Enter test board location long. If the board continues to fail, replace the board. 16384– 16900 FAIL A SCOTCH device failed: 1. Enter busyout board location. 2. Enter reset board location. 3.
PAGE 1370
Communication Manager Maintenance-Object Repair Procedures Table 481: Test #1406 MP Diagnostic Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct. Administer the IPMEDPRO interface if it is not already administered. 2.
PAGE 1371
IPMEDPRO (TN2302 IP Media Processor) An audio channel using G.711 is setup between both boards. A 1004-Hz test tone is transmitted from the source PN to the destination PN over the G.711 audio channel. The test tone is then transmitted from the destination PN to the source PN. Table 482: Short IP 2-Way Transmission Test (#1505) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate timeslots for the test.
PAGE 1372
Communication Manager Maintenance-Object Repair Procedures Table 482: Short IP 2-Way Transmission Test (#1505) (continued) Error Code Test Result Description / Recommendation 2801 ABRT The IP Media Processor board has not been administered on the ip-interface form. 2806 ABRT The system could not find any in-service IP Media Processor boards to use as a destination for this test. 2807 ABRT The specified IP Media Processor board has been disabled on the ip-interfaces form.
PAGE 1373
IPMEDPRO (TN2302 IP Media Processor) Table 482: Short IP 2-Way Transmission Test (#1505) (continued) Error Code Test Result Description / Recommendation XX XX = PN # PASS The board is functioning properly. The test tone was transmitted and received successfully between: ● The IP Media Processor specified in the test command ● An IP Media Processor in the PN specified in the error code (XX). (The test tone was sent and received in both directions). XX = PN number.
PAGE 1374
Communication Manager Maintenance-Object Repair Procedures A 1004-Hz test tone is transmitted from the source PN to the destination PN over the G.711 audio channel. The test tone is then transmitted from the destination PN to the source PN. Table 483: Long IP 2-Way Transmission Test (#1506) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate timeslots for the test.
PAGE 1375
IPMEDPRO (TN2302 IP Media Processor) Table 483: Long IP 2-Way Transmission Test (#1506) (continued) Error Code Test Result Description / Recommendation 2801 ABRT The IP Media Processor board has not been administered on the ip-interfaces form. 2806 ABRT The system could not find any in-service IP Media Processor boards to use as a destination for this test. 2807 ABRT The specified IP Media Processor board has been disabled on the ip-interfaces screen.
PAGE 1376
Communication Manager Maintenance-Object Repair Procedures Table 483: Long IP 2-Way Transmission Test (#1506) (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Resolve either wrong board (Error 125) or no board (Error 131) issues, if applicable. 2. Check that the board is properly translated and inserted. a. If so, check for hyperactivity (Error 1538). b. If hyperactive, use reset board location. 3. Run the test again.
PAGE 1377
IPMEDPRO (TN2302 IP Media Processor) Verify NIC Options Test (#1511) This test is nondestructive. This test verifies if the NIC interface parameters, speed, and duplex (full/half) match with administration. The test passes if the NIC parameters match administration. The test fails if the NIC parameters do not match administration. Table 484: Verify NIC Options Test (#1511) Error Code Test Result Description / Recommendation 1014 ABRT Board is not inserted. Insert and administer a TN2302 board.
PAGE 1378
Communication Manager Maintenance-Object Repair Procedures Table 484: Verify NIC Options Test (#1511) (continued) Error Code Test Result Description / Recommendation 2807 ABRT The board is administered but not enabled on the ip-interfaces form. 1. Use the change ip-interfaces location to enable the board. 2. Retest the board. 1 FAIL The board is reporting that it is running half duplex with auto-negotiate (y).
PAGE 1379
IPMEDPRO (TN2302 IP Media Processor) Table 484: Verify NIC Options Test (#1511) (continued) Error Code Test Result Description / Recommendation 2 FAIL The board is reporting different options than what is administered. Software tried to correct the options but the board did not take the option update. It could be argued that this is a false alarm, especially if the link is operating correctly with no observable degradation of service. Note: Do not immediately replace the board for this fault.
PAGE 1380
Communication Manager Maintenance-Object Repair Procedures IPMEDPRO (TN2602AP IP Media Resource 320) S8700 | 8710 / S8500 The IPMEDPRO Maintenance Object applies to the TN2302 IP Media Processor and the TN2602AP IP Media Resource 320. To identify which type of circuit pack is alarmed use the list configuration command for the location recorded in the error log. If the circuit pack type displayed from the list configuration command is a TN2602AP use this MO.
PAGE 1381
IPMEDPRO (TN2602AP IP Media Resource 320) ● 320 voice channels, considered the standard IP Media Resource 320 ● 80 voice channels, considered the low-density IP Media Resource 320 Up to two TN2602AP circuit packs may be installed in a single port network for load balancing. The TN2602AP circuit pack is also compatible with and can share load balancing with the TN2302 circuit pack. Actual capacity may be affected by a variety of factors, including the codec and fax support.
PAGE 1382
Communication Manager Maintenance-Object Repair Procedures Table 485: TN2602AP IP Media Resource Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 1 (a) 0 Circuit pack removed or sanity failure MIN ON 18 (b) 0 busyout board location WRN OFF release board location 23 (c) 0 Board administered but not inserted WRN OFF add ds1 location Wrong board MIN ON 125 (d) 257 (e) 65535 Control Channel Loop test (#52) MIN ON 513 (f) 4352,
PAGE 1383
IPMEDPRO (TN2602AP IP Media Resource 320) Table 485: TN2602AP IP Media Resource Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 3073 (o) Any Aggregator Hardware Query (#1629) MIN ON 3329 (p) Any Duplicate network IP address detected (#1371) MIN OFF 3585 (q) 1 or 2 Verify NIC option test (#1511) MIN OFF 3841(r) None Inconsistent downlink or board error 3841(s) 4283 RTCP Monitor Server error 3999 (t) Any None Test to Clear Va
PAGE 1384
Communication Manager Maintenance-Object Repair Procedures b. Physically remove the circuit pack from the slot. b. Error Type 18: The IP Media Resource was busied out by a busyout board location. 1. Release the circuit pack (release board location). c. Error Type 23: The IP Media Resource is not completely administered.
PAGE 1385
IPMEDPRO (TN2602AP IP Media Resource 320) m. Error Type 2561: the ping test has failed. The diagnostics that are run by this failure start up analysis testing and rerun the test. Testing will continue until the problem is cleared. n. Error Type 2817: Ethernet hardware failure on the TN2602AP IP Media Resource. The switch takes resources associated with every DSP out of service and attempts to reset the Ethernet hardware.
PAGE 1386
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented. By clearing error codes associated with the Control Channel Loop test, you may also clear errors generated from other tests in the sequence.
PAGE 1387
IPMEDPRO (TN2602AP IP Media Resource 320) Table 487: Test #52 Control Channel Loop-around Test (continued) Error Code Test Result Description / Recommendation FAIL The circuit pack failed to return the circuit pack code or vintage. 1. Retry the command up to 5 times. 2. If the problem continues, replace the circuit pack. 3. Retry the command up to 5 times. 0 PASS Communication with this circuit pack is successful. NO BOARD The test could not relate the internal ID to the port (no board).
PAGE 1388
Communication Manager Maintenance-Object Repair Procedures Table 488: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1015 ABRT Port is not out of service. 1. Busy out the circuit pack. 2. Execute command again. 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1389
IPMEDPRO (TN2602AP IP Media Resource 320) IP Address Update Test #1371 This test is conditionally destructive. This test queries the Media Resource for its IP address, subnet mask, and gateway translation (IP parameters). If the parameters do not match software translation, maintenance software reboots the board. or: This test sends the IP Media Resource the IP address, subnet mask, and gateway translation (IP parameters). If the parameters do not match software translation, the system reboots the board.
PAGE 1390
Communication Manager Maintenance-Object Repair Procedures Network Connectivity (#1383) This test is nondestructive. This test passes if the Ethernet port is connected. It fails, with no error code or aux data, if no electrical signal is detected. Table 490: Test #1383 Network Connectivity Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1391
IPMEDPRO (TN2602AP IP Media Resource 320) Ping Test (#1379) This test is nondestructive. This test verifies that the IP Media Resource can communicate with other nodes on the LAN. This test pings the gateway IP address as defined on the IP Interface screen. If the PING is successful, this test looks at the PING round-trip delay. If a round-trip delay of greater than 4 seconds is reported, a separate error is logged. Excessive round-trip delays do not take the IP Media Resource out of service.
PAGE 1392
Communication Manager Maintenance-Object Repair Procedures Table 491: Test #1379 Ping Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT The necessary system resources to execute the test could not be allocated. 1. Retry the command at 1-minute intervals up to 5 times. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times. 2801 ABRT No IP address defined. Verify IP interfaces translations and retest.
PAGE 1393
IPMEDPRO (TN2602AP IP Media Resource 320) For logged failures reseat the board to run the test again. If the board still fails, replace the board. Table 492: Test #1402 Aux Data values Aux Data Description Board in service? 20481 Field Programmable Gate Array (FPGA) not functioning properly.
PAGE 1394
Communication Manager Maintenance-Object Repair Procedures An audio channel using G.711 is setup between both boards. A 1004-Hz test tone is transmitted from the source PN to the destination PN over the G.711 audio channel. The test tone is then transmitted from the destination PN to the source PN. Table 493: Short IP 2-Way Transmission Test (#1505) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate timeslots for the test.
PAGE 1395
IPMEDPRO (TN2602AP IP Media Resource 320) Table 493: Short IP 2-Way Transmission Test (#1505) (continued) Error Code Test Result Description / Recommendation 2801 ABRT The IP Media Resource has not been administered on the change ip-interface form. 2806 ABRT The system could not find any in-service IP Media Resources to use as a destination for this test. 2807 ABRT The specified IP Media Processor has been disabled on the change ip-interfaces form.
PAGE 1396
Communication Manager Maintenance-Object Repair Procedures Table 493: Short IP 2-Way Transmission Test (#1505) (continued) Error Code Test Result Description / Recommendation XX XX = PN # PASS The board is functioning properly. The test tone was transmitted and received successfully between: ● The IP Media Resource specified in the test command ● An IP Media Resource in the PN specified in the error code (XX). (The test tone was sent and received in both directions). XX = PN number.
PAGE 1397
IPMEDPRO (TN2602AP IP Media Resource 320) test tone is transmitted from the source PN to the destination PN over the G.711 audio channel. The test tone is then transmitted from the destination PN to the source PN. Table 494: Long IP 2-Way Transmission Test (#1506) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate timeslots for the test. The system may be under heavy traffic conditions or it may have timeslots out of service due to TDM-BUS errors. 1.
PAGE 1398
Communication Manager Maintenance-Object Repair Procedures Table 494: Long IP 2-Way Transmission Test (#1506) (continued) Error Code Test Result Description / Recommendation 2801 ABRT The IP Media Resource has not been administered on the ip-interfaces form. 2806 ABRT The system could not find any in-service IP Media Resources to use as a destination for this test. 2807 ABRT The specified IP Media Resource has been disabled on the ip-interfaces screen.
PAGE 1399
IPMEDPRO (TN2602AP IP Media Resource 320) Table 494: Long IP 2-Way Transmission Test (#1506) (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Resolve either wrong board (Error 125) or no board (Error 131) issues, if applicable. 2. Check that the board is properly translated and inserted. a. If so, check for hyperactivity (Error 1538). b. If hyperactive, use reset board location. 3. Run the test again.
PAGE 1400
Communication Manager Maintenance-Object Repair Procedures Table 495: Test #1511 Verify NIC Options (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received within the allowable time. Retry the command at 1 minute intervals a maximum of 3 times. 1. If this result occurs repeatedly, attempt to reset the circuit pack with busyout board location and reset board location. 2.
PAGE 1401
IPMEDPRO (TN2602AP IP Media Resource 320) Table 495: Test #1511 Verify NIC Options (continued) Error Code Test Result Description / Recommendation 1 FAIL The board is reporting that it is running half duplex with auto-negotiate (y). Communication Manager is trying to negotiate the settings on the circuit pack to match the administered settings and, under the above condition, it is logging a fault.
PAGE 1402
Communication Manager Maintenance-Object Repair Procedures Table 495: Test #1511 Verify NIC Options (continued) Error Code Test Result Description / Recommendation 2 FAIL The board is reporting different options than what is administered. Software tried to correct the options but the board did not take the option update. It could be argued that this is a false alarm, especially if the link is operating correctly with no observable degradation of service.
PAGE 1403
IPMEDPRO (TN2602AP IP Media Resource 320) If the status is bad, the DSPs are taken out-of-service. A reset of the Aggregator hardware is attempted, and if this is successful the DSPs are placed pack into service.
PAGE 1404
Communication Manager Maintenance-Object Repair Procedures Table 497: Test #1630 Packet Count Query (continued) Error Code Test Result Description / Recommendation 1003 ABRT No tone receivers available 1007 ABRT Port not translated 1014 ABRT Board not translated 1115 ABRT No in-service port available for testing 1139 ABRT Packet Bus in Port Network is out-of-service 1144 ABRT PPN Packet Bus is out-of-service 2000 ABRT Response was not received within the allowable time 2012 ABRT S
PAGE 1405
IPSV-CTL (Ipserver Interface Control) IPSV-CTL (Ipserver Interface Control) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO IPSV-CTL NA set ipserver-interface Ipserver Interface Control The TN2312AP IPSI and TN2312BP circuit packs are duplicated in a high- or critical-reliability system. As part of duplicated IPSIs, PKT-INTs, Archangels, and Tone-Clocks are also duplicated.
PAGE 1406
Communication Manager Maintenance-Object Repair Procedures The active media server’s maintenance software is responsible for maintaining the SOH of both the active and standby IPSI in each PN. If an active IPSI’s SOH is lower than the standby’s, IPSI interchange is initiated. The following list contains failures and actions that cause an interchange: Active IPSI has a faulty Tone-Clock. 1. IPSI’s hardware detects loss of clock, and its firmware initiates clock interchange. 2.
PAGE 1407
IPSV-CTL (Ipserver Interface Control) Table 499: IPSI A is Active Function IPSI A Tone-Clock X PKT-INT X Archangel X IPSI B EI IPSI in Another PN EI IPSI in Another PN Table 500: IPSI B is Active Function IPSI A IPSI B Tone-Clock X PKT-INT X Archangel X Table 501: IPSI A Provides Tone-Clock; Fall-Back to EI-EAL Function Tone-Clock IPSI A IPSI B EI IPSI in another PN X PKT-INT X Archangel X Table 502: IPSI B Provides Tone-Clock; Fall-Back to EI-EAL Function Tone-Clock IPSI A
PAGE 1408
Communication Manager Maintenance-Object Repair Procedures System Configurations with Duplicated IPSIs Figure 76 shows a critical-reliability system with duplicated IPSIs and directly connected PNCs. Figure 77: Duplicated IPSI Duplicated PNC with Center Stage Switch Connectivity on page 1409 shows a critical-reliability system with duplicated IPSIs and CSS-connected PNCs. Table 503: Cabinets that support IPSI and IPSI duplication on page 1409 shows a complete list of cabinets.
PAGE 1409
IPSV-CTL (Ipserver Interface Control) Figure 77: Duplicated IPSI Duplicated PNC with Center Stage Switch Connectivity PN IPSI A T/C AA TDM PKT-INT LAN Switch Node Maint/ Test EI ... PN 1 EI EI PN n PN n+m EI EI EI EI S N I S N I S N I S N I S N I S N I EI Switch Node S N I S N I S N I S N I S N I S N I CSS A EI ...
PAGE 1410
Communication Manager Maintenance-Object Repair Procedures Table 503: Cabinets that support IPSI and IPSI duplication (continued) Cabinet type Supported IPSI Duplication TN2312AP TN2312BP Primary slot MCC1 EPN - 1 PN Y Y A00 B01 MCC1 EPN - 2 PNs Y Y A00 B01 E02 D01 A00 N/A B02 N/A D02 N/A A00 N/A B02 N/A C02 N/A D02 N/A A00 N/A B02 N/A C02 N/A D02 N/A E02 N/A MCC1 EPN - 3PNs MCC1 EPN - 4 PNs MCC1 EPN - 5 PNs Y Y Y Y Y Y Secondary slot G600 Y Y A02 N/A
PAGE 1411
IPSV-CTL (Ipserver Interface Control) Error Log Entries Whenever an IPSI interchange takes place, an error is logged against IPSV-CTL with a code that conveys information about the cause of the interchange and which IPSI became active.
PAGE 1412
Communication Manager Maintenance-Object Repair Procedures Table 505: Encoding of Error Codes for Software Requested IPSI interchange (continued) Field y z Variable Name Value Fault class/stimulus causing software action Fault or improvement Description 1 EAL fault class 2 PKT-INT fault class 3 TONE-BD fault class (not TDM-CLK) 4 TDM-CLK fault class (loss of clock) 7 Preference migration to A-side IPSI 0 This is an improvement in the previous fault class (y).
PAGE 1413
IPSV-CTL (Ipserver Interface Control) IPSI Interchange (Duplicated IPSIs) Software will take action upon any fault that affects the IPSI and attempt to interchange to the healthier IPSI. In addition, when neither IPSI is completely healthy to provide clock, packet interface and archangel, one IPSI will be chosen to be the clock, and the archangel will move to the EI. Moving the archangel’s functionality to the EI requires another port network to have a healthy IPSI, and this port network to have an EI.
PAGE 1414
Communication Manager Maintenance-Object Repair Procedures An example of the output of the list ipserver-interface command is: list ipserver-interface IP SERVER INTERFACE INFORMATION Port Ntwk Num ---2 Pri/ Sec Bd Loc -----2A01 Primary/ Primary/ Primary/ Secondary Secondary Secondary Serv IP Address Host Name DHCP ID State --------------- ---------------- --------- ----172.18.18.181 172.18.18.181 ipsi-A02a IN State Of Control Health State C P E G ------- ------actv-aa 0.0.0.0 3 3A02 172.18.18.
PAGE 1415
IP-SVR (IP Server Interface) IP-SVR (IP Server Interface) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO IP-SVR WRN busyout/release ipserver-interface IP Server Interface TN2312 IP Server Interface Circuit Pack Note: The only error type reported against this MO is error Type 18.
PAGE 1416
Communication Manager Maintenance-Object Repair Procedures Table 508: IPSI state-of-health components Fault Class Circuit pack function that is monitored Priority Clock Clocking signal for the TDM bus 1 (highest) PKTINT Sending and receiving packet control messages 2 EAL Noting the state of the expansion archangel link (up or down) 3 Generation Generating tones 4 (lowest) TN2312AP IP Server Interface (IPSI) Figure 78: TN2312AP IPSI TDM Bus Clocks Spi tfir e2 Packet Bus LA NIS MP C8 260
PAGE 1417
IP-SVR (IP Server Interface) Control Network Interface This is a 10/100 BaseT Ethernet interface used to connect to the Control network. This interface is available through the backplane I/O as well as through the faceplate. When the IPSI I/O adapter is plugged onto the Amphenol connector, located on the rear of the carrier, the backplane connections will be selected, otherwise, connectivity to the faceplate will be selected.
PAGE 1418
Communication Manager Maintenance-Object Repair Procedures The TN2312BP and the 655A power supply provide the following information to the G650: ● Environment maintenance - Inlet temperature - Inlet temperature of the G650 (sensor is in the 655A power supply) - Exhaust temperature - G650 carrier exhaust air sensor - Hot Spot temperature status- 655A power supply sensor - Voltage - +5VDC - -5VDC - -48VDC - Fan Control - The speed at which the fans are operating: - Undr indicates that the fan voltage is und
PAGE 1419
IP-SVR (IP Server Interface) You can use the following Communication Manager SAT commands for emergency transfer: - set emergency-transfer on|off|auto - Use this to set emergency transfer to on (not in emergency transfer), off (in emergency transfer), or auto (emergency transfer is controlled by Communication Manager). - status cabinet nn - Use this to verify the current setting of emergency transfer. When the emergency transfer is set to other than auto an alarm is generated.
PAGE 1420
Communication Manager Maintenance-Object Repair Procedures IPSI Circuit Pack Faceplate The faceplate view of the TN2312AP IPSI is shown in Figure 78: TN2312AP IPSI on page 1416 and described in the following sections. IPSI LEDs There are four LEDs on the TN2312AP IPSI faceplate, and five LEDs on the TN2312BP IPSI faceplate. The top three LEDs are the standard ones found on most TN circuit packs. The fourth LED imitates the TN2182B Tone-Clock’s amber LED.
PAGE 1421
IP-SVR (IP Server Interface) Table 509: IPSI LEDs (continued) Function LED State Description Clock status TN2312BP, (same as TN2182B) Amber Flashing 2.7 sec on 0.3 sec off Active: Master clock, using offboard synchronization source. Winking 0.3 sec on 2.7 sec off Active: Master clock, using its local reference source. Steady on Active: Board has been reset and is providing clocks but has not been told which synchronization source to use. Steady off Standby: Applying no tones to the network.
PAGE 1422
Communication Manager Maintenance-Object Repair Procedures 4-Character LED The 4-character LED is used to display the circuit pack status related to the Ethernet interfaces. If automatic IP address assignment via DHCP is enabled, the top character displays the Switch ID and the next two characters display the Cabinet Number. The last character is used to display the link status of the two Ethernet interfaces. Services Interface The top RJ45 jack is the services interface.
PAGE 1423
ISDN-PLK (ISDN-PRI Signaling Link Port) ISDN-PLK (ISDN-PRI Signaling Link Port) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run1 Full Name of MO ISDN-LNK MIN test port location l ISDN-PRI Signaling Link port ISDN-LNK WRN test port location sh ISDN-PRI Signaling Link port 1. For this MO, location is 24 for 24-channel interfaces and 16 for 32-channel interfaces. This MO was formerly known as “ISDN-LNK (ISDN-PRI Signaling Link Port)”.
PAGE 1424
Communication Manager Maintenance-Object Repair Procedures In a 24-channel system, the DS1 ISDN Trunk or PRI endpoint port (B-channels) may use any of the first 23 ports. The ISDN-PRI Signaling Link Port must be the 24th port. In certain configurations (NFAS), the 24th port may be used as a B-channel. Refer to ISDN-SGR (ISDN-PRI Signaling Group) on page 1429 for further details.
PAGE 1425
ISDN-PLK (ISDN-PRI Signaling Link Port) Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures. b. Error Type 18: The D channel is demand busied out. No calls can be made over this D channel. c. Error Type 130: the circuit pack or media module has been removed or has been insane for more than 11 minutes.
PAGE 1426
Communication Manager Maintenance-Object Repair Procedures h. Error Type 3842: Receive FIFO Overflow error. This error occurs when the circuit pack or media module detects an overflow of its receive buffers. If it occurs frequently, it may indicate a LAPD parameter mismatch between the two endpoints of a packet-switched connection. LAPD should be able to recover from this problem, but it may degrade the performance of the LAN bus.
PAGE 1427
ISDN-PLK (ISDN-PRI Signaling Link Port) Table 512: Test #643 Signaling Link Board Check (continued) Error Code Test Result Description / Recommendation 1700 ABRT Rollabout video abort. The PRI terminal adapter associated with this D-channel port is detached from the circuit pack. This is normal when the rollabout video feature is enabled. To complete a test on this port: 1. Re-attach the disconnected PRI terminal adapter. 2.
PAGE 1428
Communication Manager Maintenance-Object Repair Procedures Table 513: Test #939 Signaling Port LAN Loop back Error Code Test Result Description / Recommendation 1015 ABRT The port is not in the out-of-service state. Use busyout port location to place it in the out-of-service state and repeat this test. ! CAUTION: CAUTION: 1139 ABRT The busyout prevents new call originations on every B channel in the signaling group until the port is released. This port network’s packet bus is out of service. 1.
PAGE 1429
ISDN-SGR (ISDN-PRI Signaling Group) ISDN-SGR (ISDN-PRI Signaling Group) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run1 Full Name of MO ISDN-SGR MIN test signaling-group grp# ISDN-PRI Signaling Group ISDN-SGR WRN test signaling-group grp# ISDN-PRI Signaling Group 1. grp# is the signaling group number (1–166); the test sequence can be either short or long.
PAGE 1430
Communication Manager Maintenance-Object Repair Procedures ISDN-PRI D-channel signaling can be combined with a group of B channels in three basic ways: ● FAS (facility-associated signaling) ● NFAS (non-facility-associated signaling) ● Backup NFAS signaling In a FAS signaling group, the 24th port of the TN464 UDS1 Interface circuit pack or MM710 DS1 Interface Media Module carries D-channel signaling for up to 23 B-channel ports on the same circuit pack or media module.
PAGE 1431
ISDN-SGR (ISDN-PRI Signaling Group) Table 514: ISDN-PRI Signaling Group Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 769 Any Primary Signaling Link Hardware Check (#636) test signaling-group grp# 1025 Any Secondary Signaling Link Hardware Check (#639) test signaling-group grp# 1793 (e) Any Layer 2 Status Test (#647) WRN OFF test signaling-group grp# 2049 (f) Any Layer 2 Status Test (#647) WRN OFF test signaling-group
PAGE 1432
Communication Manager Maintenance-Object Repair Procedures does recover, the B channels will be negotiated back to the In-Service state and their alarms will be retired. When this error occurs, the state of the Signaling Group is changed to out of service (verify using status signaling-group grp#). d. Error Type 513: the secondary signaling channel connection has been lost for more than 90 seconds.
PAGE 1433
ISDN-SGR (ISDN-PRI Signaling Group) Table 515: Descriptions and Recommendations for Error Types 3842-3942 Error Code Description 3842 A request has been made to use a transit network or common carrier that cannot be accessed. Recommendation 1. From the circuit pack or media module and port number (in the Aux Data field), determine the trunk group against which the error was reported. 2.
PAGE 1434
Communication Manager Maintenance-Object Repair Procedures Table 515: Descriptions and Recommendations for Error Types 3842-3942 (continued) Error Code Description 3878 The far-end switch has indicated that the network is not functioning correctly and that the condition may last a relatively long period of time (for example, immediately re-attempting the call may not be successful). 3890 A request to use a network service (e.g., SDN) has been denied.
PAGE 1435
ISDN-SGR (ISDN-PRI Signaling Group) Table 515: Descriptions and Recommendations for Error Types 3842-3942 (continued) Error Code Description Recommendation 3894 Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone. First, eliminate any transitory state mismatch problems by issuing test port location for the trunk port shown in the Aux Data field. Test #256 (Service State Audit) is the important test in the sequence.
PAGE 1436
Communication Manager Maintenance-Object Repair Procedures Table 515: Descriptions and Recommendations for Error Types 3842-3942 (continued) Error Code Description 3910 Only restricted digital BC available. 3919 Service or option not implemented, unspecified. Used when no other cause in this class applies. 3928 A call was denied because of a basic incompatibility existed between the type of call and either the facilities selected by the routing pattern or the called user.
PAGE 1437
ISDN-SGR (ISDN-PRI Signaling Group) Primary Signaling Link Hardware Check (#636) The ISDN-PRI Signaling Group D-channel port depends on the health of the TN464C or higher suffix UDS1 Interface circuit pack or MM710 DS1 Interface Media Module on which it resides. This test will fail if there are problems with either the ISDN-PRI Primary D-channel port or the UDS1 circuit pack or MM710 DS1 Media Module.
PAGE 1438
Communication Manager Maintenance-Object Repair Procedures Table 516: Test #636 Primary Signaling Link Hardware Check (continued) Error Code Test Result Description / Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Ensure that the board translations are correct.
PAGE 1439
ISDN-SGR (ISDN-PRI Signaling Group) Figure 79: Remote Layer 3 Query Test (#637) PKTINT CIRCUIT PROCESSOR UDS1 PACKET PACK (UN331) INTERFACE CIRCUIT BUS (TN1655) PACK TO FAR-END PROCESSOR TN464C/D For systems supporting circuit packs (S8700, S8500) Figure 79 illustrates a UDS1 Interface circuit pack located in the PN. When the UDS1 board resides in a PN, there is additional PNC hardware connecting the packet buses of the IPSI PN and PN.
PAGE 1440
Communication Manager Maintenance-Object Repair Procedures Table 517: Test #637 Remote Layer 3 Query (continued) Error Code Test Result Description / Recommendation 1113 ABRT The signaling channel is down. Therefore, no messages can be sent to the far-end switch or terminal adapter. 1. Examine the results of Tests #636 and #639 and follow recommendations provided there. 2100 ABRT Could not allocate the necessary system resources to run this test. 1.
PAGE 1441
ISDN-SGR (ISDN-PRI Signaling Group) Table 517: Test #637 Remote Layer 3 Query (continued) Error Code Test Result Description / Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Ensure that the board translations are correct.
PAGE 1442
Communication Manager Maintenance-Object Repair Procedures Table 518: Test #639 Secondary Signaling Link Hardware Check (continued) Error Code Test Result Description / Recommendation 4 FAIL There is a problem with the Processor Interface Link. No DS1 ISDN Trunk (B-channel) or Wideband PRI Endpoint calls can be made until the problem is resolved. 1.
PAGE 1443
ISDN-SGR (ISDN-PRI Signaling Group) Layer 2 Status Test (#647) The Layer 2 Status Test checks the layer-2 status of the ISDN-PRI Signaling Channel (D channel). This test will fail if there is a hardware failure or a facility problem, or if the primary and secondary ISDN-PRI D channels are not administered correctly.
PAGE 1444
Communication Manager Maintenance-Object Repair Procedures Table 519: Test #647 Layer 2 Status Query Test (continued) Error Code Test Result Description / Recommendation 1 FAIL Layer 2 of the primary signaling channel is down: 1. Examine the results of the Primary Signaling test (#636), and follow recommendations provided there. 2.
PAGE 1445
ISDN-SGR (ISDN-PRI Signaling Group) Table 519: Test #647 Layer 2 Status Query Test (continued) Error Code Test Result Description / Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Ensure that the board translations are correct.
PAGE 1446
Communication Manager Maintenance-Object Repair Procedures ISDN-TRK (DS1 ISDN Trunk) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO ISDN-TRK MAJ1 test port location l DS1 ISDN Trunk ISDN-TRK MIN test port location l DS1 ISDN Trunk ISDN-TRK WRN test port location s DS1 ISDN Trunk 1. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options.
PAGE 1447
ISDN-TRK (DS1 ISDN Trunk) Two types of DS1 interfaces exist: ● 24 DS0 channels on a 1.544-Mbps link ● 31 DS0 channels + 1 framing channel on a 2.048-Mbps link On 24-channel interfaces, any of the first 23 ports on the DS1 circuit packs or media modules can be a B channel.
PAGE 1448
Communication Manager Maintenance-Object Repair Procedures Alarming Based on Service States A warning alarm is logged against a DS1 ISDN B-channel trunk when it is placed in the Maintenance/Far-End or Out-Of-Service/Far-End states, during which the trunk is unusable for outgoing calls. When a warning alarm is present, use the status trunk grp#/mem# command to determine the exact state. Other alarms can be diagnosed by using the short and/ or long test sequences.
PAGE 1449
ISDN-TRK (DS1 ISDN Trunk) ● Maintenance/Far-End (MTC/FE) This state is reached when the far end does not respond after a certain amount of time to messages sent over the signaling link for a particular trunk. This state is different from OOS/ FE since the signaling link must have initially been up and the B channels in service. The switch will periodically send messages to the far end to try to negotiate the trunk (B channel) into service.
PAGE 1450
Communication Manager Maintenance-Object Repair Procedures Figure 80: Common Progressions in Service States Out-ofService Near End Craft busyout of B-channel (TRK-GRP/MBR), or problem with near en d PI-LINK, DS1-BD, PI-BD, or port. Craft release of B-channel or clearing of near-end problem with DS1-BD, PI-BD, PI-LINK or port. Administer B-channel as member of a trunk group. Craft busyout of signaling link busyout link LINK-NO or transient state for demand long test of the trunk.
PAGE 1451
ISDN-TRK (DS1 ISDN Trunk) ISDN-PRI Trunk Service States Use status trunk grp#/mem# to see DS1 ISDN Trunk service states, as shown in Table 520: Service States on page 1451. Note: Note: Refer to Troubleshooting ISDN-PRI in Maintenance Procedures (03-300192) for a layered approach to processing ISDN-PRI problems. Table 520: Service States Service State Alarm1 Possible Cause Possible Solution out-of-service/NE WRN Trunk is demand busied out. Enter release trunk grp#/ mem#.
PAGE 1452
Communication Manager Maintenance-Object Repair Procedures Table 520: Service States (continued) Service State Alarm1 Possible Cause Possible Solution maint/FE WRN Signaling channel has been down for over 90 sec. Consult ISDN-SGRP and/or ISDN-LNK. Far-end signaling channel may be busied out, or the far-end switch may currently be restarting. WRN Repeated failure of far end to respond to messages. Maintenance software will periodically try to resend messages.
PAGE 1453
ISDN-TRK (DS1 ISDN Trunk) Table 521: DS1 ISDN Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 513 (h) Any None WRN OFF test port location 769 (g) Any None 1025 (i) 0 None 1281 Any Conference Circuit Test (#7) MAJ MIN WRN1 ON test port location l r 4 1537 Any NPE Crosstalk Test (#6) MAJ MIN WRN ON test port location l r 3 1793 (j) Any None test port location 3073 (k) Any Service State Audit (#256) test
PAGE 1454
Communication Manager Maintenance-Object Repair Procedures f. Error Type 130: The circuit pack or media module has been removed or has been insane for more than 11 minutes. To clear the error, reinsert or replace the circuit pack or media module. g. Error Types 257 and 796: Disagreement between this switch and the switch at the other end of the trunk connection with regard to the ISDN service state of the DS1 ISDN Trunk. This switch will automatically try to recover by performing a service state audit.
PAGE 1455
ISDN-TRK (DS1 ISDN Trunk) The meanings of Aux Data values are shown below; ignore any others. Table 522: ISDN Trunk - Error 3585 Aux Data Values Aux Data Cause 0 A idle trunk received a restart. 10 A call in a stable, talking state was cleared unexpectedly by the far end with an ISDN RESTART message. This state is called the “active” state.
PAGE 1456
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing error codes associated with the NPE Crosstalk test (#6), you may also clear errors generated from other tests in the sequence. Table 523: System Technician-Demanded Tests: DS1-BD Long Test Sequence D/ND1 NPE Crosstalk test (#6) S8300 / G700 On the G700/G350, aborts with Error Code 1412.
PAGE 1457
ISDN-TRK (DS1 ISDN Trunk) Table 524: Test #6 NPE Crosstalk Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be in use on a valid call. 1. Use status station or status trunk to determine when the port is available for testing. 2.
PAGE 1458
Communication Manager Maintenance-Object Repair Procedures Table 524: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation S8300 / G700: ABRT This test does not execute on a G700 Media Gateway. 2000 ABRT Response to the test was not received within the allowable time period. 1412 1. Retry the command at 1-minute intervals up to 5 times. 2020 ABRT The test did not run due to an already existing error on the specific port or a more general circuit pack error.
PAGE 1459
ISDN-TRK (DS1 ISDN Trunk) Table 525: Test #7 Conference Circuit Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be in use on a valid call. Use status station or status trunk to determine when the port is available for testing.
PAGE 1460
Communication Manager Maintenance-Object Repair Procedures Audit and Update Test (#36) This test sends port level translation data from the switch processor to the DS1 interface circuit pack or media module to assure that the trunk’s translation is correct. The port audit operation verifies the consistency of the current state of trunk kept in the DS1 interface circuit pack or media module and in the switch software.
PAGE 1461
ISDN-TRK (DS1 ISDN Trunk) Table 526: Test #36 Audit and Update Test (continued) Error Code Test Result Description / Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Ensure that the board translations are correct. Execute add ds1 location command to administer the MM710 interface if it is not already administered.
PAGE 1462
Communication Manager Maintenance-Object Repair Procedures Table 527: Test #255 Signaling Link State Check Test (continued) Error Code Test Result Description / Recommendation 4 FAIL There is a problem with the signaling channel. 1. If the Packet Control circuit pack is used, consult the procedures for the ISDN-PRI Signaling Group (ISDN-SGRP). Further information may also be obtained by consulting the procedures for the ISDN-PRI Signaling Channel (ISDN-LNK). 2.
PAGE 1463
ISDN-TRK (DS1 ISDN Trunk) was initially in service, it is placed in the maintenance/far-end state. No outgoing calls will be placed over this trunk, but incoming calls will be accepted. If an incoming call is presented with the trunk in such a state, a Service State Audit is immediately attempted (the switch does not wait for the 15-minute cycle, but tries to recover immediately).
PAGE 1464
Communication Manager Maintenance-Object Repair Procedures Table 528: Test #256 Service State Audit Test (continued) Error Code Test Result Description / Recommendation 1113 FAIL The signaling link has failed; the system cannot send any messages on behalf of this trunk. 1. Consult procedures for ISDN-SGR (ISDN-PRI Signaling Group) and ISDN-LNK (ISDN Signaling Link Port). FAIL Internal system error 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1465
ISDN-TRK (DS1 ISDN Trunk) Call State Audit Test (#257) If a call is active on the trunk, the switches on both sides of the connection should agree on the ISDN state of the call, as defined in the ISDN Protocol Specification. This test audits internal call state data by querying the far-end switch as to the ISDN state of the call. It can be helpful when trying to clear a hung call.
PAGE 1466
Communication Manager Maintenance-Object Repair Procedures Table 529: Test #257 Call State Audit Test (continued) Error Code Any Test Result Description / Recommendation PASS This switch sent a call state auditing message to the far-end switch to verify the state of the call active on this trunk. If a call state mismatch is found, then the call will be torn down within two minutes. If no call was active, then no message was sent.
PAGE 1467
ISDN-TRK (DS1 ISDN Trunk) Figure 81: Outgoing ISDN-PRI Test Call ....................................................... . . . . . . . . . . .. .. TDM Bus . . . . . . .. .. . . . . . . . . . . . . . . .. .. . . . . .. .. . . . . . . .. .. . . . . . . . . . . UDS1 M/T . . . . .. TN464 TN771 .. . . . . .. .. . . ....................................................... ISDN Trunk (B-Channel) DS1 Facility ............................ . . . . . . . . . . . . . . . . . . . . . . . . . . .......................
PAGE 1468
Communication Manager Maintenance-Object Repair Procedures Figure 82: ISDN-PRI Outgoing Test Call PI (TN765) or PACCON (TN778) NETCON SPE B-channel D-channel Setup B-channel TDM BUS M/T DS1/UDS1 TN7771B Synchronous Test Calls Use one of the following commands to initiate a synchronous outgoing test: ● test trunk grp#/mem# long [repeat #] ● test board address long [repeat #] ● test port address long [repeat #] The previous test sequences include a test call for ISDN-PRI trunks.
PAGE 1469
ISDN-TRK (DS1 ISDN Trunk) ● clear isdn-testcall grp#/mem# This command terminates an outgoing test call already in progress. Measurements already collected are not cleared until the next test call begins. A PASS of the asynchronous test indicates only that the test call was successfully established. Use status and list to get the results of the test.
PAGE 1470
Communication Manager Maintenance-Object Repair Procedures Table 530: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1019 ABRT Another Test call is in progress. 1. Enter list isdn-testcall to locate the test call. 2. Enter status isdn-testcall to find out the duration and start time of the test call. 3. Enter clear isdn-testcall to stop the test call from running. 4.
PAGE 1471
ISDN-TRK (DS1 ISDN Trunk) Table 530: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1118 ABRT Far end of ISDN trunk is not administered. 1. Check the administration of the far-end ISDN trunk. 2. Enter status trunk grp#/mem#. 3. Try the test again. 1119 ABRT The test call was aborted due to a normal call attempt on this trunk. The test call will only be performed if the trunk is idle. 1.
PAGE 1472
Communication Manager Maintenance-Object Repair Procedures Table 530: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2040 ABRT Internal system error. 1. Follow recommendations for ABORT code 2012. 2041 ABRT The call has timed out, perhaps because of a lack of system resources. Follow recommendations for ABORT code 2035. 2066 ABRT Could not establish test call. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1473
ISDN-TRK (DS1 ISDN Trunk) Table 530: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2206 ABRT Could not allocate the necessary system resources to run this test. 1. Follow recommendations for ABORT code 2100. 2208 ABRT Internal system error. 1. Follow recommendations for ABORT code 2012. 2209, 2210 ABRT 2211 ABRT Could not allocate the necessary system resources to run this test. 1. Follow recommendations for ABORT code 2100. Internal system error. 1.
PAGE 1474
Communication Manager Maintenance-Object Repair Procedures Table 530: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2042 FAIL Comparison of data sent to data received indicates a loss of integrity on the communications path. 1. Take the trunk out of service and check the quality of the DS1 connection, including the transmission facility and any external equipment such as DACs, CSUs, etc.
PAGE 1475
JNL-PRNT (Journal Printer Link) JNL-PRNT (Journal Printer Link) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO JNL-PRNT MIN test journal wakeup-log Journal Printer Link JNL-PRNT WRN test journal wakeup-log Journal Printer Link The maintenance strategies for JNL-PRNT (Journal Printer Link) and PMS-PRNT (PMS Printer Link) are the same. Refer to the “PMS-PRNT/JNL-PRNT (PMS Printer Link)” section of this chapter.
PAGE 1476
Communication Manager Maintenance-Object Repair Procedures LGATE-AJ S8700 | 8710 / S8500 See BRI-SET, Various Adjuncts on page 708. 1476 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1477
LGATE-BD (ISDN-BRI Line Circuit Pack) LGATE-BD (ISDN-BRI Line Circuit Pack) S8700 | 8710 / S8500 See BRI-BD (ISDN-BRI Line Circuit Pack) on page 677.
PAGE 1478
Communication Manager Maintenance-Object Repair Procedures LGATE-PT S8700 | 8710 / S8500 See BRI-PORT (ISDN-BRI Port) on page 685. 1478 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1479
LIC-ERR (License-Error Mode) LIC-ERR (License-Error Mode) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO LIC-ERR MAJ test license License-Error Mode The LIC-ERR MO works with the NO-LIC MO to look for any errors and violations associated with a License File.
PAGE 1480
Communication Manager Maintenance-Object Repair Procedures The License File is loaded onto a server during initialization of Communication Manager software, restoration of translations, and periodically during normal operation. After initialization, a query is made to WebLM, a license server plug-in that ● Reads the serial number in a License file. ● Compares this file’s serial number to a serial number in hardware. ● Compares the file’s serial number with a running software version.
PAGE 1481
LIC-ERR (License-Error Mode) b. Error Type 513: the license has expired, and the 30-day timer has started. When the 10-day timer expires, the system enters No-License mode (see NO-LIC (No License) on page 1727, Error Type 513). c. Error Type 769: feature use has exceeded limits, if the license has expired and the 30-day timer begins. When the timer expires, the system enters No-License mode. d. Error Type 1281: a new license was not installed after an upgrade.
PAGE 1482
Communication Manager Maintenance-Object Repair Procedures Table 531: Test #1484 and Test #19 License File Test (continued) Error Code Test Result Description / Recommendation 1014 ABRT Within the first 30 minutes after a system restart, the system cannot test the License file. 1. Enter display initcauses to find out when the system last restarted. 2. Wait for the remaining time plus 2 minutes, and retry the test. PASS The system is in License-Normal mode.
PAGE 1483
LIC-ERR (License-Error Mode) - Feature use exceeded prescribed limits - License expired - After a system had a valid license, the License file is missing or corrupt. Note: System resets do not reset the 30-day timer. If a system in License-Error mode is reset and the license error remains, the timer picks up the countdown where it left off. Note: To clear LIC-ERR alarms, the License file must match the switch hardware and administered parameters.
PAGE 1484
Communication Manager Maintenance-Object Repair Procedures Table 532: Error messages and repair procedures (continued) License Mode Description Explanation and repair procedure License-Error Warning mode; Communication Manager supported, 30-day countdown timer begins. If you log in to the server through the SAT, a message reads: “System Administration Will Be Blocked in Approximately XXX hours. Contact Your Service Representative.
PAGE 1485
LIC-ERR (License-Error Mode) ● Type III: includes the product ID (license serial identification number), release number, and capacities. Type III features cannot be changed by any login under any circumstances (applies to IP Telephones, IP Softphones, and IP Agents). Table 533: License error messages If the system goes into this mode... And reports this error message... It means that... No-License License File is Missing or Corrupted License could not be decrypted.
PAGE 1486
Communication Manager Maintenance-Object Repair Procedures Table 533: License error messages (continued) If the system goes into this mode... And reports this error message... It means that... License-Error Feature Usage Exceeds Limits The value of the Used field for any TYPE II or TYPE III field on the Customer Options forms (pages 1, 5, 6, and 9) is greater than the value of the field.
PAGE 1487
LOG-SVN (Login Security Violation) LOG-SVN (Login Security Violation) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO LOG-SVN MAJ enable login loginID1 Login Security Violation 1. Where loginID is the Avaya services login ID for which the security violation was detected. The Alt Name field indicates the login ID associated with the security violation and the major alarm.
PAGE 1488
Communication Manager Maintenance-Object Repair Procedures 4. The affected login ID will be disabled as a result of detection of the security violation, unless it is the system’s last enabled INADS-type login. The provision to disable a login ID following detection of a security violation involving that login ID is administrable on a login ID basis. 5. Use enable login to enable a login that has been disabled, and to retire any login security violation alarms associated with the login ID. 6.
PAGE 1489
LOG-SVN (Login Security Violation) Procedure to Retire SVN Alarm To retire a SVN alarm: 1. Enter the enable login loginID. The login ID associated with that alarm is displayed in the Alt Name field of the alarm report and the alarm is retired.
PAGE 1490
Communication Manager Maintenance-Object Repair Procedures MAINT (PN’s Maintenance Circuit Pack) S8700 MC MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MAINT MIN test maintenance sh PN’s Maintenance circuit pack MAINT MAJ test maintenance l PN’s Maintenance circuit pack The PN’s TN775D Maintenance circuit pack monitors and supports environmental maintenance for PN multicarrier or single-carrier cabinets.
PAGE 1491
MAINT (PN’s Maintenance Circuit Pack) closing the relay on either the PN’s Maintenance circuit pack (whichever is specified) for 1 minute. The repeat parameter may be used to close the relay for a longer length of time where the number of the repeat is the number of minutes for which the device will be activated (5 minutes is the suggested repeat value). Note: Note: S8700 and S8500 media servers equipped with G650 carriers will differ from this MO, in that the IPSI board provides the CPAD leads.
PAGE 1492
Communication Manager Maintenance-Object Repair Procedures TN775D Maintenance Circuit Pack Used with a TN2312AP IPSI Circuit Pack Connectivity when installed in an Existing System There is no backplane connectivity from the TN775D Maintenance circuit pack to the TN2312AP IPSI circuit pack in existing pre-R11carrier backplanes. To achieve connectivity for pre-R11 carriers, a faceplate cable must be used. The faceplate cable runs between the TN775D and the TN2312AP IPSI circuit packs faceplates.
PAGE 1493
MAINT (PN’s Maintenance Circuit Pack) Table 535: PN’s Maintenance Circuit Pack Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 2561 (b) 0 1 Sanity Handshake test (#106) MIN ON test maintenance sh r 3 2817 (b) 0 (c) 1 Serial Channel Loop test (#229) MIN ON test maintenance sh r 3 3329 (e) Any Serial Link Test (#337) MIN WRN1 OFF test maintenance sh r 3 3585 (f) Any Serial Link Test (#337) MIN WRN2 OFF test maintenanc
PAGE 1494
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1495
MAINT (PN’s Maintenance Circuit Pack) Table 536: Test #106 Sanity Handshake Test Error Code Test Result Description / Recommendation ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT Response to cabinet query was not received in the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1496
Communication Manager Maintenance-Object Repair Procedures Table 536: Test #106 Sanity Handshake Test (continued) Error Code Test Result Description / Recommendation FAIL PN’s Maintenance circuit pack did not respond to Sanity Handshake and the test timed out. 1. Verify that the carrier A power units are good. If the -5 Volt unit is defective in the A carrier, then communication with the PN’s Maintenance circuit pack will not be possible. 2.
PAGE 1497
MAINT (PN’s Maintenance Circuit Pack) Management Terminal Channel Local Loop-Around Test (#228) This test is destructive. This test checks TN775D on-board circuitry associated with the serial link for the management terminal connection. This test will not cause the local terminal login to drop, but any data displayed on the terminal while the test is running will be lost.
PAGE 1498
Communication Manager Maintenance-Object Repair Procedures Table 537: Test #228 Management Terminal Channel Local Loop-Around Test (continued) Error Code Test Result Description / Recommendation PASS The serial interface circuitry on the PN’s Maintenance circuit pack which controls the PN-connected terminal is functioning properly. If there are still troubles with the PN G3-MT terminal, the problem may be one of the following: 1. The PN-connected terminal is not configured properly.
PAGE 1499
MAINT (PN’s Maintenance Circuit Pack) Table 538: Test #229 Serial Channel Local Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2033 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1500
Communication Manager Maintenance-Object Repair Procedures Table 538: Test #229 Serial Channel Local Loop-Around Test (continued) Error Code Test Result Description / Recommendation PASS The on-board circuitry associated with both Expansion Interface circuit pack serial links is good. If there is still a problem communicating with the PN’s Maintenance circuit pack, check the following: 1.
PAGE 1501
MAINT (PN’s Maintenance Circuit Pack) Table 539: Test #303 PN’s Maintenance Circuit Pack Sanity Maze Test (continued) Error Code Test Result Description / Recommendation 2033 ABRT Response to the test was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. FAIL The Sanity Maze of the PN’s Maintenance circuit pack is defective. 1. Replace the PN’s Maintenance circuit pack.
PAGE 1502
Communication Manager Maintenance-Object Repair Procedures Table 540: Test #306 PN Maintenance Circuit Pack Reset Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test disabled via software patch. 2029 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 1204 1205 FAIL EI circuit pack could not reset the PN’s Maintenance circuit pack.
PAGE 1503
MAINT (PN’s Maintenance Circuit Pack) Table 540: Test #306 PN Maintenance Circuit Pack Reset Test (continued) Error Code Test Result Description / Recommendation 3. Replace the PN’s Maintenance circuit pack, and run the test again. If the test passes, the problem is with the Maintenance circuit pack. Interchange the PNC by entering reset pnc interchange, and run the test again. The test should pass with both EI circuit packs being active. 1205 (cont’d) 4.
PAGE 1504
Communication Manager Maintenance-Object Repair Procedures Table 540: Test #306 PN Maintenance Circuit Pack Reset Test (continued) Error Code Test Result Description / Recommendation PASS The active EI circuit pack can reset the PN’s Maintenance circuit pack. This implies the Maintenance circuit pack, the active EI circuit pack, and active serial link are sane. There could still be a problem with the standby EI circuit pack and standby serial link in a Duplication Option system.
PAGE 1505
MAINT (PN’s Maintenance Circuit Pack) Table 541: TEST #303 PN Maintenance Circuit Pack Sanity Maze Test (continued) Error Code Test Result Description/ Recommendation FAIL The hardware vintage of the PN’s Maintenance circuit pack does not support battery holdover for all carriers. This failure indicates that the cabinet administration is set for battery holdover for all carriers. 1.
PAGE 1506
Communication Manager Maintenance-Object Repair Procedures Table 542: Test #337 PN Maintenance Circuit Pack Serial Link Test (continued) Error Code Test Result 2500 Description / Recommendation Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. FAIL The serial link between the currently standby EI or standby IPSI circuit pack and the PN’s Maintenance circuit pack is defective. If the standby EXP-INTF or IPSI is on Carrier A, then error type 3329 is logged.
PAGE 1507
MAINT (PN’s Maintenance Circuit Pack) However, when the repeat option is used, the results for Test #115 come back immediately and, for each test that passed, the CPAD is kept on for one minute. The CPAD does not go off after the PASS result and then come back on for a repeat. Instead, the CPAD is kept on continuously for the entire time. If the CPAD is being activated and deactivated in a flickering fashion, there is a problem with either the CPAD or a PN’s Maintenance circuit pack.
PAGE 1508
Communication Manager Maintenance-Object Repair Procedures MAPD-BD (MAPD Interface Circuit Pack TN802) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MAPD-BD MAJ test board location sh MAPD Interface circuit pack MAPD-BD MIN test board location l MAPD Interface circuit pack MAPD-BD WRN test board location sh MAPD Interface circuit pack The TN802 Multiple Application Platform (MAP-D) circuit pack allows sending voice and fax from a Communica
PAGE 1509
MAPD-BD (MAPD Interface Circuit Pack TN802) Table 544: IP trunk feature/performance limitations on page 1509 describes the feature limitations for S8700 Media Server. Table 544: IP trunk feature/performance limitations Feature/ Performance Description Recommendation Abbreviated Dialing Abbreviated Dial strings with embedded pauses lose digits after the pause Most calls work. Do not create Abbreviated dial strings with embedded pauses.
PAGE 1510
Communication Manager Maintenance-Object Repair Procedures Table 544: IP trunk feature/performance limitations (continued) Feature/ Performance Description Recommendation ISDN IP trunking has no signalling capability. ISDN not supported. This includes: Voice mail Calls that have terminated at one location and then cover to a second site for voice mail coverage can have voice quality degradation.
PAGE 1511
MAPD-BD (MAPD Interface Circuit Pack TN802) Table 545: Backing up TN802 administration data (continued) Step Description Comments 5. Wait Backup can take as much as 20 minutes to complete. 6. Release circuit pack At the S8700 Media Server terminal, type release board location (the address of the TN802 circuit pack), and press Enter.
PAGE 1512
Communication Manager Maintenance-Object Repair Procedures PSTN Fallback Public Switched Telephone Network (PSTN) fallback is available on the Internet trunk application software, which periodically pings the remote destinations that the software calls. When the far end returns a poor response time to the ping, ARS or AAR network routing patterns bypass those ports and direct the call to another port, typically on a PSTN trunk.
PAGE 1513
MAPD-BD (MAPD Interface Circuit Pack TN802) Figure 84: TN802 faceplate 1 2 3 4 5 fpdfmapd KLC 030899 Figure notes: 1. LCD display (see Table 547: TN802 LCD messages for IP trunks on page 1513) 4. PCMCIA card slot 2. Reset button (recessed) 5. Amber PCMCIA disk-in-use LED 3. Red board-status LED Table 547: TN802 LCD messages for IP trunks on page 1513 lists the TN802 LCD messages that you might see if installing or servicing an IP Trunk.
PAGE 1514
Communication Manager Maintenance-Object Repair Procedures Table 547: TN802 LCD messages for IP trunks (continued) Display Explanation IML DWN # Internal error on the IP Trunk. System shuts down and sends an error message to the board. MSHUT #, where both MSHUT and # are blinking The system is in the process of shutting down due to a front panel button press. Do not attempt to remove board. MSHUT #, where # is blinking The system has shut down gracefully.
PAGE 1515
MAPD-BD (MAPD Interface Circuit Pack TN802) 5. Click on Details and configure the settings (Table 548: Remote connection settings on page 1515): Table 548: Remote connection settings Field Value Speed 38,400 Parity None (default) Flow Control RTS/CTS Started by Carrier detect (DCD) Ended by Carrier detect (DCD) 6. Click on the new item icon, and the laptop connects to the host pcANYWHERE application on the TN802 circuit pack.
PAGE 1516
Communication Manager Maintenance-Object Repair Procedures S8700 | 8710 / S8500 Directly-Connected Keyboard, Monitor, Mouse You need 2 power sources for the monitor and the modem in order to complete this procedure. The TN802 circuit pack must be booted with a local mouse and keyboard connected to it for these devices to work. 1. Connect the VGA monitor to the VGA connector of the TN802 external cable. 2. Plug the monitor into an AC power receptacle, and turn it on. 3.
PAGE 1517
MAPD-BD (MAPD Interface Circuit Pack TN802) 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. 4. At the command prompt, type ping nnn.nn.nn.nn (the IP address of another computer on the network), and press Enter.
PAGE 1518
Communication Manager Maintenance-Object Repair Procedures 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. Check that the internal cables on the TN802 circuit pack (Notes 4 and 6 in Figure 87: TN802 board assembly and cables (side view) on page 1520) have not worked loose. b. Otherwise, replace the circuit pack. 4.
PAGE 1519
MAPD-BD (MAPD Interface Circuit Pack TN802) Board Assembly and Cables Figure 86 shows the circuit pack with the two additional boards connected through the side plane. Figure 86: TN802 board assembly 1 2 16 4 15 14 13 12 11 10 3 9 8 7 6 5 4 5 indfmap2 KLC 031699 Figure notes: 1. Main TN802 board 4. Side plane 2. Texas Microsystems Inc. (TMI) board 5. SCSA (Signal Computing System Architecture) ribbon cable 3.
PAGE 1520
Communication Manager Maintenance-Object Repair Procedures Figure 87: TN802 board assembly and cables (side view) 1 2 3 5 4 6 cddfmap2 KLC 040699 Figure notes: 1. Main TN802 board 4. SCSA (Signal Computing System Architecture) ribbon cable 2. Side plane 5. Hard drive 3. Analogic board 6. Processor I/O ribbon cable Figure 88: TN802 board assembly and cables (end view) on page 1521 shows the end view of the three boards and interconnecting cables on the TN802.
PAGE 1521
MAPD-BD (MAPD Interface Circuit Pack TN802) Figure 88: TN802 board assembly and cables (end view) 1 4 2 ckdfmap3 KLC 040699 3 Figure notes: 1. Analogic board 3. SIMMs (memory)1 2. TMI (Texas Microsystems Inc.) board 4. SCSA (Signal Computing System Architecture) ribbon cable 1. If the board is seated and you hear fast beeping, it means that one of the small boards containing the memory chips is dislodged. Secure the memory board firmly in the receptacle and reseat the circuit pack.
PAGE 1522
Communication Manager Maintenance-Object Repair Procedures Table 549: Replacing the TN802 hard drive (continued) Step Description Comments 5. Replace the circuit pack. Slide the circuit pack into the slot, and lock the latching lever. 6. Wait for initialization. Wait for: ● the circuit pack to reseat (faceplate LEDs light go out). ● Windows 2000 boots (PC BOOT appears on the faceplate LCD). ● IP Trunk application to run (IP TRK # appears on the faceplate LCD).
PAGE 1523
MAPD-BD (MAPD Interface Circuit Pack TN802) Table 550: MAPD (TN802) Error Log entries (continued) Error Type Aux Data 514 (i) Alarm Level On/Off Board 46086 MIN WRN3 ON 769 (j) 46085 MIN WRN3 ON 770 (k) 46096 MIN WRN3 ON 1025 (e) 4363 NPE Audit test (#50) 1281 Any Loss of Signal Alarm Inquiry (#138) MIN WRN3 OFF 1537 (l) 46082 MIN WRN3 ON 1538 (m) Any MIN WRN3 ON 1793 Any Blue Alarm Inquiry test (#139) MAJ MIN WRN3 OFF test board location 2049 Any Red Alarm Inquiry t
PAGE 1524
Communication Manager Maintenance-Object Repair Procedures Table 550: MAPD (TN802) Error Log entries (continued) Error Type Aux Data 3841 (r) 4358 3842 (s) 46097 3843 (t) 46081 3999 (u) Any Associated Test Alarm Level On/Off Board Test to Clear Value None 3 of 3 1. If ports are assigned to the circuit pack, then a minor alarm is raised. If no ports are assigned to the circuit pack, then a warning alarm is raised.
PAGE 1525
MAPD-BD (MAPD Interface Circuit Pack TN802) If the circuit pack is properly administered and the red LED is still on, follow the instructions for LED alarms without Alarm Log entry or with Error Type 1 on page 258. c. Error Type 2: Windows 2000 is down and the system attempts to reset the board. If the reset fails, the board may be bad. 1. Replace the circuit pack. d. Error Type 18: The circuit pack has been busied out. 1. Release the board (release board location). e.
PAGE 1526
Communication Manager Maintenance-Object Repair Procedures j. Error Type 769: Transmit FIFO Underflow (threshold is 3 errors within 10 minutes); the circuit pack cannot find the “end of frame” bit when transmitting a frame to the packet bus. 1. Clear the alarm with: a. busyout board location b. reset board location c. test board location long clear d. release board location 2. If the error recurs within 10 minutes, replace the circuit pack.
PAGE 1527
MAPD-BD (MAPD Interface Circuit Pack TN802) m. Error Type 1538: Hyperactive circuit pack is out-of-service and may exhibit one or more of the following symptoms: ● The common circuit pack tests (for example, Test #50 and/or Test #52) abort with Error Code 2000. ● Port tests on this circuit pack return NO-BOARD. ● A busyout/release of the circuit pack has no effect on test results. ● A list configuration shows that the circuit pack and ports are properly installed.
PAGE 1528
Communication Manager Maintenance-Object Repair Procedures 4098 Bad data 4099 Bad sub-qualifier 4100 State inconsistency 4101 Bad logical link 2 of 2 r. Error Type 3841: The circuit pack detected a transient hardware logic error (for example, program logic inconsistency). This error resolves when no faults are detected for 100 minutes. The value in Aux Data field (4358) indicates the type of hardware problem. s. Error Type 3842: Bad Translation RAM Location Found error.
PAGE 1529
MAPD-BD (MAPD Interface Circuit Pack TN802) Shutting Down NT on the TN802 Before removing the TN802 circuit pack from the carrier, shut Windows NT down first by following either procedure described in Table 551: Windows NT shutdown procedures on page 1529: Table 551: Windows NT shutdown procedures Step Faceplate button PC interface 1. Push the recessed button on the front faceplate and hold it in. Click on the Start button in the lower left corner. 2.
PAGE 1530
Communication Manager Maintenance-Object Repair Procedures Order of Investigation D/ND2 Apply to TN802?1 Short Test Sequence Long Test Sequence Red Alarm Inquiry test (#140) N X X ND Yellow Alarm Inquiry test (#141) N X X ND Major Alarm Inquiry test (#142) N X X ND Minor Alarm Inquiry test (#143) N X X ND Slip Alarm Inquiry test (#144) N X X ND Misframe Alarm Inquiry test (#145) N X X ND Translation Update test (#146) N X X ND SAKI Sanity test (#53) Y Reset Board S
PAGE 1531
MAPD-BD (MAPD Interface Circuit Pack TN802) Table 552: Test #50 NPE Connection Audit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct. Execute add ds1 location to administer the MAPD interface if it is not already administered.
PAGE 1532
Communication Manager Maintenance-Object Repair Procedures Control Channel Loop-Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 553: Test #52 Control Channel Loop-Around Test Error Code Test Result Description / Recommendation None 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1533
MAPD-BD (MAPD Interface Circuit Pack TN802) 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 location. Table 554: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry reset board at 1-minute intervals up to 5 times. 1015 ABRT Port is not out-of-service. 1.
PAGE 1534
Communication Manager Maintenance-Object Repair Procedures Loss of Signal Alarm Inquiry Test (#138) This test is meaningless for the TN802 MAPD circuit pack. Table 555: Loss of Signal Inquiry Test (#138) results Windows 2000 up on the TN802? Then Y Test passes Y Test aborts with ABORT 2000 Error Code. Windows 2000 is not communicating with the angel firmware. N Test aborts with ABORT 2000 Error Code. Windows 2000 down.
PAGE 1535
MAPD-BD (MAPD Interface Circuit Pack TN802) Red Alarm Inquiry Test (#140) This test is meaningless for the TN802 MAPD circuit pack. Table 557: Red Alarm Inquiry Test (#140) results If Windows 2000 is up on the TN802 When the switch confirms Red alarm: Y Test passes N Test aborts with ABORT 2000 Error Code. Yellow Alarm Inquiry Test (#141) This test is meaningless for the TN802 MAPD circuit pack.
PAGE 1536
Communication Manager Maintenance-Object Repair Procedures Minor Alarm Inquiry Test (#143) This test is meaningless for the TN802 MAPD circuit pack. Table 560: Minor Alarm Inquiry Test (#142) results If Windows 2000 is up on the TN802 When the switch confirms Minor alarm: Y Test passes N Test aborts with ABORT 2000 Error Code. Slip Alarm Inquiry Test (#144) This test is meaningless for the TN802 MAPD circuit pack. Note: Note: The query for slips always returns a 0 count.
PAGE 1537
MAPD-BD (MAPD Interface Circuit Pack TN802) Translation Update Test (#146) The Translation Update test sends the circuit pack-level information to the MAPD Interface circuit pack.
PAGE 1538
Communication Manager Maintenance-Object Repair Procedures Table 563: Test #146 Translation Update Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1539
MEDPRO (Media Processor MAPD Circuit Pack) MEDPRO (Media Processor MAPD Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MEDPRO MAJ test board location sh Media Processor MAPD circuit pack MEDPRO MIN test board location l Media Processor MAPD circuit pack MEDPRO WRN test board location sh Media Processor MAPD circuit pack The TN802B MedPro circuit board provides voice over IP connectivity.
PAGE 1540
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 564: Media Processor MAPD Circuit Pack Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test board location 1 (b) 0 Circuit pack removed or SAKI (#53) MIN WRN1 ON 18 (c) 0 busyout board location WRN OFF release board location 23 (d) 0 WRN OFF add ip-interface board location 125 (e) None Non
PAGE 1541
MEDPRO (Media Processor MAPD Circuit Pack) Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description, and follow its procedures. b. Error Type 1: the circuit pack stopped functioning or is not fully administered. The alarm is logged approximately 15 minutes after the circuit pack has been removed or 11-minutes after the SAKI test (#53) fails.
PAGE 1542
Communication Manager Maintenance-Object Repair Procedures e. Error Type 125: No Aux Data: The wrong circuit pack is inserted in the slot where this circuit pack is logically administered. ● Remove the wrong circuit pack and insert the logically administered circuit pack or ● Re-administer this slot to match the circuit pack inserted (change circuit-pack). f. Error Type 257: Associated with the Common Port circuit pack maintenance test.
PAGE 1543
MEDPRO (Media Processor MAPD Circuit Pack) Order of Investigation Reset Board Sequence D/ND1 Short Test Sequence Long Test Sequence IP Address Query (#1371) X X D NIC Query test (#1383) X X ND PING test (#1379) X X ND Windows 2000 Reset (#1381) X D 2 of 2 1. D = Destructive; ND = Nondestructive Control Channel Loop-Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage, and verifies its records.
PAGE 1544
Communication Manager Maintenance-Object Repair Procedures Table 565: Test #52 Control Channel Loop-Around Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct. Administer the MedPro interface if it is not already administered. 2.
PAGE 1545
MEDPRO (Media Processor MAPD Circuit Pack) Table 566: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1015 ABRT Port is not out-of-service. 1. Busyout the circuit pack. 2. Execute command again. 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1546
Communication Manager Maintenance-Object Repair Procedures IP Address Query Test #1371 This test is destructive. A Media Processor has two administration interfaces: ● SAT interface using CCMS messages ● Windows 2000 PC interface However, the Windows 2000 PC interface allows changes that cause the Media Processor board to be inconsistent with Communication Manager translations (including the IP address, subnet mask, and gateway translation).
PAGE 1547
MEDPRO (Media Processor MAPD Circuit Pack) Ping Test (#1379) This test is a nondestructive test. It runs because of in-line errors, during periodic and scheduled maintenance, and on demand. This test verifies that the MedPro circuit pack can communicate to other nodes on the LAN by pinging the gateway IP address as defined on the IP Interfaces screen (display ip-interface location). If the PING is successful, this test looks at the PING round trip delay.
PAGE 1548
Communication Manager Maintenance-Object Repair Procedures Table 568: Test #1379 Ping Test (continued) Error Code Test Result Description / Recommendation 2801 ABRT No IP address defined. 1. Verify IP Interfaces translations and retest. 2802 ABRT Different IP address pinged than software had allocated for the test. 1. Retry the command at 1-minute intervals up to 3 times. 2805 FAIL The number of pings received did not match the number sent (normally one ping sent).
PAGE 1549
MEDPRO (Media Processor MAPD Circuit Pack) Table 569: Test #1381 NT Reset Test (continued) Error Code Test Result Description / Recommendation 1015 ABRT Port is not out-of-service. 1. Busyout the circuit pack (busyout board location). 2. Execute reset board location. 2100 ABRT System resources required for this test are not available. 1. Retry reset board location at 1-minute intervals up to 5 times. 1 FAIL The circuit pack failed to reset. 2 FAIL The circuit pack failed to restart. 1.
PAGE 1550
Communication Manager Maintenance-Object Repair Procedures NIC Query Test (#1383) This test is nondestructive. The 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 570: Test #1383 NIC Query Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1015 ABRT Port is not out-of-service. 1.
PAGE 1551
MEDPRO-C (Media-Processor Control) MEDPRO-C (Media-Processor Control) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run MEDPRO-C This MO is not hardware-based, there will be no alarms, commands to run, or tests to clear. Events appear in display event logs. Full Name of MO Media-Processor Control The TN2602AP IP Media Resource 320 provides high-capacity voice over Internet protocol (VoIP) audio access to the switch for local stations and outside trunks.
PAGE 1552
Communication Manager Maintenance-Object Repair Procedures ● Be physically inserted into the correct slot If the circuit pack has an entry on the circuit pack screen and any of the other conditions are not met, a MINOR alarm is logged. To resolve the error: ● Make sure every condition for administration is met, and that a functioning Media Resource is inserted in the correct slot. ● Completely remove the IP Media Resource from the system: a.
PAGE 1553
MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MEDPROPT MIN WRN test port location [short/ long] [repeat#] | [clear] TN802/TN2302/TN2602 MEDPRO DSP PORT The Media Processor Port (MEDPROPT) MO monitors the health of the Media Processor (MEDPRO) digital signal processors (DSPs).
PAGE 1554
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 572: MEDPROPT Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test board location 1 (b) Any DSP Capacity test (#1382) ON test board location l r 5 18 (c) 0 busyout port location WRN OFF release port location 258 (d) Any DSP Capacity test (#1382) WRN ON test board location l r 5 DSP Capacity test (#1382
PAGE 1555
MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) f. Error Type 515: For the TN802B only, this error type indicates that every DSP is OOS (out of service), and a MINOR alarm is raised. The Aux Data field contains the number of DSPs that are OOS. g. Error Type 1025: The port is OOS (out of service) because of a board-level failure. Check for errors/alarms against the board, in particular ping problems, IP address inconsistency, or board sanity problems. 1. Verify correct administration. 2.
PAGE 1556
Communication Manager Maintenance-Object Repair Procedures For the TN2302 and TN2602 When using the TN2302 or TN2602, this test polls the circuit pack for the state of health of a specific DSP. If the DSP is bad, an error will be logged and the board will be polled again. If the circuit pack is still failing, the DSP will be taken out of service and a MINOR alarm will be raised. Table 573: DSP Query Test (#1382) Error Code Test Result Description / Recommendation 1014 ABRT Board not inserted.
PAGE 1557
MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) DSP Port TDM 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. The tone generator places a test tone (440Hz) onto a timeslot. The timeslot is listened to by the Media Processor board.
PAGE 1558
Communication Manager Maintenance-Object Repair Procedures Table 574: DSP PORT TDM Loop-Around Test (#1380) (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1559
MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) DSP Port Status Query Test (#1407) This test is nondestructive. This test queries the state of the DSP port. Table 575: DSP Port Status Query Test (#1407) Error Code Test Result Description / Recommendation 1 ABRT 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 1560
Communication Manager Maintenance-Object Repair Procedures MET-BD (MET Line Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MET-BD MIN test board location sh MET Line circuit pack MET-BD WRN test board location sh MET Line circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors. See also MET-LINE (MET Line) Maintenance documentation for related line information.
PAGE 1561
MET-LINE (MET Line) MET-LINE (MET Line) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MET-LINE MIN test port location l MET Line MET-LINE WRN test port location sh MET Line The TN735 MET Line circuit pack supports four Multibutton Electronic Telephone (MET) station sets. Each MET set uses three pairs of wires: an analog voice pair, a transmit pair, and a receive pair. Power is sent over the transmit and receive pairs.
PAGE 1562
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 576: MET Line Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 40987 None 18 (c) 0 busyout port location WRN OFF release port location None WRN ON test port location sh 130 (d) 257 (e) 40988 None MIN WRN1 OFF 513 (f) 40965 Hybrid Line Station Audits (#61) WRN OFF te
PAGE 1563
MET-LINE (MET Line) b. Error Type 1: the data link between the port and the terminal is not operational (that is, the port circuitry has detected an off-board problem). Verify that the MET set is connected and that the EPF (Electronic Power Feed) test passes. If data transmission problems are experienced, check for defective wiring or a defective voice terminal, or move terminal electrically closer to the switch (that is, reduce the length of the wiring between the terminal and the switch).
PAGE 1564
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1565
MET-LINE (MET Line) Table 578: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension of the port. Use status station to determine the service state of the port. If the port is in use, wait until the port is idle before testing. 2.
PAGE 1566
Communication Manager Maintenance-Object Repair Procedures Table 578: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT Test disabled by administration. This only applies to analog stations. The default for this field is y, so you may want to determine why it was turned off on this station. 1. To enable the test for the particular analog station being tested, enter change station extension and set the Test field on the Station screen to y.
PAGE 1567
MET-LINE (MET Line) Table 578: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config and resolve any problems that are found. 2.
PAGE 1568
Communication Manager Maintenance-Object Repair Procedures Table 579: Test #35 Port Diagnostic Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension of the port. Use status station to determine the service state of the port. If the port is in use, wait until the port is idle before testing. 2.
PAGE 1569
MET-LINE (MET Line) Table 579: Test #35 Port Diagnostic Test (continued) Error Code Test Result Description / Recommendation FAIL Battery Feed test failed. This port is out-of-service. 1. Other ports on this circuit pack are not affected. Place user on a different port, if available, until a replacement circuit pack can be obtained. 2. Replace circuit pack when available. PASS Battery Feed test passed. Current flow is properly detected for this port. 1.
PAGE 1570
Communication Manager Maintenance-Object Repair Procedures Table 580: Test #56 MFAT Electronic Power Feed Test Error Code Test Result Description / Recommendation ABRT The test was aborted due to an internal system error on a software request to the board. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension of the port.
PAGE 1571
MET-LINE (MET Line) Table 580: Test #56 MFAT Electronic Power Feed Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config and resolve any problems that are found. 2.
PAGE 1572
Communication Manager Maintenance-Object Repair Procedures Table 581: Test #57 Hybrid Circuit and Conference Circuit Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension of the port.
PAGE 1573
MET-LINE (MET Line) Table 581: Test #57 Hybrid Circuit and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2012 ABRT Internal system error. 2103 ABRT The system could not make the conference connection for the test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1574
Communication Manager Maintenance-Object Repair Procedures Table 581: Test #57 Hybrid Circuit and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 57 FAIL Hybrid Circuit test failed. This can result in noisy or bad connections. 1. Run circuit pack tests to check the Tone Generator circuit pack and the Tone Detector circuit pack, using test board location short. 2.
PAGE 1575
MET-LINE (MET Line) 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. Table 582: Test #60 MET Line Station Lamp Updates Test Error Code Test Result Description / Recommendation 1 ABRT This port may have been busied out. 1. Look in the Error Log for Error Type 18 (port busied out) for this port.
PAGE 1576
Communication Manager Maintenance-Object Repair Procedures Table 582: Test #60 MET Line Station Lamp Updates Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config and resolve any problems that are found. 2.
PAGE 1577
MET-LINE (MET Line) Table 583: Test #61 MET Line Station Audits Test Error Code 1 Test Result Description / Recommendation ABRT Internal system error ABRT The test was aborted due to an internal system error during the switchhook audit. 2 The test was aborted due to an internal system error during the bad scan inquiry. 3 The test was aborted due to an internal system error during the EPF audit inquiry. 1. Make sure that the station is not in an out-of-service state. 2.
PAGE 1578
Communication Manager Maintenance-Object Repair Procedures Table 583: Test #61 MET Line Station Audits Test (continued) Error Code Test 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 1579
MET-LINE (MET Line) 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 584: Test #62 MET Line Ringer Update Test Error Code Test Result Description / Recommendation 3 ABRT This port may have been busied out. 1. Look in the Error Log for Error Type 18 (port busied out) for this port. If present, release the port using release station extension and run the test again. 2.
PAGE 1580
Communication Manager Maintenance-Object Repair Procedures Table 584: Test #62 MET Line Ringer Update Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port. This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config and resolve any problems that are found. 2.
PAGE 1581
MED-GTWY (MEDIA GATEWAY) MED-GTWY (MEDIA GATEWAY) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MED-GTWY MAJ test board location MEDIA GATEWAY The MEDIA GATEWAY maintenance object monitors the H.248 link to the Avaya G700 Media Gateway. It logs errors when the Keep Alive messages that are exchanged between the server and G700 fail. These messages indicate the status of the H.248 link between the two.
PAGE 1582
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Short Test Sequence Long Test Sequence D/ND1 link audit (#1527) X X ND board audit (#1586) X X ND Order of Investigation 1. D = Destructive; ND = Nondestructive test media-gateway nn Test #1527 - Link Audit. This test verifies the Media Gateway H.248 link state and alarm state.
PAGE 1583
MG-ANA (ANALOG MM711) MG-ANA (ANALOG MM711) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log For Location Full Name of MO MG-ANA GGGVSPP ANALOG MEDIA MODULE Consult local records for the location and designation of the equipment rack where the G700 is mounted. Note: Note: For more information, refer to XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 of this document. In addition, refer to AN-LN-PT (Analog Line Port) on page 426 and to CO-TRK (Analog CO Trunk) on page 835.
PAGE 1584
Communication Manager Maintenance-Object Repair Procedures Analog modems are supported on the G700 only in limited configurations, in which the modem call stays within a single Media Gateway. If the modem is connected to an MM711 Analog Media Module, and the call goes to either ● Another modem on an MM711 within the same Media Gateway. or ● The PSTN through an analog, T1/E1, or BRI trunk on the same Media Gateway, the call will succeed.
PAGE 1585
MG-ANN (Voice Announcements) MG-ANN (Voice Announcements) S8700 | 8710 / S8500 / S8300 / G700 Voice Announcements over the LAN The MG-ANN (Voice Announcements) maintenance object provides per board announcement storage time of up to 20 minutes (15 playback ports and 1 recording port that can also be used as a playback port), and allows for announcement file portability via LAN connectivity. MG-ANN also allows for LAN backup and restore of announcement files and the use of customer provided waveform (.
PAGE 1586
Communication Manager Maintenance-Object Repair Procedures MG-BRI (BRI Trunk Media Module MM720) S8700 | 8710 / S8500 / S8300 / G350 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MG-BRI MIN test board location MO_MG_BRI The MM720 BRI Media Module contains eight ports that can be administered either as BRI trunk connections or BRI endpoint (telephone and data module) connections.
PAGE 1587
MG-BRI (BRI Trunk Media Module MM720) ISDN Interface Reference Points Figure 89: Integrated Trunk-Side BRI, ISDN Interface Reference Points on page 1588 shows, for a generic integrated trunk-side BRI, the ISDN Interface Reference Points. Table 587: ISDN Interface Reference Point definitions on page 1588 gives definitions for the generic ISDN Interface Reference Points.
PAGE 1588
Communication Manager Maintenance-Object Repair Procedures Figure 89: Integrated Trunk-Side BRI, ISDN Interface Reference Points PBX CO V S NT2 TE 4-Wire PRI 1 S R NT2 U LT NT1 NT 2-Wire 4-Wire 2 T TE NT 4-Wire NT2 3 LT S/T NT1 NT 2-Wire NT2 NT 4-Wire U NT1 TE U LT 4 Terminal Adapter T NT 2-Wire S/T T NT 2-Wire TE TE 5 PBX ISDN Interface Reference Points cydfisdn RPY 072397 Table 587: ISDN Interface Reference Point definitions LT Logical Terminal V Primary Rate user/n
PAGE 1589
MG-BRI (BRI Trunk Media Module MM720) Table 587: ISDN Interface Reference Point definitions (continued) U Basic Rate network-side 2-wire line interface. 1 TN556B ISDN-BRI 4-Wire S/T-NT Line (A-law) 2 TN 2185 ISDN-BRI 4-Wire S Interface (Trunk Side) 3 TN2198 ISDN-BRI 2-Wire U Interface 4 TN2198 ISDN-BRI 2-Wire U Interface 5 TN 2185 ISDN-BRI 4-Wire S Interface (Trunk Side) 2 of 2 1. Network Termination 2 (NT2), that terminates Layer 1 and higher layers.
PAGE 1590
Communication Manager Maintenance-Object Repair Procedures Table 588: MG-BRI Error Log Entries and Test to Clear Values (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 1291 (g) 4359 Clear Error Counters (#270) MIN ON MIN OFF 3586 (h) 3840 (i) 4096 to 4101 3842 (j) 46095 3843 (k) 46097 Test to Clear Value 2 of 2 Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence.
PAGE 1591
MG-BRI (BRI Trunk Media Module MM720) e. Error Type 769: the circuit pack detects a program logic error. While no action is required, this error can lead to other errors against this circuit pack. f. Error Type 1025: 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. g.
PAGE 1592
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence. Short Test Sequence Long Test Sequence D/ND1 X X ND NPE/NCE Audit Test (#50).
PAGE 1593
MG-DCP (Digital Line Media Module) MG-DCP (Digital Line Media Module) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MG-DCP MIN test board location sh Digital Line Media Module MG-DCP WRN test board location sh Digital Line Media Module DIG-LINE maintenance monitors and tests ports on digital line Media Modules and the hardware connected to those ports for lines administered as a digital station.
PAGE 1594
Communication Manager Maintenance-Object Repair Procedures MG-DS1 (DS1 Interface Media Module) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MG-DS1 MAJ test board location sh DS1 Interface Media Module MG-DS1 MIN test board location l DS1 Interface Media Module MG-DS1 WRN test board location sh DS1 Interface Media Module MM710 DS1 Media Module The MM710 Universal DS1 Interface Media Module provide an interface to the DS1 facilit
PAGE 1595
MG-DS1 (DS1 Interface Media Module) Echo Cancellation The MM710 Media Module features an integrated echo canceller. Echo cancellation supports channels carrying voice and is not intended for channels that support data. The MM710 has the capability to detect modem tone and turn off echo cancellation accordingly for the duration of a data call. Echo cancellation on the MM710 will be administrable per channel. The echo cancellation circuitry on a given MM710 is driven by administrable parameters.
PAGE 1596
Communication Manager Maintenance-Object Repair Procedures Echo cancellation on the MM710 is selectable per channel, even though it is administrable on a trunk group basis. For example, if all but two ports on a MM710 need to have echo cancellation applied, those two ports must be put in a trunk group where the DS1 Echo Cancellation field is set to n. The remaining ports will be in a trunk group(s) where the DS1 Echo Cancellation field is set to y.
PAGE 1597
MG-DS1 (DS1 Interface Media Module) Table 589: DS1 Interface Media Module Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 125 (e) none 3 None MIN WRN1 ON 257 65535 Control Channel Loop (#52) MIN ON 257 (f) Any None 513 (g) Any MIN WRN1 ON 514 (h) 46086 MIN WRN1 ON 769 (i) 46085 MIN WRN1 ON 770 (j) 46096 MIN WRN1 ON 1281 Any Loss of Signal Alarm Inquiry Test (#138) MIN WRN1 OFF test board locat
PAGE 1598
Communication Manager Maintenance-Object Repair Procedures Table 589: DS1 Interface Media Module Maintenance Error Log Entries (continued) Error Type Aux Data 1538 (m) Any 1793 Any 1794 Alarm Level On/Off Board MMIN WRN1 ON Blue Alarm Inquiry (#139) MAJ MIN WRN2 OFF test board location Any Blue Alarm Inquiry (#139) MAJ MIN WRN2 OFF test board location 1795 Any Blue Alarm Inquiry (#139) MAJ MIN WNG2 OFF test board location 2049 Any Red Alarm Inquiry (#140) MIN WRN1 OFF test bo
PAGE 1599
MG-DS1 (DS1 Interface Media Module) Notes: a. Error Type 0: run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. b. Error Type 1: the Media Module has totally stopped functioning or is not fully administered. The alarm is logged about 15 minutes after the Media Module has been removed or 11-minutes after the SAKI Test (#53) fails.
PAGE 1600
Communication Manager Maintenance-Object Repair Procedures f. Error Type 257: associated with the Common Port Media Module Maintenance Test. Refer to XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 Maintenance documentation for details. g. Error Type 513: the MG-DS1 (MM710) has detected a transient hardware problem.
PAGE 1601
MG-DS1 (DS1 Interface Media Module) Echo Cancellation is no longer being supplied by the board. Clear the alarm using the following commands: busyout board location, test board location long, release board location. If Test #1420 (Echo Canceler Test) fails, replace the Media Module. l. Error Type 1537: is a LAN Bus Timeout Error. This error occurs when the Media Module transmits too many bytes on the LAN bus for a single frame.
PAGE 1602
Communication Manager Maintenance-Object Repair Procedures p. Error Type 3840: is not service-affecting. No action is required. These errors are reported by the Media Module when it receives a bad control channel message from the switch. The Aux Data identifies the following error events: Aux Data Event 4096 Bad major heading 4097 Bad port number 4098 Bad data 4099 Bad sub-qualifier 4100 State inconsistency 4101 Bad logical link q.
PAGE 1603
MG-DS1 (DS1 Interface Media Module) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order they are presented. By clearing Error Codes associated with the Echo Cancellation Test you may also clear errors generated from other tests in the sequence.
PAGE 1604
Communication Manager Maintenance-Object Repair Procedures Control Channel Looparound Test (#52) This test queries the Media Module for its Media Module vintage to verify angel communication. Table 590: Test #52 Control Channel Looparound Test Error Code Test Result Description/ Recommendation None 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times.
PAGE 1605
MG-DS1 (DS1 Interface Media Module) SAKI Sanity Test (#53) ! CAUTION: CAUTION: This test resets the Media Module. The test is highly destructive and can only be initiated by a system technician-demanded reset board location command. Table 591: Test #53 SAKI Sanity Test Error Code Test Result Description/ Recommendation None ABRT System resources required for this test are not available. 1. Retry the reset board command at 1-minute intervals a maximum of 5 times.
PAGE 1606
Communication Manager Maintenance-Object Repair Procedures Table 591: Test #53 SAKI Sanity Test (continued) Error Code Test Result Description/ Recommendation PASS The Media Module initializes correctly. 1. Run the Short Test Sequence. Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1607
MG-DS1 (DS1 Interface Media Module) Echo Cancellation If the MM710 firmware detects a serious echo canceller hardware error, it notifies maintenance software. When the maintenance subsystem receives notification of the echo cancellation error, it executes this Loss Of Signal Alarm Inquiry test. This test, in addition to querying for a loss of signal condition and CSU errors, also queries MM710 to confirm the echo canceller error. A minor alarm is raised if the error is confirmed.
PAGE 1608
Communication Manager Maintenance-Object Repair Procedures Table 592: TEST #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 2000 ABRT 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 1609
MG-DS1 (DS1 Interface Media Module) Table 592: TEST #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation FAIL MM710 detects a Loss of Signal alarm. The physical link is broken or the remote DS1 endpoint is down. All trunks or ports of this MM710 are out-of-service. 1. Check the physical connection of the MM710 Interface Media Module and the cable. 2. Check the physical connection of the MM710 Interface Media Module to the terminating device. 3.
PAGE 1610
Communication Manager Maintenance-Object Repair Procedures Table 592: TEST #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1611
MG-DS1 (DS1 Interface Media Module) Line Loopback Alarm The Line Loopback (LLB) is used by the remote DS1 endpoint to put the DS1 board into a loopback mode. When the DS1 board is in the LLB mode, the arriving bit pattern is regenerated and sent back. The Line Loopback (LLB) Alarm activates when the in-band activate LLB bit pattern arrives continuously for 5 seconds on the DS1 line. The LLB deactivates when the in-band deactivate LLB bit pattern arrives continuously for 5 seconds on the DS1 line.
PAGE 1612
Communication Manager Maintenance-Object Repair Procedures Table 593: TEST #139 Blue Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 2000 ABRT 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 1613
MG-DS1 (DS1 Interface Media Module) Table 593: TEST #139 Blue Alarm Inquiry Test (continued) Error Code 1 1794 Test Result Description/ Recommendation FAIL The remote DS1 endpoint is out-of-service. FAIL The MM710 Interface Media Module detects a Line Loopback Alarm (LLB). 1. If the DS1-M interface Media Module connects to a T1 facility, call the vendor of the T1 carrier to diagnose the remote DS1 endpoint. 2.
PAGE 1614
Communication Manager Maintenance-Object Repair Procedures Table 593: TEST #139 Blue Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1615
MG-DS1 (DS1 Interface Media Module) Loss of Multiframe Alarm If the MM710 Interface Media Module is administered using DMI-BOS signaling, the MM710 Interface Media Module raises a Loss of Multiframe Alarm (LMA) when it cannot interpret the incoming signaling bits to synchronize to the multiframe pattern received in the 24th channel. Once the MM710 Interface Media Module detects an LMA, the Media Module transmits a Remote Multiframe Alarm (RMA) to the remote DS1 endpoint.
PAGE 1616
Communication Manager Maintenance-Object Repair Procedures Table 594: TEST #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation FAIL The MM710 interface Media Module detected a red alarm. An out of frame condition occurred on the MM710 interface Media Module. The MM710 interface Media Module will transmit a yellow alarm to the remote MM710 endpoint until the red alarm is retired.
PAGE 1617
MG-DS1 (DS1 Interface Media Module) Table 594: TEST #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 FAIL The test failed. The MM710 interface Media Module detected a loss of multiframe alarm (LMA). An out of frame condition occurred on the MM710 interface Media Module. The MM710 interface Media Module will transmit a remote multiframe alarm (RMA) to the remote MM710 endpoint until the LMA is retired.
PAGE 1618
Communication Manager Maintenance-Object Repair Procedures Table 594: TEST #140 Red Alarm Inquiry Test (continued) Error Code Any Test Result Description/ Recommendation PASS No Red alarm is detected on the MM710 Interface Media Module. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1619
MG-DS1 (DS1 Interface Media Module) When the Yellow alarm is cleared, the maintenance software restores all trunks or ports on the MM710 Interface Media Module back to their previous service state before the Yellow alarm was raised. This Yellow alarm corresponds to the yellow F2 state documented in CCITT Recommendation I.431.
PAGE 1620
Communication Manager Maintenance-Object Repair Procedures Table 595: TEST #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 2000 ABRT 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 1621
MG-DS1 (DS1 Interface Media Module) Table 595: TEST #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation FAIL The MM710 interface Media Module detected a yellow alarm sent by the remote DS1 endpoint. An out of frame condition occurred at the DS1 endpoint. If the MM710 connects to a T1 network facility or to another switch, do the following: 1.
PAGE 1622
Communication Manager Maintenance-Object Repair Procedures Table 595: TEST #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 FAIL The MM710 interface Media Module detected a remote multiframe alarm (RMA) sent by the remote DS1 endpoint. An out of frame condition occurred at the DS1 endpoint. If the MM710 connects to a T1 network facility or to another switch, do the following: 1.
PAGE 1623
MG-DS1 (DS1 Interface Media Module) Table 595: TEST #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 2 FAIL The MM710 interface Media Module 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. If the MM710 connects to a T1 network facility: 1.
PAGE 1624
Communication Manager Maintenance-Object Repair Procedures Table 595: TEST #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1625
MG-DS1 (DS1 Interface Media Module) When the Major alarm is cleared, the maintenance software restores all trunks or ports on the Media Module to their previous service state before a Major alarm occurs. Table 596: TEST #142 Major Alarm Inquiry Test Error Code Test Result Description/ Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 2000 ABRT Response to the test was not received within the allowable time period.
PAGE 1626
Communication Manager Maintenance-Object Repair Procedures Table 596: TEST #142 Major Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation FAIL The performance of the DS1 link between the MM710 interface Media Module and the remote DS1 endpoint is very poor. Enter the list measurement ds1-log location command to read the error seconds measurement. If the MM710 connects to a T1 network facility or to another switch, do the following: 1.
PAGE 1627
MG-DS1 (DS1 Interface Media Module) Table 596: TEST #142 Major Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1628
Communication Manager Maintenance-Object Repair Procedures Table 597: TEST #143 Minor Alarm Inquiry Test Error Code Test Result Description/ Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 2000 ABRT 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 1629
MG-DS1 (DS1 Interface Media Module) Table 597: TEST #143 Minor Alarm Inquiry Test (continued) Error Code Test 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. The performance of the DS1 link between the MM710 interface Media Module and the remote DS1 endpoint is poor. Enter the list measurement ds1-log location command to read the error seconds measurement.
PAGE 1630
Communication Manager Maintenance-Object Repair Procedures Table 597: TEST #143 Minor Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1631
MG-DS1 (DS1 Interface Media Module) If the count of slips is over the threshold, a Minor alarm is raised against the MM710 Interface Media Module. All trunks or ports of the MM710 Interface Media Module remain in the in-service state. Table 598: TEST #144 Slip Alarm Inquiry Test Error Code Test Result Description/ Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 2000 ABRT Response to the test was not received within the allowable time period.
PAGE 1632
Communication Manager Maintenance-Object Repair Procedures Table 598: TEST #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 to 88 FAIL The test failed because the MM710 interface Media Module and the remote DS1 endpoint are not synchronized to the same clock rate. The MM710 interface Media Module detected a slip alarm. The Error Code equals the number of slips detected by the MM710 interface Media Module since the last slip alarm inquiry test.
PAGE 1633
MG-DS1 (DS1 Interface Media Module) Table 598: TEST #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 to 88 (cont’d) FAIL (cont’d) If the MM710 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following: 1. Retry the command at 1-minute intervals for a maximum of 5 times. 2. Enter the list measurement ds1-log location command to read the error seconds measurement. 3.
PAGE 1634
Communication Manager Maintenance-Object Repair Procedures Table 598: TEST #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1635
MG-DS1 (DS1 Interface Media Module) A Minor alarm against the MM710 Interface Media Module is raised, but all trunks or ports of the MM710 Interface Media Module remain in the in-service state. Table 599: TEST #145 Misframe Alarm Inquiry Test Error Code Test Result Description/ Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 2000 ABRT Response to the test was not received within the allowable time period. This may be due to hyperactivity.
PAGE 1636
Communication Manager Maintenance-Object Repair Procedures Table 599: TEST #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 to 17 FAIL The test failed because the MM710 interface Media Module detected errors in the received framing bits pattern. The Error Code equals the number of misframes detected by the MM710 interface Media Module since the last misframe alarm inquiry test.
PAGE 1637
MG-DS1 (DS1 Interface Media Module) Table 599: TEST #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation 1 to 17 (cont’d) FAIL If the MM710 connects to a line-side terminating device such as a PRI terminal adapter: 1. Retry the command at 1-minute intervals for a maximum of 5 times. 2. Enter list measurement ds1-log GGGVS to read the error seconds measurement. 3.
PAGE 1638
Communication Manager Maintenance-Object Repair Procedures Table 599: TEST #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description/ Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1639
MG-DS1 (DS1 Interface Media Module) Translation Update Test (#146) The Translation Update Test sends the circuit-pack-level information specified by System Administration to the MM710 Interface Media Module.
PAGE 1640
Communication Manager Maintenance-Object Repair Procedures Echo Canceller Test (#1420) ! CAUTION: CAUTION: This test is executed only for MM710 Media Modules that have been administered on the DS1 Media Module form to provide echo cancellation. The MM710 must be busied out before this demand test is run. This test is for the MM710 Media Module. The test originates from a manually initiated test board long demand test of a MM710 Media Module.
PAGE 1641
MG-DS1 (DS1 Interface Media Module) Table 601: Test #1420 Echo Canceller Test (continued) Error Code Test Result Description/ Recommendation 2000 ABRT 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 1642
Communication Manager Maintenance-Object Repair Procedures Table 601: Test #1420 Echo Canceller Test (continued) Error Code Test Result Description/ Recommendation 1400, 1401 FAIL The Echo Cancellation Test has failed: ● 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 1643
MG-IAMM (Integrated Analog Media Module) MG-IAMM (Integrated Analog Media Module) S8700 | 8710 / S8500 / S8300 - G250 G250-BRI G350 MO Name Alarm Level Initial SAT Command to Run Full Name of MO MG-IAMM MIN test board location l 6-Port Integrated Analog Media Module MG-IAMM WRN test board location sh 6-Port Integrated Analog Media Module The MG-IAMM Maintenance Object represents the Integrated Analog Media Module (IAMM) located on the main board of the G250, G250-BRI and G350 media gateway.
PAGE 1644
Communication Manager Maintenance-Object Repair Procedures G250, G250-BRI, G350 See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for media module level errors. For individual port problems see the relevant MO: ● If the port is administered as a CO trunk, see CO-TRK (Analog CO Trunk) on page 835. ● If the port is administered as a DID trunk, see DID-TRK (Direct Inward Dial Trunk) on page 898. ● If the port is administered as a CAMA/E911 trunk, see DIOD-TRK (DIOD Trunk) on page 964.
PAGE 1645
MG-IAMM (Integrated Analog Media Module) media module or the SAKI Sanity Test fails. NOTE: The IAMM is not removable, this error indicates that there may be a firmware or hardware problem with the media gateway. 1. Reset the Integrated Analog Media Module with the SAT command reset board . Retest the board using the SAT command test board location. 2. If this error persists, replace the media gateway. b.
PAGE 1646
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing error codes associated with one test may also clear errors generated from other tests in the sequence.
PAGE 1647
MG-IAMM (Integrated Analog Media Module) Ringing Application Test (#51) This test is not applicable to media modules and will always abort. Table 604: Test #51 Ringing Application Test Error Code Test Result 1412 ABRT Description / Recommendation 1. This test is not run on media modules and will always abort. Control Channel Loop Test (#52) This test has two parts.
PAGE 1648
Communication Manager Maintenance-Object Repair Procedures SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack or media module. This test is executed as part of the reset board location command. Table 606: Test #53 SAKI Sanity Test Error Code Test Result Description / Recommendation None ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1015 ABRT Port is not out-of-service. 1.
PAGE 1649
MG-IAMM (Integrated Analog Media Module) Flow Control Update Test (#1) This test is not applicable to media modules and will always PASS. Table 607: Test #51 Ringing Application Test Error Code Test Result PASS Description / Recommendation 1. This test is not run on media modules and will always PASS. Neon Test (#220) This test is not applicable to media modules and will always abort. Table 608: Test #51 Ringing Application Test Error Code Test Result 1412 ABRT Description / Recommendation 1.
PAGE 1650
Communication Manager Maintenance-Object Repair Procedures MG-ICC (Internal Call Controller) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MG-ICC MAJ None INTERNAL CALL CONTROLLER This maintenance object monitors the H.323 link between the S8300 Media Server running as an LSP or as the primary call controller. It logs errors when the Keep Alive messages that are exchanged between the servers fail.
PAGE 1651
MG-VOIP (MM760 MED PRO DSP PORT) MG-VOIP (MM760 MED PRO DSP PORT) S8700 | 8710 / S8500 / S8300 / G700 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MG-VOIP MIN WRN test port location [short/long] [repeat#] | [clear] Voice Over IP The MM760 Media Module provides the audio bearer channels for voice over IP calls, and is under control of the G700. One MM760 Media Module has one VOIP-MM media processing resource.
PAGE 1652
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Order of Investigation Short Test Sequence Long Test Sequence D/ND X X Nondestructive Control Channel Loop Test (#52) Control Channel Looparound Test (#52) This test queries the Media Module for its type and vintage to verify angel communication.
PAGE 1653
MG-VOIP (MM760 MED PRO DSP PORT) Table 611: TEST #52 Control Channel Looparound Test (continued) Error Code Test Result Description/ Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 1654
Communication Manager Maintenance-Object Repair Procedures MIS (Management Information System) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MIS WRN release mis Management Information System Use the Management Information System (MIS)/Call Management System (CMS) to monitor MIS busyouts during administration of MIS translations. There are no hardware failures associated with this MO.
PAGE 1655
MMI-BD MMI-BD S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MMI-BD MAJ test board location l r# Multimedia Interface circuit pack MMI-BD MIN test board location l r# Multimedia Interface circuit pack MMI-BD1 WRN test board location s r# Multimedia Interface circuit pack 1. Refer to XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 1656
Communication Manager Maintenance-Object Repair Procedures Figure 90: TN787 Multimedia Interface (MMI) Circuit Pack TN2207/Expansion Services Module The TN2207 circuit pack permits connecting an ESM (Expansion Services Module). See Figure 91: Typical ESM connections on page 1657 for connectivity. ● The TN2207 circuit pack 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.
PAGE 1657
MMI-BD Figure 91: Typical ESM connections 6 1 8 2 3 7 5 4 cydf012 KLC 092801 Figure notes: 1. Port B Y-cable connector to a TN787 MMI (Multimedia Interface) circuit pack 5. D8W cord connected to 356A adapter port 1 2. Port A Y-cable connector to a TN2207 PRI circuit pack 6. Expansion Service Module (ESM) 3. 25-pair Y-cable 7. Port B on compatible PRI (primary rate interface) card 4.
PAGE 1658
Communication Manager Maintenance-Object Repair Procedures Table 613: MMI-BD Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 257 (e) 65535 Control Channel Loop test (#52) MIN ON test board location r 3 513 (f) 4352 to 4357 Uplink error from circuit pack 769 (g) Any MMI Synchronization Status (#1123) 1281 (h) Any Circuit Pack Restart test (#594) MAJ ON 1538 (i) Any Software detected error MIN ON 1793 (j) Any TSI XTa
PAGE 1659
MMI-BD f. Error Type 513: the circuit pack detected an Angel on-board hardware failure. The reported Aux Data values correspond to the following detected errors: 4352 — External RAM error 4253 — Internal RAM error 4355 — ROM Checksum error 4357 — Instruction set error Use busyout board location, reset board location, and release board location. When reset, the circuit pack executes a set of tests to detect the presence of any of the above faults.
PAGE 1660
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Code Investigate tests in the order presented when inspecting errors in the system. By clearing Error Codes associated with the first test, you may also clear errors generated from other tests in the sequence.
PAGE 1661
MMI-BD Table 614: Test #6 TSI Crosstalk Test Error Code Test Result Description / Recommendation ABRT Internal system error. This is an abnormal abort. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 1662
Communication Manager Maintenance-Object Repair Procedures 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. If the digital count is correct, then the test passes. The test is done for both TDM buses. Failures indicate that the TSI is unreliable.
PAGE 1663
MMI-BD Table 615: Test #1108 TSI Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary resources to run this test. This is an abnormal abort. 1. Retry the command at 1-minute intervals up to 5 times. FAIL The TSI was found to be transmitting in error, causing noisy and unreliable connections. 1. Replace the circuit pack. PASS The TSI is correctly using its allocated time slots.
PAGE 1664
Communication Manager Maintenance-Object Repair Procedures Table 616: Test #1122/1123 MMI Synchronization Status Test Error Code Test Result Description / Recommendation ABRT Internal system error. This is an abnormal abort. 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT A response to the test was not received from the MMI circuit pack within the allowable time period. 1.
PAGE 1665
MMI-BD Control Channel Loop-Around Test (#52) Refer to the repair procedure described in XXX-BD (Common Port Circuit Pack) as Control Channel Loop-Around Test (#52) on page 2551. SAKI Sanity Test (#53) Refer to the SAKI Sanity Test (#53) on page 2552 repair procedure in the XXX-BD (Common Port Circuit Pack/Media Module) on page 2539.
PAGE 1666
Communication Manager Maintenance-Object Repair Procedures MMI-LEV (Multimedia Interface Resource Level) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO MMI-LEV MAJ See 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 screen.
PAGE 1667
MMI-LEV (Multimedia Interface Resource Level) exists, yet no alarms have been raised against MMI-BD or MMI-PT MOs, a MMI circuit pack may have been removed from service causing the MMI-LEV error/alarm. To resolve a MMI-LEV MAJOR alarm, restore the number of MMI ports available for service to be equal to or greater than the calculated port capacity. To determine how many MMI circuit packs are needed for the MMCH feature: 1.
PAGE 1668
Communication Manager Maintenance-Object Repair Procedures available for service to be equal to or more than the calculated port capacity. See the Resolving MMI-LEV Errors/Alarms on page 1666 section for details. 3. If this error continues, escalate the problem. System Technician-Demanded Tests: Descriptions and Error Code There are no System Technician-Demanded tests for MMI-LEV. 1668 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1669
MMI-PT MMI-PT S8700 | 8710 / S8500 Note: MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MMI-PT MAJ test port location l r# Multimedia Interface Port MMI-PT MIN test port location l r# Multimedia Interface Port MMI-PT WRN test port location l r# Multimedia Interface Port Note: Refer to Chapter 4: General troubleshooting in Maintenance Procedures (03-300192) for MMCH troubleshooting information. The Multimedia Interface circuit pack provides a number of H.
PAGE 1670
Communication Manager Maintenance-Object Repair Procedures Figure 92: TN787 MMI (MULTIMEDIA INTERFACE) CIRCUIT PACK Error Log Entries and Test to Clear Values Table 618: MMI-PT Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) Any Uplink error from pack 18 (c) 0 busyout port location WRN OFF release port location 130 (d) Any Software generated WRN ON 257 (e) Any None MAJ MIN O
PAGE 1671
MMI-PT Table 618: MMI-PT Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 513 (f) Any Resource Loop-Back test (#1111) MIN ON test port location sh r 3 1025 (g) Any Uplink error from pack 3841 to 3844 (h) Any Uplink error from pack 2 of 2 Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description and follow its procedures. b.
PAGE 1672
Communication Manager Maintenance-Object Repair Procedures h. Error Types 3841 - 3844: are not related to VSP-MCU. They could be caused by network problems or from the customer endpoints. They are presented here for logging purposes only. Code Description 3841 CRC4 Error (Frame checksum error) 3842 Correctable BAS (Control msg bit error – 1- or 2-bit error, correctable) 3843 Uncorrectable BAS (Control msg bit error – 3-bit error or more, not correctable) 3844 Protocol Error (H.
PAGE 1673
MMI-PT Table 619: Test #1111 Resource Loop-Around Test Error Code Test Result Description / Recommendation 1000 ABRT 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. Use status conference to determine if there is an active conference. If a call is active, the test cannot run until the conference call finishes. 1002 ABRT The system could not allocate time slots for the test.
PAGE 1674
Communication Manager Maintenance-Object Repair Procedures Table 619: Test #1111 Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary resources to run this test. Abnormal abort. 1. Retry the command at 1-minute intervals up to 5 times. 0, 1, 2 FAIL This resource cannot guarantee data integrity and is out-of-service.
PAGE 1675
MMI-SYNC MMI-SYNC S8700 | 8710 / S8500 Note: MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO MMI-SYNC MIN test board location l r# Multimedia Interface circuit pack Note: Refer to Chapter 4: General troubleshooting in Maintenance Procedures (03-300192) for MMCH troubleshooting information. Each Port Network (PN) must have a TN787D or later MMI circuit pack assigned as the Multimedia Interface (MMI) master synchronization source for that PN.
PAGE 1676
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 620: MMI-SYNC Error Log Entries Error Type Aux Data Associated Test 1 (a) Any None 257 (b) Any None Alarm Level On/Off Board MIN OFF Test to Clear Value Notes: a. Error Type 1: an MMI synchronization switch was successful. 1. Refer to MMI-BD errors for the reason for the switch. b. Error Type 257: the requested MMI synchronization switch failed. 1. Resolve every MMI-BD alarm.
PAGE 1677
MODEM-BD (Modem Pool Circuit Pack) MODEM-BD (Modem Pool Circuit Pack) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO MODEM-BD MIN test board location sh Modem Pool circuit pack MODEM-BD WRN test board location sh Modem Pool circuit pack Refer to XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level errors. See also MODEM-PT (Modem Pool Port) on page 1678 for related port information.
PAGE 1678
Communication Manager Maintenance-Object Repair Procedures MODEM-PT (Modem Pool Port) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO MODEM-PT MIN test port location s Modem Pool Port The Modem Pool Port provides an interface for digital and analog data communication devices or ports connected to the PBX.
PAGE 1679
MODEM-PT (Modem Pool Port) Figure 93: Typical Modem Pool Switched Connection with Integrated Pooled Modem TERMINAL DATA MODULE DCP DIGITAL DCP LINE (TN754) DIGITAL DCP POOLED MODEM PORT PBX DIGITAL CONVERSION NETWORK ANALOG RESOURCE PCM PORT (TN758) CENTRAL OFFICE PCM TELEPHONE TIP/RING NETWORK ANALOG TRUNK (TN747B) ANALOG MODEM HOST COMPUTER Combined Modem Pools The Combined Modem Pool conversion resource is the second type available.
PAGE 1680
Communication Manager Maintenance-Object Repair Procedures Figure 94: Typical Modem Pool Switched Connection with Combined Modem Pool DCP TERMINAL DATA MODULE DIGITAL DCP DCP LINE (TN754) DATA DIGITAL MODULE LINE DCP (TN754) PBX DIGITAL RS-232 COMBINED MODEM POOL DCP ANALOG MODEM Tip/Ring TELEPHONE NETWORK NETWORK PCM LINE CENTRAL OFFICE PCM TRUNK ANALOG (TN747B) ANALOG MODEM HOST COMPUTER 1680 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1681
MODEM-PT (Modem Pool Port) 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 error message on the terminal. In this case, check the Modem Pool administration and Data Module option settings.
PAGE 1682
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 621: Modem Pool Port Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 18 0 busyout port location WRN OFF release port location 130 (b) None WRN ON test port location sh 257 Conversion Resource Loop (#98) MIN ON test port location s r 3 513 Modem Conference (#97) MIN ON test
PAGE 1683
MODEM-PT (Modem Pool Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1684
Communication Manager Maintenance-Object Repair Procedures Table 622: Test #96 Modem Pool NPE Crosstalk Test (continued) Error Code Test Result 1000 ABRT Description / Recommendation Note: Note: System resources required for this test are not available. The port may be in use on a valid call. Determine whether the port is available for testing. 2. Retry the command at 1-minute intervals up to 5 times. 1001 ABRT System resources required to run this test are not available. 1.
PAGE 1685
MODEM-PT (Modem Pool Port) Table 622: Test #96 Modem Pool NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 6000 ABRT System resources needed to complete the test could not be allocated for the digital section of the Modem Pool conversion resource. Ordinarily, this means the conversion resource or other hardware used during the test was in use. 1. Wait 1 minute and attempt the test again. 2.
PAGE 1686
Communication Manager Maintenance-Object Repair Procedures 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.
PAGE 1687
MODEM-PT (Modem Pool Port) Table 623: Test #97 Modem Pool Conference Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT The response to the test was not received in the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. 2012 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1688
Communication Manager Maintenance-Object Repair Procedures Table 623: Test #97 Modem Pool Conference Test (continued) Error Code Test Result Description / Recommendation None FAIL The test failed. This error is internal to the Pooled Modem circuit pack and does not involve external equipment or interfaces. 1. Busyout both of the TN758 Pooled Modem conversion resources on the circuit pack containing the failing conversion resource. 2.
PAGE 1689
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 1690
Communication Manager Maintenance-Object Repair Procedures Table 624: Test #98 Modem Pool Conversion Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1180 ABRT A Maintenance/Test board’s digital port could not be allocated for this test.
PAGE 1691
MODEM-PT (Modem Pool Port) Table 624: Test #98 Modem Pool Conversion Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2005 ABRT The Maintenance/Test and the Pooled Modem boards’ digital ports failed to handshake. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test still aborts, replace the Pooled Modem circuit pack. 2312 ABRT The Loop-around test did not complete, failed to receive loop-back data. 1.
PAGE 1692
Communication Manager Maintenance-Object Repair Procedures Table 624: Test #98 Modem Pool Conversion Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2325 FAIL The Modem Pool port did not respond with an on-hook message when the connection to the TN711 Maintenance/Test digital port was broken, indicating a likely problem with the TN758 Pooled Modem circuit pack. 1.
PAGE 1693
MODEM-PT (Modem Pool Port) Table 624: Test #98 Modem Pool Conversion Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 5004 ABRT The test was not able to allocate the analog portion of the Modem Pool Port. 1. Follow the repair procedures for Error Code 5000. 5005 ABRT The test was not able to establish a connection for the analog portion of the Modem Pool Port. 1. Follow the repair procedures for Error Code 5000.
PAGE 1694
Communication Manager Maintenance-Object Repair Procedures Table 624: Test #98 Modem Pool Conversion Resource Loop-Around Test (continued) Error Code Test Result Description / Recommendation 5011 ABRT The Network Control Channel allocated for this test did not disconnect properly. 1. Follow the repair procedures for Error Code 5001. 5012 ABRT The digital portion of the tested Modem Pool Port did not disconnect properly. 1. Follow the repair procedures for Error Code 5000.
PAGE 1695
MODEM-PT (Modem Pool Port) 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 test the Pooled Modem circuit pack, so there are no FAIL codes. The audit can only be performed on idle conversion resources. If the conversion resource is in use, the audit aborts.
PAGE 1696
Communication Manager Maintenance-Object Repair Procedures M/T-ANL (Maintenance/Test Analog Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO M/T-ANL MIN test port location l Maintenance/Test analog port M/T-ANL WRN release port location Maintenance/Test analog port The Maintenance/Test analog port is port number 1 on the TN771D Maintenance/ Test circuit pack.
PAGE 1697
M/T-ANL (Maintenance/Test Analog Port) Error Log Entries and Test to Clear Values Table 626: M/T-ANL Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location 1 (b) 41018 none MIN ON test port location l r 3 18 0 busyout port location WRN OFF release port location 257 Any NPE Crosstalk test (#9) MIN ON test port location l r 3 513 Any Analog Port Sanity test (#963) MIN ON test port location r
PAGE 1698
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented. By clearing Error Codes associated with the Analog Port Sanity test (#963), you may also clear errors generated from other tests in the sequence.
PAGE 1699
M/T-ANL (Maintenance/Test Analog Port) Table 627: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. A system is considered under heavy traffic when the Call Processing Occupancy is greater than 50% or when the System Management and the Call Processing Occupancies together exceed 65%.
PAGE 1700
Communication Manager Maintenance-Object Repair Procedures Table 627: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL The NPE of the tested port was found to be transmitting in error. This will cause noisy and unreliable connections. 1. If the remaining ports are currently idle (amber LED is off), try to reset the circuit pack using busyout board location, reset board location, and release board location. Repeat the test. 2.
PAGE 1701
M/T-ANL (Maintenance/Test Analog Port) Table 628: Test #13 Analog Port Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT The port is in use on a valid ATMS test call. 1. Retry the command at 1-minute intervals up to 3 times. 2. If the test continues to abort and the port is idle on a valid ATMS test call, escalate the problem.
PAGE 1702
Communication Manager Maintenance-Object Repair Procedures Table 628: Test #13 Analog Port Digital Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 3 times. 7 FAIL Conference test failed on the primary information channel. 1.
PAGE 1703
M/T-ANL (Maintenance/Test Analog Port) counter, so that if the port continues to fail during or after Communication Manager demands testing, the Angel will send a message to indicate that fact. This test is only used to send a message to the Angel on the Maintenance/Test circuit pack. Therefore, this test should never abort or fail.
PAGE 1704
Communication Manager Maintenance-Object Repair Procedures 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 1705
M/T-BD (Maintenance/Test Circuit Pack) M/T-BD (Maintenance/Test Circuit Pack) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO M/T-BD MIN test board location l Maintenance/Test circuit pack M/T-BD WRN release board location Maintenance/Test circuit pack The Maintenance/Test circuit pack (TN771D) supports packet-bus fault detection and bus reconfiguration for the port network where it is installed.
PAGE 1706
Communication Manager Maintenance-Object Repair Procedures Hardware Error Log Entries and Test to Clear Values Maintenance/Test Board Error Log Entries Error Type Aux Data Associated Test Alarm Level1 On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 1 (b) 0 SAKI Sanity test (#53) MIN ON 18 (c) 0 busyout board location WRN OFF 36 (d) 0 WRN ON MIN ON WRN ON 217 (f) 257 (e) 0 CC Loop test (#52) 267 (f) 513 (g) 4352 to 4357 769 (h) 4358 1025 (i)
PAGE 1707
M/T-BD (Maintenance/Test Circuit Pack) c. Error Type 18: the circuit pack has been busied out by the command busyout board location. Execute release board location. d. Error Type 36: a port processor on the circuit pack failed to initialize. Reset the circuit pack using busyout board location, reset board location, and release board location. If the problem does not go away, replace the circuit pack. e. Error Type 257: a Control Channel Protocol error has occurred.
PAGE 1708
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1709
M/T-DIG (Maintenance/Test Digital Port) M/T-DIG (Maintenance/Test Digital Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO M/T-DIG MIN test port location l Maintenance/Test digital port M/T-DIG WRN release port location Maintenance/Test digital port The Maintenance/Test digital port is a port on the TN771D circuit pack. Ports 2 and 3 are digital ports. The Maintenance/Test digital port provides the ability to perform digital (i.e.
PAGE 1710
Communication Manager Maintenance-Object Repair Procedures Figure 97: ISDN-PRI Outgoing Test Call PBX Equipment SPE UN332 MSSNET Looped-back data stream pattern is generated by digital port 1 and checked by digital port 2 on the TN771 TN1655 PKT-INT . . . ......................................... . . . . . . ................. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital Digital . . . Port 2 Port 1 . . . . . . . . . . TN771 . . . Maintenance/Test . . . . . . . . . . . .
PAGE 1711
M/T-DIG (Maintenance/Test Digital Port) Table 632: M/T-DIG Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 257 (d) Any NPE Crosstalk test (#9) MIN ON test port location l r 3 513 (e) Any Digital Port Sanity test (#565) MIN ON test port location r 2 769 (f) Any Digital Port Loop Around test (#13) MIN ON test port location r 3 3840 (g) Any Hook State Inquiry test (#566) 2 of 2 Notes: a.
PAGE 1712
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1713
M/T-DIG (Maintenance/Test Digital Port) Table 633: Test #9 NPE Crosstalk Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be in use on a valid ISDN-PRI test call. Use list isdn-testcall to determine whether the port is in use (listed in the M/T Port column).
PAGE 1714
Communication Manager Maintenance-Object Repair Procedures Table 633: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port has been seized by a valid ISDN-PRI test call. Use list isdn-testcall to determine which call is using the port (from the M/ T Port column).
PAGE 1715
M/T-DIG (Maintenance/Test Digital Port) Only one value (Pass, Fail, or Abort) is generated as a result of the two tests. If it fails or aborts, the sequence is stopped. Table 634: Test #13 Digital Port Loop-Around Test Error Code Test Result Description / Recommendation ABRT 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. 1000 ABRT The port is use on a valid ISDN-PRI test call.
PAGE 1716
Communication Manager Maintenance-Object Repair Procedures Table 634: Test #13 Digital Port Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a valid ISDN-PRI test call. Use list isdn-testcall to determine which call is using the port (from the M/T Port column).
PAGE 1717
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 1718
Communication Manager Maintenance-Object Repair Procedures The test passes if all four self-tests are successful. The test stops when any one of the self-tests fails. This test aborts if an ISDN test call is in progress on the Maintenance/Test digital port when the test is requested, or if an ISDN test call is initiated while the Digital Port Sanity test is in progress.
PAGE 1719
M/T-DIG (Maintenance/Test Digital Port) Table 636: Test #565 Digital Port Sanity Test (continued) Error Code Test Result Description / Recommendation 1019 ABRT An ISDN test call is in progress using this Maintenance/Test circuit pack. The Maintenance/Test circuit pack cannot perform a self-test on one of its digital ports while an ISDN test call is using either of the digital ports. Use list isdn-testcall to determine which call is using the port, from the M/T Port column.
PAGE 1720
Communication Manager Maintenance-Object Repair Procedures Table 636: Test #565 Digital Port Sanity Test (continued) Error Code Test Result Description / Recommendation 101 FAIL Data was not sent from port 3 to port 2 successfully in asynchronous mode. 1. Reset the circuit pack using busyout board location, reset board location, and release board location. 2. Test the port again using test port location (02) l. 3. If the test fails again, replace the circuit pack.
PAGE 1721
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 637: Test #566 Hook State Inquiry Error Code Test Result Description / Recommendation 1 ABRT Switch hook audit timed out. No response was received from the circuit pack for information about the switch hook state. 1.
PAGE 1722
Communication Manager Maintenance-Object Repair Procedures M/T-PKT (Maintenance/Test Packet Bus Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO M/T-PKT MIN test port location l Maintenance/Test Packet Bus port M/T-PKT WRN release port location Maintenance/Test Packet Bus port The Maintenance/Test packet-bus port (M/T-PKT) is Port #4 on the TN771D Maintenance/Test circuit pack.
PAGE 1723
M/T-PKT (Maintenance/Test Packet Bus Port) Table 638: M/T-PKT Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 (c) 0 busyout port location WRN OFF release port location 257 (d) Any none MIN ON 513 (e) Any Packet Bus Port Health Inquiry (#567) MIN ON test port location r 3 2 of 2 Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence.
PAGE 1724
Communication Manager Maintenance-Object Repair Procedures 3. If the error recurs, replace the Maintenance/Test circuit pack. 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. It is OK to replace the Maintenance/Test circuit pack.
PAGE 1725
M/T-PKT (Maintenance/Test Packet Bus 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. The circuit pack’s Angel continuously runs port self-tests on idle ports and keeps track of any errors it detects by incrementing a firmware counter. When the counter value reaches some preset threshold, the Angel sends a single CCMS (Control Channel Message Set) error message uplink to Communication Manager.
PAGE 1726
Communication Manager Maintenance-Object Repair Procedures 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 1727
NO-LIC (No License) NO-LIC (No License) S8700 | 8710 / S8500 / S8300 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO NO-LIC MAJ None NO License Note: The NO-LIC MO (No License) is non-traditional in that there are no associated tests or commands that you can execute. Note: How systems go into No-License mode The NO-LIC MO works with the LIC-ERR MO to find any errors/violations associated with the License File.
PAGE 1728
Communication Manager Maintenance-Object Repair Procedures Figure 98: License mode algorithm System initialization 1 License-Error present? No Yes No Timer value readable? Yes Timer expired? No Yes No-License mode License-Error mode 2 3 License-Normal mode fldfmode KLC 052504 Figure notes: 1. See Troubleshooting License File errors on page 1482. 2. See How systems go into No-License mode on page 1727. 3. See Troubleshooting License File errors on page 1482.
PAGE 1729
NO-LIC (No License) Error Log Entries and Test to Clear Values Error Type Aux Data Associated Test 1 (a) Alarm Level On/Off Board MAJ OFF 513 (b) None MAJ OFF 769 (c) None MAJ OFF 1281 (d) None MAJ OFF 1537 (e) None MAJ OFF 1793 (f) None MAJ OFF 2305 (g) None MAJ OFF 2561 (h) None MAJ OFF Test to Clear Value1 1. These Error Types are cleared by installing a valid License File that matches the hardware ID(s). Notes: a.
PAGE 1730
Communication Manager Maintenance-Object Repair Procedures f. Error Type 1793: a Software Version Mismatch has occurred. The system enters No-License mode. g. Error Type 2305: the Offer Category of the License does not match the Offer Category in translations. The system enters No-License mode. h. Error Type 2561: during the last attempted License File audit, the license server did not respond in time. On-Demand Tests for System Technicians This MO provides no on-demand tests for system technicians.
PAGE 1731
NR-CONN (Network-Region Connect) NR-CONN (Network-Region Connect) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO NR-CONN WRN test failed-ip-network-region Network-Region Connect NR-CONN MIN test failed-ip-network-region Network-Region Connect A network region is a logical grouping of IP endpoints (including IP stations, IP trunks, and media gateways) sharing the same transmission characteristics and/or VoIP and signaling resources, such as a Me
PAGE 1732
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 641: NR-CONN Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board 1(a) 0 Network Region Interconnectivity (#1417) MIN ON Test to Clear Value Note: a. Error Type 1: one or more network-region connections have failed. 1. Enter display failed-ip-network-region to verify that connections between pairs of network regions are failing. 2.
PAGE 1733
NR-CONN (Network-Region Connect) Network Region Interconnectivity Test (#1417) This test is nondestructive. Test #1417 is a nonstandard test, since it does not specify and list Error Codes in the usual manner. If this background test detects a failure, the test is retried using different IP endpoints (if available) from the same two network regions. If the test still fails between these network regions: 1. Maintenance software marks the connectivity between them as “failed.” 2.
PAGE 1734
Communication Manager Maintenance-Object Repair Procedures Table 642: Test #1417 Network Region Interconnectivity Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Did not receive a response from a circuit pack being used for the test within the allowable time period. 1. Reset the circuit pack (busyout board location, reset board location, and release board location). 2. If the test fails again, replace the circuit pack. 2012 ABRT Internal system error. 1.
PAGE 1735
NR-CONN (Network-Region Connect) Table 642: Test #1417 Network Region Interconnectivity Test (continued) Error Code Test Result Description / Recommendation 7 89 1007 FAIL Ping to the destination failed due to the destination down. 2805 FAIL The number of pings received did not match the number sent (normally one ping is sent). This means that no ping responses were received from the destination region endpoint being tested back to the source endpoint sending the ping.
PAGE 1736
Communication Manager Maintenance-Object Repair Procedures OPS-LINE (DS1 Off-Premises Station Line) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO OPS-LINE MIN test station extension l DS1 OPS Line OPS-LINE WRN test station extension DS1 OPS Line An analog Off-Premises Station (OPS) can be connected to the system through a DS1 link. A TN767 DS1 Interface circuit pack or a TN464 UDS1 Interface circuit pack can support up to 24 DS1 OPS lines.
PAGE 1737
OPS-LINE (DS1 Off-Premises Station Line) Error Log Entries and Test to Clear Values Table 643: DS1 OPS Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test station ext 15 (b) Any Audit and Update test (#36) 18 (c) 0 busyout station ext WRN OFF release station ext 130 (d) None WRN ON test station ext 1281 Conference Circuit test (#7) MIN ON test station ext l r 4 1537 NPE Crosstalk test (#6) M
PAGE 1738
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1739
OPS-LINE (DS1 Off-Premises Station Line) Table 644: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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 1740
Communication Manager Maintenance-Object Repair Procedures Table 644: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2. If the test aborts with Error Code 2000 again, run short test sequence on the associated DS1-BD or UDS1-BD.
PAGE 1741
OPS-LINE (DS1 Off-Premises Station Line) Table 644: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config, and resolve any problems that are found. 2.
PAGE 1742
Communication Manager Maintenance-Object Repair Procedures Table 645: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The test was aborted because the system could not allocate time slots for the test. The system might be under heavy traffic conditions, or it might have time slots out of service due to TDM-BUS errors. Use status health to determine if the system is experiencing heavy traffic. 1.
PAGE 1743
OPS-LINE (DS1 Off-Premises Station Line) Table 645: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation G700: ABRT This test does not execute on a G700 media gateway. 2000 ABRT The test was aborted because response to the test was not received within the allowable time period. 1412 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test aborts with Error Code 2000 again, run short test sequence on the associated DS1-BD or UDS1-BD.
PAGE 1744
Communication Manager Maintenance-Object Repair Procedures Table 645: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation Any FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1. Enter list configuration board location. If the circuit pack is a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3 or later. The error log may have error type 1281 entries. 2.
PAGE 1745
OPS-LINE (DS1 Off-Premises Station Line) Table 645: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config, and resolve any problems that are found. 2.
PAGE 1746
Communication Manager Maintenance-Object Repair Procedures Table 646: Test #36 Audit and Update Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT The test was aborted because system resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension of the port. Use status station to determine the service state of the port.
PAGE 1747
OPS-LINE (DS1 Off-Premises Station Line) Table 646: Test #36 Audit and Update Test (continued) Error Code Test 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. To verify that the station is in-service: 1. Enter status station to verify that the station is in-service.
PAGE 1748
Communication Manager Maintenance-Object Repair Procedures 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 1749
OPS-LINE (DS1 Off-Premises Station Line) Table 647: Test #312 DS1 OPS Switchhook Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT The test was aborted because response to the test was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test aborts with Error Code 2000 again, run short test sequence on the associated DS1-BD or UDS1-BD.
PAGE 1750
Communication Manager Maintenance-Object Repair Procedures Table 647: Test #312 DS1 OPS Switchhook Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board translations are correct. Use list config, and resolve any problems that are found. 2.
PAGE 1751
PDMODULE (Processor Data Module) PDMODULE (Processor Data Module) Error log entries and tests also apply to TDMODULE. S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PDMODULE1 MIN test port location long Processor Data Module PDMODULE WRN test port location short Processor Data Module TDMODULE 2 MIN test port location long Trunk Data Module TDMODULE WRN test port location short Trunk Data Module 1.
PAGE 1752
Communication Manager Maintenance-Object Repair Procedures Stand-Alone DCP Data Modules There are two types of stand-alone DCP data modules as shown in Table 648. Table 648: Stand-Alone DCP Data Modules Type Name1 Interfaces to: MPDM Modular Processor Data Module DTE (data terminals, host computers, printers, etc.) MTDM Modular Trunk Data Module DCE (modems, data modules, etc.) 1. Early versions of these data modules were referred to as PDMs and TDMs, respectively.
PAGE 1753
PDMODULE (Processor Data Module) Configurations and Maintenance The MPDM provides an interface for Data Terminal Equipment (terminals), and the MTDM (see Note) provides an interface for Data Communications Equipment (transmission equipment such as modems). Note: Note: Early versions of these data modules were referred to as PDMs and TDMs, respectively.
PAGE 1754
Communication Manager Maintenance-Object Repair Procedures Disconnected The port is administered but the associated digital link does not respond. An administered port is put in a disconnected state after a system reboot or circuit pack insertion. This state persists until a link-reset-pass message is received from firmware on the circuit pack. In-Service When switch software receives a link-reset-pass message from the port, the port is placed in service.
PAGE 1755
PDMODULE (Processor Data Module) Error Log Entries and Test to Clear Values Table 650: PDMODULE, TDMODULE Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board 0 (a) 0 None 1 (b, n) 40987 1 (c, n) None WRN OFF 1– 20 None WRN OFF 15 (d) Any None 18 (e) 0 busyout port location WRN OFF release port location 257 (f) 40971 None 513 0 Data Module audits (#17) WRN OFF test port location sh r 6 769 (g, n) 40988 None WRN OFF 1281 Any Data Module au
PAGE 1756
Communication Manager Maintenance-Object Repair Procedures 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. Error Type 1, Aux Data 40987 indicates an off-board problem detected by the port circuit, and may result in a noisy port or link. See note n for recommendations.
PAGE 1757
PDMODULE (Processor Data Module) determine the state of the data module. The off-hook should have changed the service state to in-service. No action is necessary. k. Error Type 2305, Aux Data 40967: the link between the circuit pack and the data module has been reset successfully.
PAGE 1758
Communication Manager Maintenance-Object Repair Procedures Order of Investigation Short Test Sequence Port Circuit Information Channel and Control Channel Loop-Around (#13) G700: Aborts with Error Code 1412 on a G700 Media Gateway. Data Module Audits test (#17) X Long Test Sequence D/ND1 X ND X ND 2 of 2 1.
PAGE 1759
PDMODULE (Processor Data Module) Table 651: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the extension of the data module port. Use status data-module to determine the service state of the port. If the port is in use, wait until the port is idle before testing. 2.
PAGE 1760
Communication Manager Maintenance-Object Repair Procedures Table 651: Test #9 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. 2020 ABRT The test did not run due to a previously existing error on the specific port or a more general circuit pack error. 1.
PAGE 1761
PDMODULE (Processor Data Module) Information and Control Channel Local Loop Test (#13) This is a set of four tests that check the operation of the information and control channels used between Communication Manager and the Digital Line port circuit. This is an Internal Loop around test only and does not check building wiring. See Test #175 for external loop around tests to the data module. 1.
PAGE 1762
Communication Manager Maintenance-Object Repair Procedures Table 652: Information and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 1001 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABRT 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. 1.
PAGE 1763
PDMODULE (Processor Data Module) Table 652: Information and Control Channel Local Loop Test (continued) Error Code Test Result Description / Recommendation 7 FAIL Conference test failed on the primary information channel. In some cases, user may not notice disruption in service. In extreme cases, conferencing feature may not work at all. 14 FAIL The primary information channel is not transmitting properly. User impact may range from noticing nothing to not being able to use this port.
PAGE 1764
Communication Manager Maintenance-Object Repair Procedures ● EPF inquiry: The status of the Electronic Power Feed is sent uplink. EPF is not used for data modules. ● ID Request: A request is made to the data module for its status. The data module sends its configuration information and health information back. This information is checked and a pass/fail result is provided. ● Ringer Update: This updates the data module’s ringer state according to processor records.
PAGE 1765
PDMODULE (Processor Data Module) Table 653: Test #17 Data Module Audits Test (continued) Error Code Test Result Description / Recommendation 5 ABRT Ringer update aborted (data module not in the in-service state) 1. Verify that the data module is powered (power LED on). 2. Make sure data module is connected to the building wiring, check for faulty wiring, check for faulty data module. 3. Retry the command at 1-minute intervals up to 5 times. 4. Replace the Data Module and repeat the test. 5.
PAGE 1766
Communication Manager Maintenance-Object Repair Procedures Data Module Internal Loop-Around Test (#175) This test verifies that a data message can be sent from the PBX, through the building wiring, through an internal loop-around path in the data module, and back to the PBX. This path is illustrated below. For this test to run, the Remote Loop-Around Test field on the Data Module administration screen must be set to y, indicating that the data module endpoint supports the test.
PAGE 1767
PDMODULE (Processor Data Module) Table 654: Test #175 Data Module Internal Loop-Around Test Error Code Test Result Description / Recommendation S8700 | 8710 / S8500 1000 ABRT 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. 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT Loop around testing is not enabled on the data module administration screen. 1.
PAGE 1768
Communication Manager Maintenance-Object Repair Procedures Table 654: Test #175 Data Module Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1340 ABRT No Maintenance/Test digital port is currently available to perform this test. 1. Use list config to determine whether any Maintenance/Test digital ports (ports 02 and 03 on the Maintenance/Test circuit pack) are present in the system.
PAGE 1769
PDMODULE (Processor Data Module) Table 654: Test #175 Data Module Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2312 ABRT The loop-around test did not complete, failed to receive loop-back data. 1. Check for M/T-DIG error in the Error Log. If present, see M/T-DIG (Maintenance/Test Digital Port) on page 1709. 2. Retry the test, if still aborts, replace the Data Module. 3. If the test aborts again, replace the Digital Line circuit pack.
PAGE 1770
Communication Manager Maintenance-Object Repair Procedures Table 654: Test #175 Data Module Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT Could not get translation information for port. 1. Verify that port circuit is administered. 2. Wait one minute and attempt the test again. 3. If the test continues to abort and the port is not in use, escalate the problem. 1005 ABRT This test is not applicable to the given hardware configuration. 1.
PAGE 1771
PDMODULE (Processor Data Module) Table 654: Test #175 Data Module Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Data module disconnected. 1. Verify that the data module is powered (power LED on). 2. Make sure data module is connected to the building wiring. Check for faulty wiring and faulty data module. 3. Retry the command at one-minute intervals a maximum of 5 times. 4. Replace the Data Module and repeat the test. 5.
PAGE 1772
Communication Manager Maintenance-Object Repair Procedures Table 654: Test #175 Data Module Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1070 FAIL Internal software response. 1. Wait one minute and attempt the test again. 2. If the same error persists after five attempts in one-minute intervals, escalate the problem. 1072 FAIL Poor response from auxiliary channel. 1. Test the Network Control (Netcon) circuit pack using the test data-module command. 2.
PAGE 1773
PE-BCHL (PRI Endpoint Port) PE-BCHL (PRI Endpoint Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PE-BCHL1 MIN test port location l PRI Endpoint Port PE-BCHL WRN test port location sh PRI Endpoint Port 1. For additional repair information, see also UDS1-BD and Troubleshooting ISDN-PRI endpoints (wideband) in Maintenance Procedures (03-300192).
PAGE 1774
Communication Manager Maintenance-Object Repair Procedures Multiple PRI endpoints on one line-side facility are separate and distinct within the facility. Non-overlapping contiguous sets of B channels are associated with each PRI endpoint, and the endpoint equipment is expected to initiate calls within these boundaries.
PAGE 1775
PE-BCHL (PRI Endpoint Port) Figure 102: PRI Endpoint Port Interactions Packet Bus UDS1 Interface Circuit Pack (TN464C) Terminal Adapter Data PE-BCHL Processor (UN331) (Port 23) .. . . . .. .. .. .. . PE-BCHL PKTINT Circuit Pack (TN1655) Signaling (Port 24) ISDN-LNK .. . . .. . . . . . . . . MSSNET Circuit Pack (UN332) Data (Port 1) TDM Bus PRI Endpoint Port Service States The status pri-endpoint extension command displays the following possible service states for PRI endpoint ports.
PAGE 1776
Communication Manager Maintenance-Object Repair Procedures ports in the PRI endpoint can still be used for incoming and outgoing calls. No messages are sent to the far-end terminal adapter until the signaling link comes back into service or the port is released by command. ● Maintenance/Far-End (MTC/FE) This state is reached when the far-end terminal adapter does not respond to messages sent over the signaling link for a particular port within a certain amount of time.
PAGE 1777
PE-BCHL (PRI Endpoint Port) Table 655: PRI Endpoint Port Service States (continued) Service State Alarm Possible Cause Possible Solution OOS/FE WRN Far-end problems or incompatibility Check administration and status of the corresponding port on the terminal adapter. WRN The far-end port is busied out. Check the status of the far-end terminal adapter. OOS/FE PINS Service message was sent and the switch is waiting up to 2 minutes for a reply from the far-end terminal adapter.
PAGE 1778
Communication Manager Maintenance-Object Repair Procedures Figure 103: Common Progressions in PRI Endpoint Service States OUT-OFSERVICE NEAR END CRAFT RELEASE OF A B-CHANNEL OR NEAR-END LINK PROBLEM (PI-LINK OR SYS-LINK) CLEARS UP ADMINISTER B-CHANNEL AS MEMBER OF A PRI ENDPOINT MAINTENANCE NEAR END CRAFT BUSYOUT OF B-CHANNEL BUSYOUT PORT/PRI-ENDPOINT, LINK PROBLEM AT NEAR END (PI-LINK OR SYS-LINK), DS1 BOARD NOT INSERTED, OR DS1 BOARD FAILURE.
PAGE 1779
PE-BCHL (PRI Endpoint Port) Table 656: PRI endpoint port Error Log Entries (continued) Error Type Aux Data Associated Test 18 (d) 0 busyout pri-endpoint extension busyout port location Alarm Level On/Off Board Test to Clear Value release pri-endpoint extension release port location 129 (e) None WRN OFF test port location sh r 1 130 (f) None WRN ON test port location sh 257 (g) Any None 513 (h) Any None 769 (g) Any None 1281 (i) Any Conference Circuit test (#7) MIN ON test
PAGE 1780
Communication Manager Maintenance-Object Repair Procedures d. Error Type 18: the PRI endpoint port has been busied out by busyout pri-endpoint extension or busyout port location. No wideband calls can be made to this port, although wideband calls can still be made to other ports within this PRI endpoint if they are in service. e. Error Type 129: the far-end terminal adapter changed its ISDN service state to out-of-service or maintenance.
PAGE 1781
PE-BCHL (PRI Endpoint Port) Table 657: PE-BCHL - Error 3585 Aux Data Values Aux Data Meaning 10 A call in a stable, talking state (the active state) was cleared unexpectedly by the far-end terminal adapter with an ISDN RESTART message. 4 7 8 260 263 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 1782
Communication Manager Maintenance-Object Repair Procedures 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. This test is usually part of a port’s long test sequence and takes about 20 to 30 seconds to complete.
PAGE 1783
PE-BCHL (PRI Endpoint Port) Table 658: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port has been seized by a user for a valid call. Use status pri-endpoint extension to determine when the port is available for testing. 1. Retry the command at 1-minute intervals up to 5 times. 1117 ABRT A service state audit message is outstanding. 1. Wait 2 minutes and then try again.
PAGE 1784
Communication Manager Maintenance-Object Repair Procedures 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 measured by a tone detector port. If the level of the tone is within a certain range, the test passes.
PAGE 1785
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. Table 660: Test #36 Audit and Update Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 1786
Communication Manager Maintenance-Object Repair Procedures 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 661: Test #255 Signaling Link State Check Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 1787
PE-BCHL (PRI Endpoint Port) port, but incoming calls will be accepted. The service state of this port does not affect the service state of other ports in the PRI endpoint. If an incoming call that uses this port is presented while in such a state, a Service State audit attempt will immediately be attempted (that is, the switch will not wait for the 15-minute cycle, but will instead try to recover immediately). To investigate the status of this PRI endpoint port, enter status pri-endpoint extension.
PAGE 1788
Communication Manager Maintenance-Object Repair Procedures Call State Audit Test (#257) If a call is active on the port, the switches on both sides of the connection should agree on the ISDN state of the call as defined in the ISDN Protocol Specification. This test audits internal call state data by querying the far-end terminal adapter as to the ISDN state of the call. It can be helpful when trying to clear a hung call.
PAGE 1789
PE-BCHL (PRI Endpoint Port) Table 663: Test #257 Call State Audit Test (continued) Error Code Test Result Description / Recommendation FAIL Internal system error 1. Retry the command at 1-minute intervals up to 5 times. PASS This switch sent a call-state auditing message to the far-end terminal adapter to verify the state of the call active on this port. If a call-state mismatch is found, then the call is torn down within two minutes. If no call was active, then no message was sent.
PAGE 1790
Communication Manager Maintenance-Object Repair Procedures PKT-BUS (Packet Bus) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run1 Full Name of MO PKT-BUS MAJ test pkt P l r 21 Packet Bus PKT-BUS MIN test pkt P l Packet Bus PKT-BUS WRN test pkt P l Packet Bus 1. P is the port-network number indicated in the PORT field from the Alarm or Error Log. The packet bus consists of a single bus, and one such bus appears in each port network.
PAGE 1791
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. ● The Maintenance/Test circuit pack (TN771D) is a critical tool for isolating packet bus faults. This circuit pack resides in each port network of a critical-reliability system (duplicated servers and PNC).
PAGE 1792
Communication Manager Maintenance-Object Repair Procedures Hardware Error Log Entries and Test to Clear Value Table 664: PKT-BUS Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board1 Test to Clear Value 0 (a) 0 Any Any Any test pkt port-network 1 (b) 1–2 Packet circuit pack Audit (#570) MAJ ON test pkt port-network P l r 2 513 (c) 1–2 4 Maintenance/Test Circuit Pack Query test (#572) MAJ ON test pkt port-network P l r 2 1793 (d) Any None 2049 (e) 1–3 M
PAGE 1793
PKT-BUS (Packet Bus) e. Error Type 2049: S8700 MC: The Maintenance/Test packet bus port (M/T-PKT) has detected a Packet Bus fault and has taken corrective action by swapping to spare leads. This error appears only in high/critical-reliability systems (duplicated PNC). The Aux Data value indicates the number of faulty leads. If this is the only active error against the packet bus, the packet bus is still in service.
PAGE 1794
Communication Manager Maintenance-Object Repair Procedures ● The packet bus port has been busied out (indicated by Error Type 18), and a Warning alarm is active against M/T-PKT in the same port network. Release the port by entering release port location04. ● The packet bus port has failed. Look for alarms against M/T-PKT, and attempt to resolve these alarms. ● The Maintenance/Test circuit pack was not recognized by the system at the last system restart. Replace the Maintenance/Test circuit pack.
PAGE 1795
PKT-BUS (Packet Bus) Table 665: Test #572 Maintenance/Test Circuit Pack Query Test Error Code Test Result Description / Recommendation 1006 ABRT The packet bus port of the Maintenance/Test circuit pack is out of service. 1. Determine whether the port is busied out. If so, release it with release port location04. Then retry the test command. 2. If there are alarms active against the packet bus port (MT-PKT), see M/T-PKT (Maintenance/Test Packet Bus Port) on page 1722 to resolve them.
PAGE 1796
Communication Manager Maintenance-Object Repair Procedures Table 665: Test #572 Maintenance/Test Circuit Pack Query Test (continued) Error Code Test Result Description / Recommendation 2077 ABRT The Maintenance/Test Circuit Pack Query located more than one Maintenance/Test packet bus port in the PN. The software should not allow this to occur. This is an internal system error. Escalate the problem, but also attempt the following work-around steps. 1.
PAGE 1797
PKT-BUS (Packet Bus) Table 665: Test #572 Maintenance/Test Circuit Pack Query Test (continued) Error Code Test Result Description / Recommendation 1xxx The Maintenance/Test packet bus port has reconfigured the packet bus around the faulty leads. This action only occurs in a high- or critical-reliability system (duplicated PNC). 2xxx The Maintenance/Test packet bus port is unable to correct every Packet Bus fault it has detected. x0xx None of the packet bus faults are open faults.
PAGE 1798
Communication Manager Maintenance-Object Repair Procedures 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 1799
PKT-INT (Packet Interface) PKT-INT (Packet Interface) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PKT-INT MAJ reset packet-interface location Packet Interface PKT-INT MIN test packet-interface location Packet Interface PKT-INT WRN test packet-interface location Packet Interface The Packet Interface (PKT-INT) MO resides on the TN2312 IP Server Interface (IPSI) circuit pack and serves as an interface between the media server and the packet
PAGE 1800
Communication Manager Maintenance-Object Repair Procedures S8700 | 8710: If the active IPSI’s Packet Interface module causes a MAJOR alarm in a high- or critical-reliability system (with duplicated IPSIs), an IPSI interchange occurs if the standby IPSI’s state of health (SOH) is high enough to permit the interchange. A MAJOR alarm due to a failure of the standby IPSI’s Packet Interface module lowers the standby’s state of health (SOH), preventing a subsequent interchange.
PAGE 1801
PKT-INT (Packet Interface) S8700 IP: All port networks must have IPSI/PKT-INTs. They can be all simplex (one IPSI per PN) or all duplex (two IPSI per PN).
PAGE 1802
Communication Manager Maintenance-Object Repair Procedures the standby PKT-INT. In S8700 Multi-Connect, the active media server communicates directly with both active and standby PKT-INTs and performs maintenance activities on both PKT-INTs without the standby media server getting involved. Earlier G3r PKT-INT duplication relied on the duplication hardware to automatically duplicate and write each command from the processor into the active and standby PKT-INT’s dual-port RAMs.
PAGE 1803
PKT-INT (Packet Interface) Planned PKT-INT Interchange (Link Migration) A planned interchange of PKT-INTs uses link migration to assure that no data is lost during the interchange. On a planned interchange of PKT-INTs, software initiates the link migration by sending commands to the active and standby PKT-INTs to make a peer link between the PKT-INTs and to start the link migration process. Down-stream and up-stream messages can be processed by the PKT-INTs during the link migration process.
PAGE 1804
Communication Manager Maintenance-Object Repair Procedures PKT-INT and System Reliability S8700 IP A PKT-INT module resides on each IPSI board. On an S8700 IP Connect, there is a duplicated server, and one server is in active mode and one server is on standby. The control network(s) for S8700 IP Connect may be implemented in a simplex, see Figure 105: IP Connect Duplex Reliability - Simplex Control Network on page 1805, or a optional duplicated configuration. There is only one PKT-INT per port network.
PAGE 1805
PKT-INT (Packet Interface) Figure 105: IP Connect Duplex Reliability - Simplex Control Network 1 4 2 3 1 4 2 Ethernet 1 Ethernet 1 Ethernet 0 5 6 6 1 2 7 10 8 IPSI 9 IPSI 9 10 10 100bT BBI 100bT BBI 100bT BBI LINK LINK LINK LINK LINK LINK TRMT TRMT TRMT TRMT TRMT TRMT RCV RCV RCV RCV RCV RCV PN 1 8 8 PN 2 cydsdup KLC 042204 IPSI 9 PN Figure notes: 1. S8700 Media Server 1 – two are always present, one in an active mode and one on standby. 6.
PAGE 1806
Communication Manager Maintenance-Object Repair Procedures S8700 MC On S8700 Multi-Connect, a PKT-INT module resides on each IPSI board. LAPD links are terminated by the PKT-INT modules in the IPSIs that are distributed out to the port networks. The non IPSI connected port networks do not have their own PKT-INT capability, so their LAPD links are terminated by IPSIs in the IPSI connected port networks.
PAGE 1807
PKT-INT (Packet Interface) Figure 106: Duplex-Reliability Configuration Server A Server B Control Network A IPSI IPSI PN 1 PN 2 PN n EI EI EI Bearer Network High-Reliability Configuration - Multi-Connect The high-reliability configuration shown in Figure 107: High-Reliability Configuration Multi-Connect on page 1808 has duplicated media servers, duplicated control networks, and duplicated IPSIs in the IPSI connected PNs.
PAGE 1808
Communication Manager Maintenance-Object Repair Procedures Figure 107: High-Reliability Configuration - Multi-Connect Server A Server B Control Network A Control Network B IPSI IPSI IPSI IPSI PN 1 PN 2 PN n EI EI EI Bearer Network Figure 108: High-Reliability Configuration - IP Connect Server A Server B Customer Corporate LAN IPSI Med Pro PN 1 IPSI IPSI Med Pro PN 2 IPSI IPSI Med Pro IPSI PN n 1808 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1809
PKT-INT (Packet Interface) Critical-Reliability Configuration - Multi-Connect The critical-reliability configuration shown in Figure 109: Critical-Reliability Configuration Multi-Connect on page 1809 has full duplication of the following options: media servers, control networks, IPSIs and PNCs (bearer networks). As with the high-reliability configuration, this configuration requires that IPSI connected PNs have duplicated IPSIs.
PAGE 1810
Communication Manager Maintenance-Object Repair Procedures Administration PKT-INT modules are automatically administered as a component of an IPSI circuit pack. See add/remove ipserver-interface and test/status/reset packet-interface in Maintenance Commands Reference (03-300191). Packet Interface Circuit Replacement To replace a Packet Interface module that is part of a TN2312AP IPSI circuit pack, follow the procedure for replacing an IPSI circuit pack.
PAGE 1811
PKT-INT (Packet Interface) S8700 | 8710 If the circuit pack’s diagnostic tests do not pass in a standard- or duplex-reliability system (unduplicated IPSIs), the failing Packet Interface is placed in an out-of-service state. Every link handled by that IPSI goes down, and may be re-established using other Packet Interface resources. Calls associated with these links may drop.
PAGE 1812
Communication Manager Maintenance-Object Repair Procedures Maintenance-Object Interactions ● Packet Bus maintenance A Packet Interface physically interacts with the PKT-BUS. It may be difficult to isolate faults to one or the other component for certain types of Packet Interface errors. In each of these cases, Packet Interface maintenance forwards an error report to packet-bus maintenance, where it records a packet-bus fault in the hardware error log and runs Packet Bus tests.
PAGE 1813
PKT-INT (Packet Interface) For a case where not every link appears in the Failed Links category, examine the alarm and error logs for failures of the following circuit packs, and follow the repair procedures for those circuit packs before considering replacing the associated IPSI circuit pack: ● S8700 MC: TN570 Expansion Interface circuit pack (EXP-INTF) ● S8700 MC: TN573 Switch Node Interface circuit pack (SNI-BD) ● S8700 MC: Switch Node Clock circuit pack (SNC-BD) ● ISDN-BRI Line circuit packs, po
PAGE 1814
Communication Manager Maintenance-Object Repair Procedures Table 668: Packet Interface Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1025 (h) Any Private Loop-Around (#885) MAJ ON reset packet-interface location1 1281 (i) Any None MAJ ON reset packet-interface location1 1537 (j) Any Memory Checksum (884) MIN ON test packet-interface location l r 2 1793 (k) Any Memory Checksum (#884) MIN ON test packet-interface lo
PAGE 1815
PKT-INT (Packet Interface) When 3 of these errors occur in 15 minutes, maintenance places the Packet Interface into an out-of-service state, and a MAJOR on-board alarm is raised on the Packet Interface (PKT-INT). 1. See if Error Codes 257, 513, 769, 1025, 1281, or 3841 are present in the hardware error log. If one or more are present, follow the repair procedures for those errors. 2.
PAGE 1816
Communication Manager Maintenance-Object Repair Procedures g. Error Type 769 and 770: failure in the Packet Loop-Around test. A maintenance loop-around link cannot be established or the Packet Interface cannot send and receive data correctly as part of the Loop-Around test (#886). If the number of errors exceeds a defined threshold, a Major alarm is raised. In a high- or critical-reliability system (duplicated IPSIs), a failure of the Maintenance Loop-Around test may have caused an IPSI interchange.
PAGE 1817
PKT-INT (Packet Interface) m. Error Type 2305: parity failure was detected by the packet-bus interface. The Packet Interface received packets with parity errors from the packet bus. 1. Check for errors logged against the packet bus and Maintenance/ Test circuit pack. Refer to repair procedures to clear those errors first. 2. Check every other circuit pack connected to the packet bus in the same cabinet.
PAGE 1818
Communication Manager Maintenance-Object Repair Procedures q. Error Type 3585: a packet-bus failure has been detected and that the packet bus is alarmed. Refer to the packet bus maintenance documentation for further action. r. Error Type 3841: the Packet Interface reported a fatal fault failure condition that might be caused by a packet-bus fault on the PN containing the failed PKT-INT. ● If Error Type 3585 has also been reported, see PKT-BUS (Packet Bus) on page 1790.
PAGE 1819
PKT-INT (Packet Interface) Memory Checksum Test (#884) This test involves sending a message to the Packet Interface module to run private nondestructive memory checksum tests on the firmware text residing in Boot PROM and FLASH memory on the IPSI circuit pack. If the test fails during background testing, the Packet Interface module remains operational until an executed reset. Then, the initialization firmware fails and puts the Packet Interface in an out-of-service state.
PAGE 1820
Communication Manager Maintenance-Object Repair Procedures Table 669: Test #884 Memory Checksum Test (continued) Error Code Test Result Description / Recommendation NO BOARD The IPSI circuit pack’s Packet Interface module is assigned, but is not detected as being physically present. 1. If the IPSI circuit pack is present, replace it. 2. If the IPSI circuit pack is not present, insert a TN2312AP IPSI circuit pack in the assigned slot, and run the test again.
PAGE 1821
PKT-INT (Packet Interface) Table 669: Test #884 Memory Checksum Test (continued) Error Code Test Result Description / Recommendation 2 FAIL The Flash memory checksum test failed. The circuit pack may still be operational, but will fail if a reset is executed. 1. This may be the result of old firmware not supporting new software operation. Verify the IPSI circuit pack’s firmware vintage and download the new firmware if appropriate. 2. The firmware image on the IPSI circuit pack may have been corrupted.
PAGE 1822
Communication Manager Maintenance-Object Repair Procedures ● Broadcast Link Loop Around Each ISDN-BRI port has two associated broadcast signaling links, one for call control, and one for maintenance and management. Since these links have separate routing circuitry from the Level-2 Loop Around, this test forces a CRC error to verify the CRC hardware associated with the broadcast data path. These tests are also run as part of the reset tests.
PAGE 1823
PKT-INT (Packet Interface) Table 670: Test #885 Private Loop-Around Tests (continued) Error Code Test Result Description / Recommendation NO BOARD The IPSI circuit pack’s Packet Interface module is assigned, but is not detected as physically present. 1. If the IPSI circuit pack is present, replace it. 2. If an IPSI circuit pack is not present, insert a TN2312AP IPSI circuit pack in the assigned slot, and rerun the test. 1 FAIL The Private Link Broadcast Loop-Around test failed.
PAGE 1824
Communication Manager Maintenance-Object Repair Procedures Table 670: Test #885 Private Loop-Around Tests (continued) Error Code Test Result Description / Recommendation 2 FAIL The Private Level-2 Loop-Around test failed. When this occurs, the Packet Interface module on the IPSI Circuit pack enters a fatal-fault state, and the Packet Interface maintenance software should put the Packet Interface out of service.
PAGE 1825
PKT-INT (Packet Interface) Maintenance Loop-Around Test (#886) This test checks whether an IPSI circuit pack’s Packet Interface module correctly sends and receives data. It establishes a LAPD link from the IPSI’s Packet Interface module back to the same Packet Interface module, and transmits and receives test data over that testing link.
PAGE 1826
Communication Manager Maintenance-Object Repair Procedures Table 671: Test #886 Maintenance Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1373 ABRT Could not establish the link loop around link to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2060 ABRT 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 1827
PKT-INT (Packet Interface) Table 671: Test #886 Maintenance Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1–5 FAIL Fail Codes 1 - 4: 1 = Did not receive looparound data 2 = Looparound data not correct length 3 = Looparound data did not match 4 = Transmit buffer exhaustion Either maintenance could not establish a loop-around link from the IPSI’s Packet Interface module back to itself, or it could not receive data that was sent on one side of the loop-around link. 1.
PAGE 1828
Communication Manager Maintenance-Object Repair Procedures Table 671: Test #886 Maintenance Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1–5 FAIL Fail Code 5: old firmware not compatible with new software. (cont’d) 1. Verify the IPSI circuit pack’s firmware vintage and download the new firmware if appropriate. Note: Note: At the Avaya support site (http://support.avaya.com) search on “Firmware Compatibility Matrix” to find the latest firmware vintage.
PAGE 1829
PKT-INT (Packet Interface) Running this test on the active IPSI circuit pack’s Packet Interface module reads and clears the Parity Error counter and FIFO Overflow counter. S8700 MC: Those counters are not used when a Packet Interface module is in standby mode. S8700 MC: Running this test on the standby IPSI circuit pack’s Packet Interface module, reads but does not clear a Translation RAM counter.
PAGE 1830
Communication Manager Maintenance-Object Repair Procedures Table 672: Test #887 Read and Clear Board Counters (continued) Error Code Test Result Description / Recommendation 256 512 768 FAIL The active IPSI circuit pack’s Packet Interface module has an error counter set. The following Error Codes are possible: 256 (parity error), 512 (FIFO overflow), 768 (parity error and FIFO overflow error). 1. This may be the result of old firmware not supporting new software operation.
PAGE 1831
PKT-INT (Packet Interface) Table 672: Test #887 Read and Clear Board Counters (continued) Error Code Test Result 256 512 768 (cont’d) FAIL (cont’d) Description / Recommendation 5. If Error Code 512 or 768 is reported for an active IPSI’s Packet Interface module, the receive FIFO in the PKT-INT has overflowed. This may indicate the need for additional IPSI circuit packs. For the current hardware configuration, only one IPSI circuit pack is allowed per PN.
PAGE 1832
Communication Manager Maintenance-Object Repair Procedures Table 672: Test #887 Read and Clear Board Counters (continued) Error Code Test Result Description / Recommendation 1024– 1096 FAIL Firmware 1. This may be the result of old firmware not supporting new software operation. Verify the IPSI circuit pack’s firmware vintage and download the new firmware if appropriate. 2. The firmware image on the IPSI circuit pack may have been corrupted. Download the firmware image. 3. Retry the command. 4.
PAGE 1833
PKT-INT (Packet Interface) S8700 MC Active-Standby Peer Link Test (#888) The Active-Standby Peer Link test is run only in a system equipped with the high- or critical-reliability configuration. It verifies that a peer link can be set up between the active and standby PKT-INTs. A peer link is a logical connection established between the packet bus and an IPSI circuit pack’s Packet Interface module for both active and standby IPSIs.
PAGE 1834
Communication Manager Maintenance-Object Repair Procedures Table 673: Test #888 Active-Standby Peer Link Test (continued) Error Code Test Result Description / Recommendation 1336 ABRT Internal system error. 1. Use set ipserver-interface location to make the standby Packet Interface active. 2. Run the test. 1337 ABRT The test is not allowed to run because a PNC interchange is in progress. A PNC interchange may have been initiated with reset pnc interchange, or as part of a recovery action. 1.
PAGE 1835
PKT-INT (Packet Interface) Table 673: Test #888 Active-Standby Peer Link Test (continued) Error Code Test Result Description / Recommendation 1 FAIL Setting up peer links between the active and standby IPSI circuit pack’s Packet Interface modules failed. The standby IPSI circuit pack’s Packet Interface module did not respond to the peer link setup. 1. This may be the result of old firmware not supporting new software operation.
PAGE 1836
Communication Manager Maintenance-Object Repair Procedures Reset Test (#889) The reset action initializes the Packet Interface firmware on the IPSI circuit pack and runs a comprehensive set of diagnostic tests. The demand-reset action aborts if the specified IPSI circuit pack’s Packet Interface module is in the active in-service state.
PAGE 1837
PKT-INT (Packet Interface) Table 674: Test #889 Reset Test (continued) Error Code Test Result Description / Recommendation NO BOARD The IPSI circuit pack’s Packet Interface module is assigned but is not detected as physically present. 1. If the IPSI circuit pack is present, replace it. 2. If not, insert a TN2312AP IPSI circuit pack in the assigned slot, and rerun the test. 5001 ABRT The TDM clock in the Processor port network has failed. 1.
PAGE 1838
Communication Manager Maintenance-Object Repair Procedures PLAT-ALM (Platform Alarms) S8700 | 8710 / S8500 / S8300 The PLAT-ALM is a virtual MO used by Communication Manager to keep track of its media server and G700/G350 media gateway alarms. A MAJOR, MINOR, or WARNING alarm can be logged against this MO to indicate the presence of one or multiple: Note: ● S8700, S8500, and S8300 media server alarms ● G700 media gateway alarms Note: The MO initials “CMG” can be seen in some G700 traps.
PAGE 1839
PMS-LINK (Property Management System Link) PMS-LINK (Property Management System Link) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PMS-LINK MIN test pms-link l PMS Link PMS-LINK WRN test pms-link 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 1840
Communication Manager Maintenance-Object Repair Procedures Procedures for Restoring the PMS Link 1. Determine the status of the PMS Link. Enter status pms-link, and make sure that the PMS Link is not busied out for maintenance. If the link is “down,” then continue with the next step. 2. Where does the PMS Link connect? Enter display system-parameters hospitality, and find out the destinations of the PMS Link. 3. Determine the status of the data extension.
PAGE 1841
PMS-LINK (Property Management System Link) Table 675: PMS Link Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1025 (f) 40–49 None 1281 (g) 10–19 None 1537 (h) N0–N9 None 1793 (i) Any None 2049 (j) Any None 2305 (k) 50–59 None release pms-link, or test pms-link 2561 (l) Any None test pms-link 2817 (m) 100–109 200–209 300–309 None 3073 (n) 70–79 None 3841 (o) 20–29 None test pms-link 2 of 2 1.
PAGE 1842
Communication Manager Maintenance-Object Repair Procedures e. Error Type 769: there has been no communication between the switch and the PMS for a period of time specified in “system hospitality” administration. The PMS Link is torn down. To clear this error, see Procedures for Restoring the PMS Link on page 1840. f. Error Type 1025: The link was taken down because the switch could not receive an incoming message from the PMS.
PAGE 1843
PMS-LINK (Property Management System Link) l. Error Type 2561: the PMS Link is physically established, but the protocol has not been started by the PMS before the protocol timer expires. 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. Once the PMS Link is successfully established, this error disappears from the Hardware Error Log.
PAGE 1844
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence. Order of Investigation Short Test Sequence Link Tear Down test (#213) Link Retry test (#215) X Long Test Sequence D/ND X Destructive X Nondestructive Link Tear Down Test (#213) This test is destructive.
PAGE 1845
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. Table 677: Test #215 Link Retry Test Error Code Test Result Description / Recommendation 10 20 ABRT Internal system error. 30 ABRT 1. Retry the command at 1-minute intervals up to 5 times. Internal system error. 1.
PAGE 1846
Communication Manager Maintenance-Object Repair Procedures PMS-PRNT/JNL-PRNT (PMS Printer Link) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO PMS-PRNT/JNL-PRNT MIN test journal [pms-log | wakeup-log] long PMS Printer/ Journal Printer PMS-PRNT/JNL-PRNT WRN test journal [pms-log | wakeup-log] PMS Printer/ Journal Printer A journal printer is a printer to which Emergency Access to Attendant, Wakeup and Property Management System (PMS) events are prin
PAGE 1847
PMS-PRNT/JNL-PRNT (PMS Printer Link) PMS Printer Link Maintenance does not cover the maintenance of the elements composing the journal printer physical link (for instance, the external printer device, Data Module (PDM/MPDM/ DTDM), Digital Line Port or ADU and Data Line Port). If PMS Printer Link maintenance cannot restore the PMS Printer Link, then the maintenance tests of individual components of the PMS Link must be executed to diagnose faults.
PAGE 1848
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 678: PMS-PRNT/JNL-PRNT Link Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test journal wakeup-log | pms-log sh 18 (b) 0 busyout journal wakeup-log | pms-log WRN OFF release journal wakeup-log | pms-log 257 (c) Any Link Retry test (#215) MIN1 WRN OFF test journal wakeup-log | pms-log long 513 (
PAGE 1849
PMS-PRNT/JNL-PRNT (PMS Printer Link) e. Error Type 769: link idle timer; link comes down. 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 to set up the printer link. System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below.
PAGE 1850
Communication Manager Maintenance-Object Repair Procedures Table 679: Test #213 Link Tear Down Test (continued) Error Code Test Result Description / Recommendation FAIL Internal System error. 1. Retry the command at 1-minute intervals up to 5 times. PASS The link is torn down. 2 of 2 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.
PAGE 1851
PNC-DUP (PNC Duplication) PNC-DUP (PNC Duplication) S8700 MC only MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO PNC-DUP NA status pnc PNC duplication In systems with the Critical Reliability option, the following components, which together comprise the Port Network Connectivity (PNC), are duplicated: ● Expansion Interface (EI) TN570 circuit packs in the port networks (PNs) ● Switch Node Interface (SNI) TN573 circuit packs in switch nodes ● DS1 Converter (DS1C) TN574
PAGE 1852
Communication Manager Maintenance-Object Repair Procedures PNC-DUP Related Commands The following commands are described in Maintenance Commands Reference (03-300191). status pnc Lists information about the operational status of both PNCs including state of health, alarms, busyouts and locks. reset pnc interchange Initiates a demand PNC interchange. If the standby is healthy with state of health indexes all 0, there is no effect on service. Otherwise, calls may be dropped.
PAGE 1853
PNC-DUP (PNC Duplication) Figure 110: Duplicated Direct Connect PNC Connectivity EPN 1 EPN 2 EPN 3 EI EI EI EI EI IPSI A T/C AA PKT-INT TDM PORT CARRIER EI LAN EI EI MAINT/ Test EI EI EI EI PORT CARRIER LAN TDM T/C AA PKT-INT IPSI B Issue 1 June 2005 1853
PAGE 1854
Communication Manager Maintenance-Object Repair Procedures Figure 111: Duplicated PNC with Center Stage Switch Connectivity EPN IPSI A T/C AA TDM PKT-INT LAN 5 SWITCH NODE MAINT/ Test EI EI ....... EPN 11 EPN 10 S N I S N I S N I S N I S N I S N I S N I CSS A EI ......
PAGE 1855
PNC-DUP (PNC Duplication) Enabling and Removing PNC Duplication Note: Note: PNC duplication requires IPSI duplication. To Enable PNC Duplication To enable PNC duplication: 1. Enable PNC-DUP on the change system-parameters customer-options screen. 2. Fully administer duplicate fiber link connectivity. Verify by issuing list fiber-link. For IP Duplication go to Step 3. 3. Fully administer IPSI duplication (ipserver-interface duplication). Verify by using list ipserver-interface. 4.
PAGE 1856
Communication Manager Maintenance-Object Repair Procedures 4. Remove the B-PNC fibers by removing the Endpoint Board Locations on the change fiber-link screen for all fibers. For fibers using DS1Cs, remove the B-PNC DS1C Board Locations on the change fiber-link screen. 5. Remove the B-PNC circuit packs starting with the switch node carrier most distant from the media server complex. Use change circuit-pack location, page to the B-PNC carrier and remove all of the circuit packs there.
PAGE 1857
PNC-DUP (PNC Duplication) ● Standby DS1Cs amber LEDs are off. ● DS1C facility green LEDs are on if the corresponding facility is equipped. PNC State of Health PNC-DUP software monitors the health of the two PNCs as determined by their state of health (SOH) vectors, and initiates an interchange when the health of the active falls below that of the standby (unless prevented from doing so by a PNC lock, busyout, or anti-thrashing mechanism).
PAGE 1858
Communication Manager Maintenance-Object Repair Procedures The Inter-PN Index contains six fields (XX.XX.XX.XX.XX.XX), and the Inter-SN Index has two (XX.XX). The Inter-PN Index reports faults in connectivity between port networks and supersedes the Inter-SN Index, which reports faults in connectivity between switch nodes. (The Inter-SN Index is only meaningful for systems with a center stage switch having two switch nodes, each of which is duplicated).
PAGE 1859
PNC-DUP (PNC Duplication) In multi-node CSS configurations FC_DS1 is considered less critical that FC_SNINL since DS1C constraints affect only one PN and indicate restricted bandwidth. However FC_SNINL can indicate problems for all PNs on the far end switch node (the one downlink from the PN) If the DS1C problem is critical (for example, loss of all bandwidth to the affected PN) a constraint with a higher order fault class will be reported to PNC DUP.
PAGE 1860
Communication Manager Maintenance-Object Repair Procedures PNC Interchanges PNC spontaneous interchanges occur when PNC duplication software determines that the SOH of the standby PNC is better than that of the active PNC.
PAGE 1861
PNC-DUP (PNC Duplication) Antithrashing and PNC Interchanges Following a spontaneous PNC interchange, subsequent PNC interchanges are prevented for 5 minutes. This condition is indicated by a y in the Interchange Disabled field of the status PNC screen. After 5 minutes, the anti-thrashing, timer expires, interchange decisions are re-enabled, and the field entry is n.
PAGE 1862
Communication Manager Maintenance-Object Repair Procedures 3. At this point, the faulty component is on the standby PNC, and the PNCs are locked in their current active/standby state. Busy-out the PNC. 4. Use fault isolation and component testing procedures for the individual PNC components. Replacement of components will not disrupt operation of the active PNC. 5. Once the failed component is replaced, test the standby PNC component from the terminal to ensure the replacement is functioning properly. 6.
PAGE 1863
PNC-DUP (PNC Duplication) - If it is not clear which port board may be at fault, or maintenance is being performed remotely, verify that the EAA is not at fault by executing a PNC interchange. If the interchange solves the problem, then the EAA is faulty. - If the problem persists after the interchange, but TDM bus maintenance finds no problem, then the port board is faulty.
PAGE 1864
Communication Manager Maintenance-Object Repair Procedures Error Type Aux Data Error Code Aux Data 11701 – 11764 (p) 1 53000 (ah) 1 20000 – 20063 (q) 1 60801 (ai) 1 20100 – 20163 (r) 1 60800 (aj) 1 2 of 2 1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes PNC-A; “1” denotes PNC-B. Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 None busyout pnc-dup WRN ON release pnc-dup Notes: a.
PAGE 1865
PNC-DUP (PNC Duplication) f. Error Type 10400-10463: a spontaneous PNC interchange took place in response to the retiring of an alarm on the A-PNC associated with fault class FC_DS1. Use status pnc to look at the state of health indexes for the PNCs, and investigate any associated alarms. Adding 1 to the last two digits of the Error Code gives the PN number of the port network that reported the retired alarm. (10403 points to port network 4.
PAGE 1866
Communication Manager Maintenance-Object Repair Procedures m. Error Type 11300 – 11363: a spontaneous PNC interchange took place in response to the occurrence of a major or minor alarm on the A-PNC associated with fault class FC_PER. This indicates one or more faults on peer links that connect SNIs to EIs. Investigate any alarms against SNI-PEER. Adding 1 to the last two digits of the Error Code gives the PN number of the port network that reported the alarm. (11303 points to port network 4.
PAGE 1867
PNC-DUP (PNC Duplication) t. Error Type 20300 – 20363: a spontaneous PNC interchange took place in response to the retiring of an alarm on the B-PNC associated with fault class FC_PER. Use status pnc to look at the state of health indexes for the PNCs, and investigate any associated alarms. Adding 1 to the last two digits of the Error Code gives the PN number of the port network that reported the retired alarm. (20303 points to port network 4.
PAGE 1868
Communication Manager Maintenance-Object Repair Procedures aa. Error Type 21200-21263: a spontaneous PNC interchange took place in response to the occurrence of a major or minor alarm on the B-PNC associated with fault class FC_HW. This indicates that one or more neighbor or indirect neighbor links with an EI as an endpoint have experienced faults. Investigate any alarms against EXP-PN and SN-CONF.
PAGE 1869
POWER POWER S8700 MC This MO covers maintenance for: ● Battery and Charger for AC-Powered Systems on page 1869 ● Battery and Charger for DC-Powered Systems on page 1878 Battery and Charger for AC-Powered Systems MO Name in Alarm Log Alarm Level Initial Command to Run POWER MIN test environment C Full Name of MO 1 Battery and Battery Charger 1. C is the cabinet number indicated in the PORT field from the Alarm or Error Log.
PAGE 1870
Communication Manager Maintenance-Object Repair Procedures In a multicarrier-cabinet system, the Battery and Battery Charger MO represents the battery charger and the battery which are located in the lower left corner of the cabinet. Should anything go wrong with the battery or charger, they must be replaced using the procedure described in Replacing the Battery and Battery Charger (J58890CE) on page 1870.
PAGE 1871
POWER 7. Close the cover and secure it with the screw. 8. Reconnect the cord and move the power switch to ON. Replacing the Battery Assembly (J58890CH) The batteries are replaced as an entire assembly. 1. Check the battery voltages at the test points on the BIU (Battery Interface Unit). 2. Remove the BIU from the power distribution unit. 3. Disconnect the battery plug from the power distribution unit (J20). 4. Remove the battery assembly from the rear of the cabinet. 5.
PAGE 1872
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1873
POWER Battery and Battery Charger Query Test (#5) This test queries the PN’s Maintenance circuit pack for the status of the battery pack and battery charger, and reports the result. During this test, the status LED on the battery charger is lit and extinguished if the status of the battery charger is reported as normal. This event is a result of checking that the battery charger is connected.
PAGE 1874
Communication Manager Maintenance-Object Repair Procedures Table 684: Test #5 Battery and Battery Charger Query Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. 1. Retry the command at 1-minute intervals up to 5 time. 2. If the test continues to ABORT with Error Code 2000, check for system powering problems with the A carrier.
PAGE 1875
POWER Table 684: Test #5 Battery and Battery Charger Query Test (continued) Error Code Test Result Description / Recommendation 4 FAIL The battery is currently being charged. 1. After 30 hours, the battery should be fully charged, and this error should clear. 2. If after 30 hours the battery is still in the high charge rate, an alarm will be raised. Use display errors to see the Error Log, and select the category “environs” to show only environment-related errors. Look for POWER errors of type 257.
PAGE 1876
Communication Manager Maintenance-Object Repair Procedures Table 684: Test #5 Battery and Battery Charger Query Test (continued) Error Code Test Result Description / Recommendation 8 FAIL For a global AC MCC (J58890CH), use the procedures outlined in step 3. There is a reserve power fault. A problem exists with the battery charger or, less likely, the batteries. Also, this fault could be generated if the charger is switched off or a battery is unplugged. 1. Replace the battery charger and the battery.
PAGE 1877
POWER Table 684: Test #5 Battery and Battery Charger Query Test (continued) Error Code Test Result 8 (cont’d) FAIL (cont’d) Description / Recommendation d. If there is an alarm and every LED is OK (PWR OK and BOK) on the rectifier modules and the BIU (Battery Interface Unit), make sure the BIU and the RM0850 rectifiers are seated properly (plugged in). If the BOK LED on the BIU is OK, check the number of rectifiers serving this cabinet: No. of carriers/cabinet No.
PAGE 1878
Communication Manager Maintenance-Object Repair Procedures Battery and Charger for DC-Powered Systems MO Name in Alarm Log Alarm Level Initial SAT Command to Run POWER MIN test environment UU 1 Full Name of MO Battery and Battery Charger 1. UU is the cabinet number indicated in the PORT field from the Alarm or Error Log. Note: This MO applies to the J58890CE and the J58890CH-1 with large battery holdover. Note: This MO represents the battery backup unit found in AC-powered multicarrier cabinets.
PAGE 1879
POWER Battery Holdover (Large Batteries) The large batteries are mounted inside a separate battery cabinet and can supply holdover times of 2 to 8 hours depending on the size of the battery. The batteries are circuit breaker protected and are charged by the J58890CH-1. The batteries also contain a thermal sensor that change the charging voltage depending on the battery temperature. System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below.
PAGE 1880
Communication Manager Maintenance-Object Repair Procedures c. See EMG-XFER (Emergency Transfer) on page 1134 for a description of this test. d. See CABINET (Cabinet Sensors) on page 758 for a description of this test. e. See EXT-DEV (External device alarm) on page 1240 for a description of this test. f. See RING-GEN (Analog Ring Generator) on page 1942 for a description of this test.
PAGE 1881
POW-SUP (power supply) POW-SUP (power supply) G650 MO name in Alarm Log Alarm level1 Initial SAT command to run Full name of MO POW-SUP WRN test board location Power Supply POW-SUP MIN test board location Power Supply POW-SUP MAJ test board location Power Supply 1. This is a minor alarm if there is a redundant power supply, and a major alarm if there is only one power supply.
PAGE 1882
Communication Manager Maintenance-Object Repair Procedures Recycle carrier (demand only, Test #1534) The recycle carrier command is useful for three different troubleshooting actions: ● To verify that a redundant power supply can carry the full load. This is done by issuing the SAT command recycle carrier location with the slot number of the power supply that is to be momentarily shut down. Each power supply monitors the voltage on the backplane and not the voltages from the power supply itself.
PAGE 1883
POW-SUP (power supply) Error log entries and test-to-clear values Table 687: POW-SUP Hardware Error Log Error Type Aux Data Associated test Alarm level 1 On/Off board Test-to-clear value 1 (a) Any Power supply detection test (#1535) MAJ MIN ON test environment location test board location recycle carrier location [override] 23 (b) Power supply recycle test (#1534) WRN ON test environment location test board location recycle carrier location [override] 257 (c) Power supply recycle test (#1
PAGE 1884
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 1: power supply not detected. b. Error Type 23: the power supply is administered, but not present. 1. Verify that the power is plugged in. 2. Check the yellow LED to determine that the power is on. c. Error Type 257: recycle failed (recycle carrier demand test). Aux Data shows the failure(s), according to the table below (Aux Data values may be added together).
PAGE 1885
POW-SUP (power supply) 1. Run test board location. Aux Data Description 1 Analog-to-digital converter failure 2 Digital-to-analog converter failure 4 Internal Mux failure 8 EEPROM failure 64 Calibration contents CRC check failure 128 Power supply firmware CRC check failure i. Error Type 1793: operational failure. 1. Run test board location. Aux Data Description 1 No AC or DC input 2 The power supply is off because of a system command.
PAGE 1886
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1887
POW-SUP (power supply) Table 688: Power supply recycle test (#1534) (continued) Error code Test result Description and recommendation 1973 ABRT The carrier does not contain a redundant power supply. 1977 ABRT There is an active Expansion ArchAngel (EAA) in the carrier that a recycle was attempted on. Recycling the carrier with the active EAA will result in loss of network control to the entire port network. 1.
PAGE 1888
Communication Manager Maintenance-Object Repair Procedures Table 688: Power supply recycle test (#1534) (continued) Error code Test result Description and recommendation PASS The power supply recycle test passes. NO BOARD Power supply is administered but not detected. 1. Verify that the power supply is plugged in. 2. Replace the power supply. 3 of 3 Power supply detection test (#1535) The power supply detection test verifies that: ● The power supply is detected.
PAGE 1889
POW-SUP (power supply) Table 689: Test 1535 power supply detection test (continued) Error code Test result Description and recommendation 11 FAIL The system does not detect a power supply. 1. Verify that the power supply is plugged in. 2. Verify that the yellow LED on the power supply is lit and that at least one of the two green input power LEDs is lit. ● If the yellow LED is OFF and/or the red LED is ON, replace the power supply.
PAGE 1890
Communication Manager Maintenance-Object Repair Procedures Table 689: Test 1535 power supply detection test (continued) Error code Test result Description and recommendation PASS The power supply detection test passes. NO BOARD Power supply is administered but not detected. 1. Verify that the power supply is plugged in. 2. Replace the power supply. 3 of 3 1.
PAGE 1891
POW-SUP (power supply) Table 690: Test #1536 power supply voltage (continued) Error code Test result Description and recommendation 2500 ABRT An internal operation failed. 1. Retry the command. 2. Escalate the problem if the test continues to abort. 11 FAIL The +5V is out of tolerance. 1. Use the status environment command to check the voltages. a. +5V (+/- 5%) (4.75 to 5.25 V) 2. If redundant power supplies are present, there may be a problem with the backplane.
PAGE 1892
Communication Manager Maintenance-Object Repair Procedures Table 690: Test #1536 power supply voltage (continued) Error code Test result Description and recommendation 41 FAIL The -48V is out of tolerance. 1. Use the status environment command to check the voltages: 48V (+/- 8%) (- 44.2 to 51.8 V) 2. If redundant power supplies are present, there may be a problem with the backplane.
PAGE 1893
PPP-PT (Control LAN Packet/Port) PPP-PT (Control LAN Packet/Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PPP-PT MAJ test port location long PPP Port Maintenance PPP-PT MIN test port location long PPP Port Maintenance PPP-PT WRN test port location PPP Port Maintenance The TN799DP Control LAN (C-LAN) packet port circuit pack provides TCP/IP connection to adjuncts applications such as CMS, INTUITY, and DCS Networking.
PAGE 1894
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Value Table 691: PPP-PT Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location s 1 (b) 0 SCOTCH Sync Loop- Around (#1275) MIN ON test port location l r 3 257 (c) 0 WRN OFF 513 (d) 0 MIN OFF 769 (e) 0 WRN OFF 1281 (f) 0 1537-8 (g) See note Session Status test (#1286) MIN OFF 1793– 1920 (h) See n
PAGE 1895
PPP-PT (Control LAN Packet/Port) 2. See SCOTCH Synchronous Loop-Around Test (#1275) on page 1898 for repair procedures to verify repair. 3. Clear the alarm (test port location long clear). d. Error Type 513: PPP link lost end-to-end connectivity. 1. Test for hardware problem (test port location long). 2. Run TDM Loop-Around Test (#1285) on page 1897, 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. e.
PAGE 1896
Communication Manager Maintenance-Object Repair Procedures i. Error Type 2305-2816: 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. j. Error Type 3329: TCP/IP Ping test failed. 1. Test the port (test port location short). 2. See TCP/IP Ping Test (#1281) on page 1900 for repair procedures. k. Error Type 3585: TDM Port Loop-around test (#1285) failed. 1.
PAGE 1897
PPP-PT (Control LAN Packet/Port) TDM Loop-Around Test (#1285) 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. The tones are looped through the ppp port.
PAGE 1898
Communication Manager Maintenance-Object Repair Procedures Table 692: Test #1285 TDM Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Did not receive circuit pack test response within the allowable time period. 1. If this problem persists, reset the circuit pack (busyout board location, reset board location, and release board location). 2. If the problem persists, replace the circuit pack. 2012 ABRT Internal system error. 1.
PAGE 1899
PPP-PT (Control LAN Packet/Port) Table 693: Test #1275 SCOTCH Synchronous Loop-Around Test Error Code Test Result Description / Recommendation 1000 ABRT The port is in use or PPP link is connected. 1. Use status clan-port location to determine when the port is available for testing. 2. Use busyout port location to force the port to the idle state. This command is destructive, causing every call and link using the port to be torn down. 1002 ABRT No TDM bus timeslots available for the test. 1.
PAGE 1900
Communication Manager Maintenance-Object Repair Procedures 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 694: Test #1281 TCP/IP Ping Test Error Code Test Result Description / Recommendation 1 2 7 11 ABRT Internal error 1005 ABRT 1. Retry the command at 1-minute intervals up to 3 times Test configuration is incorrect. 1.
PAGE 1901
PPP-PT (Control LAN Packet/Port) Table 694: Test #1281 TCP/IP Ping Test (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times. 2100 ABRT Could not allocate the necessary system resources to run test. 1. Retry the command at 1-minute intervals up to 5 times. 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 1902
Communication Manager Maintenance-Object Repair Procedures Session Status Test (#1286) This nondestructive test determines the status of every PPP port session. This test queries the system software on port session status.
PAGE 1903
PPP-PT (Control LAN Packet/Port) Table 695: Test #1286 Session Status Test (continued) Error Code Test Result Description / Recommendation 2500 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 3 times. 1 FAIL System software indicates at least one PPP link session is down (SOME UP). 1. Isolate downed sessions (status port location or status link n). Follow actions based on session information. 2 FAIL System software indicates every PPP session is down (ALL DOWN). 1.
PAGE 1904
Communication Manager Maintenance-Object Repair Procedures Table 696: Test #1279 PPP Link Status Inquiry Test (continued) Error Code Test Result Description / Recommendation 1125 ABRT PPP Link is not in service. 1. Verify whether PPP link is in-service (status port location or status link n). 2. If the PPP link is not in service, release the link (release link n or release port location). 3. Repeat the test. 2100 ABRT Could not locate the necessary system resources to run this test. 1.
PAGE 1905
PRI-CDR (Call Detail Recording Link) PRI-CDR (Call Detail Recording Link) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO PRI-CDR/SEC-CDR MIN test cdr primary | secondary l CDR Link PRI-CDR/SEC-CDR WRN 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 1906
Communication Manager Maintenance-Object Repair Procedures 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 1907
PRI-CDR (Call Detail Recording Link) Error Log Entries and Test to Clear Values Table 697: CDR Link Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test cdr-link primary | secondary sh 18 (b) 0 busyout cdr-link primary|secondary WRN OFF release cd-link primary | secondary 257 (c) Any Link Retry test (#215) MIN1 WRN OFF test cd-link primary | secondary l 513 (d) test cdr-link primary | secondary 1025
PAGE 1908
Communication Manager Maintenance-Object Repair Procedures 3. Use display system-parameters maintenance to see the start time of daily maintenance. 4. If the error occurs and is resolved during of daily maintenance, it can be ignored. e. Error Type 1025: the CDR output device is in an off-line state, (for example, due to paper jam or paper out for a printer device). The CDR link is torn down. 1. Check the CDR output device and act promptly to put it back to on-line state. 2.
PAGE 1909
PRI-CDR (Call Detail Recording Link) 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 already been disconnected, the test returns PASS. Every resource allocated for a CDR link is released after this test. Table 698: Test #213 Link Tear Down Test Error Code Test Result Description / Recommendation 40 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1910
Communication Manager Maintenance-Object Repair Procedures 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. Table 699: Test #215 Link Retry Test Error Code Test Result Description / Recommendation 10 ABRT Internal system error. 20 ABRT Internal system error. 1.
PAGE 1911
PROC-SAN (Process Sanity Audits) PROC-SAN (Process Sanity Audits) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm 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. If the Process Sanity Audits MO detects that a process has gone insane (does not respond to a sanity message within an allotted time period), the process will be restarted.
PAGE 1912
Communication Manager Maintenance-Object Repair Procedures PS-RGEN (Power supply ring generator) G650 MOs name in Alarm Log Alarm level Initial SAT command to run Full name of MO PS-RGEN MIN test board location Power Supply Ring Generator PS-RGEN MAJ test board location Power Supply Ring Generator The PS-RGEN maintenance object monitors the ringing voltage of each 655A power supply. The TN2312BP IPSI uses the ring detection circuit on the 655A to monitor ring voltage for the G650.
PAGE 1913
PS-RGEN (Power supply ring generator) Table 701: PS-RGEN Error Log Entries (continued) Error Type Aux Data 257 (b) Associated test Alarm level On/Off board Test-to-clear value Ring generator status test (#1540) MAJ MIN1 ON test environment location test board location 512 1 513 (c) Any Ring generator status test (#1540) MAJ MIN ON test environment location test board location 769 64 Ring generator status test (#1540) MAJ MIN ON test environment location test board location 1025 64
PAGE 1914
Communication Manager Maintenance-Object Repair Procedures System technician-demanded tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1915
PS-RGEN (Power supply ring generator) Table 702: Test #1539 Ring generator interchange (continued) Error Code Test result Description and recommendation 2028 ABRT There is a problem communicating with the environmental maintenance firmware. 1. Enter test maintenance nn to verify communication with the port network. 2100 ABRT The system could not allocate resources. 1. Repeat the command at one-minute intervals 1 to 3 times. 2. If the test continues to abort escalate the problem.
PAGE 1916
Communication Manager Maintenance-Object Repair Procedures Ring Generator Status Test (#1540) The ring generator status test verifies that: 1. The power supply ring voltage detector detects the presence of ringing voltage 2.
PAGE 1917
PS-RGEN (Power supply ring generator) Table 703: Test 1540 Ring generator status (continued) Error Code Test Result Description / Recommendation 4 FAIL There is an internal fault in the ring generator. 1. Run test board location 2. If the test continues to fail replace the power supply. 8 FAIL The ring generator is off by command. 1. Run test board location 2. If the test continues to fail replace the power supply. 16 FAIL The ringer on the primary power supply is not active. 1.
PAGE 1918
Communication Manager Maintenance-Object Repair Procedures RANL-STA (Remote Analog Line (Station) Port) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO RANL-STA MIN test port location l Remote Analog Line Port RANL-STA WRN test port location sh Remote Analog Line Port A per-port instance of this MO (RANL-STA) is used to maintain the circuitry associated with a port which has been translated as analog station.
PAGE 1919
RANL-STA (Remote Analog Line (Station) Port) Table 704: Analog Line Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 0 busyout station extension WRN ON release station extension 257 (d) 40973 none 513 (e) Station Present test (#48) WRN OFF test port location sh r 2 769 Battery Feed test (#35) MIN WRN1 ON test port location sh r 2 2817 (f) Hyperactive MIN OFF 2 of 2 1.
PAGE 1920
Communication Manager Maintenance-Object Repair Procedures e. Error Type 513: Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this disturbs the customer or the terminal equipment, disable it by setting the Tests field on the change station extension screen to n. On some software releases, this will also disable Tests #7 and 35. f.
PAGE 1921
RANL-STA (Remote Analog Line (Station) Port) Table 705: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is. 1. Enter display port location to determine the station’s extension.
PAGE 1922
Communication Manager Maintenance-Object Repair Procedures Table 705: Test #35 Battery Feed Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. FAIL The port's battery feed chip is unable to supply sufficient power to the terminal equipment. This could be a marginal test, and the terminal equipment may be operating satisfactorily. 1.
PAGE 1923
RANL-STA (Remote Analog Line (Station) Port) Table 706: Test #36 Station Status and Translation Audits and Updates (continued) Error Code Test Result Description / Recommendation 1005 ABRT The test was aborted due to a configuration problem. This test may not be applicable, or it may be disruptive to terminal equipment other than a voice terminal (for example, the modem pool member or Music On Hold). 2000 ABRT Response to the test request was not received within the allowable time period. 1.
PAGE 1924
Communication Manager Maintenance-Object Repair Procedures 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. If this ringing disturbs the customer or the terminal equipment, disable it using the Tests field on the Station screen.
PAGE 1925
RANL-STA (Remote Analog Line (Station) Port) Table 707: Test #48 Station Present Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT The test has been disabled by administration. The default for the Test field on the change station screen is y. Determine why this field has been set to n on this station (this may be due to the brief ringing disturbance that this test may cause). 1.
PAGE 1926
Communication Manager Maintenance-Object Repair Procedures RDIG-STA (Remote Digital Station) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO RDIG-STA MIN test station location l Remote Digital Station RDIG-STA WRN test station location sh Remote Digital Station A per-port instance of this MO (RDIG-STA) is used to maintain the circuitry associated with a port which has been translated as a digital station (or DCP Console).
PAGE 1927
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 1. 84xx multi button digital voice terminals (8403D01A, 8410B, 8410D02A, 8434D01A) with optional expansion module. 2. 603A1 and 603D1 Callmaster terminals for telemarketing applications. 3. 302B1 and 302C1 attendant console.
PAGE 1928
Communication Manager Maintenance-Object Repair Procedures Nonvolatile Memory Nonvolatile memory stores downloadable parameters in programmable terminals. Once the terminal is downloaded, it is not be necessary to download it again, even if power is removed from the terminal. If nonvolatile memory fails with power still present, the terminal reverts to its default factory settings except for its A-law/mu-law companding settings which are stored in RAM.
PAGE 1929
RDIG-STA (Remote Digital Station) 3. Terminal Administration A downloadable terminal is automatically downloaded when translation changes associated with downloadable parameters are made as part of system administration. As shown in the previous table, these changes can be for a specified terminal or may be system-wide. If the change is for a system-level parameter, a background global update request must be submitted to download every programmable terminal.
PAGE 1930
Communication Manager Maintenance-Object Repair Procedures Demand Download Actions 1. Busyout/Release Command A maintenance demand busyout/release request for a station will cause the terminal to be downloaded regardless of its previous download status. 2. Feature Access Code A Refresh Terminal Parameters Feature Access Code can be used to request a terminal download action.
PAGE 1931
RDIG-STA (Remote Digital Station) Possible reasons for no terminal download include: ● Terminal is off-hook. ● Terminal detected a bad checksum. ● Terminal detected a bad or missing EEPROM (refer to Hardware Error Log). ● Terminal is busy programming data from a previous PROGRAM message. ● Terminal is in the Programming Disabled state. ● Terminal is in the Local Program Options mode. ● Terminal is disconnected or out of service (use status station).
PAGE 1932
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description, and follow its procedures. b. Error Type 1 with Aux Data 40987: could be caused by a noisy port or link. This is an off-board problem detected by the port circuit.
PAGE 1933
RDIG-STA (Remote Digital Station) j. Error Type 2304: internal system error. No action is necessary. k. Error Type 2305 with Aux Data 32770: the station went off-hook while it was in the ready-for-service state. Use the status station command to determine the state of the station. The off-hook should have moved the station to ready-for-service. No craft action is necessary.
PAGE 1934
Communication Manager Maintenance-Object Repair Procedures Digital Line Electronic Power Feed/Positive Temperature Coefficient/PPF Test (#11) This is an Electronic Power Feed (EPF) restoration test. In this test, the processor requests that the EPF be turned on for a given port, and an attempt is made to turn on the power supply to the station. If no current is drawn, the station is probably not connected. If an overcurrent condition is sensed, there may be a short in the loop.
PAGE 1935
RDIG-STA (Remote Digital Station) Table 710: Test #11 Digital Line Electronic Power Feed Test (continued) Error Code Test Result Description / Recommendation PASS Electronic Power Feed test passed. The message to turn on the power to the station was successfully sent to the port. Although this test will never actually return a FAIL result except for the Internal system error described above, it will log an error indicating the real results of the test. 1.
PAGE 1936
Communication Manager Maintenance-Object Repair Procedures Table 711: Test #16 DIG-LINE Station Lamp Updates Test (continued) Error Code Test Result Description / Recommendation 1 ABRT This port may have been busied out by system technician. 1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this error type is present, then release the port using release station extension and run the test again. 2. Make sure that the terminal is connected. 3.
PAGE 1937
RDIG-STA (Remote Digital Station) Table 711: Test #16 DIG-LINE Station Lamp Updates Test (continued) Error Code Test 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. 2.
PAGE 1938
Communication Manager Maintenance-Object Repair Procedures Table 712: Test #17 Station (Digital) Audits Test Error Code Test Result Description / Recommendation 1 ABRT Switchhook audit timed out. 1. Make sure voice terminal is connected and repeat test. 2. If test fails, replace voice terminal and repeat test. 2 ABRT ID request fails, health bit returned from voice terminal is bad. 1. Make sure voice terminal is connected and repeat test. 2. If test fails, replace voice terminal and repeat test.
PAGE 1939
RDIG-STA (Remote Digital Station) Table 712: Test #17 Station (Digital) Audits Test (continued) Error Code Test Result Description / Recommendation 1392 ABRT 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 display port, where the display shows that the port is a TTI port, or list config, where the display shows a t for the port. 2. If list config or display port indicate that the port is not a TTI port, escalate the problem.
PAGE 1940
Communication Manager Maintenance-Object Repair Procedures REM-OFF (Remote Office) S8700 | 8710 / S8500 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO REM-OFF MIN ping node-name node-name | ip-address location Remote Office REM-OFF WRN ping node-name node-name | ip-address location Remote Office An instance of this MO (REM-OFF) is associated with every Remote Office box that is administered on the switch.
PAGE 1941
REM-OFF (Remote Office) The aux data associated with this error indicates whether the endpoint that failed to respond was a DCP, Analog, or Signaling Group type. Aux data with a value of: ● 1096 = Analog Line ● 1095 = DCP Line ● 6179 = H.323 Signaling Group System Technician-Demanded Tests: Descriptions and Error Codes There are no demand tests for this MO. Use ping ip-address | node-name to ping the Remote Office.
PAGE 1942
Communication Manager Maintenance-Object Repair Procedures RING-GEN (Analog Ring Generator) S8700 | 8710 MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO RING-GEN MAJ test environment location Analog Ring Generator Analog phones must be provided with a voltage that allows them to ring. The Analog Ring Generator MO represents the device that provides the ringing voltage for every analog phone associated with a given cabinet.
PAGE 1943
RING-GEN (Analog Ring Generator) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1944
Communication Manager Maintenance-Object Repair Procedures e. See EXT-DEV (External device alarm) on page 1240 for a description of this test. Short Test Sequence Long Test Sequence D/ND1 Analog Ring Generator Initialization test (#117) X X ND Analog Ring Generator Query test (#118) X X ND Single-Carrier Cabinet Power Query test (#79) (a) X X ND Emergency Transfer Query test (#124) (b) X X ND External Alarm Lead Query test (#120) (c) X X ND Order of Investigation 1.
PAGE 1945
RING-GEN (Analog Ring Generator) Table 715: Test #117 Analog Ring Generator Initialization Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the request was not received within the allowable time period. 1. Look for TDM-CLK errors and alarms. Resolve every other Tone-Clock problem first. 2. Rerun the test. PASS The active Tone-Clock has successfully been enabled to monitor the ringing voltage level.
PAGE 1946
Communication Manager Maintenance-Object Repair Procedures Table 716: Test #118 Analog Ring Generator Query Test (continued) Error Code Test Result Description / Recommendation FAIL The ringing voltage is below acceptable levels. For a multicarrier cabinet system: 1. If this is a duplicated system, use status port-network to determine the active Tone-Clock circuit pack. 2. Use set tone-clock location to make the standby Tone-Clock circuit pack active 3. Rerun the test. a.
PAGE 1947
RING-GEN (Analog Ring Generator) Table 716: Test #118 Analog Ring Generator Query Test (continued) Error Code Test Result Description / Recommendation FAIL (cont’d) Since the test still fails, the ring generator is defective. a. If the reset button on the ring generator is out, press it in. b. Originate calls to several analog stations on different port circuit packs in different carriers in the affected port network. c. If called stations ring, the fault is cleared. Proceed to Step d.
PAGE 1948
Communication Manager Maintenance-Object Repair Procedures Table 716: Test #118 Analog Ring Generator Query Test (continued) Error Code Test Result Description / Recommendation Procedure for a single-carrier cabinet system: This failure indicates that there is no ringing voltage in the carrier where the active Tone-Clock circuit pack resides. Other carriers may or may not have ringing voltage. 1. If this is a duplicated system, use status system to determine the active Tone-Clock circuit pack.
PAGE 1949
RMB (Remote Maintenance Board) RMB (Remote Maintenance Board) MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO RMB MAJ Not Applicable Remote Maintenance Board Remote Maintenance Board (RMB) functionality for selected media servers is provided by a circuit card that is plugged into the media server. Two different circuit cards are used on the S8500 and S8500B media servers. The S8500 server uses a Remote Supervisor Adapter (RSA) board.
PAGE 1950
Communication Manager Maintenance-Object Repair Procedures RMB-REPORT (Remote Maintenance Board - Report) MO Name in Alarm Log Alarm Level Initial SAT Command to Run Full Name of MO Not Applicable (N/A) N/A N/A Remote Maintenance Board - Report Remote Maintenance Board functionality for the S8500 and S8500B media servers is implemented by circuit cards plugged into the servers. These boards monitor the servers for health and environment integrity.
PAGE 1951
RMC-ENV (Power/Fan Sensors) RMC-ENV (Power/Fan Sensors) G600 only MO Name in Alarm Log Alarm Level Initial Command to Run Full Name of MO RMC-ENV MAJ test environment Power/Fan Sensors The AC Power Supply (650A) for a G600 media gateway (Rack-Mounted Cabinet - RMC) 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 1952
Communication Manager Maintenance-Object Repair Procedures Figure 113: Fan Removal fndpremv LJK 102600 Hardware Error Log Entries and Test to Clear Values Table 718: Cabinet sensors error log entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test environment 1 (b) Any Cabinet Temperature or Voltage Query test (#122) MAJ ON test environment Notes: a. Error Type 0: run the short test sequence first.
PAGE 1953
RMC-ENV (Power/Fan Sensors) (e.g., fan blockage), a single event may be an anomaly that eventually clears. However, a repeating condition causes a major alarm. On-Demand Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1954
Communication Manager Maintenance-Object Repair Procedures Table 719: TEST #122 Cabinet Temperature Query Test (continued) Error Code Test Result Description / Recommendation 2029 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 1 FAIL There is a fan, temperature, power, or voltage problem in one or more of the cabinets. The power supply’s LEDs may indicate the problem’s source. 1.
PAGE 1955
RMC-ENV (Power/Fan Sensors) Table 719: TEST #122 Cabinet Temperature Query Test (continued) Error Code Test Result 1 FAIL (cont’d) 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. ● Check filter; if the filter is dirty or clogged it should be cleaned or replaced. The filter can either be washed with soap and water or vacuumed.
PAGE 1956
Communication Manager Maintenance-Object Repair Procedures SEC-CDR (Call Detail Recording Link) S8700 | 8710 / S8500 See PRI-CDR (Call Detail Recording Link) on page 1905. 1956 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1957
SER-BUS (Serial communication bus) SER-BUS (Serial communication bus) G650 MO name Alarm level Initial SAT command to run Full name of MO SER-BUS MIN test environment location sh SER communication bus SER-BUS MAJ test environment location l SER communication bus Each port network of G650s has a Serial Bus that allows the TN231O2BP IPSI to communicate with the 655A power supplies. This Serial Bus uses 2 previously unused leads in the Universal Port Slot.
PAGE 1958
Communication Manager Maintenance-Object Repair Procedures Figure 114: Wiring diagram for serial bus data and clock leads 1958 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 1959
SER-BUS (Serial communication bus) Figure 115: G650 Cabinet Environmental Hardware Components Use status environment to obtain: ● Inlet temperature - 655A power supply sensor ● Exhaust temperature - G650 carrier exhaust air sensor ● Hot Spot temperature - 655A power supply sensor - The system generates a warning at 176o Fahrenheit (80o Celsius). - The power supply shuts down at 194o Fahrenheit (90o Celsius).
PAGE 1960
Communication Manager Maintenance-Object Repair Procedures ● Source of input power - AC, DC, or both ● Input power - Indicates the type of power currently in use, AC or DC ● AuxSig signal status Note: If the TN 2312BP IPSI cannot get data from the power supplies, the data entries for status environment will be dashed out.
PAGE 1961
SER-BUS (Serial communication bus) Serial Bus problem appeared.) Also examine which power supplies the system is unable to show using list configuration power-supply C and concentrate your efforts on those carriers and their cabling. ! CAUTION: CAUTION: When straightening or replacing backplane pins in a carrier, power to that carrier must be shut off. Failure to follow this procedure may result in damage to circuit packs and power supplies, and can be hazardous to the technician.
PAGE 1962
Communication Manager Maintenance-Object Repair Procedures After cabling changes are made and verified, power must be restored to the port network. Circuit packs in carriers that are not part of the shortened bus are not inserted. As a result, these circuit packs are alarmed. Ignore these alarms for now. All alarms should be resolved when the cabinet is restored to its original configuration.
PAGE 1963
SER-BUS (Serial communication bus) Serial bus communications test (#1531) The TN2312BP IPSI requests status information from the power supplies every 5 seconds. If it does not receive a response, or if it does not detect at least one power supply at initialization, it generates a serial bus failure error message. Table 720: Test 1531 Serial bus status Error code Test result Description and recommendation 1000 ABRT This is an internal software error. 1.
PAGE 1964
Communication Manager Maintenance-Object Repair Procedures Table 720: Test 1531 Serial bus status (continued) Error code Test result Description and recommendation FAIL FAIL 1. Enter list configuration power-supply cab and check if any power supplies are detected. 2. Enter list configuration all and verify that the carrier locations for the power supplies appear correct. If not, verify that the paddle boards are inserted in the correct position for the carrier location. 3.
PAGE 1965
SER-BUS (Serial communication bus) Table 720: Test 1531 Serial bus status (continued) Error code Test result FAIL (cont’d) Description and recommendation 4. Run list configuration power-supply C to determine if some power supplies are still not showing and the Serial Bus fault is still present. 5. If the fault is still present: 1. Check if the backplane pins in the removed circuit pack’s slot appear to be bent. 2.
PAGE 1966
Communication Manager Maintenance-Object Repair Procedures Table 720: Test 1531 Serial bus status (continued) Error code Test result Description and recommendation FAIL (cont’d) Procedure 2: - This procedure attempts to isolate the Serial Bus failure to a particular set of carriers. Only the circuit packs in selected carriers are checked. Procedure 2 is organized into two parts. Part 1 attempts to clear the Serial Bus fault by replacing all the bus cabling and terminators within a port-network.
PAGE 1967
SER-BUS (Serial communication bus) Table 720: Test 1531 Serial bus status (continued) Error code Test result FAIL (cont’d) Description and recommendation 3. If list configuration power-supply C does show a power supply, extend the TDM/LAN/Serial Bus to another carrier, and repeat the procedure in the previous step. When a carrier that causes the fault to recur is added, perform Procedure 1 for only the circuit packs in that carrier. 4.
PAGE 1968
Communication Manager Maintenance-Object Repair Procedures SIP-BCH (SIP B Channel) S8700 | 8710 / S8500 / S8300 No maintenance diagnostic tests exist for this object. SIP signaling is similar to ISDN Q.931 signaling. In order to take advantage of existing ISDN Avaya™ Communication Manager, SIP trunk AvayaCommunication Manager software includes SIP signaling groups, SIP D channels and SIP B channels. SIP signaling groups are similar in concept to ISDN PRI signaling groups.
PAGE 1969
SIP-BCH (SIP B Channel) Notes: a. Error Type 18: Indicates that this specific SIP trunk group member has been craft busied-out System Technician Commands The following commands are available to the system technician: ● busyout port location - on a specific SIP B channel, drops any active call on that B channel and reduces the trunk group’s capacity by one. No physical piece of hardware is removed from service.
PAGE 1970
Communication Manager Maintenance-Object Repair Procedures SIP-SGRP (SIP Signaling Group) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO SIP-SGRP MIN test signaling-group grp# SIP Signaling Group SIP-SGRP WRN test signaling-group grp# SIP Signaling Group The SIP Signaling Group (SIP-SGRP) MO supports a signaling channel (D channel) for SIP trunk connections.
PAGE 1971
SIP-SGRP (SIP Signaling Group) Table 721: SIP-SGRP Signaling Group Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 1281 (h) Any MEDPRO Status test (#1392) MIN OFF 1537 (i) Any MEDPRO Status test (#1392 MIN OFF MEDPRO Status test (#1392) MIN OFF 1794 (j) 2561 (k) Any Registered to LSP Inline Error MIN OFF 3073 (l) 19 Far-end TLS Certificate Failure Inline Error MIN OFF 3329 (m) 21 Near-end TLS Certificate failure Inline Error MIN OFF
PAGE 1972
Communication Manager Maintenance-Object Repair Procedures g. Error Type 1025: the signaling group has been placed into a BYPASS condition because of IP network congestion. The signaling group accepts incoming calls, but every outgoing call is denied. The system routes these calls over a secondary route, if one has been administered. h. Error Type 1281: Implies that no medpro resources are in service to provide media connections for the trunk members of the signaling group.
PAGE 1973
SIP-SGRP (SIP Signaling Group) 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 CLAN Ethernet Status test (#1386), you may also clear errors generated from other tests in the testing sequence.
PAGE 1974
Communication Manager Maintenance-Object Repair Procedures Table 722: Test #1386 CLAN Ethernet Status Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received from the TN799DP C-LAN circuit pack within the allowable time period. 1. If this result occurs repeatedly, attempt to reset the circuit pack if the other ports on the board are idle (amber LED is off).
PAGE 1975
SIP-SGRP (SIP Signaling Group) If the PING is successful, this test looks at the PING round-trip delay. If a round-trip delay of greater than four (4) seconds is reported, a separate error is logged. Excessive round-trip delays within the signaling group will not take the signaling group out of service. Services can execute the standard PING command using the C-LAN board’s address and far-end IP address from the signaling group screen to see the actual round-trip delay.
PAGE 1976
Communication Manager Maintenance-Object Repair Procedures Table 723: Test #1387 SIP Signaling Group Ping Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received from the C-LAN circuit pack within the allowable time period. 1. If this result occurs repeatedly, attempt to reset the circuit pack if the other ports on the board are idle (amber LED is off).
PAGE 1977
SIP-SGRP (SIP Signaling Group) MedPro Status Test (#1392) This test is nondestructive. This test determines if at least one media processor port exists that is in service, and that serves the same region as the C-LAN that the signaling group uses. If at least one exists and is in service, the test passes; otherwise, the test fails.
PAGE 1978
Communication Manager Maintenance-Object Repair Procedures S-SYN-BD (Speech Synthesis Circuit Pack) S8700 | 8710 / S8500 MO name Alarm Level Initial SAT Command to Run Full Name of MO S-SYN-BD MIN test board location sh Speech Synthesis circuit pack S-SYN-BD WRN test board location sh Speech Synthesis circuit pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for errors at the circuit-pack level. See S-SYN-PT (Speech Synthesis Port) on page 1979 for related port information.
PAGE 1979
S-SYN-PT (Speech Synthesis Port) S-SYN-PT (Speech Synthesis Port) S8700 | 8710 / S8500 MO name Alarm Level Initial SAT Command to Run Full Name of MO S-SYN-PT MAJ test port location sh Speech Synthesis port S-SYN-PT MIN test port location l Speech Synthesis port S-SYN-PT WRN test port location sh Speech Synthesis port The TN725B Speech Synthesis circuit pack provides four independent Speech Synthesis ports which may be connected to any of the voice time slots on the Time Division Multiplex
PAGE 1980
Communication Manager Maintenance-Object Repair Procedures Table 725: Speech Synthesis Port Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 0 busyout port location WRN OFF release port location 130 (c) None WRN ON test port location sh 257 Speech Synthesis PSS Handshake test (#168) MAJ ON test port location sh r 2 513 17922 Speech Synthesis Memory test (#166) MIN ON test port location sh r 2 769 17664 Speech Syn
PAGE 1981
S-SYN-PT (Speech Synthesis Port) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing error codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 1982
Communication Manager Maintenance-Object Repair Procedures Table 727: TEST #6 NPE Crosstalk Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call and therefore unavailable for certain tests. Wait until the port is idle (amber LED is off) before retesting. 1.
PAGE 1983
S-SYN-PT (Speech Synthesis Port) Table 727: TEST #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. Any FAIL The NPE of the tested port was found to be transmitting in error. This will cause noisy and unreliable connections. 1. Replace the circuit pack. PASS The port is correctly using its allocated time slots.
PAGE 1984
Communication Manager Maintenance-Object Repair Procedures Table 728: TEST #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1020 ABRT The test did not run due to an already existing error on the specific port or a more general circuit pack error. 2. Examine Error Log for existing errors against this port or the circuit pack and attempt to diagnose the already existing error.
PAGE 1985
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. If any of the tones were not detected correctly, the test fails.
PAGE 1986
Communication Manager Maintenance-Object Repair Procedures 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.
PAGE 1987
S-SYN-PT (Speech Synthesis Port) Table 731: TEST #165 Speech Synthesis DSP Tone Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call and therefore unavailable for certain tests. Wait until the port is idle (amber LED is off) before retesting. 1.
PAGE 1988
Communication Manager Maintenance-Object Repair Procedures 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 1989
S-SYN-PT (Speech Synthesis Port) Table 732: TEST #166 Speech Synthesis Memory Test (continued) Error Code Test Result Description / Recommendation PASS The computed checksum values were successfully compared against the stored checksum values. User-reported troubles should be investigated using other tests and by verifying other ports on this circuit pack are working correctly.
PAGE 1990
Communication Manager Maintenance-Object Repair Procedures 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. ● An invalid command is received by the on-board microprocessor from the PSS controller.
PAGE 1991
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 735: TEST #169 Speech Synthesis Parameter Update Test Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 1992
Communication Manager Maintenance-Object Repair Procedures SN-CONF (Switch Node Configuration) S8700 MC only MO Name Alarm Level Initial SAT Command to Run Full Name of MO SN-CONF MAJ test board location Switch Node Configuration SN-CONF MIN test board location1 Switch Node Configuration 1. If the error and alarm logs display the switch node carrier location UUC (cabinet and carrier only), run the long test sequence on the active SNC in the carrier, (slot 10 or 12).
PAGE 1993
SN-CONF (Switch Node Configuration) Error Log Entries and Test to Clear Values Table 736: SN-CONF Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test board location sh r 1 5000 (b) Any Processor Route Audit (#760) MIN OFF test board location l rep 1 6000 (c) 1 Configuration Audit (#759) MAJ OFF test board location rep 1 6000 (c) 2 Configuration Audit (#759) MAJ OFF test board location rep 1 6001 (d) Any
PAGE 1994
Communication Manager Maintenance-Object Repair Procedures c. Error Type 6000: no neighbor link is administered, but the SNI has one. If the Aux Data is 1, an EI is connected as a neighbor link. If the Aux Data is 2, an SNI is connected as a neighbor link. To resolve Error Type 6000 with Aux Data 1, refer to FAIL code 133 for test 759. To resolve Error Type 6000 with Aux Data 2, refer to FAIL code 134 for the Configuration Audit test (#759). d.
PAGE 1995
SN-CONF (Switch Node Configuration) Aux Data (slot no.) Test 759 FAIL Code 15 115 16 116 17 117 18 118 19 119 20 120 2 of 2 h. Error Type 6005: a link does not exist to one of the SNCs. If the Aux Data is not 1 or 2, the link from this SNI to the active SNC does not exist. If the Aux Data is 1, the link from this SNC to the active SNC does not exist. If the Aux Data is 2, the link from this SNC to the standby SNC does not exist.
PAGE 1996
Communication Manager Maintenance-Object Repair Procedures Configuration Audit (#759) This test is nondestructive. Note: For descriptions of result codes for this test see: Note: ● SNC-BD (Switch Node Clock Circuit Pack) on page 2000 when the circuit pack tested is a Switch Node Clock (circuit pack slots 10 or 12). ● SNI-BD (SNI Circuit Pack) on page 2046 when the circuit pack tested is a Switch Node Interface (circuit pack slots 2–9 or 13–20).
PAGE 1997
SN-CONF (Switch Node Configuration) 2. If they are not lit, check that the fiber connections to the port network are consistent with the administered fibers (list fiber-link) that does not light the LEDs as expected. 3. Run test led switch-node on each administered switch node carrier and verify that the LEDs on the correct carrier are lit. 4. If they are not, check the connectivity to the switch node carrier that does not light the LEDs as expected.
PAGE 1998
Communication Manager Maintenance-Object Repair Procedures 4. If the PN’s LEDs are lit and there are multiple fibers to the distant switch node, remove the SNC that is listed by list fiber-link for this path. If not, enter list fiber-link to verify that the fiber connections to the PN are consistent with the administration assignments. 5. Use status sys-link to determine the new path from the IPSI connected PN to the distant switch. 6.
PAGE 1999
SN-CONF (Switch Node Configuration) Table 737: TEST #760 Processor Route Audit Test (continued) Error Code Test Result Description / Recommendation 2306 ABRT None of the circuit packs in this switch node carrier are responding to the processor route messages sent by software. 1. Run test led switch-node for the switch node where this switch node carrier resides to verify whether the LEDs on any of the boards light. 2.
PAGE 2000
Communication Manager Maintenance-Object Repair Procedures SNC-BD (Switch Node Clock Circuit Pack) S8700 MC MO Name Alarm Level Initial SAT Command to Run Full Name of MO SNC-BD MAJ test board location s SNC Circuit Pack SNC-BD MIN test board location s SNC Circuit Pack The Switch Node Clock (SNC) TN572 circuit pack is part of the Center Stage Switch (CSS) configuration. It resides in a switch node carrier that alone or with other switch nodes make up a CSS.
PAGE 2001
SNC-BD (Switch Node Clock Circuit Pack) Figure 116: A Center Stage Switch Configuration EPN EI switch node carrier EPN EI EPN EI EPN EI EPN EI EPN EI EPN EI PPN EI EPN EI EPN EI EPN EI OLS * S N I S N I S N I S N I S N I S N I S N I S N I S N C slot number 1 2 3 4 5 6 7 8 9 10 S N C S N I S N I EPN EI EPN EI S N I S N I EPN EI EPN EI EPN EI S N I S N I S N I fiber links S N * * OLS I 11 12 13 14 15 16 17 18 19 20 21 * = An EI or a DS1C circuit pack may res
PAGE 2002
Communication Manager Maintenance-Object Repair Procedures SNC LEDs SNC circuit packs have the standard red, green, and yellow LEDs. The red and green LEDs operate as usual: red means an alarm condition and green indicates maintenance testing in progress. If the yellow LED is lit, this indicates that the SNC is the active circuit pack, supplying timing to the carrier. In a duplex- or high-reliability system (unduplicated PNC), the standby SNC in a carrier is unlit.
PAGE 2003
SNC-BD (Switch Node Clock Circuit Pack) 4. Use test alarm long clear category exp-intf. Do not busyout the Expansion Interface circuit packs. 5. Wait 5 minutes for SNI-BD, SNI-PEER, FIBER-LK, and DS1C-BD alarms to clear, or enter clear firmware-counters. High-Reliability System (Duplicated Server and SNCs, Unduplicated PNC) This procedure is nondestructive. 1.
PAGE 2004
Communication Manager Maintenance-Object Repair Procedures 7. Wait 5 minutes for SNI-BD, SNI-PEER, FIBER-LK, and DS1C alarms to clear, or enter clear firmware-counters a-pnc | b-pnc. Use the letter designation of the PNC that holds the replaced component (the standby PNC). 8. Enter status pnc. If either PNC’s state of health is not “functional”, consult PNC-DUP (PNC Duplication) on page 1851. 9. Enter release pnc.
PAGE 2005
SNC-BD (Switch Node Clock Circuit Pack) c. Error Type 18: the SNC circuit pack was busied out using busyout board location. To resolve this error, use release board location to release the SNC circuit pack. d. Error Type 257: these errors occur when firmware detects failure of the phase-locked loop, inability to lock, or failure of the clock drivers and the problem is off-board. 1.
PAGE 2006
Communication Manager Maintenance-Object Repair Procedures f. Error Type 769: the standby SNC determined that there is a problem communicating with the active SNC through the connecting serial channel. 1. If the active SNC (yellow LED is on) has this error, escalate the problem. (The status switch-node command also shows the active and standby SNCs.) 2. Use display errors to check the error log.
PAGE 2007
SNC-BD (Switch Node Clock Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing error codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2008
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2009
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 102 FAIL The SNC circuit pack cannot communicate with the SNI in slot 2. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to see if an SNI is physically present in slot 2.
PAGE 2010
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 103 FAIL The SNC circuit pack cannot communicate with the SNI in slot 3. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2011
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 104 FAIL The SNC circuit pack cannot communicate with the SNI in slot 4. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 4.
PAGE 2012
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 105 FAIL The SNC circuit pack cannot communicate with the SNI in slot 5. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2013
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 106 FAIL The SNC circuit pack cannot communicate with the SNI in slot 6. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 6.
PAGE 2014
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 107 FAIL The SNC circuit pack cannot communicate with the SNI in slot 7. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2015
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 108 FAIL The SNC circuit pack cannot communicate with the SNI in slot 8. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 8.
PAGE 2016
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 109 FAIL The SNC circuit pack cannot communicate with the SNI in slot 9. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2017
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 112 FAIL The SNC circuit pack cannot communicate with the other SNC. If this test was run on the active SNC and if the switch node carrier is administered with duplicate SNCs: 1. If the system originally had duplicate SNCs and the standby SNC was removed and never replaced, this error will occur. If you do not intend to replace the SNC: a.
PAGE 2018
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 113 FAIL The SNC circuit pack cannot communicate with the SNI in slot 13. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2019
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 114 FAIL The SNC circuit pack cannot communicate with the SNI in slot 14. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 14.
PAGE 2020
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 115 FAIL The SNC circuit pack cannot communicate with the SNI in slot 15. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2021
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 116 FAIL The SNC circuit pack cannot communicate with the SNI in slot 16. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 16.
PAGE 2022
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 117 FAIL The SNC circuit pack cannot communicate with the SNI in slot 17. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2023
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 118 FAIL The SNC circuit pack cannot communicate with the SNI in slot 18. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 18.
PAGE 2024
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 119 FAIL The SNC circuit pack cannot communicate with the SNI in slot 19. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2.
PAGE 2025
SNC-BD (Switch Node Clock Circuit Pack) Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 120 FAIL The SNC circuit pack cannot communicate with the SNI in slot 20. 1. If a standby SNC (one with its yellow LED off) was tested and resulted in this error code, follow normal escalation procedures. Use status switch-node to show the active and standby SNCs. 2. Use list configuration carrier to determine whether an SNI is physically present in slot 20.
PAGE 2026
Communication Manager Maintenance-Object Repair Procedures Table 739: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that SNC board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNC should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNC.
PAGE 2027
SNC-BD (Switch Node Clock Circuit Pack) Table 740: TEST #760 Processor Route Audit Test (continued) Error Code Test Result Description / Recommendation 2301 ABRT The software timer could not be set before sending the downlink message necessary to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2306 ABRT None of the circuit packs in this switch node carrier are responding to the processor route messages sent by software. 1.
PAGE 2028
Communication Manager Maintenance-Object Repair Procedures Table 740: TEST #760 Processor Route Audit Test (continued) Error Code Test Result Description / Recommendation FAIL If this test fails, one or more administered circuit packs in this switch node carrier did not respond with a “board insertion” uplink message. Use list config carrier location to verify that the administered SNI and SNC boards match the physically installed SNI and SNC boards.
PAGE 2029
SNC-BD (Switch Node Clock Circuit Pack) Failure Audit (#777) This test is nondestructive. This test queries an SNC for any existing failures and any unacknowledged “cleared failure” messages. Each failure generates an error and alarm entry against SNC-BD, SNC-LINK, or SNC-REF. A “cleared failure” message is a message an SNI circuit pack sends to software indicating the resolution of a previous failure.
PAGE 2030
Communication Manager Maintenance-Object Repair Procedures Table 741: TEST #777 Failure Audit (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNC circuit pack is not responding to test requests sent by software. 1. Run test led switch-node for the switch node where this board resides to verify whether the LEDs on the board light. 2.
PAGE 2031
SNC-BD (Switch Node Clock Circuit Pack) Table 741: TEST #777 Failure Audit (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that SNC board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNC should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNC.
PAGE 2032
Communication Manager Maintenance-Object Repair Procedures Table 742: TEST #778 SNC On-Board Test (continued) Error Code Test Result Description / Recommendation 2303 ABRT The SNC circuit pack responded that the software test requested is not valid. 1. Retry the command at 1-minute intervals up to 3 times. 2304 ABRT SNC firmware is not able to run the test. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2033
SNC-BD (Switch Node Clock Circuit Pack) Table 742: TEST #778 SNC On-Board Test (continued) Error Code Test Result Description / Recommendation 101 FAIL The SNC circuit pack has on-board microcontroller failure. 1. Replace the SNC circuit pack. 128 FAIL The SNC circuit pack has a problem with its clock; firmware has detected a phase-locked loop failure, an inability to lock, or a failure of the clock drivers. 1. Replace the SNC circuit pack.
PAGE 2034
Communication Manager Maintenance-Object Repair Procedures TPN Test (#779) This test is nondestructive. This test queries the SNC circuit pack for status of the ROM and internal RAM background tests for the TPN microcontroller. Table 743: TEST #779 TPN Test Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2035
SNC-BD (Switch Node Clock Circuit Pack) Table 743: TEST #779 TPN Test (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNC circuit pack is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node where this board resides to verify whether the LEDs on the board light. 2.
PAGE 2036
Communication Manager Maintenance-Object Repair Procedures Switch Node Clock Reset Test (#780) This test is destructive. This test resets the SNC circuit pack using reset board location when an SNC circuit pack location is entered. If the system has PNC duplication, the active SNC on the active PNC cannot be reset. If the SNC is active and reset board is executed, an SNI in the same carrier as the SNC will be told by software to reset the SNC via the TPN link.
PAGE 2037
SNC-BD (Switch Node Clock Circuit Pack) Table 744: TEST #780 Switch Node Clock Reset Test (continued) Error Code Test Result Description / Recommendation 2304 ABRT SNC circuit pack responded that it is not able to run the test requested by software. 1. Retry the command at 1-minute intervals up to 3 times. 2306 ABRT The SNC circuit pack is not responding to test requests sent by software. 1.
PAGE 2038
Communication Manager Maintenance-Object Repair Procedures Table 744: TEST #780 Switch Node Clock Reset Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that SNC board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNC should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNC.
PAGE 2039
SNC-LINK (Switch Node Clock Link) SNC-LINK (Switch Node Clock Link) S8700 MC MO Name Alarm Level Initial SAT Command to Run Full Name of MO SNC-LINK MIN test board location s SNC Link The SNC-LINK MO reports errors in communications between the active Switch Node Clock and Switch Node Interfaces over the serial channel (Aux Data 1) and the TPN link (Aux Data 2). SNC-LINK errors are described on the following pages.
PAGE 2040
Communication Manager Maintenance-Object Repair Procedures Table 745: SNC-LINK Hardware Error Log Entries (continued) Error Type Aux Data SNI Slot1 Associated Test Alarm Level On/Off Board Test to Clear Value 1537 2 (c) 8 Failure audit (#777) MIN OFF test board location r 1 1793 1 (b) 9 Failure audit (#777) MIN OFF test board location r 1 1793 2 (c) 9 Failure audit (#777) MIN OFF test board location r 1 2049 1 (b) 13 Failure audit (#777) MIN OFF test board location r 1 20
PAGE 2041
SNC-LINK (Switch Node Clock Link) 1. Use display errors to check the error log. 2. If a SNI-PEER error exists in the hardware error log, follow the repair procedures for SNI-PEER errors. 3. If the SNC has SNC-LINK errors with Aux Data of 1 against other SNIs and/or has SNC-BD error 513, replace the SNC circuit pack. 4. If SNIs in the same carrier have SNI-BD error 257 logged indicating they are having trouble communicating with the SNC, replace the SNC circuit pack. 5.
PAGE 2042
Communication Manager Maintenance-Object Repair Procedures c. If the problem persists, replace the active SNC circuit pack. Otherwise: d. Insert an SNI circuit pack. 4. Replace the SNI circuit pack that the SNC is complaining about. 5. Retry the command. If this error is still in the error log, replace the SNC circuit pack. 6. If a standby SNC (the one with its yellow LED off) has this error, escalate the problem. Use status switch-node to show the active and standby SNCs. 7. Retry the command.
PAGE 2043
SNC-REF (Switch Node Clock Reference) SNC-REF (Switch Node Clock Reference) S8700 MC MO Name Alarm Level Initial SAT Command to Run Full Name of MO SNC-REF MAJ test board location s SNC Reference The SNC-REF MO reports errors in SNI reference signals detected by the active Switch Node Clock. Descriptions of SNC-REF errors appear on the following pages.
PAGE 2044
Communication Manager Maintenance-Object Repair Procedures Table 746: SNC Reference Error Log Entries (continued) Error Type Aux Data SNI Slot1 Associated Test Alarm Level On/Off Board Test to Clear Value 3585 (b) Any 19 Failure audit (#777) MAJ OFF test board location r 1 3841 (b) Any 20 Failure audit (#777) MAJ OFF test board location r 1 2 of 2 1. The slot location of the SNI with which the SNC cannot communicate. Notes: a. Error Type 0: run the short test sequence first.
PAGE 2045
SNC-REF (Switch Node Clock Reference) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing error codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2046
Communication Manager Maintenance-Object Repair Procedures SNI-BD (SNI Circuit Pack) S8700 MC MO Name Alarm Level Initial SAT Command to Run Full Name of MO SNI-BD MAJ test board location s SNI Circuit Pack SNI-BD MIN test board location s SNI Circuit Pack SNI-BD WRN test board location s SNI Circuit Pack The TN573 Switch Node Interface (SNI) circuit pack is part of the Center Stage Switch (CSS) configuration.
PAGE 2047
SNI-BD (SNI Circuit Pack) Figure 118: CSS Configuration with Unduplicated PNC and 1 Switch Node Carrier EPN EI EPN EI TN Numbers: SNI - TN573 SNC - TN572 EI - TN570 PPN EI switch node carrier * slot number 1 S N I EPN EI S N I S N I EPN EI EPN EI S N I S N I S N I EPN EI EPN EI S N I S N I EPN EI S N C not used S N C S N I S N I EPN EI EPN EI S N I EPN EI EPN EI EPN EI EPN EI S N I S N I S N I EPN EI S N I S N I . . . . . . . . .. . . . . .. . . . . .. . . . . .. . .
PAGE 2048
Communication Manager Maintenance-Object Repair Procedures Figure 119: CSS Configuration with Duplicated PNC and 4 Switch Node Carriers EPN EI PPN EI slot number 1 switch node carrier 1E 2 EPN EI EPN EI EPN EI 3 4 EPN EI 5 6 EPN EI 7 8 EPN EI EPN EI EPN EI EPN EI 9 10 11 12 13 14 15 16 17 18 19 20 21 S S S S S S S S S N N N N N N N N N I I I I I I I I C S S S S S S S S S N N N N N N N N N C I I I I I I I I PNC A inter-switch node fibers switch node carrier 2E S S S S S S S S S N N N
PAGE 2049
SNI-BD (SNI Circuit Pack) Remote PNs A DS1 converter complex can used to provide connectivity to a remotely located port network. The DS1 converter complex consists of two TN574 DS1 converter (DS1C) circuit packs connected by 1 to 4 DS1 facilities. The DS1C complex is administered as a fiber link.
PAGE 2050
Communication Manager Maintenance-Object Repair Procedures SNI Administration and SNI Board Insertion The circuit packs in the switch node carrier will not function properly unless administration is performed first. For example, without fiber link administration, phone calls cannot be made through the CSS, CSS circuit packs will not be inserted, and maintenance software cannot test the CSS circuit packs.
PAGE 2051
SNI-BD (SNI Circuit Pack) Clear Firmware-Counters Command SNI firmware generates error reports autonomously. This takes place independently of technician-demanded tests. Therefore, test board location clear does not affect the error status reported by firmware. The clear firmware-counters command clears every firmware-generated error unconditionally.
PAGE 2052
Communication Manager Maintenance-Object Repair Procedures Replacing an SNI Circuit Pack— Duplicated PNC ! WARNING: WARNING: On a system with duplicated PNC synchronization may be provided over a combination of active and standby components. This condition is indicated by an OFF-BOARD WRN alarm against TDM-CLK with Error Type 2305. Repairs to standby PNC in this state may disrupt service. If the active PNC is functional, replacement of a standby component does not disrupt service.
PAGE 2053
SNI-BD (SNI Circuit Pack) Switch Node Interface Manual Loop Back Procedure This procedure is destructive. Use this procedure when an SNI circuit pack cannot be tested by software. This can occur when communication between the switch node carrier and the server is down. Before using this procedure, use test board location s to run the configuration audit test (#759) on SNI circuit packs where possible.
PAGE 2054
Communication Manager Maintenance-Object Repair Procedures If this procedure is run on both endpoints on a fiber link (Expansion Interface circuit packs or Switch Node Interface circuit packs), and both check out fine, then the failure is most likely in the connection (fiber or metallic) itself if neither endpoint circuit pack is busied out, but the link remains inactive. 1. Use busyout board location to busyout the circuit pack (Expansion Interface or SNI). 2.
PAGE 2055
SNI-BD (SNI Circuit Pack) Figure 121: Interconnection of Lightwave Transceiver Transmit/Receive Jacks Back Skin of Cabinet Lightwave Transceiver Rx Tx Fiber Jumper Error Log Entries and Test to Clear Values Table 748: SNI Board Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test board location r 1 1 (b) Any Failure audit (#777) (c) MAJ MIN WRN ON test board location r 1 18 (d) 0 busyout board location WRN OFF
PAGE 2056
Communication Manager Maintenance-Object Repair Procedures Table 748: SNI Board Error Log Entries (continued) Error Type Aux Data 125 (e) Associated Test Alarm Level On/Off Board None MIN ON Test to Clear Value 257 (f) Any Failure audit (#777) (c) MAJ MIN WRN OFF test board location r 1 513 (g) Any Failure audit (#777) (c) MAJ MIN WRN OFF test board location r 1 769 (h) Any Failure audit (#777) (c) MAJ MIN WRN OFF test board location r 1 1025 (i) Any Failure audit (#777) (c)
PAGE 2057
SNI-BD (SNI Circuit Pack) d. Error Type 18: the SNI circuit pack was busied out using busyout board location. To resolve this error, use release board location to release the SNI circuit pack. e. Error Type 125: the SNI circuit pack is incompatible with the TN1654 DS1 Converter board. A TN573B or higher suffix SNI board must be used when connecting to a TN1654 DS1 Converter board. 1. Replace the SNI circuit pack with a newer suffix. f. Error Type 257: the SNI cannot communicate with the active SNC. 1.
PAGE 2058
Communication Manager Maintenance-Object Repair Procedures 1. Enter display alarms and display errors and follow the procedures for any on-board SNI-BD error and alarm entries. 2. If more than one SNI circuit pack in the same switch node carrier has SNI-BD error 769 with an off board alarm, replace the active SNC in the same carrier. 3. Replace this SNI. 4. Replace the active SNC in the same carrier. Procedure 2 Suspect clock generation out-of-lock problem: 5.
PAGE 2059
SNI-BD (SNI Circuit Pack) k. Error Type 1537: excessive slips have occurred. Follow the steps for diagnosing synchronization problems when slips have occurred in the SYNC section. l. Error Type 2561: the SNI cannot communicate with its neighbor. The SNI is at fault. 1. Replace the SNI circuit pack. m. Error Type 2817: the SNI cannot communicate with one of its peers. The SNI is at fault. 1. Replace the SNI circuit pack.
PAGE 2060
Communication Manager Maintenance-Object Repair Procedures SNI Circuit Path Test (#755) This test is nondestructive test of the circuit path. Table 749: TEST #755 SNI Circuit Path Test Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent. 1.
PAGE 2061
SNI-BD (SNI Circuit Pack) Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1. Run test led switch-node for the switch node where the SNI resides to verify whether the LEDs on the board light. 2.
PAGE 2062
Communication Manager Maintenance-Object Repair Procedures Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 102 FAIL The SNI circuit pack cannot communicate with the SNI in slot 2 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 2. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Follow the repair procedures for SNI-BD. 2.
PAGE 2063
SNI-BD (SNI Circuit Pack) Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 104 FAIL The SNI circuit pack cannot communicate with the SNI in slot 4 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 4. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Follow the repair procedures for SNI-BD. 2.
PAGE 2064
Communication Manager Maintenance-Object Repair Procedures Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 106 FAIL The SNI circuit pack cannot communicate with the SNI in slot 6 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 6. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Then follow the repair procedures for SNI-BD. 2.
PAGE 2065
SNI-BD (SNI Circuit Pack) Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 108 FAIL The SNI circuit pack cannot communicate with the SNI in slot 8 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 8. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Follow the repair procedures for SNI-BD. 2.
PAGE 2066
Communication Manager Maintenance-Object Repair Procedures Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 113 FAIL The SNI circuit pack cannot communicate with the SNI in slot 13 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 13. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Then follow the repair procedures for SNI-BD. 2.
PAGE 2067
SNI-BD (SNI Circuit Pack) Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 115 FAIL The SNI circuit pack cannot communicate with the SNI in slot 15 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 15. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Then follow the repair procedures for SNI-BD. 2.
PAGE 2068
Communication Manager Maintenance-Object Repair Procedures Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 117 FAIL The SNI circuit pack cannot communicate with the SNI in slot 17 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 17. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Then follow the repair procedures for SNI-BD. 2.
PAGE 2069
SNI-BD (SNI Circuit Pack) Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 119 FAIL The SNI circuit pack cannot communicate with the SNI in slot 19 over the circuit path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 19. Use display errors to find any SNI-BD errors and check display alarms to see if the errors have on-board alarms. Follow the repair procedures for SNI-BD. 2.
PAGE 2070
Communication Manager Maintenance-Object Repair Procedures Table 749: TEST #755 SNI Circuit Path Test (continued) Error Code Test Result Description / Recommendation 122 FAIL The SNI circuit pack cannot communicate with its neighbor via the circuit path. 1. Fix any on-board errors (SNI-BD, EXP-INTF, and/or DS1C-BD) against the components of this fiber link by using display errors and display alarms and following the repair procedures.
PAGE 2071
SNI-BD (SNI Circuit Pack) SNI Off-Board Destructive Facility Test (#756) This test is destructive. The SNI runs a destructive loop around of the on-board and off-board Looparound. This test returns the result of the off-board loop around, while Test #757 returns the result of the on-board loop around.
PAGE 2072
Communication Manager Maintenance-Object Repair Procedures Table 750: TEST #756 SNI Off-Board Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 2304 ABRT SNI circuit pack responded that it is not able to run the test requested by software. 1. Retry the command at 1-minute intervals up to 3 times. 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1.
PAGE 2073
SNI-BD (SNI Circuit Pack) Table 750: TEST #756 SNI Off-Board Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNI should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNI.
PAGE 2074
Communication Manager Maintenance-Object Repair Procedures Table 751: TEST #757 SNI Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 2301 ABRT The software timer could not be set before sending the downlink message necessary to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2304 ABRT SNI circuit pack responded that it is not able to run the test requested by software. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2075
SNI-BD (SNI Circuit Pack) Table 751: TEST #757 SNI Destructive Facility Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNI should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNI.
PAGE 2076
Communication Manager Maintenance-Object Repair Procedures Incorrectly Connected Administered Fibers Some physically connected fibers that do not match fiber administration can cause port network problems that are not detected and alarmed by PNC tests. The symptoms may be many phone calls not working correctly, and port network component alarms because of translation mismatches.
PAGE 2077
SNI-BD (SNI Circuit Pack) 2. Run test led to a port network as described above to verify this fiber connection. 3. Repeat this procedure for each of the other SNI-to-SNI fibers terminating on this distant switch node. Another method for testing multiple fiber connections to a distant switch node is described below. 1. Use list fiber-link to see the number of SNI-to-SNI fibers that are administered to and terminating on this switch node. 2.
PAGE 2078
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1. Run test led switch-node for the switch node where this board resides to verify whether the LEDs on the board light. 2.
PAGE 2079
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 102 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 2. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 1, replace the SNI being tested. Replacing an SNI may be service interrupting.
PAGE 2080
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 104 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 4. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 513, replace the SNI being tested.
PAGE 2081
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 106 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 6. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 1025, replace the SNI being tested. Replacing an SNI may be service interrupting.
PAGE 2082
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 108 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 8. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 1537, replace the SNI being tested.
PAGE 2083
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 112 FAIL The SNI circuit pack cannot communicate with the active SNC. 1. Check the error log for other SNI circuit packs in the same carrier with a 257 SNI-BD error. Use display errors with category PNC to view SNI-BD errors. If other SNI circuit packs in the same switch node carrier have error 257, then replace the active SNC in this switch node carrier.
PAGE 2084
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 114 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 14. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 2305, replace the SNI being tested.
PAGE 2085
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 116 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 16. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 2817, replace the SNI being tested. Replacing an SNI may be service interrupting.
PAGE 2086
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 118 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 18. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 3329, replace the SNI being tested.
PAGE 2087
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 120 FAIL The SNI circuit pack cannot communicate with the equipped SNI in slot 20. 1. Perform the Fiber link fault isolation procedure in Maintenance Procedures (03-300192). This will resolve multiple SNI-PEER errors. 2. If the SNI being tested has SNI-PEER Error Type 3841, replace the SNI being tested. Replacing an SNI may be service interrupting.
PAGE 2088
Communication Manager Maintenance-Object Repair Procedures Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 137 FAIL The SNI’s administered neighbor does not match the physical neighbor connected. The type of neighbor administered is an EI and the type of neighbor physically connected is an SNI. 1. Enter list fiber-link, and verify that the fiber-optic cable and metallic cable connections are installed as administered.
PAGE 2089
SNI-BD (SNI Circuit Pack) Table 752: TEST #759 Configuration Audit (continued) Error Code Test Result Description / Recommendation 140 FAIL The SNI is physically connected to a DS1C but is not administered to be connected to a DS1C. Either add the DS1 converter complex to the fiber that this SNI is associated with by: 1. Use list fiber-link to determine the fiber associated with the SNI. 2. Use remove fiber-link to remove the fiber. 3.
PAGE 2090
Communication Manager Maintenance-Object Repair Procedures Switch Node Interface Reset Test (#761) This test is destructive. This test resets the SNI circuit pack using reset board location when an SNI circuit pack’s location is entered. The SNI is reset via the active SNC circuit pack in the carrier. If the SNI is connected to an IPSI connected PN’s EI, the SNI is reset via its IPSI connected PN’s EI neighbor.
PAGE 2091
SNI-BD (SNI Circuit Pack) Table 753: TEST #761 Switch Node Interface Reset Test (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node where the SNI resides to verify whether the LEDs on the board light. 2.
PAGE 2092
Communication Manager Maintenance-Object Repair Procedures Table 753: TEST #761 Switch Node Interface Reset Test (continued) Error Code 0 Test Result Description / Recommendation PASS The “reset” message was sent out successfully to the active SNC or to the SNI’s neighbor. A PASS does not necessarily mean the SNI circuit pack was successfully reset. The reset can be verified by checking that the red and green LEDs turn on and then turn off.
PAGE 2093
SNI-BD (SNI Circuit Pack) Packet Neighbor Link Test (#767) This test is nondestructive. This test checks the packet path of the neighbor circuit pack and the peer circuit packs. A packet is sent from the SNI being tested to the peer SNIs and to the neighbor EI or SNI. If the other EI or SNI sends the same data back in the packet, this test passes. Otherwise, this test fails.
PAGE 2094
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node carrier where the SNI resides to verify whether the LEDs on the board light. 2.
PAGE 2095
SNI-BD (SNI Circuit Pack) Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 102 FAIL The SNI circuit pack cannot communicate with the SNI in slot 2 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 2. Use the display errors command to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2096
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 104 FAIL The SNI circuit pack cannot communicate with the SNI in slot 4 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 4. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2097
SNI-BD (SNI Circuit Pack) Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 106 FAIL The SNI circuit pack cannot communicate with the SNI in slot 6 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 6. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2098
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 108 FAIL The SNI circuit pack cannot communicate with the SNI in slot 8 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 8. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2099
SNI-BD (SNI Circuit Pack) Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 113 FAIL The SNI circuit pack cannot communicate with the SNI in slot 13 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 13. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2100
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 115 FAIL The SNI circuit pack cannot communicate with the SNI in slot 15 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 15. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2101
SNI-BD (SNI Circuit Pack) Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 117 FAIL The SNI circuit pack cannot communicate with the SNI in slot 17 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 17. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2102
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 119 FAIL The SNI circuit pack cannot communicate with the SNI in slot 19 over the packet path. 1. Fix any on-board SNI-BD errors against this SNI and the SNI in slot 19. Use display errors to find any SNI-BD errors and use the display alarms command to determine whether the errors have on-board alarms.
PAGE 2103
SNI-BD (SNI Circuit Pack) Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 123 FAIL The SNI circuit pack cannot communicate with its neighbor using the packet path. 1. Fix any on-board errors (SNI-BD, EXP-INTF, and/or DS1C-BD) against the components of this fiber link by using display errors and display alarms and following the repair procedures. Use list fiber-link to find the fiber link associated with this SNI.
PAGE 2104
Communication Manager Maintenance-Object Repair Procedures Table 754: TEST #767 Packet Neighbor Link Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD No board was detected by the test. 1. Check that board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNI should be reset instead of reseating the circuit pack. The reset board command should almost never be used on an SNI.
PAGE 2105
SNI-BD (SNI Circuit Pack) Table 755: TEST #777 Failure Audit (continued) Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times. 2300 ABRT The downlink message necessary to run this test could not be sent. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2106
Communication Manager Maintenance-Object Repair Procedures Table 755: TEST #777 Failure Audit (continued) Error Code Test Result Description / Recommendation FAIL The SNI circuit pack reported failures or retransmitted a “cleared failure” message. 1. If this is the first time this test was run, run the test again. If there were any previous failure messages that software did not acknowledge, this test will FAIL even if the failure messages indicate a FAIL to PASS transition (i.e.
PAGE 2107
SNI-BD (SNI Circuit Pack) SNI Fiber Out of Frame Query (#989) This test is nondestructive. The SNI circuit pack reports whether a fiber out of frame condition exists, whether a loss of signal condition exists, and whether the lightwave transceiver is present. Table 756: TEST #989 SNI Fiber Out of Frame Query Error Code Test Result Description / Recommendation 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 3 times.
PAGE 2108
Communication Manager Maintenance-Object Repair Procedures Table 756: TEST #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 2306 ABRT The SNI circuit pack is not responding to test requests sent by software. 1. Run the test led switch-node for the switch node where the SNI resides to verify whether the LEDs on the board light. 2.
PAGE 2109
SNI-BD (SNI Circuit Pack) Table 756: TEST #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 141 FAIL The SNI circuit pack has a fiber out of frame condition, but no loss of signal condition. Also, a lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed. The connected circuit pack is the other endpoint of the fiber-link if no DS1C complex is administered (check using list fiber-link).
PAGE 2110
Communication Manager Maintenance-Object Repair Procedures Table 756: TEST #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 143 FAIL The SNI circuit pack has a loss of signal condition, but no fiber out of frame condition. Also, a lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed.
PAGE 2111
SNI-BD (SNI Circuit Pack) Table 756: TEST #989 SNI Fiber Out of Frame Query (continued) Error Code Test Result Description / Recommendation 145 FAIL The SNI circuit pack has a fiber out of frame condition and a loss of signal condition. Also, a lightwave transceiver is connected to the SNI circuit pack. 1. Check that the connected circuit pack is physically installed. The connected circuit pack is the other endpoint of the fiber-link if no DS1C complex is administered (check using list fiber-link).
PAGE 2112
Communication Manager Maintenance-Object Repair Procedures Table 756: TEST #989 SNI Fiber Out of Frame Query (continued) Error Code 0 Test Result Description / Recommendation PASS No problems associated with this test are detected on the SNI. NO BOARD No board was detected by the test. 1. Check that board is properly translated and inserted. 2. Run the test again. If it fails, reset the board. An SNI should be reset instead of reseating the circuit pack.
PAGE 2113
SNI-PEER (SNI Peer Link) SNI-PEER (SNI Peer Link) S8700 MC only MO Name Alarm Level Initial SAT Command to Run Full Name of MO SNI-PEER MAJ test board location s SNI Peer Link SNI-PEER MIN test board location s SNI Peer Link SNI-PEER WRN test board location s SNI Peer Link SNI Peers are Switch Node Interfaces residing on the same Switch Node Carrier. SNI-PEER maintenance involves testing of the links between SNI Peers. SNI-PEER errors are described on the following pages.
PAGE 2114
Communication Manager Maintenance-Object Repair Procedures Table 757: SNI-PEER Hardware Error Log Entries (continued) Error Type Aux Data SNI Slot1 Associated Test Alarm Level On/Off Board Test to Clear Value 1281 Any 7 Failure audit (#777) MAJ MIN WRN OFF test board location r 1 1537 Any 8 Failure audit (#777) MAJ MIN WRN OFF test board location r 1 1793 Any 9 Failure audit (#777) MAJ MIN WRN OFF test board location r 1 2049 Any 13 Failure audit (#777) MAJ MIN WRN OFF tes
PAGE 2115
SNI-PEER (SNI Peer Link) Notes: For every error in Table 757: SNI-PEER Hardware Error Log Entries on page 2113, the SNI circuit pack reporting the error indicates that it has a problem with the control path, circuit path, or packet path to the SNI peer in the slot indicated on the error table. 1. Run the Failure Audit test (#777) to confirm if the error still exists. 2.
PAGE 2116
Communication Manager Maintenance-Object Repair Procedures Procedure 2 If either of the two patterns described before are present, then the clock signal between active SNC and 2 Adjacent SNIs is suspect. Proceed through the following steps until the problem is resolved: 1. If only one SNC exists in this switch node carrier, replace the SNC. If two SNCs exist in this switch node carrier, perform the following steps: a.
PAGE 2117
SRP-EPN SRP-EPN S8700 MC only MO Name Alarm Level Full Name of MO SRP-EPN MAJ SRP-EPN The Survivable Remote Expansion Port Network (SREPN) provides PN service to the customer when the link to the main processor fails or is broken, or when the processor or center stage fails. SREPN is a disaster recovery operation rather than an additional reliability option.
PAGE 2118
Communication Manager Maintenance-Object Repair Procedures STA-FWDL MO Name Alarm Level Initial Craft Command To Run Full Name of MO STA-FWDL WRN test firmware station-download Firmware Station Download The Firmware Station Download feature provides the ability to download new firmware to one or more DCP stations of the same type residing in the same system. The download image is copied from a tftp file server into Communication Manager memory through the change tftp command.
PAGE 2119
STA-FWDL Downloading firmware to DCP stations You can download updated firmware to a range of up to 1000 Avaya 2420 DCP stations. This eliminates the need to use a FAC (feature access code) to perform the firmware update for each station. To download firmware to these stations, Communication Manager requires: ● A valid firmware image loaded into Communication Manager memory through the change tftp command. ● Communication Manager 2.0 or greater software. ● Craft login.
PAGE 2120
Communication Manager Maintenance-Object Repair Procedures Read the image into memory Before you can download firmware to the target stations, you must first read the image file into Communication Manager memory: 1. At the System Access Terminal (SAT) using the craft login and password, type change tftp-server and press Enter. The TFTP Server Configuration form displays.
PAGE 2121
STA-FWDL Schedule the download You can download the new firmware image immediately or schedule the download for a later time. Due to the potentially large volume of switch activity as a result of the firmware download, Avaya recommends that you schedule the download for a time when the system will be at its lowest possible occupancy level. This will also limit the number of stations that are aborted because they were in use at the scheduled download time. To schedule a station firmware download: 1.
PAGE 2122
Communication Manager Maintenance-Object Repair Procedures Troubleshooting firmware download problems You cannot start a station download while there are active STA-FWDL alarms. To clear all active STA-FWDL alarms, use test firmware station-download. In the event of a STA-FWDL alarm, you can find more details by using the status firmware station-download command. status firmware station-download STATUS FIRMWARE STATION DOWNLOAD Image File: 2420v01.
PAGE 2123
STA-FWDL Table 758: STA-FWDL Hardware Error Log entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 257 13 None WAR OFF test firmware station-download 257 14 None WAR OFF test firmware station-download 257 15 None WAR OFF test firmware station-download 258 (b) 5 None WAR OFF test firmware station-download 513 (c) 4 None MIN OFF test firmware station-download 513 8 None MIN OFF test firmware station-download 513 11
PAGE 2124
Communication Manager Maintenance-Object Repair Procedures Table 759: Error Type 257 Aux Data descriptions (continued) Aux Data Description 14 Station firmware download to a terminal had too many retries, timeout occurred. 2 of 2 b. Error Type 258 with Aux Data 5: one or more terminals in the download list were skipped and not downloaded because the terminal was not in the appropriate state (in-service and idle). Resolve the alarm with the test firmware station-download.
PAGE 2125
STA-FWDL Table 760: Error Type 513 Aux Data descriptions (continued) Aux Data Description 13 Two consecutive terminals failed to download due to internal timeouts. It is likely that all terminals will fail as well so the schedule is stopped and any remaining terminals in the download list are aborted. 14 Could not build a list of terminals from the range specified in the change firmware station-download form. Check the administered stations for exact extension numbers.
PAGE 2126
Communication Manager Maintenance-Object Repair Procedures Table 761: Schedule States of status firmware station-download command (continued) State Schedule Done? Description Failed Yes At least two terminals rejected the firmware as invalid. As a result, the download was aborted to avoid problems with any further terminals.
PAGE 2127
STA-FWDL Table 762: Reason Codes for status firmware station-download command (continued) Reason Code Status Description 3 ABRT The terminal was not downloaded before the scheduled stop time occurred. Schedule a new download with adequate time for the downloads to complete, or select the continue daily option to allow the schedule to resume the following day. 4 ABRT The terminal could not be downloaded because the schedule aborted for an unknown reason.
PAGE 2128
Communication Manager Maintenance-Object Repair Procedures STRAT-3 (Stratum-3 Clock) S8700 MC only MO Name Alarm Level Initial SAT Command to Run Full Name of MO STRAT-3 MAJ test synchronization Stratum-3 clock STRAT-3 MIN test synchronization Stratum-3 Clock The Digital Synchronization Network Plan (PUB 60110) specifies a hierarchy of synchronization nodes consisting of Strata 1 to 4, where the public network’s sole Stratum-1 clock is the most accurate.
PAGE 2129
STRAT-3 (Stratum-3 Clock) Figure 122: Stratum-3 Clock Hardware Configuration DS1 TN464 TN767 or TN722 DS1 PPN ToneClock ToneClock TN780 TN780 Timing output TN464 TN767 or TN722 Timing output Alarms TOC TOC PAI A DS1 Ref A B ST3 ST3 A B CI CI A B -48V -48V DS1 Ref B Issue 1 June 2005 2129
PAGE 2130
Communication Manager Maintenance-Object Repair Procedures Stratum-3 Clock LED Strategy Note: When looking in the Stratum-3 cabinet, “A” card is on the left and “B” card is on the right. Note: Note: The normal LED scheme is not followed for this device. Green LEDs do not indicate maintenance activity. There are no yellow LEDs, and there are more than three LEDs per circuit pack. Note: Note: Removal of a card in the Stratum-3 clock may cause alarm(s) to be resolved and the query test to pass.
PAGE 2131
STRAT-3 (Stratum-3 Clock) The output of the CI and PAI cards go directly to the TN780 Tone-Clock circuit pack via two 25-pair amphenol terminated cables. Every card has red and/or green LEDs for providing status or alarm indications. The abbreviations used in the table are defined above except for SRC (source) and PLL (Phase Locked Loop).
PAGE 2132
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 764: Stratum-3 Clock Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test synchronization r 4 1 (b) Any Stratum-3 Clock Alarm Query (#649 MIN OFF test synchronization r 4 18 (c) 0 disable sync WRN OFF enable sync 257 (d) Any Stratum-3 Clock Alarm Query (#649) MIN OFF test synchronization r 4 513 (e)
PAGE 2133
STRAT-3 (Stratum-3 Clock) f. Error Type 769: this Error Type corresponds to FAIL code 8 of the Stratum-3 Clock Alarm Query test (#649): either reference B failed or the CI card B failed. g. Error Type 1025: this Error Type corresponds to FAIL code 16 of the Stratum-3 Clock Alarm Query test (#649): every power supplied failed.
PAGE 2134
Communication Manager Maintenance-Object Repair Procedures If the alarm is MAJOR: ● Check connections between the Stratum-3 clock and the switch. ● If there are no loose connections, use the Stratum-3 Wiring Guide and check that the wiring installation is correct. ● After reconnecting the loose connection or correctly rewiring it, clear the alarm by issuing disable synchronization-switch, followed by enable synchronization-switch. ● Wait 1 minute, then run status synchronization.
PAGE 2135
STRAT-3 (Stratum-3 Clock) j. Error Type 1793: this error can be caused by one of the following conditions: ● One or both TOCs (Timing Output Cards) has failed. ● The connection between the Stratum-3 clock and the TN780 Tone-Clock circuit pack is faulty. ● The TN780 Tone-Clock circuit pack is defective. System Technician-Demanded Tests: Descriptions and Error Codes The test synchronization command also runs the Test Synchronization test (#417).
PAGE 2136
Communication Manager Maintenance-Object Repair Procedures Table 766: TEST #161 Loop-Around Test Error Code Test Result Description / Recommendation 1001 ABRT The system could not allocate the necessary resources to run this test. 1. Retry the command at 1-minute intervals up to up to 3 times. 1005 ABRT This test aborts when it is run on a Stratum-4 system. Do not change synchronization to Stratum 3 without consulting the synchronization plan administrator for this switch.
PAGE 2137
STRAT-3 (Stratum-3 Clock) Table 766: TEST #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1 FAIL Either Reference A failed or CI card A failed. This condition usually indicates a failure of the DS1 reference; however, there may also be a failure of the CI card to which the reference is connected. The system technician dispatched to investigate this problem should take a spare CI card in case the CI card caused the failure.
PAGE 2138
Communication Manager Maintenance-Object Repair Procedures Table 766: TEST #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2 FAIL One power supply failed. This error occurs when the Stratum-3 clock has two power supplies, and one of them has failed. However, the clock can function with one power supply. 1. Locate the failed power supply (the one with a red LED), and replace it. The power supplies reside under the Stratum-3 clock’s carrier. 2.
PAGE 2139
STRAT-3 (Stratum-3 Clock) Table 766: TEST #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 8 FAIL Reference B failed or CI card B failed. This condition usually indicates a failure of the DS1 reference; however, there may also be a failure of the CI card to which the reference is connected. The system technician dispatched to investigate this problem should take a spare CI card in case the CI card caused the failure.
PAGE 2140
Communication Manager Maintenance-Object Repair Procedures Table 766: TEST #161 Loop-Around Test (continued) Error Code Test Result Description / Recommendation 16 FAIL Every power supply failed. 1. Replace the failed power supplies. 2.
PAGE 2141
SVC-SLOT (Service Slot) SVC-SLOT (Service Slot) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command to Run Full Name of MO SVC-SLOT MIN none Service Slot The Service Slot MO detects the insertion of an invalid circuit pack into a dedicated SERVICE slot. The SERVICE slot is the left-most slot in the J58890BB port carrier, and is identified as slot location “00” in commands and screen fields.
PAGE 2142
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 767: Service Slot Error Log Entries Error Type 600 (a) Aux Data Associated Test Alarm Level On/Off Board None MIN ON Test to Clear Value Note: a. Indicates that an invalid circuit pack was inserted in slot 00, the SERVICE slot, of a J58890BB port carrier. See the previous list of valid circuit packs. 1.
PAGE 2143
SYNC (Port-Network Synchronization) SYNC (Port-Network Synchronization) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO SYNC MIN display errors Port Network Synchronization SYNC WRN test synchronization Port Network Synchronization This section discusses synchronization problems local to the switch. For further information about synchronization including network synchronization, refer to AT&T Network and Data Connectivity, 555-025-201.
PAGE 2144
Communication Manager Maintenance-Object Repair Procedures For DS1- or BRI-based synchronization, a particular DS1 or PRI interface is configured as the synchronization reference. The IPSI/Tone-Clock board in the same PN locks on to this reference and regenerates clock signals that are placed on the PN’s backplane. In turn, the Center Stage Switch (CSS) components transfer this timing to every other PN.
PAGE 2145
SYNC (Port-Network Synchronization) S8700 IP IP-Connected S8700 Media Server Sync Operation 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. Inter-PN bearer traffic is carried as VOIP, while the Media Processors’ internal jitter buffers deal with differences in transmission rates.
PAGE 2146
Communication Manager Maintenance-Object Repair Procedures Clock Synchronization Note: S8700 MC: Stratum-3 clocking is not available for a PN where the Tone-Clock function is supplied by either a: Note: ● TN2312 IPSI circuit pack’s Tone-Clock circuit ● TN2182 Tone-Clock circuit pack This section discusses synchronization with Stratum-3 and -4 clocking devices.
PAGE 2147
SYNC (Port-Network Synchronization) ● When both the primary and secondary source become valid, the system switches to the primary source, since the primary source is always preferred over the secondary source when both sources are equally healthy. Synchronization Troubleshooting For Stratum-4 operation, major and minor alarms indicate that there is a problem with the system synchronization references. These alarms will be resolved when the alarmed synchronization reference is restored.
PAGE 2148
Communication Manager Maintenance-Object Repair Procedures DS1 and UDS1 circuit packs can be administered with slip detection enabled using the Slip Detection field set to y on the add ds1 or change ds1 administration screens (See the Administrators Guide for Avaya Communication Manager - 555-233-506).
PAGE 2149
SYNC (Port-Network Synchronization) Table 769 lists circuit packs that can report slips and related circuit packs whose hardware problems that cause those slips.
PAGE 2150
Communication Manager Maintenance-Object Repair Procedures Figure 125: Synchronization Troubleshooting, Fig. 1 of 5 Start Here Use display errors and follow the repair procedures for non-slip errors against, SYNC, TDM-CLK, TONE-BD, EXP-INTF, SNI-BD, and DS1C-BD maintenance objects.
PAGE 2151
SYNC (Port-Network Synchronization) Figure 126: Synchronization Troubleshooting, Fig. 2 of 5 From Fig 1 There is an administration discrepancy. This system is administered as the timing master but it should not be because there are DS1 spans with more accurate clocks. A No Slips on any DS1 facilities? Does the administration of this system agree with the Network synchronization plan? Make sure that there is only one master clock source. Examine the synchronization plan for the network.
PAGE 2152
Communication Manager Maintenance-Object Repair Procedures Figure 127: Synchronization Troubleshooting, Fig. 3 of 5 B From Fig 1 Slips on Reference Facilities? From Fig 1 Is there a loss-of-signal or network alarm on the DS1 references? Yes From Fig 2 See the DS1-BD and UDS1-BD MOs to resolve any outstanding alarms. Investigate external causes for the loss of the primary and/or secondary reference. Change interface boards as a last resort.
PAGE 2153
SYNC (Port-Network Synchronization) Figure 128: Synchronization Troubleshooting, Fig. 4 of 5 From Figure 1, 2, or 3 D For an S8xxx media server Multi-connect CSS, the problem is in the IPSI or Tone Clock, EI, or SNI of the PN containing Many DS1 spans with slips in the PN containing the master reference? Yes the master reference. If equipped, switch PNC and/or system tone clocks to try and change the symptoms. Then change . circuit packs above, one at a time.
PAGE 2154
Communication Manager Maintenance-Object Repair Procedures Figure 129: Synchronization Troubleshooting, Fig 5 of 5 The synchronization issue covers a large portion of the system. The problem is in a center stage switch (CSS), IPSI or Tone-Clock, EI, SNI, or DS1 spans in port networks (PN) other than the timing master PN. This procedure attempts to isolate the problem. When instructed to do so, perform the steps indicated while slips remain.
PAGE 2155
SYNC (Port-Network Synchronization) Figure 130: Synchronization Troubleshooting, Fig. 1 of 4 Slips Is synchronization enabled? Enable synchronization. No 1 Yes Is reference a free-running IPSI Tone-Clock circuit? Yes A Synchronization is enabled for this port network. Fig 2 1 No Slips on DS1 facilities? 2 Yes C Problems with reference PN or synchronization plan Fig 4 No Problem is in switch.
PAGE 2156
Communication Manager Maintenance-Object Repair Procedures Figure 131: Synchronization Troubleshooting, Fig. 2 of 4 From Fig 1 Retranslate to have DS1 operate according to the network’s plan. A No Slips on DS1 facilities? Yes 2 Examine cabinet’s role in network’s synchronization plan. Is this DS1 supposed to be PN’s timing reference? Yes No Refer problem for investigation at other end of facility. Slips on IPSI’s Tone-Clock circuit? Yes Problem is in PN, IPSI’s Tone-Clock or DS1s.
PAGE 2157
SYNC (Port-Network Synchronization) Figure 132: Synchronization Troubleshooting, Fig. 3 of 4 B Slips on DS1 reference facilities? Is there a loss-of-signal or network alarm? Yes 4 Yes Fix DS1-BD and UDS1-BD alarms. 5 No 5 No Replace circuit packs: – IPSI/Tone-Clock in the PN – DS1 in PN 6 Are there many facilities with excessive slips? Many Problem is in PN, IPSI’s Tone-Clock or DS1s. Escalate, if the problem is not fixed.
PAGE 2158
Communication Manager Maintenance-Object Repair Procedures Figure 133: Synchronization Troubleshooting, Fig. 4 of 4 C From Fig 1 Is reference on line? Yes 8 No Is the reference administered and SYNC enabled? Yes B To Fig 3 B To Fig 3 No Administer the reference, and enable synchronization. Slips on IPSI’s Tone-Clock circuit? Yes Problem is in PN, IPSI’s Tone-Clock or DS1s. Escalate No Done 2158 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2159
SYNC (Port-Network Synchronization) Notes for Sheet 1 through Sheet 5 flowcharts. (When checking for slip errors, use the previous Table 768: Error Log Entries for Slip Errors on page 2148. 1. Use status synchronization to see if synchronization is enabled, and to determine the on-line reference. If the on-line reference is a Tone-Clock board, the switch is operating in free run mode.
PAGE 2160
Communication Manager Maintenance-Object Repair Procedures problems next. See the DS1-BD and/or UDS1-BD for the error log entries associated with the previously mentioned alarms. Replace the circuit packs one at a time and wait at least 1 hour to determine if the problem went away. This procedure is disruptive and should be done after hours if possible. If problems persist it may be useful to compare translations for line coding and frame formats with the far end service provider.
PAGE 2161
SYNC (Port-Network Synchronization) the EI or the SNI on the previously active PNC. Replace one at a time and make the PNC active again to see if the problem is fixed. Instead of replacing the Tone-Clock circuit pack in systems where the Tone-Clocks are duplicated, run set tone-clock to interchange Tone-Clocks. If the problem goes away, replace the previously active Tone-Clock. Also, before replacing a Switch Node Clock circuit pack, use set switch-node-clock if SNCs are duplicated in the carrier.
PAGE 2162
Communication Manager Maintenance-Object Repair Procedures Figure 134: Manual Loop-Around for Facility Fault Sectionalization on page 2162 shows a sequence of units (1 though n) that may be connected as the on-site equipment. A typical example is the case where the only on-site equipment is channel-terminating equipment designated Unit #1. A more complex, less typical example might have a DACS as Unit #1, a protection switch as Unit #2, and a DS1-level microwave radio system as Unit #3.
PAGE 2163
SYNC (Port-Network Synchronization) Figure 135: Facility Fault Sectionalization START (DS1 Interface refers to the TN722, TN767 or TN464 circuit pack.) Since this technique is time-consuming, first fix 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. Loop transmit to receive on the G3r side of the equipment connected to the DS1 Interface. (See Note 1).
PAGE 2164
Communication Manager Maintenance-Object Repair Procedures 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. The loop-around signal may take different forms depending on the installation.
PAGE 2165
SYNC (Port-Network Synchronization) Synchronization Switches away from Current Timing Reference Synchronization changes away from a DS1 reference (primary or secondary) if the current DS1 reference does not provide a valid timing signal. The other DS1 reference is used if one is administered and providing a valid timing signal. Otherwise, the local oscillator of the Tone-Clock circuit pack in the same port network as the DS1 reference is used.
PAGE 2166
Communication Manager Maintenance-Object Repair Procedures The amber and green LED patterns for TN768, TN780, and TN2182 Tone-Clock circuit packs are listed in Table 770: Table 770: Tone-Clock Amber/Green LED Flashing Codes Circuit Pack Condition Tone-Clock State Explanation Flashing amber1 2.7 seconds on 0.3 seconds off Active An external timing source is being used as a synchronization reference. Flashing amber 0.3 seconds on 2.
PAGE 2167
SYNC (Port-Network Synchronization) Table 771: Synchronization Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value None WRN MIN (g) OFF None disable sync WRN OFF enable sync 257 (d)(i) None WRN MIN (i)(g) OFF None 513 (e)(i) None WRN MAJ (i)(g) OFF None 769 (f) None MAJ OFF None 1 (b)(i) 0 18 (c) 1793 (g)1 0–50 None MAJ OFF None 2049 (h) 0 None WRN OFF None 2 of 2 1.
PAGE 2168
Communication Manager Maintenance-Object Repair Procedures 4. Enter test tone-clock location long to test the active Tone-Clock circuit pack in the master port network. Check the Error Log for TDM-CLK errors, and verify that TDM Bus Clock Circuit Status Inquiry test (#148), passes. If Test #148 fails with Error Code 2–32, see TDM-CLK (TDM Bus Clock) on page 2252 to resolve the problem. If not, continue with the following. 5. Use disable synchronization-switch and enable synchronization-switch.
PAGE 2169
SYNC (Port-Network Synchronization) 2. Test the active Tone-Clock circuit pack in the master port network using test tone-clock location long. Check the Error Log for TDM-CLK errors, and verify that TDM bus Clock Circuit Status Inquiry test (#148) passes. If Test #148 fails with Error Code 2–32, see TDM-CLK (TDM Bus Clock) on page 2252 to resolve the problem. If not, continue with the following. 3.
PAGE 2170
Communication Manager Maintenance-Object Repair Procedures ● Replace the active Expansion Interface circuit pack in the master port network. ● In a CSS configuration, replace the Switch Node Interface circuit pack connected to the active Expansion Interface circuit pack in the master port network. Use list fiber-link to determine the Switch Node Interface circuit pack that is connected to the active Expansion Interface circuit pack in the master port network.
PAGE 2171
SYNC (Port-Network Synchronization) ● In a CSS configuration, replace the Switch Node Interface circuit pack connected to the active Expansion Interface circuit pack in the master port network. Use list fiber-link to determine the Switch Node Interface circuit pack that is connected to the active Expansion Interface circuit pack in the master port network. ● If the problem persists and any slip errors remain, follow the procedures described in the troubleshooting section above.
PAGE 2172
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 1: problem with the primary DS1 reference. It is cleared when the primary reference is restored. The following steps should give an indication of the source of the problem: 1. Check if the primary DS1 interface circuit pack is inserted in the carrier using list configuration board location. 2. Check the connection of the cable supplying the external timing source to the primary DS1 interface circuit pack. 3.
PAGE 2173
SYNC (Port-Network Synchronization) Bus Clock Test #148 passes successfully. If Test #148 fails with an Error Code 2 through 32, refer to the TDM-CLK (TDM Bus Clock) Maintenance documentation to resolve the problem. If not, continue with the following steps. 3. Replace the primary and secondary (if administered) DS1 Interface circuit packs. 4. Check for an error logged against the primary or secondary DS1 board. If there is an error, follow the DS1 section to resolve the errors.
PAGE 2174
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes S8700 MC: If Stratum 3 is administered using change synchronization, the Stratum-3 Clock Alarm Query test (#649) also executes when test synchronization is run. Test #649 is described in Stratum-3 Synchronization on page 2146.
PAGE 2175
SYS-LINK (System Links) SYS-LINK (System Links) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO SYS-LINK MIN test sys-link location SYSTEM LINKS SYS-LINK WRN test sys-link location SYSTEM LINKS System links are packet links that originate at the Packet Interface board and traverse various hardware components to specific endpoints.
PAGE 2176
Communication Manager Maintenance-Object Repair Procedures Identifying a System Link In order to trace problems associated with a system link, it is necessary to find its location. Use the following methods to find the location of the system link. Display Errors/Alarms The output of display errors or display alarms shows the location of the system link for entries with a Maintenance Name of SYS-LINK.
PAGE 2177
SYS-LINK (System Links) Note: Note: For systems using ATM-EI (TN2305/6 circuit packs) and where link alarms are present, see ATM-EI (Expansion Interface Circuit Pack) on page 525 and Troubleshooting ATM in Maintenance Procedures (03-300192). 3. When every component is alarm free, wait for 3 minutes to allow the links to recover. 4. Test the system link (test sys-link location long clear), and notice any tests that fail. 5.
PAGE 2178
Communication Manager Maintenance-Object Repair Procedures b. Error Type 257: the link has experienced uplink flow control, and the endpoint may be hyperactive. The system link is alarmed if 4 or more errors of this type are detected within 10 minutes. 1. Follow the information in Common Procedure for Repairing Link Problems on page 2176. 2. Clear errors and wait for 10 minutes. c.
PAGE 2179
SYS-LINK (System Links) h. Error Type 1793: This error indicates that the link has experienced slow transmit rate due to unknown causes, meaning that the endpoint location may experience slower throughput rate and the Packet Interface may experience backup or congestion. The system link is alarmed if 4 or more errors of this type are detected within 10 minutes. 1. Follow the information in Common Procedure for Repairing Link Problems on page 2176. 2. Clear errors and wait for 10 minutes. i.
PAGE 2180
Communication Manager Maintenance-Object Repair Procedures System Link Status (#985) This test is nondestructive. This test queries the switch for the status of the system link and verifies that every switch component has the same view of the link state. Table 775: TEST #985 System Link Status Error Code Test Result Description / Recommendation 1007 ABRT Could not locate the system link associated with this location 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2181
SYS-PRNT (System Printer) SYS-PRNT (System Printer) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO SYS-PRNT MIN test sp-link l System Printer SYS-PRNT WRN release sp-link System Printer The Report Scheduler feature provides the capability to schedule printing of output screen selected administration commands on an asynchronous System Printer (SYS-PRNT) or a Personal Computer (PC).
PAGE 2182
Communication Manager Maintenance-Object Repair Procedures 3. Verify the availability of the external SYS-PRNT output device. Make sure that the output device is on-line and ready-for-service. Check the physical connectivity between the Data Module and the SYS-PRNT output device. 4. Verify that there is at least one C-LAN port available. The System Printer Link cannot be established without an available C-LAN port. For more information about C-LAN ports, see CLAN-BD (Control LAN Circuit Pack) on page 789.
PAGE 2183
SYS-PRNT (System Printer) Table 777: Aux Data, Error Type 257 Aux Data Description 1 No C-LAN port available. See CLAN-BD (Control LAN Circuit Pack) on page 789 for explanation. 3, 4 Time-out during setup attempt. Most likely due to problem with physical link or printer status. 5 Internal system error. Most likely temporary/sporadic failure. 2, 6 The data module the printer is trying to use is busy with another call. Use status data module to determine when the port is available for testing.
PAGE 2184
Communication Manager Maintenance-Object Repair Procedures Link Tear Down Test (#213) This test is destructive. The Link Tear Down test disconnects the existing link between the media server and the external SYS-PRNT output device. If the link has already been disconnected, this test returns PASS. Every resource allocated for a System Printer Link is released after this test. Table 778: TEST #213 Link Tear Down Test Error Code Test Result Description / Recommendation 40 50 ABRT Internal system error.
PAGE 2185
SYS-PRNT (System Printer) 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 779: TEST #215 Link Retry Test Error Code Test Result Description / Recommendation 10 20 ABRT Internal system error. 30 ABRT 1. Retry the command at 1-minute intervals up to two times.
PAGE 2186
Communication Manager Maintenance-Object Repair Procedures SYSTEM (System) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command to Run1 Full Name of MO SYSTEM None None System 1. SYSTEM has no associated alarms and thus appears only in the Error Log. There are no tests that run on SYSTEM. The SYSTEM maintenance object is used to log information about system resets, including interchanges.
PAGE 2187
SYSTEM (System) Table 780: System Error Log Entries (continued) Error Type Aux Data Associated Test 6101 (i) Any None 6102 (j)(l) (l) None 6103 (k)(l) (l) None Alarm Level On/Off Board Test to Clear Value 2 of 2 Notes: a. Error Type 9: software requested a System Restart Level 2. b. Error Type 10: software requested a System Restart Level 1. c. Error Type 601: an error occurred during initialization. d. Error Type 605: a reset system interchange or a scheduled server interchange failed.
PAGE 2188
Communication Manager Maintenance-Object Repair Procedures k. Error 6103: an application alarm occurred on the standby server. See note (l) to diagnose the error using the Aux Data. l. 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 2189
SYSTEM (System) Table 781: SYSTEM Error 605 Aux Data, Failure of Planned Interchange (continued) 1361 (d) 4 SW-CTL failure 1369 (g) 7 Could not suspend G3-MT connectivity * 1370 (d) 4 Could not freeze active SW-CTL * 1371 (e) 5 Internal Error associated with processor interrupts * 1372 (f) 6 Minor alarm on standby SYSAM or PKT-INT 1395 Server Duplication not administered 1396 (c) 3 PKT-INT Link Migration failure in Begin Step * 1397 (c) 3 PKT-INT Link Migration denied, (peer test in p
PAGE 2190
Communication Manager Maintenance-Object Repair Procedures d. Aux Data 1361, 1370, 1400, 1401: consult SW-CTL service documentation. Test SW-CTL on both carriers with the long test sequence. Follow repair instructions for any failures. Once every test of both SW-CTLs passes, try the interchange again. e. Aux Data 1371, 1402, 1403, 1404, 2500: ensure that the standby server is refreshed, then try the interchange again. f.
PAGE 2191
SYSTEM (System) b. Error Type 8: a System Restart Level 3 was requested. c. Error Type 9: a System Restart Level 2 was requested. This can happen due to a loss of tones (due to a faulty Tone-Clock circuit pack). d. Error Type 10: a System Restart Level 1 was requested. e. Error Type 21: a process trapped. f. Error Type 355: a Restart Level 2 occurred due to a power loss. g. Error Type 356: a Restart Level 2 occurred due to a tone clock loss. h. Error Type 601: an error occurred during initialization. i.
PAGE 2192
Communication Manager Maintenance-Object Repair Procedures TBRI-BD (TN2185 ISDN Trunk-Side BRI) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TBRI-BD MIN test board location long r# TBRI-BD Note: Note: G700: The separate, but equivalent MG-BRI MO can reside in slots 1–4 of a G700 media gateway. Refer to MG-BRI (BRI Trunk Media Module MM720) on page 1586 for information about the MG-BRI MO.
PAGE 2193
TBRI-BD (TN2185 ISDN Trunk-Side BRI) Figure 136: Integrated Trunk-Side BRI, ISDN Interface Reference Points PBX CO V S NT2 TE 4-Wire PRI 1 S R NT2 U LT NT1 NT 2-Wire 4-Wire 2 T TE NT 4-Wire NT2 3 NT 2-Wire NT2 NT 4-Wire U NT1 TE NT1 LT 4 LT S/T U Terminal Adapter T NT 2-Wire S/T T NT 2-Wire TE TE 5 PBX ISDN Interface Reference Points cydfisdn RPY 072397 Figure notes:ISDN Interface Reference Point definitions LT Logical Terminal V Primary Rate user/network (asymmetric
PAGE 2194
Communication Manager Maintenance-Object Repair Procedures S/T 4-wire Basic Rate connection to an NT2 Termination1. T 4-wire Basic Rate interface to an NT Termination.2 TE Terminal Equipment U Basic Rate network-side 2-wire line interface. 1 TN556B ISDN-BRI 4-Wire S/T-NT Line (A-law) 2 TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) 3 TN2198 ISDN-BRI 2-Wire U Interface 5 TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side) 2 of 2 1.
PAGE 2195
TBRI-BD (TN2185 ISDN Trunk-Side BRI) Table 783: TBRI-BD Error Log Entries (continued) Error Type Aux Data 1537 (i) Alarm Level On/Off Board 46082 MIN ON 1793 (j) 46080 MIN ON 1794 (j) 46094 MIN ON 1795 (j) 46085 MIN ON 2305 (k) 46104 None ON 2306 (k) 46081 None ON 3330 (k) 46083 MIN OFF MIN OFF 3586 (l) 3841 (m) 4096 4101 3842 (n) 46095 3843 (o) 46097 Associated Test Test to Clear Value 2 of 2 Notes: a. Error Type 0: run the short test sequence first.
PAGE 2196
Communication Manager Maintenance-Object Repair Procedures d. Error Type 513: on-board hardware failure. Aux Data values correspond to the following detected errors: 4352 External RAM error 4353 Internal RAM error 4355 ROM Checksum error 4357 Instruction set error Use busyout board location and reset board location to reset the circuit pack. When reset, the circuit pack executes a set of tests to detect the presence of any of the faults listed above.
PAGE 2197
TBRI-BD (TN2185 ISDN Trunk-Side BRI) j. Error Type 1792 - 1795: the circuit pack is having problems transmitting/receiving data to/ from the Packet bus. 1793 Parity errors are detected when transmitting data to the Packet bus. 1794 Packet bus transmit buffers overflow. 1795 Circuit pack cannot find end of frame when transmitting to Packet bus. Clear the alarm with busyout board location, reset board location, test board location long clear, release board location.
PAGE 2198
Communication Manager Maintenance-Object Repair Procedures a LAPD parameter mismatch. LAPD should recover from this problem, but it may degrade the performance of the LAN bus. When this error is reported, maintenance reads and clears the board counter and logs the problem in the maintenance error log. o. Error Type 3843: bad translation RAM detected, but the call continues by using another translation location. The circuit pack reports this error when it cannot update NPE/NCE memory and read it back.
PAGE 2199
TBRI-BD (TN2185 ISDN Trunk-Side BRI) LAN Receive Parity Error Counter Test (#595) This test is nondestructive. The test reads and clears the circuit pack’s LAN Receive Parity Error Counter. This counter is incremented by the circuit pack when it detects a parity error in data received from the Packet bus. These errors may indicate problems with a circuit pack, Packet bus, or with another circuit pack on the bus. Use this test to verify the repair.
PAGE 2200
Communication Manager Maintenance-Object Repair Procedures TBRI-PT (ISDN Trunk-Side BRI Port) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TBRI-PT MAJ test port location l r# TBRI-PT TBRI-PT MIN test port location l r# TBRI-PT TBRI-PT WRN test port location sh r# TBRI-PT This document describes the port maintenance features of the TN2185 Trunk-Side ISDN-BRI board.
PAGE 2201
TBRI-PT (ISDN Trunk-Side BRI Port) Figure 137: Integrated Trunk-Side BRI, ISDN Interface Reference points PBX CO V S NT2 TE 4-Wire PRI 1 S R NT2 U LT NT1 NT 2-Wire 4-Wire 2 T TE NT 4-Wire NT2 3 LT 4 LT S/T NT1 NT 2-Wire NT2 NT 4-Wire U NT1 TE U Terminal Adapter T NT 2-Wire S/T T NT 2-Wire TE TE 5 PBX ISDN Interface Reference Points cydfisdn RPY 072397 Issue 1 June 2005 2201
PAGE 2202
Communication Manager Maintenance-Object Repair Procedures Figure notes:ISDN Interface Reference Point definitions LT Logical Terminal V 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. R Interface between Terminal Equipment and Network Termination S Basic Rate network-side 4-wire line interface S/T 4-wire Basic Rate connection to a NT2 Termination1.
PAGE 2203
TBRI-PT (ISDN Trunk-Side BRI Port) Table 785: TBRI-PT Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 513 (e) 46222 XMIT FIFO Overflow MIN ON 514 (f) XMIT FIFO Overflow (TDM) MIN ON 769 (g) Traffic Hyperactivity MIN OFF BRI NPE Crosstalk test (#617) MIN ON CRC error (D-channel) MIN OFF 1538 (k) CRC error (TDM D-channel) MIN OFF 1793 (l) BRI Port Local TDM Loop-around test (#619) MIN ON MIN OFF Test to Clear Value 1025 (h) 1281 (i
PAGE 2204
Communication Manager Maintenance-Object Repair Procedures b. Error Type 1: loss of continuity of Layer 1 to the far end. It is assumed that Layer 1 remains active, even when both B channels are idle. This test determines whether Layer 1 is active or not. If Layer 1 is not active, the test attempts to activate it. If Layer 1 cannot be activated, the port is taken out of service, and the test fails. c.
PAGE 2205
TBRI-PT (ISDN Trunk-Side BRI Port) i. Error Type 1281: this error occurs when the BRI NPE Crosstalk test (#617) has failed. The test will be repeated every 15 minutes until it passes. Follow normal trouble shooting procedures for BRI NPE Crosstalk test (#617). If this does not fix the problem, follow normal escalation procedures. j. Error Type 1537: the board received a bad Cyclical Redundancy Check (CRC) over the D channel. This error is reported on a per-port basis.
PAGE 2206
Communication Manager Maintenance-Object Repair Procedures s. Error Type 3588: the board receives D-channel data from the bus faster than it can process the data. The FIFO RAM buffers overflowed. This error occurs occasionally due to the statistical sizing of the buffers; however, frequent occurrences may indicate a LAPD parameter mismatch between the two endpoints of a packet-switched connection.
PAGE 2207
TBRI-PT (ISDN Trunk-Side BRI Port) Table 786: Aux Data Values for Error 3841–3942 (continued) Aux Data Value Type of Problem Meaning 62 subscription Service not authorized 63 admin/sub Service/option not available 65 admin/sub Bearer capability not implemented 66 admin/sub Channel type not implemented 69 admin/sub Requested facility not implemented 70 admin/sub Only restricted digital BC available 79 admin Service/option not implemented 88 admin Incompatible destination 102 swit
PAGE 2208
Communication Manager Maintenance-Object Repair Procedures Order of Investigation Short Test Sequence Long Test Sequence D/ND1 Slip Query test (#1244) X X ND Clear Error Counters test (#270) X X ND X D BRI NPE Crosstalk test (#617) S8300 / G700: Aborts with Error Code 1412 on a G700 1. D = Destructive; ND = Nondestructive 2208 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2209
TBRI-PT (ISDN Trunk-Side BRI Port) Clear Error Counters Test (#270) This test is nondestructive. This test clears the error counters associated with each TBRI-PT. This test passes if maintenance software is able to successfully send the downlink messages. The test aborts otherwise. Table 787: Test #270 Clear Error Counters Error Code Test Result Description / Recommendation Any ABRT Maintenance could not send the downlink message.
PAGE 2210
Communication Manager Maintenance-Object Repair Procedures Table 788: Test #617 BRI NPE Crosstalk Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the station extension or trunk group/member number of the port. Use status bri-port location to determine the service state of the port.
PAGE 2211
TBRI-PT (ISDN Trunk-Side BRI Port) Table 788: Test #617 BRI NPE Crosstalk Test (continued) Error Code Test 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. 2. If complaints still exist, examine the connections and wiring. 2 of 2 BRI Port Local LAN Loop-Around Test (#618) This test is destructive.
PAGE 2212
Communication Manager Maintenance-Object Repair Procedures Table 789: Test #618 BRI Port Local LAN Loop Around Error Code Test Result Description / Recommendation 1015 ABRT The port is not out-of-service. 1. Use status bri-port location to determine the status of the port. 2. If it is in use, wait until it is idle, and then use busyout port location to place it in the out-of-service state and repeat this test.
PAGE 2213
TBRI-PT (ISDN Trunk-Side BRI Port) Table 789: Test #618 BRI Port Local LAN Loop Around (continued) Error Code Test Result Description / Recommendation FAIL The Loop-Around test has failed. 1. If the test fails repeatedly, try to reset the circuit pack with busyout board location and reset board location if the other ports on the board are idle. 2. If the test fails again, execute test pkt P. If this fails, follow failure procedures in the PKT-BUS section. 3.
PAGE 2214
Communication Manager Maintenance-Object Repair Procedures Table 790: Test #619 BRI Port Local TDM Loop Around Error Code Test Result Description / Recommendation 1000 ABRT The system resources required to run this test are not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status bri-port location to determine the service state of the port.
PAGE 2215
TBRI-PT (ISDN Trunk-Side BRI Port) Table 790: Test #619 BRI Port Local TDM Loop Around (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test was not received from the BRI-TRUNK circuit pack within the allowable time period. 1. If this result occurs repeatedly, try to reset the circuit pack with busyout board location and reset board location if other ports on the board are idle. 2. If this result occurs again, replace the circuit pack.
PAGE 2216
Communication Manager Maintenance-Object Repair Procedures 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. The CRC error counter is incremented by the circuit pack when it detects a CRC error. The test passes if the value of the counter is 0 (that is, the error is cleared).
PAGE 2217
TBRI-PT (ISDN Trunk-Side BRI Port) Table 792: Test #625 Receive FIFO Overflow Error Counter Test Error Code Test Result Description / Recommendation 2000 ABRT 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 busyout board location and reset board location. 2. If the test aborts again, replace the circuit pack. 2012 ABRT Internal system error 1.
PAGE 2218
Communication Manager Maintenance-Object Repair Procedures The Pending Activation state indicates a problem with the channels, the wiring, or the TBRI-BD circuit pack. When in this state, the Level 1 interface is either not receiving any L1 framing from the channel, or it is communicating with the channel but cannot transition to the Activated state. The Deactivated state indicates a problem with the TBRI-BD circuit pack.
PAGE 2219
TBRI-PT (ISDN Trunk-Side BRI Port) Table 793: Test #1242 Level 1 Status Query (continued) Error Code Test Result Description / Recommendation 1 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. 2. Verify that the connections between the switch and the NT1 are good. Verify that the NT1 has power. 3.
PAGE 2220
Communication Manager Maintenance-Object Repair Procedures Table 793: Test #1242 Level 1 Status Query (continued) Error Code Test Result Description / Recommendation 3 FAIL Received a status of Level 1 Deactivated; the port is out-of-service. 1. Run status bri-port location to verify that the service state of the port is out-of-service. If the service state of the port is not out-of-service, escalate the problem to the next tier. Otherwise, proceed to Step 2. 2.
PAGE 2221
TBRI-PT (ISDN Trunk-Side BRI Port) Layer 3 Query Test (#1243) This test is nondestructive. This test is used to check the application layer communications across the in-service ISDN D channel. The test passes if a status inquiry message is successfully sent, fails if the signaling link is down, and aborts if a query is already running or there is an internal error.
PAGE 2222
Communication Manager Maintenance-Object Repair Procedures 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 BRI Slip Query test polls the total number of slips that have occurred on a link. When the TN2185 circuit pack detects a slip condition, maintenance software initiates the BRI Slip Query test to query the slip counters on the TN2185 circuit pack.
PAGE 2223
TBRI-PT (ISDN Trunk-Side BRI Port) Table 795: Test #1244 BRI Port Slip Query Test (continued) Error Code Test Result Description / Recommendation 1 to 88 FAIL The circuit pack and the remote endpoint are not synchronized to the same clock rate, which has generated the Slip alarm. The Error Code equals the number of slips detected by the TN2185 circuit pack since the last Slip Alarm Inquiry test. 1. Retry the command at 1-minute intervals up to 5 times. 2.
PAGE 2224
Communication Manager Maintenance-Object Repair Procedures TBRI-TRK (Trunk-Side ISDN BRI Channel) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TBRI-TRK1 MAJ2 test trunk location l Trunk-Side ISDN BRI Channel TBRI-TRK MIN test trunk location l Trunk-Side ISDN BRI Channel TBRI-TRK WRN test trunk location sh Trunk-Side ISDN BRI Channel 1.
PAGE 2225
TBRI-TRK (Trunk-Side ISDN BRI Channel) Hardware Error Log Entries and Test to Clear Values Table 796: TBRI-TRK Error Log Entries Error Type Aux Data Associated Test Alarm Level On/ Off Board Test to Clear Value 0 (a) 0 Any Any Any test port location sh r 1 Service State Audit (#256) WRN OFF WRN OFF WRN OFF 513 (b) 1793 (c) 3073 (d) 8, 9 Service State Audit (#256) 3585 (e) 3841 (f) Notes: a. Error Type 0: run the Short Test Sequence first. If all tests pass, run the Long Test Sequence.
PAGE 2226
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2227
TBRI-TRK (Trunk-Side ISDN BRI Channel) Table 797: Test #1251 Signaling Link State Test (continued) Error Code Test Result Description / Recommendation 1114 ABRT The signaling link is in a transitional state. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to abort, escalate the problem. 8 FAIL The signaling link is down. 1. Consult the procedures for the TBRI-PT MO. 9 FAIL The port is out of service. 1. Return the port to an in-service state.
PAGE 2228
Communication Manager Maintenance-Object Repair Procedures Table 798: Test #256 Service State Audit Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT The test aborted due to a configuration problem. This test may not be applicable, or it may be disruptive to terminal equipment other than a voice terminal (for example, a modem pool member or Music on Hold). This error can be ignored. 1018 ABRT The test is disabled. 1.
PAGE 2229
TBRI-TRK (Trunk-Side ISDN BRI Channel) 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. The test can be helpful when trying to clear a hung call. If the internal call state data to the near-end switch is different from that of the far-end switch, the call will be torn down.
PAGE 2230
Communication Manager Maintenance-Object Repair Procedures Table 799: Test #257 Call State Audit Test (continued) Error Code Test Result Description / Recommendation FAIL Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to fail, escalate the problem. PASS The audit passed successfully. 2 of 2 ISDN Test Call Test (#258) This test performs a far-end loop around to a far-end switch over an ISDN trunk.
PAGE 2231
TBRI-TRK (Trunk-Side ISDN BRI Channel) Synchronous Commands You can demand a synchronous outgoing test call by using the following maintenance commands: ● test trunk grp#/mem# long [repeat number] ● test board location long [repeat number] ● test port location long [repeat number] Whenever a circuit translates to a trunk-side ISDN-BRI channel during a long test sequence, an outgoing test call is invoked, and the duration of the test call is 8.6 seconds.
PAGE 2232
Communication Manager Maintenance-Object Repair Procedures Table 800: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1024 ABRT (M/T-DIG) Maintenance/Test Digital Port in use. 1. Wait until yellow and green LEDs are turned off on the M/T-BD (Maintenance/Test circuit pack). 2. Retry the test. If problem persists, see M/T-DIG (Maintenance/ Test Digital Port) on page 1709.
PAGE 2233
TBRI-TRK (Trunk-Side ISDN BRI Channel) Table 800: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 1120 ABRT The trunk-side ISDN-BRI facility is in the ISDN out-of-service/far-end state. 1. Try to change the service state via Test #256 (Service State Audit test). Then retry this test. However, the trunk may be in the out-of-service/far-end state due to problems at the far-end switch. If that is the case, no remedial action can be taken at this end.
PAGE 2234
Communication Manager Maintenance-Object Repair Procedures Table 800: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2040 ABRT 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. 2041 ABRT 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. If the test continues to abort, escalate the problem.
PAGE 2235
TBRI-TRK (Trunk-Side ISDN BRI Channel) Table 800: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2104 ABRT Call dropped or could not be originated. 1. Make sure service is provisioned by the network. 2. Check the administration of the far-end test line extension on the trunk group administration screen. 3. Check the administration of the test call BCC (Bearer Capability Class) on the trunk group administration screen. 4. Try the test again. 5.
PAGE 2236
Communication Manager Maintenance-Object Repair Procedures Table 800: Test #258 ISDN Test Call (continued) Error Code Test Result Description / Recommendation 2213 ABRT 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. If the test continues to abort, escalate the problem. 2214 ABRT Call terminated by unexpected disconnect. 1. Wait one minute and then try again. 2215– 2219 ABRT Internal system error 1.
PAGE 2237
TDM-BUS (TDM Bus) TDM-BUS (TDM Bus) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command to Run1 Full Name of MO TDM-BUS MAJ test tdm P TDM bus TDM-BUS MIN test tdm P TDM bus TDM-BUS WRN test tdm P TDM bus 1. P is the port network number. Use list cabinet to find the port network(s) contained in a cabinet. Description Each port network has a pair of TDM buses, designated TDM bus A and TDM bus B, each with 256 time slots.
PAGE 2238
Communication Manager Maintenance-Object Repair Procedures 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 2239
TDM-BUS (TDM Bus) 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.
PAGE 2240
Communication Manager Maintenance-Object Repair Procedures 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. If causing a disruption to all users in the port network is deemed permissible, large groups of circuit packs should be worked with in order to get the job done quickly.
PAGE 2241
TDM-BUS (TDM Bus) Procedure 3: Removing and Reinserting PN Control Circuit Packs This procedure removes and reinserts a PN’s control circuit packs. Use this procedure to test: ● TN570 Expansion Interface ● TN768, TN780 Tone-Clock Check the Tone-Clock circuit pack next-to-last. Check the Expansion Interface circuit pack (TN570) last, because removing this circuit pack disconnects its PN.
PAGE 2242
Communication Manager Maintenance-Object Repair Procedures 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. Repeat Procedure 3 for the next circuit pack on the list for this procedure. If none of the TDM-bus tests fail, the procedure is completed.
PAGE 2243
TDM-BUS (TDM Bus) Part 2 1. Run set tone-clock to make the currently active Tone-Clock standby. 2. Run test tdm P to determine whether the TDM-bus fault is still present. If the TDM-bus fault is gone: a. Replace the formerly active Tone-Clock circuit pack. b. Run set tone-clock again to make the new Tone-Clock circuit pack active. c. Run test tdm P to determine whether the TDM-bus fault is still present.
PAGE 2244
Communication Manager Maintenance-Object Repair Procedures 4. If every standby circuit pack has been tested but the TDM-bus failure still exists, execute reset pnc interchange and set tone-clock to put the currently active circuit packs into standby mode. Repeat Part 3 of this procedure for each of the newly active circuit packs. Procedure 4: Isolating TDM-Bus Failures to Carriers Procedure 4 attempts to isolate a TDM-bus failure to a particular set of carriers.
PAGE 2245
TDM-BUS (TDM Bus) After cabling changes are made and verified, power must be restored to the PN. Circuit packs in carriers outside the shortened bus are not inserted. As a result, these circuit packs are alarmed. Ignore these alarms for now. Every alarm should be resolved when the cabinet is restored to its original configuration. Procedure 4 is organized into two parts. Part 1 attempts to clear a TDM-bus fault by replacing every bus cable and terminator within a PN.
PAGE 2246
Communication Manager Maintenance-Object Repair Procedures 3. If none of the TDM-bus tests fail, extend the TDM bus to another carrier, and repeat the procedure in the previous step. When a carrier that causes the fault to recur is added, perform Procedure 2 for only the circuit packs in that carrier. 4. If any of the TDM-bus tests fail and Procedures 2 and 3 did not resolve the problem, the added carrier(s) are defective and must be replaced.
PAGE 2247
TDM-BUS (TDM Bus) Error Log Entries and Test to Clear Values Table 801: TDM Bus Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 0 Any Any Any test tdm P 1 0 Control Channel test (#296) MIN ON test tdm P r 3 18 (a) 0 busyout tdm PC WRN ON release tdm PC 35 (b) 0-1 TDM bus Corruption MIN ON set tdm PC 257 (c) 0 None MAJ ON 513 (d) Any Idle Time Slot test (#294) MIN ON test tdm P r 3 769 (e) Any Idle Time Slot test
PAGE 2248
Communication Manager Maintenance-Object Repair Procedures c. Error Type 357: this error indicates the TDM bus was switched to the other bus due to TDM bus corruption. The Aux Data value is not meaningful and no action is required. Look for other TDM-BUS errors to determine the cause of this error. d. Error Type 513: some time slots are corrupted in the specified TDM bus. The Minor alarm is raised when there are more than 50 bad time slots in the bus.
PAGE 2249
TDM-BUS (TDM Bus) Idle Time Slot Test on TDM bus A or B (#294) The Idle Time Slot test detects noisy time slots on the bus and takes them out-of-service. The Tone Detector circuit is told to listen to idle time slots and if it detects any noise on a time slot, it returns a failure. At the end of the test, any out-of-service time slots are retested to see if they are still noisy and restored to service if they are idle.
PAGE 2250
Communication Manager Maintenance-Object Repair Procedures 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). If a reply from the queried circuit pack is received, the TDM bus is considered operational and the test passes.
PAGE 2251
TDM-BUS (TDM Bus) Digit Detection Test (#297) This test is executed on the Non-Control Channel bus. The Tone-Clock circuit is told to put a tone on the Non-Control Channel bus and the Tone Detector circuit is told to listen to it. The test passes if the tone is successfully transmitted on the Non-Control Channel bus. Table 804: Test #297 Digit Detection Test Error Code Test Result Description / Recommendation None 1001 2100 ABRT Could not allocate the necessary system resources to run this test.
PAGE 2252
Communication Manager Maintenance-Object Repair Procedures TDM-CLK (TDM Bus Clock) S8700 | 8710 / S8500 Note: MO Name Alarm Level Initial SAT Command to Run Full Name of MO TDM-CLK MAJ test tone-clock location short TDM bus Clock TDM-CLK MIN test tone-clock location short TDM bus Clock TDM-CLK WRN release tone-clock location TDM bus Clock Note: Replacing the Tone-Clock circuit pack or the IPSI requires a special procedure described in the documentation for TONE-BD (Tone-Clock Circuit) on
PAGE 2253
TDM-CLK (TDM Bus Clock) Table 805: Synchronization - Tone Clock Roles (continued) Tone-Clock Role Synchronization Facilities Initial External Synchronization Source Backup External Synchronization Source Internal Source MASTER DS1 Primary and Secondary DS1 Primary DS1 Secondary Local oscillator DS1 Primary Only DS1 Primary None No External Source None None PNC Duplication Active EI Standby EI No PNC Duplication Active EI None S8700 MC SLAVE 2 of 2 See SYNC (Port-Network Synchronizat
PAGE 2254
Communication Manager Maintenance-Object Repair Procedures Table 806: TDM Bus Clock Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board1 Test to Clear Value 769 (g) Any Clock Circuit Status inquiry (#148) MAJ‡ ON test tone-clock location sh r 10 1025 (h) Any Clock Slip inquiry(#149) 1281 1282 (i) Any None 1537 Any Clock PPM inquiry (#150) 2049 (j) Any Standby Reference Health Check test (#651) MAJ2 ON 2305 (k) 0 None WRN OFF test tone-cl
PAGE 2255
TDM-CLK (TDM Bus Clock) e. Error Type 257: the Tone-Clock circuit pack in PN 1 is not a TN780 although Stratum-3 synchronization is administered. Either: 1. If a Stratum-3 clock is being used, replace this Tone-Clock with a TN780. 2. If not, change synchronization administration to Stratum 4. f. Error Type 513: the tone-clock has reported an out-of-lock condition. A aux value of 1 indicates this error is an out-of-lock with the primary reference.
PAGE 2256
Communication Manager Maintenance-Object Repair Procedures h. Error Type 1025: Processor/Tone-Clock circuit on-board maintenance has detected one or more clock slips, timing differences between its internal reference source and the synchronization signal provided by the master Tone-Clock. Although no clock slip errors are expected during normal operation, both manual and automatic interchanges of Tone-Clock circuit, synchronization references, and PNCs could result in clock slip counts.
PAGE 2257
TDM-CLK (TDM Bus Clock) j. Error Type 2049: S8700 MC The Tone-Clock circuit in the master port network was unable to detect the incoming synchronization signal, but the other tone-clock was able to detect the references. If the Aux Data is 0, the problem is with the signal on the primary. If the Aux Data is 1, the problem is with the signal on the secondary. The system should switch clocks in this situation. 1.
PAGE 2258
Communication Manager Maintenance-Object Repair Procedures c. If not, replace the standby Tone-Clock circuit. See Replacing the IPSI or Tone-Clock Circuit Pack on page 2337. If this clears the error, the problem has been resolved. 5. Replace the EI circuit pack for the active PNC. 6. If the problem is still not cleared and the IPSI or Tone-Clock circuit pack reported in the error log has not yet been replaced, replace it. See Replacing the IPSI or Tone-Clock Circuit Pack on page 2337.
PAGE 2259
TDM-CLK (TDM Bus Clock) Notes: a. See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for a descriptions of this test. b. See TONE-BD (Tone-Clock Circuit) on page 2327 for a description of this test. c. See TONE-PT (Tone Generator) on page 2353 for descriptions of this test. d. S8700 MC:This test only runs on the standby IPSI or Tone-Clock circuit pack in a port network with more than one IPSI or Tone-Clock circuit pack (high- or critical-reliability option).
PAGE 2260
Communication Manager Maintenance-Object Repair Procedures Table 808: Test #148 TDM bus Clock Circuit Status Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 FAIL This error means the Tone-Clock circuit framing verification firmware reports an error in the clock synchronization signal coming into this port network. 1. If the Tone-Clock circuit reporting the problem is a master clock, then the system synchronization reference is providing a bad timing source.
PAGE 2261
TDM-CLK (TDM Bus Clock) Table 808: Test #148 TDM bus Clock Circuit Status Inquiry Test (continued) Error Code Test Result Description / Recommendation 65 FAIL The Processor/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. Examine the error log for any DS1-BD, SYNC or other TDM-CLK errors and resolve as applicable. 2. Run this test again using test tone-clock location. 3.
PAGE 2262
Communication Manager Maintenance-Object Repair Procedures Note: Note: This test does not apply to the TN2182. Table 809: Test #149 TDM bus Clock Slip Inquiry Test Error Code Test Result Description / Recommendation ABRT The system could not allocate the necessary resources for the test. 1. Wait 1-minute, and retry the test. 1001 ABRT The system could not allocate the necessary resources for the test. 1. Wait 1-minute, and retry the test.
PAGE 2263
TDM-CLK (TDM Bus Clock) Table 809: Test #149 TDM bus Clock Slip Inquiry Test (continued) Error Code Test Result Description / Recommendation Any FAIL The Error Code represents the number of timing slips detected on the incoming synchronization source since the last slip inquiry was sent to the Tone-Clock circuit. The incoming synchronization signal can be from one of the following sources: 1.
PAGE 2264
Communication Manager Maintenance-Object Repair Procedures TDM bus Clock PPM Inquiry Test (#150) This test evaluates the quality of the synchronization source for the Tone-Clock circuit. Table 810: Test #150 TDM bus Clock PPM Inquiry Test Error Code Test Result Description / Recommendation ABRT The system could not allocate the necessary resources for the test 1. Wait 1-minute, and retry the test. 1001 ABRT The system could not allocate the necessary resources for the test. 1.
PAGE 2265
TDM-CLK (TDM Bus Clock) Table 810: Test #150 TDM bus Clock PPM Inquiry Test (continued) Error Code Test Result Description / Recommendation PASS The IPSI or Processor/Tone-Clock circuit pack does not detect timing any PPM errors. This indicates that the external synchronization timing source is valid or that the system synchronization reference is an IPSI or Processor/ Tone-Clock circuit pack.
PAGE 2266
Communication Manager Maintenance-Object Repair Procedures S8700 MC Board Type Check Test (#574) This test verifies that a Tone-Clock circuit pack administered with a Stratum-3 clock source has code TN780. Table 812: Test #574 Board Type Check Test Error Code Test Result Description / Recommendation 2012 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2267
TDM-CLK (TDM Bus Clock) Standby Reference Health Check Test (#651) This test evaluates the quality of the external synchronization timing source for a standby IPSI or Tone-Clock circuit pack. Every administered synchronization timing source must be valid for this test to pass. If the Tone-Clock circuit and the synchronization timing sources are in different port networks, the EI circuit packs transport the timing sources to the tone-clock.
PAGE 2268
Communication Manager Maintenance-Object Repair Procedures TDMODULE (Trunk Data Module) S8700 | 8710 / S8500 The TDMODULE (Trunk Data Module) is covered in the PDMODULE (Processor Data Module) on page 1751. 2268 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2269
TIE-BD (Tie Trunk Circuit Pack) TIE-BD (Tie Trunk Circuit Pack) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command To Run Full Name of MO TIE-BD MIN test board location sh Tie Trunk Circuit Pack TIE-BD WARNNG test board location sh Tie Trunk Circuit Pack See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit-pack level errors. See TIE-TRK (Analog Tie Trunk) on page 2302 for trunk information.
PAGE 2270
Communication Manager Maintenance-Object Repair Procedures TIE-DS1 (DS1 Tie Trunk) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TIE-DS11 MAJ2 test trunk grp#/mem# long3 DS1 Tie Trunk TIE-DS1 MIN test trunk grp#/mem# long3 DS1 Tie Trunk TIE-DS1 WRN test trunk grp#/mem# DS1 Tie Trunk 1. For additional repair information, see DS1-BD (DS1 Interface Circuit Pack) on page 978 if the tie trunk is on a TN722 or TN767 DS1 circuit pack.
PAGE 2271
TIE-DS1 (DS1 Tie Trunk) MM710 DS1 Interface Media Module. Throughout this TIE-DS1 section, the term DS1 Interface applies to DS1 or UDS1 circuit packs, or to MM710 Media Modules. Note: S8300 / G700: Although the TIE-DS1 MO is provided for a G700 Media Gateways, Note: this MO only partially supports the MM710 DS1 Media Module.
PAGE 2272
Communication Manager Maintenance-Object Repair Procedures Table 814: DS1 Tie Trunk Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level 257 (g) 57473 57474 513 (h) 769 (i) On/Off Board Test to Clear Value 57392 DS1 Tie Trunk Seizure (#136) MAJ MIN2 57393 DS1 Tie Trunk Seizure (#136) MAJ MIN2 1025 DS1 Tie Trunk Seizure (#136) MIN WRN2 OFF test trunk grp#/mem# r 2 1281 Conference Circuit Test (#7) MIN WRN2 ON test trunk grp#/mem# l r 4 1 1537 NP
PAGE 2273
TIE-DS1 (DS1 Tie Trunk) b. Error Type 1: the DS1 Interface circuit pack or media module detects a hardware error on the DS1 tie trunk. This error can be caused by incompatible translations. Make sure the parameters administered on the DS1 circuit pack or media module form match those administered on the far-end switch. See Administrator Guide for Avaya Communication Manager, 03-300509 for details.
PAGE 2274
Communication Manager Maintenance-Object Repair Procedures i. Error Type 769: the DS1 Interface circuit pack or media module detects a hardware error on the DS1 tie trunk. This error usually occurs after an occurrence of Error Type 513. The trunk has received the belated “on-hook” that it has been waiting for from the far-end switch. The trunk is restored to in-service/idle and can be used for calls. Aux Data 57393 indicates delayed external release on PBX disconnect. This error can be ignored. j.
PAGE 2275
TIE-DS1 (DS1 Tie Trunk) System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence. Order of Investigation Short Test Sequence Long Test Sequence D/ND1 NPE Crosstalk test (#6) S8500 / G700: Aborts with Error Code 1412 on a G700. X ND Conference Circuit test (#7) S8500 / G700: Aborts with Error Code 1412 on a G700.
PAGE 2276
Communication Manager Maintenance-Object Repair Procedures Table 815: Test #6 NPE Crosstalk Test Error Code Test Result Description / Recommendation ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/member number of the port.
PAGE 2277
TIE-DS1 (DS1 Tie Trunk) Table 815: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port was seized by a user for a valid call. 1. Use display port location to determine the trunk group/member number of the port. Use status trunk to determine the service state of the port. If the service state indicates that the port is in use, then the port is unavailable for certain tests. Wait until the port is idle before retesting. 2.
PAGE 2278
Communication Manager Maintenance-Object Repair Procedures Table 815: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation FAIL This can be due to either on- or off-board problems. Off-board problems of concern include EXP-PN and EXP-INTF faults (S8700 MC), RMC-ENV faults (S8700 IP), TDM-BUS faults, and faults associated with the tone detectors/tone generators. Clear every off-board problem before replacing the board.
PAGE 2279
TIE-DS1 (DS1 Tie Trunk) Conference Circuit Test (#7) Note: S8500 / G700: This test aborts with Error Code 1412 on the G700. Note: 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 2280
Communication Manager Maintenance-Object Repair Procedures Table 816: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1003 ABRT 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 of the tone detectors may be out of service. Enter list measurements tone-receiver to display basic information about the system's tone receivers. 1. Resolve any TTR-LEV errors. 2.
PAGE 2281
TIE-DS1 (DS1 Tie Trunk) Table 816: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 2100 ABRT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 2053 ABRT At least one of the following errors is found on the DS1 circuit pack: 1281 – Loss of signal,1793 – Blue alarm, 2049 – Red alarm, 2305 – Yellow alarm, or 1537 – Hyperactivity.
PAGE 2282
Communication Manager Maintenance-Object Repair Procedures Table 816: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1. Enter list configuration board location. If the circuit pack is a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3 or later. The error log may have Error Type 1281 entries. 2.
PAGE 2283
TIE-DS1 (DS1 Tie Trunk) Table 816: Test #7 Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board’s translations are correct. Use list configuration, and resolve any problems that are found. 2.
PAGE 2284
Communication Manager Maintenance-Object Repair Procedures Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface circuit pack or media module 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 2285
TIE-DS1 (DS1 Tie Trunk) Table 817: Test #36 Port Audit and Update Test (continued) Error Code Test Result Description / Recommendation FAIL Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack or media module and switch software are consistent. If the trunk is busied out, the test does not run but returns a PASS. To verify that the trunk is in-service: 1.
PAGE 2286
Communication Manager Maintenance-Object Repair Procedures DS1 Tie Trunk Seizure Test (#136) The DS1 Tie Trunk Seizure test is run to verify the trunk’s signaling capability. The test is composed of two parts. The first part queries the circuit pack or media module for the following errors: Loss of Signal, Red alarm, Blue alarm, Yellow alarm, and Hyperactivity alarm.
PAGE 2287
TIE-DS1 (DS1 Tie Trunk) Table 818: Test #136 DS1 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test were not available. The port may be busy with a valid call. 1. Use display port location to determine the trunk group/ member number of the port. Use status trunk to determine the service state of the port. If the port is in use, wait until the port is idle before testing. 2.
PAGE 2288
Communication Manager Maintenance-Object Repair Procedures Table 818: Test #136 DS1 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation 1020 ABRT The test did not run due to an already existing error on the specific port or due to a more general circuit pack or media module error. 1. Examine the error log for existing errors against this port or the circuit pack or media module and attempt to diagnose the already existing error. 2. Retry the test.
PAGE 2289
TIE-DS1 (DS1 Tie Trunk) Table 818: Test #136 DS1 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation FAIL The far-end trunk did not respond to the seizure of the near-end trunk within the allowable time period. This test could have associated in-line errors in the error log. 1. Enter list configuration board location. 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 2290
Communication Manager Maintenance-Object Repair Procedures Table 818: Test #136 DS1 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Check to ensure that the board’s translations are correct. Use list config, and resolve any problems that are found. 2.
PAGE 2291
TBRI-PT (ISDN Trunk-Side BRI Port) TBRI-PT (ISDN Trunk-Side BRI Port) MO Name Alarm Level Initial Command to Run* Full Name of MO TBRI-PT MAJ test port GGGVSPP l r# TBRI-PT TBRI-PT MIN test port GGGVSPP l r# TBRI-PT TBRI-PT WRN test port GGGVSPP s r# TBRI-PT Note: Consult local records for the location and designation of the equipment rack where the Media Gateway is mounted.
PAGE 2292
Communication Manager Maintenance-Object Repair Procedures Table 819: TBRI-PT Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 46222 XMIT FIFO Overflow MIN ON 514 (f) XMIT FIFO Overflow (TDM) MIN ON 769 (g) Traffic Hyperactivity MIN OFF CRC error (D-Channel) MIN OFF CRC error (TDM D-Channel) MIN OFF MIN OFF Test to Clear Value 257 (d) 513 (e) 1025 (h) 1537 (i) 46210 1538 (j) 2049 (k) 2305 (l) Layer 3 Query (#1243) MIN OFF 3073 (m)
PAGE 2293
TBRI-PT (ISDN Trunk-Side BRI Port) b. Error Type 1: loss of continuity of Layer 1 to the far-end. It is assumed that Layer 1 remains active, even when both B-Channels are idle. This test determines whether Layer 1 is active or not. If Layer 1 is not active, the test attempts to activate it. If Layer 1 cannot be activated, the port is taken out of service, and the test fails. c. Error Type 129: the far-end switch changed the ISDN service state. This may be a temporary condition. d.
PAGE 2294
Communication Manager Maintenance-Object Repair Procedures i. Error Type 1537: the board received a bad Cyclical Redundancy Check (CRC) over the D-Channel. This error is reported on a per-port basis. When the CRC errors exceed 5 within 15 minutes, the port is taken out of service for 5 seconds. If 5 more CRC errors are received within 15 minutes of the first set of 5 errors, the port is taken out of service for 1 minute.
PAGE 2295
TBRI-PT (ISDN Trunk-Side BRI Port) s. Error Type 3590: an activated BRI port receives a frame containing a DLCI over a D-Channel for which it does not have a translation. This error normally indicates an off-board problem related to a state mismatch between the far-end and the switch. This error is logged only. t. Error Type 3591: the circuit pack received a frame containing a DLCI over the TED D-channel for which it does not have a translation.
PAGE 2296
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2297
TBRI-PT (ISDN Trunk-Side BRI Port) Clear Error Counters Test (#270) This test is nondestructive. This test clears the various error counters associated with each TBRI-PT. This test passes if maintenance software is able to successfully send the downlink messages; the test aborts otherwise. Table 822: TEST #270 Clear Error Counters Error Code Test Result Description/ Recommendation Any ABRT Maintenance could not send the downlink message.
PAGE 2298
Communication Manager Maintenance-Object Repair Procedures Receive FIFO Overflow Error Counter Test (#625) This test is nondestructive. This test reads and clears the BRI port’s Receive FIFO Overflow error counter maintained on the TBRI-BD media module. This counter is incremented by the media module when it detects an overflow of its receive buffers. The test passes if the value of the counter is 0 (that is, the error is cleared).
PAGE 2299
TBRI-PT (ISDN Trunk-Side BRI Port) Layer 3 Query Test (#1243) This test is nondestructive. This test is used to check the application layer communications across the in-service ISDN D-Channel. The test passes if a status enquiry message is successfully sent, fails if the signaling link is down, and aborts if a query is already running or there is an internal error.
PAGE 2300
Communication Manager Maintenance-Object Repair Procedures Table 825: TEST #1243 Layer 3 Query (continued) Error Code Test Result Description/ Recommendation 1187 ABRT The media module or port might have been busied out. 1. Look in the Error Log for Error Type 18 (busied out) for TBRI-BD or TBRI-PT. If this Error Type is present for TBRI-PT, then release the port with the release port GGGVSpp command and run the test again. 2.
PAGE 2301
TBRI-PT (ISDN Trunk-Side BRI Port) Table 826: TEST #1244 Slip Alarm Inquiry Test Error Code 2000 Test Result Description/ Recommendation ABRT Internal system error ABRT Response to the test request was not received within the allowable time period. 1. If Error Type 1538 is present in the Error Log, follow the maintenance strategy recommended for this Error Type. 2100 ABRT Could not allocate the necessary system resources to run this test. 1.
PAGE 2302
Communication Manager Maintenance-Object Repair Procedures TIE-TRK (Analog Tie Trunk) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run1 Full Name of MO TIE-TRK MAJ2 test port location l Tie Trunk TIE-TRK MIN test port location l Tie Trunk TIE-TRK WRN test port location sh Tie Trunk 1. If ATMS testing is enabled, check the error log for ATMS errors 3840 and 3841.
PAGE 2303
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. The port must be idle for these tests to run. If an incoming call seizes the port while a test is in progress, the test aborts and the call proceeds (except for TN497). The test are as follows: 1.
PAGE 2304
Communication Manager Maintenance-Object Repair Procedures Additional in-line testing is performed whenever a call is in progress, logging errors that occur during operation. You can reproduce these types of errors by making a call over the trunk and then checking the Hardware Error Log. By making translation and cross-connect changes, circuit packs (except for TN497) can be configured for back-to-back testing, also known as connectivity testing.
PAGE 2305
TIE-TRK (Analog Tie Trunk) Table 828: TIE Trunk Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board 1025 (n) Any None MAJ MIN WRN1 OFF 1281 (m) Any EPF M and E Lead (#74) MAJ MIN WRN1 ON test port location sh r 3 1537 Looparound and Conference (#33) MAJ MIN WRN1 ON test port location l r 3 1793 Tie Trunk Seizure (#73) Dial Test #747 for TN439 MAJ MIN WRN1 OFF test port location sh r 2 2049 NPE Crosstalk (#6) MAJ MIN WRN1 ON test port loca
PAGE 2306
Communication Manager Maintenance-Object Repair Procedures b. Error Type 1: 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. Check the far-end PBX to ensure a translation match at both ends. This error does not apply to TN497. c. Error Type 1: rotary dial before wink.
PAGE 2307
TIE-TRK (Analog Tie Trunk) o. Error Type 2305: 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. This service state shows up as disconnected on the Trunk Status screen. Run the Tie Trunk Seizure test, and follow recommended procedures. TN439 logs Aux Data 57424 or 50944.
PAGE 2308
Communication Manager Maintenance-Object Repair Procedures Order of Investigation Port Audit and Update test (#36) Short Test Sequence Long Test Sequence X X Transmission test - ATMS (#844-848)2 D/ND1 ND ND 2 of 2 1. D = Destructive, ND = Nondestructive 2. ATMS tests are not part of either sequence. They are run either on demand with test analog-testcall, or by the ATMS schedule.
PAGE 2309
TIE-TRK (Analog Tie Trunk) Table 829: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, repeat test at 1-minute intervals up to 5 times. 1003 ABRT The system could not allocate a tone receiver for the test.
PAGE 2310
Communication Manager Maintenance-Object Repair Procedures Table 829: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation Any FAIL This test can fail due to either on- or off-board problems. Off-board problems of concern include EXP-PN, EXP-INTF, or RMC-ENV faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators. Clear every off-board problem before replacing the board.
PAGE 2311
TIE-TRK (Analog Tie Trunk) Looparound and Conference Circuit Test (#33) This test verifies signal transmission and conferencing capabilities of a port using 404-, 1004-, and 2804-Hz tones. This is an on-board test only: each tone is transmitted to and looped around within the port and then returned. This test can fail due to noise induced by adjacent electric power lines. If this is the case, the customer must resolve it with their local power company.
PAGE 2312
Communication Manager Maintenance-Object Repair Procedures Table 830: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, repeat test at 1-minute intervals up to 5 times.
PAGE 2313
TIE-TRK (Analog Tie Trunk) Table 830: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation 7 129 131 133 FAIL The conference capabilities of the port failed (Error Code 7). The reflective 404-Hz Tone test failed. No transmission was detected to or from the port (Error Code 129). The reflective 1004-Hz Tone test failed. No transmission was detected to or from the port (Error Code 131). The reflective 2804-Hz Tone test failed.
PAGE 2314
Communication Manager Maintenance-Object Repair Procedures Table 830: Test #33 Looparound and Conference Circuit Test (continued) Error Code Test Result Description / Recommendation PASS Tie trunk Looparound and Conference test is successful. This port is functioning properly. 1. If users are reporting troubles, examine loop connections to the port. 0 NO BOARD The test could not relate the internal ID to the port (no board). 1. Verify that the board’s translations are correct.
PAGE 2315
TIE-TRK (Analog Tie Trunk) Table 831: Test #36 Audit Update Test (continued) Error Code Test Result Description / Recommendation 1006 ABRT (TN497 circuit pack only.) The port is in the out-of-service state. The test cannot be run. 1. Retry the command once the port is in service. 2100 ABRT Could not allocate the necessary system resources to run the test. This could be due to a failure to seize the port. 1. Retry the command at 1-minute intervals up to 5 times. FAIL Internal system error 1.
PAGE 2316
Communication Manager Maintenance-Object Repair Procedures Tie Trunk Seizure Test (#73) and Tie Trunk Dial Test (#747) For wink-start, delay-dial and TN2140 (cont-seize-ack or discont-seize-ack) trunks, this test activates the M lead and checks for a response from the far end within 10 seconds. For TN497, the test seizes a trunk and outpulses a pause. The port reports uplink the result of the seizure. This test can be disabled using the Test field on the Trunk Group Administration screen.
PAGE 2317
TIE-TRK (Analog Tie Trunk) Table 832: Test #73,#747 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT This test is not valid for this trunk translation. Must be a wink-start or delay dial trunk and must be outgoing or 2-way for this test to run. For the TN2140, the trunk must also be continuous-seize-ack or discontinuous-seize-ack. 1. Check trunk translation. If it is not a wink-start or delay dial trunk, this abort message should be ignored.
PAGE 2318
Communication Manager Maintenance-Object Repair Procedures Table 832: Test #73,#747 Tie Trunk Seizure Test (continued) Error Code Test Result Description / Recommendation S8700 | 8710: FAIL Seizure message is not received back within 10 seconds. 2000 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to fail, check the far-end PBX to ensure a translation match at both ends. 3. Check the facility. PASS The relevant Seizure test passes.
PAGE 2319
TIE-TRK (Analog Tie Trunk) Table 833: Test #74 Tie Trunk EPF Test (continued) Error Code Test Result Description / Recommendation 1 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The trunk may be busy with a valid call. Use display trunk-group xx to determine trunk group/member number of the port. Use status trunk to determine the service state of the port.
PAGE 2320
Communication Manager Maintenance-Object Repair Procedures Table 833: Test #74 Tie Trunk EPF Test (continued) Error Code Test Result Description / Recommendation 1040 ABRT This test is not performed for trunk ports administered as access endpoints. 1. Verify this port is an access endpoint by using display port. 2. If the port has been administered as an access endpoint, then this test should abort. 2000 ABRT Response to the test request was not received within the allowable time period. 1.
PAGE 2321
TIE-TRK (Analog Tie Trunk) Transmission Test (#844-848) This test is nondestructive. Note: 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 2322
Communication Manager Maintenance-Object Repair Procedures Table 834: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port has been seized by a user for a valid call. Use status trunk to determine when the port is available for testing. 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT Trunk has been administered as incoming-only; transmission tests can only be run on outgoing trunks.
PAGE 2323
TIE-TRK (Analog Tie Trunk) Table 834: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1915 ABRT Busy tone detected from far end. 1. Since the test line at the far end was busy. Try the test again. 2. If the test continues to abort, the problem is with the far-end system. 1918 ABRT Test progress tone not removed from far end (type 105 test line only). 1.
PAGE 2324
Communication Manager Maintenance-Object Repair Procedures Table 834: Test #844-848 Transmission Test (continued) Error Code Test Result Description / Recommendation 1940 ABRT Far-end noise self check failed. 1. The problem is with the far-end system; a technician at the far end should test the test line (TN771 or ADFTC). 1941 ABRT High frequency singing return loss self check failed. 1. Test the TN771 circuit packs. 1942 ABRT Echo return loss self check failed. 1. Test the TN771 circuit packs.
PAGE 2325
TIE-TRK (Analog Tie Trunk) Table 834: Test #844-848 Transmission Test (continued) Error Code 8000 Test Result Description / Recommendation FAIL Measured transmission performance was in the unacceptable range as administered on the trunk group screen. Retrieve a measurement report using list testcalls. Make sure that ATMS thresholds are set properly on page 4 of the trunk group screen. Besides the facility, test failures can be caused by faulty test lines or switch paths.
PAGE 2326
Communication Manager Maintenance-Object Repair Procedures TIME-DAY (Time of Day) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TIME-DAY MIN 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. The Time of Day MO monitors the time-of-day clock, and raises an alarm if the time-of-day clock is not set or cannot be read by the software.
PAGE 2327
TONE-BD (Tone-Clock Circuit) TONE-BD (Tone-Clock Circuit) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO TONE-BD MAJ test tone-clock location sh Tone-Clock circuit TONE-BD MIN test tone-clock location sh Tone-Clock circuit TONE-BD WRN release tone-clock location Tone-Clock circuit S8700 | 8710 / S8500 The TONE-BD MO supports PNs in a system using either a TN2312 IP Server Interface (IPSI) circuit pack, or for non IPSI EPNs equipped with Tone Clock circ
PAGE 2328
Communication Manager Maintenance-Object Repair Procedures The TN2182 is a combined Tone-Clock/Detector circuit pack, providing Tone-Clock functionality to a non IPSI PN. It provides 8 Enhanced Tone Receiver (ETR) ports. Each of these ports combines the individual capabilities of a DTMR-PT, a GPTD-PT, and a CLAS-PT. Thus, each TN2182 port offers any tone-detection function previously provided by a TN748, TN420, or TN744 Tone Detector board. The TN2182 also provides either Mu-law or A-law tone detection.
PAGE 2329
TONE-BD (Tone-Clock Circuit) Figure 139: S8700 IP Connect Duplex Reliability Configuration 1 4 2 3 1 4 2 Ethernet 1 Ethernet 1 Ethernet 0 5 6 6 1 2 7 10 8 IPSI 9 IPSI 9 10 10 100bT BBI 100bT BBI 100bT BBI LINK LINK LINK LINK LINK LINK TRMT TRMT TRMT TRMT TRMT TRMT RCV RCV RCV RCV RCV RCV PN 1 8 8 PN 2 cydsdup KLC 042204 IPSI 9 PN Figure notes: 1. S8700 Media Server 1 - two are always present, one in a active mode and the other on standby. 6.
PAGE 2330
Communication Manager Maintenance-Object Repair Procedures S8700 MC In IPSI connected port networks, the Tone Clock circuit is found on the IPSI circuit pack. In non IPSI connected port networks, there is a Tone Clock circuit pack. The following sections describe the relationship between the various reliability options and the IPSIs or Tone Clock circuits. S8700 Multi-Connect architecture has three items that can be duplicated: server, IPSI, and PNC.
PAGE 2331
TONE-BD (Tone-Clock Circuit) Figure 140: Duplex-Reliability Configuration Server A Server B Control Network A IPSI IPSI T/C PN 1 PN 2 PN 3 EI EI EI Bearer Network Standard Reliability Systems with the standard-reliability option (no duplication options) have one Tone-Clock circuit pack in each port network. For the first Port Network of a cabinet this is in the A carrier. Cabinets containing a second EPN will also have a Tone-Clock circuit pack in the E carrier.
PAGE 2332
Communication Manager Maintenance-Object Repair Procedures Figure 141: High-Reliability Configuration Server A Server B Control Network A Control Network B IPSI IPSI IPSI IPSI T/C PN 1 PN 2 PN 3 EI EI EI Bearer Network Systems with the High Reliability Option (duplicated SPE, simplex PNC) have one Tone-Clock circuit pack in each Port Network control carrier, A and B.
PAGE 2333
TONE-BD (Tone-Clock Circuit) Critical Reliability S8700 MC: The critical-reliability configuration shown in Figure 142 has full duplication of the following options: servers, control networks, IPSIs and PNCs (bearer networks). As with the high-reliability configuration, this configuration also requires that IPSI connected port networks have duplicated IPSIs. This configuration also requires that the non IPSI connected port networks have duplicated Tone-Clock boards (either TN2182 or TN780).
PAGE 2334
Communication Manager Maintenance-Object Repair Procedures Software Initiated Tone-Clock Interchanges Tone-Clock interchanges may be initiated by software in two ways: 1. A scheduled Tone-Clock or IPSI circuit pack interchange occurs according to the parameters set by change system-parameters maintenance. This parameter can be disabled or set to run weekly, the default is for it to occur daily, at a time specified in the system-parameters list for scheduled maintenance to begin.
PAGE 2335
TONE-BD (Tone-Clock Circuit) In addition the TN780 allows customization of up to six system tones in order to meet specific country needs. These changes are made using the change system-parameters country-options form. The TN2182 allows the same International changes as the TN780 but allows the customization of up to 24 system tones in order to meet specific country needs. These changes are made using the change tone-generation form.
PAGE 2336
Communication Manager Maintenance-Object Repair Procedures 3. A particular Tone-Clock circuit pack can be made active by issuing the set tone-clock location [override] command. If the Tone-Clock to be made active is less healthy than the currently active one, no interchange will occur unless the override option is specified; without it a message will inform the user that it is required.
PAGE 2337
TONE-BD (Tone-Clock Circuit) Stratum 3 Since the clock module on the TN2312 does not support synchronization with an external Stratum-3 clocking device, you may provide Stratum-3 clocking for a S8700 Media Server system by using the TN780 Tone-Clock circuit pack in a non-IPSI connected port network. To bring in the external Stratum-3 clocking signals into the TN780, a processor carrier is needed.
PAGE 2338
Communication Manager Maintenance-Object Repair Procedures S8700 | 8710 The following circuit-pack code(s) are supported: S8700 MC: This is a general-purpose Tone-Clock circuit pack for EPNs. It can be used in every situation, except as the Master Tone-Clock circuit pack when a Stratum-3 clock is administered. S8700 MC: The Stratum-3 clock feature requires the use of this circuit pack code in PN 1. The Stratum-3 clock will operate only with this code as the Master Tone-Clock circuit pack.
PAGE 2339
TONE-BD (Tone-Clock Circuit) Port Networks with a Single Tone-Clock Circuit Pack This procedure is destructive. 1. Pull out the defective IPSI or Tone-Clock circuit pack. This will remove the clocks and cause the system to activate emergency measures. If this is an IPSI supported port network, use busyout ipserver-interface: ● All calls to and from the PN will drop, and the PN will activate Emergency Transfer within about one minute. But the rest of the system should operate normally. 2.
PAGE 2340
Communication Manager Maintenance-Object Repair Procedures The active/standby state of a Tone-Clock circuit pack may also be determined by looking at its LED. A continuously lit red LED on the Tone-Clock circuit pack indicates a reported fault on one or more of the maintenance objects on the circuit pack. Flashing patterns of the yellow and green LEDs correspond to the following service states: Condition Tone-Clock Circuit State Explanation Flashing yellow 2.7 seconds on,.
PAGE 2341
TONE-BD (Tone-Clock Circuit) Note: Note: For a critical-reliability system (duplicated PNC), the system generally expects a PN to have its “preferred” Tone-Clock circuit pack active. For the first PN in a given cabinet, this is carrier A. For a second PN in the cabinet, this is carrier E. b. status system — Verify the Tone-Clock circuit pack switched to the other Tone-Clock circuit pack or check the LEDs.
PAGE 2342
Communication Manager Maintenance-Object Repair Procedures Table 837: LED Condition/Tone-Clock Circuit States Condition Tone-Clock Circuit State Explanation Flashing yellow 2.7 seconds on 0.3 seconds off Active An external timing source is being used as a synchronization reference1. Flashing yellow 0.3 seconds on 2.7 seconds off Active The local oscillator on the IPSI or Tone-Clock circuit pack is being used as a synchronization reference.
PAGE 2343
TONE-BD (Tone-Clock Circuit) Error Log Entries and Test to Clear Values Table 838: Tone-Clock Circuit Pack Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 0 (a) 0 Any Any Any test tone-clock location sh 1 (b) 0 Circuit pack removed or SAKI Sanity test (#53) MIN ON 18 (c) 0 busyout tone-clock location WRN OFF 23 (d) 0 None WRN OFF 125 (e) None MIN ON 126 (f) None MIN ON MIN ON release tone-clock location 257 (g) Any 65
PAGE 2344
Communication Manager Maintenance-Object Repair Procedures Table 838: Tone-Clock Circuit Pack Error Log Entries (continued) Error Type Aux Data Associated Test 3856 (q) 3857 3858 (r) NONE 3872 (s) 0 None 3999 (t) Any None Alarm Level On/Off Board Test to Clear Value MAJ ON set tone-clock location override1 MAJ ON busyout/release ipserver-interface set tone-clock location override1 2 of 2 1. *For a TN2312 IPSI supported port network, use the command set ipserver-interface. 2.
PAGE 2345
TONE-BD (Tone-Clock Circuit) Table 839: Effects of Tone-Clock Failures Depending on Reliability (continued) Reliability Option Effects High IPSI interchange in IPSI connected PN non IPSI connected PN goes down Critical IPSI interchange in IPSI connected PN Interchange to standby Tone-Clock circuit pack in non IPSI connected PN 2 of 2 If an interchange is attempted in an MCC PN and the system is unable to activate the standby Tone-Clock, Emergency Transfer is activated.
PAGE 2346
Communication Manager Maintenance-Object Repair Procedures j. Error Type 1025: this error is not service-affecting, and no action is required. k. Error Type 1538: the circuit pack was taken out of service because of an excessive rate of uplink messages. Use test tone-clock location long to reset the circuit pack and put it back into service. If the command is not successful, replace the circuit pack using the procedure described in Replacing the IPSI or Tone-Clock Circuit Pack on page 2337.
PAGE 2347
TONE-BD (Tone-Clock Circuit) 4. If the error has not been corrected at this point, there is a problem with the TDM bus within the port network containing the reported Tone-Clock circuit. This may include TDM bus intercarrier cables, bus terminators, bent pins on the backplane, and errors on any circuit pack plugged into the same port network. See TDM-BUS (TDM Bus) on page 2237. m.
PAGE 2348
Communication Manager Maintenance-Object Repair Procedures 4. Interchange the IPSI or Tone-Clock circuits, using set tone-clock location. If the command succeeds, the interchange that previously failed has been accomplished and the problem has been satisfactorily resolved. If it fails, proceed to the next step. You may want to proceed in any case to definitively test all relevant components. 5. Interchange the t/c selector using set expansion-interface.
PAGE 2349
TONE-BD (Tone-Clock Circuit) Note: Note: Whenever, the active archangel detects a loss of clock, it will alternate the state of the CLKSEL lead until the lost clock signals are restored. If the IPSI archangel restores the clock signals by activating the [A] IPSI/ Tone-Clock, then Error Type 3857 is reported. If the clock signals are restored by activating the [B] IPSI/Tone-Clock, then Error Type 3858 is reported.
PAGE 2350
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2351
TONE-BD (Tone-Clock Circuit) Notes: a. See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for descriptions of these tests. b. See TONE-PT (Tone Generator) on page 2353 for descriptions of these tests. c. See TDM-CLK (TDM Bus Clock) on page 2252 for descriptions of these tests. d. This test runs only on the standby IPSI or Tone-Clock circuit in a port network with duplicated Tone-Clocks (high- or critical-reliability systems). The circuit pack must be a TN780 with firmware version 2 or above.
PAGE 2352
Communication Manager Maintenance-Object Repair Procedures Table 841: Test #46 Clock Health Inquiry Test (continued) Error Code Test Result Description / Recommendation None FAIL This Tone-Clock or 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. Correct the problem according to the appropriate error log entries.
PAGE 2353
TONE-PT (Tone Generator) TONE-PT (Tone Generator) S8700 | 8710 / S8500 Note: MO Name Alarm Level Initial SAT Command to Run Full Name of MO TONE-PT MAJ test tone-clock location sh Tone Generator TONE-PT MIN test tone-clock location sh Tone Generator TONE-PT WRN release tone-clock location Tone Generator Note: Replacing the IPSI or Tone-Clock circuit pack requires a special procedure which is described in TONE-BD (Tone-Clock Circuit) on page 2327.
PAGE 2354
Communication Manager Maintenance-Object Repair Procedures Table 842: Tone Generator Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 18 (c) 0 busyout tone-clock location WRN OFF release tone-clock location None MIN ON test tone-clock location sh 130 (d) 257 (e)(g) 17667 None MIN ON 513 (f)(g) 17666 Tone Generator Audit/ Update (41) MIN ON test tone-clock location r 3 1281 (h) Any Tone Generator Audit/ Update (41) M
PAGE 2355
TONE-PT (Tone Generator) g. Error Types 257 and 513: infrequent errors, at a rate which does not bring up an alarm, probably do not affect service, unless there are customer complaints of no tones, or incorrect tones which can not be explained in any other way. However, if an alarm is raised because this error is being repeatedly logged, then the circuit pack should be replaced. See Replacing the IPSI or Tone-Clock Circuit Pack on page 2337. h.
PAGE 2356
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order listed. By clearing Error Codes associated with the SAKI Reset test for example, you may also clear errors generated from other tests in the sequence.
PAGE 2357
TONE-PT (Tone Generator) Tone Generator Transmission Test (#40) The purpose of this test is to verify that the tone generation hardware on the IPSI or Tone-Clock circuit pack is capable of generating a subset of system tones and a set of test tones. This test does not verify all system tones the tone generator produces during normal system operation. The test is performed in two parts. For the first part, the Tone Generator is told to generate the touch-tone digits.
PAGE 2358
Communication Manager Maintenance-Object Repair Procedures Table 843: Test #40 Tone Generator Transmission Test Error Code Test Result Description / Recommendation None ABRT The system was not able to allocate all the resources needed for this test or there was an Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 1 ABRT The system could not allocate all the resources needed to test the DTMF tones. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2359
TONE-PT (Tone Generator) Table 843: Test #40 Tone Generator Transmission Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT Response to the test request was not received within the allowable time period. System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2360
Communication Manager Maintenance-Object Repair Procedures a. All the failure Error Codes marked with (a) may affect users if the failure is on the active tone generator. When this type failure is detected, the system will attempt to move the tone generation function to the alternate IPSI or Tone-Clock circuit pack, if one is present in the affected port network.
PAGE 2361
TONE-PT (Tone Generator) Table 844: Test #41 Tone Generator Update/Audit Test (continued) Error Code Test Result Description / Recommendation 1 FAIL The system requires a TN780, TN2182, or TN2312 Tone-Clock circuit to support the administered tone-generation parameters. 1. Check the administration on the tone-generation screen. Specifically, the Base Tone Generation Set on page 1 and any custom tone administration beginning on page 2. 2. Replace any existing IPSI with a TN2312.
PAGE 2362
Communication Manager Maintenance-Object Repair Procedures Table 845: Test #90 Tone Generator Crosstalk Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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 ABRT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. FAIL The Tone Generator could be defective.
PAGE 2363
TR-LN-BD (Trunk Line Board) TR-LN-BD (Trunk Line Board) S8700 | 8710 / S8500 / G700 The TN797 Analog Trunk and Line circuit pack provides 8 ports, any of which may be administered as one of the following: Table 846: TN797 Analog Trunk and Line circuit pack – port administration Function Group Type Trunk Type Central Office trunk (CO) co fx wats loop start ground start CAMA/E911 trunk cama Direct Inward Dialing (DID) trunk did wink start immed start Analog Line on-or-off premises n/a n/a LED
PAGE 2364
Communication Manager Maintenance-Object Repair Procedures TSC-ADM (Administered Temporary Signaling Connections) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command 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). Administered temporary signaling connections (TSC) provide a path through ISDN-PRI networks for supplementary D-channel messages.
PAGE 2365
TSC-ADM (Administered Temporary Signaling Connections) The two maintenance commands for ADM TSCs are as follows: ● test tsc-administered signaling-group-number [/tsc-index] ● status tsc-administered signaling-group-number [/tsc-index] Error Log Entries and Test to Clear Values Table 847: ADM TSC Error Log Entries Error Type Aux Data Associated Test Alarm Level 38403967 (a) tsc index # test tsc-administered On/Off Board Test to Clear Value Note: a.
PAGE 2366
Communication Manager Maintenance-Object Repair Procedures TSC Heartbeat Inquiry Test (#604) This test can be invoked by system technician personnel for any ADM TSC administered in the switch. Most of the error conditions on the following table will not log an error, but switched services may take some type of recovery action in certain instances.
PAGE 2367
TSC-ADM (Administered Temporary Signaling Connections) Table 848: Test #604 TSC Heartbeat Inquiry Test (continued) Error Code Test Result Description / Recommendation 1146 ABRT The congestion just occurred in the network. 1. Enter status tsc-administered at 1-minute intervals up to 3 times. 2. If congestion does not clear, disable and enable the Administered TSC using change signaling-group grp#.
PAGE 2368
Communication Manager Maintenance-Object Repair Procedures Table 848: Test #604 TSC Heartbeat Inquiry Test (continued) Error Code Test Result Description / Recommendation 1181 ABRT Ran out of ADM TSC resources. 1. Execute test tsc-administered at 1-minute intervals up to 3 times. 1182 ABRT The BX.25 link is down at the gateway. 1. Disable the ADM TSC. 2. Check the status of the gateway link using status link lnk#. 3. Once the gateway link indicates an in-service state, enable the Administered TSC.
PAGE 2369
TSC-ADM (Administered Temporary Signaling Connections) Table 848: Test #604 TSC Heartbeat Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 FAIL The Administered TSC is not active (far end). 1. Execute test tsc-administered. 2. Verify that the Administered TSC node on the other side of the network is active. 3. Disable and enable the Administered TSC. 4. Retry test tsc-administered. 2 FAIL Facility IE (Information Element) reject. 1.
PAGE 2370
Communication Manager Maintenance-Object Repair Procedures TTR-LEV (TTR Level) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command to Run Full Name of MO TTR-LEV WRN See the Repair Procedure for TTR-LEV. TTR Level TTR-LEV MIN See the Repair Procedure for TTR-LEV. TTR Level TTR-LEV MAJ See the Repair Procedure for TTR-LEV. TTR Level TN748 and TN420 Tone Detector circuit packs and TN744 Call Classifier circuit packs provide tone receivers for detecting various types of signaling tones.
PAGE 2371
TTR-LEV (TTR Level) Another alarm is logged if the number falls to zero. At this point, system operation is severely compromised. Typical causes of these events are: 1. The threshold for GPTD-PTs or DTMR-PTs is administered incorrectly on the Maintenance-Related System-Parameters screen. 2. Too many GPTD-PTs, DTMR-PTs, or CLSFY-PTs have been taken out of service, possibly by maintenance software or a demand busyout. 3.
PAGE 2372
Communication Manager Maintenance-Object Repair Procedures 4. Enter display alarms and determine the location of the circuit pack with the alarmed GPTD-PT, DTMR-PT, or GPTD-PT. Run test board location l r 3 for that circuit pack. If this does not clear the TTR Level alarm, replace the Tone Detector or Call Classifier circuit pack with the alarmed GPTD-PT, DTMR-PT, or CLSFY-PT.
PAGE 2373
TTR-LEV (TTR Level) than the threshold. These errors are typically generated during boot time or other transitional states when the ports are being brought into service. d. Error Type 4: the total number of GPTD ports currently in service is below the administered threshold. To clear the alarm, see Repair Procedure for TTR-LEV on page 2371. e. Error Type 5: does not indicate a current error condition.
PAGE 2374
Communication Manager Maintenance-Object Repair Procedures UDS1-BD (UDS1 Interface Circuit Pack) S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO UDS1-BD MAJ test board location sh UDS1 Interface Circuit Pack UDS1-BD MIN test board location l UDS1 Interface Circuit Pack UDS1-BD WRN test board location sh UDS1 Interface Circuit Pack Note: G700: The separate, but equivalent, MG-DS1 MO can reside in slots 1–4 of a Note: G700 Media Gateway.
PAGE 2375
UDS1-BD (UDS1 Interface Circuit Pack) The TN464F or later circuit pack combined with an 120A1 CSU module forms an Enhanced Integrated CSU. The 120A1 CSU module, when combined with the functionality provided by the TN464F hardware and firmware, and switch software, provides functionality equivalent to an external stand-alone ESF T1 CSU. The 120A1 CSU module connects to the TN464F circuit pack on the I/O connector panel on the back of the port carrier.
PAGE 2376
Communication Manager Maintenance-Object Repair Procedures ● BLB = Board Loopback ● ELB = Equipment Loopback ● LLB = Line Loopback ● RLB = Repeater Loopback ● CLJ = Loop-Back Jack Loopback ● R-LLB = Remote Line Loopback ● SMRT = Smart Jack ● LPBK = Loopback 2Mbit Japan Trunk (TN2242) The TN2242 2-Mbit, 30-port trunk circuit pack supports Japanese TTC private networking environments.
PAGE 2377
UDS1-BD (UDS1 Interface Circuit Pack) Upgrading to TN2242 Figure 144 shows the hardware connections for public network access in Japan. The upgrade procedure requires removing the JRC (Japan Radio Corporation) external converter. Figure 144: Japanese TTC public network connections 1 1 2 2 3 4 4 cydfjap1 LJK 012899 Figure notes: 1. Communications System 3. JRC (Japan Radio Corporation) external converter 2. UDS1-BD DS1-CONV circuit pack (24-trunk digital tie trunk) 4.
PAGE 2378
Communication Manager Maintenance-Object Repair Procedures Figure 145: TN2242 Japan trunk TTC private network connections 1 1 2 3 4 4 3 2 cydfjap2 LJK 012999 Figure notes: 1. Communications System 3. H600-513 cable assembly cable (see H600-513 Cable Pinout on page 2379) 2. TN2242 2-Mbit Japan trunk circuit pack 4. TDM facilities To upgrade a system to the TN2242 circuit pack: 1. Busyout the UDS1-BD DS1-CONV circuit pack (busyout board location). 2.
PAGE 2379
UDS1-BD (UDS1 Interface Circuit Pack) H600-513 Cable Pinout The following table shows the pinout for the H600-513 cable assembly: TN2242 TDM 50-pin connection pin number Color Lead Designation Color 15-pin connection pin number 22 W-BL Line in + W-BL 4 23 W-O Line out - W-O 9 47 Bl-W Line in - Bl-W 11 48 O-W Line out + O-W 2 TN2242 Administration The TN2242 circuit pack requires board-level translation data.
PAGE 2380
Communication Manager Maintenance-Object Repair Procedures Table 850: TN2242 administration (continued) Field Value Incoming Dial Type tone, rotary, mf (to other Avaya systems only) Wink Timer for wink type 300 Wink Timer for delay type 4500 Trunk Group screen, Page 3 (Administrable Timers) Incoming Disconnect 100 Incoming Glare Guard 800ms or higher Incoming Dial Guard 10 Incoming Incomplete Dial Alarm 25 or higher Incoming Partial Dial 18 PPS 10 or 20 Make (for PPS 10) 35 Break (for
PAGE 2381
UDS1-BD (UDS1 Interface Circuit Pack) LEDs The LEDs on the faceplate of the TN2242 circuit pack indicate its status as described in Table 851: TN2242 LED interpretation on page 2381. Table 851: TN2242 LED interpretation LED Red Meaning ● MAJOR alarm ● MINOR alarm ● Firmware initialization during circuit pack insertion Amber A port on the circuit pack is in use. Green Maintenance testing is in progress on the circuit pack or its ports.
PAGE 2382
Communication Manager Maintenance-Object Repair Procedures TN2242 Serviceability Hardware Connections This circuit pack can be: ● Mated to another circuit pack of the same type when interconnecting two Communication Manager systems ● Directly connected to the TDM network device ● Directly connected to another vendor PBX using ISDN-PRI signaling Loopbacks There is no automatic process to signal the remote end to provide loopbacks for testing purposes.
PAGE 2383
UDS1-BD (UDS1 Interface Circuit Pack) The DS1 Circuit Pack screen for the TN464GP/TN2464BP circuit packs has fields to support echo cancellation: Echo Cancellation, EC Direction, and EC Configuration. The Echo Cancellation field appears when the Echo Cancellation feature is activated on the System-Parameters Customer Options screen. The EC Direction and EC Configuration fields appear when the DS1 Echo Cancellation field is enabled.
PAGE 2384
Communication Manager Maintenance-Object Repair Procedures The TN464 UDS1 Circuit Pack The TN464C, D, E, F, and GP Universal DS1 Interface circuit packs provide an interface to the DS1 facility, and are designed to support 24 DS0 channels on a 1.544-Mbps DS1 link, or 32 DS0 channels on a 2.048-Mbps link. (The 32-channel interface is not supported on G3r V1 systems.
PAGE 2385
UDS1-BD (UDS1 Interface Circuit Pack) The TN464 supports digital Tie, CO, and DID trunks, and OPS lines. On-board firmware performs call control signaling for the Tie, CO and DID trunks and OPS lines. ISDN-PRI trunk and PRI-endpoint signaling (Q.921, Q.931) is received and generated by system software and is transmitted on a system link through the TN1655 Packet Interface and packet bus to the UDS1 where it is placed on the D channel.
PAGE 2386
Communication Manager Maintenance-Object Repair Procedures Two option jumpers located on the side of the TN464C/D circuit pack must be installed correctly. The figures on the following page show how to configure the circuit pack for 24- or 32-channel DS1, and for 75*W (coaxial) or 120*W trunk connections. The channel selection must match the parameters administered on the corresponding DS1 Circuit Pack screen. (US applications use 24 Channels.
PAGE 2387
UDS1-BD (UDS1 Interface Circuit Pack) Figure 148: TN464E/F DS1 Option switches Ω Ω Firmware Download Feature Firmware Download allows new firmware to be downloaded to one or more UDS1 circuit boards residing in the system. The download image is copied onto a source (C-LAN) board, using FTP. The image is then copied to a target board’s flash memory over the TDM bus. The transfer of the download image from the source board to a target board is done under switch software’s control.
PAGE 2388
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 852: DS1 Interface Circuit Pack Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test board location 1(a) 0 Circuit pack removed or SAKI (#53) failed WRN2 MIN ON 18(b) 0 busyout board location WRN OFF release board location 23(c) 0 WRN OFF add ds1 location 125(d) none or 3 None WRN3 MIN ON
PAGE 2389
UDS1-BD (UDS1 Interface Circuit Pack) Table 852: DS1 Interface Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 1311(o) Any Equipment Loopback test (#1210) WRN3 MIN OFF test board location ds1/csu-loopback-tests 1312(p) Any Repeater Loopback test (#1211) WRN3 MIN OFF test board location ds1/csu-loopback-tests 1313(q) Any CPE Loop-Back Jack test (#1212) WRN3 MIN OFF test board location end-loopback/
PAGE 2390
Communication Manager Maintenance-Object Repair Procedures Table 852: DS1 Interface Circuit Pack Maintenance Error Log Entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 2305 Any Yellow Alarm Inquiry test (#141) WRN3 MIN OFF test board location 2306 Any Yellow Alarm Inquiry test (#141) WRN3 MIN OFF test board location 2561 Any Major Alarm Inquiry test (#142) WRN3 MIN OFF test board location Minor Alarm Inquiry test (#143) WRN3 MIN
PAGE 2391
UDS1-BD (UDS1 Interface Circuit Pack) Notes: a. Error Type 1: indicates that the circuit pack has 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 2392
Communication Manager Maintenance-Object Repair Procedures Aux Data 3: the 24-/32-channel option jumper setting on the circuit pack does not match the option set on the DS1 Circuit Pack administration screen. The circuit pack must be physically removed to see the setting of the jumper. e. Error Type 257: associated with the Common Port Circuit Pack Maintenance test. See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for details. f.
PAGE 2393
UDS1-BD (UDS1 Interface Circuit Pack) on back of the carrier. Otherwise, set the Near-End CSU Type field using the change ds1 screen to other. If this error remains after plugging the CSU module/T1 sync splitter into the board’s connector, there could be a problem with the I/O connector panel.
PAGE 2394
Communication Manager Maintenance-Object Repair Procedures DS1 circuit pack suffix incorrect for E1 synchronization splitter: The E1 Sync-Splitter field on the add ds1 screen is set to y but the DS1 circuit pack is not a TN464F or higher suffix UDS1 board. If the 402A or 403A E1 synchronization splitter is to be used, remove the circuit pack and replace it with a TN464F or higher suffix board. Otherwise, use change ds1 to set the E1 Sync-Splitter field to n. n. Error Type 1310: BLB failure.
PAGE 2395
UDS1-BD (UDS1 Interface Circuit Pack) q. Error Type 1313: CPE Loop-Back Jack deactivation error. This error occurs when the UDS1 circuit pack could not deactivate a CPE Loop-Back Jack on power-up/reset or upon software request. Try to clear the alarm using busyout board location, test ds1-loop location end-loopback/span-test, and release board location. If the attempt to deactivate the CPE Loop-Back Jack continues to fail, other steps must be taken to deactivate the loopback. r.
PAGE 2396
Communication Manager Maintenance-Object Repair Procedures The circuit pack is isolated from the system and every trunk or port on this circuit pack is placed into the out-of-service state. The system will try to restore the circuit pack within 20-30 minutes. When no faults are detected for 20-30 minutes, the UDS1 Interface circuit pack is restored to normal operation. Every trunk or port of the UDS1 Interface circuit pack is then returned to the in-service state.
PAGE 2397
UDS1-BD (UDS1 Interface Circuit Pack) aa. Error Type 3842: bad translation RAM location found error. This error is not service-affecting. No action is required. A Bad Translation RAM is detected, but the call continues by using another translation location. ab. Error Type 3843: LAN Receive Parity Error. This error occurs when the circuit pack detects an error in a received frame from the Packet bus. These errors are most likely caused by a Packet bus problem, but may be due to a circuit pack fault.
PAGE 2398
Communication Manager Maintenance-Object Repair Procedures Note: Note: G700: If the One-Way Span test is run between a circuit pack and an MM710 DS1 Interface Media Module on a G700 Media Gateway, the test will fail, because the MM710 does not frame-align its test pattern. af. Error Type 3999: indicates that the circuit pack sent a large number of control channel messages to the switch within a short period of time.
PAGE 2399
UDS1-BD (UDS1 Interface Circuit Pack) Table 853: UDS1 - Demand Test order of investigation (continued) Order of Investigation Short Test Sequence Long Test Sequence Internal Loop-Around test (#135) Reset Board Sequence test ds1-loop X D/ND1 D DS1/CSU Loopback tests: DS1 Board Loopback test (#1209) CSU Equipment Loopback test (#1210) CSU Repeater Loopback test (#1211) X X X D D D CPE Loop-Back Jack test (#1212) X D Far CSU Loopback test (#1213) X D One-Way Span test (#1214) X D Inject Si
PAGE 2400
Communication Manager Maintenance-Object Repair Procedures Table 854: Test #50 NPE Connection Audit Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2401
UDS1-BD (UDS1 Interface Circuit Pack) Table 855: Test #52 Control Channel Loop-Around Test (continued) Error Code 0 Test Result Description / Recommendation PASS Communication with this circuit pack is successful. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2402
Communication Manager Maintenance-Object Repair Procedures Table 856: Test #53 SAKI Sanity Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT Wrong circuit pack configuration to run this test. This error applies only to DS1 Interface circuit packs. It means the DS1 Interface circuit pack is providing timing for the system, and therefore, it cannot be reset without major system disruptions. 1.
PAGE 2403
UDS1-BD (UDS1 Interface Circuit Pack) Table 856: Test #53 SAKI Sanity Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered. 2.
PAGE 2404
Communication Manager Maintenance-Object Repair Procedures Table 857: Test #135 Internal Loop-Around Test Error Code Test Result Description / Recommendation 1002 ABRT 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. 1. If system has no TDM-BUS errors and is not handling heavy traffic, repeat test at 1-minute intervals up to 5 times.
PAGE 2405
UDS1-BD (UDS1 Interface Circuit Pack) Table 857: Test #135 Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 2012 ABRT Internal system error 1. Retry the reset board location command at 1-minute intervals up to 5 times. 2100 ABRT Could not allocate the necessary system resources to run this test. 1. Retry reset board location at 1-minute intervals up to 5 times. FAIL The UDS1 Interface circuit pack failed the Internal Loop-Around test.
PAGE 2406
Communication Manager Maintenance-Object Repair Procedures Table 857: Test #135 Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation FAIL (cont’d) If the UDS1 connects to a line-side terminating device such as a PRI terminal adapter: 1. Retry reset board location at 1-minute intervals up to 5 times. 2. Enter list measurement ds1-log location to read the error seconds measurement. 3.
PAGE 2407
UDS1-BD (UDS1 Interface Circuit Pack) Table 857: Test #135 Internal Loop-Around Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered. 2.
PAGE 2408
Communication Manager Maintenance-Object Repair Procedures 120A1 CSU Module/Sync Splitter This test is also used to maintain the 120A1 CSU module or the 401A T1 sync splitter, and the 402A or 403A E1 synchronization splitter. The CSU module, when combined with the functionality provided by the UDS1 circuit pack, provides functionality equivalent to an external stand-alone ESF T1 CSU. The combination of the UDS1 and 120A1 CSU module is known as an Enhanced Integrated CSU (I-CSU).
PAGE 2409
UDS1-BD (UDS1 Interface Circuit Pack) Table 858: Test #138 Loss of Signal Alarm Inquiry Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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 2410
Communication Manager Maintenance-Object Repair Procedures Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test 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 2411
UDS1-BD (UDS1 Interface Circuit Pack) Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1300 FAIL The CSU module/T1 sync splitter or the E1 Sync Splitter is missing. The CSU module/T1 sync splitter is missing: The Near-End CSU Type field on the add ds1 screen has been administered as integrated but the 120A1 CSU module or the 401A T1 sync splitter is not physically connected to the UDS1 board on the back of the port carrier. 1.
PAGE 2412
Communication Manager Maintenance-Object Repair Procedures Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1301 FAIL The 120A1 CSU module or the 401A T1 sync splitter, or the 402A or 403A E1 synchronization splitter is not expected.
PAGE 2413
UDS1-BD (UDS1 Interface Circuit Pack) Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1303 FAIL The UDS1 circuit pack Suffix is incorrect for CSU module/T1 sync splitter or E1 Sync Splitter administration. The UDS1 circuit pack Suffix is incorrect for CSU module/T1 sync splitter administration.
PAGE 2414
Communication Manager Maintenance-Object Repair Procedures Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test 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.
PAGE 2415
UDS1-BD (UDS1 Interface Circuit Pack) Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1313 FAIL The UDS1 circuit pack could not deactivate a CPE Loop-Back Jack loopback. 1. Execute test ds1-loop location end-loopback/span-test 2. If the attempt to deactivate the CPE Loop-Back Jack is not successful, check the cabling and investigate the problem at the CPE Loop-Back Jack. 3. Run the test again.
PAGE 2416
Communication Manager Maintenance-Object Repair Procedures Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1322 FAIL No 5-Volt power detected from the UDS1 circuit pack to the CSU module or the Sync Splitter. Problem is probably due to an open fuse on the UDS1 board or to a faulty ICSU/Sync Splitter. Note: Do not immediately swap a UDS1 board as this may blow the fuse on the new board. 11.
PAGE 2417
UDS1-BD (UDS1 Interface Circuit Pack) Table 858: Test #138 Loss of Signal Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1401 FAIL Echo Canceller memory failed. This could be a hardware problem on the TN464GP/TN2464BP: 1. Enter busyout board location. 2. Enter reset board location. 3. Enter test board location long. 4. Enter release board location. 5. If the test still fails, replace the TN464GP/TN2464BP.
PAGE 2418
Communication Manager Maintenance-Object Repair Procedures 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 2419
UDS1-BD (UDS1 Interface Circuit Pack) Table 859: Test #139 Blue Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2420
Communication Manager Maintenance-Object Repair Procedures Table 859: Test #139 Blue Alarm Inquiry Test (continued) Error Code Test 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 2421
UDS1-BD (UDS1 Interface Circuit Pack) 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 2422
Communication Manager Maintenance-Object Repair Procedures Table 860: Test #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2423
UDS1-BD (UDS1 Interface Circuit Pack) Table 860: Test #140 Red Alarm Inquiry Test (continued) Error Code Test 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. If the UDS1 connects to a T1 network facility or to another switch, do the following. 1.
PAGE 2424
Communication Manager Maintenance-Object Repair Procedures Table 860: Test #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 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. The UDS1 interface circuit pack will transmit a remote multiframe alarm (RMA) to the remote UDS1 endpoint until the LMA is retired.
PAGE 2425
UDS1-BD (UDS1 Interface Circuit Pack) Table 860: Test #140 Red Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered. 2.
PAGE 2426
Communication Manager Maintenance-Object Repair Procedures Yellow F5 Fault Alarm For 32-channel E1 operation with CRC4 on, the F5 fault state is defined as a fault in the user-network interface, specifically in the direction from the user (PBX) to the network. Refer to CCITT recommendation I.431. Table 861: Test #141 Yellow Alarm Inquiry Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2427
UDS1-BD (UDS1 Interface Circuit Pack) Table 861: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test 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 2428
Communication Manager Maintenance-Object Repair Procedures Table 861: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 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. If the UDS1 connects to a T1 network facility or to another switch, do the following: 1.
PAGE 2429
UDS1-BD (UDS1 Interface Circuit Pack) Table 861: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2 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. If the UDS1 connects to a T1 network facility: 1.
PAGE 2430
Communication Manager Maintenance-Object Repair Procedures Table 861: Test #141 Yellow Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2431
UDS1-BD (UDS1 Interface Circuit Pack) Table 862: Test #142 Major Alarm Inquiry Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited.
PAGE 2432
Communication Manager Maintenance-Object Repair Procedures Table 862: Test #142 Major Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation FAIL If the UDS1 connects to a T1 network facility or to another switch, do the following: 1. The performance of the DS1 link between the UDS1 interface circuit pack and the remote DS1 endpoint is very poor. Enter list measurement ds1-log location to read the error seconds measurement. 2.
PAGE 2433
UDS1-BD (UDS1 Interface Circuit Pack) Table 862: Test #142 Major Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered. 2.
PAGE 2434
Communication Manager Maintenance-Object Repair Procedures Table 863: Test #143 Minor Alarm Inquiry Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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 2435
UDS1-BD (UDS1 Interface Circuit Pack) Table 863: Test #143 Minor Alarm Inquiry Test (continued) Error Code Test 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. If the UDS1 connects to a T1 network facility or to another switch, do the following: 1. The performance of the DS1 link between the UDS1 interface circuit pack and the remote DS1 endpoint is poor.
PAGE 2436
Communication Manager Maintenance-Object Repair Procedures Table 863: Test #143 Minor Alarm Inquiry Test (continued) Error Code 0 Test Result Description / Recommendation PASS No Minor alarm is detected in the UDS1 Interface circuit pack. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2437
UDS1-BD (UDS1 Interface Circuit Pack) Table 864: Test #144 Slip Alarm Inquiry Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2438
Communication Manager Maintenance-Object Repair Procedures Table 864: Test #144 Slip Alarm Inquiry Test (continued) Error Code Test 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. The Error Code equals the number of slips detected by the UDS1 interface circuit pack since the last slip alarm inquiry test.
PAGE 2439
UDS1-BD (UDS1 Interface Circuit Pack) Table 864: Test #144 Slip Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 to 88 FAIL (cont’d) If the UDS1 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following: 1. Retry the command at 1-minute intervals up to 5 times. 2. Enter list measurement ds1-log location to read the error seconds measurement. 3.
PAGE 2440
Communication Manager Maintenance-Object Repair Procedures Misframe Alarm Inquiry Test (#145) A Misframe Alarm indicates that framing bits observed on a UDS1 Interface circuit pack are in error. The Misframe Alarm Inquiry test queries the total number of misframes that have occurred on a UDS1 Interface circuit pack since the last inquiry. When the UDS1 Interface circuit pack detects a misframe error, it increments its misframe counter by one. If the counter reaches a specified threshold (i.e.
PAGE 2441
UDS1-BD (UDS1 Interface Circuit Pack) Table 865: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2442
Communication Manager Maintenance-Object Repair Procedures Table 865: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test 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 2443
UDS1-BD (UDS1 Interface Circuit Pack) Table 865: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 1 to 17 FAIL (cont’d) If the UDS1 connects to a line-side terminating device such as a PRI terminal adapter: 1. Retry the command at 1-minute intervals up to 5 times. 2. Enter the list measurement ds1-log location command to read the error seconds measurement. 3.
PAGE 2444
Communication Manager Maintenance-Object Repair Procedures Table 865: Test #145 Misframe Alarm Inquiry Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2445
UDS1-BD (UDS1 Interface Circuit Pack) Table 866: Test #146 Translation Update Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute interval s up to 5 times. FAIL Internal system software error. 1. Enter display ds1 location to verify the UDS1 Interface circuit pack translation. 0 PASS Translation data has been downloaded to the UDS1 Interface circuit pack successfully.
PAGE 2446
Communication Manager Maintenance-Object Repair Procedures When the BLB test is initiated, maintenance software sends an appropriate message to the UDS1 Interface circuit pack to start the test. The board sets up the BLB loopback, transmits a test pattern, and verifies that the pattern is received unaltered through the loopback. If the transmitted and received pattern is different, the test fails.
PAGE 2447
UDS1-BD (UDS1 Interface Circuit Pack) Table 867: Test #1209 DS1 Board Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1950 ABRT Another loopback/span test is already executing on the DS1 board or the board is in a network-requested loop-back mode (line loopback or payload loopback).
PAGE 2448
Communication Manager Maintenance-Object Repair Procedures Table 867: Test #1209 DS1 Board Loop-Back Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2449
UDS1-BD (UDS1 Interface Circuit Pack) When the test is complete, each trunk or port on the UDS1 Interface circuit pack is restored to the in-service state after the release board location command is entered. Table 868: Test #1210 CSU Equipment Loop-Back Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry test ds1-loop location ds1/csu-loopback-tests at 1-minute intervals up to 5 times.
PAGE 2450
Communication Manager Maintenance-Object Repair Procedures Table 868: Test #1210 CSU Equipment Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1950 ABRT Another loopback/span test is already executing on the DS1 board or the board is in a network-requested loop-back mode (line loopback or payload loopback).
PAGE 2451
UDS1-BD (UDS1 Interface Circuit Pack) Table 868: Test #1210 CSU Equipment Loop-Back Test (continued) Error Code Test Result Description / Recommendation FAIL UDS1 Interface circuit pack failed the CSU Equipment Loopback test. 1. Retry test ds1-loop location ds1/csu-loopback-tests. 2. If the ELB test continues to fail, then either the UDS1-BD board, the CSU module/T1 sync splitter, or the I/O cable between the backplane and the CSU module/T1 sync splitter (or any combination thereof) has failed.
PAGE 2452
Communication Manager Maintenance-Object Repair Procedures 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 or the 401A T1 sync splitter and tests the connection from the DS1 board up to and including the CSU module/T1 sync splitter circuitry. This test is only performed if the 120A1 CSU module or the 401A T1 sync splitter is present, administered, and connected to a 1.
PAGE 2453
UDS1-BD (UDS1 Interface Circuit Pack) Table 869: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1015 ABRT Ports on the UDS1 Interface circuit pack have not been busied out to out-of-service. 1. Enter busyout board location to put each trunk or port of the UDS1 Interface circuit pack into the out-of-service state. 2. Retry the command. 1039 ABRT The UDS1 Interface circuit pack is providing timing for the system.
PAGE 2454
Communication Manager Maintenance-Object Repair Procedures Table 869: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2455
UDS1-BD (UDS1 Interface Circuit Pack) Table 869: Test #1211 CSU Repeater Loop-Back Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered.
PAGE 2456
Communication Manager Maintenance-Object Repair Procedures The status of the CPE Loop-Back Jack test is available in the hardware error log via Error Type 3900. Several distinct Aux values give the user information about the status of the test. The list measurements ds1 summary command shows the length of time the test has been running (Test Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field).
PAGE 2457
UDS1-BD (UDS1 Interface Circuit Pack) Table 870: Test #1212 CPE Loop-Back Jack Test (continued) Error Code Test Result Description / Recommendation 1039 ABRT 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 or Tone-Clock circuit pack via the following command sequence: 1.
PAGE 2458
Communication Manager Maintenance-Object Repair Procedures Table 870: Test #1212 CPE Loop-Back Jack Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited.
PAGE 2459
UDS1-BD (UDS1 Interface Circuit Pack) Table 870: Test #1212 CPE Loop-Back Jack Test (continued) Error Code Test Result Description / Recommendation 3 FAIL The CPE Loop-Back Jack 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 CPE Loop-Back Jack, could not be detected properly by the UDS1 circuit pack. 1. Retry test ds1-loop location cpe-loopback-jack-test-begin 2.
PAGE 2460
Communication Manager Maintenance-Object Repair Procedures 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.
PAGE 2461
UDS1-BD (UDS1 Interface Circuit Pack) Table 871: Test #1213 Far CSU Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT Far CSU Loopback test cannot be executed in the current configuration. To run this test, the TN464F or higher suffix UDS1 must be administered for 24-channel operation. The Bit Rate field on the DS1 circuit pack administration screen must be set to 1.544 for 24-channel operation.
PAGE 2462
Communication Manager Maintenance-Object Repair Procedures Table 871: Test #1213 Far CSU Loop-Back Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2463
UDS1-BD (UDS1 Interface Circuit Pack) Table 871: Test #1213 Far CSU Loop-Back Test (continued) Error Code Test Result Description / Recommendation 3 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. 1. Retry test ds1-loop location far-csu-loopback-test-begin. 2.
PAGE 2464
Communication Manager Maintenance-Object Repair Procedures One-Way Span Test (#1214) This test is destructive. 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 UDS1 board to the remote test equipment or other Avaya communications system. The test is destructive and can only be initiated with the test ds1-loop location one-way-span-test-begin command.
PAGE 2465
UDS1-BD (UDS1 Interface Circuit Pack) Table 872: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 1005 ABRT One-Way Span test cannot be executed in the current configuration. To run this, the TN464F or higher suffix UDS1 must be administered for 24-channel operation. The Bit Rate field on the DS1 Circuit Pack administration screen must be set to 1.544 for 24-channel operation. 1015 ABRT Ports on the UDS1 Interface circuit pack have not been busied out. 1.
PAGE 2466
Communication Manager Maintenance-Object Repair Procedures Table 872: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2467
UDS1-BD (UDS1 Interface Circuit Pack) Table 872: Test #1214 One-Way Span Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct. Execute add ds1 location to administer the UDS1 interface if it is not already administered. 2.
PAGE 2468
Communication Manager Maintenance-Object Repair Procedures The list measurements ds1 summary command shows the number of bit errors detected (Loopback/Span Test Bit-Error Count field). Injecting this single bit error should increment the bit error count of the loopback/span test by one. Table 873: Test #1215 Inject Single Bit Error Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 2469
UDS1-BD (UDS1 Interface Circuit Pack) Table 873: Test #1215 Inject Single Bit Error Test (continued) Error Code 0 Test Result Description / Recommendation PASS A single bit error has been successfully injected into an active framed 3-in-24 test pattern. NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1.
PAGE 2470
Communication Manager Maintenance-Object Repair Procedures The list measurements ds1 summary command will display the length of time the test ran (Test Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field). To restore the trunks or ports on the UDS1 Interface circuit pack to the in-service state, execute release board location. Table 874: Test #1216 End Loopback/Span Test Error Code Test Result Description / Recommendation ABRT Internal system error 1.
PAGE 2471
UDS1-BD (UDS1 Interface Circuit Pack) Table 874: Test #1216 End Loopback/Span Test (continued) Error Code Test Result Description / Recommendation 2000 ABRT 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. The hyperactive circuit pack is out of service, and one or more of the following symptoms may be exhibited. 1.
PAGE 2472
Communication Manager Maintenance-Object Repair Procedures Table 874: Test #1216 End Loopback/Span Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2473
UDS1-BD (UDS1 Interface Circuit Pack) If the 120A1 CSU module or the 401A T1 sync splitter is not physically installed, the status LEDs are always off and this test aborts. Table 875: Test #1227 ICSU Status LEDs Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1005 ABRT The ICSU Status LEDs test cannot be executed for the current configuration.
PAGE 2474
Communication Manager Maintenance-Object Repair Procedures Table 875: Test #1227 ICSU Status LEDs Test (continued) Error Code Test Result Description / Recommendation 0 NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Verify that the board’s translations are correct.
PAGE 2475
UDS1-BD (UDS1 Interface Circuit Pack) Table 876: Test #1420 Echo Canceller Test Error Code Test Result Description / Recommendation 1015 ABRT The board is not busied out. This test will abort if the UDS1 circuit pack under test is in service. 2000 ABRT 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 2476
Communication Manager Maintenance-Object Repair Procedures Table 876: Test #1420 Echo Canceller Test (continued) Error Code Test Result Description / Recommendation 1400, 1401 FAIL The Echo Cancellation test has failed: ● 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 2477
VAL-BD (Voice Announcements over LAN Circuit Pack) VAL-BD (Voice Announcements over LAN Circuit Pack) S8700 | 8710 / S8500 / G700 MO Name Alarm Level Initial SAT Command to Run Full Name of MO VAL-BD MIN test board location long Voice Announcements over the LAN Circuit Pack VAL-BD WRN test board location short Voice Announcements over the LAN Circuit Pack Voice Announcements over the LAN Circuit Pack The Voice Announcements over the LAN (VAL) board (TN2501AP) provides per-pack announcement stor
PAGE 2478
Communication Manager Maintenance-Object Repair Procedures Configurations Figure 149 shows the configuration options for the TN2501AP (VAL) circuit pack within a system. Figure 149: VAL configuration options 3 1 2 1 7 8 5 4 1 2 6 3 4 5 7 8 9 0 # 6 cydfval LJK 032001 Figure notes: 1. TN2501AP VAL announcement circuit pack 6. Your LAN (See LAN cable on page 2483) 2. System access terminal (SAT) 7.
PAGE 2479
VAL-BD (Voice Announcements over LAN Circuit Pack) Hardware specifications The following table contains a list of the required VAL hardware. Part Number TN2501AP 1 Backplane Adapter (Label reads IP Media Processor) 1 Faceplate LEDs The following figure shows the 9 LEDs on the TN2051AP faceplate. Descriptions of each LED are in Table 877.
PAGE 2480
Communication Manager Maintenance-Object Repair Procedures Figure 150: TN2501AP faceplate LEDs LINK TRMT RCV 100M FDX fpdfval LJK 032101 COL Table 877: TN2501AP LEDs on page 2480 lists the TN2501AP faceplate LEDs, the type of behavior (on, off, flashing, or intermittent), and a description of the condition.
PAGE 2481
VAL-BD (Voice Announcements over LAN Circuit Pack) Table 877: TN2501AP LEDs (continued) LED Behavior Description Amber On solid Firmware is self-downloading to the circuit pack. ! CAUTION: You can lose the resident firmware image file if you reset the circuit pack during firmware download. If this happens, FTP a new firmware image file to the VAL circuit pack and perform the Firmware download procedure again.
PAGE 2482
Communication Manager Maintenance-Object Repair Procedures Other hardware To establish LAN connections the TN2501AP circuit pack requires a ● Backplane Adapter that attaches to the Amphenol connector on the back of the cabinet, corresponding to the TN2501AP integrated announcement circuit pack slot. ● LAN cable on page 2483 that attaches to the Backplane Adapter. Backplane Adapter The following figure shows the Backplane Adapter (label reads IP Media Processor).
PAGE 2483
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.
PAGE 2484
Communication Manager Maintenance-Object Repair Procedures Table 878: VAL maintenance commands (continued) Command Use this command to status data-module Obtain general information about the data-module connection to port 33 on the VAL circuit pack status firmware download Obtain information about a demand or scheduled firmware download. list sys-link Generate a list of administered links and the general status of each.
PAGE 2485
VAL-BD (Voice Announcements over LAN Circuit Pack) Error Log Entries and Test to Clear Values Table 879: VAL Hardware Error Log entries Error Type Aux Data Associated Test Alarm Level On/Off Board 1 (a) 0 Sanity MIN ON 18 (b) 0 WRN OFF 217 (c) 0 None WRN ON 257 65535 Control Channel Loop (#52) MIN ON MIN ON Test to Clear Value release board location test board location l r 20 257 (d) 513 (e) 4352– 4357 769 (f) 4358 1281, 1290– 1295 (g) Any MIN ON 1537, 1796 (h) Any MI
PAGE 2486
Communication Manager Maintenance-Object Repair Procedures Table 879: VAL Hardware Error Log entries (continued) Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 3841, 3843 (s) 3842 (t) Receive FIFO Overflow Error Counter test (#596) 3844 (u) Any 3845 (v) Any 3846 (w) Any 3848 (x) Any 3851 (y) Any 3852 (z) Any 3853 (aa Any 3854 (ab) Any 3855 (ac) Any 3856 (ad) Any 2 of 2 Notes: a.
PAGE 2487
VAL-BD (Voice Announcements over LAN Circuit Pack) e. Error Type 513: circuit pack detected and reported hardware failure. 1. Reset the circuit pack (reset board location). Aux Data: 4352 External RAM error 4353 Internal RAM error 4355 ROM Checksum error 4356 Angel Message Corruption error 4357 Instruction set error f. Error Type 769: logic error. By itself this error can be ignored, but it can result in other Error Types being reported. g.
PAGE 2488
Communication Manager Maintenance-Object Repair Procedures i. Error Type 1794: packet bus transmit buffers have overflowed. 1. Attempt to clear the alarm (reset board location). 2. If the error recurs within 15 minutes, replace the circuit pack. j. Error Type 1798: unable to write translation RAM. 1. Attempt to clear alarm (reset board location). 2. If alarm recurs within 15 minutes, replace the circuit pack. k. Error Type 2049: packet Interface test (#598) failed. 1.
PAGE 2489
VAL-BD (Voice Announcements over LAN Circuit Pack) Note: Note: 2561–2668 is a range of reserved numbers for future applications. 2570 currently represents an SNMP socket failure. n. Error Type 2817–2819: Congestion Query test (#600) failed. The Error Types correspond to the descriptions: 2817 Every buffer exhausted. 2819 Utilized buffers exceed threshold. If: Then: Active buffers exceed threshold, VAL enters congested state. 1.
PAGE 2490
Communication Manager Maintenance-Object Repair Procedures 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 2491
VAL-BD (Voice Announcements over LAN Circuit Pack) s. Error Type 3841, 3843: errors do not affect service. 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). t.
PAGE 2492
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2493
VAL-BD (Voice Announcements over LAN Circuit Pack) Control Channel Loop-Around Test (#52) This nondestructive test fails if the circuit pack does not return to a sane state after being reset. This test queries the circuit pack for its code and vintage, and verifies its records. Table 880: Test #52 Control Channel Loop-Around Test Error Code Test Result Description / Recommendation None, 2100 ABRT Could not allocate the necessary system resources to run test. 1.
PAGE 2494
Communication Manager Maintenance-Object Repair Procedures Circuit Pack Restart Test (#594) 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. The circuit pack resets through the SAKI Sanity test (#53).
PAGE 2495
VAL-BD (Voice Announcements over LAN Circuit Pack) PPE/LANBIC Receive Parity Error Counter Test (#595) This test is nondestructive. 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.
PAGE 2496
Communication Manager Maintenance-Object Repair Procedures Receive FIFO Overflow Error Counter Test (#596) This test is nondestructive. 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 occasional, then they can be due to statistical buffer sizing.
PAGE 2497
VAL-BD (Voice Announcements over LAN Circuit Pack) Invalid LAPD Frame Error Counter Test (#597) This test is nondestructive. 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. This test reads and clears the counter, and verifies the repair of the problem.
PAGE 2498
Communication Manager Maintenance-Object Repair Procedures Table 884: Test #597 Invalid LAPD Frame Error Counter Test (continued) Error Code Test Result Description / Recommendation 1–10 FAIL The circuit pack detects LAPD frame errors. The Error Code indicates the value of the on-board error counter. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the test continues to fail, execute the Packet Interface test (#598) (test board location long). 3.
PAGE 2499
VAL-BD (Voice Announcements over LAN Circuit Pack) Table 885: Test #598 Packet Interface Test (continued) Error Code Test Result Description / Recommendation FAIL Circuit pack has detected a failure of the Packet Interface test (#598). 1. Retry command at 1-minute intervals up to 5 times. 2. If the problem persists, reset the circuit pack (reset board location). 3. If the test continues to fail, replace the circuit pack. PASS The Packet Interface test (#598) passed.
PAGE 2500
Communication Manager Maintenance-Object Repair Procedures Table 886: Test #600 Congestion Query Test (continued) Error Code Test Result Description / Recommendation 2012 ABRT Could not allocate the necessary system resources to run test. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the problem persists, escalate the problem. 2100 ABRT Internal system error. 1. Retry the command at 1-minute intervals up to 5 times. 2. If the problem persists, escalate the problem.
PAGE 2501
VAL-BD (Voice Announcements over LAN Circuit Pack) Link Status Test (#601) This nondestructive 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 2502
Communication Manager Maintenance-Object Repair Procedures Table 887: Test #601 Link Status Test (continued) Error Code Test Result Description / Recommendation 3 FAIL Received no response to RSCL control link test frame. 1. Retry command at 1-minute intervals up to 5 times. 2. If the problem persists, reset the circuit pack (reset board location). 3. If test continues to fail, replace the circuit pack. PASS RSCL control link connected.
PAGE 2503
VAL-PT (Voice Announcements over LAN Packet/Port) VAL-PT (Voice Announcements over LAN Packet/Port) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO VAL-PT MAJ test port location long VAL Port Maintenance VAL-PT MIN test port location long VAL Port Maintenance VAL-PT WRN test port location short VAL Port Maintenance Note: Note: G700: Although the VAL-PT MO can reside in a G700 Media Gateway, neither of the tests described herein execute against
PAGE 2504
Communication Manager Maintenance-Object Repair Procedures VAL Congestion Controls The switch activates congestion controls on VAL when it detects buffers exceeding the threshold. The switch releases the congestion controls when the VAL reports that its buffer level has returned to normal levels.
PAGE 2505
VAL-PT (Voice Announcements over LAN Packet/Port) 2. See SCOTCH Synchronous Loop-Around Test (#1275) on page 2507 repair procedures to verify repair. 3. Clear the alarm (test port location long clear). d. Error Type 3585: TDM Port Loop-Around Test (#1285) failed. 1. Test the port (test port location long). 2. See the TDM Loop-Around Test (#1285) repair procedure. System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below.
PAGE 2506
Communication Manager Maintenance-Object Repair Procedures Test failure indicates failure of one or more of the following components: ● VAL (TN2501) circuit pack ● TDM bus ● Tone generator / tone receiver circuit pack Table 888: Test #1285 TDM Loop-Around Test Error Code Test Result Description / Recommendation 1000 ABRT The port is in use. 1. Retry the command when the port is idle. You can force the port to the idle state with busyout port location. 2. Escalate if the problem persists.
PAGE 2507
VAL-PT (Voice Announcements over LAN Packet/Port) Table 888: Test #1285 TDM Loop-Around Test (continued) Error Code Test Result Description / Recommendation FAIL Received tones do not match transmitted tones. 1. Retry command at 1-minute intervals up to 3 times. 2. If the problem persists, see TDM-BUS (TDM Bus) on page 2237, TONE-PT (Tone Generator) on page 2353, and Tone Receiver repair procedures. 3.
PAGE 2508
Communication Manager Maintenance-Object Repair Procedures Table 889: Test #1275 SCOTCH Synchronous Loop-Around Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT No TDM bus timeslots available for the test. 1. Retry the command at 1-minute intervals up to 5 times. 2. Escalate if the problem persists. G700: 1412 ABRT On the G700, this test aborts with Error Code 1412. 1963 ABRT The port is in use. 1. Retry the command when the port is idle.
PAGE 2509
VC-BD VC-BD S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO VC-BD MAJ test board location l r# Voice Conditioner circuit pack VC-BD MIN test board location l r# Voice Conditioner circuit pack VC-BD WRN1 test board location s r# Voice Conditioner circuit pack 1. See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539. ! CAUTION: CAUTION: If the TN788 Voice Conditioner circuit pack (VC-BD) is not Vintage 2 or later, it must be replaced.
PAGE 2510
Communication Manager Maintenance-Object Repair Procedures Table 890: VC-BD Error Log Entries (continued) Error Type Aux Data 1538 (j) 46082 Associated Test Alarm Level On/Off Board MIN ON Test to Clear Value 2 of 2 Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures. b. Error Type 1: the circuit pack stopped functioning or it was removed from the system.
PAGE 2511
VC-BD f. Error Type 769: the circuit pack detects a program logic error. While no action is required, this error may lead to errors of other types being reported against this circuit pack. g. Error Type 1025: the circuit pack cannot update NPE memory and read it back. This Error Type can be ignored, but it may lead to other Error Types being reported against this circuit pack. h. Error Type 1281: a critical hardware failure has been detected on the circuit pack.
PAGE 2512
Communication Manager Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Code Order of Investigation Control Channel Loop-around test (#52)1 Short Test Sequence Long Test Sequence X X D/ND Nondestructive 1. See repair procedures described in XXX-BD (Common Port Circuit Pack/Media Module) on page 2539. ! CAUTION: CAUTION: If the TN788 Voice Conditioner circuit pack (VC-BD) is not Vintage 2 or later, it must be replaced.
PAGE 2513
VC-DSPPT VC-DSPPT S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO VC-DSPPT MAJ test port location Voice Conditioner DSP Port VC-DSPPT MIN test port location Voice Conditioner DSP Port VC-DSPPT WRN test port location Voice Conditioner DSP Port Each Voice Conditioner circuit pack (VC-BD) provides two types of resources: ● Transcoder Resources used for encoding and decoding audio formats ● Summer Resources used for summing audio from different sources T
PAGE 2514
Communication Manager Maintenance-Object Repair Procedures Notes: a. Error Type 0: run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures. b. Error Type 18: this port has been busied out by busyout port location. c. Error Type 257: the VC DSP Port NPE Crosstalk test (#1103) failed. d. Error Type 513: the VC DSP Port Local TDM Loopback test (#1104) failed. Run the long test sequence. e.
PAGE 2515
VC-DSPPT Table 892: Test #1103 NPE Crosstalk Test Error Code Test Result Description / Recommendation 1000 1001 ABRT 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 ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2100 ABRT Could not allocate the necessary resources for this test. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2516
Communication Manager Maintenance-Object Repair Procedures Figure 152: VC Circuit Pack DSP Port Local TDM Loop-Back Test Table 893: Test #1104 VC DSPPT Local TDM Loop-Back Test Error Code Test Result Description / Recommendation 1000 1001 ABRT 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. 1 of 3 2516 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2517
VC-DSPPT Table 893: Test #1104 VC DSPPT Local TDM Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate time slots for the test. The traffic load on the system is very high, or time slots may be out-of-service due to TDM-BUS errors. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, repeat the test at 1-minute intervals up to 5 times. 1003 ABRT The system could not allocate a Tone Detector for the test.
PAGE 2518
Communication Manager Maintenance-Object Repair Procedures Table 893: Test #1104 VC DSPPT Local TDM Loop-Back Test (continued) Error Code Test Result Description / Recommendation 4–7 FAIL The Conference Circuit test failed. 1. Replace circuit pack. PASS The VC DSP Port Local TDM Loop-Around test passed. 3 of 3 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.
PAGE 2519
VC-DSPPT Figure 153: VC Circuit pack DSP Port DSP Loop-Around Test Table 894: Test #1105 VC-DSP Port DSP Loop-Back Test Error Code Test Result Description / Recommendation 1000 ABRT 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.
PAGE 2520
Communication Manager Maintenance-Object Repair Procedures Table 894: Test #1105 VC-DSP Port DSP Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate time slots for the test, the traffic load on the system is very high, or time slots are out-of-service due to TDM-BUS errors. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command at 1-minute intervals up to 5 times.
PAGE 2521
VC-DSPPT 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. If these self-tests fail, the test will fail; otherwise the test will pass. Before executing the test, the VC-DSPPT must be busied out by executing busyout port location. After the completion of the test, the VC-DSPPT must be released by executing release port location.
PAGE 2522
Communication Manager Maintenance-Object Repair Procedures VC-LEV (Voice Conditioner DSP Port Level) S8700 | 8710 / S8500 MO Name Alarm Level Initial Command to Run Full Name of MO VC-LEV MAJ See Resolving VC-LEV Errors/Alarms VC-LEV The MMCH feature must be enabled on the System-Parameters Customer-Options screen before you can change these fields.
PAGE 2523
VC-LEV (Voice Conditioner DSP Port Level) The VC circuit pack is maintained by the software similarly to the Tone Detector circuit pack. Tone Detector circuit packs may be removed and reinserted in any port-board slot without administration. The same rule applies to VC circuit packs.
PAGE 2524
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 896: VC-LEV Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board 1 (a) Any None MAJ OFF Test to Clear Value Notes: a. Error Type 1: the number of VC resources in the system that are in service has fallen below the calculated minimum value.
PAGE 2525
VC-SUMPT VC-SUMPT S8700 | 8710 / S8500 MO Name Alarm Level Initial SAT Command to Run Full Name of MO VC-SUMPT MAJ test port location Voice Conditioner Summer Port VC-SUMPT MIN test port location Voice Conditioner Summer Port VC-SUMPT WRN test port location Voice Conditioner Summer Port Each Voice Conditioner circuit pack (VC-BD) provides two types of resources: ● Transcoder Resources that are used for encoding and decoding audio formats ● Summer Resources that are used for summing audi
PAGE 2526
Communication Manager Maintenance-Object Repair Procedures d. Error Type 257: the NPE Crosstalk test (#1103) failed. e. Error Type 513: the VC Summer Port Local TDM Loopback test (#1100) failed. System Technician-Demanded Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2527
VC-SUMPT Table 898: Test #6 VC-SUMPT Port NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 0–3 FAIL The NPE of the tested port was transmitting in error. This causes noisy and unreliable connections. 1. Replace circuit pack. PASS The port is correctly using its allocated time slots. 1. Verify that this is not an intermittent problem by repeating this test up to 10 times. 2. If complaints continue, examine the station, connections, and wiring.
PAGE 2528
Communication Manager Maintenance-Object Repair Procedures Figure 154: VC Circuit Pack Summer Port Loop-Back Test Table 899: Test #1100 VC Summer Port Local TDM Loop-Back Test Error Code Test Result Description / Recommendation 1000 ABRT System resources required to run this test are not available, or the port may be busy with a valid call. 1. Retry the command at 1-minute intervals up to 5 times. 1 of 3 2528 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2529
VC-SUMPT Table 899: Test #1100 VC Summer Port Local TDM Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1002 ABRT The system could not allocate time slots for the test. The traffic load on the system is very high, or time slots are out-of-service due to TDM-BUS errors. 1. If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command at 1-minute intervals up to 5 times.
PAGE 2530
Communication Manager Maintenance-Object Repair Procedures Table 899: Test #1100 VC Summer Port Local TDM Loop-Back Test (continued) Error Code Test Result Description / Recommendation 1 FAIL The Conference Circuit test failed. 1. Replace circuit pack. PASS The VC Summer Port Local TDM Loopback test passed. 3 of 3 2530 Maintenance Procedures for Avaya Communication Manager 3.
PAGE 2531
WAE-PORT (Wideband Access Endpoint Port) WAE-PORT (Wideband Access Endpoint Port) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run1 Full Name of MO WAE-PORT MIN test access-endpoint extension l Wideband Access WAE-PORT WRN test access-endpoint extension Endpoint Port 1. For additional repair information, see also DIG-BD (Digital Line Circuit Pack) on page 915 and MG-DS1 (DS1 Interface Media Module) on page 1594.
PAGE 2532
Communication Manager Maintenance-Object Repair Procedures Wideband Access Endpoint interface, and because faults can occur end-to-end, troubleshooting procedures based on an end-to-end view of the network is required. Wideband access endpoint port maintenance provides a strategy to maintain a wideband access endpoint port via a port on the Universal DS1 interface circuit pack or the MM710 DS1 Interface Media Module hardware.
PAGE 2533
WAE-PORT (Wideband Access Endpoint Port) b. Error Type 130: the circuit pack or media module has been removed or has been insane for more than 11 minutes. To clear the error, reinsert or replace the circuit pack or media module. c. Error Type 1281: the Conference Circuit test (#7) failed on this port. See Test #7 for repair procedures. d. Error Type 1537: the NPE Crosstalk test (#6) failed on this port. See Test #6 for repair procedures. e.
PAGE 2534
Communication Manager Maintenance-Object Repair Procedures NPE Crosstalk Test (#6) Note: G700: On the G700, this test aborts with Error Code 1412. Note: The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected time slot, 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 2535
WAE-PORT (Wideband Access Endpoint Port) Table 901: Test #6 NPE Crosstalk Test (continued) Error Code Test Result Description / Recommendation 1004 ABRT The port has been seized by a user for a valid call. Use status access-endpoint extension to determine when the port is available for testing. The port is available when it is in the in-service/idle state. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2536
Communication Manager Maintenance-Object Repair Procedures Table 902: Test #7 Conference Circuit Test Error Code Test Result Description / Recommendation ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABRT System resources required to run this test are not available. The port may be in use on a valid call. Use status access-endpoint extension to determine when the port is available for testing.
PAGE 2537
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 903: Test #36 Port Audit and Update Test Error Code Test Result Description / Recommendation ABRT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 1006 ABRT The port is out-of-service. If the port is busied out: 1.
PAGE 2538
Communication Manager Maintenance-Object Repair Procedures Table 903: Test #36 Port Audit and Update Test (continued) Error Code Test Result Description / Recommendation Any NO BOARD The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. 1. Ensure that the board translations are correct.
PAGE 2539
XXX-BD (Common Port Circuit Pack/Media Module) XXX-BD (Common Port Circuit Pack/Media Module) S8700 | 8710 / S8500 / S8300 MO Name Alarm Level Initial SAT Command to Run Full Name of MO XXX-BD1 MAJ test board location Common Port Circuit Pack/ Media Module maintenance XXX-BD1 MIN test board location Common Port Circuit Pack/ Media Module maintenance XXX-BD1 WRN test board location Common Port Circuit Pack/ Media Module maintenance 1.
PAGE 2540
Communication Manager Maintenance-Object Repair Procedures Table 904: XXX-BD Common Circuit Packs Apparatus Code Name Type CPP1 Memory Expansion Control ED-1E546 (TN2169) (TN2170) (TN566) (TN567) EMBEDDED AUDIX R3 System Port Assembly ED-1E546 (TN2208) (TN2170) Call Visor ASAI over the DEFINITY (LAN) Gateway R1 Port Assembly TN417 Auxiliary Trunk Port TN419B Tone-Clock Control TN420B/C Tone Detector Service TN429 Direct Inward/Outward Dialing (DIOD) Trunk Port TN433 Speech Synthesi
PAGE 2541
XXX-BD (Common Port Circuit Pack/Media Module) Table 904: XXX-BD Common Circuit Packs (continued) Apparatus Code Name Type TN556/B ISDN-BRI 4-Wire S/T-NT Line (A-Law) Port TN722B Digital Signal Level 1 Tie Trunk Port TN725B Speech Synthesizer Service TN726/B Data Line Port TN735 MET Line Port 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
PAGE 2542
Communication Manager Maintenance-Object Repair Procedures Table 904: XXX-BD Common Circuit Packs (continued) Apparatus Code Name Type TN788/B Multimedia Voice Conditioner Service TN789 Radio Controller Control TN793 Analog Line, 24-Port, 2-Wire Port TN797 Analog Trunk and Line Port TN800 Multi-Application Platform for DEFINITY (MAPD) Service TNPRI/BRI PRI-to-BRI Converter Port TN2135 Analog Line Port TN2136 Digital Line 2-Wire DCP Port TN2138 Central Office Trunk Port TN2139
PAGE 2543
XXX-BD (Common Port Circuit Pack/Media Module) Additional circuit packs specific to S8700 MC systems are listed in Table 905: XXX-BD Common Circuit Packs - S8700 MC Specific on page 2543. .
PAGE 2544
Communication Manager Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 907: Common Port Circuit Pack Maintenance Error Log Entries Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value 01 0 Any Any Any test board location sh r 1 1 (a) 0 Circuit pack or Media Module removed or SAKI Sanity (#53) MIN ON 18 (b) 0 busyout board location WRN OFF 23 (c) 0 None WRN OFF 36 (d) 4368 none None MIN ON 125 (e) 217 (f) 0 No
PAGE 2545
XXX-BD (Common Port Circuit Pack/Media Module) b. Error Type 18: the circuit pack or media module has been busied out. Release the circuit pack or media module using release board location. c. Error Type 23: the circuit pack or media module has been logically administered but not physically installed. The alarm should clear when the circuit pact or media module is installed. If the circuit pack or media module is already installed: 1.
PAGE 2546
Communication Manager Maintenance-Object Repair Procedures k. Error Type 1025: this error is not service-affecting and no action is required. l. Error Type 1281: no ringing current is detected. Run Test #51, Ringing Application Test, and follow the procedures for Test #51. G700: On the G700, the associated test for this Error Type aborts with Error Code 1412. m. Error Type 1538: the hyperactive circuit pack or media module is out-of-service and may exhibit one or more of the following symptoms: 1.
PAGE 2547
XXX-BD (Common Port Circuit Pack/Media Module) System Technician-Demand Tests: Descriptions and Error Codes Investigate tests in the order presented below. Clearing Error Codes associated with the one test may also clear errors generated from other tests in the sequence.
PAGE 2548
Communication Manager Maintenance-Object Repair Procedures NPE Audit Test (#50) Note: G700: On the G700/G350, this test aborts with Error Code 1412. Note: 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 909: Test #50 NPE Audit Test Error Code Test Result Description / Recommendation None 2100 ABRT System resources required for this test are not available.
PAGE 2549
XXX-BD (Common Port Circuit Pack/Media Module) Ringing Application Test (#51) This test checks the ringing application circuitry common to every port on an Analog Line circuit pack. Table 910: Test #51 Ringing Application Circuit Test Error Code Test Result Description / Recommendation ABRT Internal system error. Could not allocate the necessary system resources to run test. The circuit pack is not installed. 1000 2100 ABRT Could not allocate the necessary system resources to run test.
PAGE 2550
Communication Manager Maintenance-Object Repair Procedures Table 910: Test #51 Ringing Application Circuit Test (continued) Error Code Test Result Description / Recommendation G700: ABRT G700: On the G700, this test aborts with Error Code 1412. 2000 ABRT There was no response from the board. 1412 1. If Error Type 1538 (hyperactivity) is present in the error log, follow the maintenance strategy that is recommended for this Error Type. 2.
PAGE 2551
XXX-BD (Common Port Circuit Pack/Media Module) Control Channel Loop-Around Test (#52) This test queries the circuit pack or media module for its code and vintage, and verifies its records. Table 911: Test #52 Control Channel Loop-Around Test Error Code Test Result Description / Recommendation None 2100 ABRT System resources required for this test are not available. 1. Retry the command at 1-minute intervals up to 5 times.
PAGE 2552
Communication Manager Maintenance-Object Repair Procedures SAKI Sanity Test (#53) This test is destructive. This test resets the circuit pack or media module. It is executed as part of the long test sequence only for the Tone-Clock circuit pack and DS1 interface circuit packs, and for the MM710 DS1 Interface Media Module. Other common circuit packs and media modules can be reset with the reset board location command which also executes this test.
PAGE 2553
XXX-BD (Common Port Circuit Pack/Media Module) Table 912: Test #53 SAKI Sanity Test (continued) Error Code Test Result Description / Recommendation 2 FAIL The circuit pack or media module failed to restart. 1. Execute command again. 2. If the problem persists, replace the circuit pack or media module. PASS The circuit pack or media module initializes correctly. 1. Run the short test sequence.
PAGE 2554
Communication Manager Maintenance-Object Repair Procedures 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. The neon test runs only for TN746 and TN769 Analog circuit packs and for the MM711 Analog Line Media Module.
PAGE 2555
XXX-BD (Common Port Circuit Pack/Media Module) Table 913: Test #220 Neon Test (continued) Error Code Test Result Description / Recommendation 1018 ABRT There are not any translated ports on the circuit pack, or if there are ports, then none are administered to have "neon." 1. Verify that there are ports administered on the circuit pack. If no ports are administered, no further action is required. 2.
PAGE 2556
Communication Manager Maintenance-Object Repair Procedures Table 913: Test #220 Neon Test (continued) Error Code Test Result Description / Recommendation ABRT Could not allocate the necessary system resources to run this test. Internal system error. 1. If Error Type 1538 is present in the Error Log, follow the recommended maintenance strategy. FAIL The test failed because no neon current was detected. 1.
PAGE 2557
Index Index Symbols _TM, see Translation Manager _WD, see Watchdog Numerical 8-port analog line (ANL-LINE, ANL-NE-L) . . . 404, 425 A abort code 1412 . . . . . . . . . . . . . . . . . ABRI-PORT (ASAI ISDN-BRI Port) MO . . . . . . AC power AC-powered systems . . . . . . . . . . 333, distribution in multicarrier cabinets . . . . . . . . . . . unit . . . . . . . . . . . . . . . . . . . . to UPS . . . . . . . . . . . . . . . . . . . . ACK LED . . . . . . . . . . . . . . . . . . . .
PAGE 2558
Index Analog Media Module . . . . . . . . 328, 1583, 1651 port administration . . . . . . . . . . . . . . 1583 ANL-16-L (16-Port Analog Line) MO . . . . . . . .384 ANL-BD (Analog Line Circuit Pack) MO . . . . . . .403 ANL-LINE (8-Port Analog Line) MO . . . . . . 404, 425 ANL-LN-PT (Analog Line Port) MO . . . . . . . . .426 ANL-NE-L (8-Port Neon Analog Line) MO . . . 404, 425 ANN-BD MO. . . . . . . . . . . . . . . . . . . .447 ANNOUNCE (announce) . . . . . . . . . . . . . .477 ANNOUNCE MO . . . . . . . . . .
PAGE 2559
Index circuit packs, (continued) expansion interface (EI) . . . . LEDs . . . . . . . . . . . green LEDs . . . . . . . . . LEDs . . . . . . . . . . . . maintenance/test, LEDs . . . . TN2182 . . . . . . . . . . . TN2242 . . . . . . . . . . . TN2305 . . . . . . . . . . . TN2306 . . . . . . . . . . . TN464 . . . . . . . . . . . . TN464F . . . . . . . . . . . TN570 . . . . . . . . . . . . TN722 . . . . . . . . . . . . TN767 . . . . . . . . . . . . TN768 . . . . . . . . . . . . TN775 . . . . . . . . . . . .
PAGE 2560
Index Denial Events, (continued) Type Call Processing (1225 - 1899) . . . . . . . .193 Call Processing Events (1001 - 1172) . . . . .177 Call Processing Events (2021- 2299) . . . . .238 Connection Manager Events (2300 - 2399) . . 247 Contact Closure Events (3500 - 3503) . . . .253 Data Error Events (3400 - 3499) . . . . . . .252 Data Manager Events (3001 - 3003) . . . . .249 Dial Access Plan Events (3101 - 3200) . . . .250 Dial Plan Manager Events (2400 - 2406) . . . 249 ESS Events (3600 - 3604) . . . . .
PAGE 2561
Index event log . . . . . . . . event logging, failures . . expansion interface (EI) circuit packs . . . . . fiber links, viability . . TN570 circuit packs . . tone-clock interactions EXP-INTF MO . . . . . . EXP-PN MO . . . . . . . EXT-DEV ADMIN? N MO. EXT-DEV ADMIN? Y MO . EXT-DEV MO . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 2562
Index HTTP Linux daemon (httpd) and SVC_MON Event #8 . . . . . . . . . . . . 87 HYB-BD MO . . . . . . . . . . . . . . . . . . . 1328 HYB-LINE MO . . . . . . . . . . . . . . . . . . 1329 I inaccurate clock and time stamps . . . . . . . . . . 84 INADS . . . . . . . . . . . . . . . . . . . . 29, 32 INADS MO . . . . . . . . . . . . . . . . . . . 1351 incomplete command time-out . . . . . . . . . . .976 inet (internet server) daemon and SVC_MON Event #3 . . . . . . . . . . . . 82 initialization E1/T1 LEDs . .
PAGE 2563
Index LEDs, (continued) standard DEFINITY server LEDs . . . . . . . .288 states . . . . . . . . . . . . . . . . . . . . .294 testing server LEDs . . . . . . . . . . . . . . . . .280 Tone-Clock circuit packs . . . . . . . . . . . .266 UPS . . . . . . . . . . . . . . . . . . . . . .269 LGATE-AJ MO . . . . . . . . . . . . . . . . . 1476 LGATE-BD MO . . . . . . . . . . . . . . . . . 1477 LGATE-PT MO . . . . . . . . . . . . . . . . . 1478 license files LIC-ERR (License-Error Mode) MO . . . . . .
PAGE 2564
Index maintenance objects . . . . . . . . . . . . . . . . 27 abort code 1412 . . . . . . . . . . . . . . . .331 Analog Media Module . . . . . . . . . . 328, 1583 BRI Trunk Media Module . . . . . . . . . . . .328 Communication Manager . . . . . . . . . . . .325 DCP Media Module . . . . . . . . . . . . . . .328 Digital Line Media Module . . . . . . . . . . . 1593 DS1 Interface Media Module . . . . . . . . . 1594 G700 media gateway . . . . . . . . . . . . . .327 groupings by Media Module type. . . . . . . . .
PAGE 2565
Index MG-ANN MO . . . . . . . MG-BRI . . . . . . . . . . MG-BRI MO . . . . . . . . MG-DCP . . . . . . . . . MG-DCP MO . . . . . . . MG-DS1 . . . . . . . . . MG-DS1 MO . . . . . . . MG-IAMM MO . . . . . . . MG-ICC . . . . . . . . . . MG-ICC MO . . . . . . . . MG-VOIP . . . . . . . . . MG-VOIP MO . . . . . . . minor alarms . . . . . . . MIS MO . . . . . . . . . . MM710 . . . . . . . . . . MM711 . . . . . . . . . . MM712 . . . . . . . . . . MM720 . . . . . . . . . . MM760 . . . . . . . . . . MMI-BD MO . . . .
PAGE 2566
Index MOs (maintenance objects), (continued) DTMR-PT . . . . . . . . . . . . . E-DIG-BD . . . . . . . . . . . . . E-DIG-RES. . . . . . . . . . . . . E-DIG-STA . . . . . . . . . . . . . E-MAINT . . . . . . . . . . . . . . EMG-XFER . . . . . . . . . . . . EPN-SNTY . . . . . . . . . . . . . ERR-LOG . . . . . . . . . . . . . ESS . . . . . . . . . . . . . . . . ETH-PT . . . . . . . . . . . . . . ETR-PT . . . . . . . . . . . . . . EXP-INTF . . . . . . . . . . . . . EXP-PN . . . . . . . . . . . . . . EXT-DEV . .
PAGE 2567
Index MOs (maintenance objects), (continued) TDM-CLK . . . . . . . . . . . . . TDMODULE . . . . . . . . . . . . TIE-BD . . . . . . . . . . . . . . . TIE-DS1 . . . . . . . . . . . . . . TIE-TRK . . . . . . . . . . . . . . TIME-DAY . . . . . . . . . . . . . TONE-BD . . . . . . . . . . . . . TONE-PT . . . . . . . . . . . . . TR-LN-BD . . . . . . . . . . . . . TSC-ADM . . . . . . . . . . . . . TTR-LEV . . . . . . . . . . . . . . UDS1-BD . . . . . . . . . . . . . VAL-BD . . . . . . . . . . . . . . VAL-PT . . .
PAGE 2568
Index R R2-MFC signaling . . . . . . . . . . . . . . . RALM-SVC MO . . . . . . . . . . . . . . . . RAM errors multibit . . . . . . . . . . . . . . . . . . . single-bit . . . . . . . . . . . . . . . . . . RANL-STA MO . . . . . . . . . . . . . . . . RDIG-STA MO . . . . . . . . . . . . . . . . reboots hard reboot . . . . . . . . . . . . . . . . . red ALM LED . . . . . . . . . . . . . . . . . relay, DC power . . . . . . . . . . . . . . . . REM-OFF MO . . . . . . . . . . . . . . . . .
PAGE 2569
Index single-carrier cabinets environment (DC-POWER) . . . . . . . . . . .880 power system . . . . . . . . . . . . . . . . .333 SME alarm, in media server . . . . . . . . . . . . 78 SNC-BD MO. . . . . . . . . . . . . . . . . . . 2000 SNC-LINK MO . . . . . . . . . . . . . . . . . . 2039 SNC-REF MO . . . . . . . . . . . . . . . . . . 2043 snd2Inads string, in trace log . . . . . . . . . . . . 78 SNI circuit pack (SNI-BD) . . . . . . . . . . . . . 2046 LEDs . . . . . . . . . . . . . . . . . . . . .
PAGE 2570
Index tests and audits, (continued) #135 Customer-Provided Alarming Device Test . 1507 #135 Internal Loop Around Test . . . . . 994, 2404 #136 DS1 Tie Trunk Seizure Test . . . . . . . 2286 #1371 IP Address Query Test . . . . . . . . . 1546 #1373 Signaling Path PING Test . . . . . . . . 1326 #1379 Ping Test . . . . . . . . 1366, 1391, 1547 #138 Loss of Signal Alarm Inquiry Test996, 997, 2409 #1380 TDM NIC Loop-Around Test . . . . . . 1557 #1381 NT Reset Test . . . . . . . . . . . . .
PAGE 2571
Index tests and audits, (continued) #43 Tone Detector Audit/Update Test815, 1119, 1173, 1312 #46 Clock Health Inquiry Test . . . . . . . . . 2351 #47 Loop Around and Conference Test . . . . .417 #48 Station Present Test . . . . . .397, 422, 1924 #5 Battery & Battery Charger Query Test .1873, 1880 #50 NPE Audit Test . . . . . . . . . . . . . . 2548 #50 NPE Connection Audit Test . . 989, 1530, 2399 #50 NPE/NCE Audit Test . . . . . . . . . . . 1646 #51 Ringing Application Circuit Test . . . . . .
PAGE 2572
Index threads, see Linux, threads tickling, of server’s hardware sanity timer . . . . . . 114 tie trunk circuit pack (TIE-BD) . . . . . . . . . . . 2269 TIE-BD MO . . . . . . . . . . . . . . . . . . . 2269 TIE-DS1 MO. . . . . . . . . . . . . . . . . . . 2270 TIE-TRK MO . . . . . . . . . . . . . . . . . . 2302 time stamps, inaccurate . . . . . . . . . . . . . . 84 TIME-DAY MO . . . . . . . . . . . . . . . . . 2326 time-division multiplex (TDM) . . . . . . . . . . .
PAGE 2573
Index trunk data module (TDMODULE) . trunking ATM . . . . . . . . . . . . trunks administration . . . . . . . DS1 . . . . . . . . . . . . TIE-DS1 . . . . . . . . . . UDS1 . . . . . . . . . . . trunks, DS1 . . . . . . . . . . TSC-ADM MO . . . . . . . . . TTC private networking (Japan) . TTR-LEV MO . . . . . . . . . . . . . . . . . . 2268 . . . . . . . . . .598 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .817 . . . . 1594 . . . . 1508 . . . . 2374 .
PAGE 2574
Index 2574 Maintenance Procedures for Avaya Communication Manager 3.