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-93
ServerNet ID
ServerNet ID. A unique identifier for an addressable unit on a ServerNet communications
network. A unit can have multiple ServerNet node IDs. This ID is used for routing. Each
packet has a source ServerNet node ID and a destination ServerNet node ID. A pair of
processors operating in duplex mode share one ServerNet node ID.
ServerNet LAN Systems Access (SLSA) subsystem. A subsystem of the HP NonStop™
Kernel operating system for configuration and management of ServerNet local area
network (LAN) objects in G-series release version updates (RVUs).
ServerNet link. Two unidirectional point-to-point communication paths, one in each
direction, connecting a router to a ServerNet node or another router. Each ServerNet
link contains a transmit channel and a receive channel.
ServerNet memory interface (SMI). An application-specific integrated circuit (ASIC) that
provides the interface between the microprocessor and the two ServerNet fabrics and
main memory.
ServerNet node. A system in a ServerNet cluster. See also node.
ServerNet node number. A number that identifies a member system in a ServerNet cluster.
The ServerNet node number is a simplified expression of the 6-bit node-routing ID that
determines the node to which a ServerNet packet is routed. The ServerNet node
number is assigned based on the port to which the node is connected on the cluster
switch. The ServerNet node number, which can be viewed using the Subsystem
Control Facility (SCF), the OSM Service Connection, or the TSM Service Application,
is unique for each node in a ServerNet cluster.
ServerNet node routing ID. A bit field used to route ServerNet packets across the external
ServerNet X and Y fabrics. The ServerNet node routing ID occupies the upper six bits
of the 20-bit ServerNet ID, and it is unique for each member, or node, in a ServerNet
cluster. This term is the fully qualified form of
node routing ID.
SERVERNET object type. In the Kernel subsystem, the object type for either the $ZSNET
ServerNet subsystem manager process or the ServerNet X fabric or Y fabric.
ServerNet packet. The unit of transmission in a ServerNet communications network. A
ServerNet packet consists of a header, a variable-size data field, and a 32-bit cyclic
redundancy check (CRC) checksum covering the entire packet. The header contains
fields for control, virtual memory address, and destination and source fields to identify
the processor or I/O controller transmitting and receiving the packet. See also request
packet and response packet.
ServerNet port. A connector used for ServerNet links. Six ServerNet ports are located on a
ServerNet expansion board (SEB). Ten ServerNet ports are located on a modular
ServerNet expansion board (MSEB).
ServerNet router. An application-specific integrated circuit (ASIC) responsible for routing
ServerNet packets along ServerNet links in the ServerNet fabrics, using routing
information that is present within the packets. A ServerNet router acts as a fully duplex