The swagent log will show this error:
...
VRTSat.CLIENT-IA32 VRTSat.CLIENT-IA64 VRTSat.CLIENT-PA32
VRTSat.CLIENT-PA64 VRTSat.SERVER-PA32
Blowing away old lower case package
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvwx] -e pattern_list...
[-f pattern_file...] [file...]
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvwx] [-e pattern_list...]
-f pattern_file... [file...]
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvwx] pattern [file...]
* Installing fileset "VRTSat.CLIENT-IA32,r=5.0.32.11" (1 of
15).
ERROR: Software "VRTSat" was not found on host
* Installing fileset "VRTSat.CLIENT-IA64,r=5.0.32.11" (2 of
15).
* Installing fileset "VRTSat.CLIENT-PA32,r=5.0.32.11" (3 of
15).
* Installing fileset "VRTSat.CLIENT-PA64,r=5.0.32.11" (4 of
15).
* Installing
fileset "VRTSat.SERVER-PA32,r=5.0.32.11" (5 of
15).
ERROR: Software "VRTSat" was not found on host
....
After the failed installation "swlist -l fileset VRTSat" does not show any version of this package to be installed.
The reason for this error is because some older versions of the VRTSat package were named differently, so the install has to check the various upgrade paths. As earlier/older versions of VRTSat have a different fileset name, the "swinstall" command cannot detect and upgrade these packages directly, so the installer executes a "swmodify" to remove entries of old VRTSat packages. In this case, this command fails when swmodify does not get correct arguments when the installer falsely detects a nonexistent prior version. This leads to the VRTSat package install failure, which may cause the install of the SF to fail.
Since in this case there is no older VRTSat package, the swmodify step is not needed and a workaround is to comment this step out in the preinstall script. The preinstall script is located in: dvd1-hpux1131/depot/catalog/VRTSat/pfiles/preinstall and adding a comment (#) mark at the start of the lines with $SWMODIFY will prevent these commands from being run.
NOTE, this problem will not occur in the 6.0 or newer versions as the VRTSat package has been deprecated.
Applies To
This problem may happen when upgrading from SF (Storage Foundation) 5.0 to 5.1SP1 on HP-UX 11.31 using the installer script.