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+.
Responding to Alarms and Errors Page 5-1 Safety Precautions 5 DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 5 5Responding to Alarms and Errors Safety Precautions By observing the prescribed safety precautions when working on the system, you can avoid unnecessary disruption of service and damage to the equipment. The items on this list should be a regular part of your routine. !WARNING: Failure to comply with these procedures can have catastrophic effects on system service and hardware. Read the explanations following the list to ensure a complete understanding of these necessary procedures. nWhenever touching any component inside the cabinet, ground yourself by means of the wrist strap attached to the cabinet, and avoid sources of static electricity. nWhen logging on with the terminal, be aware that INADS alarm notification is normally disabled. Log off the terminal when leaving the system. nThink carefully before moving SPE-SELECT switches. Always set them one at a time to the letter of the PPN control carrier that is currently active (unless a procedure specifically tells you to do otherwise). nNever “hot plug” an SPE circuit pack, except for the tape and disk drives on a simplex SPE. Lock and power down the PPN control carrier first. nDo not power down switch node or port carriers to replace a board. nHandle fiber optic cables with care. Bending, piercing, or cutting the cable can sever communications between major subsystems. nWhen disconnecting fiber optic cables, grasp of both the lightwave transceiver and the cable connector.
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-2 DEFINITY AUDIX System Power Procedures 5 nBefore powering down a cabinet or carrier that contains DEFINITY AUDIX circuit packs (TN566), first power down the AUDIX unit to avoid damaging the AUDIX software. Instructions for powering down this unit are in the ‘‘ DEFINITY AUDIX System Power Procedures’’ below, on the circuit pack, and in DEFINITY AUDIX documentation. nWhen you are finished working on a cabinet, replace and secure all panels and covers to avoid disseminating electromagnetic interference. DEFINITY AUDIX System Power Procedures Manually Power Down AUDIX System A yellow caution sticker on the system’s power unit notifies technicians to shut down the DEFINITY 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. The button is located at the top right portion of the front panel. 2. Hold the boot/Shutdown button in until the LCD display flashes the message MSHUT. 3. Release the Boot/Shutdown button. NOTE: The DEFINITY AUDIX System takes about five minutes to shut down. The “heartbeat” indication on the display continues to flash. Manually Power Up AUDIX System 1. Using a pointed object such as a paper clip or a pen (do not use a pencil), press the Boot/Shutdown button. 2. Hold the boot/Shutdown button in until the display indicates the message, BTEST, steady on. 3. Release the Boot/Shutdown button. the DEFINITY AUDIX system takes approximately 5 minutes to power up. nThe display has the following sequence of steady on messages: —OSINIT —OS —AINIT —ADX nThe DEFINITY AUDIX System is now powered up. When the system is in the active state, the display indicates ADX, and the red LED is off.
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-3 Electrostatic Discharge 5 NOTE: When powering up, the DEFINITY ADUXI System automatically reboots. This sequence may show an MD or MJ ADX alarm in the display until the system how powered up. When the system has completed its power up sequence, the display reads: ADX. Electrostatic Discharge Whenever a circuit pack is inserted or removed, the grounding wrist strap attached to the cabinet must be used to avoid damage or disruption from ESD. Use of the wrist strap is also required whenever touching any components inside the switch cabinet, including the SPE-SELECT and EMERGENCY TRANSFER switches. While such actions may not cause a problem in a highly controlled environment, disruption to the system could result when conditions are not ideal, (for example, when the air is very dry). If you must proceed when a wrist strap is not available, grab the outside panel of the cabinet with one hand before touching any components, and keep your extra hand grounded throughout the procedure. Handle a circuit pack only by the faceplate, latch, or top and bottom edges. Do not touch board components, leads or connector pins. Keep circuit packs away from plastic and other synthetic materials such as polyester clothing. Do not set a circuit pack on a non-conductive surface such as paper. Use the anti-static bag, if available. Never hand a circuit pack to another person unless that person is also using a wrist ground strap. The body collects potentially damaging amounts of static electricity from many ordinary activities. The smallest amount of ESD that can be felt is far above that which can damage a sensitive component or disrupt service! Figure 5-1 shows the location of the grounding jack.
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-4 Suppress Alarm Origination [y] 5 Figure 5-1. Multi-Carrier Cabinet ESD Grounding Wrist Strap Jack Suppress Alarm Origination [y] When logged in as “craft,” no alarms are reported to INADS. After logging off, INADS automatically reactivates, and any unresolved alarms are reported to INADS. Also, when logged in as “craft,” an automatic logoff of the terminal occurs after 30 minutes of non-use. At that time, any unresolved alarms are reported to INADS. If you are logged in as “craft” at 2 different terminals, the logoff occurs when the second terminal remains unused for 30 minutes. NOTE: The test inads-link command functions even if INADS Alarm Origination is overridden. ESD JACK
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-5 Reseating and Replacing Circuit Packs 5 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. After reseating a circuit pack, make sure the problem is really fixed by thorough testing and observing the component in operation. When a port board is removed from the backplane, no alarm is logged for about 11 minutes to allow for maintenance activity to proceed. After that, a minor on-board alarm is logged. If the port board is not administered, no alarm is logged. !WARNING: This procedure can be destructive, resulting in a total or partial service outage. !WARNING: Proceed only after consulting and understanding the applicable service documentation for the component. !WARNING: Observe all Safety Precautions described above. !WARNING: If the yellow LED on the circuit pack to be removed is lit, the circuit pack is active and services using it will be interrupted. !WARNING: Follow special procedures for the circuit packs listed 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-6 Replacing a BIU or Rectifier 5 Special Procedures The following circuit packs require special procedures. For components of the SPE, see “Replacing SPE Circuit Packs”. nUN331B Processor (SPE) nTN1650B Memory (SPE) nTN1655 Packet Interface (SPE) nTN1648 SYSAM (SPE) nUN332 MSSNET (SPE) nTN1657 Disk (SPE) nTN1656 Tape (SPE) nTN768/780 Tone/Clock nUN330B Duplication Interface nTN750 Expansion Interface nTN573 Switch Node Interface nTN572 Switch Node Clock nDS1 CONV 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 then follow the steps listed below: 1. Unlock the latch pin. 2. Pull down on the locking lever until the BUI or rectifier moves forward and disconnects from its socket. 3. Pull the BIU or rectifier out just enough to break contact with the backplane connector. Use steady even force to avoid disturbing the backplane. 4. Carefully slide the BIU or rectifier out of slot. To install a BIU or rectifier first attach a grounding strap from the cabinet to your bare wrist than follow the steps listed below: 1. Insert the back edge of the BIU or rectifier making sure that it is horizontally aligned. Slide the unit in to the slot until it engages the backplane. Use extreme care in seating the backplane connectors. 2. Lift the locking lever until the latch pin engages. 3. Verify that the unit is seated correctly by observing the operation of the LED’s.
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-7 Replacing SPE Circuit Packs 5 Replacing SPE Circuit Packs All circuit packs on the processor carrier of the PPN except for the Tone/Clock board are components of the SPE. In addition to the customary MO documentation, there are additional diagnostic techniques for these boards described in the following section, Troubleshooting a Duplicated SPE, and in the section SPE-down Interface. Instructions for replacing the Tone/Clock circuit pack can be found in the TDM-CLK MO documentation. !WARNING: DO NOT “HOT PLUG” AN SPE BOARD. Before removing any SPE circuit pack you must power down the carrier in which it resides, (except in the case of a tape or disk drive in a simplex SPE). Powering down the processor carrier is destructive on a simplex system, causing a total service outage. Be sure you have consulted the appropriate documentation for the component you are replacing. Be sure you are familiar with the precautions at the beginning of this chapter. Simplex SPE This procedure is destructive, resulting in a total service outage except for lines administered with Emergency Transfer. The processor must be powered down to avoid hardware damage. Arrange to perform this procedure when a service outage will have the least impact on the customer. 1. Attach the grounding strap to your wrist. 2. Remove power to the processor carrier, (carrier A), by unplugging the power cords located on the front of the power units located at both ends of the carrier. 3. Remove or reseat the circuit pack using the procedure described previously in Reseating and Replacing Circuit Packs. 4. Restore power to the carrier by plugging both power cords back in. 5. Monitor the system reboot by observing the LEDs and G3-MT output. These indicators are described in Initialization and Recovery. 6. Test the replaced component(s) using the appropriate MO documentation. 7. If the same problem persists, reinstall the original circuit pack to avoid confusing further troubleshooting.
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-8 Replacing SPE Circuit Packs 5 Replacing Circuit Packs on a Duplicated SPE: Lock-and-Power-Down By following the lock-and-power-down procedure, components of a duplicated SPE can usually be replaced with no disruption of service. !WARNING: In a system with duplicated SPEs, a spontaneous SPE interchange may occur if the active SPE is not in good health and either an unlocked SPE completes its reboot and handshake is reestablished, or a locked SPE in which the Standby Maintenance Monitor (SMM) is running is unlocked. !WARNING: Use the status spe command to determine the health of the active SPE and whether an interchange will occur. 1. Enter status spe to verify that the component to be replaced is on the standby SPE. If it is, go to step 2. If the component is on the active SPE, initiate a planned SPE interchange by entering reset system interchange. If the interchange fails, there may be faults on the standby SPE preventing the interchange. You must either repair the fault on the standby SPE first, or force an interchange by using reset system interchange health-override. !WARNING: Forcing an interchange may disrupt service. Arrange to do so at a time suitable for the customer. 2. Enter status port-network 1 to check the health of the PPN Tone/Clocks. The Tone/Clock in the same carrier as the active SPE should have a service state of “in.” If not, repair it using “TDM-CLK” before proceeding. 3. Lock the active SPE. After grounding yourself, move the SPE-SELECT switches on both DUPINT boards, 1 at a time, to the carrier designation of the active SPE. For example, if the A carrier SPE is currently active, move the switches to position “A.” 4. Enter status port-network 1 to verify that the active Tone/Clock is in the same carrier as the active SPE. If not, repeat the command until this condition is met. If the active Tone/Clock has not migrated to the active carrier after 1 minute, there is a Tone/Clock problem. The Tone/Clock problem must be fixed first to avoid service disruption. See “TDM-CLK” maintenance object.
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-9 Replacing SPE Circuit Packs 5 5. Power down the standby processor carrier by: a. Remove the power plug from the left side of the carrier first. b. Remove the second power plug from the right side of the carrier. 6. Remove the failed circuit pack and replace it with a new one of the same type. 7. Power up the standby processor carrier by: a. Insert the power plug in the right side of the carrier first. b. After inserting the first power plug in the right insert the second power plug in the left side of the carrier. The red and green LEDs will light indicating restoration of power and testing of the boards. These LEDs will go out as tests pass. 8. This step is optional. Use a terminal and the SPE-down interface to test the standby SPE as follows. If a terminal is connected to the STANDBY connector on the back of either PPN control carrier, the power-up reboot of the standby aborts and the SPE-Down interface can then be used to enter commands to the LMM firmware. Use t al, or the SPE-Down interface test command for the replaced component, to confirm that the problem is fixed. Repair any failures reported. When testing is finished, move the SPE-Select switches to the AUTO position one at a time. This unlocks the standby and begin a reboot which can be monitored from the terminal. 9. Verify that the standby is up. Regular flashing of the yellow LED on the Processor board indicates that the standby SPE is up and cycling. If the yellow LED is not flashing after five minutes, test the standby SPE as described in the above step. Relock the SPE standby, attach a terminal to the STANDBY connector on the back of either PPN control carrier and execute the SPE-down interface tests. All tests must pass before unlocking. 10. If the standby SPE is still locked, unlock it by returning both SPE-Select switches to the AUTO position one at a time. 11. Enter status spe to confirm that handshake is up. This should occur within 2 minutes. When it is, enter the test long clear command for the replaced component. If an alarm does not clear, consult the appropriate MO. 12. Verify that the standby SPE is brought into service. Enter status spe. The standby SPE is fully operational when handshake is up, shadowing is on, and memory is refreshed. It can take up to 10 minutes after unlocking for the standby to be brought fully into service. 13. If the standby SPE does not fully return to service, consult ‘‘ STBY-SPE (Standby SPE Maintenance)’’.
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-10 Troubleshooting a Duplicated SPE 5 Troubleshooting a Duplicated SPE The section on maintenance object ‘‘STBY-SPE (Standby SPE Maintenance)’’ contains procedures for troubleshooting specific problems such as handshake failure, memory shadowing failure, and poor state of health. The following procedures describe a method for determining the cause of a spontaneous SPE interchange and resolving any related problems. If a spontaneous SPE interchange has occurred, assume that a serious fault has occurred on the SPE that is currently the standby. The following symptoms indicate that a spontaneous SPE interchange has taken place: nA MINOR alarm with error type 103 is logged against STBY-SPE. nAn interchange entry is recorded in the initcauses log. nThe system is put into recent interchange mode, which prevents further SPE interchanges from taking place. The presence of recent interchange mode is displayed on the status spe screen. The system is released from this mode, and the minor alarm is cleared, after 1 hour, or upon the execution of test spe-standby long, regardless of whether all tests pass. There are three possible causes of a spontaneous interchange: nMajor hardware failure nFailed recovery that has been software escalated nSwitching both SPE-SELECT switches to the standby carrier (not a recommended procedure) In the last case, the interchange is not fault-driven, and no specific repair action is required. To determine whether this is the case, enter display initcauses. If the interchange was initiated by the SPE-SELECT switches, the Cause field will appear as in the following example. If the interchange was fault-driven, there are two ways of finding the cause. 1. Using alarm and error logs in conjunction with the timestamp described above. After a spontaneous SPE interchange has occurred, the Alarm Log retains a record of any MAJOR ON-BOARD alarm against an SPE component that took place before the interchange. This record is retained for three hours and may indicate the cause of the interchange when testing is not possible or conclusive. Other information in the Error Log may also be helpful. 2. Testing the standby SPE when the logs do not identify the problem. Cause Action Escalated Carrier Time SPE-SELECT switch 1 no 1B 11/27 14:53