Page 1 0DLQWHQDQFH IRU $YD\D '(),1,7< 6HUYHU 6, Š Volumes 1, 2, and 3 555-233-123 Issue 4 May 2002...
Page 2 How to Get Help These compromises may become more acute if you fail to follow For additional support telephone numbers, go to the Avaya Web site: Avaya's recommendations for configuration, operation and use of the http://www.avaya.com/support/ equipment.
Page 3 Technical Service Center at 1-800-242- sion signaling is in violation of Part 68 rules. This equipment returns 2121 or contact your local Avaya representative. If the equipment is answer-supervision signals to the public switched network when: causing harm to the telephone network, the telephone company may •...
Page 4 Haverhill, MA 01835 USA but many have been registered with the FCC before the SDoC process Attention: Avaya Account Management was available. A list of all Avaya registered products may be found at: E-mail: totalware@gwsmail.com http://www.part68.org/ by conducting a search using “Avaya” as manufacturer.
Page 5: Table Of Contents
Contents Volume One About this Book xxvii General xxvii Conventions Used in This Document xxviii Organization xxix Safety Precautions Class 1 Laser Device xxxi Security Issues xxxi Standards Compliance xxxii Electromagnetic Compatibility Standards xxxiii Trademarks and Service Marks xxxiv How to Order Documentation xxxv How to Comment on This Document xxxv...
Page 6 Contents Circuit Packs and Power Circuit Packs Power Management Terminals General Management Terminals System Login Procedure Password Aging Administrable Logins System Logoff Procedure 3-21 Switch-Based Bulletin Board 3-22 DEC VT220 Terminal 3-25 Initialization and Recovery Reset commands Procedure for SPE-Down Mode Procedure for Duplication Interface —...
Page 7 Contents Preventive Maintenance Procedures 5-24 System Features 5-25 Troubleshooting Backplane Voltage Problems 5-50 Multimedia Call Handling (MMCH) 5-51 Install DS1 CPE Loopback Jack (T1 Only) 5-58 ATM Tips 5-71 Unusual ATM trouble conditions 5-97 Reliability Systems: A Maintenance Aid General Reliability Options Duplicated Hardware Duplication Concepts...
Page 8 Contents Maintenance Commands and Trouble-Clearing Aids busyout access-endpoint busyout board busyout cdr-link busyout data-module busyout journal-printer busyout link busyout mis 8-10 busyout modem-pool 8-11 busyout packet-control 8-12 busyout pms-link 8-13 busyout port 8-15 busyout pri-endpoint 8-16 busyout sp-link 8-17 busyout spe-standby 8-18 busyout station 8-19...
Page 9 Contents disable administered-connection 8-50 disable filesystem board ppcss 8-50 disable firmware download 8-51 disable mst 8-51 disable suspend-alm-orig 8-51 disable synchronization-switch 8-52 disable test-number 8-52 display alarms 8-53 display cabinet 8-58 display capacity 8-60 display communication-interface 8-70 display communication-interface hop-channels 8-71 display communication-interface links 8-72...
Page 10 Contents get boot-image 8-134 get ethernet options 8-135 get vector 8-136 list configuration 8-139 list configuration license 8-143 list config software-version 8-144 list directory 8-148 list disabled-mos 8-149 list history 8-150 list ip-route 8-152 list isdn-testcall 8-154 list marked-ports 8-155 list measurements clan ethernet 8-156 list measurements clan ppp...
Page 11 Contents ping 8-243 recycle carrier 8-247 refresh route-table 8-248 refresh spe-standby 8-250 release access-endpoint 8-251 release board 8-252 release cdr-link 8-253 release data-module 8-254 release journal-printer 8-255 release link 8-256 release mis 8-257 release modem-pool 8-258 release packet-control 8-259 release pms-link 8-260 release port 8-261...
Page 12 Contents save announcements 8-280 save translation 8-283 set boot-image 8-284 set ethernet-options 8-285 set expansion-link 8-286 set options 8-286 set signaling-group 8-292 set synchronization 8-293 set tdm 8-294 set time 8-295 set tone-clock 8-296 set vector 8-297 status access-endpoint 8-299 status administered-connection 8-301 status attendant...
Page 13 Contents status pri-endpoint 8-379 status processor-channel 8-380 status psa 8-382 status signaling-group 8-382 status sp-link 8-384 status station 8-385 status synchronization 8-390 status system 8-392 status trunk 8-400 status tsc-administered 8-406 status tti 8-408 status val-ip 8-410 test access-endpoint 8-411 test alarms 8-412 test analog-testcall...
Page 14 Contents test modem-pool 8-461 test network-control 8-463 test packet-control 8-465 test pkt 8-467 test pms-link 8-469 test port 8-471 test pri-endpoint 8-473 test processor 8-475 test shadow-link 8-477 test signaling-group 8-479 test sp-link 8-481 test spe-standby 8-483 test station 8-485 test synchronization 8-487 test tdm...
Page 15 Contents Volume Two Maintenance Object Repair Procedures 10-1 Escalation Procedures 10-1 Cabling Precautions 10-2 ABRI-PORT (ASAI ISDN-BRI Port) 10-2 AC-POWER 10-3 ADM-CONN (Administered Connection) 10-11 ADX8D-BD (AUDIX Circuit Pack) 10-15 ADX8D-PT (AUDIX Digital Port) 10-16 ADX16D-B (16 Port AUDIX Circuit Pack) 10-24 ADX16A-BD (AUDIX Circuit Pack) 10-24...
Page 16 Contents ATM-TRK (Circuit Emulation Service Circuit Pack) 10-227 AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX Circuit Packs) 10-257 AXA12-RS/ADX8D-RS/AXD12-RS (AUDIX Reserve Slots) 10-258 BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) 10-259 BRI-DAT (ISDN-BRI) 10-266 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) 10-267 BRI-SET, ASAI-ADJ, BRI-DAT 10-292 CABINET (Cabinet Sensors) 10-323 CAP-MEM (Memory Card Capacity) 10-338...
Page 17 Contents DIG-IP-STN (Digital IP Station) 10-551 DIG-LINE (Digital Line) 10-558 DIOD-DS1 (DS1 DIOD Trunk) 10-584 DIOD-TRK (DIOD Trunk), DIOD-BD (DIOD Circuit Pack) [G1.2SE] 10-596 DIOD-TRK (DIOD Trunk) [G1.2SE] 10-596 DLY-MTCE (MO-DAILY) 10-608 DS1-BD (DS1 Interface Circuit Pack) 10-611 DT-LN-BD (Data Line Circuit Pack) 10-695 DTMR-PT [Dual Tone Multifrequency Port (TTR)] 10-696...
Page 18 Contents ISDN-LNK (ISDN-PRI Signaling Link Port) 10-934 ISDN-PLK (ISDN-PRI Signaling Link Port) 10-941 ISDN-SGR (ISDN-PRI Signaling Group) 10-949 ISDN-TRK (DS1 ISDN Trunk) 10-977 Volume Three JNL-PRNT (Journal Printer Link) 10-1005 LGATE-AJ 10-1006 LGATE-BD 10-1006 LGATE-PT 10-1006 LIC-ERR (License-Error Mode) 10-1007 LOG-SVN (Login Security Violation) 10-1015 MAINT (EPN Maintenance Circuit Pack)
Page 19 Contents PE-BCHL (PRI Endpoint Port) 10-1202 PI-BD (Processor Interface Circuit Pack) 10-1223 PI-LINK (Processor Interface Link) 10-1230 PI-PT (Processor Interface Port) 10-1248 PI-SCI (System Communication Interface) 10-1253 PKT-BUS (Packet Bus) 10-1261 PKT-CTRL (Packet Control Circuit Pack) 10-1273 PKT-INT (Packet Interface) 10-1290 PMS-LINK (Property Management System Link) 10-1323...
Page 20 Contents STBY-SPE (Standby SPE) 10-1517 STRAT-3 (Stratum 3 Clock) 10-1557 SVC-SLOT (Service Slot) 10-1569 SW-CTL (Switch Control) 10-1571 SYNC (Synchronization) 10-1586 SYS-LINK (System Links) 10-1598 SYS-PRNT (System Printer) 10-1603 SYSTEM (System) 10-1609 TAPE (Tape Unit) [G3iV1.1-286] 10-1611 TAPE-DAT (Tape Consistency) 10-1641 TBRI-BD (TN2185 ISDN Trunk-Side BRI)
Page 21 Contents VC-DSPPT 10-1974 VC-LEV (Voice Conditioner DSP Port Level) 10-1984 VC-SUMPT 10-1987 WAE-PORT (Wideband Access Endpoint Port) 10-1993 XXX-BD (Common Port Circuit Pack) 10-2001 Error Messages from Chapter 8: Maintenance Commands busyout access-endpoint busyout board busyout cdr-link busyout data-module busyout journal-printer busyout link busyout mis busyout modem-pool...
Page 22 Contents clear interface A-29 clear isdn-testcall A-30 clear link A-31 clear mst A-32 clear pkt A-32 clear port A-32 copy update-file A-33 disable administered-connection A-34 disable mst A-35 disable suspend-alm-orig A-35 disable synchronization-switch A-35 disable test-number A-36 display alarms A-37 display errors A-39 display initcauses...
Page 23 Contents mark port A-55 monitor bcms A-56 monitor health A-57 monitor system A-57 monitor traffic A-58 monitor trunk A-58 recycle carrier A-59 refresh spe-standby A-60 release access-endpoint A-60 release board A-61 release cdr-link A-62 release data-module A-63 release journal-printer A-64 release link A-65 release mis...
Page 24 Contents set expansion-link A-84 set options A-85 set signaling-group A-86 set synchronization A-87 set tdm A-88 set time A-89 set tone-clock A-90 set vector A-91 status access-endpoint A-92 status administered-connection A-93 status attendant A-94 status audits A-95 status bri-port A-95 status card-mem A-96 status cdr-link...
Page 25 Contents status trunk A-109 status tsc-administered A-110 status tti A-111 test access-endpoint A-112 test alarms A-113 test analog-testcall A-115 test board A-117 test card-mem A-118 test cdr-link A-119 test customer-alarm A-120 test data-module A-120 test ds1-loop A-121 test duplication-interface A-123 test environment A-124 test hardware-group...
Page 26 Contents test station A-145 test synchronization A-146 test tdm A-147 test tone-clock A-148 test trunk A-149 test tsc-administered A-150 traceroute A-151 upgrade software A-153 Index IN-1 xxvi Issue 4 May 2002 555-233-123...
Page 27: About This Book
About this Book General This book has the information needed to monitor, test, and maintain the Avaya software running on Avaya DEFINITY ® Server SI, and covers ™ MultiVantage many of the faults and troubles that can occur in the system. Most maintenance requirements are simple procedures due to the modular, self-testing nature of the system.
Page 28: Conventions Used In This Document
About this Book Each DEFINITY Server has a customer system manager who is responsible for administration of the system. The maintenance technician should work closely with the system manager. This book is not intended to solve all levels of troubles. It is limited to troubles that can be solved by using the Alarm Log, Error Log, trouble-clearing procedures, maintenance tests, and traditional troubleshooting methods.
Page 29: Organization
Organization Admonishments used in this book are as follows: CAUTION: This sign is used to indicate possible harm to software, possible loss of data, or possible service interruptions. WARNING: This sign is used where there is possible harm to hardware or equipment.
Page 30: Safety Precautions
Time Division Multiplex (TDM) Bus. Avaya listens carefully to its readers. The organization of this book is a direct result of user feedback. Your feedback is important. Use the feedback form at the back of this book to send your comments to Avaya.
Page 31: Class 1 Laser Device
Class 1 Laser Device The Avaya DEFINITY Server SI contains a Class 1 Laser device if single-mode fiber optic cable is connected to a remote Expansion Port Network (EPN). The LASER device operates within the following parameters:...
Page 32: Standards Compliance
About this Book Standards Compliance The equipment presented in this document complies with the following (as appropriate): ITU-T (Formerly CCITT) ECMA ETSI IPNS DPNSS National ISDN-1 National ISDN-2 ISO-9000 ANSI FCC Part 15 and Part 68 EN55022 EN50081 EN50082 CISPR22 Australia AS3548 (AS/NZ3548) Australia AS3260 IEC 825...
Page 33: Electromagnetic Compatibility Standards
Radiated radio frequency field immunity requirements IEC 1000-4-3 Electrical fast transient/burst immunity requirements IEC 1000-4-4 European Union Standards Avaya Business Communications Systems declares that the Avaya DEFINITY Server equipment specified in this document bearing the “CE” mark conforms to the European Union Electromagnetic Compatibility Directives.
Page 34: Trademarks And Service Marks
AC powered Single-Carrier Cabinet (SCC) with 25-Hz ring generator AC powered Compact Single-Carrier Cabinet (CSCC) with 25-Hz ring generator Enhanced DC Power System Trademarks and Service Marks The following are trademarks or registered trademarks of Avaya, Inc.: AUDIX® Cajun® CallVisor® Callmaster®...
Page 35: How To Order Documentation
In addition to this book, other description, installation and test, maintenance, and administration books are available. This document and any other Avaya documentation can be ordered directly from the Avaya Publications Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax). International customers should use +1.410.568.3680 (voice) and +1.410.891.0207 (fax).
Page 36: Where To Call For Technical Support
Canada 1-800-387-4268 Technical Service Center (INADS Database 1-800-248-1111 Administration) DEFINITY Helpline 1-800-225-7585 Avaya Toll Fraud Intervention 1-800-643-2353 Avaya Technical Service Center (maintenance/repair) 1-800-242-2121 Avaya Corporate Security 1-800-822-9009 1-925-224-3401 North America 1-800-248-1111 Central/Latin America, Caribbean (dealers only) Contact your local representative...
Page 37: Maintenance Architecture
Maintenance Architecture The maintenance subsystem is a part of the software that initializes and maintains the system. The software continuously monitors system health, and keeps a record of errors detected in the system. The maintenance subsystem also provides a user interface for on-demand testing. This chapter provides a brief description of the maintenance strategy and the background information on the system’s overall functions.
Page 38 Maintenance Architecture Table 1-1. Alarm levels, reporting conditions and action to take Reported Reported Alarm level Description INADS? console? What action to take? MAJOR Critical service Yes, after 4 Immediate attention degradation attempts to call INADS MINOR Some service Same as Check to see what service degradation but does not above...
Page 39 How to use the Maintenance book a. The report can be restricted by typing either y (yes) or n (no) in these fields (shown above in bold): Active Major Minor Warning CAUTION: If you choose n for major alarms and y for minor and warning alarms, you will not see the macro-level information that you may need to determine what is wrong with the system.
Page 40 Maintenance Architecture 7. Find the DID-TRK MO in the Maintenance Object chapter of the appropriate maintenance book. 8. In the first table look up the initial command to run in the MAJOR row of the table (Step 4 indicated that a DID trunk in slot 10, carrier C has a MAJOR alarm).
Page 41 How to use the Maintenance book 14. Look in Table 1-3 for Test #35, then “61472” in the Error Code column, and “FAIL” in the Test Result column. See the Description/Recommendation information. Table 1-3. TEST #35 Port Diagnostic Test Error Test Code Result...
Page 42: Maintenance Objects
Maintenance Architecture mbus memory misc mnt-test modem mssnet pms/jrnl pncmaint pnc-peer procr quick-st s-syn stabd stacrk stations sys-link sys-prnt tape tone trkbd trkcrk trunks wideband wireless Enter assigned extension, or blank Extension Trunk Enter group number between 1-666 Group Enter group member between 1-255, or blank Member Maintenance Objects The system is partitioned into separate entities called Maintenance Objects...
Page 43: Alarm And Error Reporting
Alarm and Error Reporting Alarm and Error Reporting During normal operations, software or firmware may detect error conditions relevant to specific MOs. The system attempts to fix or circumvent these problems automatically. However, if a hardware component incurs too many errors, an alarm is raised.
Page 44: Maintenance Testing
Maintenance Architecture Maintenance Testing Most troubles are reduced to the circuit pack level and can be identified by LEDs on the circuit packs and software reports generated by the system. The maintenance tests in the system are divided into three groups: Periodic Background tests are performed by software maintenance, usually on an hourly basis.
Page 45: Protocols
Protocols Protocols This section describes the protocols handled by the system and the points where these protocols change. Figure 1-1 on page 1-10 is a pictorial guide through data- transmission state changes. Figure 1-1 illustrates the flow of data from DTE equipment, like a terminal or host, through DCE equipment, like a modem or data module, into a communications port on the system.
Page 46 Maintenance Architecture ORIGINATING SYSTEM DESTINATION DATA DATA MODULE MODULE DATA DATA MODULE MODULE RS232C RAW BITS RS232C ASCII ASCII USER DEFINED MODEM MODEM POOLING CABLE MODEM MODEM RS232C ANALOG ANALOG RS232C ASCII VOICE GRADE DATA ASCII USER DEFINED RS232C ADU PROT RAW BITS ADU PROT RS232C...
Page 47 Protocols Usage The following is a list of the protocols when data is transmitted to and through the system. The list is organized by protocol layers. Refer to Figure 1-1 on page 1-10. Layer-1 Protocols Layer-1 protocols are used between the terminal or host DTE and the DCE, used between the DCE equipment and the system port, and used inside the system.
Page 48 Maintenance Architecture — Analog A modulated voice-frequency carrier signal — ADU Proprietary A signal generated by an ADU. The signal is for communication over limited distances and can be understood only by a destination ADU or destination system port with a built-in ADU —...
Page 49 Protocols Protocol States Table 1-4 summarizes the protocols used at various points in the data transmission stream. See Figure 1-1 on page 1-10. Table 1-4. Protocol States for Data Communication Incoming Transmis- DTE to Protocols DTE to DCE to System sion Type Layer Port...
Page 50 Maintenance Architecture Table 1-6. Digital Multiplexed Interface (DMI) Mode Versus Character Code DMI Mode Code Synchronous (64 kbps) Synchronous (56 kbps) Asynchronous 8-bit ASCII (up to 19.2 kbps), and synchronous Asynchronous 8-bit ASCII, and private proprietary Connectivity Rules Figure 1-1 on page 1-10 implies the following connectivity rules: Only the DS1 port and the analog trunk port are trunking facilities (all other ports are line ports).
Page 51 Protocols Data cannot be carried over analog facilities unless inside the system it is represented as a Pulse Code Modulation (PCM)-encoded analog signal. To do this for data originating at a digital terminal, the signal enters the system at a digital port and exits the system at a digital port. The signal then reenters the system through a modem-pool connection (data-module to modem to analog-port) and exits the system again at an analog port.
Page 52 Maintenance Architecture Transfer on Ringing A station or attendant may conference in a ringing station or transfer a party to a ringing station. When a station conferences in a ringing station and then drops the call, the ringing station is treated like a party without disconnect supervision. However, when a station transfers a party to a ringing station, the ringing station party is treated like a party with disconnect supervision.
Page 53 Protocols Table 1-7. Protocols Used in DEFINITY Maximum Protocol Applications Data Rate Maximum Distance Digital switch to data 64 kbps 5000 feet (1524 m) for data endpoints 3000 feet (915 m) for voice RS-232 System to administration 19.2 kbps 50 feet (15.2 m) terminal.
Page 54 Maintenance Architecture Table 1-7. Protocols Used in DEFINITY — Continued Maximum Protocol Applications Data Rate Maximum Distance Category Data modules to terminals 64 kbps 500 feet (152 m) or cluster controller Data module in ASCII 9.6 kbps emulation mode ISDN-BRI Communication interface 64 kbps 655 feet (199.3 m) to network...
Page 55 Protocols Frequency Response Table 1-8 lists the analog-to-analog frequency response for station-to-station or station-to-CO trunk, relative to loss at 1 kHz for the United States. Table 1-8. Analog-to-Analog Frequency Response Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB) — 300 to -0.5 3000 3200...
Page 56 Maintenance Architecture Insertion Loss for Port-to-Port; Analog or Digital Table 1-10 lists the insertion loss in the system for different connection types for the United States. Table 1-11 shows the overload and cross-talk characteristics. NOTE: The following numbers apply only to DCP or BRI station types. They do not apply to IP stations.
Page 57 Protocols Intermodulation Distortion Table 1-12 lists the intermodulation distortion in the system for analog-to-analog and analog-to-digital, up to 9.6 kbps data NOTE: The following numbers apply only to DCP or BRI station types. They do not apply to IP stations. Table 1-12.
Page 58 Maintenance Architecture Table 1-14 lists the quantization distortion loss in the system for analog port to digital port and digital port to analog port. Table 1-14. Quantization Distortion Loss Analog Port-to-Digital Port or Digital Port-to-Analog Port Signal Level Distortion Loss 0 to -30 dBm0 >35 dB -40 dBm0...
Page 59: Service Codes
Service Codes Peak Noise Level DCP or BRI phones only decibels above reference noise with C-filter) Analog to analog 20 dBrnC Analog to digital 19 dBrnC Digital to analog 13 dBrnC Echo Path Delay DCP or BRI phones only < Analog port to analog port 3 ms Digital interface port to digital interface port...
Page 60: Facility Interface Codes
Maintenance Architecture Facility Interface Codes A Facility Interface Code (FIC) is a five-character code (United States only) that provides the technical information needed to order a specific port circuit pack for analog private lines, digital lines, MTS lines, and WATS lines. Table 1-15 through Table 1-17 on page 1-25...
Page 61: Multimedia Interface (Mmi)
Multimedia Interface (MMI) Table 1-17. MTS and WATS Port Circuit Packs Ringer Equivalency Network Circuit Pack Number (REN) Jack TN742 and TN746B Analog Line 02LS2 None RJ21 and RJ11C TN747B Central Office Trunk 02GS2 1.0A RJ21X TN753 DID Trunk 02RV2-T 0,0B RJ21X TN2404/TN790 Processor...
Page 62 Maintenance Architecture 1-26 Issue 4 May 2002 555-233-123...
Page 63: Circuit Packs And Power
This chapter also discusses the power sources required to enable the various components within the system. Circuit Packs For circuit pack information, please see the Avaya MultiVantage Hardware Solutions Guide. 555-233-123 Issue 4 May 2002...
Page 64: Power
Circuit Packs and Power Power There are two basic powering options available with the DEFINITY Server SI. These options include AC and DC. The cabinets and their associated power supplies can be powered by 120/208 volts AC either directly or from a Universal Power Supply (UPS) system.
Page 65 Power Table 2-2. Response to Power Service Interruption with an Internal Holdover Battery Holdover for Holdover for Entire System and Entire Cabinet Control Carrier (in Configuration Cabinet (in seconds) minutes) Standard PPNMCC High, Critical PPNMCC Standard/High, Critical PPN SCC/ESCC Standard/High, Critical EPN MCC none Standard/High, Critical...
Page 66 Circuit Packs and Power The SPE control cabinet has a battery that furnishes power to the processor memory complex for a minimum of two minutes if the battery is fully charged. This battery is recharged after power is restored, but the charging process is not monitored by the system.
Page 67: Management Terminals
Management Terminals General Maintenance personnel can use the management terminal to initiate the same tests that the system initiates. Test results appear on the terminal screen. This chapter illustrates management terminals, explains how to use them, and identifies the typical maintenance tasks that can be performed from them. This chapter discusses the following topics: ‘‘Management Terminals’’...
Page 68 Management Terminals In a standard reliability system, the terminal connects to the Processor circuit pack. In the PPN of a high or critical reliability system, the administration terminal connects to the Duplication Interface circuit pack in the PPN. In the EPN of a standard reliability system or of a high or critical reliability system, the administration terminal connects to the Maintenance circuit pack in the EPN.
Page 69: System Login Procedure
System Login Procedure Editing Keys: Two editing keys, , are provided. BACKSPACE Clear BACKSPACE used to erase the character at the current cursor position. The cursor moves one position to the left each time the key is pressed. If the cursor is at the first position of the data entry field, it erases the character at the first position.
Page 70 Management Terminals 5. Set INADS alarm origination if you logged in as craft. Unless you are in a special situation, enter y to suppress Alarm Origination and reduce trouble tickets. The test inads-link command works regardless of the INADS Alarm Origination setting. Enter n to allow alarm origination.
Page 71 Specific screen forms exist for each type of administrable function. Administrator’s Guide for Avaya MultiVantage Software contains detailed information and examples of the screen forms generated by the system.
Page 72: Password Aging
Management Terminals To Remove a Login 1. Type remove login [login name] and press Enter The Login Administration screen appears. 2. Press the key to remove the login, or press Cancel to exit the ENTER remove login procedure without making a change. Testing a Login 1.
Page 73: Administrable Logins
Administrable Logins Administrable Logins The system is delivered to the customer with one customer “super-user” login/password defined. The customer then administers additional customer login/passwords as needed. The super-user login has full customer permissions and can customize any customer login that he/she creates. Adding Customer Logins and Assigning Initial Password The system provides enhanced login/password security by adding a security...
Page 74 Management Terminals 5. Enter y in the Disable Following a Security Violation field to disable a login following a login security threshold violation. Default is y. This field appears when SVN Login Violation Notification is enabled. 6. Enter y in the Access to INADS Port field to allow access to the remote administration port.
Page 75 Administrable Logins 13. Decide whether or not to leave y in the Remote Access Acknowledgment Required field. If y, the user is required to acknowledge that they wish to logoff while remote access is still administered. If you do not want to force the user to acknowledge, set the field to n.
Page 76 Management Terminals 6. To allow access to the remote administration port, enter y in the Access to INADS Port field. This field appears when customer super-user access to the INADS Remote Administration port is enabled. 7. Enter a password for the new login in the Login’s Password field. A password must be from 4 to 11 characters in length and contain at least 1 alphabetic and 1 numeric symbol.
Page 77 Administrable Logins Command Permissions screen Entries — Display Administration and Maintenance for a list of command objects and actions. Use the information in the tables to help to establish command permissions for user logins. To administer command permissions, log in as super-user and: 1.
Page 78 Management Terminals Page 2 of 3 COMMAND PERMISSION CATEGORIES RESTRICTED OBJECT LIST _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ Screen 3-5. Command Permissions Categories (Page 2 of 3) Page 3 of 3 COMMAND PERMISSION CATEGORIES RESTRICTED OBJECT LIST...
Page 79 Administrable Logins Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test aca-parameters access-endpoint adjunct-names adjunct-controlled-agents administered-connection agent-loginID alarms alias-station alphanumeric-dial-table alternate-frl analog -testcall announcements ars analysis ars analysis ars digit-conversion ars digit-conversion ars route-chosen...
Page 80 Management Terminals Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test cleared-alarm-notif communication-interface hop-channels communication-interface links communication-interface proc-channels configuration all configuration board configuration carrier configuration control configuration network configuration software configuration station configuration trunk...
Page 81 Administrable Logins Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test enp-number-plan environment errors events external-device-alarm extension-type external-device-alarming feature-access-code fiber-link (MIPS Only) groups-of-extensions hardware-group health history hunt-group inads-link integrated-annc-boards intercom-group...
Page 82 Management Terminals Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test meas-selection principal meas-selection route-pattern meas-selection trunk-group meas-selection wideband-trunk-grp measurements security-violations detail measurements security-violations summary memory modem-pool multi-frequency signaling network-control node-routing...
Page 83 Administrable Logins Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test system 1st-cabinet system 2nd-cabinet system 3rd-cabinet system all-cabinets system conn system-parameters customer-options system-parameters features system-parameters maintenance system-parameters cdr system-parameters country-options system-parameters hospitality...
Page 84 Management Terminals Table 3-1. Command Permissions screen Entries — Display Administration and Maintenance — Continued Action Object Change Display List Monitor Remove Status Test usage-extensions usage-hunt vector wakeup incomplete wakeup requests wakeup station wakeup-log Continued on next page Table 3-2. Command Permissions screen Entries — Administer Permissions Action Object Change...
Page 85 Administrable Logins Table 3-3. Command Permissions screen Entries — Administer Stations Action Object Change Duplicate Remove abbreviated-dialing 7103A-buttons abbreviated-dialing enhanced abbreviated-dialing group abbreviated-dialing personal abbreviated-dialing system alias-station attendant console-parameters data-module routing-table station terminal-parameters 603/302B1 terminal-parameters 8400 vector Issue 4 May 2002 3-19...
Page 86 Management Terminals Table 3-4. Command Permissions screen Entries — Administer Trunks Action Object Change Display Duplicate Remove aar analysis aar digit-conversion access-endpoint announcements ars analysis ars digit-conversion ars toll digit-absorption meas-selection route-pattern meas-selection trunk-group meas-selection wideband-trunk-grp modem-pool personal-CO-line pri-endpoint remote-access rhnpa route-pattern time-of-day...
Page 87: System Logoff Procedure
System Logoff Procedure System Logoff Procedure Perform the system logoff procedure any time the terminal is not being used. This assures that system translations are not accidentally corrupted. The monitor system command, when canceled, automatically causes a terminal user to be logged off and, thus, prevents unauthorized use of the terminal.
Page 88: Switch-Based Bulletin Board
The bulletin board feature makes it easy for the customer to communicate with Avaya (and vise-versa). For example, when a new load is installed on a switch in the customer’s system, Avaya can leave the customer messages which describe new functionality.
Page 89 The Bulletin Board feature provides up to 3 pages of text for each message. Each page is limited to 20 lines of text, and each line of text is limited to 40 characters per line. The first 10 lines of text on page 1 is reserved for Avaya Service’s High-Priority messages.
Page 90 A message may contain up to three pages of information. Message lines 1 through 10 on page 1 are reserved for Avaya Services High-Priority messages (the “init” and “inads” logins can edit the first 10 lines on page 1). Pages 2 and 3 allow up to 20 lines of text, with up to 40 characters per line.
Page 91: Dec Vt220 Terminal
DEC VT220 Terminal DEC VT220 Terminal The system supports use of the DEC VT220 connected to the system and used in the same way as the other terminals. When logging in, at the terminal-type prompt, enter”VT220” to initialize the correct parameters. Keyboard definitions are shown in Table 3-5:...
Page 92 Management Terminals 3-26 Issue 4 May 2002 555-233-123...
Page 93: Initialization And Recovery
Initialization and Recovery When the system is initially powered up, or when it experiences a catastrophic fault that interrupts its basic functions, the system either initializes or reboots. Reset commands Besides “reboot,” there are several less severe resets available to the system that allow it to recover from disrupting errors.
Page 94 Initialization and Recovery The administration terminal display and circuit pack LEDs indicate the progress of the recovery process. LEDs are discussed in Chapter 7, ‘‘LED Interpretation’’. The sections that follow discuss successful system resets. For each level of reset, a typical administration terminal display is provided. Note that any hexadecimal numbers shown in parentheses, such as”(=8B89),”...
Page 95 Reset commands Reset System 2 (System Cold Start Without Translations Loading) All Port circuit packs are reset. All telephone sessions are dropped. Telephones begin to reconnect to the switch within 30 seconds. In a large system, reconnection of all telephones may take up to five minutes. In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth) is reset.
Page 96 Initialization and Recovery Typical display (TN2404/TN790) INTERNAL REGISTER TEST PASSED LOCAL BUS TEST PASSED ROM CHECKSUM TEST PASSED CONTROL STATUS TEST PASSED DCACHE TEST PASSED ICACHE TEST PASSED WRITE BUFFER TEST PASSED BTO TEST PASSED TIMER TEST PASSED RESET 3 (COLD_1) PERFORMED Reset System 4 (System Reboot) Emergency Transfer is invoked.
Page 97 Reset commands MEMORY FUNCTIONAL TEST PASSED MEMORY MODULE A STUCK BIT TEST PASSED MEMORY MODULE A PARITY TEST PASSED MEMORY MODULE A BURST TEST PASSED MEMORY MODULE B STUCK BIT TEST PASSED MEMORY MODULE B PARITY TEST PASSED MEMORY MODULE B BURST TEST PASSED MEMORY MODULE C STUCK BIT TEST PASSED...
Page 98 Initialization and Recovery Typical display (TN2404/TN790) INTERNAL REGISTER TEST PASSED LOCAL BUS TEST PASSED ROM CHECKSUM TEST PASSED CONTROL STATUS TEST PASSED DCACHE TEST PASSED ICACHE TEST PASSED WRITE BUFFER TEST PASSED BTO TEST PASSED MEM CONFIG TEST PASSED MEMORY FUNCTIONAL TEST PASSED MEMORY MODULE A STUCK BIT TEST PASSED...
Page 99 Reset commands DECOMPRESSING IDATA in_cnt = 455532, out_cnt = 1802240 RAM DATA CHECKSUM TEST PASSED RESET 5 (EXT REBOOT) PEFORMED Continued on next page Reset System Interchange (High or Critical Reliability Systems Only) SPE-interchange (system hot start) is denoted by an “i” in the initcauses log. This restart is used to transfer control from the Active SPE to the Standby SPE in the least disruptive manner.
Page 100: Procedure For Spe-Down Mode
Initialization and Recovery Procedure for SPE-Down Mode Due to fatal hardware and software problems, it is possible for a system to go into SPE-Down Mode. In this mode, the system invokes emergency transfer and does not provide any other service. Moreover, while in this mode, the software does not (or cannot) run at all.
Page 101 Procedure for SPE-Down Mode Display for SPE-Down in a High or Critical Reliability System: **************SPE DOWN MODE************ You can display alarms [a|b] and reset system(4) [a|b]. SPE_DOWN-> Screen 4-2 shows only one SPE-Down alarm in a high or critical reliability system after entering the display b command: DISPLAY ALARMS B: Physical...
Page 102 Initialization and Recovery The procedure to get a system out of SPE-Down mode follows. NOTE: This is important! If you cannot complete the first step or have problems with the maintenance interface, then replace the Processor circuit pack. In a high or critical reliability system the DUPINT-A circuit pack can also cause SPE-Down.
Page 103 Procedure for SPE-Down Mode Table 4-1. Order of Circuit Pack Replacement Alarm Suggested Circuit Packs To Replace PROC_BD 1) Processor 2) Network Control MEM_BUS 1) Processor 2) Network Control PROC_MEM 1) Processor OFFBD_MEM 1) Processor 2) Network Control INVALID_ERR 1) Processor 2) Network Control MAINT_BD 1) Processor...
Page 104: Procedure For Duplication Interface - Processing Element Communication Down
Initialization and Recovery Procedure for Duplication Interface — Processing Element Communication Down In a High or Critical Reliability system, it is possible for both SPEs to stop communicating with the A-carrier TN772 Duplication Interface (DUPINT-A) circuit pack. Thus, the DUPINT-A, which is in charge of maintenance, prints the following message on the administration terminal: Duplication Interface-Processing Element Communication down The system may continue to function on one of the SPEs.
Page 105: Routine Maintenance Procedures
Routine Maintenance Procedures The following general purpose maintenance procedures may be used with other repair strategies to clear system-alarmed and user-reported troubles. Suppress Alarm Origination [y] When logged in as “craft”, no alarms are reported to INADS. After logging off, INADS automatically reactivates, and any unresolved alarms are reported to INADS.
Page 106: Handling Control Circuit Packs
Routine Maintenance Procedures Handling Control Circuit Packs PPN Control Circuit Packs WARNING: It is NOT recommended that you reseat circuit packs unless the documentation specifically instructs you to do so. If it is required to reseat a circuit pack, follow the instructions below which explain how to unseat, reseat, and replace circuit packs.
Page 107 Handling Control Circuit Packs To install a new circuit pack or return the original one to service: 1. Carefully insert the circuit pack and push it all the way into its mounting slot. 2. Lift the locking lever until the latch pin engages. 3.
Page 108: Tn2404/Tn790 Processor Circuit Pack
SIMMs as the replaced circuit pack. You must obtain a license file each time you replace a processor circuit pack. CAUTION: Be sure to use an Avaya-provided SIMM. Other brands may have incompatible edge connectors and could produce unpredictable results. Issue 4 May 2002...
Page 109: Removing Power
Removing Power Removing Power When power is removed, the following features deactivate: Attendant Trunk Group Control Automatic Callback Call Park Make Busy for Direct Department Calling (DDC) and Uniform Call Distribution (UCD) WARNING: Before powering down a cabinet or carrier that contains EMBEDDED AUDIX circuit packs (TN566), first power down the AUDIX unit to avoid damaging the AUDIX software.
Page 110 Routine Maintenance Procedures Removing Power in a Single-Carrier Cabinet PPN Follow these steps to remove power to an AC- or DC-powered single-carrier cabinet PPN with high or critical reliability. WARNING: If a translation card alarm is present, or if a translation card problem is suspected, do not save translations of the translation card that is provided with the system.
Page 111: Restoring Power
Restoring Power Removing Power in a Single-Carrier Cabinet EPN NOTE: Power may be removed from the EPN without affecting the PPN. Follow these steps to remove power to an AC- or DC-powered single-carrier EPN with or without high or critical reliability. Before you start In a high or critical reliability system, if power is to be removed from an individual cabinet only, verify that the affected cabinet does not contain an Expansion...
Page 112 Routine Maintenance Procedures To restore power to the cabinet: 1. Turn on the power in each cabinet individually. The power ON/OFF switch is located behind the power unit: WP-91153 Power Unit for an AC-powered system. 676B Power Unit for a DC-powered system If the cabinet is powered by a 676B Power Unit, the 676B must have been powered off for at least 10 seconds before being powered on.
Page 113 Restoring Power 1. To restore power to the cabinet: In an AC-Powered single-carrier cabinet system, turn on the power in each cabinet individually. The ON/OFF switch is located at the back of the cabinet behind the WP-91153 Power Unit. In a DC-Powered single-carrier cabinet system, turn on the power in each cabinet individually.
Page 114: Troubleshooting Power Units
Routine Maintenance Procedures Troubleshooting power units Use the following procedures to troubleshoot the power unit: 1. Check that the translation card is in its slot. 2. Type save translation and press to save translations. Enter 3. Set the EMER XFER (Emergency Transfer) switch on the Processor circuit pack in the PPN to ON.
Page 115 Troubleshooting power units 8. If the yellow LED on the power supply does not light during the reseating of the control circuit packs, unseat all port circuit packs. 9. Reseat the port circuit packs one at a time, as you did in Step 7 above. 10.
Page 116 Routine Maintenance Procedures 1. Power down AUDIX and any other circuit pack that might be running an application (for example, MAPD, TN802 may be running the Internet trunking application on Windows NT 2. Power down the cabinet. 3. Make sure you are wearing a ground strap. 4.
Page 117 Troubleshooting power units Replacing a 631AR or 631BR AC power unit To replace either power unit use the following procedures and Figure 5-1. CIRCUIT BREAKER STATUS LOCKING LEVER POWER CORD LOCKING SLIDE OUTLET Figure 5-1. 631AR or 631BR AC Power Unit 1.
Page 118 Routine Maintenance Procedures 4. Before installing the replacement power unit in the carrier, turn the power unit on its side and operate rocker switches 1 through 4 on the DIP switch as follows: Switch 631AR Position 631BR Position open open closed closed open...
Page 119 Troubleshooting power units Replacing a 631DA or 631DB AC power unit To replace the power unit use the following procedures and Figure 5-2. STATUS LEDS AMBER LOCKING LEVER POWER CORD LOCKING SLIDE OUTLET Figure 5-2. 631DA or 631DB AC Power Unit 1.
Page 120 Routine Maintenance Procedures Replacing a TN736 or TN752 power unit circuit pack Replacing either power unit interrupts the -5 volt supply to the carrier. This causes all the analog circuit packs in the carrier to fail their Loop Around Tests and may cause failures in circuit packs in the control complex.
Page 121 Troubleshooting power units 1. Remove the four screws on the top of the cabinet. 2. Remove the four screws from the fan panel at the rear of the unit. 3. Remove the fan panel. 4. If the unit is attached to the wall, disconnect the entire fan panel. 5.
Page 122 Routine Maintenance Procedures Fans Figure 5-5 while performing the following steps to replace the fan assembly. Hex Nut Flow Direction uard Screw Panel Figure 5-5. Fan sub-assembly 1. At the back of the unit, remove the four screws from the fan panel. Then remove the panel.
Page 123: System Backup
System Backup System Backup System translations can be restored by using the data on the system or on the backup translation card if the length of power failure is appropriate for the corresponding system. Table 5-2 lists the requirements: Table 5-2. Requirements for System Backup Minimum Length of Power Failure (min.) System...
Page 124 Routine Maintenance Procedures The system blocks the execution of any commands that change the translation, access a translation card, or trigger a maintenance action. CAUTION: It is recommended that “save translation” be performed after business hours so that dial tone delays are not encountered. CAUTION: Do not use the “save translation”...
Page 125 System Backup Type save announcements to save recorded announcements in the system on the translation card. NOTE: A 10 MByte or larger translation card is required to save and restore announcements. The system takes about 10 minutes to complete this task. Because the terminal is unavailable during this time, it is recommended that this command be used after business hours.
Page 126 Routine Maintenance Procedures save announcements SAVE ANNOUNCEMENTS Processor Command Completion Status Error Code SPE_A Success Command successfully completely Screen 5-2. Save Announcements Screen — SPEA 6. Verify that the command successfully completes. If not, an error message appears. In such a case, refer to the “Translation Card Errors” section. 7.
Page 127: Software Upgrade
— The correct translation card for the desired operation has not been inserted. Load the appropriate translation card. 10. File size exceeded — There is no more file space. Call your Avaya representative. 11. Upgrade Memory Card inserted — The system upgrade translation card may have been inserted instead of the translations card.
Page 128: Preventive Maintenance Procedures
Preventive Maintenance Procedures Preventive Maintenance Log Table 5-3 shows the Avaya DEFINITY Server Preventive Maintenance Log. Post this table near the switch. When you complete a maintenance procedure described in this section, fill in the information in the spaces provided.
Page 129: System Features
Trunk Identification by Attendant Facility Test Calls Analog Tie Trunk Back-to-Back Testing Terminating Trunk Transmission Testing Troubleshooting ISDN-PRI Problems Troubleshooting PRI Endpoint Problems Troubleshooting ISDN-PRI Test Calls See Administrator’s Guide for Avaya MultiVantage Software for feature descriptions. 555-233-123 Issue 4 May 2002 5-25...
Page 130 Routine Maintenance Procedures See DEFINITY Communications System Generic 1 and Generic 3 — Console Operations, 555-230-700, and DEFINITY Communications System Generic 1 and Generic 3 Voice Terminal Operations for detailed operating procedures (does not include Facility Test Calls, Analog Tie Trunk Back-to-Back Testing, Terminating Trunk Transmission Testing, Troubleshooting ISDN-PRI Problems, Troubleshooting ISDN-PRI Test Calls, or Troubleshooting ISDN-BRI Problems described in this chapter.)
Page 131 System Features Busy Verification of Terminals and Trunks Requires the use of a multi-appearance voice terminal or attendant console equipped with a "verify" button. Busy Verification of Terminals and Trunks allows a user at a voice terminal or attendant console to make test calls to trunks, voice terminals, and hunt groups (DDC/UCD).
Page 132 Routine Maintenance Procedures Facility test calls The Facility Test Calls feature provides a voice terminal user the capability of placing test calls to access specific trunks, touch-tone (DTMF) receivers, time slots, and system tones. The test call can be made by a local voice terminal user by dialing an access code.
Page 133 System Features 3. Listen for one of the following tones: Dial Tone or Silence—trunk is connected. Go to Step 4. If you hear a dial tone, it is coming from the far end. If the far end has been disabled, you do not hear dial tone. However, depending on far-end administration, you may still be able to dial digits.
Page 134 Routine Maintenance Procedures 4. Dial 1234567890*# and listen for Confirmation tone (test passed) or intercept tone (test failed). The test fails if the touch-tone (DTMF) receiver does not recognize all the touch-tone (DTMF) signals. 5. To test another touch-tone (DTMF) receiver, repeat Steps 2 through 4. 6.
Page 135 System Features Table 5-4. TDM Bus Time Slot Numbers TDM Bus A time slot TDM Bus B time slot Tone Heard Reorder Reorder Reorder Reorder Reorder Touch Tone 1 - 697Hz Touch Tone 2 - 770 Hz Touch Tone 3 - 852Hz Touch Tone 4 - 941 Hz Touch Tone 5 - 1209 Hz Touch Tone 6 - 1336Hz...
Page 136 Table 5-5 on page 5-33. 3. Listen for the tone that was specified. NOTE: For a definition of Call Progress Tones see Avaya MultiVantage Hardware Solutions Guide. 5-32 Issue 4 May 2002 555-233-123...
Page 137 System Features Table 5-5. System Tone Identification Numbers Number Description Null tone Dial tone Reorder tone Alert tone Busy tone Recall dial tone Confirmation tone Internal call waiting tone Ringback tone Special ringback tone Dedicated ringback tone Dedicated special ringback tone Touch tone 1 Touch tone 2 Touch tone 3...
Page 138 Routine Maintenance Procedures Table 5-5. System Tone Identification Numbers — Continued Number Description Busy verification Executive override/intrusion tone Incoming call identification Dial zero Attendant transfer Test calls Recall on don’t answer Audible ring Camp-on recall Camp-on confirmation Hold recall Hold confirmation Zip tone 2804 Hz 1004 Hz (-16db)
Page 139 System Features Table 5-5. System Tone Identification Numbers — Continued Number Description Restore music (or silence) Warning tone Forced music tone Zip tone (first of 2 sent) Incoming call ID (first of 2 sent) Tone on hold CO dial tone Repetitive confirmation tone Conference/bridging tone Continued on next page...
Page 140 Routine Maintenance Procedures E & M Mode Test Procedure The procedures to perform the Analog Tie Trunk port test in the E & M mode are as follows: 1. At the administration terminal, enter list configuration trunks command to determine which ports are assigned on the Tie Trunk circuit pack. 2.
Page 141 System Features Examples of Trunk Group forms are shown in Screen 5-3 Screen 5-4. display trunk-group 10 Page 1 of 5 TRUNK GROUP Group Number: 10 Group Type: tie CDR Reports? y Group Name: tr 10 COR: 1 TAC: 110 Direction: two-way Outgoing Display? n Data Restriction? n...
Page 142 Routine Maintenance Procedures 11. At the cross-connect field, disconnect outside trunk facilities from the Tie Trunk ports and mark the disconnected wires for later reconnecting the Tie Trunk ports back to normal operation. The D Impact Tool (AT-8762) is required to perform this step. 12.
Page 143 System Features Table 5-6. Carrier Lead Appearances at 110 Cross-Connect Field — Continued 110 Connecting Block Terminals CO Trunk TN747B Tie Trunk TN760B Continued on next page 555-233-123 Issue 4 May 2002 5-39...
Page 144 Routine Maintenance Procedures Table 5-6. Carrier Lead Appearances at 110 Cross-Connect Field — Continued 110 Connecting Block Terminals CO Trunk TN747B Tie Trunk TN760B Continued on next page Simplex Mode Test Procedure To perform the Analog Tie Trunk Port Test in the simplex mode: 1.
Page 145 System Features An example of the Trunk Group Form Page 2 is shown in Screen 5-5. Page 2 of 5 TRUNK GROUP GROUP MEMBER ASSIGNMENTS Port Name Mode Type Answer Delay 1: B1901 simplex type 5 2: B1902 simplex type 5 Screen 5-5.
Page 146 Routine Maintenance Procedures Terminating Trunk Transmission Testing The Terminating Trunk Transmission (TTT) (noninteractive) feature provides for extension number access to three tone sequences that can be used for trunk transmission testing from the far end of the trunks. The three test types should have extension numbers assigned on the Maintenance-Related System Parameters Form.
Page 147 System Features START ARE THERE DETERMINE PRESENT ALARMS OR STATUS OF DS-1 FACILITY ERRORS AGAINST VIA DS1-BD MO SECTION. DS1-BD FOLLOW REPAIR PROCEDURES IF MULITPLE ALARMS EXIST, INVESTIGATE IN FOLLOWING ARE THERE ORDER: ALARMS OR PI-BD ERRORS AGAINST PI-PT PI-BD, PI-PT, PI-SCI, PI-SCI PI-LINK, OR PI-LINK...
Page 148 Routine Maintenance Procedures COMPARE INDICATED FROM FACILITY TO RECORD PAGE OF PREVIOUS PROBLEMS PERFORM AN IN-DEPTH ANALYSIS OF T1 FACILITY INCLUDING: TRANSMISSION FACILITY, EXTERNAL EQUIPMENT THERE ARE BIT (DACS, CSUs, ETC.,) TRANSIENT ERRORS OCCURRING AND ANY OTHER MORE FREQUENTLY PROBLEMS MAKING NOISE-PRODUCING ISDN-PRI THAN PREVIOUS...
Page 149 System Features The troubleshooting procedure described here diagnoses faults between the switch and the line-side PRI terminal adapter/ISDN-PRI endpoint equipment. Problems encountered on the network-side of a wideband connection or problems with end-to-end equipment compatibility are out of the scope of this section. START Are there alarms or...
Page 150 Routine Maintenance Procedures FROM PAGE 1 Does every TRANSIENT FAILURES ALWAYS FAIL call fail or are the failings transient? CHECK THE HEALTH OF THE Are there APPLICATION EQUIPMENT bit errors (FOR EXAMPLE, VIDEO CODEC) Perform an in-depth over the DS1 AND THE HEALTH OF THE analysis of DS1 interface between the...
Page 151 System Features Placing an Outgoing ISDN-PRI Test Call NOTE: An ISDN-PRI test call can be placed only if the circuit translates to an ISDN-PRI trunk. An ISDN-PRI test call can be originated by via either the synchronous or the asynchronous method: Synchronous Method Use one command to start, stop and query an ISDN-PRI test call.
Page 152 Routine Maintenance Procedures status isdn-testcall <grp>/<mbr> (query) test isdn-testcall <grp>/<mbr> [minutes] (start) NOTE: Before placing an outgoing ISDN-PRI test call, verify that the FAC on the System Features Form has been administered as well as the Far End Test Line No and TestCall Bearer Capability Class (BCC) on the Trunk Group Administration Form.
Page 153 System Features The functions of the clear, list, and status commands associated with the ISDN Testcall are summarized in the following list. For more detailed information, refer to the appropriate sections as directed. Clear isdn-testcall <grp>/<mbr> enables you to cancel an in-progress ISDN-PRI test call and allow another test call to start.
Page 154: Troubleshooting Backplane Voltage Problems
Routine Maintenance Procedures by the network. The user must subscribe to Test Type 108 service and have the correct far-end test call number administered on the trunk group form for the call to be allowed. Troubleshooting Backplane Voltage Problems The TN2036 Voltage Range circuit pack is a test tool that allows easy access to the backplane pins that provide various voltages to control and port slots.
Page 155: Multimedia Call Handling (Mmch)
T.120 data sharing capability on a MMCH multipoint H.320 video conference. Each conference participant must have endpoints administered and a personal computer with the H.320 video application installed. The Avaya DEFINITY Server must have an expansion service module. cydf012 RPY 100697 Figure Notes 1.
Page 156 Some 2x64 Kbps conferences on the DEFINITY MMCH do not establish because of framing, audio, or video problems. For calls that are routed in the network through a Avaya/LEC interface, the originating equipment may launch a 64 Kbps call attempt, and the far end receives either a 56 Kbps or 64 Kbps indication.
Page 157 Multimedia Call Handling (MMCH) Some Parties Cannot Be Heard by Others (Audio Subsetting) Description Problems where varying subsets of the conference hear different things may have problems with the various summing resources/groups that are in use. Traditionally theses faults are caused by the SPE not cleaning up the connections properly. Isolation and diagnosis should focus on the VC resources in use by that conference.
Page 158 Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to instability. The Avaya Vistium also disconnects fairly infrequently. Last, the CLI Rembrandt II VP freezes video and waits for framing to be recovered. Network Configuration Concerns with Synchronization When auditing a network for synchronization, avoid unnecessary hops.
Page 159 Multimedia Call Handling (MMCH) PRI D-Channel Backup A somewhat unlikely source of call stability problems occur where the translations for PRI D-channel Backup between two non-MCU switches were incorrect. As an example, on switch A, DS1 1A10 was designated as the primary source, and on switch B, the corresponding DS1 was designated as the secondary source.
Page 160 Routine Maintenance Procedures UCC-designated broadcaster, status conference X indicates a Video Status of u . Also, for UCC rollcall the return video may appear to be stuck. Check the Video Status for an “ R ,” indicating rollcall. If none of the examples above appears to be the cause, and if the room was quiet, all speakers are valid video sources, the conference is voice-activated, and the speaker can be heard, then escalate the problem.
Page 161 Multimedia Call Handling (MMCH) For some Avaya Vistium endpoints, if an external speaker is attached or was attached when the system was last rebooted, this endpoint will cause audio echo throughout the conference. First, isolate the offending endpoint by asking each endpoint to mute, one at a time, until the echo disappears.
Page 162: Install Ds1 Cpe Loopback Jack (T1 Only)
Routine Maintenance Procedures The MMCH does not detect the loop and continues to VAS. In most scenarios, the switch occurs, but within a few seconds, the broadcaster’s return video becomes its own image. Once the broadcaster stops speaking, the system “false” switches to an apparently random port that was not speaking.
Page 163 Install DS1 CPE Loopback Jack (T1 Only) Installation 1. To install the loopback jack, simply disconnect the RJ-48 (8-wide) connector (typically an H600-383 cable) at the appropriate interface point and connect the loopback jack in series with the DS1 span. See Figure 5-11 on page 5-64 through...
Page 164 Routine Maintenance Procedures The second part of the test sends the standard DS1 3-in-24 stress testing pattern from the DS1 board, through the loopback jack, and back to a bit error detector and counter on the DS1 board. The bit error rate counter may be examined at will via the management terminal, and provides the results of the second part of the test.
Page 165 Install DS1 CPE Loopback Jack (T1 Only) Table 5-7. DS1 Span Troubleshooting Displayed Field Function Indication Test: cpe- Pattern The loopback jack test is active. loopback-jack 3-in-24 Synchronized Y or N If “y” displays, the DS1 circuit pack has synchronized to the looped 3-in-24 pattern and is accumulating a count of the bit errors detected in the pattern until the test has ended.
Page 166 Routine Maintenance Procedures 11. Terminate the test by entering test ds1-loop <location> end cpe-loopback-jack-test. Wait about 30 seconds for the DS1 to re-frame on the incoming signal and clear DS1 facility alarms. Loopback termination fails under the following conditions: a. The span is still looped somewhere. This could be at the loopback jack, at the ICSU, or somewhere in the network.
Page 167 Install DS1 CPE Loopback Jack (T1 Only) Configurations Using a Smart Jack The addition of the loopback jack and the presence of a Smart Jack divides the DS1 span into 3 separate sections for fault isolation. These sections are shown in Figure 5-11 on page 5-64 through Figure 5-13 on page 5-66...
Page 168 Routine Maintenance Procedures Figure Notes: 1. Span Section 1 5. RJ-48 to Network Interface (Up to 1000 Feet) (305 m) 2. Span Section 2 6. Loopback Jack 3. Span Section 3 7. Network Interface Smart Jack 4. 120A2 (or later) Integrated Channel Service Unit (ICSU) 8.
Page 169 Install DS1 CPE Loopback Jack (T1 Only) Figure Notes: 1. Span Section 1 6. Loopback Jack 2. Span Section 2 7. “Dumb” Block (Extended Demarcation) 3. Span Section 3 8. Network Interface Smart Jack 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
Page 170 Routine Maintenance Procedures Figure Notes: 1. Span Section 1 6. “Dumb” Block (Extended Demarcation) 2. Span Section 2 7. Loopback Jack 3. Span Section 3 8. Network Interface Smart Jack 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
Page 171 Install DS1 CPE Loopback Jack (T1 Only) Configurations Without a Smart Jack When the loopback jack is added to a span that does not contain a Smart Jack, the span is divided into 2 sections. See Figure 5-14 on page 5-67 Figure 5-15 on page 5-68.
Page 172 Routine Maintenance Procedures Figure Notes: 1. Span Section 1 5. Loopback Jack 2. Span Section 2 6. “Dumb” Block (Demarcation Point) 3. 120A2 (or later) Integrated 7. Repeater Channel Service Unit 8. Fiber MUX (ICSU) 9. Central Office 4. RJ-48 to Network Interface (Up to 1000 Feet) (305 m) Figure 5-15.
Page 173 Install DS1 CPE Loopback Jack (T1 Only) A problem can exist in 1 or both of the 2 sections. The field technician is responsible for finding and correcting problems in section 1 and the loopback cable portion of section 2. The DS1 service provider is responsible for finding and correcting problems in the majority of section 2.
Page 174 Routine Maintenance Procedures Configurations Using Fiber Multiplexers Use the loopback jack when customer premises DS1 wiring connects to an on-site fiber multiplexer (MUX) and allows wiring to the network interface point on the MUX to be remotely tested. This requires that ICSUs be used on DS1 wiring to the MUX.
Page 175: Atm Tips
ATM Tips ATM Tips This section provides tips for DEFINITY ATM PNC when interfacing with the Cajun A500 ATM switch. Initial LED inspection Visually inspect the LEDs on both the TN230X (Table 5-8) and the ATM switch (Table 5-9) for a high-level status of the system. Table 5-8.
Page 176 Routine Maintenance Procedures Table 5-9. A500 LED Quick Reference — Continued Component Label Color State Meaning NBOOT Green Normal state. Green Normal state. Green Steady on Normal state. The switch processor is running. Green Steady on Normal state. The switch processor board is powered up.
Page 177 ATM Tips Table 5-9. A500 LED Quick Reference — Continued Component Label Color State Meaning RPRD Yello Normal state Power Supply AC OK Green Steady on Normal state. AC power is okay. DC OK Green Steady on Normal state. DC power is okay. Continued on next page Cajun A500 Diagnostics The first step in any diagnostic procedure involving the A500 is to identify the...
Page 178 Can you log into the A500 console using the diagnostic account root from the local console terminal or through telnet? (See Screen 5-7.) A500 System Console (c) 1997 Avaya Inc. login: root password: XXXXXX ********** New System Alarms ********** [1] Failed to fetch configuration files...
Page 179 TFTP server, does the TFTP server field have the customer-provided Internet address, as configured using tftp setserver? e. Does the ATM address field have the customer- or Avaya-provided network prefix (the first thirteen bytes and set by using modify atmprefix)?
Page 180 Routine Maintenance Procedures status pnc PORT NETWORK CONNECTIVITY Duplicated? no Software Locked? Standby Busied? Standby Refreshed? Interchange Disabled? A-PNC B-PNC Mode: active Mode: State of Health: State of Health: Inter PN Index: Inter PN Index: Major Alarms: 0 Major Alarms: Minor Alarms: 0 Minor Alarms: Warning Alarms: 0...
Page 181 ATM Tips display circuit-packs 1 CIRCUIT PACKS Cabinet: 1 Carrier: A Cabinet Layout: five-carrier Carrier Type: processor *** PROCESSOR BOARDS NOT ADMINISTERABLE IN THIS SCREEN *** CIRCUIT PACKS Cabinet: 1 Carrier: B Cabinet Layout: five-carrier Carrier Type: port Slot Code Name Slot Code Name...
Page 182 Routine Maintenance Procedures Administered with hard coded PNNI routes If the port networks are addressed using hard coded PNNI routes in the A500, the display looks like Screen 5-13 (pnc 1) and Screen 5-14 (pnc 2). display atm pnc 1 ATM PNC Connection Number: 1 Location: 01B02...
Page 183 ATM Tips display atm pnc 1 ATM PNC Connection Number: 1 A - PNC Location: 01B02 Name: Address Format: E.164 ATM Private AFI: 45 E.164: 0001013035381053 HO-DSP: 00000000 ESI: 000000000011 SEL: 00 Screen 5-15. Screen output for display atm pnc 1 with End System Identifiers display atm pnc 2 ATM PNC Connection Number: 2...
Page 184 Routine Maintenance Procedures a. If an A500 port to which a DEFINITY port network is attached is not listed in this display, it is likely that the port was administered incorrectly as having no UNI signaling (admin link command). Ensure that fields listed have the values indicated below. Field Value IntType...
Page 185 ATM Tips A500:show signaling esi Addresses registered on A1.1 ---------------------------- * 45.0001.01303538105300000000.000000000011.00 Addresses registered on A1.2 ---------------------------- * 45.0001.01303538105300000000.000000000012.00 ( * - configured ) Screen 5-19. Screen output A500: show signaling esi command Check that Addresses registered (use admin signaling esi add) match those administered in DEFINITY.
Page 186 Routine Maintenance Procedures Device Oper Admin State Type Status Status _________________________________________________________________ A1.1 present STS_3c (MultiMode) A1.2 present STS_3c (MultiMode) A1.3 down down present STS_3c (MultiMode) A1.4 down down present STS_3c (MultiMode) A1.5 down down present STS_3c (MultiMode) A1.6 down down present STS_3c (MultiMode) A1.7...
Page 187 ATM Tips TN230X Did the TN230X come up correctly? 1. Review the LED conditions for the TN230X: Do the TN230X LEDs (see Table 5-8 on page 5-71) indicate a normal operational state (any of the following): — Active in the PPN —...
Page 188 Routine Maintenance Procedures list configuration carrier 2a SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 02A01 ATM PNC EI TN2305 000001 02A09 DS1 INTERFACE TN767E 000004 02A10 DIGITAL LINE TN754B 000016 02A11 ANALOG LINE TN746B 000010 01 u 02A17...
Page 189 ATM Tips test board 2a01 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 02A01 ATM-EI PASS 02A01 ATM-EI PASS 02A01 ATM-EI 1258 PASS 02A01 ATM-EI PASS 02A01 ATM-EI PASS 02A01 ATM-EI 1259 PASS Screen 5-24. Screen output for the test board 2a01 command The Result should be PASS for each test number.
Page 190 Routine Maintenance Procedures Physical Layer Is there an optical signal between the TN230X and the A500? 1. Does the TN230X’s yellow LED flash 100ms on/100ms off, indicating a loss of signal on the fiber? The TN230X detects continuity problems with either the Transmit (bottom) or the Receive (top) fibers.
Page 191 ATM Tips Device Oper Admin State Type Status Status _________________________________________________________________ A1.1 present STS_3c (MultiMode) A1.2 present STS_3c (MultiMode) A1.3 down down present STS_3c (MultiMode) A1.4 down down present STS_3c (MultiMode) A1.5 down down present STS_3c (MultiMode) A1.6 down down present STS_3c (MultiMode) A1.7 down...
Page 192 Routine Maintenance Procedures Possible Causes The fiber is disconnected from the A500 and/or the TN230Xs. The Transmit and Receive fibers are swapped at the A500 or the TN230X (but not both). There is a break in the fiber. The TN230X is not transmitting a carrier (not inserted, not powered, or not administered).
Page 193 ATM Tips Sonet per Port Statistics --------------------------------- Receive Cell Count: 80654 Transmit Cell Count: 79555 Section Level Bit Err: Line Bit Err: Line FEB Err: Path Bit Err: Path FEB Err: Correctable HCS Err: Uncorrectable HCS Err: Loss of Frame Err: Loss of Signal Err: Out of Frame Err: Path Signal Label:...
Page 194 Routine Maintenance Procedures Q.SAAL (Data Link) Layer Are ATM signaling messages reaching A500 Call Control? 1. Enter show signaling stats port qsaal on the A500 console. Screen 5-28 on page 5-90 shows the screen output. A500: show signaling stats a1.2 qsaal ------------------------Q.SAAL Statistics------------------------ Port A1.2: ----------...
Page 195 ATM Tips Q.93B (Network) Layer Are connection requests being received by A500 Call Control? 1. Enter show signaling stats port q93b (or the port of interest) on the A500 console. Screen 5-29 shows the screen output. A500:show signaling stats a1.2 q93b -------------------------Q.93B Statistics------------------------ Port A1.2: ----------...
Page 196 Routine Maintenance Procedures Enter show signaling cause causecode on the A500 console. Screen 5-30 shows the screen output for this command. A500:show signaling cause 31 Cause 31: Normal, unspecified Screen 5-30. A500:show signaling cause 31 3. At the DEFINITY SAT type display errors and press Enter Set the Error List to errors and Category to PNC on the input screen (Screen...
Page 197 ATM Tips Screen 5-32 shows the screen output for display errors. display errors Page SPE A HARDWARE ERROR REPORT Port Mtce First Last Err Err Rt/ Al Ac Name Name Type Data Occur Occur Cnt Rt AT01A ATM-NTWK 11/12/16:59 12/09/15:10 14 0 AT01A ATM-NTWK 11/13/18:27 11/20/20:02 5...
Page 198 Routine Maintenance Procedures ATM Call Control Are ATM signaling connections being setup to A500 Call Control? 1. Enter show switch circuittable on the A500 console. Screen 5-33 shows the screen output. A500:show switch circuittable _______________________________________________________ Input Output Connection | port vpi vci| port vpi vci| type class parameters...
Page 199 ATM Tips 1. Enter list sys-link on the DEFINITY SAT. Screen 5-34 shows the output. list sys-link SYSTEM LINKS INFORMATION Location Link Type/ State Current Faulted Last Fault Channel Path Path Recorded 02A0101 present present 12/06/1997 16:20 01B0202 PACL present present 12/06/1997 16:17 02A0102...
Page 200 Routine Maintenance Procedures CaPro Layer Are talk paths being established between port networks? Diagnostics Can you talk both ways on a set on one port network dialed from another port network and vice versa? 1. Enter show switch circuit on the A500 console. Screen 5-36 shows the screen output.
Page 201: Unusual Atm Trouble Conditions
Unusual ATM trouble conditions — There may be other CBR virtual circuits between A500 ports that are not associated with DEFINITY port networks. A common CBR application is Circuit Emulation, in which T-1, T-3, etc. circuits are carried over ATM. Unusual ATM trouble conditions There are a few failure modes in the DEFINITY/A500 combination that are difficult to diagnose.
Page 202 Routine Maintenance Procedures Swapped Routes, End System Identifiers, or Fiber between a PPN and an EPN Symptoms An incorrectly-connected EPN TN230X does not complete board insertion. Dial tone is present on end stations on the PPN and on correctly-connected EPNs, but no dial tone is present on the affected EPN end stations. Calls cannot be made between the PPN and the correctly connected EPNs, because talk paths cannot be routed correctly.
Page 203 Unusual ATM trouble conditions Action 1. Correct the ATM addresses (or swap fibers) on the A500 between the incorrectly connected EPNs. Swapped Routes, End System Identifiers, or Fiber between A and B side TN230Xs on an EPN Symptoms The PPN establishes links to what it thinks is the active TN230X on the EPN.
Page 204 Routine Maintenance Procedures 5-100 Issue 4 May 2002 555-233-123...
Page 205: Reliability Systems: A Maintenance Aid
Reliability Systems: A Maintenance General A High or Critical Reliability system provides highly-available call processing because single points-of-failure in the system that result in loss of call processing are minimized. Such a system Uses existing duplicated TDM buses Duplicates the SPE, translation card, and Tone-Clock circuit pack Packet bus redundancy Each of these components are single points of failure in a standard reliability system.
Page 206 Reliability Systems: A Maintenance Aid Under normal conditions, the system operates using both TDM Buses. If the system detects transmission problems on one of the buses, it takes that bus out of service and operates with only one bus, but also reduces capacity. However, if the system detects a problem with one of the Tone-Clock circuit packs, it is able to take that circuit pack out of service without any impact on system capacity or performance.
Page 207: Reliability Options
Reliability Options Reliability Options Standard, High and Critical reliability systems offer an increased level of reliability by duplicating various components so that standby components can take over (interchange) when a failure occurs on an active component. Most interchanges take place with no disruption of current service and allow for repairs to be made without disruption.
Page 208: Duplicated Hardware
Reliability Systems: A Maintenance Aid Critical Reliability Critical Reliability systems include all of the features of the High Reliability option described in the previous section. Additionally, these systems duplicate components of Port Network Connectivity (PNC) and of other components that are critical to the viability of each EPN.
Page 209 Duplicated Hardware Processor Interface Circuit Pack(s) (TN765) NOTE: There may be zero, one, or two Processor Interface circuit pack. However, both SPEs must have an equal number of Processor Interface circuit packs. Duplication Interface Circuit Pack (TN772) Duplication Interface Circuit Pack The Duplication Interface circuit pack is required to support SPE duplication.
Page 210 Reliability Systems: A Maintenance Aid The Duplication Interface circuit packs support serial links that provide for system access terminal connection, memory shadowing from Active SPE Memory to Standby SPE Memory, and communication between software on the Active SPE and the Standby SPE. Four serial links are supported: 1.
Page 211 Duplicated Hardware Each switch has three positions: SPE-A (the left position) AUTO (the middle position) SPE-B (the right position) To hard-select SPE A as the Active SPE, both SPE Select switches must be moved one at a time to the SPE-A position. To hard-select SPE-B as the Active SPE, both SPE Select switches must be moved to the SPE-B position.
Page 212 Reliability Systems: A Maintenance Aid Tone-Clock Circuit Pack Duplication For more information about the Tone-Clock circuit packs see TONE-BD in Chapter 10, ‘‘Maintenance Object Repair Procedures’’. The TONE-BD (Tone-Clock) MO functionality is made up of the TONE-PT (Tone Generator) and the TDM-CLK (TDM Bus Clock). The Tone Generator provides all tones required by the system;...
Page 213 Duplicated Hardware Packet Bus Redundancy The Packet Bus is used to provide ISDN-BRI signaling via the TN778 Packet Control circuit pack. The Packet Bus is not physically duplicated in the same way that the TDM Bus is duplicated. However, there are several spare leads on the Packet Bus itself that are not normally used.
Page 214: Duplication Concepts
Reliability Systems: A Maintenance Aid Duplication Concepts High and Critical Reliability systems employ several concepts of duplication. These are described in the following sections. Memory Shadowing Most of the time the Standby SPE is in a mode known as Standby Mode (see ‘‘SPE Modes’’...
Page 215 Duplication Concepts Bus so that it does not attempt to control the Packet bus, and thus interfere with the Active SPE Packet Control circuit pack. The Standby SPE PROCR (Processor) is held in a reset state so that it does not run software. Finally, —...
Page 216 Reliability Systems: A Maintenance Aid This means that all of Active SPE DRAM Memory is shadowed over into Standby SPE Memory. The refresh is necessary because, while in Maintenance Mode, memory shadowing to the Standby SPE is disabled, and Standby SPE Memory is not updated to reflect changes in Active SPE Memory.
Page 217 Duplication Concepts SPE Select Switches An SPE-interchange can be initiated by moving both SPE Select Switches, one at a time, to the position that selects the Standby SPE for Active Mode. The SPE Select Switches were described earlier in this chapter. Scheduled Maintenance An SPE-interchange can be requested as a part of scheduled maintenance.
Page 218 Reliability Systems: A Maintenance Aid Table 6-2. Software-Requested Interchanges Caused by Alarm Conditions Maintenance On/Off Fault Severity Object Alarm Level Board Level Restart Level STBY-SPE WARNING None MEM-BD MAJOR or MINOR Hot or Warm MEMORY MAJOR or MINOR Hot or Warm STBY-SPE MAJOR None...
Page 219: System Technician Commands For High And Critical Reliability Systems
System Technician Commands for High and Critical Reliability Systems System Technician Commands for High and Critical Reliability Systems The following system technician commands support high and critical reliability systems. Complete descriptions of these commands are found in Chapter 8, ‘‘Maintenance Commands and Trouble-Clearing Aids’’.
Page 220 Reliability Systems: A Maintenance Aid The test duplication-interface [1] a | b [short | long] command tests the specified TN772 Duplication Interface circuit pack. The test shadow-link command tests the SHDW-LINK (Memory Shadowing Link). Refer to “MEM-BD” in Chapter 10, ‘‘Maintenance Object Repair Procedures’’...
Page 221 System Technician Commands for High and Critical Reliability Systems The following side-effects may occur: Testing of the Standby SPE components that are the target of the maintenance activity may not have completed. Depending on the maintenance activity and the point at which it is terminated, tests that detect faults and/or lack of faults on those Standby SPE components may not have had the opportunity to run.
Page 222 Reliability Systems: A Maintenance Aid Commands for Packet Bus Redundancy The status system command displays the status of the Packet Bus, and the number of faulty and open leads that the Maintenance/Test circuit pack has found. The test pkt port-network [1 | 2 | 3] command tests the Packet Bus. Commands for Tone-Clock Circuit Pack Duplication The status system command displays the Tone-Clock circuit pack that is...
Page 223: Processor Complex Circuit Pack Led Strategies
Processor Complex Circuit Pack LED Strategies Processor Complex Circuit Pack LED Strategies The LEDs on the circuit packs in the two SPEs have the following meanings: Processor Circuit Pack Yellow Green Meaning Active mode Active mode: Maintenance running Maintenance mode; Memory not refreshed Maintenance mode;...
Page 224 Reliability Systems: A Maintenance Aid Each Duplication Interface circuit pack has another red LED associated with the SPE Select Switch. The purpose of the red switch LED is to serve as a reminder that an SPE is being forced to be the Active SPE and, therefore, the system is not duplicated.
Page 225: Repair Procedures For High And Critical Reliability
Repair Procedures for High and Critical Reliability Repair Procedures for High and Critical Reliability This section describes the procedure for installing or replacing Standby SPE circuit packs. These circuit packs are: Processor Circuit Pack Network/Packet Control Circuit Pack Processor Interface circuit pack(s) Duplication Interface circuit pack NOTE: If you are replacing the Processor Circuit Pack, you need to obtain a new...
Page 226 Reliability Systems: A Maintenance Aid Replacing Defective SPE Circuit Packs Determine that software is running by looking at the G3MT and verifying that it does not have either the “SPE DOWN MODE” or the “Duplication Interface - Processing Element Communication Down” message displayed. Software Not Running If system software is not running or if it stops running at any point during this procedure, the suggested order of Processor Complex circuit packs to replace in...
Page 227 Repair Procedures for High and Critical Reliability Handling SHDW-CIR and SHDW-LNK Alarms in the Active SPE Check for the existence of SHDW-CIR alarms against the Active SPE Duplication Interface circuit pack or SHDW-LNK alarms. If there are Active SPE SHDW-CIR or SHDW-LNK alarms, inform the customer that a COLD 2 restart of the system is needed and determine a time at which to restart may be.
Page 228 Reliability Systems: A Maintenance Aid However, if the defect in the Duplication Interface circuit pack did not sever the Memory Shadowing Link, the SPE-interchange results in the new Active SPE performing a Warm Start instead. 4. After the SPE-interchange is complete, log into the terminal. Follow the ‘‘Circuit Pack Replacement Procedure’’...
Page 229 Repair Procedures for High and Critical Reliability Circuit Pack Replacement Procedure NOTE: If you are replacing the Processor Circuit Pack, obtain a new license file. NOTE: This procedure does not apply to the TN768 Tone-Clock circuit pack. Please refer to “TONE-BD”, “TONE-PT”, or “TDM-CLK” in Chapter 10, ‘‘Maintenance Object Repair Procedures’’...
Page 230 Reliability Systems: A Maintenance Aid b. If the SERVICE STATE field indicates that the 1B carrier Tone-Clock is “in” (that is, in service) but the SYSTEM CLOCK and SYSTEM TONES fields indicate that it is “standby,” then check the Error Log for an active Error Type 3329 against the 1B TONE-BD by issuing the display error command.
Page 231 Repair Procedures for High and Critical Reliability If the Standby Processor is not being replaced Install the replacement circuit pack and reinsert the Standby SPE Processor circuit pack. a. If the circuit pack that was replaced was the TN772 Duplication Interface in the A carrier, the system access terminal is logged off.
Page 232 Reliability Systems: A Maintenance Aid g. Issue the busyout spe-standby command followed by the release spe-standby command to force the Standby SPE into a mode to accept the list configuration software-versions long command. Wait 5 minutes for the Standby SPE to initialize and issue the status system 1st-cabinet command.
Page 233 Repair Procedures for High and Critical Reliability Maintenance activity is performed automatically on the Standby SPE after the SPE Select Switches are returned to their AUTO positions in Step 10. This can be verified by issuing the status system command and noting that the Standby SPE is labeled as “maint.”...
Page 234 Reliability Systems: A Maintenance Aid Additional Tests for Replaced DATA-CHL, PKT-CTRL, and PROCR Circuit Packs After all affected circuit packs have been replaced, if the replaced circuit packs include the Network Control circuit pack(s), the Packet Control circuit pack(s), or the Processor circuit pack(s), additional testing is required to ensure that the new circuit packs are healthy.
Page 235 Repair Procedures for High and Critical Reliability Are there SHDW-CIR alarms in the active SPE or are there SHDW-LNK alarms? Issue the "save translations spe-active" command Are there Exchange the Issue the DUPINT alarms active SPE "save translations in the active and STANDBY spe-active"...
Page 236 Reliability Systems: A Maintenance Aid Is the defective circuit pack the carrier A DUPINT? Is the 1B CARRIER TONE CLOCK "in" service and "active"? Is the 1B CARRIER TONE CLOCK "in" service and "standby"? Issue the "set tone 1b" command to make it "active"...
Page 237 Repair Procedures for High and Critical Reliability In se r t so ftw a re In s ta ll n ew c ircu it In s ta ll n ew c ircu it m e m o ry ca rd in to th e p a ck p a ck a ctive S P E .
Page 238: Procedure For Installing/Replacing The Inter-Cabinet Cable
Reliability Systems: A Maintenance Aid Procedure for Installing/Replacing the Inter-Cabinet Cable The Inter-Cabinet Cables (ICCs) are physically located on the back of the cabinet behind the panels and between the A control cabinet and the B control cabinet. The panels must first be opened to see the ICCs. WARNING: Damage can be done to the Inter-Cabinet Cables during removal or installation.
Page 239: Blocking Standby Spe Maintenance Activities For System Testing
Blocking Standby SPE Maintenance Activities for System Testing Blocking Standby SPE Maintenance Activities for System Testing Sometimes it is necessary to block Standby SPE maintenance activities so that system technician commands that test Standby SPE components can be conducted without being blocked with the G3MT terminal message line “Standby SPE busy with another task;...
Page 240 Reliability Systems: A Maintenance Aid Maintenance activity is performed automatically on the Standby SPE after the SPE Select Switches are returned to their AUTO positions in Step 4. This can be verified by issuing status system and noting that the Standby SPE is labeled as “maint.”...
Page 241: Led Interpretation
LED Interpretation General The lighting and unlighting of LEDs indicates the status of various maintenance components in the system. LEDS are located on the attendant console, on all circuit packs in the switch cabinets and, optionally, on customer-designated voice terminals. The following LEDS are included in the system: ‘‘Processor and Maintenance Circuit Pack LEDs’’...
Page 242: Terminal Alarm Notification
LED Interpretation Terminal Alarm Notification Terminal Alarm Notification is an optional feature which displays several types of alarms on voice terminals with administered feature buttons or the attendant console. A maximum of ten digital and/or hybrid voice terminals may be used. When an alarm occurs, the green status LED associated with the assigned button will be in a steady state.
Page 243: Processor And Maintenance Circuit Pack Leds
Processor and Maintenance Circuit Pack LEDs Processor and Maintenance Circuit Pack LEDs The front panels of the Processor circuit pack and the Maintenance circuit pack are identical. Each has two groups of LEDs. One group indicates the status of the pack, and the other group (which includes Major, Minor, and Warning alarms) reflects maintenance conditions in the entire system, including the PPN and EPN cabinets.
Page 244: Duplication Interface Circuit Pack Leds
LED Interpretation ALARM LED (RED) TEST LED (GREEN) BUSY LED (AMBER) ALARMS MAJOR MAJOR ALARM LED (RED) MINOR MINOR ALARM LED (RED) WRNG WARNING ALARM LED (AMBER) ACKNOWLEDGEMENT LED (GREEN) EMERGENCY TRANSFER EMERGENCY TRANSFER CONTROL SWITCH AUTO EMERGENCY TRANSFER LED (RED) Figure 7-1.
Page 245 Duplication Interface circuit pack LEDs NOTE: Failure to move both SPE Select switches to the same position causes the system to retain control of processor selection. To return control of the SPE selection to the system, return the SPE Select switches on both Duplication Interface circuit packs to the AUTO position (one at a time to avoid accidentally selecting the other SPE).
Page 246: Attendant Console Leds
LED Interpretation Attendant console LEDs The console has two red LEDs, labeled ALM and ACK, on the left side of the dial. The left LED lights steadily when there is a Major or Minor alarm at the switch cabinet. The right LED lights steadily if the alarm has been successfully reported to INADS.
Page 247: Control And Port Circuit Pack Status Leds
Control and port circuit pack status LEDs Control and port circuit pack status LEDs Each circuit pack has three LEDs on the front panel visible at the front of the carrier. On all circuit packs, except the TN736 Power Unit, the LEDs indicate: —...
Page 248 LED Interpretation If the system seems to be functioning correctly, but the circuit pack does not start communicating with the system, replace the circuit pack. — 2. Green (test) the system is running tests on this circuit pack. — 3. Yellow (busy) indicates that the circuit pack is in use.
Page 249 Control and port circuit pack status LEDs Table 7-1. Circuit Pack Status LEDs — Continued Equipment Type Description On briefly during power up and system reset. Steadily on if circuit pack fails start-up test or fails while in use. Off during normal operation. Green On briefly during board testing following power up and system reset.
Page 250 LED Interpretation 7-10 Issue 4 May 2002 555-233-123...
Page 251: Maintenance Commands And Trouble-Clearing Aids
Maintenance Commands and Trouble-Clearing Aids For Maintenance Objects and Maintenance Commands for the DEFINITY Wireless Business System (DWBS), refer to the DWBS maintenance documentation. This chapter provides additional trouble-clearing information for resolving both system-alarmed and user-reported troubles. This chapter supplements the information found in Chapter 10, ‘‘Maintenance Object Repair Procedures’’.
Page 252: Busyout Access-Endpoint
Maintenance Commands and Trouble-Clearing Aids busyout access-endpoint This command is destructive. This command busies out a specified access endpoint. Action/ Qualifier Feature Object Qualifier Description Logins Defaults Interactions busyout extension Extension number of init none See below access- access endpoint (per inads endpoint dial-plan)
Page 253: Busyout Board
busyout board Field descriptions Port address (cabinet-carrier-slot-circuit) Port Name of maintenance object (WAE-PORT = wideband Maintenance Name access endpoint; TIE-DS1 = single port access endpoint) The alternate way of identifying the maintenance object - the Alt. Name extension number of the access endpoint. Test result: Pass, Fail, Abort Result Numeric code explaining why the release failed or aborted.
Page 254 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output from the busyout board 1c07 command, and assumes that board in cabinet 1, carrier c, slot 7 is an analog board with three administered ports. The responses display on a test-by-test basis with one line of data for each test result.
Page 255: Busyout Cdr-Link
busyout cdr-link busyout cdr-link This command busyouts a maintenance object associated with the specified call detail recording (cdr) link. Action/ Feature Object Qualifier Qualifier Description Logins Default Interactions busyout link-id Link identifier (primary or init Primary None cdr-link secondary) inads craft Examples: busyout cdr-link primary...
Page 256: Busyout Data-Module
Maintenance Commands and Trouble-Clearing Aids busyout data-module This command puts the specified data module in a maintenance busy state, even uninstalled data modules. No periodic or scheduled tests is performed on the busied out data module or data channel until it is released and no call processing can be executed on the data modules or over the data channels.
Page 257: Busyout Journal-Printer
busyout journal-printer Field descriptions Port address (cabinet-carrier-slot-circuit) or the data channel Port number The name of maintenance object Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object is The field contains station extension trunk xxx/yyy (xxx = trunk group, yyy = member private CO line P/xxx (xxx = private CO line group number) Test result: Pass, Abort, or Fail...
Page 258 Maintenance Commands and Trouble-Clearing Aids Action/ Feature Object Qualifier Qualifier Description Logins Default Interactions busyout pms-log Link to pms (in output, port init None See below journal- name for pms link =1) inads printer craft wakeup-log Link to the wakeup logging facility (in output, port name = Examples: busyout journal-printer...
Page 259: Busyout Link
busyout link busyout link This command places maintenance objects associated with a specified link in a maintenance busy state. No periodic or scheduled tests are performed on the busied out maintenance objects until they are released. The link is marked out of service and is inaccessible to call processing.
Page 260: Busyout Mis
Maintenance Commands and Trouble-Clearing Aids busyout mis This command places the management information system in the maintenance busy state. No periodic or scheduled maintenance is performed until it is released. When the object is busied out no call processing activity may be performed over the link.
Page 261: Busyout Modem-Pool
busyout modem-pool busyout modem-pool This command places specified installed and uninstalled modem pool groups or group members in the maintenance busy state. No periodic or scheduled tests are performed on the busied out modem pool groups or group members until they are released.
Page 262: Busyout Packet-Control
Maintenance Commands and Trouble-Clearing Aids Field descriptions Port address (cabinet-carrier-slot-circuit) Port Name of busied out maintenance object: MODEM-PT Maintenance Name Not applicable Alt. Name Test result: Pass, Abort, Fail Result Numeric code explaining why the release failed or aborted. Error Code Refer to the detailed list of codes by test number for each MO.
Page 263: Busyout Pms-Link
busyout pms-link Output The following example shows the output from the busyout packet-control 1A command. The responses display on a test-by-test basis with one line of data for each test result. busyout packet-control 1A SPE A COMMAND RESULTS Port Maintenance Name Alt.
Page 264 Maintenance Commands and Trouble-Clearing Aids For information on PMS, see the description of the ‘‘status pms-link’’ command. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions busyout Example: init none See below pms-link busyout pms-link inads craft Feature Interactions Maintenance of a particular component on a link sometimes interferes with the maintenance of the link itself.
Page 265: Busyout Port
busyout port busyout port This command places the specified port on a circuit pack in a maintenance busy state. No periodic or scheduled tests are performed on the busied out port until it is released. When the object is maintenance busy, it is deactivated (no call processing activity may include the busied object).
Page 266: Busyout Pri-Endpoint
Maintenance Commands and Trouble-Clearing Aids busyout pri-endpoint This command places all PRI endpoint ports (B-channels) associated with the specified PRI endpoint in a maintenance busy (system technician busy) state. No periodic or scheduled tests are performed on the busied out PRI endpoint ports until they are released.
Page 267: Busyout Sp-Link
busyout sp-link Field descriptions Port address (cabinet-carrier-slot-circuit) Port Type of busied out maintenance object: PE-BCHL Maintenance Name Extension number of PRI endpoint Alt. Name Test result: Pass, Fail, Abort Result Numeric code explaining why the release failed or aborted. Error Code Refer to the detailed list of codes by test number for each MO.
Page 268: Busyout Spe-Standby
Maintenance Commands and Trouble-Clearing Aids busyout spe-standby This command raises the Fault Severity Level of the Standby SPE (see reference 5) of the standby Switch Processing Element (SPE) by raising a Warning Off-board alarm against STBY-SPE. Because a Warning Off-board STBY-SPE alarm is defined to have the highest Fault Severity of all alarms the affect the health of an SPE (refer to the Reset System MUS), the chance that an SPE interchange will occur is diminished, but does not guarantee that an SPE...
Page 269: Busyout Station
busyout station Output The following example is a display of the busyout spe-standby command. busyout spe-standby SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code STBY-SPE PASS Command successfully completed Field descriptions Standby SPE cabinet and carrier location (01A or 01B) Port Always STBY-SPE Maintenance...
Page 270 Maintenance Commands and Trouble-Clearing Aids Output The following example is a display of the busyout station command. busyout station 1002 SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C1102 DIG-LINE PASS Command successfully completed Field descriptions Port address (cabinet-carrier-slot-circuit) Port Type of busied out maintenance object...
Page 271: Busyout Tdm
busyout tdm busyout tdm This command places the specified tdm bus in a maintenance busy state. No periodic or scheduled tests are performed on the busied out bus until it is released. When the object is maintenance busy it is deactivated (no call processing activity may include the busied object).
Page 272: Busyout Tone-Clock
Maintenance Commands and Trouble-Clearing Aids Field descriptions Port address and associated TDM number and bus (PNA or Port PNB) Not applicable Alt. Name Type of busied out maintenance object: TDM-BUS Maintenance Name Test result: Pass, Abort, Fail Result Numeric code explaining why the release failed or aborted. Error Code Refer to the list of codes by test number for each MO.
Page 273: Busyout Trunk
busyout trunk Field descriptions Tone/clock board address (cabinet-carrier) Port Circuit pack name: TONE-PT TDM-CLK TONE-BD Maintenance Name Not applicable Alt. name Test result: Pass, Abort, Fail Result Numeric code explaining why the release failed or aborted. Error Code Refer to the detailed list of codes by test number for each MO. busyout trunk This command places the specified installed or uninstalled trunk group or trunk group member in a maintenance busy state.
Page 274 Maintenance Commands and Trouble-Clearing Aids Output The following example is a display of the busyout trunk command. busyout trunk 78/1 SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C1505 CO-TRK 78/01 PASS Command successfully completed Field descriptions Port address (cabinet-carrier-slot-circuit) Port Type of busied out maintenance object.
Page 275: Cancel Hardware-Group
cancel hardware-group cancel hardware-group This command temporarily or permanently aborts the execution of a test hardware-group command. To resume testing, enter resume hardware-group or test hardware group. Feature Qualifier Inter- Action/Object Qualifier Description Logins Defaults actions cancel Examples: init none hardware-group cancel inads...
Page 276 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output from the change circuit-packs 1 command (SCC) All five pages are shown here. change circuit-packs 1 Page 1 of CIRCUIT PACKS Cabinet: 1 Carrier: A Cabinet Layout: single-carrier Carrier Type: processor Slot Code Name...
Page 277 change circuit-packs change circuit-packs 1 Page 3 of CIRCUIT PACKS Cabinet: 1 Carrier: C Cabinet Layout: single-carrier Carrier Type: port Slot Code Name Slot Code Name 11: TN754 DIGITAL LINE 01: TN748 TONE DETECTOR 12: TN753 DID TRUNK 13: TN742 ANALOG LINE 14: TN760 TIE TRUNK...
Page 278 Maintenance Commands and Trouble-Clearing Aids change circuit-packs 1 Page 5 of CIRCUIT PACKS Cabinet: 1 Carrier: E Cabinet Layout: single-carrier Carrier Type: port Slot Code Name Slot Code Name 01: TN570 EXPANSION INTF 02: TN747 CO TRUNK 03: TN747 CO TRUNK 04: TN747 CO TRUNK 05: TN747...
Page 279: Change Firmware Download
change firmware download change firmware download change firmware download Use change firmware download to view the following screen. change firmware download Page 1 of FIRMWARE DOWNLOAD Source Board Location: _____ Firmware Image File Name: ________________________________________ Target Board code: ______ Suffix: __ Firmware Vintage: ___ Schedule Download? y Remove Image File After Successful Download? n...
Page 280: Change Ip-Network-Region
Maintenance Commands and Trouble-Clearing Aids Field descriptions The C-LAN board location (ppcss) where the firmware image resides. Source Board Location Enter the firmware image file name to download. Firmware image file Firmware Image File Name names can be from 1 to 40 alphanumeric characters (i.e., printable characters, including blanks).
Page 281 See Avaya MultiVantage Administrator’s Guide for field definitions for this screen. Output change ip-network-region 1 Page 1 of IP Network Region Region: 1 Name: Audio Parameters Direct IP-IP Audio Connections? n Codec Set: 1 IP Audio Hairpinning? y...
Page 282: Change Synchronization
Maintenance Commands and Trouble-Clearing Aids change synchronization Each system contains a hierarchy of sources used for timing synchronization. DS1 inputs to the external stratum 3 clock affect stratum 3 synchronization hierarchy. Primary and secondary fields reflect Stratum 4 synchronization. If all fields are blank, the tone clock board within each PN provides timing for that PN.
Page 283 change synchronization change synchronization Page 1 of SYNCHRONIZATION PLAN SYNCHRONIZATION SOURCE (DS1 circuit pack location) Stratum: 3 Port Network: 1 Field descriptions Current synchronization stratum (3, 4) Stratum First choice system synchronization source (blank entry = no Primary synchronization); field valid only if stratum 4 synchronization is specified.
Page 284: Change System-Parameters Maintenance
Maintenance Commands and Trouble-Clearing Aids change system-parameters maintenance This command specifies and displays scheduled maintenance operations and maintenance support functions. It also activates and deactivates INADS alarm origination during repairs. To deactivate alarm origination: 1. Make a note of the current entries in the Alarm Origination and CPE Alarm fields so you can restore them later.
Page 285 change system-parameters maintenance Output The following output example shows a display of the change system-parameters maintenance command. change system-parameters maintenance Page 1 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS OPERATIONS SUPPORT PARAMETERS Product Identification: 1000000000 First OSS Endpoint: 5551212 Abbrev Alarm Report? y Second OSS Endpoint: 5551213 Abbrev Alarm Report? n Alarm Origination to OSS Numbers: both...
Page 286 Maintenance Commands and Trouble-Clearing Aids Indicates one of four options for alarm origination (neither): Alarm Origination to both = Major and Minor alarms result in an automatic call to OSS Numbers both administered OSS telephone numbers. = Major and Minor alarms result in an automatic first-only call to the first administered OSS number.
Page 287 To prevent customer login ID access to system administration Customer Access to INADS Port and maintenance interface control, set this field to no. Avaya services has sole access to this field. (n) Number of minutes that the system must wait before attempting...
Page 288 Maintenance Commands and Trouble-Clearing Aids Scheduled Maintenance An automated series of maintenance tests and operations runs daily according to the schedule and settings specified in the following fields. Table 8-1. Scheduled Maintenance Settings Hour and minute (24-hour notation) when daily scheduled Start Time maintenance starts The hour and minute when scheduled daily maintenance ceases.
Page 289 change system-parameters maintenance Table 8-1. Scheduled Maintenance Settings — Continued This field indicates if expansion links between port-networks EXP-LINK Interchange interchange as part of scheduled maintenance. The value, “daily”, means that EXP-LINK interchanges automatically occur everyday. The value “no'' means that EXP-LINK interchanges do not automatically occur as part of scheduled maintenance.
Page 290 Maintenance Commands and Trouble-Clearing Aids Table 8-1. Scheduled Maintenance Settings — Continued This field specifies extensions assigned to receive tie-trunk calls Test Type 100, from other switches that have test line origination capability. The Test Type system responds by sending a sequence of test tones. Test Type 102, Test 100 tests far end to near end loss and C-message by sending: Type 105...
Page 291 change system-parameters maintenance Table 8-1. Scheduled Maintenance Settings — Continued The extension used to set up a DSO loop around connection for Loop-Around testing non-ISDN DS1 trunks. The DSO Loop-Around Test Call Test Call feature is used primarily for testing DSO channels associated with Extension non ISDN-PRI trunks.
Page 292 Maintenance Commands and Trouble-Clearing Aids Page 2 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS MINIMUM MAINTENANCE THRESHOLDS ( Before Notification ) TTRs: 4 CPTRs: 1 Call Classifier Ports: 0 MMIs: 0 VCs: 0 TERMINATING TRUNK TRANSMISSION TEST (Extension) Test Type 100: Test Type 102: Test Type 105: ISDN MAINTENANCE ISDN-PRI TEST CALL Extension: _____...
Page 293 change system-parameters maintenance Output (page 3) change system-parameters maintenance Page 3 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS Modem Connection: external Data Bits: 8 Parity: none Modem Name: _______ RTS/CTS Enabled: \Q3 Auto Answer Ring Count (rings): S0=10 Asynchronous Data Mode: &M0&Q0 Dial Type: T DTE Auto-Data Speed: ______...
Page 294 Maintenance Commands and Trouble-Clearing Aids This field will configure the modem as an asynchronous Asynchronous communications device. This field is 8 characters long and is Data Mode case in-sensitive. (&M0&Q0) This option will adjust the speed of the data source (DTE) DTE Auto-Data UART to the outgoing (modem-to-modem) data rate.
Page 295 change system-parameters maintenance This field can be of particular importance when using a modem Adjustable that may be transferable from country to country. The intent of Make/Break this field is to control the make/break ratios of pulses and DTMF Ratio dialing.
Page 296: Clear Audits
Maintenance Commands and Trouble-Clearing Aids clear audits This command clears cumulative and/or peak hour’s data collected for each data relation audit since the last clear audits command. Using this command before the status audits command ensures that the status audits report reflects current conditions.
Page 297: Clear Interface
clear interface clear interface This command reintializes counter values maintained by the Processor Interface (PI) circuit pack. The status interface command displays the counters. The PI circuit pack is a front end processor that implements the packet and link layers of the BX.25 protocol and the ISDN procedure-D protocol.
Page 298: Clear Link
Maintenance Commands and Trouble-Clearing Aids clear link This command clears the counters associated with a numbered PPP C-LAN link. The clear clan-port command accomplishes the same thing. The statistical counters cannot be cleared for an Ethernet C-LAN link. Action/ Feature Object Qualifier Qualifier Description...
Page 299: Clear Port
clear port clear port This command removes maintenance marks from a port, freeing it for use. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions clear port location Port location (PCsspp) init none none inads Examples: cust clear port 01c1102 copy update-file In Duplex systems only, this command copies update files from the active SPE to the standby SPE.
Page 300: Disable Administered-Connection
Maintenance Commands and Trouble-Clearing Aids When checking software, the test compares the memory resident software version and the patch identifier. It also searches for the presence of field update files. If found, it compares the old and new patch identifiers to ensure that the same patch file id is loaded on each processor.
Page 301: Disable Firmware Download
disable firmware download disable firmware download disable firmware download This command stops the current firmware download. If a target board is currently downloading the download is first completed for the current board but the remaining boards are not downloaded. disable mst This command stops the message trace facility.
Page 302: Disable Synchronization-Switch
Maintenance Commands and Trouble-Clearing Aids disable synchronization-switch This command stops the automatic clock switching capability of the maintenance subsystem. The clock refers to the oscillator on a tone/ clock or DS1 interface. The synchronization subsystem (TDM bus clock, DS1 trunk board, and maintenance and administration software) provides error-free digital communication between the switch and other PBXs, COs, or customer equipment.
Page 303: Display Alarms
display alarms display alarms This command creates an Alarm Report. The user completes an option screen to select the parameters for the report. The system creates the reports from the logs of the maintenance subsystem. The subsystem monitors the system hardware and logs problems as errors or alarms. The type of alarm indicates the impact of the problem, as defined below: —...
Page 304 Maintenance Commands and Trouble-Clearing Aids System resets, that are less severe than a reboot, rarely affect the error and alarm logs. NOTE: If the error and alarm logs contain SYSTEM errors, then use display initcauses to search for information that the system could not log during reset operation.
Page 305 display alarms display alarms Page 1 of 1 ALARM REPORTS The following options control which alarms will be displayed. ALARM TYPES Active? y_ Resolved? n_ Major? y_ Minor? y_ Warning? y_ REPORT PERIOD Interval: m_ From: __/__/__:__ To: __/__/__:__ EQUIPMENT TYPE ( Choose only one, if any, of the following ) Cabinet: ____ Port Network: __ Board Number: _______...
Page 306 Maintenance Commands and Trouble-Clearing Aids Output After you complete the options screen, the system displays a 1- or 2-page Alarm Report. To toggle between the pages and to exit the report, use the keys described below: For 513 and 715 terminals, use F8 for NEXT PAGE PREV PAGE commands...
Page 307 display alarms Identifies the location of maintenance object, as follows: Alt Name Station = extension number Trunk = Group number (78/__) or group and member numbers (78/01) Private CO Line = private CO line (P) and group number. (P/xxx) Alarm level: MAJOR, MINOR, or WARNING Alarm Type Identifies the service state of the station and trunk ports, as Service...
Page 308: Display Cabinet
Maintenance Commands and Trouble-Clearing Aids display cabinet This command displays the cabinet description and location and the carrier description for a selected cabinet number. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none none cabinet...
Page 309 display cabinet Field descriptions Administered cabinet number Cabinet Type of cabinet (five-carrier or single-carrier-stack) Cabinet Layout Type of port network (processor or expansion) Cabinet Type Number of port networks (1 or 2) Number of Port networks Room where cabinet is located, administered on the cabinet form. Room Floor where cabinet is located, administered on the cabinet form.
Page 310: Display Capacity
Maintenance Commands and Trouble-Clearing Aids display capacity Use display capacity to show how you administered your system and provide a snapshot of the switch resource status. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none none...
Page 311 Field descriptions (page 1) AAR/ARS The number of route patterns. For more information, AAR/ARS Patterns see Administrator’s Guide for Avaya MultiVantage Software. Number of 12-character inserted-digit strings Inserted Digit available for AAR/ARS preferences. For more Strings information, see Administrator’s Guide for Avaya MultiVantage Software.
Page 312 The number of authorization codes used for security Authorization purposes. For more information, see Administrator’s Codes Guide for Avaya MultiVantage Software. Basic Call Management System (BCMS) The number of agents the Basic Call Management Measured Agents System (BCMS) is measuring.
Page 313 Administrator’s Guide for Avaya MultiVantage Software. The number of call pickup groups have been administered. Call Pickup For more information, see Administrator’s Guide for Avaya Groups MultiVantage Software. The maximum number of active calls at a given time. This...
Page 314 Data Parameters The number of connections between two access or data Administered endpoints. For more information, see Administrator’s Guide Connections for Avaya MultiVantage Software. For more information, see Administrator’s Guide for Avaya Alphanumeric MultiVantage Software. Dialing Entries Dial Plan This includes stations, data endpoints, hunt groups,...
Page 315 display capacity (Page 5) SYSTEM CAPACITY System Used Available Limit - - - - - - - - - - - - - HUNT GROUPS, SPLITS, OR SKILLS Groups/Splits/Skills: Administered Logical Agents: Administered Logical Agent-Skill Pairs: Logged-In ACD Agents: 5200 5200 Logged-In Advocate Agents: Logged-In IP-Softphone Agents:...
Page 316 The number of intercom groups set up within your Intercom Groups organization. Per System The number of modem pool groups. For more information, Modem Pool see Administrator’s Guide for Avaya MultiVantage Groups Per Software. System The number of PCOL trunk groups. For more information, Personal CO Line see Administrator’s Guide for Avaya MultiVantage...
Page 317 display capacity Trunks The number of allowed DS1 circuit packs. DS1 Circuit Packs The number of Incoming Call Handling Table ICHT For ISDN Trunks (ICHT) entries administered for trunk groups. The number of call-by-call trunk groups. ISDN CBC Service Selection Trunks The number of trunk groups administered.
Page 318 Maintenance Commands and Trouble-Clearing Aids The number of voice terminals not having an Stations Without Port administered port, such as AWOH. The number of ports used as conversion Other Stations resources, agent login ID, MASI, and analog announcements. The number of ports assigned by TTI TTI Ports features.
Page 319 display capacity Field descriptions (page 8) Total Subscribed Ports The number of subscribed radio controller Radio Controllers circuit packs. The total number of ports in the system. Station and Trunk Ports The number of subscribed wireless terminals. Wireless Terminals System-Wide Registration Counts The number of IP stations currently registered IP Stations in the system.
Page 320: Display Communication-Interface
Maintenance Commands and Trouble-Clearing Aids Field descriptions (page 10) Current System Information Software Load The current software load on which the system is running. Memory The system platform. Configuration Offer Category The system’s offer category. Last Translation Loaded Information Software Load The software load translations saved before upgrade or reboot.
Page 321: Display Communication-Interface Hop-Channels
display communication-interface hop-channels display communication-interface hop-channels The display communication-interface hop-channels command displays the translation data for hop channels. A hop channel is a bi-directional network channel between two interface links for DCS message hopping. A hop channel is used to tandem DCS messages from one interface link to another interface link. See also ‘‘status link n’’...
Page 322: Display Communication-Interface Links
Maintenance Commands and Trouble-Clearing Aids Output for Hop-channels qualifier When you enter the command display comm hop, the systems displays the Hop Channel Assignment screen, similar to the figure below. The number of the local processor channel, used to hop the interface link channels, is not shown. display communication-interface hop-channels Page 1 of...
Page 323 display communication-interface links Output The following example shows the output from the display communication-interface links command. display communication-interface links Page 1 of INTERFACE LINKS Link Enable Est Ext Type Destination DTE Conn Name Conn Number DCE Mod. 1: y 2991 ETHERNET ethernet on link 1 2: n...
Page 324: Display Communication-Interface Processor-Channel
Maintenance Commands and Trouble-Clearing Aids display communication-interface processor-channel This command displays the translation information for each of the local processor channels. A processor channel is one several data streams which are multiplexed by the X.25 protocol onto a single data link. The system has 128 total processor channels;...
Page 325 display communication-interface processor-channel Field descriptions Displays the BX.25 virtual channel number or the TCP/IP Proc Chan listen port channel to carry this processor (virtual) channel. Type y to enable a processor channel. Type n to disable a Enable processor channel. Identifies the switch application used over this link.
Page 326: Display Disabled-Tests
Maintenance Commands and Trouble-Clearing Aids display disabled-tests The display disabled-tests command lists the numbers for all maintenance tests that have been disabled by INADS. These tests are not available for background or demand testing. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions...
Page 327: Display Errors
display errors display errors This command creates an Alarm Report from a user-option screen to select the report parameters. The system creates the reports from the logs of the maintenance subsystem, which monitors the system hardware and logs problems as errors or alarms. Errors can result from in-line firmware errors, periodic tests, failures detected while executing a test command, software inconsistency, or a data audit discrepancy.
Page 328 Maintenance Commands and Trouble-Clearing Aids Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display high Highlights the time stamps on init all errors none errors resolution the Error Report for the first and inads displayed last occurrences of the error. craft cust print...
Page 329 display errors Field descriptions Enter a specific error type; press HELP in this field to view a list Error Type of codes. If the field is blank, the system displays all errors. Enter one: Error List active-alarms errors cleared-errors The title for the Hardware Error Report includes the name of the selected error list.
Page 330 Maintenance Commands and Trouble-Clearing Aids Form output After completing the options screen, the system displays a 1- or 2-page Hardware Error Report. To toggle between the pages and to exit the report, use the keys described below: For 513 and 715 terminals, use F8 for NEXT PAGE PREV PAGE commands...
Page 331 display errors Error number for the type of problem encountered. Use this error Error Type number in conjunction with the logical name information to determine the exact nature of the error. Additional information concerning the error condition. Like the Aux Data error type, this data is specific to the maintenance object type.
Page 332: Display Events
Maintenance Commands and Trouble-Clearing Aids The figure below is an example of an Hardware Error Report -- Active Alarms, using the high-resolution qualifier. When you enter the command display errors high-resolution, the system adds the Seq Cnt (sequence count) column. The number in the column indicates the order of errors logged within a second for the time stamps associated with the first occurrence and the last occurrence of an error.
Page 333 display events Input form The following entry form is displayed to allow limiting the report to events of a certain type or from a certain time period. Enter the desired parameters and press Enter. display events Page 1 of SPE B EVENT REPORT The following options control which events will be displayed.
Page 334 Maintenance Commands and Trouble-Clearing Aids Output See DEFINITY Communications System Generic 3 Call Vectoring and Expert Agent Selection (EAS) Guide, 555-230-520, for more information on how to interpret this report. In particular, the Event Data 2 field are associated with possible causes and repair strategies for the event.
Page 335 display events Table 8-2. Denied IP events Event Event Event Event Type Description Explanation Data 1 Data 2 1907 IP RRJ-Invalid Registration Rejected because the IP address RAS addr RAS address in the RRQ is invalid. that sent the 1908 IP RRJ-Invld call IP Registration Rejection because IP address...
Page 336 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1914 IP RRJ-ProdID Registration rejected because the T/S: Product Major version search fail search for registering application’s ID of the number Product ID failed.
Page 337 display events Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1923 IP RRJ-No E164 Registration rejected; no valid E.164 IP address number phone number available. The extension is not administered. 1924 IP RRJ-No GRQ Registration rejected;...
Page 338 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1930 IP RRJ-No voice Registration rejected: endpoint has IP address path spec neither an associated multimedia extension nor a specified voice path, hence, no audio path.
Page 339 display events Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1942 IP KA-from unreg Keep Alive registration request Endpoint IP address user rejected: unregistered extension. 1943 IP-KA-from unreg Keep Alive registration request Endpoint IP address SigGrp...
Page 340 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1954 IP GRJ-Invld auth Gatekeeper request rejected: no IP address algrthm compatible authentication algorithm exists between the endpoint and the gatekeeper.
Page 341 display events Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1963 IP LRJ-Build LCF Location Request rejected: failure to IP address build a Location Request Confirm (LCF) message (internal software error).
Page 342 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1976 IP ARJ-Endpt not Admission Request rejected: the IP address endpoint is not registered. 1977 IP ARJ-No avail Admission Request rejected: no IP address B-channel...
Page 343 display events Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 1989 IP URJ-Endpt not Unregistration Request rejected: IP address endpoint is not registered. 1990 IP URJ-No Unregistration Request rejected: no IP address endpoint ID endpoint ID provided.
Page 344 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 2002 IP URJ-Build UCF Unregistration Request rejected: IP address failure to build an unregistration request confirm (UCF) message (internal software error).
Page 345 display events Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 2010 IP FURQ-Restart Force Unregistration Request. cleanup Instruct the RAS manager to cleanup a UID that had just been registered prior to: a system reset a system restart...
Page 346 Maintenance Commands and Trouble-Clearing Aids Table 8-2. Denied IP events — Continued Event Event Event Event Type Description Explanation Data 1 Data 2 2018 IP FURQ-Mtc: Force Unregistration Request. H323/Vphone Maintenance has unregistered an H.323 or IP Softphone station. 2019 IP FURQ-Mtc: Force Unregistration Request.
Page 347: Display Failed Ip-Network-Region
display failed ip-network-region display failed ip-network-region The display failed network-region command will provide a list of the worst first 100 network regions with broken connectivity rank ordered by the worst to least worst. display failed-ip-network-region WORST NETWORK REGIONS Network Region:Number of Broken Paths Command: The network regions are ordered from worst to best, for example: 5:9 (i.e.
Page 348: Display Initcauses
Maintenance Commands and Trouble-Clearing Aids display initcauses The display initcauses command displays a history of recovery steps taken by the system. This command displays information for restarts of the active processor only. Each time the system performs some type of recovery (user request or a hardware or software problem), the recovery information is stored.
Page 349 display initcauses Output The following example shows the output from the display initcauses command. display initcauses INITIALIZATION CAUSES Cause Action Escalated Carrier Time Initialized 08/01 1:14 System Technician Request 08/01 2:14 System Technician Request 08/01 2:18 Sanity Timer Reset 08/02 6:03 Sanity Timer Reset 08/02...
Page 350 Maintenance Commands and Trouble-Clearing Aids Field descriptions Reason for the restart: Cause Active Down: (High or Critical Reliability system only) The Active SPE went into SPE Down mode. The Duplication Interface initiated an SPE-interchange to the Standby SPE. If this initcause triggers an SPE interchange when the Standby is NOT in Maintenance mode, the previous entry in the log may actually represent a restart that occurred on the Standby SPE.
Page 351 display initcauses LMM Request: A sanity time-out was requested by the LMM firmware. The three processor circuit pack LEDs blink until the sanity timer goes off. The LMM requests a restart like this when it gets into trouble, usually with memory. Maintenance Reset: The Maintenance/Test Processor or Duplication Interface reset the system.
Page 352 Maintenance Commands and Trouble-Clearing Aids SPE-Select Lead Change: (High or Critical Reliability system only) The system could not determine why the SPE changed its status from Active or Standby. However, this change usually indicates a transition from Active to Standby. If a High or Critical Reliability System does a PEI with a warm start, the system software often requests a Cold 2 restart to recover properly only minutes after the warm start has occurred.
Page 353 display initcauses LMM Put Fail: This initcause occurs when the LMM has failed to place the request for initcause message in the DPR. This could occur if the MTP does not respond to the DPR handshake. Level of Restart: Warm (escalation turned on). LMM Get Fail: This initcause occurs when the LMM does not receive a response to the request for initcause message from the MTP.
Page 354: Display Memory-Configuration
Maintenance Commands and Trouble-Clearing Aids display memory-configuration This command indicates the total memory available for the active, and if present, the standby processor(s). This command is a single page display with hidden fields for the standby-processor, if available. Action/ Qualifier Feature Object Qualifier...
Page 355: Display Node-Names
display node-names Output The following output example is for the display memory-configuration command when executed on the G3V9si platform with SPE duplication: display memory-configuration SP_A PROCESSOR MEMORY-CONFIGURATION (M bytes) SPE_A SPE_B Flash ROM: Total DRAM: SIMM A: SIMM B: SIMM C: Command successfully completed For the Simplex SPE configuration, the column under “SPE_B”...
Page 356 Maintenance Commands and Trouble-Clearing Aids Page 1 page 1 of 6 NODE NAMES Audix Name IP address 1. _______ ___.___.___.___ 2. _______ ___.___.___.___ 3. _______ ___.___.___.___ 4. _______ ___.___.___.___ 5. _______ ___.___.___.___ 6. _______ ___.___.___.___ 7. _______ ___.___.___.___ 8. _______ ___.___.___.___ Field descriptions (page 1) Identifies the name of the adjunct or switch node.
Page 357: Display Port
display port Field descriptions (page 2) Non-specific node name (up to 15 characters each) for CMS Name nodes, DCS nodes, and so forth. Valid entries are alpha-numeric and/or special characters for identification. IP address for the adjunct or switch. Enter 0 - 255 or leave IP Address blank.
Page 358 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for display port 1c0801. display port 1c0801 SPE A PORT INFORMATION Port: 01C0801 Equipment Type: Station Identification: 1021 Field descriptions Port address (cabinet-carrier-slot-circuit) Port: Hardware that is physically connected to the specified port. Equipment Type: Depends on the hardware that is physically connected to Identification:...
Page 359: Display Synchronization
display synchronization display synchronization This command calls up the synchronization form where the administered synchronization stratum and reference sources are displayed. (No changes can be made to the system synchronization with this command.) Action/ Qualifier Feature Object Qualifier Description Logins Defaults Interactions display...
Page 360 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for display synchronization. display synchronization Page 1 of SYNCHRONIZATION SOURCE (DS1 circuit pack location) Stratum: 4 Primary: Secondary: DS1 CIRCUIT PACKS Location Name Slip Location Name Slip 02B10 D92D1 ds1 2b10 02B11 d92D1 ds1 2b11 01C10 D92D1 ds1 1c10 01C11 D92D1 ds1 1c11...
Page 361: Display System-Parameters Duplication
display system-parameters duplication display system-parameters duplication This command displays the status (enabled or disabled) of Switch Processing Element (SPE) and Port Network Connectivity (PNC) duplication. The following must be duplicated: Each switch node record and every switch node with its duplicate (cabinet administration is a prerequisite) Every fiber link containing either an expansion interface circuit pack as an endpoint, or a DS1-C (fiber link administration is a prerequisite;...
Page 362: Display System-Parameters Maintenance
Maintenance Commands and Trouble-Clearing Aids Field descriptions Status of SPE duplication: y is enabled; n is disabled Enable Operation of SPE Duplication? Status of PNC duplication: y is enabled; n id disabled. This Enable Operation of PNC field appears when PNC Duplication is y on the Duplication?
Page 363 display system-parameters maintenance Output The following display shows a typical result when display system-parameters maintenance is entered. display system-parameters maintenance Page 1 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS OPERATIONS SUPPORT PARAMETERS Product Identification: 1000000000 First OSS Telephone Number: 5551212 Abbrev Alarm Report? y Second OSS Telephone Number: 5551213 Abbrev Alarm Report? n Alarm Origination to OSS Numbers: both...
Page 364 Maintenance Commands and Trouble-Clearing Aids display system-parameters maintenance Page 3 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS Modem Connection: external Data Bits: 8 Parity: none Modem Name: RTS/CTS Enabled: \Q3 Auto Answer Ring Count (rings): S0=10 Asynchronous Data Mode: &M0&Q0 Dial Type: T DTE Auto-Data Speed: Adjustable Make/Break Ratio:...
Page 365 display system-parameters maintenance One of four options for alarm origination (neither): Alarm Origination to both , all Major and Minor alarms result in an automatic OSS Numbers call to both OSS telephone numbers. Both OSS telephone numbers must be administered. first-only , all Major and Minor alarms result in an automatic call to the first OSS number only.
Page 366 INADS Port administration and maintenance interface, via the INADS port when using customer login ID’s. This field can only be activated by Avaya services through system-parameters maintenance administration. (n) Indicates the number of minutes that the system must wait...
Page 367 display system-parameters maintenance Scheduled Maintenance A series of maintenance tests and operations runs automatically every day according to the schedule and settings specified in the following fields. The hour and minute (24-hour notation) at which daily Start Time scheduled maintenance begins. (22:00) Time (hour and minute) when scheduled daily maintenance Stop Time stops.
Page 368 Maintenance Commands and Trouble-Clearing Aids When the number of touch tone receivers (TTRs) in service Minimum Threshold for falls below this number (4 to 200), a WARNING alarm is raised TTRs against TTR-LEV. These are also known as dual-tone multifrequency receivers (DTMRs). There are 4 TTRs on each TN748, TN718, TN420, or TN756;...
Page 369 display system-parameters maintenance Extension number for the test call. This test extension number DSO Loop-Around Test Call is used to establish a loop-around connection on the selected Extension trunk. The DSO Loop-Around Test Call feature is used primarily for testing DSO channels associated with non-ISDN-PRI trunks. The loop-around is activated by dialing the test extension number.
Page 370 Maintenance Commands and Trouble-Clearing Aids These fields indicate whether a Disk circuit pack is present in SPE Optional Boards the system, and which Packet Interface slots are administered. If a Packet Interface circuit pack is physically present, the Packet Interface field is y when the system boots, and no change to that field is allowed.
Page 371 display system-parameters maintenance This option will adjust the speed of the data source (DTE) UART to Auto-Data the outgoing (modem-to-modem) data rate. So, at maximum this Speed speed would be 9600 baud. This field is 6 characters long and is case in-sensitive.
Page 372: Display Test-Schedule
Maintenance Commands and Trouble-Clearing Aids This field can be of particular importance when using a modem that Adjustable Make/Break may be transferable from country to country. The intent of this field is Ratio to control the make/break ratios of pulses and DTMF dialing. The Intel product information has support for the different make/break options for pulse dialing only.
Page 373 display test-schedule Output The following is the output from the display test-schedule n command. Page 1 of 1 ATMS TRUNK TEST SCHEDULE Schedule No: __ Schedule Time: __:__ Schedule Test Days Interval: __ Schedule Date: __/__/__ SU: _ TU: _ TH: _ SA: _ Duration: __...
Page 374 Maintenance Commands and Trouble-Clearing Aids One of the following types of test to be performed on the trunk Test Type group/members in this schedule: full runs the most comprehensive test and collects all associated measurements for each TTL type. supv performs a supervision test and only confirms the presence of the test set at the far end.
Page 375: Display Time
display time display time Use display time to see but not change the system time on the time form. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none Date and time time inads are generally schedule...
Page 376: Download Update-File
Maintenance Commands and Trouble-Clearing Aids download update-file The update file is transferred to the switch asynchronously from either an INADS host or a personal computer (PC) using the XMODEM protocol. Remote download Remote users can dial into the switch by either using the “call” command (from an INADS host) or by dialing the switch directly with a modem.
Page 377 download update-file There is no feedback to the user on the status of the standby copy. If an error is encountered during the copy or validation process on the standby, an error is logged in the software error log. Because the data consistency audit discovers that the two patch files are inconsistent, the user must manually copy the valid file on the active processor over to the standby processor.
Page 378 Maintenance Commands and Trouble-Clearing Aids The flash checksum test acts as a backup check to ensure that the entire field update file was applied correctly. It can fail because of a bad checksum update from a poorly constructed update file or because the patching operation has aborted.
Page 379 download update-file Error on Application of the Patch A patch may not have been applied for the following reasons: 1. The memory card is write-protected. Remove this protection and issue a reset system x command. 2. The patch identifiers are inconsistent. Run list configuration software and compare the old patch identifier with the values in the update file.
Page 380 Maintenance Commands and Trouble-Clearing Aids Inconsistent software versions on a duplicated switch As indicated by a failure in the data consistency test, inconsistent software can be caused by problems in copying the update file to the standby or validation test failures on the standby.
Page 381: Enable Administered-Connection
enable administered-connection enable administered-connection This command restarts scheduled and periodic maintenance for a single or all administered connections and can be used to track the maintenance processing of administered connections without interference from other maintenance processing. This command also restarts the processing of in-line errors for all or the selected administered connection.
Page 382: Enable Mst
DS1 alarms before a customer resolves facility problems (for example, a T1 trunk that has developed an off-board condition). Improved control over internal (Avaya) problems that cannot be resolved immediately. For example, the command can be used to suspend Alarm Origination for a bad circuit pack detected late Friday night when dispatch personnel cannot respond until Monday.
Page 383: Enable Synchronization-Switch
enable synchronization-switch Action/ Qualifier Feature Object Qualifiers Description Logins Defaults Interactions enable board/port Physical location of init Both on- and none suspend- location the hardware inads off-board alm- orig craft alarms if the off-board-o cust off-board- optional; if not rcust only keyword specified, both on-and expires-in-...
Page 384: Enable Test-Number
Maintenance Commands and Trouble-Clearing Aids enable test-number This command enables a previously disabled test number. At the next request by maintenance or the technician, this test number runs. Action/ Qualifier Feature Object Qualifier Description Logins Defaults Interactions enable number The test number to init none display...
Page 385: Get Ethernet Options
get ethernet options Field descriptions Board Type For VAL, this field is TN2501. FW Vintage The firmware vintage number HW Signature The hardware signature number Suffix The circuit pack suffix code letter Date The date the firmware file was created or transferred to the circuit pack Timestamp The time that the firmware file was created or transferred to the...
Page 386: Get Vector
Maintenance Commands and Trouble-Clearing Aids Field descriptions Auto Negotiation Yes means that the system automatically negotiates the highest possible network speed. No means that the Speed and Duplex fields are manually assigned. Speed 10Mbps 100Mbps N/A (not available) Duplex Half Full N/A (not available) Link Integrity...
Page 387 get vector Output get vector GET RESULTS Core Dump Vector Set Vector Command Option spe-active Core Dump Time SPE_A SPE_B Field descriptions A hexadecimal value representing the condition(s) that cause(s) a core Core Dump dump. This hexadecimal value is a bit map of the four reset conditions (from Vector least to most significant bit): warm start...
Page 388 Maintenance Commands and Trouble-Clearing Aids Table 8-3. Vector-Condition Mapping — Continued value warm-start cold-2 cold-1 reboot Continued on next page The user-specified SPE prior to the core dump. For simplex SPE Vector systems this field is always unless the vector is cleared or spe-active Command not set.
Page 389: List Configuration
list configuration list configuration Hardware configuration reports list, for each circuit pack in the group specified, the type, code, suffix, and vintage of the requested circuit packs as installed in the switch, and all ports assigned to the circuit pack. Action/ Feature Object...
Page 390 Maintenance Commands and Trouble-Clearing Aids Hardware Groups Enter one of the following hardware groups: Displays all circuit packs administered and/or physically carriers all inserted in the port, switch node, and control carriers on the system. Displays all assigned ports on the circuit pack specified by board PCSS cabinet, carrier, and slot.
Page 391 list configuration Output The following display shows the output from list configuration all. list configuration all Page SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01C02 ATM PNC EI TN2305 HW02 FW102 01C03 ATM PNC EI TN2305 HW02 FW102 01C04...
Page 392 Maintenance Commands and Trouble-Clearing Aids The following display shows output from the list configuration ds1 command. list configuration ds1 SYSTEM CONFIGURATION - DS1 Circuit Packs Location Code Vintage Signaling Name CSU MOD 01B05 TN464F 000002 isdn-pri 120A1 01B06 TN464D 000002 isdn-pri 01B10 TN767C...
Page 393: List Configuration License
list configuration license list configuration license The License Serial Numbers screen displays the license file serial number(s) embedded in the current License File. In duplicated systems, use the list configuration license long command to display the serial number of both active and standby hardware from one of the following circuit packs: TN2404 Vintage 3 Processor (csi) TN2402 Vintage 3 Processor (si)
Page 394: List Config Software-Version
Maintenance Commands and Trouble-Clearing Aids list config software-version This command displays Software version numbers and compatibility indexes of the software load modules stored in system memory (RAM) and on the MSS devices (tape). The dates and times when translation and announcement data were last saved to the MSS.
Page 395 list config software-version The following shows the output from list configuration software-version. list configuration software-version Page SOFTWARE VERSIONS SPE-A SPE-B UPDATE FILE Creation (GMT) Date: 4:17 pm FRI NOV 3,1995 4:17 pm FRI NOV 3, 1995 Old Version Tape: G3V4i.03.0.044.0 G3V4i .03.0.044.0 Old Identifier Tape: none none...
Page 396 Maintenance Commands and Trouble-Clearing Aids Translation Date Displays information related to the translation files as Section stored in memory and the MSS. Date and time when translation data was last read from the Memory Resident MSS into memory. This is stored in SPE memory and is not modified by changes to translation data.
Page 397 list config software-version Announcement Date Displays information related to the announcement files. Section Information is displayed for the memory resident copy as well as the corresponding MSS file The last date and time that announcement data was saved Mem Card Resident to the memory card.
Page 398: List Directory
Maintenance Commands and Trouble-Clearing Aids deferred partially applied — an error condition that is valid only when a update that is in the process of being applied fails. Check the validity of the update file that was sent, and then check the hardware error log for tape errors, and follow standard maintenance procedures.
Page 399: List Disabled-Mos
list disabled-mos list disabled-mos This command displays all the MOs that have been maintenance disabled. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions list print Report sent to printer. init none none disabled- inads schedule Schedule execution of the command.
Page 400: List History
Maintenance Commands and Trouble-Clearing Aids list history The list history command generates a log listing of the most recently completed “data affecting” administration and maintenance commands. Data commands are those administration and maintenance commands that change the data state associated with any object and qualifier in the system. Administration data commands affect translation data, while maintenance data commands affect state information.
Page 401 list history Also, if you use set time to alter the system clock, it could look as if the recent change history report is not in true LIFO order. Output list history list history Page 1 Page HISTORY HISTORY Date of Loaded Translation: 10:08pm Wed Feb 14,2001 Date of Loaded Translation: 10:08pm Wed Feb 14,2001 Date Time Date Time...
Page 402: List Ip-Route
Maintenance Commands and Trouble-Clearing Aids list ip-route This command displays a list of the IP routes from the Avaya DEFINITY Server out to the LAN. Enter the “board” parameter and specify the C-LAN circuit pack for the IP routes you want to see (for example, list ip-route board UUCss).
Page 403 list ip-route Specifies the desirability of the IP route in terms of the efficiency of Metric data transmission over the route. Valid entries are (a simple route) (a complex route). A metric value of is used only when the switch has more than one C-LAN board installed. A metric-1 route diverts usage of the route to a metric - 0 route, if available.
Page 404: List Isdn-Testcall
Maintenance Commands and Trouble-Clearing Aids list isdn-testcall This command displays the ISDN-PRI trunks in use for ISDN-PRI test calls. This is useful to determine which trunk is in use for an outgoing ISDN-PRI test call. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions...
Page 405: List Marked-Ports
list marked-ports list marked-ports This command lists all the ports that have been marked unusable with the mark port command (maximum of fifteen marked ports per page). Action/ Qualifier Feature Object Qualifier Description Logins Defaults Interactions list marked- print Report sent to printer. init none none...
Page 406: List Measurements Clan Ethernet
The primary use of this command is to quickly and unambiguously determine if the fault lies within the Avaya-provided equipment or if the fault is with the LAN or LAN administration to which the Avaya DEFINITY Server switch is connected.
Page 407 list measurements clan ethernet Output The following example shows the output from list measurements ethernet. list measurements clan ethernet 1C1017 Page 1 of x Switch Name: sierra Date:4:07pm MON AUG 01,1999 C-LAN ETHERNET PERFORMANCE MEASUREMENT DETAILED REPORT Date Time CRC Check Collision Count total delta...
Page 408: List Measurements Clan Ppp
Maintenance Commands and Trouble-Clearing Aids list measurements clan ppp This command provides a 24-hour history of important packet-level statistics from which you can infer some LAN performance characteristics. For example, Invalid frames—the number of frames that are misaligned CHAP failures—Challenge Handshake Authentication Protocol—the number of attempts for ppp authentication that failed High Cyclic Redundancy Check (CRC)—detects and corrects errors on every frame) errors could suggest that the connection may be “noisy”...
Page 409 list measurements clan ppp Output The following example shows the output from list measurements clan ppp. list measurements clan ppp 1C1001 Page 1 of x Switch Name: sierra Date:02/02/1999 C-LAN PPP PERFORMANCE MEASUREMENT DETAILED REPORT Date Time CRC Check Invalid Frame CHAP Failures Total Delta...
Page 410: List Measurements Clan Sockets
Maintenance Commands and Trouble-Clearing Aids list measurements clan sockets list measurements clan sockets x List measurements clan sockets works on IP Media Processor & Medpro. Action/ Qualifier Feature Object Qualifier Description Logins Default Interactions list hourly Lists the measurements none measurements <CCccss>...
Page 411 list measurements clan sockets Output The following screen shows the Measurements CLAN SOCKETS hourly - Page 1. list measurements clan sockets hourly 01B12 Page Switch Name: Date: 5:27 pm WED MAR 26, 1992 CLAN SOCKETS HOURLY REPORT (Last 24 Hours) Socket Socket Meas...
Page 412 Maintenance Commands and Trouble-Clearing Aids The following screen shows Measurements CLAN SOCKETS summary yesterday-peak - Page 1. list measurements clan sockets summary yesterday-peak Page Switch Name: Date: 5:27 pm WED MAR 26, 1992 CLAN SOCKETS PEAK REPORT Peak Hour: 0400 Socket Socket Meas...
Page 413: List Measurements Ds-1
list measurements ds-1 list measurements ds-1 This command lists performance measurements of a DS-1 link indicating the quality of the DS-1 physical interface between the system and a far end system. The ds1 summary option provides a summary report while ds1 log provides a detailed report.
Page 414 Maintenance Commands and Trouble-Clearing Aids Output list measurements ds1 summary 2a19 SPE A Switch Name: Date: 1:25 pm THU APR 16, 1992 DS-1 Link Performance Measurements Summary Report Counted Since: 1:20 pm THU APR 16, 1992 Number of Seconds Elapsed Into Current 15-min Interval: 323 Total of Valid 15-min Intervals in Past 24-hr Period: Total of Current...
Page 415: List Measurements
list measurements ds-1 The date(Date), end time(Time), and error count (Count; from 0 Worst_15-Min_ Interval to 900 in increments of four) of the 15-minute interval in the previous 24-hour period that contains the maximum value for each of the four error categories. The sum of all valid 15-minute counts for the previous 24-hour Total of 24-Hour Count...
Page 416 Maintenance Commands and Trouble-Clearing Aids The value of the severely errored seconds counter for the specified SEVERELY ERR SECS 15-minute interval (0 - 900 or N/A if data for the 15-minute interval is invalid). The value of the failed seconds counter for the specified 15-minute FAILED SECONDS interval (0 - 900 or N/A if data for the 15-minute interval is invalid).
Page 417: List Measurements Ip Codec
list measurements ip codec list measurements ip codec list measurements ip codec x Supports IP media processing resource measurements. The list measurements ip codec command works on IP Media Processor & Medpro. Action/ Feature Object Qualifier Qualifier Description Default Interactions list hourly <region Lists the measurements for...
Page 418 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the IP Codec Hourly Output For Region 4. list measurements ip codec hourly 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP CODEC RESOURCE HOURLY REPORT G711 G723/9 --------------------- ------------------------- Meas...
Page 419 list measurements ip codec The total number of times an IP media processor port was needed in G.711 Out of Reg peg the region for a G.711 call, but was successfully allocated to a resource in another region. Out of Region does not include denials. If “Network regions are interconnected”...
Page 420 Maintenance Commands and Trouble-Clearing Aids The reports list measurements ip codec summary today-peak and list measurements ip codec summary last-hour are similar to the above report. The following screen shows the Sample IP Codec detail yesterday-peak Output For Region 4. list measurements ip codec detail 4 yesterday-peak 4 Switch Name: Date: 5:32 pm...
Page 421: List Measurements Ip Dsp-Resource
list measurements ip dsp-resource list measurements ip dsp-resource list measurements ip dsp-resource x Supports IP media processing resource measurements. The list measurements ip codec command works on IP Media Processor & Medpro. Action/ Feature Object Qualifier Qualifier Description Default Interactions list hourly Lists the measurements for...
Page 422 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the dsp-resource Hourly Output For Region 4. list measurements ip dsp-resource hourly 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP DSP RESOURCE HOURLY REPORT Meas DSP Usage In Reg Out of Denied...
Page 423 list measurements ip dsp-resource Total number of times an IP media processor port in the region was In Reg allocated to a call. Range: 0-65535. The total number of times an IP media processor port was needed in Out of Reg peg the region for a call, but was successfully allocated to a resource in another region.
Page 424 Maintenance Commands and Trouble-Clearing Aids The following example shows the IP dsp-resource detail yesterday peak Output For Region 4. list measurements ip dsp-resource detail 4 yesterday-peak 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP DSP RESOURCE DETAIL REPORT Meas DSP Usage In Reg...
Page 425: List Measurements Ip-Signaling-Group
list measurements ip-signaling-group list measurements ip-signaling-group list measurements ip-signaling-group x Shows the 10 worst signaling groups for each hour of today, starting with the most recent whole hour. The forms for the today and yesterday qualifiers are 24 pages, one for each hour. The groups for each hour will be rank-ordered from worst to least worst based on the Hour Average Latency.
Page 426 Maintenance Commands and Trouble-Clearing Aids The following example shows the list measurements ip-signaling-group last-hour command. list measurements ip-signaling-group last-hour Page 1 of 24 SPE A Switch Name: Date: 6:28 pm THU FEB 4, 1997 IP SIGNALING GROUPS LATENCY AND LOSS REPORT LAST FULL HOUR 10 WORST PERFORMING IP SIGNALING GROUPS RANK ORDERED WORST TO LEAST WORST Hour...
Page 427: List Mst
list mst Field descriptions The group number, rank ordered. Sig Grp No The network region of the group. Region The average latency for the whole hour. Hour Average Latency (ms) The number of packets sent during the whole hour. Hour Packets Sent The percent lost packets for the whole hour (if 100% the Hour Packets% corresponding latency is shown as ****).
Page 428 Maintenance Commands and Trouble-Clearing Aids Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions continuous Display updates as new messages enter the trace buffer (FIFO). This option is most useful in conjunction with “auto-page.” The command terminates only when canceled by the user. LIFO Newest message displayed first.
Page 429 list mst Output list mst MST DATA Number Date/Time Type Message 12/21/90 14:30:21.220 00 00 74 17 08 02 00 11 05 04 03 80 90 a2 18 03 a1 83 86 70 01 80 96 28 0d 73 74 61 74 69 6f 6e 20 35 31 30 30 31 14:30:22.420 00 00 74 17 08 02 80 11 02 18 03 a9 83 86...
Page 430 Maintenance Commands and Trouble-Clearing Aids Table 8-4. Summary of MST Message Types — Continued Code Description 0x23 IMT miscellaneous hooks (dbug) 0x24 Hardware error log 0x25 PREC message 0x26 CMS outgoing (individual) 0x27 CMS incoming (individual) 0x30 CCMS uplink message 0x31 CCMS downlink message 0x32...
Page 431 list mst Table 8-4. Summary of MST Message Types — Continued Code Description 0x72 Time changed while trace enabled 0xA0 X.25 Outgoing application data message 0xA1 X.25 Incoming application data message 0xA2 X.25 Application error message 0xB0 X.25 Outgoing session layer control message 0xB1 X.25 Incoming session layer control message 0xCF...
Page 432 Maintenance Commands and Trouble-Clearing Aids MST message types contain a version number. Whenever the structure of the MST message changes, the version field in the MST buffer is changed. Version 1 displays a blank in the version field which is immediately after the MST message type field.
Page 433 list mst Vector Event Trace (D92 Only) Message type: 0x11 Message format: Message[1-4] = cid (defined in $BASEPJ/hdrs/capro.h) Message[5-6] = event Message[7+] = auxiliary data (based on event) Events are defined in $BASEPJ/hdrs/evnt_defs.h. Events based on the call_p will have the following auxiliary data: Message[7-8] = vector number Message[9-10]...
Page 434 Maintenance Commands and Trouble-Clearing Aids 0x22 - IMT crec Message format: Message[1+] = call record (defined as CALLR typedef in $BASEPJ/hdrs/callr.h) 0x23 - MT_IMT (miscellaneous IMT hooks) This message type is for miscellaneous IMT hooks. The only sub-type currently available is for a debug button (dbut). The button number is provided in the debug button MST message so that more than one button can be administered (through IMT) to convey different meanings.
Page 435 list mst serv_d (map-type messages): Table 8-5. Message[1-4] = user identifier Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h) Message[7] = STIM type Message[8-11] = service identifier Message[12] = port network number Message[13] = endpoint number Message[14] = angel number Message[15] = circuit number Message[16+] = message...
Page 436 Maintenance Commands and Trouble-Clearing Aids CCMS Message types: 0x30 uplink 0x31 downlink Message format: Message[1] = port network number Message[2] = endpoint number Message[3] = angel number Message[4] = circuit number Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h) Message[7] = message length Message[8] = angel id Message[9+]...
Page 437 list mst Message format: Message[1] = port network number Message[2] = endpoint number Message[3] = angel number Message[4] = circuit number Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h) Message[7-10] = link identifier Message[11+] = standard packet message ASAI ASAI messages listed on the MST screen consist of a 4 octet header and a variable length body.
Page 438 Maintenance Commands and Trouble-Clearing Aids 0x50 - ASAI level 2 uplink primitive Message[1] = Port Network Number of ASAI port Message[2] = reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = SAPI Message[6] = TEI Message[7,8]...
Page 439 list mst Message[7-10] = Link ID Message[11] = Uplink encode 0x01 - ASAI Link State 0x02 - TEI Management Message 0x03 - XID Message Message[12] = ASAI Link State: 0x00 - the link has gone down 0x01 - the link has come up 0x02 - the link id has changed 0x03 - the link has gone hyperactive 0x04 - the link has recovered...
Page 440 Maintenance Commands and Trouble-Clearing Aids NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0x.ff Message[9] = Downlink encode 0x01 - ASAI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[10] = ASAI Link Events:...
Page 441 list mst Message[7-10] = Link ID NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0xff 0xff 0x.ff Message[11] = Downlink encode 0x01 - ASAI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[12] = ASAI Link Events:...
Page 442 Maintenance Commands and Trouble-Clearing Aids 0x53 - ASAI maintenance downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI 3 ort Message[5] Message[6+] = standard or abbreviated ASAI message format 0x54 - ASAI unrecognized uplink Message[1] = Port Network Number of ASAI port...
Page 443 list mst 0x55 - ASAI unrecognized downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = failure reason Failure reasons 1 - link flow controlled 2 - internal software error - see software error log 3 - packet interface problem - see error log Message[6+]...
Page 444 Maintenance Commands and Trouble-Clearing Aids 0x57 - ASAI Association downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = association type Message[6+] = standard or abbreviated ASAI message format 0x58 - ASAI error uplink Message[1]...
Page 445 list mst ISDN 0x60 - ISDN PRI uplink Message[1] = Port Network Number of D-channel port Message[2] = Reserved Message[3] = Carrier Address of D-channel port Message[4] = Port number of D-channel port Message[5+] = standard ISDNPRI format NOTE: In abbreviated format, the header of the Q.931 message, the cause IE (if present) and the channel id Information Element (IE) (if present) are the only IEs present.
Page 446 Maintenance Commands and Trouble-Clearing Aids 0x64 - ISDN BRI uplink Message[1] = Port Network Number of BRI port Message[2] = Reserved Message[3] = Carrier Address of BRI port Message[4] = Port number of BRI port Message[5] = SAPI Message[6] = TEI Message[7,8] = Link ID Message[9+]...
Page 447 list mst Message[7-10] = Link ID Message[11+] = standard ISDNBRI format NOTE: In abbreviated format, the header of the Q.931 message, the cause IE (if present) and the channel id IE (if present) are the only IEs present. An additional cancel byte (0xCA) may be present after the standard ISDNBRI formatted message if the message was not sent.
Page 448 Maintenance Commands and Trouble-Clearing Aids Message[7-10] = Link ID Message[11] = Uplink encode 0x01 - BRI Link State 0x02 - TEI Management Message 0x03 - XID Message Message[12] = BRI Link State: 0x00 - the link has gone down 0x01 - the link has come up 0x02 - the link id has changed 0x03 - the link has gone hyperactive 0x04 - the link has recovered...
Page 449 list mst NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0xff Message[9] = Downlink encode 0x01 - BRI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[10] = BRI Link Events: 0x02 - link release request...
Page 450 Maintenance Commands and Trouble-Clearing Aids NOTE: The cancel byte is present if the message was built, but could not be sent. 0x6C - ISDN PRI level 2 uplink primitive Message[1] = Port Network Number of D-channel port Message[2] = Reserved Message[3] = Carrier Address of D-channel port Message[4]...
Page 451 list mst 0x6F - ISDN BRI Unrecognized Messages Message[1] = Port Network Number of BRI port Message[2] = Reserved Message[3] = Carrier Address of BRI port Message[4] = Port number of BRI port Message[5] = SAPI Message[6] = TEI Message[7,8] = Link ID Message[9] = type of failure...
Page 452 Maintenance Commands and Trouble-Clearing Aids General 0x71 - GAP marker Message[1] = GAP reason Message[2] = GAP count (since last clear - high byte) Message[3] = GAP count (since last clear - low byte) GAP reasons: 0x01 - disabled, disable mst command executed 0x02 - disabled, mst timer expired 0x03 - disabled, buffer full on no-wrap 0x04 - disabled, restart occurred...
Page 453 list mst 0xA0 - X.25 outgoing application message Message[1] = processor channel number Message[2] = sequence number Message[3] = buffer id Message[4] = 0x00 Message[5+] = application message Application messages will contain the session layer data headers and the data. In abbreviated mode, the application message is not saved.
Page 454 Maintenance Commands and Trouble-Clearing Aids Version 2: Message[1] = processor channel number Message[2] = application error/notification Message[3+] = pm stimulus ignored (For message[2] == 0x10 only) Errors/Notifications: R1/R3: 0x01 - no outgoing buffer available 0x05 - pvc session down 0x06 - pvc session up 0x07 - pvc session connect 0x08 - pvc session restart 0x09 - message buffer overload uplink...
Page 455 list mst session layer message type: 0x00 - session connect 0x01 - session accept 0x02 - session reject 0x03 - session disconnect 0x04 - reserved 0x05 - reserved 0x06 - resynch 0x07 - reserved 0x08 - resynch acknowledge In abbreviated mode, the session layer message is not saved. 0xB1 - X.25 incoming session layer control message Message[1]...
Page 456 Maintenance Commands and Trouble-Clearing Aids Processor Channel Control 0xD0 - outgoing control message Message[1] = processor channel number Message[2] = message event Message events for R1: 0x00 - Request Reset of Logical Channel 0x05 - Ack. Reset of Logical Channel 0x06 - Flow Control Uplink 0x07 - Release Uplink Flow Control 0x0A - Flow Control Downlink...
Page 457 list mst Link Control 0xD2 - link control Message[1] = interface link number Message[2] = message event R1 Message events: 0x00 - Busy Out Link 0x01 - Release Busied Out Link 0x0A - Level 3 Restarting R3 Message events: 0x00 - Stop Link 0x01 - Start Link 0x0A - Level 3 Restarting 0xD3 - link status (R3 Only)
Page 458 Maintenance Commands and Trouble-Clearing Aids Timers: 0x00 - ST2(session connect) 0x01 - ST3(retransmission) Message[3] = countdown from A1 0x02 - ST4(resynchronization) No count 0x03 - ABT1(abort session 1) Message[3] = protocol machine state where timeout occurred 0x04 - ABT2(abort session 2) Message[3] = protocol machine state where timeout occurred 0x05 - State Timer...
Page 459 list mst X.25 Errors 0xF0 - X.25 Error Message (Outgoing Message Lost) Note that 0xA2, 0xF0 and 0xF2 messages will be turned on by responding ‘y’ to the ‘Application Errors?’ field. Version 1: Message[1] = processor channel number Message[2] = sequence number Message[3+] = message Version 2:...
Page 460: List Registered-Ip-Stations
Maintenance Commands and Trouble-Clearing Aids 0xF1 - Unrecognized X.25 Messages Message[1] = processor channel number Message[2] = Failure type Message[3+] = session message Failure types: 0x00 - Reserved 0x01 - Unknown session layer message type 0x02 - unrecognized control message 0xF2 - BX.25 Error Message (DIP ICOM Record Aborted) R2 only...
Page 461: List Skill-Status
list skill-status list skill-status This command displays administration and status data about skilled hunt groups. The list skill-status command supports “start” and “count” command line options. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions list xx count xx is a hunt group number init none none...
Page 462 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output of list skill-status for three PAD skills with the Dynamic Percentage Adjustment enhancement enabled. list skill-status SKILL STATUS S C O D D D Grp Name/ Grp L S C T P Q Service Level 1 Level 2...
Page 463: List Station
list station list station list station list station movable - shows extensions that have the Automatic Moves field set to always or once list station movable once - shows extensions available to be moved once list station movable done - shows extensions that had the Automatic Moves field set to once, and have moved list station movable always - shows extensions available for moves anytime list station movable error- shows mis-administered, non-serialized...
Page 464: List Suspend-Alm-Orig
Maintenance Commands and Trouble-Clearing Aids list suspend-alm-orig This command lists active entries in the Suspend Alarm Origination table. Even though this command only lists active entries, an entry that expires during the list process still appears in the output. If the Suspend Alarm Origination table is empty, the output contain only the title and field headings.
Page 465: List Testcalls
list testcalls list testcalls This command generates an Automatic Transmission Measurement System (ATMS) report. The ATMS allows the voice and data trunk facilities to be measured for satisfactory transmission performance. The performance of the trunks is evaluated according to measurements produced by a series of analog tests and are compared against user-defined threshold values.
Page 466 Maintenance Commands and Trouble-Clearing Aids Action/ Qualifiers/ Object Options Qualifier/Option Description count count Specify (limit) the number of records displayed. number print Report sent to printer schedule Schedule execution of the command. The command is placed in the command queue and is executed at the specified time. The information displayed is sent to the system printer instead of the screen.
Page 467 list testcalls Output The following example is of the output for list testcalls detail grp 80. list testcalls detail grp 80 Page SPE A ATMS MEASUREMENT REPORT Group: 80 Type: co Vendor: TTL Type: 105-w-rl THRESHOLD VALUES Loss dev at 1004Hz-loss 404Hz 2804Hz C-msg C-ntch SRL SRL Noise Noise...
Page 468 Maintenance Commands and Trouble-Clearing Aids Transmission tests at low frequency. These tests measure a maximum Loss dev at 404Hz positive and negative deviation of +9 and -9 dB from the 1004-Hz loss measurements. Transmission tests at high frequency. These tests measure a maximum Loss dev at 2804Hz positive and negative deviation of +9 and -9 dB from the 1004-Hz loss...
Page 469: List Trace
list trace The number of trunks that failed a marginal threshold, but not an Trunks Failed Marginal unacceptable threshold according to the threshold values defined Threshld on the trunk group form. This is taken from the unacceptable threshold administered on the Trunks Failed Unaccept Trunk group form.
Page 470 Maintenance Commands and Trouble-Clearing Aids list trace station 52501/a Page 1 of 1 SPE B LIST TRACE Time Data 15:12:07 Calling party station 57405 cid 0x20 15:12:09 dial 52501 15:12:09 ring station 52501 cid 0x20 15:12:09 ATM setup PN01-0081 to PN03-0045 15:12:09 ATM setup PN03-0046 to PN01-0082 15:12:11...
Page 471: Mark Port
mark port mark port The mark port command marks faulty ports as defective to prevent their use in other administrative operations (for example, adding a data-module or station). Ports on any type of circuit pack may be marked except for installed circuit packs that are administered automatically (for example, Tone Detector, Tone Generator, Announcement, Speech Synthesizer, Call Classifier and Maintenance/Test circuit packs).
Page 472 Maintenance Commands and Trouble-Clearing Aids Qualifier Description split Specifies that the command display status information for a specified split number (an ACD hunt group). split number The split’s identity to the switch and BCMS; an ACD hunt group number (split number). This parameter is entered only when the “split”...
Page 473 monitor bcms Field descriptions The current date and time which is updated every 30 seconds or when Date the UPDATE key is pressed. The name of the split being reported, if no name is administered then SPLIT the split extension is displayed in the form “EXTxxxxx”. Splits are displayed in split number order.
Page 474 Maintenance Commands and Trouble-Clearing Aids monitor bcms split 1 Page 1 of SPE A BCMS SPLIT (AGENT) STATUS Split: 1 Split Name: hunt group 1 Date: 9:02 TUE OCT 22 1991 Calls Waiting: Oldest Call: 0:00 0=Staffed 0=Avail 0=ACD 0=ACW 0=AUX 0=Extn 0=OtherSplit...
Page 475 monitor bcms The number of agents in this split currently in AUX work for this split. If an agent is on another split’s call or in After Call Work (ACW) for another split, this agent is not considered in AUX work and is not be recorded here.
Page 476: Monitor Health
Maintenance Commands and Trouble-Clearing Aids monitor health Use monitor health to see the current system alarm summary, maintenance busy summary, user summary, critical system status, and cabinet status that are updated each minute. Action/ Qualifier Feature Object Qualifier Description Logins Default Interactions monitor...
Page 477 monitor health Field descriptions The number of logged major alarms (0 – 200). Major The number of logged minor alarms (0 – 200). Minor Number of warnings logged in the alarm file (0 – 200). Warning Number of busied out maintenance trunks. Trunks Number of busied out maintenance stations.
Page 478: Monitor Security-Violations
Maintenance Commands and Trouble-Clearing Aids Current setting of the emergency transfer switch for each cabinet. Five Emerg Trans options are available: auto-on (“auto+” or “a+”), auto-off (“auto-” or “a-”), “on”, “off”, and “n.a.”. If “auto+” or “auto-” option are enabled, emergency transfers automatically activate when cabinets fail (“+”...
Page 479 monitor security-violations Output The following example is a display of the monitor security-violations command. monitor security-violations SPE A SECURITY VIOLATIONS STATUS Date: 9:12 MON DEC 30 1991 SYSTEM MANAGEMENT VIOLATIONS REMOTE ACCESS VIOLATIONS Date Time Login Port Date Time TG No. 12/30 09:12 init MGR1...
Page 480: Monitor System
Maintenance Commands and Trouble-Clearing Aids monitor system The monitor system view1 and view2 commands summarize the system’s condition. This on-line status report automatically updates every minute (or by pressing the UPDATE key) until the command is canceled by pressing the CANCEL key.
Page 481 monitor system Output Below are displays of monitor system view 1 and monitor system view 2. monitor system view1 ATTENDANT STATUS MAINTENANCE STATUS Console no. # of alarms for trunks: 4 Activated: 1 2 3 4 5 6 # of alarms for stations: 2 # of alarms for other res: 1 Deactivated: 7 8 First OSS number has been informed? n...
Page 482 Maintenance Commands and Trouble-Clearing Aids Field descriptions A list of console numbers that are activated or deactivated. Console # The attendant console is active. An attendant console activated if: Activated: its handset/headset is plugged in it is not busied out, and the system is in day service and the console is a day or day/night or principle console, or the system is in night service and the console is a night or day/night console.
Page 483 monitor system The following example is a display of the monitor system conn command. Time Slot Status Bus Status State *Idle Count State Maint Avail Normal Avail Maint Avail Normal Avail Maint Avail Normal Avail Maint Normal *Callrate: Maint *Interval: Normal *Max_callrate:45 Maint...
Page 484 Maintenance Commands and Trouble-Clearing Aids Total number of requested fiber time slots. This field increments each tot_fts_ time a fiber time slots is allocated since the last top of the hour measurement polling. Three values appear; one for each requested pnn.
Page 485: Monitor Traffic
monitor traffic monitor traffic Use monitor traffic to see information on the number of trunk group and hunt group calls waiting to be serviced, and the time the oldest call in the group has been waiting for service. Action/ Feature Object Qualifier Qualifier Description...
Page 486 Maintenance Commands and Trouble-Clearing Aids Output The following output example is a display of monitor traffic hunt-groups. monitor traffic hunt-groups HUNT GROUP STATUS 22:49 SAT DEC 31 1988 LCIQ LCIQ (#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting) (LCIQ: Longest Call In Queue in seconds) Field descriptions...
Page 487: Monitor Trunk
monitor trunk monitor trunk This command displays internal software status information. This command helps to locate facilities to which the trunk is communicating. If a trunk group number is entered without a member number, and with or without “/”, it is member 1. If a trunk group and member number are both entered, status for specified members displays.
Page 488: Netstat Ip-Route
Maintenance Commands and Trouble-Clearing Aids In-service/active, in-service/idle, out-of-service, out-of-service-NE Service State (Near End), out-of-service-FE (Far End), maint-NE/active, maint-FE/active, maint-NE/idle, maint-FE/idle, pending-in-service, pending-maint, or disconnected. NE (Near End) and FE (Far End) refer to the “end” of the trunk that has placed the facility in its current state. This field identifies maintenance testing that occurs on the trunk.
Page 489: Netstat Arp
netstat arp Field descriptions The location of the circuit pack that provides the interface for the Board/Pt route. Display-only field showing the IP address of each route’s destination. Destination The Destination is administered on the Node Name screen. On the Node Name screen, “Default” in the Destination field administers the default route.
Page 490 Maintenance Commands and Trouble-Clearing Aids Instructions 1. At a system terminal type netstat-arp and one of the following qualifiers: unsorted (Screen 8-17) ip-sorted 8-18) (Screen mac-sort 8-19) (Screen ck-dup Screen 8-20) and press Enter Output netstat arp unsorted netstat arp unsorted Page 1 of Net to Media Table...
Page 491 netstat arp netstat arp ip-sort netstat arp unsorted Page 1 of Net to Media Table C-LAN Device IP Address Phys Addr Type 12D15 135.009.004.007 00:20:fc:1e:13:f9 15D14 135.009.004.021 08:00:20:87:f0:87 13D15 135.009.004.026 00:80:c7:ac:f0:dc 05A10 135.009.004.039 00:50:04:d9:b2:b0 11E09 135.009.004.041 00:a0:c9:a4:76:4d 12E14 135.009.004.044 00:50:da:ba:c7:93 11D10 135.009.004.052 00:50:04:d9:b1:4f...
Page 492 Maintenance Commands and Trouble-Clearing Aids The entries shown in bold with “DUP” by the Net Seq field indicate duplicate IP addresses found in the ARP data. Use the Field descriptions (netstat arp) further interpret this report. NOTE: The report contains as many pages as are required to display all of the data received from the C-LAN circuit packs.
Page 493: Ping
ping ping When debugging connectivity problems, a ping only indicates low-level connectivity. If an external ping works but higher-level applications such as DCS, CMS, or INTUITY do not, then you can only assume that there is connectivity to the board. Interrogate the switch for other clues as to why the higher-level application is not working.
Page 494 Maintenance Commands and Trouble-Clearing Aids ping ip-address This command “pings” the given IP address of the destination to ping. The command returns the port used to perform the test the pass/fail results of the test the round-trip delay time for successful tests the error code on tests that failed.
Page 495 ping If the packet length is not specified, the default is 64 bytes. You can add the packet-length qualifier and the packet size (64-1500 bytes) to the other ping commands. Some examples include: ping node-name packet-length 800 ping ip-address 24.103.5.7 packet-length 100 ping board UUCSS packet-length 1000 NOTE: The default DiffServ and 802.1p/Q parameters downloaded to a IP Media...
Page 496 Maintenance Commands and Trouble-Clearing Aids Error messages The system returns error messages listed in Table 8-7. Table 8-7. Ping command error messages Message Interpretation The system cannot find the IP address. www.xxx.yyy.zzz Internet address not assigned The IP address is not in the route table of the Internet address not specified board.
Page 497: Recycle Carrier
recycle carrier recycle carrier This command recycles power for specified carriers. When power units are replaced in carriers, this command recycles that carrier’s power. Processor carriers and their duplicates and EPN control carriers or SCC carriers cannot be recycled. Carriers with active, recycled EIs, experience disrupted communications with their cabinets.
Page 498: Refresh Route-Table
Maintenance Commands and Trouble-Clearing Aids Output The following output example displays recycle carrier c. recycle carrier c TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code CARR-POW PASS Command successfully completed Field descriptions Port address (cabinet-carrier) for tested maintenance objects. This Port field displays cabinet and carrier values.
Page 499 refresh route-table Instructions 1. At the switch terminal type refresh route-table and one of the following qualifiers: (Screen 8-22) location (CCcss) See examples in the Board Location field in Screen 8-23. and press Enter refresh route-table all Page 1 of C-LAN Board Location Number of Routes Removed Number of Routes Added...
Page 500: Refresh Spe-Standby
Maintenance Commands and Trouble-Clearing Aids Field descriptions (refresh route-table) The physical location of the circuit pack in CCcss C-LAN Board format (cabinet, carrier, slot) Location The number of routes that were deleted from the Number of Routes TN799 (C-LAN) route tables Removed The number of routes that were added from the TN799 Number of Routes...
Page 501: Release Access-Endpoint
release access-endpoint release access-endpoint This command removes all ports associated with the specified access endpoint from a maintenance busy state. Periodic and scheduled tests subsequently resume on the released ports. Maintenance completes background initialization testing on the released ports. For details of the test sequence, refer to [3]. Action/ Feature Object...
Page 502: Release Board
Maintenance Commands and Trouble-Clearing Aids release board This command activates administered maintenance objects on the circuit pack at specified locations. Tests are executed to ensure its usability. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release board location Physical location: PCsspp init none none...
Page 503: Release Cdr-Link
release cdr-link release cdr-link This command removes maintenance objects associated with specified call detail recording (cdr)-links from a maintenance busy state. These links provide asynchronous data connections from switches to peripherals; they are composed of a: Far end data module Simulated data channel on a PKTINT board Manager that initiates and maintains the link Controller/protocol that services the link...
Page 504: Release Data-Module
Maintenance Commands and Trouble-Clearing Aids release data-module This command activates the specified data module (or data channel). Hardware tests are executed to verify that the equipment is functioning. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release extension Extension number associated with init none none...
Page 505: Release Journal-Printer
release journal-printer release journal-printer This command activates maintenance objects associated with a specified pms-log or wakeup-log link. Execute hardware tests to verify that equipment is functioning. For information on journal printer links, see ‘‘busyout pms-link’’. For information on journal printers, see ‘‘status journal-link’’.
Page 506: Release Link
Maintenance Commands and Trouble-Clearing Aids release link The release link command activates MOs associated with a specified link. Hardware tests are executed to verify that equipment is functioning properly. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions release link-id Number associated with each link (1–8).
Page 507: Release Mis
release mis release mis The release mis command activates management information systems. Hardware tests are executed to verify that equipment is functioning properly. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release mis init none none inads craft cust rcust Output The following output example is a display of release mis.
Page 508: Release Modem-Pool
Maintenance Commands and Trouble-Clearing Aids release modem-pool The release modem-pool command deactivates specified modem pool groups or group members. Specifying group numbers, member numbers releases single group members. Specifying modem pool group numbers releases members in a modem pool group. Feature Action/Object Qualifier...
Page 509: Release Packet-Control
release packet-control release packet-control This command activates the packet-control circuit pack, and reestablishes each terminated point-to-point signaling link on this packet-control. It is the complement to busyout packet-control, which deactivates packet control and destroys terminated point-to-point signaling links. Action/ Feature Object Qualifier Qualifier Description...
Page 510: Release Pms-Link
Maintenance Commands and Trouble-Clearing Aids release pms-link The release pms-link command deactivates MOs that are associated with a property management system link.These links provide asynchronous data connections from switches to peripherals. They are composed of: Far end data module Simulated data channel on a NETCON board Manager that initiates and maintains the link Controller/protocol that services the link Feature...
Page 511: Release Port
release port release port The release port command deactivates specified ports on circuit packs. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release port location Physical location: PCsspp init none none inads Examples: craft release port 01c1101 release port 02c1501 Output The following output example is a display of the release port 1c0701 command.
Page 512: Release Pri-Endpoint
Maintenance Commands and Trouble-Clearing Aids release pri-endpoint The release-PRI endpoint command removes PRI endpoint ports (B-channels) associated with specified PRI endpoint from maintenance busy states. Periodic and scheduled tests resume on released ports. The switch attempts to negotiate with the far-end PRI terminal adapter activating PRI endpoint port (B-channel). Maintenance does background initialization testing on released ports.
Page 513: Release Sp-Link
release sp-link release sp-link The release sp-link command reactivates busied out system printer links and resolves active alarms for system printer links. The system printer link is a link from the switch to an external printer. Administering system printer extensions to call system printers creates the links. Feature Action/Object Qualifier...
Page 514: Release Spe-Standby
Maintenance Commands and Trouble-Clearing Aids release spe-standby The release spe-standby command removes busyout statuses of standby SPEs. Memory shadowing restores, a memory refresh of the standby SPE occurs, and 1 minute later the equivalent of scheduled standby SPE maintenance returns the standby SPE’s Fault Severity Level to its appropriate value.
Page 515: Release Station
release station release station This command removes specified administered extensions from a maintenance busy state. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release station extension extension number associated with the init none none desired voice terminal inads craft Examples: cust release station 10020 release station 32770...
Page 516: Release Tdm
Maintenance Commands and Trouble-Clearing Aids release tdm This command removes specified tdm buses from a maintenance busy state. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions release port- specifies the Port Network number of the init none System tears network TDM bus to be released.
Page 517: Release Tone-Clock
release tone-clock release tone-clock This command removes specified tone/clocks from maintenance busy states. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release location Physical location: PCsspp init 1 (one) none tone-clock inads Examples: craft release tone-clock c Output The following output example is a display of the release tone-clock 1a command. release tone-clock 1a COMMAND RESULTS Port...
Page 518: Release Trunk
Maintenance Commands and Trouble-Clearing Aids release trunk The release trunk command removes specified trunk groups or trunk group members from a maintenance busy state. Specifying the group number, releases a single group member and the member number. Specifying the trunk group number releases members in a trunk group.
Page 519: Remove File
remove file remove file remove file [path] board ppcss This command requests the board ppcss to remove the file given by path. If the file does not exist on the source board’s filesystem, an error message, file not found is displayed on the SAT. To remove a file in a subdirectory, specify the entire path starting at “/”.
Page 520: Reset Board
Maintenance Commands and Trouble-Clearing Aids reset board This command performs a soft reset of every specified, administered port on the port circuit pack. Ports must be busied out before the port circuit pack resets. WARNING: This command is service disrupting and may cause extraneous alarms. Feature Action/Object Qualifier...
Page 521: Reset Interface
reset interface reset interface This command resets the Processor Interface circuit pack, reads its associated software from tape, restarts applications processes, re-establishes permanent switched calls, and sets up each enabled link. If the interface cannot be established, a Major alarm raises on the interface and all enabled links deactivate. When the Distributed Communications System (DCS), Audio Information Exchange (AUDIX), or Call Management System (CMS) are initially administered, links for these applications and submitting the form restarts the interface.
Page 522: Reset Maintenance
Maintenance Commands and Trouble-Clearing Aids reset maintenance This command resets technician-specified EPN maintenance circuit packs. Specifying cabinets 2 or 3 resets EPN maintenance circuit packs in carrier “a” of the specified cabinet. This command also drops a SAT terminal session on the reset EPN maintenance circuit pack.
Page 523: Reset Spe-Standby
reset spe-standby reset spe-standby The reset spe-standby command converts standby SPEs from standby mode to maintenance mode with the defined restart level. This command applies to high or critical reliability systems. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions reset level 1 = Warm Restart init...
Page 524 Maintenance Commands and Trouble-Clearing Aids All successful reset system commands log users off. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions reset system level See below init none see below interchange inads Examples: health-override craft reset system 1 reset system 2 reset system interchange health-override level...
Page 525: Reset System
reset system Maintenance On/Off Fault Severity Restart Object Alarm Level Board Level Level PI-BD MAJOR or MINOR PKT-CTRL MAJOR ON or OFF PKT-CTRL MINOR ON or OFF PI-PT MAJOR DATA-CHL MINOR DATA-CON MINOR DATA-BD MINOR MEM-CARD MINOR ON or OFF PR-MAINT MINOR A reset system interchange command aborts if:...
Page 526: Reset System 3
Maintenance Commands and Trouble-Clearing Aids reset system 3 This command has been modified to require an additional parameter, but only if the reset level is 3. The reset system 3 command includes the periodic synchronization of translations in a ATM WAN spare processor (WSP). When you issue this command, you must indicate whether you want to preserve the license or not: reset system 3 preserve-license—the License File information is retained...
Page 527: Reset Translation-Id
This command resets the translation-ID on the translation card(s) to match the processor(s), saves translations to the memory card, and restores use of the add, change, remove, and duplicate commands. NOTE: This command can be executed only by Avaya Services. Feature Action/Object Qualifier...
Page 528: Restore Announcements
Maintenance Commands and Trouble-Clearing Aids restore announcements This command copies announcement data from the active MSS devices to announcement boards. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions restore print Report sent to printer. init Tape-based: see below announcem inads Announcement schedule]...
Page 529 restore announcements To prepare for a failure, users should copy announcement files to announcement boards. If errors result from hardware or firmware failures, MSS software logs hardware errors with maintenance. When errors occur, the system continually attempts to download boards in 10-minute intervals until a download succeeds, announcements record, or downloads initiate from the SAT.
Page 530: Resume Hardware-Group
Maintenance Commands and Trouble-Clearing Aids resume hardware-group The resume hardware-group command resumes the previous test hardware-group command its canceled position. Entering another test hardware-group disables the resume hardware-group command. A canceled test hardware-group command appears as “canceled” on the status hardware-group screen.
Page 531 save announcements Simplex In a simplex system, no options for the save announcements command exist. This command saves announcement files to the MSS device. Duplex If no options are specified, the system saves announcements to both processors’ MSS devices. Action/ Feature Object Qualifier...
Page 532 Maintenance Commands and Trouble-Clearing Aids The standby processor must be in service with shadowing enabled, so that the system can save announcements to the standby processor. When MSS devices on both processors in High or Critical Reliability Systems are specified, the save announcements command saves announcement data from announcement boards to active MSS devices, then to standby MSS devices.
Page 533: Save Translation
save translation save translation This command allows users to save to tape or memory card the in-memory translation data. This command runs as part of scheduled maintenance and/or on demand by the technician. All translation data in memory during system operation is volatile, meaning that if the switch goes down, the system loses all data.
Page 534: Set Boot-Image
Maintenance Commands and Trouble-Clearing Aids save translation SAVE TRANSLATION Processor Command Completion Status Error Code SPE-A Success SPE-B Success Command Successfully Completed Field descriptions Identifies the processor carrier where translation data Processor saves. (SPE-A, or SPE-B.) Displays a variety of messages, identifying the Command Completion Status success or failure of the command.
Page 535: Set Ethernet-Options
set ethernet-options set ethernet-options Use this command to manually or automatically set the ethernet connection parameters. NOTE: The ethernet port must be both administered and busied out before you can issue this command. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions set ethernet- location...
Page 536: Set Expansion-Link
Maintenance Commands and Trouble-Clearing Aids set expansion-link The set expansion-link command sets the Expansion-Interface Link between: the PPN and an EPN two EPNs to a specific Interface Link circuit pack between PPN and EPN. NOTE: This command can corrupt any active data links between the PPN and an EPN or between two EPNs.
Page 537: Set Options
set options Form Input The following example is a display of set options. set options Page 1 of ALARM REPORTING OPTIONS Major Minor On-board Station Alarms: Off-board Station Alarms: On-board Trunk Alarms (Alarm Group 1): Off-board Trunk Alarms (Alarm Group 1): On-board Trunk Alarms (Alarm Group 2): Off-board Trunk Alarms (Alarm Group 2): On-board Trunk Alarms (Alarm Group 3):...
Page 538 Maintenance Commands and Trouble-Clearing Aids The first page of the Alarm Reporting Options Form, provides the following alarm options: the four trunk alarm severity groups, the adjunct alarms, off-board DS1 alarms, and PI-LINK alarms, memory card translation capacity alarms, and other off-board alarms.
Page 539 set options Trunk alarms have four alarm severity groups with administrable alarm options in the categories listed below. For G1, technicians can administer alarm options on a system-wide basis for the following categories: Major on-board trunk alarms Minor on-board trunk alarms Major off-board trunk alarms Minor off-board trunk alarms Technicians assign alarm severity options to the following Adjunct categories:...
Page 540 Maintenance Commands and Trouble-Clearing Aids Station MOs Affected By This Command NOTE: Although alarms on some MOs appear as warnings, they should be investigated with user-reported problems. Analog Lines (ANL-LINE, ANL-NE-L, ANL-16-L) Digital Lines (DIG-LINE) Hybrid Lines (HYB-LINE) ISDN-BRI Lines (BRI-PORT, BRI-SET) If more than 75% of the members of the trunk group alarm, minor alarms escalate to major alarms.
Page 541 NOTE: Although alarms on some MOs appear as warnings, the alarms should be investigated with user-reported problems. ASAI Adjunct (ASAI-ADJ) Avaya Adjunct Port (ATT-PORT) Ethernet ASAI Port (LGATE-PT) Ethernet ASAI Adjunct (LGATE-AJ) Ethernet Avaya Port (ATTE-PT) Ethernet Avaya Adjunct (ATTE_AJ) ISDN-BRI Ports connected to Adjuncts (ABRI-PORT) Adjuncts are administered as stations;...
Page 542: Set Signaling-Group
Maintenance Commands and Trouble-Clearing Aids Other MOs Affected by this Command NOTE: Although alarms on some MOs appear as warnings, the alarms should be investigated with user-related problems. EPN Maintenance Circuit Pack (MAINT) Expansion Interface (EXP-INTF) ISDN-PRI Signaling Group (ISN-SGR) Journal Printer (JNL-PRNT) PMS Link (PMS-LINK) PMS log printer (PMS-LOG)
Page 543: Set Synchronization
set synchronization set synchronization This command sets DS1 trunks or active tone/clock circuit packs that supply references for synchronization. The set synchronization command works after the disable synchronization command disables synchronization. Technicians may administer DS1 trunks or active tone/clocks with the set synchronization command.
Page 544: Set Tdm
Maintenance Commands and Trouble-Clearing Aids set tdm This command establishes the TDM bus on a port network that houses control channels and dedicated tones. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions set tdm port specifies the Port Network number of the TDM init none see below...
Page 545: Set Time
set time set time This command allows system technicians to change the day of the week, the day of the month, the month, year, hour, and minute. The second field resets to zero (0) whenever the time on the clock is altered, but cannot be modified by the technician.
Page 546: Set Tone-Clock
Maintenance Commands and Trouble-Clearing Aids Field descriptions Monday through Sunday. Day of the Week: 1-31. The system also checks for leap year. Day of the Month: January through December. Month: 1970-2999 Year: 0-23. Hour: 0-59 Minute: The system sets this field to zero when the time of day clock is Second: set.
Page 547: Set Vector
set vector set vector This command specifies restart levels for core dumps. This command places core dumps on primary Mass Storage System (a tape in a tape system and core dump memory cards in a memory card system) devices for later examination. The set vector command allows technicians to tailor restart levels that copy memory to primary Mass Storage System devices.
Page 548 Maintenance Commands and Trouble-Clearing Aids Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions set vector spe-standby see below. init spe-standby none spe-active inads SIMPLEX SYSTEM Examples: (High or spe-maint craft set vector f Critical set vector 9 Reliability DUPLEX SYSTEM Examples: Systems) set vector f spe-standby set vector f spe-active...
Page 549: Status Access-Endpoint
status access-endpoint spe-standby The default option for a High or Critical Reliability System. If a restart occurs on active SPEs and the corresponding vector bit is set, a core dump occurs on the standby SPE (after the standby SPE has performed a memory refresh). spe-active Option for a High or Critical Reliability System;...
Page 550 Maintenance Commands and Trouble-Clearing Aids Output The following output example is a display of the status access-endpoint 22502 command. Assume that access endpoint ports for extension 22502 are in cabinet 1, carrier C, slot 11, circuit 1 to 6 — that access endpoints are connected on an active call to ports 7 to 12 of the board in location 1B19 (cabinet 1, carrier B, slot 19).
Page 551: Status Administered-Connection
status administered-connection status administered-connection The status administered-connection provides automatic end-to-end connections between two access/data endpoints. Action/ Feature Object Qualifier Qualifier Description Logins Default Interactions status number assigned to an administered init none none administered number connection. inads -connection craft print reports print to SAT printers.
Page 552: Status Attendant
Maintenance Commands and Trouble-Clearing Aids status attendant This command diagnoses internal software. This command help to locate facilities to which the attendant console communicates. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions status console number assigned to an attendant (1 –16). init none none...
Page 553: Status Audits
status audits status audits This command displays results of Data Relation Audits that are built into the switch. Data Relation Audits check for inconsistencies between selected data items in the switch, and report inconsistencies. Data Relation Audits are useful during development and testing phases of projects to uncover software errors. In the field they help the switch to recover from data corruption before service is interrupted.
Page 554 Maintenance Commands and Trouble-Clearing Aids Action/ Feature Object Qualifier Qualifier Description Logins Default Interactions status peak-hour Data collected since the last reboot or since init none see below audits the last clear audits cumulative command. inads cumulative Data for the peak hour since the last reboot or since the last clear audits cumulative or clear audits peak-hour command.
Page 555 status audits Output The following example is a display of status audits. status audits cumulative AUDIT STATUS INFORMATION Start Date: 13:00 MON MAR 19 1990 # of Audit Cycles Completed: 67532 Audit # Cycles # Cycles Could # Cycles First Most Recent Name Fixed Data...
Page 556 Maintenance Commands and Trouble-Clearing Aids Field descriptions Date and time that interval begins. Start Date “cumulative” = date and time of the last reboot or execution of clear audits cumulative. “peak-hour” = date and time of the beginning of the peak hour since the last reboot or execution of a clear audits cumulative or clear audits peak-hour.
Page 557 status audits Table of Audits The following table shows the names of the audits that are run as part of time available maintenance, the audit number (pname) and a short description of each audit. These audits execute using lname MO_DR_AUDIT (8192). These audits may execute using the test MO command with lname 8192, pname “audit number,”...
Page 558 Maintenance Commands and Trouble-Clearing Aids Audit Audit Name Number Description Data module connections audit CO-ADM Coverage group administration audit CO-CALLS Coverage group calls audit CPROC Call process/call record audit CPTRTAB Call Progress Tone Receiver Table Audit CPTR-SID Call progress tone receiver audit CPWAKEUP Wake up call process audit CR-AUDIT...
Page 559 status audits Audit Audit Name Number Description LOG-A MDM error/alarm log audit MAP-HMM HMM map status table audit MCT-ADM Malicious call trace administration audit MIS-FAC MIS facility state audit MP-ADM Modem pool group administration audit MP-CALLS Modem pool group calls audit MSGQ-HMM HMM map request queue audit MST-LOG...
Page 560 Maintenance Commands and Trouble-Clearing Aids Audit Audit Name Number Description S-TAB Service Table Audit TEGLK TEG member lock audit TKLK Trunk lock audit TONE-TS Tone Time Slot Subtable Audit TR-ADM Trunk group administration audit TR-CALLS Trunk group calls audit TR-QUE Trunk group queue audit TSC-PRI ISDN-PRI TSC resource audit...
Page 561: Status Bri-Port
status bri-port status bri-port This command displays the service state, maintenance state and layer 1 state of an ISDN-BRI port. This form also displays information about point-to-point signaling links that transport over the port. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions status bri-port...
Page 562 Maintenance Commands and Trouble-Clearing Aids BRI Layer 1 (physical) state on the port. Valid states are “activated,” Layer 1 State “pend-activation,” and “deactivated.” “activated” state = layer 1 frames are passing between the port and BRI endpoints. “pend-activation” state = the port is in-service, the layer 1 interface device is on, layer 1 frames are sending to the BRI endpoints connected to this port, but BRI endpoints are not responding.
Page 563 status bri-port Status Interpretation The following table provides information on the status bri-port form. Table 8-10. Status BRI-Port Command Interpretation Endpoint Voice Service Types Range Layer 2 State Extension SPID Description /Recommendation ASAI, 0-126 Assigned blank blank Transitory state for BRI endpoints and ASAI adjuncts.
Page 564 Maintenance Commands and Trouble-Clearing Aids Table 8-10. Status BRI-Port Command Interpretation — Continued Endpoint Voice Service Types Range Layer 2 State Extension SPID Description /Recommendation ASAI 0-63 Established blank blank Transitory state for ASAI adjuncts. ASAI signaling is connects at Layer 2.
Page 565 status bri-port Table 8-10. Status BRI-Port Command Interpretation — Continued Endpoint Voice Service Types Range Layer 2 State Extension SPID Description /Recommendation BRI, blank Technicians conduct SPID ASAI Established facilitation tests on the port. Links are not associated with BRI port endpoints.
Page 566 Maintenance Commands and Trouble-Clearing Aids Table 8-10. Status BRI-Port Command Interpretation — Continued Endpoint Voice Service Types Range Layer 2 State Extension SPID Description /Recommendation 0-126 blank Transitory state for BRI endpoints (cont’d) Assigned which support MIM initialization. 2. Wait for five seconds and repeat the command.
Page 567 status bri-port Table 8-10. Status BRI-Port Command Interpretation — Continued Endpoint Voice Service Types Range Layer 2 State Extension SPID Description /Recommendation ASAI 0-126 Hyperactive ignore ignore Link has sent too many messages per unit time. Signaling suspends. System timeouts in 60 seconds and attempts reactivate the link.
Page 568: Status Card-Mem
Maintenance Commands and Trouble-Clearing Aids status card-mem Memory cards are portable, compact memory cards that contain banks of flash EPROM chips. Non-volatile memory cards are eraseable and randomly programmed with user data. Main memory stores system software in its “flash” section.
Page 569 status card-mem Feature Interactions If the Announcement feature is unavailable in the system features configuration, the Data Present field is always “n” for the “announcements” file. The Announcement feature requires a memory card with a minimum capacity of 4 MB. If the memory card is less than 4 MB, Announcements cannot be save in the memory card.
Page 570 Maintenance Commands and Trouble-Clearing Aids Table 8-11. Capacity of Memory Card Card Size User Customer File Names 8 Mb With Announcements translation/ announcements 16 Mb DEFINITY Wireless Business translation/ announcements/firmware Systems 48 Mb System Upgrade translation/ announcements/core_dump Note: Post-G3V8 48 Mb System Upgrade system_software Note: Post-G3V8...
Page 571: Status Cdr-Link
status cdr-link status cdr-link status cdr-link [print] The status cdr-link command displays the status of the call detail recording (CDR) links. If a link is down, the report includes the number of times the switch has tried to re-establish the link. The CDR link is the physical link that the SPE uses to send call detail records to an output device such as a Call Detail Recording Utility (CDRU).
Page 572: Status Clan-Port
Maintenance Commands and Trouble-Clearing Aids status clan-port The same information that is displayed by the status clan-port command can be invoked with: status link n status pgate-port for PGATE links status clan-port or netstat link n for C-LAN links. See status link n for more information. status cleared-alarm-notif Expert Systems use status cleared-alarm-notif to detect chronic alarming conditions.
Page 573: Status Conference
status conference status conference Use status conference to solve the following multimedia problems: 1. A user cannot join or remain connected to a conference. 2. Automatic algorithms — audio AUTO mode and the Px64 video picture specifications downgrade the conference, causing poor video quality. 3.
Page 574 Maintenance Commands and Trouble-Clearing Aids Output Screen 8-27. status conference: page 1 of 2 It is possible for several records to display. Active conferences display first (in order of conference-ID), followed by completed conferences (most recently completed first). Conferences that have not begun have no data or information. Conference data displays in 2 parts: the first screen describes the status of the conference and indicates the modes and levels of the conference.
Page 575 status conference Field descriptions (status conference, page 1) Current status of the conference (active, in-use, status complete) (MMCH DYNAMIC) conference name (Voice-activated) conference mode Not Applicable password Not Applicable password scope Conference cascade mode (blank) cascade mode Current operating audio mode (G.711-A, G.711-mu, G.728. audio mode G.722) Conference type (dedicated)
Page 576 Maintenance Commands and Trouble-Clearing Aids The video format for single-screen conferences: CIF, QCIF, Format QCIF/CIF, H.CTS, H.CTX+, and SG4. (in/out) non-H.261 conferences = input and output formats are always symmetric and the mode is the same for input and output. (H.CTX, H.CTX+, and SG4).
Page 577 status conference The Meet-Me Number administered for the Meet-Me Extension. Meet-me number “in” = dial-in to join endpoint to conference. Dial Type “out” = dial-out to join endpoint to conference. “y” = the endpoint is in use and is fully-connected on all media In Use in an active conference.
Page 578 Maintenance Commands and Trouble-Clearing Aids “y” = the endpoint has the required audio capability. Audio add-on endpoints always set the Aud field to y when the endpoint joins the conference. “c” = the endpoint is PCM only and it changes the conference video quality by changing the operating audio from G.728 to G.711.
Page 579 status conference Rate adaptation/Interworking indicator (5, 6, y, c, e, n, blank). Rate Adpt 5 and “6” apply to Low Speed/High Speed Interworking. All other values apply to Rate Adaptation. “5” = 56-kbps (Low Speed) endpoint joins a High Speed (128 kbps or above) conference.
Page 580 Maintenance Commands and Trouble-Clearing Aids MCU endpoint video state (a, b, B, c, i, r, R, s, S, u, U, v, blank). Quad-screen conferences = an * appears before the Vs value indicating that an endpoint belongs to the mixed image. # appears before Vs values indicating that an endpoint is set to be in the mixed image (via administration or UCC/CRCS Agent), but instead, Fill video displays in its place.
Page 581 status conference “S” = UCC/CRCS Agent interface suppresses this endpoint’s video. For continuous presence conference with fixed quadrant (cont’d) participants, #S represents endpoints that are fixed in a particular quadrant S displays when both the endpoint and the UCC/CRCS Agent suppress the endpoint video. “u”...
Page 582 Maintenance Commands and Trouble-Clearing Aids Field descriptions (status conference, page 2) The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for Sum Grp each assigned group (1-4). Summer parts are assigned only for conferences with over 6 participants. When a conference operates at an audio mode of 7 kHz (administered audio mode is 7 kHz, or auto with the bandwidth greater than 128 kbps), the system allocates “primary”...
Page 583 status conference Endpoint Clearing received from DS1. The endpoint causes the Drop disconnect. The endpoint notifies the MCU that it intends to Reason disconnect. (cont’d) Far-end Clearing received from DS1. The network or endpoint cause the disconnect. “Handshake” = Framing is not located or is lost for over 40 seconds and the endpoint disconnects.
Page 584 Expansion Service Module MMI data port. This field defaults to Ports ESM blank. Endpoint’s assigned summer group number. The summer group port Sum Grp assignments are on screen 1. For Avaya use only. software 8-334 Issue 4 May 2002 555-233-123...
Page 585 status conference Field descriptions (status conference endpoint) The status conference x endpoint y command specifies that the conference is found. Data relevant for each endpoint displays in 6 pages. If technicians use the endpoint-ID all, every specified endpoint displays. Page 1 - Status Conference Endpoint status conference endpoint page 1 of 6 STATUS OF CONFERENCE ___...
Page 586 Maintenance Commands and Trouble-Clearing Aids Is the endpoint participating in the conference or connecting to the In Use conference? - blank “y” = The endpoint is in use and fully-connected on all media in an active conference. “c” = The endpoint is in use and fully-connected; however, the endpoint changes the conference audio or video capability, or the rate of the conference due to rate adaptation.
Page 587 status conference Does it have the required audio capability? - blank “y” = The endpoint has the required audio capability. Audio add-on endpoints set the Aud field y when the endpoint joins the conference. “c” = This PCM-only endpoint changes conference video quality by changing the operating audio from G.728 to G.711.
Page 588 Maintenance Commands and Trouble-Clearing Aids Rate adaptation/Interworking indicator = blank Rate Adpt 5 and 6 apply to Low Speed/High Speed Interworking. All other values apply to Rate Adaptation. “5”= 56-kbps (Low Speed) endpoints join High Speed (128 kbps or above) conferences. This endpoint connects with audio only capability, but is not a valid video source and destination.
Page 589 status conference The talking state of the endpoint - blank “t” = The endpoint detects voice energy (talking). “m” = The endpoint indicates that it is muted to the MCU. Endpoints may mute, but not send an indication to the MCU. “M”...
Page 590 Maintenance Commands and Trouble-Clearing Aids “i” = The endpoint is not a valid video source. For continuous presence conference, #i represents endpoints that are is fixed in a (cont’d.) particular quadrant. “r” For full-screen conferences, t he endpoint’s video is the return video to the broadcaster.
Page 591 status conference Page 2 - Endpoint Channel Information This section describes fields specific to endpoint-level command output. status conference endpoint page 2 of 6 ENDPOINT CHANNEL INFORMATION Chan. Join Drop ----Drop---- ------------Ports---------- Time Time Reason Code Num Trunk Video Aud/ESM BONDng Err Software _____ _____ _________ __ ___ ______ ______ ______ ______...
Page 592 Maintenance Commands and Trouble-Clearing Aids Channels disconnect because: Drop Reason “2-pri” = Administration errors cause mismatches in primary- secondary designations for cascade links. This mismatch indicates that both MCUs are administered as primaries (see “Cascading” for a description of primary-secondary compatibility).
Page 593 status conference “Endpoint” = Clearing received from DS1. The endpoint initiates Drop Reason the disconnect. The endpoint notifies the MCU that it intends to (cont’d) disconnect. “Far-end” = Clearing received from DS1. The network or endpoint initiate the disconnect. “Handshake” = Framing is never found or is lost for over 40 seconds and the endpoint is disconnected.
Page 594 Maintenance Commands and Trouble-Clearing Aids “Pre-AnsDrop” = The call disconnects an endpoint answers. Drop Reason The network, an endpoint, or a terminal adapter may cause the (cont’d) disconnect. This drop reason differs from ‘No-answer,’ which indicates that a 60-second timeout occurs during alerting. In this case, the call drops before the 60-second timer expires.
Page 595 status conference The MMI port used for channel BONDing. Ports BONDng Frame error counter. A circular hex counter (0-FF) to indicates Fr Err framing error occurrences. Page 3 - Conference Information This section describes fields that are specific to endpoint-level command output. status conference endpoint page 3 of 6 CONFERENCE INFO:...
Page 596 Maintenance Commands and Trouble-Clearing Aids Field descriptions The current broadcaster endpoint number. The following Broadcaster keywords qualify the broadcaster: “Broadcast” = A broadcast mode broadcaster. “Chair” = The chair designates the broadcaster. “See-Me” = The endpoint initiates a MCV broadcaster request. “Presenter”...
Page 597 status conference Field descriptions The desired conference operating mode. This may differ from CONF the endpoint in ( ) or endpoint out ( ) modes. EPT-IN EPT-OUT Labels for the various types of mode commands Conference and incoming mode compatibility. STAT “y”...
Page 598 Maintenance Commands and Trouble-Clearing Aids Field descriptions XRATE may be 64 when the endpoint dials in, or in the event XRATE that problems occur. It implies that only one B channel is in use. (cont’d.) Conference and endpoint Audio rates (kbps bandwidth) must AUDIO be the same.
Page 599 status conference Field Descriptions Other possible AUDIO mode values include neutral AUDIO (cont’d.) (neutralized I-channel), (no audio signal) Au-off, which never match conference modes and are unsupported by MCU. field s when operating at 64kbps, 65/64 derestrict 56/64 128kbps, 192kbps, 256kbps, 320kbps, 384kbps, 512kbps, 768 kbps, 1472kbps, 1536kbps, or 1920kbps per channel speeds;...
Page 600 Maintenance Commands and Trouble-Clearing Aids Endpoint Miscellaneous (EPT MISC) Information. EPT MISC contains miscellaneous states and counters for an endpoint. Flags can y or n. Counters start with 0x00, increment to 0xff, and wrap around to 0x01. AIM and VIS are BAS commands that can be sent as input to MCU from an endpoint or as output from MCU to an endpoint Field descriptions...
Page 601 status conference Single and quad-screen presentation mode conferences. BCLS “y” = The endpoint is watching the video of the broadcast source. Single screen conferences. RTLS “y” = The endpoint is watching the video of the return source. “y” = Endpoint hyperactivity (MCU isolates endpoints from the HYPR MMCH conference due to “thrashing”...
Page 602 Maintenance Commands and Trouble-Clearing Aids Frame Alignment Signal (FAS) channel number (1 or 2). This number should match the column header. MCU Frame Alignment Loss (MCUFAL). Counts the number of MCUFAL times the MCU reports lost endpoint FAW or multichannel synchronization (M-FRM) to the endpoint.
Page 603 status conference Field descriptions Video and frame rate types that the endpoint supports. “vfmt” = Does not display if the endpoint has no video capability. All values are blank if an active call or audio-only endpoint exists. Otherwise, values for this field include: FCIF for full CIF for quarter CIF.
Page 604 Maintenance Commands and Trouble-Clearing Aids Transfer rate capabilities. Endpoint speeds over current connections and Px64 Multiplexes. For 384 kbps (H0) calls, endpoints indicate 384 kbps support, that displays . On 336 kbps calls, endpoints must signal 384 kbps support. If an endpoint does not indicate support for 384 kbps on a 384/336 kbps conference, the MCU provides Audio Only Communications Mode (ACOM).
Page 605 status conference status conference endpoint page 5 of 6 ENDPOINT CALL STATUS INFORMATION Join Join Drop -------------- Drop -------- --- Previous ----- Chan Count Time Time Reason Code BondCode DropCode Software _____ _____ __________ ________ _____ _____ __________ ________ _____ _____ __________ ________ _____ _____...
Page 606 Maintenance Commands and Trouble-Clearing Aids Field descriptions Numbers that are dialed out by administered connections for Dial-out number each channel in the call. The dial Out #1 and #2 on page 1 of the forms display the DCP endpoint number. This is particularly useful with bonding dial-out calls.
Page 607 status conference Table 8-14. Status AC - Failure Cause Values Failure Cause (hexadecimal) Description 0x00 (0t0) 0x01 (0t1) Incorrect destination address 0x02 (0t2) Reason unknown 0x06 (0t6) Reason unknown 0x10 (0t16) Normal call clearing 0x11 (0t17) Endpoint not available 0x12 (0t18) ISDN timer expired 0x15 (0t21) Reason unknown...
Page 608: Status Data-Module
Maintenance Commands and Trouble-Clearing Aids Table 8-14. Status AC - Failure Cause Values — Continued Failure Cause (hexadecimal) Description 0x62 (0t98) ISDN protocol error 0x64 (0t100) ISDN protocol error 0x66 (0t102) ISDN timer expired 0x7f (0t127) Reason unknown 0xC2 (0t194) Ring no answer 0xC8 (0t200) Hi and dry - no feedback detected...
Page 609 status data-module Output For the following output example, the command that was entered is “status data-module 301". status data-module 301 DATA-MODULE STATUS Data Ext/Stn Ext for Stn DM: 301 Service State: out-of-service Port/Channel Number: 01C1103 Maintenance Busy? no CF Destination Ext: Connected Ports: Field descriptions The data module extension number.
Page 610: Status Esm
Maintenance Commands and Trouble-Clearing Aids status esm This command displays the link status and equipment and software revision identifiers for the Expansion Service Module (ESM). See ‘‘Expansion Services Module’’ Chapter 5, ‘‘Routine Maintenance Procedures’’ for more information. Feature Action/Object Qualifier Qualifier Description Logins Defaults...
Page 611: Status Firmware Download
status firmware download status firmware download status firmware download <last> This command displays the download status for each board. The qualifier <last> displays the last download schedule. This command displays a blank download schedule if there is no active download schedule or there was no previous schedule for the last qualifier to invoke.
Page 612: Status Hardware-Group
Maintenance Commands and Trouble-Clearing Aids status hardware-group Summary information for the active or last hardware group test displays. This display includes the number and percentage of tested maintenance objects, the percentage of tests passed, failed, and aborted, the time elapsed since initiating the hardware group test, the specific hardware group test command (see ‘‘test hardware-group’’...
Page 613 status hardware-group Field descriptions “active” = testing in progress, “canceled” = testing canceled, Hardware Group Command State “complete” = command completed; no testing occurring. Number of MOs in the specified group (refer to test Number of MOs Tested hardware-group command) that the hardware-group command tests, including MOs that were tested or aborted due to resource contention.
Page 614: Status Health
Maintenance Commands and Trouble-Clearing Aids status health This command displays the current system alarm summary, maintenance busy summary, user summary, critical system status, and cabinet status. This same page displays with the monitor health command, except that the status health output page does not update periodically.
Page 615 status health Proportion of the CPU that is dedicated to system management or periodic and scheduled maintenance. If many periodic or scheduled maintenance tests perform, this occupancy percentage can be high without affecting service. This percentage rounds to the nearest integer;...
Page 616: Status Interface
Maintenance Commands and Trouble-Clearing Aids Number of warnings associated with the cabinet. Asterisks are used to fill fields when numbers exceed 99. Port Network Connectivity (PNC) status for each port networks within a cabinet. When multiple port networks exist, Carriers A, B, and C are listed first and separated from Carriers D and E by a slash (for example, up/up).
Page 617: Status Ip-Board
status ip-board status ip-board status ip-board CCcss The status ip-board command has the same syntax and output as the status c-lan-ip command except the list of allowed boards is larger. The command can be run on either a TN799 or a TN2302. NOTE: This SAT command cannot be run on the other IP-capable DEFINITY board, the MAPD, although somewhat similar commands can be carried out...
Page 618 Maintenance Commands and Trouble-Clearing Aids Table 8-15. status c-lan-ip CCcss — Continued Field Name on output type MIB data Description switch output Incoming data- Counter Long ipInDiscards The number of input IP datagrams for grams dis- which no problems were encountered carded to prevent their continued processing, but which were discarded (e.g., for...
Page 619: Status Ip-Network-Region
status ip-network-region status ip-network-region status ip-network-region The status ip-network-region x (where x is between 1 to 250 for r and 80 for si/csi/d) will provide the status of the administered inter-network region connection management based on the background maintenance ping test. If the background maintenance test concluded a failed connectivity between two regions x and y, then the matrix for status ip-network-region x, or status ip-network-region y will indicate the result as “f”...
Page 620: Status Isdn-Testcall
Maintenance Commands and Trouble-Clearing Aids status isdn-testcall The status isdn-testcall command displays the progress of an outgoing ISDN-PRI test call. The status form displays the tested ISDN-PRI B-channel port number, bit error rate, number of bits transmitted, block error rate, number of blocks transmitted, start time, duration specified, duration of test call and reason of termination.
Page 621 status isdn-testcall Field descriptions (cabinet/carrier/slot/circuit) of the ISDN-PRI B-channel. Port The measured bit error count based on the comparison Bit Error Rate between sent and received bit patterns. (Number displays in scientific notation) Number of bits generated. (Number displays in scientific Number of Bits notation) The measured block error count based on the...
Page 622: Status Journal-Link
Maintenance Commands and Trouble-Clearing Aids status journal-link The status journal-link command displays if the link is up or down. If the link is down, the system displays the number of times the switch tries to initialize the link. A journal printer documents automatic wake-up events, emergency access to attendant events, and housekeeping events when the property management system is not functional.
Page 623: Status Link N
status link n status link n (csi, si, r models with C-LAN circuit pack - Ethernet connection) This command displays: static information about the link the data extension and port used, connect speed, and protocol information a counter of CHAP failures for PPP links time information for PPP and Ethernet links (includes the time of the last reset, the last hour start time, and end time for the error counter statistics).
Page 624 Maintenance Commands and Trouble-Clearing Aids Field descriptions (page 1) Administered link number (assigned by add/change Link Number data-module command) Displays no, yes, unavail, connected, disconnected, Link Status enabled, out-of-service, or restarting The type of interface according to the physical/link Link Type protocol(s) immediately “below”...
Page 625 status link n Field descriptions, page 2 The number of subnetwork-unicast packets delivered to a Incoming received Unicast packets higher-layer protocol. The number of non-unicast (subnetwork-broadcast or Incoming received multicast packets subnetwork-multicast) packets delivered to a higher-layer protocol. The total number of octets received on the interface, Incoming dropped octets including framing characters.
Page 626 Maintenance Commands and Trouble-Clearing Aids status link 1 Page 3 of PROCESSOR CHANNEL STATUS UP: 001, 007, 010-115 199, 300:310 DN: 001-002 PND: 003, 216-220, 299 Field descriptions, page 3 NOTE: A dash (-) or a colon “1” between numbers indicates all numbers including and between the indicated numbers.
Page 627: Status Logins
status logins status logins status logins [print] This command will display information about all of the users that are currently logged into the system. This information will contain their login names, location of physical access, and their currently executing command. The screen does not automatically update, and is a reflection of the system at the time the request was made.
Page 628: Status Pms-Link
Maintenance Commands and Trouble-Clearing Aids status pms-link This command displays the status of the property management system interface link. If the link is up, whether or not a data base swap is taking place between the switch and the property management system (PMS), is displayed. If the link is down, the number of times the switch has tried to set up the link is displayed.
Page 629: Status Pri-Endpoint
status pri-endpoint status pri-endpoint This command displays internal software state information for diagnosis and can help locate facilities with which a PRI endpoint is communicating. Status information for each of the B-channels making up the PRI endpoint display in addition to some overall PRI endpoint information. Action/ Feature Object...
Page 630: Status Processor-Channel
Maintenance Commands and Trouble-Clearing Aids Field descriptions PRI endpoint extension Extension Administered number of B-channels associated with the Width specified PRI endpoint ID number of the signaling group that handles the signaling for Signaling Group the ports in the specified PRI endpoint Administered option for the auto restore feature (restores calls Originating Auto Restoration...
Page 631 status processor-channel Output The following example shows the output from the status processor-channels 1 command. PROCESSOR CHANNEL STATUS Channel Number: 1 Channel Status: Administered but not connected Link Number: 3 Link Type: BX.25 Message Buffer Number: 0 Reset Count: 0 Retransmission Count: 0 Field descriptions The processor channel number 1-64.
Page 632: Status Psa
Maintenance Commands and Trouble-Clearing Aids status psa ‘‘status tti’’. status signaling-group This command displays the state, type, port location, and state of the Primary and Secondary D-channels within the group. A signaling group is a collection of B-channels signaled for by a designated single D-channel or set of D-channels over an ISDN-PRI.
Page 633 status signaling-group Field descriptions Numerical ID of the signaling group (1-8) Group : all members are on a facility associated signaling Type single DS-1 facility. Facility associated signaling groups support only the simplex D-channel configuration. non-facility associated signaling : members can be carried by multiple DS-1 facilities.
Page 634: Status Sp-Link
Maintenance Commands and Trouble-Clearing Aids maintenance-busy : a D-channel is “maintenance-busy” when it is not in the multiple-frame-established state at layer 2. This state is entered automatically when an active D-channel is declared failed. A D-channel that has been placed in the “maintenance-busy” state may be placed in the “out-of-service”...
Page 635: Status Station
status station Field descriptions Operational mode of the link: Link State : the link is administered and a call is setup between the switch and the system printer. down : the link is administered, but a call is not setup between the switch and the system printer.
Page 636 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for the status station 1002 command. status station 1002 GENERAL STATUS Administered Type: 7405D Service State: in-service/on-hook Connected Type: N/A Download Status: Pending Extension: 1002 Maintenance Busy? no Port: 01C0702 SAC Activated? no Call Parked? no...
Page 637 status station Whether the agent is on an ACD call currently ( On ACD Call? Work mode of each hunt group that an agent is logged into Work Mode In service/on-hook, in service/off-hook, in-service/in-tsa Service State (Terminal Self Administration), out of service, or disconnected. Whether maintenance is testing the object ( Maintenance Busy State...
Page 638 Maintenance Commands and Trouble-Clearing Aids Field descriptions Shows the Part ID Number (comcode) of the telephone. If this Part ID Number field shows Unavailable, then the software was unable to determine the Part ID Number. This is the serial number of the telephone. This field may Serial Number show Unavailable if the software is unable to determine the Serial Number.
Page 639 (page 4) does not appear. See also “Shuffling, Hairpinning, Codec and Inter-Network Management Features” in the Administration for Network Connectivity for Avaya MultiVantage Software. status station 78020 Page 4 of 4...
Page 640: Status Synchronization
Maintenance Commands and Trouble-Clearing Aids SSRC Change for Call The number of SSRC changes occurring during the current connection Last Rx Sequence No. Last received data packet sequence number Last Tx Sequence No. Last transmitted data packet sequence number Worst Case this Call Jitter: the worst-case, 1-second jitter buffer size (ms) experienced during the current connection Packet Loss: the worst-case, 1-second packet loss...
Page 641 status synchronization Output The following example shows the output for the status synchronization command. status synchronization SYNCHRONIZATION STATUS Stratum Level:4 Maintenance Name: TONE-BD Physical Location: 01A Switching Capability: Enabled Excessive Reference Switching: No Field descriptions Synchronization stratum level (3 or 4) Stratum Level Either TONE-BD...
Page 642: Status System
Maintenance Commands and Trouble-Clearing Aids status system This command displays the status, mode, and operational attributes of the SPE(s), TDM and Packet busses, tone-clock circuit packs, expansion interface links (exp-links), and emergency transfer switch of cabinets in the system. CAUTION: This command provides general information about the cabinet status.
Page 643 status system Field descriptions Switch Process Element (SPE) identifier: SPE modes are different for simplex systems than for MODE duplicated systems. See ‘‘SPE Modes’’ section that follows. SPE select switch position: SELECT SWITCH auto : the switch is in the middle position and automatically switches SPE depending upon conditions : spe-a position spe-a...
Page 644 Maintenance Commands and Trouble-Clearing Aids Shows which Tone-Clock circuit pack supplies the system SYSTEM TONE tones for the cabinet being displayed. active : Tone-Clock active and supplying system tones : Tone-Clock is standby and ready to supply standby the system tones for this cabinet if the active clock fails. : Tone-Clock failed some maintenance activity and down cannot supply the system tones for this cabinet.
Page 645 status system Whether Minor alarms exist for packet bus components (y/n) ALARMS-MINOR Number of faulty bus leads (defined as shorted to another BUS FAULTS lead, stuck at some value, or an open lead: 0 - 24). This field may take on any integer between 0 and 24. This field displays blank if: Maintenance/Test circuit pack not present Packet Bus port of the Maintenance/Test circuit pack has...
Page 646 Maintenance Commands and Trouble-Clearing Aids Expansion Links that originate from this cabinet and the EXP-LINK locations of the two Expansion Interface circuit packs that make up the link. If the Expansion Link does not exist in the system then a dash ( ) displays.
Page 647 status system SPE Modes Simplex SPE Modes 1A SPE in a simplex system is always the active SPE active No 1B SPE in a simplex system blank Duplex Active SPE Modes This SPE is the active SPE. active This the active SPE; however, it was forced active active/ through a reset system interchange health-override override-on...
Page 648 Maintenance Commands and Trouble-Clearing Aids SPE in maintenance mode, but no current maintenance maint/idle activity. The active SPE can be either active or selected. SPE currently restarting the switch software on this SPE. maint/entering After the switch software on this SPE finishes its initialization, the standby SPE is available to perform maintenance functions.
Page 649 status system SPE in down mode, however, no maintenance activity is down/idle currently taking place. The active SPE could be either active or selected. SPE in down mode, but is currently trying to restart the down/entering switch software on this SPE. As soon as the switch software on this SPE finishes its initialization, the standby SPE is ready to perform background or SAT requested maintenance activity.
Page 650: Status Trunk
Maintenance Commands and Trouble-Clearing Aids status trunk status trunk group# [/ member#] [print] The status trunk command displays information about the operational status of a single trunk or of all members of a trunk group. You can also use it to locate facilities with which the trunk is communicating.
Page 651 status trunk Output Group and member numbers of specified trunks. Trunk Group/ Member The location of the port associated with the trunk. Port For ISDN trunks, the number of the signaling group to which the Signaling Group ID trunk group belongs. For other trunk types, the field is blank. Locations of ports currently connected to the trunk.
Page 652 Maintenance Commands and Trouble-Clearing Aids The following display shows a typical result when status trunk 1/19 is entered. status trunk 1/19 SPE B TRUNK STATUS Trunk Group/Member: 01/19 Service State: in-service/active Port: T00123 Maintenance Busy? no Signaling Group ID: 1 CA-TSC state: not allowed MM Conference ID: 8 MM Endpoint ID: 2...
Page 653 status trunk For an ip-medpro-ip hairpin call, the audio switch port field shows a cabinet and slot, but not a port, on a TN2302 Prowler board. status trunk 1/19 SPE B TRUNK STATUS Trunk Group/Member: 01/19 Service State: in-service/active Port: T00123 Maintenance Busy? no Signaling Group ID: 1 CA-TSC state: not allowed...
Page 654 If you issue a status trunk command for a non-IP station or the connection is hairpinned or shuffled, then the packet loss and jitter size information (page 4) does not appear. See the Administration for Network Connectivity for Avaya MultiVantage Software for more information.
Page 655 status trunk Output, page 4 The ten most recent one-second samples of the Average Jitter (ms) Last 10 Samples jitter buffer size for the requested endpoint. The ten most recent one-second samples of the Packet Loss per Sec Last 10 Samples lost packet information for the requested endpoint.
Page 656: Status Tsc-Administered
Maintenance Commands and Trouble-Clearing Aids status tsc-administered The status tsc-administered command displays the operational status of TSC’s administered for an administered signaling group. The status represents the state of the TSC according to switched services. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions...
Page 657 status tsc-administered Field descriptions The administered TSC index (1-64). TSC Index State of the administered TSC: TSC State : the administered TSC is not functioning (for inactive example, D-channel out-of-service, or disabled) : indicates that the administered TSC is up and user active information can be exchanged end-to-end.
Page 658: Status Tti
Maintenance Commands and Trouble-Clearing Aids status tti status tti [print] Use status tti to see the if the TTI background maintenance task is active. If the TTI background maintenance task is active, the screen shows if TTI ports are being generated or removed, the number of TTI-supported boards that have been processed, and the number of TTI-supported boards that have not yet been processed.
Page 659 status tti Field descriptions generating TTI ports Background removing TTI ports Task State suspended not active completed - all ports translated: The last background maintenance task completed normally. completed - some ports not translated: last background maintenance task stopped when resources were exhausted, and some ports were not translated.
Page 660: Status Val-Ip
Maintenance Commands and Trouble-Clearing Aids status val-ip Use this command to generate an IP-related status report about the VAL circuit pack’s LAN connection. See status c-lan-ip for field descriptions. status val-ip 1C02 IP STATUS Reset Time: mm/dd/hh:mm Last Hour Start Time: mm/dd/hh:mm End Time: mm/dd/hh:mm Incoming Received: Octets...
Page 661: Test Access-Endpoint
test access-endpoint test access-endpoint This command performs hardware diagnostic tests on all port circuits that are associated with the specified access endpoint extension. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test extension Access endpoint extension (# of digits init Test none...
Page 662: Test Alarms
Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for the test access-endpoint 22502 command, and assumes the access endpoint ports for extension 22502 are in cabinet 1, carrier C, slot 11, circuit 1 to 6. The responses are displayed on a port-by-port and test-by-test basis with one line of data for each test result.
Page 663 test alarms Several alarms may be logged against a single maintenance object, each alarm representing a different problem. Even if there are multiple entries in the alarm log for a single object, the test alarms command only tests each physical object once.
Page 664 Maintenance Commands and Trouble-Clearing Aids WARNING: Executing a clear with short option may not clear all alarms, even if all tests pass. WARNING: Since the “clear long” options clear all counters if tests pass, it is possible for firmware counters to be cleared even when a problem exists. In some cases customer service might degrade since calls may be routed over defective equipment.
Page 665 test alarms Field descriptions (Hardware Test Alarm Query) The type of alarm to be tested: put y or n in the field(s) to Alarm Types selects one or a combination of alarms. Tests alarms for the last hour (h), last day (d), last week (w) or Interval all (a) [default].
Page 666 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output from the test alarms command (query form left empty by pressing ). The responses display on a test-by-test basis ENTER with one line of data for each test result. test alarms Page ALARM ENTRY...
Page 667: Test Analog-Testcall
test analog-testcall Day, hour, and minute of alarm. Date Alarmed Count of the current alarm entry versus the total number of alarms Alarm Count to be tested. Test results section Port address (cabinet-carrier-slot-circuit) Port The name of maintenance object Maintenance Name Alternate way to identify maintenance objects.
Page 668 Maintenance Commands and Trouble-Clearing Aids Feature Action/ Inter- Object Qualifier Qualifier Description Logins Default actions test full Executes the most comprehensive test call init Test analog- available using the administered test set type. inads sequence below testcall craft = long; Executes a supervision-only test call (approx.
Page 669 test analog-testcall Feature Interactions Additional data is available after running a test. See the ‘‘list measurements ds-1’’ command with the test-call option for details on how to access the additional data. If the trunk is in use by call processing, the test aborts. If the trunk is in use by maintenance, the test queues and runs when the current maintenance activity finishes.
Page 670: Test Board
Maintenance Commands and Trouble-Clearing Aids test board This command performs a set of hardware diagnostic tests on a specified circuit pack. The system first validates that the board exists at the specified location. Then, based on the logical type of board (for example, Analog, Digital, Hybrid, and others), a series of tests perform diagnostics on the board and then returns results of the test along with any possible error codes.
Page 671 test board Output The following example shows the output from the test board 1c07 short command. The responses display on a test-by-test basis with one line of data for each test result. test board 01C07 short TEST RESULTS Port Maintenance Name Alt.
Page 672: Test Card-Mem
Maintenance Commands and Trouble-Clearing Aids test card-mem This command executes a sequence of tests on the memory card in the specified switch processor element. The test sequences in order for both long and short options are listed in the following table: Test Short Long...
Page 673 test card-mem Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Carrier location where memory card init Test See below card-mem resides: High or Critical Reliability (a or inads sequence ; duplicated (a, A, b, or B) craft = short;...
Page 674 Maintenance Commands and Trouble-Clearing Aids Feature Interactions The test card-mem long command invokes the Memory Card Erase/Write/Read Test. This means that the save translation and save announcement commands are rejected while the write-to-memory-card operation is active. This test also invokes the Memory Card Capacity Test which determines whether the memory card is more than 98% full.
Page 675: Test Cdr-Link
test cdr-link Field descriptions Port address (cabinet-carrier-slot-circuit): cabinet 1, carrier is A Port (control carrier A in a simplex system) and either A or B (control carriers A and B in a duplex system). The slot and circuit fields in the port address for the CAP-MEM, and CARD-MEM maintenance objects are always blank.
Page 676: Test Customer-Alarm
Maintenance Commands and Trouble-Clearing Aids test customer-alarm This command performs hardware diagnostic tests on the leads of the Processor and EPN maintenance circuit packs, used for customer-provided alarms by closing the appropriate relay for 1 minute. Failure is verified by checking the customer alarm attached to the specified circuit pack.
Page 677 test customer-alarm Output The following example shows the output from test customer-alarm 02a. test customer-alarm 02A TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code CUST-ALM PASS Command Successfully Completed Field Definitions The port address (cabinet-carrier-slot) Port The maintenance name (always CUST-ALM) Maintenance Name...
Page 678: Test Data-Module
Maintenance Commands and Trouble-Clearing Aids test data-module This command performs hardware diagnostic tests on a data module or data channel. Test results are determined by the interface to the digital switch-data line port, digital line port, or network control data channel. Action/ Feature Object...
Page 679 test data-module Output The following example shows the output from test data-module 300 The responses display on a test-by-test basis with one line of data for each test result. test data-module 300 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01C1103 PDMODULE...
Page 680: Test Ds1-Loop
Maintenance Commands and Trouble-Clearing Aids test ds1-loop This command validates that the board exists at the specified location and that the board is a TN464F or TN767E or later suffix DS1 Interface board. Long-duration loopback tests execute for an extended period of time until manually terminated. Short-duration loopback tests return the result of the test to the screen after executing.
Page 681 test ds1-loop Feature Interactions Loopback or span tests are not allowed on DS1 boards unless the board has been busied out. Only one of the CPE Loopback Jack, far-end CSU, one-way span, or DS1/CSU loopback tests may be active at any given time on a DS1 span. Output The following example shows the output for test ds1-loop 1c07, and assumes that the board in cabinet 1, carrier c, slot 7 is a TN767E DS1 board.
Page 682: Test Duplication-Interface
Maintenance Commands and Trouble-Clearing Aids test duplication-interface This command performs hardware diagnostic tests on the indicated duplication interface circuit pack, under the control of the active SPE that tests the SHDW-CIR, SPE-SELECT, and DUPINT maintenance objects. SHDW-CIR is associated with that portion of the duplication interface circuit pack that handles memory shadowing from the active to the standby SPE-SELECT is associated with the SPE Select switch located on the front of the circuit pack...
Page 683 test duplication-interface Output The following example shows the output from the test duplication-interface 1A command, where A is the active carrier in an SPE duplex system. The responses display on a test-by-test basis with one line of data for each test result. test duplication-interface a long SPE A TEST RESULTS...
Page 684: Test Eda-External-Device-Alrm
Maintenance Commands and Trouble-Clearing Aids test eda-external-device-alrm This command performs a hardware diagnostic test on all or specific port’s administered external device alarms. The test PASSES if the external device is not reporting an external device alarm and FAILS if the external device is reporting an external device alarm.
Page 685 test eda-external-device-alrm Output The following example shows the output for test external-device-alarm all. The responses display on a test-by-test basis with one line of data for each test result. test eda-external-device-alrm all TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 03major EXT-DEV...
Page 686: Test Environment
Maintenance Commands and Trouble-Clearing Aids test environment This command performs hardware diagnostic tests of the environment monitoring and control, and emergency transfer functions of both Processor Port Network (PPN) cabinets and Expansion Port Network (EPN) cabinets. Circuit packs involved are the Processor circuit pack (PPN simplex systems), the Duplication Interface circuit pack (PPN duplex systems), and EPN Maintenance circuit packs.
Page 687 test environment Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test environment location Cabinet (1-3); 1 = PPN, 2-3 = init Cabinet = 1; See below optional EPN. inads test sequence = craft short; repeat = 1 short Option for a brief series of nondestructive diagnostic tests.
Page 688 Maintenance Commands and Trouble-Clearing Aids Output The following screen shows the output for test environment 1 to test a MCC/PPN cabinet. The responses appear on a test-by-test basis with one line of data for each test result. test environment 1 TEST RESULTS Port Maintenance Name...
Page 689: Test Failed Ip-Network-Region
test failed ip-network-region The following example show the output for test environment 2, where cabinet 2 is an SCC cabinet. test environment 2 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code DC-POWER PASS EMG-XFER PASS EXT-DEV PASS RING-GEN PASS...
Page 690: Test Firmware Download
Maintenance Commands and Trouble-Clearing Aids test firmware download This command runs a series of demand maintenance tests on all hardware in a specified group: a carrier, cabinet, port network, PNC (A or B), SPE, circuit pack or the entire system. When this command is executed, the tests that are run vary depending on the options chosen and types of hardware in the group.
Page 691 test hardware-group Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test system System-wide test of all hardware-groups init Test See below hardware- inads sequence = Carrier address: cabinet (1-3), carrier (A-E) group short; carrier Cabinet address (1-3) repeat = 1 location cabinet Board address in PCSS format...
Page 692 Maintenance Commands and Trouble-Clearing Aids Feature Interactions test hardware-group Only one test hardware-group command can be active at any given time. If the test hardware-group command is issued with the all-ports option when the TTI background task is active, some unadministered ports may not be tested. In addition, active alarms on line ports may be cleared by this task.
Page 693 test hardware-group Setting the Test Parameters Once the user has entered the desired action (test hardware-group) and the object (board, carrier, etc.), then an options form displays. test hardware-group system Page 1 of 1 TEST HARDWARE-GROUP SELECTIONS Select the desired options for the specified test. Test sequence: short Test repetition: repeat count: 1...
Page 694 Maintenance Commands and Trouble-Clearing Aids Run the command in the background, thus freeing the SAT (n / Background? y). The error results are tabulated in the error log, but no results display on the terminal. This option cannot be used if either the continuously or the auto-page options are selected.
Page 695 test hardware-group Table 8-16. Test of ‘all ports’ option for the following boards: — Continued Board Board Number Description Number Description TN722B DS1 Tie Trunk TN2146 Direct Inward Dialing Trunk TN726B Data Line TN2147 Central Office Trunk TN742 8 port Analog Line TN2149 Analog Line TN2180...
Page 696: Test Inads-Link
Maintenance Commands and Trouble-Clearing Aids Field descriptions Port address (cabinet-carrier-slot-circuit) Port The name of maintenance object Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object is The field contains station extension trunk xxx/yyy (xxx = trunk group, yyy = member) private CO line P/xxx (xxx = private CO line group number) The test being executed Test No.
Page 697 test inads-link Once the call is answered by INADS, the system sends a message with a test alarm type. INADS acknowledges receipt of the message and creates a trouble ticket. The trouble ticket is closed immediately and has a “INADS LINK TEST” message entered in the description field.
Page 698: Test Interface
Maintenance Commands and Trouble-Clearing Aids test interface This command performs hardware diagnostic tests on the specified processor interface circuit pack. In addition to testing the PI board, the tests examine the protocol and link interface that is transmitted over the board. Feature Action/Object Qualifier...
Page 699 test interface Output The following example shows the output for the test interface a1 command. The responses display on a test-by-test basis with one line of data for each test result. test interface a1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01A1 PI-SCI...
Page 700: Test Isdn-Testcall
Maintenance Commands and Trouble-Clearing Aids test isdn-testcall This command starts an outgoing, asynchronous ISDN-PRI test call in the asynchronous method from a specified trunk. If the test results are PASS, the test call is started. A test result of ABORT means that a resource wasn’t available, for example, B-channel or a Maintenance/Test circuit pack.
Page 701 test isdn-testcall Output The following example shows the output for the test isdn-testcall 80/1 command. The responses display on a test-by-test basis with one line of data for each test result. test isdn-testcall 77/1 SPE A TEST RESULTS Port Maintenance Name Alt.
Page 702: Test Journal-Printer
Maintenance Commands and Trouble-Clearing Aids test journal-printer This command performs hardware diagnostics on the link between the switch and one of the specified journal printer links. There are two types of journal printer links: pms-log and wakeup-log. For general information on journal printer links, see the second paragraph in the “Description”...
Page 703 test journal-printer Feature Interactions The maintenance of a particular component on a link sometimes interferes with the maintenance of the link itself. Maintenance can put a link component in a busy state causing link set-up to fail. Frequent attempts at re-setup of a link may delay the recovery of a faulty component due to the maintenance test of a component only taking place when the component is idle.
Page 704: Test Led
Maintenance Commands and Trouble-Clearing Aids test led This command performs a test on all the LEDs in a specified cabinet. Once the cabinet is validated and the range of circuit packs determined, the test led command turns on all LEDs on the circuit packs contained in each carrier until all affected carriers are lit.
Page 705: Test Link
test link test link This command validates that a specified link is administered and then performs a set of hardware diagnostic tests on the link. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test link link-id Link number (1-8; assigned via the init Test none...
Page 706 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for the test link 1 long command. The responses display on a test-by-test basis with one line of data for each test result. test link 1 long TEST RESULTS Port Maintenance Name Alt.
Page 707: Test Maintenance
test maintenance test maintenance This command tests the EPN maintenance circuit pack in any Expansion Port Network control carrier. Specifying cabinets 2 - 3 allows testing of any connected EPN maintenance circuit packs. The test sequence checks the SAT interface, EI link, reset, and sanity functions on the EPN maintenance circuit pack.
Page 708 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for the test maintenance 2 command. The responses display on a test-by-test basis with one line of data for each test result. test maintenance 2 TEST RESULTS Port Maintenance Name Alt.
Page 709: Test Memory
test memory test memory This command performs hardware diagnostic tests on any or all memory circuit packs in the specified carrier. Both short and the long test are nondestructive when testing memory. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test memory location Physical location of the memory...
Page 710 Maintenance Commands and Trouble-Clearing Aids Output The following example show the output for the test memory 1b command. The responses display on a test-by-test basis with one line of data for each test result. test memory 1b TEST RESULTS Port Maintenance Name Alt.
Page 711: Test Modem-Pool
test modem-pool test modem-pool This command performs hardware diagnostic tests on the specified modem pool group or an individual member of a specified group (Combined or Integrated). A Combined modem-pool group consists of pairs of Analog and Digital Line ports. One pair of Analog and Digital Line ports used for modem-pooling is called a conversion resource.
Page 712 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output for test modem-pool 1/3. The responses display on a test-by-test basis with one line of data for each test result. test modem-pool 1/3 short SPE B TEST RESULTS Port Maintenance Name Alt.
Page 713: Test Network-Control
test network-control test network-control This command performs hardware diagnostic tests on a specified network control circuit pack. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Network control board carrier location in a init Cabinet 1, none network- High or Critical Reliability System (a or b).
Page 714 Maintenance Commands and Trouble-Clearing Aids Output The following example shows the output from test network-control a. The responses display on a test-by-test basis with one line of data for each test result. test network-control a TEST RESULTS Port Maintenance Name Alt.
Page 715: Test Packet-Control
test packet-control test packet-control This command performs hardware diagnostic tests on the specified packet-control circuit pack. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Applies only to duplicated configurations: if simplex, init Simplex: See below packet- parameter is not used and thus is not valid; if inads location control...
Page 716 Maintenance Commands and Trouble-Clearing Aids Output The following example is the screen output for the test packet-control 1B long command. Note that carrier B is the active carrier in this example. test packet-control 1B l TEST RESULTS Port Maintenance Name Alt.
Page 717: Test Pkt
test pkt test pkt The test pkt runs a series of tests on the Packet bus of the specified PPN or EPN. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test pkt pn number The Packet bus to be tested: nn (1-3) init Test none...
Page 718 Maintenance Commands and Trouble-Clearing Aids Output The following example is the output for the test pkt port-network 1 command. The responses display on a test-by-test basis with one line of data for each test result. test pkt port-network 1 TEST RESULTS Port Maintenance Name Alt.
Page 719: Test Pms-Link
test pms-link test pms-link This command performs the specified property management system link tests on the specified pms link by checking to see if the link is accessible and then performing a reset on the link (long test only). For general information on PMS links, refer to the description of the ‘‘busyout pms-link’’...
Page 720 Maintenance Commands and Trouble-Clearing Aids Feature Interactions The maintenance of a particular component on a link may interfere with the maintenance of the link itself. Maintenance can put a link component in a busy state causing link set-up to fail. Frequent attempts at re-setup of a link may delay the recovery of a faulty component due to the maintenance test of a component only taking place when the component is idle.
Page 721: Test Port
test port test port This command performs hardware diagnostic tests on an individual port circuit. In most cases, tests are performed on hardware connected to the port. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test port location PCSSpp init Test none...
Page 722 Maintenance Commands and Trouble-Clearing Aids Output The following example is the output for the test port command and assumes that the port in cabinet 1, carrier c, slot 7, circuit 1 is an analog port. The responses display on a test-by-test basis with one line of data for each test result. test port 01c0701 short TEST RESULTS Port...
Page 723: Test Pri-Endpoint
test pri-endpoint test pri-endpoint This command performs hardware diagnostic tests on all port circuits (B-channels) that are associated with the PRI endpoint extension. The test pri-endpoint command performs hardware diagnostic tests on all port circuits (B-channels) that are associated with the specified PRI endpoint. Feature Action/Object Qualifier...
Page 724 Maintenance Commands and Trouble-Clearing Aids Output The following output example is for the test pri-endpoint 22501 command and assumes that the PRI endpoint ports for extension 22501 are in cabinet 1, carrier B, slot 20, circuits 1 to 3. The responses display on a port-by-port and test-by-test basis with one line of data for each test result.
Page 725: Test Processor
test processor test processor This command performs hardware diagnostic tests on a specified processor circuit pack. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test processor location Cabinet number (optional for init none simplex) and carrier letter (optional inads below a for simplex;...
Page 726 Maintenance Commands and Trouble-Clearing Aids Output The following output example is for the test processor a command. The responses display on a test-by-test basis with one line of data for each test result. test processor a SPE B TEST RESULTS Port Maintenance Name Alt.
Page 727: Test Shadow-Link
test shadow-link test shadow-link This command performs hardware diagnostics for the shadow link between the two duplication-interface circuit packs. This command works only with High or Critical Reliability systems. Refer to Chapter 6, ‘‘Reliability Systems: A Maintenance Aid’’ for more details. Action/ Feature Object...
Page 728 Maintenance Commands and Trouble-Clearing Aids Output The following output example is for the test shadow-link command. The responses display on a test-by-test basis with one line of data for each test result. test shadow-link TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code SHDW-LNK PASS...
Page 729: Test Signaling-Group
test signaling-group test signaling-group This command validates that the specified signaling group is administered and runs a series of diagnostic tests that return results of the test along with possible error codes. A signaling group is a collection of B-channels signaled for by a designated single D-channel or set of D-channels over an ISDN-PRI.
Page 730 Maintenance Commands and Trouble-Clearing Aids Feature Interactions Additional data is available after running a test. See the status signaling-group command for how to access the additional data. Output The following output example is for the test signaling-group 1 command. The responses display on a test-by-test basis with one line of data for each test result.
Page 731: Test Sp-Link
test sp-link test sp-link The test sp-link command validates that the system printer link is administered and runs a series of diagnostic tests that return results of the test along with possible error codes. The system printer link is a link from the switch to an external printer over which jobs can be printed.
Page 732 Maintenance Commands and Trouble-Clearing Aids Output The following output example is for the test sp-link command. The responses display on a test-by-test basis with one line of data for each test result. test sp-link SPE A TEST RESULTS Port Maintenance Name Alt.
Page 733: Test Spe-Standby
test spe-standby test spe-standby This command allows the technician to perform hardware diagnostic tests on the standby Switch Processing Element (SPE) in a duplex SPE system. This command tests all MOs in the standby MO. The STBY-SPE MO itself does not have any defined tests.
Page 734 Maintenance Commands and Trouble-Clearing Aids Output The following output example for the test spe-standby command assumes that the standby SPE is located in carrier B. The responses display on a test-by-test basis with one line of data for each test result. test spe-standby SPE A TEST RESULTS...
Page 735: Test Station
test station test station This command performs hardware diagnostic tests on an individual port circuit assigned to that extension. The technician must specify the extension and a translation is automatically done to the physical port location. Action/ Feature Object Qualifier Qualifier Description Logins Defaults...
Page 736 Maintenance Commands and Trouble-Clearing Aids Output The following screen is an example of the output from the test station 81902 short command with the assumptions that port in cabinet 1, carrier c, slot 7, circuit 1 is an analog port and extension 81902 is connected to that port. The responses display on a test-by-test basis with one line of data for each test result.
Page 737: Test Synchronization
test synchronization test synchronization This command updates all the boards with the correct synchronization source and parameters. The system sends a downlink message to the tone clock, DS1, and Expansion Interface boards to place them in the correct synchronization configuration, providing error-free digital communication between the switch and other PBXs, COs, or customer premise equipment.
Page 738 Maintenance Commands and Trouble-Clearing Aids Output The responses display on a test-by-test basis with one line of data displayed for each test result. The following screen is an example of the output for the test synchronization short command. test synchronization short TEST RESULTS Port Maintenance Name...
Page 739: Test Tdm
test tdm test tdm This command tests all the time slots on a bus associated with a PPN or an EPN. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test tdm pn number nn = number of the port network to init Test none...
Page 740 Maintenance Commands and Trouble-Clearing Aids Output The following screen is an example of the output for the test tdm port-network 1 command. The responses display on a test-by-test basis with one line of data for each test result. test tdm port-network 1 TEST RESULTS Port Maintenance Name...
Page 741: Test Tone-Clock
test tone-clock test tone-clock The test tone/clock command performs hardware diagnostic tests on a technician-specified tone or clock circuit pack. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test location PCSS init Test none tone-clock inads Sequence short Option for a brief series of craft = short;...
Page 742 Maintenance Commands and Trouble-Clearing Aids Output The responses display on a test-by-test basis with one line of data for each test result. The following is the output for the test tone-clock 1a command. test tone-clock 1a TEST RESULTS Port Maintenance Name Alt.
Page 743: Test Trunk
test trunk test trunk This command performs hardware diagnostic tests on an entire trunk group or an individual trunk group member, depending on the options entered. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test group Administered group number (1-99) init Test Seq.
Page 744 Maintenance Commands and Trouble-Clearing Aids Output The responses display on a test-by-test basis with one line of data for each test result. The following screen is an example of the output for the test trunk 78 command. test trunk 78 TEST RESULTS Port Maintenance Name...
Page 745: Test Tsc-Administered
test tsc-administered test tsc-administered This command submits a switched services request to run the Temporary Signaling Connection’s heartbeat test for all administered TSCs on a signaling group. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test signaling Signaling group number (1–8) init repeat = Additional...
Page 746: Traceroute
The primary use of this command is to determine quickly and unambiguously if the fault lies within Avaya-provided equipment or if the fault is with the LAN or LAN administration to which the Avaya DEFINITY Server switch is connected.
Page 747 traceroute Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions traceroute ip-address where IP address is init Primary None www.xxx.yyy.zzz inads craft board Cabinet-carrier-slot customer address of the C-LAN circuit pack Examples: traceroute ip-address 123.4.56.789 traceroute board 1C14 source an endpoint’s virtual port Example: trace-route ip-address 106.245.27.205 source...
Page 748 Maintenance Commands and Trouble-Clearing Aids Field descriptions This C-LAN entry identifies the port on the board from which clan port the traceroute command is issued. The node number (in sequence). The first node (0) is the address from which the traceroute command is issued. Time from the board to each intermediate destination in Time (ms) milliseconds.
Page 749: Upgrade Software
upgrade software upgrade software This command upgrades the software text image, the flash component of the LMM firmware, the MTP firmware, the Packet Control (PACCON), and the Processor Interface (PI) firmwares. Depending on whether the system is simplex (Standard reliability) or Duplex (High or Critical reliability), the processes for the upgrade are different: System Description of Upgrade...
Page 750 Maintenance Commands and Trouble-Clearing Aids Initcauses Executing display initcauses shows the software upgrade and the system reset level. Multi-User Contention When this command is executing, all other maintenance commands are blocked. Exceptions to these are most of the status or display commands. All administration commands are not blocked.
Page 751 upgrade software Output The following is the output from the upgrade software command and a successful simplex upgrade. INITIATING SOFTWARE UPGRADE MEM-CARD CHECKSUM PASSED REPROGRAMMING MTP PASSED ERASING MEMORY PASSED REPROGRAMMING SPE PASSED FLASH TEXT CHECKSUM PASSED UPGRADE COMPLETE <beep> REPLACE SOFTWARE MEM-CARD WITH TRANSLATION MEM-CARD <beep>...
Page 752 Maintenance Commands and Trouble-Clearing Aids FLASH TEXT CHECKSUM: If the checksum fails, the software may or may not be healthy, but it will try to run for as long as it can until further system reset through system technician intervention. REPLACE SOFTWARE The system technician is prompted by a beep and MEM-CARD WITH...
Page 753: Packet Bus Fault Isolation And Correction
Packet Bus Fault Isolation and Correction General This chapter describes the fault isolation/correction procedures for the Packet Bus and for the various MOs that use the Packet Bus. Because the Packet Bus is shared by all circuit packs that must communicate on it, a faulty circuit pack can disrupt communication over the Packet Bus.
Page 754: Remote Maintenance Versus On-Site Maintenance
Packet Bus Fault Isolation and Correction ‘‘Maintenance of the Packet Bus’’ describes the Packet Bus maintenance software strategy. Similarities and differences between the Packet Bus and the TDM Bus are discussed. An overview of the Fault Isolation and Correction Procedures is also presented. ‘‘The Maintenance/Test Circuit Pack (TN771D)’’...
Page 755: Tools For Packet Bus Fault Isolation And Correction
Tools for Packet Bus Fault Isolation and Correction The Maintenance/Test Packet Bus port (described in detail later in this chapter) can give the remote technician information about the state of the packet bus. This information can be obtained via the status system command and via the PKT-BUS test sequence.
Page 756: Packet Bus
Packet Bus Fault Isolation and Correction Packet Bus Each port network has its own packet bus, and, accordingly, there is one packet bus MO in each port network. The packet bus is not duplicated, as is the TDM Bus. However, there are several spare leads on the packet bus and, in high and critical reliability systems, these spare leads are used to recover from some failures on the packet bus.
Page 757: Circuit Packs That Use The Packet Bus
Circuit Packs That Use the Packet Bus Packet bus faults do not necessarily cause service interruptions. However, most packet bus shorts do cause these interruptions. Depending on what leads are defective, the system may be able to recover and continue to communicate. This can be detrimental because it makes isolating the fault difficult.
Page 758 Packet Bus Fault Isolation and Correction TN556, TN2198 and TN2208 ISDN-BRI circuit packs [BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ] provides connections for ISDN-BRI station sets and data modules and for ASAI adjuncts. The Packet Bus is used to carry signaling information for sets and data modules.
Page 759 Circuit Packs That Use the Packet Bus TN556 ISDN-BRI Circuit Pack. A failure of the ISDN-BRI circuit pack typically causes some or all ISDN-BRI sets and data modules and/or an ASAI adjunct connected to the circuit pack to fail to function. If the failure is on the Packet Bus interface, the Packet Bus may be alarmed as well.
Page 760: Maintenance Of The Packet Bus
Packet Bus Fault Isolation and Correction Maintenance of the Packet Bus The following topics are discussed: Comparison between the Packet Bus and the TDM Bus Packet Bus Maintenance Software Overview of Fault Correction Procedures Packet Bus and TDM Bus: a Comparison Although the Packet Bus is similar to the TDM Bus in many ways, there are some important differences.
Page 761 Maintenance of the Packet Bus Packet Bus Maintenance Software Packet Bus maintenance software involves the traditional set of error conditions, tests, and alarms relevant to Packet Bus faults. These are described in the PKT-BUS section in Chapter 10, ‘‘Maintenance Object Repair Procedures’’, and they are similar in design to the maintenance strategy for most maintenance objects.
Page 762: The Maintenance/Test Circuit Pack (Tn771D)
Packet Bus Fault Isolation and Correction Overview of Fault Correction Procedures This section gives an overview of the procedures used to (1) isolate the cause of Packet Bus faults and to (2) correct the Packet Bus faults. These procedures are applicable to High and Critical Reliability systems, and they are detailed fully later in this chapter: 1.
Page 763 The Maintenance/Test Circuit Pack (TN771D) The yellow LED on the TN771D Maintenance/Test circuit pack provides a visual indication of the state of the packet bus, as follows: Blinking at a rate of 1 per sec — the Maintenance/Test Packet Bus port cannot swap leads to correct a Packet Bus fault (that is, there are too many faults).
Page 764 Packet Bus Fault Isolation and Correction The list configuration command is used to check for the presence of a circuit pack in the system. If a circuit pack is not present in the system, one must be taken to the customer site. The ‘‘Special Precaution Concerning the TN771’’...
Page 765 The Maintenance/Test Circuit Pack (TN771D) Entering and Exiting Standalone Mode NOTE: When in standalone mode, the red LED on the TN771 is lit. This function is correct, and it serves as a reminder to remove the TN771 from standalone mode. CAUTION: The TN771 in standalone must be the ONLY TN771 in the port network.
Page 766 Packet Bus Fault Isolation and Correction If there is no TN771 in the Port Network, use the following steps to enter the standalone mode: 1. Attach the 258A Six-Port Male Amphenol Adapter to the Amphenol connector for the slot into which the TN771 is to be inserted. Connect one end of a D8W 8-wire modular cable to port 1 of the 258A.
Page 767 The Maintenance/Test Circuit Pack (TN771D) Use the following procedures to exit standalone mode: 1. Remove the 258A Adapter from the Amphenol connector. 2. If the TN771 was installed for this procedure, remove it. Otherwise, reseat the TN771. 3. Be sure that alarm origination is re-enabled on the Maintenance-Related System Parameters form if it was disabled there (if it was disabled at login, it is automatically re-enabled at logoff).
Page 768 Packet Bus Fault Isolation and Correction SLOT XXX ......Backplane Separation Figure 9-3. Packet Bus Leads on the Backplane - Front View 9-16 Issue 4 May 2002 555-233-123...
Page 769 The Maintenance/Test Circuit Pack (TN771D) SLOT XXX ......Backplane Separation Figure 9-4. Packet Bus Leads on the Backplane - Back View 555-233-123 Issue 4 May 2002 9-17...
Page 770 Packet Bus Fault Isolation and Correction Special Precaution Concerning the TN771 NOTE: A new TN771 Maintenance/Test circuit pack must be taken to the customer site whenever the following is true: Maintenance/Test Packet Bus port indicates that a Packet Bus fault is present.
Page 771: Packet Bus Fault Isolation Flowchart
Packet Bus Fault Isolation Flowchart 8. If the data matches the previously recorded data, a Packet Bus problem exists. The original TN771 Maintenance/Test circuit pack is not defective, and it does not need to be returned to the factory. Replace the original TN771, then correct the Packet Bus problem by using the procedures in the sections that follow.
Page 772 Packet Bus Fault Isolation and Correction The Packet Bus Fault Isolation Flowchart appears on the following two pages. NOTE: See the ‘‘Flowchart Description and Supplement’’ section following the flowchart for a description of the flowchart as well as for supplementary information, the availability of which is indicated by the uppercase letters that appear in the flowchart.
Page 773 Packet Bus Fault Isolation Flowchart From page Is a Are there Follow the repair TN771 present alarms or errors procedure for against in this port M/T-PKT M/T-PKT? network? Are the packet bus Place the TN771 problems in standalone mode resolved? Does the Is the Follow the board,...
Page 774 Packet Bus Fault Isolation and Correction Flowchart Description and Supplement An uppercase letter in bold (for example, A, B, C, etc.) indicates that there is supplemental information with details about the relevant process that could not fit into the appropriate box or diamond. NOTE: Due to space restrictions, individual error codes and alarms are not detailed on the flowchart.
Page 775 Packet Bus Fault Isolation Flowchart c. If only a single EPN is affected, the Packet Control is probably not the source of the problem. However, if all of the ISDN-BRI circuit packs are located in a single EPN, assume that the answer to this question is ‘‘No,’’ and check the Packet Control.
Page 776: Packet Bus Fault Correction
Packet Bus Fault Isolation and Correction Packet Bus Fault Correction Using and interpreting results from the status system command The status system command can be issued to retrieve information about the Packet Bus. This command is described fully in the “Status Commands” section in Chapter 8, ‘‘Maintenance Commands and Trouble-Clearing Aids’’.
Page 777 Packet Bus Fault Correction Considerations for High and Critical Reliability Systems If a High or Critical Reliability system is involved, special considerations involving the features of this type of system must be kept in mind. In particular, if a Packet Bus problem is caused by a duplicated component, switching to the standby component may both alleviate the problem and isolate the faulty circuit pack.
Page 778 Packet Bus Fault Isolation and Correction CAUTION: Since Packet Bus fault isolation procedures involve removing circuit packs and possibly disconnecting entire carriers, these procedure have a profound effect on service. Therefore, if possible, implement these procedures after hours or during hours of minimum system use. NOTE: Each of these procedures contains one or more steps that require a determination as to whether the Packet Bus problem has been resolved.
Page 779 Packet Bus Fault Correction 1. Display the Error and Alarm Logs for the circuit pack via the display errors and display alarms commands. 2. If there are errors for the circuit pack, refer to the appropriate maintenance documentation in Chapter 10, ‘‘Maintenance Object Repair Procedures’’, and follow the recommended maintenance procedure to resolve the errors.
Page 780 Packet Bus Fault Isolation and Correction Procedure 2 Procedure 2 removes and reinserts port circuit packs (those in the purple slots) one or several at a time. Use Procedure 2 for each port circuit pack in the port network until either (1) the problem is resolved or (2) there are no more circuit packs in the port network.
Page 781 Packet Bus Fault Correction Steps for Procedure 2: 1. Remove one or several circuit packs as appropriate, according to the considerations presented in the previous paragraphs. Any circuit pack(s) (whether Packet or non-Packet) that have been recently inserted should be checked first.
Page 782 Packet Bus Fault Isolation and Correction Procedure 3 Procedure 3 removes and reinserts control carrier circuit packs one at a time. The Packet Control, Tone-Clock, and Expansion Interface circuit packs are the only processor complex circuit packs that communicate on the Packet Bus. In addition, the Memory 1 and EPN Maintenance Board circuit packs are connected to the Packet Bus in the backplane (while the Memory 2 circuit pack is not).
Page 783 Packet Bus Fault Correction If Procedure 3 fails to identify the cause of the problem, go to Procedure 4. In a High or Critical Reliability System, do the following: 1. If the circuit pack to be replaced is in the SPE, perform an SPE interchange by entering the reset system interchange command.
Page 784 Packet Bus Fault Isolation and Correction Procedure 4 Procedure 4 tries to isolate the failure to a particular set of carriers. Only the circuit packs in those carriers are checked. Procedure 4 is used if the preceding procedures fail, because it can help locate multiple circuit pack failures as well as failures of the carrier hardware.
Page 785 Packet Bus Fault Correction Terminator TDM/LAN Cable Control Carrier Normal Cabinet Modified Cabinet (Rear View) (Rear View) Figure 9-7. Carrier Rewiring Example Procedure 4 is organized into two parts, as follows: Part 1: 1. Power down the PN. See ‘‘Removing Power’’ section in Chapter 5, ‘‘Routine Maintenance...
Page 786 Packet Bus Fault Isolation and Correction 2. Determine if the Packet Bus fault is still present. If so, and if there are shorts on the Packet Bus, perform Procedure 2 and/or Procedure 3 for only the circuit packs in those carriers that are connected to the ‘‘shortened’’ Packet Bus.
Page 787: Maintenance Object Repair Procedures
Maintenance Object Repair Procedures For Maintenance Objects on the DEFINITY Wireless Business System (DWBS), refer to the documentation that accompanies the DWBS. Trouble-clearing is based on the type of indication received, system-alarmed troubles, or user-reported troubles. When viewing the Alarm Log, all major alarms display first, followed by minor alarms, and warning alarms.
Page 788: Cabling Precautions
Maintenance Object Repair Procedures Cabling Precautions CAUTION: Do not cut or bend fiber optic cables. Doing so may adversely affect communication between the EPN and the PP N cabinets. CAUTION: To avoid damaging the cable-to-connector interface when removing any Inter-Carrier Cable, grasp the cable connector, not the cable itself. ABRI-PORT (ASAI ISDN-BRI Port) MO Name (in Alarm Log)
Page 789: Ac-Power
AC-POWER AC-POWER AC Power for AC-Powered Systems MO Name (in Full Name of Alarm Log) Alarm Level Initial Command to Run AC-POWER WARNING test environment P AC Power Where P is an appropriate port network number determined via the PORT field from the Alarm or Error Log.
Page 790 Maintenance Object Repair Procedures CONVENIENCE OUTLET CONVENIENCE OUTLET FUSE F7 IS FOR CONVENIENCE OUTLETS BACK OF POWER DISTRIBUTION UNIT FRONT OF POWER DISTRIBUTION UNIT FUSE LOCATIONS FUSE LOCATIONS THE 3 FANS ARE ACTUALLY ON BACK OF CABINET AND ARE NOT VISIBLE FROM FRONT OF CABINET.
Page 791 AC-POWER AC Power Query Test (#78) Table 10-2. TEST #78 AC Power Query Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 792 Maintenance Object Repair Procedures Table 10-2. TEST #78 AC Power Query Test — Continued Error Test Code Result Description / Recommendation FAIL NOTE: For a Global AC MCC (J58890CH) use the procedures outlined in step 2. The switch is currently without AC power. WARNING: Turn off power to the 397C Battery Charger before removing Fuse F5.
Page 793 AC-POWER Table 10-2. TEST #78 AC Power Query Test — Continued Error Test Code Result Description / Recommendation FAIL 2. Procedures for a Global MCC (J58890CH): (cont) (cont) a. For a nominal holdover system if there is no AC power at the wall outlet, then the problem is not with the system itself.
Page 794 Maintenance Object Repair Procedures The environment maintenance strategy to be used depends on both the cabinet configuration and the type of powering. Refer to the “DC-POWER (Single-Carrier Cabinet Power)” information for environment maintenance strategy. In a DC-powered multicarrier cabinet system, the AC-POWER maintenance object still exists, but serves no functional purpose.
Page 795 AC-POWER Table 10-4. System Technician-Demanded Tests: AC-Power — Continued Short Test Long Test Order of Investigation Sequence Sequence D/ND Emergency Transfer Query Test (#124) (c) Cabinet Temperature Query Test (#122) (d) External Alarm Lead Query Test (#120) (e) Analog Ring Generator Initialization Test (#117) (f) Analog Ring Generator Query Test (#118) (f) Continued on next page D = Destructive, ND = Non-destructive...
Page 796 Maintenance Object Repair Procedures Table 10-5. TEST #78 AC Power Query Test Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. 2000 ABORT Response to the test request was not received within the allowable time period.
Page 797: Adm-Conn (Administered Connection)
ADM-CONN (Administered Connection) ADM-CONN (Administered Connection) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ADM-CONN MAJOR status administered-connection N Administered Connection ADM-CONN MINOR status administered-connection N Administered Connection ADM-CONN WARNING status administered-connection N Administered Connection Where N is an appropriate Administered Connection number determined via the PORT field from the Alarm or Error Log.
Page 798 Maintenance Object Repair Procedures Table 10-6. Administered Connection Error Log Entries — Continued Associated Alarm On/Off Test to Clear Error Type Data Test Level Board Value 22 (a)(b)(c)(d)(j) None None 28 (a)(b)(c)(d)(e) None None 29 (a)(b)(c)(k) None None 31 (a)(b)(c)(g) None None 34 (a)(b)(c)(l)
Page 799 ADM-CONN (Administered Connection) Table 10-6. Administered Connection Error Log Entries — Continued Associated Alarm On/Off Test to Clear Error Type Data Test Level Board Value 111 (a)(b)(c)(q) None None 127 (a)(b)(c)(g) None None Continued on next page Notes: a. These errors have no specific test associated with them. Refer to Notes b through p for an explanation and appropriate action.
Page 800 Maintenance Object Repair Procedures g. The destination endpoint is not available. Check the status of the destination endpoint (using status access-endpoint or status data-module) and verify that the endpoint is not busy or otherwise unavailable (for example, out-of-service). The status for the destination endpoint is not available on the switch where this error is logged.
Page 801: Adx8D-Bd (Audix Circuit Pack)
ADX8D-BD (AUDIX Circuit Pack) ADX8D-BD (AUDIX Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO ADX8D-BD MINOR or test board PCSS sh AUDIX Circuit Pack WARNINGS UU is the universal cabinet number (1 for PPN, 2 - 3 for EPNs). C is the carrier designation (A, B, C, D, or E).
Page 802: Adx8D-Pt (Audix Digital Port)
Maintenance Object Repair Procedures ADX8D-PT (AUDIX Digital Port) MO Name (in Alarm Alarm Log) Level Initial Command To Run Full Name of MO ADX8D-PT MINOR test port PCSSpp l AUDIX Digital Port ADX8D-PT WARNING test port PCSSpp sh AUDIX Digital Port UU is the universal cabinet number (1 for PPN, 2 - 3 for EPNs).
Page 803 ADX8D-PT (AUDIX Digital Port) Error Log Entries and Test to Clear Values Table 10-7. EMBEDDED AUDIX Digital Port Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test port PCSSpp sh r 1 1(a) 40987 None...
Page 804 Maintenance Object Repair Procedures e. The circuit pack is administered but not physically installed. The alarm will clear when a circuit pack is inserted. f. The circuit pack has been removed or has been insane for more than 21 minutes. To clear the error, reinsert or replace the AUDIX circuit pack (see p caution at the beginning of this section).
Page 805 ADX8D-PT (AUDIX Digital Port) NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The tests listed below apply only to DIG-LINE and not to EMBEDDED AUDIX. These are referred to as NO-OP tests, and they always return PASS. Electronic Power Feed Test (#11) Station Lamp Updates Test (#16) Station (Digital) Audits Test (#17)
Page 806 Maintenance Object Repair Procedures Table 10-8. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use. 1. Use the display port PCSSpp command to determine the voice port extension of the port.
Page 807 ADX8D-PT (AUDIX Digital Port) Table 10-8. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL The NPE of the tested port is transmitting in error. This causes noisy and unreliable connections. Failure code 1 indicates that the Crosstalk test failed on the primary channel.
Page 808 Maintenance Object Repair Procedures Table 10-9. TEST #13 Voice and Control Channel Local Loop Test Error Test Code Result Description/Recommendation ABORT Internal System Error. Try (a). 1000 ABORT System resources required to run this test are not available. The port may be in use. 1.
Page 809 ADX8D-PT (AUDIX Digital Port) Table 10-9. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation FAIL Conference Test failed on the primary channel. Some users may not notice a disruption in service. In extreme cases, the conferencing feature may not work at all.
Page 810: Adx16D-B (16 Port Audix Circuit Pack)
Maintenance Object Repair Procedures ADX16D-B (16 Port AUDIX Circuit Pack) MO Name (in Alarm Alarm Log) Level Initial Command To Run Full Name of MO ADX16D-B MINOR test board PCSS sh AUDIX Circuit Pack ADX16D-B WARNING test board PCSS sh AUDIX Circuit Pack UU is the universal cabinet number (1 for PPN, 2 - 3 for EPNs).
Page 811: Adx16D-P (16-Port Audix Digital Port)
ADX16D-P (16-Port AUDIX Digital Port) ADX16D-P (16-Port AUDIX Digital Port) MO Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO ADX16D-P MINOR or WARNINGS test port PCSSpp l AUDIX Digital Port UU is the universal cabinet number (1 for PPN, 2-3 for EPNs). C is the carrier designation (A, B, C, D, or E).
Page 812 Maintenance Object Repair Procedures Error Log Entries and Test to Clear Values Table 10-10. EMBEDDED AUDIX Digital Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 1(a) 40987 None...
Page 813 ADX16D-P (16-Port AUDIX Digital Port) e. The circuit pack is administered but not physically installed. The alarm will clear when a circuit pack is inserted. f. The circuit pack has been removed or has been insane for more than 21 minutes.
Page 814 Maintenance Object Repair Procedures NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The tests listed below apply only to DIG-LINE and not to EMBEDDED AUDIX. These tests always return PASS. Electronic Power Feed Test (#11) Station Lamp Updates Test (#16) Station (Digital) Audits Test (#17) Digital Terminal Remote Loop Around Test (1201)
Page 815 ADX16D-P (16-Port AUDIX Digital Port) Table 10-11. TEST #9 NPE Crosstalk Test Error Test Code Result Description/Recommendation ABORT 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.
Page 816 Maintenance Object Repair Procedures Table 10-11. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of tone detectors present, or some tone detectors may be out-of-service.
Page 817 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 Switch Processing Element (SPE) and the EMBEDDED AUDIX port circuit. The SPE sends a message to loop around both the information and control channels for the port.
Page 818 Maintenance Object Repair Procedures Table 10-12. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation 1002 ABORT The system could not allocate time slots for the test. The system may be under heavy traffic conditions, or it may have time slots that are out-of-service due to TDM-BUS errors.
Page 819 ADX16D-P (16-Port AUDIX Digital Port) Table 10-12. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation FAIL Conference Test failed on the primary channel. In some cases, users may not notice a disruption in service. In extreme cases, the conferencing feature may not work at all.
Page 820: Adx16A-Pt (Audix Analog Line/Control Link)
Maintenance Object Repair Procedures ADX16A-PT (AUDIX Analog Line/Control Link) MO Name (in Alarm Initial Command To Alarm Log) Level Full Name of MO ADXCL-PT or MINOR test port PCSSpp l AUDIX Analog Line/ Control Link ADX16A-PT ADXCL-PT or WARNING test port PCSSpp sh AUDIX Analog Line/ Control Link ADX16A-PT UU is the universal cabinet number (1 for PPN, 2 - 3 for EPNs).
Page 821 ADX16A-PT (AUDIX Analog Line/Control Link) Error Log Entries and Test to Clear Values Table 10-13. EMBEDDED AUDIX Analog Line/Control Link Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 1(a) 40977 None...
Page 822 Maintenance Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. By clearing error codes associated with the Loop Around Test #161 for example, you may also clear errors generated from other tests in the testing sequence. Short Test Long Test Order of Investigation...
Page 823 ADX16A-PT (AUDIX Analog Line/Control Link) Table 10-14. TEST #6 NPE Crosstalk Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources for this test. Try (a). 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call.
Page 824 Maintenance Object Repair Procedures Table 10-14. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. 1. Use the display port PCSSpp command to determine the station extension.
Page 825 ADX16A-PT (AUDIX Analog Line/Control Link) Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. Table 10-15. TEST #7 Conference Circuit Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources to run this test.
Page 826 Maintenance Object Repair Procedures Table 10-15. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation 2100 ABORT Could not allocate the necessary system resources for this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 827 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 10-16. TEST #161 Loop Around Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources for this test. Try (a).
Page 828 Maintenance Object Repair Procedures Table 10-16. TEST #161 Loop Around Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT Test disabled by administration. To enable the test for the particular analog station being tested, enter the change station <extension> command and change the field on the Test? Station Form from...
Page 829: Alarm-Pt (Alarm Port)
ALARM-PT (ALARM PORT) ALARM-PT (ALARM PORT) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ALARM-PT test port PCSSpp l Alarm-Port ALARM-PT test port PCSSpp sh Alarm-Port Where P is the port network number (1 for PPN and 2 or 3 for EPN); C is the carrier designation (for example, A, B, C, D, or E);...
Page 830: Anl-24-L (24-Port Analog Line)
Maintenance Object Repair Procedures ANL-24-L (24-Port Analog Line) MO Name (in Initial Command to Alarm Level Full Name of MO Alarm Log) ANL-24-L test port PCSSpp l 24-Port Analog Line ANL-24-L test port PCSSpp sh 24-Port Analog Line Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
Page 831 ANL-24-L (24-Port Analog Line) Error Log Entries and Test to Clear Values Table 10-17. 24-Port Analog Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 1(a) 40960 none 40975...
Page 832 Maintenance Object Repair Procedures 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. Call the terminal equipment and verify that the terminal rings.
Page 833 ANL-24-L (24-Port Analog Line) 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 usually part of the long test sequence and takes about 20 to 30 seconds to complete.
Page 834 Maintenance Object Repair Procedures Table 10-18. TEST #6 NPE Crosstalk Test — Continued Error Test Description/Recommendation Code Result 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of tone detectors present or some tone detectors may be out-of-service.
Page 835 ANL-24-L (24-Port Analog Line) Table 10-18. TEST #6 NPE Crosstalk Test — Continued Error Test Description/Recommendation Code Result FAIL This test can fail due to on-board or off-board problems. Off-board problems include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators.
Page 836 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 10-19. TEST #7 Conference Circuit Test Error Test Description/Recommendation Code Result ABORT Could not allocate the necessary system resources to run this test.
Page 837 ANL-24-L (24-Port Analog Line) Table 10-19. TEST #7 Conference Circuit Test — Continued Error Test Description/Recommendation Code Result 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT System resources required to run this test are not available. 1.
Page 838 Maintenance Object Repair Procedures Battery Feed Test (also called Port Diagnostic Test) (#35) The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing, transmission, and balance. This test checks the signaling and switchhook capabilities of the battery feed chip by terminating the port, applying battery and detecting the resulting current.
Page 839 ANL-24-L (24-Port Analog Line) Table 10-20. TEST #35 Battery Feed Test — Continued Error Test Description/Recommendation Code Result 1392 ABORT This port is currently a TTI port and the test will not execute on 1. Verify that the port is a TTI port using either the display port command (the display shows that the port is a TTI port) or the list config command (the display shows a t for the port).
Page 840 Maintenance Object Repair Procedures Table 10-20. TEST #35 Battery Feed Test — Continued Error Test Description/Recommendation Code Result PASS The port’s battery feed chip is able to provide power to the station equipment to detect on-/off-hook, but may not be able to supply power for touch-tones.
Page 841 ANL-24-L (24-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 10-21. Test #36 Station Status and Translation Audits and Updates Error Test Description/Recommendation...
Page 842 Maintenance Object Repair Procedures Table 10-21. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Description/Recommendation Code Result FAIL This does not indicate a hardware problem. The switchhook audit failed. The other updates were not performed because of this failure.
Page 843 ANL-24-L (24-Port Analog Line) Station Present Test (also called 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 844 Maintenance Object Repair Procedures Table 10-22. TEST #48 Station Present Test — Continued Error Test Description/Recommendation Code Result 1018 ABORT The test has been disabled by administration.The default for Test field on the station form is y. Determine why this field has been set to on this station (this may be due to the brief ringing disturbance that this test may cause).
Page 845 ANL-24-L (24-Port Analog Line) Table 10-22. TEST #48 Station Present Test — Continued Error Test Description/Recommendation Code Result FAIL The terminal equipment is not connected to the circuit pack. Some terminal equipment, such as modems, may fail even when connected properly. 1.
Page 846 Maintenance Object Repair Procedures Looparound Test (#161) 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 10-23.
Page 847 ANL-24-L (24-Port Analog Line) Table 10-23. TEST #161 Looparound Test — Continued Error Test Description/Recommendation Code Result 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. 1. Use the display port PCSSpp command to determine the station extension.
Page 848 Maintenance Object Repair Procedures Table 10-23. TEST #161 Looparound Test — Continued Error Test Description/Recommendation Code Result FAIL The reflective loop around 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. 1.
Page 849: Anl-16-L (16-Port Neon Analog Line)
ANL-16-L (16-Port Neon Analog Line) ANL-16-L (16-Port Neon Analog Line) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ANL-16-L test port PCSSpp l 16-Port Neon Analog Line ANL-16-L test port PCSSpp sh release station <ext> 16-Port Neon Analog Line Where P is the port network number (1 for PPN and 2 or 3 for EPN);...
Page 850 Maintenance Object Repair Procedures Hardware Error Log Entries and Test to Clear Values Table 10-24. 16-Port Neon Analog Line Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test port PCSSpp sh r 1 1 (a) 40960 none...
Page 851 ANL-16-L (16-Port Neon Analog Line) b. This is a software audit error that does not indicate any hardware malfunction. Run Short Test Sequence and investigate associated errors (if any). c. This error type indicates that the circuit pack has been removed or has been insane for more than 11 minutes.
Page 852 Maintenance Object Repair Procedures NPE Crosstalk Test (#6) One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM Bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis. The 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.
Page 853 ANL-16-L (16-Port Neon Analog Line) Table 10-25. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of Tone Detectors present or some Tone Detectors may be out-of-service.
Page 854 Maintenance Object Repair Procedures Table 10-25. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL This test can fail due to on-board or off-board problems. Off-board problems of concern include EXP-INTF faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators.
Page 855 ANL-16-L (16-Port Neon Analog Line) Conference Circuit Test (#7) One or more NPEs reside on each circuit pack with a TDM Bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis. The Conference Circuit Test verifies that the NPE channel for the port being tested can correctly perform the conferencing function.
Page 856 Maintenance Object Repair Procedures Table 10-26. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT The test has been disabled via administration. The default for the ’Test’ field on the ’Station’ form is ’y’; thus, you may want to determine why this field has been set to ’n’...
Page 857 ANL-16-L (16-Port Neon Analog Line) Table 10-26. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This will cause noisy and unreliable connections. 1. Issue the display port and the status station commands to determine if the station is idle.
Page 858 Maintenance Object Repair Procedures Battery Feed Test (also called 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 by trying to detect a current.
Page 859 ANL-16-L (16-Port Neon Analog Line) Table 10-27. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation 1005 ABORT 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).
Page 860 Maintenance Object Repair Procedures Table 10-27. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation 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.
Page 861 ANL-16-L (16-Port Neon 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 (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 862 Maintenance Object Repair Procedures Table 10-28. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate the necessary system resources to run this test.
Page 863 ANL-16-L (16-Port Neon Analog Line) Table 10-28. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/Recommendation FAIL This does not indicate a hardware problem. However, there may be an internal software error. The message waiting lamp update failed.
Page 864 Maintenance Object Repair Procedures Station Present Test (also called Ringing Application Test) (#48) This test provides a burst of ringing current to the terminal equipment and detects that current flows. This test ascertains whether terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 865 ANL-16-L (16-Port Neon Analog Line) Table 10-29. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation 1008 ABORT Could not allocate a ringing circuit. Either all the ringing circuits are in use or the ringing generator is defective or it is not wired correctly.
Page 866 Maintenance Object Repair Procedures Table 10-29. TEST #48 Station Present Test — Continued Error Test Code 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.
Page 867 ANL-16-L (16-Port Neon Analog Line) Loop Around Test (#161) Each Analog port consists of: an NPE for port connectivity and gain, and conferencing functionality a code that converts the digital signals of the TDM Bus to analog signals a battery feed chip that provides power to the telephone set for signaling, dial pulsing, transmission, and balance This test is designed to check the on-board transmission capabilities of the NPE, the codec, and the battery feed chip of the analog port.
Page 868 Maintenance Object Repair Procedures Table 10-30. TEST #161 Loop Around Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test are not available.
Page 869 ANL-16-L (16-Port Neon Analog Line) Table 10-30. TEST #161 Loop Around Test — Continued Error Test Code Result Description/Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. Use the display port PCSSpp command to determine the station extension.
Page 870 Maintenance Object Repair Procedures Table 10-30. TEST #161 Loop Around Test — Continued Error Test Code Result Description/Recommendation FAIL The reflective loop around 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.
Page 871: Anl-Bd (Analog Line Circuit Pack)
ANL-BD (Analog Line Circuit Pack) ANL-BD (Analog Line Circuit Pack) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ANL-BD test board PCSS sh 8-Port Analog Line Circuit Pack ANL-BD test board PCSS sh 8-Port Analog Line Circuit Pack ANL-BD test board PCSS sh...
Page 872: Anl-Line (8-Port Analog Line), Anl-Ne-L (8-Port Neon Analog Line)
Maintenance Object Repair Procedures ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ANL-LINE test port PCSSpp l 8-Port Analog Line ANL-LINE test port PCSSpp sh 8-Port Analog Line ANL-NE-L test port PCSSpp l...
Page 873 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Hardware Error Log Entries and Test to Clear Values Table 10-31. 8-Port Analog Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 1 (a) 40960 None...
Page 874 Maintenance Object Repair Procedures rings. If the terminal doesn’t ring, then replace it. Otherwise, issue the test port PCSSpp command, and follow the procedure for Test #48. — 40977 indicates that no terminal equipment was connected when ringing was attempted. Run the Short Test via the test port PCSSpp command, and follow the procedure for the results of Test #48.
Page 875 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) NPE Crosstalk Test (#6) One or more NPEs reside on each circuit pack with a TDM Bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis.
Page 876 Maintenance Object Repair Procedures Table 10-32. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of Tone Detectors present or some Tone Detectors may be out-of-service.
Page 877 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-32. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1020 ABORT The test did not run due to a previously existing error on the specific port or a more general circuit pack error. 1.
Page 878 Maintenance Object Repair Procedures Table 10-32. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL This test can fail due to on-board or off-board problems. Off-board problems of concern include EXP-INTF faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators.
Page 879 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-32. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation The test could not relate the internal ID to the port (no board). BOARD This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 880 Maintenance Object Repair Procedures Battery Feed Test (also called 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 881 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-33. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT Test disabled via administration. The default for the ’Test’ field on the ’Station’ form is ’y’; thus, you may want to determine why this field has been set to ’n’...
Page 882 Maintenance Object Repair Procedures Table 10-33. TEST #35 Battery Feed Test — Continued Error Test Code 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.
Page 883 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon 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 (such as station type, dial type, network connection) with information kept in the software.
Page 884 Maintenance Object Repair Procedures Table 10-34. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/Recommendation 1006 ABORT This port has been busied out by command or taken out-of-service by the failure of the NPE Crosstalk Test. 1.
Page 885 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-34. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/Recommendation FAIL This does not indicate a hardware problem but may be an internal software error.
Page 886 Maintenance Object Repair Procedures Loop Around and Conference Test (#47) Each Analog Port consists of: an NPE for port connectivity and gain, and conferencing functionality a code that converts the digital signals of the TDM Bus to analog signals a battery feed chip that provides power to the telephone set for signaling, dial pulsing, transmission, and balance.
Page 887 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) BFC* TN742, TN769, ETC. CODEC PORT TONE TONE LEVEL NPE* SOURCE MEASUREMENT TDM BUS * BFC - BATTERY FEED AND HYBRID CHIP NPE - NETWORK PROCESSING ELEMENT Figure 10-3. Analog Loop Around and Conference Test 555-233-123 Issue 4 May 2002 10-101...
Page 888 Maintenance Object Repair Procedures Table 10-35. TEST #47 Loop Around and Conference Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 889 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-35. TEST #47 Loop Around and Conference Test — Continued Error Test Code Result Description/Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of Tone Detectors present or some Tone Detectors may be out-of-service.
Page 890 Maintenance Object Repair Procedures Table 10-35. TEST #47 Loop Around and Conference Test — Continued Error Test Code Result Description/Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT System resources required to run this test are not available. Either a system allocation to get information about the port or to put the port into a service state failed or the attempt to put the port in connection with a tone source failed (this could be a...
Page 891 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-35. TEST #47 Loop Around and Conference Test — Continued Error Test Code Result Description/Recommendation FAIL 1. Disconnect the terminal equipment from the circuit pack at the cross-connect and run the test again. (cont’d.) 2.
Page 892 Maintenance Object Repair Procedures Table 10-35. TEST #47 Loop Around and Conference Test — Continued Error Test Code 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 893 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-36. TEST #48 Station Present Test Error Test Code Result Description/Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 894 Maintenance Object Repair Procedures Table 10-36. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation 1008 ABORT Could not allocate a ringing circuit for one of the following reasons: All the ringing circuits are in use, or The ringing generator is defective, or It is not wired correctly.
Page 895 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 10-36. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation FAIL The terminal equipment is not connected to the circuit pack or the ringing generator may have failed. 1.
Page 896 Maintenance Object Repair Procedures Table 10-36. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation The test could not relate the internal ID to the port (no board). BOARD This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 897: An-Ln-Pt (Analog Line Port)
AN-LN-PT (Analog Line Port) AN-LN-PT (Analog Line Port) MO Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO AN-LN-PT test port UUCSSpp l Analog Line Port AN-LN-PT test port UUCSSpp sh Analog Line Port UU is the universal cabinet number (1 for PPN, 2 -3 for EPNs). C is the carrier designation (A, B, C, D, or E).
Page 898 Maintenance Object Repair Procedures Error log entries and test to clear values Table 10-37. Analog line error log entries Error Associated Alarm On/Off Type Data Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1(a) 40960 none 40975 40977...
Page 899 AN-LN-PT (Analog Line Port) 1. Call the terminal equipment and verify that the terminal rings. 2. If the terminal does not ring, then replace it. 3. Otherwise, issue the test port UUCSSpp command, and follow the procedure for Test #48. 40977 indicates that no terminal equipment was connected when ringing was attempted.
Page 900 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 Battery Feed Test, for example, you may also clear errors generated from other tests in the testing sequence.
Page 901 AN-LN-PT (Analog Line Port) NPE Crosstalk Test (#6) This test verifies that the 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 the long test sequence and takes about 20 to 30 seconds to complete.
Page 902 Maintenance Object Repair Procedures Table 10-38. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized for the number of tone detectors present or some tone detectors may be out-of-service.
Page 903 AN-LN-PT (Analog Line Port) Table 10-38. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL This test can fail due to on-board or off-board problems. Off-board problems include TDM-BUS faults, EXP-PN and EXP-INTF faults, and faults associated with the tone detectors/tone generators.
Page 904 Maintenance Object Repair Procedures Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested correctly performs the conferencing function. Table 10-39. TEST #7 Conference Circuit Test Error Test Code Result Description/Recommendation ABORT Necessary system resources could not be allocated to run this test.
Page 905 AN-LN-PT (Analog Line Port) Table 10-39. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT System resources required to run this test are not available. 1.
Page 906 Maintenance Object Repair Procedures Battery Feed Test (also called 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 907 AN-LN-PT (Analog Line Port) Table 10-40. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT 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).
Page 908 Maintenance Object Repair Procedures Table 10-40. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation FAIL The port’s battery feed chip is unable to supply sufficient power to the terminal equipment. This test result might be marginal, and the terminal equipment may be operating satisfactorily.
Page 909 AN-LN-PT (Analog Line Port) Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 10-41. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 910 Maintenance Object Repair Procedures Table 10-41. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description/Recommendation 2100 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals no more than 5 times.
Page 911 AN-LN-PT (Analog Line Port) Table 10-41. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description/Recommendation FAIL The ringer update failed. There may be an internal software error. 1. Retry the command at 1-minute intervals no more than 5 times.
Page 912 Maintenance Object Repair Procedures Table 10-42. TEST #48 Station Present Test Error Test Code Result Description/Recommendation ABORT Necessary system resources could not be allocated to run this test. 1. Retry the command at 1-minute intervals no more than 5 times. 2.
Page 913 AN-LN-PT (Analog Line Port) Table 10-42. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation 1008 ABORT A ringing circuit could not be allocated. Either all of the ringing circuits are in use, the ringing generator is defective, or it is not wired correctly.
Page 914 Maintenance Object Repair Procedures Table 10-42. TEST #48 Station Present Test — Continued Error Test Code 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.
Page 915 AN-LN-PT (Analog Line Port) Looparound Test (#161) 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 10-43.
Page 916 Maintenance Object Repair Procedures Table 10-43. TEST #161 Looparound Test — Continued Error Test Code Result Description/Recommendation 1004 ABORT A valid call seized the port during the test and aborted the test. 1. Use the display port UUCSSpp command to determine the station extension.
Page 917 AN-LN-PT (Analog Line Port) Table 10-43. TEST #161 Looparound Test — Continued Error Test Code Result Description/Recommendation FAIL The reflective Looparound 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. 1.
Page 918: Ann-Bd (Announcement Circuit Pack)
Maintenance Object Repair Procedures ANN-BD (Announcement Circuit Pack) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ANN-BD MINOR test board PCSS l Announcement Circuit Pack ANN-BD test board PCSS l Announcement Circuit Pack Where P is the port network number (1 for PPN and 2 or 3 for EPN); C is the carrier designation (for example, A, B, C, D, or E);...
Page 919 ANN-BD (Announcement Circuit Pack) General Notes Here are a few very 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.
Page 920 It may also be necessary to save and restore announcements as part of the maintenance procedures. For a complete description of integrated announcement administration, see the Administrator’s Guide for Avaya MultiVantage Software. 10-134...
Page 921 ANN-BD (Announcement Circuit Pack) 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 Feature Access Code (FAC), administered as Announcement access code on the FACs form.
Page 922 Maintenance Object Repair Procedures Hardware Error Log Entries and Test to Clear Values Table 10-44. Announcement Circuit Pack Error Log Entries Alarm Level Error Associated (See WARNING Type Data Test below) Board Test to Clear Value test board PCSS sh r 1 1(a) Circuit pack MINOR...
Page 923 ANN-BD (Announcement Circuit Pack) Table 10-44. Announcement Circuit Pack Error Log Entries — Continued Alarm Level Error Associated (See WARNING Type Data Test below) Board Test to Clear Value 2561 Super Frame MINOR test board PCSS sh r 3 Match Inquiry Test (#211) 17676 In-line Error...
Page 924 Maintenance Object Repair Procedures WARNING: Reseating and/or replacing the circuit pack results in loss of integrated announcements. See “General Notes” near the beginning of this Maintenance procedure.  b. Error Type 14 Whenever the Announcement Checksum Test (#209) fails, this error is logged. The Aux Data indicates the number of the first defective announcement found.
Page 925 ANN-BD (Announcement Circuit Pack)  j. Error Type 1281 The SP found a fault in the speech main memory (SMM) (that is, it found one or more faulty memory locations). Whenever this error is logged, error 2817 is also logged [see Note (k)], which causes the maintenance system to run the Announcement Checksum Test (#209) to determine if the bad memory location was being used by an announcement.
Page 926 Maintenance Object Repair Procedures  o. 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. If error type 1538 is also present, then the circuit pack was taken out-of-service due to hyperactivity.
Page 927 ANN-BD (Announcement Circuit Pack) Angel-Speech Processor (SP) Handshake Test (#208) This test checks the integrity of the communication link between the two processors on the Announcement circuit pack. Failure of this test indicates that the Speech Processor is insane and results in the loss of all integrated announcements on the circuit pack.
Page 928 Maintenance Object Repair Procedures Announcement Checksum Test (#209) Associated with every recorded announcement is a checksum. In this test, the SP checks a stored global checksum covering all recorded announcements against a calculated one and returns the results to the maintenance system. If the global checksum failed, maintenance requests the SP to check each individual announcement’s checksum.
Page 929 ANN-BD (Announcement Circuit Pack) Table 10-47. TEST #209 Announcement Checksum Test — Continued Error Test Code Result Description/Recommendation 1024 ABORT This abort code is given for the following reasons: 1. An announcement upload or download is in progress. 2. An announcement upload or download is requested when this test is running.
Page 930 Maintenance Object Repair Procedures Table 10-47. TEST #209 Announcement Checksum Test — Continued Error Test Code Result Description/Recommendation 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 931 ANN-BD (Announcement Circuit Pack) Table 10-47. TEST #209 Announcement Checksum Test — Continued Error Test Code 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.
Page 932 Maintenance Object Repair Procedures 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.
Page 933 ANN-BD (Announcement Circuit Pack) Table 10-48. TEST #210 140AY Loop Around Test — Continued Error Test Code Result Description/Recommendation 1002 ABORT The system could not allocate time slots for the test. The system may be under heavy traffic conditions or it may have time slots out-of-service due to TDM-BUS errors.
Page 934 Maintenance Object Repair Procedures Table 10-48. TEST #210 140AY Loop Around Test — Continued Error Test Code Result Description/Recommendation 1024 ABORT Announcement circuit pack blocked the test because an announcement download is in progress. If an announcement download is in progress, a status data-module <announcement data extension>...
Page 935 ANN-BD (Announcement Circuit Pack) Table 10-48. TEST #210 140AY Loop Around Test — Continued Error Test Code Result Description/Recommendation ABORT Internal System Error. 1. Retry the command at 1-minute intervals a maximum of 5 times. FAIL Test failed. The error code indicates at which speech compression rate the test actually failed (one being the first rate tested, three being the last).
Page 936 Maintenance Object Repair Procedures 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 937 ANN-BD (Announcement Circuit Pack) Table 10-49. TEST #211 Super Frame Match Inquiry — Continued Error Test Code Result Description/Recommendation FAIL Test failed. Announcement playbacks should sound corrupted. 1. Reset the circuit pack via the reset board PCSS command and then run this test again. If the test continues to fail, replace the circuit pack (see Warning).
Page 938 Maintenance Object Repair Procedures Table 10-50. TEST #212 Clock Match Inquiry Test Error Test Code Result Description/Recommendation 2000 ABORT 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.
Page 939 ANN-BD (Announcement Circuit Pack) Table 10-50. TEST #212 Clock Match Inquiry Test — Continued Error Test Code Result Description/Recommendation 3. If this is a Standard system (that is, not a High or Critical Reliability system), replace the ANN-BD. Rerun the test. If the test continues to fail, replace the Tone-Clock circuit pack located in the same Port Network as the ANN-BD.
Page 940: Ann-Pt (Announcement Port)
Maintenance Object Repair Procedures ANN-PT (Announcement Port) MO Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO ANN-PT MINOR test port PCSSpp l Announcement Port ANN-PT test port PCSSpp l Announcement Port Where P is the port network number (1 for PPN and 2 or 3 for EPN); C is the carrier designation (for example, A, B, C, D, or E);...
Page 941 ANN-PT (Announcement Port) 2. If a customer has announcements on the Announcement circuit pack that cannot be re-recorded easily, then announcements must be saved on the system tape to ensure that they are not lost. This should be done as soon as the announcements are recorded on the circuit pack (or whenever they are changed), assuming that the pack is in proper working order (see Note).
Page 942 It may also be necessary to save and restore announcements as part of the maintenance procedures. For a complete description of integrated announcement administration, see Administrator’s Guide for Avaya MultiVantage Software. Announcement Session Announcements can be recorded, played back, and deleted from an announcement session.
Page 943 ANN-PT (Announcement Port) 4. Either the announcement data module is busy or all the administered NETCON data modules are busy. 5. There is no tape in the system. 6. The tape in the system does not have a valid announcement file saved on it.
Page 944 Maintenance Object Repair Procedures b. This error is logged and the port is alarmed when an alarm is raised on the Announcement circuit pack because of a faulty condition with a common circuit pack resource. Any one of the following alarmed errors on the Announcement circuit pack causes this error to be logged against the Announcement Port: 1793, 2049, 2305, 2561.
Page 945 ANN-PT (Announcement Port) Table 10-52. TEST #205 Channel Administration Memory Array (CAMA) Test Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use on a valid call. 1.
Page 946 Maintenance Object Repair Procedures 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 947 ANN-PT (Announcement Port) number, the more severe the problem with that port. If this test fails, announcements played over this port should sound corrupted. Table 10-53. TEST #206 Playback Speech Memory Array (PSMA) Test Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available.
Page 948 Maintenance Object Repair Procedures Table 10-53. TEST #206 Playback Speech Memory Array (PSMA) Test — Continued Error Test Code Result Description/Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate the necessary system resources to run this test.
Page 949 ANN-PT (Announcement Port) Table 10-53. TEST #206 Playback Speech Memory Array (PSMA) Test — Continued Error Test Code Result Description/Recommendation FAIL Test failed. The Announcement Port and the Tone Detector never synchronized. Check for active GPTD-PT errors, and refer to “GPTD-PT [General Purpose Tone Detector Port (CPTR)]”...
Page 950 Maintenance Object Repair Procedures 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 951 ANN-PT (Announcement Port) 140AY Channel Sanity Inquiry Test (#222) The Angel keeps a sanity status bit for each of the 16 channels on the 140AY device. This test queries the Angel to determine the status for a particular channel. If a channel is insane, that implies that announcements cannot be played back on that channel.
Page 952: Announce (Announce)
Maintenance Object Repair Procedures ANNOUNCE (Announce) MO Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO ANNOUNCE none none ANNOUNCEMENT The ANNOUNCE MO logs an error in the hardware error log if at least one of the following is true: The save announcements or restore announcements command does not complete successfully, or the...
Page 953 ANNOUNCE (Announce) Hardware Error Log Entries ANNOUNCE Error Log Entries Associated Alarm On/Off Error Type Data Test Level Board Test to Clear Value 1(a)(f) None 257(b)(f) None 513(c)(f) None 769(d)(f) None 1025(e)(f) None Notes: a. Error occurred while saving announcements. (See Table 10-42 in the next section for an explanation of Aux Data and for recommended repair actions.) b.
Page 954 Maintenance Object Repair Procedures Aux Data Error Codes and Recommended Repair Procedures Table 10-55. Aux Data Error Codes and Recommended Repair Procedures Data Description/Recommendation 9000 CARD-MEM [386 systems] errors. through 9031 Check and resolve CARD-MEM [386 systems] errors and alarms. 30001 Tape [286 systems] errors.
Page 955 ANNOUNCE (Announce) Table 10-55. Aux Data Error Codes and Recommended Repair Procedures — Continued Data Description/Recommendation 32006 Announcement Data Module not available. 1. Use the status command to check the status of the Announcement Data Module. 32007 Announcement Data Module out of service. 1.
Page 956 Maintenance Object Repair Procedures Table 10-55. Aux Data Error Codes and Recommended Repair Procedures — Continued Data Description/Recommendation 32015 Time of day not set. 1. Set the time of day, and reenter the save/restore announcements command. 32016 Internal System errors. Check for any other ANNOUNCE errors and take corrective action.If there are no other announcements errors, do the following: 1.
Page 957: Asai-Bd (Multi-Application Platform Board)
ASAI-BD (Multi-Application Platform Board) ASAI-BD (Multi-Application Platform Board) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ASAI-BD test board PCSS sh ASAI-BD ASAI-BD test board PCSS sh ASAI-BD Where P is the port network number (1 for PPN and 2 or 3 for EPN); C is the carrier designation (for example, A, B, C, or D);...
Page 958 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 a typical port board on or off. On the MAPD, only the red LED is controlled by this message.
Page 959: Asai-Ept
MINOR, or MAJOR for all ASAI adjuncts in the system. The maintenance strategy for this endpoint MO is built on maintenance facilities offered in the Avaya ISDN-BRI protocol and in the ASAI adjuncts. Currently there are no facilities in the protocol that provide for maintenance of set data features.
Page 960 Timers associated with certain Layer 3 messages have expired before a required response was received. In the following table, the aux data column indicates which timer has just expired. For more information, refer to the Avaya ISDN-BRI Specification. Aux Data Timer Type...
Page 961 See “status bri-port” in Chapter 8 for an explanation of the ASAI link states. For ASAI or Avaya adjuncts, the switch queries the adjunct every two minutes. The Layer 3 Query Test is not executed for ASAI or Avaya adjuncts through a command issued from the management terminal. While alarmed for this error, the switch takes the associated port out-of-service for five seconds every 15 minutes.
Page 962 Maintenance Object Repair Procedures f. This error occurs when the ASAI-EPT 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 adjunct.
Page 963 ASAI-EPT l. The switch software logs certain ASAI cause values. The cause value is determined from the following formula: — If the error type is greater than 3968, then the ASAI cause value is equal to the error type minus 3968. The switch sent this value to the endpoint.
Page 964 Maintenance Object Repair Procedures Table 10-57. ASAI Cause Values — Continued Code Explanation Recommendation Requested Requested facility is implemented, but not administered. facility not Potential administration problem with endpoint or adjunct. subscribed For BRI endpoints: 1. Verify the switch administration of endpoint using either the display station or display data-module commands.
Page 965 ASAI-EPT Table 10-57. ASAI Cause Values — Continued Code Explanation Recommendation Service or Requested service or option (or combination of selected option not options) is not supported (implemented) in switch or the implemented adjunct. 1. Consult switch and adjunct documentation to determine ASAI service and options supported by both switch and adjunct.
Page 966 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 967 ASAI-EPT Table 10-58. TEST #626 Signaling Link Status Test — Continued Error Test Code Result Description/Recommendation 2012 ABORT Internal system error 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 968: Asai-Pt
Maintenance Object Repair Procedures ASAI-PT MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ASAI-PT MAJOR test port PCSSpp l ASAI ISDN BRI Port ASAI-PT WARNING test port PCSSpp l ASAI ISDN BRI Port Where P is the port network number (1 for PPN and 2 or 3 for EPN);...
Page 969 ASAI-PT Error Log Entries and Test to Clear Values Table 10-59. ASAI-PT Port Error Log Entries Error Alarm Level On/Off Type Data Associated Test ASAI-PORT Board Test to Clear Value test port PCSSpp sh r 1 1 (a) Level 1 Status test port PCSSpp sh r 2 Inquiry (#621) 513 (b)
Page 970 Maintenance Object Repair Procedures c. The port received an invalid frame over the D-channel. When the Cyclical Redundancy Check (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 one minute.
Page 971 ASAI-PT BRI Port Local LAN Looparound Test (#618) This test is destructive. This test verifies the connectivity of a BRI port across the LAN Bus and executes only if the port is out-of-service. The test aborts if calls associated with the port are in-progress.
Page 972 Maintenance Object Repair Procedures Table 10-60. TEST #618 BRI Port Local LAN Looparound Error Test Code Result Description/Recommendation 1015 ABORT The port is not in the out-of-service state. 1. Display the Port Status form using the status bri-port PCSSpp command to determine which stations or adjuncts are on this port.
Page 973 ASAI-PT Table 10-60. TEST #618 BRI Port Local LAN Looparound — Continued Error Test Code Result Description/Recommendation 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 974 Maintenance Object Repair Procedures Table 10-61. TEST #621 Level 1 Status Inquiry Error Test Code Result Description/Recommendation 1187 ABORT The board, port, or station may have been busied-out by a technician. 1. Look in the Error Log for Error Type 18 (port busied out) for this port and ASAI-BD (board busied out).
Page 975 ASAI-PT Table 10-61. TEST #621 Level 1 Status Inquiry — Continued Error Test Code Result Description/Recommendation 2012 ABORT Internal system error 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 976 Maintenance Object Repair Procedures Table 10-62. TEST #624 Layer 1 Transmission Error Counter Test Error Test Code Result Description/Recommendation 2000 ABORT Response was not received from the circuit pack within the allowable time period. 1. If the test aborts repeatedly a maximum of 5 times, reset the circuit pack using the busyout board PCSS and reset board PCSS commands.
Page 977 ASAI-PT Table 10-63. TEST #625 Receive FIFO Error Counter Test Error Test Code Result Description/Recommendation 2000 ABORT Response was not received from the circuit pack within the allowable time period. 1. If the test aborts repeatedly a maximum of 5 times, reset the circuit pack via the busyout board PCSS and reset board PCSS commands.
Page 978 Maintenance Object Repair Procedures 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, therefore, should neither abort nor fail.
Page 979: Asai-Res/E-Dig-Res (Tn800 Reserve Slot)
ASAI-RES/E-DIG-RES (TN800 reserve slot) ASAI-RES/E-DIG-RES (TN800 reserve slot) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ASAI-RES NONE NONE TN800 ASAI reserve slot E-DIG-RES NONE NONE TN800 DIG reserve slot There are no tests associated with these MOs. Both the test board and busy out board commands abort when either is attempted on a reserved slot.
Page 980: Atm-Bch (Atm B-Channel Trunk)
Maintenance Object Repair Procedures ATM-BCH (ATM B-Channel Trunk) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ATM-BCH MAJOR test port UUCSSppp l ATM B-Channel Trunk ATM-BCH MINOR test port UUCSSppp l ATM B-Channel Trunk ATM-BCH WARNING test port UUCSSppp sh...
Page 981 ATM-BCH (ATM B-Channel Trunk) Table 10-65. ATM ISDN service states Category Description Service states Active A call is connected over the B-channel. B-channel is in normal operating In-Service (INS) state Idle There is no call on the B-channel. Out-of-Service/Far-en The switch has not successfully negotiated B-channel connection as of d (OOS/FE) yet.
Page 982 Maintenance Object Repair Procedures Table 10-66. ATM-BCH alarms by service state Service state Alarm Possible cause Possible solution Warning Trunk busied out Release the port (release trunk grp#/mbr#). Minor NPE Crosstalk Test Replace ATM circuit pack. (#6) failed Out-of-Service/NE None ATM circuit pack lost Install circuit pack or cable.
Page 983 ATM-BCH (ATM B-Channel Trunk) Error Log Entries and Test to Clear Values Table 10-67. ATM-BCH Error Log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSppp 1(a) None test port UUCSSppp busyout trunk grp/mbr release trunk grp/mbr 129 (b) None...
Page 984 Maintenance Object Repair Procedures b. Error Type 129: the far-end switch changed its ISDN service state to either out-of-service or maintenance. This may be a temporary condition because the far-end is testing that trunk or a hardware problem with the trunk. Outgoing calls may not be allowed over that trunk.
Page 985 ATM-BCH (ATM B-Channel Trunk) i. Error Type 3585: ISDN RESTART message received. Active calls have been dropped. The following Aux Data values (Error Type 3585 only) below represent the trunk’s ISDN call state at the time Error 3585 occurred. This information can be useful if users report dropped calls on the ISDN-PRI trunks.
Page 986 Maintenance Object Repair Procedures Table 10-68. System Technician-Demanded Tests: ATM-BCH Short Test Long Test Destructive or Order of Investigation Sequence Sequence Non-destructive Signaling Link State Check Test (#255) Service State Audit Test (#256) Call State Audit Test (#257) ISDN Test Call Test (#258) Continued on next page Signaling Link State Audit Test (#255) This non-destructive test checks the status of the TN230x ATM-CES Interface...
Page 987 ATM-BCH (ATM B-Channel Trunk) Service State Audit (#256) This test checks the service state of the trunk. Country protocol 1. If the interface uses country protocol 1 (includes USA), the service-state audit executes in all trunk service states. It queries the service state on the far end and waits 2 minutes for a reply.
Page 988 Maintenance Object Repair Procedures Table 10-70. TEST #256 Service State Audit Test — Continued Error Test Code Result Description/Recommendation 1114 ABORT Signaling link in transitional state 1. Retry the command up to 5 times at 1-minute intervals. 1116 ABORT Trunk not in Out-of-Service/Far-end state and country protocol other than 1 1117 ABORT...
Page 989 ATM-BCH (ATM B-Channel Trunk) Table 10-71. TEST #257 Call State Audit Test Error Test Code Result Description/Recommendation 1018 ABORT Maintenance disabled 1. Enable maintenance by entering y in the Maintenance Tests? field on page 2 of the change trunk-group form. 1019 ABORT Audit already in progress...
Page 990 Maintenance Object Repair Procedures Synchronous Test Calls You can initiate a synchronous outgoing test call (including a test call for ISDN-PRI trunks) with these commands: test trunk grp#/mbr# long [repeat #] test board UUCSS long [repeat #] test port UUCSSpp long [repeat #] Table 10-72.
Page 991 ATM-BCH (ATM B-Channel Trunk) Table 10-72. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 1113 ABORT Signaling link failed 1. Check the results of Test #255 (Signaling Link State Check Test). 1116 ABORT Switch could not change the service state 1.
Page 992 Maintenance Object Repair Procedures Table 10-72. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 2036- ABORT Internal system error 2037 1. Retry the command up to 5 times at 1-minute intervals. 2038- ABORT Problem reading test data 2039 1.
Page 993 ATM-BCH (ATM B-Channel Trunk) Table 10-72. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 2209- ABORT Could not allocate needed resources 2210 1. Follow recommendations for ABORT code 2100. 2211 ABORT Internal system error. 1. Retry the command at 1-minute intervals a maximum of 5 times.
Page 994: Atm-Dch (Atm D-Channel Port)
Maintenance Object Repair Procedures ATM-DCH (ATM D-Channel Port) Initial System MO Name (in Alarm Technician Command Full Name of Alarm Log) Level to Run ATM-DCH MINOR test port UUCSSpp l ATM D-Channel ATM-DCH WARNING test port UUCSSpp sh ATM D-Channel pp is administered as a port in the range of 9 through 32.
Page 995 ATM-DCH (ATM D-Channel Port) Hardware Error Log Entries and Test to Clear Values Table 10-73. ATM D-channel Error Log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp 18 (a) busyout port UUCSSpp WARNING release port UUCSSpp 130 (b)
Page 996 Maintenance Object Repair Procedures Signaling Link Board Check (#643) This nondestructive test checks the health of the ATM TN230X trunk circuit pack 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 997: Atm-Intf (Tn2305/6)
ATM-INTF (TN2305/6) ATM-INTF (TN2305/6) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ATM-INTF WARNING test board UUCSSpp ATM interface board The TN2305/6 is recognized by the system as an ATM Interface board (ATM-INTF) if it has not been assigned a personality through the add atm-pnc command or add atm trunk command.
Page 998 Maintenance Object Repair Procedures Error Log Entries and Test to Clear Values Table 10-77. ATM-INTF Error Log Entries Error Alarm On/Off Test to Clear Value Type Data Associated Test Level Board 23(a) None 125(b) None 217(c) None Notes: a. Error Type 23: ATM Expansion Interface circuit pack is administered through a change circuit-pack command, but has not been inserted into the system.
Page 999 ATM-INTF (TN2305/6) Control Channel Loop-Around Test (#52) This test is non-destructive. This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 10-78. TEST #52 Control Channel Loop-Around Test Error Test Code Result Description/Recommendation 2000 ABORT...
Page 1000: Atm-Sgrp (Atm Signaling Group)
Maintenance Object Repair Procedures ATM-SGRP (ATM Signaling Group) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ATM-SGRP MINOR test sig-group grp# ATM-CES Signaling Group ATM-SGRP WARNING test sig-group grp# ATM-CES Signaling Group grp# is the signaling group number (1-166); the test sequence can be either short or long.

Avaya Definity SI Maintenance Manual

About this Book

1 Maintenance Architecture

2 Circuit Packs and Power

3 Management Terminals

4 Initialization and Recovery

5 Routine Maintenance Procedures

Reliability Systems: a Maintenance Aid

LED Interpretation

Maintenance Commands and Trouble-Clearing Aids

Quick Links

Troubleshooting

Related Manuals for Avaya Definity SI

Summary of Contents for Avaya Definity SI