Managing Superdome Complexes: A Guide for HP-UX System Administrators HP 9000 Computers Edition 1 Manufacturing Part Number: B2355-90702 E1200 United States © Copyright 1983-2000 Hewlett-Packard Company. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Copyright 1979, 1980, 1983, 1985-93 Regents of the University of California. This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. Copyright 1988 Carnegie Mellon University Copyright 1990-1995 Cornell University Copyright 1986 Digital Equipment Corporation. Copyright 1997 Isogon Corporation Copyright 1985, 1986, 1988 Massachusetts Institute of Technology. Copyright 1991-1997 Mentat, Inc.
X Window System is a trademark of the Massachusetts Institute of Technology. Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service. Contact your HP sales representative for details.
Contents What's in This Document 1. Overview of the Superdome System Environment Overview of Superdome System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Superdome Partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Superdome Server Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Superdome System Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3. Managing the Overall Complex Introduction to Complex-wide Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Viewing / Setting the Complex Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . 61 Naming / Renaming a Superdome Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Determining Which Partitions are Defined in the Complex. . . . . . . . . . . . . . . . . . . .
Contents Advantages of Using The Partition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Start The Partition Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Partition Manager from the HP-UX Command Line . . . . . . . . . . . . . . . Starting Partition Manager from SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Partition Manager From a Web Browser . . . . . . . . . . . . . . . . . . . . . . . .
Contents parstatus Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . parstatus Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . parunlock Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 215 217 218 5.
Contents Configuring the Boot Timer for a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deconfiguring Cells, Processors, and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Automatic System Restart for a Partition . . . . . . . . . . . . . . . . . . . . . . Powering On and Powering Off Partition Hardware . . . . . . . . . . . . . . . . . . . . . . . . Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Points to Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building a Complex from Scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Performance and High Availability . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Expandability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partitions, Cells and I/O Chassis . . . . . . . . . . . . . . . . .
What's in This Document Managing Superdome Complexes: A Guide for HP-UX System Administrators describes tasks and concepts related to configuring and partitioning an HP Superdome computer.
1 Overview of the Superdome System Environment This chapter introduces the HP Superdome server environment by covering the following topics: • “Overview of Superdome System Features” on page 14 • “HP Superdome System Hardware Components” on page 18 • “HP Superdome Cabinet Overview” on page 22 • “Supported Superdome Configurations and Hardware Configuration Rules” on page 24 • “Listing Your Superdome Server’s Hardware and Partition Configuration” on page 25 • “HP-UX 11i Features for Superdome Servers” on pa
Overview of the Superdome System Environment Overview of Superdome System Features Overview of Superdome System Features Hewlett-Packard’s new Superdome system provides a highly configurable, high-performance HP-UX server environment. HP Superdome Server Cabinet © 2000 Hewlett-Packard AES—1.1 Figure 1-1 Within each HP Superdome server cabinet are multiple cells, each of which contains processors and memory. Each server cabinet also can have multiple I/O chassis that provide PCI slots for I/O cards.
Overview of the Superdome System Environment Overview of Superdome System Features HP Superdome Partitions A new feature of HP Superdome systems is the ability to run multiple instances of the HP-UX 11i operating system on a single server. This capability is accomplished by defining multiple partitions within a Superdome server. Because partitions are managed through software, you can reconfigure a server’s partition definitions without physically modifying the server’s hardware configuration.
Overview of the Superdome System Environment Overview of Superdome System Features HP Superdome Server Models Three models of Superdome systems are available, providing a powerful base set of functionality and increasing capacities in the larger models. See “HP Superdome System Hardware Components” on page 18 for details on the physical components that comprise a server.
Overview of the Superdome System Environment Overview of Superdome System Features needed. A Superdome 16-way server can be upgraded to a Superdome 32-way server, and likewise the Superdome 32-way server can be upgraded to Superdome 64-way server. Superdome System Hardware Configuration Configuring HP Superdome system hardware involves performing the following tasks. You can manage the tasks and issues listed below by consulting with your HP sales or HP support representative.
Overview of the Superdome System Environment HP Superdome System Hardware Components HP Superdome System Hardware Components This section provides a brief review of the components that comprise an HP Superdome server. As discussed in “HP Superdome Server Models” on page 16, three models of Superdome servers are available. Each model provides a different physical resource capacity (processors, memory, I/O), but provides the same powerful base functionality.
Overview of the Superdome System Environment HP Superdome System Hardware Components • I/O Chassis HP Superdome servers can contain up to four 12-slot I/O chassis per Superdome cabinet. For the first release, each I/O chassis provides 12 PCI card slots and resides within the same system cabinet as the cells. Each I/O chassis is connected by cables to one of the cells in the same cabinet as the I/O chassis. The HP Superdome cabinet contains two I/O bays, each of which supports up to two 12-slot I/O chassis.
Overview of the Superdome System Environment HP Superdome System Hardware Components HP Superdome Cell and I/O Connection I/O Chassis Cell RIO Cables © 2000 Hewlett-Packard AES—1.3 Figure 1-3 The backplane-connection cables (Flex cables) establish how backplane crossbar components communicate within a Superdome server complex. • Power and Service (“Attention”) Lights Each cell and each I/O chassis has two sets of lights (LEDs): power/status LEDs (green) and service LEDs (amber/yellow).
Overview of the Superdome System Environment HP Superdome System Hardware Components supplies (BPS 0–5). Note that five BPS components is the minimum requirement per cabinet, and six can be installed for redundancy. The following fans are installed in each Superdome cabinet: four blowers (0–3, at the cabinet’s top) and five I/O fans (0–4, inside the cabinet above the I/O chassis). See Figure 1-4 on page 22 for an overview of these items and their locations.
Overview of the Superdome System Environment HP Superdome Cabinet Overview HP Superdome Cabinet Overview This section provides a detailed look at the physical HP Superdome server cabinet, including the various indicator lights and the locations of the main components: cells, I/O bays, power, blowers, and so on. These components are described in “HP Superdome System Hardware Components” on page 18.
Overview of the Superdome System Environment HP Superdome Cabinet Overview Each HP Superdome cabinet has the following physical features. Note that all I/O peripherals reside in an external rack, not in the Superdome cabinets. • Front The front of each cabinet includes the following items: — Power—48V Power Switch. — Cabinet LCD—Indicates the cabinet ID. — Cabinet Service (“Attention”) LED. — Cell Power LEDs and Cell Service LEDs—These LEDs are visible when the front cabinet door is open.
Overview of the Superdome System Environment Supported Superdome Configurations and Hardware Configuration Rules Supported Superdome Configurations and Hardware Configuration Rules While HP Superdome servers are highly configurable systems, Hewlett-Packard recommends only specific hardware configurations and specific partition configurations. Consult with your HP sales or service representative for assistance.
Overview of the Superdome System Environment Listing Your Superdome Server’s Hardware and Partition Configuration Listing Your Superdome Server’s Hardware and Partition Configuration This section gives brief procedures and examples for determining your Superdome server’s current hardware and partition configurations. For more details on partition procedures, see Chapter 4, “Configuring and Managing Superdome Partitions,” on page 113.
Overview of the Superdome System Environment HP-UX 11i Features for Superdome Servers HP-UX 11i Features for Superdome Servers The HP-UX 11i release includes several new commands and utilities for managing and configuring HP Superdome partitions and system hardware. Also, the new rad command and the ioscan command provide Superdome-specific output as described in the following sections. These key HP-UX 11i Superdome features are discussed below.
Overview of the Superdome System Environment HP-UX 11i Features for Superdome Servers HP-UX Hardware Paths on HP Superdome Systems The HP-UX hardware path on HP Superdome systems is provided in the format described here. The ioscan HP-UX command reports the hardware path for components within the partition in which the command is issued. Note that the ioscan command reports information only for the currently active hardware components in the local partition.
Overview of the Superdome System Environment HP-UX 11i Features for Superdome Servers • f Is the target of the I/O device, or SCSI ID. • g Is a device-specific address such as a SCSI controller (initiator). Refer to the ioscan (1M) manpage for details on using ioscan to list hardware path information.
Overview of the Superdome System Environment HP-UX 11i Features for Superdome Servers HP Superdome PCI I/O Slots and Hardware Paths You should note that on HP Superdome servers, the PCI card slots (within an HP Superdome I/O chassis) do not directly correspond to their local bus adapter (LBA) number, such as is reported by the ioscan HP-UX command. The following table shows the correlation among HP Superdome PCI slots and the LBA number.
Overview of the Superdome System Environment HP-UX 11i Features for Superdome Servers rad Command Output on Superdome Servers This section covers the rad command’s output on Superdome servers. For complete details refer to the rad (1M) manpage. NOTE When adding or replacing I/O cards use the equivalent SAM procedures, when possible, rather than using rad. See also the sam (1M) and rad (1M) manpages.
Overview of the Superdome System Environment HP Superdome Console and Service Interfaces HP Superdome Console and Service Interfaces This section presents a brief overview of Superdome console and service features. Two methods of HP Superdome service and console use are: • The Service Management Station (SMS)—An external A-Class workstation connected to an HP Superdome complex.
Overview of the Superdome System Environment Related Information Related Information This section lists other sources for information on the topics covered in this chapter. Chapters in This Book The following chapters in this book include details about topics covered in this chapter.
2 Superdome Console and Service Interface This chapter describes the main service and console interfaces for configuring, monitoring, and for booting HP Superdome servers. The Guardian Service Processor (GSP) utility hardware provides a method of connecting to the Superdome complex to perform service or monitoring tasks.
Superdome Console and Service Interface Overview of Superdome Service Interface Tasks and Concepts Overview of Superdome Service Interface Tasks and Concepts Each Superdome complex has a single Guardian Service Processor (GSP), which provides service and console access to the complex. On the Superdome 64-way server, which includes two tightly interconnected cabinets that operate as a single server, the GSP is in the left cabinet (cabinet 0); the right cabinet has a subset of utility components.
Superdome Console and Service Interface Overview of Superdome Console and Service Interfaces Overview of Superdome Console and Service Interfaces The Guardian Service Processor (GSP) is the main point for using a Superdome server’s service and console interfaces. These interfaces provide the following features: • Partition Consoles Each partition on an HP Superdome server has its own console.
Superdome Console and Service Interface Overview of Superdome Console and Service Interfaces — The Show Chassis Logs Menu (SL) Three types of chassis code logs are maintained for each Superdome complex: (1) activity logs, (2) error logs, (3) live chassis code logs. The activity log and error log provide a snapshot of past chassis codes. The live chassis code log provides: — Real-time view of chassis codes.
Superdome Console and Service Interface GSP Login Accounts and Access Levels GSP Login Accounts and Access Levels To use the Superdome service and console interfaces you must have account access to log in to the server’s Guardian Service Processor (GSP). Each Superdome complex has its own set of GSP accounts, which are defined for the complex and may differ from accounts on other Superdome servers.
Superdome Console and Service Interface Accessing the Superdome Guardian Service Processor (GSP) Accessing the Superdome Guardian Service Processor (GSP) This section describes how to log in to the GSP utility hardware for an HP Superdome complex. You can connect to a Superdome server’s GSP by using the telnet HP-UX command on a remote system. Use telnet to open a connection with the GSP, then log in by entering the GSP account name and corresponding password.
Superdome Console and Service Interface Accessing the Superdome Guardian Service Processor (GSP) Procedure: Logging in to a GSP This procedure is for logging in to a the Guardian Service Processor (GSP) for a Superdome complex. Step 1. Use the HP-UX telnet command on a remote system to connect to the GSP utility hardware for the Superdome server.
Superdome Console and Service Interface Using Superdome GSP Menus Using Superdome GSP Menus The Guardian Service Processor (GSP) provides a set of menus that give you access to various service commands, consoles, log files, and other features. To use these menus, see “Navigating through GSP Menus” on page 42.
Superdome Console and Service Interface Using Superdome GSP Menus Figure 2-2 Overview of HP Superdome GSP Menus CO — Console Menu Partitions available: # --0) 1) Q) Name ---Partition 0 Partition One Quit Please select partition number: VFP — Virtual Front Panel Partition VFP’s available: # Name --- ---0) Partition 0 1) Partition One S) System (all chassis codes) Q) Quit GSP Main Menu GSP MAIN MENU: Consoles Virtual Front Panel Command Menu Console Logs Show chassis Logs Help Exit Connection GSP> GSP:
Superdome Console and Service Interface Using Superdome GSP Menus Navigating through GSP Menus This section describes how to navigate through Superdome GSP menus and sub-menus. As Figure 2-3 on page 43 shows, there are various commands and options for returning to the GSP Main Menu and escaping or ending a GSP login session. The following list has additional tips for navigating through GSP menus and using GSP features: • Control-b Exit current console, console log, chassis log, or Virtual Front Panel.
Superdome Console and Service Interface Using Superdome GSP Menus Figure 2-3 Navigating through HP Superdome GSP Menus telnet sdome-g (log in to GSP) GSP Main Menu CO GSP Console Menu Q or ^b Please select partition number: VFP GSP Virtual Front Panel Q or ^b GSP:VFP> CM ^] GSP Command Menu MA GSP:CM> CL GSP Console Log Viewer Menu Q or ^b GSP:VW> SL Q or ^b GSP:VW> Connection closed by foreign host. X Chapter 2 © 2000 Hewlett-Packard AES—2.3/gsp-6.
Superdome Console and Service Interface Accessing Partition Consoles Accessing Partition Consoles The GSP Console Menu provides access to all partition consoles within a Superdome complex. Each partition in a Superdome complex has its own console. Enter CO from the GSP main menu to access a partition’s console. Only one console exists per partition. However, multiple connections to the console are supported, allowing multiple people to simultaneously view the console output.
Superdome Console and Service Interface Accessing Partition Consoles • Whether HP-UX is installed, booted, and properly configured on the partition. If HP-UX is not installed on a partition, you should access the partition’s console (through the GSP) in order to install and configure HP-UX. See Chapter 5 for details on booting an HP-UX install source. You should directly log in to HP-UX running on a partition when you do not need to use GSP features and do not want to record a log of your activity.
Superdome Console and Service Interface Using GSP Commands Using GSP Commands This section summarizes the commonly used GSP commands, and provides details about the various categories of GSP commands. See Chapter 2 for details on using GSP commands to manage and configure Partitions. To return to the GSP main menu from the command menu, enter the MA command. All users connected to a Superdome server’s GSP command menu share access to the menu. Only one command can be issued at a time.
Superdome Console and Service Interface Using GSP Commands Commonly Used GSP Commands The following list summarizes GSP commands that are commonly used by system administrators. All of these commands are available to all GSP users. Table 2-1 Commonly Used GSP Commands Command Description BO Boot a protection domain. CP Display partition cell assignments. HE Help: list the available commands. LS Display LAN connected console status. MA Return to the GSP main menu.
Superdome Console and Service Interface Using GSP Commands GSP Command Menu: Service Commands The service commands available from the GSP Command menu provide boot, reset, power, TOC, status, and other commands for common service activities. Table 2-2 GSP Command Menu: Service Commands Service Command Description BO Boot a protection domain. DF Display FRU information of an entity. MA Return to the Main menu. MFG Enter the manufacturing mode. (Administrator only.) MR Modem reset.
Superdome Console and Service Interface Using GSP Commands GSP Command Menu: Status Commands The status commands available from the GSP Command menu provide command help and system status information, such as the server’s hardware configuration (the “USB topology”). All status commands are available to all GSP users. Table 2-3 GSP Command Menu: Status Commands Status Command Description CP Display partition cell assignments. HE Display the list of available commands.
Superdome Console and Service Interface Using GSP Commands GSP Command Menu: System and Access Configuration Commands The System and Access Configuration commands available from the GSP command menu provide ways to configure system security and console and diagnostic settings. These commands also enable you to specify a default partition for your current GSP session, and allow for modifying some Superdome complex configuration settings.
Superdome Console and Service Interface Using GSP Commands Table 2-4 GSP Command Menu: System and Access Configuration Commands Access Level(s) System / Access Config Command Description Administrator EL Enable LAN console access. Administrator, Operator, Single Partition User ER Configure remote/modem port access options. Administrator, Operator, Single Partition User ID Change certain Group A complex profile fields. Administrator, Operator IT Modify command interface inactivity time-out.
Superdome Console and Service Interface Using GSP Commands GSP: Manufacturing Commands You normally should not need to use any of the various manufacturing commands available from the GSP command menu. CAUTION The manufacturing commands are provided for use by Hewlett-Packard service personnel only. Table 2-5 GSP Command Menu: Manufacturing Commands Manufacturing Command Description CM Modify clock margin. MFG Enter the manufacturing mode. (Administrator only.) RD Read utility processor memory.
Superdome Console and Service Interface Using Virtual Front Panels Using Virtual Front Panels The GSP Virtual Front Panel menu provides ways to monitor the chassis codes for a particular partition or the entire system (all partitions). The Virtual Front Panel (VFP) provides a real-time display of activity on the selected partition(s). To interpret the VFP output see Chapter 5 for details.
Superdome Console and Service Interface Using the GSP to Access Boot Console Handler (BCH) Using the GSP to Access Boot Console Handler (BCH) This section gives some brief details on how to access the Boot Console Handler (BCH) menu for a specific Superdome partition. See Chapter 5 for details on booting and rebooting Superdome partitions. The BCH menu is provided for managing and configuring the HP-UX boot process for a Superdome partition.
Superdome Console and Service Interface Using the GSP to Access Boot Console Handler (BCH) Figure 2-4 Accessing a Partition’s BCH Menu telnet sdome-g (log in to GSP) GSP Main Menu CO (select Console menu) GSP Console Menu 1 (select Partition 1 console) ---- Main Menu --------------------------------------------------------------Command ------BOot [PRI|HAA|ALT|] PAth [PRI|HAA|ALT] [] SEArch [ALL|] ScRoll [ON|OFF] Description ----------^b Boot from specified path Display or modify a pat
Superdome Console and Service Interface Related Information Related Information This section lists other sources for information on the topics covered in this chapter. Chapters in This Book The following chapters in this book include details about topics covered in this chapter.
3 Managing the Overall Complex Collectively, all of the hardware components within a Superdome system are referred to as a complex. Each Superdome complex is comprised of the following building blocks: cabinets (including power, cooling, and utility hardware), cells, and I/O chassis. You can configure each Superdome complex into one or more partitions: independent virtual systems each capable of running an instance of HP-UX.
Managing the Overall Complex Introduction to Complex-wide Tasks Introduction to Complex-wide Tasks The tasks described in this chapter are arranged in three categories: • “Viewing / Setting the Complex Hardware Configuration” on page 61 • “Detecting / Controlling Power in the Complex” on page 83 • “Viewing the Current Status of the Complex” on page 101 The following table lists the tasks you will need to do in order to manage the components of a Superdome complex that are common to all partitions, the comp
Managing the Overall Complex Introduction to Complex-wide Tasks Table 3-1 HP Superdome Complex-Wide Tasks Task Description “Determining the Processor and Memory Configurations of Cells” on page 67 Tools • BCH • GSP • HP-UX Commands: parstatus • Partition Manager (parmgr) “Determining Firmware Versions in a Partition or Complex” on page 73 • BCH • GSP • HP-UX Commands: parstatus • Partition Manager (parmgr) “Determining the Serial Number of a Complex” on page 79 • HP-UX Commands: parstatus “Determini
Managing the Overall Complex Introduction to Complex-wide Tasks Table 3-1 HP Superdome Complex-Wide Tasks Task Description Tools “Determining if Memory DIMMS Have Failed” on page 105 • HP-UX Commands: parstatus “Determining if Blowers, Fans, or Power Supplies Have Failed” on page 108 • HP-UX Commands: parstatus 60 • Partition Manager (parmgr) • Partition Manager (parmgr) Chapter 3
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Viewing / Setting the Complex Hardware Configuration The procedures in this section allow you to gather information about how your Superdome complex is currently configured.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Naming / Renaming a Superdome Complex When you are working with more than one Superdome complex, it is useful to distinguish them by assigning them each a unique name. This is especially helpful if you are viewing information about multiple complexes on a single monitor. The complex name will be displayed as the root of the tree shown on the left-hand side of the Partition Manager display, and in many other useful places.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining Which Partitions are Defined in the Complex A list of the partitions currently defined in a Superdome complex can be displayed using the HP-UX command parstatus, or using the Partition Manager. You can perform this task using HP-UX commands or Partition Manager. • “HP-UX Commands” on page 63 • “Partition Manager” on page 63 HP-UX Commands Step 1.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining How Many Cabinets are Present in a Complex If you are working with a Superdome complex that is at a remote location, a complex that you might not be familiar with, you cannot simply walk over to it and observe how many cabinets it has. However, you can use the HP-UX command parstatus or the Partition Manager to determine this information. You can perform this task using HP-UX commands or Partition Manager.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2. Select “Show Complex Details” from the “Complex” menu The Complex Details Window will pop-up, displaying its “General” panel.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining the Processor and Memory Configurations of Cells You can determine the processor and memory configuration for cells in a Superdome complex by using the procedures provided in this section. You can perform this task using GSP menus, the BCH interface, HP-UX commands, or Partition Manager.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration GSP:CM> PS This command displays detailed power and hardware configuration status.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration The BCH information menu’s PR command reports details about all processors on all active cells in the partition. The ME command reports details about all active cells’ memory configurations. The ME command summarizes memory (DIMM) details for each ranks of memory. Each rank is a set of 4 DIMMs. These BCH commands do not report details for inactive cells.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Step 2. Use the parstatus command to view detailed cell hardware information, including processor and memory configurations. You can use any of the following parstatus commands to view details about the cell processor and memory configurations within the complex: • parstatus -V -c# List detailed processor and memory configuration information for the specified cell.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Partition Manager Step 1. Log into any running partition in the complex as the root user and start parmgr using the command: /opt/parmgr/bin/parmgr When parmgr starts, it displays the complex-level view which lists the partitions on the right-hand side of the display.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration There are two panels in the Cell Details window: General, and CPUs/Memory. Step 4. To see how many processors a cell board has, and their current status, or to see how much memory is installed on the selected cell board, click on the CPUs/Memory tab.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining Firmware Versions in a Partition or Complex Each Superdome complex has six types of firmware installed on the hardware components within the complex.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Step 1. Log in to the Superdome complex’s GSP and access the GSP command menu. From the GSP main menu, enter CM to access the command menu. Step 2. Use the GPS command menu’s PS command to list details, including all installed firmware versions, for any specified hardware component in the Superdome complex.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration The following example shows using the PS command to list the PM and CLU firmware versions for the UGUY utilities board in cabinet number 1. GSP:CM> PS This command displays detailed power and hardware configuration status.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration The following example shows the FV command displaying the PDC version for cells 0 and 2 (the only active cells in the partition). Information Menu: Enter command > FV FIRMWARE INFORMATION Cell ---00 02 Cab/Slot -------00/00 00/02 PDC Ver ------006.000 006.000 PDC Date Code ------------40.34 40.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Partition Manager Step 1. Log into any running partition in the complex as the root user and start parmgr using the command: /opt/parmgr/bin/parmgr When parmgr starts, it displays the complex-level view which lists the partitions on the right-hand side of the display.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration There are two panels in the Cell Details window: General, and CPUs/Memory. Step 4. To see the firmware revision for the selected cell board, click on the General tab.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining the Serial Number of a Complex If you need to determine the serial number of your Superdome complex, for example when making a support call, you can use the -X option to the HP-UX command parstatus, or you can use the Partition Manager to locate this information. You can perform this task using HP-UX commands or Partition Manager.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration For details see “How to Start The Partition Manager” on page 141. Step 2. Select “Show Complex Details” from the “Complex” menu The Complex Details Window will pop-up, displaying its “General” panel which includes Superdome serial number information. Step 3. [Optional] Print the results to a file or printer by clicking on the “Print ...” button. A “Print Dialog” window will be displayed.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration Determining the Product Number of a Complex If you need to determine the product number of your Superdome complex, for example when making a support call, you can use the -X option to the HP-UX command parstatus, or you can use the Partition Manager to locate this information. You can perform this task using HP-UX commands or Partition Manager.
Managing the Overall Complex Viewing / Setting the Complex Hardware Configuration For details see “How to Start The Partition Manager” on page 141. Step 2. Select “Show Complex Details” from the “Complex” menu The Complex Details Window will pop-up, displaying its “General” panel which includes Superdome product number information. Step 3. [Optional] Print the results to a file or printer by clicking on the “Print ...” button. A “Print Dialog” window will pop-up.
Managing the Overall Complex Detecting / Controlling Power in the Complex Detecting / Controlling Power in the Complex The procedures in this section allow you to gather information about (and control) the power status of the various components in your Superdome complex.
Managing the Overall Complex Detecting / Controlling Power in the Complex Determining Hardware Power Status You can use system software to check whether the following Superdome complex components are powered on or powered off: • Superdome Cabinets • Cell Boards • I/O Chassis • Individual PCI Slots The procedures described in this section allow you to check power status from remote locations, without physically inspecting the Superdome server hardware.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 2. Issue the PS command from the GSP command menu. The PS command allows you to list detailed information about components within the Superdome complex. GSP:CM> PS This command displays detailed power and hardware configuration status.
Managing the Overall Complex Detecting / Controlling Power in the Complex The following example shows cabinet power details for cabinet 0 of an SD64000 model Superdome server.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 2. Issue the HP-UX commands to check the power status for the Superdome complex components of interest to you. You can check power status details by using the HP-UX commands shown in the following list. For more details on these HP-UX commands, see the manpage for parstatus (1), frupower (1M), and rad (1M). This list covers cabinet, cell, I/O chassis, and PCI card slot power.
Managing the Overall Complex Detecting / Controlling Power in the Complex • Cell Power—Use the frupower command for cell power status. For status on all cells’ power, use the frupower -d -C command. For status on a specific cell’s power, use frupower -d -c# and specify the cell ID.
Managing the Overall Complex Detecting / Controlling Power in the Complex Partition Manager How to Determine if a Cell Board has Power: Step 1. Run the Partition Manager (parmgr). The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2. From the Complex menu, select Show Complex Details.
Managing the Overall Complex Detecting / Controlling Power in the Complex NOTE For safety reasons do not rely on this value unless you have just updated the display by rescanning the complex. Cell boards may have changed state if time has passed since the last complex scan. To force a rescan of the complex, hit the Rescan Complex button in the lower-right corner of the Complex Details window. How to Determine if an I/O Chassis has Power: Step 1. Run the Partition Manager (parmgr).
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 4. Locate the entry for the chassis that you are interested in, and look at the Usage column to find the current status of the chassis. I/O chassis with a usage value of powered-off were powered off at the time of the last scan of the complex. All other values indicate a chassis that was powered on at the time of the last complex scan.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 4. Click on the entry for the I/O chassis that contains the slot you are interested in, and then click the Show Details ... button, to display a new window containing the power status of the individual slots in the chassis.
Managing the Overall Complex Detecting / Controlling Power in the Complex Powering Cells and I/O Chassis On and Off You can power on or power off cells and I/O chassis within a Superdome complex by using system software. The procedures in this section allow you to control power for Superdome cells and I/O chassis from remote locations, without physically accessing the Superdome server hardware. NOTE On Superdome servers, powering on a cell also powers on any I/O chassis attached to the cell.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 1. Log in to the Superdome complex’s GSP and access the GSP command menu. From the GSP main menu, enter CM to access the command menu. Step 2. Issue the PE command and specify the type of hardware whose power you want to turn on or turn off. You can manage power to cells, I/O chassis, and cabinets (including all components in the cabinet). Step 3. Specify the hardware device to power on or power off.
Managing the Overall Complex Detecting / Controlling Power in the Complex HP-UX Commands Use this procedure to power on or power off cells (and their associated I/O chassis) using HP-UX commands. When using HP-UX commands to manage power, you are restricted to powering on or off inactive cells that are either assigned to the local partition or are not assigned to a partition. You cannot use HP-UX commands to manage the power of active cells or cells assigned to a remote partition.
Managing the Overall Complex Detecting / Controlling Power in the Complex Partition Manager Powering cells on and off can be done through the Partition Manager, though the Partition Manager limits what you can do based on whether the cell you are trying to control is in an active state, and whether it is in the local partition or a remote partition. If you attempt to power off a cell in a remote partition the Partition Manager will report an error message.
Managing the Overall Complex Detecting / Controlling Power in the Complex Turning Service Indicator Lights (LEDs) On and Off Within an HP Superdome complex, every cell and I/O chassis has a service indicator LED that is an amber (orange) “attention” light. You can illuminate these service LEDs to indicate which cells and I/O chassis require maintenance or inspection. Each Superdome cabinet also has a cabinet number LED on the cabinet’s front panel.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 2. Use the fruled command to turn on or off cabinet number LEDs or the service LEDs for cells and I/O chassis. Use the fruled -f option to turn off an LED and use fruled -o to turn on an LED. When issuing the fruled command, specify cells and I/O chassis using the notation described in the fruled (1) manpage. The following example turns off and turns on various cell, I/O chassis, and cabinet LEDs.
Managing the Overall Complex Detecting / Controlling Power in the Complex Step 3. If you want to check the status of cell and I/O chassis LEDs, use the GSP command menu’s PS command. Log in to the Superdome complex’s GSP and access the command menu. In the following example, the service LEDs for cells 0, 2, and 4 are turned on, as are the service LEDs for I/O chassis 0/0/1 and 0/0/3. GSP:CM> PS This command displays detailed power and hardware configuration status.
Managing the Overall Complex Detecting / Controlling Power in the Complex I/O chassis indicator LEDs: Select Light I/O Chassis LED from the I/O menu. In addition to lighting the LED on the I/O chassis, and the two-digit cabinet number for the cabinet containing the I/O chassis will flash. Step 2. A requestor will appear, regardless of the type of indicator you chose to light.
Managing the Overall Complex Viewing the Current Status of the Complex Viewing the Current Status of the Complex The procedures in this section allow you to gather information about the operating status of the various components in your Superdome complex.
Managing the Overall Complex Viewing the Current Status of the Complex Analyzing the Health of the Complex The easiest way to get an overall picture of how well your Superdome Complex is functioning is to use the Partition Manager’s “Analyze Complex Health” feature. This will run a series of problem detectors to check everything from cell boards, to I/O chassis, to the fans and blowers that cool the system and the power supplies that power Superdome components.
Managing the Overall Complex Viewing the Current Status of the Complex Determining if Processors Have Failed If you are specifically interested in the status of processors on a particular cell board, you can get this information using the HP-UX parstatus command, or the Partition Manager. You can perform this task using HP-UX commands or Partition Manager.
Managing the Overall Complex Viewing the Current Status of the Complex Any processors listed as failed have either failed self tests or have been deconfigured via the Boot Console Handler’s CPUCONFIG command. Partition Manager Step 1. Run the Partition Manager (parmgr). The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2.
Managing the Overall Complex Viewing the Current Status of the Complex Determining if Memory DIMMS Have Failed Use this procedure from any partition in the complex, to determine if memory modules have failed. You can perform this task using HP-UX commands or Partition Manager. • “HP-UX Commands” on page 105 • “Partition Manager” on page 106 HP-UX Commands The parstatus command (see parstatus (1)) can be used to determine the operating status of a cell’s processors. Step 1.
Managing the Overall Complex Viewing the Current Status of the Complex # parstatus -V -c2 [Cell] Hardware Location Global Cell Number Actual Usage Normal Usage Connected To : : : : : cab0,cell2 2 active base base cab 0,bay1,chassis3 [Memory Details] DIMM Size (MB) Status ==== ========= ========= 0 512 ok 1 512 ok 2 512 ok 3 512 failed 4 512 ok 5 512 ok 6 512 ok 7 512 failed 8 512 ok 9 512 ok 10 512 ok 11 512 failed 12 512 ok 13 512 ok 14 512 ok 15 512 failed 16 512 ok 17 512 ok 18 512 ok 19 512 ok 20 51
Managing the Overall Complex Viewing the Current Status of the Complex • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2. Click on the partition (or “Available Resources”) on the left-hand-side of the Partition Manager’s primary display. This will show the list of cells and I/O chassis for the partition on the right-hand-side of the display. Step 3.
Managing the Overall Complex Viewing the Current Status of the Complex Determining if Blowers, Fans, or Power Supplies Have Failed If you are working with a Superdome complex that is at a remote location, you cannot simply walk over to it and observe the operational status of the blowers, fans, and power supplies in the complex. However, you can use the HP-UX parstatus command (see parstatus (1) ) or the Partition Manager to determine this information.
Managing the Overall Complex Viewing the Current Status of the Complex # parstatus -V -b0 [Cabinet] Cabinet Blowers OK/ Cab Failed/ Num Cabinet Type N Status === ============ ========= 0 SD32000 4/ 0/ N+ I/O Fans OK/ Failed/ N Status ========= 5/ 0/ ? Bulk Power Supplies OK/ Failed/ N Status ========== 3/ 1/ N Backplane Power Boards OK/ Failed/ N Status ============ 3/ 0/ N+ GSP ====== active Cabinet Blowers =============== Fan 0 ok Fan 1 ok Fan 2 ok Fan 3 ok I/O Fans ============== Fan 0 ok Fan 1 ok
Managing the Overall Complex Viewing the Current Status of the Complex Step 2. Select “Show Complex Details” from the “Complex” menu The Complex Details Window will pop-up, displaying its “General” panel. Step 3. Click on the Power/Cooling tab to bring up the panel that contains information about the status of the blowers, fans and power supplies in your complex. Step 4. [Optional] Print the results to a file or printer by clicking on the “Print ...” button. A “Print Dialog” window will pop-up.
Managing the Overall Complex Related Information Related Information This section lists other sources for information on the topics covered in this chapter. Chapters in This Book The following chapters in this book include details about topics covered in this chapter. • Chapter 1, “Overview of the Superdome System Environment,” on page 13 • Chapter 2, “Superdome Console and Service Interface,” on page 33 HP-UX Man Pages The man pages listed here provide details on topics covered in this chapter.
Managing the Overall Complex Related Information 112 Chapter 3
4 Configuring and Managing Superdome Partitions This chapter describes the tools, procedures, and guidelines for configuring and managing Superdome partitions. On an HP Superdome system, each partition is a “logical server.” One or more cells (processors and memory), and I/O chassis (I/O cards and devices) are assigned to the partition for its exclusive use.
Configuring and Managing Superdome Partitions Introduction to Partition Tasks Introduction to Partition Tasks The following table lists the supported partition configuration tasks on HP Superdome servers. Detailed procedures for all tasks in Table 4-1 are provided in “Procedures for Managing Partitions” on page 152.
Configuring and Managing Superdome Partitions Introduction to Partition Tasks Table 4-1 Partition Configuration and Management Tasks Task Procedures Task Description Tools “Naming and Renaming Partitions” on page 174 Establish the partition’s name, which is used in various reports and console menus. BCH HP-UX: parmodify Partition Manager (parmgr) “Modifying Partitions’ Boot Paths” on page 177 Set the boot device paths, including the PRI, ALT, and HAA devices.
Configuring and Managing Superdome Partitions Introduction to Partition Tasks Table 4-1 Partition Configuration and Management Tasks Task Procedures Task Description Tools “Moving I/O to a Different Partition” on page 198 Using software only, you can accomplish this by assigning the corresponding cell (to which the I/O is connected) to a different partition. HP-UX “Moving an I/O Chassis to a Different Cell” on page 200 HP Service Personnel Only None. Must reconfigure the hardware.
Configuring and Managing Superdome Partitions Overview of Superdome Partition Concepts Overview of Superdome Partition Concepts The following concepts and issues related to configuring partitions are introduced in this section: • “Local and Remote Partitions” on page 117 • “Active and Inactive Partitions” on page 117 • “Types of Cells” on page 118 • “Genesis Partition” on page 119 • “Partition Numbers” on page 120 • “Complex Profiles” on page 120 More details on general Superdome complex tasks and features
Configuring and Managing Superdome Partitions Overview of Superdome Partition Concepts An inactive partition is in a ready-for-reconfig state, and thus all cells in the partition are in a boot-is-blocked state at a cell firmware level. When managing and configuring partitions, you can reconfigure all features of the local partition. You also can reconfigure all features of remote partitions that are inactive.
Configuring and Managing Superdome Partitions Overview of Superdome Partition Concepts Although you can have multiple cells with I/O chassis and core I/O cards within the same partition, only one core I/O card is active (the one belonging to the core cell). You also can define one or more core cell choices, which are cells you specify to be used as the core cell.
Configuring and Managing Superdome Partitions Overview of Superdome Partition Concepts that point install HP-UX. This installation requires either having access to an HP-UX install server, or a DVD-ROM drive (and associated PCI card) connected to the I/O chassis. After you boot HP-UX on the Genesis Partition, you can modify the partition to include additional cells. You also can create other, new partitions and can modify them from the Genesis Partition or any other partition running HP-UX.
Configuring and Managing Superdome Partitions Overview of Superdome Partition Concepts Each complex profile maintains the following information for the complex. • Stable Complex Configuration Data This portion of the complex profile stores complex-wide information, including the following details: — The name of the complex. — Which cells are assigned to which partitions, and which cells are unassigned (those on the free cell list, which are available to be assigned to any partition).
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Configuring Superdome Hardware and Partitions You can arrange Superdome system components, such as cells and I/O chassis, both physically (by configuring hardware) and logically (by defining partitions using software). The following sections discuss the hardware requirements and configuration guidelines for partitions, and the procedure for assigning cells to partitions.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions • Configure the partitions. Your partition configuration should exactly match the overall configuration you established with your HP representative. NOTE To ensure that your chosen Superdome configuration is recommended by HP and will match your requirements, check with your HP sales or support representative for assistance.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Partition Hardware Requirements The physical hardware prerequisites, shown below, determine which cells and I/O chassis are eligible to be configured in a partition. Every partition you configure must meet the following basic hardware requirements: • Each partition must have at least two cells. • The same firmware revision must be present on all cells.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Partition Configuration Guidelines HP offers the following general partition configuration guidelines in addition to the hardware prerequisites listed in the previous section. These guidelines are incorporated in the procedure that follows (“Procedure for Assigning Cells to Partitions” on page 126). Use these guidelines to help determine which cells to assign to the partitions you create.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Procedure for Assigning Cells to Partitions Use this procedure to help decide which cells to assign to partitions in your Superdome complex. NOTE Consult with your HP sales or support representative, and refer to Appendix A, “Planning Superdome Configurations,” on page 283 for important planning information before implementing partition changes on your Superdome complex.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions For partitions for which HP recommends multiple configurations, select the first available set of cells. For example, for a two-cell partition select configuration 2A, if possible, before selecting 2B or 2C. Step 4. Confirm that the cells you have selected are eligible to be assigned to the partition.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Examples The following example cell assignments show how the procedure discussed above selects cells for two sample complex configurations. Refer to the procedure, above, and the recommended partition charts that follow. For reference in the following examples, Figure 4-1 and Figure 4-2 on page 131 list a unique number for each partition configuration set.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions The following example illustrations show how the two example complex partition configurations would be selected, using Figure 4-1 and Figure 4-2 to determine which recommended partitions to use. Example 1 Superdome 32-way complex partition configuration. One six-cell partition and one two-cell partition.
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Superdome 16-way and Superdome 32-way Recommended Partition Configurations Cell Slots Config Set Superdome 16-way 0 1 2 3 2B Two-Cell Partitions 1 2A 2B 2A Three-Cell Partition 2 3A 3A 3A Four-Cell Partition 3 4A 4A 4A 4A Superdome 32-way Cell Slots 0 1 2 3 4 5 6 7 2C 2B 2D 2B 2D 3B 3B 3B 4B 4B 4B Two-Cell Partitions 4 2A 2C 2A Three-Cell Partitions 5 3A 3A 3A Four
Configuring and Managing Superdome Partitions Configuring Superdome Hardware and Partitions Two-Cell Partitions 11 Superdome 64-way Cabinet 0 Superdome 64-way Cabinet 1 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 2A 2E 2A 2E 2C 2G 2C 2G 2B 2F 2B 2F 2D 2H 2D 2H 2I 2I 12 13 Three-Cell Partitions 14 2J 2J 3A 3A 3A 3C 3C 3C 3B 3B 3B 3D 15 Four-Cell Partitions 16 4A 4A 4A 4A 4C 4C 4E 17 4C 4C 4B 4B 4B 4B 4D 18 5A 5A 5A 5A Six-Cell Partitions 19 6
Configuring and Managing Superdome Partitions Overview of Partition Management Tools Overview of Partition Management Tools You can use several different software tools to create, modify, and monitor HP Superdome partitions and hardware. These tools have capabilities that overlap in some cases, but each also has unique features and access requirements.
Configuring and Managing Superdome Partitions Overview of Partition Management Tools Table 4-2 HP Superdome Partition Management Tools Partition Tool Features and Restrictions Boot Console Handler (BCH) interface Description—The BCH interface is the method for interacting with a partition before it has booted HP-UX. Each partition’s BCH interface provides menus for configuring partition settings and booting HP-UX.
Configuring and Managing Superdome Partitions Overview of Partition Management Tools Table 4-2 HP Superdome Partition Management Tools Partition Tool Features and Restrictions Partition Manager (parmgr) Description—Partition Manager provides a graphical interface for configuring, modifying, and managing partitions and hardware within a Superdome complex. Availability—You can use Partition Manager when HP-UX is running in multi-user mode on the partition.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—An Introduction HP-UX Superdome Configuration Commands—An Introduction HP-UX Release 11i provides you with several new HP-UX commands for configuring and managing HP Superdome partitions and hardware, including: parcreate, parmodify, parremove, parstatus, parunlock, fruled, and frupower.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—An Introduction Table 4-3 HP-UX Commands for Configuring Superdome Partitions Command Description parstatus Display partition information and hardware details for a Superdome complex. See “parstatus Command” on page 215. parunlock Unlock complex profile data (use this command with caution); root permission is required. See “parunlock Command” on page 217.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—An Introduction Specifying Cells and I/O Chassis When you use the HP-UX Superdome configuration commands to manage, configure, and inquire about cells and I/O chassis, you must use the cell and I/O chassis notation described in this section.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—An Introduction Both of these cell ID formats specify each cell’s precise physical location in a Superdome complex. For example parstatus -c9 and parstatus -c1/1 refer to the same cell. # parstatus -c9 [Cell] CPU OK/ Hardware Actual Deconf/ Location Usage Max ========== ============ ======= cab1,cell1 active base 4/0/4 Memory (GB) OK/ Deconf Connected To ========= =================== 8.2/ 0.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—An Introduction The following example shows the parstatus command listing details about two different I/O chassis (cabinet 0/bay 0/chassis 1, and cabinet 0/bay 1/chassis 3).
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour The Partition Manager—A Guided Tour The Partition Manager provides a graphical user interface for configuring partitions (and other resources) in your Superdome complex. Patterned after a commonly used PC-based file exploration utility, the Partition Manager (also known as parmgr) is easy to learn and use.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour How to Start The Partition Manager Though it can be used to configure all of the partitions in a Superdome complex (except the Genesis Partition), the Partition Manager must run in (or via) an existing partition in the complex that you are configuring.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Starting Partition Manager from SAM From SAM: If you are running SAM, the Partition Manager is one of the selections available from the primary level of SAM’s interface Starting Partition Manager From a Web Browser From an HP-UX environment, the preferred method of running Partition Manager is from the HP-UX command line as described in the previous section.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour first activated, point your browser to the following URL to view instructions on installing and configuring the Java Plug-in and the Java Runtime Environment: http://hostname:1188/jpi/pc-compatible-only.html where hostname is the network hostname of the partition that will run Partition Manager. By default, only systems from the same network domain may access the web server running on a partition.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Before Partition Manager is launched, a login dialog will appear, prompting for a user name and password. Only the superuser is allowed to run Partition Manager. Once the user is authorized, Partition Manager will be launched in a window outside the browser. Additional dialogs for the tasks performed by Partition Manager will be displayed in new windows (just as though you were running the program locally).
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour /usr/obam/server/bin/apachectl start If you modify the configuration file after the web server has already been started, you must restart it by executing the following HP-UX command before the new configuration will be recognized: /usr/obam/server/bin/apachectl restart TIP If you want to start the web server automatically every time the partition is booted, the WEBADMIN variable should be set to 1 in the system configuration
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour space, delete (or move) it and restart the Apache web server using the command: /usr/obam/server/bin/apachectl restart Problem: On the client side, the Java console is enabled, but is not being displayed when Partition Manager is started. What to do: Try shutting down the browser and restarting it.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Figure 4-3 Partition Manager Object Hierarchy COMPLEX Partition 1 Partition 2 ... Partition n I/O Chassis I/O Chassis Cell Cell Processors and Memory Available Resources Cell Cell Processors and Memory PCI I/O Cards I/O Chassis I/O Chassis PCI I/O Cards Partition Manager Views The Partition Manager allows you to view a Superdome complex at various levels of detail.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Tool Bar Underneath the menu bar is a tool bar that allows you to change view types and levels, and bring up the help system. Context Menu The context menu provides a shortcut to all of the items on the menu bar that apply to the current context. To bring up the context menu, press the right mouse button while the mouse pointer is in the Object Summary pane (right-hand-side of the display).
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Viewing Partition Information If you want information about the resources of a specific partition, first select the partition by clicking on its name in the object list on the left-hand-side of the display. The right-hand-side of the display will update to show a summary of the resources for the selected partition.
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Details ...” button to get information about that chassis. CPUs / Memory The CPUs / Memory panel provides a list of processors, and memory modules along with their type and status. Viewing I/O Chassis Information At least one of the cell boards in every partition must have an I/O chassis connected to it (more than one can).
Configuring and Managing Superdome Partitions The Partition Manager—A Guided Tour Notes The Notes panel contains a list of errors, warnings, and notes about the information available on the I/O Cards and Storage tabs. For example, if I/O information is not available for a particular cell, a message will be displayed in the notes panel. The entries in the I/O Details window can be filtered to show a sub-set of all available information. This allows you to focus on specific cards or entries.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Procedures for Managing Partitions You can use the detailed procedures given in this section to configure and manage your Superdome server’s partitions. You can perform these tasks using several different partition management tools, including the Guardian Service Processor (GSP) menus, the Boot Console Handler (BCH) interface, HP-UX commands, and the Partition Manager (parmgr) utility.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Creating a Genesis Partition When you create a Genesis Partition, you establish a one-cell partition on the HP Superdome complex. The Genesis Partition replaces all other partitions, and once created it is the only partition on the system. Additional details are given in “Genesis Partition” on page 119. You can perform this task using the GSP menus.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 3. Ensure that all partitions within the complex are in a ready-for-reconfig state. If a partition is running HP-UX, you can shut down the partition to a ready-for-reconfig state by using the shutdown -R- H command. Or you can put the partition into a ready-for-reconfig state using the BCH interface’s RECONFIGRESET command or using the GSP command menu’s RR command. Step 4.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 7. Confirm that the Genesis Partition was successfully created. If the Genesis Partition is successfully created, the CC command reports that the “complex profile will be modified”. When the Genesis Partition is created, it is in a boot-is-blocked state, so must be booted manually. Step 8. Issue the BO command to boot the Genesis Partition. This boots the partition to the Boot Console Handler (BCH) interface.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Restoring a Complex Profile You can restore a previous complex profile configuration, which effectively allows you to undo your last partition configuration change. Restoring the previous complex profile allows you to revert to the previous complex configuration—including all partition configurations—that existed before you made your last change.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 4. Issue the CC command, select Last Complex Profile, and confirm that you want to modify the complex profile configuration. GSP:CM> CC This command allows you to change the complex profile. WARNING: You must shut down all Protection Domains before executing this command.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions existing partition configuration—you can repeat this procedure to restore the configuration you had before beginning the procedure. One level of undo is provided by the GSP command menu’s CC command. This allows you to undo your last partition change, and undo your undo. Step 6. Issue the BO command to boot any partitions you want to make active.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Determining the Local (Current) Partition Number On a single HP Superdome complex you can potentially access many partitions. Use the procedures here to determine the local partition you currently are using. You can perform this task using the BCH interface or HP-UX commands. • “BCH” on page 159 • “HP-UX Commands” on page 160 BCH Use this procedure to determine the local partition number from the BCH interface. Step 1.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions HP-UX Commands The following procedure uses the parstatus HP-UX commands to determine the partition number of the local (current) partition. Step 1. Log in to HP-UX running on the partition. Step 2. Issue the parstatus -w command to list the partition number for the local partition. # parstatus -w The local partition number is 0.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Creating a New Partition Use the procedures in this section when creating new partitions using the available cells within your Superdome complex. At least one cell in each partition must be connected to an I/O chassis that has the appropriate PCI cards and devices installed. When creating a partition, you must adhere to the requirements and guidelines described in “Partition Configuration Guidelines” on page 125.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 1. Plan your partition configuration by selecting which cells will comprise the new partition. Use the parstatus -AC command to list all unassigned (available) cells in your Superdome complex.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions When you create a multiple-cell partition, you should specify the -c option multiple times (once for each cell) issuing a single command line. # parcreate -c4:base:y:ri -c6:base:y:ri Partition Created. The partition number is : 1 # If the partition is successfully created, the parcreate command reports “Partition Created” and reports the partition number (“partition number is...”).
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 3. Modify the partition configuration in order to set the partition name, core cell, core alternate cells, and boot paths. Use the parmodify command to modify the partition’s configuration. # parmodify -p1 -P "hostname05" Command succeeded. # parmodify -p1 -r0/4 -r0/6 Command succeeded. # parmodify -p1 -b 4/0/1/0/0.9 Command succeeded. # If each modification takes place, parmodify reports “Command succeeded”.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 4. Confirm the partition’s configuration settings. Use the parstatus -Vp# command to list details about your newly created and configured partition. If any configuration details should be modified, use the parmodify command before booting the partition. # parstatus -Vp1 [Partition] Partition Number : 1 Partition Name : hostname05 Status : inactive IP address : Prmary Boot Path : 4/0/1/0/0.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Partition Manager Step 1. Determine which cell boards and I/O Chassis are to be a part of the partition you are creating. NOTE At least one cell in the partition must have an I/O chassis connected to it that has a core I/O board in I/O chassis slot 0. Without this, the Partition Manager will not let you create the partition. Step 2. Free up needed resources from other partitions (if necessary).
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 4. Select Create Partition... from the Partition menu. Step 5. The Create Partition task wizard will, in seven stages, guide you through the process of creating the new partition: 1. Naming (identifying) the partition. 2. Selecting the cells for the partition. 3. Setting the attributes for the cells you select in Stage 2. 4.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Stage 3: Set Cell Attributes Specify each cell’s “Failure Usage”. Cells can be included in a partition for several reasons, most notably: • Performance • Redundancy (High Availability) Cells can operate in two modes: normal mode and failure mode. In normal mode all of the processors and memory in a cell are operating normally, and participating in the partition’s operations.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Stage 5: Initial Boot Options Specify whether or not you want to have the new partition automatically booted immediately after it is created. Stage 6: Verify the Partition Settings At this point, the Partition Manager will show you a summary of the resources and settings that will define your new partition.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Deleting (Removing) a Partition You can delete (remove) any partition within an HP Superdome complex. The supported partition deletion methods provide restrictions, for security reasons: you can delete only the local partition and inactive remote partitions. Use extreme caution before deleting a partition.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 2. If you plan to remove a remote partition that currently is active, then put the partition into a ready-for-reconfig state. If a partition is running HP-UX, you can shut down the partition to a ready-for-reconfig state by using the shutdown -R -H command. You also can put the partition into a ready-for-reconfig state using the BCH interface’s RECONFIGRESET command or using the GSP command menu’s RR command.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions 2. Issue the parremove -F -p# command, which initiates the complex profile revisions that will take place when the partition is removed. When using parremove to remove the local partition, you must specify both the -p# option (to specify the local partition number) and the -F option (to force-remove the local partition). # parremove -F -p0 Use "shutdown -R" to shutdown the partition.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions NOTE If you will be running the Partition Manager in the partition that you are removing, you cannot shut down HP-UX or you will not be able to run the Partition Manager. Therefore, proceed directly to the next step. Step 2. Run the Partition Manager (parmgr). The Partition Manager can be run from an HP-UX command line, from a Web browser, or from the HP-UX System Administration Manager (SAM).
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Naming and Renaming Partitions You can name and rename partitions using the methods described here. Only the local partition, or inactive remote partitions, can be renamed. Partition names are used, in addition to partition numbers, in various reports and menus that the Guardian Service Processor (GSP) and the HP-UX partition tools provide.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Enter PD to check the current name, or enter PD New Name to set the partition’s name to the new name. No quotation marks are needed when specifying the new name.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Partition Manager Step 1. Run the Partition Manager (parmgr). The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2. On the left-hand side of the Partition Manager’s primary display window, highlight the entry for the partition that you want to remove. Step 3.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Modifying Partitions’ Boot Paths Each HP Superdome partition has its own boot path settings that specify the primary (PRI), alternate (ALT), and high-availability alternate (HAA) boot devices. See Chapter 5 for details on boot paths and procedures for booting and rebooting partitions. You can modify boot path settings for the local partition and remote partitions within the same Superdome complex.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Adding Cells to a Partition Adding cells to a partition involves selecting available cells (those not currently assigned to a partition) and assigning them to an existing partition. Both the selected cells and any I/O chassis connected to the cells are assigned to the designated partition.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions cell to an inactive remote partition, and you did not specify -B, then use the GSP command menu’s BO command to boot the partition. Partition Manager Step 1. Through careful planning, determine which cell(s) you want to add to the partition. Step 2. Run the Partition Manager (parmgr).
Configuring and Managing Superdome Partitions Procedures for Managing Partitions • Do you want to change the failure usage for any of the cells in the partition? • Do you want to change which cells will be used by the partition the next time it is booted? All of these things can be set from the Modify Partition window before you proceed. For help in changing any of these items, see “Setting and Checking a Partition’s Core Cell Choices” on page 185. Step 7.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Removing Cells from a Partition Removing a cell involves 1. using a partition configuration tool to designate that the cell be removed from a partition 2. rebooting the partition for reconfiguration (performing a reboot-for-reconfig). Once a cell is removed from a partition, the cell is unassigned and available for general use, along with any I/O resources connected to the cell.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Determine the partition number of the partition to which the cell is assigned. Step 2. List the current status for the partition. Use the parstatus -p# command to list the partition’s status (active or inactive); specify the partition number for the cell’s partition. The partition to which the cell is assigned must be inactive, or the cell must be assigned to the local cell. Step 3.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Partition Manager Step 1. Determine which cell(s) you want to remove from the partition. Step 2. Run the Partition Manager (parmgr). The Partition Manager can be run from: • an HP-UX command line • a Web browser • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 3.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions • Do you want to change which cells will be used by the partition the next time it is booted? All of these things can be set from the Modify Partition window before you proceed. For help in changing any of these items, see “Setting and Checking a Partition’s Core Cell Choices” on page 185. Step 7.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Setting and Checking a Partition’s Core Cell Choices You can establish each partition’s core cell choices. The core cell and core alternate cell settings establish which cells in the partition are preferred to be used as the core cell. For details about core cells, see “Types of Cells” on page 118. You can perform this task using the BCH interface, HP-UX commands, or Partition Manager.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 5. If you have changed the setting for the core cell, and you want the cell you have specified to immediately become active as the core cell, reboot the partition: issue the BCH menu’s REBOOT command. This step is optional. If you do not perform this step, the active core cell will change (if you’ve modified the setting) the next time the partition is rebooted.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 2. Modify the partition’s core cell settings. You can modify the local partition or any remote partition in the Superdome complex. Use the parmodify command: parmodify -p# -r# -r#... Specify the partition number (-p#) and the cell ID (-r#) for all cells you wish to designate as core cell preferences. # parmodify -p0 -r2 -r0 Command succeeded.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions • the System Administration Manager utility (SAM) For details see “How to Start The Partition Manager” on page 141. Step 2. On the left-hand side of the Partition Manager’s primary display window, highlight the entry for the partition you want to modify. The right-hand side of the display will change to show the resources currently assigned to the partition. Step 3. From the Partition menu, select Modify Partition. Step 4.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Setting and Checking Cell Attributes Each cell assigned to a partition has several attributes that determine when the cell is used. You can list and set each cell’s use-on-next-boot and failure-usage attribute settings. These settings determine when the cell becomes active by joining the partition during the boot process.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions You can list and set a cell’s use-on-next-boot setting by using the BCH interface for the cell’s partition. BCH Use the following procedure to modify the use-on-next-boot settings from BCH. Note that you cannot use the BCH interface to list or modify cell failure-usage settings. Instead use HP-UX commands or Partition Manager. Step 1.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions For example, CELLCONFIG 6 OFF sets the use-on-next-boot setting for cell 6 to OFF. This causes the cell to not be used (not rendezvous) in the partition the next time the partition boots. Configuration Menu: Enter command > CELLCONFIG 6 OFF Are you sure you want to DECONFIGURE cell 6 for next boot? (y/[n]) >> y Cell 6 will be disabled during next reboot. Configuration Menu: Enter command > Step 4.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions You can use HP-UX commands to list and configure the use-on-next-boot and failure-usage settings for cells assigned to any partitions within the Superdome complex. HP-UX Step 1. Log in to HP-UX running on the partition. You can log in to HP-UX on the partition either by directly connecting with telnet or rlogin, or by logging in to its complex’s GSP and accessing the partition’s console.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions To list a specific cell’s failure-usage and use-on-next boot settings, issue the parstatus -V -c# command and specify the cell number. # parstatus -V -c2 [Cell] Hardware Location Global Cell Number Actual Usage Normal Usage Connected To Core Cell Capable Firmware Revision Failure Usage Use On Next Boot Partition Number : : : : : : : : : : cab0,cell2 2 active base base cab0,bay1,chassis3 yes 6.0 activate yes 0 Memory OK : 2.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 4. If you have modified a cell’s attribute settings, for the settings to be used you must reboot the partition to which the cell is assigned. Rebooting the cell’s partition allows the partition to use each cell’s new attribute settings.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions b. To change whether or not a cell will be used the next time the selected partition is booted, highlight the entry for the cell for which you want to modify the settings for and click the Modify Cell(s) ... button. The Modify Cell Attributes window will be displayed allowing you to modify the cell’s Use on Next Boot setting. c.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Moving Cells to a Different Partition To move a cell to a different partition, use the high-level procedure describe here. This involves: 1. making the cells current partition inactive 2. removing the cell from its current partition 3. adding the cell to the new partition 4.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions In this step you perform a reboot-for-reconfig of the partition that initially contains the desired cell(s). This returns the cells to the free cell list so that they are available in the next step. Step 2. Use the procedure “Adding Cells to a Partition” on page 178 to add the cell(s) you made available in step 1 to the partition (that will be their new location).
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Moving I/O to a Different Partition CAUTION Moving a cell or I/O chassis from one partition to another is effectively the same as moving the associated I/O devices from one computer to another. All precautions you would take when moving I/O devices from one computer to another should be taken here.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions For details see “Moving Cells to a Different Partition” on page 196. Disks, filesystems, volume groups, and networking may need to be reconfigured once the I/O chassis is moved to its new partition.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Moving an I/O Chassis to a Different Cell Each I/O chassis is physically cabled to one of the cells in the same Superdome complex. This cabling makes the I/O chassis available to the cell and to the partition to which the cell is assigned. Normally each I/O chassis remains directly cabled to the same cell.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Listing All Configured Partitions You can configure each Superdome complex to include one or more partitions that are composed of cells in the complex. This section presents ways to list all partitions that are configured in a Superdome complex. You can perform this task using GSP menus, HP-UX commands, or Partition Manager.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Step 2. From the GSP command menu, enter the CP command to list all configured partitions within the Superdome complex. The GSP command menu’s CP command lists each partition (by partition number) and indicates which cells from each cabinet are assigned to the partition. In the following example the complex has two partitions: partition number 0 has cells 0 and 2, and partition number 1 has cells 4 and 6.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions The parstatus -P command lists all partitions and shows each partition’s number, the number of cells and I/O chassis assigned to it, the partition’s active core cell, and its name.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Partition Manager Step 1. Run the Partition Manager: /opt/parmgr/bin/parmgr When the Partition Manager starts up both the left-hand-side and the right-hand-side of the display will list the partitions in the complex. If you are already running the Partition Manager and are not at the Complex View, just click on the root of the tree (My Complex) on the left-hand-side of the display to display the list of partitions.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Listing Cell Partition Assignments Each cell in a Superdome complex is either assigned to a partition, or it is unassigned (it is on the “free cell list”). This section presents a method for listing all cells in a Superdome complex and their partition assignments (if any). You can perform this task using HP-UX commands.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Consolidating Multiple Partitions Consolidating multiple partitions involves (1) removing a partition, thus making all the partition’s cell available to be assigned to other partitions, and (2) assigning those cells to another partition. This general process effectively removes one or more virtual systems (partitions) and allocates those resources to another partition within the same Superdome complex.
Configuring and Managing Superdome Partitions Procedures for Managing Partitions Unlocking Complex Profiles Unlocking complex profiles is not recommended. You can, if required, use the parunlock command. See “parunlock Command” on page 217 for details.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax HP-UX Superdome Configuration Commands—Details and Syntax This section provides you with additional details and the command-line syntax for the new HP-UX Superdome configuration commands.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax parcreate Command NOTE For the most up-to-date reference information on the parcreate command, see the parcreate (1M) manpage on your system. The information here is provided for quick reference. The parcreate command creates a new partition. This command takes the specified cells (and any attached I/O chassis) from the free cell list and assigns them to the partition.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax • The only valid failure_usage value is: ri Reactivate with interleave (the default). -b path Specifies the primary (PRI) boot path. -t path Specifies the alternate (ALT) boot path. -s path Specifies the secondary (HAA) boot path. -r cell Specifies the root alternates. One to four cells can be specified. -B Specifies to boot the partition. The default is not to boot.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax parmodify Command NOTE For the most up-to-date reference information on the parmodify command, see the parmodify (1M) manpage on your system. The information here is provided for quick reference.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax Note that you must also to specify any one or more of the following options. -a cell:[cell_type]:[use_on_next_boot]:[failure_usage] Specifies the cell(s) to be added to the partition. • The valid cell_type value is: base Base cell. (The default.) • The valid use_on_next_boot values for cells are: y Participate in reboot. (The default.) n Do not participate in reboot.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax parremove Command NOTE For the most up-to-date reference information on the parremove command, see the parremove (1M) manpage on your system. The information here is provided for quick reference. The parremove command removes an existing partition. This will remove all cells from the partition and destroy the partition definition.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax 214 Chapter 4
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax parstatus Command NOTE For the most up-to-date reference information on the parstatus command, see the parstatus (1) manpage on your system. The information here is provided for quick reference. The parstatus command displays information about the partitions or hardware within a Superdome complex. If you specify no arguments, parstatus lists information about all major components of the complex.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax -X Display the complex’s attributes. -A Only display the available resources in the complex. -V Increase the amount of information displayed. -M Produce a machine readable/parseable output. -C Show information for all the cells in the complex. -I Show information for all I/O chassis in the complex. -B Show information for all cabinets in the complex.
Configuring and Managing Superdome Partitions HP-UX Superdome Configuration Commands—Details and Syntax parunlock Command NOTE For the most up-to-date reference information on the parunlock command, see the parunlock (1M) manpage on your system. The information here is provided for quick reference. The parunlock command unlocks the Stable Complex Configuration Data or Partition Configuration Data. Use this command with extreme caution.
Configuring and Managing Superdome Partitions Related Information Related Information This section lists other sources for information on the topics covered in this chapter. Chapters in This Book The following chapters in this book include details about topics covered in this chapter. • Chapter 1, “Overview of the Superdome System Environment,” on page 13—Gives an overview of the Superdome server environment and relevant tasks.
Configuring and Managing Superdome Partitions Related Information The Hewlett-Packard Technical Documentation home page. This site provides free online access to HP-UX documentation, hardware documentation, related development information, and more.
Configuring and Managing Superdome Partitions Related Information 220 Chapter 4
5 Booting and Resetting Superdome Partitions This chapter covers the tasks and concepts involved in booting HP Superdome partitions. HP Superdome servers and partitions boot in much the same way as do other HP 9000 servers, but you can boot, reboot, and reset each partition independently of the other partitions within a Superdome complex.
Booting and Resetting Superdome Partitions Introduction to Boot and Reset Tasks Introduction to Boot and Reset Tasks The following table lists the supported partition boot and reset tasks for HP Superdome servers. Detailed procedures for the tasks listed in Table 5-1 are provided in “Procedures for Booting and Resetting Partitions” on page 241.
Booting and Resetting Superdome Partitions Introduction to Boot and Reset Tasks Table 5-1 HP Superdome Booting and Resetting Tasks Task Procedures Description Tools “Booting HP-UX in Single-User or LVM-Maintenance Mode” on page 254 Boot HP-UX on a partition, but boot in single-user or LVM-maintenance mode. BCH “Booting from an HP-UX Installation Source” on page 256 Boot the partition from an HP-UX installation source, in order to install HP-UX on the partition.
Booting and Resetting Superdome Partitions Introduction to Boot and Reset Tasks Table 5-1 HP Superdome Booting and Resetting Tasks Task Procedures Description Tools “Listing Partition Boot Settings” on page 269 List the current settings that establish the partition’s boot-time behavior. BCH “Configuring Boot Paths for a Partition” on page 273 Set the primary (PRI) high-availability (HAA), and alternate (ALT) boot path variables for a partition.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues Overview of Partition Booting Concepts and Issues This section covers the issues, options, and features related to booting HP Superdome partitions. Also covered are the requirements for booting and an overview of the cell and partition boot process. Details are in the following sections.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues See “Performing a Reboot-for-Reconfig for a Partition” on page 263, or “Resetting a Partition to a Ready-for-Reconfig State” on page 264 for details. Types of Superdome Booting The following list summarizes all types of booting, rebooting, and resetting that are supported for HP Superdome partitions. • Reboot—Shuts down HP-UX and reboots the partition. Only the partition’s active cells are rebooted.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues • Ready-for-Reconfig State—Shuts down a partition, performs any partition reconfigurations, and keeps all cells at a boot-is-blocked (BIB) “cell firmware” state, thus making the partition and all of its cells inactive. When a partition is in a ready-for-reconfig state, you can reconfigure (or remove) the partition from a remote partition.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues signal from the GSP command menu; be certain to reset the correct partition. • The GSP command menu’s RS (reset) command provides the method for resetting and booting a Superdome partition’s hardware after the partition has been shut down and halted. You can shut down and halt a partition by using the shutdown -h or reboot -h commands.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues Partition and Cell Boot States and Activities Using a partition’s Virtual Front Panel, you can view details about partition and cells boot states and activities. From the GSP main menu, select the VFP menu for Virtual Front Panel options. You can view a Virtual Front Panel for a specific partition that includes details for all cells in the partition, as shown below.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues Table 5-2 Partition State Superdome Partition and Cell Boot States and Activities Partition Activity Cell States Cell Activities Cell(s) Booting Late CPU self-test Processor test, Cell firmware test, Processor firmware slave rendezvous Cell(s) Booting I/O discovery I/O system bus adapter configuration, I/O local bus adapter configuration Cell(s) Booting Remote fabric initialization Partition rendezvous s
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues Requirements for Booting Partitions Before you boot a partition, HP recommends that the partition meet the requirements listed here. • All partitions within a Superdome complex must conform to an HP-recommended complex configuration. See Chapter 4, “Configuring and Managing Superdome Partitions,” on page 113 for partition requirements and guidelines.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues Partition Cell and HP-UX Booting Process On HP Superdome servers, each partition goes through the stages described here when proceeding from being powered on (or reset) to booting the HP-UX operating system. See also Appendix A for a discussion of the Superdome cell booting process.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues 3. Power-On Self Test (POST) Cells and other system components go through self-test (POST) activities. 4. Boot-Is-Blocked (BIB) or Partition Rendezvous Each cell whose use-on-next-boot value is “n” (do not use) remains at boot-is-blocked and does not proceed to rendezvous with the other cells in the partition.
Booting and Resetting Superdome Partitions Overview of Partition Booting Concepts and Issues 6. Initial System Loader (ISL) and Secondary System Loader (hpux) In most situations you need not use the ISL and hpux interfaces. However, when using the BCH interface’s BO (boot) command you can select to stop at the ISL prompt to perform more detailed booting tasks. For example, you can use the ISL interface to boot HP-UX in single-user or LVM-maintenance mode, or to boot an HP-UX kernel other than /stand/vmunix.
Booting and Resetting Superdome Partitions Planning and Configuring Partition Boot Settings Planning and Configuring Partition Boot Settings Each partition has its own collection of boot-related settings that specify which hardware manages the boot process (the core cell), how the boot process proceeds (automatically boot, or wait for BCH commands), and which I/O device is selected for booting HP-UX.
Booting and Resetting Superdome Partitions Planning and Configuring Partition Boot Settings The auto-start option specifies what occurs when any of a partition’s components (processors or memory) fails self-test. By default, AUTOSTART is OFF, causing the partition to stop at the BCH interface following a self-test failure. If AUTOSTART is ON then the partition proceeds with the normal boot behavior following a failure.
Booting and Resetting Superdome Partitions Planning and Configuring Partition Boot Settings the core cell is not directly connected to the I/O chassis where the boot device resides). See Appendix A for more details. • Cell “Use-on-Next-Boot” Setting—Each cell in a partition has an associated use-on-next-boot setting that determines if the cell’s resources are used by the partition.
Booting and Resetting Superdome Partitions Planning and Configuring Partition Boot Settings Typically the HAA device is a secondary boot device that is a mirror of the PRI device, and the ALT device is an alternate device such as DVD-ROM or tape device from which the system can boot via install or recovery media. • Ensure that the core I/O, PRI boot device, and network card(s) all are connected to same cell (the core cell).
Booting and Resetting Superdome Partitions Tools for Managing Superdome Booting Tools for Managing Superdome Booting HP Superdome servers support the following software tools for configuring and managing partition boot settings. For an overview of procedures that use these boot management tools, see “Introduction to Boot and Reset Tasks” on page 222. While these tools do overlap in some of the functionality they provide, each provides unique capabilities.
Booting and Resetting Superdome Partitions Tools for Managing Superdome Booting • HP-UX utilities—Several HP-UX utilities allow you to check and set a partition’s HP-UX boot options, check other partitions’ boot settings, and perform reboot, shutdown, and reboot-for-reconfiguration tasks. The reboot, shutdown, parmodify, and parstatus commands provide these features.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Procedures for Booting and Resetting Partitions Use the detailed procedures given in this section to boot and reset partitions and to configure boot-related settings for your Superdome partitions. You can perform these tasks using one or more of the following tools: • The Guardian Service Processor (GSP) menus. • The Boot Console Handler (BCH) interface. • The system loaders (ISL and hpux). • HP-UX commands.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Monitoring Partition Boot Activity On HP Superdome servers you can monitor the partition boot process, from power-on or reset to HP-UX start-up, using the Virtual Front Panel for the partition. You can perform this task using the GSP menu. • “GSP” on page 242 For details on the partition and cell boot states and activities that you can observe from a partition’s Virtual Front Panel, refer to Table 5-2 on page 229.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. Select the partition you wish to monitor. Skip this step if you are accessing the GSP using a single-partition-user account. If using an operator or administrator account, select the partition to monitor or select the system VFP to monitor all partitions. Partition VFP’s available: # --0) 1) S) Q) Name ---jules00 jules01 System (all chassis codes) Quit GSP:VFP> 1 Step 3.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Accessing a Partition’s Console and BCH Interface Each partition has its own Boot Console Handler (BCH) interface that provides you a method for interacting with the partition before HP-UX has booted. The BCH interface allows you to manage the partition’s HP-UX boot process and to configure various boot-related settings.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Use the following procedure to access a partition’s console and BCH interface. GSP Step 1. Log in to the GSP for the partition’s Superdome complex. Use telnet to connect to the Superdome complex’s GSP. # telnet sdome-s Trying... Connected to sdome-s.rsn.hp.com. Escape character is ’^]’. Local flow control off GSP login: Accountname GSP password: Welcome to Superdome’s Guardian Service Processor Step 2.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 3. Select the partition whose console (and BCH interface) you wish to access. Skip this step if you are accessing the GSP using a single-partition-user account. If using an operator or administrator account, select the partition whose console you wish to access.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Once the partition has completed resetting, or has completed booting HP-UX, you can interact with the partition’s BCH or HP-UX prompts. • When another user already is attached to the console, you can access the partition’s console only in spy (read-only) mode. Spy mode allows you to view console information but does not enable you to enter commands.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Finding Bootable Devices You can search for and find bootable devices for a partition by using the BCH interface’s SEARCH command. This searches for all bootable devices connected to any of the partition’s currently used cells. Note that you cannot access any I/O connected to a partition’s unused cells (those cells that are deconfigured for the current partition boot).
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions The SEARCH command reports the potential boot devices it locates.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Booting a Partition Past Boot-Is-Blocked When a partition is inactive, all cells in the partition are in a boot-is-blocked state. This is the case when a partition is in a ready-for-reconfig state. You can boot a partition to make it active by using the GSP command menu’s BO (boot) command. This boots the cells past boot-is-blocked and allows the cells to rendezvous and form the partition.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. From the GSP command menu, enter the BO command and specify which partition is to be booted. The GSP releases the selected partition from boot-is-blocked: the configured cells proceed past boot-is-blocked and rendezvous to form the partition. As a result of the BO command, the partition is active and no longer is in a ready-for-reconfig state.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Booting HP-UX on a Partition You can boot HP-UX on a partition using the BCH interface, which is available from the partition’s console. Each partition has its own console that is available from its Superdome complex’s GSP console menu. Each partition can boot and reboot its instance of HP-UX independently from all other partitions. You can perform this task using the BCH interface.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 3. Boot the device using the BCH interface’s BOOT command. To boot the /stand/vmunix HP-UX kernel from the device without stopping at the ISL prompt, enter n to automatically proceed past ISL. In most situations you will boot /stand/vmunix and not need to stop at ISL. Main Menu: Enter command or menu > BOOT PRI Primary Boot Path: 0/0/1/0/0.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Booting HP-UX in Single-User or LVM-Maintenance Mode You can boot HP-UX in single-user mode or LVM-maintenance mode. To do this use the BCH interface to boot the desired device, and use the Initial System Loader (ISL) and the Secondary System Loader (hpux) to specify the options for booting HP-UX in the desired mode. See the hpux (1M) manpage for details on options for other boot modes.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions • To boot HP-UX in single-user mode: hpux boot -is /stand/vmunix • To boot in LVM-maintenance mode: hpux boot -lm /stand/vmunix ISL Revision A.00.42 JUN 19, 1999 ISL> hpux -is /stand/vmunix Boot : disk(0/0/2/0/0.13.0.0.0.0.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Booting from an HP-UX Installation Source You can boot a partition from an HP-UX installation source—such as an install CD or an Ignite server—by specifying the install source using the BCH interface’s BOOT command. This allows you to install HP-UX on any of the partition’s eligible devices.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Booting a Partition to the ISL Prompt You can stop a partition’s booting at the Initial System Loader (ISL) in order to interact with the ISL prompt. Normally you will not need to access ISL unless you need to use the Secondary System Loader (hpux). For details about ISL, see the isl (1M) manpage. You can perform this task using the BCH interface.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Shutting Down HP-UX on a Partition When HP-UX is running on a partition, you can shut down HP-UX using either the shutdown command or the reset command. On Superdome servers you have the following four options when shutting down HP-UX: • Shut down HP-UX and halt the partition. • Shut down HP-UX and reboot the partition. • Perform a reboot-for-reconfig of the partition.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Refer to the following list for the available HP-UX shut down options for Superdome partitions. • Shut down HP-UX and halt the partition. Use the shutdown -h or reboot -h command to shut down and halt the partition. This leave the partition and all its cells in an active state (the partition cannot be reconfigured) after HP-UX shuts down and halts.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Rebooting or Resetting a Partition You can reset a partition by using the GSP command menu, using the partition’s BCH interface, or by issuing commands from HP-UX running on the partition. Using the procedures in this section, you can reset a partition and boot it back to BCH or HP-UX. HP Superdome servers also support other types of partition resetting.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. At the GSP command menu, enter the RS command, specify which partition is to be reset, and confirm whether to reset it. The GSP command menu’s RS command resets all active cells in the partition and reboots them past partition rendezvous to BCH or HP-UX.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. From the partition’s BCH main menu, enter the REBOOT command to reboot the partition. The BCH interface’s REBOOT command resets all active cells in the partition and reboots them past partition rendezvous to BCH or HP-UX.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Performing a Reboot-for-Reconfig for a Partition When you perform a reboot-for-reconfig of a partition, the HP-UX command that you issue (shutdown or reboot) does the following tasks: • Shuts down HP-UX and resets all cells that are assigned to the partition, including any inactive cells. • Reconfigures the partition if necessary (adds or removes cells). • Boots all cells in the partition.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Resetting a Partition to a Ready-for-Reconfig State Resetting a partition to a ready-for-reconfig state performs any changes to the partition’s configuration and puts the partition and all its cells in a boot-is-blocked (inactive) state. You can reset a partition to ready-for-reconfig by using the GSP command menu, the partition’s BCH interface, or HP-UX commands.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. At the GSP command menu, enter the RR command, specify which partition is to be reset, and confirm whether to reset it to ready-for-reconfig. The GSP command menu’s RR command resets all cells in the partition, performs any partition reconfigurations, and halts all cells at a boot-is-blocked state, thus making the partition and all its cells inactive.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 2. From the partition’s BCH main menu, enter the RECONFIGRESET command to reset the partition to a ready-for-reconfig state. The BCH interface’s RECONFIGRESET command resets all cells in the partition, performs any partition reconfigurations, and halts all cells at a boot-is-blocked state, thus making the partition and all its cells inactive.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Performing a Transfer-of-Control (TOC) Reset of a Partition You can use the GSP command menu’s TC command to perform a transfer-of-control (TOC) reset on a partition. If crash dump is configured for HP-UX on the partition, when you TOC the partition while it is running HP-UX the partition performs a crash dump and gives you an opportunity select the type of dump. You can perform this task using the GSP menu.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Be certain to correctly select the partition to be reset. IMPORTANT GSP:CM> TC This command TOCs the selected partition. WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition. # --0) 1) Name ---jules00 jules01 Select a partition number: 0 Do you want to TOC partition number 0? (Y/[N]) y -> The selected partition will be TOCed.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Listing Partition Boot Settings You can list a partition’s boot-related settings by using the partition’s BCH interface or by using the parstatus HP-UX command. This section covers listing a partition’s boot settings. Refer to the following procedures for details on configuring a partition’s boot settings.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Use the following list to determine which BCH menu and command provides the boot information that interests you. • BCH main menu If you are at one of the other BCH menus, enter MA to return to the BCH interface’s main menu. PATH Displays or sets the boot paths: primary (PRI), high-availability (HAA), and alternate (ALT). • BCH configuration menu From the BCH main menu, enter CO to access the configuration menu.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions The following example shows using the PATH command to list the partition’s boot paths, then accessing the BCH configuration menu and issuing the AU command to list the partition’s auto-start setting. Main Menu: Enter command or menu > PATH Primary Boot Path: HA Alternate Boot Path: Alternate Boot Path: 4/0/2/0/0.10 4/0/2/0/0.a (hex) 4/0/1/0/0.6 4/0/1/0/0.6 (hex) 4/0/1/0/0.5 4/0/1/0/0.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions The boot setting information that parstatus reports is equivalent to the following BCH commands: PATH, CELLCONFIG, and CORECELL. The following example lists detailed information for partition number 0, including the partition’s boot path settings, its core cell information, and its cells’ use-on-next-boot settings.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring Boot Paths for a Partition Each partition in an HP Superdome complex has three boot path variables. The boot path variables are: primary (PRI), secondary (HAA, the “high-availability alternate”), and the alternate (ALT) boot device paths. Typically, HAA is a mirror of PRI, and ALT refers to a DVD-ROM or tape device. This section describes how to set these variables.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Step 3. As necessary, configure the boot path variable to the new value that corresponds to the target boot device. Use the BCH main menu’s PATH command. For example, to set the PRI boot path to a new value (4/0/2/0/0.10, in this case): Main Menu: Enter command or menu > PA PRI 4/0/2/0/0.10.0 Primary Boot Path: 4/0/2/0/0.10 4/0/2/0/0.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring Boot Actions for Partition Boot Paths Each boot path for a partition has associated with it a boot action. The boot actions are set through path flags, which can be set to the following values: • 0—Go to BCH (Boot Console Handler). • 1—Boot from this path. If unsuccessful, go to BCH. • 2—Boot from this path. If unsuccessful, go to the next path. • 3—Skip this path and go to the next path.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring Auto Start for a Partition The BCH interface’s auto-start setting for each partition determines how the boot process occurs when one of the partition’s components (processors or memory) fails self-test. By default AUTOSTART is set to OFF, and the partition stops at the BCH interface when a processor or DIMM fails self-test.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring Fast Boot Settings for a Partition The fast boot settings for a partition determine the self-tests that the partition performs during power on or partition boot. NOTE On Superdome servers use the BCH interface’s FASTBOOT command to set the fast boot settings. Do not use the ISL interface, which has no effect for Superdome partition self tests. You can perform this task using the BCH interface.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring the Boot Timer for a Partition The boot timer setting establishes the number of seconds a partition will wait for a boot device before timing out. You can perform this task using the BCH interface. • “BCH” on page 278 BCH Use this procedure to configure a partition’s boot timer setting. Step 1. Log in to the Superdome complex’s GSP, access the partition’s console, and access the BCH configuration menu.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Deconfiguring Cells, Processors, and Memory Refer to Chapter 3, “Managing the Overall Complex,” on page 57 for details on deconfiguring cells, processors, and memory for a partition.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Configuring Automatic System Restart for a Partition Only GSP users who have administrator authority can configure automatic system restart for a partition. To perform this task use the GSP command menu’s AR command. CAUTION Refer to your HP support representative for details and assistance in setting automatic system restart. This setting enables a partition to automatically reset upon specified events.
Booting and Resetting Superdome Partitions Procedures for Booting and Resetting Partitions Powering On and Powering Off Partition Hardware Chapter 3, “Managing the Overall Complex,” on page 57 contains details on powering on and powering off HP Superdome hardware components.
Booting and Resetting Superdome Partitions Related Information Related Information This section lists other sources for information on the topics covered in this chapter. Chapters in This Book The following chapters in this book include additional details about topics covered in this chapter.
Planning Superdome Configurations A Planning Superdome Configurations What follows is a white paper intended to help system administrators and system architects plan, configure and reconfigure the structural components of a Superdome complex. It contains the following sections: 1. “How To Use this Document” on page 284. 2. “Building Blocks and Definitions” on page 286. 3. “Rules and Guidelines for Configuring a Complex” on page 323.
Planning Superdome Configurations How To Use this Document How To Use this Document Terms: • Cell: see “What is a Cell?” on page 303. - Unassigned cell: see “Cell Types” on page 309. • Complex: see “What Is a Complex?” on page 292. • I/O chassis: see “What is an I/O Chassis?” on page 317. • Partition: see “What is a Partition?” on page 298. Full Glossary on page 287 .
Planning Superdome Configurations How To Use this Document You may be reading this paper in the form of an appendix to Managing Superdome Complexes, or as PDF file delivered in the /usr/share/doc directory of an HP-UX 11i system. The most recent version is published on Hewlett-Packard’s documentation website, docs.hp.com. To check that version for changes, go to docs.hp.com, then choose “Browse by Topic”, then “HP-UX 11i Operating System” and then “White Papers” under “System Administration”.
Planning Superdome Configurations Building Blocks and Definitions Building Blocks and Definitions Outline of this Section • • • • • • • • • • • • “Glossary” on page 287 “What is a Superdome System?” on page 291 “What Is a Complex?” on page 292 “What is the Guardian Service Processor?” on page 296 “What is a Partition?” on page 298 “What is a CPU Cabinet?” on page 299 “What is a Cell?” on page 303 “What is an XBC (Crossbar Controller)?” on page 312 “Crossbar Connections” on page 314 “What is an I/O Chassis
Planning Superdome Configurations Building Blocks and Definitions Glossary • 16-, 32-, 64-way-capable system: The three Superdome models currently available; see “What is a CPU Cabinet?” on page 299. • CPU cabinet: Superdome’s hardware “box”; see “What is a CPU Cabinet?” on page 299. • Cell; cell board: Superdome’s hardware building blocks, containing memory, processors and other core components; see “What is a Cell?” on page 303. ❏ active cell: a cell in use in a partition; see “Active Cell” on page 309.
Planning Superdome Configurations Building Blocks and Definitions • Complex: A hardware configuration that can support multiple instances of an operating system (by means of partitions); see “What Is a Complex?” on page 292. • Complex Profile: The data structure managed by the GSP that represents the configuration of a complex. See “The Complex Profile” on page 292. • Core I/O: Comprises console support and 10/100 Base T LAN; see “Core I/O” on page 318.
Planning Superdome Configurations Building Blocks and Definitions • I/O slots: The slots in an I/O chassis; see “I/O Cards” on page 317. • IPL: Initial Program Load(er). See “What Happens when a Cell Boots” on page 311. • Local Bus Adapter: The chip that connects an individual I/O slot to the System Bus Adapter, and thence to a cell; see “Cell Connectivity” on page 308. • Monarch CPU: The processor that performs selftest and other functions when a cell is activated as part of a booting partition.
Planning Superdome Configurations Building Blocks and Definitions • SAM: The menu-driven System Administration Manager tool used to configure HP-UX. • Single Computer Board (SBC) and SBC Hub (SBCH): The components of the Guardian Service Processor (GSP). See “What is the Guardian Service Processor?” on page 296. There is one SBC per complex, and one SBCH per CPU cabinet.
Planning Superdome Configurations Building Blocks and Definitions What is a Superdome System? Terms: • • • • Cell: see “What is a Cell?” on page 303. Complex: see “What Is a Complex?” on page 292. CPU cabinet: see “What is a CPU Cabinet?” on page 299. Partition: see “What is a Partition?” on page 298. Full Glossary on page 287 .
Planning Superdome Configurations Building Blocks and Definitions What Is a Complex? Terms: • • • • • • • • Active, inactive, unassigned cell: see “Active Cell” on page 309. Cell: see “What is a Cell?” on page 303. Core cell: see “Core Cell” on page 309. CPU cabinet; 32-way-capable system; 64-way-capable system: see “What is a CPU Cabinet?” on page 299. Guardian Service Processor (GSP): see “What is the Guardian Service Processor?” on page 296. iCOD: see “Instant Capacity on Demand (iCOD)” on page 307.
Planning Superdome Configurations Building Blocks and Definitions • Stable complex configuration information (Group A), including: ❏ Attributes of the complex (its name, model number, serial number, etc) ❏ cell-to-partition assignments and unassigned cells ❏ XBC connections ❏ other complex-wide information • Dynamic complex configuration information (Group B).
Planning Superdome Configurations Building Blocks and Definitions ❏ iCOD information indicating how many processors in the partition, if any, you have not purchased; see “Instant Capacity on Demand (iCOD)” on page 307.
Planning Superdome Configurations Building Blocks and Definitions • If the partition configuration information (Group C) has changed: ❏ The changes are broadcast to the cells in that partition immediately, though the information will normally not be used until the next time the partition boots. Point to note: The GSP will not update stable complex configuration information (Group A) for any cell unless it can update all cells, and it cannot update the partition assignment of an active cell.
Planning Superdome Configurations Building Blocks and Definitions What is the Guardian Service Processor? Terms: • • • • Complex: see “What Is a Complex?” on page 292. CPU cabinet: see “What is a CPU Cabinet?” on page 299. Partition: see “What is a Partition?” on page 298. Support Management Station (SMS): see “Support Management Station (SMS)” on page 322. Full Glossary on page 287 .
Planning Superdome Configurations Building Blocks and Definitions • Always-on capability. The GSP is alive so long as the circuit breakers are closed. • Access control. Provides three levels of capabilities. • Multiple access methods: ❏ Local RS232 port, providing support for directly connected terminal or laptop computer. ❏ Remote-modem port. ❏ Customer LAN port, providing support for telnet access.
Planning Superdome Configurations Building Blocks and Definitions What is a Partition? Terms: • • • • Cell: see “What is a Cell?” on page 303. Complex: see “What Is a Complex?” on page 292. CPU cabinet: see “What is a CPU Cabinet?” on page 299. I/O chassis: see “What is an I/O Chassis?” on page 317. Full Glossary on page 287 . A partition corresponds roughly to a single, standalone system.
Planning Superdome Configurations Building Blocks and Definitions What is a CPU Cabinet? Terms: • • • • Cell: see “What is a Cell?” on page 303 Complex: see “What Is a Complex?” on page 292 I/O chassis: see “What is an I/O Chassis?” on page 317 Guardian Service Processor: see“What is the Guardian Service Processor?” on page 296.
Planning Superdome Configurations Building Blocks and Definitions A CPU cabinet is Superdome's hardware “box.” It contains: • cells; • The Guardian Service Processor (one per complex); • I/O chassis (a maximum of four chassis for a maximum of 48 slots); • five top-venting I/O fans; • four top-venting cabinet fans; • six power supplies, connected to the power source by one or (for redundancy) two cables. This block diagram shows how all the components in a 32-way-capable system communicate.
Planning Superdome Configurations Building Blocks and Definitions Appendix A 301
Planning Superdome Configurations Building Blocks and Definitions NOTE A CPU cabinet has no room for internal disks; all peripherals are external, attached to the I/O chassis. Cabinets can be cabled together to form a complex. A complex comprises a maximum of two cabinets. A single cabinet is a 16-way-capable (SD1600) or 32-way-capable (SD3200) system; two contiguous cabinets cabled together are a 64-way-capable system (SD6400).
Planning Superdome Configurations Building Blocks and Definitions What is a Cell? Terms: • • • • • • • • • • • • CPU cabinet: see “What is a CPU Cabinet?” on page 299. Cell Controller (CC): see “Cell Controller (CC)” on page 306. Complex: see“What Is a Complex?” on page 292. Complex profile: see “The Complex Profile” on page 292. Core I/O: see “Core I/O” on page 318. GSP: see “What is the Guardian Service Processor?” on page 296. I/O chassis: see “What is an I/O Chassis?” on page 317.
Planning Superdome Configurations Building Blocks and Definitions A cell, or cell board, is the basic building block of a Superdome system. When configuring or reconfiguring a complex, you assign cells to partitions. A cell provides processing power comparable to that of a mid-range server, but a Superdome system supports this processing power with much greater memory capacity and I/O bandwidth. For more information, see: • • • • • “Cell Components” on page 304. “Cell Compatibility” on page 308.
Planning Superdome Configurations Building Blocks and Definitions This cell contains four double speed busses, each connecting a single processor to the cell controller(CC) chip, which controls the cell's memory and links the cell to other cells and to I/O.
Planning Superdome Configurations Building Blocks and Definitions Cell Controller (CC) The cell controller chip co-ordinates memory between the major components of a cell board • memory controllers (DIMMs), • processors, • the I/O bus (System Bus Adapter) - and determines if a request requires communication with another cell or with the I/O subsystem.
Planning Superdome Configurations Building Blocks and Definitions Processors Each cell contains four processors. All the processors in the same partition must be of the same type (the partition will not boot if they are not). At first release, the only processor type available is PA-8600. Instant Capacity on Demand (iCOD) All cells are delivered with four processors, but you pay only for the processors you use.
Planning Superdome Configurations Building Blocks and Definitions Memory Each cell can contain up to 16 GB RAM in 2 GB increments. Performance and High Availability For high availability reasons, a cell should contain at least 8 memory DIMMs (Dual Inline Memory Modules) for a minimum of 4 GB RAM. For the best performance, all the cells in a partition should contain the same amount of RAM.
Planning Superdome Configurations Building Blocks and Definitions Crossbar Link to CPU Cabinet Cells are connected to the cabinet by means of the cell controller's crossbar (XBC) link. A maximum of four cells plug into a crossbar; there are two crossbar in a CPU cabinet. See “What is an XBC (Crossbar Controller)?” on page 312 for more information.
Planning Superdome Configurations Building Blocks and Definitions NOTE In a booted partition that has more than one viable core cell, the only core I/O card that is active is the core cell’s. How the Core Cell is Selected. If a partition has more than one viable core cell, PDC (Processor Dependent Code) decides when the partition is booting which cell should be the core cell. It does this on the basis of a prioritized list which is part of the Partition Configuration Data maintained by the GSP.
Planning Superdome Configurations Building Blocks and Definitions What Happens when a Cell Boots This section explains how a cell becomes active as its partition boots. The sequence is as follows: 1. The system administrator enables power to the cell. (This can be done by means of the HP-UX frupower command, or from SAM or the GSP.) 2. The cell is held in the reset state until power stabilizes. 3. The cell is released from reset and boot is blocked (that is, the cell is on but is not allowed to boot). 4.
Planning Superdome Configurations Building Blocks and Definitions What is an XBC (Crossbar Controller)? Terms: • 64-way-capable system; CPU cabinet: see “What is a CPU Cabinet?” on page 299. • Cell: see “What is a Cell?” on page 303. • Cell Controller: see “Cell Controller (CC)” on page 306. • Partition: see “What is a Partition?” on page 298. Full Glossary on page 287 . Each CPU cabinet contains two crossbar backplane boards.
Planning Superdome Configurations Building Blocks and Definitions Appendix A 313
Planning Superdome Configurations Building Blocks and Definitions The two XBCs in a cabinet are connected to each other and, in a 64-way-capable system, to the two XBCs in the other cabinet as well. These connections allow cells to communicate and to share memory both within and across crossbars, allowing partitions comprising more than four cells. You need to be careful when configuring partitions that cross crossbar boundaries; not all configurations which are physically possible are supported.
Planning Superdome Configurations Building Blocks and Definitions In a 64-way-capable-system, another of these three ports connects the crossbar to the corresponding XBC in the other cabinet: Direct and Flex Links (64-way-capable-system) +------+ +------+ | | B | | | XBC0 |----------| XBC8 | | | | | +------+ +------+ |A |A | | +------+ +------+ | | B | | | XBC4 |----------|XBC12 | | | | | +------+ +------+ This figure shows the XBC-XBC links between crossbars (A) and the flex links between corresponding XB
Planning Superdome Configurations Building Blocks and Definitions U-Turn (32-way-capable-system) +------+ | | B | XBC0 |-----| | +------+ A| |C | | +------+ | | B | XBC4 |-----| | +------+ In this figure, C shows a second XBC-XBC link (a flex link) between XBCs in the same cabinet. This is a U-Turn configuration for a 32-way-capable-system. Note that the ports labeled B are not connected to anything.
Planning Superdome Configurations Building Blocks and Definitions What is an I/O Chassis? Terms: • • • • CPU cabinet: see “What is a CPU Cabinet?” on page 299. Cell: see “What is a Cell?” on page 303. Partition: see “What is a Partition?” on page 298. GSP (Guardian Service Processor): see “What is the Guardian Service Processor?” on page 296. Full Glossary on page 287 .
Planning Superdome Configurations Building Blocks and Definitions Core I/O Each partition must contain at least one cell that is attached to an I/O chassis containing core I/O, which comprises primarily: • console support • 10/100 BaseT LAN Placement of Core I/O, Boot and Removable Media Cards: • Put the core-I/O card in the rightmost slot (slot 0) of an I/O chassis (this is the only slot it can go in). • Put the boot device controller in the same I/O chassis as the core I/O card.
Planning Superdome Configurations Building Blocks and Definitions Configuring and Controlling an I/O Chassis Before a chassis is installed in its I/O bay and cabled to a cell, you will not be able to power it on. Once the chassis is cabled to a cell, powering on the cell will power on the chassis and powering off the cell will power off the chassis. Powering off a chassis that is attached to an active cell requires some planning.
Planning Superdome Configurations Building Blocks and Definitions What is an I/O Expansion Cabinet? Terms: • CPU cabinet: see “What is a CPU Cabinet?” on page 299. • I/O chassis: see “What is an I/O Chassis?” on page 317. Full Glossary on page 287 . NOTE I/O expansion cabinets are not available with early shipments of Superdome. Contact your HP Sales Representative for up-to-date information. An I/O expansion cabinet contains up to six twelve-slot I/O chassis (cardcages).
Planning Superdome Configurations Building Blocks and Definitions The Console and the Support Management System Appendix A 321
Planning Superdome Configurations Building Blocks and Definitions Support Management Station (SMS) The Support Management Station (SMS), sometimes called a scan station, is an HP-UX workstation (A500 or equivalent) that runs Superdome diagnostics and testing tools. These tools are used by HP Customer Engineers or Service Engineers to monitor the health of your Superdome systems and to aid in system upgrades and hardware replacement.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Rules and Guidelines for Configuring a Complex This section contains information on the following topics: • “Recommendations for Cabling Crossbar Controllers (XBCs)” on page 324. • “Choosing Cells for Partitions” on page 325. • “Partitions, Cells and I/O Chassis” on page 333. • “Checklist for Performance” on page 341. • “Checklist for High Availability” on page 342.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Recommendations for Cabling Crossbar Controllers (XBCs) Before you go on, read: • “What is a Partition?” on page 298. • “What is a Cell?” on page 303. • “What is an XBC (Crossbar Controller)?” on page 312: - “Crossbar Connections” on page 314. Other terms and concepts: • 32-way, 64-way-capable system: see“What is a CPU Cabinet?” on page 299. • CPU cabinet: see “What is a CPU Cabinet?” on page 299.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Choosing Cells for Partitions Before you go on, read: • “What is a Partition?” on page 298. • “What is a Cell?” on page 303: - “Core Cell” on page 309 • “What is an XBC (Crossbar Controller)?” on page 312: - “Crossbar Connections” on page 314. Other terms and concepts: • “Recommendations for Cabling Crossbar Controllers (XBCs)” on page 324.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Building a Complex from Scratch When building a complex from scratch, begin with the largest partition and proceed to the smallest. Put the first cell of the largest partition in slot 0 of the left CPU cabinet, then start the next largest partition in the lowest-numbered of the remaining empty slots, and so on.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Priority Cabinet-Slot Priority Cabinet-Slot 1 0-0 9 0-1 2 1-0 10 1-1 3 0-4 11 05 4 1-4 12 1-5 5 0-2 13 0-3 6 1-2 14 1-3 7 0-6 15 0-7 8 1-6 16 1-7 Guidelines for Performance and High Availability In general, what you do to improve performance will also improve availability. Exceptions are noted below.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Where To Add Cells • If the cells in a given partition will not fill all four of the slots in a given crossbar, plug the cells into alternate slots. Explanation: Pairs of slots (0 and 1, 2 and 3, etc.) share ports on the crossbar controller (XBC). To even out traffic, a partition that uses only two slots in a crossbar should use slots that don’t share ports, such as 0 and 2, or 1 and 3.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex • If a partition comprises four cells or fewer, all the cells should be connected to the same crossbar. For example, two four-cell partitions should be configured such that the cells of each plug into a single crossbar. Explanation: There are two crossbars to a CPU cabinet, and a maximum of four cells can plug into each.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Exception: A 64-way-capable system containing a large partition may need to break this rule. See the Exceptions under the previous guideline and “Building a Complex from Scratch” on page 326.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Distributing Resources • Each partition should consist of at least two cells. • Each partition should contain at least two viable core cells. See “Partitions, Cells and I/O Chassis” on page 333 for more information. • Each cell should have at least two active CPUs. • Configure cells into partitions by powers of two if possible.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Guidelines for Expandability When populating a CPU cabinet, plan, as far as possible, not only for your immediate needs but also for what you may want to add in the future. For example, if you define four 2-cell partitions in a 32-way-capable-system, you are leaving no room for expansion in that cabinet.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Partitions, Cells and I/O Chassis Before you go on, read: • “What is a Cell?” on page 303: - “Cell I/O” on page 308. - “Core Cell” on page 309. • “What is an I/O Chassis?” on page 317: - “Core I/O” on page 318 • “What is an I/O Expansion Cabinet?” on page 320. • “What is a Partition?” on page 298. Other terms and concepts: • 16-, 32-way, 64-way-capable system; CPU cabinet: see “What is a CPU Cabinet?” on page 299.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex That is, the cell that is attached to the I/O chassis must not only have been assigned to the partition, but also powered on and booted; see “What Happens when a Cell Boots” on page 311. • A 16- or 32-way-capable system should have at least two I/O chassis, and a 64-way-capable system should have at least four I/O chassis.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Then continue by assigning the second I/O chassis to the first cell in the next partition; continue until all partitions in (or beginning in) this CPU cabinet have an I/O chassis inside the CPU cabinet attached to their lowest-numbered cell; each of these chassis should contain a core I/O card.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Rules • Each I/O chassis can be connected to only one cell, and each cell can be connected to only one I/O chassis. See “Cell I/O” on page 308 for more information. • Each partition must contain at least one cell that is attached to an I/O chassis containing core I/O. This cell should be the lowest-numbered cell in the partition (the leftmost cell in the partition when you are looking at the cabinet from the front).
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex • An I/O expansion cabinet can be used by only one complex. This means that the two CPU cabinets in a 64-way-capable system can share an expansion cabinet, but two 32-way-capable systems (that is, single cabinets not combined into a 64-way-capable system) cannot. NOTE The two CPU cabinets in a 64-way-capable system can share the first expansion cabinet, but the second can be used by cells in the right CPU cabinet only.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Guidelines for High Availability • Make sure that more than one cell in each partition has an I/O chassis containing core I/O (partitions containing only one cell, or connected to only one I/O chassis, are not recommended). The cells attached to chassis containing core I/O should be the partition’s lowest-numbered cells.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex is primarily connected is disabled (or one card or any single connection fails). Paths to boot and root disk For a partition performing mission-critical tasks, configure the following paths to the boot device: 1. Primary attached to one viable core cell. 2. Secondary attached to the same viable core cell. 3.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Guidelines for Performance • If more than one cell in a partition is attached to an I/O chassis, spread out the I/O devices amongst the cells. Performance will probably not be as good if all or most I/O operations go through one cell. • Do not use the core I/O card as the partition’s main connection to the network (to your site LAN, for example).
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Checklist for Performance This section summarizes the recommendations in “Recommendations for Cabling Crossbar Controllers (XBCs)” on page 324, “Choosing Cells for Partitions” on page 325 and “Partitions, Cells and I/O Chassis” on page 333. Explanations are in those sections or as noted in parentheses below.
Planning Superdome Configurations Rules and Guidelines for Configuring a Complex Checklist for High Availability In many cases, best practices for high availability are the same as those for performance, though the underlying reasons are different. This section summarizes the recommendations in “Recommendations for Cabling Crossbar Controllers (XBCs)” on page 324, “Choosing Cells for Partitions” on page 325 and “Partitions, Cells and I/O Chassis” on page 333. Explanations are in those sections.
Index Numerics 12-slot I/O chassis, 19 48V Power Switch, 23 9000/800/SD16000, 16 9000/800/SD32000, 16 9000/800/SD64000, 16 A access configuration, 50 commands, 46 accessing BCH menu, 54 cabinet internals, 23 GSP and menus, 38, 42 partition consoles, 44 accounts Administrator (GSP), 37 Operator (GSP), 37 Single Partition User (GSP), 37 A-Class, 31 A-Class workstation, 21 activity logs, 36 adding cells to partitions, 178 adding partitions, 161 Administrator GSP account, 37 ALT, see alternate boot path alterna
Index function, 27 cell types, 118 cells, 18 boot states, 229 Boot-is-Blocked, 225, 229, 264 controlling power to, 93 controllng power to, 93 deconfiguring, 279 Failure Usage, 185 firmware versions of, 73 I/O connection, 17 installing, 17 listing configuration assignments, 205 memory configuration of, 67 Next Boot Flag, 185, 237 overview, 14 power status, 89 powering on/off, 93 processor configuration of, 67 selecting alternate core, 185 selecting core, 185 types of, 118 use-on-next-boot flag, 263 chassis c
Index direct access RS-232, 21 dual-cabinet server, 16 DVD-ROM devices, 19, 256 E Each, 57 error logs, 36 exiting exit console using ^b, 35 GSP session, 39, 42 external cabinet, 19 F Failure Usage (cell), 185 fan failure, detecting, 108 fans, 20 FASTBOOT setting, 277 filtering chassis codes, 36 firmware version, 73 firmware versions, determining, 73 Flex cables, 17, 20 forcing console write access (^ecf), 44 formats of chassis codes, 36 fruled, 97 frupower, 86, 95 function of I/O card, 27 G Genesis Partitio
Index moving between cells, 200 overview, 14 partitions, 15 service indicator lights, 99 I/O chassis, controlling power to, 93 I/O fans, 21 I/O runway busses, 19 Initial System Loader, 234 booting partitions, 257 initiator, 28 installing cells, 17 installing HP-UX, 256 installing PCI cards, 17 ioscan command, 27 ISL, see Initial System Loader L LAN HP Private LAN, 21 LEDs, 20, 23, 57 LEDs, see service indicator lights lights, 20 listing cabinets in a complex, 65 listing configured partitions, 201 listing pa
Index Analyze Complex Health, 102 blower status, 109 cabinet identification, 65 cell power status, 89 complex product number, 81 complex serial number, 79 controlling cell power, 96 controlling I/O chassis power, 96 Creating Partitions, 166 detecting memory failure, 105, 106 detecting processor failure, 104 fan status, 109 I/O power status, 90 listing cell memory configuration, 71 listing cell processor configuration, 71 listing defined partitions, 63 listing firmware versions in a complex, 77 naming/renami
Index power status, 84 cells, 89 I/O chassis, 90 PCI I/O slots, 91 power status, I/O chassis, 90 power supply failure, detecting, 108 powering cells on/off, 93 powering service indicator lights on/off, 97 Power-On Self Test, 233 PRI, see primary boot path primary boot path, 228, 270, 273, 275 Processor Dependent Code, 232 processors, 18 deconfiguring, 279 product number (of a complex), 81 Q quit GSP, 42 R rad command listing PCI slots, 30 on Superdome, 26, 30 real-time chassis codes, 36 real-time partition
Index W write access to console, 44 349
