Technical data

Reconﬁguring du

mpdevicesintheeventofpathfailover

In the event of a p

ath failover to a device conﬁgured as a system dump device, a reconﬁguration using

an alternate active path to the device is attempted automatically.

NOTE:

This section applies only to HP-UX 11i v1.0. Reconﬁguration of dump devices in the event of a path

failover is automatic in later versions of HP-UX.

Under certain circumstances, dump reconﬁguration using the new path may fail (for example, dump

conﬁguration through crashconf(1M) o ccurring in parallel to a path failover event and the event

timing out).

If this occurs, an error message is log ged in /var/adm/syslog/syslog.log, indicating the device

name for the failed automatic path reconﬁguration.

To correct this situation:

1. Note the ctd/volume nameofthedeviceforwhichconﬁ guration has failed (based on

informationintheerrormessage).

2. Ensure that this device is a dump device using the crashconf(1M) command.

3. Reconﬁgure this device as a d ump device using the crashconf(1M) command.

Installing Secure Path in a Virtual Pa rtitions environment

To install Secure Path i n a Virtual Pa rtitions (vPars) environment on an EVA boot LUN, complete the

steps below:

1. Install the HP-UX op erating system on an EVA LUN.

2. Install the following kernel patch:

PHKL_33581 (s700_800 11.23 USB DVD Boot, EFI Device Path, HW Enablement)

3. Install the HP-UX vPars software A.04.02.01 or later.

4. Use the vparcreate command to create virtual partitions, and then boot each partition.

NOTE:

You must install the patch PHKL_33581 on each partition.

5. Install Secure Path 3.0F SP3 on each par tition.

NOTE:

If you in

stalledSecurePathonanEVAbootLUN,youcannotinstallvParsonthatLUN.See

Installing and

Managin

g HP-UX Virtual Partitions

for more information on vPars.

LUN collision

If path veriﬁcation is disabled and a device is unpresented before deleting it with the spmgr delete

command, and a new device is added with the same virtual disk or unit number as the old device,

the new device is bound to the WWLUNID of the old deleted device. This leaves the n ew device in an

Inconsistent state. Do not perform any operations until you perform the following recovery procedure:

1. Ensure that the old LUN is not in use (for example, suspend I/O).

2. Put the LUN in the Inactive state:

• If the LUN is mounted, unmount it.

HPStorageWorksSecurePath3.0FServicePack3forHP-UX11iv1.0and11iv2.0