NonStop S-Series System Expansion and Reduction Guide
Table Of Contents
- NonStop S-Series System Expansion and Reduction Guide
- What’s New in This Guide
- About This Guide
- 1 The Resizing Process
- 2 Planning System Expansion
- 3 Planning System Reduction
- 4 Reducing a System Online
- 1.Prepare the Donor System for Reduction
- 2.Record Information About the Donor System
- 3.Prepare Both ServerNet Fabrics
- 4.Inventory Enclosures to Be Removed
- 5.Prepare and Stop Devices and Processes
- 6.Ensure Devices and Processes Are Stopped
- 7.Delete Devices and Processes If Necessary
- 8.Prepare Enclosures for Removal
- 9.Finish the Reduction
- 10.Remove Other Cables From Powered-Off Enclosures
- 11.Physically Remove Enclosures From the System
- Adding Enclosures to Another System
- 5 Reducing a System Offline
- 6 Expanding a System Online
- Preparation for Online Expansion
- 1.Prepare Target System for Expansion
- 2.Record Information About Target System
- 3.Prepare Target System for Addition of Block
- 4.Save Current Target System Configuration
- 5.Copy SP Firmware File From the Target System to the System Console
- 6.Finish Gathering Information
- 7.Connect a System Console to the Enclosure
- 8.Change Group Number of Enclosure to 01
- 9.Power On Enclosure
- 10.Verify Connection Between System Console and Enclosure
- 11.Configure System Console and Enclosure
- 12.Verify SP Firmware Is Compatible
- 13.Update SP Firmware in Enclosure If Necessary
- 14.Configure Topology of Enclosure If Necessary
- 15.Power Off Enclosure
- 16.Repeat Steps 6 Through 15 If Necessary
- 17.Assemble Enclosures Into a Block
- 18.Change Group Numbers of Block to Fit Target System
- 19.Disconnect System Console From Block
- 20.Power On Added Block
- 21.Cable Block to Target System
- 22.Verify Resized Target System
- 23a.Update Firmware and Code in Block (Using TSM)
- 23b.Update Firmware and Code in Block (Using OSM)
- 24.Reload Processors in Block If Necessary
- 25.Verify Operations in Added Block
- 26.Configure CRUs in Added Block
- 7 Troubleshooting
- A Common System Operations
- Determine the Processor Type
- Determine the ServerNet Fabric Status
- Determine the Product Versions of the OSM Client Software
- Determine the Product Version of the TSM Client Software
- Move the System Console
- Stop the OSM or TSM Low-Level Link
- Start a Startup TACL Session
- Start the OSM or TSM Low-Level Link
- Start the OSM Service Connection or TSM Service Application
- B ServerNet Cabling
- C Checklists and Worksheets
- D Stopping Devices and Processes
- Safety and Compliance
- Glossary
- Index
Stopping Devices and Processes
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
D-8
Stop the E4SA Adapter
This example screen shows the TACL commands you can use to trace processes
started from a TCP/IP session. The processes highlighted in bold type might be
affected by the removal of this E4SA.
The previous five example screens show one session on one LIF on one E4SA.
On this LIF, a number of processes are affected when you stop the E4SA. Each of the
following processes might need to be moved or stopped before you continue with the
system reduction procedure:
•
Processes that access the LIF through the following subsystems: Expand-Over-IP,
PAM, SNAX over Ethernet, and IPX/SPX
•
Direct openers of these same subsystems
•
Clients of those direct openers
Determining this and similar information on any system is highly system-specific. Your
procedures for determining critical processes in the enclosure you will remove might
vary. Consult your system analyst.
Stop the E4SA Adapter
After you have identified the processes that need to be moved or stopped, enter the
appropriate SCF commands to stop the E4SA adapter, its LIF, and the TCP/IP process.
Depending on the subsystem, use the STOP command first, followed by the ABORT
command if necessary.
In this example, the SCF STOP command performs an orderly shutdown of processes:
1-> STOP LIF $ZZLAN.LAN02*
2-> STOP ADAPTER $ZZLAN.E4SA02A, SUB ALL
3-> STOP PROCESS $ZTC20
If a process is still running when you try to stop it, SCF can return a message like:
SLSA E00012 Object $ZZLAN.LAN21 has registered client(s) and
cannot stop.
If all components have not been stopped and you have determined that they can be
forcibly stopped, use the ABORT command:
1-> ABORT LIF $ZZLAN.LAN02*
2-> ABORT ADAPTER $ZZLAN.E4SA02A, SUB ALL
3-> ABORT PROCESS $ZTC20
TACL> STATUS *, TERM $ZTN20.#PTCZA3G
Process Pri PFR %WT Userid Program file Hometerm
$Z02F 7,20 169 005 255,255 SYSTEM.SYS00.TACL $ZTN20.#PTCZA3G
Process Pri PFR %WT Userid Program file Hometerm
$Z02F 6,45 168 P 000 255,255 SYSTEM.SYS00.FUP $ZTN20.#PTCZA3Y