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
Planning System Reduction
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
3-4
Is the Enclosure Providing Critical Resources?
Is the Enclosure Providing Critical Resources?
Information about critical resources is system-specific. Therefore, consult your system
analyst and service provider to determine the actions most appropriate for your
system.
Determine the following information about each enclosure you will remove:
•
What devices, adapters, and processes it contains
•
What communication paths it maintains for other enclosures
You need to know this information so that you can reconfigure your system to maintain
any processes and communication paths that otherwise would be disrupted when
enclosures are removed.
For example:
•
Removing an enclosure that contains Ethernet 4 ServerNet Adapters (E4SAs),
Gigabit Ethernet ServerNet Adapters (GESAs), or Gigabit Ethernet 4-Port
ServerNet Adapters (G4SAs) will disrupt TCP/IP processes that are configured to
use the Ethernet adapters.
•
Removing an enclosure that has Kernel-Managed Swap Facility (KMSF) swap files
on its disks might cause applications or system processes to terminate.
Devices, Adapters, and Processes
Devices, adapters, and processes in the enclosure you plan to remove can be located
by using either the OSM Service Connection or TSM Service Application.
Before you begin the reduction procedure, record this information on the appropriate
worksheets in Appendix C
. Then, with your system analyst, determine critical
operations that should first be moved to other enclosures or terminated.
Indirect Communication Paths
Neither the OSM Service Connection or TSM Service Application displays indirect
paths of communication. However, these indirect paths can affect other enclosures
significantly.
For example: groups 08 and 41 communicate with each other through group 04. Group
41 might connect through group 04 to use a process that is running in group 08.
Therefore, if you remove group 08, group 41 is also affected.
Dependent processes and indirect communication paths can be of three types:
•
Active processes and communication paths using a device
•
Active processes and communication paths not currently using a device
For Information About See
KMSF swap files Kernel-Managed Swap Facility (KMSF) Manual