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-44
HP NonStop™ Cluster Switch (model 6770)
HP NonStop™ Cluster Switch (model 6770). An assembly that routes ServerNet
messages across an external fabric of a ServerNet cluster. The cluster switch consists
of a ServerNet II Switch, an uninterruptible power supply (UPS), and AC transfer
switch, and it can be packaged in a switch enclosure or in a 19-inch rack. The cluster
switch is used with star, split-star, and tri-star topologies. See also HP NonStop™
ServerNet Switch (model 6780).
HP NonStop™ Kernel Open System Services (OSS). The product name for the OSS
environment. See also Open System Services (OSS)
.
HP NonStop™ Kernel operating system. The operating system for HP NonStop systems.
HP NonStop™ Kernel user ID. A user ID within an HP NonStop system. The Guardian
environment normally uses the structured view of this user ID, which consists of either
the
group-number, user-number pair of values or the group-name.user-name
pair of values. For example, the structured view of the super ID is (255, 255). The
Open System Services (OSS) environment normally uses the scalar view of this user
ID, also known as the UID
, which is the value (group-number * 256)
+
user-number. For example, the scalar view of the super ID is (255 * 256) + 255
= 65535.
HP NonStop™ K-series servers. The set of servers in the HP NonStop servers having
product numbers beginning with the letter
K. These servers run the HP NonStop
Kernel operating system, but they do not implement the ServerNet architecture.
HP NonStop™ Open System Management (OSM) Interface. Replacement for TSM as
the system management tool of choice for NonStop S-series servers. OSM provides
the same functionality as TSM while overcoming limitations of TSM. OSM is required
for support of new functionality released in G06.21 and later.
HP NonStop™ S700 server. A special configuration of HP NonStop S-series server that is
limited to one processor enclosure and a maximum of two I/O enclosures. A matched
pair of any model of PMF CRU can be used in a NonStop S700 server.
HP NonStop™ S7000 server. The first server in a product line of servers (HP NonStop
S-series servers) that implement the ServerNet architecture and run the HP NonStop
Kernel operating system.
HP NonStop™ S7400 server. A model of HP NonStop S-series server that provides a
midrange upgrade option for migrating from an HP NonStop K-series server or a
NonStop S7000 server.
HP NonStop™ S7600 server. A model of HP NonStop S-series server that implements the
ServerNet architecture and runs the HP NonStop Kernel operating system. The
NonStop S7600 PMF CRU is based on the NonStop S74000 PMF CRU, and the
NonStop S7600 server supports all S-series hardware products that are compatible
with the NonStop S74000 server.