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-71 Packet Bus Fault Isolation and Repair 5 NOTE: The Tone/Clock circuit pack should be the next-to-last one checked. (The TN771D must be reseated after the Tone/Clock is reinstalled.) Refer to Procedure 3 for the TN768 or TN780 Tone/Clock circuit pack in a PPN with duplicated SPEs. 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. Keep in mind that there may be more than one failure cause. In Procedure 2, you may try one circuit pack at a time, or multiple circuit packs simultaneously. The allowable level of service disruption should guide this choice. If the entire port network can be disrupted, trying large groups of circuit packs will save time. If traffic is heavy, trying 1 circuit pack at a time is slow but will minimize outages. If the TN771D Standalone mode does not indicate packet bus faults, perform Procedure 2 for only the port circuit packs (purple slots) listed in Table 5-3 in Procedure 1. In this case, you need not check for problems with the backplane pins. It is sufficient to determine whether the problem is resolved by removing circuit packs. If you decide to remove multiple circuit packs, consider working with an entire carrier at a time to more quickly and reliably determine which circuit packs are not the source of trouble. Any circuit packs, (packet or non-packet), that have been recently inserted should be checked first. Packet circuit packs should be checked before non-packet circuit packs. 1. Remove one or several circuit packs. 2. Determine if the packet bus fault is still present. If not, go to step 4. 3. If the packet bus fault is still present: a.Determine if the backplane pins in the removed circuit pack’s slot are bent using the output from the Maintenance/Test standalone mode and the backplane illustrations which appear earlier in this discussion. b. If the backplane pins are bent: Power down the carrier (see ‘‘ Replacing a BIU or Rectifier’’), straighten or replace the pins, reinsert the circuit pack and restore power. Repeat Step 2 for the same circuit pack. c. If the backplane pins are not bent: Reinsert the circuit pack(s), and repeat this procedure for the next set of 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-72 Packet Bus Fault Isolation and Repair 5 4. If the packet bus fault is not present: a. Reinsert circuit packs one at a time and repeat the following substeps until all circuit packs have been reinserted. b. Determine if the packet bus fault has returned. c. If the packet bus fault has returned, the reinserted circuit pack is defective. Replace the circuit pack and then continue. d. If the packet bus fault does not return when all of the circuit packs have been reinserted, you are finished. Continue with Procedure 3 if all the port circuit packs have been checked, but the packet bus fault is still not resolved. Procedure 3 Procedure 3 removes and reinserts SPE and EPN control circuit packs one at a time. In the PPN, the following SPE circuit packs either use the packet bus or are connected to it in the backplane wiring: nTN1655 Packet Interface nTN768/TN780 Tone/Clock nUN332 MSSNET In the EPN, the following control circuit packs either use the packet bus for communication or are connected to it in the backplane wiring: nTN775 EPN Maintenance Board nTN768/TN780 Tone/Clock These are the only SPE and EPN control circuit packs that are likely to cause a packet bus problem in a stable system. Perform this procedure on only these circuit packs. If the TN771D Standalone mode does not indicate packet bus faults, perform Procedure 3 for only the Packet Interface and Tone/Clock circuit packs and do not check for problems with the backplane pins. Determining if the problem is resolved by removing circuit packs is sufficient. For a system with simplex SPE: 1. Power down the control carrier. Refer to ‘‘Replacing SPE Circuit Packs’’. 2. Remove the suspect circuit pack. 3. Determine if the backplane pins in the removed circuit pack’s slot are bent. 4. If the backplane pins are bent: a. Straighten or replace the pins.
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-73 Packet Bus Fault Isolation and Repair 5 b. Insert the same circuit pack. 5. If the backplane pins are not bent: a. Replace the circuit pack (reinsert the old one if a replacement is not available). 6. Turn the power back and allow the system to reboot. This may take up to 12 minutes. Log in at the terminal. 7. Determine if the packet bus fault is still present. If not, you are finished. If the problem is still present, a. If the old circuit pack was reinserted in Step 5, replace the circuit pack, and repeat Procedure 3. b. If the circuit pack was replaced in Step 5, repeat Procedure 3 for the next SPE circuit pack. If Procedure 3 fails to identify the cause of the problem, go to Procedure 4. For a system with duplicated SPEs: 1. For SPE circuit packs, follow the ‘‘Replacing Circuit Packs on a Duplicated SPE: Lock-and-Power-Down’’ procedure within the ‘‘Replacing SPE Circuit Packs’’ section to remove and replace the circuit pack. 2. To remove an EPN Tone/Clock circuit pack, use set tone-clock if necessary to make the suspect circuit pack the standby. (Always check the status of the standby Tone/Clock with status port network before executing an interchange.) 3. Determine if the backplane pins in the removed circuit pack’s slot are bent. 4. 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. 5. If the backplane pins are not bent: Insert or replace the circuit pack. 6. Determine if the packet bus fault is still present. If not you are finished. 7. If the packet bus fault is still present, do the following: a. If the old circuit pack was reinserted in Step 5, replace the circuit pack and repeat Procedure 3 starting at Step 2. b. If the circuit pack was replaced with a new one, proceed with 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-74 Packet Bus Fault Isolation and Repair 5 8. Repeat this procedure for the other SPE or Tone/Clock. If both have already been checked, go to the next step. 9. If all SPE and/or EPN control circuit packs have been checked and the problem is not resolved, continue with Procedure 4. Procedure 4 Procedure 4 is used when the preceding procedures fail or when open leads are present. It is helpful in identifying multiple circuit pack faults and carrier hardware faults. It attempts to isolate the failure to a particular set of carriers and checks only the circuit packs in those carriers. In Procedure 4, the TDM/LAN Cable Assemblies and TDM/LAN termination resistor packs are replaced. If this action does not resolve the packet bus fault, the carriers are reconfigured by moving the termination resistor packs on the carrier backplanes in such a manner that certain carriers are disconnected from the bus. To terminate the packet bus at the end of a particular carrier, unplug the cable that connects the carrier to the next carrier and replace the cable with a TDM/LAN terminator resistor pack (see Figure 5-16 ). When the length of the packet bus is modified with this procedure, circuit packs that are essential to system operation (and the TN771D Maintenance/Test in standalone mode) must still be connected to the new ‘shortened’ packet and TDM busses. !DANGER: Power must be removed from the entire port network before any cables or terminators are removed. Failure to do so can cause damage to circuit packs and power supplies, and can be hazardous to the technician. !DANGER: Circuit packs in carriers that are not part of the shortened bus are not inserted. As a result, these circuit packs are not alarmed Ignore alarm status for these circuit packs for now All alarms should be resolved when the cabinet is restored to its original configuration.
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-75 Packet Bus Fault Isolation and Repair 5 Figure 5-16. Carrier Rewiring Example—Rear View of Multicarrier Cabinet Procedure 4 consists of two parts. Part 1 attempts to clear the packet bus fault by replacing all the bus cabling and terminators within a port-network. Part 2 attempts to isolate the fault to a particular carrier by extending the packet bus from the control carrier to additional carriers one at a time. Part 1: 1. Power down the port network. 2. Replace all of the TDM/LAN Cable Assemblies and both TDM/LAN Terminators. 3. Restore power to the port network. 4. Determine if the packet bus fault is still present. 5. If the packet bus fault is resolved, the procedure is completed. Otherwise, go to Part 2. TDM/LAN Bus Cable TDM/LAN Bus Terminator Normally Con®gured Cabinet (All 5 Carriers Used)Bus Shortened to Carrier A Only (Control Carrier)Shortened Bus Extended to Include A and B Carriers Carrier D Carrier EFans Carrier A Carrier B Carrier C
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-76 Packet Bus Fault Isolation and Repair 5 Processor Port Network: 1. Power down the cabinet and terminate the packet bus so that it extends only from the carrier that contains the active SPE (A or B) to the carrier that contains the Maintenance/Test circuit pack. 2. Power up the cabinet, allow the system to reboot, and determine if the packet bus fault is still present. If not, proceed to the next step. If there are shorts on the packet bus, perform Procedures 2 and/or 3 for the circuit packs in the active SPE and carriers connected to it on the shortened bus. (Procedure 2 is performed for port circuit packs, and Procedure 3 is performed for SPE circuit packs.) 3. If the packet bus fault is not present, extend the packet bus to another carrier, and repeat the procedure in the previous step. When the addition of a carrier causes the fault to recur, and if there are shorts, perform Procedure 2 and/or Procedure 3 for only the circuit packs in that carrier. 4. If the packet bus fault recurs when the packet bus is extended, and if there are no shorts, or Procedures 2 and 3 do not resolve the problem, the added carrier(s) that caused the problem to recur are defective and must be replaced. Expansion Port Networks: 1. Place the Maintenance/Test circuit pack into a carrier that contains the active Expansion Interface circuit pack to permit isolation of the failure to the smallest possible number of carriers. 2. Power down the cabinet and terminate the packet bus on the carrier with the M/T and active EI. 3. Determine if the packet bus fault is still present If so, and if there are shorts on the packet bus, perform Procedure 2 and/or Procedure 3 for only the circuit packs in carriers connected to the ‘‘shortened’’ packet bus. 4. If the packet bus fault is not present, extend the packet bus to another carrier, and repeat the procedure in the previous step. When a carrier that causes the fault to recur is added, and if there are shorts, perform Procedure 2 and/or Procedure 3 for only the circuit packs in that carrier. 5. If the packet bus fault recurs as the packet bus is extended, and if there are no shorts, or Procedures 2 and 3) do not resolve the problem, the added carrier(s) that caused the problem to recur are defective and must be replaced.
Additional Maintenance Procedures Page 6-1 Software Updates 6 DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 6 6Additional Maintenance Procedures Software Updates A software update is the complete replacement of the software load running on a switch with a new version of software. Updates are used to provide new features and improved services, and to repair bugs discovered in the field. Note that the process is called a software update; the command used is upgrade software. A description of this command appears in Chapter 8, ‘‘ Maintenance Commands’’. Software field updates are partial replacements of a software load normally used for emergency bug fixes. Usually, a field update is transmitted electronically to the system from a remote site, but a technician must be on site to apply the update to backup tapes and insure that the system returns to normal operation. This procedure should be guided by the remote facility applying the update. Refer to DEFINITY Enterprise Communications Server Release 5.4 Upgrades and Additions for R5r for specific upgrade information. Software Version Number Each software load is identified by a version number. The following are typical software version numbers displayed when list configuration software-version is entered: SOFTWARE VERSION: DG3r01.06.1.00.0 SOFTWARE VERSION: G3r5.01.2.0.078 This identifier is also called the release number or the vintage number. Version numbers are interpreted as follows:
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Additional Maintenance Procedures Page 6-2 Software Updates 6 Release 5r loads: The boot image field contains “m” (mips) for G3r systems. The system expects any software upgrade to be going from a lower, or older version number, to a higher, or newer version number. To install an older version (for example, when backing out a failed upgrade), follow normal escalation procedures to avoid putting the system into a corrupted state. Each software version also has a compatibility index of the form: Differences between old and new version numbers and compatibility indexes can be used to determine what service effects can be expected from the update. See the ‘‘ Service Effects of a Software Update’’ section that follows. Service Effects of a Software Update Simplex SPE The upgrade software command executes a system reboot similar to a reset system 4. Emergency transfer is invoked and all calls drop. The MT login is terminated and error logs are cleared. The service outage lasts for a period of up to 15 minutes. Results of each step in the upgrade process and initialization diagnostics are displayed on the terminal screen. Screen output is described in Maintenance Commands, upgrade software. Failure of initialization will produce an SPE-down mode, described in Initialization and Recovery. Translations are reloaded from the primary storage device and reformatted for the new software if necessary. Duplicated SPE On a system with a duplicated SPE, a software update may be either call-preserving or call-dropping. The compatibility of the old and new versions determines which type of update is performed. If the major fields of the compatibility indexes of the two versions are equal, then a call-preserving update is possible. The documentation accompanying the update tapes (Engineering Design Information, or EDI, and the Release Letter) should confirm this. With rare exceptions, this is the case when the Feature Version and Product ID numbers match.G3r5 m 01 2 0 078 Product Boot Major Minor Unscheduled Load ID Image Release Release Release Number 81 Major Field Minor Field
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Additional Maintenance Procedures Page 6-3 Software Updates 6 If these conditions are not met, The upgrade software call-override option must be used, and the update will result in a system reset level 2 (cold-2 restart). An additional option, preserve-calls, can be added to force the system to attempt to preserve calls, but this must be used with care. If the incompatibility is great enough, this option may cause the system to escalate to a reboot (reset system 4). It is recommended that you escalate any such software update. Call-Preserving Update During a call-preserving update, calls in which two or more parties are connected and talking are preserved. The following types of calls are dropped: wideband calls, held calls, dialing calls, and calls that are connected to announcements, speech synthesizers, or tones. Administered connections are dropped and automatically restored. Feature activation attempts are ignored. No new calls are processed for a brief period. This period usually lasts less than 5 seconds but can last up to 1 minute depending on traffic load during the SPE interchange. Conference calls that attempt a new connection are either ignored or dropped. Call-Dropping Update During a call-dropping update, the effect will be similar to a cold-2 restart (reset system 2). All calls and system links drop, and the MT login is terminated. The service outage lasts up to 4 minutes. Preparing for a Software Update 1. Notify users of anticipated service effects described in the preceding section and arrange to do the update at a suitable time. Also advise appropriate users of the following feature interactions: nAdministered connections are temporarily dropped. nLeave Word Calling messages stored in the SPE are lost. Those stored in a Message Server Adjunct or AUDIX system are saved. nSome feature settings will be lost and must be restored afterward. The effect is the same as a cold-2 restart. Features affected include night service, trunk/hunt group control, and manual/clock-manual override status on time of day routing. For example, hunt groups and attendant are put into night service after the update. nACD queues will be lost. There is no mechanism to drain the queues. CMS or BCMS can be used to monitor the queue lengths. If it is important to empty all queues before the update, you must coordinate with the customer to redirect traffic away from ACD splits before the update. Changing vectors to temporarily route calls to a disconnect announcement is one way to accomplish this. ACD agents will need to log in again after the update and their status lamps may be incorrect for about an hour (until periodic background maintenance completes one cycle).
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Additional Maintenance Procedures Page 6-4 Software Updates 6 nCMS links are dropped and restored, resulting in a loss of incoming data during the upgrade. Data loss can be minimized by performing the update soon after the end of a CMS measurement interval. nWideband calls are dropped. 2. Some information which is stored in system memory will be lost and must be manually recorded and then re-entered after the update: nRecord all busied out maintenance objects. Enter display errors print, and select error type 18 on the menu. All busyouts will be lost during the update and must be reentered afterward. Disabled maintenance objects will likewise be re-enabled by the update. nAll measurement data stored in memory, including BCMS, is lost. Print any desired reports before the update. nEnter list report-scheduler. Reports that are currently printing or queued will be lost. Wait until reports are finished printing or notify the customer. Reports are printing if the Link State field displays up on the status sp-link screen. nEnter list wakeup print and list do-not-disturb stations print. These feature settings will be lost and must be re-entered afterwards. 3.Make sure that the system’s health and activity can support a successful update: nEnter status spe and verify that the state of health of the SPE is functional. This must hold true for active and standby SPEs when duplicated. nEnter display alarms and display errors. Resolve any active alarms or errors against SPE components or the PPN Tone-Clock. nEnter status logins and make sure that no other logins except yours are active. nEnter status health and look at the amount of load on the system. If call processing is greater than 50 percent, an update is not recommended due to increased customer impact. nDisable TTI changes by the change system-parameters features. nEnter change system-parameters maintenance and make sure that scheduled daily maintenance will not be running during the update. The Start Time field should be set to a time well after the session will end. If scheduled daily maintenance is running and needs to be shut off, set the Stop Time field to one minute after the current time. Be sure to restore the original settings when finished.