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-59
logical segment
MS8. An LMU must have memory units installed either in all of its slots or in none of its
slots. See also memory unit
.
logical segment. A single data area consisting of one or more consecutive 128-kilobyte
unitary segments that is dynamically allocated by a process. The two types of logical
segments are selectable segments and flat segments. See also selectable segment
and flat segment
.
logic board (LB). (1) See cluster switch logic board. (2) A printed wiring assembly (PWA)
on which computer circuits (chips and wiring) are mounted. One type of logic board is a
processor and memory board (PMB). Another type is a multifunction I/O board
(MFIOB).
logical network partitioning. An HP NonStop™ TCP/IPv6 feature that allows you to divide
the system into separately addressed IP subnetworks whereby applications have
access only to a defined set of network interfaces (IP addresses).
logical unit number (LUN). The logical unit in the Enterprise Storage System (ESS) that
maps the LDEV onto a port
. Specification of the port and LUN specifies an LDEV.
login. The activity by which a user establishes a locally authenticated identity on a server.
Each login has one login name.
login name. A user name associated with a session.
logon sequence. The process through which the HP NonStop™ S-series server to be
managed is determined, the security constraints to interact with that server are met,
and a connection with that server is established.
low-level link. A connection between the OSM or TSM client software running on a system
console and the master service processors (MSPs) on an HP NonStop™ S-series
server. When the HP NonStop Kernel operating system is not running, communication
must take place over a low-level link. You can also communicate with a NonStop
S-series server over a low-level link when the operating system is running. See also
service connection
.
low PIN. A process identification number (PIN) that is in the range 0 through 254. Contrast
with high PIN
.
LUN. See logical unit number (LUN).
MAC address. See media access control (MAC) address.
main bonding jumper. The connection between the grounded circuit conductor and the
equipment grounding conductor at the service.
main memory. Data storage, specifically the chips that store the programs and data
currently in use by a processor. On HP NonStop™ S-series servers, main memory is
stored on the processor and memory board (PMB) in the processor multifunction