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-4
application binary interface (ABI)
The appearance side is opposite the service side. System enclosures are typically
arranged so that the appearance side is the most visible side. See also service side
.
application binary interface (ABI). The conventions used to call functions and access
global or external data.
application development environment (ADE). A set of methods and tools that are used
throughout the lifecycle of an application project to design, code, and manage that
project.
Application Program Examiner (APE). A tool used to browse through TNS object files that
have been accelerated by the Accelerator. APE displays MIPS RISC code in addition
to TNS code.
application program interface (API). A set of services (such as programming language
functions or procedures) that are called by an application program to communicate with
other software components. For example, an application program in the form of a client
might use an API to communicate with a server program.
application-specific integrated circuit (ASIC). A custom-built integrated circuit (IC) used
to perform highly specialized functions.
Apply. The Distributed Systems Management/Software Configuration Manager (DSM/SCM)
action of executing the instructions contained in an activation package, such as placing
new software on the target system and taking a snapshot of the new target system.
appropriate privileges. In the Open System Services (OSS) environment, an
implementation-defined means of associating privileges with a process for function
calls or function call options that need special privileges.
Archive. A set of unstructured files used to collect the software received onto the host
system. Files received as input are placed in the Archive, and attributes of the files are
stored in the host database. The planner specifies the Archive location in the
Configuration Manager profile, using the Archive and Database Maintenance Interface.
Archive and Database Maintenance Interface. A block-mode interface run by a database
or system administrator at both the host system and target systems to perform
Distributed Systems Management/Software Configuration Manager (DSM/SCM)
maintenance functions.
ASCII. American Standard Code for Information Interchange. A single-byte code set that
uses only 7 of the 8 bits in a byte to represent each character. The ASCII code set
contains the uppercase and lowercase characters of the U.S. English alphabet, some
punctuation symbols, the digits 0 through 9, and some symbols and control characters.
Because of its limited characters, and because the 8th bit is sometimes used in ASCII
programs as a utility bit, the ASCII code set is not appropriate for use in international
software.
ASIC. See application-specific integrated circuit (ASIC).