HP Restricted / DRAFT DRAFT NOV 2001 HP System Partitions Guide Administration for nPartitions Revised Second Edition Preliminary HP rp7410 Draft Revision 2.1 Please send review comments to: schwartz@rsn.hp.com Manufacturing Part Number: B2355-90744 December 2001 © Copyright 2001 Hewlett-Packard Company. All rights reserved.
HP Restricted / DRAFT DRAFT NOV 2001 Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
HP Restricted / DRAFT Contents DRAFT NOV 2001 Publication History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP Restricted / DRAFT DRAFT NOV 2001 HP Superdome Partition Configuration Guidelines . . . . . . . . . . . . . . . Process for Selecting Cells for nPartitions . . . . . . . . . . . . . . . . . . . . . . . Chart of Supported HP rp7410 nPartition Configurations . . . . . . . . . . Chart of Supported HP rp8400 nPartition Configurations . . . . . . . . . . Charts of Supported HP Superdome nPartition Configurations. . . . . . Example Partition Configurations for an HP Superdome Server Complex . . . . . . . . .
DRAFT NOV 2001 HP Restricted / DRAFT Using Virtual Front Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 4. Boot and Reset Overview for nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Types of Booting and Resetting for nPartitions . . . . . . . . . . . . . . . . . . Boot Process for nPartitions, Cells, and HP-UX. . . . . . . . . . . . . . . . . . Overview of nPartition Boot Features . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT NOV 2001 HP Restricted / DRAFT 6. Procedures for Managing nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Listing the Local (Current) Partition Number . . . . . . . . . . . . . . . . . . . Listing All Configured nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Cell nPartition Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Genesis Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP Restricted / DRAFT DRAFT NOV 2001 New iCOD Issues for Managing nPartitions . . . . . . . . . . . . . . . . Tools for Managing iCOD Processors . . . . . . . . . . . . . . . . . . . . . . . . . . iCOD Requirements for nPartition Servers . . . . . . . . . . . . . . . . . . . . . Installing and Configuring iCOD on nPartitions . . . . . . . . . . . . . . . . . Procedures for Changing iCOD Configurations on nPartitions . . . . . Managing iCOD Utility (Pay Per Use) on nPartitions . . . . . . . . . . . . .
HP Restricted / DRAFT DRAFT NOV 2001 8 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Restricted / DRAFT Figures DRAFT NOV 2001 HP nPartition Server Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 HP rp7410 Supported nPartition Configurations . . . . . . . . . . . . . . . . . 57 HP rp8400 Supported nPartition Configurations . . . . . . . . . . . . . . . . . 58 Superdome 16-way and Superdome 32-way Supported nPartition Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Superdome 64-way Supported nPartition Configurations. . . . . . . . .
HP Restricted / DRAFT DRAFT NOV 2001 10 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Restricted / DRAFT Tables DRAFT NOV 2001 Numbering of PCI slots and Busses (LBAs) . . . . . . . . . . . . . . . . . . . . . 28 HP nPartition Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 HP-UX nPartition Configuration Commands . . . . . . . . . . . . . . . . . . . . 69 Cell IDs in Global Cell Number Format . . . . . . . . . . . . . . . . . . . . . . . . 70 Cell IDs in Hardware Location Format . . . . . . . . . . . . . . . . . . . . . . . . .
HP Restricted / DRAFT DRAFT NOV 2001 12 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Restricted / DRAFT DRAFT NOV 2001 Publication History The publication date and part number indicate this information’s current revision level. The publication date will change when a new edition is released. The part number will change when extensive changes are made. Second Edition December 2001, B2355-90744. CD-ROM, EPSS, and Web (http://www.docs.hp.com/) delivery. Enhancements include coverage of HP rp7410 servers.
HP Restricted / DRAFT DRAFT NOV 2001 Preface The HP System Partitions Guide describes nPartition administration and operations: the commands, procedures, concepts, and principles for configuring, monitoring, and maintaining nPartition system environments. This edition covers HP rp7410 servers, HP rp8400 servers and HP Superdome servers, including Superdome I/O Expansion cabinets.
NOTE CAUTION HP Restricted / DRAFT DRAFT NOV 2001 Notational Conventions The following notational conventions are used in this publication. • Commands and options are represented using this font. • Text to be typed by users is represented using this font. • Text to be replaced with text the user supplies is represented using this font. Example: “Enter the ls -l filename command” means you must replace filename with your own text.
HP Restricted / DRAFT DRAFT NOV 2001 Related Information You can find other information on general HP-UX 11i administration and nPartition server management in the following publications: • HP Technical Documentation Web Site http://www.docs.hp.com • HP-UX 11i Information Managing Systems and Workgroups: A Guide for HP-UX System Administrators HP-UX 11i Release Notes http://docs.hp.com/hpux/os/11i/index.html Information in the /usr/share/doc directory.
Overview 1 HP Restricted / DRAFT DRAFT NOV 2001 Overview This chapter introduces Hewlett-Packard’s nPartition server solutions, covers HP-UX 11i operating system features for nPartitions, and presents an overview of HP server support for nPartitions. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Overview Introduction to nPartition System Features HP Restricted / DRAFT DRAFT NOV 2001 Introduction to nPartition System Features Hewlett-Packard’s nPartition system capabilities enable you to configure a single server complex as one large system or as multiple smaller systems. Each nPartition definition establishes a subset of the server hardware resources that are used as a system environment for booting a single instance of HP-UX.
Overview Administration Tools for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Administration Tools for nPartitions You can use several administration tools to manage nPartitions in a server complex, including the service processor, consoles, Boot Console Handler (BCH) interfaces, HP-UX commands, and Partition Manager. • Server complex’s service processor, which including the Command menu, partition consoles, partition Virtual Front Panels, partition Console Logs, and the Chassis Log viewer.
Overview Server Hardware Support for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Figure 1-1 Server Hardware Support for nPartitions Three Hewlett-Packard servers support nPartitions: HP Superdome, HP rp8400, and HP rp7410 servers. These HP nPartition servers provide highly configurable, high-performance HP-UX system environments. HP Superdome, HP rp8400, and HP rp7410 server cabinets are shown in Figure 1-1.
Overview Server Hardware Support for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 An HP Superdome complex can consist of one cabinet or two server cabinets, and can also include one or two I/O expansion cabinets (to provide additional I/O chassis). Each HP rp8400 or HP rp7410 server complex consists of a single cabinet only. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Restricted / DRAFT Overview Supported HP Server Models DRAFT NOV 2001 Supported HP Server Models The HP servers that support nPartitions include the HP rp7410 server (see HP rp7410 Server Model), the HP rp8400 server (see HP rp8400 Server Model), and three models of HP Superdome servers (see HP Superdome Server Models on page 24). These nPartition servers have different hardware configurations and limits, as described in the following sections, and both include support for nPartitions.
Overview HP rp8400 Server Model HP Restricted / DRAFT DRAFT NOV 2001 • Up to 2 core I/O devices, one connected to cell 0, and the other connected to cell 1. • A total server complex capacity of: 2 cells, 8 processors, 32 DIMMs, and 16 PCI card slots. • The model string for HP rp7410 servers is 9000/800/rp7410. HP rp7410 servers include a single server cabinet.
Overview HP Superdome Server Models DRAFT NOV 2001 HP Restricted / DRAFT HP rp8400 servers include a single server cabinet. HP Superdome Server Models HP Superdome servers are highly scalable systems that allow you a tremendous amount of configurability to adapt the server resources to meet your particular hardware and software needs. HP Superdome servers include complete support for HP-UX hardware partitions (nPartitions).
Overview HP Superdome I/O Expansion Cabinet HP Restricted / DRAFT DRAFT NOV 2001 Superdome 64-way servers also can have optional I/O expansion cabinet hardware. The model string for Superdome 64-way servers is 9000/800/SD64000. With HP’s Superdome servers you can start with a system that meets your needs now, and add more components as your needs increase. You can add components (cells and I/O chassis) to your existing system as needs arise, and can also upgrade to larger-capacity systems as needed.
NOTE HP Restricted / DRAFT Overview HP-UX Hardware Paths for nPartitions DRAFT NOV 2001 HP-UX Hardware Paths for nPartitions The HP-UX hardware path for nPartition systems is provided in the format described here. The /usr/sbin/ioscan HP-UX command reports the hardware path for active components within the partition in which the command is issued. You also can use the /usr/bin/rad -q command to list details about active I/O slots and cards in the local nPartition.
Overview HP-UX Hardware Paths for nPartitions DRAFT NOV 2001 HP Restricted / DRAFT • d Is the card’s address on the slot’s PCI bus. Typically this is 0 (zero), although the core I/O card has multiple devices and addresses in a single card. • e Is the function for the I/O card. Typically this is 0 (zero) for single-function cards. • f Is the target of the I/O device, or SCSI ID. • g Is a device-specific address such as a SCSI controller (initiator).
Overview PCI Card Slot and Hardware Path Numbering HP Restricted / DRAFT DRAFT NOV 2001 PCI Card Slot and Hardware Path Numbering On nPartition servers, the PCI card slot numbers (within an I/O chassis) are not necessarily the same as their local bus adapter (LBA) number, such as is reported by the ioscan or rad HP-UX commands. Table 1-1 shows the correlations among PCI slots and their LBA numbers.
Overview rad Command Output in nPartitions NOTE HP Restricted / DRAFT DRAFT NOV 2001 rad Command Output in nPartitions This section covers the rad command’s output on nPartitions. For complete details refer to the rad (1M) manpage. When adding or replacing I/O cards use the SAM (/usr/sbin/sam) procedures, when possible, rather than equivalent rad command procedures. See also the sam (1M) and rad (1M) manpages.
HP Restricted / DRAFT Overview Getting Product Licensing Information DRAFT NOV 2001 Getting Product Licensing Information When you license a software product to run on an HP system you may need to provide machine or system details to the software vendor as part of the software registration process. This section describes how to obtain information you may need when licensing non-HP software to run on an HP nPartition server.
Overview nPartition Unique Identifiers NOTE HP Restricted / DRAFT DRAFT NOV 2001 nPartition Unique Identifiers Use the getconf command or the confstr() call to obtain unique machine and partition ID information. Do not use the uname -i command, which does not report unique IDs for nPartition systems. In order to guarantee compatibility on current and future platforms use the interfaces to getconf (1M) and confstr (3C) to retrieve unique machine identifiers.
HP Restricted / DRAFT Overview HP-UX 11i Release Features DRAFT NOV 2001 HP-UX 11i Release Features The HP-UX 11i Release Notes lists the latest feature additions and changes to HP-UX operating system and the various “operating environment” bundles. A copy of the release notes is installed in /usr/share/doc directory; see the 11iRelNotes.txt or 11iRelNotes.html file. Each of the HP-UX operating environment bundles includes its own collection of applications.
Overview HP-UX 11i Release Features HP Restricted / DRAFT DRAFT NOV 2001 The Read Before Installing or Updating HP-UX 11i booklet, which is distributed with HP-UX media, also has current details on release and operating environment features. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
DRAFT NOV 2001 HP Restricted / DRAFT Overview HP-UX 11i Release Features 34 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
2 HP Restricted / DRAFT Introduction to nPartitions HP-UX 11i Release Features DRAFT NOV 2001 Introduction to nPartitions This chapter describes HP’s nPartition features and presents related concepts and guidelines for managing nPartitions. For procedures related to managing nPartitions, refer to Procedures for Managing nPartitions on page 195. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Restricted / DRAFT Introduction to nPartitions Overview of nPartitions DRAFT NOV 2001 Overview of nPartitions On HP’s nPartition servers, each nPartition is a “logical system” that has its own dedicated portion of the server hardware that can run a single instance of the HP-UX 11i operating system. Each nPartition can boot, reboot, and operate independently of any other partitions and hardware within the same server complex.
Introduction to nPartitions Properties of Cells HP Restricted / DRAFT DRAFT NOV 2001 Properties of Cells Cells in an HP nPartition server have various properties that determine how the cells can be used and managed. The cell properties discussed here include: Assigned and Unassigned Cells, Base Cells, Core Cells, and Active and Inactive Cells. To list details about all cells in a server complex you can use the parstatus -C command.
Introduction to nPartitions Properties of Cells HP Restricted / DRAFT Core Cells Active and Inactive Cells DRAFT NOV 2001 One cell in each nPartition must serve as the active core cell. The core cell is a cell that is connected to an I/O chassis that has core I/O attached. The core cell controls the partition until HP-UX has booted and provides access to the nPartition’s console.
Introduction to nPartitions Genesis Partition HP Restricted / DRAFT DRAFT NOV 2001 The resources belonging to inactive cells are not actively used by a partition. For a cell’s resources to be actively used the cell must boot and participate in partition rendezvous. Genesis Partition The Genesis partition is the initial, one-cell nPartition created within a server complex. The Genesis partition is just like any other nPartition except in how it is created.
HP Restricted / DRAFT Introduction to nPartitions Partition Numbers DRAFT NOV 2001 Partition Numbers Each nPartition has its own unique partition number that the partition commands and utilities use for identifying the nPartition. When you create an nPartition, the utility you use assigns the partition the lowest available partition number.
Introduction to nPartitions Active and Inactive nPartitions HP Restricted / DRAFT DRAFT NOV 2001 • Listing Information—You can use the parstatus command or the Partition Manager utility from any nPartition to list partition and complex information. • Adding (Assigning) a Cell to an nPartition—You can use parmodify or Partition Manager from any nPartition to assign a cell to any nPartition in the server complex.
HP Restricted / DRAFT Introduction to nPartitions Active and Inactive nPartitions DRAFT NOV 2001 Use the parstatus -P HP-UX command to list all partitions and their boot states (active or inactive).
Introduction to nPartitions Active and Inactive nPartitions HP Restricted / DRAFT DRAFT NOV 2001 All three methods above reboot an nPartition and hold all of its cells at boot-is-blocked; as a result the rebooted partition is placed in a ready for reconfig (inactive) state. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
NOTE HP Restricted / DRAFT Introduction to nPartitions Tools for Managing Partitions DRAFT NOV 2001 Tools for Managing Partitions You can use several different software tools to create, modify, and monitor a server’s nPartitions and related server complex hardware. These tools have capabilities that overlap in some cases, but each tool also has unique features and access requirements.
Introduction to nPartitions Tools for Managing Partitions Table 2-1 HP Restricted / DRAFT DRAFT NOV 2001 Use Table 2-1 to select the most appropriate partition management tool based on the tasks you need to perform and the ways in which you can access the system.
Introduction to nPartitions Tools for Managing Partitions HP nPartition Management Tools HP Restricted / DRAFT Table 2-1 DRAFT NOV 2001 Partition Tool Features and Restrictions Boot Console Handler (BCH) interface The BCH interface is the method for interacting with a partition before it has booted HP-UX. Each partition’s BCH interface provides menus for configuring partition settings and booting HP-UX.
Introduction to nPartitions Tools for Managing Partitions DRAFT NOV 2001 HP nPartition Management Tools HP Restricted / DRAFT Table 2-1 Partition Tool Features and Restrictions Partition Manager (parmgr) Partition Manager (/opt/parmgr/bin/parmgr) provides a graphical interface for configuring, modifying, and managing partitions and hardware within a server complex.
Introduction to nPartitions Rebooting to Implement nPartition Changes HP Restricted / DRAFT DRAFT NOV 2001 Rebooting to Implement nPartition Changes Currently HP-UX 11i supports nPartitions on HP servers that support them, including HP rp8400 and HP Superdome servers. Once an nPartition has booted and is active, the partition has a fixed set of active hardware resources. In order to establish a different set of active hardware resources for an nPartition you must reboot the partition, as described below.
Introduction to nPartitions Rebooting to Implement nPartition Changes HP Restricted / DRAFT DRAFT NOV 2001 • Reset an nPartition to a ready for reconfig state (shutdown -R -H) to make the partition inactive. All cells in a partition remain inactive when the partition is in a ready for reconfig state; the cells do not perform a partition rendezvous. • Perform a standard reboot (shutdown -r) of an nPartition in most other situations where you do not need to add or remove cells from the partition.
Introduction to nPartitions nPartition Requirements and Recommendations HP Restricted / DRAFT DRAFT NOV 2001 nPartition Requirements nPartition Requirements and Recommendations The hardware requirements shown below determine which cells are eligible to be assigned to an nPartition. Also consider the partition recommendations, which can improve an nPartition’s performance and availability. Every nPartition you configure must meet the following hardware requirements.
Introduction to nPartitions nPartition Requirements and Recommendations DRAFT NOV 2001 HP Restricted / DRAFT • You should assign multiple core-capable cells to each nPartition. This allows the partition to boot at least to the BCH interface if a core cell fails to boot. (Disregard this recommendation if you are configuring multiple partitions in an HP rp8400 server or HP rp7410 server, each of which has a maximum of two core cells.
Introduction to nPartitions nPartition Requirements and Recommendations DRAFT NOV 2001 HP Restricted / DRAFT Under this configuration, if the cell to which the PRI disk is connected fails or is otherwise inactive, then if the HAA disk’s cell is available the nPartition still can boot HP-UX. Even if the PRI and HAA devices connect to the same cell (such as on a multiple-partition HP rp8400 server), the HAA device can be used to boot the partition to HP-UX should the PRI device fail.
Introduction to nPartitions HP Superdome Partition Configuration Guidelines NOTE HP Restricted / DRAFT DRAFT NOV 2001 HP Superdome nPartition Guidelines HP Superdome Partition Configuration Guidelines On HP Superdome servers, the locations of the cells you assign to each nPartition and the resulting loads on server interconnections can affect system performance within the server’s nPartitions.
Introduction to nPartitions HP Superdome Partition Configuration Guidelines DRAFT NOV 2001 HP Restricted / DRAFT • Place each partition within an empty cabinet, if possible. This applies to partitions in HP Superdome 64-way servers only. Assign each partition cells from a cabinet whose cells have no partition assignments, if possible. Do this before assigning cells from a cabinet that already has cells assigned to a partition.
Introduction to nPartitions Process for Selecting Cells for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Process for Selecting Cells for nPartitions The following steps provide a basic procedure for selecting which cells to assign to the nPartitions you will create in an HP server. Step 1. Determine the sizes of all partitions you will create in the server complex.
Introduction to nPartitions Process for Selecting Cells for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 will cause the partition to wait 10 minutes for the cell during the partition boot process, if the cell has a “y” use-on-next-boot setting. If any of the cells does not adhere to these requirements, go back to Step 3 and select a different set of cells for the partition. Step 5. Assign the cells to the partition.
Introduction to nPartitions Chart of Supported HP rp7410 nPartition Configurations Figure 2-1 Chart of Supported HP rp7410 nPartition Configurations The chart in Figure 2-2 lists the nPartition configurations that HP supports for HP rp7410 servers. HP rp7410 Supported nPartition Configurations HP rp7410 Cell Slots 0 1 One-Cell Partitions 1B 1A Two-Cell Partition 2A 2A HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Introduction to nPartitions Chart of Supported HP rp8400 nPartition Configurations Figure 2-2 Chart of Supported HP rp8400 nPartition Configurations The chart in Figure 2-2 lists the nPartition configurations that HP supports for HP rp8400 servers.
Introduction to nPartitions Charts of Supported HP Superdome nPartition Configurations HP Restricted / DRAFT DRAFT NOV 2001 Charts of Supported HP Superdome nPartition Configurations The chart in Figure 2-3 lists the nPartition cell configurations that HP supports for Superdome 16-way and Superdome 32-way servers. Figure 2-4 lists the nPartition cell configurations that HP supports for Superdome 64-way servers.
Introduction to nPartitions Charts of Supported HP Superdome nPartition Configurations DRAFT NOV 2001 Superdome 16-way and Superdome 32-way Supported nPartition Configurations Cell Slots Config Set Superdome 16-way 0 1 2 3 One-Cell Partitions 1 1A 1C 1B 2D Two-Cell Partitions 2 2A 2B 2A 2B Three-Cell Partition 3 3A 3A 3A Four-Cell Partition 4 4A 4A 4A 4A Superdome 32-way Cell Slots One-Cell Partitions 5 Two-Cell Partitions 6 0 1 2 3 4 5 6 7 1A 1E 1C 1G 1B 1F
Introduction to nPartitions Charts of Supported HP Superdome nPartition Configurations DRAFT NOV 2001 Superdome 64-way Supported nPartition Configurations Config Set 0 One-Cell Partitions 14 1A 1I 1E 1M 1C 1K 1G 1O 1B 1J 1F 1N 1D 1L 1H 1P Two-Cell Partitions 15 2A 2E 2A 2E 2C 2G 2C 2G 2B 2F 2B 2F 2D 2H 2D 2H 2I 2I Cell Slots Three-Cell Partitions Four-Cell Partitions Superdome 64-way Cabinet 0 Superdome 64-way Cabinet 1 1 2 3 4 5 6 7 0 1 2 3 4 5 6
Introduction to nPartitions Example Partition Configurations for an HP Superdome Server Complex HP Restricted / DRAFT DRAFT NOV 2001 Example Partition Configurations for an HP Superdome Server Complex The following example cell assignments demonstrate the procedure for selecting cells for two sample server complex configurations. For reference in the following examples, Figure 2-3 on page 60 and Figure 2-4 on page 61 list a unique number for each partition configuration set.
Introduction to nPartitions Example Partition Configurations for an HP Superdome Server Complex 1 The following example illustrations show how the two example complex partition configurations would be selected, using Figure 2-3 and Figure 2-4 to determine which recommended partitions to use. Example 1 Superdome 32-way complex partition configuration. One six-cell partition and one two-cell partition.
HP Restricted / DRAFT Introduction to nPartitions Server Complex Profiles DRAFT NOV 2001 Server Complex Profiles Each HP nPartition server’s Complex Profile includes the data that determine how the server’s hardware is assigned to and is used by nPartitions. When you configure partitions and modify partition settings, the commands and utilities you use lock and unlock the server’s Complex Profile when revising it, as discussed in Locking and Unlocking Complex Profiles on page 65.
Introduction to nPartitions Locking and Unlocking Complex Profiles HP Restricted / DRAFT DRAFT NOV 2001 The Partition Configuration Data includes the following details for each nPartition in the server complex: — The partition’s name, number, and IP address. — The PRI, HAA, and ALT boot paths and boot actions (path flags). — The use-on-next-boot setting for each cell. This determines whether the cell is allowed to become active and join (rendezvous) the rest of the cells in the partition.
HP Restricted / DRAFT Introduction to nPartitions Coordinating Changes to nPartitions DRAFT NOV 2001 Coordinating Changes to nPartitions When you modify nPartitions you should perform your changes so that they occur at a time when they will not conflict with other nPartition changes in the same server complex.
Introduction to nPartitions Coordinating Changes to nPartitions HP Restricted / DRAFT DRAFT NOV 2001 • When removing an active cell from a partition you must perform a reboot for reconfig (shutdown -R) of the modified partition to release the Complex Profile lock, regardless of whether you use parmodify or Partition Manager. You must perform the reboot for reconfig before you can add or remove other cells from nPartitions in the server complex.
Introduction to nPartitions Using HP-UX nPartition Configuration Commands NOTE HP Restricted / DRAFT DRAFT NOV 2001 Using HP-UX nPartition Configuration Commands HP-UX 11i provides you with several HP-UX commands for configuring and managing nPartitions and related server hardware. The nPartition commands include: parcreate, parmodify, parremove, parstatus, parunlock, fruled, and frupower. Table 2-2 on page 69 describes each of these commands.
Introduction to nPartitions Using HP-UX nPartition Configuration Commands Table 2-2 HP Restricted / DRAFT DRAFT NOV 2001 Table 2-2 describes the nPartition configuration commands and lists sections where you can find each command’s syntax and details. HP-UX nPartition Configuration Commands Command Description parcreate Create a new partition; root permission is required. parmodify parremove parstatus parunlock fruled frupower See parcreate Command on page 76.
Introduction to nPartitions Specifying Cells and I/O Chassis to Commands Table 2-3 HP Restricted / DRAFT DRAFT NOV 2001 Specifying Cells and I/O Chassis to Commands Use the cell and I/O chassis notation described in this section when you manage, configure, and inquire about cells and I/O chassis using the HP-UX nPartition configuration commands. Details are in the Cell Format and I/O Format sections that follow.
Introduction to nPartitions Specifying Cells and I/O Chassis to Commands Table 2-4 HP Restricted / DRAFT DRAFT NOV 2001 • 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.
Introduction to nPartitions Specifying Cells and I/O Chassis to Commands HP Restricted / DRAFT DRAFT NOV 2001 I/O Format Use the following I/O hardware location format when specifying an I/O chassis to the HP-UX nPartition configuration commands: cabinet/bay/chassis 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.
Introduction to nPartitions Specifying Cells and I/O Chassis to Commands DRAFT NOV 2001 HP Restricted / DRAFT On HP Superdome servers, the chassis number is: — 1 — Chassis 1, the left chassis in the bay, as viewed when facing the bay/chassis. — 3 — Chassis 3, the right chassis in the bay, as viewed when facing the bay/chassis. In HP Superdome servers all chassis are 12-slot I/O chassis, both in Compute cabinets and in I/O Expansion cabinets.
Introduction to nPartitions Specifying Cells and I/O Chassis to Commands DRAFT NOV 2001 HP Restricted / DRAFT # parstatus -I [Chassis] 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,ch
Introduction to nPartitions nPartition Commands—Details and Syntax NOTE HP Restricted / DRAFT DRAFT NOV 2001 nPartition Commands—Details and Syntax This section has details and command-line syntax for the following HP-UX nPartition configuration commands: • parcreate Command on page 76 • parmodify Command on page 77 • parremove Command on page 79 • parstatus Command on page 80 • parunlock Command on page 82 The sections that follow provide useful reference information for using the HP-UX nPartition com
Introduction to nPartitions parcreate Command DRAFT NOV 2001 Synopsis Options HP Restricted / DRAFT parcreate Command The /usr/sbin/parcreate command creates a new nPartition. This command assigns the specified cells (and any attached I/O chassis) to an nPartition after removing the cells from the free cell list. This command assigns a number to the new partition and returns the partition number of the newly created partition. Root permission is required to use parcreate.
Introduction to nPartitions parmodify Command DRAFT NOV 2001 Synopsis Options HP Restricted / DRAFT parmodify Command You can use the /usr/sbin/parmodify command to modify the following attributes of an existing partition: Partition name Cell assignments (add cells or remove cells) Attributes of existing cells (such as the use-on-next-boot value) Core cell and core alternate cells Boot paths (the primary, alternate, and HA alternate paths) Root permission is required to use this command.
HP Restricted / DRAFT Introduction to nPartitions parmodify Command DRAFT NOV 2001 -m cell:[cell_type]:[use_on_next_boot]:[failure_usage] Modify attributes of a cell already assigned the partition. For details on cell_type, use_on_next_boot, and failure_usage see the -a option’s descriptions (above). -I IPaddress Specifies the IP address that should be used by management tools (like SAM) to address this partition. -r cell Specifies the core cell and core alternate cells.
Introduction to nPartitions parremove Command DRAFT NOV 2001 Synopsis Options HP Restricted / DRAFT parremove Command The /usr/sbin/parremove command removes an existing partition. This removes all cells from the partition and destroys the partition definition. To remove the local nPartition (the partition from which you issue this command) you must specify the -F option.
Introduction to nPartitions parstatus Command DRAFT NOV 2001 Synopsis Options HP Restricted / DRAFT parstatus Command The /usr/sbin/parstatus command displays information about the partitions 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 partition) to restrict the output to information about that component.
Introduction to nPartitions parstatus Command HP Restricted / DRAFT DRAFT NOV 2001 -P Show information for all partitions in the complex. -c cell Show information about the specified cell. -i IOchassis Show information about the specified I/O chassis. -b cabinet Show information about the specified cabinet. -p partition Show information about the specified partition. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Introduction to nPartitions parunlock Command DRAFT NOV 2001 Synopsis Options HP Restricted / DRAFT parunlock Command The /usr/sbin/parunlock command unlocks the Stable Complex Configuration Data or Partition Configuration Data. Use this command with caution. Root permission is required to run this command. See the parunlock (1M) manpage for details. parunlock [-p PartitionNumber] [-s] parunlock -A -p PartitionNumber Unlock the Partition Configuration Data of the specified partition.
Introduction to nPartitions Using the Partition Manager Utility HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager Primary Window Figure 2-5 Using the Partition Manager Utility The Partition Manager utility (/opt/parmgr/bin/parmgr) provides a graphical user interface for configuring nPartitions and managing resources within a server complex.
HP Restricted / DRAFT Introduction to nPartitions Using the Partition Manager Utility Running Partition Manager DRAFT NOV 2001 The left side of the primary window lists all partitions, available resources (installed hardware that is not assigned to a partition), and empty cell and I/O chassis slots. Selecting an item on the left side of the primary window displays its details on the primary window’s right side. You can access Partition Manager using the following methods.
Introduction to nPartitions Using the Partition Manager Utility HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager Online Help • Partition Manager provides graphical interfaces only, and does not provide a terminal (text mode) interface. • Using Partition Manager requires root permission. • HP-UX must be running in multi-user mode to support Partition Manager. • You can run only one instance of Partition Manager or SAM (/usr/sbin/sam) per user login session.
DRAFT NOV 2001 HP Restricted / DRAFT Introduction to nPartitions Using the Partition Manager Utility 86 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
3 NOTE HP Restricted / DRAFT Using Console and Service Processor Interfaces Using the Partition Manager Utility DRAFT NOV 2001 Using Console and Service Processor Interfaces This chapter covers the service processor and nPartition console interfaces available for HP’s nPartition servers. The service processor in HP servers is sometimes called the Management Processor (MP) and sometimes the Guardian Service Processor (GSP).
Using Console and Service Processor Interfaces Service Processor (GSP or MP) Features HP Restricted / DRAFT DRAFT NOV 2001 Service Processor (GSP or MP) Features The service processor (GSP or MP) utility hardware is an independent support system for nPartition servers. It provides a way for you to connect to a server complex and perform administration or monitoring tasks for the server hardware and its nPartitions.
Using Console and Service Processor Interfaces Service Processor (GSP or MP) Features HP Restricted / DRAFT DRAFT NOV 2001 The service processor also controls power, reset, and TOC capabilities, displays and records system events (chassis codes), and can display detailed information about the various internal subsystems.
Using Console and Service Processor Interfaces Service Processor (GSP or MP) Features DRAFT NOV 2001 HP Restricted / DRAFT • Console Logs Enter CL from the service processor Main menu to access the console logs menu. To exit the console log, type ^b (Control-b). Each nPartition has its own console log, which has a history of the nPartition console’s output, including boot output, BCH activity, and any HP-UX console login activity.
Using Console and Service Processor Interfaces Service Processor Accounts and Access Levels HP Restricted / DRAFT DRAFT NOV 2001 Service Processor Accounts and Access Levels To access the service processor interface for a server complex, you must have a user account that enables you to log in to the service processor. Each server complex has its own set of service processor user accounts, which are defined for the server complex and may differ from accounts on other complexes.
Using Console and Service Processor Interfaces Accessing Service Processor Interfaces HP Restricted / DRAFT DRAFT NOV 2001 Accessing Service Processor Interfaces This section describes how to log in to the service processor (GSP or MP) for an nPartition server complex. You can connect to a server complex’s service processor using the following methods: • Connecting through the customer LAN port by using telnet, if login access through the customer LAN is enabled for the service processor.
Using Console and Service Processor Interfaces Procedure: Logging in to a Service Processor DRAFT NOV 2001 Example: Connecting to a Service Processor HP Restricted / DRAFT Figure 3-1 > telnet hpsys-s Trying... Connected to hpsys-s.rsn.hp.com. Escape character is ’^]’. Local flow control off MP login: Accountname MP password: Welcome to the S Class 16K-A Management Processor (c) Copyright 1995-2001 Hewlett-Packard Co., All Rights Reserved. Version 0.
Using Console and Service Processor Interfaces Procedure: Logging in to a Service Processor HP Restricted / DRAFT DRAFT NOV 2001 All telnet commands and escape options are supported while you are connected to the service processor. See the telnet(1) manpage for details. (On non-HP-UX platforms such as various PC environments you can instead use an alternate telnet program.) Step 2. Log in using your service processor user account name and password. GSP login: Accountname GSP password: Password Step 3.
Using Console and Service Processor Interfaces Using Service Processor Menus HP Restricted / DRAFT DRAFT NOV 2001 NOTE Using Service Processor Menus The service processor (GSP or MP) has a set of menus that give you access to various commands, consoles, log files, and other features. See Navigating through Service Processor Menus on page 97 for details on using these menus.
Using Console and Service Processor Interfaces Using Service Processor Menus DRAFT NOV 2001 Overview of Service Processor (GSP or MP) Menus HP Restricted / DRAFT CO — Console Menu Partitions available: # --0) 1) Q) Please select partition number: VFP — Virtual Front Panel Service Processor (GSP or MP) Main Menu GSP MAIN MENU: CO: VFP: CM: CL: SL: HE: X: GSP> Name ---Partition 0 Partition One Quit Consoles Virtual Front Panel Command Menu Console Logs Show chassis Logs Help Exit Connection Partiti
Using Console and Service Processor Interfaces Navigating through Service Processor Menus HP Restricted / DRAFT DRAFT NOV 2001 Navigating through Service Processor Menus Figure 3-3 on page 98 shows the commands and options for returning to the service processor Main menu and for ending a service processor login session.
Using Console and Service Processor Interfaces Navigating through Service Processor Menus DRAFT NOV 2001 Navigating through Service Processor (GSP or MP) Menus HP Restricted / DRAFT Figure 3-3 telnet sdome-g (log in to service processor) Service Processor Main Menu Console Menu VFP Please select partition number: Virtual Front Panel Menu CM MA GSP:CM> Console Log Viewer Menu SL Q or ^b GSP:VFP> Command Menu CL Q or ^b Q or ^b GSP:VW> Chassis Log Viewer Menu Q or ^b GSP:VW> Connection c
Using Console and Service Processor Interfaces Using Service Processor Commands HP Restricted / DRAFT DRAFT NOV 2001 Using Service Processor Commands You can issue commands at the service processor Command menu. To access the service processor Command menu, enter CM at the service processor’s Main menu. To exit the Command menu, enter the MA command to return to the Main menu. All service processor users accessing the Command menu share access to the menu. Only one command can be issued at a time.
Using Console and Service Processor Interfaces Commonly Used Service Processor Commands HP Restricted / DRAFT DRAFT NOV 2001 Commonly Used Service Processor Commands Table 3-1 summarizes commands that are commonly used by system administrators. These commands are available to all service processor users. Table 3-1 Commonly Used Service Processor Commands Command Description BO Boot an nPartition past an inactive boot-is-blocked (BIB) state to make it active. CP Display nPartition cell assignments.
Using Console and Service Processor Interfaces Service Processor Commands: Quick Reference NOTE HP Restricted / DRAFT DRAFT NOV 2001 Service Processor Commands: Quick Reference The following tables list commands available from the service processor Command menu: • Service Commands on page 101 • Status Commands on page 102 • System and Access Configuration Commands on page 103 For a complete and current list of all service processor commands, enter the HE command at the service processor Command menu.
Using Console and Service Processor Interfaces Service Processor Commands: Quick Reference DRAFT NOV 2001 HP Restricted / DRAFT Table 3-2 Service Processor: Service Commands Command Description RS Reset an nPartition. SYSREV Display all cabinet FPGA and firmware revisions. (HP rp8400 and HP rp7410 servers only.) TC Send a TOC signal to an nPartition. TE Broadcast a message to all users of the Command menu. VM Margin the voltage in a cabinet. (HP Superdome servers only.
Using Console and Service Processor Interfaces Service Processor Commands: Quick Reference DRAFT NOV 2001 Table 3-4 HP Restricted / DRAFT System and Access Configuration Commands The system and access configuration commands provide ways to configure system security and console and diagnostic settings. These commands also enable you to modify some complex configuration settings.
Using Console and Service Processor Interfaces Service Processor Commands: Quick Reference DRAFT NOV 2001 Service Processor: System and Access Configuration Commands HP Restricted / DRAFT Table 3-4 Access Level(s) Command Description Administrator, Operator IT Modify command interface inactivity time-out. Administrator LC Configure LAN connections. Administrator, Operator, Single Partition User LS Display LAN connected console status. Administrator ND Enable/disable network diagnostics.
Using Console and Service Processor Interfaces Configuring Service Processor Network Settings HP Restricted / DRAFT DRAFT NOV 2001 Configuring Service Processor Network Settings This section describes how to list and configure the network settings for service processor (GSP or MP) hardware. These settings are used for connections to the service processor and are not used for HP-UX networking.
Using Console and Service Processor Interfaces Configuring Service Processor Network Settings HP Restricted / DRAFT DRAFT NOV 2001 The following examples show service processor LAN status for various HP nPartition servers. HP rp7410 or rp8400 Service Processor LAN Status MP:CM> LS Current configuration of MP customer LAN interface MAC address : 00:30:6e:05:19:ac IP address : 15.99.84.140 (0x0f63548c) Hostname : redxii-c Subnet mask : 255.255.255.0 (0xffffff00) Gateway : 15.99.84.
Using Console and Service Processor Interfaces Configuring Service Processor Network Settings DRAFT NOV 2001 HP Restricted / DRAFT Table 3-6 Default Configuration for Service Processor Private LAN (HP Superdome Servers Only) Private LAN IP Address 192.168.2.10 Private LAN Host Name priv-00 Private LAN Subnet Mask 255.255.255.0 Private LAN Gateway 192.168.2.
Using Console and Service Processor Interfaces Configuring Service Processor Network Settings HP Restricted / DRAFT DRAFT NOV 2001 After you reconfigure the service processor’s networking, you can remove these network routing table changes with the route delete... command. 3. Enter this command to confirm the new network connection to the service processor: ping 198.168.1.1 -n 2 4. Use the telnet 192.168.1.1 command from the PC or workstation to connect to the service processor. Step 2.
Using Console and Service Processor Interfaces Accessing nPartition Consoles HP Restricted / DRAFT DRAFT NOV 2001 Accessing nPartition Consoles The service processor Console menu provides access to all nPartition consoles within the server complex. Enter CO from the service processor Main menu to access an nPartition’s console. To exit the partition console, type ^b (Control-b) to return to the Main menu. Each nPartition in a complex has a single console.
Using Console and Service Processor Interfaces nPartition Console Access versus Direct HP-UX Log-In HP Restricted / DRAFT DRAFT NOV 2001 You should log in to HP-UX running on an nPartition when you do not need to use service processor features and do not want to record a log of your activity. Before HP-UX has booted, the service processor nPartition consoles are the primary method of interacting with an nPartition.
Using Console and Service Processor Interfaces Accessing the Boot Console Handler (BCH) HP Restricted / DRAFT DRAFT NOV 2001 Accessing the Boot Console Handler (BCH) Each nPartition in a server complex has its own Boot Console Handler (BCH) interface. When an nPartition is booted to BCH, its BCH interface is available through the nPartition’s console. The nPartition BCH interface enables you to manage and configure the HP-UX boot process for an nPartition.
Using Console and Service Processor Interfaces Accessing the Boot Console Handler (BCH) DRAFT NOV 2001 HP Restricted / DRAFT To display the current BCH menu and commands, type DI.
Using Console and Service Processor Interfaces Accessing the Boot Console Handler (BCH) HP Restricted / DRAFT DRAFT NOV 2001 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Using Console and Service Processor Interfaces Viewing Console Logs HP Restricted / DRAFT DRAFT NOV 2001 Viewing Console Logs Each nPartition in a server complex has its own console log that stores a record of the nPartition’s most recent console activity. To access an nPartition’s console log, enter CL from the service processor Main menu and select which nPartition’s console log you want to view. To exit the console log viewer, type ^b (Control-b) to return to the Main menu.
Using Console and Service Processor Interfaces Using Chassis Code Log Viewers HP Restricted / DRAFT DRAFT NOV 2001 NOTE Using Chassis Code Log Viewers The service processor’s chassis log viewer enables you to view chassis codes that are emitted throughout the entire server complex. To enter the chassis log viewer enter SL at the service processor Main menu. To exit the viewer type ^b (Control-b) to return to the Main menu.
Using Console and Service Processor Interfaces Using Chassis Code Log Viewers HP Restricted / DRAFT DRAFT NOV 2001 On nPartition servers, chassis codes are recorded in the server complex activity log (for events of alert level 0 or alert level 1) or the error log (for events alert level 2 or higher).
Using Console and Service Processor Interfaces Using Virtual Front Panels HP Restricted / DRAFT DRAFT NOV 2001 Using Virtual Front Panels The Virtual Front Panel (VFP) provides ways to monitor the chassis codes for a particular nPartition or the entire server complex (all nPartitions). The VFP presents a real-time display of activity on the selected nPartition(s) and it automatically updates when cell and nPartition status change. To access the VFP feature, enter VFP from the service processor Main menu.
Using Console and Service Processor Interfaces Using Virtual Front Panels HP Restricted / DRAFT DRAFT NOV 2001 118 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
4 HP Restricted / DRAFT Boot and Reset Overview for nPartitions Using Virtual Front Panels DRAFT NOV 2001 Boot and Reset Overview for nPartitions This chapter presents an overview of booting and reset concepts and issues for HP nPartition servers. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Boot and Reset Overview for nPartitions Types of Booting and Resetting for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Types of Booting and Resetting for nPartitions All standard boot and reboot methods are supported for HP nPartition servers, though some boot and reset procedures differ slightly or use different tools than on other HP servers.
Boot and Reset Overview for nPartitions Types of Booting and Resetting for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 The shutdown -R -H command, the BCH interface’s RECONFIGRESET command, and the service processor Command menu’s RR command all reset a partition to ready for reconfig state. nPartition Booting The following list summarizes all types of booting, rebooting, and Summary resetting that are supported for HP hard-partitionable systems.
Boot and Reset Overview for nPartitions Types of Booting and Resetting for nPartitions HP Restricted / DRAFT DRAFT NOV 2001 use-on-next-boot setting participate in partition rendezvous and synchronize to boot as a single partition. To perform a reboot for reconfig use the shutdown -R command.
Boot and Reset Overview for nPartitions Boot Process for nPartitions, Cells, and HP-UX HP Restricted / DRAFT DRAFT NOV 2001 Boot Process for nPartitions, Cells, and HP-UX On HP nPartition servers, each partition’s cells go through the stages described here when proceeding from being powered on or reset to forming an nPartition (partition rendezvous) to booting the BCH interface and booting the HP-UX operating system on a partition.
Boot and Reset Overview for nPartitions Boot Process for nPartitions, Cells, and HP-UX HP Restricted / DRAFT DRAFT NOV 2001 Each nPartition goes through the following process, from power on to booting HP-UX: 1. Power On or Reset The boot process starts when any of the following events occurs: • A partition is reset or rebooted. • The entire server complex is powered on. • Power is turned on for components in the partition (such as cells). 2.
Boot and Reset Overview for nPartitions Boot Process for nPartitions, Cells, and HP-UX DRAFT NOV 2001 HP Restricted / DRAFT 5. Boot-Is-Blocked (BIB) or Partition Rendezvous Each cell either will remain at a boot-is-blocked state (spins at BIB) or will rendezvous with any other available cells in the partition. Cells that remain at BIB are inactive, and cells that rendezvous into the partition are active.
Boot and Reset Overview for nPartitions Boot Process for nPartitions, Cells, and HP-UX DRAFT NOV 2001 HP Restricted / DRAFT 6. Boot Console Handler (BCH) The BCH interface provides the main method for interacting with a partition during its boot process. BCH runs on top of PDC, and it provides menus for getting partition status, for configuring partition boot settings, and for booting HP-UX and rebooting the partition.
Boot and Reset Overview for nPartitions Overview of nPartition Boot Features HP Restricted / DRAFT DRAFT NOV 2001 Overview of nPartition Boot Features This section lists several boot issues particular to HP nPartition servers. Each nPartition is booted, rebooted, shut down, and reset individually. In many situations you can boot and reboot nPartitions using the same basic procedures that are used on other HP servers.
Boot and Reset Overview for nPartitions Overview of nPartition Boot Features HP Restricted / DRAFT DRAFT NOV 2001 • Before powering off a cell, the cell should be inactive; unassigned; or assigned to a partition that either has been shut down and halted or has been reset to a ready for reconfig state. Powering on or powering off an I/O chassis resets the cell to which it is connected (if any). Follow the same guidelines for power cycling I/O chassis that you follow for power cycling cells.
Boot and Reset Overview for nPartitions Tools for Managing nPartition Booting HP Restricted / DRAFT DRAFT NOV 2001 Tools for Managing nPartition Booting HP nPartition servers support the following software tools for booting and resetting nPartitions and for configuring and managing partition boot settings. These tools overlap in some of the functionality they provide, but each has unique capabilities. The primary tools for managing nPartition booting are shown below.
Boot and Reset Overview for nPartitions Tools for Managing nPartition Booting HP Restricted / DRAFT DRAFT NOV 2001 Replying “n” (no, do not stop at ISL) skips the ISL prompt and proceeds to boot HP-UX (/stand/vmunix) on the partition. See the isl (1M) and hpux (1M) manpages for details.
Boot and Reset Overview for nPartitions Configuring and Planning Partition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 Configuring and Planning Partition Boot Settings Each partition has its own collection of boot-related settings that specify which hardware manages the boot process (the core cell), how the boot process proceeds (automatically boot HP-UX, or wait for BCH commands), and whether cells are configured as active cells when the partition boots.
Boot and Reset Overview for nPartitions Configurable Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 Configurable Boot Settings You can configure the following boot settings for each partition. • Boot Device Paths You can set boot device paths to reference the hardware paths where bootable devices reside within the local nPartition.
Boot and Reset Overview for nPartitions Configurable Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 You can stop a partition from automatically booting, and instead access the partition’s BCH interface, by typing a key within ten seconds of the partition booting to BCH. Primary Boot Path: Boot Actions: 0/0/1/0/0.8 Boot from this path. If unsuccessful, go to BCH. Attempting to boot using the primary path.
Boot and Reset Overview for nPartitions Guidelines for Configuring Partition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 When a cell’s use-on-next-boot value is “y” (use the cell), the cell can participate in partition rendezvous and become an active member of the partition, which enables its processors, memory, and any connected I/O to be made available for use by the partition.
Boot and Reset Overview for nPartitions Guidelines for Configuring Partition Boot Settings DRAFT NOV 2001 HP Restricted / DRAFT • Have multiple core cells available within each partition, if possible. In order to have multiple core cell choices, the partition must have at least two cells, each connected to an I/O chassis and core I/O. Having such a configuration provides redundancy and potentially improved system availability.
Boot and Reset Overview for nPartitions Checklist for Booting Partitions HP Restricted / DRAFT DRAFT NOV 2001 Checklist for Booting Partitions Before you boot a partition, check the items listed here. • All cells in the partition that have a “y” use-on-next-boot value should be powered on. If any cells that are set to be used are powered off, the partition will take longer to boot. During partition rendezvous, the partition will wait up to 10 minutes for all cells that are designated to be used.
Boot and Reset Overview for nPartitions Monitoring Partition Boot Activity NOTE HP Restricted / DRAFT DRAFT NOV 2001 Monitoring Partition Boot Activity On HP nPartition servers you can monitor the partition boot process—from power-on or reset to HP-UX start-up—using the Virtual Front Panel (VFP) view of the partition. Each partition has its own VFP that displays details about the partition’s cells and the partition’s boot state and activity.
Boot and Reset Overview for nPartitions Monitoring Partition Boot Activity HP Restricted / DRAFT DRAFT NOV 2001 Skip this step if you are accessing the service processor using a single-partition-user account. Partition VFP’s available: # --0) 1) S) Q) Name ---jules00 jules01 System (all chassis codes) Quit GSP:VFP> 1 Step 3. View the VFP details for information about the partition and its current boot state. To exit the VFP and return to the service processor main menu, type ^b (Control-b).
Boot and Reset Overview for nPartitions Troubleshooting Boot Issues HP Restricted / DRAFT DRAFT NOV 2001 Troubleshooting Boot Issues On HP nPartition servers you might encounter different boot issues than on other HP servers. The following boot issues are possible on nPartition servers. • Problem: Not all cells boot to join (rendezvous) a partition.
Boot and Reset Overview for nPartitions Troubleshooting Boot Issues HP Restricted / DRAFT DRAFT NOV 2001 • Problem: An nPartition does not boot to BCH and instead all cells remain at a boot-is-blocked (BIB) state. Causes: The partition has been reset to a ready for reconfig state, or no valid core cell is available to the partition.
Boot and Reset Overview for nPartitions Boot States and Activities for Partitions and Cells HP Restricted / DRAFT DRAFT NOV 2001 Boot States and Activities for Partitions and Cells On HP nPartition servers, the cell and nPartition boot process proceeds from one boot state to the next; cells and partitions complete various boot activities within each boot state before proceeding to the next boot state.
Boot and Reset Overview for nPartitions Boot States and Activities for Partitions and Cells Table 4-1 HP Restricted / DRAFT DRAFT NOV 2001 Partition State Inactive cells remain at a “Boot Is Blocked (BIB)” state following I/O discovery and do not participate in partition rendezvous.
Boot and Reset Overview for nPartitions Boot States and Activities for Partitions and Cells DRAFT NOV 2001 HP nPartition and Cell Boot States and Activities HP Restricted / DRAFT Table 4-1 Partition State Partition Activity Cell States HPUX Launch Processor system initialization Cell has joined partition HPUX Launch Partition IPL launch configuration Cell has joined partition HPUX Launch Processor display_activity update Cell has joined partition HPUX init process start Cell has joined parti
Boot and Reset Overview for nPartitions Boot States and Activities for Partitions and Cells HP Restricted / DRAFT DRAFT NOV 2001 144 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
5 HP Restricted / DRAFT Procedures for Booting and Resetting nPartitions Boot States and Activities for Partitions and Cells DRAFT NOV 2001 Procedures for Booting and Resetting nPartitions This chapter presents procedures for booting and resetting nPartitions. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Procedures for Booting and Resetting nPartitions Accessing a Partition Console and BCH Interface NOTE HP Restricted / DRAFT DRAFT NOV 2001 Accessing a Partition Console and BCH Interface Each nPartition has its own Boot Console Handler (BCH) interface that provides you a method for interacting with the partition before HP-UX has booted on it. You must access an nPartition’s console and BCH interfaces through the server complex’s service processor (GSP or MP).
Procedures for Booting and Resetting nPartitions Accessing a Partition Console and BCH Interface DRAFT NOV 2001 HP Restricted / DRAFT In most situations you can telnet to the service processor. # telnet sdome-s Trying... Connected to sdome-s.rsn.hp.com. Escape character is ’^]’. Local flow control off GSP login: Accountname GSP password: Welcome to Superdome’s Guardian Service Processor Step 2. Select the Console menu (CO) from the service processor’s Main menu.
Procedures for Booting and Resetting nPartitions Accessing a Partition Console and BCH Interface HP Restricted / DRAFT DRAFT NOV 2001 If using an operator or administrator account, select the partition whose console you wish to access. GSP> CO Partitions available: # --0) 1) Q) Name ---jules00 jules01 Quit Please select partition number: 1 Connecting to Console: jules01 (Use ^B to return to main menu.
Procedures for Booting and Resetting nPartitions Accessing a Partition Console and BCH Interface HP Restricted / DRAFT DRAFT NOV 2001 • When a partition has booted to ISL you can use the EXIT command to exit ISL and return to the partition’s BCH interface. • When a partition has booted HP-UX, in order to access the BCH interface you must reboot HP-UX (shutdown -r) and if necessary interrupt the automatic boot process.
Procedures for Booting and Resetting nPartitions Finding Bootable Devices NOTE BCH HP Restricted / DRAFT DRAFT NOV 2001 Finding Bootable Devices You can search for and find bootable devices for an nPartition by using the BCH interface’s SEARCH command. This command searches for and reports all bootable devices connected to any of the partition’s currently active cells.
Procedures for Booting and Resetting nPartitions Finding Bootable Devices DRAFT NOV 2001 HP Restricted / DRAFT The SEARCH command reports all potential boot devices it locates.
Procedures for Booting and Resetting nPartitions Booting HP-UX on an nPartition BCH HP Restricted / DRAFT DRAFT NOV 2001 Booting HP-UX on an nPartition nPartitions boot and reboot HP-UX independently from each other. You can boot HP-UX on an nPartition using the BCH interface’s BOOT command. Each partition’s BCH interface is available through its console. All nPartition consoles are available from the complex’s service processor (GSP or MP) Console menu.
Procedures for Booting and Resetting nPartitions Booting HP-UX on an nPartition HP Restricted / DRAFT DRAFT NOV 2001 main boot device for the partition. You also can use the SEARCH command to find and list potentially bootable devices for the partition. Main Menu: Enter command or menu > PATH Primary Boot Path: HA Alternate Boot Path: Alternate Boot Path: 0/0/2/0/0.13 0/0/2/0/0.d (hex) 0/0/2/0/0.14 0/0/2/0/0.e (hex) 0/0/2/0/0.0 0/0/2/0/0.0 (hex) Main Menu: Enter command or menu > Step 3.
Procedures for Booting and Resetting nPartitions Booting HP-UX on an nPartition HP Restricted / DRAFT DRAFT NOV 2001 To boot the /stand/vmunix HP-UX kernel from the device without stopping at the ISL prompt, enter n to automatically proceed past ISL. In most situations you will boot /stand/vmunix and not need to stop at ISL. Main Menu: Enter command or menu > BOOT PRI Primary Boot Path: 0/0/1/0/0.
Procedures for Booting and Resetting nPartitions Booting an nPartition to the ISL Prompt NOTE BCH HP Restricted / DRAFT DRAFT NOV 2001 Booting an nPartition to the ISL Prompt When you issue the BCH interface’s BOOT command you can stop an nPartition’s booting at the Initial System Loader (ISL) interface in order to interact with the ISL prompt. To exit ISL and return to the BCH interface, enter the EXIT command at the ISL prompt. For help enter HELP at the ISL prompt.
Procedures for Booting and Resetting nPartitions Booting an nPartition to the ISL Prompt HP Restricted / DRAFT DRAFT NOV 2001 The EXIT command exits ISL and returns to the partition BCH interface, and the HELP command lists all available ISL interface commands. Main Menu: Enter command or menu > BOOT 0/0/2/0/0.13 BCH Directed Boot Path: 0/0/2/0/0.13 Do you wish to stop at the ISL prompt prior to booting? (y/n) >> y Initializing boot Device. ISL Revision A.00.
Procedures for Booting and Resetting nPartitions Booting HP-UX in Single-User or LVM-Maintenance Mode HP Restricted / DRAFT DRAFT NOV 2001 BCH, ISL, and hpux Booting HP-UX in Single-User or LVM-Maintenance Mode On an nPartition you can boot HP-UX in single-user mode or LVM-maintenance mode by specifying options to the Secondary System Loader (hpux).
Procedures for Booting and Resetting nPartitions Booting HP-UX in Single-User or LVM-Maintenance Mode DRAFT NOV 2001 HP Restricted / DRAFT Step 3. From the ISL prompt, issue the appropriate Secondary System Loader (hpux) command to boot the HP-UX kernel in the desired mode. Use the hpux loader to specify the boot mode options and to specify which kernel (such as: /stand/vmunix) to boot on the nPartition.
Procedures for Booting and Resetting nPartitions Booting from an HP-UX Installation Source NOTE BCH HP Restricted / DRAFT DRAFT NOV 2001 Booting from an HP-UX Installation Source You can boot an nPartition from an HP-UX installation source—such as an install CD or an Ignite server—by specifying the install source using the BCH interface’s BOOT command. This allows you to install HP-UX on any of the nPartition’s eligible devices.
Procedures for Booting and Resetting nPartitions Shutting Down HP-UX on an nPartition NOTE HP-UX HP Restricted / DRAFT DRAFT NOV 2001 Shutting Down HP-UX on an nPartition When HP-UX is running on an nPartition, you can shut down HP-UX using either the shutdown command or the reset command. The reboot command does not invoke the shutdown scripts associated with subsystems. The shutdown command invokes the scripts and terminates all running processes in an orderly and cautious manner.
Procedures for Booting and Resetting nPartitions Shutting Down HP-UX on an nPartition DRAFT NOV 2001 HP Restricted / DRAFT • Shut down HP-UX and halt the partition. Issue the shutdown -h command to shut down and halt the partition. This leaves the partition and all its cells in an active state (the partition cannot be reconfigured) after HP-UX shuts down and halts. To reboot the partition you must reset the partition using the GSP command menu’s RS command. • Shut down HP-UX and reboot the partition.
Procedures for Booting and Resetting nPartitions Rebooting or Resetting an nPartition NOTE HP Restricted / DRAFT DRAFT NOV 2001 Rebooting or Resetting an nPartition When you perform a reboot or reset of an nPartition, all active cells in the partition reboot and return to BCH or HP-UX. Any inactive cells in the nPartition are not rebooted in this procedure.
Procedures for Booting and Resetting nPartitions Rebooting or Resetting an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Service Processor This procedure (service processor Command menu RS command) resets (GSP or MP) an nPartition using the service processor. Step 1. Log in to the server complex’s service processor (GSP or MP) and access the Command menu. After logging in to the service processor, enter CM to select the Command menu.
Procedures for Booting and Resetting nPartitions Rebooting or Resetting an nPartition BCH HP Restricted / DRAFT DRAFT NOV 2001 If using an operator or administrator service processor account, you can select which of the server complex’s nPartitions you want to reset. This procedure (BCH interface REBOOT command) resets an nPartition using the partition’s BCH interface. Step 1. Log in to the server complex’s service processor, access the nPartition’s console, and access the BCH Main menu.
Procedures for Booting and Resetting nPartitions Performing a Reboot for Reconfig for an nPartition HP-UX HP Restricted / DRAFT DRAFT NOV 2001 Performing a Reboot for Reconfig for an nPartition During a reboot for reconfig of a partition, the HP-UX command that you issue (shutdown -R) performs the following tasks: 1. Shuts down HP-UX and resets all cells that are assigned to the partition, including any inactive cells. 2. Reconfigures the partition if necessary (adds or removes cells). 3.
Procedures for Booting and Resetting nPartitions Holding a Partition at a Ready for Reconfig State HP Restricted / DRAFT DRAFT NOV 2001 Holding a Partition at a Ready for Reconfig State Resetting an nPartition to a ready for reconfig state performs any changes to the partition’s configuration and holds the partition and all its cells in a boot-is-blocked (inactive) state.
Procedures for Booting and Resetting nPartitions Holding a Partition at a Ready for Reconfig State HP Restricted / DRAFT DRAFT NOV 2001 Service Processor This procedure (Command menu RR command) resets an nPartition to a (GSP or MP) ready for reconfig state from the service processor. Step 1. Log in to the server complex’s service processor and enter CM to access the Command menu. GSP> CM Enter HE to get a list of available commands GSP:CM> Step 2.
Procedures for Booting and Resetting nPartitions Holding a Partition at a Ready for Reconfig State DRAFT NOV 2001 HP Restricted / DRAFT BCH This procedure (RECONFIGRESET command) resets an nPartition to a ready for reconfig state from the partition’s BCH interface. Step 1. Log in to the server complex’s service processor, access the nPartition’s console, and access the BCH interface. From the partition console you access the partition’s BCH interface.
Procedures for Booting and Resetting nPartitions Performing a Transfer-of-Control (TOC) Reset of a nPartition HP Restricted / DRAFT DRAFT NOV 2001 Performing a Transfer-of-Control (TOC) Reset of a nPartition You can use the service processor Command menu’s TC command to perform a transfer-of-control (TOC) reset of an nPartition.
Procedures for Booting and Resetting nPartitions Performing a Transfer-of-Control (TOC) Reset of a nPartition DRAFT NOV 2001 HP Restricted / DRAFT Be certain to correctly select the nPartition to be reset. GSP:CM> TC This command TOCs the selected partition. WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition.
Procedures for Booting and Resetting nPartitions Booting an Inactive nPartition Past Boot-Is-Blocked (BIB) HP Restricted / DRAFT DRAFT NOV 2001 Booting an Inactive nPartition Past Boot-Is-Blocked (BIB) When all cells in an nPartition are at boot-is-blocked, the partition is inactive. This is the case, for example, when an nPartition is held at a ready for reconfig state.
Procedures for Booting and Resetting nPartitions Booting an Inactive nPartition Past Boot-Is-Blocked (BIB) DRAFT NOV 2001 HP Restricted / DRAFT Step 2. From the Command menu, enter the BO command and specify which nPartition is to be booted (released from boot-is-blocked).
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 Listing nPartition Boot Settings You can list an nPartition’s boot-related settings by using the partition’s BCH interface or by using HP-UX commands. To list boot settings for nPartitions you can use the following methods: • BCH on page 173 This procedure (Main menu, Information menu, and Configuration menu BCH commands) lists a partition’s boot settings using the BCH interface.
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 From the partition console you access the partition’s BCH interface. If the partition is not at the BCH interface you must either boot the partition or shut down HP-UX to return to the BCH interface. Step 2. Access the BCH menu that provides the information you want to list.
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings DRAFT NOV 2001 HP Restricted / DRAFT • BCH Information menu From the BCH Main menu, enter IN to access the Information menu. Table 5-3 BOOTINFO BCH Information Menu Boot Settings Displays boot configuration information. Step 3. At the appropriate BCH menu issue the command to display the boot information of interest to you. See the list in the previous step for commands and menus.
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings DRAFT NOV 2001 NOTE HP Restricted / DRAFT HP-UX This procedure (parstatus -V -p# and setboot commands) lists an nPartition’s boot settings using HP-UX commands. Use the parstatus command to list various partition boot settings for any nPartition in a server complex. The setboot command only provides information about the local partition’s PRI and ALT boot paths and PRI boot actions. Step 1.
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 The following example lists detailed information for partition number 0, including the partition’s boot path settings, its core cell information, and its cells’ use-on-next-boot settings.
Procedures for Booting and Resetting nPartitions Listing nPartition Boot Settings HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager The setboot command reports the local partition’s PRI and ALT boot path values, but does not list the HAA boot path. The setboot command also reports the “autoboot” and “autosearch” settings for the PRI boot path. Combined, these two settings are equivalent to the PRI path’s boot actions (its “path flags” setting).
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions HP Restricted / DRAFT DRAFT NOV 2001 Configuring Boot Paths and Boot Actions You can configure each nPartition’s boot paths (device paths for booting HP-UX) and boot actions (preferred automatic boot behavior) by using the following methods: • BCH on page 181 This procedure (BCH Main menu PATH command, and Configuration menu PATHFLAGS command) configures an nPartition’s boot paths and boot actions (path flags) throug
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions DRAFT NOV 2001 HP Restricted / DRAFT • 1—Boot this path, if fail go to BCH. • 2—Boot this path, if fail attempt to perform the next path’s boot action. • 3—Skip this path, attempt to perform the next path’s boot action. By default, all path flags are set to 0 (“Go to BCH”). The boot actions are performed automatically by the BCH interface when an nPartition boots to BCH, as possible and necessary.
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions DRAFT NOV 2001 HP Restricted / DRAFT BCH This procedure (BCH Main menu PATH command, and Configuration menu PATHFLAGS command) configures an nPartition’s boot paths and boot actions (path flags) through its BCH interface. To list all boot path and action settings for an nPartition, you also can use the BCH Information menu’s BOOTINFO command. Step 1.
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions DRAFT NOV 2001 HP Restricted / DRAFT Step 4. Access the BCH Configuration menu by entering CO at the Main menu, and set the boot action for each boot path, as desired, by using the PATHFLAGS command. At the BCH Configuration menu, you can list the path flags (boot actions) for all boot path variables by entering PATHFLAGS with no arguments.
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions HP Restricted / DRAFT DRAFT NOV 2001 You can modify the boot paths for any partition from any other partition in the complex when using the parmodify command. However, when using the setboot command to modify the PRI and ALT paths or the PRI boot action, you can modify only the local partition’s settings. Step 3. Configure boot path settings using the parmodify -p#... command.
Procedures for Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions DRAFT NOV 2001 HP Restricted / DRAFT -b Autoboot setting for the local partition: -b on to automatically boot the PRI path. -b off to not boot PRI. -s Autosearch setting for the local partition: -s on to attempt to perform the HAA path’s boot action when PRI is not booted (either when -b is off, or when PRI fails to boot when -b is on). -s off to never attempt to perform the HAA action.
Procedures for Booting and Resetting nPartitions Configuring Autoboot and Autostart HP Restricted / DRAFT DRAFT NOV 2001 Configuring Autoboot and Autostart The Autoboot setting specifies whether an nPartition automatically boots HP-UX. You can configure each nPartition’s Autoboot setting by modifying the partition’s boot actions for its boot paths. See the Autoboot Configuration section.
Procedures for Booting and Resetting nPartitions Autostart Configuration NOTE HP Restricted / DRAFT DRAFT NOV 2001 This procedure applies to nPartitions on HP Superdome servers only. Step 1. Log in to the Superdome complex’s service processor (GSP), access the nPartition’s console, and access the BCH Configuration menu. From the nPartition console you can access the partition’s BCH interface.
Procedures for Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition CAUTION HP Restricted / DRAFT DRAFT NOV 2001 Configuring Automatic System Restart for a nPartition The automatic system restart feature on nPartition servers enables you to configure an nPartition to be automatically rebooted when HP-UX hangs on the partition. By default automatic system restart is disabled for nPartitions.
Procedures for Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition 129 128 128 HP Restricted / DRAFT DRAFT NOV 2001 The following output shows the chassis codes (with keywords) for an HP-UX timeout and automatic reset.
Procedures for Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition HP Restricted / DRAFT DRAFT NOV 2001 To use the AR command you must be logged in using an account that has administrator authority. GSP:CM> AR This command modifies the automatic system restart configuration of the selected partition. # --0) 1) Name ---feshd5a feshd5b Select a partition number: 0 Automatic system restart for partition 0 is currently enabled.
Procedures for Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition NOTE HP Restricted / DRAFT DRAFT NOV 2001 Configuring Fast Boot Settings (Self Tests) for a nPartition The fast boot settings for an nPartition determine which self tests the partition performs during the power on or partition boot process.
Procedures for Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition DRAFT NOV 2001 HP Restricted / DRAFT BCH This procedure (Configuration menu, FASTBOOT command) configures an nPartition’s fast boot settings using its BCH interface. Step 1. Log in to the server complex’s service processor (GSP or MP), access the partition’s console, and access the BCH Configuration menu. From the partition console you access the partition’s BCH interface.
Procedures for Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition DRAFT NOV 2001 HP Restricted / DRAFT The self test details listed by setboot -v include: TEST—The keyword names of self tests that you can enable or disable. CURRENT—The nPartition’s setting for the test in stable storage: on means the test is normally executed on each boot, off means the test is normally omitted on each boot, partial means some subtests normally are executed on each boot.
Procedures for Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition NOTE HP Restricted / DRAFT DRAFT NOV 2001 HP recommends that all self tests be performed for all nPartitions.
Procedures for Booting and Resetting nPartitions Configuring the Boot Timer for a Partition BCH HP Restricted / DRAFT DRAFT NOV 2001 Configuring the Boot Timer for a Partition The boot timer setting establishes the number of seconds an nPartition will wait for a boot device before timing out. When a boot device does not respond to a boot request within the number of seconds defined by the boot timer setting, the boot is considered unsuccessful.
6 HP Restricted / DRAFT Procedures for Managing nPartitions Configuring the Boot Timer for a Partition DRAFT NOV 2001 Procedures for Managing nPartitions This chapter presents the procedures for creating, configuring, and managing nPartitions on HP servers that support them. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Procedures for Managing nPartitions Listing the Local (Current) Partition Number BCH HP Restricted / DRAFT DRAFT NOV 2001 Listing the Local (Current) Partition Number Each nPartition within a server complex has a unique number assigned to it. This partition number identifies the nPartition in various menus, commands, and utilities. You also can specify the partition number when performing operations on an nPartition, such as adding or removing cells or resetting a partition.
Procedures for Managing nPartitions Listing the Local (Current) Partition Number DRAFT NOV 2001 HP Restricted / DRAFT HP-UX Commands This procedure (parstatus -w) lists the partition number of the local (current) partition from HP-UX. Step 1. Log in to HP-UX running on the nPartition. Step 2. Issue the parstatus -w command to list the partition number for the local partition. # parstatus -w The local partition number is 0.
Procedures for Managing nPartitions Listing All Configured nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Listing All Configured nPartitions You can configure each server complex to have multiple nPartitions, which are composed of cells in the complex.
Procedures for Managing nPartitions Listing All Configured nPartitions DRAFT NOV 2001 HP Restricted / DRAFT Step 2. From the service processor Command menu, enter the CP command to list all configured partitions within the server complex. The CP command lists each partition (by partition number) and indicates which cells from each cabinet are assigned to the partition. In the following example the complex has two partitions: partition number 0 has cells 0 and 2, and partition number 1 has cells 4 and 6.
Procedures for Managing nPartitions Listing All Configured nPartitions HP Restricted / DRAFT DRAFT NOV 2001 The parstatus -P command lists all partitions and shows each partition’s number and name, the number of cells assigned to it, the number of active I/O chassis, and the partition’s active core cell.
Procedures for Managing nPartitions Listing All Configured nPartitions DRAFT NOV 2001 HP Restricted / DRAFT Partition Manager This procedure (viewing the left side of Partition Manager primary window) lists all nPartitions in a server complex using Partition Manager. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. When the Partition Manager starts up the left side of its primary display lists the partitions in the complex.
Procedures for Managing nPartitions Listing Cell nPartition Assignments HP Restricted / DRAFT DRAFT NOV 2001 Listing Cell nPartition Assignments Each cell in an nPartition server complex either is assigned to an nPartition, or it is unassigned (if it is on the “free cell list”, making it an available resource).
Procedures for Managing nPartitions Listing Cell nPartition Assignments DRAFT NOV 2001 HP Restricted / DRAFT HP-UX This procedure (parstatus -C) lists all cells in a server complex and their partition assignments. Step 1. Log in to HP-UX running on one of the server complex’s partitions. Step 2. Issue the parstatus -C command to list all cells, any I/O chassis connections, and any partition assignments for the cells.
Procedures for Managing nPartitions Listing Cell nPartition Assignments HP Restricted / DRAFT DRAFT NOV 2001 window’s right side, or select Available Resources to list all unassigned cells. On the right side of the primary window, for each selected nPartition, Partition Manager lists the cell assignments and any I/O chassis connected to the cells. 204 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Procedures for Managing nPartitions Creating a Genesis Partition HP Restricted / DRAFT DRAFT NOV 2001 Creating a Genesis Partition When you create a Genesis Partition, you establish a one-cell partition on the server complex. The Genesis Partition replaces all other partitions, and once created it is the only partition in the server. The only way to create a Genesis Partition is to use the service processor Command menu’s CC command on the server complex.
Procedures for Managing nPartitions Creating a Genesis Partition HP Restricted / DRAFT DRAFT NOV 2001 If a partition is running HP-UX, you can shut down the partition to a ready for reconfig state by using the shutdown -R -H command. Or you can put an nPartition into a ready for reconfig state by using the BCH interface’s RECONFIGRESET command or using the service processor Command menu’s RR command. Step 4. Log in to the server complex’s service processor (GSP or MP).
Procedures for Managing nPartitions Creating a Genesis Partition HP Restricted / DRAFT DRAFT NOV 2001 not at a ready for reconfig state. If this is the case, go back to Step 3 and ensure all nPartitions are inactive at a ready for reconfig state. Step 7. Issue the BO command to boot the Genesis Partition past its ready for reconfig state and make it an active nPartition.
Procedures for Managing nPartitions Creating a New nPartition HP Restricted / DRAFT DRAFT NOV 2001 Creating a New nPartition In a server complex you can create multiple nPartitions if the server has enough cells and core I/O to support the partitions. You can create a new nPartition by using the following methods: • HP-UX Commands on page 208 This procedure (using the parstatus, parcreate, and parmodify commands) creates and configures a new nPartition from HP-UX.
Procedures for Managing nPartitions Creating a New nPartition HP Restricted / DRAFT DRAFT NOV 2001 For example, the commands performed in steps 2–5 could be replaced with the following parcreate command line. # parcreate -c4:base:y:ri -c6:base:y:ri -P "hostname05" -r0/4 -r0/6 -b 4/0/1/0/0.9 -B Partition Created.
Procedures for Managing nPartitions Creating a New nPartition HP Restricted / DRAFT DRAFT NOV 2001 When using the parcreate command, do not specify the -B option for this procedure. (The -B option causes parcreate to immediately boot the newly created partition past the default ready for reconfig state, thus making the nPartition active and preventing you from further modifying it.
Procedures for Managing nPartitions Creating a New nPartition DRAFT NOV 2001 HP Restricted / DRAFT Step 3. Use the parmodify command to modify the new nPartition’s configuration and set the partition name (-P), boot paths (-b, -s, and -t), and any core cell choices (-r). When using the parmodify command you must use the -p# option to specify the partition number for the nPartition. Use the partition number that the parcreate command reported in Step 2. # parmodify -p1 -P "hostname05" Command succeeded.
Procedures for Managing nPartitions Creating a New nPartition DRAFT NOV 2001 HP Restricted / DRAFT Step 5. Boot your newly created nPartition past boot-is-blocked to make it active and make its BCH interface available. Partition Manager Use the service processor Command menu’s BO command to boot the partition. Once the nPartition is booted, you can access its BCH interface through its console. Use the service processor Console menu (enter CO at the service processor Main menu).
Procedures for Managing nPartitions Creating a New nPartition HP Restricted / DRAFT DRAFT NOV 2001 The following window shows the first step and overview for Partition Manager’s create Partition —> Create Partition action. If you specify for Partition Manager to automatically boot the new nPartition, you can access the new nPartition’s BCH interface from its console when you finish using the create partition task wizard.
Procedures for Managing nPartitions Adding Cells to an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Adding Cells to an nPartition You can add cells to the local nPartition or to any remote nPartitions in the same server complex. Adding cells to an nPartition involves selecting available cells (those not currently assigned to a partition) and assigning them to an existing partition. Both the selected cells and any I/O chassis connected to the cells are assigned to the designated nPartition.
Procedures for Managing nPartitions Adding Cells to an nPartition DRAFT NOV 2001 HP Restricted / DRAFT HP-UX Commands This procedure (using the parstatus and parmodify commands) adds cells to an nPartition using HP-UX commands. Step 1. Use the parstatus -A -C command to list all available cells (the unassigned cells) in the server complex. Step 2. Choose one or more eligible cells from the list to add to the nPartition.
Procedures for Managing nPartitions Adding Cells to an nPartition HP Restricted / DRAFT DRAFT NOV 2001 • When you specify -B to modify an inactive nPartition, the inactive partition completes partition rendezvous and becomes active if possible. • When you specify -B to modify an active nPartition, you must perform a reboot for reconfig of the nPartition before any other cell assignment changes can be made within the server complex.
Procedures for Managing nPartitions Adding Cells to an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Adding the cell(s) to the nPartition should create a configuration that adheres to the hardware requirements and performance guidelines. Step 5. After you add the new cells to the partition’s cell list, click the OK button. The cells are not actually assigned to the nPartition until after the next step. Step 6.
Procedures for Managing nPartitions Removing Cells from an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Removing Cells from an nPartition Removing a cell from an nPartition involves unassigning the cell from the partition to which it is assigned and, if necessary, performing a reboot for reconfig of the nPartition. You can remove any cell from the local nPartition and can remove inactive cells from remote partitions in the same server complex.
Procedures for Managing nPartitions Removing Cells from an nPartition HP Restricted / DRAFT DRAFT NOV 2001 • You must immediately perform a reboot for reconfig of an nPartition when you have removed an active cell from the partition. • 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.
Procedures for Managing nPartitions Removing Cells from an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Specify the partition number (-p#) and each cell (-d#) that you want to remove from the partition. If removing multiple cells from a partition, specify each cell with a separate -d# option on the same command line (such as: parmodify -p1 -d0 -d2... to remove cells 0 and 2 from partition number 1). Slightly different procedures are required for removing active cells and inactive cells.
Procedures for Managing nPartitions Removing Cells from an nPartition HP Restricted / DRAFT DRAFT NOV 2001 modified partition is booted past its inactive ready for reconfig state and becomes an active nPartition. For example, the following command removes cell 2 from partition 0. Because cell 2 is inactive, it is immediately unassigned. # parmodify -p0 -d2 Command succeeded. # Step 3. As needed, perform a reboot for reconfig (shutdown -R) of the partition being modified.
Procedures for Managing nPartitions Removing Cells from an nPartition DRAFT NOV 2001 HP Restricted / DRAFT Step 4. In the Modify Partition window, click the Add/Remove Cells tab. Step 5. Select the cells that you want to remove from the nPartition from the “Cells in the Partition” list, then click the Remove button to move them to the Available Cells list. If removing multiple cells, you can select multiple cells by pressing the Control key while clicking on the cells.
Procedures for Managing nPartitions Removing Cells from an nPartition HP Restricted / DRAFT DRAFT NOV 2001 • When a reboot for reconfig is required, the Notes and Warnings tab also has a check box (“Automatically boot partition”) that—when selected—enables the partition to rendezvous and be active after the reboot for reconfig. To cancel all partition changes, click the Cancel button in the Notes and Warnings window and then click Cancel in the Modify Partition window.
Procedures for Managing nPartitions Removing Cells from an nPartition DRAFT NOV 2001 HP Restricted / DRAFT Step 9. As needed, perform a reboot for reconfig (shutdown -R) of the modified nPartition. • If you have removed only inactive cells from an nPartition, then you do not need to perform a reboot for reconfig of the nPartition.
Procedures for Managing nPartitions Deleting (Removing) an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Deleting (Removing) an nPartition You can delete (remove) any nPartition within a server complex. The HP-UX nPartition deletion capabilities include restrictions for security reasons: you can delete only the local nPartition and inactive remote nPartitions.
Procedures for Managing nPartitions Deleting (Removing) an nPartition HP Restricted / DRAFT DRAFT NOV 2001 remote nPartition, 2) shutting down all applications and warning users, and 3) issuing the shutdown -R -H command. You also can put the partition into a ready for reconfig state by using the BCH interface’s RECONFIGRESET command or the service processor Command menu’s RR command. Step 3. Save all current configuration details about the nPartition you plan to remove.
Procedures for Managing nPartitions Deleting (Removing) an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager When using parremove to remove the local nPartition, you must specify both the -p# option (to specify the local partition number) and the -F option (to force-remove the local partition). Note that the local nPartition remains active following the parremove -F -p# command, until you perform a shutdown for reconfig (shutdown -R -H) to complete the removal.
Procedures for Managing nPartitions Deleting (Removing) an nPartition DRAFT NOV 2001 HP Restricted / DRAFT Step 3. Select the Partition —> Delete Partition action to request that the selected nPartition be removed (deleted). Partition Manager presents the following window to confirm whether you want to delete the selected nPartition. You can view details about the nPartition by clicking the Show Details button, or cancel the deletion by clicking Cancel. Step 4.
Procedures for Managing nPartitions Deleting (Removing) an nPartition HP Restricted / DRAFT DRAFT NOV 2001 Because the Complex Profile will remain locked until the local partition’s removal is completed, no other changes can occur in the server complex until you perform the shutdown for reconfig. After Partition Manager removes an nPartition, the nPartition no longer exists—its configuration information has been deleted.
Procedures for Managing nPartitions Naming and Renaming nPartitions HP Restricted / DRAFT DRAFT NOV 2001 BCH Naming and Renaming nPartitions Each nPartition has both a partition number and a partition name. The partition name for each nPartition can have from 1 to 64 characters, including upper- and lowercase letters; numbers; and dashes, underscores, and spaces (“-” “_” and “ ”). You can customize each partition’s name to help you distinguish among the nPartition in a server complex.
Procedures for Managing nPartitions Naming and Renaming nPartitions DRAFT NOV 2001 HP Restricted / DRAFT If necessary, type ^ecf (Control-e c f) to get write access for the console. Note that if the partition is booted to HP-UX, you should instead use the HP-UX command method of modifying the partition name. Step 3. Access the BCH interface’s Configuration menu. From the Main menu, enter CO to access the Configuration menu.
Procedures for Managing nPartitions Naming and Renaming nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Specify both the partition number (-p#) and the new name for the partition (-P name). If the partition name contains spaces then quotation marks must surround the name. # parmodify -p1 -P "New Name" Command succeeded. # Partition Manager You can list the nPartition’s new name by using the parstatus -p# command or parstatus -P.
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP Restricted / DRAFT DRAFT NOV 2001 Setting and Checking Cell Attributes Each cell assigned to an nPartition has use-on-next-boot and failure usage attributes that determine how the cell is used within the partition.
Procedures for Managing nPartitions Setting and Checking Cell Attributes BCH HP Restricted / DRAFT DRAFT NOV 2001 The reactivate-with-interleave setting allows a cell to actively join its partition following processor or memory failures during the cell’s self tests. The cell joins its partition if at least one processor and any valid amount of memory passes self tests. Any of the cell’s components that fail (processors or memory) are not available to the partition.
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP Restricted / DRAFT DRAFT NOV 2001 To list the use-on-next-boot settings for all cells in the partition, issue the CELLCONFIG command with no arguments.
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP-UX HP Restricted / DRAFT DRAFT NOV 2001 If you have changed any cell from OFF (“n”, do not use on next boot) to ON (“y”, use the cell on next boot) then you must perform these two tasks; this resets and reconfigures the partition and boots it. BCH Configuration Menu: Enter command > RECONFIGRESET Reset the partition for reconfiguration of Complex Profile ...
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP Restricted / DRAFT DRAFT NOV 2001 “Yes” is equivalent to a BCH cell configuration value of ON and “no” is equivalent to OFF. • A failure usage setting of “activate” (equivalent to “ri”) indicates that the cell is set to reactivate with interleave in the event of any failure during the cell’s self test. Use the parstatus -C command to list the use-on-next-boot setting for all cells, which is shown in the “Use On Next Boot” column.
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP Restricted / DRAFT DRAFT NOV 2001 Specify both the -p (partition number) and -m (modify cell) options when using parmodify. The following example modifies cell 2 to not be used the next time its partition (partition number 0) boots. # parmodify -p0 -m2:base:n:ri Command succeeded.
Procedures for Managing nPartitions Setting and Checking Cell Attributes DRAFT NOV 2001 HP Restricted / DRAFT Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. In the Partition Manager primary window, select the nPartition whose cell attributes you want to change. Click the partition’s name in the list on the left side of the primary window to select the nPartition. Step 3.
Procedures for Managing nPartitions Setting and Checking Cell Attributes HP Restricted / DRAFT DRAFT NOV 2001 • If a cell’s use-on-next-boot setting is changed from “no” (do not use) to “yes” (use), you must perform a reboot for reconfig of the cell’s partition by using the shutdown -R command. • Otherwise, if the cell use-on-next-boot settings are only changed from “yes” to “no” then you can perform a standard reboot using the shutdown -r command.
Procedures for Managing nPartitions Setting and Checking nPartition Core Cell Choices NOTE NOTE HP Restricted / DRAFT DRAFT NOV 2001 Setting and Checking nPartition Core Cell Choices The core cell choice settings for an nPartition are optional preferences that establish which cells in the partition are preferred to be selected as the core cell for the partition.
Procedures for Managing nPartitions Setting and Checking nPartition Core Cell Choices DRAFT NOV 2001 HP Restricted / DRAFT BCH This procedure (Configuration menu, COC command) sets the core cell choices for an nPartition using the partition’s BCH interface. Step 1. Access the BCH menu for the nPartition whose core cell choices you wish to set. Step 2. Access the BCH Configuration menu for the partition. From the BCH Main menu, enter CO to enter the Configuration menu. Step 3.
Procedures for Managing nPartitions Setting and Checking nPartition Core Cell Choices HP Restricted / DRAFT DRAFT NOV 2001 The parstatus -V -p# command list detailed status, including the current active core cell (“Core Cell”), and any core cell choice settings (the “Core Cell Alternate” listings, if any).
Procedures for Managing nPartitions Setting and Checking nPartition Core Cell Choices HP Restricted / DRAFT DRAFT NOV 2001 The order in which you list the cells is the order in which the nPartition’s core cell choices are established; the first cell listed is the first preferred core cell (choice 1), and the subsequent cells are lower-priority core cell choices (choices 2 through 4, if specified). Step 3. (Optional.
Procedures for Managing nPartitions Setting and Checking nPartition Core Cell Choices HP Restricted / DRAFT DRAFT NOV 2001 Review any Notes and Warnings that Partition Manager presents, then click OK to proceed or Cancel to cancel the changes. If the cell choice priority changes are implemented, Partition Manager presents a final confirmation that the partition was successfully modified. The new core cell choice priorities will be used the next time the nPartition is rebooted.
Procedures for Managing nPartitions Moving a Cell to a Different nPartition CAUTION HP Restricted / DRAFT DRAFT NOV 2001 Moving a Cell to a Different nPartition To move a cell from one nPartition to another nPartition in the same server complex, use the high-level procedure described here. This high-level procedure involves: 1. Removing (unassigning) the cell from its original nPartition. 2. Performing a reboot for reconfig (shutdown -R) of the original nPartition, if needed. 3.
Procedures for Managing nPartitions Moving a Cell to a Different nPartition HP Restricted / DRAFT DRAFT NOV 2001 You can perform these steps using either HP-UX commands or Partition Manager. Step 1. Refer to the procedure Removing Cells from an nPartition to remove the cell that you want to move to the other nPartition. As part of this step you perform a reboot for reconfig (shutdown -R) of the nPartition to which the cell is originally assigned.
Procedures for Managing nPartitions Restoring a Complex Profile HP Restricted / DRAFT DRAFT NOV 2001 Restoring a Complex Profile You can restore a previous Complex Profile configuration, which effectively allows you to undo your last nPartition configuration change. Restoring the previous Complex Profile allows you to revert to the previous complex configuration—including the nPartition configurations—that existed before you made your last change.
Procedures for Managing nPartitions Restoring a Complex Profile DRAFT NOV 2001 HP Restricted / DRAFT Step 3. Issue the CC command, select Last Complex Profile (L), and confirm that you want to modify the Complex Profile configuration. GSP:CM> CC This command allows you to change the complex profile. WARNING: You must either shut down the OSs for reconfiguration or execute the RR (reset for reconfiguration) command for all partitions before executing this command.
Procedures for Managing nPartitions Restoring a Complex Profile DRAFT NOV 2001 HP Restricted / DRAFT Step 5. Issue the BO command to boot any nPartitions you want to make active. After you use the CC command, all partitions still are in a boot-is-blocked ready for reconfig state and thus are inactive nPartitions. You can use the Command menu’s BO command to boot the partitions past boot-is-blocked to make the partitions active.
7 HP Restricted / DRAFT Listing and Managing Server Hardware Restoring a Complex Profile DRAFT NOV 2001 Listing and Managing Server Hardware This chapter covers the tools and methods for listing details about the hardware assigned to nPartitions. This chapter also covers getting information about server hardware, and managing the hardware resources in nPartitions and their server complexes. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Listing and Managing Server Hardware Tools for Listing and Managing Hardware NOTE HP Restricted / DRAFT DRAFT NOV 2001 Tools for Listing and Managing Hardware You can use several software tools to list server hardware details and manage the hardware in a server complex. These tools have features that overlap for some tasks, but each tool also has unique features.
Listing and Managing Server Hardware Tools for Listing and Managing Hardware DRAFT NOV 2001 HP Restricted / DRAFT • Partition Manager ( /opt/parmgr/bin/parmgr) Partition Manager provides a graphical interface for managing and monitoring partitions and hardware within a server complex. Hardware management features include menus and windows that list details about cells, I/O chassis, and PCI I/O card slots in the server complex.
Listing and Managing Server Hardware Powering Server Cabinets On and Off CAUTION CAUTION HP Restricted / DRAFT DRAFT NOV 2001 Powering Server Cabinets On and Off You can power on and power off the cabinets within a server complex either by using the main power switch on the front of the cabinet, or by using the service processor Command menu.
Listing and Managing Server Hardware Powering Server Cabinets On and Off HP Restricted / DRAFT DRAFT NOV 2001 Cabinet Power Switch Changes in cabinet power status do not affect the standby power that supplies system utilities such as the service processor (GSP or MP) and keeps some fans running. These utilities and fans can receive power as long as standby power is enabled. The way in which standby power is enabled and disabled differs for various HP server models.
Listing and Managing Server Hardware Powering Server Cabinets On and Off DRAFT NOV 2001 HP Restricted / DRAFT Service Processor This procedure (Virtual Front Panel, and Command menu’s PE (GSP or MP) command) turns a cabinet’s 48-volt power on or off using the service processor. Step 1. Log in to the system’s service processor and access the Virtual Front Panel for the system.
Listing and Managing Server Hardware Powering Server Cabinets On and Off HP Restricted / DRAFT DRAFT NOV 2001 When using the PE command enter B to power on or off a cabinet; specify the cabinet number; and then enter ON (power on), OFF (power off), or Q (quit without changing the power status). GSP:CM> PE This command controls power enable to a hardware device. B - Cabinet C - Cell I - IO Chassis Select Device: b Enter cabinet number: 1 The power state is ON for Cabinet 1.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off NOTE HP Restricted / DRAFT DRAFT NOV 2001 Powering Cells and I/O Chassis On and Off This section covers cell and I/O chassis power management procedures, which allow you to control power for cells and I/O chassis from remote locations, without physically accessing the system hardware.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off HP Restricted / DRAFT DRAFT NOV 2001 I/O chassis. The PE command does not check the current usage of components. Service Processor This procedure (Command menu, PE command) powers on and powers off (GSP or MP) cells, I/O chassis, and cabinets using the service processor interface.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off HP Restricted / DRAFT DRAFT NOV 2001 • I/O Chassis—When you power off an I/O chassis from the service processor Command menu, the system firmware resets the cell attached to the I/O chassis (if the cell located and mapped the I/O chassis during its cell boot process). When specifying an I/O chassis, you indicate the cabinet, bay, and chassis numbers to identify it.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off HP Restricted / DRAFT DRAFT NOV 2001 To manage a cell’s power you must log in to the partition to which the cell is assigned. If the cell is not assigned to a partition, you can manage its power from any partition. Step 2. Use the frupower command to turn on or turn off the cell’s power. Specify the frupower -f -c# command to power off a cell. (-c#). This also powers off any I/O chassis connected to the cell.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off HP Restricted / DRAFT DRAFT NOV 2001 To power on or off an I/O chassis using Partition Manager, do so by power cycling the cell to which it is connected. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. Select the partition that contains the cell you want to power on or off. Partitions are listed on the left side of the Partition Manager primary window.
Listing and Managing Server Hardware Determining Hardware Power Status NOTE HP Restricted / DRAFT DRAFT NOV 2001 Determining Hardware Power Status You can use system software to check power status for the following components from remote locations: • Cabinets • Bulk Power Supplies and Power Boards • Cell Boards • I/O Chassis • Individual PCI Slots Cabinet power details and power supply details are specific to each server model.
Listing and Managing Server Hardware Determining Hardware Power Status HP Restricted / DRAFT DRAFT NOV 2001 Service Processor This procedure (Command menu, PS command) checks power status for (GSP or MP) cabinets, bulk power supplies and power boards, cells, and core I/O using the service processor. Step 1. Log in to the system’s service processor and enter CM to access the Command menu. Step 2. Issue the service processor Command menu’s PS command.
Listing and Managing Server Hardware Determining Hardware Power Status HP Restricted / DRAFT DRAFT NOV 2001 • Core I/O Card Power—Whether power is enabled and on for all core I/O cards within the cabinet. For system complexes that have multiple cabinets, you must check details for each cabinet separately. You also can use the PS command to check individual cell (C) or core I/O (I) hardware and power status.
Listing and Managing Server Hardware Determining Hardware Power Status HP Restricted / DRAFT DRAFT NOV 2001 To check the power status for PCI card slots, you must log in to the local partition where their PCI card cage resides. You can check the power status for cabinets, cells, and I/O chassis from any partition. Step 2. Issue the HP-UX commands to check the power status for the system components of interest to you.
Listing and Managing Server Hardware Determining Hardware Power Status DRAFT NOV 2001 HP Restricted / DRAFT # parstatus -V -b0 [Cabinet] Cabinet Blowers OK/ Cab Failed/ Num Cabinet Type N Status === ============ ========= 0 SD32000 4/ 0/ N+ I/O Fans OK/ Failed/ N Status ========= 5/ 0/ ? Bulk Power Supplies OK/ Failed/ N Status ========== 5/ 0/ N+ Backplane Power Boards OK/ Failed/ N Status ============ 3/ 0/ N+ GSP ====== active Cabinet Power Bulk Power Supplies(BPS) ======================== Power
Listing and Managing Server Hardware Determining Hardware Power Status HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager This procedure (Complex —> Show Complex Details menu) lists system hardware power status using Partition Manager. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. Select the Complex —> Show Complex Details menu item.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off NOTE HP Restricted / DRAFT DRAFT NOV 2001 Turning Attention Indicators (LEDs) On and Off HP’s nPartition systems provide attention indicators (LEDs) to help you to visually select and confirm which hardware you want to perform operations on. Attention indicators are amber (orange) lights. Table 7-1 on page 270 lists attention indicator meanings and LED states (off, blinking, and on).
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off Table 7-1 HP Restricted / DRAFT DRAFT NOV 2001 Table 7-1 lists the meanings for the various attention indicator states. When all of a system’s components are functioning, and no service operations are occurring, every attention indicator should be turned off. (HP Superdome cabinet number LCDs remain lit or blinking when cabinet power is on.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off NOTE HP Restricted / DRAFT DRAFT NOV 2001 • Cabinet Number—On HP Superdome servers only, each cabinet has a cabinet number LCD that serves as the cabinet’s attention indicator. The cabinet “attention” light on HP Superdome and HP rp8400 servers is not user-controllable.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off HP Restricted / DRAFT DRAFT NOV 2001 — Turn Off: The fruled -f -i#/#/# command turns off the attention indicator for the specified I/O chassis (-i#/#/#). To turn off all I/O chassis attention indicators use the fruled -f -I command. — Blink: The fruled -o -i#/#/# command blinks the attention indicator for the specified I/O chassis (-i#/#/#).
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off HP Restricted / DRAFT DRAFT NOV 2001 The following example turns off and blinks various attention indicators on an HP Superdome system, including cell, I/O chassis, PCI slot, and cabinet LEDs. # fruled -f -C # fruled -f -I Turn off all cell and I/O chassis attention # fruled -o -c0 -c2 -c4 # fruled -o -i0/0/1 -i0/0/3 # fruled -o -b0 Blink attention indicators for cells 0, 2, and 4 and I/O chassis 0/0/1 and 0/0/3.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off HP Restricted / DRAFT DRAFT NOV 2001 This menu item blinks the selected cell’s attention indicator. On HP Superdome servers this also blinks the cabinet number LCD for the cabinet in which the cell resides. • I/O Chassis—Select the I/O chassis in Partition Manager’s primary window, then select the I/O —> Light I/O Chassis LED menu item.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations HP Restricted / DRAFT DRAFT NOV 2001 Listing Cell Processor and Memory Configurations You can determine the processor and memory configurations for cells in a server complex by using software tools and utilities.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations HP Restricted / DRAFT DRAFT NOV 2001 The PS command reports details for the cell including its processor configuration (CPU population) and its memory configuration (DIMM population). For the cell memory configuration details, the PS command displays each populated DIMM and identifies it using its rank notation (0A–0D, 1A–1D, and so on).
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations HP Restricted / DRAFT DRAFT NOV 2001 Using the BCH interface, you can check these details only for the active cells in the local partition. Step 1. Access the BCH interface for the partition to which the cell is assigned, and access the BCH Information menu. From the BCH Main menu, enter IN to access the BCH Information menu. (If you are not at the BCH Main menu, enter MA to go to the Main menu.) Step 2.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations DRAFT NOV 2001 HP Restricted / DRAFT Information Menu: Enter command > PR PROCESSOR INFORMATION Cell ---4 6 Cab/ Slot ---0/4 0/6 CPU --0 1 2 3 0 1 2 3 Speed -------552 MHz 552 MHz 552 MHz 552 MHz 552 MHz 552 MHz 552 MHz 552 MHz HVERSION -------0x5c70 0x5c70 0x5c70 0x5c70 0x5c70 0x5c70 0x5c70 0x5c70 SVERSION -------0x0491 0x0491 0x0491 0x0491 0x0491 0x0491 0x0491 0x0491 CVERSION -------0x0301 0x0301 0x0301 0x0301
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations HP Restricted / DRAFT DRAFT NOV 2001 HP-UX Commands This procedure (parstatus command, with various options) lists cell processor and memory configurations from HP-UX. You can check these details for any cell in the complex. Step 1. Log in to HP-UX running on any of the system’s partitions. You can list processor and memory details from any partition. Step 2.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations HP Restricted / DRAFT DRAFT NOV 2001 # parstatus -V -c0 [Cell] Hardware Location Global Cell Number Actual Usage Normal Usage Connected To Core Cell Capable Firmware Revision Failure Usage Use On Next Boot Partition Number Partition Name The following example shows the parstatus -V -c0 command’s output. This presents detailed processor and memory info for cell 0 in cabinet 0.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory HP Restricted / DRAFT DRAFT NOV 2001 BCH Deconfiguring Cells, Processors, and Memory You can deconfigure (make inactive) a cell that is assigned to a partition by setting its use-on-next-boot value to “n” (do not use). This causes the cell to remain assigned to the partition, but the cell will be inactive the next time its partition boots, meaning the cell’s resources will not be used.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory DRAFT NOV 2001 HP Restricted / DRAFT Step 2. To change cell or processor configurations access the Configuration menu, or to change memory configurations access the Service menu. To access the Configuration menu enter CO at the BCH interface’s main menu. To access the Service menu enter SER. Step 3. Configure or deconfigure the cell, processors, or memory. You cannot deconfigure the last cell, processor, or DIMM rank.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory HP Restricted / DRAFT DRAFT NOV 2001 DIMMDEALLOC cell dimm OFF deconfigures the specified DIMM (dimm) on the cell (cell) indicated. DIMMDEALLOC cell dimm ON configures the specified DIMM on the cell. For example, DIMMDEALLOC 0 1B OFF sets DIMM 1B on cell 0 to be deallocated the next time the partition boots, and as a result all other DIMMs in the same rank (1A, 1C, and 1D) also will not be used.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager The shutdown -R command performs a reboot for reconfig for the partition, which allows all cells to reboot, including any currently inactive cells in the partition. This procedure (Partition —> Modify Partition menu, Change Cell Attributes tab) configures and deconfigures (makes inactive) cells using Partition Manager. Step 1.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number HP Restricted / DRAFT DRAFT NOV 2001 Listing the Server Product Number and Serial Number You can list the product number and the serial number for your server complex by using software commands and utilities.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number DRAFT NOV 2001 HP Restricted / DRAFT Step 3. Type n (or type q) to not modify the system complex information that was displayed. 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. GSP modifiable stable complex configuration data fields.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number DRAFT NOV 2001 HP Restricted / DRAFT Partition Manager This procedure (Complex —> Show Complex Details menu) lists the system complex’s product and serial numbers using Partition Manager. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. Select the Complex —> Show Complex Details menu item.
Listing and Managing Server Hardware Checking Blower and Fan Status NOTE HP Restricted / DRAFT DRAFT NOV 2001 Checking Blower and Fan Status You can remotely check the operating status of a server complex’s blowers and fans by using software commands and utilities. Different HP server and cabinet models have different blower and fan configurations.
Listing and Managing Server Hardware Checking Blower and Fan Status HP Restricted / DRAFT DRAFT NOV 2001 HP-UX Commands This procedure (parstatus -B or parstatus -V -b#) lists the status of blowers and fans from HP-UX. Step 1. Log in to HP-UX running on any of the system’s nPartitions. You can check blower and fan details from HP-UX running on any partition. Step 2. Issue the parstatus -B or parstatus -V -b# command. The parstatus -B command gives a brief summary of all cabinets including fan status.
Listing and Managing Server Hardware Checking Blower and Fan Status DRAFT NOV 2001 HP Restricted / DRAFT Partition Manager This procedure (Complex —> Show Complex Details menu, Power/Cooling tab) lists fan status from Partition Manager. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. Select the Complex —> Show Complex Details menu item. This displays the Complex Details window. Step 3.
Listing and Managing Server Hardware Analyzing a Server Complex’s Health HP Restricted / DRAFT DRAFT NOV 2001 Partition Manager Analyzing a Server Complex’s Health You can quickly check for hardware problems in an nPartition server by using Partition Manager’s “Analyze Complex Health” feature. This feature scans the server complex and uses problem detectors to check the operating status of cells, I/O chassis, fans and blowers, and power supplies.
Listing and Managing Server Hardware Listing the Cabinets in a Server Complex HP Restricted / DRAFT DRAFT NOV 2001 Listing the Cabinets in a Server Complex You can list all cabinets in a server complex by using software commands and utilities, which allow you to determine the complex’s cabinet configuration from a remote location.
Listing and Managing Server Hardware Listing the Cabinets in a Server Complex DRAFT NOV 2001 HP Restricted / DRAFT HP-UX Commands This procedure (parstatus -B or parstatus -V -b#) lists cabinet details from HP-UX. Step 1. Log in to HP-UX running on any of the server’s partitions. You can list cabinet information from any partition. Step 2. Issue the parstatus -B command and option to list all cabinets and their current status.
Listing and Managing Server Hardware Listing the nPartitions in a Server HP Restricted / DRAFT DRAFT NOV 2001 Listing the nPartitions in a Server You can list details about the nPartitions defined in a server complex, including the partition numbers, partition names, and the cells assigned to the partitions. You can perform this procedure using the following methods: • Service Processor (GSP or MP) on page 294 This procedure (Command menu, CP command) lists all nPartitions using the service processor.
Listing and Managing Server Hardware Listing the nPartitions in a Server DRAFT NOV 2001 HP Restricted / DRAFT HP-UX Commands This procedure (parstatus -P) lists a server’s nPartitions from HP-UX. Step 1. Log in to HP-UX running on any of the server’s partitions. You can list all partitions from any partition in the server. Step 2. Issue the parstatus -P command and option to list all nPartitions and their current status.
Listing and Managing Server Hardware Naming or Renaming a Server Complex NOTE HP Restricted / DRAFT DRAFT NOV 2001 Naming or Renaming a Server Complex You can assign a name for each server complex in order to better identify the complex as you work with it. Several commands and utilities display the server complex name as part of their output and interfaces. For example, some nPartition commands and Partition Manager list the complex name.
Listing and Managing Server Hardware Naming or Renaming a Server Complex HP Restricted / DRAFT DRAFT NOV 2001 The ID command lists some of the current server complex’s “stable complex configuration” data, 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. GSP modifiable stable complex configuration data fields.
Listing and Managing Server Hardware Checking for Power Supply Failures HP Restricted / DRAFT DRAFT NOV 2001 Checking for Power Supply Failures From remote locations you can check the operating status of power supplies by using software commands and utilities. Different HP server and cabinet models have different supply requirements and configurations.
Listing and Managing Server Hardware Checking for Power Supply Failures HP Restricted / DRAFT DRAFT NOV 2001 detailed power status for a specific cabinet (-b#) whose details you want to view. • The parstatus -B command summarizes the power status for all cabinets in the system complex. • The parstatus -V -b# command displays a detailed status (“ok” or “failed”) for all power supplies in the specified cabinet (-b#).
Listing and Managing Server Hardware Checking for Power Supply Failures DRAFT NOV 2001 HP Restricted / DRAFT Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. Select the Complex —> Show Complex Details menu item. This displays the Complex Details window. Step 3. Click the Power/Cooling tab to bring up the panel that contains information about the status of the power supplies in the complex.
Listing and Managing Server Hardware Checking for Memory DIMM Failures HP Restricted / DRAFT DRAFT NOV 2001 Checking for Memory DIMM Failures You can list cell memory configurations and check for memory DIMM failures using software tools and utilities. You can perform this procedure using the following methods: • HP-UX Commands on page 301 This procedure (parstatus -V -c#) lists a cell’s memory status, including any DIMM failures, from HP-UX.
Listing and Managing Server Hardware Checking for Memory DIMM Failures HP Restricted / DRAFT DRAFT NOV 2001 In the example that follows, eight DIMMs (0A–0D and 1A–1D) are installed and are available (“ok”) for use by the cell’s partition.
Listing and Managing Server Hardware Checking for Memory DIMM Failures DRAFT NOV 2001 HP Restricted / DRAFT Partition Manager This procedure (Cell —> Show Cell Details menu, CPUs/Memory tab) lists a cell’s memory status, including any DIMM failures, from Partition Manager. Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2.
Listing and Managing Server Hardware Checking for Processor Failures HP Restricted / DRAFT DRAFT NOV 2001 Checking for Processor Failures You can list cell processor configuration, including any processor failures, using software tools and utilities. You can perform this procedure using the following methods: • HP-UX Commands on page 304 This procedure (parstatus -V -c#) lists a cell’s processor status, including any failures, from HP-UX.
Listing and Managing Server Hardware Checking for Processor Failures HP Restricted / DRAFT DRAFT NOV 2001 Any processors listed as “failed” either have failed self-tests or have been software deconfigured by the Boot Console Handler (BCH) Configuration menu’s CPUCONFIG command.
Listing and Managing Server Hardware Checking for Processor Failures HP Restricted / DRAFT DRAFT NOV 2001 306 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
8 HP Restricted / DRAFT HP Instant Capacity on Demand (iCOD) for nPartitions Checking for Processor Failures DRAFT NOV 2001 HP Instant Capacity on Demand (iCOD) for nPartitions This chapter covers using Hewlett-Packard’s iCOD (Instant Capacity on Demand) product on nPartitions. iCOD is an optional product that enables you to instantly increase or adjust processing power within nPars. As you need more or fewer processors, you use iCOD tools to adjust the number of activated processors in the nPartition.
HP Instant Capacity on Demand (iCOD) for nPartitions Introduction to iCOD on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Introduction to iCOD on nPartitions HP’s iCOD product is available for both nPartition servers and non-partitionable HP servers. This document covers iCOD issues that are unique to nPartition systems. See the Instant Capacity on Demand (iCOD) and Pay Per Use (PPU) User’s Guide for complete information about iCOD on all supported platforms.
HP Instant Capacity on Demand (iCOD) for nPartitions New iCOD Issues for Managing nPartitions HP Restricted / DRAFT DRAFT NOV 2001 While there is one iCOD license for the entire server complex, iCOD processors are activated and deactivated independently for each nPar. Each nPar has its own settings for iCOD contact, notification, and processor configuration purposes. • Passwords are not required for activating and deactivating iCOD processor on nPartitions.
HP Instant Capacity on Demand (iCOD) for nPartitions New iCOD Issues for Managing nPartitions HP Restricted / DRAFT DRAFT NOV 2001 However, if the number of active cells is greater than the number of “requested active processors” then the iCOD software activates more processors than were requested: one processor is activated for each active cell in the nPar. • Only processors on active cells can be activated by iCOD. Inactive cells in an nPar cannot have processors activated by iCOD in the nPar.
HP Instant Capacity on Demand (iCOD) for nPartitions New iCOD Issues for Managing nPartitions HP Restricted / DRAFT DRAFT NOV 2001 When not enough processors are configured, the iCOD software activates as many processors as possible and the number of activated processors is less than the number of “requested active processors”. Other sections in this publication provide more iCOD details. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Instant Capacity on Demand (iCOD) for nPartitions Tools for Managing iCOD Processors HP Restricted / DRAFT DRAFT NOV 2001 Tools for Managing iCOD Processors The HP Instant Capacity on Demand (iCOD) product includes the following commands for managing iCOD settings and processor configurations. This same set of commands is used for both the iCOD Purchase and iCOD Utility products. For details on these commands refer to the icod_modify (1M), icod_notify (1M), and icod_stat (1M) manpages.
HP Instant Capacity on Demand (iCOD) for nPartitions Tools for Managing iCOD Processors HP Restricted / DRAFT DRAFT NOV 2001 iCOD for all nPars in the server, and only one license is needed for the entire complex. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
HP Instant Capacity on Demand (iCOD) for nPartitions iCOD Requirements for nPartition Servers NOTE HP Restricted / DRAFT DRAFT NOV 2001 iCOD Requirements for nPartition Servers HP’s iCOD software has the following requirements and restrictions for using and managing iCOD processors in an nPartition server complex. • Each nPartition server complex can optionally be under either an iCOD Purchase contract or a pay per use (iCOD Utility) contract.
HP Instant Capacity on Demand (iCOD) for nPartitions iCOD Requirements for nPartition Servers HP Restricted / DRAFT DRAFT NOV 2001 • Only configured processors on active cells that are assigned to an nPartition can be activated by iCOD software. Processors that are deconfigured cannot be activated by iCOD; they first must be configured (for example, by using the BCH Configuration menu’s CPUCONFIG command). Cells that are inactive cannot have processors activated by iCOD.
HP Instant Capacity on Demand (iCOD) for nPartitions Installing and Configuring iCOD on nPartitions NOTE HP Restricted / DRAFT DRAFT NOV 2001 Installing and Configuring iCOD on nPartitions This section describes iCOD software install and configuration for an nPartition server complex. You also must establish a contract with HP for either iCOD Purchase or iCOD Utility (pay per use) to properly use this software product.
HP Instant Capacity on Demand (iCOD) for nPartitions Installing and Configuring iCOD on nPartitions DRAFT NOV 2001 HP Restricted / DRAFT Step 3. Configure sendmail so that it can send e-mail to an HP mail server that is outside of your company’s firewall. HP iCOD software sends encrypted e-mail from the local nPar running iCOD to HP for billing purposes and to request licensing information. Details on sendmail configuration are in the user’s guide for iCOD.
HP Instant Capacity on Demand (iCOD) for nPartitions Installing and Configuring iCOD on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 To list iCOD configuration details for the local nPartition, use the icod_stat command (with no options). For an nPar complex that has iCOD Purchase configured for multiple nPars, you also can use the icod_stat -p command to display iCOD processor usage statistics for all nPars in the server complex.
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Procedures for Changing iCOD Configurations on nPartitions This section covers the following procedures for changing the iCOD configuration on nPartitions. These procedures apply for both iCOD Purchase and iCOD Utility software and contracts. • Activating and Deactivating Processors with iCOD on page 320 This procedure (using the icod_modify -a...
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions DRAFT NOV 2001 NOTE HP Restricted / DRAFT Activating and Deactivating Processors with iCOD This procedure (using the icod_modify -a... or icod_modify -d... command) activates or deactivates processors in an nPar with iCOD. Activating or deactivating processors can affect your billing for iCOD services.
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions DRAFT NOV 2001 HP Restricted / DRAFT # icod_modify -a 2 "two CPUs added":Ann:Joe:jdoe@comp.com:555-5555 In the next example, one processor is deactivated (-d 1): # icod_modify -d 1 "one less CPU":Ann:Joe:jdoe@comp.com:555-5555 See also the icod_modify (1M) manpage for details. Step 3.
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 activated processors in the nPar (depending on the number of processors available before the command is issued). # icod_modify -s 10 "activate 10 CPUs total":Ann:Joe:jdoe@comp.com:555-5555 See also the icod_modify (1M) manpage for details. Step 3.
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 If HP processor set (Pset) software is installed, deactivating processors removes the corresponding CPU IDs from the Pset to which they were assigned. Step 2. Login to the second nPartition and activate the same number of processors you deactivated in the previous step.
HP Instant Capacity on Demand (iCOD) for nPartitions Procedures for Changing iCOD Configurations on nPartitions DRAFT NOV 2001 HP Restricted / DRAFT Removing iCOD Software and Functionality from nPars This procedure describes how to remove iCOD software and functionality from an nPar server complex after completing your iCOD purchasing and contract obligations. For more details see the Instant Capacity on Demand (iCOD) and Pay Per Use (PPU) User’s Guide. Step 1.
HP Instant Capacity on Demand (iCOD) for nPartitions Managing iCOD Utility (Pay Per Use) on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Managing iCOD Utility (Pay Per Use) on nPartitions This section describes several methods of managing processor resources for a server complex that is under a pay per use (iCOD Utility) contract. If your server complex is under an iCOD Utility contract then you are billed for all activated processors in the whole nPar server complex.
HP Instant Capacity on Demand (iCOD) for nPartitions Managing iCOD Utility (Pay Per Use) on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Deactivated Processors Inactive Processors When an nPar is inactive all its cells and processors are inactive and cannot be used until the nPar is booted (using the GSP or MP Command menu’s BO command). • Individual cells that are inactive are not billed for iCOD Utility purposes, because all processors on inactive cells also are inactive.
HP Instant Capacity on Demand (iCOD) for nPartitions Managing iCOD Utility (Pay Per Use) on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 Deconfigured Processors To put an nPar in an inactive, ready for reconfig state: if HP-UX is running use the shutdown -R -H command, or if at the Boot Console Handler (BCH) interface use the RECONFIGRESET command. None of an inactive cell’s resources (processors, memory, or any I/O connected to the cell) are available for use in an nPartition.
HP Instant Capacity on Demand (iCOD) for nPartitions Managing iCOD Utility (Pay Per Use) on nPartitions HP Restricted / DRAFT DRAFT NOV 2001 328 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
9 HP Restricted / DRAFT Processor Sets (Psets) on nPartitions Managing iCOD Utility (Pay Per Use) on nPartitions DRAFT NOV 2001 Processor Sets (Psets) on nPartitions This chapter describes how to use and manage processor sets (Psets) on nPartition systems. Using Psets, you can create multiple independent processor groups in an nPar. Each Pset has its own processors and attributes. Because Psets are dynamic, you can create, modify, and destroy Psets instantly as your system needs demand.
Processor Sets (Psets) on nPartitions Introduction to Psets HP Restricted / DRAFT DRAFT NOV 2001 Thread and Process Pset Bindings Introduction to Psets HP’s processor set (Pset) product is an optional software package that runs on any HP-UX 11i system, including all nPartition servers. The Pset software package is free and is available from the http://software.hp.com Web site. Each processor set (Pset) is a group of active processors that functions as an independent scheduling allocation domain.
Processor Sets (Psets) on nPartitions Introduction to Psets DRAFT NOV 2001 HP Restricted / DRAFT HP-UX Processor Numbering and Availability on nPars The HP-UX operating system number processors from 0 to n-1, where n is the number of configured processors on active cells in an nPartition. Each physical processor is not necessarily given the same logical HP-UX processor ID each time the nPar is booted. HP-UX processor IDs are assigned on a first-come first-numbered basis.
Processor Sets (Psets) on nPartitions Introduction to Psets HP Restricted / DRAFT DRAFT NOV 2001 The System Default Pset Pset Attributes and Access Permissions Locality Domain Count: 1 Processor Count : 5 Domain -----0 # Processors ---------0 3 4 7 8 When Pset software is installed, a system default Pset always exists that gives all users access to the processors assigned to it. The default Pset is Pset 0, which always has at least processor ID 0 assigned to it.
Processor Sets (Psets) on nPartitions Introduction to Psets DRAFT NOV 2001 HP Restricted / DRAFT Pset Binding and Inheritance Using PRM on nPars with Psets Child threads and processes inherit the Pset bindings of their parents. So, for example, when a process creates child processes, the children are are launched into the same Pset as the parent. By using the Pset programming interface you can have more control over the Pset locations where threads and processes are spawned and run.
Processor Sets (Psets) on nPartitions Table of Pset Management Tasks Table 9-1 Task HP Restricted / DRAFT DRAFT NOV 2001 Table of Pset Management Tasks This section lists only the psrset command-line procedures for managing Psets. Common Pset tasks are given in Table 9-1. Also see the psrset (1M) manpage for details, or refer to the section with Pset examples for command output and examples.
Processor Sets (Psets) on nPartitions Table of Pset Management Tasks DRAFT NOV 2001 Task Processor Set (Pset) Management Tasks HP Restricted / DRAFT Table 9-1 Commands Assigning (reassigning) processors to Psets /usr/sbin/psrset -a pset_id processor_list where pset_id is the Pset to which the processors specified in processor_list are assigned.
Processor Sets (Psets) on nPartitions Table of Pset Management Tasks DRAFT NOV 2001 Task Processor Set (Pset) Management Tasks HP Restricted / DRAFT Table 9-1 Commands Setting Pset access permissions Use the psrset command’s -t option, as described in Configuring Pset attribute values in this table. To configure access permissions (OWNID, GRPID, PERM) you must have root or superuser access or membership in a group that has PSET privileged capabilities.
Processor Sets (Psets) on nPartitions Table of Pset Management Tasks DRAFT NOV 2001 Task Processor Set (Pset) Management Tasks HP Restricted / DRAFT Table 9-1 Commands Binding threads and processes to a Pset /usr/sbin/psrset -b pset_id pid_list where pset_id is the Pset in which the specified process IDs (pid_list) will be bound. The user issuing this command must have execute permission for both the original and new Psets in which the process ID executes.
Processor Sets (Psets) on nPartitions Tools for Managing and Using Psets HP Restricted / DRAFT DRAFT NOV 2001 Tools for Managing and Using Psets This section lists several tools for managing Psets. For details refer to these manpages: psrset (1M), xprm (1), prmconfig (1), mpsched (1), rtsched (1), sar (1M), setprivgrp (1M), and getprivgrp (1). • /usr/sbin/psrset This command provides the main command-line interface for Psets.
Processor Sets (Psets) on nPartitions Tools for Managing and Using Psets HP Restricted / DRAFT DRAFT NOV 2001 To remove privileged capabilities for a group, issue the setprivgrp command with no capabilities specified (for example: setprivgrp mygrp). The getprivgrp command reports privileged capabilities for the user issuing the command. HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets NOTE HP Restricted / DRAFT DRAFT NOV 2001 Example 9-1 Examples: Sample Uses of Psets These examples show the use of processor sets (Psets) on an HP Superdome server that also has HP Instant Capacity on Demand (iCOD) “pay per use” software installed. Uses of the optional HP iCOD software commands are noted in the text accompanying the examples. Refer to the chapter on iCOD for iCOD management information.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets HP Restricted / DRAFT DRAFT NOV 2001 The icod_modify command sets the total number of processors to four. As the psrset -i command shows, this reduces the number of processors that are available and assigned to Psets. Note that processor IDs (listed in the SPU_LIST) are not sequentially numbered because several processors have been deactivated by the iCOD software. # icod_modify -s 4 "set to 4":Ann:Joe:jdoe@comp.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 # 3 755 ALLOW DFLTPSET FAIL DFLTPSET HP Restricted / DRAFT GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU Example 9-2 Destroying a Pset and Reassigning Processors List the local nPar’s Pset configuration using the psrset -i command. There are three Psets: the default Pset 0, Pset 10, and Pset 11.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets # HP Restricted / DRAFT DRAFT NOV 2001 Destroy Pset 10 because it is no longer needed. Its processors (9, 10, and 11) are assigned back to the default processor set (Pset 0). Then list the new Pset configurations using the psrset -i command.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU # FAIL DFLTPSET HP Restricted / DRAFT EMPTY LASTSPU Example 9-3 11 4 5 0 3 755 ALLOW DFLTPSET FAIL DFLTPSET 7 8 9 Running and Binding Programs in Psets List the current Pset configuration for the local nPar. Two Psets are configured: Pset 0 and Pset 2. Note that processor ID 10 is not active in this nPartition (because iCOD software has deactivated it).
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets HP Restricted / DRAFT DRAFT NOV 2001 Use the mpsched command to run the “potato” program and bind it to processor ID 2. Then use the psrset -q... command to list the Pset binding for “potato” (process ID 10368); “potato” is bound to Pset 0. # mpsched -c 2 .
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets # HP Restricted / DRAFT DRAFT NOV 2001 2 0 2 8 9 11 system 0 0 0 9 0 1 0 0 5 9 8 7 95 90 92 84 Use the mpsched -u... command to unbind the “potato” program (process ID 10368) from processor ID 3, to allow the program’s threads to migrate to other processors in the Pset to which it is bound. Then use sar to list the local nPar’s current processor usage, including all processor and Pset details.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 Managing Pset Permissions and Attributes HP Restricted / DRAFT Example 9-4 This example modifies Pset owner, group, and access permissions; lists various Pset details; and includes other sample Pset uses by various users on the system. Use psrset -i to list the current Pset configuration for the local nPartition. Three Psets are configured: Pset 0, Pset 7, and Pset 8.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 HP Restricted / DRAFT # psrset -t 8 GRPID=20 # psrset -t 8 PERM=774 # Using the psrset -t... command, change the owner for Pset 7 to user ID 103 (the user named ann). # psrset -t 7 OWNID=103 # Now ann uses the id command to list the user ID and group memberships for her user account. She then lists the current Pset configuration for the local nPartition.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 ann $ 20 774 ALLOW DFLTPSET FAIL DFLTPSET HP Restricted / DRAFT GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU Because ann is the owner for Pset 7, she has authority to modify the Pset’s user, group, and access permissions attributes. Using the psrset -t... command, ann sets the group for Pset 7 to 102 (the group named prog). Another psrset -t...
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU ann $ HP Restricted / DRAFT DRAFT NOV 2001 8 6 7 0 20 774 ALLOW DFLTPSET FAIL DFLTPSET Now a different user in the same nPartition attempts to list and use the new Pset configurations. This user, joe, lists his user ID and the IDs for the groups to which he belongs, and then lists all Pset configurations using the psrset -i command.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets DRAFT NOV 2001 joe $ DFLTPSET FAIL DFLTPSET HP Restricted / DRAFT NONEMPTY EMPTY LASTSPU When joe uses the psrset -e 7... command to attempt to execute the “potato” program in Pset 7 he cannot because he does not have execute permission in the Pset. However, when joe uses the psrset -e 8... command to execute “potato” in Pset 8 the program is run in that Pset.
Processor Sets (Psets) on nPartitions Examples: Sample Uses of Psets HP Restricted / DRAFT DRAFT NOV 2001 352 HP System Partitions Guide: Administration for nPartitions—rp7410 EMSP—schwartz@rsn.hp.
