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-98
skin effect
skin effect. The tendency of higher frequency signals to flow on the outside surface, or
skin, of a conductor instead of through the entire cross-section of the conductor. The
result is less total conductor area available for carrying current and an increase in the
resistance of the conductor at that high signal frequency.
slot. A physical, labeled space for a customer-replaceable unit (CRU) or field-replaceable
unit (FRU) that is part of a module. A module contains one or more slots.
slot location. A three-number identifier for a particular slot on a system that consists of the
group number, module number, and slot number; for example, 02,01,08 (group 02,
module 01, slot 08).
SLSA subsystem. See ServerNet LAN Systems Access (SLSA) subsystem.
small computer system interface (SCSI). An ANSI-standard protocol used by a controller
to access a device.
SMB. See serial maintenance bus (SMB).
SMB domain. See serial maintenance bus (SMB) domain.
SMF. See storage pool.
SMF PIC. See single-mode fiber-optic (SMF) plug-in card (PIC).
SMF ServerNet cable. See single-mode fiber-optic (SMF) ServerNet cable.
SMI. See ServerNet memory interface (SMI).
SMN. The mnemonic name for the external system area network manager process
(SANMAN).
SMP. See Security Manager Process (SMP).
SMT. See SWAN manager task (SMT).
snapshot. (1) A file that can be created by OSM and TSM client software to record
information about the status of an HP NonStop™ S-series server, including the
attributes values of all system resources, at the time it was created. The file can be
forwarded to your service provider to help with troubleshooting problems. (2) For
Distributed Systems Management/Software Configuration Manager (DSM/SCM), a list
of the target system tape and disk locations, file fingerprints for files managed by
DSM/SCM, and DSM/SCM target information. The snapshot is compiled on the target
system from the target database and sent to the host system to store in the host
database. An instruction to create a snapshot is part of every activation package sent
from the host and can also be requested independently through the Target Interface.
(3) In Visual Inspect, a disk file created by the Save Snapshot command or by DMON if
the SAVEABEND attribute for a process is ON and the process abends. A snapshot is
an image of the process, its data, and its status at the moment it was saved. Visual