Release Notes HP StorageWorks Secure Path 3.0F Service Pack 3 for HP-UX 11i v1.0 and 11i v2.
Legal and notice information © 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.
About this document This document summarizes the most recent product information for HP StorageWorks Secure Path 3.0F Service Pack 3 for HP-UX 11i v1.0 and 11i v2.0 systems: • • • • Release notes information Intended audience Accessing future product updates Other documentation Release notes information This document describes the following: • Secure Path 3.0F SP3 kit contents • Secure Path 3.0F SP3 for Active-Passive disk arrays • What’s new with Secure Path 3.
• HP StorageWorks Secure Path 3.0F Service Pack 3 for HP-UX 11i v1.0 and 11i v2.0 installation and reference guide (part number AA–RR4VK–TE). • White papers and best-practices documents are available at:http://www.hp.com/country/us/ eng/prodserv/storage.html. Secure Path 3.0F SP3 kit contents The Secure Path 3.0F SP3 for HP-UX kit includes: • Secure Path 3.0F Service Pack 3 for HP-UX readme.txt document • HP StorageWorks Secure Path 3.0F Service Pack 3 for HP-UX 11i v1.0 and 11i v2.
Operating system support Table 1 lists the system features and requirements for Secure Path 3.0F SP3 for Active-Passive disk arrays. For additional support information, go to the HP web site http://www.hp.com/support. Table 1 Secure Path 3.0F SP3 for Active-Passive disk arrays system features and requirements Requirement System feature HP-UX version HP-UX 11i (v1.0, v2.0) 64-bit HP-UX 11i (v1.
Table 2 Secure Path 3.0F SP3 for Active-Passive disk arrays supported devices and driver requirements HP-UX version Supported HBAs Driver version (minimum) Supported storage arrays 11i v1.0 A5158A A6685A A6795A A6826A Fibre Channel B.11.11.01 EVA3000 (HSV100) EVA5000 (HSV110) 11i v1.0 A6826A A9782A A9784A AB378A AB379A Fibre Channel B.11.11.07.01 EVA3000 (HSV100) EVA5000 (HSV110) 11i v2.0 A6795A A6826A A9782A A9784A AB378A AB379A Fibre Channel B.11.23.04.
Table 4 lists the configuration limits for Secure Path 3.0F SP3 for Active-Passive disk arrays. Table 4 Configuration limits for Secure Path 3.
• • • • • • • • In the case of a write operation, LVM records the error and continues as long as the data has been successfully written to at least one mirror. In either case, with Secure Path installed, this initial timeout can last up to one minute. After the timeout, LVM keeps track of the physical volume status as Unavailable, and future I/O request do not suffer the delay. Do not make any SAN configuration changes to the system during the upgrade or installation of Secure Path 3.0F SP3.
disk 14 0/2/1/0.16.4.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ Acpi(HWP0002,200)/Pci(1|0)/Fibre(WWN5002B36D,Lun0)/ HD(Part1,SigC8FB3EDE-79D3-11D9-8002-D6217B60E588)/\EFI\HPUX\HPUX.EFI disk 17 0/5/1/0.16.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ Acpi(HWP0002,500)/Pci(1|0)/Fibre(WWN5002B36C,Lun0)/ HD(Part1,SigC8FB3EDE-79D3-11D9-8002-D6217B60E588)/\EFI\HPUX\HPUX.EFI disk 26 0/5/1/0.16.4.0.0.0.
NOTE: To list the LUNs of other controllers, see “Enumerating all Fibre Channel devices”. To determine the EFI path of a physical hardware path of the device, see “Identifying the EFI path of the physical hardware path with Secure Path”. 5. Select any of the Fibre Channel options (as described in step 1). Select the boot partition Part1.
14. Select Save changes to NVRAM. Identify the EFI path of the physical hardware path on systems that have Secure Path installed. Determining the active or standby path’s hardware path To determine the hardware path of a standby path by using the spmgr display and ioscan commands, see “Installing Secure Path on a SAN boot device” in the HP StorageWorks Secure Path 3.0F Service Pack 3 for HP-UX 11i v1.0 and 11i v2.0 installation and reference guide. To determine the hardware path of a standby path: 1.
Identifying the EFI path of the physical hardware path with Secure Path To identify the EFI path of the physical hardware path with Secure Path: 1. Note the active controller serial number using spmgr display -dv . In this example, it is P5849D5AAPN00W. Server: aphia3.india.hp.
Reconfiguring dump devices in the event of path failover In the event of a path failover to a device configured as a system dump device, a reconfiguration using an alternate active path to the device is attempted automatically. NOTE: This section applies only to HP-UX 11i v1.0. Reconfiguration of dump devices in the event of a path failover is automatic in later versions of HP-UX.
• If the LUN is part of an LVM volume group, deactivate it. 3. When the LUN is in the Inactive state, enter the following commands: spmgr delete old_device ioscan insf -e 4. Use the spmgr display command to confirm that the new LUN is discovered. NOTE: To prevent the LUN from being left in the Inconsistent state, delete the device by using the spmgr delete command before unpresenting the device.
occurs because the Secure Path persistence module is loaded (at init level 1) only when the LVM configuration is complete (before init level 1). The volume groups are activated by Secure Path’s init script at init level 2. • Concurrent or overlapping ioscans can result in the first ioscan reporting intermediate path states of the second ioscan. The second ioscan correctly reports the state of the paths. An application doing ioscan compares could erroneously detect an error when another ioscan begins.
• • • • The error message should read: Unable to locate an unclaimed unit with that World Wide LUN ID. The spmgr display –d device command requires a device (c#t#d#) as an argument, but accepts a WWLUNID as the argument and responds with missing or incorrect data. Use only device with the –d option. The spmgr select and spmgr restart commands occasionally respond with the following error message: Error: Invalid Argument The command completes successfully.
• An issue which could, under certain instances, when the proactive path polling and Lun Collision occurs simultaneously on the same logical unit causing system panic has been addressed in this release. • Earlier Secure Path releases reported PPM Path Failing message as a debug log message. This syslog message has been modified to be more informative in this release.
Table 6 Secure Path 3.0F SP3 for Active-Active disk arrays supported devices and driver requirements HP-UX version Supported HBAs Driver version (minimum) 11i v1.0 A5158A A6685A A6795A Fibre Channel B.11.11.01 11i v1.0 A6685A A6826A A9782A A9784A AB378A AB379A Fibre Channel B.11.11.07.01 11i v2.0 A6795A A6826A A9782A A9784A AB378A AB379A Fibre Channel B.11.23.04.
Table 8 Configuration limits for Secure Path 3.
IMPORTANT: For information about Secure Path device path representation and usage, see “Secure Path device path representation and usage”.
Secure Path for Active-Active disk arrays with LVM PVLINKS Secure Path takes control of the device configured under LVM with PVLINKS for alternate paths, and overrides LVM PVLINKS to provide automatic I/O path failover and failback functionality. LVM PVLINKS provides an alternate path for the device during system reboot. HP recommendations HP recommends that you specify the physical volume paths while configuring LVM with PVLINKS and using LVM PVLINKS with Secure Path for Active-Active disk arrays.
The following example shows how to configure PVLINKS using the vgextend command: vgextend - extend an LVM volume group by adding physical volumes SYNOPSIS /usr/sbin/vgextend [-f] [-A autobackup] [-g pvg_name] [-x extensibility] [-z sparepv] vg_name pv_path ...
