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-95
service equipment
server. A service connection can be used to communicate with the server only when
the HP NonStop™ Kernel operating system is running. A service connection provides
a comprehensive service and maintenance picture of the server and is used to perform
most service management tasks. See also low-level link
.
service equipment. The necessary equipment, usually consisting of circuit breakers and
their accessories, that is located near the entrance point of supply conductors. This
equipment constitutes the main control and cutoff means of the supply.
service processor (SP). A physical component of the processor multifunction (PMF)
customer-replaceable unit (CRU) or I/O multifunction (IOMF) CRU that controls
environmental and maintenance functions (including system load functions) in the
enclosure. SPs operate in pairs to provide fault tolerance. The two SPs in group 01 are
designated the master service processors (MSPs). Other pairs of SPs within a system
are called expansion service processors (ESPs). See also expansion service
processor (ESP) and master service processor (MSP).
service provider. (1) A person trained and qualified to service field-replaceable units
(FRUs). (2) An organization, such as the Global Customer Support Center (GCSC),
that helps you resolve problems with your HP NonStop™ S-series server. OSM and
TSM allow you to use the help of a service provider by configuring client software to
support remote notification and remote access.
service side. The side of a system enclosure that contains, behind an optional door,
processor multifunction (PMF) customer-replaceable units (CRUs) or I/O multifunction
(IOMF) CRUs, ServerNet expansion boards (SEBs), modular SEBs (MSEBs), and
ServerNet adapters. The service side is opposite the appearance side
. Cables are
accessed from the service side. System enclosures are typically arranged so that the
service side is the least visible side.
session. In the Open System Services (OSS) environment, a set of process groups
associated for job control purposes. A session can have a controlling terminal.
session leader. In the Open System Services (OSS) environment, the process that created
a session.
session lifetime. In the Open System Services (OSS) environment, the period that begins
when a session is created and ends when the lifetime of the last remaining process
group of the session ends.
setup configuration. A simple stand-alone network used to configure the OSM or TSM
environment. The setup configuration consists of the server, the primary system
console, an Ethernet hub, and two local area network (LAN) cables. One cable
connects the primary system console to the hub, and another cable connects the hub
to a processor multifunction (PMF) customer-replaceable unit (CRU) in group 01 of the
server. When OSM or TSM configuration is complete, the setup configuration can
serve as the working network configuration. Variations of the setup configuration can
be constructed using additional cables and hubs to increase fault tolerance.