Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-41 Troubleshooting ISDN-BRI/ASAI Problems 5 Figure 5-11. Troubleshooting ISDN-BRI Problems (Page 2 of 2) PAGE NOYES END FROM 1 IS THE PROBLEM AFFECTING MOs ON MULTIPLE BRI-BD CIRCUIT IS THE PROBLEM AFFECTING MULTIPLE MOs ON THE SAME BRI-BD CIRCUIT A NO FOLLOW THE REPAIR PROCEDURE FOR BRI-PORT, BRI-DAT, ABRI-PORT, BRI-SET, OR ASAI-ADJ, AS APPROPRIATE IS THE ISDN-BRI PROBLEM RESOLVED FOLLOW THE REPAIR PROCEDURE FOR BRI-BDYES FOLLOW THE REPAIR PROCEDURE FOR PKT-BUS PAGEFROM 1B * THESE MOs WOULD BE BRI-PORT, ABRI-PORT, BRI-DAT, BRI-SET, OR ASAI-ADJPACKS * PACKS * ESCALATE THE PROBLEM YESNO
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-42 Troubleshooting ISDN-PRI Test Call Problems 5 Troubleshooting ISDN-PRI Test Call Problems 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. The ISDN-PRI test call can access ISDN-PRI trunks only. An ISDN-PRI test call can be placed only if the circuit translates to an ISDN-PRI trunk. An ISDN-PRI test call can be originated via either the synchronous or the asynchronous method. Each method is described below. NOTE: Before attempting to make an ISDN-PRI test call to the public network (that is, the network is the far-end), make sure that test call service is provisioned by the network. The user must subscribe to Test Type 108 service and have the correct far-end test call number administered on the trunk group form for the call to be allowed. Synchronous Method One command is used in this method to start, stop and query an ISDN-PRI test call. In the synchronous method, an outgoing ISDN-PRI test call may be part of one of the following long test sequences entered at the terminal: ntest trunk grp/mbr long [repeat #] ntest port UUCSSpp long [repeat #] ntest board UUCSS long [repeat #] The long qualifier must be entered in the above commands in order for the ISDN test call to run. The repeat number (#) can be any number from 1 through 99 (default = 1). The following information is displayed in response to the above commands: nPort: The port address (UUCSSpp) is the port network number, carrier designation, slot, and circuit of the maintenance object under test. nMaintenance Name: The type of maintenance object tested. nTest Number: The actual test that was run. nTest Results: Indicates whether the test passes, fails, or aborts. nError Code: Additional information about the results of the test (See the ISDN-TRK section of Chapter 9 for details.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-43 Troubleshooting ISDN-PRI Test Call Problems 5 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, query, and list an outgoing ISDN-PRI test call: Before placing an outgoing ISDN-PRI test call, verify that the Feature Access Code has been administered on the System Features Form, and that the Far End Test Line Number and TestCall Bearer Capability Class (BCC) have been administered on the Trunk Group Administration Form. Furthermore, if the ISDN-PRI trunk is of the cbc (call by call) service type, then the Testcall Service field on Trunk Group Administration Form must have been administered also. To initiate an outgoing ISDN-PRI test call with the asynchronous method, issue the start command listed above, which enables you to specify a specific the trunk on which to originate the ISDN-PRI test call. An optional qualifier can be used that specifies in minutes (1 to 120) the duration of the test call. If no duration is specified, the default is either 8.4 or 9.6 seconds. Screen 5-1 shows a typical response to the test isdn-testcall command: Screen 5-1. Test ISDN-TestCall Response The displayed fields have the following meanings:Start:test isdn-testcall grp/mbr[minutes] Stop:clear isdn-testcall grp/mbr List:list isdn-testcall Query:status isdn-testcall / PortThe port address (UUCSSpp) is the port network number, carrier designation, slot, and circuit of the maintenance object under test. Maint. NameThe type of maintenance object tested. Test NumberThe actual test that was run. Test ResultsIndicates whether the test passes, fails, or aborts. Error CodeAdditional information about the results of the test (See the ISDN-TRK section in Chapter 9 for details). test isdn-testcall Port Maintenance Name Test Number Test Result Error Code 1B1501 ISDN-TRK 258 PASS
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-44 Troubleshooting the Outgoing ISDN-Testcall Command 5 The functions of the clear, list, and status commands associated with the ISDN Testcall are summarized below. 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 all the ISDN-PRI trunks in use for an ISDN-PRI test call in the system. status isdn-testcall: enables you to check on the progress of an outgoing test call. When an outgoing ISDN-PRI test call completes in a specific port network, another ISDN-PRI trunk from the same port network is available for testing (regardless of whether the status information has been displayed). 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: If the ISDN-PRI trunk is of type cbc make sure the TestCall Service field on the Trunk Group Administration Form indicates the correct service so that a network facility message can be sent across the ISDN-PRI network. If the outgoing ISDN-PRI test call keeps aborting, make sure that the far-end device can handle DCP Mode 0 or DCP Mode 1. NOTE: Before attempting to make an ISDN-PRI test call to the public network (that is, the network is the far-end), make sure that test call service is provisioned by the network. The user must subscribe to Test Type 108 service and have the correct far-end test call number administered on the trunk group form for the call to be allowed.0Voice 1Digital Communications Protocol Mode 1 2Mode 2 Asynchronous 3Mode 3 Circuit 4Digital Communications Protocol Mode 0 (that is usually the default).
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-45 Packet Bus Fault Isolation and Repair 5 Packet Bus Fault Isolation and Repair The following procedures provide a means of isolating and correcting faults on both the packet bus and the various maintenance objects that use the packet bus. The packet bus is shared by all circuit packs that communicate on it, and a fault on one of those can disrupt communications over the packet bus. Furthermore, a circuit pack that does not use the packet bus can also cause service disruptions by impinging on the backplane or otherwise modifying the configuration of the bus. (this is discussed in more detail later). For these reasons, isolating the cause of packet bus failure can be complicated. This discussion provides a flowchart and descriptions of the tools and procedures used to isolate and correct packet bus faults. This discussion is organized into the following sections which provide background information and troubleshooting procedures. The packet bus Fault Isolation Flowchart is intended to be the normal starting point for isolating and resolving packet bus problems. Before using it you should familiarize yourself with packet bus maintenance by reading the introductory sections. n‘‘Remote Maintenance versus On-Site Maintenance’’discusses the strategy and the requirements for performing remote maintenance and on-site maintenance for the packet bus. n‘‘Tools for Packet Bus Fault Isolation and Correction’’ discusses the tools that are needed to isolate and correct packet bus faults. n‘‘What is the Packet Bus?’’ describes the packet bus, its use in G3r, and the types of faults that can occur on the packet bus. A diagram shows the physical and logical connections between circuit packs connected to the packet bus. n‘‘Circuit Packs That Use the Packet Bus’’ describes the various circuit packs, ports, and endpoints that use the packet bus. The section discusses how these maintenance objects interact, how a failure of one maintenance object can affect another, and failure symptoms of these maintenance objects. n‘‘Maintenance of the Packet Bus’’ describes the strategy of maintenance software for packet bus. Similarities and differences between the packet bus and the TDM Bus are discussed. An overview of the Fault Isolation and Correction Procedures is also presented. n‘‘The Maintenance/Test Circuit Pack (TN771)’’ discusses the use of the Maintenance/Test circuit pack in both packet bus fault isolation and other switch maintenance. The standalone mode of the Maintenance/Test circuit pack, which is used to perform on-site packet bus fault isolation and correction, is discussed in detail.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-46 Packet Bus Fault Isolation and Repair 5 n‘‘Packet Bus Fault Isolation Flowchart’’ is the starting point for the troubleshooting process. It is used to determine if a failure of service is caused by the packet bus itself or by another maintenance object on the packet bus. n‘‘Correcting Packet Bus Faults’’ presents the procedures required to correct either a problem with the packet bus itself or one that is caused by a circuit pack connected to the Packet Bus. Remote Maintenance versus On-Site Maintenance Most packet bus fault isolation and repair procedures require a technician to be on-site. This is because a packet bus failures are caused by a hardware failure of either the packet bus itself or a circuit pack that is connected to it. Initial diagnoses can be made via use of the packet bus Fault Isolation Flowchart, but the Maintenance/Test Standalone Mode Procedure and the packet bus Fault Correction Procedure require that a technician be on-site. These procedures are presented with this requirement in mind. The flowchart refers to the repair procedures in Chapter 9, ‘‘ Maintenance Object Repair Procedures’’ for various maintenance objects. When a decision point is reached, a remotely located technician can refer to the appropriate section and attempt to resolve any fault conditions. Some procedures require on-site repair action. Keep in mind that failure of a maintenance object appearing early in the flowchart can cause alarms with maintenance objects that appear later in the flowchart. Multiple dispatches can be prevented by remotely checking subsequent stages on the flowchart and preparing the on-site technician for replacement of several components if necessary. The Maintenance/Test packet bus port described below provides status information that is accessed with the status port-network P command and the PKT-BUS test sequence. The Maintenance/Test circuit pack may or may not be present at a customer site, depending on the configuration of the switch. If a Maintenance/Test circuit pack is not present, one must be taken to the site for diagnosing packet bus problems. In a system with duplicated SPEs, an SPE interchange may resolve the packet bus problem. This operation can be executed remotely, and is discussed in Packet Bus Fault Correction Procedures below.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-47 Packet Bus Fault Isolation and Repair 5 Tools for Packet Bus Fault Isolation and Correction The following tools may be required on-site to perform packet bus fault isolation and correction. nTN771D Maintenance/Test circuit pack for use in standalone mode, and the connectors and cables necessary to install it (see the Maintenance/Test Circuit Pack section). nA replacement for the TN771D Maintenance/Test circuit pack in the system may be needed. See the A Special Precaution Concerning the TN771D section. nA backplane pin-replacement kit may be required (see Packet Bus Fault Correction ) If the kit is not available, replacement of a carrier may be required. What is the Packet Bus? The packet bus is a set of 24 leads in the backplane of each Port Network. Twenty of these leads are data leads, three are control leads, and one lead is a spare. This distinction is important only for understanding why some circuit packs are able to detect only certain faults; the distinction does not affect fault isolation and repair. Each Port Network has its own packet bus and there is one packet bus maintenance object (PKT-BUS) in each port network. The packet bus is not duplicated as is the TDM Bus. There are however several spare leads on the packet bus and, in Critical Reliability systems (duplicated PNC), these spare leads are used to recover from some failures on the packet bus. The packet bus carries various types of information: nSignaling and data traffic destined for other port-networks and/or Center Stage Switches. The TN570 Expansion Interface circuit pack provides packet bus access for these connections. nISDN-BRI signaling information for ISDN-BRI stations, data modules and ASAI adjunct connections. The TN556 ISDN-BRI circuit pack provides packet bus access for these connections. nX.25 signaling information and data traffic to support system adjunct applications. The TN577 Packet Gateway circuit pack provides packet bus access for these connections. nISDN-PRI signaling information carried in the D-channels of ISDN-PRI facilities connected to the switch. The TN464F Universal DS1 circuit pack provides packet bus access for these connections. nSystem Port traffic to support various input/output devices such as dial-up modems and printers, as well as system adjunct applications. The TN553 Packet Data circuit pack provides packet bus access for these connections.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-48 Packet Bus Fault Isolation and Repair 5 The SPE interface to the packet bus is the TN1655 Packet Interface circuit pack. When SPEs are duplicated, there is one TN1655 in each SPE. The TN771D Maintenance/Test Circuit Pack (discussed in detail later) provides packet bus maintenance testing and reconfiguration capabilities. Packet Bus Faults Two types of packet bus faults occur: Shorts are far more common than opens, since they can be caused by incorrect insertion of a circuit pack. It is possible for a circuit pack to be the cause of a packet bus fault but still operate trouble-free itself. For example, the insertion of a TDM-only circuit pack such as a TN754 Digital Line could bend the packet bus pins on the backplane, but remain unaffected since it does not communicate over the packet bus. Packet bus faults do not necessarily cause service interruptions, but shorts on it usually do. Depending on what leads are defective, the system may be able to recover and continue to communicate. While this allows uninterrupted service, it makes isolating the fault difficult. The Maintenance/Test circuit pack provides the capability to detect, and, in some cases, correct packet bus faults. Packet Bus Connectivity Various circuit packs communicate on the packet bus (see the next section). For more details, refer to Chapter 9, ‘‘ Maintenance Object Repair Procedures’’ for the following circuit packs: nTN1655 Packet Interface: PKT-INTF nTN570 Expansion Interface: EXP-INTF nTN556 ISDN-BRI: BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ nTN577 Packet Gateway: PGATE-BD, PGATE-PT nTN553 Packet Data: PDATA-BD, PDATA-PT nTN464F Universal DS1: UDS1-BD, ISDN-LNK 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. A fault occurring during normal operation is usually caused by a circuit pack. A fault that occurs while moving circuit packs or otherwise modifying the switch is usually due to bent pins on the backplane. Opens An open occurs when there is a break on the packet bus such that the electrical path to the termination resistors is interrupted. Usually, this break is caused by a failed TDM/LAN cable or terminator. A less likely possibility is a failure in the backplane of a carrier.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-49 Packet Bus Fault Isolation and Repair 5 nTN771D Maintenance/Test: M/T-BD, M/T-DIG, M/T-PKT Circuit Packs That Use the Packet Bus This section describes the circuit packs that use the packet bus and the effects of circuit pack and bus failures on each other. Seven circuit packs can use the packet bus: The maintenance objects pertaining to each circuit pack, (described further in Chapter 9), are listed in brackets. nTN1655 Packet Interface [PKT-INTF] provides the SPE interface to the packet bus (as the UN332 MSSNET does to the TDM Bus). All traffic on the packet bus passes through the Packet Interface. The Packet Interface can detect some control lead failures and many data lead failures via parity errors on received data. nTN570 Expansion Interface [EXP-INTF] connects the Port Networks (PNs) in the system. (Only TN570s can be used in Release 5r). All Packet traffic between PNs passes through a pair of TN570s (one in each port network). The Expansion Interface can detect some control lead failures, and many data lead failures via parity errors on received data. nTN556, TN2198, and TN2208 ISDN-BRI circuit packs [BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ] carries signaling information for ISDN-BRI station sets and data modules, as well as signaling information and ASAI messages between the SPE and an ASAI adjunct. The ISDN-BRI circuit pack has the same fault detection capabilities as the TN570 Expansion Interface. nTN577 Packet Gateway circuit pack [PGATE-BD, PGATE-PT] provides X.25 connectivity to support external system adjuncts such as Audix ® and DCS. The packet bus carries both signaling and customer traffic. The Packet Gateway circuit pack has the same fault detection capabilities as the TN570 Expansion Interface. nTN553 Packet Data circuit pack [PDATA-BD, PDATA-PT] connects via a backplane cable to a TN726B Data Line circuit pack in an adjacent carrier slot. Together, the two circuit packs perform a protocol conversion from mode 3 packet bus traffic originating in the SPE to mode 2 TDM Bus traffic destined for external system devices and adjuncts. This connectivity is referred to as a System Port. System Ports support devices and adjuncts such as the System Printer, the PMS Journal Printer, the PMS Wakeup Log Printer, data terminals, remote administration terminals, and equipment to support the Call Detail Recording (CDR) feature. System Ports are also used for saving and restoring System Announcements. The packet bus carries both signaling and data for the Packet Data circuit pack. The Packet Data circuit pack has the same fault detection capabilities as the TN570 Expansion Interface.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-50 Packet Bus Fault Isolation and Repair 5 nTN464F Universal DS1 circuit pack [UDS1-BD, ISDN-LNK] supports ISDN-PRI communications over an attached DS1 facility. It transports of D-channel signaling information over the packet bus, and B-channel data over the TDM bus. The Universal DS1 circuit pack has the same fault detection capabilities as the TN570 Expansion Interface. nTN771D Maintenance/Test circuit pack [M/T-BD, M/T-DIG, M/T-PKT, M/T-ANL] is the workhorse of packet bus maintenance. This circuit pack can detect all packet bus failures for the Port Network in which it resides. In Critical Reliability systems (duplicated PNC), this circuit pack enables the reconfiguring of the packet bus around a small number of failed leads. The TN771D circuit pack provides a standalone mode (one that does not involve communication with the SPE), for inspecting the packet bus for faults. Standalone mode is a critical tool for troubleshooting packet bus faults. NOTE: All Maintenance/Test circuit packs must be of vintage TN771D or later. This circuit pack is also used for ISDN-PRI trunk testing (M/T-DIG) and ATMS trunk testing (M/T-ANL). Effects of Circuit Pack Failures on the Packet Bus Certain failures of any of the above circuit packs can disrupt traffic on the packet bus Some failures cause packet bus failures with corresponding alarms, while others cause service outages without alarming the packet bus, (although the failed circuit pack should be alarmed). Packet bus circuit pack failures affect the bus in the following ways: nTN1655 Packet Interface. A failure of the Packet Interface typically causes all Packet traffic in the system to fail. As a result, — Expansion Port Networks and Center Stage Switches are disabled. — ISDN-BRI sets are not able to make or receive calls. — Communication with ASAI adjuncts fail — X.25 communications with external adjuncts fail. — System Ports are disabled. — ISDN-PRI D-channel signaling is disabled. If the failure is on the packet bus interface, the packet bus may be alarmed as well. In a system with duplicated SPEs, there is one TN1655 Packet Interface in each SPE. If a Packet Interface failure in the active SPE causes a packet bus disruption, an SPE interchange may restore service. In other cases, replacement of the circuit pack may be required before service is restored.