HP XP7 RAID Manager Installation and Configuration User Guide (T1610-96065)
Table Of Contents
- XP7 RAID Manager Installation and Configuration User Guide
- Contents
- 1 Installation requirements
- System requirements
- Supported environments
- Supported Business Copy environments
- Supported Continuous Access Synchronous environments
- Supported Continuous Access Asynchronous environments
- Supported Continuous Access Journal environments
- Supported Snapshot environments
- Supported Data Retention environments
- Supported Database Validator environments
- Supported guest OS for VM
- Supported IPv4, IPv6 platforms
- Requirements and restrictions for z/Linux
- Requirements and restrictions for VM
- Porting notice for OpenVMS
- Using RAID Manager with Hitachi and other storage systems
- 2 Installing and configuring RAID Manager
- 3 Upgrading RAID Manager
- 4 Removing RAID Manager
- 5 Troubleshooting
- 6 Support and other resources
- A Fibre-to-SCSI address conversion
- B Sample configuration definition files
- Glossary
- Index
following naming format specifying Serial#/LDEV#/Port# as notation of the command device for
only Windows. For XP7 Storage, set the number to which 300,000 is added to the serial number.
\\.\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 examples
\\.\CMD-30095-250-CL1-A \\.\CMD-30095-250-CL1
dev_name for UNIX
In UNIX SAN environment, there are situations when the device file name is changed, a failover
operation in UNIX SAN environment or every reboot under Linux when the SAN is reconfigured.
The RAID Manager user needs to find NEW "Device Special File" and change HORCM_CMD
described in the RAID Manager configuration file. Thus, RAID Manager supports the following
naming format specifying Serial#/LDEV#/Port#:HINT as notation of the command device for UNIX.
For XP7 Storage, set the number to which 300,000 is added to the serial number:
\\.\CMD-Ser#-ldev#-Port#:HINT
HORCM_CMD
#dev_name dev_name dev_name
\\.\CMD-30095-250-CL1-A-1:/dev/rdsk/
If these names are specified, HORCM finds "\\.\CMD-Serial#-Ldev#-Port#" from the device files
specified by HINT at HORCM start-up. HINT must be specified "directory terminated with '/' on
the device file name" or "directory including device file name pattern" as below, for example:
/dev/rdsk/ → this finds a specified CMD from /dev/rdsk/* /dev/rdsk/c10
→ this finds a specified CMD from /dev/rdsk/c10* /dev/rhdisk → this
finds a specified CMD from /dev/rhdisk*
The device files discovered during HINT are filtered with the following pattern:
• HP-UX: /dev/rdsk/* or /dev/rdisk/disk*
• Solaris: /dev/rdsk/*s2
• AIX: /dev/rhdisk*
• Linux: /dev/sd....
• z/Linux: /dev/sd....
• MPE/iX: /dev/...
• Tru64: /dev/rrz*c or /dev/rdisk/dsk*c or /dev/cport/scp*
• IRIX64: /dev/rdsk/*vol or /dev/rdsk/node_wwn/*vol/*
60 Sample configuration definition files