HP-UX Virtual Partitions Release Notes A.05.03 vPars A.05.03 HP Part Number: T1335-90091 Published: March 2008 Edition: 1.
© Copyright 2008 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.
Table of Contents vPars A.05.03 Release Notes...........................................................................................7 vPars Overview.......................................................................................................................................7 New and Changed Features in This Release..........................................................................................7 New Features...............................................................................
List of Examples 1 Using a Modified Agile Hardware Path........................................................................................
vPars A.05.03 Release Notes This document provides information about the HP-UX Virtual Partitions (vPars) A.05.03 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://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1335CCE • Support for mixed HP-UX 11i v1/v2/v3 vPars environments on PA-RISC systems only. A mixed HP-UX 11i v1/v2/v3 vPars environment allows you to have a vPars A.05.03 Monitor and database that simultaneously supports virtual partitions running HP-UX 11i v1 (B.11.11), HP-UX 11i v2 (B.11.23), and HP-UX 11i v3 (B.11.31) in the same nPartition.
Compatibility and Installation Requirements This section describes the compatibility information and installation requirements for this release. For specific installation instructions, see the HP-UX Virtual Partitions Administrator's Guide. Required Patches vPars A.05.03 requires the HP-UX 11i v3 (B.11.31) March 2008 update release, including the following patch bundles from the HP-UX 11i v3 March 2008 update release: • B.11.31.
NOTE: 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. • Long hardware path from AD221A (PCIe 1 port 4Gb FC & 1 port GigE HBA) card not recognized by vparmodify Related Defect ID and Patch Number Applicable On QXCR1000753480 vPars A.05.
Description If PDC firmware is not updated, side effect can be a panic during dynamic memory migration. Symptoms Panic during dynamic memory migration. 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.05.xx on PA-RISC • vPars A.04.xx on PA-RISC • vPars A.03.
Workaround The preferred workaround is to avoid using agile hardware paths for bridged devices in the vPars commands. If agile hardware paths must be used, then one of the following workarounds can be used. — vparboot -B modifiedAgilePath -p vparName — vparmodify -p vparName -a io:modifiedAgilePath:BOOT The modifiedAgilePath is the agile hardware path reported by the ioscan command with the string “.0.0.0.0” appended to it.
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 command.
Description On Integrity systems running the sx2000 chipset and Intel Itanium 2 single-core processor with 9 MB cache, a virtual partition remains in the load state for at least 30 seconds and does not complete its boot process. Symptoms The console display includes the following: Initializing IO Devices ... LBA Cell 01 (01): Occupied PCI-X 133MHz Scan PCI: Rope Slot Seg Bus Dev Fun Card .. Loading.: 1/0/1/1/0/4/0.6.0.0.0.0.0 Executing Image: "\EFI\HPUX\HPUX.EFI" Optional Data : "\EFI\HPUX\HPUX.
Severity............: Monitor.............: Event #.............: System..............: Summary: INIT initiated CRITICAL fpl_em 267 winona2 Workaround Note that in a vPars environment, when system events are reported via EMS either from system firmware or an OS instance, the system events are decoded and reported on all virtual partitions. The OS instance that is shown as sending the event is not necessarily indicative of the actual virtual partition that encountered the problem.
— — — vPars A.05.xx on PA-RISC vPars A.04.xx on PA-RISC vPars A.03.xx on PA-RISC Description On the nPartitionable servers, using the vparutil command to configure an Ultra2 or Ultra160 SCSI card can cause the virtual partition that owns the SCSI card to fail to boot. Symptoms On the nPartitionable servers, the virtual partition connected to an Ultra2 or Ultra160 SCSI boot device fails to boot after the SCSI card was configured using the vparutil command. Workaround — For vPars A.03.
0) vpar8cell 1) vpar4cell 2) vpar3cell Select a partition number: 2 Automatic system restart for partition 2 is currently enabled. Do you want to disable automatic system restart? (Y/[N]) y -> Automatic system restart is disabled. GSP:CM> • 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.
... port port port port port 0: 1: 2: 3: 4: ---sw sw No_Module No_Module No_Module Online F-Port 50:06:0b:00:00:10:23:fa 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”.
For more information on using vPars with fibre channel devices, see the HP-UX Virtual Partitions Ordering and Configuration Guide. • On sx2000 Integrity Servers, Booting an OS Kernel while in the Wrong Mode May Cause a Panic Instead of Displaying Error Messages Related JAG or Patch ID Number JAGag06132 Applicable On — vPars A.05.xx on Integrity — vPars A.04.
— — — — — — — — — — — — — — Booting, Installing, Recovery, and Sharing in a vPars Environment from DVD/CDROM/TAPE/Network Configuring and Migrating Memory on vPars CPU Configuration Guidelines for vPars Guidelines for Configuring Virtual Partitions on Cellular Platforms Introducing HP-UX 11i Virtual Partitions LVM/VxVM and vPars sx2000 Upgrade Mixed OS (HP-UX 11i v2/v3) Considerations in vPars A.05.
