Technical data

• 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.
• DonotmakeanySANconfiguration changes to the system d uring the upgrade or installation of
Secure Path 3.0F SP3. For example, do not add new a rrays or LUNs, or delete arrays or LUNs
during upgrade or installation of Secure Path 3.0F SP3.
• Due to constraints imposed by the software distributor (SD) tools, the server’s network must be
configured before installation of Secure Path.
• Stopping spagent using the spinit stop command, and then starting spagent using
the spinit start comm and results in stderr messages. To prevent these messages from
printing, start spagent in a new session and then exit that session.
• Do not use the HP System Administration Manager (SAM) to create or extend volume groups.
Creating and extending volume groups must be done using HP-UX comma nds. When SAM scans
for hardware, any HSV1xx LUNs created after the first LUN are not parsed correctly by SAM and
cannot be selected to create a volume group. Use HP-UX commands to create or extend volume
groups, and then use SAM to create and manage logical volumes.
• Ensure tha t 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 con figure LVM
properly. After creating a snapshot or clone of a p hysical volume, always run vgchgid(1M) to
break the association bet ween the volume group and the snapshot or clone. Otherwise, LVM
assumes tha t the snapshot or clone is an alternate path to the original physical volume. This could
lead to data c orruption if the snapshot or clone was added later to the volume group using
vgextend(1M), vgimport(1M),or vgscan(1M).
• When replacing a rray controllers online, enable p ath verification to update controller IDs in
Secure Path data structures. If path verific ation is not enabled during controller replacement, use
the spmgr refreshdisplay com m a nd to upd a te the serial numbers of the controller.
Proble
m with setboot command
The setboot command fails to set the alternate or high-availability hardware path on the HP-UX 11i
v2.0 IA-64 platform for SAN boot disks on EVA Active-Passive disk arrays.
Follow the steps below to set the primary, alternate, and high-availability hardware paths from the EFI
shell
, which requires a system reboot:
1. If Secure Path is not installed on your system , run ioscan –fneC disk andrecordtheEFI
path and hardware path for each bootable device. If Secure Path is installed on your system,
see “
Determining the active or standby path's hardware path”.
Class I H/W Path Driver S/W State H/W Type Description
===============================================================
disk 2
0/0/2/1.3.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c1t3d0 /dev/rdsk/c1t3d0
Acpi(HWP0002,0)/Pci(2|1)/Scsi(Pun3,Lun0)/\EFI\HPUX\HPUX.EFI disk 0
0/1/1
/0/1/1.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c3t0d0 /dev/dsk/c3t0d0s2 /dev/rdsk/c3t0d0 /dev/rdsk/
c3t0d0s2
/dev/
dsk/c3t0d0s1 /dev/dsk/c3t0d0s3 /dev/rdsk/c3t0d0s1
/dev/rdsk/c3t0d0s3
Acpi(HWP0002,0)/Pci(2|1)/Scsi(Pun3,Lun0)/\EFI\HPUX\HPUX.EFI disk 0
0/1/1
/0/1/1.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
Acpi(HWP0002,100)/Pci(1|0)/Pci(1|1)/Scsi(Pun0,Lun0)/
HD(Part1,SigC44D04A0-0672-11D9-8002-D6217B60E588)/\EFI\HPUX\HPUX.EFI
disk 6
0/2/1/0.16.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110
(C)COMPAQ
Acpi(HWP0002,200)/Pci(1|0)/Fibre(WWN5002B36C,Lun0)/
HD(Pa
rt1,SigC8FB3EDE-79D3-11D9-8002-D6217B60E588)/\EFI\HPUX\HPUX.EFI
8