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

Glossary
G-Series Common Glossary
Glossary-116
WAN shared driver
WAN shared driver. A driver, provided as part of the wide area network (WAN) subsystem,
that provides a simplified interface to HP NonStop™ TCP/IP for use by I/O processes.
The shared driver interface is similar to that provided by DOIOPLEASE on earlier
systems.
WAN subsystem. See wide area network (WAN) subsystem.
WAN subsystem manager process. A process named $ZZWAN provided as part of the
wide area network (WAN) subsystem that starts and manages the WAN subsystem
objects, the WAN product process, and device objects. Subsystem Control Facility
(SCF) commands are directed to the WAN subsystem manager process for configuring
and managing the WAN subsystem and the ServerNet wide area network (SWAN)
concentrator.
WAN Wizard Pro. A graphical user interface (GUI) that guides you step-by-step through the
configuration of wide area network (WAN) and local area network (LAN) software and
hardware.
wide area network (WAN). A network that operates over a larger geographical area than a
local area network (LAN)
; typically, an area with a radius greater than one kilometer.
The elements of a WAN can be separated by distances great enough to require
telephone communications.
wide area network (WAN) subsystem. The Subsystem Control Facility (SCF) subsystem
for configuration and management of WAN objects in G-series release version updates
(RVUs).
wild-card character. A character that stands for any possible character or characters in a
search string or in a name applying to multiple objects. In Subsystem Control Facility
(SCF) object-name templates, two wild-card characters can appear: ? (question mark)
for a single character and * (asterisk) for zero or more consecutive characters. See
also object-name template.
Windows Internet Name Service (WINS). A name resolution service that resolves
Windows NT networking computer names to Internet protocol (IP) addresses in a
routed environment. A WINS server handles name registration, queries, and release
version updates (RVUs). See also IP address
.
WINS. See Windows Internet Name Service (WINS).
work files. Temporary files created during system generation that serve as storage areas.
Work files are useful for debugging purposes after system generation. You can choose
to make specified work files permanent.
working directory. In the Open System Services (OSS) environment, a directory,
associated with a process, that is used in pathname resolution for relative pathnames.
worldwide name (WWN). A unique, 64-bit number assigned to hardware ports.