Installation and Reference Guide HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 (5697-8001, March 2009)

Removing Secure Path software
You can remove Secure Path by using HP’s SD utility or the System Administration Manager (SAM).
When you remove Secure Path, all files, including configuration files, are removed.
You can use SAM or enter the following command to remove Secure Path:
# swremove –x autoreboot=true CPQswsp,r=*
NOTE:
After removing Secure Path, you must reconfigure the array for transparent failover mode and restore
the server to a single-path RAID storage environment. In a single-path configuration, the HSG80
controllers is set to transparent failover mode. See the
HSG80 ACS Solution Software for HP-UX
installation and configuration guide
for details.
If Secure Path is installed on a SAN boot device (EVA LUN), refer to Secure Path Boot Device (EVA
LUN) for further details.
Upgrading Secure Path software
This section describes the requirements and procedures to upgrade Secure Path software, including:
Upgrade requirements
Upgrade preparation
Upgrading from the Web
Upgrade requirements
The following requirements must be met to ensure a successful installation:
At least 100 MB of free disk space is required in the /tmp file system for installation.
The system must have an additional 10 MB of space in /usr and 10 MB in /opt.
Upgrade preparation
Secure Path 3.0F SP2 does not support HSG80 array controllers using ACS 8.6 in SCSI-3 mode. It
still supports ACS 8.6 or later in SCSI-2 mode. Since 3.0F SP4 with ACS 8.7 or later enables the
support of up to 127 LUNs per array, HP recommends that you configure the array for SCSI-3
operation.
If you are upgrading an existing Secure Path 3.0 configuration, and you are adding Enterprise Virtual
Array (EVA) systems to the configuration, perform the upgrade on the existing HSG80-based storage
first. Then, add the HSV110-based storage using the hardware setup described in Secure Path for
Active-Passive disk arrays hardware setup after the Secure Path 3.0F SP4 upgrade is complete and
verified.
This procedure does not change your existing StorageWorks device file assignment or modify any
existing logical volumes. It only adds and attaches all new or unattached LUNs that can be seen by
your server. Depending on the existing target or LUN numbering, it can add these devices in
nonsequential order.
To add and attach the new or unattached LUNs, complete the following steps:
1. Ensure that all users have logged off the server and that all I/O from the server has ceased.
Secure Path for Active-Passive disk arrays70