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+.
![Page 180
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...](http://img.usermanuals.tech/thumb/3002/85165/w64_definity-ecs-r6-maintenance-for-r6r_d-179.png "Page 180
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...")
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-51 Packet Bus Fault Isolation and Repair 5 nTN570 Expansion Interface. A failure of the Expansion Interface typically causes all packet traffic in the connected EPN or Center Stage Switch to fail. If the failure is on the packet bus interface, the packet bus may be alarmed as well. If an active Expansion Interface failure causes a packet bus disruption in a Critical Reliability system (duplicated PNC), a PNC Interchange may restore service. In other cases, replacement of the circuit pack may be required before service is restored. nTN556 ISDN-BRI Circuit Pack. A failure of the ISDN-BRI circuit pack typically causes some or all ISDN-BRI sets and data modules and/or an ASAI adjunct connected to the circuit pack to stop functioning. If the failure is on the circuit pack’s packet bus interface, the packet bus may be alarmed. nTN577 Packet Gateway Circuit Pack. A failure of the Packet Gateway circuit pack disrupts communications with the adjunct (for example, Audix, DCS) connected to the far end of the X.25 link. If the failure is on the circuit pack’s packet bus interface, the packet bus may be alarmed. nTN553 Packet Data Circuit Pack. A failure of the Packet Data circuit pack disrupts System Port traffic. If the failure is on the circuit pack’s packet bus interface, the packet bus may also be alarmed. Applications that use System Ports include: — Saving and restoring announcements — Call Detail Recording (CDR) — Journal Printer for the Property Management System (PMS) — Wakeup Log Printer for the Property Management System (PMS) —System Printer — Data Terminals — Remote administration terminals nTN464F Universal DS1 Circuit Pack. A failure of the Universal DS1 Circuit Pack disrupts ISDN-PRI signaling traffic carried on the D-channel. The loss of that signaling may impact the pack’s 23 B-channels. If the D-channel supports Non Facility Associated Signaling (NFAS), the B-channels of up to 20 other DS1 circuit packs may also be affected. In cases where all 24 channels of the circuit pack are B-channels, packet bus related failures may not affect the B-channels, since only D-channel signaling is carried on the packet bus. If the failure is on the circuit pack’s packet bus interface, the packet bus may be alarmed as well. nTN771D Maintenance/Test. A failure of the Maintenance/Test may cause an incorrect indication of a packet bus failure or the inability to detect such a failure. If the failure is on the packet bus interface, the packet bus may be alarmed as well.
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-52 Packet Bus Fault Isolation and Repair 5 Failure of any circuit pack’s bus interface may alarm the packet bus due to shorting of the packet bus leads. This typically disrupts all packet bus traffic in the affected PN. A failure of the packet bus in the PPN affects packet traffic in the EPNs as well. Some packet bus failures do not affect all endpoints, so a packet bus failure cannot be ruled out just because some packet service is still available. A circuit pack can fail in a manner such that it transmits bad data on the packet bus. If the Packet Interface so fails, all Packet traffic is disrupted. Such a failure on an Expansion Interface may disrupt all Packet traffic in that port network. If an ISDN-BRI circuit pack fails such that it transmits bad data, all devices connected to the circuit pack fail to function. This failure may also disrupt the entire packet bus whenever the circuit pack tries to transmit data. Such a disruption may be indicated by packet bus alarms that occur and go away, intermittent failures of other packet circuit packs, and/or interference with other connected endpoints. These failures are difficult to isolate because of their intermittent nature. In most cases, the failed circuit pack is alarmed, and all connected endpoints on the circuit pack are out of service until the circuit pack is replaced. These symptoms help in isolating the fault. Maintenance of the Packet Bus The following topics are covered in this section: n‘‘Packet Bus and TDM Bus: a Comparison’’ n‘‘Packet Bus Maintenance Software’’ n‘‘Fault Correction Procedures: Overview’’ Packet Bus and TDM Bus: a Comparison The packet and TDM busses have several similarities and differences. There are two physical TDM buses in each PN. 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. A failure of that bus can disrupt all packet traffic in that PN. In critical reliability systems, the Maintenance/Test circuit pack provides packet bus reconfiguration capabilities. This allows the packet bus to remain in service with up to 3 lead failures. There is no corresponding facility on the TDM Bus. Instead, the second physical TDM Bus continues to carry traffic until repairs are completed. System response varies according by type of bus failure and whether or not the failure occurs in the PPN or an EPN. In an EPN, a catastrophic TDM Bus failure (one that affects both TDM Buses) disables all traffic in the PN. A catastrophic packet bus failure affects only packet traffic, so that TDM traffic is unaffected, while all ISDN-BRI, ASAI, X.25, and ISDN-PRI signaling traffic is disrupted. The significance of this distinction depends on the customer’s applications. A customer whose primary application requires ASAI would consider the switch to be out of service, while a customer with a large number of Digital/Analog/Hybrid sets and a small number of ISDN-BRI sets would probably not consider the
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-53 Packet Bus Fault Isolation and Repair 5 packet bus failure a catastrophic problem. The only way an EPN packet bus failure can affect TDM traffic is via possible impact on system response time in a large switch due to running of ISDN-BRI endpoint maintenance. This should rarely happen because the packet bus maintenance software is able to prevent this for most faults (see the next section). If packet bus failure occurs in the PPN, the impact is much more widespread. Because the PPN packet bus carries the signaling and control links for all EPNs, PPN packet bus failure effectively removes all the EPNs from service, including both TDM and packet busses. Packet bus traffic in the PPN is also disrupted. !CAUTION: Packet bus fault correction and fault isolation often involve circuit pack removal, which is destructive to service. Minimize time devoted to destructive procedures by the use of non-destructive ones where possible. Packet Bus Maintenance Software Packet bus maintenance software involves the usual set of maintenance object error conditions, tests, and alarms. These are described in “PKT-BUS” in Chapter 9. Because a packet bus failure can cause all BRI/ASAI endpoints in the affected Port Network, and all their associated ports and circuit packs, to report failures, special care must be taken to ensure that the flood of error messages does not overload the system and interfere with TDM Bus traffic. When such a failure occurs , circuit pack maintenance is affected in the following manner: nIn-line errors for the following MOs which indicate possible packet bus failures are logged but not acted upon: BRI-BD, PGATE-BD, PDATA-BD, UDS1-BD. nIn-line errors for the following MOs which indicate possible packet bus failures are neither logged nor acted upon: BRI-PORT, ABRI-PORT, PGATE-PT, PDATA-PT, ISDN-LNK. nAll in-line errors for the following MOs are neither logged nor acted upon: BRI-SET, BRI-DAT, ASAI-ADJ. nCircuit pack and port in-line errors that are not related to the packet bus, or that indicate a circuit pack failure, are acted upon in the normal fashion. nPeriodic and scheduled background maintenance is not affected. nForeground maintenance (for example, commands executed from the terminal) is not affected. These interactions allow normal non-packet system traffic to continue unaffected, and they reduce the number of entries into the Error/Alarm Logs. If the packet bus failure is caused by a failed circuit pack, errors against the circuit pack should appear in the Error/Alarm Logs as an aid for fault isolation. The above strategy is implemented when: nIn-line errors indicate a possible packet bus failure reported by two or more Packet circuit packs.
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-54 Packet Bus Fault Isolation and Repair 5 nA packet bus Uncorrectable report is sent from the Maintenance/Test packet bus port (M/T-PKT). When such a failure occurs, a PKT-BUS error is logged. Refer to the PKT-BUS section in Chapter 9 for more detailed information. Fault Correction Procedures: Overview This section gives an overview of the procedures used to isolate the cause of and correct packet bus faults. Details are presented in following sections. 1. Procedure 1 attempts to determine if a circuit pack that interfaces to the packet bus is the cause of the packet bus problem. This involves examination of the Error and Alarm logs followed by the usual repair actions. 2. If the packet bus problem persists, remove port circuit packs (those in purple slots) to look for circuit packs that have failed and/or damaged the packet bus pins. 3. If the packet bus problem persists, perform the same procedure for control complex circuit packs. 4. If the problem persists, or if the packet bus faults are known to have open leads, replace bus terminators and cables. If this does not resolve the problem, reconfigure the carrier connectivity of the port network to attempt to isolate a faulty carrier. The Maintenance/Test Circuit Pack (TN771) The TN771 Maintenance/Test circuit pack provides the following functions: nAnalog Trunk (ATMS) Testing nDigital Port Loopback Testing nISDN-PRI Trunk Testing nPacket Bus Testing nPacket Bus Reconfiguration (Critical Reliability systems only) The PPN always contains a TN771D. Critical Reliability systems have a TN771D in each EPN. A TN771D is optional in EPNs of other configurations. The ISDN-PRI Trunk Testing functions are discussed in the ‘‘ ISDN-PLK (ISDN-PRI Signaling Link Port)’’ section in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. The Digital Port Testing functions are discussed in the ‘‘ DIG-LINE (Digital Line)’’, DAT-LINE (Data Line Port), ‘‘ PDMODULE (Processor Data Module) TDMODULE (Trunk Data Module)’’, ‘‘TDMODULE (Trunk Data Module)’’, ‘‘PGATE-PT (Packet Gateway Port)’’, ‘‘PDATA-PT (Packet Data Line Port)’’, and ‘‘MODEM-PT (Modem Pool Port)’’, sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. The Analog Trunk Testing functions are discussed in the ‘‘ TIE-TRK (Analog Tie Trunk)’’, ‘‘DID-TRK (Direct Inward Dial Trunk)’’, ‘‘CO-TRK (Analog CO Trunk)’’,
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-55 Packet Bus Fault Isolation and Repair 5 and ‘‘AUX-TRK (Auxiliary Trunk)’’, sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. NOTE: All Maintenance/Test circuit packs must be of TN771D vintage or later. TN771D Packet Functions The Maintenance/Test packet bus port (M/T-PKT) provides the packet bus testing and reconfiguration capabilities. When the port is in service, it continuously monitors the packet bus for faults and fault recoveries, and reports results to PKT-BUS maintenance. The yellow LED on the TN771D Maintenance/Test circuit pack provides a visual indication of the state of the packet bus: NOTE: It takes 5 to 10 seconds for the LED to respond to a change in the state of the packet bus. During normal switch operation, the Maintenance/Test provides visual feedback of the packet bus state. When in standalone mode (see the next section), these visual indications are still present, but the packet bus is never reconfigured. The yellow LED either blinks or is off. Flashing Flashing of the yellow LED once per second indicates that there are too many faults for the Maintenance/Test packet bus port to recover by swapping leads. The packet bus may be unusable. If the failures detected are open lead failures, the packet bus may still be operating. On steady The Maintenance/Test packet bus port has swapped leads on the packet bus to correct a fault. The packet bus is still operating . Or, one of the other ports on the Maintenance/Test circuit pack is in use. NOTE: First busy out the Maintenance/Test circuit pack ports used for other than packet bus testing before using the Maintenance/Test circuit pack to help resolve packet bus faults. This is done by entering busyout port UUCSS01, busyout portUUCSSl02, and busyout port UUCSS03. Be sure to release these ports when the process is completed. Off There is no packet bus fault present.
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-56 Packet Bus Fault Isolation and Repair 5 TN771D in Standalone Mode In TN771D standalone mode, a terminal is connected to the Maintenance/Test circuit pack with an Amphenol connector on the back of 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 thus available even if switch is not in service. When in standalone mode, the TN771D does not reconfigure the packet bus. Required Hardware nTN771D: Standard or High Reliability systems may not have a TN771D in each EPN. (Use list configuration to determine if this is so.) When this is the case, one must be taken to the site. See the following section, ‘‘ Special Precaution Concerning the TN771D’’. nTerminal or PC with terminal-emulation software: The EIA-232 (RS-232) port should be configured at 1200 baud, no parity, 8 data bits, and one stop bit. This is not the same configuration as for the G3-MT. If a terminal configured as a G3-MT is used, change the SPEED field from 9600 to 1200 on the terminal’s options setup menu. (This menu is accessed on most terminals by pressing the CTRL and F1 keys together. On the 513 BCT, press SHIFT/F5 followed by TERMINAL SET UP). Remember to restore the original settings before returning the G3-MT to service. n355A EIA-232 Adapter (COMCODE 105 012 637). n258B Six-Port Male Amphenol Adapter (COMCODE 103 923 025). A 258A Adapter and an extension cable can also be used. nD8W 8-wire modular cable of an appropriate length to connect the 258A on the back of the cabinet to the 355A adapter. The relevant COMCODE is determined by the length of the cable, as follows: — 103 786 786 (7 feet)(2.1 m) — 103 786 802 (14 feet)(4.3 m) — 103 786 828 (25 feet)(7.6 m) — 103 866 109 (50 feet)(15.2 m) Slot Selection for Standalone Mode When selecting a carrier slot to use for standalone mode in a port network that does not already contain a TN771D, keep the following points in mind: nA port circuit slot (indicated by a purple label) should be used. The service slot (slot 0) cannot be used for standalone mode, although a TN771D may normally be installed there. n-5 volt power supply must be available in the carrier. (Refer to ‘‘ CARR-POW’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ for a description of carrier power supply units.)
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-57 Packet Bus Fault Isolation and Repair 5 nA slot in the A carrier is preferable for EPNs if the above conditions are met. Entering and Exiting Standalone Mode When in standalone mode, the red LED on the TN771D is lit This is normal and serves as a reminder to remove the TN771 from standalone mode. !CAUTION: The TN771D in standalone must be the only TN771D in the port network. If a TN771D is already in the port network, place that TN771D in standalone mode. Do not insert a second TN771D. Otherwise, the system is not able to detect the extra circuit pack and will behave unpredictably. !CAUTION: If the TN771D packet bus port has reconfigured the packet bus in a Critical Reliability system (indicated by error type 2049 against PKT-BUS), placing the Maintenance/Test in standalone mode causes a loss of service to the packet bus. In this case, this procedure disrupts service. For port networks with a TN771D already installed: 1. Ensure that Alarm Origination is suppressed either at login or via change system-parameters maintenance. 2. Attach the 258A 6-Port Male Amphenol Adapter to the Amphenol connector on the back of the carrier corresponding to the TN771D’s slot. Connect one end of a D8W 8-wire modular cable to port 1 of the 258A. Connect the other end of the cable to a 355A EIA-232 Adapter. Plug the EIA-232 Adapter into the terminal to be used, and turn the terminal on. 3. Reseat the TN771D circuit pack. NOTE: On a Critical Reliability system, this causes a MINOR OFF-BOARD alarm to be raised against PKT-BUS. This alarm is not resolved until the TN771D’s packet bus port (M/T-PKT) is returned to service. To ensure that PKT-BUS alarms have been cleared, it may be necessary to restore the TN771D to normal mode. For port networks without a TN771D installed: 1. Attach the 258A 6-Port Male Amphenol Adapter to the Amphenol connector on the back of the carrier corresponding to the slot into which the TN771D is to be inserted. Connect one end of a D8W 8-wire modular cable to port 1 of the 258A. Connect the other end of the cable to a 355A EIA-232 Adapter. Plug the EIA-232 Adapter into the terminal to be used, and turn the terminal on.
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-58 Packet Bus Fault Isolation and Repair
5
2. Insert the TN771D circuit pack into the slot. The system will not recognize
the presence of the circuit pack.
If the standalone mode is entered successfully, the following is displayed on the
connected terminal:
!CAUTION:
If the above display does not appear, check the wiring between the
terminal and the TN771D, and the terminal parameters settings. If these are
correct, the TN771D may be defective. In such a case, use the following
procedures to exit standalone mode and then test the Maintenance/Test
circuit pack. Refer to M/T-BD and M/T-PKT in
Chapter 9, ‘‘Maintenance
Object Repair Procedures’’. If the TN771D fails while in standalone mode,
the message
TN771 circuit pack failed is displayed, and no further
input is accepted on the terminal. The circuit pack must be replaced.
To exit standalone mode:
1. Remove the 258A Adapter from the Amphenol connector.
2. If the TN771D was installed for this procedure, remove it. Otherwise,
reseat the TN771D.
3. If change system-parameters maintenance was used to disable alarm
origination, re-enable it now.
Using Standalone Mode in Packet Bus Fault
Isolation and Correction
When the TN771D is in standalone mode, three commands are available:
ds Displays the current state of the packet bus leads.
dsa Toggles auto-report mode on and off. In auto-report mode, the
state of the packet bus leads are displayed and the terminal
beeps whenever a change occurs.
? Displays the available commands.
TN771 STANDALONE MODE
(Type “?” at the prompt for help)
Command:
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-59 Packet Bus Fault Isolation and Repair
5
Below is an example of a standalone mode display. The symbols above the line
represent specific leads on the backplane. The bottom line indicates the
following:
NOTE:
This information is available only from the standalone mode. It is not
available from the MT or a remote login.
Figure 5-12
shows the location of the packet bus leads for a given slot as seen
from the front and back of the carrier. OOpen lead
S Shorted lead
blank No fault
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
_______________________________________________
S S O
Command:
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-60 Packet Bus Fault Isolation and Repair 5 Figure 5-12. Packet Bus Leads on the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Front View . . . .. . . .. . . . Backplane SeparationGND GNDL8 H0 SB H2 H4 SF H6 H7 H8 SS CLK +5v +5v +5v +5v +5vL5 LP L2 L4 L1 +5v L7 GND LF GND GND GNDL3 GND L6 GND HP H1 GND H3 GND H5L0 GND GND