Technical data

• 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 conﬁrm 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 com mand b efore unpresenting the device.

If path veriﬁcation is enabled, the LUN collision is identiﬁed and an appropriate message is logged in the

syslog. Follow the instructions in the syslog to resolve this problem.

Event Monitoring Service

This section describes the Secure Path’s Event Monitoring Service (EMS):

• High-availability EVA environment recommendations

•EVA

High-availability EVA environment recommendations

In high-availability environments with heavy I/O loads, you m ay experience I/O timeout conditions. If

I/O timeouts occur, HP recommends that you use the pvchange comma nd to increase the IO_timeout

value from a default of 30 seconds to a maximum of 60 seconds for LUNs (vir tual disks) on EVA 2.0 or

EVA 3.0. Under heavy I/O load conditions, the increased IO_timeout valueallowsforlongerI/O

completion times and for LUN access delays if a controller failover occurs.

NOTE:

Make sure that HP MC/ServiceGuard is conﬁgured properly. See the HP MC/ServiceGuard

documentation for conﬁgurationinformationorgototheHPwebsiteh

ttp://docs.hp.com.

EVA

Disable EMS for all devices or LUNs on a n EVA storage system.

Secure P ath driver for Active-Passive disk arrays

The following problems may arise with Secure Path driver for Active-Passive disk arrays:

• On a server reboot, the a ctive path comes up on the last path probed and not necessarily on

the pref

erred path, regardless of the status of auto-restore or whether a preferred path has been

selecte

d. To restore the active paths to their preferred paths, use the spmgr restore all

command.

• 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

statu

softhedeviceWWLUNID.

• DonotmakeanySANconﬁguration changes to the system when up grading or installing Secure

Path. For example, do not add new LUNs or delete arrays or LUNs.

• When t

he system is booting, do not execute Secure Path commands until the Secure Path startup

services have started.

• If you conﬁgure Secure Path devices under volume g roups and reboot the system, the volume

groups are not activated as part of the system’s volume group conﬁguration during boot time. This