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-75
ping
ping. A utility used to verify connections to one or more remote hosts. The ping utility uses 
the Internet control message protocol (ICMP)
 echo request and echo reply packets to 
determine whether a particular IP system on a network is functional. The ping utility is 
useful for diagnosing IP network or router failures.
pipe. In the Open System Services (OSS) environment, an unnamed FIFO, created 
programmatically by invoking the 
pipe() function or interactively with the shell pipe 
syntax character (
|). A shell pipe redirects the standard output of one process to 
become the standard input of another process. A programmatic pipe is an interprocess 
communication mechanism.
planned outage. Time during which a computer system is not capable of doing useful work 
because of a planned interruption. A planned outage can be time when the system or 
user application is shut down to allow for servicing, upgrades, backup, or general 
maintenance.
planner. The Distributed Systems Management/Software Configuration Manager 
(DSM/SCM) user who is responsible for planning and managing new software 
revisions. The planner uses the DSM/SCM Planner Interface to carry out these 
functions.
Planner Interface. A graphical user interface (GUI) to the Distributed Systems 
Management/Software Configuration Manager (DSM/SCM) that runs on the host 
system. It provides an interface to all the host DSM/SCM planner functions.
plug-in card (PIC).  A replaceable component that provides a unique function when 
installed in a customer-replaceable unit (CRU) or field-replaceable unit (FRU). PICs for 
modular ServerNet expansion boards (MSEBs) and I/O multifunction (IOMF) 2 CRUs 
provide a choice of connection media for attaching ServerNet cables.
PM. See product module (PM).
PMB. See processor and memory board (PMB).
PMCU. See power monitor and control unit (PMCU).
PMF CRU. See processor multifunction (PMF) CRU.
PMF 2 CRU. See processor multifunction (PMF) 2 CRU.
pNA+. The support for the Transmission Control Protocol/Internet Protocol (TCP/IP) layers 
and the Ethernet interface provided by Integrated Systems Inc. as part of the Portable 
Silicon Operating System (pSOS) system product. pNA+ is provided as part of the 
wide area network (WAN) architecture in each ServerNet wide area network (SWAN) 
concentrator communications line interface processor (CLIP).
Point-to-Point Protocol (PPP). A data communications protocol that provides a standard 
method of encapsulating Transmission Control Protocol/Internet Protocol (TCP/IP) 










