HP-UX Virtual Partitions Release Notes A.05.08 HP-UX 11i v3 HP Part Number: T1335-91010 Published: March 2011 Edition: 1.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents vPars A.05.08 Release Notes..........................................................................5 vPars Overview........................................................................................................................5 New and Changed Features in This Release.................................................................................5 Changes in This Release.......................................................................................................
vPars A.05.08 Release Notes This document provides information about the HP-UX Virtual Partitions (vPars) A.05.08 release. vPars Overview The HP-UX Virtual Partitions (vPars) product runs multiple instances of HP-UX simultaneously on one server, or nPartition, by dividing it 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. vPars provides application and operating system fault isolation.
http://itrc.hp.com/ vPars Checklist This section is a brief checklist of common but significant items you should check while setting up vPars. Firmware Checklist • Check Server Firmware: Check the HP-UX Virtual Partitions Ordering and Configuration Guide for the required server firmware. For the non-nPartition-able systems, firmware upgrades must be done outside of the vPars environment (in standalone mode). For nPartition-able systems, call your HP Support Representative.
and Installation Requirements” (page 5) for further information on using vPars A.05.xx and vPars A.04.xx on Integrity systems, including other Integrity-only specifics. CAUTION: After using vparenv to change the boot mode from vPars mode to nPars mode, further booting and loading of virtual partitions will fail although the vPars monitor has not been rebooted. To boot or load virtual partitions, use vparenv to change the boot mode back to vPars mode.
Known Problems and Workarounds This section provides a list of problems and limitations known to HP at the time of publication. If workarounds are available, they are included. For information on specific defects, see the HP ITRC at http://itrc.hp.com. • No support of agile addressing (extended hardware paths) for non-11.31 virtual partitions in mixed HP-UX 11i v1/v2/v3 vPars environments Related Defect ID and Patch Number QXCR1000764993 Applicable On vPars A.04.xx on HP-UX 11i v2 (B.11.23), vPars A.03.
Workaround Update PDC firmware to the supported revision as specified in the HP-UX Virtual Partitions Ordering and Configuration Guide. • vparreset: Error: Cannot access PIM data for virtual partition Applicable On • vPars A.04.xx on PA-RISC • vPars A.03.xx on PA-RISC Description On PA-RISC systems configured with virtual partitions, the vparreset command sometimes reports an error message, however the reset succeeds.
Symptoms The virtual partitions will not boot after a reboot. One or more of the following errors may appear in the vPars Monitor event log: iodc_perror: dev_open/Boot device init (0x42) iodc_perror: reinit_bootdev/Read ENTRY IO (0x44) iodc_perror: dev_reopen/Read ENTRY IO (0x47) iodc_perror: iodc_io_init/init module and device(0x4b) Could not read IODC firmware for HPA Unknown filesystem for path Workaround Manually boot the virtual partitions with the vparboot or vparload command.
where TAPE is a Fibre Channel tape device previously configured using the :TAPE attribute, the target virtual partition may hang, remaining in the load state indefinitely. Further, the target virtual partition does not reset when using vparreset. Workaround None. HP recommends that you not attempt to boot a Fibre Channel tape device. • A Virtual Partition Remains in Load State with sx2000 Chipset Related Defect ID and Patch Number JAGaf88969 Applicable On ◦ vPars A.05.xx on Integrity ◦ vPars A.04.02, A.
• System Activity Events Reported Through IPMI by EMS Related Defect ID and Patch Number JAGaf62654 Applicable On ◦ vPars A.05.xx ◦ vPars A.04.xx on Integrity ◦ vPars A.04.xx on PA-RISC Description In a vPars environment, system activity events are decoded and reported on all virtual partitions. When examining any single virtual partition, this can be misleading, such that it may appear the events occurred on the virtual partition that reported the problem.
Workaround After the mirror is created, use the vparefiutil -u command to add the new hardware path to EFI path mapping to the vPars database. Note that on Integrity systems running vPars, whenever the EFI path of a boot disk changes (for example, if an OS is re-installed on the disk), the new hardware to EFI path mapping has to be updated in the vPars database. This can be done by running the vparefiutil -u command.
• System Resets During a Crash Dump Due to Watchdog Timer Related Defect ID and Patch Number JAGae79790 Applicable On ◦ vPars A.05.xx on PA-RISC ◦ vPars A.04.xx on PA-RISC ◦ vPars A.03.xx on PA-RISC Description During a crash dump of a virtual partition, hardware heartbeats are delayed long enough such that the watchdog timer is triggered. If the watchdog timer has been configured to reset, then the entire system is reset (TOC).
• Topology of A5158A Changes from Fabric to Public Loop After the Virtual Partition Reboots Related Defect ID and Patch Number JAGaf15533 Applicable On ◦ vPars A.05.xx on PA-RISC ◦ vPars A.04.xx on PA-RISC ◦ vPars A.03.xx on PA-RISC Description When the A5158A is connected to the Brocade 2800 or 12000 switch, the topology of the A5158A changes after the virtual partition reboots.
port 3: sw Online F-Port 50:06:0b:00:00:10:23:fa port 4: sw Online L-Port 1 public Workaround ◦ To permanently set the device to fabric, set the setting on the switch. For example: switch> portcfggport port_#,1 where port_# is the port number of the switch that is connected to the A5158A card and 1 represents “true”.
Description On Integrity servers, if you are in vPars mode and you boot the OS Kernel (boot vmunix) instead of the vPars Monitor (boot vpmon), an error message is typically displayed on the console. You may, however, receive a system panic message, instead of an error message. Symptoms The system panic displays messages similar to the following EFI\HPUX\AUTO ==> boot vmunix ................
◦ Mixed OS (HP-UX 11i v2/v3) Considerations in vPars A.05.xx ◦ Securing Virtual Partitions with HP-UX Role-Based Access Control ◦ Top Ten Tips for Using Virtual Partitions ◦ Using Golden Images with Virtual Partitions ◦ Kernel Memory Allocation ◦ LPMC and resulting CPU States ◦ LVM & vPars I/O Backplane Upgrade ◦ Resizing vPars automatically with HP-UX Workload Manager ◦ Increasing Flexibility by Mixing Minor Release of Virtual Partitions Ordering vPars Product Numbers The vPars A.03.
