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-25
DLC
DLC. See data link control (DLC).
DNS. See Domain Name System (DNS).
DNS server. A server that resolves hostnames to Internet protocol (IP) address mapping
queries. These queries originate from either client computers, which are known as
resolvers, or other Domain Name System (DNS)
servers, which accounts for the
distributed nature of DNS. See also Network Information Service (NIS)
.
domain. (1) In the Internet, a part of the naming hierarchy. Syntactically, a domain name
consists of a sequence of names (labels) separated by periods (dots).
(2) In a NonStop S-series server, a pair of service processors, the associated router
clouds, and the attached replaceable units.
(3) A set of objects over which control or ownership is maintained. Types of domains
include power domains and service processor (SP) domains.
Domain Name System (DNS). A system that defines a hierarchical, yet distributed,
database of information about hosts on a network. The network administrator
configures the DNS with a list of hostnames and Internet protocol (IP) addresses,
allowing users of workstations that are configured to query the DNS to specify remote
systems by hostnames rather than by IP addresses. DNS domains should not be
confused with Windows NT networking domains. See also DNS server
, Network
Information Service (NIS), and ping.
donor system. The computer system you make smaller by removing enclosures, either to
reduce the system or to add the removed enclosures to another target system
, using a
process known as system reduction.
double-high ServerNet adapter. A ServerNet adapter that occupies an entire ServerNet
adapter slot in an HP NonStop™ S-series server. Contrast with single-high ServerNet
adapter.
double-high stack. A stack that includes a base, a frame, and two system enclosures.
Contrast with single-high stack
.
double-wide plug-in card (PIC). A large-form-factor plug-in card (PIC) that occupies two
adjacent PIC slots within a customer-replaceable unit (CRU). See also single-wide
plug-in card (PIC).
download. The process of transferring software from one location to another, where the
transferring entity initiates the transfer.
download line task. Any task running under the Portable Silicon Operating System (pSOS)
system product, such as a data protocol.
downtime. Time during which a computer system is not capable of doing useful work
because of a planned or unplanned outage. From the end user’s perspective,
downtime is any time a needed application is not available.