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-61
memory-exact point
memory-exact point. A potential breakpoint location within an accelerated object file at
which the values in memory (but not necessarily the values in registers) are the same
as they would be if the object file were running in TNS interpreted mode or on a TNS
system. Most source statement boundaries are memory-exact points. Complex
statements might contain several such points: at each function call, privileged
instruction, and embedded assignment. Contrast with register-exact point
and
nonexact point
.
memory manager. An HP NonStop™ Kernel operating system process that implements the
paging scheme for virtual memory. This process services requests generated by
different interrupt handlers as well as by other system processes.
memory page. A unit of virtual storage. In TNS systems, a memory page contains 2048
bytes. In TNS/R systems, the page size is determined by the memory manager and
can vary, depending on the processor type.
memory slot. One of eight slots for memory units on the processor and memory board
(PMB). The slots are labeled MS1 through MS8.
memory unit. A unit consisting of a dual inline memory module (DIMM) or a single inline
memory module (SIMM) that is installed in groups of four on the processor and
memory board (PMB) of the processor multifunction (PMF) customer-replaceable unit
(CRU). Memory units constitute the processor memory. The memory units in certain
models of PMF CRU are not replaceable by customers or in the field.
message monitor process (MSGMON). A helper process for the ServerNet cluster monitor
process (SNETMON) that runs in each processor on every node of a ServerNet
cluster. MSGMON is started by the persistence manager process, $ZPM. It performs
duties for SNETMON in those instances where SNETMON needs an agent in each
system processor. In addition, MSGMON monitors the connections within the
processor and reports changes back to SNETMON when required.
MFIOB. See multifunction I/O board (MFIOB).
MIC. See Media Interface Connector (MIC).
microcode. Any machine code or data that can run in a microprocessor. HP produces two
types of microcode for HP NonStop™ S-series systems: volatile and nonvolatile.
Volatile microcode is loaded into the volatile random-access memory (RAM) of some
types of printed wiring assemblies (PWAs) and is not retained in a host PWA when
power to the PWA is interrupted. For nonvolatile microcode, see firmware
. See also
millicode
.
millicode. RISC instructions that implement various TNS low-level functions such as
exception handling, real-time translation routines, and library routines that implement
the TNS instruction set. Millicode is functionally equivalent to TNS microcode
.
mirrored disk or volume. A pair of identical disk drives that are used together as a single
logical volume. One drive is considered primary, and the other is called the mirror.