HP System Partitions Guide Administration for nPartitions Fifth Edition Revision 5.1 Manufacturing Part Number: B2355-90762 September 2002 © Copyright 2002 Hewlett-Packard Company. http://docs.hp.com/hpux/onlinedocs/B2355-90762/B2355-90762.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Preface The HP System Partitions Guide describes nPartition system administration procedures, concepts, and principles for HP rp7410 servers, HP rp8400 servers, and HP Superdome servers running the HP-UX 11i operating system.
About This Book: Overview of Chapters About This Book: Overview of Chapters 1. nPartition System Overviews on page 31 This chapter introduces Hewlett-Packard’s nPartition system features, server models, nPartition concepts, administration tools, and HP-UX 11i support for nPartitions. 2. Planning nPartition Configurations on page 109 This chapter describes how you can plan nPartition configurations for HP rp7410, rp8400, and Superdome servers.
About This Book: Overview of Chapters 9. Processor Instant Capacity on Demand (iCOD) on page 399 This chapter covers using Hewlett-Packard’s processor iCOD (Instant Capacity on Demand) product on nPartitions. iCOD is an optional software product that enables you to instantly increase or adjust processing power within nPartitions. As you need more or fewer processors, you use iCOD tools to adjust the number of activated processors in the nPartition. 10.
How to Buy This Book How to Buy This Book You can purchase a printed copy of the HP System Partitions Guide from Hewlett-Packard’s http://software.hp.com Web site. When at this Web site, click the Documentation link for a list of current publications. The http://www.software.hp.com/BOOKS_products_list.html Web site lists technical books currently available for sale, including this book. You also can find this book by searching for “Partitions Guide” using the HP software depot search facility.
Related Information Related Information For the most current HP-UX 11i nPartition administration details refer to this publication, the HP System Partitions Guide. You also can find other information on general HP-UX 11i administration, HP nPartition server hardware management, and diagnostic support tools in the following publications. Web Site for HP Technical Documentation: http://docs.hp.com The main Web site for Hewlett-Packard technical documentation is the http://docs.hp.
Related Information Server Hardware Information The following Web sites and publications describe HP nPartition server hardware management, including site prep, installation, and other details. • http://docs.hp.com/hpux/hw/ — This is the systems hardware portion of the docs.hp.com Web site. The following Superdome, rp8400, and rp7410 server Web sites are available from this systems hardware page. • HP Superdome — http://docs.hp.
Related Information Web Site for HP Technical Support: http://us-support2.external.hp.com Hewlett-Packard’s IT resource center Web site at http://us-support2.external.hp.com/ provides comprehensive support information for IT professionals on a wide variety of topics, including software, hardware, and networking. Books about HP-UX Published by Prentice Hall The http://www.hp.
Publication History Publication History The publication history for the HP System Partitions Guide includes the following editions and revisions. The version and part number indicate this information’s current revision level. The version number changes when a new revision is released. The part number changes when extensive changes are made. Fifth Edition August 2002, B2355-90762. CD-ROM, EPSS, Web (http://docs.hp.com/), and print delivery. You can order this book in print from the http://software.hp.
Notational Conventions Notational Conventions The following notational conventions are used in this publication. WARNING A warning lists requirements that you must meet to avoid personal injury. CAUTION A caution provides information required to avoid losing data or avoid losing system functionality. NOTE A note highlights useful information such as restrictions, recommendations, or important details about HP product features. • Commands and options are represented using this font.
Notational Conventions 12 HP System Partitions Guide: Administration for nPartitions, rev 5.
Contents Chapter 1. nPartition System Overviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported HP Server Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rp7410 Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rp8400 Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licensing Information: Getting Product Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 nPartition and Virtual Partition Unique Identifiers . . . . . . . . . . . 83 Using HP-UX nPartition Configuration Commands . . . . . . . . . . . . . . . 85 Specifying Cells and I/O Chassis to Commands. . . . . . . . . . . . . . . 87 nPartition Commands—Details and Syntax . . . . . . . . . . . . . . . . . 92 parcreate Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Processor Commands: Quick Reference. . . . . . . . . . . . . . . . . . Network Configuration for a Service Processor . . . . . . . . . . . . . . . . . . Console Access to nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . nPartition Console Access versus Direct HP-UX Login . . . . . . . . Boot Console Handler (BCH) Access. . . . . . . . . . . . . . . . . . . . . . . . . . . Console Log Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Booting an Inactive nPartition past Boot-Is-Blocked (BIB) . . . . . . . . Configuring Boot Paths and Boot Actions . . . . . . . . . . . . . . . . . . . . . . Configuring Autoboot and Autostart . . . . . . . . . . . . . . . . . . . . . . . . . . Autoboot Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Autostart Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Automatic System Restart for a nPartition . . . . . . . . . . .
Deconfiguring Cells, Processors, and Memory . . . . . . . . . . . . . . . . . . . Listing the Server Product Number and Serial Number. . . . . . . . . . . Checking Blower and Fan Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complex Health Analysis of a Server . . . . . . . . . . . . . . . . . . . . . . . . . . Listing the Cabinets in a Server Complex . . . . . . . . . . . . . . . . . . . . . . Listing the nPartitions in a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing and Configuring iCOD on nPartitions . . . . . . . . . . . . . . . . . 408 Procedures for Changing Processor iCOD Configurations on nPartitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Managing iCOD Utility (Pay Per Use) on nPartitions . . . . . . . . . . . . . 418 Chapter 10. Processor Sets (Psets) on nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Introduction to Psets . . . . . . . . . . . . . . . . . . . . . .
Determining if an nPartition is Running vPars . . . . . . . . . . . . . . Reboot for Reconfig or Shutdown to Ready for Reconfig from a vPar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding or Removing nPartition Cells from a Virtual Partition. . Reconfiguring nPartition Attributes from a vPar. . . . . . . . . . . . . HP System Partitions Guide: Administration for nPartitions, rev 5.
HP System Partitions Guide: Administration for nPartitions, rev 5.
Figures HP nPartition Server Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 HP rp7410 Server Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . 37 HP rp8400 Server Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . 39 HP Superdome 16-Way Architecture Overview . . . . . . . . . . . . . . . . . . . 41 HP Superdome 32-Way Architecture Overview . . . . . . . . . . . . . . . . . . . 43 HP Superdome 64-Way Architecture Overview . . . . . . . . . . . . .
HP System Partitions Guide: Administration for nPartitions, rev 5.
Tables HP Superdome I/O Chassis: Card Slot Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 HP rp7410 and rp8400 I/O Chassis: Card Slot Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Management Tools for nPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 I/O Numbering: PCI slots and Busses (LBAs) . . . . . . . . . . . . . . . . . . . . 79 HP-UX nPartition Configuration Commands. . . . . .
HP System Partitions Guide: Administration for nPartitions, rev 5.
Procedures Procedures for nPartition System Overviews Accessing Superdome Compute Cabinet I/O Chassis and PCI Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Accessing Superdome IOX I/O Chassis and PCI Card Slots . . . . . . . . . 52 Procedures for Planning nPartition Configurations Selecting Cells for an nPartition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Holding an nPartition at the Ready for Reconfig State [HP-UX] . . . . Performing a TOC Reset of an nPartition [Service Processor] . . . . . . Booting an Inactive nPartition past BIB [Service Processor] . . . . . . . Configuring Boot Paths and Actions [BCH] . . . . . . . . . . . . . . . . . . . . . Configuring Boot Paths and Actions [HP-UX] . . . . . . . . . . . . . . . . . . . Configuring Superdome nPartition Autostart [BCH] . . . . . . . . . . . . .
Setting nPartition Core Cell Choices [HP-UX]. . . . . . . . . . . . . . . . . . . Setting nPartition Core Cell Choices [Partition Manager] . . . . . . . . . Reassigning (Moving) a Cell to a Different nPartition . . . . . . . . . . . . Restoring a Complex Profile [Service Processor] . . . . . . . . . . . . . . . . . 297 299 302 303 Procedures for Listing and Managing Server Hardware Powering Server Cabinets On and Off [Power Switch] . . . . . . . . . . . .
Renaming a Server Complex [Service Processor]. . . . . . . . . . . . . . . . . Renaming a Server Complex [Partition Manager]. . . . . . . . . . . . . . . . Checking Power Supply Status [Service Processor]. . . . . . . . . . . . . . . Checking Power Supply Status [HP-UX] . . . . . . . . . . . . . . . . . . . . . . . Checking Power Supply Status [Partition Manager] . . . . . . . . . . . . . . Checking Memory Status [HP-UX] . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedures for Virtual Partitions (vPars) Management on nPartitions vPars Software Installation for an HP nPartition . . . . . . . . . . . . . . . . vPar Management: Creating a New vPar in an nPartition . . . . . . . . . vPar Management: Deleting a vPar from an nPartition . . . . . . . . . . . vPar Management: Modifying vPar Attributes in nPartition Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vPar Management: Listing vPar Status from an nPartition . . . . . . . .
HP System Partitions Guide: Administration for nPartitions, rev 5.
1 nPartition System Overviews This chapter introduces Hewlett-Packard’s nPartition system features, server models, nPartition concepts, administration tools, and HP-UX 11i support for nPartitions. • The first sections of this chapter introduce the nPartition system environment and the HP servers that support nPartitions. • Details about nPartition concepts are given starting with the section Overview of nPartitions on page 60.
nPartition System Overviews Introduction Introduction 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 an independent system environment. An nPartition includes: one or more cells (containing processors and memory) that are assigned to the nPartition as well as all I/O chassis connected to those cells.
nPartition System Overviews Introduction You can reconfigure a server’s nPartition definitions without physically modifying the server’s hardware configuration by using HP’s software-based nPartition management tools. You can reconfigure any nPartition to include more, fewer, and/or different hardware resources.
nPartition System Overviews Supported HP Server Models Supported HP Server Models The HP servers that support nPartitions include the following models: • HP rp7410 server—See rp7410 Server Model on page 36. • HP rp8400 server—See rp8400 Server Model on page 38. • Three models of HP Superdome servers—See Superdome Server Models on page 40. These nPartition servers have different hardware configurations and limits, as described in the following sections, and all include support for nPartitions.
nPartition System Overviews Supported HP Server Models Hardware Models: Superdome, rp8400, and rp7410 nPartition Servers HP Superdome, HP rp8400, and HP rp7410 server cabinets are shown in Figure 1-1. HP Superdome Server Cabinet HP nPartition Server Hardware HP rp8400 Server Hardware HP rp7410 Server Hardware © 2001 Hewlett-Packard AES—SPG-113-1 Figure 1-1 HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews rp7410 Server Model rp7410 Server Model HP rp7410 servers scale from one to two cells and include complete support for hard partitions (nPartitions). Figure 1-2 on page 37 shows an overview of the HP rp7410 server hardware architecture. You can configure a single nPartition using one or both cells, or can configure up to two separate nPartitions within an HP rp7410 server complex.
nPartition System Overviews rp7410 Server Model Also see nPartition System Hardware Details on page 47 for more information about HP rp7410 server features. Figure 1-2 HP rp7410 Server Architecture Overview HP rp7410 Server Processor Memory DIMMs PCI I/O Slot 0 Cell for rp7410 and rp8400 1 2 3 4 5 6 7 8 1 I/O Chassis for rp7410 and rp8400 System Interconnect On HP rp7410 servers: • Cell 0 directly connects to I/O domain 0. • Cell 1 directly connects to I/O domain 1.
nPartition System Overviews rp8400 Server Model rp8400 Server Model HP rp8400 servers scale from one to four cells and include complete support for hard partitions (nPartitions). Figure 1-3 on page 39 shows an overview of the HP rp8400 server hardware architecture. You can configure a single nPartition using some or all cells, or can configure up to two separate nPartitions within an HP rp8400 server complex.
nPartition System Overviews rp8400 Server Model Figure 1-3 HP rp8400 Server Architecture Overview HP rp8400 Server 0 1 1 2 3 4 5 6 7 8 2 3 1 2 3 4 5 6 7 8 Core I/O for Cell 0 Core I/O for Cell 1 0/0/0/3/0.2 Cell 0 CD/DVD-ROM 1/0/0/3/0.2 Cell 1 CD/DVD-ROM 0/0/0/2/1.9 Cell 0 Disk 0/0/0/2/0.9 Cell 0 Disk 1/0/0/2/1.9 Cell 1 Disk 1/0/0/2/0.9 Cell 1 Disk Processor Memory DIMMs On HP rp8400 servers: • Cell 0 directly connects to I/O domain 0. • Cell 1 directly connects to I/O domain 1.
nPartition System Overviews Superdome Server Models Superdome Server Models HP Superdome servers scale up to 16 cells and include complete support for hard partitions (nPartitions). You can configure a single nPartition using some or all cells, or can configure multiple nPartitions within the same Superdome server complex (up to one nPartition for each cell that has core I/O attached). You can add up to two Superdome I/O expansion cabinets to the Superdome 32-way and 64-way models.
nPartition System Overviews HP Superdome 16-Way (SD16000) Server Figure 1-4 HP Superdome 16-Way Architecture Overview HP Superdome 16-Way Server (SD16000) 0 1 11 10 9 8 7 6 5 4 3 2 1 0 2 3 11 10 9 8 7 6 5 4 3 2 1 0 Processor On HP Superdome 16-Way servers: Memory DIMMs • Each cell (0–3) can connect to any one of the available I/O chassis in the cabinet. PCI I/O Slot • PCI card slot 0 in each I/O chassis is for use by a Superdome core I/O card.
nPartition System Overviews HP Superdome 32-Way (SD32000) Server HP Superdome 32-Way (SD32000) Server The Superdome 32-way server is a single-cabinet server that has from two to eight cells, each with four HP PA-RISC processors and up to 32 DIMMs. Figure 1-5 on page 43 shows an overview of the Superdome 32-way server hardware architecture. The Superdome 32-way server can have up to 32 processors, 256 DIMMs, up to four internal 12-slot PCI I/O chassis, plus optional I/O expansion cabinet hardware.
nPartition System Overviews HP Superdome 32-Way (SD32000) Server Figure 1-5 HP Superdome 32-Way Architecture Overview HP Superdome 32-Way Server (SD32000) 0 1 2 11 10 9 8 7 6 5 4 3 2 1 0 3 4 5 6 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0 Processor On HP Superdome 32-Way servers: Memory DIMMs • Each cell (0–7) can connect to any one of the available I/O chassis. 7 11 10 9 8 7 6 5 4 3 2 1 0 • Additional I/O chassis can be provided in a connected I/O expansion cabinet.
nPartition System Overviews HP Superdome 64-Way (SD64000) Server HP Superdome 64-Way (SD64000) Server The Superdome 64-way server is a tightly interconnected dual-cabinet server that has from 4 to 16 cells, each with four HP PA-RISC processors and up to 32 DIMMs. Figure 1-6 on page 45 shows an overview of the Superdome 64-way server hardware architecture. The Superdome 64-way server can have up to 64 processors, 512 DIMMs, and up to eight internal 12-slot PCI I/O chassis.
nPartition System Overviews HP Superdome 64-Way (SD64000) Server Figure 1-6 HP Superdome 64-Way Architecture Overview HP Superdome 64-Way Server (SD64000) 11 10 9 8 7 6 5 4 3 2 1 0 0 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0 1 2 3 4 5 6 7 9 10 11 12 13 14 15 Cabinet 0 Cabinet 1 8 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0 Processor 11 10 9 8 7 6 5 4 3 2 1 0 On HP Superdome 64-Way servers: • Each cell can conne
nPartition System Overviews HP Superdome I/O Expansion Cabinet HP Superdome I/O Expansion Cabinet HP Superdome 32-way and Superdome 64-way servers can include I/O expansion cabinets in addition to the server cabinet(s) in the complex. Each I/O expansion cabinet has a cabinet number of either 8 or 9. A Superdome I/O expansion cabinet includes up to 3 I/O bays, with two 12-slot I/O chassis in each bay. This provides for up to 6 chassis with a total of 72 PCI card slots in each I/O expansion cabinet.
nPartition System Overviews nPartition System Hardware Details nPartition System Hardware Details This section gives physical details about the Hewlett-Packard servers that support nPartitions, including HP Superdome, rp8400, and rp7410 servers.
nPartition System Overviews Processors: HP PA-RISC CPUs In HP rp7410 and rp8400 servers, each cell can support up to 16 memory DIMMs and 1–4 processors. Each HP Superdome cell can be connected to an I/O chassis that resides either in the same cabinet as the cell or in an I/O expansion cabinet. In HP rp7410 and rp8400 servers, cell 0 connects to I/O chassis 0, and cell 1 connects to I/O chassis 1.
nPartition System Overviews I/O Chassis in HP Superdome Compute Cabinets • I/O Chassis in HP Superdome IOX Cabinets on page 51 • I/O Chassis for HP rp7410 and rp8400 Servers on page 54 I/O Chassis in HP Superdome Compute Cabinets Each HP Superdome I/O chassis can connect to one cell in the same compute cabinet. A Superdome I/O chassis has 12 slots, numbered from 11 to 0. The HP Superdome core I/O card fits only in slot 0. Card slot details for Superdome I/O chassis are in Table 1-1.
nPartition System Overviews I/O Chassis in HP Superdome Compute Cabinets The Superdome I/O chassis and slot locations are shown in Figure 1-7. Figure 1-7 HP Superdome I/O Chassis and PCI Card Slot Locations As Figure 1-7 shows, I/O chassis in HP Superdome compute cabinets reside both in the cabinet’s front (I/O bay 0) and its rear (I/O bay 1). When you face each I/O bay, the left I/O chassis is chassis 1 and the right chassis is I/O chassis 3.
nPartition System Overviews I/O Chassis in HP Superdome IOX Cabinets See Figure 1-7 on page 50 for details. Step 2. To access the PCI card slots in an HP Superdome compute cabinet’s I/O chassis, you must remove the cover from the top of the I/O chassis. In each Superdome compute cabinet I/O chassis—when facing the chassis—PCI slot 0 is on the right and PCI slot 11 is on the left. I/O Chassis in HP Superdome IOX Cabinets Up to two I/O expansion (IOX) cabinets can reside in an HP Superdome complex.
nPartition System Overviews I/O Chassis in HP Superdome IOX Cabinets Figure 1-8 I/O Expansion Cabinet (IOX) for HP Superdome Each I/O bay in an IOX houses two I/O chassis: the left chassis is I/O chassis 1, right is chassis 3. Thus, an IOX can have up to six I/O chassis that can connect to the cells in an attached Superdome compute cabinet.
nPartition System Overviews I/O Chassis in HP Superdome IOX Cabinets Figure 1-9 IOX Bezel, Cover, and Bay Step 2. To access the PCI card slots in an IOX I/O chassis, remove the I/O chassis cover. To access slots in chassis 1 of the bay remove the cover from the left side of the I/O bay, or remove the cover from the right side of the bay to access I/O chassis 3’s PCI card slots. See Figure 1-9 for details. HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews I/O Chassis for HP rp7410 and rp8400 Servers I/O Chassis for HP rp7410 and rp8400 Servers HP rp7410 and rp8400 servers have two I/O chassis, each with 8 slots numbered left to right from 1 to 8. Both HP rp7410 and rp8400 server cabinets have a single I/O bay on the cabinet’s rear that houses the two I/O chassis or “I/O domains”. When you face the I/O bay, viewing the rear of the cabinet, the chassis on the left is I/O chassis 0, and right is I/O chassis 1.
nPartition System Overviews Internal Disk Devices for HP rp7410 and rp8400 Servers On both HP rp7410 and rp8400 servers, slots 1–7 are dual-rope slots, which have two connections between the slot’s local bus adapter (LBA) and the I/O chassis system bus adapter (SBA). The core I/O connections (slot 0) and slot 8 are single-rope slots, which have a single connection between the slot LBA and the I/O chassis SBA. The dual-rope slots can have greater sustained bandwidth than single-rope slots.
nPartition System Overviews Disk Devices in HP rp8400 Cabinets Disk Devices in HP rp8400 Cabinets The hardware paths for internal drives in an HP rp8400 cabinet are shown in Figure 1-11. Figure 1-11 HP rp8400 Internal Storage Hardware Paths HP rp8400 Front View: Cabinet-Internal I/O Devices 0/0/0/3/0.2 Cell 0 CD/DVD 1/0/0/3/0.2 Cell 1 CD/DVD 0/0/0/2/1.9 Cell 0 Disk 0/0/0/2/0.9 Cell 0 Disk 1/0/0/2/1.9 Cell 1 Disk 1/0/0/2/0.
nPartition System Overviews nPartition Service Processor (GSP or MP) Hardware Service Processor for HP rp7410 On HP rp7410 servers, service processor functionality is provided in the core I/O card, shown in Figure 1-12. The rp7410 core I/O card’s customer LAN port, which permits remote telnet access to the service processor, is labeled “MP LAN”. The “MP Serial” port is single DB25 serial port from which three DB9 serial connectors are available (a DB25-to-3xDB9 dongle must be connected).
nPartition System Overviews nPartition Service Processor (GSP or MP) Hardware Service Processor for HP rp8400 On HP rp8400 servers, service processor functionality is provided in the core I/O card, shown in Figure 1-13. The rp8400 core I/O card’s customer LAN port, which permits remote telnet access to the service processor, is labeled “GSP LAN”. A direct RS-232 serial connection to the service processor is available through the “Local Console” port.
nPartition System Overviews nPartition Service Processor (GSP or MP) Hardware Service Processor for HP Superdome On HP Superdome servers, service processor functionality is provided by the “GSP UGUY and SUB” cabinet hardware, which can be seen in the rear of the cabinet above the LAN and console ports (see Figure 1-14). Use the cabinet 0 (not cabinet 1) LAN and RS-232 connections to access the service processor. The cabinet 0 “Customer LAN” port provides remote telnet access to the service processor.
nPartition System Overviews Overview of nPartitions 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 nPartitions and hardware within the same server complex.
nPartition System Overviews Cell Properties Cell Properties 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 HP-UX command or Partition Manager.
nPartition System Overviews Cell Properties Core Cells 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. The core cell controls the nPartition until HP-UX has booted, and it provides console access for the nPartition. The core cell’s core I/O provides console access for the nPartition through the service processor (GSP or MP).
nPartition System Overviews Genesis Partition point during the nPartition boot process when all available cells in an nPartition join together to establish which cells are active for the current boot of the nPartition.) For example, a cell can be inactive when it is powered off, has booted with a “n” use-on-next-boot value, or is assigned to an nPartition that has been reset to the ready for reconfig state. The resources belonging to inactive cells are not actively used by an nPartition.
nPartition System Overviews Partition Numbers Note that—once you create additional nPartitions—you do not necessarily have to use the Genesis partition to perform your nPartition management and configuration tasks. Partition Numbers Each nPartition has its own unique partition number that the nPartition commands and utilities use for identifying the nPartition. When you create an nPartition, the utility you use assigns the nPartition the lowest available partition number.
nPartition System Overviews nPartition Local and Remote Access # parstatus -w The local partition number is 1.
nPartition System Overviews nPartition Active and Inactive States • Turning Attention Indicators (LEDs) On or Off—You can use the fruled command or Partition Manager to control the attention indicators for all hardware in the server complex from any nPartition. nPartition Active and Inactive States Each nPartition’s boot state either is active or inactive. Active nPartition An nPartition that is active has at least one cell that is active (not in a boot-is-blocked state).
nPartition System Overviews nPartition Active and Inactive States CAUTION • When HP-UX is running on an nPartition, you can make the nPartition inactive by issuing the shutdown -R -H command to shut down HP-UX, reboot all cells, and hold all cells at a boot-is-blocked state. • When the BCH interface is available for an nPartition, you can make the nPartition inactive by issuing the BCH interface’s RECONFIGRESET command.
nPartition System Overviews Complex Profiles Complex Profiles Each HP nPartition server’s Complex Profile includes the data that determine how the server’s hardware is assigned to and used by nPartitions. When you configure nPartitions and modify nPartition settings, the commands and utilities you use lock and unlock the server’s Complex Profile when revising it.
nPartition System Overviews Complex Profiles The Partition Configuration Data includes the following details for each nPartition in the server complex: — The nPartition’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 nPartition.
nPartition System Overviews Tools for Managing nPartitions Tools for Managing nPartitions 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.
nPartition System Overviews Tools for Managing nPartitions Use Table 1-3 to select the most appropriate nPartition management tool based on the tasks you need to perform and the ways in which you can access the system. Table 1-3 Management Tools for nPartitions Partition Tool Service Processor (GSP or MP) menus Features and Restrictions The service processor menus provide a complex-wide service interface that allows access to complex hardware and nPartitions defined within the complex.
nPartition System Overviews Tools for Managing nPartitions Table 1-3 Management Tools for nPartitions (Continued) Partition Tool Features and Restrictions Boot Console Handler (BCH) interface The BCH interface is the method for interacting with an nPartition before it has booted HP-UX. Each nPartition’s BCH interface provides menus for configuring nPartition settings and booting HP-UX. Also refer to the chapter Using Console and Service Processor Interfaces on page 125 for details.
nPartition System Overviews Tools for Managing nPartitions Table 1-3 Management Tools for nPartitions (Continued) Partition Tool Partition Manager (parmgr) Features and Restrictions Partition Manager (/opt/parmgr/bin/parmgr) provides a graphical interface for configuring, modifying, and managing nPartitions and hardware within a server complex. See the section Using the Partition Manager Utility on page 106 for details.
nPartition System Overviews HP-UX 11i Release Features HP-UX 11i Release Features The HP-UX 11i June 2002 Release Notes lists the latest feature additions and changes to HP-UX operating system and the various “operating environment” bundles. Each of the HP-UX operating environment bundles includes its own collection of applications. You can install any one of the operating environments at a time. Use the swlist -l bundle command to list all installed software bundles, including operating environments.
nPartition System Overviews HP-UX 11i Release Features • HP-UX 11i Minimal Technical Operating This is an operating environment defined for HP workstations. It contains all the base functionality. However, compared to the Technical Computing Operating Environment, the set of additional applications is greatly reduced. HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews HP-UX Hardware Paths for nPartitions 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 nPartition 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.
nPartition System Overviews HP-UX Hardware Paths for nPartitions Use the rad -q command to list all active PCI slots in an nPartition along with their corresponding hardware paths. See PCI Card Slot and Hardware Path Numbering on page 79. • 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.
nPartition System Overviews HP-UX Hardware Paths for nPartitions 12/0/6 12/0/6/0/0 12/0/6/0/0.5 12/0/6/0/0.5.0 12/0/6/0/0.6 12/0/6/0/0.6.0 12/0/6/0/0.7 12/0/6/0/0.7.
nPartition System Overviews PCI Card Slot and Hardware Path Numbering 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-4 shows the correlations among PCI slots and their LBA numbers.
nPartition System Overviews PCI Card Slot and Hardware Path Numbering The order in which ioscan reports the PCI slots (in LBA number order) does not correspond to the order in which the slots physically are arranged (PCI card slot order, left-to-right or right-to-left). 80 HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews rad Command Output in nPartitions rad Command Output in nPartitions This section covers the rad command’s output on nPartitions. For complete details, see the rad (1M) manpage. NOTE 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. On HP nPartition servers, the rad command reports PCI card slot details as shown in the following example output.
nPartition System Overviews Licensing Information: Getting Product Details Licensing Information: Getting Product Details 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.
nPartition System Overviews nPartition and Virtual Partition Unique Identifiers nPartition and Virtual Partition Unique Identifiers NOTE Use the getconf command or the confstr() call to obtain unique identifiers. 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 (1) and confstr (3C) to retrieve unique machine identifiers.
nPartition System Overviews nPartition and Virtual Partition Unique Identifiers Z3e02955673f9f7c9 # /usr/bin/getconf _CS_MACHINE_SERIAL USR2024FP1 # Example 1-3 Unique IDs for Virtual Partitions (vPars) The following example shows the vPar-unique ID returned by the getconf command, as well as the local nPartition number and the current vPar’s name. # parstatus -w The local partition number is 0. # vparstatus -w The current virtual partition is Shad.
nPartition System Overviews Using HP-UX nPartition Configuration Commands 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 1-5 on page 86 describes each of these commands.
nPartition System Overviews Using HP-UX nPartition Configuration Commands Table 1-5 describes the nPartition configuration commands and lists sections where you can find each command’s syntax and details. Table 1-5 HP-UX nPartition Configuration Commands Command parcreate Description Create a new nPartition; root permission is required. See parcreate Command on page 93. parmodify Modify an existing nPartition; root permission is required. See parmodify Command on page 95.
nPartition System Overviews Specifying Cells and I/O Chassis to Commands 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.
nPartition System Overviews Specifying Cells and I/O Chassis to Commands • 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.
nPartition System Overviews Specifying Cells and I/O Chassis to Commands 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. On HP rp7410 and rp8400 servers, the cabinet number always is 0.
nPartition System Overviews Specifying Cells and I/O Chassis to Commands 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.
nPartition System Overviews Specifying Cells and I/O Chassis to Commands # 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,chassis3 cab8,bay1,chassis1 cab8,bay1,chas
nPartition System Overviews nPartition Commands—Details and Syntax nPartition Commands—Details and Syntax This section has details and command-line syntax for the following HP-UX nPartition configuration commands: NOTE • parcreate Command on page 93 • parmodify Command on page 95 • parremove Command on page 98 • parstatus Command on page 99 • parunlock Command on page 101 • fruled Command on page 102 • frupower Command on page 104 The sections that follow provide useful reference informatio
nPartition System Overviews parcreate Command 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 nPartition and returns the partition number of the newly created nPartition. Root permission is required to use parcreate. See the parcreate (1M) manpage for complete details.
nPartition System Overviews parcreate Command -b path Specifies the primary (PRI) boot path. -t path Specifies the alternate (ALT) boot path. -s path Specifies the secondary (HAA) boot path. -r cell Specifies the core cell choices. One to four cells can be specified. -B Specifies to boot the nPartition. The default is not to boot the nPartition and leave it in the ready for reconfig state. 94 HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews parmodify Command parmodify Command You can use the /usr/sbin/parmodify command to modify the following attributes of an existing nPartition: 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. See the parmodify (1M) manpage for complete details.
nPartition System Overviews parmodify Command n • Do not participate in reboot. The only valid failure_usage value is: ri Reactivate with interleave (the default). -m cell:[cell_type]:[use_on_next_boot]:[failure_usage] Modify attributes of a cell already assigned the nPartition. 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 nPartition.
nPartition System Overviews parmodify Command When you modifying an active nPartition and specify the -B option, you must perform a reboot for reconfig of the modified nPartition. You must perform this reboot for reconfig before any other cell assignments can take place in the server complex. HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews parremove Command parremove Command The /usr/sbin/parremove command removes an existing nPartition. This removes all cells from the nPartition and destroys the nPartition definition. To remove the local nPartition (the nPartition from which you issue this command), you must specify the -F option.
nPartition System Overviews parstatus Command parstatus Command The /usr/sbin/parstatus command displays information about the nPartitions or hardware within a server complex. If you specify no arguments, parstatus lists information about several of the major components of the server complex. You can specify an individual entity (cell, I/O chassis, cabinet, or nPartition) to restrict the output to information about that component. All users can issue this command.
nPartition System Overviews parstatus Command -B Show information for all cabinets in the complex. -P Show information for all nPartitions 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 nPartition. 100 HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews parunlock Command 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. Also refer to the section Unlocking Complex Profiles on page 305.
nPartition System Overviews fruled Command fruled Command The /usr/sbin/fruled command blinks hardware attention indicators (LEDs) or turns them off. This command can control the cell attention LEDs in all HP nPartition servers, as well as the I/O chassis LEDs on Superdome servers. The fruled command also can start and stop blinking the cabinet number LCDs on HP Superdome compute cabinets and I/O expansion cabinets. See the fruled (1) manpage for details.
nPartition System Overviews fruled Command Start or stop blinking the cabinet number LCD of the specified cabinet. -C Turn off all cell attention LEDs. -l cabinet Limit the scope of the -C or -I option to a given cabinet. HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews frupower Command frupower Command The /usr/sbin/frupower command turns on, turns off, or displays the current status of power for cells and I/O chassis in nPartition servers. NOTE The frupower command (and Partition Manager) permits you to power on or off inactive cells and I/O chassis that are assigned to the current nPartition or are not assigned to any nPartition. See the frupower (1M) manpage for details.
nPartition System Overviews frupower Command -I Display power status of all I/O chassis. The scope is the entire complex if the -l option is not specified. -l cabinet Limit the scope of the -C or -I option to the specified cabinet. HP System Partitions Guide: Administration for nPartitions, rev 5.
nPartition System Overviews Using the Partition Manager Utility 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. This section introduces these topics about Partition Manager: Partition Manager Primary Window, Running Partition Manager, Requirements and Limits, and Partition Manager Online Help. Complete information is in the online help.
nPartition System Overviews Using the Partition Manager Utility The left side of the primary window lists all nPartitions, available resources (installed hardware that is not assigned to an nPartition), 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. Running Partition Manager You can access Partition Manager using any one of the following methods.
nPartition System Overviews Using the Partition Manager Utility Requirements and The following are requirements and limits of Partition Manager. Limits See the parmgr (1M) manpage for other requirements. • 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.
2 Planning nPartition Configurations This chapter describes how you can plan nPartition configurations for HP rp7410, rp8400, and Superdome servers. Details include the configuration requirements for nPartitions and HP recommendations. For related procedures to manage nPartitions, refer to the chapter Managing nPartitions on page 245. Also, for an introduction to nPartition features, refer to the chapter nPartition System Overviews on page 31.
Planning nPartition Configurations nPartition Requirements and Recommendations nPartition Requirements and Recommendations The hardware requirements shown below determine which cells are eligible to be assigned to an nPartition. Also consider the nPartition recommendations, which can improve an nPartition’s performance and availability. Configuration Requirements for nPartitions Every nPartition you configure must meet the following hardware requirements.
Planning nPartition Configurations nPartition Requirements and Recommendations This allows the nPartition to boot or recover HP-UX, even if only the nPartition’s core cell is functioning. ❏ You should assign multiple core-capable cells to each nPartition. This allows the nPartition to boot at least to the BCH interface if a core cell fails to boot.
Planning nPartition Configurations nPartition Requirements and Recommendations The PRI and HAA paths should be configured to reference disks that are connected to different cells, if possible, with HAA being a mirror of the root volume and PRI being the root volume. ALT should be the path of a recovery or install device. Under this configuration, if the cell to which the PRI disk is connected fails or is otherwise inactive and the HAA disk’s cell is available, the nPartition still can boot HP-UX.
Planning nPartition Configurations Configuration Process: Selecting Cells for an nPartition Configuration Process: Selecting Cells for an nPartition The following steps provide a basic procedure for selecting which cells to assign to the nPartitions you will create in an HP server. Selecting Cells for an nPartition Step 1. Determine the sizes of all nPartitions you will create in the server complex.
Planning nPartition Configurations Configuration Process: Selecting Cells for an nPartition • The cells should be present (installed) in the server and powered on. You can assign cells that are not present or on when using parcreate or parmodify. However, you should install and power on cells before assigning them to nPartitions in order to allow commands to automatically check the cells’ compatibility with any other cells in the nPartition.
Planning nPartition Configurations HP Superdome nPartition Configuration Guidelines HP Superdome nPartition 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. HP offers specific guidelines for configuring nPartitions on HP Superdome servers in order to ensure good system performance.
Planning nPartition Configurations HP Superdome nPartition Configuration Guidelines This provides more appropriate cell assignments for larger nPartitions (those with more cells). Any smaller nPartitions with fewer cells are more easily accommodated in the remaining, available cells. ❏ Place each nPartition within an empty cabinet, if possible. This applies to nPartitions in HP Superdome 64-way servers only.
Planning nPartition Configurations Chart of Supported HP rp7410 nPartition Configurations Chart of Supported HP rp7410 nPartition Configurations Figure 2-1 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, rev 5.
Planning nPartition Configurations Chart of Supported HP rp8400 nPartition Configurations Chart of Supported HP rp8400 nPartition Configurations Figure 2-2 lists the nPartition configurations that HP supports for HP rp8400 servers.
Planning nPartition Configurations Charts of Supported HP Superdome nPartition Configurations Charts of Supported HP Superdome nPartition Configurations 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.
Planning nPartition Configurations Charts of Supported HP Superdome nPartition Configurations 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 1D 1H 2
Planning nPartition Configurations Charts of Supported HP Superdome nPartition Configurations 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 Superdome 64-way Cabinet 0 Superdome 64-way Cabinet 1 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 16 17 18 Three-Cell Partitions 19 2J 2J 2K 3A
Planning nPartition Configurations nPartition Example Configurations for an HP Superdome Server Complex nPartition Example Configurations for an HP Superdome Server Complex This section shows example cell assignments to demonstrate the procedure for selecting cells for two sample server complex configurations. For reference in the following examples, Figure 2-3 on page 120 and Figure 2-4 on page 121 list a unique number for each nPartition configuration set.
Planning nPartition Configurations nPartition Example Configurations for an HP Superdome Server Complex Example 2-1 Example nPartition Configuration for a Superdome 32-way Server This example configures an HP Superdome 32-way server with one six-cell nPartition and one two-cell nPartition. A Superdome 32-way server with a six-cell and two-cell nPartition would be configured with nPartitions 6A and 2B, as shown in Figure 2-3 on page 120.
Planning nPartition Configurations nPartition Example Configurations for an HP Superdome Server Complex Example 2-2 Example nPartition Configuration for a Superdome 64-way Server This example configures an HP Superdome 64-way server with one seven-cell nPartition and two four-cell nPartitions. A Superdome 64-way server with a seven-cell nPartition and two four-cell nPartitions would be configured with nPartitions 7A, 4B, and 4E, as shown in Figure 2-4 on page 121.
3 Using Console and Service Processor Interfaces This chapter covers the service processors and nPartition console interfaces available for HP’s nPartition servers. NOTE The service processor in HP servers is sometimes called the Management Processor (MP) and sometimes the Guardian Service Processor (GSP). Regardless of the name, the service processor in these servers provides approximately the same features and performs essentially the same role.
Using Console and Service Processor Interfaces Service Processor (GSP or MP) Introduction Service Processor (GSP or MP) Introduction 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) Introduction 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. HP System Partitions Guide: Administration for nPartitions, rev 5.
Using Console and Service Processor Interfaces Service Processor Features Service Processor Features The following list describes the primary features available through the service processor (GSP or MP) on HP rp7410, HP rp8400, and HP Superdome servers. • Command Menu The Command menu provides commands for system service, status, access configuration, and manufacturing tasks. To enter the Command menu, enter CM at the service processor Main menu.
Using Console and Service Processor Interfaces Service Processor Features The nPartition console provides console login access to HP-UX and serves as /dev/console for the nPartition. • 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 Features • Virtual Front Panel (VFP) for an nPartition Each nPartition’s Virtual Front Panel (VFP) displays real-time status of the nPartition boot status and activity, and details about all cells assigned to the nPartition. The VFP display automatically updates as cell and nPartition status changes. A system-wide VFP also is provided. Enter VFP at the Main menu to access the View Front Panel menu.
Using Console and Service Processor Interfaces Service Processor Accounts and Access Levels 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 login 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 Accessing Service Processor Interfaces This section describes how to login 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 Accessing Service Processor Interfaces Example 3-1 Service Processor Login Session The following output shows a sample login session for a server whose service processor’s hostname is “hpsys-s”. > 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.
Using Console and Service Processor Interfaces Accessing Service Processor Interfaces Logging in to a Service Processor This procedure connects to and logs in to a server complex’s service processor (GSP or MP) using telnet to access the customer LAN. If connecting through the local or remote RS-232 port, skip Step 1 (instead establish a direct-cable or dial-up connection) and begin with Step 2. Step 1.
Using Console and Service Processor Interfaces Accessing Service Processor Interfaces If accessing HP-UX on an nPartition, log out of HP-UX before exiting the console and service processor sessions. (Otherwise an open HP-UX login session will remain available to any other service processor users.) HP System Partitions Guide: Administration for nPartitions, rev 5.
Using Console and Service Processor Interfaces Using Service Processor Menus 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 138 for details on using these menus.
Using Console and Service Processor Interfaces Using Service Processor Menus Figure 3-1 Overview of Service Processor (GSP or MP) Menus CO — Console Menu Partitions available: # --0) 1) Q) Name ---Partition 0 Partition One Quit Please select partition number: VFP — Virtual Front Panel Service Processor (GSP or MP) Main Menu GSP MAIN MENU: GSP> Consoles Virtual Front Panel Command Menu Console Logs Show chassis Logs Help Exit Connection GSP:VFP> CM — Command Menu Enter HE to get a list of available
Using Console and Service Processor Interfaces Navigating through Service Processor Menus Navigating through Service Processor Menus Figure 3-2 on page 139 shows the commands and options for returning to the service processor Main menu and for ending a service processor login session. The following list also includes tips for navigating through service processor menus and using various menu features: • Control-b Exit current console, console log, chassis log, or Virtual Front Panel.
Using Console and Service Processor Interfaces Navigating through Service Processor Menus Figure 3-2 Navigating through Service Processor (GSP or MP) Menus telnet sdome-g (login to service processor) Service Processor Main Menu CO Console Menu Please select partition number: Virtual Front Panel Menu CM ^] GSP:VFP> Command Menu CL MA GSP:CM> Console Log Viewer Menu SL Q or ^b Q or ^b GSP:VW> Chassis Log Viewer Menu Q or ^b GSP:VW> X Connection closed by foreign host.
Using Console and Service Processor Interfaces Using Service Processor Commands 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 Commands Commonly Used at the Service Processor Commands Commonly Used at the Service Processor Table 3-1 summarizes commands that are commonly used by system administrators. These commands are available to all service processor users. Table 3-1 Service Processor: Commonly Used 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 Service Processor Commands: Quick Reference The following tables list commands available from the service processor Command menu: NOTE • Service Commands on page 142 • Status Commands on page 143 • System and Access Configuration Commands on page 144 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 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 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. Some of these commands are restricted (users with an “Operator” or “Single Partition User” access level can issue a subset of these commands).
Using Console and Service Processor Interfaces Service Processor Commands: Quick Reference Table 3-4 Service Processor: System and Access Configuration Commands 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 Network Configuration for a Service Processor Network Configuration for a Service Processor 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. Details on configuring service processor networking are given in the procedure Configuring Service Processor Network Settings on page 148.
Using Console and Service Processor Interfaces Network Configuration for a Service Processor 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 Network Configuration for a Service Processor 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 Network Configuration for a Service Processor From a PC command prompt: route add 192.168.1.1 ClientName On an HP-UX workstation login as root and use this command: /usr/sbin/route add 192.168.1.1 ClientName 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.
Using Console and Service Processor Interfaces Console Access to nPartitions Console Access to nPartitions 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 nPartition 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 Login You should login 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 Boot Console Handler (BCH) Access Boot Console Handler (BCH) Access 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 Boot Console Handler (BCH) Access SERvice-------------BAttery CLEARPIM MemRead PDT PIM SCSI BootINfo CAche ChipRevisions ComplexID FabricInfo FRU FwrVersion IO LanAddress MEmory PRocessor CEllConfig COreCell CPUConfig DataPrefetch DEfault FastBoot KGMemory PathFlag PD ResTart TIme ... HP System Partitions Guide: Administration for nPartitions, rev 5.
Using Console and Service Processor Interfaces Boot Console Handler (BCH) Access Figure 3-3 Accessing an nPartition’s BCH Interface telnet sdome-g (login to service processor) GSP or MP Main Menu CO (select Console menu) Console Menu 1 (select partition 1 console) ---- Main Menu --------------------------------------------------------------Command ------BOot [PRI|HAA|ALT|] PAth [PRI|HAA|ALT] [] SEArch [ALL|] ScRoll [ON|OFF] Description ----------^b Boot from specified path Display or
Using Console and Service Processor Interfaces Console Log Viewing Console Log Viewing 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 Chassis Code Log Viewing Chassis Code Log Viewing 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. Chassis codes are data that communicate information about system events from the source of the event to other parts of the server complex.
Using Console and Service Processor Interfaces Chassis Code Log Viewing 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 Chassis Code Log Viewing You also can filter the live codes by cell (C) or nPartition (P). Cell filter: only display chassis codes emitted by a specific cell in the server complex. Partition filter: only display chassis codes emitted by hardware assigned to a specific nPartition. When viewing chassis code logs, type V to change the display format. The viewers can show chassis codes in text format (T), keyword format (K), or raw hex format (R).
Using Console and Service Processor Interfaces Using Virtual Front Panels 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 160 HP System Partitions Guide: Administration for nPartitions, rev 5.
4 An Overview of nPartition Boot and Reset This chapter presents an overview of booting and reset concepts and issues for HP nPartition servers. For procedures to boot, reboot, and configure boot options, refer to the chapter Booting and Resetting nPartitions on page 197. NOTE For details on booting and rebooting Virtual Partitions within an nPartition, refer to the chapter Virtual Partitions (vPars) Management on nPartitions on page 443.
An Overview of nPartition Boot and Reset Types of Booting and Resetting for nPartitions 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. HP’s nPartition servers also provide two special types of reboot and reset for managing nPartitions: performing a reboot for reconfig, and resetting an nPartition to the ready for reconfig state.
An Overview of nPartition Boot and Reset Types of Booting and Resetting for nPartitions • Reset A reset resets the nPartition immediately. Only the nPartition’s active cells are reset. You can reset an nPartition using the BCH interface’s REBOOT command or the service processor Command menu’s RS command. The RS command does not check whether the specified nPartition is in use or running HP-UX—be certain to correctly specify the nPartition.
An Overview of nPartition Boot and Reset Types of Booting and Resetting for nPartitions After you assign a cell to an nPartition, or remove an active cell from an nPartition, you can perform a reboot for reconfig of the nPartition to complete the cell addition or removal. If an nPartition is configured to boot HP-UX automatically, it can do so immediately following a reboot for reconfig.
An Overview of nPartition Boot and Reset Boot Process for nPartitions, Cells, and HP-UX Boot Process for nPartitions, Cells, and HP-UX The boot process for nPartitions is similar to the process on other HP servers. However, on HP nPartition servers, each cell boots and performs self tests (POST) separately, and one or more cells rendezvous to form an nPartition before providing a BCH interface for the nPartition. NOTE This section covers nPartitions booting HP-UX in non-vPars mode.
An Overview of nPartition Boot and Reset Boot Process for nPartitions, Cells, and HP-UX Each nPartition goes through the boot process shown in Figure 4-1, from power on to booting HP-UX: 1. Power On or Reset The boot process starts when any of the following events occurs: • An nPartition is reset or rebooted. • The entire server complex is powered on. • Power is turned on for components in the nPartition (such as cells). 2.
An Overview of nPartition Boot and Reset Boot Process for nPartitions, Cells, and HP-UX Following this, any I/O busses connected to the cell are known and configured by the cell. 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 nPartition. Cells that remain at BIB are inactive, and cells that rendezvous into the nPartition are active.
An Overview of nPartition Boot and Reset Boot Process for nPartitions, Cells, and HP-UX — If any cells with a “y” use-on-next-boot setting do not report to rendezvous, then ten minutes after rendezvous began the cells that have not reported become inactive cells, and all other reporting cells complete rendezvous and are active. The inactive cells’ resources are not available to be used by the nPartition, although the cells still are assigned to the nPartition. 6.
An Overview of nPartition Boot and Reset Boot Process for nPartitions, Cells, and HP-UX For example, when you configure boot paths and boot actions to automatically boot HP-UX, the ISL and hpux loaders specify that the /stand/vmunix kernel is booted. HP System Partitions Guide: Administration for nPartitions, rev 5.
An Overview of nPartition Boot and Reset Overview of nPartition Boot Features 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.
An Overview of nPartition Boot and Reset Overview of nPartition Boot Features • Before powering off a cell, the cell should be inactive; unassigned; or assigned to an nPartition that either has been shut down and halted or has been reset to the 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.
An Overview of nPartition Boot and Reset Tools for Managing nPartition Booting Tools for Managing nPartition Booting HP nPartition servers support the following software tools for booting and resetting nPartitions and for configuring and managing nPartition 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.
An Overview of nPartition Boot and Reset Tools for Managing nPartition Booting ISL: Initial System Loader Replying “y” (yes, do stop at ISL) allows you to interact directly with a boot device’s Initial System Loader (ISL) and the Secondary System Loader (hpux). Enter all ISL commands from the ISL> prompt. hpux: Secondary System Loader From the ISL prompt you also can enter commands that are executed by the Secondary System Loader (hpux). Preface your Secondary System Loader command with hpux.
An Overview of nPartition Boot and Reset Configurable Boot Settings Configurable Boot Settings Each nPartition 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 nPartition boots. nPartition boot settings are stored as part of the server Complex Profile data.
An Overview of nPartition Boot and Reset Configurable Boot Settings • Boot Actions Each boot device path has an associated boot action, which is established by the path’s “path flag” setting. The boot actions (path flag settings) are referenced automatically when an nPartition initially boots to the BCH interface. Boot actions have no effect on boot behavior when you manually boot HP-UX using the BCH interface’s BOOT command.
An Overview of nPartition Boot and Reset Configurable Boot Settings One cell is selected as the active core cell for the nPartition when the nPartition boots. By default, the lowest numbered eligible cell in the nPartition is chosen. To be eligible the cell must: be active, have a connection to functioning core I/O, and be assigned to the nPartition.
An Overview of nPartition Boot and Reset Configurable Boot Settings For details on configure these boot-related settings for an nPartition refer to the chapter Booting and Resetting nPartitions on page 197. HP System Partitions Guide: Administration for nPartitions, rev 5.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings Listing nPartition Boot Settings You can list an nPartition’s boot-related settings by using the nPartition’s BCH interface or by using HP-UX commands. To list boot settings for nPartitions, use the following procedures: • Listing nPartition Boot Settings [BCH] on page 178 This procedure (Main menu, Information menu, and Configuration menu BCH commands) lists an nPartition’s boot settings using the BCH interface.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings From the nPartition console you access the nPartition’s BCH interface. If the nPartition is not at the BCH interface, you must either boot the nPartition 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. The BCH interface’s Main menu, Information menu, and Configuration menu provide commands for listing (and setting) boot options for the nPartition.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings • BCH Information menu From the BCH Main menu, enter IN to access the Information menu. Table 4-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. Enter the command with no arguments to display (but not change) the boot setting.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings Go to BCH. Configuration Menu: Enter command > Listing nPartition Boot Settings [HP-UX] This procedure (parstatus -V -p# and setboot commands) lists an nPartition’s boot settings using HP-UX commands. NOTE Use the parstatus command to list various nPartition boot settings for any nPartition in a server complex. The setboot command only provides information about the local nPartition’s PRI and ALT boot paths and PRI boot actions.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings CPU Speed : Core Cell : Core Cell Alternate [1]: Core Cell Alternate [2]: 552 MHz cab0,cell0 cab0,cell0 cab0,cell2 [Cell] CPU OK/ Hardware Actual Deconf/ Location Usage Max ========== ============ ======= cab0,cell0 active core 4/0/4 cab0,cell2 active base 4/0/4 Memory (GB) OK/ Deconf ========= 2.0/ 0.0 2.0/ 0.
An Overview of nPartition Boot and Reset Listing nPartition Boot Settings 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). When autoboot is set to ON, the nPartition attempts to automatically boot from the PRI boot path when it first boots to BCH. Otherwise, when autoboot is OFF, the nPartition remains at the BCH interface on startup.
An Overview of nPartition Boot and Reset Checklist and Guidelines for Booting nPartitions Checklist and Guidelines for Booting nPartitions This section provides both a checklist to use when booting an nPartition, and a set of guidelines to consider when configuring nPartition boot settings. Boot Checklist for nPartitions Before you boot an nPartition, check the items listed here. ❏ All cells in the nPartition that have a “y” use-on-next-boot value should be powered on.
An Overview of nPartition Boot and Reset Checklist and Guidelines for Booting nPartitions By configuring HAA and ALT boot device paths, you establish additional bootable devices that provide redundancy in case the PRI device fails. Also configure the path flags for the boot paths, to allow the HAA device to boot automatically if the device at the PRI path cannot boot. ❏ Ensure that the core I/O, PRI boot device, and network card(s) all are connected to same cell (the core cell).
An Overview of nPartition Boot and Reset nPartition Boot Activity Monitoring nPartition Boot Activity Monitoring On HP nPartition servers you can monitor the nPartition boot process—from power-on or reset to HP-UX start-up—using the Virtual Front Panel (VFP) view of the nPartition. Each nPartition has its own VFP that displays details about the nPartition’s cells and the nPartition’s boot state and activity.
An Overview of nPartition Boot and Reset nPartition Boot Activity Monitoring Step 2. Select the nPartition you wish to monitor. 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 nPartition and its current boot state.
An Overview of nPartition Boot and Reset Hanged HP-UX and Running HP-UX Detection Hanged HP-UX and Running HP-UX Detection This section describes how you can determine whether HP-UX still is running on an nPartition even when you are unable to login or access the nPartition console.
An Overview of nPartition Boot and Reset Hanged HP-UX and Running HP-UX Detection GSP> SL Chassis Logs available: (A)ctivity Log (E)rror Log (L)ive Chassis Logs (C)lear All Chassis Logs (Q)uit GSP:VW> L Entering Live Log display Step 3. From the Live Log display, type P and select the nPartition whose chassis codes you want to view by typing the partition number. By default the live chassis log viewer only displays alert codes.
An Overview of nPartition Boot and Reset Hanged HP-UX and Running HP-UX Detection To exit the live log display, type ^b (Control-b) Heartbeat for HP-UX When HP-UX is running on the nPartition, the live log partition filter shows the nPartition’s HP-UX HEARTBEAT chassis codes and corresponding ACTIVITY_LEVEL_TIMEOUT counter updates.
An Overview of nPartition Boot and Reset Hanged HP-UX and Running HP-UX Detection Step 6. Determine whether the nPartition needs to be reset in order to restore HP-UX to a running state. Review the findings from the previous steps in this procedure. HP-UX on the nPartition may be considered “hanged” if you observed all of the following VFP, live log, and console behaviors: • The VFP indicates HPUX heartbeat in the partition state with no asterisk (*) blinking to indicate activity.
An Overview of nPartition Boot and Reset Troubleshooting Boot Issues 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) an nPartition.
An Overview of nPartition Boot and Reset Troubleshooting Boot Issues • Problem: An nPartition does not boot to BCH and instead all cells remain at a boot-is-blocked (BIB) state. Causes: The nPartition has been reset to the ready for reconfig state, or no valid core cell is available to the nPartition.
An Overview of nPartition Boot and Reset Boot States and Activities for nPartitions and Cells Boot States and Activities for nPartitions and Cells On HP nPartition servers, the cell and nPartition boot process proceeds from one boot state to the next; cells and nPartitions complete various boot activities within each boot state before proceeding to the next boot state. You can view current details about nPartition and cells boot states and activities by viewing the nPartition’s Virtual Front Panel.
An Overview of nPartition Boot and Reset Boot States and Activities for nPartitions and Cells Inactive cells remain at a “Boot Is Blocked (BIB)” state following I/O discovery and do not participate in partition rendezvous.
An Overview of nPartition Boot and Reset Boot States and Activities for nPartitions and Cells Table 4-4 Partition State HP nPartition and Cell Boot States and Activities (Continued) 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 partition HPUX heartbeat Cell
5 Booting and Resetting nPartitions This chapter presents procedures for booting and resetting nPartitions and procedures for configuring an nPartition’s boot-related options. For an introduction to nPartition boot issues, refer to the chapter An Overview of nPartition Boot and Reset on page 161. NOTE For details on booting and rebooting Virtual Partitions within an nPartition, refer to the chapter Virtual Partitions (vPars) Management on nPartitions on page 443.
Booting and Resetting nPartitions Accessing an nPartition Console and BCH Interface Accessing an nPartition Console and BCH Interface Each nPartition has its own Boot Console Handler (BCH) interface that provides you a method for interacting with the nPartition 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).
Booting and Resetting nPartitions Accessing an nPartition Console and BCH Interface 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. The Console menu is the method for accessing nPartition consoles.
Booting and Resetting nPartitions Accessing an nPartition Console and BCH Interface 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.
Booting and Resetting nPartitions Accessing an nPartition Console and BCH Interface • When an nPartition is at the BCH interface you can access BCH commands from the nPartition’s console and can reboot BCH if needed. • When an nPartition has booted to ISL you can use the EXIT command to exit ISL and return to the nPartition’s BCH interface. • When an nPartition has booted HP-UX, in order to access the BCH interface you must reboot HP-UX and if necessary interrupt the automatic boot process.
Booting and Resetting nPartitions Boot Device Searching and Finding Boot Device Searching and Finding 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 nPartition’s currently active cells. NOTE You cannot access any I/O connected to an nPartition’s inactive cells (cells not being used for the current nPartition boot) or cells not assigned to the local nPartition.
Booting and Resetting nPartitions Boot Device Searching and Finding PAth [PRI|HAA|ALT] [] SEArch [ALL|] ScRoll [ON|OFF] Display or modify a path Search for boot devices Display or change scrolling capability COnfiguration menu INformation menu SERvice menu Displays or sets boot values Displays hardware information Displays service commands DIsplay HElp [
Booting and Resetting nPartitions HP-UX Booting on an nPartition HP-UX Booting on an nPartition nPartitions boot and reboot HP-UX independently from each other. This section describes how to boot a single instance of HP-UX on an nPartition. NOTE For details on booting HP-UX in Virtual Partitions (vPars), refer to the section Booting HP-UX on vPars on page 485. You can boot HP-UX on an nPartition using the BCH interface’s BOOT command. Each nPartition’s BCH interface is available through its console.
Booting and Resetting nPartitions HP-UX Booting on an nPartition Step 2. Choose which device you wish to boot. From the BCH Main menu, use the PATH command to list any boot path variable settings. The primary (PRI) boot path normally is set to the main boot device for the nPartition. You also can use the SEARCH command to find and list potentially bootable devices for the nPartition. Main Menu: Enter command or menu > PATH Primary Boot Path: HA Alternate Boot Path: Alternate Boot Path: 0/0/2/0/0.
Booting and Resetting nPartitions HP-UX Booting on an nPartition After you issue the BOOT command, the BCH interface prompts you to specify whether you want to stop at the ISL prompt. To boot the /stand/vmunix HP-UX kernel from the device without stopping at the ISL prompt, enter n to automatically proceed past ISL and execute the contents of the AUTO file on the selected device. (By default the AUTO file is configured to load /stand/vmunix.
Booting and Resetting nPartitions Booting an nPartition to the ISL Prompt 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.
Booting and Resetting nPartitions Booting an nPartition to the ISL Prompt The EXIT command exits ISL and returns to the nPartition 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.42 JUN 19, 1999 ISL> 208 HP System Partitions Guide: Administration for nPartitions, rev 5.
Booting and Resetting nPartitions Single-User or LVM-Maintenance Mode HP-UX Booting Single-User or LVM-Maintenance Mode HP-UX Booting 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).
Booting and Resetting nPartitions Single-User or LVM-Maintenance Mode HP-UX Booting ISL Revision A.00.42 JUN 19, 1999 ISL> 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.
Booting and Resetting nPartitions HP-UX Install Source Booting HP-UX Install Source Booting 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. NOTE For instructions on installing HP-UX, refer to the book HP-UX 11i Installation and Update Guide, which is supplied with the HP-UX operating environment media.
Booting and Resetting nPartitions Shutting Down HP-UX on an nPartition 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. NOTE 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.
Booting and Resetting nPartitions Shutting Down HP-UX on an nPartition Use the following list to choose an HP-UX shut down option for your nPartition. • Shut down HP-UX and halt the nPartition. Issue the shutdown -h command to shut down and halt the nPartition. This leaves the nPartition and all its cells in an active state (the nPartition cannot be reconfigured) after HP-UX shuts down and halts. To reboot the nPartition you must reset the nPartition using the GSP command menu’s RS command.
Booting and Resetting nPartitions Rebooting or Resetting an nPartition Rebooting or Resetting an nPartition When you perform a reboot or reset of an nPartition, all active cells in the nPartition reboot and return to BCH or HP-UX. Any inactive cells in the nPartition are not rebooted in this procedure.
Booting and Resetting nPartitions Rebooting or Resetting an nPartition Rebooting or Resetting an nPartition [Service Processor] This procedure (service processor Command menu RS command) resets an nPartition using the service processor. Step 1. Login 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. GSP login: Accountname GSP password: Password ....
Booting and Resetting nPartitions Rebooting or Resetting an nPartition -> The selected partition will be reset. GSP:CM> If you are accessing the service processor using a single-partition-user account, the RS command selects which nPartition is to be reset: the nPartition that your account allows you to access. If using an operator or administrator service processor account, you can select which of the server complex’s nPartitions you want to reset.
Booting and Resetting nPartitions Rebooting or Resetting an nPartition The shutdown -r command shuts down HP-UX and reboots the nPartition. All active cells in the nPartition are reset. HP System Partitions Guide: Administration for nPartitions, rev 5.
Booting and Resetting nPartitions Performing a Reboot for Reconfig for an nPartition Performing a Reboot for Reconfig for an nPartition During a reboot for reconfig of an nPartition, 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 nPartition, including any inactive cells. 2. Reconfigures the nPartition if necessary (adds or removes cells). 3. Boots all cells in the nPartition.
Booting and Resetting nPartitions Holding an nPartition at the Ready for Reconfig State Holding an nPartition at the Ready for Reconfig State Resetting an nPartition to the ready for reconfig state performs any changes to the nPartition’s configuration and holds the nPartition and all its cells in a boot-is-blocked (inactive) state. To boot an nPartition after you have reset it to the ready for reconfig state, you must use the service processor (GSP or MP) Command menu’s BO command.
Booting and Resetting nPartitions Holding an nPartition at the Ready for Reconfig State You should reset an nPartition to ready for reconfig whenever you need for the nPartition and its cells to be inactive. This enables you to modify the nPartition’s configuration from the GSP or from HP-UX running on a remote nPartition in the same system complex. 220 HP System Partitions Guide: Administration for nPartitions, rev 5.
Booting and Resetting nPartitions Holding an nPartition at the Ready for Reconfig State Holding an nPartition at the Ready for Reconfig State [Service Processor] This procedure (Command menu RR command) resets an nPartition to the ready for reconfig state from the service processor. Step 1. Login 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.
Booting and Resetting nPartitions Holding an nPartition at the Ready for Reconfig State If you are accessing the service processor using a single-partition-user account, the RR command selects which nPartition is to be reset: the nPartition that your account allows you to access. If using an operator or administrator GSP account, you can select which of the server complex’s nPartitions you want to reset.
Booting and Resetting nPartitions Holding an nPartition at the Ready for Reconfig State The shutdown -R -H command shuts down HP-UX, reset all cells in the nPartition, perform any nPartition reconfigurations, and halt all cells at a boot-is-blocked state, thus making the nPartition and all its cells inactive. HP System Partitions Guide: Administration for nPartitions, rev 5.
Booting and Resetting nPartitions Performing a Transfer-of-Control (TOC) Reset of an nPartition Performing a Transfer-of-Control (TOC) Reset of an nPartition You can use the service processor Command menu’s TC command to perform a transfer-of-control (TOC) reset of an nPartition. If crash dump is configured for HP-UX on the nPartition, when you TOC the nPartition while it is running HP-UX the nPartition performs a crash dump and gives you an opportunity select the type of dump.
Booting and Resetting nPartitions Performing a Transfer-of-Control (TOC) Reset of an nPartition WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition. # --0) 1) Name ---jules00 jules01 Select a partition number: 0 Do you want to TOC partition number 0? (Y/[N]) y -> The selected partition will be TOCed. GSP:CM> Step 3.
Booting and Resetting nPartitions Booting an Inactive nPartition past Boot-Is-Blocked (BIB) Booting an Inactive nPartition past Boot-Is-Blocked (BIB) When all cells in an nPartition are at boot-is-blocked, the nPartition is inactive. This is the case, for example, when an nPartition is held at the ready for reconfig state. You can boot an nPartition past the ready for reconfig state to make it active by using the service processor Command menu’s BO (boot) command.
Booting and Resetting nPartitions Booting an Inactive nPartition past Boot-Is-Blocked (BIB) Step 2. From the Command menu, enter the BO command and specify which nPartition is to be booted (released from boot-is-blocked). As a result of the BO command, the complex’s service processor releases the selected nPartition’s cells from boot-is-blocked: the cells proceed to rendezvous to form an active nPartition, which no longer is in the ready for reconfig state.
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions 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 procedures: • Configuring Boot Paths and Actions [BCH] on page 230 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 int
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions • 0—Go to BCH. • 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.
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions Configuring Boot Paths and Actions [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.
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions 4/0/2/0/0.a (hex) Main Menu: Enter command or menu > 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.
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions Step 1. Determine which devices will be used for booting HP-UX on the nPartition, and determine the boot behaviors you desire for the PRI boot path. Step 2. Login to HP-UX running on an nPartition in the complex. You can modify the boot paths for any nPartition from any other nPartition in the complex when using the parmodify command.
Booting and Resetting nPartitions Configuring Boot Paths and Boot Actions The setboot command supports the following options for setting local nPartition boot actions: -b Autoboot setting for the local nPartition: -b on to automatically boot the PRI path. -b off to not boot PRI. -s Autosearch setting for the local nPartition: -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).
Booting and Resetting nPartitions Configuring Autoboot and Autostart 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 nPartition’s boot actions for its boot paths. See the Autoboot Configuration section. On HP Superdome servers only, you can configure an Autostart setting for each nPartition to specify the nPartition’s boot behavior when one or more self tests fails.
Booting and Resetting nPartitions Autostart Configuration NOTE This procedure applies to nPartitions on HP Superdome servers only. Step 1. Login 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 nPartition’s BCH interface. If the nPartition is not at the BCH interface you must either boot the nPartition or shut down HP-UX to return to the BCH interface.
Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition 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 nPartition. By default, automatic system restart is disabled for nPartitions.
Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition 129 128 128 GSP 0 *13 0x591008d1a000205f 0x000065060c0f1611 PARTITION_TIMEOUT_RESET HPUX 0,0,0 *13 0x78e004d41100f000 0x0000000300000009 HPUX 0,0,0 *13 0x58e00c000000f000 0x000065060c0f1610 07/12/2001 15:22:16 Monitoring HP-UX Activity and Chassis Logs You can monitor whether HP-UX is active on an nPartition through the nPartition’s Virtual Front Panel and through the Chassis Logs viewer.
Booting and Resetting nPartitions Configuring Automatic System Restart for a nPartition the selected partition. # --0) 1) Name ---feshd5a feshd5b Select a partition number: 0 Automatic system restart for partition 0 is currently enabled. Do you want to disable automatic system restart? (Y/[N]) y -> Automatic system restart is disabled. GSP:CM> 238 HP System Partitions Guide: Administration for nPartitions, rev 5.
Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition Configuring Fast Boot Settings (Self Tests) for a nPartition The fast boot settings for an nPartition determine which self tests the nPartition performs during the power on or nPartition boot process.
Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition Configuring Fast Boot for an nPartition [BCH] This procedure (Configuration menu, FASTBOOT command) configures an nPartition’s fast boot settings using its BCH interface. Step 1. Login to the server complex’s service processor (GSP or MP), access the nPartition’s console, and access the BCH Configuration menu. From the nPartition console you access the nPartition’s BCH interface.
Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition Step 2. Enter the setboot -v command to list the current self test configuration for the local nPartition. The self test details listed by setboot -v include: TEST—The keyword names of self tests that you can enable or disable.
Booting and Resetting nPartitions Configuring Fast Boot Settings (Self Tests) for a nPartition test_name is the name of the self test (“PDH”, “early_cpu”, “late_cpu”) or is “all” (for all tests). The setboot command’s -t option changes the test setting in stable storage and affects all following boots. The -T option changes the test setting for the next boot only. NOTE HP recommends that all self tests be performed for all nPartitions.
Booting and Resetting nPartitions Boot Timer Configuration for an nPartition Boot Timer Configuration for an nPartition 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.
Booting and Resetting nPartitions Boot Timer Configuration for an nPartition 244 HP System Partitions Guide: Administration for nPartitions, rev 5.
6 Managing nPartitions This chapter presents the procedures for creating, configuring, and managing nPartitions on HP servers that support them. For an introduction to nPartition features, refer to the chapter nPartition System Overviews on page 31. For nPartition configuration requirements and related HP recommendations, refer to the chapter Planning nPartition Configurations on page 109. HP System Partitions Guide: Administration for nPartitions, rev 5.
Managing nPartitions Coordinating Changes to nPartitions 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. The HP-UX nPartition configuration commands and the Partition Manager utility coordinate their actions by using locks to restrict access to portions of the server’s Complex Profile data while they modify that data.
Managing nPartitions Coordinating Changes to nPartitions • When removing an active cell from an nPartition, you must perform a reboot for reconfig (shutdown -R, not -r) of the modified nPartition 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.
Managing nPartitions Rebooting to Implement nPartition Changes Rebooting to Implement nPartition Changes Once an nPartition has booted and is active, the nPartition 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 nPartition, as described below. You can add and remove cells from an active, booted nPartition; however, you only can add or remove inactive cells without having to reboot the nPartition.
Managing nPartitions Rebooting to Implement nPartition Changes • Reset an nPartition to the ready for reconfig state (shutdown -R -H) to make the nPartition inactive. All cells in an nPartition remain inactive when the nPartition is in the 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 nPartition.
Managing nPartitions Listing the Local (Current) Partition Number 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 an nPartition.
Managing nPartitions Listing the Local (Current) Partition Number Listing the Local nPartition Number [HP-UX] This procedure (parstatus -w) lists the partition number of the local (current) nPartition from HP-UX. Step 1. Login to HP-UX running on the nPartition. Step 2. Issue the parstatus -w command to list the partition number for the local nPartition. # parstatus -w The local partition number is 0.
Managing nPartitions Listing All Configured nPartitions Listing All Configured nPartitions You can configure each server complex to have multiple nPartitions, which are composed of cells in the complex. You can list all configured nPartitions in the server complex by using the following procedures: • Listing All nPartitions [Service Processor] on page 252 This procedure (Command menu, CP command) lists all nPartitions in a server complex from the complex’s service processor.
Managing nPartitions Listing All Configured nPartitions Step 2. From the service processor Command menu, enter the CP command to list all configured nPartitions within the server complex. The CP command lists each nPartition (by partition number) and indicates which cells from each cabinet are assigned to the nPartition. In the following example the complex has two nPartitions: partition number 0 has cells 0 and 2, and partition number 1 has cells 4 and 6.
Managing nPartitions Listing All Configured nPartitions The parstatus -P command lists all nPartitions and shows each nPartition’s number and name, the number of cells assigned to it, the number of active I/O chassis, and the nPartition’s active core cell.
Managing nPartitions Listing All Configured nPartitions For cells and nPartitions that have not finished booting, the parstatus command cannot determine processor, memory, or I/O details and instead reports a question mark (?) for these details. Listing All nPartitions [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.
Managing nPartitions Listing All Configured nPartitions The right side of the primary display also lists the complex’s nPartitions when nothing is selected on the display’s left side, or when My Complex is selected. 256 HP System Partitions Guide: Administration for nPartitions, rev 5.
Managing nPartitions Listing Cell nPartition Assignments Listing Cell nPartition Assignments Each cell in an nPartition server complex either is assigned to an nPartition, or it is unassigned (if it is an available resource).
Managing nPartitions Listing Cell nPartition Assignments Listing Cell nPartition Assignments [HP-UX] This procedure (parstatus -C) lists all cells in a server complex and their nPartition assignments. Step 1. Login to HP-UX running on one of the server complex’s nPartitions. Step 2. Issue the parstatus -C command to list all cells, any I/O chassis connections, and any nPartition assignments for the cells.
Managing nPartitions Listing Cell nPartition Assignments Step 1. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 2. At the Partition Manager primary window, select each nPartition on the left side of the window to list the nPartition’s cell assignments on the window’s right side, or select Available Resources to list all unassigned cells.
Managing nPartitions Creating a Genesis Partition Creating a Genesis Partition When you create a Genesis Partition, you establish a one-cell nPartition on the server complex. The Genesis Partition replaces all other nPartitions, and once created it is the only nPartition 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.
Managing nPartitions Creating a Genesis Partition If an nPartition is running HP-UX, you can shut down the nPartition to the ready for reconfig state by using the shutdown -R -H command. Or, you can put an nPartition into the ready for reconfig state by using the BCH interface’s RECONFIGRESET command or using the service processor Command menu’s RR command. Step 4. Login to the server complex’s service processor (GSP or MP).
Managing nPartitions Creating a Genesis Partition Step 7. Issue the BO command to boot the Genesis Partition past its ready for reconfig state and make it an active nPartition. When a Genesis Partition is created, it remains at boot-is-blocked (in an inactive, ready for reconfig state), so you must boot it manually. The Genesis Partition always is assigned partition number 0, because when it is created it is the first and only nPartition in the server complex.
Managing nPartitions Creating a New nPartition 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 nPartitions. You can create a new nPartition by using the following procedures: • Creating a New nPartition [HP-UX] on page 263 This procedure (using the parstatus, parcreate, and parmodify commands) creates and configures a new nPartition from HP-UX.
Managing nPartitions Creating a New nPartition # 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. The partition number is : 1 # In the above alternative command line, the -B option is specified and causes the nPartition to be booted past boot-is-blocked immediately, thus making the new nPartition active. (It is booted to its BCH interface.) Step 1.
Managing nPartitions Creating a New nPartition (The -B option causes parcreate to immediately boot the newly-created nPartition past the default ready for reconfig state, thus making the nPartition active and preventing you from further modifying it.) By not specifying -B, the new nPartition can be further modified because it will remain inactive at the ready for reconfig state (until you boot it using the service processor Command menu’s BO command).
Managing nPartitions Creating a New nPartition 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. # parmodify -p1 -r0/4 -r0/6 Command succeeded. # parmodify -p1 -b 4/0/1/0/0.9 Command succeeded. # When each modification takes place, parmodify reports “Command succeeded”. Otherwise it reports any problems.
Managing nPartitions Creating a New nPartition cab0,cell4 inactive cab0,cell6 inactive .... 4/0/4 4/0/4 2.0/ 0.0 cab 0,bay0,chassis3 yes 2.0/ 0.0 cab 0,bay1,chassis1 yes yes yes 1 1 Step 5. Boot your newly-created nPartition past boot-is-blocked to make it active and make its BCH interface available. Use the service processor Command menu’s BO command to boot the nPartition. Once the nPartition is booted, you can access its BCH interface through its console.
Managing nPartitions Creating a New nPartition You can cancel the new nPartition creation at any time by clicking the Cancel button. 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.
Managing nPartitions Assigning (Adding) Cells to an nPartition Assigning (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 an nPartition) and assigning them to an existing nPartition. Both the selected cells and any I/O chassis connected to the cells are assigned to the designated nPartition.
Managing nPartitions Assigning (Adding) Cells to an nPartition Adding Cells to an nPartition [HP-UX] 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.
Managing nPartitions Assigning (Adding) Cells to an nPartition You can optionally specify the parmodify command’s -B option to require that the modified nPartition be rebooted. • When you specify -B to modify an inactive nPartition, the inactive nPartition completes partition rendezvous and becomes active if possible.
Managing nPartitions Assigning (Adding) Cells to an nPartition Step 4. Select the cells that you want to add to the nPartition from the Available Cells list, then click the Add button to add them to the nPartition’s cell list. If adding multiple cells, you can select multiple cells by pressing the Control key while clicking on the cells. Adding the cell(s) to the nPartition should create a configuration that adheres to the hardware requirements and performance guidelines. Step 5.
Managing nPartitions Unassigning (Removing) Cells from an nPartition Unassigning (Removing) Cells from an nPartition Removing a cell from an nPartition involves unassigning the cell from the nPartition 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 nPartitions in the same server complex. However, at least one core-capable cell must remain in each nPartition.
Managing nPartitions Unassigning (Removing) Cells from an nPartition Reboot for Reconfig Guidelines for Removing Cells In some situations, you must immediately perform a reboot for reconfig (shutdown -R) of a modified nPartition after removing cells from it. Performing a required reboot for reconfig completes cell assignment changes and unlocks the server’s Complex Profile. • You must immediately perform a reboot for reconfig of an nPartition when you have removed an active cell from the nPartition.
Managing nPartitions Unassigning (Removing) Cells from an nPartition In order to remove cells that are not assigned to the local nPartition, the cells must be inactive (their “Actual Usage” must be “inactive”). You can list the local nPartition by issuing the parstatus -w command. To remove an active cell from its nPartition, you must do so when logged in to HP-UX running on the cell’s nPartition. Step 2. Remove the cell from the nPartition to which it is assigned by using the parmodify -p# -d#... command.
Managing nPartitions Unassigning (Removing) Cells from an nPartition • Removing an Inactive Cell When removing an inactive cell from an nPartition you do not need to specify the -B option to parmodify and do not need to perform a reboot for reconfig of the cell’s nPartition. When you use parmodify to remove an inactive cell, the cell is immediately unassigned from its nPartition.
Managing nPartitions Unassigning (Removing) Cells from an nPartition The cells must all be assigned to the same nPartition in order to remove them using a single procedure. Otherwise, if the cells are assigned to different nPartitions, you must perform this procedure separately for each nPartition. Step 2. Run Partition Manager (/opt/parmgr/bin/parmgr) or access it from SAM or a Web browser. Step 3.
Managing nPartitions Unassigning (Removing) Cells from an nPartition • 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 nPartition to rendezvous and be active after the reboot for reconfig. To cancel all nPartition changes, click the Cancel button in the Notes and Warnings window and then click Cancel in the Modify Partition window. To proceed with removing the cell(s) from the nPartition, click OK.
Managing nPartitions Unassigning (Removing) Cells from an nPartition • If you have removed one or more active cells from the nPartition, then Partition Manager provides more info about performing the required reboot for reconfig of the nPartition. You must reboot the nPartition as soon as possible, so you should click the Yes button to exit Partition Manager and proceed with the next step of this procedure. Step 9. As needed, perform a reboot for reconfig (shutdown -R) of the modified nPartition.
Managing nPartitions Removing (Deleting) an nPartition Removing (Deleting) 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. You can delete an nPartition using these procedures: • Deleting an nPartition [HP-UX] on page 280 This procedure (using the parremove command) deletes an nPartition using HP-UX commands.
Managing nPartitions Removing (Deleting) an nPartition If the remote nPartition is running HP-UX, you can shut down the nPartition to the ready for reconfig state by 1) logging in to HP-UX on the remote nPartition, 2) shutting down all applications and warning users, and 3) issuing the shutdown -R -H command. You also can put the nPartition into the ready for reconfig state by using the BCH interface’s RECONFIGRESET command or the service processor Command menu’s RR command. Step 3.
Managing nPartitions Removing (Deleting) an nPartition 2. Issue the parremove -F -p# command, which initiates the complex profile revisions that will take place when the nPartition is removed. 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 nPartition).
Managing nPartitions Removing (Deleting) an nPartition Click the nPartition’s name in the list on the left side of the primary window to select the nPartition. If you plan to remove a remote nPartition, then after you select the nPartition’s name, all of the nPartition’s hardware (listed on the right side of the primary window) should be listed as having an Actual Usage of “inactive”. To remove a remote nPartition it must be inactive. Step 3.
Managing nPartitions Removing (Deleting) an nPartition • If you are removing the local nPartition, Partition Manager will display the following information to you after you click OK to remove the nPartition. To complete the local nPartition’s removal, you must perform a shutdown for reconfig (shutdown -R -H) of the local nPartition as soon as possible.
Managing nPartitions Naming and Renaming nPartitions Naming and Renaming nPartitions Each nPartition has both a partition number and an nPartition 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 nPartition’s name to help you distinguish among the nPartition in a server complex.
Managing nPartitions Naming and Renaming nPartitions From the service processor Main menu, enter CO to access the console menu and select the nPartition. If necessary, type ^ecf (Control-e c f) to get write access for the console. Note that if the nPartition is booted to HP-UX, you should instead use the HP-UX command method of modifying the nPartition name. Step 3. Access the BCH interface’s Configuration menu. From the Main menu, enter CO to access the Configuration menu.
Managing nPartitions Naming and Renaming nPartitions Step 2. Use the parmodify -p# -P name command to set the nPartition name for any of the nPartitions in the server complex. Specify both the partition number (-p#) and the new name for the nPartition (-P name). If the nPartition name contains spaces then quotation marks must surround the name. # parmodify -p1 -P "New Name" Command succeeded. # You can list the nPartition’s new name by using the parstatus -p# command or parstatus -P.
Managing nPartitions Setting and Checking Cell Attributes 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 nPartition. You can list and set cell attributes by using these procedures: • Setting Cell Attributes [BCH] on page 289 This procedure (Configuration menu, CELLCONFIG command) lists and sets a cell’s use-on-next-boot setting from the BCH interface for the cell’s nPartition.
Managing nPartitions Setting and Checking Cell Attributes The reactivate-with-interleave setting allows a cell to actively join its nPartition following processor or memory failures during the cell’s self tests. The cell joins its nPartition 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 nPartition.
Managing nPartitions Setting and Checking Cell Attributes Cell ---4 6 Cab/ Slot ---0/4 0/6 Cell State ---------Alive Alive Configuration Status -------------------Configured Configured Configuration Menu: Enter command > To change the use-on-next-boot setting for a cell, issue the CELLCONFIG command with arguments: CELLCONFIG cell [ON|OFF] For example, CELLCONFIG 6 OFF sets the use-on-next-boot setting for cell 6 to OFF.
Managing nPartitions Setting and Checking Cell Attributes BCH Configuration Menu: Enter command > RECONFIGRESET Reset the partition for reconfiguration of Complex Profile ... Service Processor (GSP or MP) GSP:CM> BO This command boots the selected partition. # --0) 1) Name ---jules00 jules01 Select a partition number: 1 Do you want to boot partition number 1? (Y/[N]) y -> The selected partition will be booted. GSP:CM> Setting Cell Attributes [HP-UX] This procedure (parmodify -p# -m#...
Managing nPartitions Setting and Checking Cell Attributes “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.
Managing nPartitions Setting and Checking Cell Attributes Step 3. To modify a cell’s use-on-next-boot and failure usage attribute settings, use the parmodify -p# -m#... command and specify the cell’s new settings. 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 nPartition (partition number 0) boots. # parmodify -p0 -m2:base:n:ri Command succeeded.
Managing nPartitions Setting and Checking Cell Attributes Setting Cell Attributes [Partition Manager] This procedure (Partition —> Modify Partition action, Change Cell Attributes tab) lists and sets the configurable cell attributes using Partition Manager. 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.
Managing nPartitions Setting and Checking Cell Attributes If the cell attribute changes are implemented, Partition Manager presents a final confirmation that the nPartition was successfully modified. Step 6. If you have modified a cell’s attribute settings, you must reboot the nPartition to which the cell is assigned for the settings to be used. Rebooting the cell’s nPartition allows the nPartition to use each cell’s new attribute settings.
Managing nPartitions Setting and Checking nPartition Core Cell Choices Setting and Checking nPartition Core Cell Choices The core cell choice settings for an nPartition are optional preferences that establish which cells in the nPartition are preferred to be selected as the core cell for the nPartition.
Managing nPartitions Setting and Checking nPartition Core Cell Choices Setting nPartition Core Cell Choices [BCH] This procedure (Configuration menu, COC command) sets the core cell choices for an nPartition using the nPartition’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 nPartition. From the BCH Main menu, enter CO to enter the Configuration menu. Step 3.
Managing nPartitions Setting and Checking nPartition Core Cell Choices # parstatus -V -p0 [Partition] Partition Number : Partition Name : Status : IP address : Primary Boot Path : Alternate Boot Path : HA Alternate Boot Path : PDC Revision : IODCH Version : CPU Speed : Core Cell : Core Cell Alternate [1]: Core Cell Alternate [2]: 0 jules00 active 0.0.0.0 0/0/2/0/0.13.0 0/0/2/0/0.0.0 0/0/2/0/0.14.0 6.0 23664 552 MHz cab0,cell0 cab0,cell0 cab0,cell2 ....
Managing nPartitions Setting and Checking nPartition Core Cell Choices 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] If you wish to immediately use the new core cell choice settings, reboot the nPartition whose core cell choices you have changed.
Managing nPartitions Setting and Checking nPartition Core Cell Choices 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 nPartition was successfully modified. The new core cell choice priorities will be used the next time the nPartition is rebooted. 300 HP System Partitions Guide: Administration for nPartitions, rev 5.
Managing nPartitions Reassigning (Moving) a Cell to a Different nPartition Reassigning (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. Adding (assigning) the cell to the new nPartition. 4.
Managing nPartitions Reassigning (Moving) a Cell to a Different nPartition Reassigning (Moving) a Cell to a Different nPartition The following high-level procedure moves a cell to a different nPartition. You can perform these steps using either HP-UX commands or Partition Manager. Step 1. See the procedure Unassigning (Removing) Cells from an nPartition on page 273 to remove the cell that you want to move to the other nPartition.
Managing nPartitions Restoring a Complex Profile 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.
Managing nPartitions Restoring a Complex Profile G - Build genesis complex profile L - Restore last complex profile Select profile to build or restore: L Do you want to modify the complex profile? (Y/[N]) y -> The complex profile will be modified. GSP:CM> Step 4. Confirm that the nPartition cell assignments are what you intended to establish. Use the service processor Command menu’s CP command to display the current complex profile configuration.
Managing nPartitions Unlocking Complex Profiles Unlocking Complex Profiles This section describes how you can force-unlock portions of the nPartition Complex Profile data CAUTION Do not force-unlock complex profile data except in extremely rare cases following nPartition or server crashes. Improperly force-unlocking complex profiles can result in the loss of pending configuration changes to nPartitions and the server complex.
Managing nPartitions Unlocking Complex Profiles 306 HP System Partitions Guide: Administration for nPartitions, rev 5.
7 Listing and Managing Server Hardware This chapter covers the tools and procedures 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. For an introduction to nPartition servers and hardware features, refer to the chapter nPartition System Overviews on page 31. HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Tools for Listing and Managing Hardware 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 • Partition Manager ( /opt/parmgr/bin/parmgr) Partition Manager provides a graphical interface for managing and monitoring nPartitions 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 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 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 Powering Server Cabinets On and Off [Service Processor] This procedure (Virtual Front Panel, and Command menu’s PE command) turns a cabinet’s 48-volt power on or off using the service processor (GSP or MP). Step 1. Login 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 Enter cabinet number: 1 The power state is ON for Cabinet 1. In what state do you want the power? (ON/OFF) HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off 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 The service processor Command menu’s PE command permits you to power on or off any hardware in the complex, including active cells and I/O chassis. The PE command does not check the current usage of components. Powering Cells and I/O Chassis On and Off [Service Processor] This procedure (Command menu, PE command) powers on and powers off cells, I/O chassis, and cabinets using the service processor interface (GSP or MP).
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off • Cells—When you power on or off a cell, the firmware also powers on or off any I/O chassis attached to the cell. When specifying a cell, you indicate both the cabinet number and the slot in which the cell resides.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off You cannot power off active cells or power on or off cells assigned to a remote nPartition when using frupower. To power on or off an I/O chassis using frupower, do so by power cycling the cell to which it is connected. Step 1. Login to HP-UX running on one of the system’s nPartitions. To manage a cell’s power, you must login to the nPartition to which the cell is assigned.
Listing and Managing Server Hardware Powering Cells and I/O Chassis On and Off Powering Cells and I/O Chassis On and Off [Partition Manager] This procedure (Cell —> Power On Cell menu, or Cell —> Power Off Cell menu) powers on and powers off cells (and their associated I/O chassis) using Partition Manager. NOTE You can use Partition Manager to power on or off inactive cells that are assigned to the local nPartition.
Listing and Managing Server Hardware Power Status for Hardware Components Power Status for Hardware Components You can use system software to check power status for the following components from remote locations: NOTE • 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 Power Status for Hardware Components Determining Hardware Power Status [Service Processor] This procedure (Command menu, PS command) checks power status for cabinets, bulk power supplies and power boards, cells, and core I/O using the service processor. Step 1. Login 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 Power Status for Hardware Components • Cabinet Power—Whether the 48-volt cabinet power switch is on or off, whether cabinet power is enabled, and details about power boards and bulk power supplies. • Cell Power—Whether power is enabled and on for all cells within the cabinet. • Core I/O Card Power—Whether power is enabled and on for all core I/O cards within the cabinet.
Listing and Managing Server Hardware Power Status for Hardware Components Determining Hardware Power Status [HP-UX] This procedure (parstatus -B, parstatus -V -b#, frupower -d -C, frupower -d -I, or rad -q) checks the power status for system hardware from HP-UX. For details on these HP-UX commands, see the online manpages for parstatus (1M), frupower (1M), and rad (1M). Step 1. Login to HP-UX running on one of the system’s nPartitions.
Listing and Managing Server Hardware Power Status for Hardware Components # 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 Supply 0 ok Power Supply 1 ok Power
Listing and Managing Server Hardware Power Status for Hardware Components Determining Hardware Power Status [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 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 326 lists attention indicator meanings and LED states (off, blinking, and on). These states and meanings adhere to the PCI Hot-Plug specification.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off 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.) Table 7-1 Attention Indicator (LED) States and Meanings Attention Indicator State Meaning OFF Not selected.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off On HP rp7410 and rp8400 servers only, you also can view each PCI slot’s attention indicator beneath the corresponding slot, on the cabinet’s external chassis at the rear of the server cabinet. • Cabinet Number LCDs On HP Superdome servers only, each cabinet has a cabinet number LCD that serves as the cabinet’s attention indicator.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off — Blink: The fruled -o -c# command blinks the attention indicator for the specified cell (-c#). • I/O Chassis—Use fruled to blink or turn off HP Superdome I/O chassis attention indicators. Specify the I/O chassis using cabinet/bay/chassis notation (#/#/#). — Turn Off: The fruled -f -i#/#/# command turns off the attention indicator for the specified I/O chassis (-i#/#/#).
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off # 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. Blink the cabinet number LCD for # fruled -f -C # fruled -f -I # fruled -f -b0 Turn off all cell and I/O chassis attention indicators and stop blinking the cabinet number LED.
Listing and Managing Server Hardware Turning Attention Indicators (LEDs) On and Off 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 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. Table 7-2 on page 332 lists the processor version info (HVERSIONs) that is reported by the procedures given in this section.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations Table 7-2 Processor (CPU) Versions for Cells HVERSION for HP rp7410 and rp8400 Servers Cell’s Operating CPU Frequency HVERSION for HP Superdome Servers PA8600 — 552 MHz — 0x5c70 PA8700 — 650 MHz 0x5e60 0x5d70 PA8700 — 750 MHz 0x5e40 0x5e70 PA8700 — 875 MHz 0x5eb0 0x5ea0 PA-RISC Processor HVERSIONs Table 7-2 lists the processor HVERSION numbers that are reported for nPartitions and cells.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations Listing Cell Processors and Memory [Service Processor] This procedure (Command menu, PS command) lists cell processor and memory configurations using the service processor Command menu. Step 1. Login to the system’s service processor and enter CM to access the Command menu. You can check processor and memory details for any cell in the complex from the service processor. Step 2.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations GSP:CM> PS This command displays detailed power and hardware configuration status.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations Listing Cell Processors and Memory [BCH] This procedure (Information menu, PR and ME commands) lists cell processor and memory configurations from an nPartition’s BCH interface. Using the BCH interface, you can check these details only for the active cells in the local nPartition. Step 1. Access the BCH interface for the nPartition to which the cell is assigned, and access the BCH Information menu.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations Partition Memory Information Cell DIMM Size ---- -----4 2048MB --6 2048MB --- Rank 0/1 Status --------Active Active DIMM Rank 2/3 Size Status ------ ----------------- Partition Total Memory: Partition Active Memory: Partition Deconfigured Memory: DIMM Rank 4/5 Size Status ------ ----------------- DIMM Rank 6/7 Size Status ------ ----------------- 4096 4096 0 * status is scheduled to change on next boot.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations The following example shows the parstatus -V -c0 command’s output. This presents detailed processor and memory info for cell 0 in cabinet 0. # 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 : : : : : : : : : : : cab0,cell0 0 active core base cab0,bay1,chassis3 yes 10.
Listing and Managing Server Hardware Listing Cell Processor and Memory Configurations Step 4. Click the CPUs/Memory tab to list the selected cell’s processor and memory configurations. 338 HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory Deconfiguring Cells, Processors, and Memory You can deconfigure (make inactive) a cell that is assigned to an nPartition by setting its use-on-next-boot value to “n” (do not use). This causes the cell to remain assigned to the nPartition, but the cell will be inactive the next time its nPartition boots, meaning the cell’s resources will not be used.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory Step 1. Access the BCH interface for the nPartition whose cells, processors, or memory you want to configure or deconfigure. Step 2. To change cell or processor configurations, access the Configuration menu. 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.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory When you deallocate a DIMM, all other DIMMs in the rank also will not be used the next time the nPartition boots. 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.
Listing and Managing Server Hardware Deconfiguring Cells, Processors, and Memory You must reboot the partition to allow the new use-on-next-boot values to take effect. The shutdown -R command performs a reboot for reconfig for the nPartition, which allows all cells to reboot, including any currently inactive cells in the nPartition.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number 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. You can use the following procedures: • Listing Product and Serial Numbers [Service Processor] on page 343 This procedure (Command menu, ID command) lists the system complex’s product number and serial number from the service processor.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number 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 Complex Name: Model String: Original Product Number: Current Product Number: Serial Number: Enterprise ID: Number of Supported Cells: Complex Revision Number: feshd4 9000/800/SD16000 A5201A A5201A USR2025FP2 0x2020202020202020 32 1.0 Information Menu: Enter command > Listing Product and Serial Numbers [HP-UX] This procedure (parstatus -X) lists a system complex’s product number and its serial number from HP-UX.
Listing and Managing Server Hardware Listing the Server Product Number and Serial Number Step 2. Select the Complex —> Show Complex Details menu item. The Complex Details window displays the complex’s product and serial numbers through the General tab. 346 HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Checking Blower and Fan Status 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. NOTE Different HP server and cabinet models have different blower and fan configurations.
Listing and Managing Server Hardware Checking Blower and Fan Status Checking Fan Status [HP-UX] This procedure (parstatus -B or parstatus -V -b#) lists the status of blowers and fans from HP-UX. Step 1. Login to HP-UX running on any of the system’s nPartitions. You can check blower and fan details from HP-UX running on any nPartition. 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 Fan 3 ok I/O Fans ============== Fan 0 ok Fan 1 failed Fan 2 ok Fan 3 ok Fan 4 ok Bulk Power Supplies(BPS) ======================== Power Supply 0 ok .... Checking Fan Status [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.
Listing and Managing Server Hardware Complex Health Analysis of a Server Complex Health Analysis of a Server 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 Complex Health Analysis of a Server HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Listing the Cabinets in a Server Complex 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. You can use the following procedures: • Listing Cabinets [Service Processor] on page 352 This procedure (Command menu, DU command) lists all cabinets in the server complex using the service processor.
Listing and Managing Server Hardware Listing the Cabinets in a Server Complex | 8 | | * | * | | * | * | | | GSP:CM> Listing Cabinets [HP-UX] This procedure (parstatus -B or parstatus -V -b#) lists cabinet details from HP-UX. Step 1. Login to HP-UX running on any of the server’s nPartitions. You can list cabinet information from any nPartition. 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 Listing the nPartitions in a Server You can list details about the nPartitions defined in a server complex, including the partition numbers, nPartition names, and the cells assigned to the nPartitions. You can use the following procedures: • Listing nPartitions [Service Processor] on page 354 This procedure (Command menu, CP command) lists all nPartitions using the service processor.
Listing and Managing Server Hardware Listing the nPartitions in a Server Part 1 |.*..| GSP:CM> Listing nPartitions [HP-UX] This procedure (parstatus -P) lists a server’s nPartitions from HP-UX. Step 1. Login to HP-UX running on any of the server’s nPartitions. You can list all nPartitions from any nPartition 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 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 Step 2. Issue the service processor Command menu’s ID command to list the complex’s name. 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.
Listing and Managing Server Hardware Naming or Renaming a Server Complex The pop-up window shows the current complex name. If no name was previously assigned, the default name is “MyComplex”. Step 4. Click OK to set the new name or click Cancel to keep the previously assigned name. 358 HP System Partitions Guide: Administration for nPartitions, rev 5.
Listing and Managing Server Hardware Checking for Power Supply Failures 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 You can check power details from HP-UX running on any nPartition. Step 2. Issue the parstatus -B command for a brief summary of all cabinets including power status, or issue the parstatus -V -b# command for 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.
Listing and Managing Server Hardware Checking for Power Supply Failures ====================== Power Supply 0 ok Power Supply 1 ok Power Supply 2 ok Notes: N+ N N? = = = = There are one or more spare items (fans/power supplies). The number of items meets but does not exceed the need. There are insufficient items to meet the need. The adequacy of the cooling system/power supplies is unknown.
Listing and Managing Server Hardware Checking for Memory DIMM Failures Checking for Memory DIMM Failures You can list cell memory configurations and check for memory DIMM failures using software tools and utilities. You can use the following procedures: • Checking Memory Status [HP-UX] on page 362 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 In the following example, eight DIMMs (0A–0D and 1A–1D) are installed and are available (“ok”) for use by the cell’s nPartition. # parstatus -V -c0 [Cell] Hardware Location Global Cell Number Actual Usage Normal Usage Connected To : : : : : cab0,cell0 0 active core base cab0,bay0,chassis1 ....
Listing and Managing Server Hardware Checking for Memory DIMM Failures In the above example, if any DIMM had failed its status would be “failed” and all other DIMMs in its rank (for instance, rank 0 or rank 1) also would be listed as failed. Any one or more of the failed DIMMs might have been software deallocated or might have failed self tests. In either case, all DIMMs in the rank automatically are deallocated when any of the rank’s DIMMs fails or is deallocated.
Listing and Managing Server Hardware Checking for Processor Failures Checking for Processor Failures You can list cell processor configuration, including any processor failures, using software tools and utilities. You can use the following procedures: • Checking Processor Status [HP-UX] on page 365 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 Core Cell Capable Firmware Revision Failure Usage Use On Next Boot Partition Number Partition Name : : : : : : no 32.5 activate yes 0 betty [CPU Details] Type : 23664 Speed : 552 MHz CPU Status === ====== 0 ok 1 failed 2 ok 3 failed CPUs =========== OK : 2 Failed : 2 Max : 4 ....
8 Online Add and Replacement (OLAR) of PCI Cards This chapter presents background information and procedures for performing PCI I/O card online addition and replacement (OLAR) on HP’s nPartition servers. The main procedures for adding and replacing PCI cards are: • Online Addition (OLA) for a PCI Card on page 385 • Online Replacement (OLR) for a PCI Card on page 391 See the sections that follow for info on tools, requirements, limitations, and other PCI card OLAR details.
Online Add and Replacement (OLAR) of PCI Cards Overview of PCI Card Online Addition and Replacement (OLAR) Overview of PCI Card Online Addition and Replacement (OLAR) HP-UX 11i supports online addition and replacement (OLAR) of PCI I/O cards on HP nPartition systems. Without rebooting HP-UX running on an nPartition, you can add or replace PCI cards whose device drivers support OLAR.
Online Add and Replacement (OLAR) of PCI Cards OLAR Tools and Interfaces OLAR Tools and Interfaces This section discusses the tools available for performing online card addition and replacement tasks. Also given here are example uses of some of the commonly used OLAR commands and interfaces. The primary tools for performing PCI card OLAR tasks are the System Administration Manager utility (SAM, /usr/sbin/sam) and Partition Manager (/opt/parmgr/bin/parmgr).
Online Add and Replacement (OLAR) of PCI Cards OLAR Tools and Interfaces Table 8-1 Tools and Interfaces for PCI Card Online Addition and Replacement (OLAR) (Continued) OLAR Tool/Interface Partition Manager Description /opt/parmgr/bin/parmgr Partition Manager’s interface is exclusively a GUI. In addition to supporting nPartition administration tasks, Partition Manager has complete support for PCI card OLAR.
Online Add and Replacement (OLAR) of PCI Cards OLAR Tools and Interfaces Table 8-1 Tools and Interfaces for PCI Card Online Addition and Replacement (OLAR) (Continued) OLAR Tool/Interface Scripts in the directory /usr/sbin/olrad.d/ Description Each OLAR-capable card’s driver(s) may have associated scripts in the /usr/sbin/olrad.d/ directory. Each driver’s script accepts the following command-line arguments: the action to perform and path for the slot for which the action is performed.
Online Add and Replacement (OLAR) of PCI Cards Example Uses of Common rad Commands Example Uses of Common rad Commands This section gives summaries and examples uses of common rad commands and options. Table 8-2 rad Command Commonly Used Options Command Description rad -q Displays the status of all OLAR-capable slots in the local nPartition. Only displays slots in currently active I/O chassis. rad -N path Lists the slot ID for the specified hardware path (path).
Online Add and Replacement (OLAR) of PCI Cards Example Uses of Common rad Commands 0-0-0-7 0-0-0-8 # 0/0/2/0 0/0/1/0 16 8 33 33 On On No No N/A N/A N/A N/A rad -N path To determine which card slot corresponds to a hardware path, use the rad -N path command. The rad -N path command lists the card slot used by the device whose hardware path you specify. The slot is reported in cabinet-bay-chassis-slot format. # rad -N 0/0/6/0/0.6.
Online Add and Replacement (OLAR) of PCI Cards Requirements for OLAR Operations Requirements for OLAR Operations To perform a card addition or card removal-and-replacement operation, the following system requirements must be met: • The add or replace operation must be supported on the system hardware. All HP nPartition servers support PCI card OLAR. • The replacement PCI card must be identical to the original card.
Online Add and Replacement (OLAR) of PCI Cards Requirements for OLAR Operations • The card must fit into the slot. On all nPartition servers, all PCI card slots can accept PCI cards keyed as universal cards. However, in nPartition server I/O chassis the PCI card slots also are physically keyed to accept cards that either are keyed as 5-volt cards or keyed as 3.3-volt cards. See the chapter nPartition System Overviews on page 31 for details on I/O slot capabilities.
Online Add and Replacement (OLAR) of PCI Cards PCI Card OLAR Considerations PCI Card OLAR Considerations This section discusses two issues of possible concern when performing PCI card OLAR tasks: card slot power domains, and multi-function cards. Power Domains Each power domain consists of all the PCI card slots that are powered on or off together as a unit. On HP nPartition servers each slot is in its own power domain, which allows each slot to power on or off without affecting any other slots.
Online Add and Replacement (OLAR) of PCI Cards Multi-Function Cards To list all functions provided by a PCI card slot, use the rad -h slot command. For example, the following rad command lists all hardware paths associated with slot 0-1-3-8 (cabinet 0, bay 1, chassis 3, slot 8). # rad -h 0-1-3-8 0/0/11/0/0 0/0/11/0/1 # As the above example shows, slot 0-1-3-8 has two functions, one at each of the hardware paths listed. To list all drivers bound to a multi-function card, use the rad -c slot command.
Online Add and Replacement (OLAR) of PCI Cards PCI Card Slot Latches and Doorbells PCI Card Slot Latches and Doorbells NOTE This section applies only to HP rp7410 and rp8400 servers. This section introduces two features of HP rp7410 and rp8400 server I/O chassis: PCI card slot latches and PCI card slot doorbell buttons. PCI Card Slot Latches Both HP rp7410 and rp8400 servers have slot latches for all PCI card slots; each PCI card slot has its own latch.
Online Add and Replacement (OLAR) of PCI Cards PCI Card Slot “Doorbells” Figure 8-1 PCI Card Slot Latches (HP rp7410 and rp8400) PCI Card Slot “Doorbells” NOTE This section applies only to HP rp7410 and rp8400 servers. The “doorbell” buttons currently have no functions. Pressing a card slot doorbell button has no impact on system operations. On both HP rp7410 and rp8400 servers, access to the doorbell buttons is prevented by a plastic covering.
Online Add and Replacement (OLAR) of PCI Cards Determining PCI Card Slot Locations Determining PCI Card Slot Locations This section describes how to determine which PCI card slot is used by a filesystem, network interface, or hardware path (such as a boot device path). You may want to identify which PCI cards are used by critical and non-critical system resources when planning for card replacement or nPartition reconfiguration.
Online Add and Replacement (OLAR) of PCI Cards Determining PCI Card Slot Locations Determining a Network Interface’s PCI Card Slot This procedure determines which PCI card slot is used by a network interface. Step 1. At the HP-UX command line, enter the /usr/sbin/lanscan command to list the local nPartition’s LAN devices and status. Step 2. Enter the rad -N path command, and specify the hardware path (path) for the network interface whose card slot information you want.
Online Add and Replacement (OLAR) of PCI Cards Determining PCI Card Slot Locations Step 4. Enter the rad -N path command and specify the hardware path (path), which lssf reported as the “address” of the filesystem’s physical volume. The rad command displays the hardware slot for the filesystem’s card, in cabinet-bay-chassis-slot format. Example 8-3 Example of Determining a Filesystem’s PCI Card Slot This example determines which PCI card (0-1-3-5) supports the /stand filesystem.
Online Add and Replacement (OLAR) of PCI Cards Determining PCI Card Slot Locations The rad command displays the hardware slot corresponding to the boot path, in cabinet-bay-chassis-slot format. Example 8-4 Example of Determining a Boot Device Path’s PCI Card Slot # parstatus -w The local partition number is 0. # parstatus -V -p0 | grep Path Primary Boot Path : 0/0/6/0/0.6.0 Alternate Boot Path : 0/0/6/0/0.5.0 HA Alternate Boot Path : 2/0/14/0/0.6.0 # rad -N 0/0/6/0/0.6.
Online Add and Replacement (OLAR) of PCI Cards Checklist for Preparing for PCI Card OLAR Checklist for Preparing for PCI Card OLAR This section reviews the items that you must check when adding or replacing a PCI card. Most of the items in the following checklist are incorporated into the card addition and replacement procedures that follow. ❏ Review and follow all server power and safety guidelines and any related guidelines for rack operation.
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card Online Addition (OLA) for a PCI Card This section describes the procedure for adding a new PCI card on an HP nPartition server while HP-UX remains online and running. WARNING When performing this procedure you must follow all server power and safety guidelines and any related guidelines for rack operation. Also follow all site safety, maintenance, and operating procedures.
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card Step 3. Access the list of the local nPartition’s PCI card slots from SAM or Partition Manager. To list cards in SAM, access the Peripheral Devices > Cards area. To list cards in Partition Manager, select the local nPartition in the primary window, then select and open the I/O chassis where the new card will be installed. Step 4.
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card In SAM, select (highlight) the slot, then select the Actions —> Light I/O Slot LED menu item. SAM flashes the selected PCI card slot’s LED. In Partition Manager, select (highlight) the slot, then select the I/O —> Light Chassis and Slot LEDs menu item. Partition Manager flashes the selected PCI card slot’s LED, and on HP Superdome servers also flashes the corresponding I/O chassis LED and cabinet number LCD.
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card Step 9. Click either the Cancel or OK button. To cancel the card addition procedure click the Cancel button. To continue the card addition procedure click the OK button. This proceeds to power off the card’s slot and flash the card’s attention indicator (LED).
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card Step 14. Confirm the location of the card slot where the new PCI card will be installed. At this point, all attention and power indicators (LEDs) for the card slot are visible. The light bars on the card slot’s divider should indicate that the slot is powered off and its attention LED is flashing.
Online Add and Replacement (OLAR) of PCI Cards Online Addition (OLA) for a PCI Card At this point, the card slot is powered on, the slot attention indicator is turned off, and the driver(s) for the card are started to bring the card online. If the new card is not detected in the slot, SAM or Partition Manager indicates this and presents a window indicating the problem.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card Online Replacement (OLR) for a PCI Card This section describes the procedure for replacing a PCI card on an HP nPartition server while HP-UX remains online and running. WARNING When performing this procedure you must follow all server power and safety guidelines and any related guidelines for rack operation. Also follow all site safety, maintenance, and operating procedures.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card To run Partition Manager either enter /opt/parmgr/bin/parmgr from the command line or click the Partition Manager icon in the main SAM area. Step 3. Access the list of the local nPartition’s PCI cards from SAM or Partition Manager. To list cards in SAM, access the Peripheral Devices > Cards area.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card In Partition Manager, select (highlight) the slot, then select the I/O —> Light Chassis and Slot LEDs menu item. Partition Manager flashes the selected PCI card slot’s LED, and on HP Superdome servers also flashes the corresponding I/O chassis LED and cabinet number LCD. From the HP-UX command line, you can issue the rad -f attention slot command to flash the PCI card slot’s attention indicator (LED). B.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card The first lines of the analysis indicate whether the card replacement can or cannot proceed. For example: Critical Resource Analysis for slot 0-1-3-8: No affected resources are in use. If the card resource analysis determines that the card cannot be taken offline, this result is indicated with a “critical” message such as the following output. CRITICAL: Affected resources are essential for system operation.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card CAUTION Complete all steps required for replacing the selected PCI card before clicking the OK button to bring the card back online. Details for removing and replacing the card are covered in the steps that follow. NOTE Clicking the Cancel button on the Replace Cards screen causes the card to remain offline: the card slot remains powered off and the card driver(s) remain suspended.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card At this point, all attention and power indicators (LEDs) for the card slot are visible. The light bars on the replacement card’s slot divider should indicate that the slot is powered off and its attention LED is flashing. Each slot divider corresponds to the PCI card slot to its immediate right (when viewing the I/O chassis by facing the card slots with the top up). Step 15.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card Replace the I/O chassis cover and firmly push it back into place before tightening all thumb screws. Also, as needed, carefully slide all racked equipment back into place before replacing any additional covers and bezels. Close any cabinet or rack doors. Step 23. In the SAM or Partition Manager Replace Card window, click the OK button. Clicking OK indicates that the card has been removed and replaced with a new card.
Online Add and Replacement (OLAR) of PCI Cards Online Replacement (OLR) for a PCI Card 398 HP System Partitions Guide: Administration for nPartitions, rev 5.
9 Processor Instant Capacity on Demand (iCOD) This chapter covers using Hewlett-Packard’s processor iCOD (Instant Capacity on Demand) product on nPartitions. iCOD is an optional software product that enables you to instantly increase or adjust processing power within nPartitions. As you need more or fewer processors, you use iCOD tools to adjust the number of activated processors in the nPartition.
Processor Instant Capacity on Demand (iCOD) Introduction to Processor iCOD on nPartitions Introduction to Processor 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 Version B.04.x and the Instant Capacity on Demand (iCOD) User’s Guide for Version B.05.
Processor Instant Capacity on Demand (iCOD) iCOD Features for nPartitions iCOD Features for nPartitions HP’s iCOD Purchase and iCOD Utility products have some different features and behaviors on nPartition servers than iCOD on other non-partitionable systems. The following list covers some of these unique features. • iCOD on each nPartition is managed locally and independently. iCOD commands affect and list iCOD settings for the local nPartition (the nPartition where the commands are run).
Processor Instant Capacity on Demand (iCOD) iCOD Issues for Managing nPartitions iCOD Issues for Managing nPartitions iCOD introduces several new issues for managing nPartitions. The following list describes some of these new management issues for nPartition systems that have iCOD configured: • At least one iCOD processor must be activated for each active cell in an nPartition.
Processor Instant Capacity on Demand (iCOD) iCOD Issues for Managing nPartitions then the same number of activated iCOD processors are available after performing a reboot for reconfig to make the newly added cell active. For example, in a two-cell nPartition that has six of its eight processors activated with iCOD, adding another four-processor cell brings the total processors to 12. However, the iCOD software keeps the number of activated processors at six (no change).
Processor Instant Capacity on Demand (iCOD) Tools for Managing iCOD Processors 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, see the icod_modify (1M), icod_notify (1M), and icod_stat (1M) manpages.
Processor Instant Capacity on Demand (iCOD) Tools for Managing iCOD Processors When you license iCOD (by using the icod_modify -l... command) you can do so from any nPartition in the server complex. This licenses iCOD for all nPartitions in the server, and only one license is needed for the entire complex. HP System Partitions Guide: Administration for nPartitions, rev 5.
Processor Instant Capacity on Demand (iCOD) iCOD Requirements for nPartition Servers 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.
Processor Instant Capacity on Demand (iCOD) iCOD Requirements for nPartition Servers • For the iCOD software to activate processors, the processors must be configured processors on active cells that are assigned to the local nPartition 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.
Processor Instant Capacity on Demand (iCOD) Installing and Configuring iCOD on nPartitions Installing and Configuring iCOD on nPartitions NOTE 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. Software bundles for iCOD Purchase and iCOD Utility are available on the Support Plus media and at the http://software.hp.
Processor Instant Capacity on Demand (iCOD) Installing and Configuring iCOD on nPartitions Step 2. [An HP service representative must perform this step.] Validate the server complex as an iCOD server. 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 nPartition running iCOD to HP for billing purposes and to request licensing information.
Processor Instant Capacity on Demand (iCOD) Installing and Configuring iCOD on nPartitions Step 6. Use iCOD features: list iCOD statistics with icod_stat and, when required, activate or deactivate processors. To list iCOD configuration details for the local nPartition, use the icod_stat command (with no options).
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions Procedures for Changing Processor 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 412 This procedure (using the icod_modify -a... or icod_modify -d...
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions NOTE The following nPartition changes also can cause iCOD software to activate a different number or set of the nPartition’s processors: adding and removing cells from an nPartition, making cells active or inactive, or configuring or deconfiguring processors from cells in the nPartition. Activating and Deactivating Processors with iCOD This procedure (using the icod_modify -a...
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions Step 2. Issue the icod_modify command with either the -a # option (to activate # processors) or -d # option (to deactivate # processors). You must include the following details after the -a or -d option. This information is recorded in the nPartition’s iCOD change log.
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions You can activate or deactivate processors in only the local nPartition (the nPartition in which you issue the icod_modify command). Step 2. Issue the icod_modify -s... command and specify the number of processors to be activated. You must include the following details after the -s option. This information is recorded in the nPartition’s iCOD change log.
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions Also, both nPartitions must have enough activated or deactivated processors to accommodate the reduction or increase in processors. Step 1. Login to the first nPartition and deactivate the number of processors you plan to activate in the second nPartition. See the procedure Activating and Deactivating Processors with iCOD on page 412, and use the icod_modify -d...
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions Step 2. Consider any software licensing issues or nPartition system configuration issues that you must address when changing from iCOD Purchase to iCOD Utility (pay per use) or vice versa. For example, some nPartitions may have different sets of processors activated as a result of the change.
Processor Instant Capacity on Demand (iCOD) Procedures for Changing Processor iCOD Configurations on nPartitions You must remove the bundle from every nPartition that no longer is under contract. In the case of iCOD Utility contracts this involves removing the bundles from all nPartitions. On nPartitions where iCOD software is installed on multiple boot devices (such as PRI, HAA, and ALT) you should remove the bundle from all devices.
Processor Instant Capacity on Demand (iCOD) Managing iCOD Utility (Pay Per Use) on nPartitions 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 nPartition server complex.
Processor Instant Capacity on Demand (iCOD) Managing iCOD Utility (Pay Per Use) on nPartitions When an nPartition is inactive, all its cells and processors are inactive and cannot be used until the nPartition 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.
Processor Instant Capacity on Demand (iCOD) Managing iCOD Utility (Pay Per Use) on nPartitions To put an nPartition in the 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.
10 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 nPartition. Each Pset has its own processors, schedules, 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 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 HP-UX Processor Numbering and Availability on nPartitions 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 nPartition is booted. HP-UX processor IDs are assigned on a first-come first-numbered basis.
Processor Sets (Psets) on nPartitions Introduction to Psets Processor Count Domain -----0 # The System Default Pset : 5 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. All processors are initially assigned to the default Pset until you configure processors to belong to other Psets.
Processor Sets (Psets) on nPartitions Introduction to Psets Pset Binding and Inheritance 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 Tools for Managing and Using Psets Tools for Managing and Using Psets This section lists several tools for managing Psets. For details, see 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 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, rev 5.
Processor Sets (Psets) on nPartitions Procedures for Managing Psets Procedures for Managing Psets This section lists only the psrset command-line procedures for managing Psets.
Processor Sets (Psets) on nPartitions Procedures for Managing Psets Destroying (Deleting) a Pset /usr/sbin/psrset -d [pset_list | all] where you specify either all (to delete all Psets) or a list of the Psets to be deleted (pset_list). When you delete a Pset, the Pset’s ID no longer exists and all processors assigned to the Pset are assigned to the default Pset. Deleting all Psets (psrset -d all) causes all processors to be assigned to the default Pset (Pset ID 0), which then is the only Pset in the system.
Processor Sets (Psets) on nPartitions Procedures for Managing Psets You cannot modify attributes for Pset ID 0. /usr/sbin/psrset -t pset_id attr_name=attr_value where pset_id is the Pset whose attribute(s) will be configured. Each attribute (attr_name) is set to the corresponding value (attr_value) specified. Attributes include OWNID, GRPID, PERM, and others listed in the psrset (1M) manpage.
Processor Sets (Psets) on nPartitions Procedures for Managing Psets For example “PERM=754” gives the Pset owner execute, write, and read permissions; gives members of the Pset’s group execute and read permissions; and gives other users only read permission. You also can specify attributes and values to change the owner (OWNID) and group (GRPID) for the Pset. Running Programs in a Pset /usr/sbin/psrset -e pset_id command [arguments] where pset_id is the Pset in which the specified command will be executed.
Processor Sets (Psets) on nPartitions Example Uses of Psets Example Uses of Psets NOTE 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. For iCOD management information, refer to the chapter Processor Instant Capacity on Demand (iCOD) on page 399.
Processor Sets (Psets) on nPartitions Example Uses of Psets 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.com:555-5555 4 processors are now active.
Processor Sets (Psets) on nPartitions Example Uses of Psets NONEMPTY EMPTY LASTSPU DFLTPSET FAIL DFLTPSET # Example 10-2 Destroying a Pset and Reassigning Processors List the local nPartition’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 Example Uses of Psets # psrset -d 10 successfully destroyed pset 10 # psrset -i PSET 0 SPU_LIST 0 1 2 3 OWNID 0 GRPID 0 PERM 755 IOINTR ALLOW NONEMPTY DFLTPSET EMPTY FAIL LASTSPU DFLTPSET PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 11 5 6 0 3 755 ALLOW DFLTPSET FAIL DFLTPSET 7 4 9 10 11 8 # Assign processors 4 and 9 to Pset 11 using the psrset -a... command.
Processor Sets (Psets) on nPartitions Example Uses of Psets LASTSPU DFLTPSET # Example 10-3 Example of Running and Binding Programs in Psets List the current Pset configuration for the local nPartition. 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 Example Uses of Psets # psrset -q 10368 PID 10368 PSET # 0 Use the psrset -b... command to change the Pset binding for “potato” to Pset 2. Then use psrset -q... to confirm that it is bound to Pset 2, and use the mpsched -q... command to check its processor binding.
Processor Sets (Psets) on nPartitions Example Uses of Psets All processors in Pset 2 are being used fairly heavily, while processors in Pset 0 are 100% idle. This is due to Pset processor resource isolation: by default each program only uses processors in the Pset in which it is run. (The Pset programming interface can override this default to launch threads and processes in other Psets, given the right conditions.
Processor Sets (Psets) on nPartitions Example Uses of Psets PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 7 9 10 0 3 755 ALLOW DFLTPSET FAIL DFLTPSET PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 8 6 7 0 3 755 ALLOW DFLTPSET FAIL DFLTPSET 11 8 # Modify the group setting for Pset 8 to be group ID 20. Also use psrset -t... to modify the permissions for Pset 8.
Processor Sets (Psets) on nPartitions Example Uses of Psets ann $ id uid=103(ann) gid=20(users) groups=102(prog) ann $ psrset -i PSET 0 SPU_LIST 0 1 2 3 4 5 OWNID 0 GRPID 0 PERM 755 IOINTR ALLOW NONEMPTY DFLTPSET EMPTY FAIL LASTSPU DFLTPSET PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 7 9 10 103 3 755 ALLOW DFLTPSET FAIL DFLTPSET PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 8 6 7 0 20 774 ALLOW DFLTPSET FAIL DFLTPSET 11 8 ann $ Because ann is the owner for Pset 7, she
Processor Sets (Psets) on nPartitions Example Uses of Psets Processor 8 was assigned to Pset 8, but ann can reassign it because she has write permission for Pset 8 (she is a member of group ID 20, which has execute, write, and read permissions). Likewise, ann can assign the processor to Pset 7 because she has write permissions there (she is the owner, and has execute, write, and read permissions). Then ann lists the new configurations for Pset 7 and Pset 8 using the psrset -i 7 8 command.
Processor Sets (Psets) on nPartitions Example Uses of Psets joe $ id uid=102(joe) gid=20(users) joe $ psrset -i PSET 0 SPU_LIST 0 1 2 3 OWNID 0 GRPID 0 PERM 755 IOINTR ALLOW NONEMPTY DFLTPSET EMPTY FAIL LASTSPU DFLTPSET 4 5 PSET 7 SPU_LIST 8 9 10 11 psrset: no privileges for query operation on this pset PSET SPU_LIST OWNID GRPID PERM IOINTR NONEMPTY EMPTY LASTSPU 8 6 7 0 20 774 ALLOW DFLTPSET FAIL DFLTPSET joe $ When joe uses the psrset -e 7...
11 Virtual Partitions (vPars) Management on nPartitions This chapter describes how to create, configure, and manage HP’s Virtual Partitions within an HP Superdome nPartition (hard partition) system environment. Each Virtual Partition can boot a single instance of the HP-UX 11i operating system. The HP Virtual Partitions (vPars) software is an optional feature that you can use to further subdivide a server’s resources into multiple, smaller virtual machines through software partitioning.
Virtual Partitions (vPars) Management on nPartitions Introduction to Managing vPars on nPartitions Introduction to Managing vPars on nPartitions This section describes the basic features of Virtual Partitions running in nPartitions on an HP Superdome server. The current A.02.01 release of the HP vPars software does not support HP rp7410 or rp8400 servers.
Virtual Partitions (vPars) Management on nPartitions Introduction to Managing vPars on nPartitions vPar Hardware On HP nPartition servers, each Virtual Partition is assigned a subset of its nPartition’s hardware. Only the active hardware assigned to the local nPartition can be used by vPars within the nPartition. Hardware that is assigned to remote nPartitions and hardware that is inactive cannot be used by vPars in the local nPartition.
Virtual Partitions (vPars) Management on nPartitions Introduction to Managing vPars on nPartitions You can load and run a vPars-enabled HP-UX 11i kernel in both vPar environments and non-vPars environments. You do not need to reconfigure a vPars-enabled kernel for non-vPars use.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Resources and Attributes Configuring vPar Resources and Attributes When creating or reconfiguring a Virtual Partition, you manage resources and attributes that determine the vPar’s configuration and capabilities. Each Virtual Partition has three types of resources: cpu, io, and mem, which specify processor(s), I/O, and memory allocated exclusively for the vPar.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Resources and Attributes You can add (-a), delete (-d), and modify (-m) vPar hardware resources and attributes. Also see the vparresources (5) manpage for details. Descriptions of processor (cpu), I/O (io), and memory (mem) vPar hardware resource attributes are in the following list. — Processors (cpu) resources — You can specify the following attributes for processors: The path of one or more processors that are bound to the vPar.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Resources and Attributes For example, to configure a vPar to have 2 GBytes (2048 MBytes) of memory allocated: # vparmodify -p name -m mem::2048 HP recommends that you only specify the total amount of memory to be allocated for each vPar. On all supported HP vPar systems there is no benefit to specifying the base and range for memory.
Virtual Partitions (vPars) Management on nPartitions Tools for Managing vPars on nPartition Servers Tools for Managing vPars on nPartition Servers The main tools for vPars administration are the HP-UX vPars commands and the Virtual Partition Manager (vparmgr) utility. This section briefly lists these and other tools and commands you can use for managing Virtual Partitions on HP nPartition servers.
Virtual Partitions (vPars) Management on nPartitions Tools for Managing vPars on nPartition Servers NOTE The Virtual Partition Manager utility is not installed as part of the Virtual Partitions software product installation. Instead, you must install Virtual Partition Manager separately, as described in the the book Installing and Managing HP-UX Virtual Partitions (vPars). Using the Virtual Partition Manager utility requires root permission.
Virtual Partitions (vPars) Management on nPartitions Tools for Managing vPars on nPartition Servers Virtual Partition Manager has online help that you can view at any time by clicking the Help button, which displays info in a separate Web browser. You also can view Virtual Partition Manager help from a Web browser by issuing the following command: /opt/netscape/netscape file:/opt/webadmin/vparmgr/help/C/overview.html See the online help for complete details on using the Virtual Partition Manager.
Virtual Partitions (vPars) Management on nPartitions Tools for Managing vPars on nPartition Servers • HP-UX setboot Command The HP-UX setboot command affects the current vPar’s boot settings (stored in its /stand/vpdb) when you use it in a vPar environment. When used in a non-vPars nPartition environment, the setboot command affects the local nPartition’s boot settings. The nPartition boot device paths are stored in the nPartition’s Partition Configuration Data portion of the server’s Complex Profile.
Virtual Partitions (vPars) Management on nPartitions Tools for Managing vPars on nPartition Servers The vPars monitor commands include: reboot (reboot the nPartition), vparload (load/boot one or more vPars), scan (scan and list all active hardware in the local nPartition), log (list recent history from the vPars monitor’s event log), and other commands. The vPars monitor’s MON> prompt is available when the nPartition’s monarch processor is not assigned to a vPar that has been loaded/booted.
Virtual Partitions (vPars) Management on nPartitions vPars Requirements and Recommendations vPars Requirements and Recommendations HP offers the following requirements and recommendations for configuring Virtual Partitions in HP Superdome nPartition environments. Additional recommendations for avoiding obstacles to loading/booting vPars are in Fault-Tolerant vPar Configurations for nPartitions on page 458. Also see the HP-UX Virtual Partitions Ordering and Configuration Guide.
Virtual Partitions (vPars) Management on nPartitions vPars Requirements and Recommendations Adding or removing hardware from an nPartition changes the local set of hardware that is available to vPars in the nPartition. Likewise, making nPartition hardware inactive makes it unavailable to vPars. ❏ At least one processor must be bound to each vPar. Only bound processors can handle I/O interrupts. Other processors in the vPar can be either bound or unbound.
Virtual Partitions (vPars) Management on nPartitions vPars Requirements and Recommendations HP recommends that, for best performance, you do not configure HP-UX lan0 to use the nPartition’s Core I/O LAN (on HP Superdome servers, the LAN at hardware path cell/0/0/1/0). The HP Superdome Core I/O card is a PCI-1x card that possibly provides lower performance than a comparable PCI-2x or PCI-4x card. ❏ If you require that a vPar not be reconfigured then you should set the vPar to be “static”.
Virtual Partitions (vPars) Management on nPartitions Fault-Tolerant vPar Configurations for nPartitions Fault-Tolerant vPar Configurations for nPartitions You should consider the following recommendation if you intend to establish Virtual Partition configurations that are tolerant of failures, such as hardware self-test failures, or nPartition configuration changes, such as removing a cell from an nPartition.
Virtual Partitions (vPars) Management on nPartitions Fault-Tolerant vPar Configurations for nPartitions The bound attribute value cannot exceed the min attribute, and so the total of all bound processor attributes for all vPars within an nPartition also should not exceed the following amount: [(active_cells - 1) * (processors_per_cell)] When a bound processor is unavailable, the vPars monitor assigns and binds a different processor in its place.
Virtual Partitions (vPars) Management on nPartitions Fault-Tolerant vPar Configurations for nPartitions ❏ If possible, configure disks in separate I/O chassis for each vPar’s boot and altboot attributes (the PRI and ALT device paths for the vPar). Having each vPar’s boot and altboot devices on separate I/O chassis permits the vPars to load and boot HP-UX even in the event of a cell failure or I/O chassis failure.
Virtual Partitions (vPars) Management on nPartitions Dynamic vPars and Static vPars Dynamic vPars and Static vPars Each Virtual Partition has a static/dynamic attribute that determines whether resource changes can be made to the vPar. A static vPar cannot have any modifications made to its resource profile. This means that the Virtual Partition’s processor, memory, and I/O characteristics and assignments cannot be changed, even if the vPar is not running (in a “Down” state).
Virtual Partitions (vPars) Management on nPartitions Dynamic vPars and Static vPars CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== Shad 2/ 8 2 0 8 0/ 0 2048 Mesh 2/ 12 2 6 3 0/ 0 2048 # vparmodify -p Mesh -m cpu::4 vparmodify: Error: Virtual partition Mesh is static, cannot modify resources. # 462 HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions vPar Configuration Data on nPartitions vPar Configuration Data on nPartitions This section covers configuration data issues related to using vPars in nPartitions on HP Superdome servers. Virtual Partition configuration data by default is stored in the /stand/vpdb file, although you can specify that another file be used as the vPars database.
Virtual Partitions (vPars) Management on nPartitions vPar Configuration Data on nPartitions For example: when a vPar boots from its ALT device path and has a config change, and then the vPar’s nPartition reboots and loads /stand/vpmon from the same vPar’s PRI device path, then as a result the latest vPar config changes are not used (but they still reside on the vPar’s ALT device).
Virtual Partitions (vPars) Management on nPartitions vPar Console and Log Use on nPartition Servers vPar Console and Log Use on nPartition Servers On HP Superdome servers, each nPartition has its own console and its own console log that stores a record of recent console activity. When an nPartition has one or more vPars booted, the nPartition console serves as the console for all vPars loaded/booted in the nPartition.
Virtual Partitions (vPars) Management on nPartitions vPar Console and Log Use on nPartition Servers The nPartition console log also records vPars monitor (vpmon, MON> prompt) output for its nPartition, because the vPars monitor interface is accessed and displayed through the Virtual Partition’s nPartition console. The vpmon event logs file—which is viewable from the vparstatus -e command or the vPars monitor’s log command—only records vPar events. It does not record any nPartition chassis codes.
Virtual Partitions (vPars) Management on nPartitions Planning vPar Configurations for HP nPartition Servers Planning vPar Configurations for HP nPartition Servers You can use this section to help plan the Virtual Partition configurations you will establish in nPartitions.
Virtual Partitions (vPars) Management on nPartitions Listing Available nPartition Hardware Resources Listing Available nPartition Hardware Resources This section presents how you can list all available hardware resources in an nPartition server. The following are common methods of listing available hardware: • vparstatus -A lists the available processor, I/O, and memory resources in the local nPartition. This command lists the hardware that has not yet been assigned to any vPar.
Virtual Partitions (vPars) Management on nPartitions vPar Configuration Planning vPar Configuration Planning Table 11-1 is for planning vPar attributes and resource assignments. For each vPar, you must specify: a vPar name, at least one bound CPU, at least one I/O slot, a PRI boot path, and enough memory to boot HP-UX. The default vPar attributes establish a dynamic configuration that manually boots the /stand/vmunix kernel with no boot options.
Virtual Partitions (vPars) Management on nPartitions Installing and Configuring vPars on nPartition Servers Installing and Configuring vPars on nPartition Servers This section covers information on installing the vPars software product onto disks that will be used for booting HP-UX on a Virtual Partition that is loaded in an nPartition. After a boot disk has both HP-UX and the vPars software product installed, the disk can be booted to be used in either vPar or non-vPars environments.
Virtual Partitions (vPars) Management on nPartitions Installing and Configuring vPars on nPartition Servers vPars Software Installation for an HP nPartition This procedure gives a high-level overview of a process for manually installing HP’s Virtual Partitions software product on an nPartition’s disks. The book Read Before Installing HP-UX Virtual Partitions has important information you should read before performing this procedure.
Virtual Partitions (vPars) Management on nPartitions Installing and Configuring vPars on nPartition Servers If you want to create multiple vPars within an nPartition you can do so as part of this step, by issuing a vparcreate command for each new Virtual Partition within the local nPartition. You also can create any additional vPars later, after you have booted the vPars monitor and loaded/booted HP-UX 11i on the first Virtual Partition. Step 4.
Virtual Partitions (vPars) Management on nPartitions Procedures for Managing vPars on HP nPartition Servers Procedures for Managing vPars on HP nPartition Servers This section has procedures for performing typical Virtual Partitions configuration and management tasks on HP Superdome servers.
Virtual Partitions (vPars) Management on nPartitions Procedures for Managing vPars on HP nPartition Servers The book Installing and Managing HP-UX Virtual Partitions (vPars) also has detailed vPars management information. 474 HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Creating a New vPar Creating a New vPar This section gives details on how to create a new Virtual Partition. NOTE Before creating a Virtual Partition you should already have planned how the local nPartition’s resources will be assigned to the vPars running in the local nPartition. See the section Planning vPar Configurations for HP nPartition Servers on page 467 for info on planning vPars configurations for use in nPartitions.
Virtual Partitions (vPars) Management on nPartitions Creating a New vPar 6.10 6.11 6.12 6.13 [Available CPUs]: 12 [Available I/O devices (path)]: [Unbound memory (Base /Range)]: (bytes) (MB) [Available memory (MB)]: 6144 # 0.0.1 0.0.3 0.0.8 0.0.9 0.0.10 0.0.11 0.0.12 0.0.14 2.0 2.0.0 2.0.1 2.0.2 2.0.3 2.0.4 2.0.6 2.0.8 2.0.9 2.0.10 2.0.11 2.0.12 2.0.14 0x0/64 0x8000000/6080 Step 3. Issue the vparcreate -p... command to create the new vPar and as needed use vparmodify -p...
Virtual Partitions (vPars) Management on nPartitions Creating a New vPar To further modify the vPar, issue the vparmodify command after vparcreate has created the new vPar. For other details on creating and configuring vPars see the section Configuring vPar Resources and Attributes on page 447. Step 4. Issue the vparstatus command to list the configuration and boot status for the newly created vPar. For detailed vPar information, use the vparstatus -v -p... command.
Virtual Partitions (vPars) Management on nPartitions Creating a New vPar (bytes) (MB) Total Memory (MB): 2048 # 478 HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Deleting a vPar Deleting a vPar This section describes the procedure for deleting a vPar and related issues you may encounter. NOTE The vPar you delete must be in a “Down” state. You can delete Virtual Partitions that are defined in the currently active vPars database (vpdb) used by the local nPartition. You also can delete vPars from an alternate vPars database that you specify using the vparremove command’s -D database option.
Virtual Partitions (vPars) Management on nPartitions Deleting a vPar ============================== Shad Mesh # ================ 2/ 8 2 0 2/ 12 2 0 ==== 7 3 ==================== 0/ 0 2048 0/ 0 0 Step 3. Issue the vparremove -p vpname command to delete the specified vPar (vpname) and then issue the vparstatus command to list the new configuration status. You can delete only vPars that are in a “Down” state, as reported by the vparstatus command (see the example in the previous step).
Virtual Partitions (vPars) Management on nPartitions Modifying vPar Configuration Attributes Modifying vPar Configuration Attributes This section describes how to add or remove resources from a vPar, and how to change a vPar’s attribute settings. Many vPar hardware resource changes require that the vPar being modified is not running (not in an “Up” state).
Virtual Partitions (vPars) Management on nPartitions Modifying vPar Configuration Attributes See the section Configuring vPar Resources and Attributes on page 447 for descriptions of the vPars configuration options. Also see the vparmodify (1M) manpage for details.
Virtual Partitions (vPars) Management on nPartitions Listing the Status for vPars Listing the Status for vPars This section covers methods for listing the status of vPars in an HP Superdome nPartition. You can list vPar status details from HP-UX running on a vPar. You also can list vPars database details for nPartitions that are not booted in vPar mode.
Virtual Partitions (vPars) Management on nPartitions Listing the Status for vPars CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== Shad 2/ 8 2 0 8 0/ 0 2048 Mesh 2/ 12 2 2 3 0/ 0 2048 # # vparstatus -e INFO:CPU0:MON:[17:56:51 5/20/2002 GMT] VPAR Monitor version 0.2 started INFO:CPU0:MON:Version string: @(#) $Revision: vpmon: vw: -selectors: CUP 11.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars Booting HP-UX on vPars This section provides a procedure for loading and booting HP-UX on a Virtual Partition that is running in an nPartition on an HP Superdome server. As part of the vPar boot process, you will boot the /stand/vpmon vPars monitor from the nPartition BCH interface instead of booting the /stand/vmunix HP-UX kernel.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars Step 2. Access the console for the nPartition in which the vPars will boot HP-UX. From the service processor main menu enter CO to access the nPartition console menu, and select the nPartition in which you will boot the vPars. GSP> CO Partitions available: # --0) 1) Q) Name ---feshd4a feshd4b Quit Please select partition number: 0 Step 3.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars • NOTE If vparstatus reports The current virtual partition is... then the nPartition is running one or more vPars. This note applies only when an nPartition is running one or more vPars. Because at least one vPar already has loaded/booted HP-UX on the nPartition, you should check whether the vPar you wish to boot already is loaded, or whether the vPar can be loaded without rebooting HP-UX.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars When using the BOOT command you can specify a boot path variable (for example, BOOT PRI) or a hardware path for the boot device (for example, BOOT 0/0/1/0/1.3). In addition to having the vPars database (vpdb), the device must have both HP-UX 11i and the vPars software product installed. Step 5. Instruct BCH to stop the boot process at the ISL prompt by entering y at the “Do you wish to stop” prompt.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars Step 7. At the vPars monitor’s MON> prompt, enter the vparinfo command to list details about the vPars currently defined in the vPars database (vpdb). Especially note the list of vPars that the vparinfo command displays as the “Names of the partitions in the database”.
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars • To load/boot HP-UX only on the autoboot-enabled vPars, enter: vparload -auto This command loads only the vPars that have the autoboot attribute configured (the boot attribute is set to auto). The following example shows the vPar named “Shad” being loaded from the vPars monitor prompt and booting HP-UX. MON> vparload [MON] Booting [MON] Console [MON] Console -p Shad Shad...
Virtual Partitions (vPars) Management on nPartitions Booting HP-UX on vPars After you login to a vPar running on an nPartition, you can list the current vPar using vparstatus -w, and can list the local nPartition’s partition number using the parstatus -w command. # vparstatus -w The current virtual partition is Shad. # parstatus -w The local partition number is 0. # HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Rebooting or Shutting Down vPars Rebooting or Shutting Down vPars This section describes how to reboot HP-UX in a vPar and how to shut down all vPars running in an nPartition. After shutting down all vPars in an nPartition you can reboot the vPars monitor to reset the nPartition and, after resetting, make the nPartition’s BCH interface available.
Virtual Partitions (vPars) Management on nPartitions Rebooting or Shutting Down vPars vPar Management: Rebooting or Shutting Down vPars in an nPartition The following procedure is for performing a normal reboot (shutdown -r) or a shutdown-and-halt (shutdown -h) in a vPar that is running in an nPartition. This procedure also describes how to halt all vPars in an nPartition and return to the nPartition’s BCH interface. Step 1.
Virtual Partitions (vPars) Management on nPartitions Rebooting or Shutting Down vPars Step 3. From HP-UX running in the vPar you want to shut down, enter the shutdown command with the appropriate command-line options. If shutting down all vPars in the nPartition, use shutdown -h. To shut down and halt HP-UX on the vPar, enter the shutdown -h command along with any additional command-line options you need.
Virtual Partitions (vPars) Management on nPartitions Rebooting or Shutting Down vPars Attempting to boot using the primary path. ------------------------------------------------------------To discontinue, press any key within 10 seconds. HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot Configuring vPar Autoboot This section describes how you can configure an nPartition to automatically boot the Virtual Partitions Monitor and to also boot all vPars that have autoboot configured. For details on automatically booting HP-UX in non-vPars mode on an nPartition, refer to the chapter Booting and Resetting nPartitions on page 197.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot After HP-UX has booted in non-vPars mode on the nPartition, login as root, use the lvdisplay command to list device file for the boot device, and then use the mkboot command to configure the boot device’s AUTO file. You also can use the lifcp command to display the contents of the AUTO file.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot When the nPartition reboots to its BCH interface, it will proceed to boot the device path you specified using nPartition boot paths and path flags. The nPartition then will execute the device’s AUTO file contents that you specified, to load the /stand/vpmon vPars monitor. Finally, because the vPars monitor is invoked with the -a option, it will automatically load/boot all vPars that have autoboot configured.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot Next the user issues the vparstatus command to list the current settings for the vPars defined in the /stand/vpdb file. Because the vparstatus command is issued when the local nPartition is booted in non-vPars mode, the command lists info based on the vpdb file rather than the vPars monitor (which is not running). # vparstatus vparstatus: Warning: Virtual partition monitor not running, Requested resources shown.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot ============================== Mesh # ================ 1/ 2 1 1 ==== 6 ==================== 0/ 0 1024 This example nPartition now is configured so that when the nPartition reboots it will automatically boot from a device that will automatically load a vPars monitor, which then will automatically load/boot the vPar named “Mesh”. In this example’s next step the user reboots the nPartition by issuing the shutdown -r command.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot Firmware Version 35.3 Duplex Console IO Dependent Code (IODC) revision 1 -------------------------------------------------------------------------(c) Copyright 1995-2002, Hewlett-Packard Company, All rights reserved -------------------------------------------------------------------------.... Primary Boot Path: Boot Actions: 0/0/1/0/1.5 Boot from this path. If unsuccessful, go to BCH.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot .... HP-UX Start-up in progress __________________________ Configure system crash dumps ........................................ OK VxVM device node check .............................................. OK .... Start CDE login server .............................................. OK The system is ready. 2/0/1/0/0.5 feshd4b (Mesh) Console Login: [HP Release B.11.
Virtual Partitions (vPars) Management on nPartitions Configuring vPar Autoboot Mesh # 1/ 2 1 1 6 0/ 0 HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Managing nPartitions from a vPar Managing nPartitions from a vPar This section covers the nPartition management issues that are unique to Virtual Partition environments. NOTE In vPar environments, you can apply the same nPartition configuration tools and principles that you use in non-vPars environments—but you must take additional steps to perform a reboot for reconfig of an nPartition that has more than one vPar loaded/booted.
Virtual Partitions (vPars) Management on nPartitions Determining if an nPartition is Running vPars Determining if an nPartition is Running vPars This section gives you several methods for determining if an nPartition has loaded/booted HP-UX in or more vPars. For example, typing Control-a at the nPartition console, or using the vparstatus command. vPar Management: Determining if an nPartition is Running vPars Step 1.
Virtual Partitions (vPars) Management on nPartitions Determining if an nPartition is Running vPars You can type Control-a to switch among the vPar consoles. Each time you type Control-a the name of the current vPar or monitor ([MON]) is displayed in the console window. If HP-UX is running, login as root and issue the vparstatus -w command to list the current vPar’s name. The vparstatus command with no options lists all vPars.
Virtual Partitions (vPars) Management on nPartitions Determining if an nPartition is Running vPars [Virtual Partition Resource Summary] Virtual Partition Name ============================== Shad Mesh # CPU CPU Bound/ Min/Max Unbound ================ 2/ 8 2 0 2/ 12 2 2 Num IO devs ==== 8 3 Memory (MB) # Ranges/ Total MB Total MB ==================== 0/ 0 2048 0/ 0 2048 HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Reboot for Reconfig or Shutdown to Ready for Reconfig from a vPar Reboot for Reconfig or Shutdown to Ready for Reconfig from a vPar This section describes how to perform a reboot for reconfig and how to shut down an nPartition to the ready for reconfig state on nPartitions that are running HP-UX one or more vPars.
Virtual Partitions (vPars) Management on nPartitions Reboot for Reconfig or Shutdown to Ready for Reconfig from a vPar Note: A profile change is pending. rebooted to complete it. The hard partition must be If this note is presented, then in all other vPars at an “Up” or “Load” or “Boot” state issue the shutdown -r command and skip the next step. Step 4. Issue the shutdown command with the options appropriate for the type of reboot you want to perform.
Virtual Partitions (vPars) Management on nPartitions Adding or Removing nPartition Cells from a Virtual Partition Adding or Removing nPartition Cells from a Virtual Partition This section describes how you can add cells and remove cells from an nPartition that is running HP-UX in one or more Virtual Partitions.
Virtual Partitions (vPars) Management on nPartitions Adding or Removing nPartition Cells from a Virtual Partition The following procedure initiates an nPartition cell assignment change from HP-UX running on one vPar (using parmodify or Partition Manager) and then if required performs a reboot for reconfig of the nPartition. Step 1. Login to HP-UX running on one of the vPars in the nPartition you want to reconfigure. You must login as root to perform this procedure. Step 2.
Virtual Partitions (vPars) Management on nPartitions Adding or Removing nPartition Cells from a Virtual Partition Use the parmodify command or Partition Manager to initiate the cell addition or removal. For detailed information on adding or removing the cell see the following list: • You should adhere to HP’s nPartition requirements and guidelines when adding or removing cells from an nPartition; refer to the chapter Planning nPartition Configurations on page 109.
Virtual Partitions (vPars) Management on nPartitions Adding or Removing nPartition Cells from a Virtual Partition Virtual Partition Name ============================== Shad Mesh # Min/Max Unbound ================ 2/ 8 2 0 2/ 12 2 0 devs ==== 7 3 Total MB Total MB ==================== 0/ 0 2048 0/ 0 2048 To perform the reboot for reconfig of the local nPartition: • First issue the shutdown -R command in the current vPar.
Virtual Partitions (vPars) Management on nPartitions Reconfiguring nPartition Attributes from a vPar Reconfiguring nPartition Attributes from a vPar This section describes how you can modify nPartition attributes from HP-UX running in a Virtual Partition in the same server as the nPartition. For details on changing nPartition cell assignments from a vPar, see vPar Management of nPartitions: Adding and Removing nPartition Cells from a vPar on page 510.
Virtual Partitions (vPars) Management on nPartitions Reconfiguring nPartition Attributes from a vPar Step 3. Use the parmodify command or Partition Manager to modify the nPartition’s configuration. (Do not use the setboot command.) For example, parmodify -p0 -P NewName changes nPartition number 0 to be named “NewName”. For other details, refer to the chapter Managing nPartitions on page 245. HP System Partitions Guide: Administration for nPartitions, rev 5.
Virtual Partitions (vPars) Management on nPartitions Reconfiguring nPartition Attributes from a vPar 516 HP System Partitions Guide: Administration for nPartitions, rev 5.
Index About This Book: Overview of Chapters 4 Accessing an nPartition Console and BCH Interface 198 Accessing an nPartition’s BCH Interface 154 Accessing nPartition Console and BCH Interfaces [Service Processor] 198 Accessing Service Processor Interfaces 132 Accessing Superdome Compute Cabinet I/O Chassis and PCI Slots 50 Accessing Superdome IOX I/O Chassis and PCI Card Slots 52 Activating and Deactivating Processors with iCOD 412 Active nPartition 66 Activity Timeout Counter 190 Adding Cells to an nPartiti
Booting an nPartition to the ISL Prompt 207 Booting and Resetting nPartitions 197 Booting from an HP-UX Install Source [BCH] 211 Booting HP-UX in Single-User or LVM-Maintenance Mode [BCH, ISL, and hpux] 209 Booting HP-UX on an nPartition [BCH] 204 Booting HP-UX on vPars 485 Boot-Is-Blocked (BIB) 167 Cabinet Number LCDs 327 Cell IDs in Global Cell Number Format 87 Cell IDs in Hardware Location Format 88 Cell LEDs 326 Cell Properties 61 Cells 47 Chart of Supported HP rp7410 nPartition Configurations 117 Chart
Configuration Process: Selecting Cells for an nPartition 113 Configuration Recommendations for nPartitions 110 Configuration Requirements and Recommendations for Virtual Partitions 455 Configuration Requirements for nPartitions 110 Configuring an nPartition Boot Timer [BCH] 243 Configuring Autoboot and Autostart 234 Configuring Automatic System Restart for a nPartition 236 Configuring Boot Paths and Actions [BCH] 230 Configuring Boot Paths and Actions [HP-UX] 231 Configuring Boot Paths and Boot Actions 228
Destroying (Deleting) a Pset 429 Destroying a Pset and Reassigning Processors 434 Detecting if HP-UX is Running or Hanged on an nPartition 188 Determining a Boot Device Path’s PCI Card Slot 382 Determining a Filesystem’s PCI Card Slot 381 Determining a Network Interface’s PCI Card Slot 381 Determining Hardware Power Status [HP-UX] 322 Determining Hardware Power Status [Partition Manager] 324 Determining Hardware Power Status [Service Processor] 320 Determining if an nPartition is Running vPars 505 Determini
Card Slot Details 54 HP rp7410 Internal Storage Hardware Paths 55 HP rp7410 Server Architecture Overview 37 HP rp7410 Service Processor LAN and Serial Ports 57 HP rp7410 Supported nPartition Configurations 117 HP rp8400 Internal Storage Hardware Paths 56 HP rp8400 Server Architecture Overview 39 HP rp8400 Service Processor LAN and Serial Ports 58 HP rp8400 Supported nPartition Configurations 118 HP Superdome 16-Way (SD16000) Server 40 HP Superdome 16-Way Architecture Overview 41 HP Superdome 32-Way (SD32000
Installing and Configuring iCOD on nPartitions 408 Installing and Configuring vPars on nPartition Servers 470 Interactive Console Access 200 Internal Disk Devices for HP rp7410 and rp8400 Servers 55 Introduction 32 Introduction to Managing vPars on nPartitions 444 Introduction to Processor iCOD on nPartitions 400 Introduction to Psets 422 ioscan Output for a One-Cell HP Superdome nPartition 77 IOX Bezel, Cover, and Bay 53 ISL: Initial System Loader 173 LEDs for Hardware Components 326 Legal Notices 2 Licens
Listing the Local (Current) Partition Number 250 Listing the Local nPartition Number [BCH] 250 Listing the Local nPartition Number [HP-UX] 251 Listing the nPartitions in a Server 354 Listing the Server Product Number and Serial Number 343 Listing the Status for vPars 483 Listing, Creating, and Using Psets 432 Load Balancing Processors across nPartitions with iCOD 414 Local nPartition 64 Log Viewing Options: Activity, Error, and Live Chassis Logs 157 Logging in to a Service Processor 134 Management Tools for
Operator Account 131 Overview of HP Virtual Partitions (vPars) in an nPartition 444 Overview of nPartition Boot Features 170 Overview of nPartitions 60 Overview of PCI Card Online Addition and Replacement (OLAR) 368 Overview of Service Processor (GSP or MP) Menus 137 parcreate Command 93 PA-RISC Processor HVERSIONs 332 parmodify Command 95 parremove Command 98 parstatus Command 99 Partition Configuration Data 68 Partition Manager Primary Window 106 Partition Numbers 64 Partition Rendezvous 167 parunlock Com
Procedures for Managing vPars on HP nPartition Servers 473 Processor (CPU) Versions for Cells 332 Processor Instant Capacity on Demand (iCOD) 399 Processor Sets (Psets) on nPartitions 421 Processors: HP PA-RISC CPUs 48 Publication History 10 rad Command Commonly Used Options 372 rad Command Output in nPartitions 81 Reader Comments and Feedback 3 Ready for Reconfig State 164 Reassigning (Moving) a Cell to a Different nPartition 302 Reassigning (Moving) a Cell to a Different nPartition 301 Reboot 162 Reboot f
Restricted Rights Legend 2 rp7410 Server Model 36 rp8400 Server Model 38 Running Programs in a Pset 431 Selecting Cells for an nPartition 113 Server Hardware Information 8 Service Commands 142 Service Processor (GSP or MP) Introduction 126 Service Processor Accounts and Access Levels 131 Service Processor Features 128 Service Processor for HP rp7410 57 Service Processor for HP rp8400 58 Service Processor for HP Superdome 59 Service Processor Login Session 133 Service Processor: Commonly Used Commands 141 Se
Tools for Listing and Managing Hardware 308 Tools for Managing and Using Psets 426 Tools for Managing iCOD Processors 404 Tools for Managing nPartition Booting 172 Tools for Managing nPartitions 70 Tools for Managing vPars on nPartition Servers 450 Tools Requirements and Limits for Use in Local and Remote nPartitions 65 Troubleshooting Boot Issues 192 Turning Attention Indicators (LEDs) On and Off 325 Turning Attention LEDs On and Off [HP-UX] 327 Turning Attention LEDs On and Off [Partition Manager] 329 Typ
in nPartition Environments 481 vPar Management: Performing a Reboot for Reconfig or Shutdown to Ready for Reconfig from a vPar 508 vPar Management: Rebooting or Shutting Down vPars in an nPartition 493 vPars Requirements and Recommendations 455 vPars Software Installation for an HP nPartition 471 Warranty 2 Web Site for HP Technical Documentation: http://docs.hp.com 7 Web Site for HP Technical Support: http://us-support2.external.hp.com 9 Web Site for Partition Manager Information: http://www.software.hp.
HP System Partitions Guide: Administration for nPartitions, rev 5.
HP System Partitions Guide: Administration for nPartitions, rev 5.
