Release Notes HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.
Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P.
About this document This document summarizes the most recent product information for HP StorageWorks Secure Path 3.0F Service Pack 4 which includes: • • • • Release notes information Intended audience Accessing future product updates Other documentation Release notes information This document describes the following: • Secure Path 3.0F SP4 kit contents • Secure Path 3.0F SP4 for Active-Passive disk arrays • What's new with Secure Path 3.
• Subscribing to this service provides you with e-mail updates on product enhancements, newer versions of drivers, and firmware documentation updates, as well as instant access to other product resources. • After signing up, you can quickly locate your products by selecting Business support and then Storage under Product Category. Other documentation Additional documentation that you may find helpful includes: • HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.
What's new with Secure Path 3.0F SP4 for Active-Passive disk arrays There are no new features, fixes, and enhancements in Secure Path 3.0F SP4 for Active-Passive disk arrays. IMPORTANT: If you have Active-Passive disk arrays (EVA3000 and EVA5000 with fw 3.x), you can choose to continue using Secure Path 3.0F SP3. Operating system support Table 1 lists the system features and requirements for Secure Path 3.0F SP4 for Active-Passive disk arrays.
Table 2 lists the configuration limits for Secure Path 3.0F SP4 for Active-Passive disk arrays. Table 2 Configuration limits for Secure Path 3.
Table 3 lists the patch revisions for Secure Path 3.0F SP4 for Active-Passive disk arrays. Table 3 Patch revisions for Secure Path 3.0F SP4 for Active-Passive disk arrays HP-UX version Patch revisions (minimum) HWEnable 11iB. 11. 11.
General problems This section describes problems that may arise during Secure Path operation and how to avoid them. • When Secure Path is installed on HP-UX 11i v1.0 and 11i v2.0, the following warning messages are displayed, which you can ignore: ld: (Warning) Ignoring .IA_64.unwind_hdr section in file "/usr/conf/mod/hsx". ld: (Warning) Ignoring .IA_64.unwind_hdr section in file "/usr/conf/mod/swsp". ld: (Warning) Ignoring .IA_64.unwind_hdr section in file "/usr/conf/mod/swspBus" . 3 warnings.
• Ensure that the port speeds for 2 GB or 4 GB Fibre Channel switches have been set correctly and that they are not set to auto-negotiate. • When creating snapshots or clones of a device that is managed by LVM, be sure to configure LVM properly. After creating a snapshot or clone of a physical volume, always run vgchgid(1M) to break the association between the volume group and the snapshot or clone. Otherwise, LVM assumes that the snapshot or clone is an alternate path to the original physical volume.
disk 26 0/5/1/0.16.4.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ Acpi(HWP0002,500)/Pci(1|0)/Fibre(WWN5002B36D,Lun0) /HD(Part1,SigC8FB3EDE-79D3-11D9-8002-D6217B60E588)/\EFI\HPUX\HPUX.EFI 2. During the system boot, you must use the EFI Boot Manager to interrupt the process: EFI Boot Manager ver 1.10 [14.60] Firmware ver 2.21 [4306] Please select a boot option HP-UX Primary Boot: 0/5/1/0.16.4.0.0.0.3 HP-UX HA Alternate Boot: 0/1/1/0/1/1.0.0 HP-UX Alternate Boot: 0/1/1/0/1/1.2.
Removable Media Boot [Acpi(HWP0002,0)/Pci(2|1)/Scsi(Pun3,Lun0)] Load File [EFI Shell [Built-in]] Load File [Acpi(HWP0002,100)/Pci(1|0)/Pci(4|0)/Mac(00306E495F6F) Exit 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.
NOTE: The device already exists in the boot option if the system displays Edit Existing Boot Option or make a new entry [E-Edit N-New]:. Proceed but do not save the changes to NVRAM; that is, proceed till step 10 and enter N when prompted. 9. Enter a description to display in the available boot options in the EFI boot manager; for example: Enter New Description: 0/2/1/0.16.4.0.0.0.3 New BootOption Data.
3 c12t1d2 P4889B49IM403A td6 255/255/0/2.3 c10t1d3 WWPN: N/A Path State: Standby The output shows four operation paths: one is in Active path state, one is in Available path state, and two are in Standby path state. Select one of the path instances to determine the hardware path (for example, c6t1d3). Note the values c(6), t(1), and d(3) in the instance. 2. Enter the ioscan -kfnC ext_bus command.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0 c24t0d2 P5849D5AAPN00W td0 255/255/0/0.2 c4t0d3 WWPN: Unknown Path State: Active [P] 1 c24t0d2 P5849D5AAPN00W td0 255/255/0/0.2 c10t0d3 WWPN: Unknown Path State: Active 2 c24t0d2 P5849D5AAPU05E td0 255/255/0/0.2 c6t0d3 WWPN: Unknown Path State: Standby 3 c24t0d2 P5849D5AAPU05E td0 255/255/0/0.2 c8t0d3 WWPN: Unknown Path State: Standby 2. Note the port WWNs of the active controller using Command View EVA.
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. Under certain circumstances, dump reconfiguration using the new path may fail (for example, dump configuration through crashconf(1M) occurring in parallel to a path failover event and the event timing out). If this occurs, an error message is logged in /var/adm/syslog/syslog.log, indicating the device name for the failed automatic path reconfiguration.
2. Put the LUN in the Inactive state: • If the LUN is mounted, unmount it. • 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.
• After a LUN has been deleted using the spmgr delete command, and is unpresented at the array, any re-presenting of that device and an ioscan results in the device being displayed in the spmgr display –u unattached list. The Secure Path driver keeps track of the deleted status of the device WWLUNID. • Do not make any SAN configuration changes to the system when upgrading or installing Secure Path. For example, do not add new LUNs or delete arrays or LUNs.
Secure Path Manager (spmgr) The following problems may arise in spmgr for Active-Passive disk arrays: • If there are several Secure Path devices configured on the system, the Secure Path startup services can take longer because device scanning is initiated to synchronize Secure Path persistence data. • If a preferred path to a device is in the Failed state, and you run a spmgr restore –d device command, the command line displays the prompt only. The path remains in a Failed state and no path change is made.
Interoperability with Ignite-UX software Ignite-UX software does not support Secure Path 3.0F SP4 for the following reasons: • When Secure Path 3.0F SP4 is installed on a system, the hardware addresses of all EVA disk LUNs change. During the recovery process, importing LVM volume groups on the EVA array may fail. • If the boot disk resides on an EVA array, the system fails to boot due to an LVM configuration failure. • Secure Path 3.
System feature Requirement HFS (UFS) File systems JFS (VxFS) HP Logical Volume Manager (LVM) or Volume managers Veritas Volume Manager (VxVM) Clustering HP MC/ServiceGuard A11.15 or later Fibre Channel mode Switched Fabric and Arbitrated Loop NOTE: For supported HBAs, drivers, and firmware versions, see the HP SPOCK website: http://www.hp.com/storage/spock Table 5 lists the patch revisions for this release and earlier releases of Secure Path 3.0F SP4 for Active-Active disk arrays.
Avoiding problem situations The following problems may arise during Secure Path operations: • The status of a path is updated only when I/O occurs on that path or when proactive path monitoring is enabled. • Only Fibre Channel connectivity is supported. • When all paths to an end LUN fail in the case of I/O to non-LVM devices with the HFS file system, or asynchronous I/O to non-LVM devices, I/O to the LUN waits until connectivity through these paths are restored.
Secure Path device path representation and usage This section provides information about device path representation, usage, and HP recommendations for Secure Path devices: • Device path representation of Secure Path for Active-Active disk arrays • Differences between Secure Path for Active-Active disk arrays and LVM PVLINKS • HP recommendations Device path representation of Secure Path for Active-Active disk arrays Secure Path for Active-Active disk arrays uses the physical paths to an end device.
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.
Path: Device Special File e.g./dev/dsk/c#t#d# Example: autopath set_lbpolicy RR /dev/dsk/c30t0d1 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 ...
