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-61 Packet Bus Fault Isolation and Repair 5 Figure 5-13. Packet Bus Leads on the Backplane +5v LP L2 L4 L7 L8 H0 SB H2 H4 SF H6 H7 H8 GND SS CLK GND GND +5v +5v +5v+5v +5vL5 L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND L3 GND L6 GND HP H1 GND H3 GND H5 GND LF GND GND GND . . . . . . . . Back View . . . .. . . .. . . . L0
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-62 Packet Bus Fault Isolation and Repair 5 Special Precaution Concerning the TN771D A TN771D Maintenance/Test circuit pack must be taken to the customer site if: nThe 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; a Minor alarm is indicated by Error Type 2049. nTest #572 of the PKT-BUS test sequence is the only test that fails. This precaution is taken because certain failures of the Maintenance/Test circuit pack can appear as packet bus failures. To ensure that the problem is indeed with the packet bus, proceed through the following steps: 1. If the TN771D Maintenance/Test circuit pack is replaced during this process, enter the test pkt P long command to determine if the packet bus faults have been resolved. If there are still packet bus problems, correct them by using the procedures in the sections that follow. 2. If the Maintenance/Test circuit pack was not replaced, enter test pkt P. Record the results (PASS/FAIL/ABORT) and error codes for Test #572. 3. Enter status port-network P. Record the information listed for PKT-BUS. 4. Busyout the Maintenance/Test circuit pack with busyout board UUCSS. 5. Replace the Maintenance/Test circuit pack with the new circuit pack. 6. Release the Maintenance/Test circuit pack with release board UUCSS. 7. Enter the test pkt P and status port-network P commands as described in Steps 2 and 3. 8. If the data matches the previously recorded data, a packet bus problem exists, and the original TN771D Maintenance/Test circuit pack is not defective. Reinsert the original TN771D, and correct the packet bus problem by using the procedures in the sections that follow. 9. If the data does not match the previously recorded data, the original TN771D circuit pack is defective. If there are still indications of packet bus problems, correct them by using the procedures in the following sections. Packet Bus Fault Isolation Flowchart The flowchart below shows the steps to be taken for isolating and resolving packet bus problems. The order in which the maintenance objects should be examined can be determined by assessing how wide-spread the failure is. For example, since all ISDN-BRI devices communicate with the TN1655 Packet Interface circuit pack, this MO should be examined early in the sequence. On the other hand, a failure of a TN570 circuit pack in an EPN may cause ISDN-BRI failure in the EPN, but not in the PPN. Whenever the flowchart refers to MO documentation keep in mind that the repair procedure for that MO may in turn refer to another MO’s repair procedure. The flowchart tries to coordinate these procedures so that a logical flow is maintained
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-63 Packet Bus Fault Isolation and Repair 5 if the packet bus problems are not resolved via the first set of repair procedures. However, a packet bus failure can lead to a somewhat haphazard referencing of various MO procedures that may result in taking steps that are repetitive or unnecessary. If this occurs, return to the flowchart at the step that follows the reference to Chapter 9, ‘‘ Maintenance Object Repair Procedures’’, and continue from there. The following status commands can also help diagnose packet bus problems, especially when logged in remotely. status port-network P status packet-interface status pnc status bri-port status station status data-module status link status pms-link status sp-link status cdr-link status journal-link
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-64 Packet Bus Fault Isolation and Repair 5 Figure 5-14. Troubleshooting Packet Bus Problems (Page 1 of 2) Boldface letters in the flowchart refer to paragraphs in the explanatory section that follows. YES YESYES YESYES YE S YE S YES NO NO NO NO To page 2NO NO NO NOAAre there alarms or errors TDM -CLK? CIs only asinglePN affected? DAre there alarms or errors against PKT-INTF? FAre there alarms or errors against EXP-INTF? BAre the packet bus problems resolved? Are the packet bus problems resolved? Are the packet bus problems resolved? Is packet bus use enabled?Refer to maintenance related system parameters form in chapter 5 Follow the repair procedure for TDM -CL K Follow the repair procedure for PKT-INTF Follow the repair procedure for EXP-INTF ECheck each port network (PPN f irst) A START END END END fcdfpbp1 RPY 101397
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-65 Packet Bus Fault Isolation and Repair 5 Figure 5-15. Troubleshooting Packet Bus Problems (Page 2 of 2) Boldface letters in the flowchart refer to paragraphs in the explanatory section that follows. Flowchart Notes The following paragraphs refer by letter to corresponding entries in the preceding flowchart. Individual errors and alarms are not detailed in the flowchart. When referring to explanations of these in Chapter 9, ‘‘ Maintenance YE S YESYES YESYES YES YE S NO NO NO NO From page 1 NO NO NO GIs a TN771 present in this port network? JDoes the TN771 indicate packet bus faults?KIs the problem isolated to a single board? HAre there alarms or errors against M/T-PKT? Are the packet bus problems resolved? Are the packet bus problems resolved? Are the packet bus problems resolved? MFollow the packet bus fault isolation and correction procedures LFollow the board, port and/or endpoint repair proceduresFollow the repair procedure for M/T-PKT IPlace the TN771 in standalone mode Escalate the problem A END ENDEND fcdfpbp2 RPY 101397
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-66 Packet Bus Fault Isolation and Repair 5 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. a. Problems with the system clock (TDM-CLK) can cause service disruptions on the packet bus. All alarms active against TDM-CLK should be resolved first, even if the explanation refers only to TDM bus. A packet bus problem cannot cause a TDM-CLK problem, but a TDM-CLK problem can cause a packet bus problem. b. Throughout the flowchart, the question, ‘‘Are the packet bus problems resolved?,’’ refers to the problems that led you to this chart, and can involve several checks, such as: nAre all packet bus alarms resolved? nAre all packet circuit pack port and endpoint alarms resolved? nAre all ISDN-BRI stations/data modules, ASAI adjuncts, System Port supported adjuncts, Packet Gateway supported adjuncts, and ISDN-PRI D-channel links in service? nDoes the Maintenance/Test packet bus port (in normal or standalone mode) still indicate a packet bus fault? c. If only a single PN is affected, the Packet Interface is probably not the source of the problem. Nonetheless, if all of the ISDN-BRI, Packet Gateway, Packet Data, and Universal DS1 circuit packs are located in a single EPN, assume that the answer to this question is ‘‘No,’’ and check the Packet Interface. d. A packet problem that affects more than one port network is probably caused by either a Packet Interface failure or a PPN packet bus failure. The Packet Interface is checked before the packet bus. e. Because the packet bus in each port network is physically separate, each affected port network must be checked individually. The PPN should be checked first since any EPN packet problems are usually resolved once a PPN packet problem is resolved. After resolving the problem in one port network, make sure that problems in other port networks have also been resolved. f. This step applies only when attempting to resolve an EPN packet bus problem. When checking the Expansion Interfaces in an EPN, be sure to check the corresponding one(s) in the PPN. (G3r supports only the TN570 Expansion Interface, not the earlier TN776 Port Network Interface). g. If a TN771D is not present, one must be installed to accommodate the standalone mode. See the above section on standalone mode. h. If a TN771D is present, it can fail in such a way that it eventually disrupts the packet bus or misinterprets a packet bus problem. i. If work is being done on-site, follow the procedures described earlier in this discussion on standalone mode. If work is not being done on-site, go to the next step.
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-67 Packet Bus Fault Isolation and Repair 5 j. The answer is yes if any of the following apply: nThe TN771D in standalone mode indicates any faulty leads. nTest #572 in the PKT-BUS test sequence fails. nThe status port-network P display indicates that faulty leads are present and the TN771D in the port network is known to be functioning correctly. k. If the non-functional endpoints are isolated to a single circuit pack, that circuit pack is probably the cause of the problem. l. Investigate errors and alarms in the following order: 1. Circuit pack-level 2. Ports 3. Endpoints m. Follow the ‘‘ Troubleshooting Procedures’’ outlined later in this discussion. If the packet bus problem cannot be resolved with these procedures, follow normal escalation procedures. Correcting Packet Bus Faults The Status Port-Network Command Status port-network P displays include the service state, alarm status, and, if the Maintenance/Test packet bus port is present, the number of faulty and open leads for the packet bus in the specified port-network. This information can be used to determine the urgency of the repair. In general, a service state of “out” indicates extreme urgency, while a service state of “reconfig” indicates moderate urgency. NOTE: Ultimately, the urgency of a repair is determined by the customer’s requirements. A customer who uses ISDN-BRI for station sets, or who relies heavily on packet bus supported system adjunct features like DCS, Audix, or CDR, probably considers a packet bus failure critical. On the other hand, a customer with little ISDN-BRI service and no adjunct features may consider even an uncorrectable packet bus fault unimportant, and may prefer to delay repairs due to their disruptive nature. If background maintenance is running on the packet bus when the status port-network command is issued, the data reported for the packet bus may be inconsistent due to updating by the tests. If the data seems inconsistent, enter the command again.
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-68 Packet Bus Fault Isolation and Repair 5 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. Then test the Maintenance/Test packet bus port with test port UUCSSpp. See ‘‘ Special Precaution Concerning the TN771D’’ above if any problems are suspected. NOTE: If the carrier into which a TN771D Maintenance/Test circuit pack is inserted does not have a -5V power supply, the Maintenance/Test packet bus port reports 24 open leads in response to status port-network, or Test #572 of the PKT-BUS test sequence. Refer to CARR-POW maintenance in Chapter 9 to ensure that a -5 volt power supply is available. Considerations for Duplicated Systems Some packet bus-related components are duplicated in systems with one of the duplication options: nIn High Reliability systems (duplicated SPE, simplex PNC), Packet Interface circuit packs are duplicated with the SPEs, a Maintenance/Test circuit pack is required in the PPN, and Maintenance/Test packet bus reconfiguration is not enabled. nIn Critical Reliability Systems (duplicated SPE and PNC), the Packet Interface circuit packs are duplicated, Maintenance/Test circuit packs are required in all port networks, and packet bus reconfiguration by the Maintenance/Test circuit packs is enabled. If a packet bus problem is caused by a duplicated component, switching to the standby component may alleviate the problem and isolate the faulty circuit pack. Start by executing the commands in the following list when they apply. nreset system interchange: If this command resolves the packet bus problem, the problem is with the Packet Interface in the SPE which was just switched to standby. Refer to ‘‘ PKT-INT (Packet Interface Circuit Pack)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. nreset pnc interchange: If this command resolves the packet bus problem, the problem is with the EIs or the link on the PNC (a or b) that just became the standby. Refer to ‘‘ EXP-INTF (Expansion Interface Circuit Pack)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. nset tone-clock: If this command resolves the packet bus problem, the problem is with the Tone/Clock that just became the standby. Refer to ‘‘ TDM-CLK (TDM Bus Clock)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ of this document. Continue with the procedures in the next section.
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-69 Packet Bus Fault Isolation and Repair 5 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. The first two faults cause shorts, while the third fault causes either shorts or opens. There are four procedures for correcting packet bus faults. Which are used depends on the nature of the fault. For example: nIf the Maintenance/Test packet bus port is activated, and if there is an indication of open leads on the packet bus from status port-network or Test #572, go directly to Procedure 4. Procedures 1 through 3 try to locate faulty circuit packs or bent pins and these do not cause open faults. nIf there are both shorts and opens, start with Procedure 4, and return to Procedure 1 if shorts persist after the open leads are fixed. !CAUTION: Packet bus fault isolation procedures involve removing circuit packs and possibly disconnecting entire carriers These procedures are destructive. Whenever possible, implement these procedures during hours of minimum system use. !CAUTION: To replace the following circuit packs, follow instructions in the appropriate sections: Tone-Clock (‘‘ TONE-BD (Tone-Clock Circuit Pack)’’), Expansion Interface (‘‘ EXP-INTF (Expansion Interface Circuit Pack)’’), Packet Interface (‘‘ Replacing SPE Circuit Packs’’). When the procedure asks whether the packet bus problem has been resolved, the following conditions should all be met: nAll faulty leads reported by the TN771D standalone mode should no longer be reported. nAll alarms against the packet bus and packet circuit packs have been resolved. nAll ISDN-BRI stations and data modules and all relevant ASAI, System Port, and Packet Gateway supported adjuncts are in service.
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-70 Packet Bus Fault Isolation and Repair 5 Procedure 1 Procedure 1 determines whether any circuit packs that use the packet bus have faults. For each circuit pack type in Table 5-3 proceed through the steps below. Check the circuit pack in the order presented by the flowchart which appears earlier in this discussion unless newly inserted circuit packs are involved. Newly added boards are the most likely cause of a problem. 1.Display errors and display alarms for the circuit pack. 2. For any errors or alarms, follow the repair actions recommended in Chapter 9, ‘‘ Maintenance Object Repair Procedures’’. 3. After following the recommended repair actions, whether they succeed or fail , determine if the packet bus fault is resolved. If so, you are finished. 4. If the packet bus fault is still present, apply this procedure to the next circuit pack. 5. If there are no more circuit packs in the list, go to Procedure 2. Procedure 2 Procedure 2 removes and reinserts port circuit packs (purple slots), and the Expansion Interface one or several at a time. Use Procedure 2 for each port circuit pack in the port network until the problem is resolved or all port circuit packs have been tried. NOTE: The Expansion Interface circuit pack should be the last one checked since removing it disconnects the EPN. To check an active Expansion Interface in a system with duplicated PNC, use reset pnc interchange to make it the standby. (Always check the status of the standby before executing an interchange.) Table 5-3. Packet Circuit Packs Circuit Pack Name Circuit Pack Code Associated Maintenance Objects ISDN-BRI TN556 BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ Maintenance/Test TN771D M/T-BD, M/T-PKT Packet Gateway TN577 PGATE-BD, PGATE-PT Packet Data TN553 PDATA-BD, PDATA-PT Universal DS1 TN464F UDS1-BD, ISDN-LNK Packet Interface TN1655 PKT-INTF Expansion Interface TN570 EXP-INTF