nPartition Administrator's Guide HP Part Number: 5991-1247B_ed2 Published: February 2009 Edition: Second Edition
© Copyright 2007–2009 Hewlett-Packard Development Company, L.P Legal Notices © Copyright 2007–2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Table of Contents About This Document.......................................................................................................11 New and Changed Information in This Edition...................................................................................11 Document Organization.......................................................................................................................11 Typographic Conventions..........................................................................
Local Management..........................................................................................................................43 Remote Management Using WBEM................................................................................................44 WBEM Remote Management Files............................................................................................44 nPartition Commands Support for Remote Management Using WBEM..................................
Booting and Resetting nPartitions...............................................................................87 Overview of nPartition System Booting...............................................................................................87 Boot Process Differences for nPartitions on HP 9000 servers and HP Integrity servers.................88 Types of Booting and Resetting for nPartitions...............................................................................
Configuring Boot-Time System Tests..................................................................................................161 6 Creating and Configuring nPartitions......................................................................165 Tools for Configuring nPartitions.......................................................................................................165 Task Summaries for Creating and Configuring nPartitions...............................................................
parunlock Command..........................................................................................................................260 fruled Command.................................................................................................................................262 frupower Command...........................................................................................................................264 cplxmodify Command.............................................................
List of Figures 1-1 2-1 2-2 2-3 8 Partition Manager Version 2.0 Switch Complexes Dialog............................................................46 Two-Cell HP Server Cabinet..........................................................................................................55 Four-Cell HP Server Cabinet.........................................................................................................56 HP Superdome Server Cabinet...............................................................
List of Tables 1-1 1-2 1-3 1-4 1-5 2-1 3-1 4-1 4-2 4-3 4-4 5-1 6-1 7-1 7-2 8-1 A-1 A-2 nPartition Operating System Support...........................................................................................15 HP Servers Supporting nPartitions...............................................................................................17 nPartition Commands Releases.....................................................................................................
List of Examples 1-1 1-2 4-1 5-1 7-1 7-2 7-3 A-1 10 Unique IDs for an nPartition and Complex..................................................................................48 Unique IDs for Virtual Partitions (vPars)......................................................................................48 Overview of a Service Processor Login Session............................................................................75 Single-User HP-UX Boot.........................................................
About This Document This book describes nPartition system administration procedures, concepts, and principles for the HP servers that support nPartitions. New and Changed Information in This Edition This edition includes changes and additions related to the Superdome SX1000 PA and SX2000 PA. Document Organization This book contains the following chapters and appendix. Chapter 1.
Typographic Conventions This document uses the following typographical conventions: 12 audit(5) A manpage. The manpage name is audit, and it is located in Section 5. Command A command name or qualified command phrase. Computer output Text displayed by the computer. Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.
Related Information You can find information on nPartition server hardware management, operating system administration, and diagnostic support tools in the following publications and Web sites. Web Site for HP Technical Documentation: http://docs.hp.com The HP Technical Documentation Web site is at http://docs.hp.com and has complete information available for free. Server Hardware Information: http://docs.hp.com/hpux/hw/ The systems hardware portion of the docs.hp.com Web site is at http://docs.hp.
1 Getting Started with nPartitions This chapter introduces cell-based HP server features, server models, supported operating systems, and administration tools, and outlines the basic information needed for managing nPartitions. Introduction to nPartitions Cell-based HP servers enable you to configure a single server complex as one large system or as multiple smaller systems by configuring nPartitions.
Table 1-1 nPartition Operating System Support (continued) Operating System Supported Cell-Based Servers HP-UX 11i v3 (B.11.31) HP-UX 11i v3 (B.11.31) is supported on HP Integrity servers and HP 9000 servers. HP-UX 11i v3 is supported on all servers based on the HP sx1000 chipset, and on HP Integrity servers based on the HP sx2000 chipset. HP-UX 11i v3 supports cell local memory. Also see “nPartition Hardware Requirements for Operating Systems” (page 61). HP OpenVMS I64 8.2-1 and 8.3 OpenVMS I64 8.
Table 1-2 HP Servers Supporting nPartitions HP 9000 Servers HP The first-generation cell-based HP 9000 servers include the following models: 9000 servers have • HP 9000 Superdome servers, including the SD16000, SD32000, and SD64000 models. PA-RISC processors. These models support up to 16 cells in a server complex. • HP 9000 rp8400 model, which supports up to four cells in a server complex. • HP 9000 rp7405/rp7410, which supports up to two cells in a server complex.
NOTE: Specific firmware, operating systems, and management tools are required to supported mixing PA-RISC nPartitions and Intel® Itanium® 2 nPartitions on Superdome hybrid servers. For details, refer to HP Superdome Hybrid Servers, which is available from the http://docs.hp.com/ en/hw.html Web site under the HP 9000 Superdome Server and HP Integrity Superdome Server links.
For service processor commands, see “Command Reference for Service Processor Commands” (page 80). • EFI Boot Manager and EFI Shell Commands On cell-based HP Integrity servers, the Extensible Firmware Interface (EFI) supports nPartition management. The EFI is accessible from an nPartition console when the nPartition is in an active state but has not booted an operating system. See “Command Reference for EFI Shell Commands” (page 81) for details.
Remote management using the commands is supported as described in “Specifying Remote Management Options to Commands” (page 247). Table 1-3 nPartition Commands Releases Original nPartition Commands Enhanced nPartition Commands • Support only local management of nPartitions and complexes. • Were distributed with HP-UX 11i v1 (B.11.11) releases prior to the December 2004 release. • Supported by HP-UX kernels built with nPartition support enabled (the hd_fabric driver) and use the libfab.1 library.
Availability of nPartition Commands The Original nPartition Commands were distributed as part of HP-UX 11i v1 (B.11.11) releases prior to the December 2004 release. The Enhanced nPartition Commands are distributed with current HP-UX releases, including the HP-UX 11i v3 (B.11.31) release, all releases of HP-UX 11i v2 (B.11.23), and releases of HP-UX 11i v1 (B.11.11) beginning with the December 2004 release.
6. To download the Enhanced nPartition Commands for Windows, choose download from the Web page. Enhanced nPartition Commands for Linux The HP Integrity Essentials Foundation Pack for Linux is a CD that includes Enhanced nPartition Commands for use with Red Hat Enterprise Linux or SuSE Linux Enterprise Server. Procedure 1-2 Downloading the HP Integrity Essentials Foundation Pack for Linux You can download the HP Integrity Essentials Foundation Pack for Linux from the http:// www.hp.
Partition Manager Version 2.0 for Windows The Partition Manager Version 2.0 for Windows can be installed and run on either 32-bit or 64-bit Windows systems. (A single Partition Manager bundle is provided for both 32-bit and 64-bit systems.) • • Using Partition Manager for Windows on any 32-bit system running Windows XP, Windows 2000 with Service Pack 3, or Windows 2003, 32-bit Edition enables you to use a 32-bit system as a remote management station for nPartition administration.
• • • • • • “Base Cells” “Core Cells” “Active and Inactive Cells” “Cell Local Memory” “Cell Property Details” “Active and Inactive nPartition Boot States” Partition Numbers Each nPartition has its own unique partition number that the nPartition administration tools use for identifying the nPartition. When you create an nPartition, the tool you use assigns the nPartition the lowest available partition number.
as the active core cell, or if no core cell choices are specified, the nPartition attempts to select an eligible cell using a default process. Active and Inactive Cells Cells that are assigned to an nPartition and have booted to form an nPartition are active cells whose resources (processors, memory, and any attached I/O) can be actively used by software running in the nPartition.
The parstatus -V -c# command gives detailed information about the properties and status for the cell (-c#) that you specify.
Active and Inactive nPartition Boot States Each nPartition has a boot state of either active or inactive. The boot state indicates whether the nPartition has booted so that it may be interactively accessed through its console (active nPartitions) or if it cannot be used interactively (inactive nPartitions) You can use the parstatus -P command or Partition Manager to list all nPartitions and their boot states (active or inactive status).
For details see Chapter 8 (page 223). • Service processor (MP or GSP) methods for listing hardware and nPartition status include the following commands, which are available from the service processor Command menu. — CP — List nPartition configurations, including all assigned cells. — PS — List cabinet, power, cell, processor, memory, I/O, and other details. — IO — List connections from cells to I/O chassis on HP Superdome servers. — ID — List product and serial numbers.
Basics of nPartition Creation Creating an nPartition involves using an nPartition administration tool to assign one or more cells in a complex to the new nPartition. At the time an nPartition is created you also can optionally specify various configuration options for the nPartition, such as its name, cell use-on-next-boot values, and other details. After an nPartition is created you can modify the nPartition, as described in “Basics of nPartition Modification” (page 30).
example, by the -u... -h... set of options). For remote administration using IPMI over LAN the tool remotely accesses the service processor of the target complex (for example, by the -g... -h... set of options). For remote administration details see “Remote and Local Management of nPartitions” (page 41). For detailed procedures for creating and managing nPartitions see Chapter 6 (page 165).
— For remote administration using WBEM the tool remotely accesses an operating system running on an nPartition in the target complex. Use the -u... -h... set of parmodify options or the Partition Manager Switch Complexes action and "remote nPartition" option. — For remote administration using IPMI over LAN the tool remotely accesses the service processor of the target complex. Use the -g... -h...
• Setting Core Cell Choices To set core cell choices for an nPartition use the parmodify -p# -r# -r#... command to specify up to four core cell choices in priority order for a specified nPartition (-p#, where # is the partition number). From Partition Manager Version 1.0 select the nPartition, use the nPartition→Modify nPartition action, Core Cell Choices tab. From Partition Manager Version 2.
c. 2. discovery, and discovery of interconnecting fabric (connections between the cell and other cells, I/O, and system crossbars). After the firmware completes cell self-tests and discovery, it reports the cell hardware configuration to the service processor (GSP or MP), informs the service processor it is "waiting at BIB", and then waits for the cell BIB flag to be cleared.
— — TC — Perform a transfer of control reset of an nPartition. PE — Power on or power off a cabinet, cell, or I/O chassis. On HP Integrity rx8620 servers, rx8640 servers, rx7620 servers, and rx7640 servers, nPartition power on and power off also is supported to manage power of all cells and I/O chassis assigned to the nPartition using a single command. • EFI Shell support for managing nPartition booting includes the following commands. (EFI is available only on HP Integrity servers.
• HP-UX includes the following commands for shutting down and rebooting the nPartition. — shutdown -r — Shuts down HP-UX and resets the local nPartition, resetting cells and then proceeding with the nPartition boot phase. On HP 9000 servers shutdown -r resets only the active cells. On HP Integrity servers shutdown -r has the same effect as shutdown -R. All cells are reset and nPartition reconfiguration occurs as needed.
• Microsoft® Windows® includes the following commands for shutting down and rebooting the nPartition. — shutdown /r — Shuts down Windows and performs a reboot for reconfig of the nPartition. All cells are reset and nPartition reconfiguration occurs as needed. The nPartition then proceeds with the nPartition boot phase. — shutdown /s — Shuts down Windows and performs a shutdown for reconfig of the nPartition.
The Complex Profile consists of three parts, or groups of data, which are described in detail in Table 1-5 (page 40): • “Stable Complex Configuration Data” (page 40) — This group contains complex-wide settings, including the complex name, serial number, the nPartition assignment for each cell, and other details that apply to the entire server complex. The Complex Profile contains one Stable Complex Configuration Data entry.
5. 6. The tool sends the revised Complex Profile entry back to the service processor along with the corresponding lock key. The service processor then "pushes out" the new, revised Complex Profile entry by updating its copy and updating all cells that have a copy of the entry. However, the service processor will not push out a revised Complex Profile entry that affects the nPartition assignment of an active cell.
the entries. After they are unlocked you can perform the modifications you had previously attempted. For details see “Unlocking Complex Profile Entries” (page 198). Aborting a Complex Profile Change A pending update of the Complex Profile can be canceled or prevented by clearing the lock for a Complex Profile entry before the service processor has pushed out the revised data for the entry.
NOTE: The Complex Profiles on cell-based HP 9000 servers and cell-based HP Integrity servers contain slightly different sets of information. Table 1-5 covers both types of Complex Profiles. The Complex Profile on cell-based HP Integrity servers includes all HP 9000 server Complex Profile data and additional components that are specific to HP Integrity servers. Some HP 9000 server Complex Profile data is unused on HP Integrity servers but is included for compatibility.
Table 1-5 Complex Profile Group Details (continued) Complex Profile Group Description and Contents The Partition Configuration Data contains configuration details specific to each nPartition in the complex. Each nPartition has its own Partition Configuration Data entry, which may be modified by administrators. The service processor (MP or GSP) has a copy of the Partition Configuration Data for every nPartition.
The service processor in all sx1000-based or sx2000-based servers supports two of the communication paths defined by the IPMI standard: the Block Transfer path and IPMI over LAN. Some background details about each of these communication paths is provided in the next sections. How and when these paths are used is covered in the explanations of the local and remote management scenarios that follow.
The service processor will accept IPMI requests over its LAN port only if the request is accompanied by the correct password. To set the IPMI password use the SO command at the service processor Command menu. Communication using IPMI over LAN is authenticated using the challenge and response protocol defined by the IPMI specification. The MD5 message digest algorithm (RFC1321) is used to encrypt the IPMI password and to ensure authentication of both the server and the client.
tools in the mode that uses IPMI over LAN (see “Remote Management Using IPMI over LAN” (page 46)). Local management is the only form of management supported by the older nPartition tools (the Original nPartition Commands and Partition Manager Version 1.0).
On a Windows system, the SSL Certificate file is in the location specified by the %PEGASUS_HOME%\cimcerver_current.conf file; in this file the sslCertificateFilePath entry specifies the SSL Certificate file location. • client.pem — WBEM Trust Certificate Store file The Trust Certificate Store file resides on the system from which WBEM remote management commands are issued. On HP-UX B.11.23 systems, the Trust Certificate Store file is the /var/opt/wbem/client.pem file.
Figure 1-1 Partition Manager Version 2.0 Switch Complexes Dialog Remote Management Using IPMI over LAN IPMI over LAN enables the second form of remote management of an nPartition complex: using nPartition management tools that are running on a system to communicate directly (without going through an nPartition) with the service processor in the complex to be managed.
Partition Manager Support for Remote Management Using IPMI over LAN Partition Manager Version 2.0 can be used in this mode in either of two ways: • • Run Partition Manager on an nPartition and then select the Switch Complexes task from the Tools menu. In the resulting dialog enter the hostname or IP address of the service processor in the target complex, and supply that service processor's IPMI password. Run Partition Manager on a system that is not an nPartition.
Refer to the confstr(3C) manpage for details on these parameters and their use. Example 1-1 Unique IDs for an nPartition and Complex The following examples show nPartition-unique and complex-unique IDs returned by the getconf command, as well as the local nPartition number and machine serial number. # parstatus -w The local partition number is 1.
2 nPartition Server Hardware Overview This chapter describes the cell-based HP server models, including system capacities, model strings, and differences among the cell-based server models. Both HP 9000 servers and HP Integrity servers are discussed here. • The HP 9000 series of servers has HP PA-RISC processors. The cell-based HP 9000 servers include three generations of servers: the first-generation models, models based on the HP sx1000 chipset, and models based on the HP sx2000 chipset.
A summary of the supported cell-based servers and their corresponding model identifiers appears in “Server Hardware Details: Cell-Based HP Servers” (page 51). You can report the machine hardware model for the local server complex using the following methods: • From HP-UX 11i use either the /usr/bin/model command or the /usr/bin/getconf MACHINE_MODEL command. • From the Windows command line, use the systeminfo command to report system details including the system model.
Server Hardware Details: Cell-Based HP Servers Table 2-1 lists the cell-based HP servers. For individual server details see the sections that follow. Table 2-1 Models of Cell-Based HP Servers Cell Capacity Server Model(s) Two-Cell Servers HP 9000 rp7405/7410 server Up to eight PA-RISC processor cores. See “Two-Cell nPartition Server Model” (page 55). Description Runs HP-UX B.11.11. Also runs the HP-UX B.11.23 September 2004 release and later. Runs HP-UX B.11.31.
Table 2-1 Models of Cell-Based HP Servers (continued) Cell Capacity Server Model(s) Description Four-Cell Servers HP 9000 rp8400 server Up to 16 PA-RISC processors. See “Four-Cell nPartition Server Model” (page 56). Runs HP-UX B.11.11. Also runs the HP-UX B.11.23 September 2004 release and later. Runs HP-UX B.11.31. model string: 9000/800/S16K-A HP 9000 rp8420 server Up to 16 dual-core PA-RISC processors (32 processor cores total). Uses the HP sx1000 chipset. Runs HP-UX B.11.11.
Table 2-1 Models of Cell-Based HP Servers (continued) Cell Capacity Server Model(s) HP 9000 Superdome Servers HP 9000 Superdome Up to 64 PA-RISC processors. SD16000, SD32000, SD64000 Runs HP-UX B.11.11. Also runs the HP-UX B.11.23 servers September 2004 release and later. Runs HP-UX B.11.31. See “Superdome Server Models” (page 57).
Table 2-1 Models of Cell-Based HP Servers (continued) Cell Capacity Server Model(s) Description HP Integrity Superdome Servers HP Integrity Superdome SD16A, SD32A, SD64A servers Up to 64 processor sockets, four per cell, with each cell having either single Intel® Itanium® 2 processors or HP mx2 dual-processor modules with Itanium 2 processors. (Up to 128 processor cores total when using HP mx2 modules.) See “Superdome Server Models” (page 57). Runs HP-UX B.11.23, HP-UX B.11.
Two-Cell nPartition Server Model The following cell-based HP servers scale from one to two cells: • The HP rp7405/rp7410 server has single-core HP PA-RISC processors. The model string is: 9000/800/rp7410. • The HP rp7420 server has dual-core HP PA-RISC processors: PA-8800 processors, which provide two processor cores per processor socket. The model string is: 9000/800/rp7420.
NOTE: On the first-generation and HP sx1000-based two-cell servers, two PCI slots by convention are dedicated for use by a combination LAN/SCSI card: PCI domain 0 slot 1 (the first slot on the left) and PCI domain 1 slot 8 (the last slot on the right). On two-cell servers based on the HP sx2000 chipset, core I/O is provided in each cell. • A total server complex capacity of: 2 cells, 8 processor sockets, 32 DIMMs, and 16 PCI card slots.
The four-cell HP servers include these features: • A single server cabinet that includes cells, I/O chassis, processors, memory, PCI cards, and core I/O. Two PCI I/O chassis in the server cabinet share the same chassis hardware. One I/O chassis is connected to cell 0, the other is connected to cell 1. Each I/O chassis has 8 PCI card slots, numbered from 1 to 8.
The HP Superdome server models include: • • • “HP Superdome 16-/32-Way Servers: SD16000, SD16A, and SD16B” (page 58) “HP Superdome 32-/64-Way Servers: SD32000, SD32A, and SD32B” (page 58) “HP Superdome 64-/128-Way Servers: SD64000, SD64A, and SD64B” (page 59) Details on these models are given in the following sections.
• The HP Integrity Superdome SD32A server has Intel® Itanium® 2 processors, either single-processor modules or HP mx2 dual-processor modules. Both HP mx2 dual-processor modules and single Itanium 2 processors can exist in the same complex, but they cannot be mixed in the same nPartition. The model command output for the HP Integrity SD32A server is: ia64 hp superdome server SD32A • The HP Integrity Superdome SD32B server has single-core or dual-core Intel® Itanium® 2 processors.
A Superdome I/O expansion cabinet includes up to 3 I/O bays, with two 12-slot I/O chassis in each bay. This provides for up to 6 chassis with a total of 72 PCI card slots in each I/O expansion cabinet. The Superdome I/O expansion cabinet is a standard-size cabinet that, space permitting, you can mount peripherals in as well as I/O chassis. Also refer to the book I/O Expansion Cabinet Guide for Superdome Servers.
3 Planning nPartitions This chapter describes how you can plan nPartition configurations. Details include the nPartition configuration requirements and recommendations. For procedures to create and configure nPartitions, see Chapter 6 (page 165). nPartition Hardware Requirements for Operating Systems Table 3-1 lists the hardware requirements for operating systems running on nPartitions. Table 3-1 Operating System Hardware Requirements Operating System nPartition Hardware Requirements HP-UX B.11.
Table 3-1 Operating System Hardware Requirements (continued) Operating System nPartition Hardware Requirements Red Hat Enterprise Linux 4 Update 4 Supports up to eight Intel® Itanium® 2 processors. On servers based on the HP sx2000 chipset, supported only in nPartitions that have dual-core Intel® Itanium® 2 processors. Supports a maximum of two cells in an nPartition. Supports a maximum of 128 GBytes memory. Supports a maximum of two I/O chassis in an nPartition.
• On HP Integrity servers, all cells assigned to an nPartition must have either mx2 dual-processor modules or single Itanium 2 processors. Both HP mx2 dual-processor modules and single Itanium 2 processors can exist in the same complex, but they cannot be mixed in the same nPartition. • • The same firmware revision must be present on all cells within an nPartition. At least one cell in every nPartition must be connected to an I/O chassis that has core I/O. Only one core I/O is active per nPartition.
• The memory configuration of each cell should include a multiple of two memory ranks (first-generation cell-based HP 9000 servers) or a multiple of two memory echelons (servers based on the HP sx1000 chipset or HP sx2000 chipset) per cell. On the first generation of cell-based HP 9000 servers, each memory rank is 4 DIMMs. If possible, install memory in sets of 8 DIMMs: 8 DIMMs or 16 DIMMs on HP rp7405/rp7410, rp8400, and Superdome (SD16000, SD32000, SD64000) cells.
• Define nPartitions in order of size. Assign cells to the nPartition that has the largest cell count first. Then select cells for the next largest nPartition, and so on, and finally choose cells for the nPartition with the fewest cells last. This provides more appropriate cell assignments for larger nPartitions (those with more cells). Any smaller nPartitions with fewer cells are more easily accommodated in the remaining, available cells. • Place each nPartition within an empty cabinet, if possible.
4 Using Management Interfaces and Tools This chapter presents the system management interfaces and tools available on Hewlett-Packard's cell-based servers. Also covered here are the nPartition boot environments, management access procedures, and detailed command references. Management differences on HP 9000 systems and HP Integrity systems are addressed in this chapter. For a discussion of the supported cell-based server models, see Chapter 2 (page 49).
Multiple users can independently interact with the service processor because each service processor login session is private. However, some output is mirrored: the Command menu and each nPartition console permit one interactive user at a time and mirror output to all users accessing those features. Likewise, the service processor mirrors live chassis codes to all users accessing the Live Chassis Logs feature (or the Live Events feature).
Each nPartition console provides access to: — The nPartition system boot environment: either BCH or EFI. The BCH or EFI system boot environment is available when the nPartition is active but has not yet loaded or booted an operating system. ◦ ◦ — The Boot Console Handler (BCH) environment is provided on HP 9000 servers only (PA-RISC servers). The Extensible Firmware Interface (EFI) is provided on HP Integrity servers only (Intel® Itanium®-based servers). HP-UX console for the nPartition.
Service processor user accounts have a specific login name, password, and access level. The three user account access levels are: • Administrator Account Provides access to all commands, and access to all nPartition consoles and Virtual Front Panels. Can manage user accounts (using the Command menu SO command) and can reconfigure various service processor settings. • Operator Account Provides access to a subset of commands, and access to all nPartition consoles and Virtual Front Panels.
Each nPartition console can display a variety of information about the nPartition, including: • • Partition startup, shutdown, and reset output. The system boot environment: either Boot Console Handler (BCH, on HP 9000 servers) or Extensible Firmware Interface (EFI, on HP Integrity servers). The system boot environment is available when the nPartition has not yet booted an operating system and has completed Power-On Self Tests (POST) and completed nPartition rendezvous to become active.
Once you begin the HP-UX boot process and load ISL, the BCH interface is no longer available. The BCH menus and commands for nPartitions differ slightly from the commands menus for BCH on other HP 9000 server systems. To display the current BCH menu and commands, type DI. The BCH interface HELP command lists BCH command or menu details.
The Special Administration Console (SAC) interface lets you interact with the Windows operating system running on an nPartition by using the SAC> command prompt that is provided at the nPartition console interface. The SAC commands listed in Table 4-1 (page 73) are provided for managing Windows. The SAC interface enables you to have administrative access to Windows on an nPartition even if Windows networking is not functional. Tips for using the SAC interface and a table of SAC commands follow.
Table 4-1 Windows SAC Commands (continued) SAC Command Description id Display the Windows nPartition identification information. k pid Kill the given process. l pid Lower the priority of a process to the lowest possible. lock Lock access to Command Prompt channels. m pid MB-allow Limit the memory usage of a process to MB-allow. p Toggle paging the display. r pid Raise the priority of a process by one. s Display the current time and date (24 hour clock used).
Example 4-1 Overview of a Service Processor Login Session The following output shows a sample login session for a server whose service processor hostname is "hpsys-s". > telnet hpsys-s Trying... Connected to hpsys-s.rsn.hp.com. Escape character is '^]'. Local flow control off MP login: Username MP password: Welcome to the S Class 16K-A Management Processor (c) Copyright 1995-2001 Hewlett-Packard Co., All Rights Reserved. Version 0.
3. Use the service processor menus and commands as needed and log out when done. To log out, select the Exit Connection menu item from the Main menu (enter X at the GSP> prompt or MP> prompt). You also can terminate a login session by issuing the telnet escape key sequence ^] (type: Control-right bracket) and entering close at the telnet> prompt. NOTE: If possible, you should log out of any consoles and menus before terminating your telnet session.
You can do this throughout the service processor menus, including the console menus, various command menu prompts, and the log and VFP menus. Note that, from the Command menu prompt (GSP:CM> or MP:CM>) you must enter MA (not Q) to return to the Main menu. However, you can enter Q or q to cancel any command. • Control-] Escape the service processor connection and return to the telnet prompt.
When you enter a console log viewer it displays the oldest data in the log first and allows you to page through the log to view the more recently recorded activity. Each console log is a circular log file that records approximately 30 to 40 pages of data. All nPartition console activity is written to this log file, regardless of whether a user is connected to the nPartition console.
A)lert filter C)ell filter P)artition filter U)nfiltered V)iew format selection ^B to Quit Current filter: ALERTS only Log Viewing Options: Activity, Error, and Live Chassis Logs When you enter the chassis log viewer by entering SL at the service processor (MP or GSP) Main menu, you can select from these viewers: • Activity Log Viewer Allows you to browse recorded event logs of alert level 0 or 1.
Command Reference for Service Processor Commands Table 4-2 lists the commands available from the service processor command menu (the MP:CM> or GSP:CM> prompt). The following categories of commands are available: • “Service Commands — Service Processor (MP or GSP)”. • “Status Commands — Service Processor (MP or GSP)”. • “System and Access Configuration Commands — Service Processor (MP or GSP)”. Some commands are restricted to users with Operator or Administrator authority.
Table 4-2 Service Processor (MP or GSP) Command Reference (continued) Command Description PARPERM Restrict/unrestrict nPartition Reconfiguration Privilege. PD Modify default nPartition for this login session. RL Rekey Complex Profile locks (unlock Complex Profile). SA Display and set (enable/disable) MP remote access methods. SO Configure security options and access control (user accounts and passwords). XD MP diagnostics and reset.
Table 4-3 EFI Shell Command Reference (continued) Command Description dimmconfig Deconfigure/reconfigure memory (DIMMs). err Display/change the error level. errdump View/clear logs. fru View FRU data. info Display hardware information. monarch Set/view a monarch processor. palproc Make a PAL call. romdrivers Enable/disable PCI expansion ROM drivers. rootcell Set/view preferred root cells. (Set nPartition core cell choices.) salproc Make a SAL call.
Table 4-3 EFI Shell Command Reference (continued) Command Description cd Update/view the current directory. comp Compare the contents of two files. cp Copy one or more files/directories to another location. edit Edit an ASCII or UNICODE file in full screen. eficompress Compress infile and write to outfile. efidecompress Decompress infile and write to outfile. hexedit Edit a file, block device, or memory region using hex. ls Display a list of files and subdirectories in a directory.
Table 4-3 EFI Shell Command Reference (continued) Command Description endif Script-only: Delimiter for IF THEN construct. for Script-only: Loop construct. goto Script-only: Jump to label location in script. if Script-only: IF THEN construct. input Take user input and place in EFI variable. pause Script-only: Prompt to quit or continue. stall Stall the processor for some microseconds.
Table 4-4 Boot Console Handler (BCH) Command Reference (continued) Command Description ScRoll [ON|OFF] Display or change scrolling capability. COnfiguration Access the Configuration Menu, which displays or sets boot values. INformation Access the information menu, which displays hardware information. SERvice Access the Service Menu, which displays service commands. Configuration Menu Commands — Boot Console Handler (BCH) Commands to display or set boot values. MAin Return to the BCH Main Menu.
Table 4-4 Boot Console Handler (BCH) Command Reference (continued) Command Description IO [cell] Display I/O interface information. MEmory [cell] Display memory information. PRocessor [cell] Display processor information Service Menu Commands — Boot Console Handler (BCH) Commands related to nPartition system service tasks. MAin Return to the BCH Main Menu. BAttery [cell] Display cell battery status.
5 Booting and Resetting nPartitions This chapter introduces nPartition system boot and reset concepts, configuration options, and procedures for booting and resetting nPartitions. This chapter covers boot details for HP-UX, HP OpenVMS I64, Microsoft® Windows® Server 2003, Red Hat Enterprise Linux, and the SuSE Linux Enterprise Server operating systems. Differences in the nPartition boot process on PA-RISC systems and Intel® Itanium®-based systems also are addressed in this chapter.
a. b. EFI Shell (command-driven boot environment) EFI Scripts and Applications EFI scripts and EFI applications can be initiated from either EFI Boot Manager or EFI Shell. 5. Operating System Loader The following OS loaders are supported on HP Integrity servers. OS loaders can be initiated from the EFI Boot Manger or the EFI Shell. a. HPUX.EFI Loader Loader for the HP-UX operating system. b. ELILO.EFI Loader Loader for Red Hat Enterprise Linux or SuSE Linux Enterprise Server. c. vms_loader.
HP 9000 Server Booting This list describes system boot features on cell-based HP 9000 servers. • The nPartition system boot environment is the Boot Console Handler (BCH). • The autoboot process is configured using boot device paths (PRI, HAA, ALT) and path flags. — PRI boot path: configured using the setboot -p... or parmodify -b... command. — HAA boot path: configured using the setboot -h... or parmodify -s... command — ALT boot path: configured using the setboot -a... or parmodify -t... command.
NOTE: On HP Integrity servers you should reset an nPartition only after all self tests and partition rendezvous have completed. For example, when the nPartition is inactive (all cells are at BIB) or is at EFI. • Boot an nPartition from the Service Processor (GSP or MP) A boot initiated from the service processor boots an inactive nPartition past the shutdown for reconfig state to allow it to become active. To boot an inactive nPartition, use the BO command from the service processor Command menu.
— • its cells to boot past BIB, rendezvous, and boot to the system boot environment (BCH or EFI) and, if configured, automatically boot an operating system. For an nPartition whose cells have been powered off, use the PE command to power on the nPartition hardware. TOC: Transfer-of-Control Reset When you initiate a transfer-of-control reset, the service processor immediately performs a TOC reset of the specified nPartition, which resets the nPartition and allows a crash dump to be saved.
NOTE: In some versions of EFI, the Boot Configuration menu is listed as the Boot Option Maintenance menu. To manage the boot options list for each system use the EFI Shell, the EFI Boot Configuration menu, or operating system utilities. At the EFI Shell, the bcfg command supports listing and managing the boot options list for all operating systems except Microsoft Windows. On HP Integrity systems with Windows installed the \MSUtil\nvrboot.
The ACPI configuration settings for the supported OSes are in the following list. — HP-UX ACPI Configuration: default On cell-based HP Integrity servers, to boot or install the HP-UX OS, you must set the ACPI configuration value for the nPartition to default. For details refer to “ACPI Configuration for HP-UX Must Be default” (page 110).
powered off when the OS issues a shutdown for reconfig command (for example, shutdown -h or shutdown /s). This is the normal behavior on HP rx7620, rx7640, rx8620, and rx8640 servers with a windows ACPI configuration setting. When softpowerdown is enabled on HP rx7620, rx7640, rx8620, and rx8640 servers, if one nPartition is defined in the server, then halting the OS powers off the server cabinet including all cells and I/O chassis.
— parconfig EFI shell command The parconfig command is a built-in EFI shell command. Refer to the help parconfig command for details. — \EFI\HPUX\vparconfig EFI shell command The vparconfig command is delivered in the \EFI\HPUX directory on the EFI system partition of the disk where HP-UX virtual partitions has been installed on a cell-based HP Integrity server. For usage details, enter the vparconfig command with no options.
Task Summaries for nPartition Boot and Reset Table 5-1 describes the main nPartition boot and reset tasks and provides brief summaries and references for detailed procedures.
Table 5-1 nPartition Boot and Reset Task Summaries (continued) Task Summary “Shutting Down HP OpenVMS” • NOTE: Only supported on HP Integrity servers. • At the OpenVMS command line issue the @SYS$SYSTEM:SHUTDOWN command and specify the shutdown options in response to the prompts given. See “Shutting Down HP OpenVMS” (page 123). “Booting Microsoft Windows” • NOTE: Only supported on HP Integrity servers. • EFI Boot Manager: select an item from the boot options list.
Table 5-1 nPartition Boot and Reset Task Summaries (continued) Task Summary “Rebooting and Resetting • Service Processor (MP or GSP): RS command; under normal operation you first shut nPartitions” down the operating system. On HP Integrity servers you should reset an nPartition only after all self tests and partition rendezvous have completed. • • • • • BCH Menu: REBOOT command. EFI Boot Manager: Boot Option Maintenance→Cold Reset. EFI Shell: reset command.
Table 5-1 nPartition Boot and Reset Task Summaries (continued) Task Summary “Booting to the HP-UX Initial System Loader (ISL)” • NOTE: Only supported on PA-RISC systems. • BCH Menu: issue the BOOT command and reply y (for "yes") to the Do you wish to stop at the ISL prompt question. See “Booting to the HP-UX Initial System Loader (ISL)” (page 149). “Booting to the HP-UX Loader (HPUX.EFI)” • NOTE: Only supported on HP Integrity servers.
Table 5-1 nPartition Boot and Reset Task Summaries (continued) Task Summary “Configuring Autoboot Options” • BCH Menu: the PATHFLAGS command from the BCH Configuration menu sets boot-time actions for an nPartition.
Use the help acpiconfig command for more details. • Problem: Not all cells boot to join (rendezvous) an nPartition. Causes: Some cells may have the use-on-next-boot value set to "n" (do not use), or the cells may have been powered off, or the cells may have booted too late to participate in partition rendezvous, or the cells have failed self-tests and cannot be used, or the cells are incompatible.
NOTE: Always login to the service processor from a tty (not console) login session. You can check your current login terminal using the who -m command. Do not login to a service processor from an nPartition console connection. Any use of the ^b (Control-b) console exit sequence would exit the original console login—not the subsequent console-based login to the service processor—thus potentially stranding the console-based login (for example, if it too were accessing a console).
[A few lines of context from the console log:] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SERvice menu Displays service commands DIsplay HElp [
4. Gain interactive access to the nPartition console. Press Enter to access the prompt currently available from the nPartition console, if any. You will have either interactive or non-interactive access, as described in the sections “Interactive Console Access” and “Non-Interactive Console Access” in this step. To exit the nPartition console and return to the service processor Main Menu, type ^b (Control-b) at any time.
Procedure 5-2 Monitoring Boot Activity (Service Processor) Use the VFP option from the service processor Main Menu to access an nPartition Virtual Front Panel for monitoring the nPartition boot status. 1. 2. Login to the service processor (MP or GSP). From the Main Menu, enter VFP to select the Virtual Front Panel option.
Finding Bootable Devices You can find bootable devices by using any one of the following procedures: • • “Finding Bootable Devices (BCH Menu)” (page 106) “Finding Bootable Devices (EFI Shell)” (page 107) Procedure 5-3 Finding Bootable Devices (BCH Menu) From the BCH Main Menu, issue the SEARCH command to find bootable devices. The BCH Menu is available only on HP 9000 systems. 1. Access the BCH Main Menu for the nPartition whose bootable devices you want to list.
3. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Procedure 5-4 Finding Bootable Devices (EFI Shell) From the EFI Shell environment, issue the map command to list bootable devices. The EFI Shell is available only on HP Integrity systems. 1.
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. GSP:CM> 3. After you initiate the TOC, you can observe its progress and select the type of crash dump through the nPartition console. Once the nPartition completes the dump, or once you cancel it, the nPartition reboots. ******* Unexpected TOC.
NOTE: HP-UX 11i Version 1 (B.11.11) does not support using CLM. Before booting HP-UX 11i Version 1 on an nPartition, you must ensure that the CLM parameter for each cell in the nPartition is set to zero (0). Although you might be able to boot HP-UX 11i Version 1 on an nPartition with CLM configured, any memory configured as cell local is unusable, and such a configuration is untested and unsupported. HP-UX 11i Version 2 (B.11.23) and HP-UX 11i Version 3 (B.11.31) support using CLM.
3. At the EFI Shell environment, use the bcfg command to manage the boot options list. The bcfg command includes the following options for managing the boot options list: • • • • bcfg boot dump — Display all items in the boot options list for the system. bcfg boot rm # — Remove the item number specified by # from the boot options list. bcfg boot mv #a #b — Move the item number specified by #a to the position specified by #b in the boot options list. bcfg boot add # file.
Procedure 5-7 HP-UX Booting (BCH Menu) From the BCH Menu, use the BOOT command to boot the HP-UX OS. The BCH Menu is available only on HP 9000 servers. 1. Access the BCH Main Menu for the nPartition on which you want to boot HP-UX. Log in to the management processor (MP) and enter CO to access the Console list. Choose the nPartition console. When accessing the console, confirm that you are at the BCH Main Menu (the Main Menu: Enter command or menu> prompt).
Main Menu: Enter command or menu > BOOT PRI Primary Boot Path: 0/0/1/0/0.15 Do you wish to stop at the ISL prompt prior to booting? (y/n) >> n ISL booting hpux Boot : disk(0/0/1/0/0.15.0.0.0.0.0;0)/stand/vmunix To boot an HP-UX kernel other than /stand/vmunix, or to boot HP-UX in single-user or LVM-maintenance mode, stop at the ISL prompt and specify the appropriate arguments to the hpux loader. 4. Exit the console and management processor interfaces if you are finished using them.
1. Access the EFI Shell environment for the nPartition on which you want to boot HP-UX. Log in to the management processor (MP) and enter CO to access the Console list. Choose the nPartition console. When accessing the console, confirm that you are at the EFI Boot Manager menu (the main EFI menu). If you are at another EFI menu, choose the Exit option from the submenus until you return to the screen with the EFI Boot Manager heading.
HP-UX Boot Loader for IA64 Revision 1.723 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot 9 6. Exit the console and management processor interfaces if you are finished using them. To exit the EFI environment, press ^B (Control-B); this exits the nPartition console and returns to the management processor Main Menu. To exit the management processor, type X at the Main Menu.
To exit the ISL prompt and return to the BCH interface, issue the EXIT command instead of specifying one of the hpux loader commands. Refer to the hpux(1M) manpage for a detailed list of hpux loader options. Example 5-1 Single-User HP-UX Boot 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.0;0)/stand/vmunix 8241152 + 1736704 + 1402336 start 0x21a0e8 .... INIT: Overriding default level with level 's' INIT: SINGLE USER MODE INIT: Running /sbin/sh # 4.
fs0:\> hpux (c) Copyright 1990-2002, Hewlett Packard Company. All rights reserved HP-UX Boot Loader for IA64 Revision 1.723 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot 9 [User Types A Key to Stop the HP-UX Boot Process and Access the HPUX.EFI Loader ] Type 'help' for help HPUX> 5. At the HPUX.EFI interface (the HP-UX Boot Loader prompt, HPUX>) enter the boot -is vmunix command to boot HP-UX (the /stand/vmunix kernel) in single-user (-is) mode.
2. 3. Boot the desired device using the BOOT command at the BCH interface, and specify that the nPartition stop at the ISL prompt prior to booting (reply y to the "stop at the ISL prompt" question). From the ISL prompt, issue the appropriate Secondary System Loader (hpux) command to boot the HP-UX kernel in the desired mode. To boot HP-UX in LVM-maintenance mode: ISL> hpux -lm boot /stand/vmunix 4. Exit the console and management processor interfaces if you are finished using them.
• To shut down HP-UX and reboot an nPartition: shutdown -r On cell-based HP Integrity servers, the shutdown -r command is equivalent to the shutdown -R command. • To shut down HP-UX and halt an nPartition: shutdown -h On cell-based HP Integrity servers, the shutdown -h command is equivalent to the shutdown -R -H command.
2. Issue the shutdown command with the appropriate command-line options. The command-line options you specify dictate the way in which HP-UX is shut down, whether the nPartition is rebooted, and whether any nPartition configuration changes (adding or removing cells) take place. Use the following list to choose an HP-UX shutdown option for your nPartition: • Shut down HP-UX and halt the nPartition. On HP 9000 servers only, issue the shutdown -h command to shut down and halt the nPartition.
HP OpenVMS I64 Support for Cell Local Memory On servers based on the HP sx1000 chipset or HP sx2000 chipset, each cell has a cell local memory (CLM) parameter, which determines how firmware interleaves memory residing on the cell. NOTE: HP OpenVMS I64 does not support using CLM. Before booting OpenVMS on an nPartition, you must ensure that the CLM parameter for each cell in the nPartition is set to zero (0).
2. Access the EFI System Partition (fsX: where X is the file system number) for the device from which you want to boot HP OpenVMS. For example, enter fs2: to access the EFI System Partition for the bootable file system number 2. The EFI Shell prompt changes to reflect the file system currently accessed. The full path for the HP OpenVMS loader is \efi\vms\vms_loader.efi and it should be on the device you are accessing. 3. At the EFI Shell environment, use the bcfg command to manage the boot options list.
Booting HP OpenVMS To boot HP OpenVMS I64 on a cell-based HP Integrity server use either of the following procedures. • • “Booting HP OpenVMS (EFI Boot Manager)” (page 122) “Booting HP OpenVMS (EFI Shell)” (page 122) CAUTION: ACPI Configuration for HP OpenVMS I64 Must Be default On cell-based HP Integrity servers, to boot the HP OpenVMS OS an nPartition must have its ACPI configuration value set to default.
3. Access the EFI System Partition (fsX: where X is the file system number) for the device from which you want to boot HP OpenVMS. For example, enter fs2: to access the EFI System Partition for the bootable file system number 2. The EFI Shell prompt changes to reflect the file system currently accessed. Also, the file system number might change each time it is mapped (for example, when the system boots, or when the map -r command is issued). 4.
2. At the OpenVMS command line, issue the @SYS$SYSTEM:SHUTDOWN command and specify the shutdown options in response to the prompts given.
NOTE: Microsoft Windows supports using CLM on cell-based HP Integrity servers. For best performance in an nPartition running Windows, HP recommends that you configure the CLM parameter to 100% for each cell in the nPartition. To check CLM configuration details from an OS, use Partition Manager or the parstatus command.
2 Dir(s) fs0:\> 4. At the EFI Shell environment, issue the \MSUtil\nvrboot.efi command to launch the Microsoft Windows boot options utility. fs0:\> msutil\nvrboot NVRBOOT: OS Boot Options Maintenance Tool [Version 5.2.3683] 1. 2. * 3. 4. SUSE SLES 9 HP-UX Primary Boot: 0/0/1/0/0.2.0 Windows Server 2003, Datacenter EFI Shell [Built-in] * = Windows OS boot option (D)isplay (M)odify (C)opy E(x)port (I)mport (E)rase (P)ush (H)elp (Q)uit Select> 5.
Refer to “Shutting Down Microsoft Windows” (page 128) for details on shutting down the Windows OS. CAUTION: ACPI Configuration for Windows Must Be windows On cell-based HP Integrity servers, to boot the Windows OS an nPartition must have its ACPI configuration value set to windows. At the EFI Shell, enter the acpiconfig command with no arguments to list the current ACPI configuration.
5. Exit the console and management processor interfaces if you are finished using them. To exit the console environment, press ^B (Control-B); this exits the console and returns to the management processor Main menu. To exit the management processor, type X at the Main menu. Shutting Down Microsoft Windows You can shut down the Windows OS on HP Integrity servers using the Start menu or the shutdown command.
1. Log in to Windows running on the system that you want to shut down. For example, access the system console and use the Windows SAC interface to start a command prompt, from which you can issue Windows commands to shut down the the system. 2. Check whether any users are logged in. Use the query user or query session command. 3. Issue the shutdown command and the appropriate options to shut down the Windows Server 2003 on the system.
NOTE: Red Hat Enterprise Linux does not support using CLM. Before booting Red Hat Enterprise Linux on an nPartition, you must ensure that the CLM parameter for each cell in the nPartition is set to zero (0). Although you might be able to boot Red Hat Enterprise Linux on an nPartition with CLM configured, any memory configured as cell local is unusable, and such a configuration is untested and unsupported. SuSE Linux Enterprise Server supports using CLM.
3. At the EFI Shell environment, use the bcfg command to manage the boot options list. The bcfg command includes the following options for managing the boot options list: • • • • bcfg boot dump — Display all items in the boot options list for the system. bcfg boot rm # — Remove the item number specified by # from the boot options list. bcfg boot mv #a #b — Move the item number specified by #a to the position specified by #b in the boot options list. bcfg boot add # file.
Choosing a Linux entry from the boot options list boots the OS using ELILO.EFI loader and the elilo.conf file. • Initiate the ELILO.EFI Linux loader from the EFI Shell. Refer to the procedure “Booting Red Hat Enterprise Linux (EFI Shell)” (page 132) for details. On a Red Hat Enterprise Linux boot device EFI System Partition, the full paths to the loader and configuration files are: \EFI\redhat\elilo.efi \EFI\redhat\elilo.
Refer to “Shutting Down Linux” (page 134) for details on shutting down the SuSE Linux Enterprise Server OS. CAUTION: ACPI Configuration for SuSE Linux Enterprise Server Must Be single-pci-domain or default On cell-based HP Integrity servers, to boot the SuSE Linux Enterprise Server OS an nPartition must have its ACPI configuration value set to single-pci-domain or default.
2. Access the EFI System Partition for the SuSE Linux Enterprise Server boot device. Use the map EFI Shell command to list the file systems (fs0, fs1, and so on) that are known and have been mapped. To choose a file system to use, enter its mapped name followed by a colon (:). For example, to operate with the boot device that is mapped as fs3, enter fs3: at the EFI Shell prompt. 3. Enter ELILO at the EFI Shell command prompt to launch the ELILO.EFI loader.
1. Log in to Linux running on the system you want to shut down. You should log in to the MP for the server and use the Console menu to access the system console. Accessing the console through the MP enables you to maintain console access to the system after Linux has shut down. 2. Issue the shutdown command with the desired command-line options, and include the required time argument to specify when the operating shutdown is to occur.
Select a partition number: 1 Do you want to reset partition number 1? (Y/[N]) y -> The selected partition will be reset. GSP:CM> If you are accessing the service processor using a single-partition-user account, the RS command selects which nPartition is to be reset: the nPartition that your account allows you to access. If using an operator or administrator service processor account, you can select which of the nPartitions in the server complex you want to reset. 3.
3. Exit the console and service processor interfaces if finished using them. To exit the EFI environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Procedure 5-29 Rebooting and Resetting nPartitions (EFI Shell) From the EFI Shell environment, issue the reset command to reset the local nPartition. The EFI Shell is available only on HP Integrity systems. 1.
2. At the OpenVMS command line, issue the @SYS$SYSTEM:SHUTDOWN command and enter Yes at the "Should an automatic system reboot be performed" prompt.
1. 2. Login to Linux running on the system you want to shut down. Issue the shutdown -r time command with the required time argument to specify when the shutdown is to occur. You can specify time in the format hh:mm, in which hh is the hour (one or two digits) and mm is the minute of the hour (two digits); or in the format +m, in which m is the number of minutes delay until shutdown; or specify now to immediately shut down.
2. At the OpenVMS command line, issue the @SYS$SYSTEM:SHUTDOWN command and enter Yes at the "Should an automatic system reboot be performed" prompt.
1. 2. Login to Linux running on the nPartition you want to shut down. Issue issue the shutdown -r time command with the required time argument to specify when the shutdown is to occur. You can specify time in the format hh:mm, in which hh is the hour (one or two digits) and mm is the minute of the hour (two digits); or in the format +m, in which m is the number of minutes delay until shutdown; or specify now to immediately shut down.
2. At the service processor Command menu, enter the RR command, specify which nPartition is to be reset, and confirm whether to reset it to the shutdown for reconfig state. The service processor RR command resets all cells in the nPartition, performs any nPartition reconfigurations, and halts all cells at a boot-is-blocked state, thus making the nPartition and all its cells inactive. Be certain to select the correct nPartition to be reset.
3. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Procedure 5-40 Shutting Down to Shutdown for Reconfig (EFI Shell) From the EFI Shell environment issue the reconfigreset command to shut an nPartition down to a shutdown for reconfig (inactive) state.
reboot be performed" prompt, then access the MP and, from the MP Command Menu, issue the RR command and specify the nPartition that is to be shutdown for reconfig. 1. Log in to HP OpenVMS running on the system that you want to shut down. You should log in to the MP for the server and use the Console menu to access the system console. Accessing the console through the MP enables you to maintain console access to the system after HP OpenVMS has shut down. 2.
Procedure 5-43 Shutting Down to Shutdown for Reconfig (Windows) From the Windows command line issue the shutdown /s command (or select the Start→Shut Down action and choose Shut down from the pull-down menu) to shut an nPartition down to a shutdown for reconfig (inactive) state or power off the nPartition hardware. CAUTION: Do not shut down Windows using Special Administration Console (SAC) restart or shutdown commands under normal circumstances.
2. Issue issue the shutdown -h time command with the required time argument to specify when the shutdown is to occur. You can specify time in the format hh:mm, in which hh is the hour (one or two digits) and mm is the minute of the hour (two digits); or in the format +m, in which m is the number of minutes delay until shutdown; or specify now to immediately shut down.
Procedure 5-46 Booting an Inactive nPartition (nPartition Commands) You can cause an inactive nPartition to be booted (made active) by using the parmodify command with the -B option when changing the configuration of an inactive nPartition. 1. Login to HP-UX running on any nPartition in the server complex, or login to any remote system with the Enhanced nPartition Commands (ParCLI) installed. When using the nPartition commands from a remote system, you can specify the -g... -h...
2. 3. At the EFI Boot Manager menu, select the Boot Option Maintenance option. At the Boot Option Maintenance menu, select the Boot from a File menu option and then select the network card whose MAC address you want to use when booting. Highlight the desired network card, then press Return or Enter to initiate booting using the selected card. EFI Boot Maintenance Manager ver 1.10 [14.60] Boot From a File.
3. Exit the console and service processor interfaces if finished using them. To exit the EFI environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Booting to the HP-UX Initial System Loader (ISL) On HP 9000 servers, you can boot to the HP-UX Initial System Loader (ISL) by using the following procedure.
4. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Booting to the HP-UX Loader (HPUX.EFI) On HP Integrity servers, you can boot to the HP-UX Loader (HPUX.EFI) by using the following procedure. NOTE: The HP-UX Loader (HPUX.EFI) is available only on HP Integrity servers.
6. Exit the console and service processor interfaces if finished using them. To exit the EFI environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Using HP-UX Loader Commands This section gives details on issuing HP-UX Boot Loader commands using the following two methods: • • “HPUX.
where command is one of the the hpux secondary system loader commands. For example: enter hpux ls to issue the ls command. Refer to the isl(1M) and hpux(1M) manpages for details. 3. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Booting to the Linux Loader (ELILO.
Linux Boot Option Management You can manage Linux boot options by interacting with the Linux loader interface (elilo.efi, the "ELILO boot" prompt) and by editing the Linux loader configuration file (elilo.conf). • The elilo.efi Linux loader boots a Linux kernel and can apply boot options that are specified in an elilo.conf file entry or are manually specified. — You can select any of the Linux kernel boot configuration entries in the boot device's elilo.conf file.
elilo.conf File Boot Options You can specify the following options, among others, in an elilo.conf file to configure a Linux device's boot behavior. For more details refer to the documentation for the Linux distribution you are using. • prompt — Specifies to make the "ELILO boot" prompt available without requiring anything to be typed. • timeout=tsecs — Sets the timeout duration in tenths of seconds.
Uncompressing Linux... done Loading initrd initrd-2.4.18-e.12.img...done • Specify additional boot options when loading a Linux boot configuration. 1. Access the "ELILO boot" prompt. 2. Type the Tab key to list all boot configuration entries in the elilo.conf file. 3. Enter the name of the boot entry you want to load, followed by any additional boot options to apply. See bootparam(7) or other Linux manpages for details on kernel boot options. ELILO boot: linux S Uncompressing Linux...
To set a boot path, enter PATH VAR hwpath, where VAR is the boot path variable (PRI, HAA, or ALT) and hwpath is a boot device hardware path. For example, to set the PRI boot path to a new value (4/0/2/0/0.10, in this case) enter PATH PRI 4/0/2/0/0.10, as shown below. Main Menu: Enter command or menu > PATH PRI 4/0/2/0/0.10.0 Primary Boot Path: 4/0/2/0/0.10 4/0/2/0/0.a (hex) Main Menu: Enter command or menu > 3. Exit the console and service processor interfaces if finished using them.
Procedure 5-57 Configuring Boot Paths and Options (EFI Shell) From the EFI Shell environment, use the bcfg command to add or delete boot options, or to change the order of items in the boot options list. The EFI Shell is available only on HP Integrity systems. 1. Access the EFI Shell environment for the nPartition whose boot paths (the EFI boot options list items) and options you want to configure. Login to the service processor (MP or GSP) and enter CO to access the Console list.
2. Configure boot path settings using the parmodify -p#... command. Use the following commands to set the boot path variables for a specified partition number (-p#): • PRI path— parmodify -p# -b PRI where PRI is the hardware path. • HAA path—parmodify -p# -s HAA where HAA is the hardware path. • ALT path—parmodify -p# -t ALT where ALT is the hardware path. If using the setboot command to set boot paths for the local nPartition, you can specify setboot -p PRI or the setboot -a ALT command.
Procedure 5-59 Configuring Autoboot Options (BCH Menu) From the BCH Menu, use the PATHFLAGS command at the BCH Configuration menu to set the boot-time actions for an nPartition. The BCH Menu is available only on HP 9000 systems. 1. Access the BCH Main Menu for the nPartition whose autoboot options you want to configure. Login to the service processor (MP or GSP) and enter CO to access the Console list. Select the nPartition console.
3. 4. Select the Set Auto Boot TimeOut menu operation from the Boot Option Maintenance menu. At the Set Auto Boot TimeOut menu, either disable autoboot by selecting the Delete/Disable Timeout menu item, or enable autoboot by setting the autoboot timeout through the Set Timeout Value menu item. When autoboot is enabled on an HP Integrity server, the local nPartition boot options are attempted to be loaded automatically at boot time, starting with the first item in the boot options list.
Procedure 5-62 Configuring Autoboot Options (HP-UX) From the HP-UX command line use the setboot -b on or setboot -b off command, to turn on (enable) or turn off (disable) autoboot. 1. 2. Login to HP-UX running on the nPartition whose autoboot options you want to configure. On HP Integrity servers only, the setboot -b on command enables autoboot, and the setboot -b off command disables autoboot.
NOTE: HP recommends that all self tests be performed for all nPartitions. To enable all tests for an nPartition, use the FASTBOOT RUN command at the BCH Configuration menu. To disable an individual test, enter FASTBOOT test SKIP, where test is the name of the self test ("PDH", "EARLY", or "LATE"). To enable an individual test, enter FASTBOOT test RUN. For details on setting self tests, enter HELP FASTBOOT at the Configuration menu. 3.
• boottest testname on — Enable the specified test (testname). For example: boottest io_hw on enables I/O hardware selftests. • boottest testname off — Disable the specified test (testname). For example: boottest io_hw off disables I/O hardware selftests. 3. Exit the console and service processor interfaces if finished using them. To exit the EFI environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu.
3. Use the setboot... command to enable or disable boot-time self tests for the local nPartition. You can use the following commands to configure tests: setboot -t test_name=[on|off|default] setboot -T test_name=[on|off|default] test_name is the name of the self test ("PDH", "early_cpu", "late_cpu") or is "all" (for all tests). The setboot command's -t option changes the test setting in stable storage and affects all following boots. The -T option changes the test setting for the next boot only.
6 Creating and Configuring nPartitions This chapter has procedures for creating, configuring, and managing nPartitions on Hewlett-Packard servers that support them. For an introduction to nPartition features, see Chapter 1 (page 15). For nPartition configuration requirements and recommendations, see Chapter 3 (page 61). Tools for Configuring nPartitions You can configure and manage nPartitions using the tools listed here.
Table 6-1 nPartition Configuration Task Summaries Task Summary “Creating a Genesis Partition” • Creating a Genesis Partition overwrites all nPartition-related complex profile data for the server and establishes one single-cell nPartition. • Service Processor (MP or GSP): CC command. See “Creating a Genesis Partition” (page 170). “Creating a New nPartition” • nPartition Commands: parcreate command. • Partition Manager: — Version 1.0 — Partition→Create Partition action. — Version 2.
Table 6-1 nPartition Configuration Task Summaries (continued) Task Summary “Unassigning (Removing) Cells from an • NOTE: When an inactive cell is specified to be removed from an nPartition the removal occurs immediately. When an active cell is specified to be removed from an nPartition” nPartition, to complete the cell removal the nPartition must perform a reboot for reconfig (HP-UX: shutdown -R; Windows: shutdown /r; Linux: shutdown -r time; OpenVMS: @SYS$SYSTEM:SHUTDOWN with an automatic system reboot).
Table 6-1 nPartition Configuration Task Summaries (continued) Task Summary “Setting Cell Attributes” • BCH Menu: Configuration menu, CELLCONFIG command to list or set cell use-on-next-boot values. • EFI Shell: cellconfig command to list or set cell use-on-next-boot values. • nPartition Commands: parmodify -p# -m#... command to modify cell attributes (-m#..., where # is the cell number) for the specified nPartition (-p#, where # is the nPartition number).
Table 6-1 nPartition Configuration Task Summaries (continued) Task Setting nPartition Boot Paths Summary • NOTE: On HP Integrity servers, nPartition boot paths can be listed and configured only from the local nPartition. See Chapter 5 (page 87) for detailed nPartition boot configuration tasks and related information. • BCH Menu: BCH Main menu, PATH command. • EFI Boot Manager: Boot Option Maintenance menu. • EFI Shell: bcfg command. • HP-UX: setboot command, or parmodify -p# -b... -s... -t... command.
Table 6-1 nPartition Configuration Task Summaries (continued) Task Configuring Remote Administration Summary • NOTE: This coverage of remote nPartition administration addresses features of HP Integrity Superdome, rx8620, and rx7620 servers. • Service Processor (MP or GSP): Remote security features. — SO command — Set MP security, including IPMI password. — SA command — Set MP network access, including IMPI LAN. — PARPERM command — Set nPartition Configuration Privilege. • HP-UX B.11.23 and HP-UX B.11.
As a result of this procedure, all existing nPartition configurations are deleted and are replaced with a single, one-cell nPartition (the Genesis Partition). You can revert to the previous nPartition configuration—if any existed before you created the Genesis Partition—by using the CC command and L option to restore the last configuration. 1. Save all current nPartition configuration details, if any nPartitions are configured in the complex.
You can confirm that the Genesis Partition was successfully created if the CC command reports that the "complex profile will be modified". If the CC command reports "Sorry, command failed", then the Genesis Partition was not created, possibly because one or more nPartitions are not at the shutdown for reconfig state. If this is the case, go back to Step 3 and ensure all nPartitions are inactive at the shutdown for reconfig state. 7.
Procedure 6-2 Creating a New nPartition (nPartition Commands) From the command line, use the parcreate command to create a new nPartition. You also can use the parstatus and parmodify commands to list nPartition and complex details and modify nPartition settings. NOTE: You can remotely perform this task using remote administration options supported by the Enhanced nPartition Commands or Partition Manager Version 2.0.
When parcreate successfully creates a new nPartition, it reports "Partition Created" and reports the nPartition number ("partition number is..."). If parcreate detects any problems or issues when creating an nPartition, it lists them in its output. If it cannot create the nPartition, parcreate reports "Command failed" along with more details. parcreate Command: Cell Attributes Differences for nPartition Command Releases The parcreate command's -c...
# 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. # When each modification takes place, parmodify reports "Command succeeded". Otherwise it reports any problems. You can specify each configuration option on a separate command line or can combine all options into a single, longer command line. For details on the various options for modifying nPartition settings, refer to the parmodify(1M) manpage. 4.
2. Run the Partition Manager task wizard for creating a new nPartition. From Partition Manager Version 1.0, select the Partition→Create Partition action. From Partition Manager Version 2.0, select the nPartition→Create nPartition action. Partition Manager guides you through the steps it requires for creating a new nPartition. 3. Exit Partition Manager. From Partition Manager Version 1.0, select the File→Exit action. From Partition Manager Version 2.
NOTE: You can remotely perform this task using remote administration options supported by the Enhanced nPartition Commands or Partition Manager Version 2.0. Remote administration is supported by the Partition Manager Tools→Switch Complexes action and by the nPartition command -u... -h... options or -g... -h... options. For details see “Tools for Configuring nPartitions” (page 165). 1.
3. Remove the nPartition. Use one of the following procedures to remove the nPartition: “Removing an Inactive Remote nPartition”, “Removing a Local nPartition”, or “Removing an Active Remote nPartition”. • Removing an Inactive Remote nPartition 1. Issue the parremove -p# command to remove the inactive remote nPartition (-p# where # is the nPartition number). For example: #parremove -p1 2. Issue the parstatus -P command to confirm that the nPartition was removed.
— — — From the EFI Shell for the nPartition, use reconfigreset to put the nPartition into a shutdown for reconfig state. From the BCH menu for the nPartition, use RECONFIGRESET to put the nPartition into a shutdown for reconfig state. From the service processor Command Menu for the server complex where the nPartition resides, use the Command menu RR command to put the nPartition into a shutdown for reconfig state. After you complete the nPartition removal, the nPartition no longer exists.
Adding cells to an nPartition involves selecting available cells (those not currently assigned to an nPartition) and assigning them to an existing nPartition. Both the selected cells and any I/O chassis connected to the cells are assigned to the designated nPartition. NOTE: Adding or removing cells from an nPartition will change the amount of memory available to the nPartition, possibly significantly.
cell The cell to be added to the nPartition. You can specify the cell in global (cell) format or in hardware location (cabinet/slot) format. type The cell type: base is the only supported cell type and it is the default. use The cell use-on-next-boot value: y or n. Use y (the default) if the cell is to be an active member of the nPartition, or use n if the cell is to remain an inactive member.
When using Partition Manager Version 1.0, select an nPartition, and use the Partition→Modify Partition action, Add/Remove Cells tab. When using Partition Manager Version 2.0, select an nPartition, and use the nPartition→Modify nPartition action, Add/Remove Cells tab. 1. Access Partition Manager. For details on accessing Partition Manager or other tools, see “Tools for Configuring nPartitions” (page 165). 2. 3. Select the nPartition to which you want to add cells.
• • • You must immediately perform a reboot for reconfig of an nPartition when you have removed an active cell from the nPartition. You must immediately perform a reboot for reconfig of an nPartition when you have removed a cell from an active nPartition and specified the -B option to the parmodify command. You do not need to perform a reboot for reconfig of an nPartition when you have removed an inactive cell from an nPartition and did not specify the -B option to the parmodify command.
Slightly different procedures are required for removing active cells and inactive cells. See the following information for details (“Guidelines for Removing an Active Cell” and “Guidelines for Removing an Inactive Cell”). If at least one of the cells you plan to remove is currently active, then follow the guidelines for removing active cells.
1. Access Partition Manager. For details on accessing Partition Manager or other tools, see “Tools for Configuring nPartitions” (page 165). 2. 3. Select the nPartition from which you want to remove cells. Specify for Partition Manager to remove one or more cells from the nPartition. From Partition Manager Version 1.0, use the Partition→Modify Partition action and select the Add/Remove Cells tab.
help you distinguish among the nPartition in a server complex. (You cannot change the nPartition number, which is a permanent unique identifier that is automatically assigned for each nPartition in a server complex.) Each nPartition name can have from 1 to 64 characters, including upper- and lowercase letters; numbers; and dashes, underscores, and spaces ("-" "_" and " ").
2. Use the parmodify -p# -P name command to set the nPartition name for any of the nPartitions in the server complex. Specify both the nPartition number (-p#, where # is the nPartition number) and the new name for the nPartition (-P name). If the nPartition name contains spaces then quotation marks must surround the name. # parmodify -p1 -P "New Name" Command succeeded. # You can list the new name of the nPartition by using the parstatus -p# command (where # is the nPartition number) or parstatus -P.
1. 2. Login to the service processor (MP or GSP) and enter CM to access the Command Menu. At the Command Menu, issue the ID command to list the complex name. The ID command lists some of the Stable Complex Configuration Data for the current server, including the complex name. GSP:CM> ID This command allows you to change certain fields in the Stable complex configuration portion of the complex profile. Retrieving the stable complex configuration portion of the complex profile.
2. Select the Complex→Set Complex Name action. Enter the new name for the complex in the text box provided, which shows the current complex name. If no name was previously assigned, the default name is "MyComplex". 3. Exit Partition Manager. From Partition Manager Version 1.0, select the File→Exit action. From Partition Manager Version 2.0, select Log off parmgr or exit the Web browser when finished.
3. From the BCH Configuration menu, use the CELLCONFIG command to list or set the use-on-next-boot value for each cell. • To list the use-on-next-boot values for all cells in the nPartition, issue the CELLCONFIG command with no arguments.
2. Use the cellconfig command to list or set the use-on-next-boot value for each cell. • To list the use-on-next-boot values for all cells in the nPartition, issue the cellconfig command with no arguments. • To change the use-on-next-boot value for a cell, issue the following command: cellconfig cell [on|off] where cell is the cell number, on sets the cell use-on-next-boot value to "y" (yes, do use the cell), or off sets the cell use-on-next-boot value to "n" (no, do not user the cell).
3. To modify cell attribute values, use the parmodify -p# -m#... command and specify the new attributes for a cell as part of the -m option. The -m... option differs slightly for the nPartition command releases. You must specify both the nPartition (-p# where # is the nPartition number) and the cell (-m#... where # is the cell number). To modify multiple cells, you can specify the -m option multiple times in the same command.
As needed, an absolute CLM specification is rounded up to the nearest 0.5 GBytes. If the clm value is rounded, the command reports the final value used. For details, refer to the parmodify(1M) manpage. 4. Reboot the nPartition to use the cells' new attribute values.
From Partition Manager Version 2.0, use the Set Cell Options tab to configure cell use-on-next-boot values, and use the Configure Memory tab to configure cell local memory values. CAUTION: Memory configured as cell local memory only can be used by operating systems that support it. Any memory configured as cell local memory is unusable when an nPartition runs an operating system that does not support it. 5. 6. 7. After changing attribute values for all the cells you plan to modify, click the OK button.
NOTE: You do not need to specify core cell choices for a valid core cell to be chosen. By default on four-cell and HP Superdome servers, system firmware selects the lowest numbered eligible cell to be the active core cell for the nPartition. By default on two-cell servers, cell 1 is selected as the core cell. Procedure 6-20 Setting Core Cell Choices (BCH Menu) From the BCH Menu, use the Configuration menu, COC command to configure core cell choices for the nPartition.
3. Exit the console and service processor interfaces if finished using them. To exit the EFI environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Procedure 6-22 Setting Core Cell Choices (nPartition Commands) From the command line, use the parmodify command to configure the core cell choices for an nPartition.
3. Modify the nPartition core cell choices using the parmodify -p# -r#... command. You can modify the core cell choices for the local nPartition or any remote nPartition in the server complex. Use the following command: parmodify -p# -r# -r#... Specify the nPartition number (-p#) and the cell ID (-r#) for all cells you wish to designate as core cell choices. # parmodify -p0 -r2 -r0 Command succeeded.
Unlocking Complex Profile Entries You can manually unlock a Complex Profile entry by using either of the following procedures: • • “Complex Profile Unlocking (Service Processor)” (page 198) “Complex Profile Unlocking (nPartition Commands)” (page 198) The Complex Profile is a set of data that determines how hardware is assigned to and used by nPartitions in an server complex. Each Complex Profile entry has its own lock which is used to restrict access to the entry.
2. Issue the parunlock command with the command-line option appropriate for the Complex Profile entry or entries you want to unlock. parunlock Options for Original nPartition Commands The Original nPartition Commands parunlock command supports the following options: -s Unlock the Stable Complex Configuration Data. -p# Unlock the Partition Configuration Data for the nPartition whose number (#) is specified.
7 Managing Hardware Resources This chapter covers the procedures for managing the hardware resources in nPartitions and their server complexes. The topics covered include power and LED (attention indicator) management, hardware configuration and deconfiguration, and analysis of the current complex status. Tools for Managing Hardware You can list and manage server hardware using the following tools.
Table 7-1 Hardware Management Task Summaries Task “Powering Server Cabinets On and Off” Summary • CAUTION: Before powering off system hardware, you first must check whether it is being used and also inspect the hardware. • Cabinet Power Switch: use the 48-volt power switch on the front of the cabinet. • Service Processor (MP or GSP): PE command. See “Powering Server Cabinets On and Off” (page 205).
Table 7-1 Hardware Management Task Summaries (continued) Task “Configuring and Deconfiguring Cells” Summary • NOTE: Configuring and deconfiguring cells may be restricted based on any Instant Capacity contract for the server complex. To make an inactive cell active (configured), its use-on-next-boot value must be "y" and its nPartition must perform a reboot for reconfig (shutdown -R).
Table 7-1 Hardware Management Task Summaries (continued) Task Summary “Enabling and Disabling • CAUTION: Some operating systems do not support Hyper-Threading. Problems can Hyper-Threading on occur when running an OS that does not support Hyper-Threading on an nPartition Dual-Core Intel® that has Hyper-Threading enabled. Itanium® 2 Processors” • NOTE: You must reset an nPartition when changing its Hyper-Threading status. Hyper-Threading will not be enabled or disabled until after the nPartition is reset.
Powering Server Cabinets On and Off You can power on or power off server cabinets by using any one of the following procedures: • “Powering Server Cabinets On and Off (Cabinet Power Switch)” (page 205) • “Powering Server Cabinets On and Off (Service Processor)” (page 205) When powering off a cabinet, you turn off 48-volt power to the cabinet thus causing all cells and all I/O chassis to power off, and causing most fans to turn off.
2. Check the VFP status to see whether any cabinet hardware is running an operating system (OS). Any nPartition whose state is "OS heartbeat" is running an OS and thus should not have its hardware powered off until after the OS is shut down. Type ^b (Control-b) to exit the VFP. 3. 4. Shut down the OS running on any cabinet hardware that you plan to power off. Confirm that nobody else is using or servicing the cabinet hardware you plan to power on or off.
Procedure 7-3 Powering Cells and I/O Chassis On and Off (Service Processor) Use the Command menu PE command to power on and power off cells, I/O chassis, and cabinets from the service processor interface (GSP or MP). CAUTION: When using the PE command at the service processor Command menu to power on or off hardware, be certain to specify the correct component to power on or off. The PE command does not check whether the hardware is actively being used.
Procedure 7-4 Powering Cells and I/O Chassis On and Off (nPartition Commands) From the command line, use the frupower -o -c# and frupower -f -c# commands to power on and power off cells (and their associated I/O chassis). NOTE: You can remotely perform this task using remote administration options supported by the Enhanced nPartition Commands or Partition Manager Version 2.0. Remote administration is supported by the Partition Manager Tools→Switch Complexes action and by the nPartition command -u... -h...
NOTE: You can use Partition Manager to power on or off inactive cells. You cannot power off active cells. To power on or off cells assigned to a remote nPartition when using Partition Manager, you must use Partition Manager Version 2.0 remote administration features. 1. Access Partition Manager. For details on accessing Partition Manager or other tools, see “Tools for Managing Hardware” (page 201). 2. Select the cell or I/O chassis you want to power on or off. In Partition Manager Version 1.
— — On HP Superdome servers, each cell attention indicator is located on the server cabinet hardware below the cell slot, just to the right of the power LED for the cell slot. On other Partition-capable servers, each cell attention indicator is located on the cell hardware, to the outside of the power LEDs for the cell. • I/O Chassis LEDs On HP Superdome servers only, each I/O chassis has a attention indicator, which is located on the cabinet above the I/O chassis.
2. Use the fruled command and either the rad command (HP-UX B.11.11) or the olrad command (HP-UX B.11.23 and HP-UX B.11.31) to manage (turn on, off, or blink) the attention indicator for a system hardware component. From the command line you can manage LEDs for the following hardware components: • Cells—Use fruled to blink or turn off a cell attention indicator. — Turn Off: The fruled -f -c# command turns off the attention indicator for the specified cell (-c#).
For details refer to the fruled(1), rad(1M), or olrad(1M) manpage. The following HP-UX B.11.11 example turns off and blinks various attention indicators on an HP Superdome system, including cell, I/O chassis, PCI slot, and cabinet LEDs.
4. Exit Partition Manager. From Partition Manager Version 1.0, select the File→Exit action. From Partition Manager Version 2.0, select Log off parmgr or exit the Web browser when finished.
4. Reboot the nPartition to use the cells' new use-on-next-boot settings. If you have changed any cell use-on-next-boot settings for the nPartition then reboot the nPartition in either of two ways: • Use the REBOOT command at the BCH interface to perform a reboot. If you have only changed cell configurations from ON to OFF, then perform a reboot using the REBOOT command. Any cells set to not be used will still be assigned to the nPartition but will not be used (will not rendezvous) in the nPartition.
3. Reboot the nPartition to use the cells' new configuration settings. If you have changed any cell use-on-next-boot settings for the nPartition then reboot the nPartition in either of two ways: • Use the reset command at the EFI Shell to perform a reboot. If you have only changed cell configurations from on to off, then perform a reboot using the reset command. Any cells set to not be used will still be assigned to the nPartition but will not be used (will not rendezvous) in the nPartition.
4. Reboot the nPartition to use the cells' new configuration (the new use-on-next-boot values). If you have changed any cell use-on-next-boot settings for the nPartition then reboot the nPartition in either of two ways: • Perform a standard reboot (HP-UX: shutdown -r; Windows: shutdown /r; Linux: shutdown -r time; OpenVMS: @SYS$SYSTEM:SHUTDOWN with an automatic system reboot). If you have only changed use-on-next-boot values from y to n, then perform a reboot.
8. Reboot the nPartition to use the cells' new attribute values. If you have changed any cell use-on-next-boot settings for the nPartition then reboot the nPartition in either of two ways: • Perform a standard reboot (HP-UX: shutdown -r; Windows: shutdown /r; Linux: shutdown -r time; OpenVMS: @SYS$SYSTEM:SHUTDOWN with an automatic system reboot). If you have only changed use-on-next-boot values from y to n, then perform a reboot.
4. Reboot the nPartition using the REBOOT command. Whenever changing processor configurations you must reboot the corresponding nPartition to allow the configuration changes to take place. 5. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu.
core that can allow additional efficiencies of processing. For example, a dual-core processor with Hyper-Threading active provides four logical processors, two on each processor core. CAUTION: Some operating systems do not support Hyper-Threading. Problems can occur when running an OS that does not support Hyper-Threading on an nPartition that has Hyper-Threading enabled. NOTE: You must reset an nPartition when changing its Hyper-Threading status.
Example 7-3 Enabling Hyper-Threading for an nPartition Shell> cpuconfig threads 1 cpuconfig: Threads are turned off. Shell> Shell> cpuconfig threads on 2 cpuconfig: Threads will be on after a reset. Shell> 1 2 The EFI Shell cpuconfig threads command indicates that Hyper-Threading currently is disabled (turned off) for the nPartition. This EFI Shell command configures Hyper-Threading to be enable after the nPartition is reset.
1. Access the BCH Main Menu for the nPartition whose memory you want to configure or deconfigure. Login to the service processor (MP or GSP) and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the BCH Main Menu (the Main Menu: Enter command or menu> prompt). If at a BCH menu other than the Main Menu, then enter MA to return to the BCH Main Menu. 2. 3. Enter SER to access the BCH Service Menu.
NOTE: When you deallocate a DIMM, all other DIMMs in the echelon also will not be used the next time the nPartition boots. dimmconfig cell dimm OFF deconfigures the specified DIMM (dimm) on the cell (cell) indicated. dimmconfig cell dimm ON configures the DIMM on the cell. Use dimmconfig cell to display the DIMM configuration for a cell. Enter the help dimmconfig command for more details. 4. Reboot the nPartition using the reset command.
8 Listing nPartition and Hardware Status This chapter covers procedures for listing the current status of nPartitions and server hardware components. For an introduction to nPartition system hardware features, see Chapter 1 (page 15). Tools for Listing Status You list hardware and nPartition status using the following tools. • Service Processor (MP or GSP) Menus Service processor menus provide a complex-wide service interface that can allow access to all hardware and nPartitions.
Table 8-1 Hardware and nPartition Status Task Summaries Task Summary “Listing Cell Configurations” • Service Processor (MP or GSP): CP command for cell nPartition assignments. PS command and select a cell for detailed information about any cell in the complex. • nPartition Commands: parstatus -C command. • Partition Manager: Version 1.0 — Details→Show Complex Details action, Cells tab. Version 2.0 — Select the Cells tab. See “Listing Cell Configurations” (page 226).
Table 8-1 Hardware and nPartition Status Task Summaries (continued) Task Summary “Listing Cabinets in a Server Complex” • Service Processor (MP or GSP): PS command and B option to list cabinet details for the desired cabinet. • nPartition Commands: parstatus -B command for summaries about all cabinets, or the parstatus -V -b# command for detailed status for the specified cabinet (-b# where # is the cabinet number). • Partition Manager: — Version 1.
Table 8-1 Hardware and nPartition Status Task Summaries (continued) Task Summary “Listing Power Status and Power Supplies” • Service Processor (MP or GSP): PS command and the cabinet option for detailed power status for the specified cabinet. • nPartition Commands: parstatus -B command for a power status summary for all cabinets, or parstatus -V -b# for detailed power status for the specified cabinet (-b#, where # is the cabinet number). frupower -d -C command for cell power status.
2. Issue the parstatus -C command to list details about the cells installed in the server complex and their nPartition assignments. Procedure 8-3 Listing Cell Configurations (Partition Manager) From Partition Manager, select the Cells tab to list cell configuration details. When using Partition Manager Version 1.0, first select the Details→Show Complex Details action, then select the Cells tab. 1. Access Partition Manager.
1. Access the BCH Main Menu for the nPartition whose processor configuration you want to list. Login to the service processor (MP or GSP) and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the BCH Main Menu (the Main Menu: Enter command or menu> prompt). If at a BCH menu other than the Main Menu, then enter MA to return to the BCH Main Menu. 2. 3. 4. Enter IN to access the BCH Information Menu.
Procedure 8-8 Listing Processor Configurations (Partition Manager) You can list the processor configuration for any of the cells or nPartitions in a server complex by using Partition Manager. When using Partition Manager Version 1.0, select the Details→Show Complex Details action, then select the CPUs/Memory tab. When using Partition Manager Version 2.0, select the Cells tab. 1. Access Partition Manager. For details on accessing Partition Manager or other tools, see “Tools for Listing Status” (page 223).
1. Access the BCH Main Menu for the nPartition whose memory configuration you want to list. Login to the service processor (MP or GSP) and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the BCH Main Menu (the Main Menu: Enter command or menu> prompt). If at a BCH menu other than the Main Menu, then enter MA to return to the BCH Main Menu. 2. 3. 4. Enter IN to access the BCH Information Menu.
2. Issue the command to list memory details. • parstatus -C — Cell and memory summaries for all cells in the server complex. • parstatus -V -c# — Detailed memory information for the specified cell (-c# where # is the cell number), including memory module (DIMM) locations and sizes. For HP Integrity servers, this includes details about the interleaved memory in the cell as well as the requested and allocated cell local memory (CLM) amounts.
2. At the Command Menu, enter the IO command to list the connections from I/O chassis to cells; the IO command is supported for HP Superdome servers only. To list the power status for I/O chassis, and the locations of installed I/O chassis, issue the PS command, and select the cabinet option for the server cabinet whose I/O configuration you want to view: • • 3. On HP Superdome servers, select the B (cabinet) option, and specify the cabinet whose information you want to view.
Procedure 8-17 Listing Input/Output (I/O) Configurations (nPartition Commands) From the command line, use the parstatus -I command to list details about all I/O chassis in the server complex. From HP-UX B.11.11 use the rad -q command, or from HP-UX B.11.23 and HP-UX B.11.31 use the olrad -q command, to list details about PCI cards and slots in the local nPartition. 1. Login to a system with the nPartition commands installed.
Listing Cabinets in a Server Complex You can list the cabinets in a server complex by using any one of the following procedures: • • • “Listing Cabinets in a Server Complex (Service Processor)” (page 234) “Listing Cabinets in a Server Complex (nPartition Commands)” (page 234) “Listing Cabinets in a Server Complex (Partition Manager)” (page 234) Cabinet details include the cabinet type, a list of cells, I/O chassis, power supplies, utilities, fans, firmware components, interconnecting hardware.
From Partition Manager Version 2.0, select the Hardware tab for an overview of cabinets in the complex. For complete details about all hardware in the complex, select the Complex→Show Complex Details action. 3. Exit Partition Manager. From Partition Manager Version 1.0, select the File→Exit action. From Partition Manager Version 2.0, select Log off parmgr or exit the Web browser when finished.
1. Login to a system with the nPartition commands installed. If using remote administration features, you can login to any system with Enhanced nPartition Commands installed. 2. Issue the parstatus -X command to display the product number and serial number. Procedure 8-25 Listing Product and Serial Numbers (Partition Manager) You can list the product number and serial number for a complex by using Partition Manager. When using Partition Manager Version 1.
1. Login to a system with the nPartition commands installed. If using remote administration features to list nPartition configurations, you can login to any system with Enhanced nPartition Commands installed. 2. Issue the parstatus -P command to list a summary of all nPartitions in the server complex. For detailed information issue the parstatus -V -p# command for more information about a specific nPartition (-p# where # is the nPartition number).
4. Exit the console and service processor interfaces if finished using them. To exit the BCH environment type ^B (Control-B); this exits the nPartition console and returns to the service processor Main Menu. To exit the service processor, type X at the Main Menu. Procedure 8-30 Listing the Local nPartition Number (EFI Shell) From the EFI Shell, use the info sys command to list the local nPartition number; this command also displays a list of active cells, CPUs, and the current memory configuration.
2. At the Command Menu, enter the PS command and select the cabinet option for the cabinet whose power status and related details you want to view: • On HP Superdome servers, select the B (cabinet) option, and specify the cabinet whose information you want to view. • On all other systems, select the T (cabinet) option. 3. To exit the service processor Command Menu, enter MA to return to the service processor Main Menu. At the Main Menu, enter X to exit the service processor interface.
Listing Fan and Blower Status You can list fan and blower status by using any one of the following procedures: • • • “Listing Fan and Blower Status (Service Processor)” (page 240) “Listing Fan and Blower Status (nPartition Commands)” (page 240) “Listing Fan and Blower Status (Partition Manager)” (page 240) Fan and blower status includes lists of cabinet blowers and I/O fans, and their status (whether ok or failed).
3. Exit Partition Manager. From Partition Manager Version 1.0, select the File→Exit action. From Partition Manager Version 2.0, select Log off parmgr or exit the Web browser when finished.
A nPartition Commands This appendix has details and command-line syntax for the HP nPartition Commands, including both the Original nPartition Commands and the Enhanced nPartition Commands. • The Original nPartition Commands were distributed as part of HP-UX 11i v1 (B.11.11) releases prior to the December 2004 release. • The Enhanced nPartition Commands are distributed with current HP-UX releases, including HP-UX 11i v3 (B.11.31), all releases of HP-UX 11i v2 (B.11.23), and releases of HP-UX 11i v1 (B.11.
Table A-1 Cell IDs in Global Cell Number Format (continued) • Global Format for rp8400, rp8420, rp8440, rx8620, and rx8640 0 1 2 3 — — — — Superdome Cabinet 0 Global Format 0 1 2 3 4 5 6 7 Superdome Cabinet 1 Global Format 8 9 10 11 12 13 14 15 Cell Hardware Location Format In cell hardware location format, each cell is identified using two numbers that specify the cabinet and the cell slot with the cabinet where the cell resides: cabinet/slot.
The cabinet, bay, and chassis fields specify the physical location of the I/O chassis. The values of these fields are as follows. • cabinet specifies the cabinet number where the I/O chassis resides. On HP rp7405/rp7410, rp7420, rp7440, rx7620, rx7640, rp8400, rp8420, rp8440, rx8620, and rx8640 servers, the server cabinet number always is 0. In HP rp8400, rp8420, rp8440, rx8620, and rx8640 complexes the I/O Expansion cabinet, if present, is 8.
Use the parstatus -I command to list all I/O chassis within a server complex, regardless of the chassis cell connections and nPartition assignments. Use the HP-UX rad -q command or olrad -q command to list the currently available PCI I/O slots in the local nPartition and their status. The rad command is available with HP-UX B.11.11, and olrad is available with HP-UX B.11.23 and HP-UX B.11.31.
Example A-1 I/O Specification Formats for Cabinets, Bays, and Chassis # parstatus -I [Chassis] 1 Hardware Location =================== cab0,bay0,chassis0 cab0,bay0,chassis1 cab0,bay0,chassis2 cab0,bay0,chassis3 cab0,bay1,chassis0 cab0,bay1,chassis1 cab0,bay1,chassis2 cab0,bay1,chassis3 cab1,bay0,chassis0 cab1,bay0,chassis1 cab1,bay0,chassis2 cab1,bay0,chassis3 cab1,bay1,chassis0 cab1,bay1,chassis1 cab1,bay1,chassis2 cab1,bay1,chassis3 cab8,bay0,chassis1 cab8,bay0,chassis3 cab8,bay1,chassis1 cab8,bay1,chas
• The -u... -h... set of options may be specified to cause the command to send its management request using WBEM to an nPartition other than the local nPartition (but can also be used as a "loopback access" to the local nPartition). NOTE: When specifying the -u... -h... options, the host specified by -h must be have the Enhanced nPartition Commands installed and have WBEM configured. Also, the client.
parcreate Command The parcreate command creates a new nPartition. This command assigns the specified cells (and any attached I/O chassis) to an nPartition, assigns a number to the new nPartition, and returns the partition number of the newly created nPartition. Root permission or IPMI LAN access is required to use parcreate. NOTE: On servers based on the HP sx1000 chipset or HP sx2000 chipset, when the nPartition Configuration Privilege is restricted the parcreate command cannot create a new nPartition.
ri • Reactivate with memory interleave (the default). Specifies to integrate the cell into the nPartition as normally occurs. Enhanced nPartition Commands only. The clm value specifies the amount of memory that will be configured as cell local memory for the cell. The clm value specified using the -c option takes precedence over the clm value specified using the -L option. You can specify the clm value in either of two forms: percentage or absolute amount of memory.
-rcell -T flag -B -u username -g -h IPaddress|hostname Specifies the core cell choices. One to four cells can be specified. Specifies whether Hyper-Threading should be enabled or not (only if cells support this feature). By default Hyper-Threading is disabled. The valid values for flag are: y Enable Hyper-Threading, which allows multiple threads to run concurrently on each processor core. n Disable Hyper-Threading. This is the default value. Specifies to boot the nPartition.
parmodify Command You can use the parmodify command to modify the following attributes of an existing nPartition: • Partition name • Cell assignments (add cells or remove cells) • Attributes of existing cells: — Cell type — Use-on-next-boot value — Failure usage — Enhanced nPartition Commands only: Cell local memory (CLM) value • Core cell choices • Enable or disable Hyper-Threading (only on supported cells) • Boot paths (the primary, alternate, and HA alternate paths) • IP address (if set, this value shoul
-p PartitionNumber Specifies the nPartition to be modified. PartitionNumber specifies the unique number (integer) assigned to the nPartition. The -p option is required. Note that you must also to specify any one or more of the following options. Specifies the cell(s) to be added to the nPartition. -a cell:[type]:[use_on_next_boot]:[failure_usage][:clm] • The only valid type value is: base Base cell. (The default.) • The valid use_on_next_boot values for cells are: y Participate in reboot. (The default.
-d cell Remove the specified cell from the nPartition. -b path Specifies the primary boot path. For HP 9000 servers, this is the PRI boot path. For HP Integrity servers -b sets the first item in the boot options list displayed by the EFI Boot Manager, and only boot options for the local nPartition can be modified. -t path Specifies the alternate boot path. For HP 9000 servers, this is the ALT boot path.
IPaddress|hostname specifies the IP address or hostname of the target nPartition (-u) or service processor (-g).
parremove Command The parremove command removes an existing nPartition. This removes all cells from the nPartition and destroys the nPartition definition. Root permission or IPMI LAN access is required to run this command. • To remove the local nPartition, you must specify the -F option. For the Original nPartition Commands, the local nPartition is the one from which you issue the parremove command.
-h IPaddress|hostname Enhanced nPartition Commands only. This option is only used in combination with either the -u or -g option. IPaddress|hostname specifies the IP address or hostname of the target nPartition (-u) or service processor (-g).
parstatus Command The parstatus command displays information about the nPartitions or hardware within a server complex. If you specify no arguments, parstatus lists information about several of the major components of the server complex. You can specify an individual entity (cell, I/O chassis, cabinet, or nPartition) to restrict the output to information about that component. All users can issue this command. Refer to the parstatus(1) manpage for complete details.
-p partition Show information about the specified nPartition. -T Only display the Hyper-Threading information for supported systems. If the -T option is used with other options, an error occurs except when the -T option is used with its related options. If the -T option is used on a non-supported system, an error occurs. Enhanced nPartition Commands only. Specifies the account and authorization to access an nPartition other than the local nPartition. The -h option is required if this option is used.
parunlock Command The parunlock command unlocks the Stable Complex Configuration Data or Partition Configuration Data. The Enhanced nPartition Commands version of parunlock also can unlock Dynamic Complex Configuration Data and cell data and can cancel pending changes to the Stable Complex Configuration Data. Use this command with caution. Root permission is required to run this command.
-A This option differs slightly for the Original nPartition Commands and Enhanced nPartition Commands releases. • For the Original nPartition Commands release, -A unlocks the Stable Complex Configuration Data and the Partition Configuration Data of all the nPartitions in the complex. • For the Enhanced nPartition Commands release, -A unlocks the Complex Configuration Data, the Dynamic Complex Configuration Data, and the Partition Configuration Data of all the nPartitions in the target complex.
fruled Command The fruled command blinks hardware attention indicators (LEDs) or turns them off. This command can control the cell attention LEDs in all cell-based servers, as well as the I/O chassis LEDs on Superdome servers. The fruled command also can start and stop blinking the cabinet number LCDs on HP Superdome compute cabinets and I/O expansion cabinets. Refer to the fruled(1) manpage for details. Synopsis fruled fruled fruled fruled fruled [-f|-o] [-f|-o] [-f|-o] [-f] -C [-f] -I [-B] -c cell [-c.
-h IPaddress|hostname Enhanced nPartition Commands only. This option is only used in combination with either the -u or -g option. IPaddress|hostname specifies the IP address or hostname of the target nPartition (-u) or service processor (-g).
frupower Command The frupower command turns on, turns off, or displays the current status of power for cells and I/O chassis in cell-based servers. Root permission is required to run this command. • By default, the frupower command permits you to power on or off inactive cells and I/O chassis that either are assigned to the target nPartition or are not assigned to any nPartition. • I/O chassis power is turned on or off when the cell to which it is connected is powered on or off.
-f -c cell -i IOchassis -C -I -l cabinet Power off the specified cells or I/O chassis. The specified cell is powered on/off or the power status is displayed. A cell can be specified either in the local (cabinet/slot) or global (cell_ID) format. The specified IOchassis is powered on/off or the power status is displayed. Display power status of all cells. By default the scope is the entire complex if the -l option is not specified. Display power status of all I/O chassis.
cplxmodify Command The cplxmodify command modifies attributes of a cell-based server complex, such as the complex name. NOTE: The cplxmodify command is only supported by the Enhanced nPartition Commands. Root permission is required to run this command. Refer to the cplxmodify(1M) manpage for details. Synopsis cplxmodify -N ComplexName [ -u username -h IPaddress|hostname | -g -h IPaddress|hostname ] • The -u... -h...
