HP-UX Virtual Partitions Administrator’s Guide Tenth Edition Manufacturing Part Number: T1335-90063 February 2007 United States © Copyright 2007 Hewlett-Packard Development Company L.P. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Trademark Notices Unix is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made.
Information on This Document Intended Audience This document is written for system administrators to help them learn and manage the product HP-UX Virtual Partitions (vPars) on HP-UX 11i v1, 11i v2, and 11i v3. Where to Get the Latest Version of This Document Go to the HP Documentation web site at • For HP-UX 11i v1: http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions • For HP-UX 11i v2: http://docs.hp.com/hpux/11iv2/index.html#Virtual%20Partitions • For HP-UX 11i v3: http://docs.hp.
Contents 1. Introduction What Is vPars? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why Use vPars? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Environments. . . . . .
Contents Choosing the Boot and Lan Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Autoboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Partition Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx . .
Contents Installing vPars with Ignite-UX on PA-RISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing vPars with Ignite-UX on Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing vPars with Software Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the vPars Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Managing: Modifying Attributes of a Virtual Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot||Shut: Booting a Virtual Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot||Shut: Shutting Down or Rebooting a Virtual Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to Shutdown All Virtual Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Memory: Assigning (Adding) Or Deleting By Address Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 GB Restriction (PA-RISC only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory: Available and Assigned Amounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vparstatus: available ILM and CLM memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents CPU: CPU Monitor (formerly known as LPMC Monitor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory, CPU: Canceling Pending Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status: Pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cancel Pending Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents CPU: Adding and Deleting by Total . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vparcreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vparmodify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU: Adding or Deleting by CLP (Cell Local Processor) . . . .
Contents CPU: Determining Whether to Use Bound or Unbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU: Determining When to Specify a Hardware Path for a Bound CPU. . . . . . . . . . . . . . . . . . . . . . . CPU: Adding and Removing Bound CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU Allocation Syntax In Brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 11. vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexible Administrative Capability Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Changing Dynamic Tunables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Migrating OSs from non-vPars Servers to a vPars Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 D. Memory Usage with vPars in nPartitions nPartition Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Partitions (fPars). . . . . . . . .
Tables Table 2-1. PA-RISC vs. Integrity Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Table 2-2. Differences Between vPars Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Table 2-3. To Migrate the Resource, the Target Virtual Partition State must be... . . . . . . . . . . . . . 47 Table 2-4. Dynamic Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 16
1 Introduction This chapter covers: • What Is vPars? • Why Use vPars? • Supported Environments • Product Interaction • Ordering vPars Chapter 1 17
Introduction What Is vPars? What Is vPars? vPars is a Virtual Partitions product that enables you to run multiple instances of HP-UX simultaneously on one hard partition by dividing that hard partition further into virtual partitions. Each virtual partition is assigned its own subset of hardware, runs a separate instance of HP-UX, and hosts its own set of applications. Because each instance of HP-UX is isolated from all other instances, vPars provides application and Operating System (OS) fault isolation.
Introduction What Is vPars? Figure 1-2A Superdome Cabinet A hard partition is any isolated hardware environment, such as an nPartition within a Superdome complex or an entire rp7400/N4000 server. An nPartition is a subset of a complex that divides the complex into groups of cell boards where each group operates independently of other groups. An nPartition can run a single instance of HP-UX or be further divided into virtual partitions.
Introduction What Is vPars? • Processing resources and memory available at boot time can be added to or removed from a virtual partition without rebooting. Why Use vPars? The following are some of the advantages of using vPars. Note that some of these features, such as dynamic memory migration, are only available in more recent releases. vPars Increases Server Utilization and Isolates OS and Application Faults In certain environments, one entire server is dedicated to a single application.
Introduction Supported Environments Supported Environments This section has been moved to the document HP-UX Virtual Partitions Ordering and Configuration Guide, available at http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions and http://docs.hp.com/hpux/11iv2/index.
Introduction HP Product Interaction HP Product Interaction • Processor Terminology Processing resources under vPars, both as input arguments and command outputs, are described as “CPUs.” For multi-core processors such as the PA-8800 and dual-core Intel Itanium 2 processors, the term “CPU” is synonymous with “core.” The term “processor” refers to the hardware component that plugs into a processor socket.
Introduction HP Product Interaction — PCI Error Recovery Product Note — PCI Error Recovery Support Matrix • Support Tools For information on the required version of the Support Tools package that can run on your vPars server, see the section on Online Diagnostics in the HP-UX Virtual Partitions Ordering and Configuration Guide. Prior to STM version A.43.
Introduction HP Product Interaction For example, if you have three virtual partitions, each with one bound CPU, and two unbound CPUs not assigned to any of the partitions, this is a total of five CPUs in the server. Ignite-UX will report three CPUs (one bound and two unbound CPUs) for each partition. The data on unbound CPUs is repeated for each virtual partition. Therefore, adding up the numbers results in a total of nine CPUs for the server when there are actually only five physical CPUs.
Introduction HP Product Interaction Expert recovery works as documented in the Ignite-UX manual; however, you must account for the vPars differences described in “Expert Recovery” on page 330. For more information on using tape devices, see also the paper titled Booting, Installing, Recovery, and Sharing in a vPars Environment from DVD/CDROM/TAPE/Network available at http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions.
Introduction HP Product Interaction Booting the machine into standalone mode from a boot disk which had its OS time ahead of the RTC will advance the RTC. If the machine is then booted into a vPars environment, the OS time of all the virtual partitions will be advanced. Administrators should ensure that the RTC is adjusted accordingly before booting the machine from standalone mode into a vPars environment and vice versa. • SCSI Initiator ID For vPars A.03.
Introduction HP Product Interaction • ioscan output On a PA-RISC system, the ioscan output for vcn and vcs drivers show a value of NO_HW in the S/W State column. On an Integrity server, these drivers do not appear in the ioscan output. This is normal. • intctl command The intctl command is an HP-UX tool that enables management of I/O interrupts among the active CPUs. It can be installed from the HP-UX Software Pack but should be used only by advanced administrators for performance tuning.
Introduction Ordering vPars Ordering vPars For the latest information on ordering vPars, please see the HP-UX Virtual Partitions Release Notes. NOTE 28 The free product known as VPARSBASE is obsolete and is no longer available or supported.
2 How vPars and its Components Work This chapter covers: • Partitioning Using vPars • vPars Monitor and vPars Partition Database • vPars Boot Sequence • EFI and Integrity Notes • Virtual Consoles and Logs • Security Chapter 2 29
How vPars and its Components Work Partitioning Using vPars Partitioning Using vPars To understand how vPars works, compare it to a server not using vPars. Figure 2-1 shows a 4-way HP-UX server. Without vPars, all hardware resources are dedicated to one instance of HP-UX and the applications that are running on this one instance. Figure 2-1 Server without vPars Processor 0 Memory 6 Host PCI Bridge 4 SCSI 0/0 Processor 2 Processor 1 Processor 3 Host PCI Bridge 5 SCSI 0/0 LAN 1/0 LAN 1/0 6.0 6.
How vPars and its Components Work Partitioning Using vPars Figure 2-3 Server Block Diagram with 2 Virtual Partitions Processor 0 Host PCI Bridge 4 SCSI 0/0 Processor 2 Processor 1 Memory (subset) Memory (subset) Processor 3 Host PCI Bridge 5 SCSI 0/0 LAN 1/0 LAN 1/0 6.0 6.0 Each application can run on top of a separate OS instance.
How vPars and its Components Work vPars Monitor and Database vPars Monitor and Database vPars Monitor For each hard partition, the vPars Monitor manages the assignment of hardware resources to virtual partitions, boots virtual partitions and their kernels, and emulates certain firmware calls. By emulating these specific calls, vPars creates the illusion to each HP-UX instance that it is running on a standalone server, consisting of the hardware that has been assigned to it.
How vPars and its Components Work Boot Sequence Boot Sequence This section describes the boot differences in a vPars system relative to a non-vPars system. For information on the HP-UX boot process, ISL, SSL, EFI, and vmunix, see the new HP-UX System Administrator's Guide: Routine Management Tasks available at http://docs.hp.com and also the following manpages: boot (1M) efi (4) hpux (1M) hpux.
How vPars and its Components Work Boot Sequence In a server without vPars, from ISL or EFI, the loader hpux or hpux.efi loads the kernel /stand/vmunix: PA-RISC Integrity ISL> hpux /stand/vmunix HPUX> boot vmunix However, in a server with vPars, from the loader (hpux or hpux.efi) loads the vPars Monitor (/stand/vpmon): PA-RISC Integrity ISL> hpux /stand/vpmon HPUX> boot vpmon The Monitor loads the partition database (the default is /stand/vpdb) from the same disk that /stand/vpmon was booted.
How vPars and its Components Work Virtual Consoles Virtual Consoles HP-UX servers have a special terminal or window called a console that allows special control and displays system error messages. With vPars, each virtual partition has its own virtual console. On Integrity, the console is virtualized by firmware (and therefore, there is no vcs driver). On PA-RISC, for each partition, its console I/O is sent to its vcn (Virtual CoNsole) driver. From the vcn driver, the console I/O is sent to the Monitor.
How vPars and its Components Work Virtual Consoles • Active Console I/O when Multiple Virtual Partitions are Booted It is not deterministic which virtual partition will be active with the physical console when multiple virtual partitions are booted.
How vPars and its Components Work Virtual Consoles If no other virtual partitions are accessible, you must reboot the server or nPartition in order to regain console input. • Toggling Past the Monitor Prompt (A.03.xx only) When the monarch CPU of the server is not assigned to any partition, you will see the Monitor prompt. Press Ctrl-A to cycle to the console window of the next partition.
How vPars and its Components Work Virtual Consoles NOTE 38 For information on logging of the command execution of vpar* commands, see “Commands: vPars Commands Logging” on page 138. Note that vpar* commands can be executed from a root window; it does not require a console window, although at times, such as during the installation of a new virtual partition, a console window may be desired.
How vPars and its Components Work Security Security You should be aware of the following security issues and solutions: • The vPars commands (as described in “Monitor and Shell Commands” on page 119) are restricted to root access, but the commands work on any of the virtual partitions, regardless of which partition the commands are executed from. Therefore, a user with the appropriate privileges on one partition can affect another virtual partition by targeting the virtual partition in a vPars command.
How vPars and its Components Work EFI and Integrity Notes EFI and Integrity Notes • EFI Shell Accessibility After the vPars Monitor (/stand/vpmon) is booted, the EFI shell will not be accessible. This includes using hpux.efi and other EFI commands. If you need to perform any EFI functions, you will need to shut down all the virtual partitions and reboot the nPartition to access the EFI shell. • New vPars Commands The vPars commands introduced in vPars A.04.
How vPars and its Components Work EFI and Integrity Notes The default EFI settings in nPars mode will be inherited when switched to vPars mode. However, when switching back to nPars mode, any EFI settings will be reset to the nPartition defaults, unless otherwise noted (for example, memory granularity). This includes the primary and alternate paths (HAA (High-Availability Alternate) is not supported).
How vPars and its Components Work EFI and Integrity Notes # vparenv -m vPars # shutdown -r ...
How vPars and its Components Work Integrity Differences Relative to PA-RISC Integrity Differences Relative to PA-RISC Beginning with vPars A.04.01, vPars is supported on both Integrity and PA-RISC platforms. This section describes the major conceptual differences for booting and running vPars on Integrity relative to the original vPars on PA-RISC.
How vPars and its Components Work Comparing vPars on PA-RISC and Integrity Comparing vPars on PA-RISC and Integrity This table shows the differences in features between vPars on PA-RISC and Integrity platforms. Table 2-1 PA-RISC vs. Integrity Differences vPars Functionality PA-RISC Integrity Supported OS 11.11 (A.03.xx) 11.23 (A.04.xx) 11.31 (A.05.xx) 11.23 (A.04.xx) 11.31 (A.05.xx) Updates Allowed 11.11 -> 11.23 11.23 -> 11.31 11.23 -> 11.
How vPars and its Components Work Comparing vPars Versions Comparing vPars Versions This tables shows the differences in features among vPars versions. Table 2-2 Differences Between vPars Versions vPars Version A.03.xx A.04.xx A.05.xx Architectures Supported PA-RISC PA-RISC, Integrity PA-RISC, Integrity Product Number T1335AC T1335BC T1335CC Media Format CD DVD DVD OS 11.11 11.23 11.31 Monitor Supports mixed HP-UX 11i v2/v3 vPars no no yes Update Supported N/A 11.11 -> 11.
How vPars and its Components Work Comparing vPars Versions Table 2-2 Differences Between vPars Versions (Continued) vPars Version A.03.xx A.04.xx A.05.xx Flexible Admin Capability yes (A.03.03 and later) yes (A.04.02 and later) yes Tape Boot Support yes (A.03.03 and later) yes (A.04.
How vPars and its Components Work Resource Migration and Required States Resource Migration and Required States The table below shows whether a resource is dynamically migratable; in other words, for each given resource type and vPars version, the intersecting box shows whether the target virtual partition must be up or down to migrate the resource. Table 2-3 To Migrate the Resource, the Target Virtual Partition State must be... Version A.03.
How vPars and its Components Work Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules) Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules) The values in a vPars database that were created using vPars A.03.xx and ported to vPars A.04.xx will have the following A.04.xx meanings for those values; likewise, using vPars A.03.xx syntax on a vPars A.04.xx system has the following A.04.xx meanings. This table summarizes the A.04.xx and A.
How vPars and its Components Work Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules) Table 2-6 CPU Rules from A.03.xx -> A.04.xx/A.05.xx vPars A.03.xx Rules => vPars A.04.xx/A.05.
How vPars and its Components Work Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules) Table 2-6 CPU Rules from A.03.xx -> A.04.xx/A.05.xx (Continued) vPars A.03.xx Rules => vPars A.04.xx/A.05.
How vPars and its Components Work Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules) Table 2-6 CPU Rules from A.03.xx -> A.04.xx/A.05.xx (Continued) vPars A.03.xx Rules => vPars A.04.xx/A.05.
How vPars and its Components Work Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.
3 Planning Your System for Virtual Partitions This chapter covers • Example System • Planning Your Virtual Partitions • Mixed HP-UX 11i v2/v3 vPars Environments (New with vPars A.05.01) Available in vPars A.05.01. See “Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx” on page 68.
Planning Your System for Virtual Partitions full ioscan output of non-cellular system named winona full ioscan output of non-cellular system named winona winona# ioscan H/W Path Class Description =================================================== root 0 ioa System Bus Adapter (803) 0/0 ba Local PCI Bus Adapter (782) 0/0/0/0 lan HP PCI 10/100Base-TX Core 0/0/1/0 ext_bus SCSI C895 Fast Wide LVD 0/0/1/0.7 target 0/0/1/0.7.0 ctl Initiator 0/0/2/0 ext_bus SCSI C875 Ultra Wide Single-Ended 0/0/2/0.
Planning Your System for Virtual Partitions full ioscan output of non-cellular system named winona 1/4/0/0.5 1/4/0/0.5.0 1/4/0/0.7 1/4/0/0.7.0 1/4/0/1 1/4/0/1.7 1/4/0/1.7.
Planning Your System for Virtual Partitions full ioscan output of cellular (nPartitionable) system named keira full ioscan output of cellular (nPartitionable) system named keira keira# ioscan H/W Path Class Description ========================================================================== root 0 cell 0/0 ioa System Bus Adapter (805) 0/0/0 ba Local PCI Bus Adapter (782) 0/0/0/0/0 tty PCI SimpleComm (103c1290) 0/0/0/0/1 tty PCI Serial (103c1048) 0/0/0/3/0 ext_bus SCSI C1010 Ultra160 Wide LVD A6793-60001
Planning Your System for Virtual Partitions full ioscan output of cellular (nPartitionable) system named keira 1/0/0/3/1.7 target 1/0/0/3/1.7.0 ctl 1/0/1 ba 1/0/1/1/0 ba 1/0/1/1/0/1/0 ext_bus 1/0/1/1/0/1/0.7 1/0/1/1/0/1/0.7.0 1/0/1/1/0/1/1 ext_bus 1/0/1/1/0/1/1.7 1/0/1/1/0/1/1.7.0 1/0/1/1/0/4/0 lan 1/0/2 ba 1/0/4 ba 1/0/4/1/0 ba 1/0/4/1/0/4/0 fc Port Combo Adapter 1/0/4/1/0/4/0.1 1/0/4/1/0/4/0.1.0.0.0 1/0/4/1/0/4/0.1.0.0.0.0 1/0/4/1/0/4/0.1.0.0.0.0.1 1/0/4/1/0/4/0.1.0.255.0 1/0/4/1/0/4/0.1.0.255.0.
Planning Your System for Virtual Partitions Planning, Installing, and Using vPars with an nPartitionable Server Planning, Installing, and Using vPars with an nPartitionable Server When using vPars, the major difference between non-nPartitionable and nPartitionable systems is the hardware path.
Planning Your System for Virtual Partitions Planning, Installing, and Using vPars with an nPartitionable Server Impact on vPars Commands: Specifying CPU Since the nPartitionable systems include the cell in the hardware path, when specifying a CPU hardware path, you must include the cell number to specify the entire CPU hardware path.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions Planning Your Virtual Partitions Virtual Partitions Layout Plan Before you install vPars, you should have a plan of how you want to configure the virtual partitions within your server. Example of a virtual partition plan for vPars A.04.xx based on the example cellular server: Partition Name keira1 keira2 keira3 Assigned CPUs (A.04.xx) num = 2 num = 1 and 1 from cell 1 num = 1 Unassigned CPUs (A.04.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions console port Autoboot NOTE owned by winona1 AUTO AUTO AUTO When you create a partition, the vPars Monitor assumes you will boot and use the partition. Therefore, even if a partition is down, the resources assigned to the partition cannot be used by any other partition. The next few sections will describe how we arrived at each portion of the partition plan.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions • a boot disk (when using a mass storage unit, please check your hardware manual to verify that it can support a boot disk) Although not required for booting a virtual partition, you can add LAN card(s) as required for networking. For your virtual partitions, use the number of CPUs, amount of memory, boot disk configuration, and lan cards as is appropriate for your OS and applications.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions We have three CPUs that were not assigned to any of the virtual partitions, so we will have three CPUs available. Unassigned CPUs three CPUs are available vPars A.03.xx and earlier For this example, winona1 will have two bound CPUs, winona2 will have two bound CPUs where the hardware paths will be 41 and 45, and winona3 will have one bound CPU.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions I/O For detailed information on I/O Assignments, see “I/O: Allocation Notes” on page 242. For simplified I/O block diagrams of the LBA to physical slot relationship of PA-RISC systems, see Appendix A, “LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only),” on page 349.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions Partition Name winona1 winona2 winona3 I/O LBAs 0.0 boot/lan 0.4 0.8 boot 1.10 lan 0.5 lan 1.4 boot Assigning the Hardware Console LBA One of the virtual partitions must own the LBA that contains the physical hardware console port. In our example server, the hardware console port is at 0/0/4/0, which uses the LBA at 0/0. The LBA 0/0 is owned by the partition winona1: CAUTION console port 0.0.4.0 1/0/0/0/1 LBA 0.0 1.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions Partition Name winona1 winona2 winona3 Autoboot AUTO AUTO AUTO For more information, see the vparmodify (1M) manpage. NOTE When using vparboot -I to install vPars, you need to leave the autoboot attribute set to AUTO during the installation due to the reboots that occur during the installation. After installation is complete, you can set the autoboot attribute to MANUAL using the vparmodify command.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions I/O LBAs 0.0 0.4 0.8 1.10 0.5 1.4 Boot Path 0.0.2.0.6.0 0.8.0.0.5.0 1.4.0.0.5.0 LAN 0.0.0.0 1.10.0.0.4.0 0.5.0.0.4.
Planning Your System for Virtual Partitions Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx Beginning with vPars A.05.01, you can have a mixed HP-UX 11i v2/v3 vPars environment. A mixed HP-UX 11i v2/v3 vPars environment allows you to have a vPars A.05.01 monitor and database that supports both virtual partitions running vPars A.05.01 on HP-UX 11i v3 (11.31) and virtual partitions running vPars A.04.02 or later on HP-UX 11i v2 (11.23).
Planning Your System for Virtual Partitions Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx Note that this only applies to performing these operations on other virtual partitions. Operations where the source and target virtual partition are the same are always supported, regardless of whether you are in a mixed HP-UX 11i v2/v3 vPars environment or not. When the flexible administrative capability is ON, setting the vPars A.04.xx/11.
Planning Your System for Virtual Partitions Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx Feature Summary The following table highlights the above rules for having a mixed HP-UX 11i v2/v3 vPars environment: Table 3-2 Feature Summary Feature vPars A.05.xx instances vPars A.04.xx instances Minimum vPars Version A.05.01 A.04.
Planning Your System for Virtual Partitions Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx Determining the Version in a Mixed HP-UX 11i v2/v3 vPars Environment In addition to using the normal HP-UX commands to determine the OS version of a specific OS instance, you can use vparstatus -P to determine the vPars version of a specific virtual partition as well as the vPars version of the vPars Monitor which is booted.
Planning Your System for Virtual Partitions Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.
4 Installing, Updating, or Removing vPars and Upgrading Servers with vPars This chapter covers • Notes, Cautions, and Other Considerations Before You Update or Install vPars • Ignite-UX. See “Setting Up the Ignite-UX Server” on page 80 • Installing or Updating vPars — — — — — For "Installing vPars with Ignite-UX on PA-RISC", see page 110. For "Installing vPars with Ignite-UX on Integrity", see page 112. For "Installing vPars with Software Distributor", see page 115. For "Updating from vPars A.04.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Notes, Cautions, and Other Considerations Before You Update or Install vPars Notes, Cautions, and Other Considerations Before You Update or Install vPars Notes Please be sure you understand vPars before attempting the updates and installations. See Chapter 2, “How vPars and its Components Work,” on page 29 and Chapter 3, “Planning Your System for Virtual Partitions,” on page 53.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Notes, Cautions, and Other Considerations Before You Update or Install vPars For vPars A.03.01 or earlier, you must explicitly specify the LBA for I/O allocation. Thus, for cellular systems on A.03.01 or earlier, you must use the cell/SBA/LBA format on the command line. If you use only the cell/SBA format the vPars commands will not assume that all LBAs under the specified SBA are to be included in the allocation.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Notes, Cautions, and Other Considerations Before You Update or Install vPars For example, if you have not modified your AUTO file in the LIF area to boot the vPars Monitor and virtual partitions, boot the vPars Monitor (for example, ISL> hpux /stand/vpmon) and then the virtual partitions (for example, MON> vparload -auto). • Mid-range Servers Once in standalone or nPars mode, install the server firmware as you normally do.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Notes, Cautions, and Other Considerations Before You Update or Install vPars You will see a message indicating the command execution will take a few seconds and then a message indicating that your settings have been updated. The virtual partitions that you create will use this terminal-type setting for their virtual console displays. TIP If you get a garbled display, you can press Ctrl-L to refresh the display.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Bundle Names Bundle Names You can install vPars on an existing HP-UX installation directly from a depot, DVD, or by using an Ignite-UX server. vPars Product Bundles The vPars bundle names are: Bundle Name Description T1335CC vPars A.05.xx for HP-UX 11i v3 T1335BC vPars A.04.xx for HP-UX 11i v2 Feature11i (HP-UX 11i v2 only) Required vPars enablement patches for vPars A.04.xx.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Bundle Names B6826AA Partition Manager for nPartitions (parmgr) (Required for vPars A.03.xx and earlier) VPARMGR vPars GUI (vparmgr) for vPars A.03.xx and earlier (Optional) Installing and Removing vPars-related Bundles B6826AA (parmgr) The Partition Manager (parmgr) is required for installation of the vPars A.03.xx and earlier.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Setting Up the Ignite-UX Server Setting Up the Ignite-UX Server If you are having problems with terminal emulation, see also “Ignite-UX and other Curses Applications” on page 25. For complete information on Ignite-UX, see the document Ignite-UX Administration Guide. Ignite-UX Versions vPars A.03.xx and A.04.xx have different version requirements.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Ignite-UX, the LAN, the LAN card, and vparboot -I Ignite-UX, the LAN, the LAN card, and vparboot -I NOTE Using vparboot -p target_partition -I On both PA-RISC and Integrity, before booting a virtual partition for installation (in other words, using vparboot -p target_partition -I...), please be sure that you have specified a boot disk using the BOOT attribute (io:boot_device:BOOT)for the virtual partition.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Ignite-UX, the LAN, the LAN card, and vparboot -I • the network interface card of the target virtual partition is able to connect to the Ignite-UX server.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Ignite-UX, the LAN, the LAN card, and vparboot -I CAUTION lanboot select connects to the first Ignite-UX server from which its gets a response. Make sure that the NICs MAC address is registered with only one Ignite-UX server or boot helper in the subnet.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> A.05.xx Updating from vPars A.04.xx -> A.05.xx This section describes how to update an existing A.04.xx vPars on 11iv2 (11.23) environment to a vPars A.05.xx vPars environment on 11iv3 (11.31). For information on vPars and OS versions, see the HP-UX Virtual Partitions Ordering and Configuration Guide.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> A.05.xx If you are unfamiliar with the Update-UX product or would like information on using or debugging Update-UX, please read the HP-UX 11.31 or 11.23 Installation and Update Guide. Also, see the applicable Software Distributor and Ignite-UX documents available at http://docs.hp.com. OE Bundle Names for Update-UX For HP-UX 11i v3, the possible OE bundles are listed below.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> A.05.xx 2. Record the current autoboot and autosearch settings of all the virtual partitions. The update process sets autoboot to manual, so you will need to restore these settings later. To find the current settings, use vparstatus.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> A.05.xx If the BOOT and ALTBOOT disks are a mirrored pair, updating is not required on the ALTBOOT disk. Otherwise, if you wish to have the alternate boot disk up dated, after updating the OS on the primary boot path disk, boot the virtual partitions from the alternate path boot disk and repeat the update-ux procedure.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> A.05.xx 10. The virtual partitions should now be running the latest vPars version. To verify this, you can login to each virtual partition and use the vparstatus command with the -P option: Example: keira1# vparstatus -P Current Virtual Partition Version: A.05.01 Monitor Version: A.05.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment This section describes how to update an existing A.04.xx vPars environment to a mixed HP-UX 11i v2/v3 vPars environment; a mixed HP-UX 11i v2/v3 vPars environment contains both vPars A.04.xx/11.23 and A.05.xx/11.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment # update-ux -s For example, the command line used in this section is # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC where depot1:/release/1131/HPUX11i-OE-Ent.DVD is the source depot HPUX11i-OE-Ent is the OE bundle T1335CC is the vPars A.05.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment Changing nPartition Boot Paths To Boot the vPars A.05.xx Monitor To boot a mixed HP-UX 11i v2/v3 vPars environment, you must boot a vPars A.05.xx Monitor. In our example below, entitled The Update Process, we are updating the first virtual partition (the virtual partition from which the vPars Monitor is booted) from vPars A.04.01 to A.05.01.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment keira1# vparstatus [Virtual Partition] Virtual Partition Name ============================== keira1 keira2 keira3 State ===== Up Up Up Attributes ============ Dyn,Auto,Nsr Dyn,Manl,Nsr Dyn,Auto,Nsr Boot Kernel Path Opts ======================= ===== /stand/vmunix /stand/vmunix /stand/vmunix 2.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment a. Find the nPartition partition number for the current nPartition: keira1# parstatus -w The local partition number is 0. The nPartition number is 0. Record this information. b. Find the boot path of the boot disk of a future vPars A.05.01 virtual partition. This boot path will become the nPartition’s new PRI boot path.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment 6. After the all updates for the above virtual partitions have completed, use Update-UX to install the latest OE and vPars bundle to the first virtual partition. Example: keira1 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment keira# parmodify -p0 -b 0.0.6.0.0.5.0 where the syntax of parmodify is -p nPartition_number -b primary_boot_path c. Verify the new PRI path using parstatus: keira# parstatus -p0 -V [Partition] Partition Number : Partition Name : Status : IP address : PrimaryBoot Path : ... 0 npar0 active 0.0.0.0 0/0/6/0/0.5.0 d.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.04.xx -> Mixed HP-UX 11i v2/v3 vPars (A.04.xx & A.05.xx) Environment 12. Verification of Virtual Partitions The virtual partitions should now be running the latest vPars version. To verify this, you can login to each virtual partition and use the vparstatus command with the -P option: Example: keira1# vparstatus -P Current Virtual Partition Version: A.05.01 Monitor Version: A.05.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.03.xx -> A.05.xx Updating from vPars A.03.xx -> A.05.xx At the time of this publication, updating directly from vPars A.03.xx to A.05.xx is not supported because the Update-UX tool does not support updating directly from 11i v1 (11.11) to 11i v3 (11.31). However, as a general workaround, you can attempt the following process. However, there are many differences not only between vPars A.03.xx and A.05.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.03.xx -> A.04.xx Updating from vPars A.03.xx -> A.04.xx This section describes how to update an existing A.03.xx PA-RISC vPars environment to the latest A.04.xx PA-RISC vPars environment.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.03.xx -> A.04.xx ============================== keira1 keira2 keira3 ===== Up Up Up ============ Dyn,Auto,Nsr Dyn,Manl,Nsr Dyn,Auto,Nsr ======================= ===== /stand/vmunix /stand/vmunix /stand/vmunix 2. Record the current autoboot and autosearch settings of all the virtual partitions so that you can change back to these settings later. To find the current settings, use vparstatus.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.03.xx -> A.04.xx Bundle Names • For HP-UX 11i v2, the possible OE bundles are listed below. HPUX11i-OE Foundation OE HPUX11i-OE-Ent Enterprise OE HPUX11i-OE-MC Mission Critical OE You should chose the same OE that your current virtual partition is running. Use the swinstall command to check which OE you are currently running: # swlist -l bundle | grep -i OE HPUX11i-OE-Ent B.11.23.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars A.03.xx -> A.04.xx 8. From ISL> load the vPars Monitor. Example: ISL> hpux /stand/vpmon 9. Boot the virtual partitions. Example: MON> vparload -all When the virtual partitions are booted, they will continue and complete their update processes. After this is completed, you should arrive at the login: prompt for each virtual partition. Login as root and continue to the next step. 10.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars (A.02.xx or A.03.xx) -> A.03.xx Updating from vPars (A.02.xx or A.03.xx) -> A.03.xx To update from an earlier vPars A.02.xx or A.03.xx version to the latest vPars A.03.xx version, perform the following: Step 1. Save a copy of the vPars database in case you need to revert back to the earlier version of vPars or you need to restore the database. Step 2. Shut down all the virtual partitions. Step 3.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updating from vPars (A.02.xx or A.03.xx) -> A.03.xx You must install the new vPars bundle on each virtual partition before putting the virtual partitions back into production. Running a mix of older and newer vPars versions within a group of virtual partitions is not supported.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Applying a vPars Sub-System Patch Applying a vPars Sub-System Patch The vPars sub-system patch includes the vPars Monitor, commands, and daemons. To apply a vPars patch to an existing version, perform the following: 1. Shut down all the virtual partitions. 2. Reboot the server into standalone mode. This consists of the following: a. At the MON> prompt, type reboot b.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Upgrading Integrity Servers from the sx1000 to sx2000 Chipset Upgrading Integrity Servers from the sx1000 to sx2000 Chipset You can upgrade the following Integrity servers from the sx1000 to sx2000 chipsets: • • • rx7620 to rx7640 rx8620 to rx8640 Integrity Superdome For the upgrade process steps, please see the hardware upgrade documentation for your server.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Upgrading Integrity Servers from the sx1000 to sx2000 Chipset — To delete an old LBA: # vparmodify -p vpar_name -d io:old_path • updating the EFI to hardware path mappings using vparefiutil: Example: — To delete the old entries and update with the new entries: # vparefiutil -d # vparefiutil -u Hardware Path Tables The tables below show the new hardware paths.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Upgrading Integrity Servers from the sx1000 to sx2000 Chipset Table 4-3 Integrity Superdome Hardware Path Changes (x=cell) Slot Chapter 4 sx1000 Path sx2000 Path 0 x/0/0/1 x/0/0/1 1 x/0/1/1 x/0/1/1 2 x/0/2/1 x/0/2/1 3 x/0/3/1 x/0/4/1 4 x/0/4/1 x/0/5/1 5 x/0/6/1 x/0/6/1 6 x/0/14/1 x/0/14/1 7 x/0/12/1 x/0/13/1 8 x/0/11/1 x/0/12/1 9 x/0/10/1 x/0/10/1 10 x/0/9/1 x/0/9/1 11 x/0/8/1 x/0/8/1 107
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Upgrading Backplanes from PCI to PCI-X Upgrading Backplanes from PCI to PCI-X If you upgrade from the PCI to PCI-X backplane with the following server upgrades: • • • rp7410 to rp7420 the rp8400 to rp8420 Superdome the hardware paths of the I/O devices will change. The I/O device paths are in the format cell/sba/lba/device/function.target.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Updates Involving VPARSBASE Updates Involving VPARSBASE VPARSBASE (the free demo product for HP-UX 11i v1) is no longer available or supported. You can update directly only from free product to newer free product or from purchased product to newer purchased product. You cannot update directly from free product to the purchased product.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Ignite-UX on PA-RISC Installing vPars with Ignite-UX on PA-RISC 1. Boot your system using the Ignite-UX server. If your Ignite server’s IP address is ww.xx.yy.zz: BCH> bo lan.ww.xx.yy.zz install Interact with IPL: n 2.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Ignite-UX on PA-RISC 6. Interrupt the boot process as your system comes back up to reach the ISL prompt. BCH> bo pri interact with IPL: y 7. At the ISL prompt, boot the Monitor and the first virtual partition. Example: ISL> hpux /stand/vpmon vparload -p winona1 8.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Ignite-UX on Integrity Installing vPars with Ignite-UX on Integrity Lan cards are used for boot during installation on Integrity systems. NOTE Unlike vPars on PA-RISC, vPars on Integrity uses the lan card of the target virtual partition for lanboot. Please check that your lan card is supported for boot on 11.23 Integrity systems.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Ignite-UX on Integrity 3. Using the Ignite-UX server, install the necessary bundles. This includes HP-UX OE, any desired patches, the Quality Pack bundle, the vPars bundle, and any desired vPars-related bundles onto the disk that will be the boot disk of the first virtual partition. 4. Use ioscan to verify the hardware addresses in your virtual partition plan.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Ignite-UX on Integrity 10. Continuing on the console of the running virtual partition (keira1), perform the following for each remaining virtual partition: a. boot the target virtual partition from the running virtual partition using vparboot.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Software Distributor Installing vPars with Software Distributor 1. For the root disk of each virtual partition, use Software Distributor to install HP-UX, desired patches, the Quality Pack bundle, the vPars software bundle, and the desired vPars-related bundles. 2. Boot the disk that is intended to be the boot disk of the first virtual partition into the normal (non-vPars) HP-UX environment.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Installing vPars with Software Distributor Shell> fs0: fs0:\> hpux HPUX> boot /stand/vpmon vparload -all Your system should now be booted with all virtual partitions up.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Removing the vPars Product Removing the vPars Product From a Single Virtual Partition To remove the vPars product, execute the swremove command from the target virtual partition. For example, to remove the vPars product from the partition winona3: winona3# /usr/sbin/swremove -x autoreboot=true VirtualPartition The product will be removed, and the virtual partition will be shut down.
Installing, Updating, or Removing vPars and Upgrading Servers with vPars Removing the vPars Product 118 Chapter 4
5 Monitor and Shell Commands This chapter covers: • Using Integrity systems — Setting Modes — EFI to Hardware Path Mappings • Using the vPars Monitor — Booting the Monitor — Accessing the Monitor Prompt — Using Monitor Commands • Using the vPars Commands — vPars Manpages — vPars Commands Logging — Obtaining Monitor and Hardware Resource Information • Managing the Virtual Partitions — — — — — — — — — — — — — • Creating a Virtual Partition Booting a Virtual Partition Shutting Down or Rebooting a Virt
Monitor and Shell Commands Notes on Examples in this Chapter Notes on Examples in this Chapter Syntax of Example Commands The example commands at the Unix shell level in the following section use the following syntax: where the shell prompt consists of the hostname of the current virtual partition and the hash sign (#).
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) Modes: Switching between nPars and vPars Modes (Integrity only) Modes On an Integrity system, you will need to set the mode in order to boot into a specific mode. For vPars usage, there are only two modes: • vPars sets the next nPartition boot to boot into the vPars environment. This allows you to boot the vPars Monitor and therefore the virtual partitions in the next nPartition boot.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) 1. Set the mode # vparenv -m vPars 2. Then, you manually reboot the nPartition: # shutdown -r ... Shell> fs0: fs0:\> hpux /stand/vpmon ... MON> • Monitor: reboot [mode] where mode has the value of either vPars or nPars reboots the nPartition into the mode mode. If any virtual partitions are up, this will cause them to be shutdown ungracefully.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) 1. First, set the mode: Shell> parconfig nPars -n 2. Then, you can reboot the nPartition from either the EFI shell using the reset option: Shell> parconfig reset Differences Between vparconfig and parconfig Table 5-1 vparconfig versus parconfig vparconfig parconfig EFI shell: vparconfig is not a built-in EFI shell command, so you must execute vparconfig from the disk.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) Note: parconfig does not support switching to vPars mode. In other words, you can use parconfig to set the mode to nPars, but you cannot use parconfig to set the mode to vPars. • During a cold-install of the OE and vPars software, the following general steps could occur: 1. Boot and install the OE and vPars software as well as create the vPars database onto the intended boot disk of a virtual partition. 2.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) The standard EFI Shell command reset should not be used to reset the system or nPartition when it is in vPars mode. • If the desired mode is not set, you will not be able to boot into that mode. For example, you will not be able to boot the vPars Monitor (/stand/vpmon) when you are in nPars mode. Likewise, you will not be able to boot into standalone mode when you are in vPars mode.
Monitor and Shell Commands EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) On PA-RISC systems, the bootloader can boot a disk using only the hardware path of the disk. However, on Integrity systems, the bootloader requires the EFI path.
Monitor and Shell Commands EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) • The virtual partitions that could not boot can be booted using the Monitor command vparload: vparload -p partition_name -E disk_index • Creating a virtual partition in vPars mode. Problem: If a virtual partition is created while in vPars mode, then it may not be possible to boot that partition if the EFI path corresponding to the boot disk hardware path is not present in the vPars database.
Monitor and Shell Commands EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) If you add a boot disk at a known hardware path, it may not be possible to immediately boot from this new disk. Solution: • CAUTION If the EFI signature of the disk is known, the vparload -E command can be used to boot from the disk. It is recommended to use the documented procedure of using vparboot -I to create the virtual partitions so that users do not have to use vparload -E.
Monitor and Shell Commands Monitor: Booting the vPars Monitor Monitor: Booting the vPars Monitor To boot the vPars Monitor, from ISL or EFI, specify /stand/vpmon: — PA-RISC: ISL> hpux /stand/vpmon — Integrity: Shell> fs0 fs0:\> hpux HPUX> boot vpmon Note: you must be in vPars mode to boot the Monitor. See “Modes: Switching between nPars and vPars Modes (Integrity only)” on page 121. Also, backspace is sometimes not parsed correctly; if the command fails, try again without backspacing.
Monitor and Shell Commands Monitor: Accessing the Monitor Prompt Monitor: Accessing the Monitor Prompt You can reach the Monitor prompt in the following ways: • From the ISL or EFI prompt, you can boot the Monitor into interactive mode (see “Monitor: Booting the vPars Monitor” on page 129). • After shutting down all virtual partitions, you will arrive at the Monitor prompt on the console (see “Boot||Shut: Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor)” on page 162). • A.03.
Monitor and Shell Commands Monitor: Using Monitor Commands Monitor: Using Monitor Commands You can use the following Monitor commands at the Monitor prompt for booting and basic troubleshooting. However, most vPars operations should be performed using the vPars shell commands. Note the following for the Monitor commands: • Unless specifically stated, all operations occur only on the boot disk from which the Monitor was booted.
Monitor and Shell Commands Monitor: Using Monitor Commands • vparload -all vparload -auto vparload -p partition_name [-b kernelpath] [-o boot_options] [-B hardware_path] boots the virtual partition partition_name; this command is similar to the vPars Unix shell command vparboot. -all boots all virtual partitions, regardless of the autoboot or autosearch attributes. For more information on the autoboot or autosearch attributes, see the vparcreate (1M) or vparmodify (1M) manpages.
Monitor and Shell Commands Monitor: Using Monitor Commands • bootpath displays the device from which the vPars Monitor (/stand/vpmon) was booted Example: MON>bootpath disk(0.0.2.0.6.0) • reboot [mode] reboots the entire hard partition. Other hard partitions are not affected. mode sets the mode for the next reboot and has the value of either nPars or vPars. This is applicable on only Integrity systems.
Monitor and Shell Commands Monitor: Using Monitor Commands • lifls lists the files in the LIF area • getauto displays the contents of the AUTO file in the LIF area Example: MON> getauto hpux /stand/vpmon • log displays the contents, including warning and error messages, of the Monitor log. The Monitor log holds up to 16 KB of information in a circular log buffer. The information is displayed in chronological order. • ls [-alniFH] [directory] lists the contents of directory.
Monitor and Shell Commands Monitor: Using Monitor Commands • settime [MM DD YYYY hh mm ss] sets the system's real time clock. Acceptable date range is 1-1-1970 00:00:00 to 12-31-2034 23:59:59. • threads controls the use of hyperthreading on servers with dual core Intel Itanium 2 processors. For usage information, see “CPU: Hyperthreading ON/OFF (HT ON/OFF)” on page 228. • time displays system real time clock and OS time of all the virtual partitions in GMT (Greenwich Mean Time).
Monitor and Shell Commands Monitor: Using the Monitor Commands from ISL or EFI Monitor: Using the Monitor Commands from ISL or EFI You can specify any of the Monitor commands either at the Monitor prompt (MON>) or at the ISL prompt (ISL>). If you are at ISL or EFI, use the desired command as the argument for the Monitor /stand/vpmon.
Monitor and Shell Commands Commands: vPars Manpages Commands: vPars Manpages The purpose of this document is to describe vPars concepts and how to perform common vPars tasks. For detailed information on the vPars commands, including description, syntax, all the command line options, and the required state of a virtual partition for each command, see the vPars manpages.
Monitor and Shell Commands Commands: vPars Commands Logging Commands: vPars Commands Logging Beginning with vPars A.03.02, vPars will log the vPars commands executed from the HP-UX shell to the local syslog file (the syslog file of the virtual partition from which the vPars command was executed). Log File Location and Log Format The default syslog file on HP-UX systems is /var/adm/syslog/syslog.log.
Monitor and Shell Commands Commands: vPars Commands Logging These commands include vparadmin, vparboot, vparcreate, vparefiutil, vparenv, vparremove, vparmodify, vparreset, and vparutil. Constraints and Restrictions to Logging Note the following: • • • Commands will be logged whether executed on the vPars database in memory, an alternate database, or in standalone mode. The command line text will be logged on only the partition from which the command was executed.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) Commands: Displaying Monitor and Resource Information (vparstatus) The Monitor and the partition database maintains information about all the virtual partitions, including the current state of the virtual partitions and their resources. Using the shell command vparstatus, you can display this information. This section describes the possible virtual partition states and the common usages of the vparstatus command.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) NOTE Chapter 5 • Actual vparstatus output differs from version to version of vPars. Depending on your version and system, the output shown below may differ. For detailed usage, syntax, and information, see the manpage vparstatus (1M) on your vPars system. • The kernel path shown in the vparstatus output is the kernel path set in the vPars database. This may differ from the actual kernel in use.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: summary information Use vparstatus with no options. Examples • vPars A.03.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: verbose information Use vparstatus with verbose (-v) option. Examples • vPars A.03.xx on a rp7400: winona1# vparstatus -p winona2 -v [Virtual Partition Details] Name: winona2 State: Up Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/8 Bound by User [Path]: 41 45 Bound by Monitor [Path]: Unbound [Path]: 97 [IO Details] 0.8.0.0.5.0 0.8 1.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) (bytes) (MB) ILM, Monitor-assigned [Base /Range]: (bytes) (MB) ILM Total (MB): 1024 ILM Granularity (MB): 128 CLM, user-assigned [CellID Base /Range]: (bytes) (MB) CLM, Monitor-assigned [CellID Base /Range]: (bytes) (MB) CLM (CellID MB): CLM Granularity (MB): • 128 vPars A.05.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: available resources Use vparstatus with available resources (-A) option. This shows the resources not assigned to any virtual partitions. Examples • A.03.xx on a rp7400 (non-nPartitionable server) winona1# vparstatus -A [Unbound CPUs (path)]: [Available CPUs]: 101 109 2 [Available IO devices (path)]: 1.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) 1.14 1.15 [CLP (CellID Count)]: [Available CPUs]: 0 2 1 5 3 [Available I/O devices (path)]: 0.0.4 0.0.6 0.0.10 0.0.12 0.0.14 1.0.1 1.0.2 1.0.6 1.0.8 1.0.10 1.0.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: CPU information on vPars A.04/A.05 While a virtual partition is in the down state, no specific CPU is assigned to the virtual partition as the boot processor but one is allocated by the Monitor if needed (there are no CPUs assigned to the virtual partition). The boot processor is determined when the virtual partition is booted.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) Table 5-4 possible commands to arrive at vparstatus output vparstatus output (final) another set of possible commands in sequence to create vparstatus output keira1 # vparstatus -p keira1 -v [Virtual Partition Details] Name: keira1 State: Up Attributes: Dynamic,Autoboot,Autosearch Kernel Path: /stand/vmunix Boot Opts: # vparcreate -p keira1 -a cpu:1.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: dual-core CPUs You can see the sibling and virtual partition assignment using vparstatus -d. If you do not have a dual-core system, the output will show dashes (-) for the sibling and assignment information. Example # vparstatus -d CPU Cell Config Sibling Information path CPU HPA ID Status Assigned to Path /vPar name ===== ================== ==== ====== ================== ======================= 0.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: pending migrating CPUs operations Migrating CPUs may not occur instantaneously. If a virtual partition has a pending (in other words, still in progress) addition or deletion of one or more CPUs, the letter p will be displayed next to the number of CPUs in the summary output and the words (migration pending) will be displayed in the detailed output: Example winona1# vparstatus . . .
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: pending migrating memory operations Migrating memory may not occur instantaneously. If a virtual partition has a pending (in other words, still in progress) addition or deletion of memory, the letter p will be displayed next to the total ILM in the summary output and the words (Migration pending) will be displayed in the detailed output: Example • winona1# vparstatus ...
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: base and float memory amounts With vPars A.05.xx, you can assign ILM and/or CLM memory as either base or float. The verbose (-v) output of vparstatus shows how much is float relative to the total ILM and CLM memory that is assigned. # vparstatus -p keira4 -v ...
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: pending nPartition RFR On an nPartitionable system, if the nPartition has a pending RFR (Reboot-for-Reconfig), the vparstatus output will show the following message: Note: A profile change is pending. The hard partition must be rebooted to complete it.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: Monitor and database information Beginning with vPars A.03.02, the -m option displays the console path, the hardware path from which the Monitor was booted, the fleshiest path of the Monitor, and the vPars database file that is being used by the Monitor. Beginning with vPars A.04.01, memory ranges used by the monitor and firmware are also displayed. Examples • vPars A.03.
Monitor and Shell Commands Managing: Creating a Virtual Partition Managing: Creating a Virtual Partition You can create a virtual partition using the vparcreate command. When you create a virtual partition, the vPars Monitor assumes you will boot and use the partition. Therefore, when a virtual partition is created, even if it is down and not being used, the resources assigned to it cannot be used by any other partition.
Monitor and Shell Commands Managing: Creating a Virtual Partition TIP For the vparcreate options, you can create a text file that includes all the options and then cat the text file within the vparcreate command line. This avoids having to remember all the options when you are typing the vparcreate command line. For example, for the vPars A.03.xx vparcreate command of winona2, you can create a text file called /stand/winona2.opts: winona1# vi /stand/winona2.
Monitor and Shell Commands Managing: Removing a Virtual Partition Managing: Removing a Virtual Partition To remove a virtual partition, use vparremove. vparremove purges the virtual partition from the vPars database. Any resources dedicated to the virtual partition are now free to allocate to a different virtual partition (for A.03, see Appendix B for exceptions). You need to shutdown the virtual partition before attempting removal. If the target virtual partition is running, vparremove will fail.
Monitor and Shell Commands Managing: Modifying Attributes of a Virtual Partition Managing: Modifying Attributes of a Virtual Partition You can change a virtual partition’s name and its resource attributes via the vparmodify command. When using vparmodify to change attributes, the partition can be running, and the changes take effect immediately. See the manpage vparmodify (1M) for more information on the attributes. For information on modifying resources, see “CPU, Memory, and I/O Resources (A.04.
Monitor and Shell Commands Boot||Shut: Booting a Virtual Partition Boot||Shut: Booting a Virtual Partition To boot a single virtual partition, use either the Monitor command vparload or the shell command vparboot. (To shutdown a booted virtual partition, see “Boot||Shut: Shutting Down or Rebooting a Virtual Partition” on page 160).
Monitor and Shell Commands Boot||Shut: Shutting Down or Rebooting a Virtual Partition Boot||Shut: Shutting Down or Rebooting a Virtual Partition A virtual partition can be gracefully shut down or rebooted via the HP-UX command shutdown; there is no vpar* command to shutdown a virtual partition. To ensure that the partition database is synchronized (see “vPars Partition Database” on page 32), execute the vparstatus command prior to executing the shutdown command.
Monitor and Shell Commands Boot||Shut: Shutting Down or Rebooting a Virtual Partition When to Shutdown All Virtual Partitions The only times you need to shutdown all the virtual partitions within a hard partition are when: • a hardware problem or nPartition modification requires the nPartition to be down. Note that PCI OL* is supported on vPars A.03.xx and A.04. • the entire hard partition hangs. This might be a problem with the Monitor.
Monitor and Shell Commands Boot||Shut: Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor) Boot||Shut: Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor) To halt or reboot the hard partition gracefully, you need to do the following: 1. Log into every virtual partition that is running and gracefully shutdown the partition via the HP-UX command shutdown. There is no command that shuts down all the virtual partitions at the same time.
Monitor and Shell Commands Boot||Shut: Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor) This command controls power enable to a hardware device. B - Cabinet C - Cell I - IO Chassis Select Device: c Enter cabinet number: 0 Enter slot number: 6 The power state is ON for the Cell in Cabinet 0, Slot 6.
Monitor and Shell Commands Boot||Shut: Setboot and System-wide Stable Storage Boot||Shut: Setboot and System-wide Stable Storage On a vPars system, the setboot command does not read from or write to system-wide stable storage. Instead, the setboot command reads from and writes to the vPars partition database, affecting only the entries of the virtual partition from which the setboot command was run.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths Boot||Shut: Using Primary and Alternate Boot Paths You can set the primary and alternate boot paths of a virtual partition by using the HP-UX setboot command or the vPars command vparmodify and the BOOT and ALTBOOT attributes. NOTE • Like many other HP-UX applications, MirrorDisk/UX software is supported. However, vPars does not have a knowledge of the mirror configuration.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths Table 5-5 Boot Attempt Results of the autoboot and autosearch Values autoboot value autosearch value auto search attempt to boot the primary path; if boot fails, attempt to boot the alternate path. manual search non-nPartitionable servers: no booting is attempted resulting boot attempt nPartitionable servers: do not attempt to boot the primary path; attempt to boot the alternate path.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths Setting the Primary or Alternate Boot Paths In the examples below, suppose you want the virtual partition winona2 to have its primary boot disk at 0/8/0/0.5.0 and its alternate boot path at 0/8/0/0.2.0. Using setboot Because setboot affects only the virtual partition from which you execute the command, execute these commands from winona2. To set the primary boot path: winona2# setboot -p 0/8/0/0.5.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths Using Primary and Alternate Paths with nPartitions The vPars database and the nPartition complex profile are entirely separate. Therefore, a change in the vPars database does not change any complex profile data. A change in the primary or alternate paths in the vPars database does not change the primary or alternate paths in the complex profile.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths keira2# vparstatus -p keira1 -v [Virtual Partition Details] Name: keira1 State: Down Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix . . . [IO Details] 0.0.6 0.0.6.0.0.5 0.0.0 0.0.4 0.0.2 0.0.6.0.0.4.0 ALTBOOT 0.0.6.0.0.5.0 BOOT 0.0.6.0.0.6.
Monitor and Shell Commands Boot||Shut: Using Primary and Alternate Boot Paths Booting Using the Primary or Alternate Boot Paths To boot winona2 using the primary path: winona1# vparboot -p winona2 -B pri However, because the primary boot path is the default, you can omit the -B portion: winona1# vparboot -p winona2 To boot winona2 using the alternate path: winona2# vparboot -p winona2 -B alt NOTE • Setting a path using vparmodify requires the target virtual partition to be down; setboot does not.
Monitor and Shell Commands Boot||Shut: Autoboot Boot||Shut: Autoboot The AUTO File on a Virtual Partition On a non-vPars server, the LIF’s AUTO file on the boot disk can contain a boot string that includes boot options, such as -lq for booting without quorum, or a boot kernel path, such as /stand/vmunix.other for booting an alternate kernel (for 11i v2 systems, alternate kernels are in /stand/alternate_config/). The AUTO file can be changed either through LIF shell commands or mkboot.
Monitor and Shell Commands Boot||Shut: Autoboot Autobooting the vPars Monitor and Virtual Partitions You can setup the Monitor and all virtual partitions to boot automatically at power up. To do this, make sure the following four conditions are met: 1. The hard partition’s primary and alternate boot paths point to the boot disks of different virtual partitions. For example, to set the primary and alternate boot paths at BCH or EFI: pa pri 0/0/2/0.6.0 pa alt 0/8/0/0.5.0 2.
Monitor and Shell Commands Boot||Shut: Autoboot NOTE For Superdome and other nPartitionable servers, you must use the boot device path "path flags" to set automatic booting past the BCH for an nPartition. See the manual HP System Partitions Guide for more information, including the proper configuration of paths for an nPartition.
Monitor and Shell Commands Boot||Shut: Single-User Mode Boot||Shut: Single-User Mode It is occasionally necessary to boot HP-UX into single-user mode to diagnose issues with networking or other components. NOTE Although you can boot a virtual partition into single-user mode to diagnosis an OS problem, once you are in single-user mode, you should not use vpar* commands in single-user mode. Reboot the target virtual partition and return to multi-user mode before using the vpar* commands.
Monitor and Shell Commands Boot||Shut: Single-User Mode winona1# vparboot -p winona2 -o “-is” NOTE After you have finished with single-user mode and if you want to turn autoboot back on, the command is: winona1# vparmodify -p winona2 -B auto For information on using vparreset, see “Resetting a Virtual Partition” on page 180.
Monitor and Shell Commands Boot||Shut: Other Boot Modes Boot||Shut: Other Boot Modes In the same way you can boot a virtual partition into single-user mode (see “Boot||Shut: Single-User Mode” on page 174), you can boot a partition using other boot options.
Monitor and Shell Commands Boot||Shut: Other Boot Modes On a vPars server, you can execute either of the following: From MON> From the Monitor prompt, to boot winona2 overriding the quorum requirement: MON> vparload -p winona2 -o "-lq" From HP-UX shell prompt From the running virtual partition winona1, to boot winona2 overriding the quorum requirement: winona1# vparboot -p winona2 -o "-lq" Specifying the boot options from the command line only affects the current boot.
Monitor and Shell Commands Boot||Shut: Other Boot Modes Preparation Before changing the hardware path of the boot device: Step 1. Create a mapfile for the root volume group. Keep the mapfile in the root (/) directory, so that it is accessible during single user mode boot. vgexport -p -m /mapfile.vg00 /dev/vg00 Step 2. Get a list of physical volumes (PVs) in the root volume group. Keep the PV list file in the root (/) directory, so that it is accessible during single user mode boot. vgexport -p -f /pvs.
Monitor and Shell Commands Boot||Shut: Other Boot Modes mkdir /dev/vg00 mknod /dev/vg00/group c 64 0x00000 Step 5. Import the root volume group (vg00). For example: vgimport -m /mapfile.vg00 /dev/vg00 /dev/dsk/c1t1d0 /dev/dsk/c1t1d1 where the device filenames are obtained from the ioscan and vgscan above Step 6.
Monitor and Shell Commands Resetting a Virtual Partition Resetting a Virtual Partition Just as it is occasionally necessary to issue a hard reset (RS) or a soft reset (TOC) for a non-vPars OS instance, it is occasionally necessary to issue similar resets for a vPars OS instance. Hard Reset On hard partition not running vPars, a hard reset cold boots the hard partition.
Monitor and Shell Commands Using an Alternate Partition Database File Using an Alternate Partition Database File By default, the local copy of the vPars partition database is kept in the file /stand/vpdb on the boot disk of each virtual partition within a hard partition. However, you can create, edit, and delete virtual partitions in an alternate partition database file by using the "-D filename" option in the vPars command string, where filename is the name of the alternate partition database file.
Monitor and Shell Commands Using an Alternate Partition Database File Autoboot AUTO AUTO To create and boot using an alternate partition database, perform the following: 1. Create the partition configuration and alternate partition database file. winona1# vparcreate -p winsim1 -D /stand/vpdb.sim -a cpu::4 -a cpu:::4 -a mem::1600 -a io:0.0 -a io:0.4 -a io:0.0.2.0.6.0:BOOT winona2# vparcreate -p winsim2 -D /stand/vpdb.sim -a cpu::4 -a cpu:::4 -a mem::1600 -a io:0.8 -a io:1.10 -a io: 1.2 -a io:0.8.0.0.5.
Monitor and Shell Commands Using an Alternate Partition Database File This change will be synchronized to the local copies of /stand/vpdb.sim. (If /stand/vpdb.sim does not exist, as in this case on winsim2, the file will be automatically created during synchronization). 4. To return to using /stand/vpdb, do the same steps as above, except on the ISL command line in Step 3 is: ISL> hpux /stand/vpmon -a By default, the file /stand/vpdb is read as the partition database file.
Monitor and Shell Commands Managing Resources With Only One Virtual Partition Managing Resources With Only One Virtual Partition In some cases, adding and deleting I/O and memory resources to and from a virtual partition requires the virtual partition to be in the down state. Therefore, if you have configured only one virtual partition, you cannot run vparmodify from that virtual partition to modify its I/O and memory resources. In this situation, you should do the following: 1.
6 CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Concepts and Functionality I/O: Concepts and Functionality With vPars, you allocate I/O resources at the LBA level. LBA Local Bus Adapter SBA System Bus Adapter System, Cells, SBA, LBA, Devices and Relationships On a server, an I/O device communicates to the system through the LBA and SBA. The path looks like Figure 6-1 System to I/O Device Relationship This corresponds to the ioscan hardware path output for an I/O device of sba/lba/ ... /device.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Concepts and Functionality Figure 6-4 vPars allocates at LBA level not SBA level A system has multiple SBAs, but assignments remain at the LBA levels.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Adding or Deleting LBAs I/O: Adding or Deleting LBAs I/O Syntax in Brief The basic core syntax for adding or deleting I/O resources is: -a|d io:hardware_path where: a d hardware_path add delete the hardware path of the I/O Examples • To add all hardware using the SBA/LBA hardware path of 1/2 to an existing partition winona2: winona1# vparmodify -p winona2 -a io:1.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Allocation Notes I/O: Allocation Notes When planning or performing I/O allocation, note the following: • Mass Storage Stack Formats The agile view of mass storage introduced in HP-UX 11i v3 (11.31) is supported with vPars. However, the lunpath hardware path format and lun hardware path format are not supported for use on the vPars command line, and are not printed by any vPars commands.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Allocation Notes NOTE When assigning I/O, if you specify a path below the LBA level (for example, cell/sba/lba/.../device, vPars automatically assigns the LBA to the virtual partition. For example, if you specify -a io:0/0/0/2/0.6.0 where 0/0/0 is the cell/sba/lba, the lba of 0/0/0 is assigned to the virtual partition. Further, this LBA assignment implies that all devices using 0/0/0 are assigned to the virtual partition.
CPU, Memory, and I/O Resources (A.05.xx) I/O: Allocation Notes For information on supported I/O interface cards and configurations, see the document HP-UX Virtual Partitions Ordering and Configuration Guide.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Concepts and Functionality Memory: Concepts and Functionality Definitions for Assigning (Adding) Or Deleting ILM or CLM Memory Physical memory can be divided into two categories: ILM and CLM. ILM Interleaved Memory, where memory consists of blocks of memory from one or more cells of the nPartition. CLM Cell Local Memory, where memory consists of blocks of memory from only a specific cell of the nPartition.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Concepts and Functionality While there is no specific minimum base memory requirement per vpar, the HPUX kernel does require a certain amount of base memory to boot successfully. For information on how much this should be, please see the document Installing and Updating Guide for HP-UX 11i v3 (11.31).
CPU, Memory, and I/O Resources (A.05.xx) Memory: Concepts and Functionality Table 6-1 Allowed Memory Migration Operations (Continued) Base Memory DOWN Allowed Allowed Float Memory Allowed Allowed Syntax for Assigning (Adding) and Deleting Base and Float Memory The resulting syntax to specify memory as either float or base is: ILM/size: -a|d mem::size[:b[ase]|f[loat]] CLM: -a|d cell:cell_ID:mem::size[:b[ase]|f[loat]] Address: -a|d mem:::base:range[:b[ase]|f[loat]] NOTE The Default is :base.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Concepts and Functionality NOTE WLM and Dynamically Migrating memory in vPars. If WLM is managing the target virtual partition, the WLM daemons wlmpard and wlmd should be stopped prior to execution of the vparmodify command to migrate the memory. For more information, see the WLM A.03.02 Release Notes at http://www.hp.com/go/wlm.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Assigning (Adding) or Deleting By Size (ILM) Memory: Assigning (Adding) or Deleting By Size (ILM) Assigning (adding) or deleting memory by specifying only size uses ILM memory.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Assigning (Adding) or Deleting By Size (ILM) See also “Memory: Notes on vPars Syntax, Rules, and Output” on page 214 and “Memory, CPU: Canceling Pending Operations” on page 233.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Assigning (Adding) Or Deleting By Size (CLM) Memory: Assigning (Adding) Or Deleting By Size (CLM) Before assigning CLM, see the section on configuring CLM: “Configuring CLM for an nPartition” on page 312. Once CLM is configured, you can assign an amount of CLM to a virtual partition.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Assigning (Adding) Or Deleting By Address Range Memory: Assigning (Adding) Or Deleting By Address Range Within the already allocated memory sizes, you can specify the memory address ranges using the mem:::base:range[:base|float] syntax. However, this is not recommended unless you are familiar with using memory addresses.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Assigning (Adding) Or Deleting By Address Range CAUTION Not allowing enough memory for the other partitions will cause the other partitions to not boot. You can boot the partition by freeing up enough memory for the partition to boot, such as by shutting down an active partition. If there are no memory ranges available to the partition below 2 GB, the partition will not boot.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Converting Base Memory to Float Memory Memory: Converting Base Memory to Float Memory In vPars A.04.xx and A.03.xx, all memory is base memory, meaning this memory cannot be removed from a virtual partition while the virtual partition is up. In vPars A.05.01, if you wish to remove memory from a virtual partition while the virtual partition is up, you will need to have that amount of memory added to the virtual partition as float.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Converting Base Memory to Float Memory For more information on the mixed HP-UX 11i v2/v3 vPars environment, see “Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx” on page 68.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Granularity Concepts Memory: Granularity Concepts Granularity refers to the unit size by which memory assigned to all virtual partitions in a vPars database (vpdb) can be increased or decreased. Granularity reflects only the unit size of memory and not the amount of memory that is assigned. This section briefly covers configuring memory granularity. The default granularity is 128 MB for ILM and 128 MB for CLM.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Granularity Issues (Integrity and PA-RISC) Memory: Granularity Issues (Integrity and PA-RISC) CAUTION (vparcreate only) When you specify the granularity value for only one type of memory (ILM or CLM), the granularity value for the other type of memory is set using the default granularity value. For example, if you specify only -g ILM:256, the -g CLM:128 is implied where 128 is the vPars default granularity value.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Setting the Granularity Values (Integrity) Memory: Setting the Granularity Values (Integrity) Syntax The syntax for setting granularity unit size is: -g ILM|CLM:unit[:y|n] where: is granularity specifies whether the unit size is applied to ILM or CLM is the granularity unit size in MBs This value must be an integral power of 2 (in other words, 2^X) and be greater than or equal to 64. specifies whether granularity unit size should be written to firmware.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Setting the Granularity Values (Integrity) If you specify the above command without the :y, vparcreate only writes the unit granularity value to the vPars database; it does not write the value to firmware. If you specify the above command with the :y, vparcreate writes the unit granularity value to both the vPars database and to firmware.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Setting the Granularity Values (Integrity) Configuring Granule Size The following procedure illustrates how to configure granule size on Integrity servers. 1. Use the parstatus command to determine the total amount of ILM in the system: # parstatus -p nPar_number -V 2. If the system has any CLM, use the parstatus command to determine the maximum amount of CLM in use by any cell: # parstatus -c cell_number... -V 3.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Setting the Granularity Values (Integrity) Thus, the maximum CLM on any cell is 48 GB and the total ILM in the system is 32 GB. Find the minimum granule size using the vparenv command: # vparenv vparenv: The next boot mode setting is "vPars". vparenv: The ILM granule size setting is 512. vparenv: The CLM granule size setting is 512. vparenv: Note: Any changes in the above settings will become effective only after the next system reboot.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Setting the Granularity Values (PA-RISC) Memory: Setting the Granularity Values (PA-RISC) Syntax The syntax for setting granularity unit size is -g ILM|CLM:unit[:y|n] where g ILM|CLM unit y|n is granularity specifies whether the unit size is applied to ILM or CLM is the granularity unit size in MBs This value must be an integral power of 2 (in other words, 2^X) and be greater than or equal to 64.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Notes on vPars Syntax, Rules, and Output Memory: Notes on vPars Syntax, Rules, and Output Memory: CLI Rules for Dynamic Migration of Memory Please note the following CLI (Command Line Interface) rules for online migration of memory and CPUs while the target partitions are up.
CPU, Memory, and I/O Resources (A.05.xx) Memory: Notes on vPars Syntax, Rules, and Output • The unit for the specified size of memory for the vPars commands is megabytes; parmodify uses gigabytes. • Memory is allocated in multiples of granule size.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Concepts and Functionality CPU: Concepts and Functionality NOTE Processor Terminology Processing resources under vPars, both as input arguments and command outputs, are described as “CPUs.” For multi-core processors such as the PA-8800 and dual-core Intel Itanium 2 processors, the term “CPU” is synonymous with “core.” The term “processor” refers to the hardware component that plugs into a processor socket.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Adding and Deleting by Total CPU: Adding and Deleting by Total The basic syntax for adding and deleting CPUs is: -[a|d|m] cpu::num where: specifies adding, deleting, or modifying the total count of CPUs. specifies the number of CPUs. a|d|m num NOTE The virtual partition can be either up or down when using the cpu::num syntax.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Adding or Deleting by CLP (Cell Local Processor) CPU: Adding or Deleting by CLP (Cell Local Processor) Similar to CLM (cell local memory), CLP (cell local processor) refers to CPUs on a specific cell. The syntax to specify CLP is: -[a|d|m] cell:cell_ID:cpu::num where: a d m cell_ID num NOTE add delete modify the cell ID the number of CPUs from the cell to be added to or deleted from the virtual partition.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Adding or Deleting by Hardware Path CPU: Adding or Deleting by Hardware Path The syntax for specifying by hardware path is: -[a|d] cpu:hw_path where: a d hw_path NOTE add delete the hw_path (you can find the hardware path using ioscan or vparstatus -v) The target virtual partition can be up or down when specifying by hardware path. CPUs that are added using the hardware path syntax can be deleted only by using the hardware path syntax.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Notes on vPars Syntax, Rules, and Output CPU: Notes on vPars Syntax, Rules, and Output CPU: CLI Rules for Dynamic Migration of Memory and CPU Please note the following CLI (Command Line Interface) rules for online migration of memory and CPUs while the target partitions are up.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Notes on vPars Syntax, Rules, and Output • When adding by hardware path, the total count changes only when the partition is up. The total does not change if the specified CPU is already assigned to the partition. • When adding by hardware path and the partition is down, you cannot have the number of CPUs added by hardware path exceed the current total value.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Dual-Core Processors CPU: Dual-Core Processors With the PA-8800s and other dual-core processors, there are two CPUs per socket. (On a cell board with four sockets, this allows 8 CPUs per cell board.) The CPUs that share the socket are called sibling CPUs. Splitting sibling CPUs across virtual partitions refers to assigning one sibling CPU to one partition and assigning the other sibling CPU to a different virtual partition.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Dual-Core Processors Figure 6-7 Using parmgr to determine dual-core processors Determining Sibling CPUs Once you have determined that you have a dual-core system, the siblings have adjacent hardware paths. The first core’s path ends in an even number, and its sibling’s path ends in the following (odd) number.
CPU, Memory, and I/O Resources (A.05.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Hyperthreading ON/OFF (HT ON/OFF) CPU: Hyperthreading ON/OFF (HT ON/OFF) Hyperthreading is a new feature supported in HP-UX 11i v3 (11.31) environments on servers with the dual core Intel Itanium 2 processors. It provides for executing multiple threads on a single core. This allows multiple hardware threads to share under-utilized resources, increasing overall throughput and performance.
CPU, Memory, and I/O Resources (A.05.xx) CPU: Hyperthreading ON/OFF (HT ON/OFF) This means that all the vPars commands for CPUs work the same as they did in vPars A.04.xx, including using the same legacy hardware path format. • HT ON is not supported in a mixed HP-UX 11i v2/v3 vPars environment. • Turning hyperthreading on or off at the EFI level or Monitor level has nPar wide scope.
CPU, Memory, and I/O Resources (A.05.xx) CPUs: Managing I/O Interrupts CPUs: Managing I/O Interrupts This section describes information you need if you are managing I/O interrupts on a vPars-enabled system. Note that migrating interrupts should only be done by advanced administrators for performance tuning. intctl command The intctl command is a HP-UX tool that allows you to manage I/O interrupts among active CPUs. For HP-UX 11i v2 and later, the software for intctl is part of the Core OS.
CPU, Memory, and I/O Resources (A.05.xx) CPU: CPU Monitor (formerly known as LPMC Monitor) CPU: CPU Monitor (formerly known as LPMC Monitor) The CPU Monitor (a part of the diagnostic tool Event Monitor Services (EMS) and not a part of the vPars Monitor) is designed to Monitor cache parity errors within the CPUs on the system. With its Dynamic Processor Resilience (DPR), if the CPU Monitor detects a pre-determined number of errors, the CPU Monitor will deactivate a CPU for the current boot session.
CPU, Memory, and I/O Resources (A.05.xx) CPU: CPU Monitor (formerly known as LPMC Monitor) Dual-core processors have two CPUs (that is, cores) per processor. Deactivation happens on a CPU level, but deconfiguration happens at the socket level. If a processor’s socket is deconfigured, both CPUs sharing the socket will be unavailable.
CPU, Memory, and I/O Resources (A.05.xx) Memory, CPU: Canceling Pending Operations Memory, CPU: Canceling Pending Operations Beginning with vPars A.05.01, you can now cancel pending CPU and memory operations with the new -C SequenceID option to the vparmodify command: # vparmodify -p vp_name -C sequenceID The sequenceID value comes from the vparstatus -v output. CPU and memory operations may not occur instantaneously.
CPU, Memory, and I/O Resources (A.05.xx) Memory, CPU: Canceling Pending Operations Online float memory addition or deletion can take significant time or even fail if the target virtual partition is under memory pressure. Use vmstat or other virtual memory monitoring tools to check the memory pressure on the target partition. In particular, if you are deleting float memory, make sure the target virtual partitions is not under memory pressure. Cancel Pending Usage To use the cancel pending feature: 1.
CPU, Memory, and I/O Resources (A.05.xx) Memory, CPU: Canceling Pending Operations Note that operations on different virtual partitions can be canceled because the sequenceID is unique within each virtual partition. Chapter 6 • An operation consists of the entire command line of the modification requests, including all options. You cannot cancel a portion of a command. • The OL* Details show N/A if there have been no CPU or memory OL* operations performed since the virtual partition was booted.
CPU, Memory, and I/O Resources (A.05.
7 CPU, Memory, and I/O Resources (A.04.xx) Managing Hardware Resources • I/O Allocation (Adding or Deleting I/O Resources) • Memory Allocation (Firmware Configuration and Adding or Deleting Memory Resources) • CPU Allocation (Adding or Deleting CPU Resources) • Using iCAP (formerly known as iCOD) with vPars • CPU Monitor (deallocation and deconfiguration) NOTE Chapter 7 Some examples in this chapter may use a non-nPartitionable system where there is no cell in the hardware path.
CPU, Memory, and I/O Resources (A.04.xx) I/O: Concepts I/O: Concepts Acronyms LBA Local Bus Adapter SBA System Bus Adapter System, Cells, SBA, LBA, Devices and Relationships On a server, an I/O device communicates to the system through the LBA and SBA. The path looks like Figure 7-1 System to I/O Device Relationship This corresponds to the ioscan hardware path output for an I/O device of sba/lba/ ... /device. A LBA actually owns all the devices attached to it.
CPU, Memory, and I/O Resources (A.04.xx) I/O: Concepts Figure 7-4 vPars allocates at LBA level not SBA level A system has multiple SBAs, but assignments remain at the LBA levels.
CPU, Memory, and I/O Resources (A.04.
CPU, Memory, and I/O Resources (A.04.xx) I/O: Adding or Deleting LBAs I/O: Adding or Deleting LBAs I/O Syntax in Brief The basic core syntax for adding or deleting I/O resources is: -a|d io:hardware_path where: a d hardware_path is adding is deleting is the hardware path of the I/O Examples • To add all hardware using the SBA/LBA hardware path of 1/2 to an existing partition winona2: winona1# vparmodify -p winona2 -a io:1.
CPU, Memory, and I/O Resources (A.04.xx) I/O: Allocation Notes I/O: Allocation Notes When planning or performing I/O allocation, note the following: • An LBA can be assigned to at most one virtual partition at any given time. When you are planning your I/O to virtual partition assignments, note that only one virtual partition may own any hardware at or below the LBA (Local Bus Adapter) level. In other words, hardware at or below the LBA level must be in the same virtual partition.
CPU, Memory, and I/O Resources (A.04.xx) I/O: Allocation Notes where the I/O assignment is specified using the LBA level (-a io:0.0.0.) and the boot disk is specified using the full hardware path (-a io:0.0.0.2.0.6.0). For information on using the LBA level on nPartitionable systems, also see “Planning, Installing, and Using vPars with an nPartitionable Server” on page 58. • SBA/LBA versus cell/SBA/LBA When viewing hardware paths, note the following: 1.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Concepts and Functionality Memory: Concepts and Functionality Acronyms ILM Interleaved Memory. • • CLM The nPartition’s system default is to have all memory configured as ILM. vPars A.03.xx and A.02.xx use and assign only ILM; vPars A.04.xx allows use of ILM and CLM. Cell Local Memory. • • Using nPartition commands, you can re-configure a portion of a cell’s memory as CLM. Beginning with vPars A.04.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Assigning by Size (ILM) Memory: Assigning by Size (ILM) Assigning memory by specifying only size uses ILM memory. ILM memory is the only type of memory used in vPars A.03.xx and earlier. vPars A.04.xx and later can use either ILM or CLM memory.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Assigning by Size (CLM) Memory: Assigning by Size (CLM) Before assigning CLM, see the section on configuring CLM: “Configuring CLM for an nPartition” on page 312.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Specifying Address Range Memory: Specifying Address Range Within the already allocated memory sizes, you can specify the memory address ranges using the mem:::base:range syntax. However, this is not recommended unless you are familiar with using memory addresses. For PA-RISC systems, you should also be familiar with the requirement that all HP-UX kernels fit within 2 GB of memory, as described in “2 GB Restriction (PA-RISC only)” on page 247.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Specifying Address Range If you use the defaults of the dynamic tunables, you will not run into the 2 GB limit. However, if you have adjusted the dynamic tunables, it is possible to run beyond the 2 GB boundary. For more information on adjusting the kernel size with dynamic tunables, see the white paper Dynamically Tunable Kernel Parameters at http://docs.hp.com.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Granularity Concepts Memory: Granularity Concepts Granularity refers to the unit size in which memory is assigned to all virtual partitions in a given vPars database (vpdb). Granularity reflects only the unit size of memory and not the amount of memory that is assigned. This section briefly covers configuring memory granularity. The default granularity is 128 MB for ILM and 128 MB for CLM. However, you can specify your own granularity for CLM and/or ILM.
CPU, Memory, and I/O Resources (A.04.xx) Granularity Issues (Integrity and PA-RISC) Granularity Issues (Integrity and PA-RISC) CAUTION (vparcreate only) When you specify the granularity value for only one type of memory (ILM or CLM), the granularity value for the other type of memory is set using the default granularity value. For example, if you specify only -g ILM:256, the -g CLM:128 is implied where 128 is the vPars default granularity value.
CPU, Memory, and I/O Resources (A.04.xx) Granularity Issues (Integrity and PA-RISC) • Especially for nPartitions or systems containing 32 GB or more of total memory, you should set the granule to the highest possible granule size to reduce the time in scanning the memory during the initial hardware boot. • (Integrity only) In order for the virtual partitions in an active database to be able to boot, the granularity values in the vPars database must match those written in the system firmware.
CPU, Memory, and I/O Resources (A.04.xx) Granularity Issues (Integrity and PA-RISC) Careful configuration planning will avoid this situation. Granularity limitations do not apply to PA-RISC platforms. However, there are guidelines that do apply to both PA-RISC and Integrity systems. These are described next. + Recommendations for ILM and CLM granularity specifications: On PA-RISC platforms, each vPar needs ILM below 2 GB to load and launch its kernel.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Choosing a Granularity Value and Boot Time (Integrity) Memory: Choosing a Granularity Value and Boot Time (Integrity) During the boot process of HP-UX on Integrity vPars, the time it takes to obtain the memory layout information for the nPartition is relative to the number of memory granules configured for the nPartition.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Setting the Granularity Values (Integrity) Memory: Setting the Granularity Values (Integrity) Syntax The syntax for setting granularity unit size is: -g ILM|CLM:unit[:y|n] where: is granularity specifies whether the unit size is applied to ILM or CLM is the granularity unit size in MBs This value must be an integral power of 2 (in other words, 2^X) and be greater than or equal to 64. specifies whether the granularity unit size should be written to firmware.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Setting the Granularity Values (Integrity) If you specify the above command without the :y, vparcreate writes the unit granularity value to only the vPars database; it does not write the value to firmware. If you specify the above command with the :y, vparcreate writes the unit granularity value to both the vPars database and to firmware.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Setting the Granularity Values (Integrity) Configuring Granule Size The following procedure illustrates how to configure granule size on Integrity servers. 1. Use the parstatus command to determine the total amount of ILM in the system: # parstatus -p nPar_number -V 2. If the system has any CLM, use the parstatus command to determine the maximum amount of CLM in use by any cell: # parstatus -c cell_number... -V 3.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Setting the Granularity Values (Integrity) Thus, the maximum CLM on any cell is 48 GB and the total ILM in the system is 32 GB. Find the minimum granule size using the vparenv command: # vparenv vparenv: The next boot mode setting is "vPars". vparenv: The ILM granule size setting is 512. vparenv: The CLM granule size setting is 512. vparenv: Note: Any changes in the above settings will become effective only after the next system reboot.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Setting the Granularity Values (PA-RISC) Memory: Setting the Granularity Values (PA-RISC) Syntax The syntax for setting granularity unit size is: -g ILM|CLM:unit[:y|n] where: g ILM|CLM unit y|n is granularity specifies whether the unit size is applied to ILM or CLM is the granularity unit size in MBs This value must be an integral power of 2 (in other words, 2^X) and be greater than or equal to 64.
CPU, Memory, and I/O Resources (A.04.xx) Memory: Allocation Notes Memory: Allocation Notes • The default memory assigned to a virtual partition is 0 MB, so you need to specify enough memory for your applications and the operating system. While there is no specific minimum base memory requirement per vpar, the HPUX kernel does require a certain amount of base memory to boot successfully. For this reason, we currently recommend that 1 GB of base memory is assigned per vpar.
CPU, Memory, and I/O Resources (A.04.xx) CPU CPU NOTE Processor Terminology Processing resources under vPars, both as input arguments and command outputs, are described as “CPUs.” For multi-core processors such as the PA-8800 and dual-core Intel Itanium 2 processors, the term “CPU” is synonymous with “core.” The term “processor” refers to the hardware component that plugs into a processor socket.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Boot Processor and Dynamic CPU Definitions CPU: Boot Processor and Dynamic CPU Definitions Beginning with vPars A.04.01, the restrictions of bound CPUs have been removed as well as the terms bound and unbound. Now, there are two types of CPUs: boot processors and dynamic CPUs. The Boot Processor is the CPU on which the OS kernel of the virtual partition was booted. There is one boot processor per virtual partition.
CPU, Memory, and I/O Resources (A.04.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Adding and Deleting by Total CPU: Adding and Deleting by Total The basic syntax for adding and deleting CPUs is: -a|d|m cpu::num where: specifies adding, deleting, or modifying the total count of CPUs specifies the number of CPUs a|d|m num NOTE The virtual partition can be either up or down when using the cpu::num syntax.
CPU, Memory, and I/O Resources (A.04.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Adding or Deleting by CLP (Cell Local Processor) CPU: Adding or Deleting by CLP (Cell Local Processor) Similar to CLM (cell local memory), CLP (cell local processor) refers to CPUs on a specific cell. The syntax to specify CLP is: -[a|d] cell:cell_ID:cpu::num where: a d cell_ID num NOTE is adding is deleting is the cell ID is the number of CPUs from the cell to be added to or deleted from the virtual partition.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Adding or Deleting by Hardware Path CPU: Adding or Deleting by Hardware Path The syntax for specifying by hardware path is: -[a|d] cpu:hw_path where: a d hw_path NOTE is adding is deleting is the hw_path (you can find the hardware path using ioscan or vparstatus -v) The target virtual partition can be up or down when specifying by hardware path. CPUs that are added using the hardware path syntax can be deleted only by using the hardware path syntax.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Syntax, Rules, and Notes CPU: Syntax, Rules, and Notes vparstatus • When a virtual partition is down, vparstatus does not show any CPU assigned as the boot processor. The boot processor is not assigned until the virtual partition is actually booted. • If a virtual partition is down and assigned only one CPU, a CPU will be reserved by the vPars Monitor, making it unavailable. The specific CPU reserved is not determined until boot time.
CPU, Memory, and I/O Resources (A.04.xx) Managing I/O Interrupts Managing I/O Interrupts This section describes information you need if you are managing I/O interrupts on a vPars-enabled system. Note that migrating interrupts should only be done by advanced administrators for performance tuning. intctl command The intctl command is a HP-UX tool that allows you to manage I/O interrupts among active CPUs. For HP-UX 11i v2 and later, the software for intctl is part of the Core OS.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx and iCAP B.07) CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx and iCAP B.07) iCAP CPUs are unlicensed CPUs. The unlicensed CPUs may be shown as available CPUs in the vparstatus -A output. To use iCAP CPUs, you must first purchase them; then, you can activate and assign them to a virtual partition.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx and iCAP B.07) Intended Active Boundary Using the iCAP software, the Intended Active number represents the number of licensed CPUs that could be activated within an nPartition. To view the current Intended Active number, you can use the iCAP command icod_stat. To change the Intended Active number, you can use the iCAP command icod_modify.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Dual-Core Processors CPU: Dual-Core Processors With the PA-8800s and other dual-core processors, there are two CPUs per socket. (On a cell board with four sockets, this allows 8 CPUs per cell board.) The CPUs that share the socket are called sibling CPUs. Splitting sibling CPUs across virtual partitions refers to assigning one sibling CPU to one partition and assigning the other sibling CPU to a different virtual partition.
CPU, Memory, and I/O Resources (A.04.xx) CPU: Dual-Core Processors Figure 7-7 using parmgr to determine dual-core processors Determining Sibling CPUs Once you have determined that you have a dual-core system, the siblings have adjacent hardware paths. The first core’s path ends in an even number, and its sibling’s path ends in the following (odd) number.
CPU, Memory, and I/O Resources (A.04.
CPU, Memory, and I/O Resources (A.04.xx) CPU: CPU Monitor (formerly known as LPMC Monitor) CPU: CPU Monitor (formerly known as LPMC Monitor) The CPU Monitor (a part of the diagnostic tool Event Monitor Services (EMS) and not a part of the vPars Monitor) is designed to Monitor cache parity errors within the CPUs on the system. With its Dynamic Processor Resilience (DPR), if the CPU Monitor detects a pre-determined number of errors, the CPU Monitor will deactivate a CPU for the current boot session.
CPU, Memory, and I/O Resources (A.04.xx) CPU: CPU Monitor (formerly known as LPMC Monitor) Dual-core processors have two CPUs (that is, cores) per processor. Deactivation happens on a CPU level, but deconfiguration happens at the socket level. If a processor’s socket is deconfigured, both CPUs sharing the socket will be unavailable.
CPU, Memory, and I/O Resources (A.04.
8 CPU, Memory, and I/O Resources (A.03.xx) NOTE The A.03.xx release of vPars, and therefore this chapter, applies only to PA-RISC systems.
CPU, Memory, and I/O Resources (A.03.xx) I/O: Concepts I/O: Concepts Acronyms LBA Local Bus Adapter SBA System Bus Adapter System, Cells, SBA, LBA, Devices and Relationships On a server, an I/O device communicates to the system through the LBA and SBA. The path looks like Figure 8-1 System to I/O Device Relationship This corresponds to the ioscan hardware path output for an I/O device of sba/lba/ ... /device. A LBA actually owns all the devices attached to it.
CPU, Memory, and I/O Resources (A.03.xx) I/O: Concepts Figure 8-4 vPars allocates at LBA level not SBA level A system has multiple SBAs, but assignments remain at the LBA levels.
CPU, Memory, and I/O Resources (A.03.
CPU, Memory, and I/O Resources (A.03.xx) I/O: Adding or Deleting LBAs I/O: Adding or Deleting LBAs I/O Syntax in Brief The basic core syntax for adding or deleting I/O resources is: -a|d io:hardware_path where: a d hardware_path is adding is deleting is the hardware path of the I/O Examples • To add all hardware using the SBA/LBA hardware path of 1/2 to an existing partition winona2: winona1# vparmodify -p winona2 -a io:1.
CPU, Memory, and I/O Resources (A.03.xx) I/O: Allocation Notes I/O: Allocation Notes When planning or performing I/O allocation, note the following: • An LBA can be assigned to at most one virtual partition at any given time. When you are planning your I/O to virtual partition assignments, note that only one virtual partition may own any hardware at or below the LBA (Local Bus Adapter) level. In other words, hardware at or below the LBA level must be in the same virtual partition.
CPU, Memory, and I/O Resources (A.03.xx) I/O: Allocation Notes where the I/O assignment is specified using the LBA level (-a io:0.0) and the boot disk is specified using the full hardware path (-a io:0.0.2.0.6.0). For an nPartitionable system, the vparcreate command would look like: #vparcreate -p vpar1 -a cpu::1 -a cpu:::1 -a mem::1024 -a io:0.0.0 \ -a io:0.0.0.2.0.6.0:BOOT where the I/O assignment is specified using the LBA level (-a io:0.0.0.
CPU, Memory, and I/O Resources (A.03.xx) Memory: Concepts and Functionality Memory: Concepts and Functionality Acronyms ILM Interleaved Memory vPars A.03.xx and A.02.xx use and assign only ILM; vPars A.04.xx allows use of ILM and CLM. Assignments You assign memory to a virtual partition: • by size This uses the nPartition’s ILM. Within the available nPartition’s ILM, you can also: • specify an address range to use This does not increase the amount of memory assigned to the virtual partition.
CPU, Memory, and I/O Resources (A.03.xx) Memory: Assigning By Size (ILM) Memory: Assigning By Size (ILM) Assigning memory by specifying only size uses ILM memory. ILM memory is the only type of memory used in vPars A.03.xx and earlier. vPars A.04.xx and later can use either ILM or CLM memory.
CPU, Memory, and I/O Resources (A.03.xx) Memory: Specifying Address Range Memory: Specifying Address Range Within the already allocated memory sizes, you can specify the memory address ranges using the mem:::base:range syntax. However, this is not recommended unless you are familiar with using memory addresses. You should also be familiar with the requirement that all HP-UX kernels fit within 2 GB of memory, as described in “2 GB Restriction” on page 286.
CPU, Memory, and I/O Resources (A.03.xx) Memory: Allocation Concepts and Notes Memory: Allocation Concepts and Notes • The unit for the specified size of memory for the vPars commands is megabytes; parmodify uses gigabytes. • The default memory assigned to a virtual partition is 0 MB, so you need to specify enough memory for your applications and the operating system.
CPU, Memory, and I/O Resources (A.03.xx) CPU CPU NOTE Processor Terminology Processing resources under vPars, both as input arguments and command outputs, are described as “CPUs.” For multi-core processors such as the PA-8800, the term “CPU” is synonymous with “core.” The term “processor” refers to the hardware component that plugs into a processor socket.
CPU, Memory, and I/O Resources (A.03.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Bound and Unbound CPU: Bound and Unbound Definitions With vPars, there are two types of CPUs: bound and unbound. A bound CPU is a CPU that is assigned to and handles I/O interrupts for a virtual partition. Every virtual partition must have at least one bound CPU to handle its I/O interrupts. CPUs that are not assigned to any virtual partition or that are assigned to a virtual partition but do not handle its I/O interrupts are unbound CPUs.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Adding and Removing Bound CPUs CPU: Adding and Removing Bound CPUs CPU Allocation Syntax In Brief To understand how to assign CPUs, you need to understand the command syntax. Below is a brief explanation of the CPU allocation syntax for the vparcreate command. For complete information, see the vparcreate (1M), vparmodify (1M), and vparresources (5) manpages.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Adding a CPU as a Bound CPU CPU: Adding a CPU as a Bound CPU All CPUs begin as not being assigned to any virtual partition, so all CPUs begin as unbound CPUs. However, you can assign CPUs as bound CPUs to the partition by specifying the min number in the -a cpu:::min command line option.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Removing a Bound CPU CPU: Removing a Bound CPU To remove a bound CPU from a virtual partition, use the vparmodify command to modify the total and min parameters for the virtual partition. NOTE When executing any operations relating to bound CPUs (adding, modifying, or deleting), the target virtual partition must be down.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Adding, Removing, and Migrating Unbound CPUs CPU: Adding, Removing, and Migrating Unbound CPUs For vPars A.03.xx and earlier, after min bound CPUs are assigned to a virtual partition, the quantity (total min) CPUs are assigned to the partition as unbound CPUs. Therefore, to migrate unbound CPUs, specify total such that (total-min) is the number of unbound CPUs assigned to the target partition.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Managing I/O Interrupts CPU: Managing I/O Interrupts This section describes information you need if you are managing I/O interrupts on a vPars-enabled system. Note that migrating interrupts should only be done by advanced administrators for performance tuning. intctl command The intctl command is a HP-UX tool that allows you to manage I/O interrupts among active CPUs.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Dual-Core Processors CPU: Dual-Core Processors With the PA-8800s and other dual-core processors, there are two CPUs per socket. (On a cell board with four sockets, this allows 8 CPUs per cell board.) The CPUs that share the socket are called sibling CPUs. Splitting sibling CPUs across virtual partitions refers to assigning one sibling CPU to one partition and assigning the other sibling CPU to a different virtual partition.
CPU, Memory, and I/O Resources (A.03.xx) CPU: Dual-Core Processors Figure 8-7 using parmgr to determine dual-core processors Determining Sibling CPUs Once you have determined that you have a dual-core system, the siblings have adjacent hardware paths. The first core’s path ends in an even number, and its sibling’s path ends in the following (odd) number.
CPU, Memory, and I/O Resources (A.03.
CPU, Memory, and I/O Resources (A.03.xx) CPU: CPU Monitor (formerly known as LPMC Monitor) CPU: CPU Monitor (formerly known as LPMC Monitor) The CPU Monitor (a part of the diagnostic tool Event Monitor Services (EMS) and not a part of the vPars Monitor) is designed to Monitor cache parity errors within the CPUs on the system. With its Dynamic Processor Resilience (DPR), if the CPU Monitor detects a pre-determined number of errors, the CPU Monitor will deactivate a CPU for the current boot session.
CPU, Memory, and I/O Resources (A.03.
9 nPartition Operations This section briefly covers nPartition operations when vPars are in an nPartition. For complete information on nPartitions, see the nPartition document nPartition Administrator's Guide available at http://docs.hp.com. Basic Conceptual Points on using vPars within nPartitions • Only one vPars Monitor is booted per nPartition. • Virtual partitions exist within an nPartition, but they cannot span across nPartitions.
nPartition Operations nPartition Information • Once the BIB (Boot-Is-Blocked) state is set in the nPartition, virtual partitions will not be able to boot up until all the virtual partitions have been shutdown and the Monitor rebooted. In other words, once there is a pending reboot for reconfiguration (RFR) within the given nPartition, no virtual partitions can be rebooted until all the virtual partitions within the given nPartition are shut down and the involved vPars Monitor is rebooted.
nPartition Operations Setting Hyperthreading (HT ON/OFF) and cpuconfig Primer Setting Hyperthreading (HT ON/OFF) and cpuconfig Primer This section describes how to set HT ON/OFF for the latest dual-core processors which offer this feature. For complete information on hyperthreading and cpuconfig, see the document nPartition Administrator's Guide. NOTE vPars and HT ON/OFF • HT ON/OFF should be set using the EFI shell’s cpuconfig command. An alternative method is to use the vPar Monitor’s threads command.
nPartition Operations Setting Hyperthreading (HT ON/OFF) and cpuconfig Primer Cell ---1 Slot/ CPU Module -----0/1/0 # of Logical CPUs ------2 Speed -------1.4 GHz L3 Cache Size -----6 MB L4 Cache Size -----None Family/ Model (hex.) ------20/00 Processor Rev State --- ------------C0 Active CPU threads are turned off. • to show only the state of the threads: Shell> cpuconfig threads cpuconfig: Threads are turned off.
nPartition Operations Setting Hyperthreading (HT ON/OFF) and cpuconfig Primer Cell ---1 Module -----0/1/0 CPUs ------2 Speed -------1.4 GHz Size -----6 MB Size -----None (hex.) ------20/00 Rev --C0 State ------------Active L4 Cache Size -----None Family/ Model (hex.) ------20/00 Processor Rev State --- ------------C0 Active CPU threads will be off after a reset.
nPartition Operations Rebooting and Reconfiguring Conceptual Points Rebooting and Reconfiguring Conceptual Points • If there is a pending reboot for reconfiguration (RFR) for the involved nPartition, no virtual partitions will be rebooted until all the virtual partitions within the given nPartition are shut down and the involved vPars Monitor is rebooted.
nPartition Operations Reconfiguring the nPartition Reconfiguring the nPartition You must perform a Reboot-for-Reconfig (RFR) on an nPartition in the following circumstances: • whenever you add cells to the nPartition • whenever you need to allow an inactive cell to join the nPartition (such as after changing a cell use-on-next-boot value from “n” to “y”).
nPartition Operations Reconfiguring the nPartition From vPars mode: 1. Perform the changes as you would in a non-vPars environment. For example, if we want to add cell 6 to partition 0 for the next boot of the vPars Monitor: keira1# parmodify -p0 -a 6:base:y:ri In order to activate any cell that has been newly added,reboot the partition with the -R option. Command succeeded. 2. Perform a Reboot-for-Reconfig (RFR) from a virtual partition.
nPartition Operations Reconfiguring the nPartition In order to activate any cell that has been newly added,reboot the partition with the -R option. Command succeeded. 2. Perform a Reboot-for-Reconfig (RFR) from a virtual partition. For example, keira1# vparstatus keira1# shutdown -R . . . Transition to run-level0 is complete. Executing "/sbin/reboot-R ".
nPartition Operations Reconfiguring the nPartition 1 0/1 Active 1000 1000 1000 1000 1000 1000 1000 1000 Primary Boot Path: Boot Actions: 1/0/0/3/0.6 Go to BCH. HA Alternate Boot Path: Boot Actions: 1/0/0/3/0.6 Go to BCH. Alternate Boot Path: Boot Actions: Console Path: 310 2A 2B 0A 0B 1A 1B 2A 2B MHz MHz MHz MHz MHz MHz MHz MHz Idle Idle Active Idle Idle Idle Idle Idle 32 32 32 32 32 32 32 32 MB MB MB MB MB MB MB MB 32 32 32 32 32 32 32 32 MB MB MB MB MB MB MB MB 1/0/12/1/0.8 Go to BCH.
nPartition Operations Putting an nPartition into an Inactive State & Other GSP Operations Putting an nPartition into an Inactive State & Other GSP Operations 1. If possible, gracefully shutdown all the virtual partitions within the target nPartition. For example: keira1# vparstatus keira1# shutdown -h keira2# vparstatus keira2# shutdown -h 2. On the console, you will arrive at the MON> prompt.
nPartition Operations Configuring CLM for an nPartition Configuring CLM for an nPartition ILM memory can be re-configured to be CLM using the parmodify command. Then, you can assign existing available CLM to a virtual partition. For complete information on CLM and configuring cells and nPartitions, see the nPartition’s Guide.
nPartition Operations Configuring CLM for an nPartition • When performing parmodify commands within a vPars environment, you will see only the cells that are within the nPartition running vPars. If you wish to add cells from outside the nPartition, you will need to be in standalone (PA-RISC) or nPars (Integrity) mode to see the other cells.
nPartition Operations Configuring CLM for an nPartition Alternate Boot Path : HA Alternate Boot Path : PDC Revision : IODCH Version : Cell Architecture : CPU Compatibility : CPU Speed : 1600 MHz Core Cell : cab1,cell4 Core Cell Choice [0] : Total Good Memory Size : Total Interleave Memory: Total Requested CLM : Total Allocated CLM : 314 3.66 ffff Itanium(R)-based BCF-640 cab1,cell4 40.0 GB 40.0 GB 0.0 GB 0.
10 Crash Processing and Recovery Crashing and Recovery Processes • Crash Processing • Network and Tape Recovery • Expert Recovery Chapter 10 315
Crash Processing and Recovery Crash Processing Crash Processing Crash processing for a virtual partition is similar to the crash processing of a non-vPars OS: the OS is quiesced, portions of memory are written to disk, and in the case of vPars, resources are released to the Monitor. When the Monitor crashes, a Monitor dump is created. By default, kernel dumps are not saved. When there is a HPMC or MCA or when a TOC is issued, the virtual partitions are launched for crash processing.
Crash Processing and Recovery Crash Processing 3. (PA-RISC only) allows you to chose an alternate device to which the Monitor dump is written. The alternate device must contain the pre-allocated file /stand/vpmon.dmp. The file vpmon.dmp is automatically created in /stand of a partition’s boot disk by the vPars startup script. 4. soft resets the current hard partition1. 5. hard resets the current hard partition. 6. boots the specified virtual partition for crash processing 7.
Crash Processing and Recovery Crash Processing Step 1. (11i v2 and above) Beginning with HP-UX 11i v2 and therefore vPars A.04, the savecrash processing has changed. Instead of copying the kernel file that was in use during the crash, the directory /stand/crashconfig is copied.
Crash Processing and Recovery Network and Tape Recovery Network and Tape Recovery This section covers different methods of network and tape recovery on vPars systems. The following table lists the supported recovery methods on each vPars release. Table 10-1 Supported Recovery methods by vPars Release Recovery Method A.03.xx A.04.xx A.05.xx Network recovery within a vPars environment yes yes yes Tape recovery within a vPars environment A.03.01/A.03.02: no A.04.01/A.04.
Crash Processing and Recovery Network and Tape Recovery For more information and an example, see “(PA-RISC only) The WINSTALL Boot Kernel Paths with Different Versions of Ignite-UX and the vparboot -I command” on page 24.
Crash Processing and Recovery Network and Tape Recovery Using make_net_recovery within a vPars Environment Archiving Virtual Partition make_net_recovery works the same for making archives of both non-vPars and vPars systems. Recovering a Virtual Partition from a Running Virtual Partition To recover a virtual partition, perform the following from a running virtual partition. (In these examples, the partition winona1 is running and the target partition winona2 is the partition being recovered.) 1.
Crash Processing and Recovery Network and Tape Recovery 2. From the Ignite-UX window, select "Install HP-UX". 3. Enter the network data using the data for the virtual partition that owns the boot disk that is set as the primary path within system-wide stable storage. 4. Select Recovery Archive Configuration -> Go After this virtual partition is recovered, recover the remaining partitions using the instructions in “Recovering a Virtual Partition from a Running Virtual Partition” on page 321.
Crash Processing and Recovery Network and Tape Recovery Using make_tape_recovery Outside of a vPars Environment The creation of make_tape_recovery tapes is supported on vPars-enabled servers. However with vPars A.04.01, A.03.01, and A.03.02, recoveries using these tapes must be done outside of the vPars environment; they cannot be used to recover a system from within a virtual partition. For example, the tape cannot be used with the vparboot -I command on PA-RISC servers.
Crash Processing and Recovery Network and Tape Recovery Archiving and Recovering a Virtual Partition Archiving the Virtual Partition(s) This section describes how to create the recovery tape. NOTE • To recover a single virtual partition from a tape, all active virtual partitions must be shutdown. The exception to this is using a dual-media boot. For information on using a dual-media boot, see “Using make_tape_recovery and Dual-media Boot” on page 327.
Crash Processing and Recovery Network and Tape Recovery 6. Reboot the nPartition. The vPars Monitor will start automatically if step (5) completed correctly. Any virtual partition that has been defined to autoboot will boot at this stage. You may have to manually start any virtual partitions not configured to autoboot. The vPars Monitor will only start automatically if the AUTO file was originally configured to do so. If not, you will boot up in standalone mode. 7.
Crash Processing and Recovery Network and Tape Recovery Archiving and Recovering a Virtual Partition Using Another Virtual Partition as the Ignite-UX Server Archiving the Virtual Partitions Using a Virtual Partition as the Ignite-UX Server The following steps describe how one or more virtual partitions can be archived using make_tape_recovery. These first three steps describe how to create a disaster recovery tape. 1. One of the virtual partitions is an Ignite server.
Crash Processing and Recovery Network and Tape Recovery Using make_tape_recovery and Dual-media Boot A dual-media boot allows you to boot the target partition using another disk and then recover using the tape device. Currently with Ignite-UX, you cannot boot over the network and then recover from tape; you must boot from a disk device.
Crash Processing and Recovery Network and Tape Recovery winona1# vparboot -p winona2 -B hardware_path -b /stand/WINSTALL 3. When the main Ignite-UX menu is displayed, select Install HP-UX. 4. When the User Interface and Media Options screen is displayed, select Media only installation from the Source Location Options, and Advanced Installation from User Interface Options, then select OK. 5. From the Media Installation Selection, select Boot from CD/DVD, Recover from Tape.
Crash Processing and Recovery Network and Tape Recovery Using make_tape_recovery within a vPars-environment on PA-RISC Servers (vPars A.03.03, A.04.03, A.05.01) For PA-RISC servers, beginning with vPars A.03.03 for HP-UX 11i v1 and A.04.03 for HP-UX 11iv2, vPars supports tape drives. This includes recovery of a virtual partition within a vPars environment and without using an Ignite-UX server as a boot helper.
Crash Processing and Recovery Expert Recovery Expert Recovery When you are performing Expert Recovery, you need to remember the following: • You can no longer read from or write to system-wide stable storage using setboot. See “Boot||Shut: Setboot and System-wide Stable Storage” on page 164. • mkboot modifies the LIF area, but vPars does not use the LIF area to boot a virtual partition. See “mkboot and LIF files” on page 26 and “The AUTO File on a Virtual Partition” on page 171.
11 vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) This chapter discusses the concepts and tasks on using the vPars Flexible Administrative Capability feature (formerly called Primary-Admin vPars Security). With this feature, you can specify vPars administration capabilities for zero, one, or more designated virtual partitions.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Synopsis Synopsis The vPars Flexible Administrative Capability feature restricts the usage of specific vPars commands such that they can be successfully executed from only designated virtual partitions. The specific vPars commands that are restricted are those that can alter other virtual partitions, such as vparmodify or vparreset.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Terms and Definitions CAUTION In a mixed HP-UX 11i v2/v3 vPars environment, the vparcreate and vparremove operations can only be performed from the vPars A.05.01/11.31-OS virtual partitions; vparmodify operations affecting other virtual partitions can only be performed from the vPars A.05.01/11.31-OS virtual partitions. When the flexible administrative capability is ON (enabled), setting only vPars A.04.xx/11.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Terms and Definitions From the HP-UX shell, if a superuser attempts to add or delete a virtual partition from the designated-admin virtual partition list, the superuser will be prompted for the flexible administrative capability password that was set. When the flexible administrative capability mode is OFF, there is no flexible administrative capability password.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) vparadmin -a|-d partition_name Adds or deletes a virtual partition to or from the designated-admin virtual partition list. No flexible administrative capability password is required here; passwords are required only at the HP-UX shell prompt. -l Lists all the virtual partitions that are currently in the designated-admin virtual partition list.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) vparadmin -l Lists all the virtual partitions that are currently in the designated-admin virtual partition list. Use vparadmin -a to add virtual partitions to the list. Note that vparstatus does not show any flexible administrative capability information. Without any options displays whether the vPars flexible administrative capability is ON (enabled) or OFF (disabled).
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Persistence across Monitor Reboots Persistence across Monitor Reboots If the flexible administrative capability mode is not changed from ON to OFF across Monitor reboots and the specific conditions are met (see below), the flexible administrative capability mode will remain and the virtual partitions designated as designated-admin virtual partitions will remain as designated-admin virtual partitions.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) vPars Commands vPars Commands When the flexible administrative capability mode is ON, the vPars flexible administrative capability feature restricts the vPars commands such that you can alter another virtual partition only if you execute the command from a partition that is in the designated-admin virtual partition list.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) vPars Commands the non-designated-admin virtual partition to a designated-admin virtual partition, you will need to add the partition to the designated-admin virtual partition list using the vparadmin -a command. vparstatus vparstatus does not show whether a virtual partition is in the designated-admin virtual partition list; you need to use vparadmin -l.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Example Monitor Scenario (monadmin) Example Monitor Scenario (monadmin) Below describes examples that include (from the Monitor): • • turning on the flexible administrative capability feature (which will include setting the password) adding virtual partitions to the designated-admin virtual partition list For this section, let’s assume we have the virtual partitions winona1, winona2, and winona3.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.01) Example HP-UX Shell Scenario (vparadmin) winona1# vparadmin -d winona2 Password: Virtual partition winona2 is deleted from the Designated-Admin virtual partitions list. Listing the Virtual Partitions in the Designated-admin Virtual Partition List We can verify that winona2 has been removed from the designated-admin virtual partition list. This can be performed from any partition.
vPars Flexible Administrative Capability (vPars A.03.03, vPars A.04.02, A.04.03, A.05.
12 Virtual Partition Manager (A.03.xx) This chapter provides an overview of the Virtual Partition Manager (vparmgr), which provides a GUI to the vPars commands. This chapter includes: • About the Virtual Partition Manager • Starting the Virtual Partition Manager • Using the vPars Graphical User Interface (GUI) • Stopping the Virtual Partition Manager For more detailed information, see the Virtual Partition Manager online help.
Virtual Partition Manager (A.03.xx) About the Virtual Partition Manager (vparmgr) About the Virtual Partition Manager (vparmgr) The virtual partition manager (vparmgr) provides an easy to use graphical interface to the vPars command utilities.
Virtual Partition Manager (A.03.xx) About the Virtual Partition Manager (vparmgr) creates a new virtual partition -t modify modifies an existing virtual partition. You must specify which virtual partition to modify, using the vp_name parameter. -tpar_details displays the status, attributes, and resources of a virtual partition. You must specify which virtual partition to display, using the vp_name parameter.
Virtual Partition Manager (A.03.xx) About the Virtual Partition Manager (vparmgr) Stopping the Virtual Partition Manager To exit vparmgr, click the Exit button on the virtual partition status screen.
A LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) This section contains a simplified PCI I/O block diagrams for the rp5470/L3000, rp7400/N4000, rp7405/rp7410, rp8400, and HP 9000 Superdome (SD16000, SD32000, SD64000) servers. These diagrams can be used to help determine which LBAs correspond to which physical I/O slots. The diagrams presented here were created due to incorrect or inaccessible PA-RISC documentation. For other supported servers, please see your server manual.
LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) rp5470/L3000 I/O Block Diagram rp5470/L3000 I/O Block Diagram Figure A-1 350 Appendix A
LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) rp7400/N4000 I/O Block Diagram rp7400/N4000 I/O Block Diagram Figure A-2 Appendix A 351
LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) rp7410 and rp7405 PCI I/O Block Diagram rp7410 and rp7405 PCI I/O Block Diagram Figure A-3 352 Appendix A
LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) rp8400 PCI I/O Block Diagram rp8400 PCI I/O Block Diagram Figure A-4 Appendix A 353
LBA Hardware Path -> Physical I/O Slot Correspondence (PA-RISC only) Superdome (SD16000, SD32000, SD64000) PCI I/O Block Diagram Superdome (SD16000, SD32000, SD64000) PCI I/O Block Diagram Figure A-5 354 Appendix A
B Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx) Unbound CPUs allow you to easily adjust processing power between virtual partitions. But a corner case can occur where you will not be able to add specific unbound CPU(s) without rebooting the target partition. This appendix discusses when this situation can occur and how to work around it.
Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx) Cause Boot the Virtual Partitions When we boot the partitions, they will boot with the following bound CPUs; their respective kernels will have the following unbound CPU entries. Note that the entries for the unbound CPUs are only entries for unbound CPUs that can potentially be added to the partition.
Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx) Cause There are now two unbound CPUs, but these CPUs are not the same ones that were available at the time the partitions vpar1 or vpar3 were booted.
Problem with Adding Unbound CPUs to a Virtual Partition (A.03.
C Calculating the Size of Kernels in Memory (PA-RISC only) One requirement of vPars is the sum of sizes of the kernels running in memory within a hard partition must be less than 2 GB. This only limits the maximum number of virtual partitions that can be created. If you use the defaults of the dynamic tunables, you will not run into this 2 GB limit. However, if you have adjusted the dynamic tunables, you can perform the calculations described in this appendix to ensure you meet this criteria.
Calculating the Size of Kernels in Memory (PA-RISC only) Calculating the Size of a Kernel Calculating the Size of a Kernel To calculate the size of the kernel, perform the following using the kernel file (for example, /stand/vmunix) on the target OS: Step 1. Get the size of the kernel: # size /stand/vmunix [18784256 + 4775224 + 6696240 = 30255720 The size of the kernel is the final number: 30255720 Step 2. Divide by (1024 * 1024): ((30255720) / (1024 * 1024)) + 1 = 29.85 Step 3.
Calculating the Size of Kernels in Memory (PA-RISC only) Examples of Using the Calculations Examples of Using the Calculations Changing Dynamic Tunables If you have already migrated to a vPars server and are adjusting the dynamic tunables of a kernel, check that there is an available memory range under the 2 GB boundary to accommodate the adjusted kernel. You should do this check after adjusting the dynamic tunables but before rebooting the partition.
Calculating the Size of Kernels in Memory (PA-RISC only) Examples of Using the Calculations 362 Appendix C
D Memory Usage with vPars in nPartitions This section discusses various usages of memory for vPars within nPartitions. Within a vPars environment, memory is used not only by the HP-UX OS and applications, but can also be used by the following: • nPartition Firmware • Firmware Partitions (fPars) on Integrity servers • vPars Monitor nPartition Firmware When the nPartition boots, the firmware requires between 8 to 64 MB of each cell (therefore, using CLM).
Memory Usage with vPars in nPartitions Example System Example System Assume our example system is: • an Integrity server • running vPars A.05.
E Moving from a Standalone to vPars A standalone system running a single instance of HP-UX can be further divided into multiple virtual partitions. This section provides a brief overview of the process for moving from a standalone system environment to a virtual partitions environment. Converting a standalone system to a virtual partitions environment divides system resources among the virtual partitions and enables the system to run multiple instances of HP-UX.
Moving from a Standalone to vPars 366 Appendix E
F Supported Configurations for Memory Migration HP-UX 11i v3 (11.31) supports dynamic memory migration in conjunction with vPars. To optimize runtime performance as well as memory migration performance, system administrators configure the amount of memory that is available for critical system needs and the amount of memory that may be deleted without a reboot.
Supported Configurations for Memory Migration 368 Appendix F
Glossary vPars A.05.xx-specific Terms vPars A.03.xx-specific Terms base memory This is memory that can be only added to virtual partitions while the virtual partition is up. This memory cannot be deleted from a virtual partition while it is up. bound CPU A CPU (core) that cannot be migrated from or to virtual partitions while the involved virtual partitions are running. Bound CPUs can handle I/O interrupts.
Glossary vPars vPars HP software product that allows software partitioning. vPars Monitor The program that manages resources using the virtual partition database, boots virtual partitions and their kernels, and emulates certain firmware calls. vPars Partition Database The database that contains the configuration for all the virtual partitions.
Index Symbols /stand filesystem, 77 A adding cpu to a partition, 217, 260, 288 adding i/o to a partition, 190, 191, 241, 242, 281, 282 adding memory resources to a partition, 195, 244, 284 alternate partition database files, 181 application fault isolation, 20 attributes, 158 AUTO file, 171 Autoboot, 65, 172 B BCH.
Index G getauto, 134 glance, 25 golden image, 319 granularity, 207, 249 GSP.
Index O ODE, 23 OLAR.
Index adding a cell, 307 adding cpu resources, 217, 260, 288 adding i/o resources, 190, 191, 241, 242, 281, 282 adding memory resources, 195, 244, 284 compared to hard partitions, 18 creating, 155 defined, 18 monitor, 32 naming, 61 rebooting, 160 removing, 157 removing cpu resources, 217, 260, 288 removing i/o resources, 190, 191, 241, 242, 281, 282 removing memory resources, 195, 244, 284 shutdown, 160 shutting down, 160 shutting down all, 161 states, 140 versions, 44, 45 Virtual Partitions product benefit
