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-102
strictly conforming POSIX.1 application
strictly conforming POSIX.1 application. An application that requires only the facilities
described in ISO/IEC IS 9945-1:1990 and the applicable computer language
standards. Such an application must accept any behavior or value described in
ISO/IEC IS 9945-1:1990 as unspecified or implementation-defined and, for symbolic
constants, accept any value permitted by ISO/IEC IS 9945-1:1990.
structured view of the user ID. A view of the HP NonStop™ Kernel user ID, normally used
in the Guardian environment, that consists of either the
group-number,
user-number pair of values or the group-name.user-name pair of values.
subnet. See subnetwork.
subnetwork. A physical network within an Internet protocol (IP) network. Each IP network
can be divided into a number of subnetworks. Within a given network, each
subnetwork is treated as a separate network. Outside the network, the subnetworks
appear as part of a single network. The terms
subnetwork and subnet are used
interchangeably.
subnetwork address. An extension of the Internet protocol (IP) addressing scheme that
allows a site to use a single IP address for multiple physical networks. A subnetwork
address is created by dividing the local part of an IP address into a subnetwork number
(identifying a particular subnetwork) and a host number (uniquely identifying the host
system within the subnetwork). The terms
subnetwork address and subnet address are
used interchangeably.
SUB option. In some Subsystem Control Facility (SCF) subsystems, the designation that
the object name given in a command stands not just for itself but for the names of all
objects at the next-lower level in the hierarchy. The given object name can stand both
for itself and for the subordinate objects, or it can stand only for the subordinate
objects, depending on the value of the SUB option.
subordinate objects. In Subsystem Control Facility (SCF), objects that are logically
subordinate to other objects. Some subsystems are structured hierarchically, with
objects of one type logically subordinate to (that is, controlled by) an object of another
type. For example, a number of subdevices can be configured on a single line. Some
SCF commands include a SUB option that refers to subordinate objects.
Subscriber Channel (SC). A type of head on a fiber-optic cable in which the pins connect
through a push-pull mating interface.
substate. Further information about the state of a device. The state and substate together
provide information about the current condition of a device or path to a device.
SUBSYS object type. The Subsystem Control Facility (SCF) object type for most
subsystems that use SCF as the user interface.
subsystem. (1) A secondary or subordinate system, usually capable of operating
independently of or asynchronously with a controlling system. (2) A program or set of
processes that manages a cohesive set of Subsystem Control Facility (SCF) objects.