HP StorageWorks Secure Path V3.0C for Linux and Linux Workgroup Edition Installation and Reference Guide (AA-RU7VD-TE, February 2004)

Installing Secure Path Software
53Secure Path v3.0C for Linux and Linux Workgroup Edition Installation and Reference Guide
If you choose N, the following message displays:
You have chosen not to continue. Exiting...
— The script displays the following for 32-Bit RHEL AS 3.0 if the errata
version is not valid:
Your system is running RHEL AS 32bit. The kernel version is
2.4.21.
The system is not running the errata 9kernel (2.4.21-9.EL).
The system is not running a supported errata version.
Would you like to install anyway? [y/N]
If you choose N, the following message displays:
You have chosen not to continue. Exiting...
— The script displays the following for 64-Bit RHEL AS 3.0 if the errata
version is not valid:
Your system is running RHEL AS 64bit. The kernel version is
2.4.21.
The system is not running the errata 41 kernel
(2.4.21-9.EL).
The system is not running a supported errata version.
Would you like to install anyways? [y/N]
If you choose N, the following message displays:
You have chosen not to continue. Exiting...
If the system has a valid kernel version or if you answer yes to any of the
above questions, the appropriate RPM is installed. An rpm -ivh or an
rpm -ivh --force is issued by the installation script.
An installation log file is created as a result of running the above
command and contains any errors encountered. If the directory
/var/log/h exists on your system, the installation log messages are
placed in /var/log/sp_log. If the /var/log directory does not
exist on your system, a log file named sp_install_results.log is
created in the /root directory.
Check the log file for any errors. If there were no errors, reboot your
system and go to “Using Secure Path persistence software” on page 55 for
more information on sps, the LUN persistence program.
If there were errors during the installation of Secure Path software, you
must fix the problems before proceeding. Refer to “Fibre Channel Device
Software” on page 113 for a complete explanation of possible problem
causes and recovery actions.