HP XP RAID Manager Software User Manual
Page 27
Figure 14 Configuration and Unit IDs for Multiple Storage systems
dev_name for Windows
In Windows SAN environment, “Volume{guid}” will be changed on every re-boot under
MSCS/Windows2k3, if Windows finds the same signature on the command device connected
with Multi-Path.Therefore, find NEW “Volume{guid}”, and change “Volume{guid}” described in
the RAID Manager configuration file. Thus, RAID Manager supports the following naming format
specifying Serial#/LDEV#/Port# as notation of the command device for only Windows.
\\.\CMD-Ser#-ldev#-Port#
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-30095-250-CL1-A
To allow more flexibility, RAID Manager allows the following format.
•
For minimum specification
Specifies to use any command device for Serial#30095 \\.\CMD-30095 If Windows has
two different array models that share the same serial number, fully define the serial number,
ldev#, port and host group for the CMDDEV.
•
For under Multi Path Driver
Specifies to use any port as the command device for Serial#30095, LDEV#250
\\.\CMD-30095-250
•
For full specification
Specifies the command device for Serial#30095, LDEV#250 connected to Port CL1-A, Host
group#1 \\.\CMD-30095-250-CL1-A-1
•
Other example
\\.\CMD-30095-250-CL1-A
\\.\CMD-30095-250-CL1
dev_name for UNIX
In the UNIX SAN environment, a device file name is changed at the failover operation under the
UNIX SAN environment, or each reboot process under the Linux when the SAM is reconfigured.
RAID Manager user is required to change the HORCM_CMD described in the RAID Manager
configuration file by searching new “Device special file”. Therefore, RAID Manager supports the
following naming format to specify “Serial#/LDEV#/Port#:HINT” as an expression way of command
device for UNIX.
\\.\CMD-Ser#-ldev#-Port#:HINT
RAID Manager instance components on the host server
27