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-5
ASSIGN
ASSIGN. An HP Tandem Advanced Command Language (TACL) command you can use to
associate a file name with a logical file of a program or to assign a physical device to
logical entities that an application uses.
assign message. Within Subsystem Control Facility (SCF), a message created by SCF for
each ASSIGN command. A new process must request its assign message following
receipt of the startup message. All assign messages set by the SCF ASSIGN
command, plus the ones read from the HP Tandem Advanced Command Language
(TACL) command interpreter, are passed to the new process.
assumed object. The object type or object name specified by a Subsystem Control Facility
(SCF) ASSUME command. If an ASSUME command has been used to establish a
default object type and fully qualified default object name, and if that object type and
object name together refer to a valid object,
object-spec can be omitted entirely
from an SCF command, and the command is applied to the object known as the
assumed object.
asynchronous wide area network (AWAN) servers. A local area network (LAN)-based
communications device that provides (1) asynchronous connections to terminals,
printers, and terminal emulators for HP NonStop S-series and K-series servers; (2)
remote-access disk operating system (DOS), Windows, and Macintosh platforms; (3)
VT-to-6530 protocol conversion; and (4) dial-out connections for LAN-attached DOS,
Windows, and Macintosh platforms.
ATM3SA. See ATM 3 ServerNet adapter (ATM3SA).
ATM 3 ServerNet adapter (ATM3SA). A ServerNet adapter that provides access to
Asynchronous Transfer Mode (ATM) networks from an HP NonStop™ S-series server.
The 3860 ATM3SA supports the ATM User-Network Interface (UNI) specification over
a 155-megabit/second (Mbps) OC-3 Sonet (Synchronous Optical Network) connection.
atomic. Behaving as a single, indivisible operation. For example, an atomic write operation
on a file cannot write data that is interleaved with data from another, concurrent write
operation on that file.
attachment. A file that contains information that augments the information in an incident
report.
attribute. (1) For the Subsystem Control Facility (SCF), a characteristic of an entity. For
example, two attributes of a process might be its program file and its user ID. An
attribute is sometimes called a modifier. (2) In OSM and TSM client interfaces, a data
item associated with a system or cluster resource. All attributes can be viewed, and
some can be modified.
audit. A Distributed Systems Management/Software Configuration Manager (DSM/SCM)
activity initiated by the operator at a target system that updates the target database
with the fingerprints of all the files in a selected set of target subvolumes (TSVs).