HP-UX vPars and Integrity VM V6.1 Release Notes HP Part Number: 5900-1578 Published: March 2012, Edition 1.
© Copyright 2012 Hewlett-Packard Company, L.P. Legal Notices 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 1 Introduction...............................................................................................7 1.1 Features and Enhancements in vPars and Integrity VM..............................................................7 1.2 Version Support..................................................................................................................8 1.3 Changes in Support............................................................................................................
.4 HP-UX vPar and VM Support..............................................................................................29 4.5 Storage Interface Support..................................................................................................30 4.5.1 vPar and VM Attached Device Support.........................................................................30 4.5.2 Multipathing Software Support ..................................................................................30 4.5.
Tables 1 2 3 4 5 vPar, VM and VSP Support..................................................................................................8 Known behaviors in vPars V6.1..........................................................................................22 Integrity VM Online Forward Migration Paths......................................................................34 Offline Forward and Backward Migration Support Paths.......................................................
1 Introduction Thank you for installing the vPars and Integrity VM V6.1 bundles (Virtualization Services Platform (VSP) software bundle, BB068AA, and vPars/VM software bundle, VirtualBase). This chapter introduces the release notes for the “converged” vPars and Integrity VM V6.1 product. Install the HP-UX GUID Manager software, which is included with the HP-UX 11i v3 March 2012 release, or can be obtained by going to http://software.hp.com and searching for the HP-UX GUID Manager.
◦ HP-UX 11i v3 VSP — HP-UX 11i v3 March 2012 release ◦ For vPars: HP-UX 11i v3 September 2011 and March 2012 guests (Intel® Itanium® Processor 9300 series VSPs only) ◦ For VMs: HP-UX 11i v3 March 2010 through March 2012 guests • Support for vPars and Integrity VM functionality in a single, common, easy-to-use management environment. • Support for the direct I/O (DIO) networking functionality. • Support for Matrix OE 7.0 fluid cross-technology logical servers with virtual machines.
• Microsoft Windows, Linux , and OpenVMS guests are not supported. Version 4.2.5 was the last version to support Microsoft Windows and Linux guests. • Use of legacy device special files (DSFs) to define virtual storage. Support for the use of legacy DSFs to define virtual storage (including virtual disks and DVDs) are deprecated. Customers should begin planning to use persistent (agile) DSFs when defining their virtual storage devices.
2 Installation Notes This chapter contains notes about installing and upgrading HP-UX vPars and Integrity VM V6.1 and associated software on the VSP system. 2.1 Installing HP-UX vPars and Integrity VM 6.1 This section describes information about installing the HP-UX vPars and Integrity VM 6.1 product bundle and associated software on the VSP system. HP-UX vPars and Integrity VM 6.1 is supported on HP Integrity servers or nPartitions running HP-UX 11i v3 March 2012 release.
3 Issues in this release This chapter contains notes about creating and configuring virtual machines on the VSP system. 3.1 Changes and Issues in this Release This section describes new information and issues in this release. 3.1.1 hpvmhwmgmt might add ports in link aggregates into the DIO pool The hpvmhwmgmt command might put a port used by a link aggregate into the direct I/O (DIO) networking pool. A LAN interface cannot be used by both APA and DIO at the same time.
3.1.3 DIO management device file appears stale to lssf The /dev/hpvmdio device file is listed by lssf -s as a stale device file, however, it is not a stale device file and should not be removed from the VSP system. Removing the /dev/hpvmdio device will result in no longer being able to see the DIO management pool with the hpvmhwmgmt -p dio commands. If the /dev/hpvmdio character device file is removed, use the mknod command to recreate it. The mknod command requires both a major and minor number.
• Cannot dynamically add, delete, modify DIO functions online (that is, virtual OLRAD); such hpvmmodify operations have to be done when the vPar/VM is down. • Removing hpvmdio-owned devices while the VSP is down might result in broken VM configurations that must be fixed manually. • Cannot dynamically add, remove vPar/VM memory with DIO functions assigned. • No Online VM Migration support. • No suspend and resume support for vPars/VMs configured with DIO.
When a VM is converted to a vPar, the vNIC hardware path will be different, so ioscan enumerates it with a different PPA (lan index). Workaround Boot the vPar to single user mode, fix the /etc/rc.config.d/netconf file with the new PPA number, and then switch to run level 3. 3.1.
3.1.17 Adding NPIV HBAs to existing guest with AVIO storage HBAs might cause a problem When adding NPIV HBAs to an existing guest that has AVIO storage HBAs, the next boot of the guest may panic with the message “panic: GVSD: Unable to allocate iocb during initialization”, due to the known defect. To work around this problem, reduce the number of AVIO storage HBAs by consolidating LUNs into fewer AVIO storage HBAs. AVIO allows up to 128 AVIO LUNs under 1 AVIO HBA.
disk disk [2,0,18] [2,0,19] /dev/rdisk/disk6201 /dev/rdisk/disk6413 /dev/rdisk/disk326 /dev/rdisk/disk333 # ioscan –kfNd gvsd Class I H/W Path Driver S/W State H/W Type Description ================================================================= ext_bus 12 0/2/0/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor Adapter 3.1.
Enumerate all SCSI LUNs (Y/N)? [current setting: N]: N Enumerate all FC LUNs (Y/N)? [current setting: N Drv[2F] Ctrl[ALL] Lang[eng] - Options set. Action Required is None None None Shell> Reset the guest for the change to take effect vMP MAIN MENU CO: Console CM: Command Menu CL: Console Log SL: Show Event Logs VM: Virtual Machine Menu HE: Main Help Menu X: Exit Connection [g1] vMP> CM (Use Ctrl-B to return to vMP main menu.
# ioscan -P ms_scan_time -C fc Class I H/W Path ms_scan_time ============================================ fc 0 44/0/0/0/0/0/0 0 min 7 sec 7 ms fc 1 44/0/0/2/0/0/0 0 min 6 sec 213 ms fc 2 44/0/0/2/0/0/1 0 min 4 sec 1 ms 3. 4. If an individual FC HBA takes more than 10 seconds to probe, check your FC switch and zone settings to see why the probe time is so high. Increase the online migration timeout value using the hpvmmodify command.
3.1.27 Probe of NPIV HBAs for Fibre Channel Targets May Timeout During online migration, the target VM Host probes any NPIV HBAs for Fibre Channel (FC) targets. If this probe takes close to 30 seconds (or longer), online migration times out and aborts. The hpvmmigrate command prints an error: # hpvmmigrate -P guest -h host2 -o ...
Table 2 Known behaviors in vPars V6.1 Problem Description/Action When the requirements for satisfying Locality-Optimized Resource Alignment requirements for satisfying LORA configuration are not met, configuration are not met, a message is displayed. Resources for a given vPar are chosen (as part of the vPar's boot up sequence) based on the resource availability and locality considerations.
Table 2 Known behaviors in vPars V6.1 (continued) Problem Description/Action vm.core will not be generated when vPar is in OS upon TC A vPar that transitions past the load of the HP-UX kernel will not produce a vm.core on the VSP when it is terminated abnormally via a TOC. Once HP-UX vm.core will not be generated when vPar is in OS upon TC transitions to the boot state, the responsibility for state capture when a TOC occurs is via DUMP.
Table 2 Known behaviors in vPars V6.1 (continued) Problem Description/Action Cannot remove a VLAN-based vNIC if the VLAN has been If a vPar was created with a vswitch based on a VLAN, removed and that VLAN has been removed, it is not possible to modify or remove a vNIC connected to that vswitch. What to do Recreate the VLAN with nwmgr and restart the vswitch. This will allow you to remove the vNIC using the vparmodify command.
Table 2 Known behaviors in vPars V6.1 (continued) Problem Description/Action Because the base page size of host is set to 64K, the following commands might show incorrect results: • acctcom • acctcms • acctprc2 These commands show incorrect values for mean memory size and kcore-minutes when the base page size is altered to any value other than 4K. In order to see the correct value, the value should be multiplied by (base page size / 4K).
Table 2 Known behaviors in vPars V6.1 (continued) Problem Description/Action Interrupt balancing daemon is disabled in vPars V6.1 Frequent interrupt migration on the vPar can lead to storage LUNs going offline. This can occur indirectly when dynamic CPU migration occurs on a frequent basis when the interrupt balancing daemon is enabled. What to do The interrupt balancing daemon is disabled by default. Do not enable the interrupt balancing daemon.
4 Integrity VM Support Policy This chapter describes the HP-UX vPars and Integrity VM support policies and software version requirements for Integrity VSP and guest operating system environments. 4.1 vPars and Integrity VM Minimum Support Life The following table shows the support date for vPars and Integrity VM versions. Integrity VM Version Release Date Expected End of Support Date Current Status A.03.50 December 2007 Same as HP-UX 11i v2 Supported B.04.10 April 2009 April 2012 Supported B.04.
4.2 vPars Firmware Requirements • Requirement: Customers must upgrade to the latest release in order to receive defect fixes. vPar system firmware requirements: The latest available firmware for the BL8x0c i2 servers that is available can be installed. Firmware bundle 2011.05 is the minimum requirement. For Superdome 2 servers, Superdome 2 Dynamic Core Firmware (2.51.102) is required. NOTE: Customers using only VMs have no firmware requirements. 4.
4.4 HP-UX vPar and VM Support Type of Guest OS Support Integrity VM Version A.03.50 Integrity VM Version Integrity VM B.04.10 B.04.20 Integrity VM Integrity VM B.04.20.05 B.04.
4.5 Storage Interface Support vPars and Integrity VM V6.1 Notes • Fibre Channel adapters supported by TD, FCD, or FLCP drivers Accelerated virtual I/O (AVIO) storage interfaces are defined using the avio_stor adapter type. (See the hpvmresources manpage.) • SCSI adapters supported by the C8xx, MPT, or CISS drivers • IDE adapters supported by the SIDE driver • USB support of the UsbScsiAdapter driver and USB 2.0 support of the usb_ms_scsi driver (AVIO HVSD support for USB 2.
1 Supported by EMC. See EMC documentation. 4.5.3 EVA Series Firmware Requirement The AVIO Storage Driver supports Active-Active firmware types on EVA series (3000/5000 and 4000/6000/8000). Be sure that the following firmware revision levels are met before configuring AVIO backing stores on these arrays: • On EVA 4000/6000/8000, all released firmware revisions support Active-Active configuration. Therefore, no action is necessary on these arrays.
4.8 Supported adapters for AVIO networking vPars and Integrity VM supports those adapters that are of Ethernet or the IEEE 802.3 CSMA/CD network. Note that AVIO interfaces are supported by a select set of Ethernet host NICs.
Adapters: • Broadcom: Device Level Assignment (DLA) ◦ LOMs: BL8x0c i2, Superdome 2 ◦ Stand-Up Cards: AM225A/AM232A/AM233A ◦ Mezzanine Cards: NC532m ◦ Broadcom cards must be running this firmware version or later: ROM Firmware (Boot code) Version: 6.2.21 NOTE: ◦ • You can obtain the ROM firmware from HP.COM or the IPF offline CD 1203. Broadcom VSP and vPars/VMs must be running this minimum driver version: 10GigEthr-02 (iexgbe) B.11.31.1203.
to a VSP running Version 4.3, can be migrated back to a VSP running version 4.2.5 (provided the VM has not been rebooted since beginning its migration).
5 Support and other resources 5.1 Contacting HP 5.1.1 Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level 5.1.
integrated with HP Systems Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced. Details for both versions are available at: http://www.hp.com/go/insightremotesupport To download the software, go to Software Depot: http://www.software.hp.com Select Insight Remote Support from the menu on the right. NOTE: HP recommends using Insight Remote Support on the VSP system.
Table 5 Documentation and its location (continued) Documents Website HP-UX 11i v3 documentation http://www.hp.com/go/hpux-core-docs In the main page, click HP-UX 11i v3. HP Serviceguard Toolkit for Integrity Virtual Servers User Guide HP Serviceguard Toolkit for Integrity Virtual Servers User Guide 5.3 Typographic conventions This document uses the following typographical conventions: %, $, or # A percent sign represents the C shell system prompt.
