Release Notes HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 (5697-8002, March 2009)

Secure Path Manager (spmgr)
The following problems may arise in spmgr for Active-Passive disk arrays:
• If there are several Secure Path devices configured on the system, the Secure Path startup services
can take longer because device scanning is initiated to synchronize Secure Path persistence data.
• If a preferred path to a device is in the Failed state, and you run a spmgr restore –d device
command, the command line displays the prompt only. The path remains in a Failed state and no
path change is made. This is the expected response to the command.
• The spmgr alias command is used to refer to a large cumbersome old name using a shorter
or clearer alias. Reversing the argument order in spmgr alias alias_name old_name results in
the alias replacing the old name. Any command using the old name results in an error. You must
delete the alias for the old name to work correctly.
• The spmgr alias command checks a table of reserved words to prevent you from using words
in an alias that would result in unexpected behavior. However, this list is not comprehensive. Be
careful to avoid using special characters that could be misinterpreted by the shell, such as a
leading “-” or “$.” The current list of reserved words maintained by spmgr are:
add alias client delete display help log notify on off password prefer
quiesce restart restore select set spmgr unalias unprefer
• The spmgr restore –r 0000-0000-0000-0000 command should produce an error for an
invalid WWNN, but instead it successfully restores all preferred paths on all attached arrays just
like the spmgr restore all command.
• If you enable auto-restore using the spmgr set –a on command, and then select a new path
using the spmgr select -p path_instance command, the path remains selected and will
not be auto-restored. Auto-restore returns to the currently active path only if that path has failed
and has been repaired.
• The spmgr addany_arg any_arg WWLUNID command generates the following error message:
Lun should be 0-7
The error message should read:
Unable to locate an unclaimed unit with that World Wide LUN ID.
• The spmgr display –d device command requires a device (c#t#d#) as an argument, but
accepts a WWLUNID as the argument and responds with missing or incorrect data. Use only device
with the –d option.
• The spmgr select and spmgr restart commands occasionally respond with the following
error message:
Error: Invalid Argument
The command completes successfully. If you see this error, verify command success using the
spmgr display command.
• Notification event messages that contain fields for the adapter instance (td#), array WWNN, or LUN
WWLUNID sometimes report either DON’T CARE or * as the identifier. This reporting error has no
impact on Secure Path operation, and specific failure or change parameters can be viewed with
the spmgr display command.
• Using spmgr set -p on|offWWNN, spmgr set -a on|offWWNN, or spmgr set
-b on|offWWNN without the on|off argument, or using spmgr set -finterval without the
interval argument always returns that parameter to the installation default values. Omitting the
on|off argument returns path verification to on, auto-restore to off, load balancing to off,
and the verification interval to 30 seconds.
18