Page 1 Maintenance for the Avaya™ S8700 Media Server for Multi-Connect Configurations Volumes 1, 2, and 3 555-233-143 Issue 1 May 2002...
Page 2 How to Get Help These compromises may become more acute if you fail to follow For additional support telephone numbers, go to the Avaya Web site: Avaya's recommendations for configuration, operation and use of the http://www.avaya.com/ equipment.
Page 3 Technical Service Center at 1-800-242- sion signaling is in violation of Part 68 rules. This equipment returns 2121 or contact your local Avaya representative. If the equipment is answer-supervision signals to the public switched network when: causing harm to the telephone network, the telephone company may •...
Page 4 Haverhill, MA 01835 USA but many have been registered with the FCC before the SDoC process Attention: Avaya Account Management was available. A list of all Avaya registered products may be found at: E-mail: totalware@gwsmail.com http://www.part68.org/ by conducting a search using “Avaya” as manufacturer.
Page 5: Table Of Contents
Contents Volume 1 About this Book Intended Use How to Use this Document Organization Conventions Used in This Document Trademarks and Service Marks xxii Where to Call for Technical Support xxiv Maintenance Architecture Maintenance Objects Alarm and Error Reporting Basic Server and IPSI Connectivity Power Interruptions Protocols 1-10...
Page 6 Contents Initialization and Recovery Initialization Recovery Reset Level 1 (Warm Restart) Reset Level 2 (Cold-2 Restart) 3-10 Reset Level 4 (MultiVantage Application Reload) 3-11 Alarms, Errors, and Troubleshooting Safety Precautions Suppress Alarm Origination [y] Reseating and Replacing Circuit Packs Replacing a BIU or Rectifier Troubleshooting a Duplicated Server 4-10 Executing a Server Interchange...
Page 7 Contents LED Interpretation Alarm Levels Terminal Alarm Notification Attendant Console LEDs Circuit Pack LEDs Server LEDs 6-16 IPSI LEDs 6-21 Duplication Memory Card LEDs 6-24 Maintenance Commands New Commands Modified Commands Command-Line Syntax Common Input Parameters Common Output Fields Contention Between Simultaneous Commands 7-12 Busyout and Release Commands 7-13...
Page 8 Contents change ipserver-interface 7-67 change ip-network-region 7-69 change station 7-71 change synchronization 7-72 change system-parameters ipserver-interface 7-74 change system-parameters maintenance 7-76 clear errors 7-82 clear firmware-counters 7-83 clear link n 7-84 disable filesystem board ppcss 7-85 disable firmware download 7-86 display alarms 7-87 display atm pnc...
Page 9 Contents list directory 7-168 list disabled-MOs 7-169 list fiber-link 7-170 list history 7-171 list ip-route 7-174 list ipserver-interface 7-176 list isdn-testcall 7-178 list marked-ports 7-179 list measurements clan ethernet 7-180 list measurements clan ppp 7-183 list measurements clan sockets 7-185 list measurements ds1 7-188 list measurements ip codec...
Page 10 Contents reset pnc interchange 7-256 reset ipserver-interface 7-260 reset login-ID n 7-261 reset maintenance 7-262 reset packet-interface 7-263 reset port-network 7-264 reset system 7-266 reset val 7-267 resume hardware-group 7-268 save translation 7-269 set boot-image 7-270 set ethernet-options 7-271 set ipserver-interface 7-273 set options 7-274...
Page 11 Contents status periodic-scheduled 7-367 status processor-channel 1 7-368 status pms-link 7-369 status pnc 7-370 status port-network 7-374 status processor-channel 7-378 status psa 7-379 status signaling-group 7-380 status sp-link 7-382 status station 7-383 status switch-node 7-393 status synchronization 7-395 status sys-link 7-396 status trunk 7-399...
Page 12 Contents test signaling-group 7-453 test synchronization 7-454 test sys-link 7-457 test tdm 7-459 test tone-clock 7-460 test trunk 7-461 test tsc-administered 7-462 traceroute 7-463 Issue 1 May 2002 555-233-143...
Page 13 Contents Volume 2 Maintenance-Object Repair Procedures Escalation Procedures ABRI-PORT (ASAI ISDN-BRI Port) AC-POWER ADM-CONN (Administered Connection) 8-12 ADX8D-BD (AUDIX Circuit Pack) 8-15 ADX8D-PT (AUDIX Digital Port) 8-16 ADX16D-B (16-Port AUDIX Circuit Pack) 8-24 ADX16A-BD (AUDIX Circuit Pack) 8-25 ADX16D-P (16-Port AUDIX Digital Port) 8-26 ADX16A-PT (AUDIX Analog Line/Control Link) 8-34...
Page 14 Contents AUDIX-BD (AUDIX Circuit Pack) 8-307 AUDIX-PT (AUDIX Port) 8-308 AUX-BD (Auxiliary Trunk Circuit Pack) 8-309 AUX-TRK (Auxiliary Trunk) 8-310 AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX Circuit Packs) 8-319 AXA12-RS/ADX8D-RS/AXD12-RS (AUDIX Reserve Slots) 8-320 BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) 8-321 BRI-DAT (ISDN-BRI Data Module) 8-329 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)
Page 15 Contents DS1 CONV-BD 8-683 DT-LN-BD (Data Line Circuit Pack) 8-718 DTMR-PT (Dual-Tone Multifrequency Receiver Port) 8-719 E-DIG-BD (Multi Application Platform Board) 8-723 E-DIG-RES (TN800 reserve slot) 8-725 E-DIG-STA (Emulated Digital Line) 8-726 EMG-XFER (Emergency Transfer) 8-736 PN-SNTY (PN Sanity Audit) 8-741 ERR-LOG (Error Log) 8-743...
Page 16 Contents Volume 3 MAINT (PN’s Maintenance Circuit Pack) 8-1025 MAPD-BD (MAPD Interface Circuit Pack TN802) 8-1039 MEDPRO (Media Processor MAPD Circuit Pack) 8-1069 MEDPROPT (TN802/TN2302 MED PRO DSP PORT) 8-1081 MET-BD (MET Line Circuit Pack) 8-1088 MET-LINE (MET Line) 8-1089 MIS (Management Information System) 8-1109 MMI-BD...
Page 17 Contents S-SYN-PT (Speech Synthesis Port) 8-1364 SN-CONF (Switch Node Configuration) 8-1376 SNC-BD (Switch Node Clock Circuit Pack) 8-1384 SNC-LINK (Switch Node Clock Link) 8-1422 SNC-REF (Switch Node Clock Reference) 8-1426 SNI-BD (SNI Circuit Pack) 8-1429 SNI-PEER (SNI Peer Link) 8-1491 SRP-EPN 8-1495 STRAT-3 (Stratum-3 Clock)
Page 18 Contents VC-SUMPT 8-1860 WAE-PORT (Wideband Access Endpoint Port) 8-1865 XXX-BD (Common Port Circuit Pack) 8-1872 Index IN-1 xviii Issue 1 May 2002 555-233-143...
Page 19: About This Book
DEFINITY G3r processor with fewer physical components and provides most of the same features and functionality with increased capacity. For more information, refer to the “Overview of the Avaya S8700 Media Server for Multi-Connect Configurations. These system’s extensive background testing and technician-demanded tests allow many problems to be addressed before they severely disrupt call processing.
Page 20: Intended Use
About this Book Intended Use As a guide for diagnosing and repairing an S8700 Media Server system for use by field technicians, remote service personnel, and user-assigned maintenance personnel As a training manual for teaching technicians how to maintain the system As a reference source on the system’s maintenance capabilities...
Page 21: Conventions Used In This Document
Conventions Used in This Document Chapter 3, ‘‘Initialization and Recovery’’, describes the various reset and reboot processes and how these are used to perform maintenance and recover systems or subsystems that are out of service. Use of the terminal SPE-down interface on non-functional or standby Switch Processor Elements is included here.
Page 22: Trademarks And Service Marks
This sign is used where there is possible harm to hardware or equipment. DANGER: This sign is used to indicate possible harm or injury to people. Trademarks and Service Marks The following are trademarks or registered trademarks of Avaya: AUDIX ® ™ Cajun Callvisor ®...
Page 23 Trademarks and Service Marks The following are trademarks or registered trademarks of AT&T: ACCUNET ® DATAPHONE ® MEGACOM ® MULTIQUEST ® TELESEER ® The following are trademarks or registered trademarks of AT&T: ACCUNET ® DATAPHONE ® MEGACOM ® MULTIQUEST ® TELESEER ®...
Page 24: Where To Call For Technical Support
Organization Telephone Number For help with feature administration and system applications: +1-800-225-7585 DEFINITY Helpline of Avaya For help with maintenance and repair: Avaya National Customer Care Center Support Line +1-800-242-2121 Avaya Toll Fraud Intervention +1-800-643-2353 Avaya Corporate Security +1-800-822-9009 +1-925-224-3401...
Page 25: Maintenance Architecture
This subsystem continuously monitors the system’s health and records detected errors. The maintenance subsystem also provides a user interface for on-demand testing. This chapter provides a brief description of the Avaya S8700 Media Server for Multi-Connect Configurations (S8700 Multi-Connect) maintenance strategy and presents background information about the system’s overall functions.
Page 26 Maintenance Architecture This chapter includes the following topics: ‘‘Maintenance Objects’’ ‘‘Alarm and Error Reporting’’ ‘‘Basic Server and IPSI Connectivity’’ ‘‘Power Interruptions’’ ‘‘Signaling’’ ‘‘Service Codes’’ ‘‘Facility Interface Codes’’ ‘‘Multimedia Interface (MMI)’’ Issue 1 May 2002 555-233-143...
Page 27: Maintenance Objects
Maintenance Objects Maintenance Objects The system is partitioned into separate entities called maintenance objects (MOs). Each MO is monitored by the system and has its own maintenance strategy. Most MOs are individual circuit packs such as the: Direct Inward Dial Trunk circuit pack (DID-BD) DS1 Tie Trunk circuit pack (TIE-DS1) Expansion Interface (EI) circuit pack (EXP-INTF) Some MOs represent hardware components that correside on a circuit pack.
Page 28: Alarm And Error Reporting
WARNING alarms identify failures that cause no significant degradation of service or failures of equipment external to the system. These are not reported to the Avaya alarm receiving system or the attendant console. ON-BOARD problems originate in circuitry on the alarmed circuit pack.
Page 29 Alarm Reporting Every major or minor alarm is reported to the Avaya alarm receiver system to generate a trouble report in the Avaya Services Ticketing System. Some warning alarms can be upgraded in conjunction with the Enhanced Remote Support (ERS) offer.
Page 30 Maintenance Architecture Some All minor downgraded major alarms warning alarms alarms Every timer and count is reset Call to alarm receiving system alarm successfully raised? completed? Call to alarm receiving system successful Fifth retry attempt? hour wait test been Call retried repeated in 7 minutes six times?
Page 31: Basic Server And Ipsi Connectivity
Basic Server and IPSI Connectivity Basic Server and IPSI Connectivity The S8700 Media Server uses IPSIs to control port networks and provide tone, clock and call classification services. The IPSI board connects to the control network via Ethernet. IPSIs are described in more detail in Getting Started with the Avaya S8700 Media Server.
Page 32: Power Interruptions
Maintenance Architecture Power Interruptions System cabinets and their associated power supplies can be powered by 110/208 Volts AC either directly or from an uninterruptible power supply (UPS) system. Alternatively, the cabinets and their power supplies may be powered by a -48 VDC battery power plant, which requires DC-to-DC conversion power units in the system.
Page 33 Maintenance circuit packs. If the switch is under warranty or a maintenance agreement, EXT-DEV alarms are generated by the equipment connected to these leads and reported to the Avaya alarm receiving system. These may be used to report failures of UPSs or battery reserves powering the switch. They are also commonly used to monitor adjuncts such as AUDIX.
Page 34: Protocols
Maintenance Architecture Protocols This section describes the protocols handled by the system and the points where these protocols change. Figure 1-2 is a pictorial guide through intra-port and inter-port data transmission state changes. Figure 1-2 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 35 Protocols 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 36 Maintenance Architecture 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. See Figure 1-2 on page 1-11. 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 37 Protocols 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 Digital Signal Level 1 (DS1) —...
Page 38 Maintenance Architecture Protocol States Table 1-3 summarizes the protocols used at various points in the data transmission stream. See Figure 1-2 on page 1-11. Table 1-3. Protocol States for Data Communication Incoming Transmission DTE to Protocols DTE to DCE to System Type Layer Port...
Page 39 Protocols Table 1-5. 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-2 on page 1-11 implies the following connectivity rules: Only the DS1 port and the analog trunk port are trunking facilities (every other port is a line port).
Page 40 Maintenance Architecture Data cannot be carried over analog facilities unless inside the system it is represented as a 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.
Page 41: Signaling
Signaling Signaling This section describes disconnect supervision and transmission characteristics. Disconnect Supervision Disconnect supervision means the CO has the ability to release a trunk when the party at the CO disconnects and the system is able to recognize the release signal.
Page 42 Maintenance Architecture Conference, Transfer, and Call-Forwarding Denial If a station or attendant attempts to connect parties without disconnect supervision together, the following is possible: Digital Station or Local Attendant Transfer If a digital station attempts to transfer the two parties together, the call-appearance lamp flutters, indicating a denial.
Page 43 Signaling Frequency Response Table 1-6 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-6. Analog-to-Analog Frequency Response Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB) – 300 to 3000 -0.5 3200 -0.5...
Page 44 Maintenance Architecture Insertion Loss for Port-to-Port, Analog or Digital Table 1-8 lists the insertion loss in the system for different connection types for the United States. Table 1-9 shows the overload and cross-talk characteristics. Table 1-8. Insertion Loss for the United States Nominal Loss Typical Connections (dB) at 1 kHz...
Page 45 Signaling Quantization Distortion Loss Table 1-11 lists the quantization distortion loss in the system for analog port to analog port. Table 1-11. Quantization Distortion Loss Analog Port-to-Analog Port Signal Level Distortion Loss 0 to -30 dBm0 >33 dB -40 dBm0 >27 dB -45 dBm0 >22 dB...
Page 46 Maintenance Architecture ERL and SFRL Talking State Echo-Return Loss (ERL) and Single-Frequency Return Loss (SFRL) performance are usually dominated by termination and/or loop input impedances. The system provides an acceptable level of echo performance if the ERL and SFRL are met, as follows:.
Page 47: Service Codes
Service Codes Service Codes Service codes (for the United States only) are issued by the Federal Communications Commission (FCC) to equipment manufacturers and registrants. These codes denote the: Type of registered terminal equipment Protective characteristics of the premises wiring of the terminal equipment ports Private line service codes are as follows: 7.0Y —...
Page 48: Facility Interface Codes
Maintenance Architecture Facility Interface Codes A Facility Interface Code (FIC) is a 5-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-13 through Table 1-15 on page 1-24...
Page 49: Multimedia Interface (Mmi)
Multimedia Interface (MMI) Multimedia Interface (MMI) The Multimedia Interface handles the following protocols: International Telecommunications Union (ITU) H.221 — Includes H.230, H.242, H.231, and H.243 protocol American National Standards Institute (ANSI) H.221 — Includes H.230, H.242, H.231, and H.243 protocol BONDING (Bandwidth On-Demand Interoperability Group) Mode 1 ESM HLP HDLC Rate Adaptation The Vistium Personal Conferencing System is supported either through the 8510T...
Page 50 Maintenance Architecture 1-26 Issue 1 May 2002 555-233-143...
Page 51: Hardware Configurations
The Avaya S8700 Media Server for Multi-Connect Configurations (S8700 Multi-Connect) is derived from the current DEFINITY G3r processor. It uses a Linux platform on a Intel server. The S8700 Multi-Connect separates call control from the bearer network and uses a dedicated LAN for transport.
Page 52: Multicarrier Cabinets
Hardware Configurations Multicarrier Cabinets For information on multicarrier cabinets and the carriers in them, refer to Avaya MultiVantage Solutions Hardware Guide. Issue 1 May 2002 555-233-143...
Page 53: Pnc Cabling - Fiber Hardware
PNC Cabling — Fiber Hardware PNC Cabling Fiber Hardware — The term “fiber” is used to refer to all the hardware needed for the three basic types of connections used to form multi-PN systems. Fiber administration specifies the endpoints to be connected, optional DS1 CONV locations, and parameters for DS1 facility line encoding and equalization.
Page 54 Hardware Configurations 9823-Type 9823-Type Lightwave Lightwave FL2P-P-xx Transceiver Transceiver Fiber-Optic Cables To I/O To I/O Connector Connector Plate Plate FL2P-P-xx Fiber-Optic Cables 9823-Type 9823-Type Lightwave Lightwave Transceiver FL2P-P-xx Transceiver Fiber-Optic Cables 100A 100A To I/O To I/O Connector Connector Plate Plate Optical Cross-Connect Facility Figure 2-1.
Page 55 PNC Cabling — Fiber Hardware EI-to-SNI or EI-to-EI Intracabinet Metallic Cabling Metallic cable may be substituted for optical cable for “fiber” connections between EIs or between an EI and an SNI in the same MCC cabinet. The same I/O plate connectors are used.
Page 56 Hardware Configurations The DS1 CONV to EI/SNI cable is a shielded metallic Y-cable held in place at the EI/SNI port connector by a 4B retainer and at the DS1 CONV port connector by a 4C retainer. The cable end with one 25-pair amphenol connector attaches to the I/O Plate connector for the EI or SNI.
Page 57 PNC Cabling — Fiber Hardware DS1C Switch 100 miles Switch TN570 846448637 circuit pack TN570 846448645 circuit TN573 pack circuit pack 650 feet 650 feet Cross TN574 maximum TN574 connect circuit circuit field pack pack For direct 846448637 846448637 cross connect, H600-348, G-( ) H600-348, G-( ) see text.
Page 58: Circuit Packs
Hardware Configurations Circuit Packs Refer to Avaya MultiVantage Solutions Guide for information on circuit packs supported by S8700 Media Server products. Issue 1 May 2002 555-233-143...
Page 59: Duplication For Reliability
Duplication for Reliability Duplication for Reliability The S8700 Multi-Connect architecture has duplicated components to increase the reliability of the system. If one duplicated component fails, the other can take over without impacting service or minimizing the impact. Which components are duplicated in your system depends on the level of reliability chosen for your configuration: duplex, high, or critical reliability.
Page 60 Hardware Configurations Ethernet 4 Ethernet 4 Ethernet 2 Ethernet 1 Ethernet 1 Ethernet 0 Ethernet 0 Ethernet 3 CONSOLE CONSOLE IPSI IPSI IPSI 100bT 100bT 100bT LINK LINK LINK LINK LINK LINK TRMT TRMT TRMT TRMT TRMT TRMT PN 1 PN 2 Figure 2-3.
Page 61 Used for administration and can be used for alarming via simple network message protocol (SNMP) traps to the Initialization and Administration System (INADS). S8700 Media Server — two are always present, one in active mode and the other on standby. Duplication interface: default Ethernet 2. The dedicated Ethernet connection between the S8700 Media Servers.
Page 62 Hardware Configurations Critical-Reliability Configuration Critical-reliability systems include all of the features and components of the high-reliability configuration described above, but it also has a duplicated bearer network. This configuration requires that not only the IPSI-connected port networks have duplicated IPSIs, but also the non-IPSI-connected port networks must have duplicated Tone-Clock boards.
Page 63: Initialization And Recovery
Initialization and Recovery This chapter describes initialization and shutdown of the servers and the causes, effects, and duration of each reset level used to restart the system. It includes the following topics: Initialization After a server is powered on, the following software/firmware modules are executed in the following order: 1.
Page 64 7. Arbiter — The Arbiter decides whether the server goes active or standby. Active Server’s Initialization These steps are executed on the active server. 1. Avaya MultiVantage — The Watchdog process creates the MultiVantage application, by starting up the Process Manager (prc_mgr). In turn, this process starts up the MultiVantage processes by: Reading the Process Table file ( /opt/defty/bin/Proc_tab.z )
Page 65 Standby Server’s Initialization These steps are executed on the standby server: 1. Avaya MultiVantage — On the standby server, many processes are frozen, so that the Standby DupMgr can shadow into them without interfering with those writes. However, some shadowed and unshadowed processes need to run on the standby.
Page 66 Initialization and Recovery When the entire system is shut down via the stop command, the Watchdog executes the Linux “shutdown -r 0” command, which is the normal way to reboot Linux. When Watchd terminates an individual process, it sends a SIGTERM signal. Shutting down a single application involves sending a SIGTERM signal to the application’s “leader”...
Page 67: Recovery
Recovery Recovery Watchdog and Applications The Watchdog monitors the sanity of the various applications it initially created. It does this using two mechanisms. The Watchdog receives: A SIGCHLD signal if any process it created dies Periodic heartbeat messages from those processes If heartbeat messages go away for a certain time (as specified in the Watchdog’s configuration file), the application is killed.
Page 68 (as a final recovery action) HiMonitor reboots Linux. CAUTION: Escalate to an Avaya engineer for explicit guidance with this recovery, since it is potentially disruptive. A process can legitimately occupy abnormally high amounts of processor time due to server load, and killing it could make the server totally unavailable.
Page 69 Watchdog’s sole purpose is to reset the hardware Watchdog. Restarts The term “restart” is a traditional Avaya term for a system restart of less severity than a full recreation. Restarts were accomplished by retaining the memory state of certain processes.
Page 70 If a reset fails to recover normal system operation, the firmware that controls reset will escalate to the next higher level, up to reboot if necessary. Hot restarts are not supported for S8700 Multi-Connect servers. An on-demand, planned, or scheduled interchange results in a warm restart of the standby server if it is in a refreshed state, or a reboot if it is not refreshed.
Page 71: Reset Level 1 (Warm Restart)
Reset Level 1 (Warm Restart) Reset Level 1 (Warm Restart) Duration Up to 10 seconds, typically 4 seconds Causes reset system 1 command from MultiVantage (SAT/ASA) command line Spontaneous server interchange (those caused by hardware faults) Software faults that are not service affecting Abort of planned server interchange Effects Stable calls are preserved;...
Page 72: Reset Level 2 (Cold-2 Restart)
Initialization and Recovery Reset Level 2 (Cold-2 Restart) Duration Up to 3.75 minutes Causes reset system 2 command from MultiVantage (SAT/ASA) command line Escalation from SAT’s reset level 1 An attempted SAT’s reset level 1 during a PNC interchange Spontaneous interchange into an unrefreshed standby server Effects Every system and application link is dropped.
Page 73: Reset Level 4 (Multivantage Application Reload)
Reset Level 4 (MultiVantage Application Reload) Reset Level 4 (MultiVantage Application Reload) CAUTION: Executing reset system 4 leads to an interchange of the system’s servers. [In response to a level-4 reset, maintenance software downgrades the active server’s state of health (SOH)., which causes the subsequent interchange.] Once the interchange occurs, the system also relies on the previous standby’s version of translations, which (in this scenario) may not be current.
Page 74 Initialization and Recovery 3-12 Issue 1 May 2002 555-233-143...
Page 75: Alarms, Errors, And Troubleshooting
Alarms, Errors, and Troubleshooting This chapter describes how to resolve problems indicated by alarms and error messages in the system. It includes the following topics: ‘‘Safety Precautions’’ on page 4-2 ‘‘EMBEDDED AUDIX System’s Power Procedures’’ on page 4-3 ‘‘Electrostatic Discharge’’ on page 4-4 ‘‘Suppress Alarm Origination [y]’’...
Page 76: Safety Precautions
While touching any component inside a cabinet, ground yourself using a wrist strap attached to the cabinet’s frame, and avoid sources of static electricity. When logging on with Avaya Site Administration (ASA), be aware that alarm notification is normally disabled. Log off ASA as you leave the system.
Page 77 Safety Precautions EMBEDDED AUDIX System’s Power Procedures Manually Power Down AUDIX System A amber caution sticker on the system’s power unit notifies technicians to shut down the EMBEDDED AUDIX system prior to powering down the system. 1. Using a pointed object, such as a paper clip or pen (do not use a pencil), press the Boot/Shutdown button.
Page 78 Alarms, Errors, and Troubleshooting Electrostatic Discharge To avoid system damage or service disruption from ESD while a circuit pack is inserted or removed, attach a grounding wrist strap to the cabinet, and wear it. Also, use a wrist strap while touching any component inside a system’s cabinet, (including EMERGENCY TRANSFER switches).
Page 79 Safety Precautions Figure 4-1 shows the location of the grounding jack. JACK Figure 4-1. Wrist-Strap Jack for ESD Grounding on Multicarrier Cabinet 555-233-143 Issue 1 May 2002...
Page 80: Suppress Alarm Origination [Y]
Also, while logged in as “craft,” an idle terminal is automatically logged off after 30 minutes. At that time, any unresolved alarms are reported to Avaya’s alarm receiving system. If you are logged in as “craft” at two terminals, the logoff occurs when the second terminal is unused for 30 minutes.
Page 81: Reseating And Replacing Circuit Packs
Reseating and Replacing Circuit Packs Reseating and Replacing Circuit Packs Most repair procedures involve replacing faulted circuit packs. In some cases, problems are resolved by reseating the existing circuit pack. Reseat a circuit pack only when explicitly instructed to do so by the documented procedures. Reseating is discouraged since it can put a faulty component back into service without addressing the cause, resulting in additional and unnecessary dispatches.
Page 82 Alarms, Errors, and Troubleshooting Special Procedures The following circuit packs require special procedures. (TBP -- cross reference) TN2312 IP Server Interface (IPSI) providing: — Packet Interface circuit (equivalent to TN1655) — Tone-Clock circuit (equivalent to TN2182) TN768, TN780, or TN2182B Tone-Clock for an EPN without an IPSI TN570 Expansion Interface TN573 Switch Node Interface TN572 Switch Node Clock...
Page 83: Replacing A Biu Or Rectifier
Replacing a BIU or Rectifier Replacing a BIU or Rectifier To remove a battery interface unit (BIU) or rectifier, first attach a grounding strap from the cabinet to your bare wrist, and then perform the following steps: 1. Unlock the latch pin. 2.
Page 84: Troubleshooting A Duplicated Server
Alarms, Errors, and Troubleshooting Troubleshooting a Duplicated Server The sections, ‘‘Initialization and Recovery’’ on page 3-1, ‘‘IP-SVR (IP Server Interface)’’ on page 8-959, and ‘‘IPSV-CTL (Ipserver Interface Control)’’ on page 8-950, contain procedures for troubleshooting specific problems with servers and IPSIs.
Page 85 Troubleshooting a Duplicated Server Determining the Time of a Spontaneous Interchange There are two ways to tell at what time a spontaneous interchange has taken place: Display initcauses The display initcauses command displays a record of every system reset. In the following example, a spontaneous interchange into Server B took place at 2:53 p.m.
Page 86 Alarms, Errors, and Troubleshooting All relevant alarms must be timestamped at or near the time of interchange. Enter display alarms for categories SPE and environ. Are there any major Consult CARR-POW in alarms against CARR-POW? Chapter 9. Is there a Major alarm against Replace the standby the standby SW-CTL? MSSNET circuit pack.
Page 87 Troubleshooting a Duplicated Server Auxiliary Data for SYSTEM Errors 6002, 6003, 6102, and 6103 The following table shows which components are indicted by the auxiliary error codes found by using the preceding flowchart (Figure 4-2 on page 4-12). Once you have identified the faulted component, consult the section for that maintenance object (MO).
Page 88 Alarms, Errors, and Troubleshooting Have you completed the steps in the preceding ﬂowchart? Enter \f(HBstatus spe\fH. Is the standby SPE Troubleshoot using MO documentation fully refreshed with handshake up? for STBY-SPE. Enter \f(HBtest spe-standby long\fH and wait for all tests to execute. Consult MO documentation for the component whose test failed.
Page 89: Executing A Server Interchange
Executing a Server Interchange Executing a Server Interchange Planned server interchanges are initiated on-demand by the reset system interchange command, or automatically by scheduled daily maintenance. The latter is administered with the System Parameters Maintenance screen. A planned interchange normally has no perceivable effect on service. Every active call, transient call, system link and stimulus, and data transmission is preserved.
Page 90: La85 Port Tester
LA85 Port Tester The LA85 port tester (Comcode 105138424) is recommended for troubleshooting every S8700 Multi-Connect station trouble involving analog, DCP, MFET, MFAT, or BRI configuration. The port tester detects the presence of voltage from equipment ports and indicates the wiring status at the:...
Page 91: La85 Port Tester
LA85 Port Tester Table 4-1. Port fault isolation using the LA85 Port Tester — Continued You may need this preliminary To begin the isolation information or procedure at the equipment And if Then Intermediate closet Isolate part of the wiring wall field span (either to the switch or to the terminal)
Page 92 Alarms, Errors, and Troubleshooting Table 4-2. LED indications for the LA85 Port Tester W-BL Port Bl-W Bl-W W-BL Analog DCP (2-wire) MFET MFAT Continued on next page The red LED lights on a reversal. If the analog set contains a polarity guard, the set is still operable.
Page 93: Fault Isolation For Fiber Links
Fault Isolation for Fiber Links Fault Isolation for Fiber Links Use the following procedure to isolate faults on a fiber link. When troubleshooting a critical-reliability system [duplicated port-network connectivity (PNC)], first busyout pnc-standby before busying out a standby: Fiber link (FIBER-LK) Expansion Interface (EXP-INTF) Switch Node Interface (SNI) DS1 Converter (DS1C).
Page 94 Alarms, Errors, and Troubleshooting Complete the following steps: 1. Enter display alarms with category pnc. Are there any on-board alarms? If so, replace the circuit pack(s). 2. Enter display errors for category pnc. Check for any of the following errors: Error Type FIBER-LK...
Page 95 Fault Isolation for Fiber Links If there are many SNI-PEER errors with the same error type, replace the indicted SNI circuit pack using the following table. Error Type SNI’s Slot 1025 1281 1537 1793 2049 2305 2561 2817 3073 3329 3585 3841 After replacing an SNI circuit pack, clear alarms by executing test...
Page 96 Alarms, Errors, and Troubleshooting Busyout and test board UUCSS long and record every test failure. When looking at test results, consult the explanations and illustrations of the tests, which appear at the end of this procedure. Is Board Not Assigned displayed for an EXP-INTF in an EPN? If yes, test maintenance long to release an EXP-INTF that may be held reset by an EPN Maintenance circuit pack.
Page 97 Fault Isolation for Fiber Links In a duplex-, or high-reliability system (unduplicated PNC), did the test return “Board not inserted” for either the near-end circuit pack (nearest the server) or far-end circuit pack? If so, replace the cabling between the DS1C circuit pack and the SNI or EXP-INTF circuit pack. Wait 1 minute and retest.
Page 98 Alarms, Errors, and Troubleshooting A short optical fiber jumper with connectors is required for this procedure. If the link uses metallic cable, the metallic connector must be removed from behind the carrier and a lightwave transceiver connected in its place. Complete the following steps: 1.
Page 99 Fault Isolation for Fiber Links Test #242 can be run as part of the test board UUCSS long command for an EI circuit pack. Besides testing on-board components, this test is helpful for isolating problems between a circuit pack and the lightwave transceiver. The loopback shown in this diagram shows only part of what Test #242 does.
Page 100 Alarms, Errors, and Troubleshooting If DS1Cs exist on the fiber link (check with list fiber-link), then additional DS1CONV loopback tests can be run to further isolate the problem. The loopback tests are shown in Figure 4-5. For more information about DS1 CONV-BD Loopback tests (#788 and #789), see: ‘‘Far-End DS1 Converter Circuit Pack Loopback Test (#788)’’...
Page 101 Fault Isolation for Fiber Links Table 4-3 shows the pin assignments for the cable used to connect the TN574 DS1 CONV circuit pack to DS1 facilities. Table 4-3. DS1 Interface Cable Connectors 50-Pin 15-Pin Connector Connector Lead Desig. Color Color Plug 04 Facility D Line In W-BL...
Page 102: Atm Tips
Alarms, Errors, and Troubleshooting ATM Tips This section provides tips for S8700 Multi-Connect ATM PNC when interfacing with the ATM switch. Throughout this section, refer to Figure 4-6. AX500 Switch PPN Switch EPN ATM call control Q.93B Q.93B CaPro Switch Q.SAAL...
Page 103 ATM Tips Table 4-4. — Continued TN230X LED reference LED color Green Amber Interpretation Fast blink – Running DSP diagnostics or downloading code to DSPs (typical during boot process). – Slow blink – Board insertion has not yet completed. – Steady on –...
Page 104 Green Steady on ATM cells are being received frequently enough that the LED is lit constantly. This is a S8700 Multi-Connect typical pattern for CBR (constant bit rate) talk paths are present. Green Loss of carrier on the fiber. The A500 detects only if the A500-receive (right-hand) fiber is not working.
Page 105 Cajun A500 Diagnostics The first step in any diagnostic procedure involving the A500 is to identify the OC-3 ports on the A500 that have S8700 Multi-Connect port networks attached. Be aware that customers may use other ports on the A500 for applications unrelated to S8700 Multi-Connect (for example, LAN traffic or multimedia applications).
Page 106 Alarms, Errors, and Troubleshooting A500 System Console (c) 1997 Avaya Inc. login: root password: XXXXXX ********** New System Alarms ********** [1] Failed to fetch configuration files ******* Hit any key to continue ******* A500: Figure 4-7. A500 login screen 8. Enter status at the A500: prompt.
Page 107 S8700 Multi-Connect Administration Is ATM PNC administered correctly? 1. Enter list atm pnc on the S8700 Multi-Connect’s SAT. The cabinet, carrier, and slot positions of each administered TN230X board display as shown in Figure 4-9. Ensure that each board’s physical location matches the display.
Page 108 Alarms, Errors, and Troubleshooting 2. Enter status pnc at the S8700 Multi-Connect SAT. This display tells you which TN230X board is active in a duplicated system and how many alarms (if any) of each severity level have been logged for the board.
Page 109 ATM Tips display circuit-packs 1 CIRCUIT PACKS Cabinet: Carrier: Cabinet Layout: five-carrier Carrier Type: processor *** PROCESSOR BOARDS NOT ADMINISTERABLE IN THIS SCREEN *** CIRCUIT PACKS Cabinet: Carrier: Cabinet Layout: five-carrier Carrier Type: port Slot Code Name Slot Code Name TN464 DS1 INTERFACE TN464...
Page 110 ’#’ indicates circuit pack conflict. Figure 4-12. Screen output for display circuit-packs 2 4. Enter display atm pnc port network on the S8700 Multi-Connect SAT. This display tells you the ATM addresses that have been administered for each TN230X. Verify that each ATM address (the concatenation of the five displayed hexadecimal fields) is correct and match those administered in the A500.
Page 111 ATM Tips display atm pnc 1 ATM PNC Connection Number: Location: 01B02 Name: Address Format: ICD ATM AFI: ICD: 0005 HO-DSP: 80FFE1000000F2071B02 ESI: 000000000000 SEL: Figure 4-13. Screen output for display atm pnc 1 display atm pnc 2 ATM PNC Connection Number: Location: 02A01...
Page 112 Alarms, Errors, and Troubleshooting display atm pnc 1 ATM PNC Connection Number: A - PNC Location: 01B02 Name: Address Format: E.164 ATM Private AFI: E.164: 0001013035381053 HO-DSP: 00000000 ESI: 000000000011 SEL: Figure 4-15. Screen output for display atm pnc 1 with End System Identifiers display atm pnc 2 ATM PNC Connection Number:...
Page 113 UNI3.1 Figure 4-17. Screen output for the show signaling summary command a. If an A500 port to which a S8700 Multi-Connect 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).
Page 114 Figure 4-18. Screen output from the show signaling routes command Check that the Address field (administered using the admin signaling route add command) matches those administered in S8700 Multi-Connect. 3. If the A500 was administered using End System Identifiers, enter show signaling esi on the A500 console.
Page 115 TenBaseT Figure 4-20. A500 screen output for show sys interfaces command For each administered port used by a S8700 Multi-Connect port network, the Admin Status should be up (using the admin up command). The state of Oper Status is not pertinent to administration of the A500 and is discussed in a later section.
Page 116 Do the TN230X LEDs indicate it is downloading its DSPs? Do the TN230X LEDs indicate that board insertion has not yet occurred? Do the TN230X LEDs indicate a maintenance alarm? 3. Enter list configuration carrier cabinet carrier on the S8700 Multi-Connect SAT. See the following Figure 4-21 (1b) and...
Page 117 ATM Tips list configuration carrier 1b SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01B02 ATM PNC EI TN2305 000001 01B04 DIGITAL LINE TN754C 000002 01B05 ANALOG LINE TN746B 000010 06 u 01B06 DID TRUNK TN753 000021 01B07...
Page 118 Refer to Replacing Circuit Packs’’ on page 4-7 4. If the TN230X is inserted and shows a vintage number, enter test board cabinetcarrierslot for this board on the S8700 Multi-Connect SAT, as shown in Figure 4-23...
Page 119 ‘‘ATM-BCH (ATM B-Channel Trunk)’’ on page 8-168. Possible Causes 1. The TN230X board is in a slot different from the S8700 Multi-Connect administration. 2. The TN230X did not complete board insertion. Physical Layer Is there an optical signal between the TN230X and the A500? 1.
Page 120 Alarms, Errors, and Troubleshooting 4. Enter show system interfaces on the A500 console. Figure 4-26 shows an example of the screen output. 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)
Page 121 ATM Tips 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 signal (not inserted, not powered, or not administered).
Page 122 Alarms, Errors, and Troubleshooting 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 123 ATM Tips Q.SAAL (Data Link) Layer Are ATM signaling messages reaching A500 Call Control? Enter show signaling stats port qsaal on the A500 console. Figure 4-28 shows the screen output. A500: show signaling stats a1.2 qsaal ------------------------Q.SAAL Statistics------------------------ Port A1.2: ---------- Type: UNI3.1...
Page 124 Alarms, Errors, and Troubleshooting 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. Figure 4-29 shows the screen output. A500:show signaling stats a1.2 q93b -------------------------Q.93B Statistics------------------------ Port A1.2: ----------...
Page 125 A500:show signaling cause 31 Cause 31: Normal, unspecified Figure 4-30. A500:show signaling cause 31 4. At the S8700 Multi-Connect SAT type display errors, and press Enter Set the Error List to errors and Category to PNC on the input screen (Figure...
Page 126 Cabinet: Port Network: Board Number: Port: Category: Extension: Trunk ( group/member ): Figure 4-31. S8700 Multi-Connect display errors input screen Figure 4-32 shows the screen output for the display errors command. display errors Page SPE A HARDWARE ERROR REPORT Port...
Page 127 (for example, a routing problem on another port that displays cause code 3). Resources unavailable, S8700 Multi-Connect call volume is too high for the unspecified available resources in the ATM network. Service or option unavailable,...
Page 128 These are established by each TN230X when it comes up, independent of S8700 Multi-Connect call processing. Other UBR virtual circuits may exist between A500 ports that are not associated with S8700 Multi-Connect port networks and may be signaling channels for other applications (for example, data network traffic). CaPro Layer...
Page 129 ATM Tips Complete the following steps: 1. Enter list sys-link on the S8700 Multi-Connect SAT. Figure 4-34 shows the screen output. list sys-link SYSTEM LINKS INFORMATION Location Link Type/ State Current Faulted Last Fault Channel Path Path Recorded 02A0101 present...
Page 130 Multi-Connect call processing. They represent the ATM Control Link (ACL) and Expansion Archangel Link (EAL). VBRnrt virtual circuits are also be used for ISDN channels between S8700 Multi-Connect port networks. Other VBRnrt virtual circuits may exist between A500 ports that are not associated with S8700 Multi-Connect port networks.
Page 131 UBR. — There may be other CBR virtual circuits between A500 ports that are not associated with S8700 Multi-Connect EPNs. A common CBR application is circuit emulation, where T1, T3, etc. circuits are carried over ATM.
Page 132: Unusual Atm Trouble Conditions
Alarms, Errors, and Troubleshooting Unusual ATM Trouble Conditions There are a few failure modes in the S8700 Multi-Connect/A500 combination that are particularly difficult to diagnose. One example might be that you can’t make a completely successful call, even though most indications from S8700 Multi-Connect and the A500 look pretty good.
Page 133 Unusual ATM Trouble Conditions 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 for PPN’s end stations and for correctly connected EPNs, but not for an affected EPN’s end stations.
Page 134 To recover, the PPN re-establishes links to what it thinks is the active TN230X, and the cycle repeats indefinitely. Diagnostics The status pnc command on the S8700 Multi-Connect SAT shows both the A and B side’s State of Health field as partially functional. Action Correct the ATM addresses (or swap fibers) on the A500 between the A and B side of the EPN.
Page 135: Multimedia Call Handling (Mmch)
An Expansion Services Module (ESM) provides T.120 data sharing capability on a MMCH multipoint H.320 video conference. Each conference participant must have endpoints administered and a personal computer with the H.320 video application installed. The S8700 Multi-Connect system must have the expansion service module installed. cydf012 KLC 092801 Figure Notes 1.
Page 136 64-kbps Calls Terminate, but Far End Receives 56-kbps Indication Description Some 2 x 64-kbps conferences on the S8700 Multi-Connect MMCH are not established because of framing, audio, or video problems. For calls that are routed in the network through an Avaya/LEC interface, the originating equipment may launch a 64-kbps call attempt, and the far end receives either a 56- or 64-kbps indication.
Page 137 S8700 Multi-Connect MMCH switches to the endpoint, but nobody sees them. The receivers see either “black” video or a frozen image of the previous speaker, depending on the codec of the manufacturer. The type occurs when the S8700 Multi-Connect MMCH does not switch to an endpoint.
Page 138 If there are different clock sources between endpoints and the S8700 Multi-Connect MMCH, some problems are sure to occur. The severity of these problems can range from a handshake failure every few seconds to one per day.
Page 139 No Switching, Full Motion Video If a room is excessively noisy: The S8700 Multi-Connect MMCH may receive sufficient audio signal to conclude that there is a speaker present. Use the Status Conference x form to determine whether the MMCH thinks an endpoint is talking. The MMCH sets the Ts field to t for each endpoint if there is voice energy detected.
Page 140 Alarms, Errors, and Troubleshooting The See-Me feature (MCV) can also cause VAS to “lock-up.” An endpoint can activate MCV to force their site to become the broadcaster. If they do not disable the feature when finished, the system remains in this mode indefinitely. Beginning with Release 3.0, the status conference X command shows that MCV is in effect by displaying av in the Video Status (Vs) column.
Page 141 Rate Adaptation Because of a lack of a clear explanation in standards, sometimes endpoints do not work well with each other and the S8700 Multi-Connect MMCH. The MMCH will only allow a conference to downgrade from 64- to 56-kbps operation on conferences that have the Rate Adaptation flag set to y .
Page 142 Endpoint or I-MUX in Loopback Mode Some endpoints have a loopback enable feature. This makes S8700 Multi-Connect MMCH data loopback at the MMCH when a connection is in progress. The loopback can be enabled prior to or during a connection.
Page 143: Troubleshooting Isdn-Pri
Troubleshooting ISDN-PRI Troubleshooting ISDN-PRI The following flow chart defines a layered approach when troubleshooting ISDN-PRI problems. Since a problem at a lower layer affects upper layers, layers are investigated from low to high. In the flowchart, the DS1 facility is layer 1, the ISDN-PRI D channel is layer 2, and the ISDN trunks are layer 3.
Page 144 Alarms, Errors, and Troubleshooting COMPARE INDICATED FROM FACILITY TO RECORD PAGE OF PREVIOUS PROBLEMS PERFORM AN IN-DEPTH ANALYSIS OF T1 FACILITY INCLUDING: TRANSMISSION FACILITY, EXTERNAL EQUIPMENT ARE BIT THERE (DACS, CSUs, ETC.) TRANSIENT ERRORS OCCURRING AND ANY OTHER PROBLEMS MAKING MORE FREQUENTLY NOISE-PRODUCING ISDN-PRI...
Page 145: Troubleshooting Isdn-Pri Endpoints (Wideband)
Check the health of the application equipment transient? Fails (for example, the video codec) and that of the → S8700 Multi-Connect network. If constant ↓ Transient Failures failures persist, follow normal escalation procedures. Use list measurements ds1 to check for...
Page 146 Alarms, Errors, and Troubleshooting Check for alarms and errors against Follow procedures described in SYNC in → SYNC. Has a synchronization source Chapter 9. been unstable, or has the system switched synch sources? ↓ NO Follow normal escalation procedures. 4-72 Issue 1 May 2002 555-233-143...
Page 147: Troubleshooting Isdn-Bri / Asai
Troubleshooting ISDN-BRI / ASAI Troubleshooting ISDN-BRI / ASAI Troubleshooting ISDN-BRI/ASAI problems can be a complex and involved procedure. The reason for this is that ISDN-BRI devices communicate with the server over the packet bus, as opposed to the TDM bus. Therefore, it is possible for another component’s fault (related to the packet bus) to cause problems with ISDN-BRI devices.
Page 148 Alarms, Errors, and Troubleshooting NOTE: If the flowchart query “Is the problem affecting MOs on multiple BRI-BD circuit packs?” is reached and the EPN in question has only one ISDN-BRI circuit pack, then assume that the answer is “Yes,” and follow the repair procedure for PKT-BUS.
Page 149 Troubleshooting ISDN-BRI / ASAI START ARE THERE ALARMS OR ERRORS AGAINST PKT-BUS IS THIS A ARE THERE FOLLOW THE CRITICAL RELIABILITY ALARMS OR REPAIR SYSTEM? ERRORS AGAINST PROCEDURE (DUPLICATED PNC) M/T-PKT FOR M/T-PKT IS THE ARE THERE FOLLOW THE PROBLEM ALARMS OR ERRORS REPAIR ISOLATED TO...
Page 150 Alarms, Errors, and Troubleshooting FROM FROM PAGE PAGE IS THE FOLLOW THE PROBLEM AFFECTING REPAIR MOs ON MULTIPLE PROCEDURE BRI-BD CIRCUIT FOR PKT-BUS PACKS * IS THE FOLLOW THE PROBLEM AFFECTING REPAIR MULTIPLE MOs ON PROCEDURE THE SAME BRI-BD FOR BRI-BD CIRCUIT PACKS * FOLLOW THE REPAIR...
Page 151: Troubleshooting Isdn-Pri Test Calls
Troubleshooting ISDN-PRI Test Calls Troubleshooting ISDN-PRI Test Calls An ISDN-PRI test call is placed across an ISDN-PRI user-network interface to a previously designated number in order to test ISDN capabilities of the switch, the trunk and the far end. An ISDN-PRI test call is also a maintenance procedure concerned with the identification and verification ISDN-PRI user-network interface problems.
Page 152 Alarms, Errors, and Troubleshooting Asynchronous Method The asynchronous method requires a Maintenance/Test circuit pack to be present in the system. In this method, 4 commands are used to start, stop, list, and query an outgoing ISDN-PRI test call: Start: test isdn-testcall grp/mbr [minutes] Stop: clear isdn-testcall grp/mbr List:...
Page 153 Troubleshooting ISDN-PRI Test Calls The functions of the clear, list, and status commands associated with the ISDN Testcall are summarized in ‘‘Troubleshooting the Outgoing ISDN-Testcall Command’’ on page 4-80. clear isdn-testcall: Enables you to cancel an in-progress ISDN-PRI test call and allow another test call to start. list isdn-testcall: Enables you to list every ISDN-PRI trunk in use for an ISDN-PRI test call in the system.
Page 154: Troubleshooting The Outgoing Isdn-Testcall Command
Alarms, Errors, and Troubleshooting Troubleshooting the Outgoing ISDN-Testcall Command If the TestCall BCC field appears on the Trunk Group Administration form, make sure the TestCall BCC field indicates the correct BCC for the service provisioned on the ISDN-PRI trunk. The TestCall BCC values are defined as follows: Voice Digital Communications Protocol Mode 1...
Page 155: Isolating And Repairing Packet-Bus Faults
Isolating and Repairing Packet-Bus Faults Isolating and Repairing Packet-Bus Faults The following procedures provide a means of isolating and correcting faults on both the packet bus and the various maintenance objects (MOs) that use the packet bus. The packet bus is shared by every circuit pack that communicates on it, and a fault on one of those circuit packs can disrupt communications over the packet bus.
Page 156 Alarms, Errors, and Troubleshooting ‘‘Packet Bus Fault Isolation Flowchart’’ on page 4-99: Is the starting point for the troubleshooting process. It is used to determine whether a failure of service is caused by the packet bus itself or by another MO on the packet bus.
Page 157 Isolating and Repairing Packet-Bus Faults Tools for Packet-Bus Fault Isolation, Correction The following tools may be required on-site to perform packet-bus fault isolation and correction. TN771D Maintenance/Test circuit pack for use in stand-alone mode, and the connectors and cables necessary to install it (see ‘‘M/T-BD (Maintenance/Test Circuit Pack)’’...
Page 158 Alarms, Errors, and Troubleshooting Packet-Bus Faults Two types of packet-bus faults can occur: Shorts A short occurs when different leads on the packet bus become electrically connected to each other. This can occur due to failures of circuit packs, cables between carriers, TDM/LAN terminators, or bent pins on the backplane.
Page 159 Isolating and Repairing Packet-Bus Faults TN771D Maintenance/Test: — ‘‘M/T-BD (Maintenance/Test Circuit Pack)’’ on page 8-1157 — ‘‘M/T-DIG (Maintenance/Test Digital Port)’’ on page 8-1161 — ‘‘M/T-PKT (Maintenance/Test Packet Bus Port)’’ on page 8-1175 Circuit Packs that Use the Packet Bus This section describes the circuit packs that use the packet bus and the mutual effects of circuit-pack and bus failures.
Page 160 Alarms, Errors, and Troubleshooting Effects of Circuit-Pack Failures on the Packet Bus Certain faults of any of the previous circuit packs can disrupt traffic on the packet bus. Some failures cause packet-bus problems with corresponding alarms, while others cause service outages without alarming the packet bus (although the failed circuit pack should be alarmed).
Page 161 Isolating and Repairing Packet-Bus Faults TN771D Maintenance/Test — A Maintenance/Test board’s fault may either: — Falsely indicate a packet-bus fault — Cause the inability to detect such a fault If the test board’s fault is on its packet-bus interface, the packet bus may also be alarmed.
Page 162 Alarms, Errors, and Troubleshooting Comparing Packet and TDM Buses The packet and TDM buses have several similarities and differences. There are two physical TDM buses in each EPN. One of the buses can fail without affecting the other, but half of the call-carrying capacity is lost. There is one packet bus in each PN.
Page 163 Isolating and Repairing Packet-Bus Faults Packet Bus maintenance software Packet Bus maintenance software involves the usual set of MO error conditions, tests, and alarms. These are described in ‘‘PKT-BUS (Packet Bus)’’ on page 8-1230. Since an EPN’s packet-bus fault can cause every BRI/ASAI endpoint and its associated port and circuit pack to report faults, be careful to prevent a flood of error messages overloading the system and interfering with traffic on the TDM bus.
Page 164 Alarms, Errors, and Troubleshooting Overview of Fault Correction Procedures This section gives an overview of the procedures used to isolate the cause and to correct packet bus faults. Details are presented in following sections. 1. Procedure 1 attempts to determine whether a circuit pack that interfaces to the packet bus is the cause of the packet bus problem.
Page 165 Isolating and Repairing Packet-Bus Faults The analog trunk testing functions are discussed in the following sections in Chapter 8, ‘‘Maintenance-Object Repair Procedures’’: ‘‘TIE-TRK (Analog Tie Trunk)’’ on page 8-1638 ‘‘DID-TRK (Direct Inward Dial Trunk)’’ on page 8-515 ‘‘AUX-TRK (Auxiliary Trunk)’’ on page 8-310 NOTE: Every Maintenance/Test circuit pack must be of TN771D vintage or later.
Page 166 Alarms, Errors, and Troubleshooting TN771D in Stand-Alone Mode In TN771D stand-alone mode, a terminal is connected to the Maintenance/Test circuit pack with an Amphenol connector behind the cabinet. This setup allows direct inspection of the packet bus and identifies shorted or open leads. This mode does not use the usual MT Maintenance User Interface and is therefore available even if switch is not in service.
Page 167 Isolating and Repairing Packet-Bus Faults Entering and Exiting Stand-Alone Mode While in stand-alone mode, the TN771D’s red LED is lit. This is normal and serves as a reminder to remove the TN771D from stand-alone mode. CAUTION: A TN771D in stand-alone mode must be the only TN771D in the EPN. If one is already in the EPN, place it in stand-alone mode.
Page 168 Alarms, Errors, and Troubleshooting If stand-alone mode is entered successfully, the following is displayed on the connected terminal: TN771 STAND-ALONE MODE (Type “?” at the prompt for help) Command: NOTE: If the previous display does not appear, check the wiring between the terminal and the TN771D, and the terminal parameters settings.
Page 169 Isolating and Repairing Packet-Bus Faults Following is an example of a stand-alone mode display. The symbols above the line represent specific leads on the backplane. The bottom line indicates the following: L L L L L L L L L L H H H H H H H H H H S S S L P 0 1 2 3 4 5 6 7 8 P 0 1 2 3 4 5 6 7 8 S F B F _______________________________________________ Command:...
Page 170 Alarms, Errors, and Troubleshooting Figure 4-43 shows the location of the packet bus leads for a given slot as seen from the front and back of the carrier. Front View Backplane Separation Figure 4-43. Packet Bus Leads on the Backplane—Front View 4-96 Issue 1 May 2002 555-233-143...
Page 171 Isolating and Repairing Packet-Bus Faults Back View Figure 4-44. Packet Bus Leads on the Backplane—Back View 555-233-143 Issue 1 May 2002 4-97...
Page 172 Alarms, Errors, and Troubleshooting Special Precaution Concerning the TN771D A TN771D Maintenance/Test circuit pack must be taken to the customer site if: The Maintenance/Test packet-bus port indicates that a packet-bus fault is present by logging a major or minor alarm against PKT-BUS. A major alarm is indicated in the error log by error type 513;...
Page 173 Isolating and Repairing Packet-Bus Faults Packet Bus Fault Isolation Flowchart Figure 4-45 on page 4-100 shows the steps to be taken for isolating and resolving a packet-bus problem. The order of examining maintenance objects (MOs) can be determined by assessing how wide-spread the failure is. For example, since every ISDN-BRI device communicates with the TN2312 IPSI circuit pack’s Packet Interface circuit, its MO should be examined early in the sequence On the other hand, a failure of an EPN’s TN570 circuit pack may cause an ISDN-BRI failure in...
Page 174 Alarms, Errors, and Troubleshooting Refer to Is packet "maintenance related START bus use system parameters enabled? form" in chapter 5 Are the Follow the repair Are there packet bus procedure for alarms or errors problems TDM-CLK TDM-CLK? resolved? Are there Follow the repair Is only alarms or errors...
Page 175 Isolating and Repairing Packet-Bus Faults From page Is a Are there Follow the repair TN771 present alarms or errors procedure for in this port against 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 176 Alarms, Errors, and Troubleshooting Flowchart Notes The following paragraphs refer by letter to corresponding entries in Figure 4-46 on page 4-101. Individual errors and alarms are not detailed in this flowchart. When referring to explanations of these in Chapter 8, ‘‘Maintenance-Object Repair Procedures’’, any that do not refer explicitly to the TDM bus (except TDM-CLK) should be considered a possible cause of packet-bus problems.
Page 177 Isolating and Repairing Packet-Bus Faults h. If work is being done on-site, follow the procedures described earlier in this discussion on stand-alone mode. If work is not being done on-site, go to the next step. i. The answer is “yes” if any of the following apply: The TN771D in stand-alone mode indicates any faulty leads.
Page 178 Alarms, Errors, and Troubleshooting If test results or the results of the status port-network command indicate that there are 24 faults on the packet bus, the problem is probably caused by faulty cables between carriers, or by defective or missing bus terminators. However, before proceeding, make sure that the Maintenance/Test packet-bus port is not generating a false report by looking for an M/T-PKT error in the error log.
Page 179 Isolating and Repairing Packet-Bus Faults Continue with the ‘‘Troubleshooting Procedures’’ in the next section. Troubleshooting Procedures Packet-bus faults are usually caused by a defective circuit pack connected to the backplane, by bent pins on the backplane, or by defective cables or terminators that make up the packet bus.
Page 180 Alarms, Errors, and Troubleshooting Procedure 1: Circuit Pack Fault Detection Procedure 1 determines whether any circuit packs that use the packet bus have faults. For each circuit pack type in Table 4-8 proceed through the following steps. Check these circuit packs in the order presented by the flowchart shown earlier in this discussion —...
Page 181 Isolating and Repairing Packet-Bus Faults If the packet-bus problem is present when the circuit pack is inserted, but is resolved when the circuit pack is removed, either the circuit pack or the backplane pins in that slot caused the problem. If the backplane pins are intact, replace the circuit pack.
Page 182 Alarms, Errors, and Troubleshooting 4. If the packet-bus fault is not present: a. Reinsert circuit packs one at a time and repeat the following substeps until every circuit pack has been reinserted. b. Determine whether the packet-bus fault has returned. c.
Page 183 Isolating and Repairing Packet-Bus Faults 3. If the pins are bent: a. Power down the carrier if it is not already. b. Straighten or replace the pins. c. Insert the same circuit pack. d. Restore power to the carrier. 4. If the backplane pins are not bent, reinsert or replace the circuit pack. 5.
Page 184 Alarms, Errors, and Troubleshooting alarm status for these circuit packs. Every alarm should be resolved when the cabinet is restored to its original configuration. TDM/LAN Bus Terminator TDM/LAN Bus Cable Carrier C Carrier B Carrier A Fans Carrier D Carrier E Bus Shortened Normally Shortened Bus...
Page 185 Isolating and Repairing Packet-Bus Faults 3. Determine whether the packet-bus fault is still present. If so, and if there are shorts on the packet bus, perform Procedure 2: Removing and Reinserting Port Circuit Packs and/or Procedure 3: Removing and Reinserting EPN’s Control Circuit Packs for only the circuit packs in carriers connected to the “shortened”...
Page 186 Alarms, Errors, and Troubleshooting 4-112 Issue 1 May 2002 555-233-143...
Page 187: Additional Maintenance Procedures
Additional Maintenance Procedures This chapter describes updates, tests and preventive measures not covered elsewhere in this book. It includes the following topics: ‘‘DS1 CPE Loopback Jack (T1 Only)’’ on page 5-2 ‘‘Facility Test Calls’’ on page 5-15 ‘‘Preventive Maintenance’’ on page 5-24 ‘‘Analog Tie Trunk Back-to-Back Testing’’...
Page 188: Ds1 Cpe Loopback Jack (T1 Only)
Additional Maintenance Procedures DS1 CPE Loopback Jack (T1 Only) Using the DS1 CPE loopback jack (apparatus code 700A, comcode 107988867), a technician can test the DS1 span between the system and the network interface point. The loopback jack is required when DC power appears at the interface to the Integrated Channel Service Unit (ICSU).
Page 189 DS1 CPE Loopback Jack (T1 Only) Installation To install the loopback jack: 1. 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-1 on page 5-8 through Figure 5-5 on page 5-12.
Page 190 Additional 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 on the management terminal, and provides the results of the second part of the test.
Page 191 DS1 CPE Loopback Jack (T1 Only) Table 5-1. DS1 Span Troubleshooting Displayed Field Function Indication Test: Pattern 3-in-24 The loopback jack test is active. cpe-loopback-jack 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 192 Additional 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 193 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 three separate sections for fault isolation. These sections are shown in Figure 5-1 on page 5-8 through Figure 5-3 on page 5-10...
Page 194 Additional 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 195 DS1 CPE Loopback Jack (T1 Only) Figure Notes 1. Span Section 1 6. Loopback Jack 2. Span Section 2 7. “Dumb” Block (Extended Demarcation) 8. Network Interface Smart Jack 3. Span Section 3 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
Page 196 Additional Maintenance Procedures Figure Notes 1. Span Section 1 6. “Dumb” Block (Extended Demarcation) 2. Span Section 2 7. Loopback Jack 8. Network Interface Smart Jack 3. Span Section 3 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
Page 197 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 two sections. See Figure 5-4 Figure 5-5 on page 5-12.
Page 198 Additional 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 (ICSU) 8. Fiber MUX 4. RJ-48 to Network Interface 9.
Page 199 DS1 CPE Loopback Jack (T1 Only) A problem can exist in one or both of the two 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 200 Additional 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 201: Facility Test Calls
Facility Test Calls Facility Test Calls The facility test calls feature allows you to use a voice terminal to make test calls to specific trunks, time slots, tones, and tone receivers within the system. The test call verifies that the accessed component is functioning properly. To use this feature, it must be enabled on the Class of Restriction form, and you must know the facility test call access code.
Page 202 Additional Maintenance Procedures Reorder tone The trunk requested is in a different port network from your station, and inter-PN resources are not available to access it. Intercept tone The port addressed is not a trunk, or it is a DID trunk, or the trunk is not administered.
Page 203 Facility Test Calls DTMR Test Call This call accesses and tests the dual-tone multifrequency receivers (DTMR-PTs) located on TN420 and TN748 Tone Detector circuit packs. These tone receivers are also known as touch-tone receivers (TTRs). Before making the test call, use list configuration to determine the location of the TN420 or TN748 that you want to test.
Page 204 Additional Maintenance Procedures TDM Bus Time Slot Test Call The time slot test call connects the voice terminal to a specified time slot on the A or B TDM Bus of a specified port network. To connect to any out-of-service time slots, refer to ‘‘Out-of-Service Time Slot Test Call’’...
Page 205 Facility Test Calls Table 5-2. TDM Bus Time Slot Numbers TDM Bus A TDM Bus B time slot time slot Tone Heard Reorder Reorder Reorder Reorder Reorder Touch Tone 1 — 697 Hz Touch Tone 2 — 770 Hz Touch Tone 3 — 852 Hz Touch Tone 4 —...
Page 206 Reorder tone Inter-PN resources are not available. System tone The specified tone will be heard if it is functioning. NOTE: For a definition of call progress tones see Overview for Avaya MultiVantage™ Software. Table 5-3. System Tone Identification Numbers Number Description...
Page 207 Facility Test Calls Table 5-3. System Tone Identification Numbers — Continued Number Description 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 Touch tone 4 Touch tone 5 Touch tone 6...
Page 208 Additional Maintenance Procedures Table 5-3. System Tone Identification Numbers — Continued Number Description Recall on don’t answer Audible ring Camp-on recall Camp-on confirmation Hold recall Hold confirmation Zip tone 2804 Hz 1004 Hz (-16db) 1004 Hz (0 db) 404 Hz Transmission test sequence 105 Redirect tone Voice signaling tone...
Page 209 Facility Test Calls Table 5-3. System Tone Identification Numbers — Continued Number Description CO dial tone Repetitive confirmation tone Conference/bridging tone Continued on next page 555-233-143 Issue 1 May 2002 5-23...
Page 210: Preventive Maintenance
Systems with an uninterruptible power supply (UPS) may not be equipped with backup batteries. Media Server UPS Batteries For information about maintaining the batteries that support the S8700 Media Servers, see the User’s Guide or other product documentation that ships with the UPS.
Page 211 Preventive Maintenance PREVENTIVE MAINTENANCE LOG Date equipment installed: ________________________ Scheduled Date Completed Scheduled Date Completed Air Filters Date Completed Date Completed Single-carrier cabinet Multicarrier cabinet Battery Scheduled Date Completed Scheduled Date Completed Packs Date Completed Date Completed Single-carrier cabinet Multicarrier cabinet Inspect annually;...
Page 212: Analog Tie Trunk Back-To-Back Testing
Additional Maintenance Procedures Analog Tie Trunk Back-to-Back Testing The TN760 circuit pack can be configured for back-to-back testing (also known as connectivity testing) by making translation and cross-connect changes. This testing configuration allows for the connection of tie trunks back-to-back in the same switch to verify the operation of tie trunk ports.
Page 213 Analog Tie Trunk Back-to-Back Testing 11. At the cross-connect field, disconnect outside trunk facilities from the tie trunk ports and mark the disconnected wires for reconnecting the tie trunk ports to their normal configuration later. The D impact tool (AT-8762) is required to perform this step.
Page 214 Additional Maintenance Procedures Table 5-4. Carrier Lead Appearances MDF — Continued 110 Connecting Block Terminals CO Trunk TN747 Tie Trunk TN760 Continued on next page 5-28 Issue 1 May 2002 555-233-143...
Page 215 Analog Tie Trunk Back-to-Back Testing Table 5-4. Carrier Lead Appearances MDF — Continued 110 Connecting Block Terminals CO Trunk TN747 Tie Trunk TN760 Continued on next page 555-233-143 Issue 1 May 2002 5-29...
Page 216 Additional Maintenance Procedures Simplex Mode Test Procedure 1. Repeat steps 1 through 7 of the ‘‘E&M Mode Test Procedure’’ on page 5-26. 2. Set the dip (option) switches for each of the two ports to be tested on the Tie Trunk circuit pack to simplex mode. 3.
Page 217: Terminating Trunk Transmission Testing
Terminating Trunk Transmission Testing Terminating Trunk Transmission Testing The Terminating Trunk Transmission (TTT) (non-interactive) 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 218: Removing And Restoring Power
Additional Maintenance Procedures Removing and Restoring Power CAUTION: If there is an alarm or problem suspected on the removable media do not save translations to the affected device. Removing and Restoring Power to the Media Gateway: 1. For a multicarrier EPN cabinet, set the emergency transfer switch to ON. This locks the EPN in the emergency transfer mode until the trouble is cleared.
Page 219 Removing and Restoring Power Removing and Restoring Power from the Media Server The media server is shut down from the media server web interface. To shut down a server: 1. On the web interface main menu, under Server, click Shutdown This Server.
Page 220: Automatic Transmission Measurement System
Additional Maintenance Procedures Automatic Transmission Measurement System The Automatic Transmission Measurement System (ATMS) performs transmission tests on analog trunks to determine whether they are performing satisfactorily. The switch automatically originates test calls from an Originating Test Line (OTL), over the trunks to be tested, to a Terminating Trunk Line (TTL) on the switch at the far end of the trunk.
Page 221 Automatic Transmission Measurement System Table 5-5. ATMS Administration Form Field Entry/Remarks System-parameters y If this field is not enabled, must be ATMS? customer options enabled via license file. Station At least one TN711 analog port must be Extension assigned. UUCSS01 where UUCSS is the location Port Number of any TN771 105TL...
Page 222 Additional Maintenance Procedures Normally you should invoke only the full or supervision tests. The other options are provided mainly for use in setting up an ATMS schedule. The tests that are run depend on the type of TTL at the far end to which the test call is made. The following table shows which tests are run for each type of TTL.
Page 223 Automatic Transmission Measurement System Table 5-6. Measurement Capability by TTL Type Terminating Test Line Type 105 Type 105 Type High-Level/ with Return without Low-Level Test Loss Return Loss Tone Source 100 Type 102 Type Loss at 1004 Hz Far End to Near End Loss at 1004 Hz Near End to Far End Loss at 404 Hz Far...
Page 224 Additional Maintenance Procedures Test Call Results If the test call successfully completes, and every trunk tests within administered thresholds for marginal and unacceptable performance, then a PASS result is returned. If the test aborts or fails, an error code indicating the cause is returned. The error codes are explained in the CO-TRK and TIE-TRK sections of ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’...
Page 225 Automatic Transmission Measurement System Output Fields The physical location of the port supporting the trunk being Port tested. The format is UUCSSpp where UU is the cabinet number, C is the carrier letter, SS is the circuit pack slot, and pp is the port circuit number.
Page 226 Additional Maintenance Procedures The detailed report lists measurements for each trunk-group member. The summary reports lists trunk groups as a whole. The measurements that are displayed depends on what type of test, if any, was last run on the trunk, and the capabilities of the TTL on the switch at the far end of the trunk.
Page 227 Automatic Transmission Measurement System Input Parameters—List Testcall Command detail This qualifier specifies a detailed report that shows each measurement made for each trunk. summary This qualifier specifies a report that shows totaled results of ATMS tests for trunk groups as a whole. grp # This qualifier specifies a report showing measurements for a specific trunk group.
Page 228 Additional Maintenance Procedures ATMS MEASUREMENT SUMMARY REPORT Trunks Trunks Trunks Last Last Passed Failed Failed Trks Trks Busied Test Test Transm Marginal Unaccept Trks Date Time Test Threshld Threshld Test Trunks 10/04/91 15:15 10/04/91 15:40 10/04/91 16:00 10/04/91 16:15 10/04/91 16:40 10/04/91 16:55 10/04/91 17:05 10.04/91 17:20...
Page 229 Automatic Transmission Measurement System ATMS Detail Report This report is divided into two sections. The upper section lists the trunk group, trunk type, trunk vendor, TTL type, and the user-defined threshold values administered on page 4 of the Trunk Group form. The lower section lists the most recent set of measurements for each member of the trunk group selected for the report.
Page 230 Additional Maintenance Procedures Output Fields—ATMS Detail Report Measurements are made in both directions, near to far end, and far to near end. For each measurement, there are two columns on the lower part of the report, “NE” for near end, and “FE” for far end. These refer to the destination end for that measurement.
Page 231 Automatic Transmission Measurement System Singing return loss from 0 to 40 dB between the sum of the circuit (repeater) gains SRL-LO and the sum of the circuit losses. SRL-LO occurs most often in the frequency range of 200 to 500 Hz. Singing return loss from 0 to 40 dB between the sum of the circuit (repeater) gains SRL-HI on a circuit and the sum of the circuit losses.
Page 232 Additional Maintenance Procedures 5-46 Issue 1 May 2002 555-233-143...
Page 233: Led Interpretation
‘‘DS1 CONV (TN574/TN1654) Circuit Pack LEDs’’ ‘‘Tone-Clock Circuit Pack LEDs’’ ‘‘Server LEDs’’ ‘‘IPSI LEDs’’ ‘‘Duplication Memory Card LEDs’’ For information on interpreting LEDs and testing procedures during installation, refer to Installing the Avaya S8700 Media Server for Multi-Connect Configurations. 555-233-143 Issue 1 May 2002...
Page 234: Alarm Levels
LED Interpretation Alarm Levels If a maintenance object in the system begins to fail some of the periodic tests, the system automatically generates an alarm that indicates the system needs to be restored to a normal condition. The system identifies three levels of alarms: Major alarms —...
Page 235: Terminal Alarm Notification
Terminal Alarm Notification 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 10 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 236: Attendant Console Leds
The ACK LED lights steadily if the alarm has been successfully reported. If the system is unable to report the alarm, the LED flashes; this signals the attendant to call the Avaya alarm receiving system and report the alarm.
Page 237: Circuit Pack Leds
Circuit Pack LEDs Circuit Pack LEDs Typically each circuit pack has three LEDs on the front panel visible at the front of the carrier. There are some exceptions to this (for example, DS1CONV or IPSI circuit pack) that are covered later in this section. On most circuit packs, the LEDs indicate the following when lit.
Page 238 LED Interpretation After a circuit pack has been initialized, a red LED should be accompanied by an alarm in the alarm log. A single fault can sometimes light alarm LEDs on several circuit packs, as in the following examples. A TDM bus problem may cause several port circuit packs to display red LEDs.
Page 239 Circuit Pack LEDs Expansion Interface Circuit Pack LEDs The Expansion Interface (EI) TN570 circuit pack has the standard red, green and yellow LEDs. The red and green LEDs have the traditional meaning, where red indicates an alarm condition, and green indicates testing in progress. The yellow LED displays various flashing patterns to provide status information useful in isolating faults in the fiber link and other components connected to the fiber link.
Page 240 LED Interpretation Table 6-2. Maintenance circuit pack LED interpretation LED color State Level/Function Interpretation flashing MAJOR Major alarm against a component in the same cabinet (EPN for MAINT). solid MAJOR Major alarm against a component in another cabinet. solid MINOR Minor alarm against a component in another cabinet.
Page 241 Circuit Pack LEDs These LEDS are illustrated Figure 6-1. Figure Notes: 1. Alarm LED (Red) 2. Test LED (Green) 3. Busy LED (Yellow) 4. Latch Pin 5. Locking Lever Figure 6-1. Circuit Pack LEDs on Faceplate 555-233-143 Issue 1 May 2002...
Page 242 LED Interpretation DS1 CONV (TN574/TN1654) Circuit Pack LEDs The TN574 and the TN1654 LEDs provide an indication of the state of the DS1 Converter and facilities. NOTE: DS1 converters are used exclusively with a CSS. TN574 Circuit Pack LEDs Seven LEDs provide an indication of the state of the DS1 converter (DS1 CONV) TN574 circuit pack and the DS1 facilities.
Page 243 Circuit Pack LEDs DS1 Facility LEDs Below the three standard LEDs on the DS1C circuit pack are four green LEDs that indicate whether a receive signal is present for each of the four DS1 facilities. Figure 6-2 shows which facility (A, B, C, or D) corresponds to each LED. If a green LED is off, there is a Loss of Signal condition on the DS1 facility associated with that LED.
Page 244 LEDs indicate the state of the DS1CONV board. These LEDs are under firmware control until the board has established a link to the S8700 Media Server via the EI or SNI. Once the link is established, software controls the three LEDs.
Page 245 Circuit Pack LEDs The bottom four LEDs on the TN1654 board are labeled SPAN LEDs. These LEDs are under firmware control. If the facility is not administered, then the LED is not lit. The LED is lit amber if the facility is running alarm free. If the facility is detecting either a red alarm (loss-of-signal or loss-of-frame), a yellow alarm (remote frame alarm) or a blue alarm (AIS signal) then the LED is lit red.
Page 246 LED Interpretation Switch Node Interface LEDs The Switch Node Interface (SNI) TN573 circuit pack has the standard red, green, and yellow LEDs. The red and green LEDs have the traditional meaning, where red indicates an alarm condition, and green indicates testing in progress. The yellow LED displays various flashing patterns to provide status information useful in isolating faults in the fiber link and other components connected to the fiber link.
Page 247 Circuit Pack LEDs Maintenance/Test Circuit Pack LEDs The TN771D maintenance/test circuit pack has the standard red, green, and yellow LEDs. The red and green LEDs have the traditional meaning, where red indicates an alarm condition, and green indicates testing in progress. The yellow LED can be off or on continuously or flashing, depending on the mode of operation of the TN771D and whether or not it has detected errors.
Page 248: Server Leds
LED Interpretation Server LEDs The server has an LED called Active/Standby that indicates whether the server is the active server or the standby server. The Active/Standby LED in the “on” state implies active and in the “flashing” state implies standby. It flashes at the rate of 400 ms “on”...
Page 249 Server LEDs System Shutdown LEDs All server and Avaya duplication memory card LEDs are in the “off” state but still powered “on” when the server is shut down. Testing Server LEDs Using the web interface, click on the Test Server LEDs screen to make sure that...
Page 250 LED Interpretation Resolving problems If the server is hung, you do not need to do anything. It should automatically reboot and fix itself. If the server does not reboot itself, power it down and then reboot it. If an LED is clearly stuck or has a burned out element, ignore the indicators until you can conveniently replace the server.
Page 251 Server LEDs For all other LEDs, refer to the quick start guide and user guide that came with the Cajun Ethernet switch. UPS LEDs All Ethernet hubs and UPSs have LEDs to indicate that they are powered on or off. LEDs “on” imply the device is powered on. LED “off” implies the device is powered down.
Page 252 LED Interpretation The LED on the top row is the Normal mode indicator, the LEDs on the second row are the Battery mode indicators, and the LED on the third row is the Bypass mode indicator. When the Normal mode LED is steady green, it has power. If the LED is flashing, the UPS is in standby mode.
Page 253: Ipsi Leds
IPSI LEDs IPSI LEDs The IPSI board has four LEDs. The top three LEDs behave like the standard LEDs that are found on all TN circuit packs. The fourth (bottom) LED imitates the TN 2182 Tone-Clock yellow LED. The archangel flashes the yellow LED when active, 2 seconds on and 200 msec off.
Page 254 LED Interpretation Figure Notes: 1. IPSI using DHCP 2. IPSI has connectivity and an IP address Figure 6-8. S8700 IP Connect IPSI Board Display 6-22 Issue 1 May 2002 555-233-143...
Page 255 IPSI LEDs Figure Notes: 1. Switch identifier 2. Cabinet (1 — 64) 3. IPSI has connectivity and an IP address Figure 6-9. S8700 Multi-Connect IPSI Board Display 555-233-143 Issue 1 May 2002 6-23...
Page 256: Duplication Memory Card Leds
LED Interpretation Duplication Memory Card LEDs The Duplication Memory Card has LEDs that indicate active/standby, fiber link integrity/activity states. Also see ‘‘System Shutdown LEDs’’. Testing the Duplication Memory Card LEDs When you test the LEDs, the DAJ-1 duplication memory card LED should blink according to the following pattern: 1 second red, 1 second red off, 1 second green, 1 second green off and so on for a total of one minute.
Page 257: Maintenance Commands
Avaya MultiVantage Software. S8700 Media Server SAT Screens For this release, some information is specific to the Avaya S8700 Media Server for Multi-Connect Configurations (S8700 Multi-Connect) or the Avaya S8700 Media Server for IP Connect Configurations (S8700 IP Connect). However, where a command is valid for both configurations but the information displayed in SAT screens differs, examples of each one are shown and labelled accordingly.
Page 258: New Commands
IPSIs or CNs, executing the command to force CN traffic should have no service impact. The following SAT commands are new for the S8700 Multi-Connect and S8700 IP Connect configurations: ‘‘add ipserver-interface’’...
Page 259 New Commands Platform/Server Commands For a list and explanation of these commands, refer to the section on network time protocol in Installing the Avaya S8700 Media Server for Multi-Connect Configurations . 555-233-143 Issue 1 May 2002...
Page 260: Modified Commands
The list configuration license command has been replaced by the serialnumber shell command. Refer to the Administrator’s Guide for Avaya MultiVantage Software . The remove license command is not available for the S8700 media servers because you can manually delete license files from the operating system. reset login-session n This command was replaced with reset login-ID prior to this release.
Page 261: Command-Line Syntax
Command-Line Syntax Command-Line Syntax Each command consists of an action word, an object upon which the action is performed, and optional qualifiers that modify the execution of the command. In some cases, the choice of a qualifier may be required. The syntax of the command appears under the heading at the beginning of each command description.
Page 262: Common Input Parameters
Table 7-1. Common Test Command Parameters Parameter Range Meaning 1-64 Specify cabinet number and carrier for S8700 Media Server you want to test. 1-64 1-digit to 2-digit cabinet number A–E Letter designation of a carrier. For many commands relating to EPN Control circuit packs, this defaults to A, the control carrier.
Page 263 Common Input Parameters Table 7-2. Less-Common Test Command Parameters — Continued Parameter Range Default Meaning schedule A scheduling form is displayed that allows you to specify a start time for the command. The command is placed in the queue and, when executed, sends the output to the system printer.
Page 264 Maintenance Commands Table 7-2. Less-Common Test Command Parameters — Continued Parameter Range Default Meaning clear Used with test commands, this specifies that the test sequence is to be repeated until any active alarms against the maintenance object is cleared by the passing of tests or until any test in the sequence fails.
Page 265: Common Output Fields
Common Output Fields Common Output Fields Common output can be any of the following information: An indication that the command successfully completed or a self-explanatory message giving a reason for a failure or abort. An input form for entering additional information required to complete the command.
Page 266 Maintenance Commands The names of MOs are as follows: Maintenance Name The name of the MO as it appears in the alarm and error logs. Alt. Name The output screens of many commands list an alternate name for certain MOs in addition to their port address (physical location).
Page 267 Common Output Fields Test No. The number of the test run on the MO as part of a test command. Descriptions of each test and its related error codes appear under the relevant MO. Other commands such as clear firmware-counters and reset also report a test number.
Page 268: Contention Between Simultaneous Commands
Maintenance Commands Contention Between Simultaneous Commands The following limits apply to simultaneous maintenance and administration activities: Up to 15 users can be logged into the system at the same time. Up to five maintenance commands can run concurrently. Up to 10 administration commands can run concurrently. In general, a maintenance object or other system entity can be acted upon by only one command at a time.
Page 269: Busyout And Release Commands
Busyout and Release Commands Busyout and Release Commands The busyout command places the object of the command in a maintenance busy state. In the busyout state: The object is removed from active service and is not available for use by call processing.
Page 270 Maintenance Commands The following display shows a typical result for most maintenance objects for busyout link 1. See ‘‘Common Output Fields’’ above for an explanation of the fields displayed. COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01A0617 ETH-PT PASS Command successfully completed...
Page 271: Common Abort And Fail Codes
Common Abort and Fail Codes Common Abort and Fail Codes Table 7-3 lists common error codes associated with abort and fail results for busyout, release, test, and reset commands. In addition to these, many maintenance objects have other unique error codes. Table 7-3.
Page 272 Maintenance Commands Table 7-3. Common Error Codes for Busyout, Release, Test, and Reset Commands — Continued Error Command Code Result Description/Recommendation EXTRA BD This result can appear for Maintenance/Test, Call Classifier, Tone Detector, Announcement, and Speech Synthesis circuit packs. Each of these circuit packs has restrictions on how many can be installed in the system or in a port network.
Page 273: Alarm And Error Categories
Alarm and Error Categories Alarm and Error Categories The display alarms and display errors commands allow you to generate reports for certain groups of maintenance objects. By entering a category from Table 7-4 into the Category field of the input form, you can restrict the report to only those maintenance objects included in that category.
Page 274 Maintenance Commands Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects detector, cont’d. GPTD-PT TONE-BD DI-BD DI-PT environ AC-POWER CABINET CARR-POW DC-POWER EMG-XFER EXT-DEV POWER RING-GEN exp-intf AC-POWER CARR-POW DC-POWER EPN-SNTY EXP-INTF MAINT SYNC TDM-CLK TONE-BD ext-dev CUST-ALM generatr STRAT-3...
Page 275 Alarm and Error Categories Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects infc, cont’d. ISDN-LNK ISDN-SGRP MEDPRO IPMEDPRO MEDPROPT H323-SGRP H323-BCH H323-STN DIG-IP-STN RDIG-STA RANL-STA NR-CONN REM-FF ASAI-IP ADJLK-IP SIP-SGRP lic-file NO-LIC LIC-ERR maint MAINT Continued on next page 555-233-143 Issue 1 May 2002 7-19...
Page 276 Maintenance Commands Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects misc CONFIG ERR-LOG PROC-SAN SYSTEM TIME-DAY MMI-BD MMI-LEV MMI-PT MMI-SYNC mnt-test M/T-ANL M/T-BD M/T-DIG M/T-PKT modem MODEM-BD MODEM-PT M/T-PKT PKT-BUS pms/jrnl JNL-PRNT PMS-LINK DS1C-BD DS1-FAC EXP-INTF FIBER-LK PNC-DUP SN-CONF...
Page 277 Alarm and Error Categories Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects pnc, cont’d. SNI-PEER pncmaint DS1C-BD DS1-FAC EXP-INTF FIBER-LK PNC-DUP SN-CONF SNC-BD SNC-LINK SNC-REF SNI-BD pnc-peer SNI-PEER procr PROCR quick-st ABRI-PT ADXDP-PT ANL-16-LINE ANL-LINE ANL-NE-LINE ANN-PT ANNOUNCE ASAI-ADJ...
Page 278 Maintenance Commands Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects quick-st, cont’d. DAT-LINE DID-DS1 DID-TRK DIG-LINE DIOD-TRK DS1-FAC DS1C-BD DTMR-PT EPN-SANITY EXP-INTF EXP-PN FIBER-LNK GPTD-PT HYB-LINE ISDN-LNK ISDN-TRK JNL-PRNT MAINT MET-LINE MODEM-PT OPS-LINE PDATA-PT PDMODULE PKT-BUS PKT-INT PMS-LINK PMS-PRNT...
Page 279 Alarm and Error Categories Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects quick-st, cont’d. SN-CONF SNC-BD SNC-LNK SNC-REF SNI-BD SNI-PEER SYS-PRNT SYSLINK SYSTEM TDM-BUS TDM-CLK TDMODULE TIE-DS1 TIE-TRK TONE-BD TTR-LEV sch-adj SCH-ADJ s-syn S-SYN-BD S-SYN-PT stabd ABRI-PORT ADXDP-BD ADXDP-PT...
Page 280 Maintenance Commands Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects stabd, cont’d. BRI-BD BRI-PORT BRI-SET DIG-BD DIG-LINE HYB-BD HYB-LINE MET-BD MET-LINE stacrk ADXDP-PT ANL-LINE ANL-16-LINE ANL-NE-LINE AUDIX-PT DIG-LINE HYB-LINE MET-LINE OPS-LINE stations ABRI-PORT ADXDP-PT ANL-16-LINE ANL-LINE ANL-NE-LINE ASAI-ADJ AUDIX-PT...
Page 281 Alarm and Error Categories Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects stations, cont’d. OPS-LINE sys-link SYS-LINK sys-prnt SYS-PRNT TDM-BUS tone CLSFY-BD CLSFY-PT DETR-BD DTMR-PT GPTD-PT STRAT-3 SYNC TDM-CLK TONE-BD TONE-PT TTR-LEV trkbd AUX-BD AUX-TRK CO-BD CO-DS1 CO-TRK DID-BD...
Page 282 Maintenance Commands Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects trkbd, cont’d. TIE-TRK UDS1-BD WAE-PT trkcrk AUX-TRK CO-DS1 CO-TRK DID-DS1 DID-TRK DIOD-TRK ISDN-LNK ISDN-TRK TIE-DS1 TIE-TRK trunks CO-TRK AUX-TRK CO-DS1 DID-DS1 DID-TRK DIOD-TRK ISDN-LNK ISDN-TRK PE-BCHL TIE-DS1 TIE-TRK WAE-PORT...
Page 283 Alarm and Error Categories Table 7-4. Alarm and Error Categories — Continued Error Category Maintenance Objects vsp, cont’d. MMI-PT MMI-LEV MMI-SYNC VC-LEV VC-BD VC-SUMPT VC-DSPPT VP-BD VP-PT VPP-BD VPP-PT DI-BD DI-PT MEDPRO IPMEDPRO MEDPROPT wide-band PE-BCHL WAE-PORT wireless RC-BD RFP-SYNC WT-STA Continued on next page 555-233-143...
Page 284 Maintenance Commands Table 7-5. Alarm and Error Categories (Sorted by MO) Maintenance Object Error Categories ABRI-PORT bri/asai quick-st stabd stations AC-POWER environ exp-intf ADJLK-IP ADM-CONN adm-conn ADXCL-BD ADXCL-PT ADXCL-RS ADXDP-BD quick-st stabd ADXDP-PT quick-st stabd ADXDP-RS ANL-16-L quick-st sta-bd stacrk stations ANL-BD stabd...
Page 285 Alarm and Error Categories Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories ASAI-ADJ bri/asai quick-st sta-bd stations ASAI-IP AUDIX-BD quick-st sta-bd AUDIX-PT quick-st stabd stacrk stations AUDIX-RES AUX-BD trkbd AUX-TRK quick-st trkbd trkcrk trunks BRI-BD bri/asai...
Page 286 Maintenance Commands Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories CARR-POW environ exp-intf wireless CDR-LNK quick-st CLSFY-BD tone CLSFY-PT tone quick-st CO-BD trkbd CO-DS1 quick-st trkbd trkcrk trunks CO-TRK quick-st trkbd trkcrk trunks CONFIG misc quick-st...
Page 287 Alarm and Error Categories Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories DI-PT, cont’d. DID-DS1 quick-st trkbd trkcrk trunks DID-TRK quick-st trkbd trkcrk trunks DIG-BD sta-bd DIG-IP-STN DIG-LINE quick-st stabd stacrk stations DIOD-BD trkbd DIOD-TRK quick-st...
Page 288 Maintenance Commands Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories DTMR-PT, cont’d. quick-st mbus EMG-XFER environ EPN-SNTY exp-intf quick-st ERR-LOG misc EXP-INTF exp-intf infc pncmaint quick-st EXP-PN quick-st EXT-DEV environ ext-dev FIBER-LK pncmaint quick-st GPTD-PT detector...
Page 289 Alarm and Error Categories Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories IPMEDPRO ISDN-LNK infc quick-st trkcrk trunks ISDN-SGR infc ISDN-TRK quick-st trkbd trkcrk trunks JNL-PRNT quick-st LIC-ERR lic-file MAINT exp-intf maint quick-st MEDPRO MEDPROPT MET-BD...
Page 290 Maintenance Commands Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories MODEM-BD modem MODEM-PT modem quick-st M/T-ANL mnt-test M/T-BD mnt-test M/T-DIG mnt-test M/T-PKT mnt-test NO-LIC lic-file NR-CONN OPS-LINE quick-st stacrk stations PDATA-BD PDATA-PT quick-st PDMODULE data-mod quick-st...
Page 291 Alarm and Error Categories Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories POWER-DC PRI-CDR quick-st PROC-SAN misc RANL-STA RC-BD wireless RDIG-STA RFP-SYNC wireless REM-OFF RING-GEN environ S-SYN-BD quick-st S-SYN-PT quick-st s-syn SCH-ADJ sch-adj SIP-SGRP SN-CONF pncmaint...
Page 292 Maintenance Commands Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories SNI-PEER pnc-peer quick-st STRAT-3 generatr tone SVC-SLOT SYNC exp-intf generatr tone SYS-LINK sys-link SYS-PRNT quick-st sys-prnt SYSTEM misc quick-st TDM-BUS quick-st TDM-CLK exp-intf generatr quick-st tone...
Page 293 Alarm and Error Categories Table 7-5. Alarm and Error Categories (Sorted by MO) — Continued Maintenance Object Error Categories TIE-TRK, cont’d. trunks TIME-DAY misc TONE-BD detector exp-intf generatr quick-st tone TONE-PT generatr tone TSC-ADM TTR-LEV quick-st tone UDS1-BD trkbd VD-BD VC-LEV VC-DSPPT VC-SUMPT...
Page 294: Add Atm Pnc
Maintenance Commands add atm pnc This command adds a new ATM PNC to the system configuration and is not valid for S8700 IP Connect configurations. Table 7-6. add atm pnc command parameters Action/ Feature Object Qualifier Qualifier Description Permissions Defaults...
Page 295: Add Ipserver-Interface
This command administers a port-network n to be IPSI controlled. Host Name and DHCP ID are display-only fields. This command applies to both S8700 Media Server Multi-Connect and IP Connect Configurations. However, only the S8700 Multi-Connect will show a secondary IPSI.
Page 296 DNCP ID: ipsi-A01a Secondary IPSI -------------- Location: 1B01 Host: ipsi-A01b DHCP ID: ipsi-A01b Output (for S8700 IP Connect) add ipserver-interface 2 Page 1 of IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 2 Socket Encryption? y Primary IPSI QoS Parameters...
Page 297: Add Station
add station add station add station extension Output change station 67403 Page 1 of STATION Extension: 67403 Lock Messages? n BCC: 0 Type: 8410D__ Security Code: 1234____ TN: 1 Port: X______ Coverage Path 1: ____ COR: 1 Name: Vphone______________________ Coverage Path 2: ____ COS: 1 Hunt-to Station: _____ STATION OPTIONS...
Page 298: Busyout Cdr-Link
Maintenance Commands busyout cdr-link busyout cdr-link [primary | secondary] The busyout cdr-link command puts a specified call detail recording link in a maintenance busy state. When busied out, the link is dropped and must be re-established later when returned to service. See the description of status link for more information about links.
Page 299: Busyout Data-Module
busyout data-module busyout data-module busyout data-module extension This command puts the specified data module in a maintenance busy state, whether or not it is installed. No call processing may be executed on the data modules or over the data channels. A list of every data module administered on the system can be displayed with list data-module .
Page 300: Busyout Ds1-Facility
Maintenance Commands busyout ds1-facility busyout ds1-facility UUCSSf [override] This command puts a specified DS1 facility of a DS1C complex into a maintenance busy state. Each DS1C complex uses from 1 to 4 DS1 facilities. The packet facility carries the control channel for every facility in the complex, all packet traffic, and some circuit connections.
Page 301: Busyout Fiber-Link
[a-pnc | b-pnc] NOTE: This command is not valid for S8700 IP Connect configurations. The busyout fiber-link command puts a specified fiber link into a maintenance busy state. (See ‘‘Busyout and Release Commands’’ on page 7-13.) A fiber...
Page 302: Busyout Ipserver-Interface
Maintenance Commands busyout ipserver-interface busyout ipserver-interface Uc The busyout command forces an IPSI to be out of service. If the IPSI is not duplicated, this will cause a fallback to traditional control where the EI is the AA, and the PKTINT functionality is moved to an IPSI in another port network.
Page 303 busyout ipserver-interface Output busyout ipserver-interface 6b COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code IP-SVR PASS Command successfully completed 555-233-143 Issue 1 May 2002 7-47...
Page 304: Busyout Journal-Printer
Maintenance Commands busyout journal-printer busyout journal-printer pms-log | wakeup-log The busyout journal-printer command puts the link to the Property Management System log or wakeup log printers in a maintenance busy state. (See Busyout and Release Commands at the beginning of this chapter). When busied out, the link is dropped and no data transfer can take place over it.
Page 305: Busyout Link
busyout link busyout link busyout link link# The busyout link command puts a specified packet gateway link in a maintenance busy state. (See ‘‘Busyout and Release Commands’’ on page 7-13.) CAUTION: Busyout of a link drops all calls and packet traffic dependent on that link. The application, adjunct, or switch connected to the link will be inaccessible and the link will have to be re-established later when returned to service.
Page 306: Busyout Pms-Link
Maintenance Commands busyout pms-link This command places every maintenance object associated with a property management system link in the maintenance busy state. No periodic or scheduled maintenance is performed on the busied out maintenance objects until they are released. When the object is maintenance busy the object is deactivated (no call processing activity may include the busied object) and the link is dropped.
Page 307: Busyout Sp-Link
busyout sp-link busyout sp-link busyout sp-link The busyout sp-link command puts the system printer link into a maintenance busy state. Placing the system printer link in a busyout state prevents access to the system printer. The system printer link is a link from the switch to an external printer. This link is created by administering the system printer extension and setting up a call to the system printer.
Page 308: Busyout Trunk
Maintenance Commands busyout trunk busyout trunk group# [/member#] The busyout trunk command puts an entire trunk group or a single trunk-group member in a maintenance busy state whether it is installed or not. Entering only the group number busies out every member in the group. (Although not recommended, entering a group number and a slash (/) without a member number to busyout the member with the lowest-numbered port location.) Examples...
Page 309: Cancel Hardware-Group
cancel hardware-group cancel hardware-group cancel hardware-group In the course of executing test hardware-group , you may find it necessary to halt the test temporarily or permanently. This can be accomplished with cancel hardware-group . The canceled test hardware-group command may be restarted where it left off with resume hardware-group , or another test hardware-group test may be started.
Page 310 Maintenance Commands Output If a test hardware-group command started in the background is successfully canceled with cancel hardware-group, this response is displayed: Hardware-group command successfully canceled If a test hardware-group command executing in the foreground is successfully canceled with a cancel hardware-group command from another terminal, the following response will be displayed on the terminal where the hardware-group command was executing: Hardware-group command aborted with cancel...
Page 311: Change Atm Pnc
NOTE: This command is not valid for S8700 IP Connect configurations. This command only allows you to change the name of the ATM switch. Table 7-8. change atm pnc command parameters Action/ Feature Object...
Page 312: Change Circuit Packs
Parameters The number of the cabinet containing the circuit packs to be modified. Default is 1. For S8700 IP Connect configurations, the number applies to port slots 1-10 only. Output The following display shows a typical result when change circuit-packs is entered for Cabinet 1.
Page 313 change circuit packs change circuit-packs Page 2 of CIRCUIT PACKS Cabinet: 1 Carrier: B Cabinet Layout: five-carrier Carrier Type: port Slot Code Sf Mode Name Slot Code Sf Mode Name 11: TN2302 IP MEDIA PROCESSOR 01: TN2312 IP SERVER INTFC 02: TN570 EXPANSION INTF 13: TN754...
Page 314 Maintenance Commands change circuit-packs Page 4 of CIRCUIT PACKS Cabinet: 1 Carrier: D Cabinet Layout: five-carrier Carrier Type: not-used Slot Code Sf Mode Name Slot Code Sf Mode Name ’#’ indicates circuit pack conflict. Field Descriptions The administered number of the cabinet (1-22). Cabinet Type of cabinet.
Page 315 Output (for S8700 IP Connect) change circuit-packs 15 Page 1 of CIRCUIT PACKS Cabinet: 15 Carrier: A Cabinet Layout: rack-mount-stack Carrier Type: rmc-port Slot Code Sf Mode Name 01: TN556 BRI LINE 02: TN2312 IP SERVER INTFC...
Page 316 Maintenance Commands change circuit-packs Page 5 of CIRCUIT PACKS Cabinet: 1 Carrier: E Cabinet Layout: five-carrier Carrier Type: switch-node Slot Code Sf Mode Name Slot Code Sf Mode Name 12: TN572 SWITCH NODE CLOCK 02: TN573 SWITCH NODE INTF 03: TN573 SWITCH NODE INTF 04: TN573 SWITCH NODE INTF...
Page 317: Change Fiber-Link
NOTE: This command is not valid for S8700 IP Connect configurations. The change fiber-link command changes the translation data associated with an existing fiber link. On critical-reliability systems (duplicated PNC), each fiber link is duplicated and exists as a pair. When PNC duplication is enabled, only the fields on pages 2 and 3 (the DS1 CONV complex attributes) can be changed.
Page 318 Enter A or B. This field is used for faster remote diagnosis. Type of Transceivers Enter Avaya or other. Appears when the converter field on the Fiber Link Converter Type Administration screen is set to y. The following fields appear on page 2 when a DS1 CONV complex is administered on the fiber link.
Page 319 change fiber-link Table 7-9. DS1 Line Equalization Settings Distance to DSX-1 Interface (feet) Equalizer Setting 22 AWG ABAM and 24 AWG PDS 26 AWG PDS 1 to 133 0 to 90 133 to 266 90 to 180 266 to 399 180 to 270 399 to 533 270 to 360...
Page 320 Maintenance Commands change fiber-link 1 Page 1 of FIBER LINK ADMINISTRATION Fiber Link #: ENDPOINT-1 ENDPOINT-2 (A-PNC) (A-PNC) Board Location: 01E01 Board Location: 01E02 Board Type: Board Type: Fiber Translation: converter? Converter? Type of Tranceivers: Converter Type: Is one endpoint remoted via DS1 Converter Complex? n 7-64 Issue 1 May 2002 555-233-143...
Page 321: Change Firmware Download
change firmware download change firmware download change firmware download Use the command change firmware download to display a firmware download form on the SAT screen. Output change firmware download Page 1 of FIRMWARE DOWNLOAD Source Board Location: Firmware Image File Name: Target Board Code: Suffix: Firmware Vintage:...
Page 322 Maintenance Commands 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 names can be from 1 to 40 alphanumeric characters (that is, printable File Name characters, including blanks).
Page 323: Change Ipserver-Interface
Use this command to change the QoS parameters and change the IPSI board. This command applies to both S8700 Media Server Multi-Connect and IP Connect Configurations. Parameters port network (1-64) Examples change ipserver-interface 2...
Page 324 Maintenance Commands Output (for S8700 IP Connect) change ipserver-interface 1 Page 1 of IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 1 Socket Encryption? y Primary IPSI QoS Parameters ------------ -------------- Location: 1A02 Call Control 802.1p: 6 Host: 135.122.50.13 Call Control DiffServ: 46...
Page 325: Change Ip-Network-Region
If ip-network-region 9 is administered with connectivity with ip-network-region 11 first and then ip-network region 11 appears, the fields are automatically populated to show connectivity with ip-network-region 9. See the Avaya MultiVantage Administrator’s Guide for field definitions for this screen. Output...
Page 326 Maintenance Commands change ip-network-region 1 Page 2 of Inter Network Region Connection Management Region (Group Of 32) 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 001-032 1 2 3 033-064 065-096...
Page 327: Change Station
change station change station change station extension Output change station 67403 Page 1 of STATION Extension: 67403 Lock Messages? n BCC: 0 Type: 8410D__ Security Code: 1234____ TN: 1 Port: X______ Coverage Path 1: ____ COR: 1 Name: Vphone______________________ Coverage Path 2: ____ COS: 1 Hunt-to Station: _____ STATION OPTIONS...
Page 328: Change Synchronization
1-64 Cabinet number only applies to S8700 IP Connect configurations Output The following example shows the output for the change synchronization command for an S8700 IP Connect configuration. change synchronization 1 Page 1 of...
Page 329 Primary (Multi-Connect only) 16-character alpha-numeric characters for identification Secondary The cabinet number applies only for S8700 IP Connect Cabinet systems. Valid range is 1-64. For IP Connect, the list of circuit packs can span two pages. The maximum number of sync sources available per cabinet is 40 (equivalent to the number of available slots).
Page 330: Change System-Parameters Ipserver-Interface
Maintenance Commands change system-parameters ipserver-interface This is the change system-parameters command with the ipserver-interface parameter. This command displays the subnet address of the two servers and allows the user to administer the switch identifier and turn on/off IPSI control of port networks. NOTE: You must run this command before running add ipserver-interface.
Page 331 change system-parameters ipserver-interface Output (for Multi-Connect) change system-parameters duplication Page 1 of DUPLICATION RELATED SYSTEM PARAMETERS Enable Operation of PNC Duplication? y Enable Operation of IPSI Duplication? y 555-233-143 Issue 1 May 2002 7-75...
Page 332: Change System-Parameters Maintenance
Maintenance Commands 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. If daily scheduled maintenance must remain idle during a maintenance procedure, set the Start Time field to a time after the session ends.
Page 333 change system-parameters maintenance Scheduled Maintenance Hour and minute (24-hour notation) when daily scheduled maintenance starts. Start Time The hour and minute when scheduled daily maintenance ceases. If any daily Stop Time maintenance operations are not completed by this time, the system notes its stopped sequence location and includes those operations during the next scheduled daily maintenance.
Page 334 Maintenance Commands Output (Page 2) The following example shows the output from page 2 of the change system-parameters maintenance command. change system-parameters maintenance Page 2 of MAINTENANCE-RELATED SYSTEM PARAMETERS MINIMUM MAINTENANCE THRESHOLDS ( Before Notification ) TTRs: 4 CPTRs: 1 Call Classifier Ports: 0 MMIs: 0 VCs: 0...
Page 335 change system-parameters maintenance Minimum Maintenance Thresholds (Before Notification) When the number of touch-tone receivers (TTRs) in service falls below this TTRs number (4 to 200), a warning alarm is raised 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 336 Maintenance Commands Terminating Trunk Transmission Test (Extension) This field specifies extensions assigned to receive tie-trunk calls from other Test Type 100 switches that have test line origination capability. The system responds by sending a sequence of test tones. Test type 100 tests far-end to near-end loss and C-message by sending: 5.5 seconds of 1004-Hz tone at 0 dB Quiet until disconnect;...
Page 337 change system-parameters maintenance DS1 Maintenance The extension used to set up a DSO loop-around connection for testing non-ISDN DS1 trunks. The DSO Loop-Around Test Call feature is used Loop-Around primarily for testing DSO channels associated with non-ISDN-PRI trunks. Test Call The loop around is activated by dialing the test extension number;...
Page 338: Clear Errors
Maintenance Commands clear errors clear errors The clear errors command moves every error and resolved alarm to the cleared errors list, thereby making room for new incoming error messages which might otherwise be dropped. This command does not clear active alarms from the alarm log.
Page 339: Clear Firmware-Counters
clear firmware-counters clear firmware-counters clear firmware-counters UUCSS | a-pnc | b-pnc This command clears the firmware error counters on the specified circuit packs). This command is valid only for SNI, SNC, and DS1C and ATM-EI board locations. When a-pnc or b-pnc is specified, every such circuit pack in a single PNC can be cleared at once.
Page 340: Clear Link N
Maintenance Commands clear link n 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 a C-LAN’s Ethernet link. 7-84 Issue 1 May 2002 555-233-143...
Page 341: Disable Filesystem Board Ppcss
disable filesystem board ppcss disable filesystem board ppcss disable filesystem board ppcss This command requests the board ppcss to remove the memory file system. This command will fail if there are any files present on the file system and an error message, “filesystem still has files,”...
Page 342: Disable Firmware Download
Maintenance Commands 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. 7-86 Issue 1 May 2002 555-233-143...
Page 343: Display Alarms
display alarms display alarms This command will display an options form that allows the technician to choose which alarms to display. Synopsis display alarms [print | schedule] Permissions The following default logins may execute this command: system technician, inads, cust, rcust, bcms, init, browse. Examples display alarms display alarms print...
Page 344 Maintenance Commands Defaults Every alarm will be displayed. Parameters print This will cause the report to be printed if a printer is linked to the SAT. schedule When the “schedule” option is specified, the command is validated and then a scheduling form is displayed to allow the technician to schedule execution of the command.
Page 345 display alarms Display alarm record to the time specified by mm/dd/hh/mm, where mm is the month, dd is the day, hh is the hour and mm is the minute. If no “to” date is entered, any alarm which is active after the from date will be selected.
Page 346 Maintenance Commands Field Help Following are the help messages that the system technician will see upon tabbing to the specified field and pressing the HELP key. Active? n(o) y(es) Resolved? n(o) y(es) Major? n(o) y(es) Minor? n(o) y(es) Warning? n(o) y(es) Interval: The interval field help is a list of objects.
Page 347 display alarms Field Error Messages Following are the error messages that display on the screen. The messages display when the system technician tabs out of a field and the validation routines are executed. In the following messages, an “x” represents the character that was entered by the user.
Page 348 Maintenance Commands Output For the following example, the key was pressed immediately after entering ENTER the display alarms print command. display alarms ALARM REPORT Port Maintenance Alarm Ack? Date Date Name Brd? Name Type State 1 2 Alarmed Resolved TONE-BD MAJOR 05/22/20:34 00/00/00:00 01C07...
Page 349 display alarms RDY (ready for service), OUT (out of service), or IN (in service). This is the Service current service state of the station and trunk ports shown. If a blank is displayed State in this field it means that no service state is associated with the MO. The columns under the “1”...
Page 350: Display Atm Pnc
Maintenance Commands display atm pnc This command displays specific atm pnc data and is not valid for S8700 IP Connect configurations. Table 7-12. display atm pnc command parameters Feature Action/ Object Qualifier Qualifier Description Permissions Defaults Interactions display atm pnc...
Page 351: Display Capacity
display capacity display capacity This form describes how you have administered your system and provides a “snapshot” status of the switch resources. Table 7-13. display capacity command parameters Action/ Feature Object Qualifier Qualifier Description Permissions Defaults Interactions display print Report sent to printer init none none...
Page 352 The number of abbreviated dialing entries (for both group and personal AD Entries Per lists). System The number of abbreviated dialing personal lists. For further information, AD Personal refer to Administrator’s Guide for Avaya MultiVantage Software and Lists Per Overview for Avaya MultiVantage Software. System Continued on next page 7-96...
Page 353 display capacity Adjunct Switch Application Interface (ASAI) The number of station domain controls that ASAI adjuncts can request. Active Controlling Associations The number of requests ASAI can make to monitor call activity at a split or Notification VDN. Requests The number of calls that can be controlled by ASAI adjuncts. Simultaneous Active Adjunct Controlled...
Page 354 A real-time snapshot of the number of calls waiting for attendant service. Queue Length The number of authorization codes used for security purposes. For further Authorization information, refer to Administrator’s Guide for Avaya MultiVantage Codes Software. Basic Call Management System (BCMS)
Page 355 Administrator’s Guide for Avaya MultiVantage Software. The number of call pickup groups have been administered. For further Call Pickup information, refer to Administrator’s Guide for Avaya MultiVantage Groups Software. The maximum number of active calls at a given time. This field does not Call Records display real-time data, just the system limit and is not administrable.
Page 356 Screen 7-3. System Capacity form (page 4 of 9) Field Descriptions (Page 4) Data Parameters The number of connections between two access or data endpoints. For Administered further information, refer to Administrator’s Guide for Avaya MultiVantage Connections Software. For further information, refer to Administrator’s Guide for Avaya Alphanumeric MultiVantage Software.
Page 357 display capacity Output - page 5 Page 5 of 9 SYSTEM CAPACITY System Used Available Limit - - - - - - - - - - - - - HUNT GROUPS, SPLITS, OR SKILLS Groups/Splits/Skills: Logged-In ACD Agents: 5200 5200 Group Members Per System: 9983 10000...
Page 358 Intercom Groups Per System The number of modem pool groups. For further information, refer to Modem Pool Administrator’s Guide for Avaya MultiVantage Software. Groups Per System The number of PCOL trunk groups. For further information, refer to Personal CO Administrator’s Guide for Avaya MultiVantage Software.
Page 359 display capacity Temporary Signaling Connections (TSC) The number of allowed Temporary Signaling Connections (TSCs). Administered TSCs The number of allowed Non-Call Associated TSCs. NCA-TSC Calls Trunks The number of allowed DS1 circuit packs. DS1 Circuit Packs The number of Incoming Call Handling Table (ICHT) entries administered ICHT For ISDN for trunk groups.
Page 360 Maintenance Commands Field Descriptions (Page 7) Voice Terminals The percentage of memory being consumed by every administered button. Station Button Memory (units) The number of resources being used by regular stations, announcements, Station and music on hold. Records The number of voice terminals. Stations The number of connected voice terminals (stations with specific Stations With...
Page 361 display capacity Output - page 8 Page 8 of 9 SYSTEM CAPACITY CURRENT SYSTEM INFORMATION Software Load: G3V6r.03.0.211.0 Memory Configuration: G3rV6 Offer Category: A LAST TRANSLATION LOADED INFORMATION: Software Load: G3V4r.06.0.075.0 Memory Configuration: G3r (large) Offer Category: unknown Screen 7-7. System Capacity form (Page 8 of 9) Field Descriptions (Page 8) Current System Information The current software load on which the system is running.
Page 362 Maintenance Commands Output - page 9 Page 9 of 9 SYSTEM CAPACITY TOTAL SUBSCRIBED PORTS System Used Available Limit - - - - - - - - - - - - - Station and Trunk Ports: Radio Controllers: Wireless Terminals: SYSTEM-WIDE REGISTRATION COUNTS Currently System...
Page 363: Display Communication-Interface Links
display communication-interface links display communication-interface links This command displays translations for the links to the servers from peripheral adjuncts. This is a display-only screen. Administration of the fields is done elsewhere. Refer to the appropriate administrator’s guide. Table 7-14. display communication-interface links command parameters Feature Action/Object Qualifier...
Page 364 Maintenance Commands Field Descriptions Number of the administered link (data module form). Link Yes ( ) or no ( ) depending upon data module administration (processor Enable interface, Ethernet, and PPP). Establish connection data from the data module forms (processor interface Est.
Page 365: Display Communication-Interface Processor-Channel
display communication-interface processor-channel display communication-interface processor-channel This command displays the TCP/IP listen port to carry each processor (virtual) channel (on an Ethernet link). Table 7-15. display communication-interface processor-channel command parameters Feature Action/ Object Qualifier Qualifier Description Permission Defaults Interaction display number Example: init...
Page 366 Maintenance Commands Field Descriptions Type y to enable a processor channel. Type n (default) to disable a Enable processor channel. Identifies the switch application used over this link. The application Appl. gateway is used for conversion between ISDN and TCP/IP. Valid entries are: audix, dcs, fp-mwi, gateway, gtwy-tcp, mis, msaamwl, msaclk, msahlwc, msallwc, msamcs, qs-mwi, blank (default) Identifies which processor channel the given processor channel is serving...
Page 367 display errors display errors display errors [high-resolution] [print | schedule] The display errors command brings up an input form that allows you to select which errors will be displayed on the hardware error report. 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 368 Maintenance Commands System Reboots and the Error and Alarm Logs The Avaya Call Processing (ACP) software attempts to save the error and alarm logs to the disk when any of the following events take place: — The save translation command is executed.
Page 369 display errors Input Form This form specifies which errors display on the report. When every selection has been made, press . If no selections are made or if the schedule option is ENTER specified, every error from the last day that are associated with active alarms display (or print).
Page 370: Display Errors
Maintenance Commands Output display errors Page 1 of ERROR REPORT The following options control which errors will be displayed. ERROR TYPES Error Type: ____ Error List: active-alarms REPORT PERIOD Interval: From: __/__/__:__ To: __/__/__:__ EQUIPMENT TYPE ( Choose only one, if any, of the following ) Cabinet: Port Network: Board Number:...
Page 371 display errors Sequence Count. These numbers give the order in which the errors were Seq Cnt logged. Each sequence covers a period of one second. Sequence numbers are assigned to the first and last occurrences of a given error within the one second period given in the time stamp. There may be gaps in the sequence numbers within a given second because the last occurrence of an error may replace an existing entry and because sequence numbers are also assigned to software events not shown in the...
Page 372 Maintenance Commands The following display shows a typical result when disp errors is entered with the default input settings. display errors Page HARDWARE ERROR REPORT - ACTIVE ALARMS Port Mtce First Last Err Err Rt/ Al Ac Name Name Type Data Occur Occur...
Page 373: Display Events
display events display events display events [print] A vector event is the occurrence of something unexpected during a vector-routed call due to resource exhaustion or faulty vector programming. (For example, route-step failures are typically due to the programming of an invalid extension.) These types of failures are not due to faulty hardware or system software error and do not constitute incorrect feature operation.
Page 374 Maintenance Commands Field Descriptions Select or type “vector” or “denial” to specify the type of event report that you Category want. The fields in this section allow you to view only those vector events that Report Period occurred within a specific time period. If these are left blank, every recorded vector event is displayed.
Page 375 display events display events Page EVENTS REPORT Event Event Event Event First Last Evnt Type Description Data 1 Data 2 Occur Occur 1012 Destination Unavailable 01/09/09:44 01/09/09:54 1012 Destination Unavailable 01/09/09:45 01/09/09:45 1012 Destination Unavailable 01/09/09:46 01/09/09:47 1012 Destination Unavailable 01/09/09:47 01/09/09:51 1934 IP RRJ - Ext already reg...
Page 376 Maintenance Commands Table 7-16 lists the event type, the text that appears in the Event Description field, a further explanation of the condition, and the type of data in the Event 1 and Event 2 fields. Table 7-16. Denied IP events Event Event Event...
Page 377 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1913 IP RRJ-Invalid Registration rejected because T/S: Major ProdID/Ver invalid Product ID / Version. Product ID version Registering Application’s product of the number ID is not administered or no...
Page 378 Maintenance Commands Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1922 IP RRJ-TTI or RO Registration for an IP set with TTI IP address inactive service rejected. Possible causes: TTI is not enabled on the System Parameters Customer Options screen.
Page 379 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1928 Registration rejected: inconsistent Endpoint RRJ-StnTyp/Protocl station type and call-signaling type (3rd protocol. An IP Softphone should and 2nd be assigned as one of the nyble);...
Page 380 Maintenance Commands Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1936 IP RRJ-Invld RO Registration rejected: invalid IP address anlg stn analog station type. 1937 IP RRJ-RemOfc not Registration rejected: Remote IP address admin Office endpoint...
Page 381 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1948 IP RRJ-Complete Registration rejected: failure to IP address pend reg obtain a station user record (internal software error – corrupt translation).
Page 382 Maintenance Commands Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1957 IP GRJ-GK will not Gatekeeper request rejected: TTI state IP address host gatekeeper is unwilling to host endpoint because: no alias address has been provided TTI is in incorrect state (for...
Page 383 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1965 IP DRJ-Bld Disengage Request rejected: IP address DCF:Gatewy/MCU failure to build Disengage Request Confirm (DCF) message for a gateway or MCU (internal software error).
Page 384 Maintenance Commands Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1977 IP ARJ-No avail Admission Request rejected: no IP address B-channel B channel is available for the call. 1978 IP ARJ-Bld Admission Request rejected: IP address ACF:Gatewy/MCU...
Page 385 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1989 IP URJ-Endpt not reg Unregistration Request rejected: IP address endpoint is not registered. 1990 IP URJ-No endpoint Unregistration Request rejected: IP address no endpoint ID provided.
Page 386 Maintenance Commands Table 7-16. Denied IP events — Continued Event Event Event Type Event 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). 2003 IP URJ-PSA Unregistration Request rejected:...
Page 387 display events Table 7-16. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 2011 IP FURQ-Aged H323 Force Unregistration Request. H.323 UID IP address Unregister H.323 user that aged out. Endpoint’s time-to-live (TTL) expired without receiving a KeepAlive RRQ.
Page 388: Display Failed Ip-Network-Region
Maintenance Commands 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:...
Page 389: Display Fiber-Link
[print | schedule] NOTE: This command is not valid for S8700 IP Connect configurations. The display fiber-link command displays the translation data associated with an existing fiber link. The output for this command is the same as that for change fiber-link .
Page 390: Display Firmware Download
Maintenance Commands display firmware download Whenever the processor resets and the system is restarted, whether initiated by a technician command or by system software, information about the recovery is stored. If the reset is escalated, only the reset that successfully completes is recorded.
Page 391: Display Initcauses
When a reset 4 (reload) occurs, the error log is saved on the disk. Records of the last 16 restarts are retained in the initcauses log in chronological order. A power failure results in loss of every record in the initcauses log. Output (for S8700 Multi-Connect) display initcauses INITIALIZATION CAUSES Cause...
Page 392 Maintenance Commands Field Descriptions This gives the reason for the system reset, as follows: Cause Agent Request: The restart was requested through the Agent/GEMINI debugger interface (not available to craft login). Craft Request: The reset was initiated using reset system. Initialized: This represents a power-up, and is always the first entry in the log unless more than 15 restarts have occurred since the last power up.
Page 393 Output (for S8700 IP Connect) display initcauses INITIALIZATION CAUSES Cause Action Escalated Time Internal Request 03/09 11:58 Software Request 03/09 18:33 Internal Request 03/09 18:34 Internal Request 03/09 18:34 Internal Request 03/09 18:34 Internal Request 03/09 21:39 Initialized...
Page 394: Display Ipserver-Interface
Maintenance Commands display ipserver-interface display ipserver-interface n This command shows administration data for a port-network n to be IPSI controlled. Parameters port network 1-64, [’print’ or ’schedule’] Examples display ipserver-interface 2 Output display ipserver-interface 2 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 2 Socket Encryption? y Primary IPSI QoS Parameters...
Page 395: Display Node-Names
display node-names display node-names This command displays a list of the administered node names. Table 7-17. display node-names command parameters Feature Action/ Object Qualifier Qualifier Description Permissions Defaults Interactions display print Example: init none none node-names schedule display node-names inads craft Output The following example shows the output from the display node-names...
Page 396 Maintenance Commands Page 2 Page 2 of 6 NODE NAMES Name IP Address Name IP Address Default _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___ _______________ ___.___.___.___...
Page 397: Display System-Parameters Duplication
display system-parameters duplication display system-parameters duplication This command displays the status (enabled or disabled) of IPSI (processing element) and PNC (port network connectivity) 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 EI circuit pack as an endpoint, or a DS1-C (fiber link administration is a prerequisite;...
Page 398 Maintenance Commands Output The following example shows the output from the display system-parameters duplication command. display system-parameters duplication DUPLICATION RELATED SYSTEM PARAMETERS Enable Operation of PNC Duplication? y Enable Operation of IPSI Duplication? y Field Descriptions Status of PNC duplication: y is enabled; n (default) id disabled. Enable Operation of This field appears only if has been enabled...
Page 399: Display System-Parameters Ipserver-Interface
display system-parameters ipserver-interface display system-parameters ipserver-interface This command displays the subnet address of the two servers and allows the user to administer the switch identifier and turn on/off IPSI control of port networks. Parameters [print | schedule] Output display system-parameters ipserver-interface IP SERVER INTERFACE (IPSI) SYSTEM PARAMETERS SERVER INFORMATION IPSI Host Name Prefix:...
Page 400: Display System-Parameters Maintenance
An input form is displayed with the following fields. Defaults for data entry fields are listed in parentheses. The following display shows a typical result when display system-parameters maintenance is entered on an S8700 Multi-Connect system. 7-144 Issue 1 May 2002...
Page 401 display system-parameters maintenance display system-parameters maintenance Page 1 of MAINTENANCE-RELATED SYSTEM PARAMETERS SCHEDULED MAINTENANCE Start Time: 01 : 00 Stop Time: 06 : 00 Save Translation: daily Command Time-out (hours): 2 Control Channel Interchange: no System Clocks/IPSI Interchange: no display system-parameters maintenance Page 2 of MAINTENANCE-RELATED SYSTEM PARAMETERS...
Page 402 Maintenance Commands display system-parameters maintenance Page 3 of MAINTENANCE-RELATED SYSTEM PARAMETERS MAINTENANCE SAVE TRANSLATION CORRUPTION AUDIT Enable Translation Audit? y Display Warning When Detected? n Alarm When Detected? n Block Save Translation When Detected? n Scheduled Maintenance A series of maintenance tests and operations runs automatically every day according to the schedule and settings specified in the following fields.
Page 403 display system-parameters maintenance When the number of touch-tone receivers (TTRs) in service falls below this Minimum number (4 to 200), a WARNING alarm is raised against TTR-LEV. These Threshold for are also known as dual-tone multifrequency receivers (DTMRs). There are TTRs 4 TTRs on each TN748, TN718, TN420, or TN756;...
Page 404 Maintenance Commands This field contains the extension number for the test call extension number. This test extension number will be used to establish a loop-around Loop-Around connection on the selected trunk. Test Call Extension The DSO Loop-Around Test Call feature is used primarily for testing DSO channels associated with non-ISDN-PRI trunks.
Page 405: Display Test-Schedule
display test-schedule display test-schedule Automatic Transmission Measurement System (ATMS) provides advanced maintenance procedures for monitoring system trunk facilities. This system performs transmission tests on system trunks to determine whether trunks are performing satisfactorily. These tests can be initiated in two ways: demand user enters command at the System Administration Terminal (SAT) to initiate a test immediately...
Page 406 Maintenance Commands The length of this schedule in weeks. If this field is 0 (default), the schedule Interval runs on the specified days only once. The number of trunk members (1 – 4) tested concurrently during a OTL Throttle schedule. If this field is set to 1, the OTL (originating test line) tests each trunk sequentially.
Page 407: Display Time
display time display time display time [print | schedule] This command displays the system date and time that is used by software processes for scheduling and so on. Output display time DATE AND TIME DATE Day of the Week: Sunday Month: January Day of the Month: 1 Year: 2002...
Page 408: Enable Administered-Connection
Maintenance Commands enable administered-connection enable administered-connection [adm-conn# | all This command re-enables scheduled and periodic testing and in-line error processing on a specified AC (administered connection) or every AC. It is used after previously disabling maintenance via the disable administered-connection command.
Page 409: Enable Filesystem Board
enable filesystem board enable filesystem board enable filesystem board ppcss size [actual-size] login [ID] This command requests the board ppcss to create a file system of actual-size KB. If the optional size parameter is not given, the maximum available is used. If more than 32K is not available an error message is given.
Page 410: Enable Synchronization-Switch
Maintenance Commands enable synchronization-switch enable synchronization-switch This command returns control of the selection of synchronization source to the maintenance subsystem and Tone-Clock after being previously turned off by the disable synch command. See ‘‘SYNC (Port-Network Synchronization)’’ on page 8-1509 for details. 7-154 Issue 1 May 2002 555-233-143...
Page 411: Enable Test-Number
enable test-number enable test-number enable test-number test# Examples enable test-number 102 This command will re-enable a specified test that was previously turned off with the disable test command. (The disable test command is not available to the craft login.) While disabled a test cannot be run by background or demand maintenance.
Page 412: Get Boot-Image
Maintenance Commands get boot-image Use this command to view the two firmware image parameters on the TN2501AP circuit pack. Table 7-19. display firmware-image command parameters Feature Action/Object Qualifier Qualifier Description Permissions Defaults Interactions get boot- location The physical location of the init image circuit pack (UUCSS).
Page 413 get boot-image Cyclic Redundancy Check (data integrity algorithm) CRC Checksum Yes in this field indicates the active firmware image file. Active Image No in this field indicates the inactive firmware image file. To change the active image file, use the set boot-image command.
Page 414: Get Ethernet Options
Maintenance Commands get ethernet options Use this command to generate a report about a specific Ethernet connection. Table 7-20. set ethernet-options command parameters Feature Action/Object Qualifier Qualifier Description Permissions Defaults Interactions location The physical location of init ethernet- the circuit pack (UUCSS) inads options craft...
Page 415: Go Shell
go shell go shell This command provides SAT access to the Linux bash shell. 1. Log into the web application interface. 2. Type go shell at the command prompt. 3. Enter your terminal type and press ENTER 4. At the prompt you can run platform commands through Linux. Output Here is a sample screen.
Page 416: List Atm Pnc
Maintenance Commands list atm pnc This command lists the administered atm-pnc equipment in the system. Table 7-21. list atm pnc command parameters Feature Action/ Object Qualifier Qualifier Description Permissions Defaults Interactions list atm pnc print init none none inads schedule craft Output The following example shows the output for the list atm pnc command.
Page 417: List Cabinet
Output The following display shows a typical result when list cabinet is entered. For S8700 IP Connect configurations, the field option rack-mount-stack (rmc) is added to the Cabinet Layout field. list cabinet...
Page 418: List Configuration
Maintenance Commands list configuration list configuration hardware-group [print | schedule] NOTE: The list configuration software-version command is discussed separately under its own heading. A hardware configuration report lists, for each circuit pack in a specified group, the type, code, suffix, and vintage of the requested circuit packs as installed in the switch, and every assigned port on the circuit packs.
Page 419 list configuration Output Assigned Ports: Board Number —The functional name of the circuit pack Code —The TN or UN code and suffix of the circuit packs are displayed. NOTE: The letter P (programmable) is added to the suffix of every R10 downloadable board in the following forms: list configuration status firmware download...
Page 420 Maintenance Commands Assigned Ports Each port on the circuit pack is represented by a position corresponding to its circuit number in ascending order from left to right. The assigned ports are not displayed for list configuration ds1 . Two rows are required for circuit packs with more then 8 ports.
Page 421 list configuration Field Descriptions The functional name of the circuit pack Board Number The TN or UN code and suffix of the circuit packs Code The vintage number of the circuit pack, or the hardware (HW) and firmware Vintage (FW) vintages of the TN802B IP interface board. The circuit pack is administered but not physically installed no board The circuit pack administered to the slot differs from the circuit pack that is...
Page 422: List Configuration Software-Version
Maintenance Commands list configuration software-version list configuration software-version [memory-resident] [print | schedule] This command displays Software version numbers and compatibility indexes of the software load modules stored in system memory (RAM) and on the Mass Storage System devices. The dates and times when translation and announcement data were last saved to the MSS.
Page 423 list configuration software-version Field Descriptions Software Version Section This section displays information related to the current software-load module stored in memory and in the MSS. Version number of the RAM-resident load module. Memory Resident The last date and time that translation data was saved to Disk Resident disk.
Page 424: List Directory
Maintenance Commands list directory list directory board ppcss This command lists every file in the path directory of the ppcss board memory filesystem. NOTE: In this release, the forward slash (/) is the default path for listing files in the root directory.
Page 425: List Disabled-Mos
list disabled-MOs list disabled-MOs list disabled-MOs [print | schedule] This command displays a list of the maintenance objects that have been disabled with the disable MO , disable all , or disable MO-all command (not available to craft logins), as well as whether or not the command has been run. Use display disabled-tests for numbers of tests that have been disabled.
Page 426: List Fiber-Link
[print | schedule] NOTE: This command is not valid for S8700 IP Connect configurations. This command displays a list of every fiber link in the system. The list is a summary of data entered on the fiber link form ( add, display, change , or remove fiber-link ).
Page 427: List History
list history list history This command generates a log listing of the most recently completed “data affecting” administration and maintenance commands. This includes the history of ACTR moves, which can be used to track moves and, thus, help reduce fraud. Data commands are those administration and maintenance commands that change the data state associated with any object and qualifier in the system.
Page 428 Maintenance Commands When a user requests a recent change history report, there could be other users concurrently issuing data commands and altering the contents of the transaction log. Therefore, if the user pages the entire way through the report, the oldest entries in the transaction log (maximum 250 commands) may have been overwritten by data commands issued by these other users.
Page 429 list history Field Descriptions The date the command was issued (mm/dd). Date The time the command was issued (hh:mm). Time The port field indicates the port type to which the user was connected when Port the command was issued. If the “CTA/PSA/TTI Transactions in History Log” field is enabled on the Feature-Related System Parameters screen, TTI, PSA, CTA and ACTR moves are recorded.
Page 430: List Ip-Route
Maintenance Commands list ip-route This command displays a list of the IP routes from DEFINITY ECS out to the LAN. You may enter the “board” parameter and specify which C-LAN circuit pack for which to show the IP routes (for example, list ip-route board UUCss ). Table 7-23.
Page 431 list ip-route Field Descriptions IP-route number Route Number Destination of the route. The destination is a name administered on the Destination Node Name form that can include the keyword indicating the Default Node default route. The node name of the Gateway through which the destination is to be Gateway reached.
Page 432: List Ipserver-Interface
Maintenance Commands list ipserver-interface This command lists out all administered IPSIs in the system. This command applies to both S8700 Media Server Multi-Connect and IP Connect Configurations. Parameters schedule Output (for S8700 IP Connect) list ipserver-interface IP SERVER INTERFACE INFORMATION...
Page 433 Output (for S8700 Multi-Connect) list ipserver-interface Page SERVER INTERFACE INFORMATION Port Pri/ Primary/ Primary/ Primary/ State Ntwk Sec Secondary Secondary Secondary Serv Control Of Bd Loc IP Address Host Name DHCP ID State State Health ---- ------ ---------------...
Page 434: List Isdn-Testcall
Maintenance Commands list isdn-testcall list isdn-testcall [print | schedule] The list isdn-testcall command displays the ISDN-PRI trunks that are currently in use for outgoing ISDN test calls. Output The following display shows a typical result when list isdn-testcall is entered. list isdn-testcall ISDN-PRI TESTCALLS B-Channel...
Page 435: List Marked-Ports
list marked-ports list marked-ports list marked-ports [print | schedule] The list marked-ports command displays every port that has been marked unusable with the mark port command. Output list marked-ports MARKED-PORT INFORMATION Port Board-Type 1C0101 DIG-BD 1C0102 DIG-BD Command successfully completed Field Descriptions The physical location (cabinet-carrier-slot-port circuit) of the marked port.
Page 436: List Measurements Clan Ethernet
“N/A” (not available), the delta equals the total. The primary use of this command is to quickly and unambiguously determine whether the fault lies within the Avaya-provided equipment or with the LAN or LAN administration to which the system is connected.
Page 437 list measurements clan ethernet Table 7-24. list measurements clan ethernet command parameters Feature Action/Object Qualifier Qualifier Description Permissions Defaults Interactions list clan Designates ethernet init measurements ethernet connection inads craft UUCss Cabinet-carrier-slot customer address of the C-LAN circuit pack print Report sent to printer schedule Command is validated...
Page 438 Maintenance Commands Output The following example shows the output from the list measurements ethernet command. 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 439: List Measurements Clan Ppp
list measurements clan ppp 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 440 Maintenance Commands Output The following example shows the output from the list measurements clan ppp command. 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 441: List Measurements Clan Sockets
list measurements clan sockets list measurements clan sockets list measurements clan sockets qualifier List measurements clan sockets works on IP Media Processor and Medpro. Table 7-26. list measurements clan sockets command parameters. Feature Action/ Object Qualifier Qualifier Description Permissions Defaults Interactions list hourly...
Page 442 Maintenance Commands Output The following example shows page 1 of a List Measurements C-LAN Sockets hourly report. list measurements clan sockets hourly 01B12 Page Switch Name: Date: 5:27 pm WED MAR 26, 2002 CLAN SOCKETS HOURLY REPORT (Last 24 Hours) Socket Socket Meas...
Page 443 list measurements clan sockets The following example shows page 1 of a Measurements C-LAN Sockets summary yesterday-peak report. list measurements clan sockets summary yesterday-peak Page Switch Name: Date: 5:27 pm WED MAR 26, 2002 CLAN SOCKETS PEAK REPORT Peak Hour: 0400 Socket Socket...
Page 444: List Measurements Ds1
Maintenance Commands list measurements ds1 list measurements ds1 UUCSS [print | schedule] list measurements ds1-log UUCSS [print | schedule] list measurements ds1-facility UUCSSf [log | summary] [print | schedule] The list measurements ds1 and l ist measurements ds1-log commands provide performance measurements on a DS1 link.
Page 445 list measurements ds1 list measurements ds1 2a19 Switch Name: Date: 1:25 pm THU APR 16, 2002 DS-1 Link Performance Measurements Summary Report Counted Since: 1:20 pm THU APR 16, 2002 Number of Seconds Elapsed Into Current 15-min Interval: Total of Valid 15-min Intervals in Past 24-hr Period: Total of Current Worst 15-Min Interval...
Page 446 Maintenance Commands list measurements ds1-log 2a19 Switch Name: Date: 1:26 pm THU APR 16, 2002 DS-1 Link Performance Measurements Detailed Log Report Counted Since: 1:20 pm THU APR 16, 2002 ERRORED BURSTY SEVERELY FAILED VALID DATE TIME SECOND ERR SECS ERR SECS SECONDS INTERVAL 4/16...
Page 447 list measurements ds1 Field Descriptions The following field descriptions pertain to the summary reports accessed by list measurements ds1 and list measurements ds1-facility summary . The start time and date when the associated measurement counters Counted Since: were cleared, or when the DS1C circuit pack or facility was administered. The number of seconds from the beginning of the current 15-minute Number of interval.
Page 448 Maintenance Commands The following field descriptions pertain to the detailed reports accessed by the list measurements ds1-log and list measurements ds1-facility log commands. The start time and date when the associated measurement counters were cleared Counted or the DS1C circuit pack was administered. Since: The date of the 15-minute interval.
Page 449: List Measurements Ip Codec
list measurements ip codec list measurements ip codec list measurements ip codec qualifier Supports IP media processing resource measurements. The list measurements ip codec command works on IP Media Processor and Medpro. Table 7-27. list measurements ip codec command parameters Feature Action/ Object Qualifier...
Page 450 Maintenance Commands These measurements are displayed by software; the report output may span multiple IP Media Processor or Medpro boards. A single report output combines statistics from both IP Media Processor and Medpro boards. Codecs are considered as part of a common pool. Output The following example shows the IP Codec Hourly Output For Region 4.
Page 451 list measurements ip codec Usage in Erlangs of G.711 codecs during the measurement interval. G.711 Usage Includes time that the voice channels are on a call. Usage shall be (ERL) measured from the time the voice channel is allocated until it is released. Calculated by: (Total Call Seconds) / 3600 where Total Call Seconds is a sum of the following:...
Page 452 Maintenance Commands The following example shows the Measurements IP CODEC yesterday-peak – Page 1. list measurements ip codec summary yesterday-peak Page Switch Name: Date: 5:27 pm WED MAR 26, 2002 IP CODEC RESOURCE SUMMARY REPORT G711 G723/9 --------------------- ------------------------- Meas Usage In Reg Out of...
Page 453: List Measurements Ip Dsp-Resource
list measurements ip dsp-resource list measurements ip dsp-resource list measurements ip dsp-resource qualifier Supports IP media processing resource measurements. The list measurements ip codec command works on IP Media Processor and Medpro. Table 7-28. list measurements ip dsp-resource command parameters Feature Action/ Object Qualifier...
Page 454 Maintenance Commands These measurements are displayed by software; the report output may span multiple IP Media Processor or Medpro boards. A single report output combines statistics from both IP Media Processor and Medpro boards. Codecs are considered as part of a common pool. Output The following example shows the dsp-resource Hourly Output For Region 4.
Page 455 list measurements ip dsp-resource Usage in Erlangs of every codec during the measurement interval. DSP Usage (ERL) Includes time that the voice channels are on a call. Usage shall be measured from the time the voice channel is allocated until it is released. Calculated by: (Total Call Seconds) / 3600 where Total Call Seconds is a sum of the following:...
Page 456 Maintenance Commands The following example shows the Measurements ip dsp-resource Summary – Page 1. list measurements ip dsp-resource summary yesterday-peak Page Switch Name: Date: 5:27 pm WED MAR 26, 2002 IP DSP RESOURCE SUMMARY REPORT Meas DSP Usage In Reg Out of Denied % Out...
Page 457: List Measurements Ip-Signaling-Group
list measurements ip-signaling-group list measurements ip-signaling-group list measurements ip-signaling-group qualifer 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 458 Maintenance Commands Output The following example shows the list measurements ip-signaling-group current-hour command. list measurements ip-signaling-group current-hour Page 1 of 1 Switch Name: Date: 6:28 pm THU FEB 4, 1997 IP SIGNALING GROUPS LATENCY AND LOSS REPORT CURRENT HOUR 10 WORST PERFORMING IP SIGNALING GROUPS RANK ORDERED WORST TO LEAST WORST Hour Hour...
Page 459 list measurements ip-signaling-group The following example shows the list measurements ip-signaling-group today command. (The yesterday form has exactly the same layout and content type as the today form but the information applies to the previous day’s 24 hours.) list measurements ip-signaling-group today Page 1 of 24 Switch Name: Date: 6:28 pm THU FEB 4, 1997...
Page 460: List Pms-Down
Maintenance Commands list pms-down list pms-down [start-time] [stop-time] [print] This command lists every event that has meaning to the Property Management System (PMS) that have occurred while the link between the switch and the PMS was down. For example, any room status codes entered by hotel housekeeping staff during a time of PMS outage would be shown in this report.
Page 461: List Registered-Ip-Stations
list registered-ip-stations list registered-ip-stations This command displays information about the ip stations registered at a customer’s facility. Table 7-30. list registered-ip-stations command parameters Feature Action/Object Qualifier Qualifier Description Permissions Defaults Interactions list none Example: init none none registered-ip- list registered-ip-stations inads stations craft...
Page 462: List Skill-Status
Maintenance Commands list skill-status This command displays administration and status data about skilled hunt groups. The list skill-status command supports the standard “start” and “count” command-line options. Table 7-31. list skill-status command parameters Feature Action/Object Qualifier Qualifier Description Permissions Defaults Interactions list xx is a hunt group number...
Page 463 Output (for S8700 IP Connect) list skill-status Page 1 of 5 SKILL STATUS S C O D D D Extension/ Grp Grp L S C T P Q Service Level 1 Level 2 No. Name Type S O W A A P SO...
Page 464 3 38000 ucd-mia n Skilled agent hunt group #6 60000 ead-loa n Skilled agent hunt group #7 60007 ead-loa n Command successfully completed Field descriptions are the same as for the S8700 IP Connect. 7-208 Issue 1 May 2002 555-233-143...
Page 465: List Station
list station list station 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 –...
Page 466: List Sys-Link
Maintenance Commands list sys-link list sys-link [print | schedule] The list sys-link displays every system link. Each link’s location, type and channel number, state, current path status, faulted path status, and last recorded fault (if any) are displayed. See SYS-LINK in Chapter 8, ‘‘Maintenance-Object Repair Procedures’’...
Page 467 list sys-link The output below for the last screen of this command shows bearer fault detection links (BFDLs). These links exist only for port networks with IPSIs. SYSTEM LINKS INFORMATION Location Link Type/ State Current Faulted Last Fault Channel Path Path Recorded 01A0101...
Page 468: List Trace
ATM-specific data. Screen 7-12 shows VPI.VCI data for a successful 2-party call setup for an S8700 Multi-Connect configuration. Use the field descriptions to interpret this report. (The S8700 IP Connect does not support ATM -specific trace data.)
Page 469 Screen 7-12. List trace screen (list trace station) list trace tac Use this command to see the VPI.VCI data for a specified trunk. For S8700 Multi- Connect, the command syntax for ATM-specific trace data is list trace tac xxx/a , where xxx is the trunk access code number.
Page 470: Mark Port
Maintenance Commands mark port mark port UUCSSpp The mark port command will identify a port as unusable by normal call processing. The port will be able to be tested, etc. but calls will not be attempted through the port. The marking of a port is saved as part of translation. The port can be restored to service by using the clear port command.
Page 471: Monitor Bcms
monitor bcms monitor bcms monitor bcms split split# | system system# | skill skill# The monitor bcms command displays output for agents and splits summarizing the Basic Call Management System (BCMS) condition. This on-line status report is automatically updated every 30 seconds or on demand by pressing UPDATE The command is canceled by pressing which results in termination of the...
Page 472 Maintenance Commands Field Descriptions The current date and time which is updated every 30 seconds or when the Date UPDATE key is pressed. The name of the split being reported, if no name is administered then the SPLIT split extension is displayed in the form “EXTxxxxx”. Splits are displayed in split number order.
Page 473 monitor bcms Output for monitor bcms split The following display shows a typical result when mon bcms spl 1 is entered. monitor bcms split 1 Page 1 of BCMS SPLIT (AGENT) STATUS Split: Split Name: hunt group 1 Date: 9:02 TUE OCT 22 1991 Calls Waiting: Oldest Call: 0:00...
Page 474 Maintenance Commands The number of agents in this split currently in After Call Work (ACW) split. This field is real-time status data. 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 will not be recorded here.
Page 475: Monitor Health
. When the command is canceled, the Cancel management terminal login is dropped. See ‘‘status health’’ for a description of the fields displayed. Output (for S8700 IP Connect) ‘‘status health’’ for field descriptions. Monitor health Page 1 of OCC: St: 11%...
Page 476 Maintenance Commands Output (for S8700 Multi-Connect) monitor health Pwr: Simplexnc:primary Logins:4 BUSYOUT:Trk: Stn: 1 Oth: comm primary Cab EmTr Maj Min Wrn PNC Cab EmTr Maj Min Wrn PNC n.a. 1| 25 up n.a. 1| 25 up n.a. 4 up/up n.a.
Page 477: Monitor Security Violations
monitor security violations monitor security violations monitor security-violations [print] The monitor security-violations command displays the following information about failed attempts to access the system: the time of the violation, the login entered, and the port accessed during the failed login attempt. For remote access violations, the trunk-group number, member number, and extension are also shown.
Page 478: Monitor System
Maintenance Commands monitor system This command with the view1 or view2 option displays one screen page of output summarizing the overall condition of the system. With the connection option, the command displays the real-time status for time slots and buses. Additionally, there are other miscellaneous parameters displayed that show call rates, intervals, etc.
Page 479 monitor system These forms contain simplified high-level information from which a basic picture of the system’s health can be drawn. The monitor system conn command displays output that shows the status of connections in the connection manager process. Data is collected frequently in the connection manager for certain key information items.
Page 480 Maintenance Commands If every available maintenance resource is currently in use, then the following message will be displayed: All maintenance resources busy; try again later Output for monitor system view1 and view2 For the following output example, the command monitor system view1 was entered.
Page 481 monitor system monitor system view2 ATTENDANT STATUS MAINTENANCE STATUS Console no. # of alarms for trunks: Activated: 1 2 3 4 5 6 # of alarms for stations: # of alarms for other res: Deactivated: First OSS number has been informed? n TRAFFIC STATUS Measurement Hour: 1800...
Page 482 Maintenance Commands Group direction: incoming, outgoing, or two way. Grp dir Total calls that arrived and were placed in the queue for trunk groups. Calls qued Total calls that were abandoned by the caller. Calls aban The ratio of outgoing calls that are not carried (due to overload conditions) on a %Out blkg: trunk group to the outgoing calls offered.
Page 483 monitor system Output for monitor system conn The following display was produced by entering monitor system conn . 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...
Page 484 Maintenance Commands This field will contain a value of 0 or 1 depending upon if the measurements Next_hour being taken are for this hour or the next. It is related to the previous field in that the maximum call rate is reflected for this hour. When this flag is set, then statistics begin to accumulate for the next hour and shortly thereafter, the maximum call rate will become zero and accumulations will begin anew.
Page 485 monitor system The total number of call progress tone receivers requested is reflected in Requests-TN748 this field. It is a running count of currently active requests. It is CPTRs decremented when a call progress tone receiver is freed and incremented when they are requested.
Page 486: Monitor Traffic
Maintenance Commands monitor traffic monitor traffic trunk-groups [starting-group#] monitor traffic hunt-groups The monitor traffic command shows the current load on specified trunk and hunt groups and the length of time that the oldest call in the group has been waiting. Parameters trunk-groups The trunk group report displays the number of calls in the queue waiting to be...
Page 487 monitor traffic The following display shows a typical result when mon tr tr is entered. monitor traffic trunk-groups TRUNK GROUP STATUS 22:49 G3-MT DEC 31, 2002 15 10 0 22 21 10 10 31 12 20 0 65 5 10 8 99 12 0 Group;...
Page 488: Monitor Trunk
Maintenance Commands monitor trunk monitor trunk group# / member# This command displays the same information as the ‘‘status trunk’’ command and updates the data automatically every minute or on demand. To manually update the display, press on most terminals). Press to cancel the UPDATE CANCEL...
Page 489: Netstat Arp
netstat arp netstat arp Use this command to: Display the contents of the C-LAN circuit pack’s Address Resolution Protocol (ARP) table Help troubleshoot, isolate, and correct duplicate IP addresses within the network Table 7-34. netstat arp command parameters Feature Action/Object Qualifier Qualifier Description Permissions...
Page 490 Maintenance Commands Output netstat arp unsorted netstat arp unsorted Page 1 of 3 Net to Media Table C-LAN IP Address Phys Addr Type 11B15 135.247.062.254 02:e0:3b:db:c8:0a 11B14 192.011.131.254 00:30:6d:19:5c:0f 11B13 135.009.191.254 00:60:2f:a9:45:05 11B12 135.009.004.092 08:00:20:81:cc:b8 11B11 135.009.160.247 00:00:81:5a:27:05 11B10 135.009.160.223 08:00:20:1d:a7:0a 12B15 135.009.160.220...
Page 491 netstat arp netstat arp ip-sort netstat arp unsorted Page 1 of 3 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...
Page 492 Maintenance Commands The entries shown in bold type 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: Netstat Ip-Route
netstat ip-route netstat ip-route This command displays the routing tables that are resident in the C-LAN circuit pack. With the “board” option, the command netstat ip-route board UUCss displays the routing tables that are resident on the specified C-LAN circuit pack. Table 7-35.
Page 494: Ping
Maintenance Commands 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 495 ping 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 ping node-name This command pings an administered node.
Page 496 Maintenance Commands 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 497 ping Error messages The system returns error messages listed in Table 7-37. Table 7-37. 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 498: Recycle Carrier
UUC NOTE: This command is not valid for S8700 IP Connect configurations. The recycle carrier command turns power off, then back on, on a specific carrier. When a power unit is replaced in a carrier, this command must be entered to restart the power on that carrier.
Page 499: Refresh Ip-Route
refresh ip-route refresh ip-route Occasionally the tables used to route IP messages become corrupted and/or contain stale routes, delaying packet delivery. This command removes every dynamic (learned) route from the TN799 (C-LAN) circuit pack’s route tables and replaces any of the stale (administered) routes that have become corrupted. NOTE: This command is call-preserving.
Page 500 Maintenance Commands Field Descriptions The physical location of the circuit pack in CCcss format C-LAN Board (cabinet, carrier, slot) Location The number of routes that were deleted from the TN799 Routes Deleted (C-LAN) route tables The number of routes that were added from the TN799 Routes Added (C-LAN) route tables 7-244...
Page 501: Refresh Route-Table
refresh route-table refresh route-table Occasionally the tables used to route IP messages become corrupted and/or contain stale routes, delaying packet delivery. This command removes every dynamic (learned) route from the TN799 (C-LAN) circuit pack’s route tables and replaces any of the stale (administered) routes that have become corrupted. Table 7-39.
Page 502 Maintenance Commands refresh route-table all Page 1 of C-LAN Board Location Number of Routes Removed Number of Routes Added 01B11 01B12 01B13 01C05 01C06 01C07 01C08 01C09 01C10 01C11 Refresh Route Table Is Completed Screen 7-18. Refresh route-table all Use the information in Field Descriptions (refresh route-table) to interpret this report.
Page 503: Release Commands
release commands release commands release board UUCSS release maintenance-name [address] Release commands release specified maintenance objects from the maintenance busyout state and puts them back into service, assuming the health of the component(s) permits. Hardware tests specific to the maintenance object are performed to verify that it is functioning.
Page 504 Maintenance Commands Output The identity of the maintenance object and the result of command execution is displayed on a screen form similar to the related busyout screen. When the command aborts or fails, an error code indicating the reason is displayed. See Common Abort and Fail Codes at the beginning of this chapter.
Page 505: Release Ipserver-Interface
release ipserver-interface release ipserver-interface release ipserver-interface Uc This command puts the IPSI back into service after it has been busied out. See ‘‘busyout ipserver-interface’’. Parameters cabinet (1-44) Specify the cabinet number with the IPSI board you want to test. carrier Supply the carrier you want to test.
Page 506: Remove File
Maintenance Commands 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 507: Remove Ipserver-Interface
This command removes a port network from IPSI control. NOTE: You may need to busy out the IPSI before you can remove it. This command is valid for both S8700 Media Server Multi-Connect and IP Connect Configurations. Parameters n port network 1-64...
Page 508 Maintenance Commands Output (for S8700 Multi-Connect) remove ipserver-interface 5 Page 1 of IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 5 Primary IPSI QoS Parameters ------------ -------------- Location: 5AXX Call Control 802.1p: 6 Host: ipsi-A05a Call Control DiffServ: 46 DHCP ID: ipsi-A05a...
Page 509 3A02 Call Control 802.1p: 6 Host: 135.122.50.140 Call Control DiffServ: 46 DHCP ID: ipsi-A03a Field Descriptions Turn encryption on the S8700 media server and IPSI Socket Encryption? link. (y or n) Primary IPSI Location of the IPSI board Location Name of the host machine...
Page 510: Reset Board
Maintenance Commands reset board reset board UUCSS [repeat#] CAUTION: This command can be service disrupting and may cause extraneous alarms. Effects of a reset vary depending upon the type of object being reset and upon whether the component is duplicated. Consult the section in Chapter 8, ‘‘Maintenance-Object Repair Procedures’’...
Page 511: Reset Fiber-Link
[a-pnc | b-pnc] NOTE: This command is not valid for S8700 IP Connect configurations. CAUTION: The reset fiber-link command is destructive on a high-reliability system (unduplicated PNC), and may cause an entire port network to be removed from service.
Page 512: Reset Pnc Interchange
Maintenance Commands reset pnc interchange reset pnc interchange [override-and-lock] NOTE: This command does not work like other reset commands. Instead of resetting or initializing hardware, a PNC interchange is executed. Before entering this command, look at the states of health of the two PNCs with status pnc .
Page 513 reset pnc interchange Parameters interchange ”interchange” (without a preceding hyphen) must be specified on the command line. override-and-lock This option is also used to override the anti-thrashing mechanism. Subsequent PNC interchanges are prevented, regardless of changes in the states health of the PNCs. Double call setup still takes place; each call is set up on both PNCs.
Page 514 Maintenance Commands Both demand and spontaneous PNC interchanges are prevented by the following conditions: The standby PNC is busied out. The PNCs are locked by means of the set pnc lock or reset PNC override-and-lock commands. For five minutes after a spontaneous PNC interchange, or for 30 seconds after a demand interchange, an anti-thrashing mechanism prevents subsequent interchanges unless the override-and-lock option is used.
Page 515 reset pnc interchange Output One of the following messages is displayed: Command successfully completed If the reset pnc interchange command is unsuccessful due to the standby PNC’s state of health (operation of anti-thrashing), the following message will be displayed: Interchange of pnc failed; try again using the ’override-and-lock’...
Page 516: Reset Ipserver-Interface
Maintenance Commands reset ipserver-interface reset ipserver-interface Uc This command performs a board reset for an IPSI in the named cabinet/carrier. This is equivalent to reset board Ucss . NOTE: The IPSI must be busied out before a reset is allowed. If you attempt to send the reset ipserver-interface command without busying out the IPSI, an error message reminds you.
Page 517: Reset Login-Id N
reset login-ID n reset login-ID n This command displays is used to terminate a SAT session on a TCP/IP link, or other traditional connection. In the command, n represents the SAT session ID that can be obtained from the status logins command that is used to display all active SAT sessions.
Page 518: Reset Maintenance
Specifying cabinets 1 through 44 resets the EPN’s Maintenance circuit pack in the ‘a’ carrier of the specified cabinet, dropping any local login to that circuit pack. Output The following screen shows results from reset maintenance on an S8700 Multi-Connect system. reset maintenance...
Page 519: Reset Packet-Interface
Taking an IPSI out of service also takes the PKTINT out of service. Attempts to reset the PKTINT on a busied-out IPSI are ignored since the “release ipserver-interface command will reset the PKTINT. Parameters cabinet (1-64) carrier Output (for S8700 Multi-Connect) reset packet-interface 2a TEST RESULTS Port Maintenance Name Alt. Name Test No. Result...
Page 520: Reset Port-Network
PNC. The command will not execute on the PN whose fiber link to the PN or CSS is down. For S8700 Multi-Connect, this command is modified so that the port network number is 1 - 64.
Page 521 reset port-network Output For more information, see ‘‘Common Output Fields’’ ‘‘Common Abort and Fail Codes’’ at the beginning of this chapter. The following display shows a typical result when reset port-network 4 lev 1 is entered. reset port-network 4 level 1 TEST RESULTS Port Maintenance Name...
Page 522: Reset System
Unless you are experienced with resetting a system, follow normal escalation procedures. This command causes the Avaya Call Processing (ACP) application to be reloaded. All system resets (except reset system interchange) are disruptive and terminate the G3-MT login.
Page 523: Reset Val
reset val reset val This command performs the functions of the reset board command but overrides querying the board to determine whether an announcement autosave is in process. This allows resetting the circuit pack if it is in the insane state. The following screen shows a reset VAL report.
Page 524: Resume Hardware-Group
Maintenance Commands resume hardware-group resume hardware-group In the course of execution of a test hardware-group command, it may be desirable to halt the test temporarily or permanently. This is accomplished by either the cancel hardware-group command for a background test, or by pressing for a foreground test.
Page 525: Save Translation
save translation save translation save translation This command backs up translations of the database to the server. It either completes or fails. NOTE: The save command can take up to 5 minutes to complete. Avoid pressing key on the keyboard during this time, since doing so will cause ENTER the result messages to be lost.
Page 526: Set Boot-Image
Maintenance Commands set boot-image Use this command to direct the system to use 1 of 2 possible firmware image files on the TN2501AP circuit pack. Table 7-42. set boot-image command parameters Default Feature Action/Object Qualifier Qualifier Description Permissions Interactions set boot- board The physical location of the init...
Page 527: 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. Table 7-43. set ethernet-options command parameters Feature Action/Object Qualifier Qualifier Description...
Page 528 Maintenance Commands Field Descriptions Auto Negotiation means that the system automatically negotiates the highest possible network speed. means that you must manually assign the Speed and Duplex fields. NOTE: If you set the Auto Negotiation field to n, the Speed fields do not display.
Page 529: Set Ipserver-Interface
Uc NOTE: This command is not valid for S8700 IP Connect configurations. This command sets an IPSI to be active for a given cabinet carrier. Parameters cabinet (1-44) Specify the cabinet number with the IPSI board you want to test.
Page 530: Set Options
Maintenance Commands set options This command allows the user to administer whether certain alarms are reported to INADS or whether they are downgraded to a minor alarm, warning alarm, or no alarm. Synopsis set options Permissions The following default logins may execute this command: inads, init . Examples set options Description...
Page 531 set options Error Messages If the command entered is in conflict with another currently executing command, then a message is displayed showing the login id of the conflicting user and the conflicting command. The message is as follows: ’login id’:’command’ has a command conflict If during the execution of a command a resource problem occurs that requires the user to restart the command, then the following message is displayed: Command resources busy;...
Page 532 Maintenance Commands set options Page 2 of ALARM REPORTING OPTIONS Major Minor Off-board Firmware Download Alarms: Off-board Signaling Group Alarms: On the first page of the Alarm Reporting Options Form, the user selects the alarm severity options for station alarms, the four trunk alarm severity groups, the adjunct alarms, off-board DS1 alarms, and other off-board alarms.
Page 533 set options Alarms are raised in the normal manner. There is no filtering of alarm data. Alarms raised on a trunk, station, or adjunct in this category are dropped. Error information is provided as before, but there is no trace of an alarm. There is no LED activity and no call to INADS.
Page 534 Maintenance Commands In every case, if the option associated with the alarm type is set to “n,” the alarm report is dropped. All error information about the alarm is intact, but there is no record of an alarm and no LEDs light on the port circuit pack, the Maintenance circuit pack, the attendant console, or alarm reporting station to indicate a problem.
Page 535 NOTE: Although alarms on these MOs may 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)
Page 536 Maintenance Commands Associated Link MOs affected by this Command NOTE: Although alarms on these MOs may appear as warnings, the alarms should be investigated with user-related problems. PN’s Maintenance circuit pack (MAINT) Expansion Interface (EXP-INTF) ISDN-PRI signaling group (ISDN-SGR) Journal printer (JNL-PRNT) PMS link (PMS-LINK) Primary CDR link (PRI-CDR) Synchronization (SYNC)
Page 537 set options Field Error Messages Since every field on the first page allows the same values, only one error message is printed for any fields. If the value is not one of the listed characters (m,n,r,w,or y) then the following message is displayed: “X”...
Page 538: Set Pnc
Maintenance Commands set pnc set pnc lock | unlock On critical-reliability systems (duplicated PNC), set pnc lock locks the active port network connectivity in the active state. PNC interchanges will be prevented, and the active PNC will remain active regardless of its state of health. Duplicate call setup will still take place, though the standby is not available for service.
Page 539: Set Signaling-Group
set signaling-group set signaling-group set signaling-group group# The set signaling-group command sets the secondary D channel in the specified signaling group to be the primary D channel. The primary D channel becomes the secondary D channel. 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 link.
Page 540: Set Snc
Maintenance Commands set snc set snc UUCSS [override] NOTE: This command is not valid for IP Connect. This command sets which switch node clock (SNC) circuit pack in a given switch node carrier is active. This command is valid only for a simplex PNC with a Center State Switch (CSS). Parameters override This qualifier will force execution of the set command regardless of the health of the...
Page 541: Set Synchronization
set synchronization set synchronization This command sets a specific DS1 trunk, Tone-Clock circuit, or ATM switch as the reference source for system synchronization signals. It is permitted only after synchronization has been disabled with disable synch . Any administered DS1 trunk or active Tone-Clock may be entered with the set command.
Page 542: Set Tdm
Maintenance Commands set tdm set tdm port-network PN# bus a | b [override] This command determines which of the paired TDM buses (A or B) on a port network will carry the control channel and dedicated tone time slots. Each port network has a 512 time-slot TDM bus configured as two separate 256 time-slot buses.
Page 543: Set Time
set time set time set time This command brings up a form showing the current day, date, month, year and time kept by the system clock. These entries can be edited to update the system time. The second field is set to zero whenever the time on the clock is altered. If no new entries are made, system time remains unchanged.
Page 544 Maintenance Commands Field Descriptions An input form with the following fields is displayed. The current time, or default time will be displayed in the fields. Valid entries are Monday through Sunday. Day of the Week: 1-31 are valid entries. A check for leap year is also made. Day of the Month: January through December.
Page 545: Set Tone-Clock
set tone-clock set tone-clock set tone-clock UUC [override] This command forces a Tone-Clock interchange for a non-IPSI controlled port network. If the port network has an IPSI for a Tone-Clock, this command is blocked. On port networks with duplicated Tone-Clocks, this command is used to select which of the two Tone-Clock circuit packs is to be active.
Page 546: Status Access-Endpoint
Maintenance Commands status access-endpoint status access-endpoint extension [print] This command displays the operational of a non-signaling port on a DS1 interface or on an analog tie trunk circuit pack. Output The following display shows a typical result when status access-endpoint 2300 is entered.
Page 547: Status Administered-Connection
status administered-connection status administered-connection status administered-connection adm-conn# [print] This commands displays the operational status of an administered connection. To view administrative information for administered connections, use list administered-connection and display administered-connection . Parameters adm-conn# The number (1-128) of the administered connection as assigned during administration.
Page 548 Maintenance Commands The current status of the administered connection as follows: Connection State: = A connection between the originating and destination connected endpoints is currently active. restored = The connection has been restored. The session may or may not have been preserved. failed = The connection failed due to either an administrative error such as a wrong number or a service-blocking condition such as...
Page 549: Status Attendant
status attendant status attendant status attendant console# [print] The status attendant command displays the operational state of the specified attendant console. This information can help in trouble diagnosis and in locating facilities to which the attendant console is connected. 555-233-143 Issue 1 May 2002 7-293...
Page 550: Status Bri-Port
Maintenance Commands status bri-port status bri-port UUCSSpp [print] The status bri-port command displays the service state, maintenance state and layer 1 state of an ISDN-BRI port. Also displayed on this form is information about the point-to-point signaling links carried over the port. For more information, see BRI-PORT in Chapter 8, ‘‘Maintenance-Object Repair Procedures’’.
Page 551 status bri-port The operational state of the physical connection (Layer 1) of the ISDN link Layer 1 State carried over the port: activated = Layer 1 frames are being passed between the port and BRI endpoints. = The port is in service, the layer 1 interface device pend-activation is turned on and layer 1 frames are being sent from the port, but the BRI endpoints are not responding.
Page 552 Maintenance Commands Interpreting Results of the status bri-port Command Table 7-45 will help to interpret results of the status bri-port command. Find the combination of output field values contained in your report and follow the recommendations for the type of endpoint connected to the portStatus Cabinet status cabinet UU [print] This command displays the operational status and attributes of the specified cabinet.
Page 553 status bri-port Table 7-45. Interpreting BRI-Port Status Reports — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value ASAI 0-63 Established blank blank This is a transitory state for ASAI adjuncts. ASAI signaling is connected at Layer 2 but the Layer 3 Restart procedure has not been completed between switch and adjunct.
Page 554 Maintenance Commands Table 7-45. Interpreting BRI-Port Status Reports — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value BRI, 64-126 L3-Established blank A demand SPID Facility test is in ASAI progress on the port, and the link is not currently associated with a BRI endpoint.
Page 555 status bri-port Table 7-45. Interpreting BRI-Port Status Reports — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0-126 L3-Assigned ext# blank This is a transitory state for BRI endpoints that support MIM initialization. 1. Wait 5 seconds and repeat the command.
Page 556 Maintenance Commands Table 7-45. Interpreting BRI-Port Status Reports — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0-126 L3-Assigned ext# This is a transitory state for BRI endpoints that support MIM initialization when a SPID Facility test has been used to initialize the station.
Page 557 status bri-port Table 7-45. Interpreting BRI-Port Status Reports — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value ASAI 0-126 Hyperactive ignore ignore Link has sent too many messages per unit time. Signaling has been suspended.
Page 558 Maintenance Commands Output The following display shows a typical result when status cabinet 1 is entered. status cabinet 1 CABINET CONFIGURATION STATUS CABINET CONNECTIVITY STATUS Carrier PN/SN Carrier Cabinet PN/SN Connectivity Status Location Number Type Type Active Standby PN 1 processor PN 1 PN 1...
Page 559 status bri-port For PNs connectivity status refers to the availability of the EAL (Expansion Connectivity Archangel Link) and INL (Indirect Neighbor Link) to the carrier for both Status active and standby PNCs (if duplicated). Possible values are: up — EAL and INL are both available. down —...
Page 560: Status Cabinet
The following example shows the output for the status cabinet command if the value in the Cabinet Layout field on the Cabinet form is rack-mount-stack. NOTE: Since S8700 IP Connect configurations do not use PN maintenance boards, the Emergency Select Transfer Switch field would equal NoEqp. status cabinet 1...
Page 561: 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 server uses to send call detail records to an output device such as a Call Detail Recording Utility (CDRU).
Page 562: Status Clan-Port
Maintenance Commands status clan-port The same information that is displayed by the status clan-port command can be invoked with: status link n status clan-port or netstat link n for C-LAN links. See status link n for more information. Defaults The test defaults to return the status of Cleared Alarm Notification of the first OSS telephone number.
Page 563: Status Conference
status conference status conference This command is a troubleshooting aid to help identify problems with a multimedia conference and can help solve more complex problems. Synopsis The first screen appears when status conference is entered and at least 1 valid conference is found.
Page 564 Maintenance Commands Parameters status conference Displays all stored conference data. status conference 2 print Displays data on conference 2 (current or last completed), and sends it to the SAT printer. Feature Interactions None. Output Depending on the command entered, it is possible to have many records display. Active conferences display first (in order of conference-ID), followed by completed conferences (most recently completed first).
Page 565 status conference Field Descriptions (status conference, Page 1) The current status of the conference - active, in-use, complete status Always set as MMCH DYNAMIC conference name Always set as voice-activated conference mode Not Applicable password Not Applicable password scope Conference cascade mode - blank cascade mode The current operating audio mode - G.711-A, G.711-mu, G.728.
Page 566 Maintenance Commands Does this conference support Rate Adaptation? - Rate adaptation For single-screen conference, the video format of the conference, Format QCIF, QCIF/CIF, H.CTS, H.CTX+ , and (in/out) For conferences other than H.261, the input and output formats are always symmetric and the mode is the same for input and output. These display as H.CTX, H.CTX+, and SG4.
Page 567 status conference Endpoint extension chosen at administration. This field is blank. The Meet-Me Number administered for the Meet-Me Extension. This field Meet-me number is blank. Indicates whether dial-in or dial-out is used to join the endpoint to the Dial Type conference - .
Page 568 Maintenance Commands Does it have the required audio capability? - blank the endpoint has the required audio capability. Audio add-on endpoint always have the Aud field set to y once the endpoint has joined the conference. this endpoint is PCM only and it changed the video quality of the conference by changing the operating audio from G.728 to G.711.
Page 569 status conference Does it have the Still Frame Graphics capability? - blank This endpoint has this capability. This endpoint did not declare this capability. The conference retains the still frame graphics capability when a non-compliant endpoint joins the conference. blank This endpoint has never joined the conference.
Page 570 Maintenance Commands Indication of the talking state of the endpoint - blank At the time the command was invoked, voice energy (talking) was detected from the endpoint. At the time the command was invoked, the endpoint indicated to the MCU that it was muted. It is possible that an endpoint may mute, but not send any indication to the MCU.
Page 571 status conference This value applies only to quad-screen conferences. *a indicates that an endpoint is part of the current mixed image and is fixed in one of the quadrants via administration. A value of indicates that the endpoint is fixed in a quadrant but is not currently connected (Fill image displays).
Page 572 Maintenance Commands Applies only to quad-screen conference and indicates that UCC/CRCS Agent designated a quadrant as VAS. An asterisk ( ) is affixed before to indicate that this endpoint is part of the current quad image. At the time the command was invoked this endpoint’s video was being broadcast to other sites.
Page 573 status conference Field Descriptions (status conference, Page 2) The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for each Sum Grp 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 574 Maintenance Commands Drop Reason Chair disconnected the endpoint, using either Chair Command Disconnect (CCD) or Chair Command Kill (CCK) signals. (cont’d) Conf End The conference was ended due to reaching stop time for a reserved conference or due to an active conference being converted to file. Clearing received from DS1 - the disconnect came from the Endpoint endpoint.
Page 575 Ports ESM Endpoint’s assigned summer group number. The summer group port Sum Grp assignments are on screen 1. For Avaya use only. software Output (status conference endpoint) status conference x endpoint y The first screen appears when status conference x endpoint y is entered and the specified conference is found.
Page 576 Maintenance Commands Page 1 - Status Conference Endpoint status conference endpoint page 1 of 6 STATUS OF CONFERENCE ___ ENDPOINT: __ Status: ________ Ext: _____ Type: ____ Manufacturer/Country: ____/____ Product: _____ Terminal Name: _______________ Data Mode: _________ MLP Rate: ____ Admin Bandwidth: ____ Rate Adaptation: _ Conf Bandwidth: ____...
Page 577 status conference Is the endpoint currently participating in the conference or in process of In Use connecting to the conference? – blank – The endpoint is in use and is fully connected on all media in an active conference. – The endpoint is in use and is fully connected, however the endpoint has changed the conference audio or video capability or has changed the rate of the conference because of rate adaptation.
Page 578 Maintenance Commands Does it have the required audio capability? – blank – The endpoint has the required audio capability. Audio add-on endpoint always have the Aud field set to y once the endpoint has joined the conference. – This endpoint is PCM only, and it changed the video quality of the conference by changing the operating audio from G.728 to G.711.
Page 579 status conference Rate adaptation/Interworking indicator – blank . Values of 5 Rate Adpt and 6 apply only to low-/high-speed interworking. Every other value applies only to rate adaptation. – A 56-kbps (low-speed) endpoint has joined a high-speed (128-kbps or above) conference. This endpoint is connected with audio-only capability, but is neither a valid video source nor destination.
Page 580 Maintenance Commands Indication of the talking state of the endpoint – blank – At the time the command was invoked, voice energy (talking) was detected from the endpoint. – At the time the command was invoked, the endpoint indicated to the MCU that it was muted.
Page 581 status conference – At the time the command was invoked the endpoint was not a valid video source. For continuous presence conference, if this endpoint is (cont’d.) fixed in a particular quadrant, an asterisk (#) is affixed before i. – For full-screen conferences, at the time the command was invoked the endpoint’s video was the return video to the broadcaster.
Page 582 Maintenance Commands Page 2 - Endpoint Channel Information This section only describes the fields that are specific to the endpoint-level command output. The following screen shows page 2 of 6: status conference x endpoint y status conference endpoint page 2 of 6 ENDPOINT CHANNEL INFORMATION Chan.
Page 583 status conference Field Descriptions Time (in 24-hour notation) when the channel joined the conference. Join Time Time (in 24-hour notation) when the channel disconnected. If the first channel Drop Time has a drop time, then it means that the endpoint is idle. If there is a drop time without a join time, it means that the call disconnected without being joined to the conference.
Page 584 Maintenance Commands Clearing received from DS1—The disconnect came from the Drop Reason Endpoint endpoint. The endpoint notified the MCU that it intended to disconnect. (cont’d) Clearing received from DS1—The disconnect came from either Far-end the network or the endpoint. Handshake Either framing was never found (the endpoint could not complete initialization—Problems finding Frame Alignment Signal (FAS), Multi Frame Alignment (MFA) and getting a corrected coded cap-set) or...
Page 585 status conference The call disconnected before answer by an endpoint. Drop Reason Pre-AnsDrop The cause of the disconnect may be the network, an endpoint, or a (cont’d) terminal adapter. This drop reason is different from ‘No-answer,’ which indicates that a 60-second timeout occurred while alerting. In this case, the call drops before the 60-second timer has expired.
Page 586 Maintenance Commands Page 3 - Conference Information This section only describes the fields that are specific to the endpoint-level command output. The following screen shows page 3 of 6: status conference x endpoint y. status conference endpoint page 3 of 6 CONFERENCE INFO: Broadcaster: xx (See-Me) Return Vid: xx ---------- MODE COMMANDS/COMMUNICATION MODES ------|...
Page 587 status conference Conference Info. This information applies mostly to full-screen conferences. The Broadcaster field also applies to quad-screen presentation mode conferences. Indicates the endpoint number that is the current broadcaster. The Broadcaster Broadcaster can be qualified with the following keywords: indicates a broadcast mode broadcaster.
Page 588 Maintenance Commands Mode Commands/Communication Modes. This is a collection of both incoming and outgoing bandwidth allocations for the multiplex. The Incoming data is the rate at which the MCU thinks the endpoint is communicating based on the Bit-rate Allocation Signal (BAS) codes received from the endpoint/codec and the capabilities the MCU has declared.
Page 589 status conference XRATE XRATE may be 64 when the endpoint is just dialing in, or in the event of problems. It implies that only one B channel is being used. (cont’d.) AUDIO Audio rate (kbps bandwidth) of the conference and the endpoint must be the same but not necessarily their mode.
Page 590 Maintenance Commands AUDIO Other possible AUDIO mode values include neutral (neutralized I-channel) (no audio signal) which never match conference mode Au-off, Frm (cont’d.) and are not supported by MCU. 56/64 56/64 field is derestrict when operating at per-channel rates of either 64, 128, 192, 256, 320, 384, 512, 768, 1472, 1536, or 1920 kbps.
Page 591 status conference Endpoint Miscellaneous (EPT MISC) Information. EPT MISC contains miscellaneous states and counters for an endpoint. The flags can be a value of y or n . The counters start with initial value of 0x00 , they increment to 0xff, and then wrap around to 0x01.
Page 592 Maintenance Commands HYPR A value of indicates hyperactivity from an endpoint (MCU isolated endpoint from the MCU conference due to “thrashing” behavior) and affects endpoint’s status as a video source (for 5 seconds of hyperactivity timer). The HYPR counter indicates the number of times this endpoint was hyperactive. DMUTE A value of indicates that the decoder was muted by the VC board or the...
Page 593 status conference Page 4 - Endpoint Capability Information This section only describes the fields that are specific to the endpoint-level command output. The following screen shows page 4 of 6: status conference x endpoint y. status conference endpoint page 4 of 6 ENDPOINT CAPABILITY INFORMATION -------------------------------------------------------------------------------- VID | vfmt: QCIF...
Page 594 Maintenance Commands field is 1 way for an endpoint to indicate that it is operating at 56 restrict MISC kbps per channel, the other way is the 56/64 command mode with a value of restrict . An endpoint on a 56-kbps conference must send one or both of the 2 indications that they are operating at 56 kbps before they become a video source in a 56-kbps conference.
Page 595 status conference Page 5 - Endpoint Call Status Information This page summarizes such call-related status as per-channel join counts, join/drop time, drop reason, drop code, and auxiliary bonding drop code. In addition, it contains a drop code and software fields from the previous call. The data on the page is always retained.
Page 596 Maintenance Commands Page 6 - Administered Connections This page summarizes information about the administered connections associated with this endpoint. This data can only be viewed while the conference is active. status conference endpoint page 6 of 6 ADMINISTERED CONNECTIONS INFORMATION Retry Failure Chan Num...
Page 597 status conference Field Descriptions The actual numbers that are dialed out by the administered connections for Dial-Out each channel in the call. Note that the dial Out #1 and #2 on page 1 of the Number forms display the DCP endpoint number. This is particularly useful with bonding dial-out calls.
Page 598 Maintenance Commands Table 7-49. 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 599 status conference Table 7-49. 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 –...
Page 600: Status Data-Module
Maintenance Commands status data-module status data-module extension [print] This command displays internal software states of a specified data-module port. It is useful for diagnosis and locating facilities to which the data module is connected. Output status data-module 70058 DATA-MODULE STATUS Data Ext/Stn Ext for Stn DM: Service State: in-service/idle Port/Channel Number: 26A0817...
Page 601: 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 602: Status Hardware-Group
Maintenance Commands status hardware-group status hardware-group [print] Summary information about the active or last hardware group tests will be displayed. This display includes the number and percentage of maintenance objects tested, the percentage of tests passed/failed/aborted, the time elapsed since initiating the hardware group test, the specific hardware group test command (see test hardware-group command) initiated, and the state (active/canceled/complete) of the hardware-group test.
Page 603 status hardware-group Field Descriptions The state of a hardware-group command: active: testing is in progress; Hardware Group canceled: testing has been canceled; complete the command has Command State: completed and there is no testing going on. The number of MOs in the specified group (refer to test hardware-group Number of MOs command) that have had been tested by the current hardware-group Tested:...
Page 604: Status Health
Permissions Defaults Interactions status health print init none none inads craft Output (for S8700 Multi-Connect) The following example shows the output for the status health command. status health PNC: Simplex ALARMS:Maj: Min: 1 Wrn: Pwr: comm Sync:primary Logins:4 BUSYOUT:Trk: Stn:...
Page 605 Output (for S8700 IP Connect) If the value in the Cabinet Layout field on the Cabinet form is rack-mount-stack, then the output looks like the following. S8700 IP Connect configurations do not use PN maintenance boards or, therefore, emergency transfer; so the EmTr field is NoEqp.
Page 606 Maintenance Commands The current source of timing signals used for system synchronization Sync Source For systems with a Stratum 3 clock: External – Normal operating condition Internal – Another source besides the Stratum 3 clock, such as a Tone-Clock circuit or circuit pack, is providing the master timing signal. For systems with Stratum 4 timing: Primary –...
Page 607 Both EAL and INL (if applicable) are not available. (Near End) The EAL is available but the INL is not available. ( Far End) The INL is available but the EAL is not available. The following are available for S8700 Multi-Connect cabinets only: up/up...
Page 608: Status Ip-Board
Maintenance Commands status ip-board status ip-board CCcss The status ip-board command runs on R10 or later systems. The 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.
Page 609 status ip-board Table 7-51. status c-lan-ip CCcss — Continued Field Name on switch output Output type MIB data Description Incoming Counter Long ipInDiscards The number of input IP datagrams for datagrams which no problems were encountered discarded to prevent their continued processing, but which were discarded (e.g., for lack of buffer space).
Page 610: Status Ip-Network-Region
Maintenance Commands status ip-network-region status ip-network-region x 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 611: Status Isdn-Testcall
status isdn-testcall status isdn-testcall status isdn-testcall group# / member# [print] Examples status isdn-testcall 78/1 print This command displays the progress of an outgoing ISDN-PRI test call on the trunk specified. The tested ISDN-PRI B channel’s 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 are displayed on the status form.
Page 612 Maintenance Commands The duration specified in minutes for how long the test call should run. Valid Duration durations are 1-120 (minutes) or blank (to indicate the default amount of Specified minutes was used to run the test). The duration specified in minutes for how long the test call has been running. Duration of A blank indicates that the default amount of time was used to run the test.
Page 613: Status Journal-Link
status journal-link status journal-link status journal-link wakeup-log | pms-log [print] This command displays the operational status of a wakeup-log or a pms-log printer link. If the link is down, the number of times the switch has tried to re-establish the link will be shown. A journal printer is used to document automatic wake-up events, emergency access to attendant events and, if the Property Management System is not functional, housekeeping events.
Page 614 Maintenance Commands Field Descriptions The operational status of the link as follows: Link State — The link is established and is capable of supporting the application. This is the normal operational state. — The link is physically down. down extension not administered —...
Page 615: Status Link N
status link n status link n status link n (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 616 Maintenance Commands Link/Port Status Form (Page 1) status link 1 Page 1 of LINK/PORT STATUS Link Number: 1 Link Status: connected Link Type: ethernet Link Name: gert_clan1 Service Port Location: 01A0317 Service Port Data Extension: 70050 Service State: in-service/active Node Name: gert_clan1 Source IP Address: 172.22.22.177 Subnet Mask: 255.255.0.0 Broadcast Address: 172.22.255.255...
Page 617 status link n Error Counters Form (Page 2) status link 1 Page 2 of ERROR COUNTERS Reset Time: 03/08 17:38 Last Hour Start Time: End Time: Incoming Received: Unicast Pkts Multicast Pkts Octets Since Reset 5649003 1401469 689650382 Last Hour Incoming Dropped: Error Pkts Discard Pkts...
Page 618 Maintenance Commands The total number of packets that higher-level protocols requested be Outgoing transmitted to a subnetwork-unicast address, including those that were Transmitted discarded or not sent. unicast packets The total number of packets that higher-level protocols requested be Outgoing transmitted to a non- unicast (subnetwork-broadcast or multicast subnetwork-multicast) address, including those that were discarded or not...
Page 619 status link n TCP/IP Applications Currently Active Form (Page 4) The following is an example of the output of page 4 of the status link n command. The form displays every TCP/IP socket link that is currently up and active and that is using the Ethernet link n via the C-LAN board or the Processor Ethernet interface.
Page 620: Status Logins
Maintenance Commands 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 621: Status Packet-Interface
status packet-interface status packet-interface status packet-interface [cabinet #] [print] The status packet-interface command displays the status of all packet-interface circuit packs in the system along with link information. The service state is displayed for both active and standby packet-interface circuit packs. Link status information including total, active and failed links are displayed for active packet-interface circuit packs only.
Page 622 Maintenance Commands Output Separate columns identify each Packet Interface circuit pack slot. Service state is displayed for both active and standby packet-interface circuit packs. A cabinet number must be specified. If there are no IPSIs in the cabinet, this error message is displayed: No IPSI in cabinet specified.
Page 623: Status Periodic-Scheduled
status periodic-scheduled status periodic-scheduled status periodic-scheduled [print] The status periodic-scheduled command displays summary information about currently active and recently completed background testing. Periodic tests are run every hour, and scheduled tests are run daily. Starting and stopping times, and other parameters for daily scheduled testing are administered on the change system parameters maintenance form.
Page 624: Status Processor-Channel 1
Maintenance Commands status processor-channel 1 The following screen applies to processor channels carried over link type of Ethernet or PPP (using the TCP/IP protocol). PROCESSOR CHANNEL STATUS Channel Number: 1 Channel Status: Administered but not connected Link Number: 3 Link Type: ethernet Message Buffer Number: 0 Reset Count: 0 Retransmission Count: 0...
Page 625: Status Pms-Link
status pms-link status pms-link status pms-link [print] The status pms-link 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 PMS, will be shown. If the link is down, the number of times the switch has tried to set up the link will be shown.
Page 626: Status Pnc
[print] NOTE: This command is not valid for S8700 IP Connect configurations. The status pnc command displays a summary of conditions on the active and standby Port Network Connectivities (PNC). If the PNC is not duplicated, the screen displays blanks in the PNC-B and other duplication-related fields.
Page 627 status pnc Most fields on this screen display blanks when the PNC is not duplicated. Whether or not the system has a duplicated PNC (critical-reliability option). Duplicated? On a system with duplicated PNC, whether the PNCs are locked by means of the Software set pnc lock or reset pnc override-and-lock commands.
Page 628 Maintenance Commands In a duplicated system, each PNC has a separate entry for the following fields, representing conditions for only that particular PNC. This field displays "active" or "standby", depending on whether or not that PNC Mode controls active call processing. On a system with duplicated PNC, the state of health of each PNC.
Page 629 status pnc Table 7-53. Fault Class Field Descriptions Fault Class Priority Description FC_EAL Number of PNs with EALs down EXP-PN FC_INL Number of PNs with LINL, RINL, or EI-SNI neighbor EXP-PN link faults SN-CONF FC_HW Number of PNs affected by hardware faults in a link EXP-INTF having an EI as an endpoint (Endpoints can be SN-CONF...
Page 630: Status Port-Network
The following example shows the output for the status port-network command for an S8700 Multi Connect. Since the PKTINTs are moved to the IPSIs in PNs for S8700 Multi-Connects, this command shows the location and state of the links, whether active or failed, and the total.
Page 631 status port-network Field Descriptions The Port Network number associated with the Port Network for which status is being displayed. The number of major alarms logged against the Port Network that is being Major Alarms displayed. The number of minor alarms logged against the Port Network that is being Minor Alarms displayed.
Page 632 Maintenance Commands This field shows whether the TDM bus has the control channel on it Control (“y”/”n”). Only one TDM bus of a TDM bus pair on each Port Network can Channel have the control channel on it at a given time. If the system does not contain a PN, blanks appear in this field.
Page 633 status port-network This field represents the operational state of the packet bus. A service Service State state of “in” means the packet bus has been installed and is in normal operation. A service state of “out” means either that the: Packet bus is out of service and has failed certain maintenance tests Maintenance object has been demand busied out.
Page 634: Status Processor-Channel
Maintenance Commands status processor-channel status processor-channel channel# [print] The status processor-channel command displays the status of the specified processor channel and the values of its various counters. A processor channel is one of 128 logical channels associated with an SCI link. Each processor channel terminates in the switch processing element with a session.
Page 635: Status Psa
status psa status psa ‘‘status tti’’ on page 7-406. 555-233-143 Issue 1 May 2002 7-379...
Page 636: Status Signaling-Group
Maintenance Commands status signaling-group status signaling-group group# [print] This command displays the service state, type, port location, and of the primary and secondary D channels within an ISDN-PRI signaling group. A signaling group is a set of B channels signaled for by a designated single D channel or combination of D channels.
Page 637 status signaling-group Field Descriptions An administered number from 1 to 666 that identifies the signaling group. Group ID: ‘‘ISDN-SGR (ISDN-PRI Signaling Group)’’ on page 8-976 for more Type: information about group types. facility: Every member is carried on a single DS1-associated facility. Facility-associated signaling groups support only simplex D-channel configurations.
Page 638: Status Sp-Link
Maintenance Commands status sp-link status sp-link [print] This command displays a summary of the operational state of the system printer link. Output The following display shows a typical result when status sp-link is entered. status sp-link SYSTEM PRINTER LINK STATUS Link State: down Number of Retries: 0 Maintenance Busy? no...
Page 639: Status Station
30001 browse status station 83277 status station 83277 print Output (from S8700 Multi-Connect) The following example shows the output for the status station 30001 command. status station 30001 page 1 of 2 GENERAL STATUS Administered Type: 6408D+...
Page 640 Maintenance Commands Field Descriptions (Page 1, status station for Multi-Connect) Administered station type Administered Type The actual type of phone connected to this port, if the information is Connected Type available Station or attendant extension Extension Port location: cabinet-carrier-slot-circuit Port Whether the station has a call parked ( Call Parked? Whether ring cut off is activated (...
Page 641 status station Page 2 displays the part ID of the station, if available. status station 30001 page 2 of 2 GENERAL STATUS CONNECTED STATION INFORMATION Part ID Number: unavailable Serial Number: unavailable Station Lock Active? no Field Descriptions (Page 2) Shows the Part ID Number (comcode) of the telephone.
Page 642 Maintenance Commands Output (from S8700 IP Connect) for Active IP Phone Conference Call The following example shows the output for the status station 70100 command. This command has been enhanced to display the relevant IP audio parameters used for each IP hop. This data is dependent on the connected ports (page 1 of the Status Station form).
Page 643 Serial Number: unavailable Station Lock Active? no Field descriptions are the same as ‘‘Field Descriptions (Page 2)’’ on page 7-385 for S8700 Multi-Connect. Page 3 of the status station 70103 command for an IP call. status station 70103 Page 3 of...
Page 644 Maintenance Commands Field Descriptions (Page 3) The C-LAN board location serving the switch end of the IP signaling link. IP Signaling: The port number is always 17 for the “ethernet” port of the C-LAN. This field Switch Port will be blank for an unregistered H.323 station. Switch-end Q.931 (H.323 station) or CCMS (IP SoftPhone) IP signaling IP Signaling: address and IP port.
Page 645 status station Set-end IP audio address and IP port. IP Address is of the form Audio: Set-end xxx.xxx.xxx.xxx where xxx have decimal values 0-255. Port is a decimal IP Addr and value 0-65535. This field will be blank for an idle station with no audio link, Port or for a telecommuter IP SoftPhone with circuit-switched audio link.
Page 646 Maintenance Commands Page 4 for the status station 70103 command for an IP call. status station 70103 Page 4 of NETWORK STATUS Average Jitter (ms) Packet Loss per Second Last Ten Seconds Last Ten Seconds # - more than 255ms * - 100% loss Per Call Info Out of Order Counter: 0...
Page 647 status station Field Descriptions (Page 4) The ten most recent one-second samples of the jitter Average Jitter buffer size for the requested endpoint. Last Ten seconds The ten most recent one-second samples of the lost Packet Loss per Second packet information for the requested endpoint. A count of the number of out-of-order packets detected Out of Order Counter during the current connection.
Page 648 Maintenance Commands Page 5 of the status station 70103 command for an IP call. status station 70103 Page 5 of CONNECTED PORTS src port: S00003 src port: S00003 ip-start: 172. 22. 22. 8:2854 172. 22. 22. 8:2854 ip-end: 172. 22. 22.233:2960 01B0905 172.
Page 649: Status Switch-Node
SN# [print] NOTE: This command is not valid for S8700 IP Connect configurations. This command displays the operational status and attributes of the user specified switch node. The operational status of the active and standby Switch Node Clock (SNC) circuit packs for the switch node are displayed along with any alarms logged against the specified switch node.
Page 650 Maintenance Commands Field Descriptions A line of information is displayed for each switch node carrier. The switch node number, 1 or 2. If the PNC is duplicated, the A and B PNCs are Switch Node each reported separately. The physical position of the switch node carrier represented as "UUc" (where Location "UU"...
Page 651: Status Synchronization
[print] status synchronization cab# This command lists the synchronization source for the system. The following examples show the output for the status synchronization command. Output (for S8700 Multi-Connect) status synchronization SYNCHRONIZATION STATUS Stratum Level: 4 Maintenance Name: TONE-BD...
Page 652: Status Sys-Link
The link is specified by giving the location of the port associated with the link. Examples status sys-link 1e0201 Output (for S8700 IP Connect) The following display shows a typical result when status sys-link 8a02 is entered. status sys-link 8a02...
Page 653 status sys-link Field Descriptions The location of the port associated with the system link Location (cabinet-carrier-slot-circuit). The type of system link as follows: Type EAL—Expansion archangel link INL—Indirect neighbor link (center stage switch) PRI—ISDN-PRI signaling link BFD—Bearer fault detection link ACL—ATM control link TACL—Trunk ATM control link RSCL—Remote socket control link...
Page 654 Maintenance Commands Output (for S8700 Multi-Connect) For S8700 Multi-Connects, this command provides status for a bearer fault detection link (BFDL) for the link location specified. The output shows status about BFDLs, which only exist in port networks with IPSIs. status sys-link 2a0101...
Page 655: Status Trunk
status trunk 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. NOTE: If you execute a status trunk command for a trunk that uses a 1d interface, you will get different information depending on whether you execute the...
Page 656 Maintenance Commands 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 trunk Signaling group belongs. For other trunk types, the field is blank. Group ID Locations of ports currently connected to the trunk.
Page 657 Output The following screen shows typical results for an S8700 IP Connect system. status trunk 20/1 TRUNK STATUS Trunk Group/Member: 0020/001 Service State: in-service/idle Port: T00016 Maintenance Busy? no Signaling Group ID: CA-TSC state: none Connected Ports: Port...
Page 658 Maintenance Commands 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 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...
Page 659 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. Refer to Administration for Network Connectivity for Avaya MultiVantage Software for more information.
Page 660: Status Tsc-Administered
Maintenance Commands status tsc-administered status tsc-administered signaling-group# [ /tsc-index] [print] This command displays the operational status of temporary signaling connections (TSCs) administered for a specified signaling group. Examples status tsc-administered 1 status tsc-administered 1/2 print Parameters signaling-group# An administered number associated with each signaling group. tsc-index A number associated with each TSC in a signaling group.
Page 661 status tsc-administered Field Descriptions The administered TSC index (1-759). TSC Index A state of "inactive" means that the administered TSC is not functioning (i.e., D TSC State channel out-of-service, disabled, etc.). A state of "active" indicates that the administered TSC is up and user information can be exchanged end-to-end. A state of "pending-inactive"...
Page 662: Status Tti
Maintenance Commands 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 whether TTI ports are being generated or removed, the number of TTI-supported boards that have processed, and the number of TTI-supported boards that have not yet been processed.
Page 663 status tti Output The following example shows the output for status tti and status psa . status tti status psa TTI/PSA STATUS TTI Background Task State: completed - all ports translated TTI State: voice # of Boards Completed: # of Boards Left to Process: Percent Complete: Elapsed Time since Task Started: 0 :0 :1...
Page 664 Maintenance Commands The number of TTI-supported circuit packs that were not processed # of Boards by the background maintenance task. Left to Process A ratio of the of number of circuit packs completed to the total Percent number of circuit packs. Complete Elapsed time in hours:minutes:seconds since the TTI background Elapsed Time...
Page 665: Status Val-Ip
status val-ip status val-ip status val-ip location Use this command to generate an IP-related status report about the specified 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...
Page 666: Test Alarms
Maintenance Commands test alarms This command tests the hardware associated with selected alarms Synopsis test alarms [auto-page] [failures] [step] [short | long] [repeat-number | clear] Permissions The following default logins may execute this command: system technician, inads, init, nms. Examples test alarms test alarms step failures test alarms long clear auto-page...
Page 667 test alarms Parameters auto-page This option provides the ability to continue testing and displaying test results, by providing a new screen every time the SAT screen is filled with test results. The screen does not scroll to accommodate new results; instead a new screen is provided after the current screen fills up.
Page 668 Maintenance Commands long This will execute a more comprehensive and longer version of the diagnostic tests. This may involve both destructive and nondestructive tests. repeat number The "number" specifies how many times each test in the sequence is to be repeated.
Page 669 test alarms Query From Input After entering the command test alarms , the system technician will be presented with an options form for alarm selection. The type of alarm to be tested is specified by placing a y or n in the alarm type fields. Alarm The technician can choose a combination of active alarms: major, minor, and/or Types...
Page 670 Maintenance Commands test alarms repeat 1 HARDWARE TEST ALARM QUERY The following options control which alarms will be tested. ALARM TYPES 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 671 test alarms Category: adm-conn, announce, bri/asai, cdr, data-mod, detector, di, environ, esm, exp-intf, ext-dev, generatr, inads-link, infc, ip, lic-file, maint, misc, mmi, mnt-test, modem, pkt, pms/jrnl, pnc, pncmaint, pnc-peer, quick-st, s-syn, sch-adj, stabd, stacrk, stations, sys-link, sys-prnt, tdm, tone, trkbd, trkcrk, trunks, vc, vsp, wideband, wireless.
Page 672 Maintenance Commands Cabinet: "Invalid entry" Port Network: "Port Network invalid" Board Number: "Invalid entry" Port: "Port invalid" Category: “xxxxxxxx” is an invalid entry; please press HELP” Extension: "Entry must be all digits" "Extension not assigned" Trunk (group) "Entry must be all digits" "Group not assigned, or group assigned but with no member"...
Page 673 test alarms Output The responses, with normal output, will be displayed on a test-by-test basis with one line of data displayed for each test result. With the failures option only the tests that have failed will be displayed. The following output fields are for the ALARM ENTRY section: The location of the alarmed object (cabinet-carrier-slot-circuit).
Page 674 Maintenance Commands For the following output example, assume that only one alarm was in the alarm log and it is on the board in cabinet 1, carrier c, slot 7. The command that was entered was “test alarms” and the query form was left empty by just pressing ENTER test alarms Page...
Page 675: Test Analog-Testcall
test analog-testcall test analog-testcall test analog-testcall trunk-group# / member# | port UUCSSpp | board UUCSS [full | supervision | no-selftest | no-return-loss | no-st-or-rl] [repeat#] [schedule] The test analog-testcall command causes the Automatic Transmission Measurement System (ATMS) to originate a test calls over analog trunks. ATMS collects performance measurements on the test call and compares them to administered thresholds.
Page 676: Test Board
Maintenance Commands test board test board UUCSS [short | long] [repeat# | clear] [schedule] The test board command will validate that the board exists at the specified location. Based on the logical type (for example, Analog, Digital, Hybrid) of board a series of tests will be executed.
Page 677: Test Cdr-Link
test cdr-link test cdr-link test cdr-link primary | secondary [short | long] [repeat-number | clear] [schedule] The test cdr-link command validates that a call detail recording link has been administered and established. The test defaults to “ short ”. Parameters [primary | secondary] A system may have up to two CDR links: a primary that is normally used and a secondary that serves as a backup in case the primary fails.
Page 678: Test Customer-Alarm
UUC [short | long] [repeat# | clear] [schedule] NOTE: This command is not valid for S8700 IP Connect configurations. The test customer-alarm command performs hardware diagnostic tests on the leads of the EPN’s Maintenance circuit pack in a specified cabinet. These leads are connected to customer equipment and provide a means of alerting the system administrator and INADS when that equipment fails.
Page 679: Test Data-Module
test data-module test data-module test data-module extension [short | long] [repeat# | clear] [schedule] The test data-module command performs hardware diagnostic tests on a data module or a data channel. Test results are determined by the interface to the digital line port. 555-233-143 Issue 1 May 2002 7-423...
Page 680: Test Ds1-Facility
Maintenance Commands test ds1-facility test ds1-facility UUCSSf [short | long | external loopback] [repeat#] [schedule] The test ds1-facility command performs a series of tests on the specified facility. Each individual test will exercise diagnostics on the facility and then return results of the test along with any possible error codes.
Page 681: Test Ds1-Loop
test ds1-loop test ds1-loop test ds1-loop – For TN464F or TN767E or later suffix DS1 Interface circuit packs. This command is used for loopback and one-way span testing of the DS1 span. Synopsis test ds1-loop location [cpe-loopback-jack-test-begin [number-of-bits bit-pattern] | far-csu-loopback-test-begin | one-way-span-test-begin | end-loopback/span-test | inject-single-bit-error | ds1/csu-loopback-tests] Permissions Logins with the following service levels may execute this command: system...
Page 682 Maintenance Commands Parameters location A location represents the physical position of the board to be tested. For standard cabinets a location is entered as UUcSS where “UU” represents the cabinet number, “c” represents the carrier, and “SS” represents the slot position. A 1-digit cabinet (1-3) is entered with or without a leading zero (0).
Page 683 test ds1-loop If the specified board is not inserted in the system, the following message will be displayed: Board not inserted If the command entered is in conflict with another currently executing command, then a message will be displayed showing the login id of the conflicting user and the conflicting command.
Page 684 Maintenance Commands Output The responses will be displayed on a test-by-test basis with one line of data displayed for each test result. The port address (cabinet-carrier-slot-circuit) of the maintenance object Port that is being tested. The type of maintenance object that is being tested. Maintenance Name The alternate means of identifying the maintenance object.
Page 685: Test Eda-External-Device-Alrm
test eda-external-device-alrm test eda-external-device-alrm test eda-external-device-alrm all | physical-location [repeat-number | clear][ schedule] This test performs hardware diagnostic tests on the alarm port for either an individual or every external device. If all is entered, the test eda-external-device-alrm command performs a hardware diagnostic test on every administered external device’s alarm port .
Page 686 Maintenance Commands Parameters physical location In addition to entering the word “physical” the system technician must specify the physical location. For an administered external device alarm analog line port, a “physical location” represents the physical position of the port to be tested and is entered as UUcSSpp where “UU”...
Page 687 test eda-external-device-alrm Output For the following output example the command that was entered was test external-device-alarm all : test eda-external-device-alrm all TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 03major EXT-DEV CMS1 PASS 03A2102 EXT-DEV CMS2 FAIL 01major EXT-DEV...
Page 688: Test Environment
‘test maintenance’ command. See ‘test customer-alarm’ for details on testing this particular MO. NOTE: A new MO, RMC-ENV, displays when the rack mount cabinet is used for the S8700 IP Connect. 7-432 Issue 1 May 2002 555-233-143...
Page 689 Output The following display shows a typical result when test environment 1 is entered on an S8700 IP Connect system. test environment 1 Page 1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code RMC-ENV...
Page 690: Test Failed Ip-Network-Region
Maintenance Commands test failed ip-network-region test failed ip-network-region [all | xxx ] The test failed ip-network-region command initiates a real-time ping test for failed network-regions connections. The default is ALL failed ip-network regions or test failed ip-network-region xxx (where xxx is in the range of 1-250 for r and 1-80 for si/csi/d).
Page 691: Test Fiber-Link
[a-pnc | b-pnc] [short | long] [repeat# | clear] [schedule] NOTE: This command is not valid for S8700 IP Connect configurations. The test fiber-link command validates that the optical fiber connection between switch node interfaces (SNI) and expansion interfaces (EI), or a combination thereof, are administered.
Page 692 Maintenance Commands Output On critical-reliability systems (duplicated PNC) there are two fibers associated Port with every fiber link number. A-PNC B-PNC distinguish one from the other. The following display shows a typical result when test fiber-link 1 b-pnc is entered. test fiber-link 1 b-pnc TEST RESULTS Port...
Page 693: Test Firmware Download
Some tests are run concurrently to speed execution, so test results for several maintenance objects may be intermixed. Output The following shows sample results on an S8700 IP Connect system. test firmware download No active alarms Command:...
Page 694: Test Hardware-Group
Maintenance Commands test hardware-group test hardware-group [system | carrier UUC | cabinet UU | port-network PN# | pnc a-pnc | b-pnc | board UUCSS] [print | schedule] 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), circuit pack or the entire system.
Page 695 test hardware-group Hardware Alarms When a hardware error is detected by the test hardware-group command the hardware goes through the standard escalation strategy. Alarms will be raised on hardware that manifest hard errors. This alarming strategy is the same, regardless of whether the ports are translated or not. System Interaction The performance of test hardware-group is affected by call processing traffic, administration activity, choice of the short or long option, whether the...
Page 696 Maintenance Commands Specifying y causes the tests to run in the background, freeing up the Background? terminal for other tasks. Error results are logged in the error log but not displayed on the screen. This option is incompatible with the auto-page and "continuously"...
Page 697 The following display shows a typical result when test hardware-group system is entered on an S8700 IP Connect system. est hardware-group system Page 1 of TEST HARDWARE-GROUP SELECTIONS Select the desired options for the specified test.
Page 698: Test Ipserver-Interface
Maintenance Commands test ipserver-interface test ipserver-interface Uc This command performs a board test for an IPSI in the named cabinet/carrier. It tests all clock and PKTINT components. Parameters cabinet (1-44) Specify the cabinet number with the IPSI board you want to test. carrier Supply the carrier you want to test.
Page 699: Test Isdn-Testcall
test isdn-testcall test isdn-testcall test isdn-testcall group#/member# [minutes num-minutes] [schedule] The test isdn-testcall command starts an outgoing ISDN-PRI test call using the asynchronous method. Only 1 ISDN trunk in each port network can be tested at one time. The maximum number of asynchronous outgoing test calls that can be run simultaneously depends on the number of Maintenance/Test circuit packs in the system.
Page 700: Test Journal-Printer
Maintenance Commands test journal-printer test journal-printer pms-log | wakeup-log [short | long] [repeat-number| clear] [schedule] The test journal-printer command performs hardware diagnostics on the link between the switch and a specified journal printer link to either the PMS-log printer or the wakeup-log printer. Parameters One of the two journal printers must be specified: pms-log...
Page 701: Test Led
test led test led test led [all | cabinet UU | port-network PN# | switch-node SN# | a-pnc | b-pnc] [repeat#] This command verifies that a specified cabinet, port network, PNC or switch node is recognized by the system. It is also useful for identifying a port network, cabinet, or PNC (A or B).
Page 702: Test Link
Links form. Display communication-interface links shows the location and identification of each link. Output The following display shows a typical result when test link 1 long is entered for an S8700 IP Connect system. test link 1 long TEST RESULTS Port Maintenance Name Alt.
Page 703: Test License
System MSP feature is active on the switch, and the customer superuser login is administered on the permissions form. This command is available for both S8700 Multi-Connect and S8700 IP Connect configurations. The [long] parameter is not available for the S8700 media server configurations.
Page 704: Test Maintenance
[C] [short | long] [repeat# | clear] [schedule] NOTE: This command is not valid for S8700 IP Connect configurations. The test maintenance command performs hardware diagnostic tests on the PN’s Maintenance circuit packs. For a PN’s Maintenance circuit pack, the MT interface, EI link, reset, and sanity functions are tested.
Page 705: Test Packet-Interface
test packet-interface test packet-interface test packet-interface [Uc] [short | long] [repeat# |clear] [schedule] This command performs hardware diagnostic tests on any or all of the Packet Interface circuit packs in a specified carrier. Tests performed include local memory checksum tests, loop-around tests, and checks of failure counters. The Maintenance Loop-Around test (#886) is included in the test sequences of active packet-interface circuit packs only.
Page 706 Maintenance Commands Output test packet-interface 2a TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code PKT-INT PASS PKT-INT PASS Command successfully completed Command: Field Descriptions A port network number (1 – 44). Port The name of maintenance object being tested. Maintenance Name Not applicable.
Page 707: Test Pkt
test pkt test pkt The test runs a series of tests on the packet bus of the specified PN. Table 7-57. test pkt command parameters Action/ Feature Object Qualifier Qualifier Description Permissions Defaults Interactions test pkt The packet bus to be tested: init Test none...
Page 708 Maintenance Commands WARNING: Since the clear long option clears every counter if the test passes, it is possible for firmware counters to be cleared even though a problem exists. In some cases customer service might degrade since calls may be routed over defective equipment.
Page 709: Test Signaling-Group
test signaling-group test signaling-group test signaling-group group# [short | long] [repeat# | clear][schedule] The test signaling-group validates the administration of a signaling group and runs a series of diagnostic tests on it. An ISDN-PRI signaling group is a set of B channels whose signaling messages are carried together on a designated D channel or set of D channels.
Page 710: Test Synchronization
Both long and short sequences run Test #417. If Stratum 3 synchronization is administered, an additional non-destructive test (#649) is run by the long sequence. The following screens show test results for the test synchronization command for S8700 IP Connect and S8700 Multi-Connect configurations. 7-454 Issue 1 May 2002...
Page 711 Output (for S8700 IP Connect) test synchronization all TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code SYNC PASS SYNC PASS SYNC PASS SYNC PASS SYNC PASS SYNC PASS SYNC PASS SYNC PASS SYNC PASS...
Page 712 Maintenance Commands Output (for S8700 Multi-Connect) test synchronization TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code SYNC PASS Command successfully completed 7-456 Issue 1 May 2002 555-233-143...
Page 713: Test Sys-Link
test sys-link test sys-link test sys-link UUCSSpp [channel# ] [current | faulted] [short | long] [repeat# | clear] [schedule] The test sys-link command will validate the existence of the specified link and run diagnostic tests on the hardware path that comprises the system link. If the “current”...
Page 714 Maintenance Commands Output The following display shows a typical result when test sys-link 1e0201 current is entered. test sys-link 1e0201 current Page TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01E0201 SYS-LINK PASS 01A1 PKT-INT PASS 01A1 PKT-INT PASS...
Page 715: Test Tdm
test tdm test tdm test tdm port-network PN# [short | long] [repeat# | clear] [schedule] The test tdm command performs hardware diagnostic tests on the time slots of the specified TDM bus. Both halves (“a” and “b”) of the TDM bus are tested. 555-233-143 Issue 1 May 2002 7-459...
Page 716: Test Tone-Clock
Maintenance Commands test tone-clock test tone-clock UUC [short | long] [repeat# | clear] [schedule] The test tone-clock command performs hardware diagnostic tests on the three maintenance objects on a specified IPSI or Tone-Clock circuit pack: TONE-BD, TONE-GEN, TDM-CLK. See the information on each of these MOs in Chapter 8, “Maintenance Objects.” 7-460 Issue 1 May 2002 555-233-143...
Page 717: Test Trunk
test trunk test trunk test trunk group# [/ member#] [short | long] [repeat# | clear] [schedule] The test trunk command performs hardware diagnostic tests on an entire trunk group or an individual trunk-group member, depending on the options entered. 555-233-143 Issue 1 May 2002 7-461...
Page 718: Test Tsc-Administered
Maintenance Commands test tsc-administered test tsc-administered signaling-group# / tsc-index [repeat#] [schedule] The test tsc-administered command runs diagnostic tests on any type of administered TSCs (Temporary Signaling Connections) on a signaling group. A switched services request to run the TSC heartbeat test is also performed. 7-462 Issue 1 May 2002 555-233-143...
Page 719: Traceroute
(*), which indicates a timeout condition. 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 server switch is connected.
Page 720 Maintenance Commands Table 7-58. traceroute command parameters Action/ Feature Object Qualifier Qualifier Description Permissions Defaults Interactions traceroute ip-address where IP address is init Primary None www.xxx.yyy.zzz inads craft node-name from node-name form customer board cabinet-carrier-slot address of the IP circuit pack clan-port port 1-17...
Page 721 traceroute Output The following shows an example output for the C-LAN traceroute command. For Medpro boards, the clan-port (1-17) qualifier does not appear. traceroute ip-address 135.9.1.22 board 1C14 traceroute ip-address 135.9.1.22 board 1C14 clan-port (1-17) clan-port (1-17) TRACE ROUTE RESULTS TRACE ROUTE RESULTS Time(ms) Time(ms)
Page 722 Maintenance Commands 7-466 Issue 1 May 2002 555-233-143...
Page 723: Maintenance-Object Repair Procedures
Maintenance-Object Repair Procedures NOTE: This chapter does not contain maintenance objects (MOs) for the DEFINITY Wireless Business System (DWBS). Refer to the appropriate maintenance documentation that accompanies DWBS products. 555-233-143 Issue 1 May 2002...
Page 724: Escalation Procedures
Maintenance-Object Repair Procedures Escalation Procedures This document is not intended to solve all levels of trouble. When the limits of these procedures have been reached and the problem has not been resolved, it is the technician’s responsibility to escalate to a higher level of technical support. Escalation should conform to the procedures in the Technical and Administration Plan.
Page 725: Abri-Port (Asai Isdn-Bri Port)
ABRI-PORT (ASAI ISDN-BRI Port) ABRI-PORT (ASAI ISDN-BRI Port) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ABRI-PORT MAJOR test port UUCSSpp l ASAI ISDN-BRI port MINOR WARNING The alarm level for ABRI ports may be administered using the set options command. The alarm level can be set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ABRI port in the system.
Page 726: Ac-Power
AC Power UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). S8700 Multi-Connect systems support two different cabinet types as EPNs: multicarrier cabinets and single-carrier cabinets. Both types may be powered by either an AC or DC power source. Environmental maintenance differs according to a cabinet’s type and its power supply.
Page 727 AC-POWER Nominal Power Holdover Multicarrier Cabinets Two types of battery holdover are available: The small battery assembly provides short-term battery holdover. If AC power fails, 48 VDC batteries power the system for: — 15 seconds in an EPN cabinet — 10 minutes in the expansion control carrier in the “A” position of an EPN cabinet Some AC-powered multicarrier cabinets (MCCs) contain three 48-Volt batteries and a battery charger (397C) to provide backup power in case...
Page 728 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order shown in the table below. For example, by clearing error codes associated with the Battery and Battery Charger Query test (#5), you may also clear errors from other tests in the testing sequence. Refer to the appropriate sections of this chapter for descriptions of each test.
Page 729 AC-POWER AC Power Query Test (#78) This test queries either the server’s watchdog (via an Ethernet or USB interface) or an MCC EPN’s Maintenance circuit pack for status of the cabinet’s AC power. Table 8-2. Test #78 Power Query Test Error Test Code...
Page 730 Maintenance-Object Repair Procedures Table 8-2. Test #78 Power Query Test — Continued Error Test Code Result Description / Recommendation FAIL 2. Procedures for a J58890CE: (Cont’d) The cabinet is currently without AC power. 1. Check for AC power at the wall outlet (99–127 or 200–250 VAC). If AC power is absent, then the problem is not with the system itself.
Page 731 ‘‘CARR-POW (Carrier Power Supply)’’ on page 8-393. S8700 Multi-Connect supports three different cabinet types for EPNs: multicarrier cabinets (MCCs), single-carrier cabinets (SCCs), and 19-inch rack mounted cabinets. Every type may be powered by either an AC or DC power source.
Page 732 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the AC Power Query test (#78), you may also clear errors generated from other tests in the testing sequence. Refer to the appropriate sections of this chapter for descriptions of each test.
Page 733 AC-POWER AC Power Query Test (#78) This test is not valid for DC-powered cabinets and should always abort or pass. Table 8-4. Test #78 Power Query Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run test are not available. 100, ABORT Response to the test request was not received within the allowable time period.
Page 734: Adm-Conn (Administered Connection)
Maintenance-Object Repair Procedures ADM-CONN (Administered Connection) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ADM-CONN MAJOR, MINOR, status administered-connection N Administered or WARNING Connection Where N is an administered connection number indicated in the PORT field of the Alarm or Error Log. An administered connection provides an end-to-end connection between two access endpoints or data modules residing in either the same switch or different switches.
Page 735 ADM-CONN (Administered Connection) Table 8-5. Administered Connection Error Log Entries — Continued Associated Alarm On/Off Test to Clear Error Type Data Test Level Board Value 17 (e) None None 18, or 102 (f) None None 22 (a, g) None None 34, 42, 44, or 58 (h) None None...
Page 736 Maintenance-Object Repair Procedures d. The exact failure cause is unknown or has been mapped to one of these values. If this is a permanent condition, try reversing the direction of the Administered Connection (originate the administered connection from the destination switch). This may yield another failure cause. e.
Page 737: Adx8D-Bd (Audix Circuit Pack)
ADX8D-BD (AUDIX Circuit Pack) ADX8D-BD (AUDIX Circuit Pack) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ADX8D-BD MINOR or test board UUCSS sh AUDIX circuit pack WARNING UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 738: Adx8D-Pt (Audix Digital Port)
Maintenance-Object Repair Procedures ADX8D-PT (AUDIX Digital Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ADX8D-PT MINOR test port UUCSSpp l AUDIX digital port ADX8D-PT WARNING test port UUCSSpp sh AUDIX digital port UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 739 ADX8D-PT (AUDIX Digital Port) Error Log Entries and Test to Clear Values Table 8-6. EMBEDDED AUDIX Digital Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 40987 None...
Page 740 Maintenance-Object Repair Procedures d. The port is busied-out by command. You can release the port via the release port UUCSSpp command. e. The circuit pack is administered but not physically installed. The alarm will clear when a circuit pack is inserted. f.
Page 741 ADX8D-PT (AUDIX Digital Port) NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The following tests 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 742 Maintenance-Object Repair Procedures Table 8-7. Test #9 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation 1001 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABORT The system could not allocate time slots for the test.
Page 743 ADX8D-PT (AUDIX Digital Port) Voice and Control Channel Local Loop Test (#13) This test checks the information and control channels between a server and the EMBEDDED AUDIX port circuit. First, the primary information (voice) channel loop back test is run. While the primary information channel is still looped around, the Control Channel Looparound test is performed.
Page 744 Maintenance-Object Repair Procedures Table 8-8. Test #13 Voice and Control Channel Local Loop 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 745 ADX8D-PT (AUDIX Digital Port) Table 8-8. Test #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description / Recommendation PASS Voice and Control Channel Local Loop test passed. Every channel is transmitting properly. 1. To be sure that this is not an intermittent problem, repeat this test up to 10 times, and see whether it continues to pass.
Page 746: Adx16D-B (16-Port Audix Circuit Pack)
Maintenance-Object Repair Procedures ADX16D-B (16-Port AUDIX Circuit Pack) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ADX16D-B MINOR test board UUCSS sh AUDIX circuit pack ADX16D-B WARNING test board UUCSS sh AUDIX circuit pack UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 747: Adx16A-Bd (Audix Circuit Pack)
ADX16A-BD (AUDIX Circuit Pack) ADX16A-BD (AUDIX Circuit Pack) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ADXCL-BD or MINOR, or test board UUCSS sh AUDIX circuit pack \ADX16A-BD WARNINGS UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 748: Adx16D-P (16-Port Audix Digital Port)
Maintenance-Object Repair Procedures ADX16D-P (16-Port AUDIX Digital Port) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ADX16D-P MINOR or test port UUCSSpp l AUDIX Digital port WARNINGS UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 749 ADX16D-P (16-Port AUDIX Digital Port) Error Log Entries and Test to Clear Values Table 8-9. EMBEDDED AUDIX Digital Port 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) 40987 None...
Page 750 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, reseat or replace the AUDIX circuit pack (see caution at the beginning of this section).
Page 751 ADX16D-P (16-Port 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 tests always return PASS. Electronic Power Feed test (#11) Station Lamp Updates test (#16) Station (Digital) Audits test (#17) Digital Terminal Remote Looparound test (#1201)
Page 752 Maintenance-Object Repair Procedures Table 8-10. 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 active. 1. Use the display port UUCSSpp command to determine the voice port extension of the port.
Page 753 ADX16D-P (16-Port AUDIX Digital Port) Table 8-10. Test #9 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation PASS The port is using its allocated time slots correctly. 1. To verify that this is not an intermittent problem, repeat this test up to 10 times, and make sure it continues passing.
Page 754 Maintenance-Object Repair Procedures Table 8-11. Test #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description / Recommendation 1001 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABORT The system could not allocate time slots for the test.
Page 755 ADX16D-P (16-Port AUDIX Digital Port) Table 8-11. Test #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description / Recommendation None FAIL The test failed for reasons external to the AUDIX. 1. Run circuit pack tests to check the IPSI Tone Generator circuit or Tone Generator circuit pack and the IPSI Tone Detector circuit or Tone Detector circuit pack using test board UUCSS s.
Page 756: Adx16A-Pt (Audix Analog Line/Control Link)
Maintenance-Object Repair Procedures ADX16A-PT (AUDIX Analog Line/Control Link) MO’s Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ADXCL-PT or MINOR test port UUCSSpp l AUDIX Analog Line/ Control Link ADX16A-PT ADXCL-PT or WARNING test port UUCSSpp sh AUDIX Analog Line/ Control Link ADX16A-PT UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 757 ADX16A-PT (AUDIX Analog Line/Control Link) Error Log Entries and Test to Clear Values Table 8-12. EMBEDDED AUDIX Analog Line/Control Link Error Log Entries Error On/Off Type Data Associated Test Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 40977 None...
Page 758 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the Looparound test (#161), you may also clear errors generated from other tests in the testing sequence. Short Test Long Test Order of Investigation...
Page 759 ADX16A-PT (AUDIX Analog Line/Control Link) Table 8-13. Test #6 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 busy with a valid call. 1.
Page 760 Maintenance-Object Repair Procedures Table 8-13. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation FAIL The NPE of the tested port was found to be transmitting in error. This causes noisy and unreliable connections. 1. Replace the circuit pack. PASS The port is correctly using its allocated time slots.
Page 761 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 8-14. Test #7 Conference Circuit Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test.
Page 762 Maintenance-Object Repair Procedures Loop-Around Test (#161) This test is designed to check the on-board transmission capabilities of the NPE on the analog port. Table 8-15. Test #161 Loop-Around Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources for this test. 1.
Page 763 ADX16A-PT (AUDIX Analog Line/Control Link) Table 8-15. Test #161 Loop-Around Test — Continued Error Test Code Result Description / Recommendation FAIL The reflective loop-around test failed. This causes noisy or unreliable connections or other users calling this port may hear an echo. 1.
Page 764: Alarm-Pt (Alarm Port)
Maintenance-Object Repair Procedures ALARM-PT (ALARM PORT) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ALARM-PT MINOR test port UUCSSpp l Alarm-Port ALARM-PT WARNING test port UUCSSpp sh Alarm-Port UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 765 ALARM-PT (ALARM PORT) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the Battery Feed test (#35), you may also clear errors generated from other tests in the testing sequence. Short Test Long Test Order of Investigation...
Page 766 Maintenance-Object Repair Procedures Table 8-17. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate the necessary system resources to run this test. 1.
Page 767 ALARM-PT (ALARM PORT) Station Status and Translation Audits and Updates Test (#36) For an analog line port that is administered as an external alarm, this test is limited to updating the software with the switchhook state. Table 8-18. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 768: Anl-16-L (16-Port Analog Line)
Maintenance-Object Repair Procedures ANL-16-L (16-Port Analog Line) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANL-16-L MINOR test port UUCSSpp l 16-Port Analog Line ANL-16-L WARNING test port UUCSSpp sh 16-Port Analog Line UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 769 ANL-16-L (16-Port Analog Line) Error Log Entries and Test to Clear Values Table 8-19. 16-Port 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...
Page 770 Maintenance-Object Repair Procedures Call the terminal equipment and verify that the terminal rings. If the terminal does not ring, then replace it. Otherwise, issue the test port UUCSSpp command, and follow the procedure for Test #48. Aux Data 40977 indicates that no terminal equipment was connected when ringing was attempted.
Page 771 ANL-16-L (16-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 executes in about 20 to 30 seconds.
Page 772 Maintenance-Object Repair Procedures Table 8-20. Test #6 NPE Crosstalk 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 773 ANL-16-L (16-Port Analog Line) Table 8-20. 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). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 774 Maintenance-Object Repair Procedures Table 8-21. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. 1. Use the display port UUCSSpp command to determine the station extension.
Page 775 ANL-16-L (16-Port Analog Line) Table 8-21. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation PASS The port can correctly conference multiple connections. User-reported troubles on this port should be investigated by using other port tests and by examining station, trunk, or external wiring.
Page 776 Maintenance-Object Repair Procedures Table 8-22. Test #35 Battery Feed Test Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABORT System resources required to run this test are not available.
Page 777 ANL-16-L (16-Port Analog Line) Table 8-22. 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 778 Maintenance-Object Repair Procedures Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 8-23. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 779 ANL-16-L (16-Port Analog Line) Table 8-23. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description / Recommendation FAIL The translation update failed. There may be an internal software error. The ringer update was not performed because of this failure. FAIL This does not indicate a hardware problem.
Page 780 Maintenance-Object Repair Procedures Station Present Test (or Ringing Application Test) (#48) This test applies momentary ringing voltage to the terminal equipment and monitors resulting current flow to determine whether terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 781 ANL-16-L (16-Port Analog Line) Table 8-24. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate necessary system resources to run this test. 1.
Page 782 Maintenance-Object Repair Procedures Loop-Around 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 8-25.
Page 783 ANL-16-L (16-Port Analog Line) Table 8-25. Test #161 Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1018 ABORT The test has been disabled by administration. 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 customer or terminal disturbing).
Page 784 Maintenance-Object Repair Procedures Table 8-25. Test #161 Loop-Around 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, or by examining the station.
Page 785: Anl-24-L (24-Port Analog Line)
ANL-24-L (24-Port Analog Line) ANL-24-L (24-Port Analog Line) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANL-24-L MINOR test port UUCSSpp l 24-Port Analog Line ANL-24-L WARNING test port UUCSSpp sh 24-Port Analog Line UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 786 Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 8-26. 24-Port Analog Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1(a) 40960 none 40975 40977...
Page 787 ANL-24-L (24-Port Analog Line) Aux Data 40975 indicates that the terminal equipment was on-hook when ring-tip was detected during ringing. This usually indicates a failure in the terminal equipment or the type of terminal has a low ringer impedance. Call the terminal equipment and verify that the terminal rings. If the terminal does not ring, then replace it.
Page 788 Maintenance-Object Repair Procedures NPE Crosstalk Test (#6) This test verifies that this port’s NPE channel talks on the selected time slot and never crosses over to time slots reserved for other connections. If the NPE is not working correctly, 1-way and noisy connections may be observed. This test is usually part of the long test sequence and executes in about 20 to 30 seconds.
Page 789 ANL-24-L (24-Port Analog Line) Table 8-27. Test #6 NPE Crosstalk 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 790 Maintenance-Object Repair Procedures Table 8-27. 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). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 791 ANL-24-L (24-Port Analog Line) Table 8-28. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation 1004 ABORT The port was seized by a valid call during the test. The test has been aborted. 1. Use the display port UUCSSpp command to determine the station extension.
Page 792 Maintenance-Object Repair Procedures Table 8-28. Test #7 Conference Circuit Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 793 ANL-24-L (24-Port Analog Line) Table 8-29. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call. This result is also reported for the system’s Music-On-Hold port when it is off-hook, which it usually is.
Page 794 Maintenance-Object Repair Procedures Table 8-29. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation 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. If touch-tones are inoperative on this station, then replace the circuit pack because this port is inoperative.
Page 795 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 8-30. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 796 Maintenance-Object Repair Procedures Table 8-30. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description / Recommendation FAIL This may be an internal software error. The message waiting lamp update failed. The translation and ringer updates were not performed because of this failure.
Page 797 ANL-24-L (24-Port Analog Line) Station Present Test (or Ringing Application Test) (#48) This test applies momentary ringing voltage to the terminal equipment and monitors resulting current flow to determine whether terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 798 Maintenance-Object Repair Procedures Table 8-31. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. 2100 ABORT Could not allocate necessary system resources to run this test. 1.
Page 799 ANL-24-L (24-Port Analog Line) Loop-Around 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 8-32.
Page 800 Maintenance-Object Repair Procedures Table 8-32. Test #161 Loop-Around Test — Continued Error Test Code Result Description / Recommendation 1018 ABORT The test has been disabled by administration. 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, that can be customer or terminal disturbing).
Page 801 ANL-24-L (24-Port Analog Line) Table 8-32. Test #161 Loop-Around Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 802: Anl-Bd (Analog Line Circuit Pack)
Maintenance-Object Repair Procedures ANL-BD (Analog Line Circuit Pack) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name Of MO ANL-BD MINOR test board UUCSS sh 16-Port Neon Analog Line circuit pack WARNING UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 803: Anl-Line, Anl-Ne-L (8-Port Analog Line)
ANL-LINE, ANL-NE-L (8-Port Analog Line) ANL-LINE, ANL-NE-L (8-Port Analog Line) MO’s Name Alarm (in Alarm Log Level Initial Command To Run Full Name of MO ANL-LINE MINOR test port UUCSSpp l 8-Port Analog Line ANL-LINE WARNING test port UUCSSpp sh 8-Port Analog Line ANL-NE-L MINOR...
Page 804 Maintenance-Object Repair Procedures Hardware Error Log Entries and Test to Clear Values Table 8-33. 8-Port Analog Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1 (a) 40960 None 40977...
Page 805 ANL-LINE, ANL-NE-L (8-Port Analog Line) Call the terminal equipment and verify that the terminal rings. If the terminal doesn’t ring, then replace it. Otherwise, issue the test port UUCSSpp command, and follow the procedure for Test #48. Aux Data 40977 indicates that no terminal equipment was connected when ringing was attempted.
Page 806 Maintenance-Object Repair Procedures NPE Crosstalk Test (#6) One or more NPEs (Network Processing Elements) reside on each circuit pack with a TDM-bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis. 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 807 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-34. 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 UUCSSpp command to determine the station extension.
Page 808 Maintenance-Object Repair Procedures Table 8-34. Test #6 NPE Crosstalk Test — Continued Error Test Code Result Description / Recommendation FAIL This test can fail due to either on- or off-board problems. Off-board problems of concern include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults associated with the Tone Detectors/Tone Generators.
Page 809 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-35. Test #35 Battery Feed Test Results Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1000 ABORT System resources required to run this test are not available.
Page 810 Maintenance-Object Repair Procedures Table 8-35. Test #35 Battery Feed Test Results — Continued Error Test Code Result Description / Recommendation 1392 ABORT This port is currently a TTI port and the test will not execute on it. 1. Verify that the port is a TTI port using either the display port command (the display shows that the port is a TTI port) or the list config command (the display shows a for the port).
Page 811 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-35. Test #35 Battery Feed Test Results — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 812 Maintenance-Object Repair Procedures Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations (such as station type, dial type, network connection) with information kept in the software. The software is updated with the switchhook state reported by the port processor.
Page 813 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-36. 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 814 Maintenance-Object Repair Procedures Table 8-36. Test #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 815 ANL-LINE, ANL-NE-L (8-Port Analog Line) The noise test is performed by filtering out the tone, and then measuring inherent port noise. NOTE: This loop-around test is sensitive to the length of the loop, the equipment in the loop, or the equipment terminating the loop, such as off-premises stations.
Page 816 Maintenance-Object Repair Procedures Table 8-37. 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 up to 5 times. ABORT The port was seized by a user for a valid call.
Page 817 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-37. Test #47 Loop Around and Conference Test — Continued Error Test Code Result Description / Recommendation 1005 ABORT The test was aborted due to a configuration problem. This code occurs under either of the following conditions: This test may not be applicable, or it may be disruptive to terminal equipment other than a voice terminal (for example, a modem pool member or music on hold).
Page 818 Maintenance-Object Repair Procedures Table 8-37. Test #47 Loop Around and Conference Test — Continued Error Test Code Result Description / Recommendation FAIL The conference test or the noise test failed. This could cause noisy or unreliable connections, or users calling this port may hear an echo. The problem can also be off-board, as described below.
Page 819 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-37. 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 820 Maintenance-Object Repair Procedures Station Present Test (or Ringing Application Test) (#48) This test provides a burst of ringing current to the terminal equipment and detects that current flows. This test is to ascertain whether or not terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 821 ANL-LINE, ANL-NE-L (8-Port Analog Line) Table 8-38. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation 1005 ABORT The test was aborted due to a configuration problem. This code occurs under either of the following conditions: 1.
Page 822 Maintenance-Object Repair Procedures Table 8-38. 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. Remotely test the equipment. 2.
Page 823: An-Ln-Pt (Analog Line Port)
AN-LN-PT (Analog Line Port) AN-LN-PT (Analog Line Port) MO’s Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO AN-LN-PT MINOR test port UUCSSpp l Analog Line port AN-LN-PT WARNING test port UUCSSpp sh Analog Line port UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC).
Page 824 Maintenance-Object Repair Procedures Error log entries and test to clear values Table 8-39. Analog line error log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1(a) 40960 none 40975 40977 15(b)
Page 825 AN-LN-PT (Analog Line Port) 40977 indicates that no terminal equipment was connected when ringing was attempted. 1. Run the short test via the test port UUCSSpp command, and follow the procedure for the results of Test #48. b. Error Type 15: this is a software audit error that does not indicate any hardware malfunction.
Page 826 Maintenance-Object Repair Procedures 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, 1-way and noisy connections may be observed. This test is usually part of the long test sequence and executes in about 20 to 30 seconds.
Page 827 AN-LN-PT (Analog Line Port) Table 8-40. Test #6 NPE Crosstalk 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 828 Maintenance-Object Repair Procedures Table 8-40. 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). This result could BOARD be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 829 AN-LN-PT (Analog Line Port) Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested correctly performs the conferencing function. Table 8-41. Test #7 Conference Circuit Test Error Test Code Result Description / Recommendation ABORT Necessary system resources could not be allocated to run this test.
Page 830 Maintenance-Object Repair Procedures Table 8-41. 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 831 AN-LN-PT (Analog Line Port) Battery Feed Test (or Port Diagnostic Test) (#35) The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing, transmission, and balance. This test checks the signaling and switchhook capabilities of the battery feed chip by terminating the port, applying battery power, and detecting the resulting current.
Page 832 Maintenance-Object Repair Procedures Table 8-42. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation 1392 ABORT This port is currently a TTI port and the test does not execute on it. 1. Verify that the port is a TTI port: Enter the display port UUCSSpp command (the display shows that the port is a TTI port).
Page 833 AN-LN-PT (Analog Line Port) Table 8-42. Test #35 Battery Feed Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This result could BOARD be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 834 Maintenance-Object Repair Procedures Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 8-43. Test #36 Station Status and Translation Audits and Updates Error Test Code...
Page 835 AN-LN-PT (Analog Line Port) Table 8-43. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description / Recommendation FAIL The switchhook audit failed. This result does not indicate a hardware problem. The other updates were not performed because of this failure. This may occur if the audit is performed at the same time the terminal equipment goes off-hook.
Page 836 Maintenance-Object Repair Procedures Station Present Test (or Ringing Application Test) (#48) This test applies momentary ringing voltage to the terminal equipment and monitors resulting current flow to determine whether terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 837 AN-LN-PT (Analog Line Port) Table 8-44. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation 1008 ABORT A ringing circuit could not be allocated. Either every ringing circuit is active, the ringing generator is defective, or it is incorrectly wired. 1.
Page 838 Maintenance-Object Repair Procedures Table 8-44. Test #48 Station Present Test — Continued Error Test Code Result Description / Recommendation PASS The station is connected properly to the switch. Investigate user-reported troubles on this port by running other port tests, by examining station wiring, or by inspecting the station.
Page 839 AN-LN-PT (Analog Line Port) Loop-Around 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 8-45.
Page 840 Maintenance-Object Repair Procedures Table 8-45. Test #161 Loop-Around 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 841 AN-LN-PT (Analog Line Port) Table 8-45. Test #161 Loop-Around Test — Continued Error Test Code Result Description / Recommendation The test could not relate the internal ID to the port (no board). This result could BOARD be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
Page 842: Ann-Bd (Announcement Circuit Pack)
Maintenance-Object Repair Procedures ANN-BD (Announcement Circuit Pack) MO’s Name (in Alarm Alarm Initial Command to Log) Level Full Name of MO ANN-BD MINOR test board UUCSS l Announcement circuit pack ANN-BD WARNING test board UUCSS l Announcement circuit pack UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 843 ANN-BD (Announcement Circuit Pack) Whenever new announcements are recorded on the circuit pack, save them on disk as soon as possible to ensure that they will not be lost due to a disruption. Periodic saves to removable media provide further backup if the disk files are lost or corrupted.
Page 844 Maintenance-Object Repair Procedures Saving and Restoring Announcements Integrated announcements on the announcement circuit pack can be uploaded to the system removable media or disk with the save announcements command. Likewise, integrated announcements can be downloaded to the announcement circuit pack with the restore announcements command. Both commands require a free system port, an announcement data module administered on the announcement circuit pack and, if saving to removable media, a non-write protected removable media cartridge in the removable media drive.
Page 845 ANN-BD (Announcement Circuit Pack) Error Log Entries and Test to Clear Values Table 8-46. Announcement Circuit Pack Error Log Entries Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value test board UUCSS sh r 1 1(a) Circuit pack removed or MINOR SAKI test (#53)
Page 846 Maintenance-Object Repair Procedures Table 8-46. Announcement Circuit Pack Error Log Entries — Continued Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 2817(j) Announcement MINOR test board UUCSS sh r 3 Checksum test (#209) 17682 In-line Error 1769(j) In-line Error 3840(l)
Page 847 ANN-BD (Announcement Circuit Pack)  e. Error Type 257 This error indicates transient communication problems with this circuit pack. This error is not service-affecting and no action is required.  f. Error Type 513 This error, when reported with Aux Data in the range of 4352 to 4358, indicates the circuit pack has reported a hardware failure on the circuit pack.
Page 848 Maintenance-Object Repair Procedures k. A transient error that does not cause an alarm can occasionally occur during a server, TDM BUS, or Tone-Clock interchange. Error Type  2049 It is possible for a marginal Tone-Clock circuit pack to cause this error against the ANN-BD without alarming the TONE-BD.
Page 849 ANN-BD (Announcement Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. For example, by clearing error codes associated with the Control Channel Looparound test (#52), you may also clear errors generated from other tests in the testing sequence.
Page 850 Maintenance-Object Repair Procedures Angel-Speech Processor Handshake Test (#208) This test checks the integrity of the communication link between the two processors on the Announcement circuit pack. CAUTION: Failure of this test indicates that the Speech Processor is insane and results in the loss of every integrated announcement on the circuit pack.
Page 851 ANN-BD (Announcement Circuit Pack) Announcement Checksum Test (#209) In this test, the Speech Processor calculates a global checksum covering the entire announcements file and compares it to a stored one. If the comparison of any announcement’s checksum fails, then the total number of defective announcements found is reported.
Page 852 Maintenance-Object Repair Procedures Table 8-48. Test #209 Announcement Checksum Test — Continued Error Test Code Result Description / Recommendation 0–256 FAIL The error code for this result gives the total number of defective announcements found in speech memory. When Test #209 fails with error code 0, the global checksum failed on the board, but no individual checksum failed.
Page 853 ANN-BD (Announcement Circuit Pack) Locked Announcement Circuit Pack The announcement circuit pack can exhibit a rare “locked” condition that renders two of its ports unusable by software. One of these ports is the record port, thus preventing any recording of announcements or execution of the save/restore announcements commands.
Page 854 Maintenance-Object Repair Procedures Table 8-49. Test #210 140AY Loop-Around Test Error Test Code Result Description / Recommendation 1–3 ABORT Response to the test request was not received within the allowable time period. The error code indicates at which speech compression rate the test aborted (1 being the first rate tested, 3 being the last).
Page 855 ANN-BD (Announcement Circuit Pack) Table 8-49. Test #210 140AY Loop-Around Test — Continued Error Test Code Result Description / Recommendation 2007 ABORT The Announcement circuit pack thinks that Port 1 or Port 9 is busy. 1. Retry the command at 1-minute intervals up to 5 times. 2.
Page 856 Maintenance-Object Repair Procedures Super Frame Match Inquiry Test (#211) The super frame is a means by which the Speech Processor (SP) synchronizes with the 140AY device on the announcement circuit pack. If the super frame is not synchronized, the SP will not be able to properly process record/playback requests.
Page 857 ANN-BD (Announcement Circuit Pack) Table 8-51. Test #212 Clock Match Inquiry Test Error Test Code Result Description / Recommendation 2000 ABORT Response to the test was not received within the allowable time period. If Error Type 1538 is present in the Error Log, follow the procedure for that error. 2100 ABORT Could not allocate the necessary system resources to run this test.
Page 858: Ann-Pt (Announcement Port)
Maintenance-Object Repair Procedures ANN-PT (Announcement Port) MO’s Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ANN-PT MINOR test port UUCSSpp l Announcement port ANN-PT WARNING test port UUCSSpp l Announcement port UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC). C is the carrier designation (A, B, C, D, or E).
Page 859 ANN-PT (Announcement Port) Error Log Entries and Test to Clear Values Table 8-52. Announcement Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port UUCSSpp sh r 1 PSMA (Playback MINOR test port UUCSSpp sh r 3 Speech Memory Array) test (#206)
Page 860 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. For example, by clearing error codes associated with the CAMA (Channel Administration Memory Array) test (#205), you may also clear errors generated from other tests in the testing sequence.
Page 861 ANN-PT (Announcement Port) Table 8-53. Test #205 CAMA (Channel Administration Memory Array) Test — Continued Error Test Code Result Description / Recommendation FAIL Test failed. Announcements played back on this port may sound corrupted. 1. Reset the circuit pack using the reset board UUCSS command and then run this test again.
Page 862 Maintenance-Object Repair Procedures Playback Speech Memory Array (PSMA) Test (#206) The PSMA test checks the integrity of a playback channel’s interface to the speech memory and the TDM Bus. This test is very important. It is the only test that actually checks an announcement port’s ability to play back an announcement on the TDM Bus.
Page 863 ANN-PT (Announcement Port) Table 8-54. Test #206 PSMA (Playback Speech Memory Array) Test — Continued Error Test Code Result Description / Recommendation 1 to FAIL Test failed. The error code indicates the number of byte count errors found by the Tone Detector. 1.
Page 864 Maintenance-Object Repair Procedures 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 of a particular channel. If a channel is insane, announcements cannot be played back on that channel. Table 8-55.
Page 865 ANN-PT (Announcement Port) Announcement Board Locked Condition The Announcement circuit pack can exhibit a condition that does not allow recording. If the circuit pack gets locked into this state (this is an extremely rare condition), two of the announcement ports on the circuit pack (one of which is the record port) will be unusable by software.
Page 866: Asai-Bd (Multi-Application Platform Board)
Maintenance-Object Repair Procedures ASAI-BD (Multi-Application Platform Board) MO’s Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO ASAI-BD MINOR test board UUCSS pp ASAI-BD ASAI-BD WARNING test board UUCSS pp ASAI-BD Where UU is the universal cabinet number (1–64 for ATM PNC, 1–44 for CSS PNC); C is the carrier designation (A, B, C, D, or E);...
Page 867 Yellow and green change requests the MAPD receives from the switch drive LCD behavior rather than LED behavior. The S8700 Multi-Connect system continues to send the same LED control messages to the MAPD that the system currently sends to every other port board.
Page 868: Asai-Ept
ASAI adjunct 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 869 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. 555-233-143 Issue 1 May 2002...
Page 870 Maintenance-Object Repair Procedures Aux Data Timer Type First T303 (SETUP timer) Second T303 (SETUP timer) T305 (DISConnect timer) First T308 (RELease timer) Second T308 (RELease timer) T316 (RESTart timer) T309 (Layer-2 Failure timer) TM100 (Management Information message Timer 1) TM200 (Management Information message Timer 2) TASAI (ASAI Routing Timer) The switch sent a message to an endpoint that did not respond in the allotted time.
Page 871 ASAI-EPT 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 872 Maintenance-Object Repair Procedures j. This occurs when the point-to-point signaling link to the endpoint goes down, except when the link goes down because either a system technician has busied out the PKT-CTRL or the PKT-BUS, or they have failed. This error raises an alarm against the endpoint or adjunct.
Page 873 ASAI-EPT Table 8-57. ASAI Cause Values — Continued Code Explanation Recommendation No circuit or A resource on the switch is unavailable for a call. For BRI endpoints, channel this cause value is not logged. For ASAI, this condition means that available there are no available trunks for an outgoing call request.
Page 874 Maintenance-Object Repair Procedures Table 8-57. ASAI Cause Values — Continued Code Explanation Recommendation Service or Requested ASAI capability or resource is not available on the switch or option not adjunct. More than one adjunct may be contending for the same switch available resource.
Page 875 ASAI-EPT System Technician-Demanded Tests: Descriptions and Error Codes When inspecting errors in the system, always investigate errors associated with the circuit pack and port first. Clearing these error codes first may also clear errors generated against the endpoint. When every circuit pack and port error has been cleared, but errors still exist against the endpoint, investigate errors in the table below.
Page 876 Maintenance-Object Repair Procedures Table 8-58. Test #626 Signaling Link Status Test Error Test Code Result Description / Recommendation 1139 ABORT The EPN’s packet bus is out-of-service. 1. Follow the repair procedures for the packet bus. 2. After completing step 1, execute the test port long UUCSSpp command and review the results of the BRI Port Local LAN Looparound test (#618) to verify the repair.
Page 877: Asai-Pt
ASAI-BD on the TN800 circuit pack. The TN800 circuit pack is a PC-based platform that allows interaction of multiple applications with an S8700 Multi-Connect system. MultiVantage software (Native mode) supports emulation of three types of port MOs on this board. The type of ports to be emulated are defined by the applications running on the TN800.
Page 878 Maintenance-Object Repair Procedures Error Log Entries and Test to Clear Values Table 8-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 UUCSSpp sh r 1 1 (a) Level 1 Status MAJOR test port UUCSSpp sh r 2...
Page 879 ASAI-PT c. The port received an invalid frame over the D channel. When the CRC (cyclical redundancy check) 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 880 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following tables when inspecting errors in the system. For example, by clearing error codes associated with the ASAI Port Local LAN Looparound test (#618), you may also clear errors generated from other tests in the testing sequence.
Page 881 ASAI-PT PACKET INTERFACE PACKET BUS ..BRI LINE CIRCUIT PACK Figure 8-2. BRI Port Local LAN Loop-Around Path Table 8-61. 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.
Page 882 Maintenance-Object Repair Procedures Table 8-61. Test #618 BRI Port Local LAN Looparound — Continued Error Test Code Result Description / Recommendation 1141 ABORT The PKT-CTRL is out-of-service. 1. Follow the repair procedures for the PKT-CTRL. 2. Issue the test port long UUCSSpp command and review the results of the BRI Port Local LAN Looparound test to verify the repair.
Page 883 ASAI-PT Level 1 Status Inquiry Test (#621) This test determines the state of the transmission facility of a BRI port at the Level 1 (L1) or physical layer. L1 can be in one of two possible states: Activated or Deactivated. The Activated state is the correct state for an ISDN-BRI port.
Page 884 Maintenance-Object Repair Procedures Table 8-62. Test #621 Level 1 Status Inquiry — Continued Error Test Code Result Description / Recommendation FAIL Received a status of Level 1 Deactivated; the port is out of service. 1. Issue the status bri-port UUCSSpp command to verify that the service state of the port is out-of-service.
Page 885 ASAI-PT CRC Error Counter Test (#623) This test reads and clears the BRI port’s CRC error counter maintained on the BRI-LINE circuit pack. This counter is incremented by the circuit pack when it receives a frame from the endpoint or adjunct with a bad CRC over the D channel. The test passes if the value of the counter is 0 (the error is cleared).
Page 886 Maintenance-Object Repair Procedures Layer 1 Transmission Error Counter Test (#624) This test reads and clears the BRI port’s Layer 1 Transmission error counter maintained on the ASAI circuit pack. This counter is incremented by the circuit pack when it detects a Layer 1 transmission problem. The test passes if the value of the counter is 0 (that is, the error is cleared).
Page 887 ASAI-PT Receive FIFO Error Counter Test (#625) This test reads and clears the BRI port’s Receive FIFO error counter maintained on the TN800 circuit pack. This counter is incremented by the circuit pack when it detects an overflow of its receive buffers. The test passes if the value of the counter is 0 (that is, the error is cleared).
Page 888 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 889: 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’s 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 busyout board commands abort when either is attempted on a reserved slot.
Page 890: Atm-Bch (Atm B-Channel Trunk)
Maintenance-Object Repair Procedures ATM-BCH (ATM B-Channel Trunk) MO’s Name (in Initial Command to Alarm Log) Alarm 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 ATM B-Channel Trunk...
Page 891 ATM-BCH (ATM B-Channel Trunk) Table 8-67. ATM ISDN service states Category Description Service states In-Service (INS) B channel is in normal Active A call is connected over operating state the B channel. Idle There is no call on the B channel. Out-of-Service/Far-End The switch has not successfully negotiated B-channel connection as of (OOS/FE)
Page 892 Maintenance-Object Repair Procedures B-Channel Alarms The Maintenance/Far-End and Out-Of-Service/Far-End states generate warning alarms displayed with status trunk grp#/mbr#. Table 8-68. ATM-BCH alarms by service state Service state Alarm Possible cause Possible solution Out-of-Service/NE Warning Trunk busied out Release the port (release trunk grp#/mbr#).
Page 893 ATM-BCH (ATM B-Channel Trunk) Error Log Entries and Test to Clear Values Table 8-69. 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)
Page 894 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.
Page 895 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 896 Maintenance-Object Repair Procedures System Technician-Demanded Tests: Descriptions and Error Codes Always investigate problems in the order presented in the table below. When you clear one of the error codes associated with a given test, you clear errors generated by other tests in the testing sequence. If you clear errors out of order, you can lose important information.
Page 897 ATM-BCH (ATM B-Channel Trunk) Signaling Link State Audit Test (#255) This nondestructive test checks the status of the TN230x ATM-CES Interface circuit pack and the ATM D-channel (ATM-DCH) trunk, which are both important elements to the health of the ATM-BCH trunk. Table 8-71.
Page 898 Maintenance-Object Repair Procedures Service State Audit Test (#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 every trunk service state. It queries the service state on the far end and waits 2 minutes for a reply.
Page 899 ATM-BCH (ATM B-Channel Trunk) Table 8-72. Test #256 Service State Audit Test — Continued Error Test Code Result Description / Recommendation 1116 ABORT Trunk not in Out-of-Service/Far-end state and country protocol other than 1 1117 ABORT Service-state audit message outstanding 1.
Page 900 Maintenance-Object Repair Procedures Call State Audit Test (#257) This test audits the internal call state by asking the far-end switch for the ISDN call state. The test is particularly useful when you are trying to clear a hung call. If the internal call state on the near end differs from that on the far end, the call is torn down.
Page 901 ATM-BCH (ATM B-Channel Trunk) ISDN Test Call Test (#258) This nondestructive test performs a far-end loop-around test over an ATM-BCH trunk if: The trunk is IN-SERVICE, MAINTENANCE/NEAR-END, or OUT-OF-SERVICE/NEAR-END. No calls are active on the trunk. The system uses country protocol 1 (including US), or the far end has loop-around capability.
Page 902 Maintenance-Object Repair Procedures Table 8-74. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 1020 ABORT TN230x circuit-pack problem 1. See the ‘‘ATM-INTF (TN2305/6)’’ 1024 ABORT Maintenance/Test digital port active 1. Wait until amber and green LEDs on the Maintenance/Test circuit pack are OFF.
Page 903 ATM-BCH (ATM B-Channel Trunk) Table 8-74. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 2000, ABORT Internal system error 2012, 1. Retry the command up to 5 times at 1-minute intervals. None 2035 ABORT Call timed out 1.
Page 904 Maintenance-Object Repair Procedures Table 8-74. Test #258 ISDN Test Call — Continued Error Test Code Result Description / Recommendation 2208 ABORT Internal system error 1. Retry the command at 1-minute intervals up to 5 times. 2209– ABORT Could not allocate needed resources 2210 1.
Page 905: Atm-Dch (Atm D-Channel Port)
ATM-DCH (ATM D-Channel Port) ATM-DCH (ATM D-Channel Port) MO’s Name (in Initial System Technician Alarm Log) Alarm Level Command to Run Full Name of MO 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 906 Maintenance-Object Repair Procedures Hardware Error Log Entries and Test to Clear Values Table 8-75. 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 907 ATM-DCH (ATM D-Channel Port) 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 908: Atm-Ei (Expansion Interface Circuit Pack)
This MO covers the ATM circuit pack administered as an Expansion Interface (ATM-EI) for ATM Port-Network Connectivity (ATM PNC). The ATM-EI provides PNC between a S8700 Multi-Connect server and every EPN through the ATM switch. The circuit packs listed in...
Page 909 ATM-EI (Expansion Interface Circuit Pack) LEDs The ATM Interface circuit pack has three LEDs: Red indicates some alarm condition. Green indicates maintenance testing in progress. Amber provides useful visual information regarding the operating mode of the ATM-EI and possible error conditions. The possible LED states are in Table 8-79.
Page 910 Maintenance-Object Repair Procedures Replacing an ATM-EI Circuit Pack Standard Reliability 1. Enter busyout atm pnc # (this is service-affecting) at the SAT. 2. Replace the ATM PNC circuit pack, and reconnect the fiber. 3. Enter release atm pnc. 4. Wait 2½ minutes for board insertion. 5.
Page 911 Basic ATM PNC Administration NOTE: This section contains basic administration information only. Refer to ATM Installation, Upgrades, and Administration for Avaya MultiVantage Solutions for more detailed information. ATM PNC connections involve administering 1 ATM-EI board in each EPN (standard, duplex, or high reliability)
Page 912 Maintenance-Object Repair Procedures Critical Reliability 1. Enter status pnc, and ensure that the A-PNC is active. If not, request a PNC interchange using the reset pnc interchange command. 2. Enter busyout pnc-standby. 3. Enter change system-parameters duplication, and change the Enable Operation of PNC Duplication field to n.
Page 913 ATM-EI (Expansion Interface Circuit Pack) Changing ATM Address of Standby ATM PNC EI — Critical Reliability 1. Enter busy pnc-standby. 2. Enter change atm pnc n (connection number), and change the ATM address for the standby side. 3. Enter release pnc-standby. Error Log Entries and Test to Clear Values Table 8-80.
Page 914 Maintenance-Object Repair Procedures Table 8-80. ATM-EI Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1793 (n) None 2049 (o) None test board UUCSS r 4 2050 (o) Expansion Interface Lock test board UUCSS r 4 Query test (#304) 2305 (p)
Page 915 ATM-EI (Expansion Interface Circuit Pack) Notes: a. Error Type 2 — The on-board DUART chip failed. This results in communication failure between the EPN’s Maintenance board and the ATM-EI board. The Maintenance board should have a red LED lit, because the link to the ATM-EI is down in this EPN.
Page 916 Some other ATM-EI board is not receiving the cells properly. The intervening ATM switch is dropping the ATM cells due to a shortage of bandwidth, or the S8700 Multi-Connect system is using more than the subscribed bandwidth. Error Type 771 — The ATM switch is sending cells with unknown VPI and VCI address (wrong connection).
Page 917 ATM-EI (Expansion Interface Circuit Pack) Table 8-81. ATM Error Types 1024 - 1151 Error Type Description General problem 1024 Next node unreachable ATM protocol stack on ATM-EI circuit pack 1056 DTL Transit not my node ID 1088 or ATM-EI circuit pack received a request with an Firmware-detected problems on the 1104 invalid connection identifier.
Page 918 Maintenance-Object Repair Procedures 1. Test the ATM-EI circuit pack (test board UUCSS) and investigate further based on each test’s results. If every test passes, the error was a transient problem. Aux Data values: For Setup and Add Party connection request failure type, the port-network and the angel number of the destination ATM-EI circuit pack are logged Aux Data values in the form XXYYY, where port-network number = XX...
Page 919 ATM-EI (Expansion Interface Circuit Pack) Table 8-82. Error Type 1024-1151 Aux Data values (XXYYY) converted to slot number — Continued Slot Carrier Failure type Failure type Failure type Failure type Failure type Slot Party Party Party Party Party 115 615 116 616 117 617 NA NA...
Page 920 Maintenance-Object Repair Procedures Table 8-83. Error type 1281 Aux Data and repair procedures — Continued Alarm Data Description Repair procedure Loss of Signal: The fiber is not connected properly to the ATM-EI board or ATM switch (or to the multiplexer section [MUX] if present).It is possible that the board transceivers are not functioning properly.
Page 921 ATM-EI (Expansion Interface Circuit Pack) Table 8-83. Error type 1281 Aux Data and repair procedures — Continued Alarm Data Description Repair procedure Multiplexer The far end is detecting a major problem with the signal that this Section Remote board is transmitting. Defect Indicator: Make sure the ATM switch port (or a MUX port, if present between MS_RDI...
Page 922 Test the board (test board long UUCSS). If Test #1260 fails, replace the board. If Test #1260 passes, make sure the ATM address on both the S8700 Multi-Connect and the ATM switch sides are the same for this board. If the address is the same, change the port on the ATM switch side.
Page 923 ATM-EI (Expansion Interface Circuit Pack) 1. Enter the reset board UUCSS command for this ATM-EI circuit pack. 2. If the same error persists, replace the ATM-EI circuit pack. n. Error Type 1793 — LANHO transmit FIFO overflow error (the transmit FIFO RAM buffers on the circuit pack overflowed).
Page 924 Maintenance-Object Repair Procedures r. Error Types 2817 and 2818 — A DSP test failure detected along the circuit path of the ATM-EI circuit pack. Error Type Description Aux Data indicates 2817 DSP test failure The Aux Data field contains the following information about the failed DSPs: X is the number of talker DSPs Y is the number of listener DSPs...
Page 925 ATM-EI (Expansion Interface Circuit Pack) Error Type 3585 Aux Data (Error Type 3585 only): Aux Data Description ATM framer failure NCE failed (only from ATM-EIs in EPN) TDM_PLD_FAILED DSP_ALL FAILED Receive Network Processor (RNP) failure Transmit Network Processor (TNP) failure MEMORY read/write failure 1.
Page 926 Maintenance-Object Repair Procedures x. Error Type 3999 — The circuit pack sent a large number of control channel messages to the switch within a short period of time. Then Error Type 1538 is also Circuit pack is taken out of service present Error Type 1538 is absent Circuit pack is not taken out of service, but has...
Page 927 ATM-EI (Expansion Interface Circuit Pack) Expansion Interface 2-Way Transmission Test (#241) This test is nondestructive and applies to every ATM-EI, both active and standby. It is run as part of craft short and long testing, periodic, scheduled, initialization, and error analysis testing. The test sets up a connection between a Tone-Clock in one cabinet and a Tone Detector in a separate cabinet and transmits a digital test count between the EPNs.
Page 928 Maintenance-Object Repair Procedures Table 8-85. Expansion Interface 2-Way Transmission Test (#241) Error Test Code Result Description / Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals up to 5 times. 1002 ABORT The system could not allocate time slots for the test.
Page 929 ATM-EI (Expansion Interface Circuit Pack) Table 8-85. Expansion Interface 2-Way Transmission Test (#241) — Continued Error Test Code Result Description / Recommendation 1033 ABORT The test cannot run because either the ATM-EI board is not administered, or there were no other PNs administered that had its ATM-EI board in-service. 1.
Page 930 ATM address on the ATM switch for the port to which this circuit pack is connected. Refer to ATM Installation, Upgrades, and Administration for Avaya MultiVantage Solutions book for the procedure to check the ATM port address on the ATM switch.
Page 931 ATM address on the ATM switch for the port to which this circuit pack is connected. Refer to ATM Installation, Upgrades, and Administration for Avaya MultiVantage Solutions book for the procedure to check the ATM port address on the ATM switch.
Page 932 MM matches the ATM address on the ATM switch for the port to which this circuit pack is connected. Refer to ATM Installation, Upgrades, and Administration for Avaya MultiVantage Solutions book for the procedure to check the ATM port address on the ATM switch.
Page 933 ATM-EI (Expansion Interface Circuit Pack) Table 8-86. Test #304 Expansion Interface Lock Query Test (#304) 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. 2500 ABORT Internal system error...
Page 934 Maintenance-Object Repair Procedures If the circuit pack is a standby ATM-EI (amber LED off), this test queries the ATM PNC Expansion Interface circuit pack for information about its type and vintage. Table 8-87. Expansion Interface Control Channel Test #316 Error Test Code Result...
Page 935 ATM-EI (Expansion Interface Circuit Pack) Packet Interface Test (#598) This test is nondestructive and attempts to send a data packet from the TN1655 Packet Interface circuit pack through any ATM PNC Expansion Interface circuit packs. The path the data packet takes depends on the location of the ATM PNC Expansion Interface circuit pack being tested and whether the system has duplicated port-network connectivity.
Page 936 Maintenance-Object Repair Procedures Table 8-88. Packet Interface Test (#598) — Continued Error Test Code Result Description / Recommendation FAIL The transmitted data packet was not received correctly by the Packet Interface circuit pack. The failure can be in the ATM-EI under test, the DS1 CONV circuit packs, or the intervening Center Stage components.
Page 937 ATM-EI (Expansion Interface Circuit Pack) Table 8-89. ATM Board Error Query Test (#1259) — Continued Error Test Code Result Description / Recommendation No board was detected by the test. BOARD 1. Check the Error Log for wrong board (Error Type 125) or no board (Error Type 131).
Page 938 Maintenance-Object Repair Procedures Table 8-90. XXYY Error Codes for Test #1259 (ATM Board Error Query Test) — Continued XX Aux Data Description Loss of frame Multiplexer Section Alarm indication signal error Multiplexer Section remote defect indicator error Loss of pointer Path signal level mismatch High level path alarm indication signal High level path remote defect indicator...
Page 939 ATM-EI (Expansion Interface Circuit Pack) ATM Board Framer Loop-Around Test (#1260) This test is destructive. NOTE: This test can be run on the standby PNC only if the board is busied out. This test places the ATM circuit pack in ATM framer loop-around mode. Once the board receives this message, it creates a dummy virtual circuit that originates and ends on the same board, without leaving the board.
Page 940 Maintenance-Object Repair Procedures — This test verifies the operation of a large portion of the ATM-EI circuit and packet paths, but does not verify the optical portion of the lightwave transceiver. If this test passes, the ATM-EI circuit pack is functioning correctly, but faults can exist in the lightwave transceiver.
Page 941 ATM-EI (Expansion Interface Circuit Pack) Table 8-91. ATM Board Framer Loop-Around Test (#1260) Error Test Code Result Description / Recommendation 1002 ABORT The system could not allocate timeslots for the test. The system could be under heavy traffic conditions or it could have timeslots out of service due to TDM-BUS errors.
Page 942 Maintenance-Object Repair Procedures Table 8-91. ATM Board Framer Loop-Around Test (#1260) — Continued Error Test Code Result Description / Recommendation 1141 ABORT The Packet Interface circuit pack is out of service. 1. Resolve any PKT-INTF problems. 1394 ABORT The ATM-EI board is out of service and the test cannot be run. This condition is due to a change in the ATM-EI board’s ability to communicate with the ATM switch.
Page 943 ATM-EI (Expansion Interface Circuit Pack) Table 8-91. ATM Board Framer Loop-Around Test (#1260) — Continued Error Test Code Result Description / Recommendation FAIL The test did not detect the test tone through the loop-around connection. NOTE: The packet portion of this test was not run since the circuit portion failed. 1.
Page 944 Maintenance-Object Repair Procedures Table 8-91. ATM Board Framer Loop-Around Test (#1260) — Continued Error Test Code Result Description / Recommendation FAIL A previously-established loop around was not released. 1. Issue the reset board UUCSS command. 2. Retry the command at 1-minute intervals up to 3 times. 3.
Page 945 This test is nondestructive. The ATM circuit pack requires a reference time to do SDH/SONET performance monitoring. This test updates the system time to the board and synchronizes the board with the S8700 Multi-Connect system’s clock during initialization, scheduled maintenance, and craft long test.
Page 946 Maintenance-Object Repair Procedures Table 8-93. ATM Board Reset (#1256) Error Test Code Result Description / Recommendation 1386 ABORT No Active EAL to the board. This error applies only if the board under test is in EPN. Check the error logs for SYS-LINK errors against the EPN where the ATM-EI resides, and take appropriate diagnostic action for the SYS-LINK.
Page 947 ATM-EI (Expansion Interface Circuit Pack) ATM Cross Talk Test (#1298) This test is nondestructive. The ATM board Cross Talk test verifies that the selected TDM bus time slot never crosses over to time slots reserved for other connections. The test also checks for cross connections, where the board talks to time slots other than those specified.
Page 948 Maintenance-Object Repair Procedures Table 8-94. ATM Crosstalk Test (#1298) — 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 949 ATM-EI (Expansion Interface Circuit Pack) If the test fails for every DSP, a MAJOR alarm is raised against the board. If the test fails for one or more DSPs, a MINOR alarm is raised. If a DSP is busy, the test for that particular DSP is considered passed.
Page 950 Maintenance-Object Repair Procedures Table 8-95. ATM Board DSP Test (#1293) — Continued Error Test Code Result Description / Recommendation 1962 ABORT Every DSPs is busy (an unlikely event). 1. Retry the command at 1-minute intervals up to 3 times. 2000 ABORT Response to the test was not received within the allowable time period for some of the DSPs.
Page 951: Atm-Intf (Tn2305/6)
ATM-INTF (TN2305/6) ATM-INTF (TN2305/6) MO’s Name (in Alarm Initial Command to Log) Alarm Level Full Name of MO ATM-INTF WARNING test board UUCSSpp ATM interface board The system recognizes a TN2305/6 as an ATM interface board (ATM-INTF) unless it has an assigned personality (using the add atm pnc command or add atm trunk command).
Page 952 Maintenance-Object Repair Procedures Error Log Entry Notes: a. Error Type 23: The ATM expansion interface circuit pack is administered through a change circuit-pack command, but has not been inserted into the system. Insert the circuit pack. b. Error Type 125: A wrong circuit pack is located in the slot where this circuit pack is logically administered.
Page 953 ATM-INTF (TN2305/6) Control Channel Loop-Around Test This test queries the circuit pack for its circuit-pack code and vintage and verifies its records. Table 8-98. Test #52: Control Channel Loop-Around Error Test Code Result Description / Recommendation 2000 ABORT The response to the test request was not received within the allowable time period.
Page 954: Atm-Ntwk (Atm Network Error)
(CES) boards are connected to an ATM switch port over a fiber-optic cable. The ports on the ATM switch are under control of its maintenance software. Refer to ATM Installation, Upgrades, and Administration for Avaya MultiVantage Solutions book for more information.
Page 955 ATM-NTWK (ATM Network Error) Table 8-99. Error codes and Aux data values ATM-NTWK Cause Code/ Error Type Data Cause Codes Description NORMAL EVENTS Network unreachable Unallocated (unassigned) number. This cause indicates that the called party cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).
Page 956 Maintenance-Object Repair Procedures Table 8-99. Error codes and Aux data values ATM-NTWK Cause Code/ Error Type Data Cause Codes Description User rejects every call with CLIR (calling line identification restriction). This cause is returned by the called party when the call is offered without calling party’s number information and the called party requires this information.
Page 957 ATM-NTWK (ATM Network Error) Table 8-99. Error codes and Aux data values ATM-NTWK Cause Code/ Error Type Data Cause Codes Description SERVICE OR OPTION UNAVAILABLE Quality of Service unavailable. This cause reports that the requested Quality of Service cannot be provided. User cell rate not available.
Page 958 Maintenance-Object Repair Procedures Table 8-99. Error codes and Aux data values ATM-NTWK Cause Code/ Error Type Data Cause Codes Description AAL parameters cannot be supported. This cause indicates that its sending equipment received a request to establish a call with ATM adaptation-layer parameters that cannot be accommodated.
Page 959 ATM-NTWK (ATM Network Error) Table 8-99. Error codes and Aux data values ATM-NTWK Cause Code/ Error Type Data Cause Codes Description 257 to 300 ATM Impaired Paths 1. Examine the error log (display errors), atm setup-events log (list measurements atm svc-setup), and atm pnc-latency (list measurements atm latency) screens to help diagnose the problem —...
Page 960 Maintenance-Object Repair Procedures Notes: a. Aux Data values for Setup and Add Party (XX = Port Network, YYY = location code). Aux Data values for WSP Setup (XX = WSP number, YYY = location code). Table 8-100 is a list of UNI 3.1 location codes: Table 8-100.
Page 961 ATM-NTWK (ATM Network Error) c. Error Type 301 — indicates that there is a system wide impaired path network problem. NOTE: Under certain circumstances network errors can be against the ATM EI board. d. Error Type 769 — ATM CLP (Cell Loss Priority) Bit Errors The ATM cell header has a bit called the cell loss priority (CLP) bit.
Page 962 Maintenance-Object Repair Procedures These errors affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs transport system links such as EAL, PACL, and PRI links. Symptoms that can affect the Constant Bit Rate (CBR) SVCs include audible artifacts in talk paths, failure of modems over voice lines, and “cell Underruns”...
Page 963 ATM-NTWK (ATM Network Error) If only cell overruns occur, locate the ATM board generating those cells. Execute test board long. If the board passes, then the ATM network remains the likely cause of transmission problems. Consult the ATM network vendor. Ask about cell delay variation, cell discard, and traffic policing.
Page 964: Atm Pnc-Dup (Atm Pnc Duplication)
Maintenance-Object Repair Procedures ATM PNC-DUP (ATM PNC Duplication) MO’s Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO PNC-DUP status pnc PNC duplication The PNC-DUP MO tracks the health of the active and standby PNCs, controls planned and spontaneous interchanges, and manages related functions such as double call refresh and unrefresh, antithrashing, and so on.
Page 965 ATM PNC-DUP (ATM PNC Duplication) PNC-DUP Related Commands The following commands and their output forms are fully described in Chapter 7, ‘‘Maintenance Commands’’. status pnc Displays information about both PNCs’ operational status, including state of health, alarms, busyouts and locks, and so on. reset pnc Used to initiate a demand PNC interchange.
Page 966 Maintenance-Object Repair Procedures 3. Fully administer IPSI duplication (ipserver-interface duplication). Verify by using list ipserver-interface. 4. Activate PNC-DUP through the change system-parameters duplication form. This is not allowed if any component of either PNC (A or B) is busied out. 5.
Page 967 ATM PNC-DUP (ATM PNC Duplication) Steady State LEDs The LEDs of PNC components in a stable duplicated system should appear as follows: For an active ATM EI (functioning as Archangel) in an EPN without IPSIs, its amber LED’s flash pattern is 2 seconds on/200 ms off. For a standby ATM EI in an EPN without IPSIs, it’s amber LED is off.
Page 968 Maintenance-Object Repair Procedures PNC State-of-Health Indexes The Inter-PN Index form the state-of-health vector is used to track and compare the states of health of both PNCs. The fields making up the indexes are 2-digit numbers separated by periods (.), with each field representing a different class of faults.
Page 969 ATM PNC-DUP (ATM PNC Duplication) Resolving Poor State of Health When both PNCs do not have an all-zero SOH (perfect health), use the following steps to identify and repair the problem. 1. Look for PNC component alarms (major or minor) for the PNC side without an all-zero SOH.
Page 970 Maintenance-Object Repair Procedures PNC Interchanges PNC spontaneous interchanges occur when PNC duplication software determines that the standby PNC’s state of health (SOH) surpasses the active PNC’s. PNC-DUP executes a spontaneous interchange in response to a message from a PNC component MO indicating that either a fault has occurred on the active PNC or a fault has been resolved on the standby PNC.
Page 971 ATM PNC-DUP (ATM PNC Duplication) Antithrashing and PNC Interchanges Following a spontaneous PNC interchange, subsequent PNC interchanges are prevented for 5 minutes. This condition is indicated by y in the Interchange Disabled? field of the status pnc form. After 5 minutes, the antithrashing, timer expires, interchange decisions are re-enabled, and the field displays n.
Page 972 Maintenance-Object Repair Procedures 3. Busyout the PNC with the busyout pnc command. 4. Use fault isolation and component testing procedures for the individual PNC components, just as for a simplex PNC. Replacement of components does disrupt operation of the active PNC. 5.
Page 973 ATM PNC-DUP (ATM PNC Duplication) Error Log Entries Whenever a PNC interchange takes place, an error is logged against PNC-DUP with a code that conveys information about the cause of the interchange and which PNC became active. There are no alarms associated with PNC-DUP errors, but there should be an alarm against the PNC component that caused the interchange.
Page 974 Maintenance-Object Repair Procedures Table 8-103. Error Log Encode Field Decoding Field Variable Name Values Description Alarm Type Alarm retired MAJOR or MINOR alarm on any PNC component EAL (Expansion Archangel Link - EXP-PN) carries CCMS messages PACL (ATM-EI) carries ATM signaling commands from Call Processing to the remote ATM-EI circuit Fault class;...
Page 975: Atm-Sgrp (Atm Signaling Group)
ATM-SGRP (ATM Signaling Group) ATM-SGRP (ATM Signaling Group) MO’s Name (in Alarm Initial Command to Log) Alarm 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. This ATM-SGRP MO applies when ATM signaling groups have been administered on an ATM circuit pack as ATM trunks.
Page 976 Maintenance-Object Repair Procedures When there are problems with ATM-SGRP (ATM signaling group), also investigate: ‘‘ATM-DCH (ATM D-Channel Port)’’ ‘‘ATM-BCH (ATM B-Channel Trunk)’’ ‘‘SYS-LINK (System Links)’’ ‘‘PKT-BUS (Packet Bus)’’ Error Log Entries and Test to Clear Values Table 8-105. ATM-SGRP Signaling Group Error Log Entries Error Alarm Type...
Page 977 ATM-SGRP (ATM Signaling Group) If no other symptoms are present, no action is required. If layer-3 communication is down: a. Check for alarms and errors against link components b. Check out other errors against ATM-SGRP, ATM-TRK, and other hardware components on the link. There is no test to clear these errors.
Page 978 Maintenance-Object Repair Procedures f. Error Type 1793: Layer 2 Query test for the primary signaling channel failed. Excessive AAL – The AAL layer is experiencing an excessive number of errors in trying to reconstruct Service Data Unit (SDUs). Possible causes: —...
Page 979 ATM-SGRP (ATM Signaling Group) Table 8-106. Descriptions and repair recommendations (Error Types 3840-3928) Error Code Description Recommendation 3842 A request has been made From the circuit pack and port number (in the Aux Data to use a transit network or field), determine the trunk group against which the error common carrier that cannot was reported.
Page 980 Maintenance-Object Repair Procedures Table 8-106. Descriptions and repair recommendations (Error Types 3840-3928) — Continued Error Code Description Recommendation 3890 A request to use a network This could indicate service (for example, SDN) a local administration problem has been denied. a mismatch between the local administration and that Administration somewhere of the network provider.
Page 981 ATM-SGRP (ATM Signaling Group) Table 8-106. Descriptions and repair recommendations (Error Types 3840-3928) — Continued Error Code Description Recommendation 3906 Protocol detail; may offer a 1. If customer is complaining of unexpected intercept clue if customer is having tones when accessing ISDN trunks or PRI endpoints ISDN calls denied with an and no other cause can be found, escalate to the unexpected intercept tone.
Page 982 Maintenance-Object Repair Procedures Table 8-107. System Technician-Demanded Tests: ATM-SGRP Short Test Long Test Order of Investigation Sequence Sequence D/ND Primary Signaling Link Hardware check (#636) Layer 2 Status test (#647) Remote Layer 3 Query test (#1291) Continued on next page D = Destructive, ND = Nondestructive Primary Signaling Link Hardware Check (#636) The ATM-SGRP Signaling Group D-channel port depends on the health of the...
Page 983 ATM-SGRP (ATM Signaling Group) Layer 2 Status Test (#647) The Layer 2 Status test checks the layer-2 status of the ATM-SRG signaling channel (D channel). This test fails when: there is a hardware failure there is a facility problem the D channels are not administered correctly The Signaling Link Hardware Check (Test #637) and the Remote Layer 3 Query test (#1291) detects most problems caused by hardware failures or incorrect administration.
Page 984 Maintenance-Object Repair Procedures Table 8-109. Test #647 Layer 2 Status Query Test — Continued Error Test Code Result Description / Recommendation FAIL The D channel is down. 1. Examine the results of the Primary Signaling Link Hardware Check (#636) and follow recommendations provided there. 2.
Page 985 ATM-SGRP (ATM Signaling Group) Table 8-110. Test #1291 Remote Layer 3 Query Error Test Code Result Description / Recommendation 1006 ABORT There are no associated B channels in an ISDN “in-service” or “maintenance” service state. This is a NORMAL ABORT. 1.
Page 986: Atm-Sync (Atm Synchronization)
TN722, TN464, and TN767 DS1 Interfaces (all suffixes) TN2305/6 ATM Expansion Interface (multimode fiber) Synchronization is achieved between the S8700 Media Server Multi-Connect IPSI and the Expansion Port Networks (EPNs) through the ATM port-network connectivity (ATM PNC) between the networks. Depending on the network’s...
Page 987 ATM-SYNC (ATM Synchronization) Stratum 4 Synchronization Systems may have primary and secondary synchronization references (DS1/UDS1 interface circuit packs or ATM-Switch) when using Stratum 4 synchronization. If the primary synchronization reference in Figure 8-10 on page 8-266 is providing a valid timing signal, then the flow of system synchronization would travel from the DS1 interface circuit pack in the EPN to the ATM switch.
Page 988 Stratum-3 synchronization is not supported in S8700 Multi-Connect with ATM PNC. Synchronization Troubleshooting A significant part of the Synchronization Recovery Strategy for a S8700 Multi-Connect with ATM PNC resides in the ATM switch’s clock hardware, firmware, and software. S8700 Multi-Connect monitors synchronization performance and alarms any faulty components.
Page 989 ATM-SYNC (ATM Synchronization) ATM-SYNC Commands Use the following commands to help troubleshoot ATM-SYNC problems: change Allows primary and secondary references to be administered for synchronization the Stratum 4 option, or ATM-Switch , indicating that the synchronization references are input directly to the ATM switch status Shows the current inferred synchronization reference synchronization...
Page 990 Maintenance-Object Repair Procedures 1. Check if the primary DS1 interface circuit pack is inserted in the carrier with the list configuration board UUCSS command. 2. Verify that the administered primary reference matches the DS1 reference from the network synchronization plan. 3.
Page 991 ATM-SYNC (ATM Synchronization) For Simplex Tone-Clock circuit packs in the master port network: replace the primary and secondary (if administered) DS1 Interface circuit packs. 4. Investigate any other SYNC errors. f. Error Type 2049: the ATM Expansion Interface circuit packs have errors that affect synchronization.
Page 992 Maintenance-Object Repair Procedures Table 8-112. Test #417 Test Synchronization Test Error Test Code Result Description / Recommendation 1000 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals up to 3 times. 1115 ABORT Could not allocate the necessary system resources to run this test.
Page 993: Atm-Trk (Circuit Emulation Service Circuit Pack)
ATM-TRK (Circuit Emulation Service Circuit Pack) ATM-TRK (Circuit Emulation Service Circuit Pack) MO’s Name Alarm Initial Command to (in Alarm Log) Level Full Name of MO ATM-TRK MAJOR test board UUCSS ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK MINOR test board UUCSS ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK...
Page 994 Maintenance-Object Repair Procedures NOTE: TN230x circuit packs are not interchangeable. ATM Circuit Emulation Service Under ATM Circuit Emulation Service (CES), you simulate ISDN-PRI circuits by assigning ports to signaling groups. Each signaling group represents a PRI circuit, and the ports in the group represent the D channel and B channels of that circuit.
Page 995 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 8-116 shows the ATM CES capacities for both T1 and E1 circuits. Table 8-116. Ports available for trunking, for each ISDN facility type Channels per Max. signaling Max. signaling group groups (trunks) available Reserved Total Type...
Page 996 Maintenance-Object Repair Procedures ATM-TRK-related commands Table 8-118 lists some commands that can be useful in troubleshooting ATM errors and alarms. Table 8-118. ATM CES troubleshooting commands Command Description display circuit-packs cabinet Shows the circuit packs in the cabinet, identifying ATM trunk as well as ATM-EI boards.
Page 997 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 8-119. ATM-TRK Error Log entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 513(f) ATM Cross talk test test board UUCSS l r 1 (#1298) 769(g) ATM Error Query test test board UUCSS (#1259)
Page 998 Maintenance-Object Repair Procedures Notes: a. Error Type 1: the ATM-TRK circuit pack does not appear to be in its assigned slot. 1. Make sure that the ATM-TRK circuit pack is installed correctly seated in the slot administered for the ATM trunk. b.
Page 999 Path-Identifier (VPI) and Virtual Channel-Identifier (VCI) addresses. 1. Make sure that the ATM-TRK circuit-pack address is administered identically on the ATM switch and the S8700 Multi-Connect system. i. Error Type 1281: Board major signals error (loss of high-level signal). The far end has detected a major problem in transmissions originating from the ATM-TRK circuit pack.
Page 1000 Maintenance-Object Repair Procedures Table 8-120. Error type 1281 Aux Data and repair procedures Alarm Data Description Repair procedure SYSCLOCK failed The board is not locked to the TDM backplane clock signal. This is probably due to a Tone-Clock problem. 1. Check for TDM-BUS or TONE-BD errors in the Error Log. 2.

Avaya S8700 Maintenance Manual

About this Book

1 Maintenance Architecture

2 Hardware Configurations

Initialization and Recovery

Alarms, Errors, and Troubleshooting

Additional Maintenance Procedures

LED Interpretation

Maintenance Commands

Maintenance-Object Repair Procedures

Quick Links

Troubleshooting

Related Manuals for Avaya S8700

Summary of Contents for Avaya S8700