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 Initialization and Recovery Page 4-9 SPE-Down Command Interface 4 SPE-Down Command Interface A limited command interface called the SPE-down interface can be used to communicate with low level firmware when system software is unavailable for executing the usual maintenance commands. This is useful in three situations. nThe SPE is down in a system without duplicated SPEs nThe standby SPE is down in a system with duplicated SPEs nOne SPE is locked standby in a system with duplicated SPEs Memory Board Burst Test Replace memory board Replace processor board The carrier may be defective. Follow normal escalation procedures. Sysam Test Replace the SYSAM board. Vm Test Replace the processor. Exception Test Replace the processor. MSS Test Replace the MSSNET board. Replace the processor. Sanity Timer Test Replace the SYSAM board. Dupint Test Replace the DUPINT board. Disk Test Replace the disk drive. Loading Disk Reformat disk. Replace the MSSNET board. Ram Data Checksum Test Reboot from whichever device (tape or disk) was not used for the failed reboot. Replace memory. Ram Text Checksum Test Reboot from whichever device (tape or disk) was not used for the failed reboot. Replace memory. Tape Test Replace the tape cartridge. Replace the tape drive. Replace the MSSNET board. Pktint Reset Test Replace the packet interface board. Mem Board Couple Test (Extended reboot only)Replace the indicated memory board. Table 4-1. Initialization Diagnostics for All Reset Levels — Continued Test Description/Recommendation Continued on next page
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-10 SPE-Down Command Interface 4 SPE-Down Mode Severe problems with components of the SPE may render a non-duplicated system incapable of call processing and other normal operations. When this happens, the system enters SPE-down mode and software is no longer in control. If the SPE is duplicated, this situation only occurs when both SPEs have fatal faults. Otherwise, if one SPE goes down, an interchange will occur and the system will run on the newly active SPE. SPE Locked Standby or Standby SPE-Down The SPE-down interface can be useful when repairing a standby SPE on a duplicated system. For example, if handshake communication is down, this is the only way to communicate with the standby SPE. Or, if a circuit pack on the standby has been replaced, this interface allows you to test both that circuit pack and the rest of the standby SPE before unlocking. When the standby SPE on a duplicated system is down, or locked by means of the SPE-Select switches, it is no longer in communication with the active side, and the system is functionally unduplicated. In this state, the normal Maintenance User Interface is unavailable to the standby SPE. You can use the SPE-down interface to test the standby SPE and verify its health before rebooting or unlocking. A test of all SPE boards takes only a short time and ensures that all problems have been fixed and the SPE is ready to return to service. Bringing Up the SPE-Down Interface When SPE-down mode is in effect, the red LED will be lit on the Processor circuit pack and the system will present the following message: An alarm-notification call already in progress will preempt input from the terminal. When the call is completed or dropped, the system displays the results of the call and a welcome message with one of the following prompts, indicating which SPE is currently connected to the terminal.*********** SPE DOWN MODE ************* SPE_A_DOWN>If SPE-A was active when the system went down SPE_B_DOWN>If SPE-B was active when the system went down SPE_DOWN>If the SPE is unduplicated
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-11 SPE-Down Command Interface 4 You can now enter SPE-down interface commands as described in ‘‘Using the SPE-Down Interface’’. If the prompt does not appear, check the connections between the terminal and the control carrier. Make sure the cable is connected to the connector labeled ACTIVE. If possible, try a different cable and/or terminal. If the prompt is still not present, replace the SYSAM circuit pack. If the SPE remains down with no prompt, follow normal escalation procedures. To return the standby SPE to service, see the following section on ‘‘ Bringing the SPE Back into Service’’. SPE Locked Standby or Standby SPE-Down To bring up the SPE-down interface on a functioning duplicated system, connect the terminal to the STANDBY terminal connector on the rear panel of either processor carrier. Assuming all cabling is intact, either connector will access the SPE which is standby. If the standby SPE is down, the message and prompt shown above are displayed. To enter SPE-locked-standby mode, carefully, and one at a time, move the SPE-Select switches to the position indicating the carrier of the currently active SPE. For example, if the SPE in carrier A is active, move the switches to position A. When the SPE is locked, SPE interchanges are prevented, memory shadowing is turned off, handshake is down, and maintenance activities normally controlled by software on the active SPE cease. The following message is printed, (in this example, A is locked standby): One of the following prompts will appear, indicating which SPE is locked standby and whether the SPE is down. SPE_A_LOCKED> SPE_B_LOCKED> SPE_A_DOWN_LOCKED> SPE_B_DOWN_LOCKED> You can now enter the commands described in ‘‘ Using the SPE-Down Interface’’. If the prompt fails to appear, check your connections. Try connecting to the connector labeled STANDBY on the other PPN control carrier (A or B). If possible, try using a different cable and/or terminal. If the above actions do not produce a prompt, replace the SYSAM circuit pack on the standby SPE. If the prompt is still not present, follow normal escalation procedures. If an SPE was down and the SPE-Select switches are set to lock, the down-and-locked-standby mode replaces the SPE-down mode. Normally, when the standby SPE is up and cycling, the yellow LED on the Processor circuit pack flashes on and off. If the SPE is locked standby and a terminal is connected to the STANDBY connector, the Processor LED remains unlit.*********SPE A locked standby************
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-12 SPE-Down Command Interface 4 To return the standby SPE to service, see the following section on ‘‘Bringing the SPE Back into Service’’. NOTE: The physical connection of the terminal to the STANDBY connector while the SPE is locked standby with the SPE-Select switches prevents the Standby Maintenance Monitor (SMM) from running. Any reboot command to the standby while it is in the locked state will abort. Using the SPE-Down Interface When one of the above prompts appear, you may enter Spe-down interface commands. These are executed by the Low-level Maintenance Monitor (LMM), which is firmware resident on the processor board for controlling initialization and recovery actions, and processor and memory diagnostics. Communications with the terminal are handled by the SYSAM board. If a remote access port (SYSAM-RMT) call is received while in this mode, it will preempt access by the local MT, and this message will be displayed: When the call is completed or dropped, the prompt will return. Note that the SPE-down interface to an SPE that is locked standby is never available to the remote access port, because the standby SPE is isolated from the active SYSAM circuit pack. A limited set of commands is available to the SPE-down interface, as follows.Local Terminal session overridden by remote access KEYBOARD LOCKED, WAIT FOR SYSAM OR LOGIN PROMPT
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-13 SPE-Down Command Interface 4 The following qualifier can be used with the test commands: Enter only the characters which appear in bold type. For instance, to test all memory boards ten times, enter t ma 10 Entering t results in testing all boards once. You can abort the execution of a command by pressing ESC 3 times. Test Commands After a command is entered, various test result messages are printed on the terminal, indicating whether each test passes, fails or aborts. If any components fail, refer to the Maintenance Object documentation that applies. Additional information for interpreting these results can be found in the ‘‘ Troubleshooting a Table 4-2. SPE-Down Interface Commands Keyboard Entry Command ?Help rReboot sSecondary reboot ddisplay alarms t al or tTest all standby SPE circuit packs t syTest SYSAM circuit pack t prTest Processor circuit pack t m1Test Memory circuit pack 1 t m2Test Memory circuit pack 2 t m3Test Memory circuit pack 3 t m4Test Memory circuit pack 4 t maTest all Memory circuit packs t duTest DUPINT circuit pack t msTest MSSNET circuit pack t p1Test PKTINT circuit pack 1 t p2Test PKTINT circuit pack 2 t p3Test PKTINT circuit pack 3 t paTest all PKTINT circuit packs 1 to 99Number of repetitions (default is 1)
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-14 SPE-Down Command Interface 4 Duplicated SPE’’ and ‘‘Testing the Standby SPE’’ sections in Chapter 5, ‘‘Responding to Alarms and Errors’’. Note that the test memory command performs exhaustive tests and can be very time-consuming. When testing is complete, the system readies itself for another command and the prompt appears. If testing does not complete within 20 minutes, the following message is displayed: LMM did not finish test in time. This is a serious error indicating that the processor, bus, and/or LMM are not working properly. Normally you will see initial test result output within a few seconds. If not, you can abort the test request by pressing ESC 3 times, and the command prompt will be returned. If the SPE-down mode is entered or re-entered as a result of the test request, the screen displays: Can’t continue - test aborted. Again, this is a serious error, but at least the processor is able to handle SPE-down reporting. Likely fault locations are memory board number 1, processor board, or processor/memory bus. Display Alarms Command The display alarms command asks for the alarms that caused the SPE to go down. It is valid only in the SPE-down or down-and-locked-standby mode. If d is entered while the SPE is in one of the down modes, the following header is displayed: DISPLAY ALARMS: Physical NameLogical NameOn Board?Alternate NameAlarm TypeDate AlarmedDate Resolved
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-15 SPE-Down Command Interface 4 The header is followed by one and only one of the following lines (except that more than one Memory circuit pack failure may be displayed): Note that the display is designed to approximate an alarm display from software maintenance, but is not populated with certain information, represented by dashed out fields. Only the first failed component detected is displayed. In the absence of any other information about the cause of the failure, replace the indicated component using the procedures described in Replacing SPE Circuit Packs. After all tests pass, return the standby SPE to service, with procedures described in the following section on ‘‘ Bringing the SPE Back into Service’’. BOOT_ERROR indicates that the LMM was not able to either load, start, or keep the SPE running following a reboot request. SPE_SAN indicates that SYSAM detected enough sanity timeouts to exceed the threshold. Reboot Commands After all SPE-down interface tests have passed, an SPE can be brought back up by using the reboot commands. The reboot command, r starts a reboot using the boot image loaded on the disk device. The secondary reboot command, s, starts a reboot using the boot image loaded on the tape device. The latter is useful if the boot image on the disk is corrupted, the disk device is faulty, or a different software load is desired. A reboot can be interrupted by pressing ESC 3 times. As noted earlier, if an SPE is locked in the standby mode, the reboot commands cannot be entered and will abort.--- PROCR y ----- MAJOR ----- ----- ----- MEM_BD_0 y ----- MAJOR ----- ----- ----- MEM_BD_1 y ----- MAJOR ----- ----- ----- MEM_BD_2 y ----- MAJOR ----- ----- ----- MEM_BD_3 y ----- MAJOR ----- ----- ----- MSS_NET y ----- MAJOR ----- ----- ----- TAPE y ----- MAJOR ----- ----- ----- DISK y ----- MAJOR ----- ----- ----- NO_TAPE y ----- MAJOR ----- ----- ----- BOOT_ERROR ----- MAJOR ----- ----- ----- SPE_SAN ----- MAJOR ----- -----
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-16 SPE-Down Command Interface 4 Bringing the SPE Back into 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 — 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. Once all tests pass using the SPE-down interface, the SPE should be competent to return to service. There are however certain problems which will not show up in testing that may prevent this. Follow the appropriate procedure below to bring the SPE back up. Simplex SPE After the reboot command is entered, a series of diagnostics is run on the SPE. Results are displayed as they occur, as described in preceding sections. If all tests pass, the boot image is loaded and control is given to the operating system. If you cannot get the SPE to reboot after replacing the components that failed SPE-down interface tests, follow normal escalation procedures. Duplicated SPE The physical connection of the terminal to the STANDBY connector, while the SPE is locked standby with the SPE-Select switches, prevents the Standby Maintenance Monitor (SMM) from running. Thus, any reboot command to the standby while in this state will abort. To reboot an SPE that is locked standby and has a terminal connected to it, simply move the SPE-SELECT switches to the AUTO position one at a time. This will automatically cause the standby SPE to reboot and its progress is displayed on the terminal. Moving the switches back to the locked position will cause the reboot to abort. To reboot the standby SPE and have it remain locked standby following the reboot, use the following procedure: 1. Start the reboot by moving the SPE-Select switches one at a time to the AUTO position.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-17 SPE-Down Command Interface 4 2. As soon as initialization diagnostics begin to appear on the screen, disconnect the MT cable from the STANDBY connector on the control carrier. 3. Return the SPE-SELECT switches to their previous locked position. When the standby is back up and cycling, the yellow LED on the Processor circuit pack will begin flashing. It is then safe to unlock the SPE-Select switches if they were relocked. At this point, the system should re-establish handshake communication, turn on memory shadowing (assuming the standby is not busied out), and perform a refresh of the standby SPE’s memory. These steps can be monitored by using the status spe command at a terminal connected to the ACTIVE terminal connector. When these steps have been completed, the standby SPE should have a “functional” state of health and be fully in service. If all tests pass, but the SPE does not return to service, there may still be problems on the standby which escaped detection by SPE-down testing. In this case, use the following steps, which describe a means of sequentially replacing circuit packs that are the most likely source of the problem. 1. First determine if memory shadowing is disabling handshake. With the standby locked, busyout the standby SPE; this prevents shadowing from turning on. 2. Bring up the standby as described above (unlock, unplug the STANDBY terminal and relock). If the yellow LED on the Processor fails to flash, follow normal escalation procedures. After the yellow LED begins flashing, unlock and monitor the recovery progress by repeatedly entering status spe on a terminal connected to the active SPE. If handshake is not established after 2 minutes, memory shadowing is not the problem. Proceed to step 4. 3. Release the standby and follow the progress of the refresh with status spe. If the refresh succeeds, the system should be fully functional. If the onset of shadowing or refresh coincides with handshake failure, replace the following circuit pack one at a time in the order shown and repeat this procedure from step 1 each time. (Use lock-and-power-down and DUP-CHL instructions). a. Standby DUPINT b. Standby PKT-INT c. Standby MSSNET d. Active DUPINT If the problem persists, follow normal escalation procedures. 4. If handshake has not come up after 2 minutes, replace each of the following circuit packs one at a time, in the order shown, and repeat this procedure from step 1 each time: a. Standby PKT-INT b. Standby DUPINT
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Initialization and Recovery Page 4-18 SPE-Down Command Interface 4 c. Standby SYSAM d. Standby PROCESSOR e. Standby MSSNET f. Standby MEMORY number 1 g. Standby MEMORY number 2 If the problem persists, follow normal escalation procedures.