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-90
serial communications controller (SCC)
derived power sources include standby power generator, uninterruptible power supply
(UPS), isolation transformer, and computer-room power center (CRPC).
serial communications controller (SCC). A type of communications controller. Each
quad-integrated communications controller (QUICC) has four SCCs to handle the two
Ethernet ports and the two wide area network (WAN) ports.
serial copper. A standard for physical connectivity in ServerNet I and ServerNet II networks
that is available both in HP NonStop™ S-series servers and in Windows NT clusters.
Serial copper uses serial encoding and supports 50 and 125 megabyte/second (MB/s)
speeds. The maximum link distance at 125 MB/s is 25 meters.
serial copper PIC. See serial copper plug-in card (PIC).
serial copper plug-in card (PIC). A plug-in card (PIC) for the modular ServerNet expansion
board (MSEB) and I/O multifunction (IOMF) 2 customer-replaceable unit (CRU) that
supports the serial copper interface. See also serial copper
and plug-in card (PIC).
serial maintenance bus (SMB). A bus that connects service processors (SPs) within an
enclosure to each other and to the customer-replaceable units (CRUs) in the group.
serial maintenance bus (SMB) domain. The set of enclosures, modules, field-replaceable
units (FRUs), and customer-replaceable units (CRUs) connected by a common serial
maintenance bus (SMB).
server. (1) An implementation of a system used as a stand-alone system or as a node in an
Expand network. (2) A combination of hardware and software designed to provide
services in response to requests received from clients across a network. For example,
HP NonStop™ servers provide transaction processing, database access, and other
services. (3) A process or program that provides services to a client or a requester.
Servers are designed to receive request messages from clients or requesters; perform
the desired operations, such as database inquiries or updates, security verifications,
numerical calculations, or data routing to other computer systems; and return reply
messages to the clients or requesters. A server process is a running instance of a
server program.
server application. An application that provides a service to a client application. An
application that provides local execution of remote procedure calls is an example of a
server application.
ServerNet. A communications protocol developed by HP that is used in HP NonStop™
S-series servers. See also ServerNet I
and ServerNet II.
ServerNet I. The first-generation ServerNet network. ServerNet I architecture is used in
current HP NonStop™ S-series servers and other products. It features 50
megabytes/second speed, 6-port ServerNet routers, 8b/9b encoding, and a 64-byte
maximum packet size. See also ServerNet II
.