HP-UX Virtual Partitions Release Notes vPars A.03.04 March 2007 Documentation Web Site: http://docs.hp.com Manufacturing Part Number : T1335-90067 E0307 U.S.A. © Copyright 2001-2007 Hewlett-Packard Development Company, L.P.
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.
1 vPars Release Notes What is in this Document This document covers the vPars A.03.04 release. The first chapter covers • • • • What’s New Customer-Requested Fixes vPars Documents Ordering vPars The second chapter covers • Known Problems and Workarounds vPars Synopsis The vPars (Virtual Partitions) product allows you to run multiple instances of HP-UX simultaneously on one server or nPartition by dividing a server or nPartition into virtual partitions.
vPars Release Notes What’s New in this March 2007 Update What’s New in this March 2007 Update This section describes what’s new in this version of vPars. (For a comparison on existing vPars version, see the vPars Version Comparisons tables in the document HP-UX Virtual Partitions Administrator’s Guide.) • vPars A.03.04 supports the sx2000 chipsets that are available on the supported PA-RISC servers. CAUTION vPars Console Assignment on sx2000-based Servers.
vPars Release Notes What’s New in this March 2007 Update NOTE Resizing CLM (Cell Local Memory) when using HP-UX 11i v1 HP-UX 11i v1 (B.11.11) does not support using CLM. Before booting HP-UX 11i v1 on an nPartition, you must ensure that the CLM parameter for each cell in the nPartition is set to zero (0). Although you might be able to boot HP-UX 11i v1 on an nPartition with CLM configured, any memory configured as cell local memory is unusable and such a configurations are untested and unsupported.
vPars Release Notes Customer-Requested Fixes in This Version Customer-Requested Fixes in This Version This section lists the customer-requested fixes in this version of vPars. For detailed information, see the HP ITRC at http://itrc.hp.com.
vPars Release Notes vPars Documents vPars Documents This section lists the official vPars documents. All documents, including additional topic-specific papers related to using vPars, are available at the HP Documentation web site at http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions. • HP-UX Virtual Partitions Release Notes (this document) This describes what’s new as well as known problems for a specific vPars release.
vPars Release Notes Ordering vPars Ordering vPars Software Depot You can order this release of vPars from the HP Software Depot at: http://www.hp.com/go/softwaredepot The direct link to the vPars products on the HP Software Depot for vPars A.03.xx is: http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1335AC For licensing and configuration information as well as required firmware, see the HP-UX Virtual Partitions Ordering and Configuration Guide.
2 Known Problems and Workarounds This section describes the critical known problems of which you should be aware before installing this version of vPars. For information on specific defects, see the HP ITRC at http://itrc.hp.com.
Known Problems and Workarounds Virtual Partition Appears to Hang After Typing control-s Virtual Partition Appears to Hang After Typing control-s Related JAG or Patch ID Number JAGae98555 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description While a virtual partition is shutting down, panicking, or booting, typing control-s to suspend its console output may cause the virtual partition to stop making forward progress. The virtual partition may appear to hang.
Known Problems and Workarounds TC Command of the GSP TC Command of the GSP Related JAG or Patch ID Number JAGae41558 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description Initiating a TC (Transfer of Control) at the GSP (Guardian Service Processor) while the vPars Monitor is booted may cause the hard partition/system to hang. Symptoms If the vPars Monitor is booted and if a TC is issued via the GSP, the hard partition/system may hang.
Known Problems and Workarounds Configuring an Ultra2 or Ultra160 Card with vparutil Configuring an Ultra2 or Ultra160 Card with vparutil Related JAG or Patch ID Number JAGaf00411 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description On the nPartition-able 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.
Known Problems and Workarounds Autoboot Fails from Fibre Channel Device via Brocade 3800 Switch Autoboot Fails from Fibre Channel Device via Brocade 3800 Switch Related JAG or Patch ID Number JAGae78109 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description Using a fibre channel mass storage device via a Brocade 3800 switch with firmware version 3.1.1 within a rp5405, L3000/rp5470, or N4000/rp7400 server running PDC 43.
Known Problems and Workarounds Virtual Partition Fails to Load after a Reboot Virtual Partition Fails to Load after a Reboot Related JAG or Patch ID Number JAGae88150 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description When using an rp7405, rp7410, or rp8400 with firmware version 6, which includes PDC 17.005, the virtual partitions will not boot to the up state after a reboot. Symptoms The virtual partitions will not boot after a reboot.
Known Problems and Workarounds System Resets During a Crash Dump Due to Watchdog Timer System Resets During a Crash Dump Due to Watchdog Timer Related JAG or Patch ID Number JAGae79790 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA 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).
Known Problems and Workarounds System Resets During a Crash Dump Due to Watchdog Timer -> Automatic System restart will be updated. Current Triggering alert levels are: 13 Do you want to modify them? (Y/[N]): n Automatic System Restart configuration has been updated GSP Host Name: keira GSP> On nPartition-able servers, use the following procedure: GSP> cm Enter HE to get a list of available commands GSP:CM> ar This command modifies the automatic system restart configuration of the selected partition.
Known Problems and Workarounds Topology of A5158A Changes from Fabric to Public Loop After the Virtual Partition Reboots Topology of A5158A Changes from Fabric to Public Loop After the Virtual Partition Reboots Related JAG or Patch ID Number JAGaf15533 Applicable on ❏ ❏ vPars A.04.01 on PA vPars A.03.xx on PA Description When the A5158A is connected to the Brocade 2800 or 12000 switch, the topology of the A5158A changes after the virtual partition reboots.
Known Problems and Workarounds Topology of A5158A Changes from Fabric to Public Loop After the Virtual Partition Reboots Logging into the switch, the switch information before the reboot shows: brocade01:admin> switchshow switchName: brocade01 switchType: 2.4 switchState: Online switchMode: Native ... port 0: -- No_Module port 1: -- No_Module port 2: -- No_Module port 3: sw Online F-Port 50:06:0b:00:00:10:23:fa port 4: sw Online F-Port 50:06:0b:00:00:00:f4:28 ...
Known Problems and Workarounds Topology of A5158A Changes from Fabric to Public Loop After the Virtual Partition Reboots Vendor ID is Device ID is TL Chip Revision No is PCI Sub-system Vendor ID is PCI Sub-system ID is Topology = = = = = = 0x00103c 0x001028 2.3 0x00103c 0x000006 PTTOPT_FABRIC ...
