Installing and Managing HP-UX Virtual Partitions (vPars) Seventh Edition Manufacturing Part Number: T1335-90041 October 2005 United States © Copyright 2005 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. Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service.
Contents 1. Introduction Information on This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How This Book is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to Get the Latest Version of This Document . . .
Contents (PA-RISC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Choosing the Boot and Lan Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Autoboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Partition Plan. . . . . . . . . . . . . . . . .
Contents EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Monitor: Booting the vPars Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Monitor: Accessing the Monitor Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Boot||Shut: Single-User Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot||Shut: Other Boot Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overriding Quorum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Memory: Allocation Concepts and Notes (vPars A.04, A.03 and earlier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU (vPars A.04, A.03 and earlier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU: Boot Processor and Dynamic CPU Definitions (vPars A.04) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents (vPars A.04 and iCAP B.07). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purchasing Licenses for iCAP CPUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating and Deactivating CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning and Unassigning CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Adding a Virtual Partition to the Primary-admin Virtual Partition List . . . . . . . . . . . . . . . . . . . . . Deleting A Virtual Partition To The Primary-admin Virtual Partition List . . . . . . . . . . . . . . . . . . . Listing the Virtual Partitions in the Primary-admin Virtual Partition List. . . . . . . . . . . . . . . . . . . Changing the Security Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 12
Tables Table 2-1. vPars Version Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Table 3-1. Hardware Path Format Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Table 5-1. vparconfig versus parconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Table 5-2. Virtual Partition States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 14
1 Introduction This chapter covers: • Information on This Document • What Is vPars? • Why Use vPars? • Supported Environments • Product Interaction • Ordering vPars Chapter 1 15
Introduction Information on This Document 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). How This Book is Organized Chapter 1 covers a brief introduction to vPars and its interaction with other HP-UX products. Chapter 2 covers conceptual material about vPars and its components. Chapter 3 covers planning your vPars environment. Chapter 4 covers vPars installation.
Introduction What Is vPars? What Is vPars? The vPars (Virtual Partitions) product allows you to run multiple instances of HP-UX simultaneously on one hard partition by dividing the 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 HP-UX instance is isolated from all other instances, vPars provides application and OS (Operating System) 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. A 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? Why Use vPars? The following explains some of the advantages of using vPars: vPars Increases Server Utilization and Isolates OS and Application Faults In certain environments one entire server is dedicated to a single application. When the demand for that application is not at peak, such as during non-business hours, the server is underutilized. If many servers are configured this way, you have many servers that are being underutilized.
Introduction Supported Environments Supported Environments Hardware and Firmware This information on supported hardware and required firmware versions 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 NOTE Updating Firmware on the rp5470/L3000 and rp7400/N4000 Installing firmware patches on these servers requires additional steps in a vPars environment.
Introduction HP Product Interaction HP Product Interaction • nPartitions (vPars A.03.xx and earlier) Parmgr Requirements: For information on which version of Partition Manager (parmgr) is required with vPars, please see the document Read Before Installing HP-UX Virtual Partitions available at http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions. For information on installing Partition Manager, see “Installing and Removing vPars-related Bundles” on page 64.
Introduction HP Product Interaction However, on a Superdome, the first element of the hardware path is the cell number. So, if the cell number is 4, the ioscan output shows: 4/0/0 • ba Local PCI Bus Adapter (782) PCI OL* (On-Line Addition and Replacement) Except for the function stated below, OL* for PCI slots works the same on a vPars server as it does on a non-vPars server. Note that you can execute PCI OL* functions only on the PCI slots that the virtual partition owns.
Introduction HP Product Interaction • 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. However, 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 • Ignite-UX and other Curses Applications On the virtual console, when using applications that use curses, such as the terminal versions of Ignite-UX and SAM, do not press Ctrl-A to toggle to the console display window of another virtual partition while you are still within the curses application. This is especially applicable when you are using vparboot -I and the Ignite-UX application to install vPars. For more information on curses, see the curses_intro (3X) manpage.
Introduction HP Product Interaction • SCSI Initiator ID (PA-RISC only) For vPars A.03.xx and earlier: the SCSI Initiator ID is the ID of the SCSI controller. Although you can display and set SCSI parameters for the SCSI controller at the BCH prompt, on a vPars server, you can also set these values from the HP-UX shell of a virtual partition using the vPars command vparutil. For more information, see the vparutil (1M) manpage. For vPars A.04.xx and later: please use the mptutil command.
Introduction HP Product Interaction • intctl command The intctl command is a HP-UX tool that allows you to manage IO interrupts among the active processors. It can be installed from the HP-UX Software Pack but should be used only by advanced administrators for performance tuning. If you are managing interrupts on vPars systems, please see the section “Managing IO Interrupts (vPars A.04, A.03 and earlier)” on page 194.
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 • Integrity Differences Relative to PA-RISC • Virtual Consoles • Security • Differences in Different Versions of vPars 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 separate OS instances.
How vPars and its Components Work Partitioning Using vPars Once a virtual partition is launched, the Monitor transfers ownership of the hardware to the virtual partition. At that point the Monitor is not involved in accessing IO hardware, physical memory, or process to processor cycles: the individual HP-UX instances have complete ownership of their respective hardware resources. This allows each partition to run at full speed.
How vPars and its Components Work Boot Sequence Boot Sequence NOTE This section describes a manual boot sequence to help explain how vPars impacts the boot process, but you can continue to use an autoboot sequence to boot all partitions. See “Boot||Shut: Autoboot” on page 141. Boot Sequence: Quick Reference On a server without vPars, a simplified boot sequence is: PA-RISC Integrity 1. ISL (Initial System Loader) 1. EFI 2. hpux (secondary system loader) 2. hpux.efi 3. /stand/vmunix (kernel) 3.
How vPars and its Components Work Boot Sequence The Monitor loads the partition database (the default is /stand/vpdb) from the same disk that /stand/vpmon was booted. The Monitor internally creates (but does not boot) each virtual partition according to the resource assignments in the partition database. Next, the vPars Monitor runs in interactive mode (when no options to /stand/vpmon are given) with a command line interface.
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 Also, while running in vPars mode, the EFI device path of a boot device, specifically the Monitor boot device, can be changed when the boot device is reformatted due to an installation (either cold or Ignite-UX). The associated EFI boot path is updated to use the new EFI device path. However, firmware-saved EFI boot path options are not updated.
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 PA-RISC. Booting • Modes On Integrity platforms, you have to set the mode (vPars or nPars) to be able to boot the nPartition into standalone (nPars) or the vPars environment (vPars).
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 IO is sent to its vcn (Virtual CoNsole) driver. From the vcn driver, the console IO is sent to the Monitor.
How vPars and its Components Work Virtual Consoles It is not deterministic which virtual partition will be active with the physical console when multiple virtual partitions are booted. • Switchover Pause with Shutting Down When the virtual partition that owns the hardware console port is shut down, there will be a pause of console output (the system is not hung) as console IO management switches over from the virtual partition to the vPars Monitor. Console output resumes automatically after the pause.
How vPars and its Components Work Virtual Consoles nPartition Logs On an nPartition server running vPars, all virtual partitions within an nPartition share the same console device: the nPartition’s console. Thus, an nPartition’s console log contains console IO for multiple virtual partitions. Further, since the vPars Monitor interface is displayed and accessed through the nPartition’s console, vPars Monitor output is also recorded in the nPartition’s console log. There is only one Monitor per nPartition.
How vPars and its Components Work Security Security You should be aware of the following security concerns: • The vPars commands (as described in “Monitor and Shell Commands” on page 91) 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 on one partition can affect another virtual partition by targeting the virtual partition in a vPars command.
How vPars and its Components Work Differences in Different Versions of vPars Differences in Different Versions of vPars Table 2-1 vPars Version Information Table Category Product Number A.03 T1335AC Obtaining vPars Bits Media Format A.04 on PA-RISC A.04 on Integrity T1335BC Order at HP Software Depot (http://www.hp.com/go/softwaredepot) CD Obtaining vPars Documents DVD Download from HP Documentation Site (http://docs.hp.
How vPars and its Components Work Differences in Different Versions of vPars Table 2-1 vPars Version Information Table (Continued) Category Supported IO and LAN cards A.
How vPars and its Components Work Differences in Different Versions of vPars 44 Chapter 2
3 Planning Your System for Virtual Partitions This chapter covers • Example System • Planning Your Virtual Partitions • Hardware Path Formats Chapter 3 45
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. On a non-nPartitionable system, if the ioscan output shows 41 processor Processor 45 processor Processor where 41 and 45 are the hardware paths of two CPUs.
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 (PA-RISC Only) 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 • RAM (sufficient for HP-UX and the applications in that partition) • 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.
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 For our example servers, the ioscan output shows the LBAs as: keira#ioscan -kC lba 0/0/0 0/0/1 0/0/2 0/0/4 0/0/6 0/0/8 0/0/10 0/0/12 0/0/14 1/0/0 1/0/1 1/0/2 1/0/4 1/0/6 1/0/8 1/0/10 1/0/12 1/0/14 ba ba ba ba ba ba ba ba ba ba ba ba ba ba ba ba ba ba Local Local Local Local Local Local Local Local Local Local Local Local Local Local Local Local Local Local PCI Bus Adapter (782) PCI-X Bus Adapter (783) PCI-X Bus Adapter (783) PCI
Planning Your System for Virtual Partitions Planning Your Virtual Partitions Ensuring the Hardware Console Port Is Owned by the First Virtual Partition (PA-RISC) 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: console port 0.0.4.0 1/0/0/0/1 LBA 0.0 1.0.0 partition winona1 keira1 console port owned by winona1 owned by keira1 When we create the virtual partitions, we will create winona1 and keira1 first.
Planning Your System for Virtual Partitions Planning Your Virtual Partitions 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 console port (PA-RISC Only) Autoboot Chapter 3 owned by winona1 AUTO AUTO AUTO 59
Planning Your System for Virtual Partitions New Hardware Path Formats (A.02.02) New Hardware Path Formats (A.02.02) Beginning with vPars version A.02.02, the way to specify hardware paths has changed. This was done so that older vPars configuration databases remain compatible with additional hardware that is being supported. For example, given a path where its sequential digits are 4 0 1 0 0 0 0, it is not possible to determine whether this path means a device at "4/0/1/0/0.0.
Planning Your System for Virtual Partitions New Hardware Path Formats (A.02.02) In the former case above, the ioscan output for a combo-card (combination of SCSI and LAN on a single PCI card) may show: disk 0 12/0/8/0/0/4/0.0.0 ... SEAGATE ST39103LC Then, the vPars command would be # vparmodify -p winona2 -a io:12/0/8/0/0/4/0.0.0 Note that this path of 12/0/8/0/0/4/0.0.0 becomes correctly padded to 12.0.8.0.0.4.0.0.0.0.0.0.0, in accordance to the table above.
Planning Your System for Virtual Partitions New Hardware Path Formats (A.02.
4 Installing, Updating, or Removing vPars This chapter covers • Installing vPars • Updating vPars to the Latest Version of vPars • Removing vPars CAUTION Hardware Paths on the vPars Command Line — Hardware Path Differences Between Cellular (nPartitionable) and Non-cellular Systems The hardware paths for some example system are formatted for non-cellular systems. For cellular systems, their hardware paths contain the prefix of the cell number.
Installing, Updating, or Removing 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: CAUTION Bundle Name Description T1335BC vPars A.04.xx and later for HP-UX 11i v2 Feature11i Required vPars enablement patches for vPars A.04.xx and later. This bundle can be obtained from the 11i v2 May 2005 Update OE DVD.
Installing, Updating, or Removing vPars Patches # swinstall -s /cdrom B6826AA To remove the Partition Manager product: # /usr/sbin/swremove PartitionManager Note that the PartitionManager product can be removed only after the vPars product is removed from a virtual partition. VPARMGR (vPars A.03.xx and earlier) The vPars GUI (vparmgr) is not automatically installed when vPars is installed.
Installing, Updating, or Removing 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. This version information has been moved to e the HP-UX Virtual Partitions Ordering and Configuration Guide.
Installing, Updating, or Removing vPars Setting Up the Ignite-UX Server 3. Enter the keyword vPars 4. You will see Ignite-UX & vPars Cookbook 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 Setting Up the Ignite-UX Server • the network interface card of the target virtual partition is able to connect to the Ignite-UX server.
Installing, Updating, or Removing vPars Setting Up the Ignite-UX Server Like on PA-RISC, only the vPars shell command vparboot can be used to boot subsequent virtual partition for installation (or recovery); the vPars Monitor command vparload cannot do this. Thus, you need at least one virtual partition successfully booted to use the vparboot command.
Installing, Updating, or Removing vPars Other Considerations Other Considerations This section covers: • “Notes on Installing Server Firmware” on page 70 • “Setting the GSP Terminal Type” on page 71 • “Increase in Size of /stand File System” on page 72 • “VxFS (Veritas File System) (vPars A.03.xx)” on page 72 Notes on Installing Server Firmware Installing Firmware for the systems running vPars must be done in a standalone (PA-RISC) or nPars (Integrity) mode.
Installing, Updating, or Removing vPars Other Considerations • Mid-range Servers Once in standalone or nPars mode, install the server firmware as you normally do. • Superdomes (PA-RISC and Integrity) Upgrading firmware on a Superdome must be performed by Hewlett-Packard qualified service personnel only. Please contact your local HP Support Representative to schedule a convenient time for the firmware upgrade service.
Installing, Updating, or Removing vPars Other Considerations 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. Increase in Size of /stand File System Due to the vPars files that will exist in /stand, you should increase by 100 MB the size of the /stand file system that you normally create. VxFS (Veritas File System) (vPars A.03.
Installing, Updating, or Removing vPars Related Information Related Information For information on the installation of HP-UX, see the manual "HP-UX 11i Installation and Update Guide". For information on swinstall and software depots, see the manual "Software Distributor Administration Guide for HP-UX". For information on using the vPars commands, see the following sections in the chapter Monitor and Shell Commands: • “Managing: Creating a Virtual Partition” on page 123.
Installing, Updating, or Removing vPars Installing vPars Using Ignite-UX (PA-RISC) Installing vPars Using Ignite-UX (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. Using the Ignite-UX server, install HP-UX, desired patches, the Quality Pack bundle, the vPars bundle, and the desired vPars-related bundles onto the disk that will be the boot disk of the first virtual partition.
Installing, Updating, or Removing vPars Installing vPars Using Ignite-UX (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 Installing vPars Using Ignite-UX (Integrity) Installing vPars Using Ignite-UX (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. For more information, see the HP-UX Virtual Partitions Ordering and Configuration Guide.
Installing, Updating, or Removing vPars Installing vPars Using Ignite-UX (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 Installing vPars Using Ignite-UX (Integrity) # vparboot -p -I For our example, if the target partition is keira2, execute the following command from keira1: # vparboot -p keira2 -I You will see messages similar to the following: keira2 loaded b. press Ctrl-A until you see the console of the target partition. [keira2] c. Select a MAC address from the list to perform a LAN boot.
Installing, Updating, or Removing vPars Installing vPars Using Software Distributor (PA-RISC or Integrity) Installing vPars Using Software Distributor (PA-RISC or Integrity) 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 Installing vPars Using Software Distributor (PA-RISC or Integrity) 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 Updating from vPars A.03.xx to A.04.xx with Update-UX (PA-RISC only) Updating from vPars A.03.xx to A.04.xx with Update-UX (PA-RISC only) 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 Updating from vPars A.03.xx to A.04.xx with Update-UX (PA-RISC only) keira2 keira3 Dyn,Manl,Nsr /stand/vmunix Dyn,Auto,Nsr /stand/vmunix Up Up 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 Updating from vPars A.03.xx to A.04.xx with Update-UX (PA-RISC only) 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 Updating from vPars A.03.xx to A.04.xx with Update-UX (PA-RISC only) 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 Updating to vPars A.03.XX (PA-RISC only) Updating to vPars A.03.XX (PA-RISC only) 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: 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. 2. Shut down all the virtual partitions. 3. Reboot the server into standalone mode. This consists of the following: a.
Installing, Updating, or Removing 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 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. If needed, interrupt the boot sequence at the BCH> and boot /stand/vmunix instead of /stand/vpmon.
Installing, Updating, or Removing 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 rp7410 to rp7420 upgrade, the rp8400 to rp8420 upgrade, or Superdome upgrade, the hardware paths will change. The IO device paths are in the format cell/sba/lba/device/function.target.lun When changing from the PCI to PCI-X backplane, the device in the hardware paths will change from 0 to 1.
Installing, Updating, or Removing 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 Removing the vPars Product 90 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) ... 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) 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. parconfig is a built-in EFI shell command, so you can execute parconfig from the EFI shell.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) 2. Set the mode to vPars so that you can boot the nPartition into the vPars environment. # vparenv -m vPars 3. Reboot the nPartition into the vPars environment and load the first virtual partition. 4. From the first virtual partition, use vparboot -I to install the OE and vPars software onto the remaining boot disks of the remaining virtual partitions.
Monitor and Shell Commands Modes: Switching between nPars and vPars Modes (Integrity only) • On an Integrity system which has vPars software installed but does not have the correct firmware version installed, you will see the following behavior depending upon the mode of operation: — If the current mode is nPars, booting vmunix works as expected. Booting vpmon exits with an unsupported environment message.
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 93. 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 101). • 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 133). • 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 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 16KB of information in a circular log buffer. The information is displayed in chronological order. • ls [-alniFH] [directory] lists the contents of directory. This command is similar to the Unix ls command. directory must be on a HFS file system.
Monitor and Shell Commands Monitor: Using Monitor Commands • vparinfo [partition_name] This command is for HP internal use only. when no partition_name is given, vparinfo displays all unassigned resources and the names of all existing virtual partitions; when partition_name is given, vparinfo displays the resources assigned to partition_name.
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.
Monitor and Shell Commands Commands: vPars Commands Logging 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. The logging of the command will not be duplicated to the target syslog file (the syslog file of the target virtual partition.
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) vparstatus: summary information To see summary information on all the virtual partitions, use vparstatus with no options: • vPars A.03.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: verbose information To see verbose (-v) information: • 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) 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): Chapter 5 128 115
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: available resources To see the available resources (-A) (resources not assigned to any virtual partition): • 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.2 [Unbound memory (Base /Range)]: (bytes) (MB) [Available memory (MB)]: 256 • 0x40000000/256 A.04.
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 filesystem path of the Monitor, and the vPars database file that is being used by the Monitor: • vPars A.03.02: # vparstatus -m Console path: 0.0.2.0 Monitor Boot disk path: 0.0.1.
Monitor and Shell Commands Commands: Displaying Monitor and Resource Information (vparstatus) vparstatus: migrating CPUs 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: • winona1# vparstatus . . .
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: # 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: CPU information on vPars A.04 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-3 possible commands to arrive at vparstatus output vparstatus output (final) 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:12 -a cpu::4 (min==1, max==12, total==4 4 non-CLPs are reserved by
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 winona1# vparcreate -p winona2 -a cpu::3 -a cpu:::2:4 -a cpu:41 -a cpu:45 –a mem::1280 –a io:0.8 -a io:1.10 -a io:0.8.0.0.5.0:boot 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.
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 IO Resources” on page 155.
Monitor and Shell Commands Managing: Performing nPartition Operations Managing: Performing nPartition Operations You can perform nPartition operations in a vPars environment, keeping in mind the following: • If you make an nPartition change where a Reboot for Reconfiguration is required, all the virtual partitions within the nPartition need to be shutdown and the Monitor rebooted in order for the reconfiguration to take effect.
Monitor and Shell Commands Managing: Performing nPartition Operations Transition to run-level0 is complete. Executing "/sbin/reboot-R ". Note: If this is a partitionable system, the requested reconfiguration will not take place until all the virtual partitions on this hard partition are shut down and the virtual partition Monitor is rebooted. Shutdown at 16:19 (in 0 minutes) At this point, all virtual partitions have been shut down. The Monitor will reboot automatically.
Monitor and Shell Commands Managing: Performing nPartition Operations 2. On the console, you will arrive at the MON> prompt. From the Monitor prompt, press Ctrl-B to enter into the GSP: MON> ^B GSP MAIN MENU: CO: Consoles VFP: Virtual Front Panel CM: Command Menu CL: Console Logs SL: Show chassis Logs HE: Help X: Exit Connection 3. At the GSP prompt, enter into the Command Menu GSP> cm Enter HE to get a list of available commands GSP:CM> 4.
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.
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. 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 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 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. On a non-vPars server, you do this by using the -is option at the ISL prompt: ISL> hpux –is On a vPars server, you can boot a virtual partition into single-user mode either at the Monitor prompt or at the HP-UX shell prompt of a running partition.
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 144), you can boot a partition using other boot options.
Monitor and Shell Commands Boot||Shut: Other Boot Modes 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" NOTE Specifying the boot options from the command line only affects the current boot.
Monitor and Shell Commands Boot||Shut: Other Boot Modes Changing the LVM Boot Device Hardware Path for a Virtual Partition Example Below are the steps to move the root disk of a single virtual partition. Verification These instructions require that the virtual partition be constrained in the following way: the logical volume used for the primary swap device must be on the boot device; in other words, boot and swap must be on the same disk device. This can be verified by the following steps: Step 1.
Monitor and Shell Commands Boot||Shut: Other Boot Modes partition_name is the target virtual partition new_path is the new hardware path of the disk old_path is the old hardware path of the disk Step 2. Verify the attributes vparstatus -v -p partition_name Boot into LVM maintenance mode Step 1. Boot the target virtual partition into LVM maintenance mode. For example, at the Monitor prompt: MON> vparload -o -lm -p partition_name LVM maintenance mode steps Step 1.
Monitor and Shell Commands Boot||Shut: Other Boot Modes Step 7. Verify that the hardware path for the boot device matches the primary boot path. lvlnboot -v /dev/vg00 Step 8. If the hardware path has not changed to the primary boot path, change it by running lvlnboot with the recovery (-R) option. This step is normally not necessary. lvlnboot -R /dev/vg00 Step 9. Reboot the target virtual partition.
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 Using an Alternate Partition Database File 154 Chapter 5
6 CPU, Memory, and IO Resources Managing Hardware Resources • IO Allocation (Adding or Deleting IO Resources) • Memory Allocation (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 6 Some examples in this chapter may use a non-nPartitionable system where there is no cell in the hardware path.
CPU, Memory, and IO Resources IO: Concepts IO: Concepts Acronyms LBA Local Bus Adapter SBA System Bus Adapter System, Cells, SBA, LBA, Devices and Relationships On a server, an IO device communicates to the system through the LBA and SBA. The path looks like Figure 6-1 System to IO Device Relationship This corresponds to the ioscan hardware path output for an IO device of sba/lba/ ... /device. A LBA actually owns all the devices attached to it.
CPU, Memory, and IO Resources IO: Concepts 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 IO Resources IO: Concepts With the addition of cells (an nPartitionable server), there are more SBAs, but IO assignments remain at the LBA level: Figure 6-6 158 vPars allocates at LBA level not at cell level Chapter 6
CPU, Memory, and IO Resources IO: Adding or Deleting LBAs (vPars A.04, A.03 and earlier) IO: Adding or Deleting LBAs (vPars A.04, A.03 and earlier) IO Syntax in Brief the basic core syntax for adding or deleting IO resources is -a|d io:hardware_path where a d hardware_path is adding is deleting is the hardware path of the IO 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 IO Resources IO: Allocation Notes (vPars A.04, A.03 and earlier) IO: Allocation Notes (vPars A.04, A.03 and earlier) When planning or performing IO allocation, note the following: • An LBA can be assigned to at most one virtual partition at any given time. When you are planning your IO to virtual partition assignments, note that only one virtual partition may own any hardware at or below the LBA (Local Bus Adapter) level.
CPU, Memory, and IO Resources IO: Allocation Notes (vPars A.04, A.03 and earlier) 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 IO 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).
CPU, Memory, and IO Resources Memory: Concepts and Functionality (vPars A.04, A.03 and earlier) Memory: Concepts and Functionality (vPars A.04, A.03 and earlier) Acronyms ILM Interleaved Memory. (vPars A.04.xx, A.03.xx, A.02.xx) • • 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. (A.04.
CPU, Memory, and IO Resources Memory: Assigning By Size (ILM) (vPars A.04, A.03 and earlier) Memory: Assigning By Size (ILM) (vPars A.04, A.03 and earlier) 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 and CLM memory.
CPU, Memory, and IO Resources Memory: Configuring CLM for an nPartition in Brief (vPars A.04) Memory: Configuring CLM for an nPartition in Brief (vPars A.04) You can assign only available CLM to a virtual partition. However, by nPartition system default, nPartition cells are configured as 100% ILM and 0% CLM. However, ILM memory can be re-configured to be CLM using the parmodify command. For complete information on CLM and configuring cells and nPartitions, see the nPartition’s Guide.
CPU, Memory, and IO Resources Memory: Configuring CLM for an nPartition in Brief (vPars A.04) • 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.
CPU, Memory, and IO Resources Memory: Assigning CLM (vPars A.04) Memory: Assigning CLM (vPars A.04) Once CLM is configured (see “Memory: Configuring CLM for an nPartition in Brief (vPars A.
CPU, Memory, and IO Resources Memory: Specifying Address Range (vPars A.04, A.03 and earlier) Memory: Specifying Address Range (vPars A.04, A.03 and earlier) Within the already allocated memory sizes, you can specify the memory address ranges using the mem:::base:range syntax.
CPU, Memory, and IO Resources Memory: Specifying Address Range (vPars A.04, A.03 and earlier) 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 IO Resources Memory: Setting Granularity Values (vPars A.04) Memory: Setting Granularity Values (vPars A.04) 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. If you are using a vPars database created using vPars A.04.xx and later, the default granularity is 128 MB for ILM and 128 MB for CLM.
CPU, Memory, and IO Resources Memory: Setting Granularity Values (vPars A.04) Setting the Granularity Values on Integrity There are two commands that can set the granularity values. Both are available at the HP-UX shell level and use the -g option: 1. vparenv -g ... writes the granularity values to the firmware only. Note that vparenv is applicable only on Integrity. 2. vparcreate -g ...
CPU, Memory, and IO Resources Memory: Setting Granularity Values (vPars A.04) # shutdown -r /* reboot the system */ vparcreate without the :y option and vparenv The following scenario is where you would want to use vparcreate with the -g option but without the :y specification. It also shows where you need to use vparenv to set the granularity value in the firmware. Note that this scenario would only occur on Integrity systems. 1.
CPU, Memory, and IO Resources Memory: Setting Granularity Values (vPars A.04) Granularity Cautions (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 IO Resources Memory: Setting Granularity Values (vPars A.04) • (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. granularity portion of vparresources (5) Granularity Memory is normally assigned to vPars in units called granules. Exceptions are described below. The granule values for CLM and ILM can be different.
CPU, Memory, and IO Resources Memory: Setting Granularity Values (vPars A.04) + Recommendations for ILM and CLM granularity specifications: On PA-RISC platforms, each vPar needs ILM below 2 GB to load and launch its kernel. However, portions of the first granule (starting at address 0) are used for the Monitor's code and data, therefore will not be used for the kernel. Hence, excluding the first granule, there should be at least one granule below 2 GB for each partition.
CPU, Memory, and IO Resources Memory: Allocation Concepts and Notes (vPars A.04, A.03 and earlier) Memory: Allocation Concepts and Notes (vPars A.04, A.03 and earlier) • 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. • (vPars A.03.xx and earlier) Memory is allocated in multiples of 64 MB.
CPU, Memory, and IO Resources CPU (vPars A.04, A.03 and earlier) CPU (vPars A.04, A.03 and earlier) CPU migration refers to adding CPUs to and deleting CPUs from a virtual partition. Dynamic CPU migration refers to migrating CPUs while the target virtual partition is running. vPars allows the assignment of most CPUs while the virtual partitions are running. For vPars A.04 and later, the two types of CPUs are Boot Processor and dynamic CPUs.
CPU, Memory, and IO Resources CPU: Boot Processor and Dynamic CPU Definitions (vPars A.04) CPU: Boot Processor and Dynamic CPU Definitions (vPars A.04) 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 processors: 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 IO Resources CPU: Specifying Min and Max Limits (vPars A.04) CPU: Specifying Min and Max Limits (vPars A.04) The syntax to specify min and max CPUs assigned to a virtual partition remains the same.
CPU, Memory, and IO Resources CPU: Adding and Deleting by Total (vPars A.04) CPU: Adding and Deleting by Total (vPars A.04) 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 IO Resources CPU: Adding and Deleting by Total (vPars A.
CPU, Memory, and IO Resources CPU: Adding or Deleting by CLP (Cell Local Processor) (vPars A.04) CPU: Adding or Deleting by CLP (Cell Local Processor) (vPars A.04) 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 IO Resources CPU: Adding or Deleting by Hardware Path (vPars A.04) CPU: Adding or Deleting by Hardware Path (vPars A.04) The syntax for specifying by hardware path is -[a|d] cpu:hw_path where is adding is deleting is the hw_path (you can find the hardware path using ioscan or vparstatus -v) a d hw_path NOTE The target virtual partition can be up or down when specifying by hardware path.
CPU, Memory, and IO Resources CPU: A.04 Syntax, Rules, and Notes (vPars A.04) CPU: A.04 Syntax, Rules, and Notes (vPars A.04) vparstatus • When a virtual partition is down, vparstatus does not show any processor 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.
CPU, Memory, and IO Resources CPU: A.04 Syntax, Rules, and Notes (vPars A.04) Comparing A.03 and A.04 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 also summarizes the A.04.xx syntax and rules Table 6-1 CPU Syntax from A.03 to A.04 vPars A.03 Syntax => vPars A.
CPU, Memory, and IO Resources CPU: A.04 Syntax, Rules, and Notes (vPars A.04) vPars CPU Rules (vPars A.04) Table 6-2 CPU Rules for A.03 -> A.04 vPars A.03 Rules => vPars A.
CPU, Memory, and IO Resources CPU: A.04 Syntax, Rules, and Notes (vPars A.04) Table 6-2 CPU Rules for A.03 -> A.04 (Continued) vPars A.03 Rules => vPars A.
CPU, Memory, and IO Resources CPU: A.04 Syntax, Rules, and Notes (vPars A.04) Table 6-2 CPU Rules for A.03 -> A.04 (Continued) vPars A.03 Rules => vPars A.
CPU, Memory, and IO Resources CPU: Bound and Unbound (vPars A.03 and earlier) CPU: Bound and Unbound (vPars A.03 and earlier) Definitions With vPars, there are two types of CPUs: bound and unbound. A bound CPU is a CPU that is assigned to and handles IO interrupts for a virtual partition. Every virtual partition must have at least one bound CPU to handle its IO interrupts.
CPU, Memory, and IO Resources Adding and Removing Bound CPUs (vPars A.03 and earlier) Adding and Removing Bound CPUs (vPars A.03 and earlier) 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 IO Resources Adding a CPU as a Bound CPU (vPars A.03 and earlier) Adding a CPU as a Bound CPU (vPars A.03 and earlier) 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 IO Resources Removing a Bound CPU (vPars A.03 and earlier) Removing a Bound CPU (vPars A.03 and earlier) To remove a bound CPU from a virtual partition, use the vparmodify command to modify the total and min parameters for the virtual partition.
CPU, Memory, and IO Resources Adding, Removing, and Migrating Unbound CPUs (vPars A.03 and earlier) Adding, Removing, and Migrating Unbound CPUs (vPars A.03 and earlier) 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 IO Resources Adding, Removing, and Migrating Unbound CPUs (vPars A.03 and earlier) If you do not know which CPUs are bound CPUs and which are unbound CPUs, use the vparstatus command. See “Commands: Displaying Monitor and Resource Information (vparstatus)” on page 112 and the vparstatus (1M) manpage. • For issues with using vparmodify, see the vparmodify (1M) manpage. For required partition states, see the vparresources (5) manpage.
CPU, Memory, and IO Resources Managing IO Interrupts (vPars A.04, A.03 and earlier) Managing IO Interrupts (vPars A.04, A.03 and earlier) This section described information you need if you are managing IO interrupts on a vPars-enabled system. Note that migrating interrupts should only be done by advance administrators for performance tuning. intctl command The intctl command is a HP-UX tool that allows you to manage IO interrupts among active processors.
CPU, Memory, and IO Resources CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04 and iCAP B.07) CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04 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 IO Resources CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04 and iCAP B.07) While in the vPars environment or in vPars mode, the total number of CPUs assigned to the virtual partitions cannot exceed the current Intended Active number. This is true regardless of whether the virtual partitions are up or down. If you encounter this situation, you may need to increase the Intended Active using icod_modify -a to activate and assign CPUs to your virtual partition.
CPU, Memory, and IO Resources CPU: Dual-Core (vPars A.04, A.03) CPU: Dual-Core (vPars A.04, A.03) With the PA-8800s and other dual-cores, 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 partition refers to assigning one sibling CPU to one partition and assigning the other sibling CPU to a different virtual partition.
CPU, Memory, and IO Resources CPU: Dual-Core (vPars A.04, A.03) Figure 6-7 using parmgr to determine dual-cores Determining Sibling CPUs Once you have determined that you have a dual-core system, the siblings have adjacent hardware paths.
CPU, Memory, and IO Resources CPU: Dual-Core (vPars A.04, A.
CPU, Memory, and IO Resources CPU: CPU Monitor (formerly known as LPMC Monitor) (vPars A.04, A.03 and earlier) CPU: CPU Monitor (formerly known as LPMC Monitor) (vPars A.04, A.03 and earlier) 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 processors on the system.
CPU, Memory, and IO Resources CPU: CPU Monitor (formerly known as LPMC Monitor) (vPars A.04, A.03 and earlier) • There is a deconfigured CPU which has been reserved for the partition as part of a CLP request (cell:cell_ID:cpu:num) and there are no free CLP in that cell. To correct this, you can make available CPUs from that cell by deleting the CPUs that are part of this cell from other partitions or delete the CPUs from the cell in this partition. (A.
CPU, Memory, and IO Resources Managing IO and Memory Resources with only One Virtual Partition Managing IO and Memory Resources with only One Virtual Partition Adding and deleting IO and memory resources to and from a virtual partition requires the virtual partition to be in the down state. However, if you are running only one virtual partition, you will not have an OS instance from which to run the vparmodify commands to add or delete the IO and memory resources.
7 Crash Processing and Recovery Crashing and Recovery Processes • Crash Processing • Network and Tape Recovery • Expert Recovery Chapter 7 203
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 Or if the kernel configuration used in the last boot is different from the current kernel configuration, use the -c option. For example, if the saved kernel configuration is named kc.custom, the command is # kconfig -c kc.custom crashconfig For more information on using the kconfig command, see the manpages kconfig (5) and kconfig (1M) Step 2.
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. For information on performing a recovery using: • • • • • • • make_net_recovery within a vPars-environment, see “Using make_net_recovery within a vPars Environment (vPars A.04, A.03 and earlier)” on page 208 make_tape_recovery outside of a vPars-environment, see “Using make_tape_recovery Outside of a vPars Environment (vPars A.04, A.03.
Crash Processing and Recovery Network and Tape Recovery Using make_net_recovery within a vPars Environment (vPars A.04, A.03 and earlier) 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.
Crash Processing and Recovery Network and Tape Recovery BCH> bo lan.ww.xx.yy.zz install interact with IPL? N 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.
Crash Processing and Recovery Network and Tape Recovery Using make_tape_recovery Outside of a vPars Environment (vPars A.04, A.03.02 and earlier) The creation of make_tape_recovery tapes is supported on vPars-enabled servers using vPars A.02.03 or later. However, 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.
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 (vPars A.04, A.03.02 and earlier)” on page 214.
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 (vPars A.04, A.03.02 and earlier) A dual-media boot allows you to boot the target partition using the Ignite-UX server and then recover using the tape device. 1. If needed, make sure the target virtual partition is in the down state. For example, if it is up, shutdown the virtual partition: winona2# shutdown -hy 0 2. Boot the virtual partition to the Ignite-UX server.
Crash Processing and Recovery Network and Tape Recovery Using make_tape_recovery within a vPars-environment (vPars A.03.03) Beginning with vPars A.03.03, 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 135. • 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 141.
8 Primary-Admin vPars Security (vPars A.03.03) This chapter discusses the concepts and tasks on using the Primary-Admin vPars Security feature. At this time, this feature is available only on vPars A.03.xx and later, beginning with vPars A.03.03; it is not available yet on vPars A.04.xx. Additionally, for this security feature to work, all the virtual partitions must be running the same version of vPars. NOTE Applying RBAC to vPars A.04.
Primary-Admin vPars Security (vPars A.03.03) Synopsis Synopsis The Primary-Admin vPars Security (PAVS) feature restricts the usage of certain vPars commands such that only those commands can only be successfully executed from specific virtual partitions. The vPars commands that are restricted are those that can alter other virtual partitions, such as vparmodify or vparreset.
Primary-Admin vPars Security (vPars A.03.03) Terms and Definitions Because this command affects another virtual partition (winona2), if the local virtual partition winona1 is a secondary-admin virtual partition, the command will not be successful. primary-admin virtual partition list This is the list of virtual partitions that are currently set as primary virtual partitions. If a virtual partition is in this list or added to this list, it becomes a primary virtual partition.
Primary-Admin vPars Security (vPars A.03.
Primary-Admin vPars Security (vPars A.03.03) # vparadmin -a|-d partition_name Adds or deletes a virtual partition to or from the primary-admin virtual partition list. No security 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 primary-admin virtual partition list.
Primary-Admin vPars Security (vPars A.03.03) Persistence across Monitor Reboots Persistence across Monitor Reboots If the security mode is not changed from ON to OFF across Monitor reboots and the specific conditions are met (see below), the security mode will remain and the virtual partitions designated as primary-admin virtual partitions will remain as primary-admin virtual partitions.
Primary-Admin vPars Security (vPars A.03.03) vPars Commands vPars Commands When the security mode is ON, the vPars security 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 primary-admin virtual partition list. When you execute the command from a secondary-admin virtual partition, if the command alters another virtual partition, it will not be allowed.
Primary-Admin vPars Security (vPars A.03.03) Example Monitor Scenario (monadmin) Example Monitor Scenario (monadmin) Below describes examples that include (from the Monitor): • • turning on the security feature (which will include setting the password) adding virtual partitions to the primary-admin virtual partition list For this section, let’s assume we have the virtual partitions winona1, winona2, and winona3.
Primary-Admin vPars Security (vPars A.03.
Primary-Admin vPars Security (vPars A.03.03) Example HP-UX Shell Scenario (vparadmin) winona1# vparadmin -d winona2 Password: Virtual partition winona2 deleted from Primary-Admin vPars list. Listing the Virtual Partitions in the Primary-admin Virtual Partition List We can verify that winona2 has been removed from the primary-admin virtual partition list. This can be performed from any partition.
9 Virtual Partition Manager (A.03.xx and earlier) 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 and earlier) 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 and earlier) About the Virtual Partition Manager (vparmgr) -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.
A LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) This section contains a simplified PCI IO block diagrams for the rp5470/L3000, rp7400/N4000, and the nPartitionable servers. These diagrams can be used to help determine which LBAs correspond to which physical IO slots. These were created due the incorrect or inaccessible PA-RISC documentation. For Integrity servers, please see your server manual.
LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) rp5470/L3000 IO Block Diagram rp5470/L3000 IO Block Diagram Figure A-1 232 Appendix A
LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) rp7400/N4000 IO Block Diagram rp7400/N4000 IO Block Diagram Figure A-2 Appendix A 233
LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) rp7410 and rp7405 PCI IO Block Diagram rp7410 and rp7405 PCI IO Block Diagram Figure A-3 234 Appendix A
LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) rp8400 PCI IO Block Diagram rp8400 PCI IO Block Diagram Figure A-4 Appendix A 235
LBA Hardware Path -> Physical IO Slot Correspondence (PA-RISC only) Superdome PCI IO Block Diagram Superdome PCI IO Block Diagram Figure A-5 236 Appendix A
B Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx and earlier) 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 and earlier) 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 and earlier) Cause There are now two unbound CPUs, but these CPUs are not the same processors 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 ending address: # nm /stand/vmunix | grep "ABS|_end" [10828] | 212937784| 0|NOTYP|GLOB |0| ABS|_end The ending address is the second number: 212937784 Step 2.
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 244 Appendix C
Glossary bound CPU a CPU that cannot be migrated from or to virtual partitions while the involved virtual partitions are running. Bound CPUs can handle IO interrupts. dynamic CPU migration the vPars ability to add or remove floater CPUs while a virtual partition is running. hard partition any isolated hardware environment, such as a rp7400 server or an nPartition within a Superdome complex.
Glossary bound CPU 246 Glossary
Index Symbols /stand filesystem, 26, 72 A adding cpu to a partition, 176 adding io to a partition, 159, 160 adding memory resources to a partition, 162 alternate partition database files, 151 application fault isolation, 19 attributes, 126 AUTO file, 141 Autoboot, 57, 142 B BCH.
Index G getauto, 105 glance, 25 golden image, 207 granularity, 169 GSP. See Guardian Service Processor Guardian Service Processor terminal type, 71 H hard partitions, 18 hardware, 20 hardware console port, 57 hardware paths specifying for CPUs, 60, 188, 190, 191 help, 105 hung partition, 150 LBA.
Index O ODE, 23 OLAR.
Index virtual consoles, 38 GSPdiag1 device file, 39 output delay, 39 terminal emulation, 39 virtual partitions, 18, 30 adding cpu resources, 176 adding io resources, 159, 160 adding memory resources, 162 compared to hard partitions, 17 creating, 123 defined, 17 monitor, 31 naming, 53 rebooting, 131 removing, 125 removing cpu resources, 176 removing io resources, 159, 160 removing memory resources, 162 shutdown, 131 shutting down, 131 shutting down all, 132 states, 112 versions, 42 Virtual Partitions product
