Chapter 17 Virtual Partitions (vPars) HP-UX Handbook Revision 13.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 TERMS OF USE AND LEGAL RESTRICTIONS FOR THE HP-UX RECOVERY HANDBOOK ATTENTION: PLEASE READ THESE TERMS CAREFULLY BEFORE USING THE HP-UX HANDBOOK. USING THESE MATERIALS INDICATES THAT YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THESE TERMS, DO NOT USE THE HP-UX HANDBOOK. THE HP-UX HANDBOOK HAS BEEN COMPILED FROM THE NOTES OF HP ENGINEERS AND CONTAINS HP CONFIDENTIAL INFORMATION.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Table of Contents Table of Contents ___________________________________________________________ 3 Introduction _________________________________________________________________ 5 Virtual Partitions Environment, vpmon and vpdb _______________________________________ 5 Virtual Console ____________________________________________________________________ 7 Daemons and vPar states ___________________________________________________________ 8 Differences b
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Using Virtual Partitions _______________________________________________________ 23 Booting the Monitor ______________________________________________________________ 23 EFI Commands (Integrity only), vPar and nPar Modes ____________________________________ 24 Using vparefiutil –u to update the EFI path mapping in the vPars database ____________________25 Boot configurations _______________________________________________________________ 25 Setting
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Introduction This chapter provides an overview of the Virtual Partitions (vPars) product. Virtual Partitions (vPars) is not included with the HP-UX operating system. The detailed product information can be found at http://docs.hp.
Chapter 17 Virtual Partitions (vPars) Application October 29, 2013 Application vPar 2 vPar 1 HP-UX 11i OE HP-UX 11i OE vPar Monitor Hardware / Firmware The vPars monitor manages the assignment of the hardware resources to the virtual partitions, boots virtual partitions and their kernels, and emulates certain firmware calls. Once a virtual partition is launched, the monitor transfers the ownership of the hardware to the virtual partition.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 To create or modify a virtual partition see section vPars commands or the online manuals at http://docs.hp.com. Virtual Console The console device should be assigned to the first vPar (PA-RISC). All vPars share the same console device. Each virtual partition has its own virtual console. You can use Ctrl-A to cycle between all running vPars. For PA-RISC based servers: 1. Each vPar has its console I/O sent to its vcn (Virtual Console) driver.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Daemons and vPar states The daemon vpard is started with the script /sbin/init.d/vpard. It synchronizes the master database and the local disk databases for all vPars in state “up”, at a default interval of 5 seconds. The vpard daemon also helps to manage communications for the virtual console. The daemon vphbd is started with the script /sbin/init.d/vparhb. It provides a heartbeat status, written to the local disk.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Differences between vPars and HP Integrity Virtual Machine vPars segments a system using dedicated CPUs and I/O hardware per partition; these are exclusively under the control of the vPar’s booted kernel. Integrity Virtual Machine allows subCPU granularity and shared I/O on the same I/O hardware among kernels known as guests. A vPar uses dedicated CPUs and LBAs. PCI-Interfaces attached to the same LBA can not be shared.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Minimum Requirements for each vPar: One processor; enough physical memory to run HP-UX 11i and applications; recommended 1GB of memory available per each installed CPU; one unique LAN card recommended (on a PCI bus/Local Bus Adapter LBA uniquely owned by the vPar), because each vPar has an independent kernel and works as a separate system; one unique boot device (connected through SCSI or Fiber Channel card, on a PCI bus/Local Bus Ad
Chapter 17 Virtual Partitions (vPars) October 29, 2013 vparenv: Unix shell command that allows you to set the mode (vPars or nPars) for the next reboot of the nPartition or to set the memory granularity unit size in the firmware. vparconfig: EFI command that allows you to set the mode (vPars or nPars) and forces a reboot of the nPartition. Note: vparconfig is not a built-in EFI command; you will need to go to the fsN:\> disk prompt to execute this command.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Planning a Virtual Partition (an Example) This section gives an overview of how to break down a system into partitions. The N-Class block diagram helps to identify the usage of bus adapters to create a partition plan from the ioscan output.
Chapter 17 0/0/2/0.6 0/0/2/0.6.0 0/0/2/0.7 0/0/2/0.7.0 0/0/2/1 0/0/2/1.7 0/0/2/1.7.0 0/0/4/0 0/0/5/0 0/1 0/2 0/4 0/4/0/0 0/4/0/0/4/0 0/4/0/0/5/0 0/4/0/0/6/0 0/4/0/0/7/0 0/5 0/5/0/0 0/5/0/0/4/0 0/5/0/0/5/0 0/5/0/0/6/0 0/5/0/0/7/0 0/8 0/8/0/0 0/8/0/0.5 0/8/0/0.5.0 0/8/0/0.7 0/8/0/0.7.0 0/8/0/1 0/8/0/1.7 0/8/0/1.7.0 0/10 0/12 1 1/0 1/2 1/2/0/0 1/2/0/0.0 1/2/0/0.0.0 1/2/0/0.7 1/2/0/0.7.0 1/2/0/1 1/2/0/1.7 1/2/0/1.7.0 1/4 1/4/0/0 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.
Chapter 17 1/12/0/0 1/12/0/0/4/0 1/12/0/0/5/0 1/12/0/0/6/0 1/12/0/0/7/0 32 33 36 37 40 41 44 45 96 97 100 101 104 105 108 109 192 Virtual Partitions (vPars) ba PCItoPCI Bridge lan HP A5506A PCI lan HP A5506A PCI lan HP A5506A PCI lan HP A5506A PCI Bus Converter Processor Bus Converter Processor Bus Converter Processor Bus Converter Processor Converter Processor Bus Converter Processor Bus Converter Processor Bus Converter Processor Memory pbc processor pbc processor pbc processor pbc processor pbc Bus pr
Chapter 17 Virtual Partitions (vPars) October 29, 2013 # vparcreate -p vpar2 -a -a -a -B cpu::2 mem::4096 io:0/8 -a io:1/1 -a io:0/8/0/0.5.0:boot auto # vparcreate -p vpar3 -a -a -a -B cpu::2 mem::2048 io:0/5 -a io:1/4 -a io:1/4/0/0.5.0:boot auto We see the three partitions in our block diagram now: Note: When using vPars A.03.01 or earlier, I/O is assigned only at or below LBA level. For correct I/O allocation, you must specify the LBA. With vPars A.03.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 # vparcreate –p vpar1 –a cpu::2 –a cpu:::4 –a cpu:0/12 –a cpu:0/13 Installing vPars Installation of vPars always begins with a non-vPar system that is already running HP-UX 11i (v1 – 3). The vPars product bundle is then added to this installation to create the partitions. The usual procedure is to create the first vPar, then boot this vPar to install and configure other partitions from it. An Ignite-UX server is used in most cases. From A.03.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Required Patch Bundles vPars A.05.xx: There are no patch bundles required for vPars. However, the vPars A.05.01 release requires the patch PHSS_36739 to resolve issues with the vPars dynamic memory migration feature. This patch fixes JAGag43006 (“Memory got removed from an active partition during memory OLA”). The patch is available at the HP IT Resource Center (at http://itrc.hp.com, select “maintenance and support for hp products”). vPars A.04.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 # vparenv –m vPars The EFI command vparconfig can be used alternatively. It is being installed in the EFI partition of the root disk with the installation of the vPars product. The file vparconfig.efi is located in \efi\hpux. Example: Shell> fs0: fs0:\> vparconfig reboot vPars ... Shell> fs0: fs0:\> hpux vpmon Installation from Ignite-UX Ignite-UX Version considerations vPars A.05.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 issues vparboot will tftp the Ignite kernel and file system from the Ignite Server and pass them to the vpmon. vpmon will load them into the newly created vPar and boot it. The Ignite files passed to the vpmon include the IP address of the Ignite Server. A LAN boot is not done; therefore no booting IP addresses will be needed on the Ignite Server for the vPar. Integrity: There is no argument to the –I option.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 # vparenv –m vPars 2. Reboot the system and run the EFI shell from the EFI Boot Manager: # shutdown –r 3. From the EFI shell, boot the monitor and the first virtual partition: Shell> fs0: Fs0:\> hpux HPUX> boot /stand/vpmon vparload –p vpar1 4. Set the TERM variable to hpterm. 5. From the vpar1 console boot vpar2 using vparboot # vparboot –p vpar2 –I A message will popup showing: vpar2 loaded 6.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Updating the vPars Product There are three different possible reason to update: Updating from a vPars version to a newer one of the same release, e.g. from A.04.xx to A.04.yy Updating from vPars A.03.xx to A.04.xx with update-ux (PA-RISC only) Update from vPars A.04.xx to A.05.xx with update-ux (Integrity only) All the steps are described in the manual “Installing and Managing HP-UX Virtual Partitions (vPars)”, e.g. http://www.docs.hp.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 # vparstatus -p vpar2 -v [Virtual Partition Details] Name: vpar2 . . . [IO Details] 1.0.14 1.0.12 1.0.14.0.0.4.0.10.0.0.0.0.0 BOOT 1.0.14.0.0.4.0.5.0.0.0.0.0 TAPE Create the tape-based recovery archive using make_tape_recovery on vpar2: # make_tape_recovery -A To recover vpar2 do the following from vpar1 with the recovery tape inserted in the tape drive 1/0/14/0/0/4/0.5.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Change of vPars install path in Ignite-UX C.6.0 If you are using Ignite-UX C.6.0 or later, the vpar boot command used to install an HP-UX 11.11 virtual partition will change: Before Ignite-UX C.6.0: # vparboot –p -I WINSTALL Ignite-UX C.6.0: # vparboot –p -I /opt/ignite/boot/Rel_B.11.11/WINSTALL Using Virtual Partitions This chapter describes the usage of the virtual partition software and its commands.
Chapter 17 -D database_filename Virtual Partitions (vPars) October 29, 2013 boots the virtual partitions using an alternate partition database file. For more information, see “Using an Alternate Partition Database File” at http://docs.hp.com. The default partition database file is /stand/vpdb. Note: Once the vpmon has been loaded, the EFI partition or LIF area is no longer accessible. vpm http://docs.hp.com/en/7042/T1335-90041.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Set the mode to nPars and then immediately reboot the nPartition into nPars mode: Shell>fs0: fs0:\> vparconfig reboot nPars It is also possible to use vparenv to set the mode. vparenv displays and sets the environment for the next boot.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 #vparcreate -p vPar1 -a io:0.8.0.0.2.0:ALTBOOT To set both the primary and alternate boot paths on the same command line: #vparcreate -p vPar1 -a io:0.8.0.0.5.0:BOOT –a io:0.8.0.0.2.0:ALTBOOT vparmodify: if the virtual partitions are already created, you can specify the primary or alternate boot paths with the BOOT and ALTBOOT attributes within the vparmodify command: To set the primary boot path: #vparmodify -p vPar1 -a io:0.8.0.0.5.
Chapter 17 Virtual Partitions (vPars) MON> MON> MON> MON> October 29, 2013 vparload vparload vparload vparload -all -auto -p vpar1 -p vpar1 –o “-is” –b /stand/vmunix.prev This command performs the same function as the vparboot command from the HP-UX shell prompt. Shows the boot path from which vpmon was loaded reboots the monitor and the whole server similar to CTRL-B, RS can be used for listing a file, similar to the cat(1) command within HP-UX.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 -b kernelpath boots the virtual partition using the kernel kernelpath, such as /stand/vmunix.prev, instead of the default kernel /stand/vmunix. -o boot_options boots the virtual partition using the options boot_options, such as -is for single-user mode or -lm for LVM maintenance mode.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 MON> cat notes.txt 10/13/2001: built new kernel today. if problems arise, revert to saved kernel vmunix.original cbuf cbuf partition_name Displays the contents of the console buffer of a partition. help help or ? lists all monitor commands.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 scan Lists all hardware discovered by the Monitor and indicates which virtual partition owns each device. toddriftreset Reset the drifts of the real-time clock. Use this command if you reset the real-time clock of the hard partition at the BCH prompt. vparinfo vparinfo [partition_name] This command is for HP internal use only.
Chapter 17 vparcreate vparboot vparmodify vpardump vparextract vparreloc vparremove vparreset vparstatus vparutil vparenv Virtual Partitions (vPars) October 29, 2013 Create a new virtual partition Boot a virtual partition Modify the attributes of a virtual partition Manages Monitor dump files Extracts memory images from a running virtual partition system Relocates the load address of a vmunix file, determines if a vmunix file is relocatable and promotes the scope of symbols in a relocatable vmunix file
Chapter 17 Virtual Partitions (vPars) October 29, 2013 It is recommended to configure LBA with the physical hardware console port as part of the first virtual partition created. vparboot The vparboot command is used to boot a second vPars from a running vPars. The vparboot command has several options as the vparload command at the Monitor prompt.
Chapter 17 Virtual Partitions (vPars) cpu::num io:path[:attr1[,attr2]] mem::size mem:::base:range October 29, 2013 Yes No No No vpardump The vpardump command is used to create and analyze a virtual partition’s monitor dump file. vparmon is the image of the virtual partition monitor and dumpfile is the crash dump file corresponding to that image. vpardump is usually run from the vparinit rc script to analyze a crash dump during the HP-UX boot.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 vptest# vparreset -p vpar1 -h vparstatus Display information about one or more virtual partitions on a system. If the monitor is not loaded the vparstatus shows a message. The output also shows the state of a vPars. Examples: Running vparstatus on system where vpar is configured, but not running at this time. # vparstatus vparstatus: Warning: Virtual partition Monitor not running, Requested resources shown.
Chapter 17 Virtual Partitions (vPars) [CPU Details] Min/Max: 1/3 Bound by User [Path]: Bound by Monitor [Path]: Unbound [Path]: [IO Details] 2.0.0 2.0.1 2.0.1.0.0.1.0 2.0.4 October 29, 2013 BOOT [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 1024 New options added to vparstatus in 3.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 vparadmin (vPars A.03.03 and A.04.02 or later) The command allows to: Turn on or turn off the vPars flexible administrative capability; change flexible admin capability password; list the current configuration in the designated admin vPars list; adding or deleting vPars to or from the designated admin vPars list.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 information, see the “A.05.01 Resources” chapter in the “HP-UX Virtual Partitions Administrator's Guide”. Mixed HP-UX 11i v2/v3 vPars Environments: You can now have a vPars A.05.01 monitor and database that simultaneously supports virtual partitions running vPars A.05.01 on HP-UX 11i v3 (11.31) and virtual partitions running vPars A.04.02 or above on HP-UX 11i v2 (11.23).
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Support for the new sx2000 chipset on Integrity servers like Integrity Superdome, rx8640, rx7640 and also PA cell-based server with PA-RISC 8900 CPU like rp8440 and rp7440. vPars Flexible Administrative Capability on Integrity Servers: Limit administration capability for certain virtual partitions, only the superuser within the designated vPars can perform vPars administration affecting other vPars.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 vPars A.03.02 (out-of-support): It is now possible to use SBA (System Bus Adapter) as a I/O resource instead of LBA during vPars configuration. Autoboot attributes have been extended with the autosearch option. Attribute autosearch can have the values “search” and “nosearch”. Value “nosearch” means that only the primary boot path is attempted, while “search” will try the alternate boot path, if the primary path boot failed.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 A.02.02 supports the SCSI/LAN Combo card as boot device. This card has a built in PCI-Bridge below the LBA. The full path length for a device is now longer than it was in A.02.01 and the database was modified to accommodate this. The notation to add hardware paths to a virtual partition can be done with the output from ioscan or the full I/O path with only dots in it. vPars accept both commands and handles them differently.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Virtual Partitions Product Support Policy The HP-UX vPar product T1335AC is not bundled with the Application (DART) DVD/CDROM, it needs to be ordered separately. Due to the high level of integration, defect fixes for the vPar product are not issued as individual patches. Product defect fixes and enhancements are delivered via the latest version of the product. All vPars versions are full releases and contain all product components.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 For more information see the document: http://docs.hp.com/en/1705/oc.pdf. Crash Dump Handling on vPars Systems If a vPar crashes and writes a dump, the crash handling is the same as on an nPar. The dump is written to /var/adm/crash and can be analyzed using the same tools as on an nPar systems. The only difference is a monitor (vpmon) crash.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Use vparreset -t (for TOC) from another running virtual partition to perform a soft reset on a vPar. For example, if vpar2 is hung, we can execute vparreset from the running partition vpar1: vpar1# vparreset -p vpar2 -t The target virtual partition either shuts down or reboots according to the setting of the autoboot attribute of that virtual partition. Other virtual partitions are unaffected by one virtual partition’s reset.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Note: On PA-RISC, /stand/vpmon.dmp is a special file. Do not delete, move, rename, or modify this file. If you need to look at the contents of the monitor dump file, use the vpmon.dmp.n file located in /var/adm/crash/vpar. Monitor Dump Analysis Tool The vPars monitor is not a HP-UX kernel and you cannot use a kernel dump analysis tool to examine a monitor dump file. Contact your HP Support Representative to analyze the monitor dump file.
Chapter 17 Virtual Partitions (vPars) October 29, 2013 Interaction of vPars with other products Please check the current “vPars Ordering and Configuration Guide” (http://docs.hp.com/en/1705/oc.pdf) for the latest information about interaction of vPars with iCAP, WLM, PPU, DIAGNOSTIC and Serviceguard products. Additional Information HP-UX Virtual Partitions Ordering and Configuration Guide http://docs.hp.com/en/1705/oc.
Chapter 17 Virtual Partitions (vPars) Resizing vPars automatically with HP-UX Workload Manager Kernel Memory Allocation (UX 11i v1) LPMC and resulting CPU States (UX 11i v1) October 29, 2013 Product Support Plan (PSP) http://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/12/psp12064.htm (HP Internal) vPars Training Web Page http://cso.fc.hp.com/ssil/uxsk/hpux/products/vPars (HP Internal) vPar Newsletter for support community http://wtec.cup.hp.
