HP HPE XP P9500 User manual

HP StorageWorks
P9000 RAID Manager Installation and
Configuration Guide
Abstract
This guide describes and provides instructions to install and configure HP StorageWorks P9000 RAID Manager Software on
HP StorageWorks P9500 disk arrays. The intended audience is a storage system administrator or authorized service provider
with independent knowledge of HP StorageWorks P9000 disk arrays and the HP StorageWorks Remote Web Console.
HP Part Number: T1610-96026
Published: January 2011
Edition: Third

© Copyright 2010, 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Export Requirements
You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.
Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident
of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.
This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce
Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly
or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified
in the U.S. Export Administration Regulations (15 CFR 744).
Revision History
DescriptionDateEdition
Applies to version 01.24.13 or later.October 2010First
Applies to version 01.24.13 or later.November 2010Second
Applies to version 01.24.16 or later.January 2011Third

Contents
1 Installation requirements..............................................................................5
System requirements..................................................................................................................5
Supported environments............................................................................................................6
Supported Business Copy environments...................................................................................6
Supported Continuous Access Synchronous environments..........................................................7
Supported Continuous Access Asynchronous environments........................................................8
Supported Continuous Access Journal environments..................................................................9
Supported Snapshot environments..........................................................................................9
Supported Data Retention environments................................................................................10
Supported Database Validator environments..........................................................................11
Supported guest OS for VM................................................................................................12
Supported IPv4 and IPv6 platforms.......................................................................................13
Requirements and restrictions for z/Linux...................................................................................14
Requirements and restrictions for VM.........................................................................................15
Restrictions for VMware ESX Server......................................................................................15
Restrictions on AIX VIO.......................................................................................................16
Restrictions on Windows 2008 Hyper-V................................................................................17
About platforms supporting IPv6..........................................................................................18
Library and system call for IPv6.......................................................................................18
Environment variable.....................................................................................................18
Porting notice for OpenVMS....................................................................................................19
Requirements and restrictions for OpenVMS..........................................................................19
Known issues ....................................................................................................................23
Startup procedures using detached process on DCL................................................................24
Command examples in DCL................................................................................................26
Startup procedures in bash..................................................................................................28
Using CCI with Hitachi and other storage systems.......................................................................30
2 Installing and configuring RAID Manager....................................................32
Installing the RAID Manager hardware......................................................................................32
Installing the RAID Manager software.......................................................................................32
UNIX installation................................................................................................................32
Changing the RAID Manager user (UNIX systems).............................................................33
Windows installation..........................................................................................................35
Changing the RAID Manager user (Windows systems).......................................................35
OpenVMS installation........................................................................................................36
Command execution by in-band and out-of-band methods...........................................................37
Setting the command device....................................................................................................38
Setting command device and virtual command device by in-band and out-of-band methods........39
About alternate command devices........................................................................................40
Creating/editing the configuration definition file.........................................................................41
3 Upgrading RAID Manager........................................................................43
Upgrading RAID Manager in a UNIX environment......................................................................43
Upgrading RAID Manager in a Windows environment................................................................43
Upgrading RAID Manager in an OpenVMS environment.............................................................44
4 Removing RAID Manager..........................................................................45
Removing RAID Manager in a UNIX environment........................................................................45
Contents 3

Removing RAID Manager in a Windows environment..................................................................45
Removing RAID Manager in an OpenVMS environment...............................................................46
Removing the RAID Manager components.................................................................................46
5 Troubleshooting........................................................................................47
Troubleshooting......................................................................................................................47
6 Support and other resources......................................................................48
Contacting HP........................................................................................................................48
Subscription service............................................................................................................48
Related information.................................................................................................................48
HP websites......................................................................................................................48
Conventions for storage capacity values....................................................................................49
Typographic conventions.........................................................................................................49
HP product documentation survey.............................................................................................50
A Fibre-to-SCSI address conversion................................................................51
Fibre-to-SCSI address conversion ..............................................................................................51
LUN configurations on the RAID storage systems.........................................................................52
Fibre address conversion tables................................................................................................53
B Sample configuration definition files............................................................56
Sample configuration definition files..........................................................................................56
Examples of RAID Manager configurations................................................................................65
Configuration definition for cascading volume pairs...............................................................85
Correspondence of the configuration file and mirror descriptors...............................................85
Cascade function and configuration files...............................................................................87
Business Copy..............................................................................................................87
Cascading connections for Continuous Access Synchronous and Business Copy....................89
Glossary....................................................................................................92
Index.........................................................................................................94
4 Contents

1 Installation requirements
Unless otherwise specified, the term P9000 in this guide refers to the following disk array:
•P9500 Disk Array
The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.
This chapter describes Installation requirements.
System requirements
RAID Manager operations involve the RAID Manager software on the UNIX/PC server host, the
command device(s) on the RAID storage system(s), and the logical volumes on the RAID storage
system(s).
The system requirements for RAID Manager are:
•RAID Manager software product. The RAID Manager software is supplied on CD-ROM or
diskette. The RAID Manager software files take up 2.5 MB of space. The log files can take up
to 3 MB of space.
•Host platforms. RAID Manager is supported on the following host platforms. See Table 2 (page
7) –Table 10 (page 13) for detailed information on supported OS versions.
◦Solaris, Solaris/x86
◦HP-UX
◦AIX
◦Linux, Linux/IA64
◦VMware
◦Windows
◦OpenVMS, OpenVMS/IA
◦DYNIX/ptx
◦IRIX
•The configuration setting command (raidcom command) supports the following host platforms:
HP-UX◦
◦Windows NT
◦Windows NT/x64
◦Solaris
◦Solaris/x86
◦AIX
◦Linux
◦Linux/IA64
For details about the configuration setting command (raidcom command), see the HP
StorageWorks P9000 RAID Manager User Guide and the HP StorageWorks P9000 RAID
Manager Reference Guide.
•Host access: Root/administrator access to the host is required to perform RAID Manager
operations.
System requirements 5

•Host memory:
Static memory capacity: minimum = 300 KB, maximum = 500 KB◦
◦Dynamic memory capacity (set in HORCM_CONF): maximum = 500 KB per unit ID
•Failover: RAID Manager supports several failover products, including FirstWatch,
MC/ServiceGuard, HACMP, TruCluster, and ptx/CLUSTERS. See Table 2 (page 7) –
Table 10 (page 13) for detailed information.
•High availability (HA) configurations: The system that runs and operates Continuous Access
Synchronous in an HA configuration must be a duplex system having a hot standby
configuration or mutual hot standby (mutual takeover) configuration. The remote copy system
must be designed for remote backup among servers and configured so that servers cannot
share the primary and secondary volumes at the same time. The information in this document
does not apply to fault-tolerant system configurations such as Oracle Parallel Server (OPS) in
which nodes execute parallel accesses. However, two or more nodes can share the primary
volumes of the shared OPS database, and must use the secondary volumes as backup volumes.
◦Host servers that are combined when paired logical volumes are defined should run on
operating systems of the same architecture. If not, one host may not be able to recognize
a paired volume of another host, even though HORCM can run properly.
•RAID storage systems:
Command Device: The RAID Manager command device must be defined and accessed
as a raw device (no file system, no mount operation).
◦
◦License keys: The option for each program product to be used must be installed and
enabled on the RAID storage system.
◦Snapshot: Bidirectional swap must be enabled between the primary and secondary
volumes. The port modes (for example, LCP, RCP, RCU target) and MCU-RCU paths must
be defined.
◦Continuous Access Journal: The path between the CUs must be set using Remote Web
Console, and bidirectional swap must be enabled between the primary and secondary
volumes.
◦Snapshot: Both Business Copy and Snapshot must be installed and enabled on the RAID
storage system.
•Other RAID storage systems: see “Using CCI with Hitachi and other storage systems” (page 30).
Supported environments
This section specifies the supported operating systems, failover software, and I/O interfaces for
data management operations using RAID Manager. For the latest information on host software
support for RAID Manager, please contact your HP account team.
Supported Business Copy environments
Table 1 Supported platforms for Business Copy
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/FibreVxVMFirst WatchSolaris 2.5Oracle
FibreVxVM–Solaris 10 /x86
6 Installation requirements

Table 1 Supported platforms for Business Copy (continued)
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/FibreLVM, SLVMMC/Service
Guard
HP-UX 10.20/11.0/11.2xHP
FibreLVM, SLVMMC/Service
Guard
HP-UX 11.2x on IA64*
SCSILSMTruClusterDigital UNIX 4.0
SCSI/FibreLSMTruClusterTru64 UNIX 5.0
Fibre––OpenVMS 7.3-1
SCSI/FibreLVMptx/ClusterDYNIX/ptx 4.4IBM
SCSI/FibreLVMHACMPAIX 4.3
Fibre (FCP)––z/Linux (SUSE 8) For restrictions on
z/Linux, see “Requirements and restrictions
for z/Linux” (page 14).
FibreLDMMSCSWindows NT 4.0; Windows 2000, 2003,
2008
Microsoft
FibreLDMMSCSWindows 2003/2008 on IA64*
Windows 2003/2008 on EM64T
SCSI/Fibre**––Red Hat Linux 6.0, 7.0, 8.0
AS/ES 2.1, 3.0, 4.0, 5.0
Red Hat
Fibre––AS/ES 2.1, 3.0 Update 2, 4.0, 5.0 on
EM64T / IA64*
SCSI/Fibre––IRIX64 6.5SGI
* IA64: using IA-32EL on IA64 (except RAID Manager for Linux/IA64)
** See the HP StorageWorks P9000 RAID Manager User Guide about RHEL 4.0 using Kernel 2.6.9.XX.
Supported Continuous Access Synchronous environments
Table 2 Supported platforms for Continuous Access Synchronous
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/FibreVxVMFirst WatchSolaris 2.5Oracle
FibreVxVM–Solaris 10 /x86
SCSI/FibreLVM, SLVMMC/Service
Guard
HP-UX 10.20/11.0/11.2xHP
FibreLVM, SLVMMC/Service
Guard
HP-UX 11.2x on IA64*
SCSILSMTruClusterDigital UNIX 4.0
SCSI/FibreLSMTruClusterTru64 UNIX 5.0
Fibre––OpenVMS 7.3-1
Supported environments 7

Table 2 Supported platforms for Continuous Access Synchronous (continued)
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/FibreLVMptx/CusterDYNIX/ptx 4.4IBM
SCSI/FibreLVMHACMPAIX 4.3
Fibre (FCP)––z/Linux (SUSE 8)
For restrictions on z/Linux, see
“Requirements and restrictions for
z/Linux” (page 14).
FibreLDMMSCSWindows NT 4.0; Windows 2000,
2003, 2008
Microsoft
FibreLDMMSCSWindows 2003/2008 on IA64*
Windows 2003/2008 on EM64T
SCSI/Fibre**––Red Hat Linux 6.0, 7.0, 8.0
AS/ES 2.1, 3.0, 4.0, 5.0
Red Hat
Fibre––AS/ES 2.1, 3.0 Update 2, 4.0, 5.0 on
EM64T / IA64*
SCSI/Fibre––IRIX64 6.5SGI
* IA64: using IA-32EL on IA64 (except RAID Manager for Linux/IA64)
** See “Troubleshooting” (page 47) about RHEL 4.0 using Kernel 2.6.9.XX.
Supported Continuous Access Asynchronous environments
Table 3 Supported platforms for Continuous Access Asynchronous
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/FibreVxVMFirst WatchSolaris 2.5Oracle
FibreVxVM–Solaris 10 /x86
SCSI/FibreLVM, SLVMMC/Service
Guard
HP-UX 10.20/11.0/11.2xHP
FibreLVM, SLVMMC/Service
Guard
HP-UX 11.2x on IA64*
SCSILSMTruClusterDigital UNIX 4.0
SCSI/FibreLSMTruClusterTru64 UNIX 5.0
Fibre––OpenVMS 7.3-1
SCSI/FibreLVMptx/CusterDYNIX/ptx 4.4IBM
SCSI/FibreLVMHACMPAIX 4.3
Fibre (FCP)––z/Linux (SUSE 8)
For restrictions on z/Linux, see
“Requirements and restrictions for
z/Linux” (page 14).
FibreLDMMSCSWindows NT 4.0; Windows 2000,
2003, 2008
Microsoft
FibreLDMMSCSWindows 2003/2008 on IA64*
Windows 2003/2008 on EM64T
8 Installation requirements

Table 3 Supported platforms for Continuous Access Asynchronous (continued)
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
SCSI/Fibre**––Red Hat Linux 6.0, 7.0, 8.0
AS/ES 2.1, 3.0, 4.0, 5.0
Red Hat
Fibre––AS/ES 2.1, 3.0 Update 2, 4.0, 5.0
on EM64T / IA64*
SCSI/Fibre––IRIX64 6.5SGI
* IA64: using IA-32EL on IA64 (except RAID Manager for Linux/IA64)
** See “Troubleshooting” (page 47) about RHEL 4.0 using Kernel 2.6.9.XX.
Supported Continuous Access Journal environments
Table 4 Supported platforms for Continuous Access Journal
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
FibreVxVMVCSSolaris 2.8Oracle
FibreVxVM–Solaris 10 /x86
FibreLVM, SLVMMC/Service
Guard
HP-UX 11.0/11.2xHP
FibreLVM, SLVMMC/Service
Guard
HP-UX 11.2x on IA64*
FibreLVMHACMPAIX 5.1IBM
FibreLDMMSCSWindows 2000, 2003, 2008Microsoft
FibreLDMMSCSWindows 2003/2008 on IA64*
Windows 2003/2008 on EM64T
Fibre**––Red Hat Linux 6.0, 7.0, 8.0
AS/ES 2.1, 3.0, 4.0, 5.0
Red Hat
Fibre**––AS/ES 2.1, 3.0 Update 2, 4.0, 5.0 on
EM64T / IA64*
FibreLSMTruClusterTru64 UNIX 5.0HP
FibreLSMTruClusterOpenVMS 7.3-1
Fibre––IRIX 64 6.5SGI
* IA64: using IA-32EL on IA64 (except RAID Manager for Linux/IA64)
** See “Troubleshooting” (page 47) about RHEL 4.0 using Kernel 2.6.9.XX.
Supported Snapshot environments
Table 5 Supported platforms for Snapshot
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
FibreVxVM–Solaris 2.8Oracle
FibreVxVM–Solaris 10 /x86
FibreLVM, SLVM–HP-UX 11.0/11.2xHP
FibreLVM, SLVM–HP-UX 11.2x on IA64*
Supported environments 9

Table 5 Supported platforms for Snapshot (continued)
I/O interfaceVolume ManagerFailover softwareOperating systemVendor
FibreLVM–AIX 5.1IBM
FibreLDM–Windows 2000, 2003, 2008Microsoft
FibreLDM–Windows 2003/2008 on IA64*
Windows 2003/2008 on EM64T
Fibre**––Red Hat Linux 6.0, 7.0, 8.0
AS/ES 2.1, 3.0, 4.0, 5.0
Red Hat
Fibre**––AS/ES 2.1, 3.0 Update 2, 4.0, 5.0
on EM64T / IA64*
FibreLSM–Tru64 UNIX 5.0HP
Fibre––OpenVMS 7.3-1
Fibre––IRIX64 6.5SGI
* IA64: using IA-32EL on IA64 (except RAID Manager for Linux/IA64)
** See “Troubleshooting” (page 47) about RHEL 4.0 using Kernel 2.6.9.XX.
Supported Data Retention environments
Table 6 Supported platforms for Data Retention
I/O interfaceVolume ManagerOperating systemVendor
SCSI/FibreVxVMSolaris 2.5Oracle
FibreVxVMSolaris 10 /x86
SCSI/FibreLVM, SLVMHP-UX 10.20/11.0/11.2xHP
FibreLVM, SLVMHP-UX 11.2x on IA64*
SCSILSMDigital UNIX 4.0
SCSI/FibreLSMTru64 UNIX 5.0
Fibre–OpenVMS 7.3-1
SCSI/FibreLVMDYNIX/ptx 4.4IBM
SCSI/FibreLVMAIX 4.3
Fibre (FCP)–z/Linux (SUSE 8)
For restrictions on z/Linux, see “Requirements and restrictions
for z/Linux” (page 14).
iSCSI/FibreLDMWindows NT4.0/2000/2003 SP1Microsoft
FibreLDMWindows 2003 SP1 on IA64*
Windows 2003 SP1 on EM64T
SCSI/Fibre**–Red Hat Linux
6.0/7.0/AS2.1, 3.0, 4.0
Red Hat
Fibre–AS2.1, 3.0 Update 2, 4.0 on IA64*
AS 4.0 on EM64T
10 Installation requirements

Table 6 Supported platforms for Data Retention (continued)
I/O interfaceVolume ManagerOperating systemVendor
SCSI/Fibre–IRIX64 6.5SGI
* IA64: using IA-32EL on IA64
** See “Troubleshooting” (page 47) for important information about RHEL 4.0 using kernel 2.6.9.XX.
Supported Database Validator environments
Table 7 Supported platforms for Database Validator
I/O interfaceVolume ManagerOperating systemVendor
SCSI/FibreVxVMSolaris 2.5Oracle
FibreVxVMSolaris 10 /x86
SCSI/FibreLVM, SLVMHP-UX 10.20/11.0/11.2xHP
FibreLVM, SLVMHP-UX 11.2x on IA64*
SCSILSMDigital UNIX 4.0
SCSI/FibreLSMTru64 UNIX 5.0
Fibre–OpenVMS 7.3-1
SCSI/FibreLVMDYNIX/ptx 4.4IBM
SCSI/FibreLVMAIX 4.3
Fibre (FCP)–z/Linux (SUSE 8)
For restrictions on z/Linux, see “Requirements and restrictions
for z/Linux” (page 14).
iSCSI/FibreLDMWindows NT4.0/2000/2003 SP1Microsoft
FibreLDMWindows 2003 SP1 on IA64*
Windows 2003 SP1 on EM64T
SCSI/Fibre**–Red Hat Linux
6.0/7.0/AS2.1, 3.0, 4.0
Red Hat
Fibre–AS2.1, 3.0 Update 2, 4.0 on IA64*
AS 4.0 on EM64T
SCSI/Fibre–IRIX64 6.5SGI
* IA64: using IA-32EL on IA64
** See “Troubleshooting” (page 47) for important information about RHEL 4.0 using kernel 2.6.9.XX.
Supported environments 11

Supported guest OS for VM
Table 8 Supported guest OS for VM
I/O interfaceVolume mappingRAID Manager support
confirmation
Guest OSLayerVM Vendor
--ConfirmedWindows 2008 R2GuestVMware ESX Server
2.5.1 or later using
Linux Kernel 2.4.9
*1
FibreRDM*ConfirmedWindows 2003 SP1
FibreRDM*UnconfirmedWindows 2000
Server
--UnconfirmedWindows NT 4.0
FibreRDM*ConfirmedRHAS 3.0
--UnconfirmedSLES 9.0
FibreRDM*ConfirmedSolaris 10 u3 (x86)
FibreDirectConfirmedLinux Kernel 2.4.9SVC
FibrePhysical modeConfirmedAIX 5.3ClientIBM AIX 5.3 VIO
Server *2
FibreDirectSee (4) in “Restrictions on
AIX VIO” (page 16)
AIX 5.3Server
FibrePath-thruConfirmedWindows 2003 SP2ChildWindows 2008
Hyper-V *3
FibrePath-thruConfirmedWindows 2008
--UnconfirmedWindows 2000 SP4
FibrePath-thruConfirmedSLES10 SP2
FibreDirectConfirmedWindows 2008Parent
* RDM: Raw Device Mapping using Physical Compatibility Mode.
1: See “Restrictions for VMware ESX Server” (page 15).
2: See “Restrictions on AIX VIO” (page 16).
3: See “Restrictions on Windows 2008 Hyper-V” (page 17).
12 Installation requirements

Supported IPv4 and IPv6 platforms
Table 9 Supported platforms: IPv4 vs. IPv6
RAID Manager / IPv6 *1 IPv6
IPv6
OpenVMSTru64LinuxWindowsAIXSolarisHP-UX
N/AAVAVAVAVAVAVHP-UXRAID
Manager /
IPv6 N/AAVAVAVAVAV–Solaris
N/AAVAVAVAV––AIX
N/AAVAVAV–––Windows
N/AAVAV––––Linux
N/AAV–––––Tru64
AV––––––OpenVMS
1: See “About platforms supporting IPv6” (page 18).
AV: Available for communicating with different platforms.
N/A: Not Applicable (Windows LH does not support IPv4 mapped IPv6).
Table 10 Supported platforms: IPv4 vs. IPv6
RAID Manager / IPv6 *1 IPv6
IPv4
OpenVMSTru64LinuxWindowsAIXSolarisHP-UX
N/AAVAVN/AAVAVAVHP-UXRAID
Manager /
IPv4 N/AAVAVN/AAVAVAVSolaris
N/AAVAVN/AAVAVAVAIX
N/AAVAVN/AAVAVAVWindows
N/AAVAVN/AAVAVAVLinux
N/AAVAVN/AAVAVAVTru64
AVAVAVN/AAVAVAVOpenVMS
N/AAVAVN/AAVAVAVIRIX64
N/AN/AN/AN/AN/AN/AN/ADYNIX
1: See “About platforms supporting IPv6” (page 18).
AV: Available for communicating with different platforms.
N/A: Not Applicable (Windows LH does not support IPv4 mapped IPv6).
Minimum platform versions for RAID Manager/IPv6 support:
•HP-UX: HP-UX 11.23 (PA/IA) or later
•Solaris: Solaris 8/Sparc or later, Solaris 10/x86/64 or later
•AIX: AIX 5.1 or later
•Windows: Windows 2008(LH), Windows 2003 + IPv6 Install
•Linux: Linux Kernel 2.4 (RH8.0) or later
•Tru64: Tru64 v5.1A or later. Note that v5.1A does not support the getaddrinfo() function, so this must be specified
by IP address directly.
•OpenVMS: OpenVMS 8.3 or later
Supported environments 13

Requirements and restrictions for z/Linux
In the following example, z/Linux defines the Open Volumes that are connected to FCP as /dev/sd*.
Also, the mainframe volumes (3390-xx) that are connected to FICON are defined as /dev/dasd*.
Figure 1 Example of a RAID Manager configuration on z/Linux
The restrictions for using RAID Manager with z/Linux are:
•Command device. RAID Manager uses a SCSI Path-through driver to access the command
device. As such, the command device must be connected through FCP adaptors.
•Open Volumes via FCP. You can control the Business Copy and Continuous Access Synchronous
pair operations without any restrictions.
•Mainframe (3390-9A) Volumes via FICON. You cannot control the volumes (3390-9A) that
are directly connected to FICON for Business Copy pair operations. Also, mainframe volumes
must be mapped to a CHF port to address target volumes using a command device, as shown
in Figure 1 (page 14). The mainframe volume does not have to be connected to an FCP
adaptor.
Business Copy supports only 3390-9A multiplatform volumes. Continuous Access Synchronous
does not support multiplatform volumes (including 3390-9A) via FICON.
•Volume discovery via FICON. The inqraid command discovers the FCP volume information by
using SCSI inquiry. FICON volumes can be discovered only by using RAID Manager to convert
the mainframe interface (Read_device_characteristics or Read_configuration_data) to SCSI
Inquiry. As such, the information that is required to run the inqraid command cannot be
implemented, as shown in the following example:
sles8z:/HORCM/usr/bin# ls /dev/dasd* | ./inqraid
/dev/dasda -> [ST] Unknown Ser = 1920 LDEV = 4 [HTC ] [0704_3390_0A]
/dev/dasdaa -> [ST] Unknown Ser = 62724 LDEV =4120 [HTC ] [C018_3390_0A]
/dev/dasdab -> [ST] Unknown Ser = 62724 LDEV =4121 [HTC ] [C019_3390_0A]
sles8z:/HORCM/usr/bin# ls /dev/dasd* | ./inqraid -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
dasda - 1920 4 - - 00C0 - 0704_3390_0A
dasdaa - 62724 4120 - - 9810 - C018_3390_0A
dasdab - 62724 4121 - - 9810 - C019_3390_0A
14 Installation requirements

In the previous example, the Product_ID, C019_3390_0A, has the following associations:
•C019 indicates the Devno
•3390 indicates the Dev_type
•0A indicates the Dev_model
The following commands cannot be used because there is no PORT information:
•raidscan -pd <device>, raidar -pd <device>, raidvchkscan -pd <device>
•raidscan -find [conf] , mkconf
Requirements and restrictions for VM
Restrictions for VMware ESX Server
Whether RAID Manager (RM) runs or not depends on the support of guest OS by VMware. In
addition, the guest OS depends on VMware support of virtual H/W (HBA). Therefore, the following
guest OS and restrictions must be followed when using RAID Manager on VMware.
Figure 2 RAID Manager configuration on guest OS/VMware
The restrictions for using RAID Manager with VMware are:
1. Guest OS. RAID Manager needs to use guest OS that is supported by RAID Manager, and
also VMware supported guest OS (for example, Windows Server 2003, Red Hat Linux, SUSE
Linux). See “Supported guest OS for VM” (page 12).
2. Command device. RAID Manager uses SCSI path-through driver to access the command device.
Therefore, the command device must be mapped as Raw Device Mapping using Physical
Compatibility Mode. At least one command device must be assigned for each guest OS.
3. RAID Manager (RM) instance numbers among different guest OS must be different, even if
the command is assigned for each guest OS, because the command device cannot distinguish
a difference among guest OS due to the same WWN as VMHBA.
4. About invisible Lun.Assigned Lun for the guest OS must be visible from SCSI Inquiry when
VMware (host OS) is started. For example, the S-VOL on VSS is used as Read Only and
Hidden, and this S-VOL is hidden from SCSI Inquiry. If VMware (host OS) is started on this
volume state, the host OS will hang.
5. Lun sharing between Guest and Host OS. It is not supported to share a command device or a
normal Lun between guest OS and host OS.
Requirements and restrictions for VM 15

6. About running on SVC. The ESX Server 3.0 SVC (service console) is a limited distribution of
Linux based on Red Hat Enterprise Linux 3, Update 6 (RHEL 3 U6). The service console provides
an execution environment to monitor and administer the entire ESX Server host. The RAID
Manager user can run RAID Manager by installing “RAID Manager for Linux” on SVC. The
volume mapping (/dev/sd) on SVC is a physical connection without converting SCSI Inquiry,
so RAID Manager will perform like running on Linux regardless of guest OS. However, VMware
protects the service console with a firewall. According to current documentation, the firewall
allows only PORT# 902,80,443,22(SSH) and ICMP(ping), DHCP, DNS as defaults, so the
RAID Manager user must enable a PORT for RAID Manager (HORCM) using the iptables
command.
Restrictions on AIX VIO
Whether RAID Manager can function completely or not depends on how VIO client/server supports
virtual HBA(vscsi), and there are some restrictions in the case of volume discovery. The following
figure shows RAID Manager configuration on an AIX VIO client.
Figure 3 RAID Manager configuration on VIO client
The restrictions for using RAID Manager on AIX VIO are as follows:
1. Command device. RAID Manager uses the SCSI Path-through driver for accessing the command
device. Therefore, the command device must be mapped as RAW device of Physical Mapping
Mode. At least one command device must be assigned for each VIO Client. The RAID Manager
instance numbers among different VIO Clients must be different, even if the command is
assigned for each VIO Client, because the command device cannot distinguish between VIO
Clients due to use of the same WWN via vscsi.
2. LUN sharing between VIO Server and VIO Clients. It is not possible to share a command device
between VIO Server and VIO Clients, and a normal Lun also cannot be shared between VIO
Server and VIO Clients.
3. Volume discovery via vscsi on VIO Client. The inqraid command discovers the volume
information by using SCSI inquiry, but VIO Client cannot report the real SCSI inquiry (Page0
and Page83) as shown below.
Example for inqraid command:
lsdev -Cc disk | /HORCM/usr/bin/inqraid
hdisk0 -> NOT supported INQ. [AIX ] [VDASD ]
hdisk1 -> NOT supported INQ. [AIX ] [VDASD ]
16 Installation requirements

hdisk2 -> NOT supported INQ. [AIX ] [VDASD ]
:
:
hdisk19 -> NOT supported INQ. [AIX ] [VDASD ]
The following commands discover the volumes by issuing SCSI inquiry. These commands
cannot be used, because there is no port/LDEV for RAID information.
raidscan -pd <device>,raidar -pd <device>,raidvchkscan -pd <device>
raidscan -find [conf] , mkconf.sh,inqraid
pairxxx -d[g] <device>,raidvchkdsp -d[g] <device>,raidvchkset -d[g] <device>
\\.\CMD-Serial#-LDEV#-Port#:/dev/rhdisk on horcm.conf
Therefore, you need to know the volume mapping information (/dev/rhdisk) on the VIO Client
by referring to the physical volume mapping through the VIO Server.
4. About running on VIO Server. The volume mapping ( /dev/rhdisk) on a VIO Server is a
physical connection without converting SCSI Inquiry, so RAID Manager will perform as if
running on AIX 5.3. However, IBM does not allow running applications in the VIO server.
Since commands or scripts would have to be run outside the restricted shell, it may be necessary
to get IBM approval to run in the VIO server. So you would have to change your scripts to
run on a VIO server to issue the oem_setup_env command to access the nonrestricted shell.
Restrictions on Windows 2008 Hyper-V
Whether RAID Manager can perform or not depends on the support of the guest OS by Windows
Hyper-V, and then the guest OS depends on how Hyper-V supports front-end SCSI interfaces.
Figure 4 RAID Manager configuration on Hyper-V
The restrictions for using RAID Manager on Hyper-V are as follows:
1. Guest OS. RAID Manager needs to use the guest OS that is supported by RAID Manager and
also the Hyper-V supported guest OS (for example, Windows Server 2003/2008, SUSE
Linux). See Table 8 (page 12) for details.
2. Command device. RAID Manager uses the SCSI path-through driver to access the command
device. Therefore the command device must be mapped as RAW device of the path-through
disk. At least one command device must be assigned for each guest OS (Child Partition).
The RM instance number among different guest OSs must be used as a different instance
number even if the command is assigned for each guest OS. This is because the command
device cannot distinguish a difference among the guest OSs because the same WWN via
Fscsi is used.
Requirements and restrictions for VM 17

3. Lun sharing between guest OS and console OS. It is not possible to share a command device
as well as a normal Lun between a guest OS and a console OS.
4. Running RAID Manager on Console OS. The console OS (management OS) is a limited
Windows, like Windows 2008 Server Core, and the Windows standard driver is used. Also
the console OS provides an execution environment to monitor and administer the entire Hyper-V
host.
Therefore, you can run RAID Manager by installing “RAID Manager for Windows NT” on the
console OS. In that case, the RAID Manager (RM) instance number between the console OS
and the guest OS must be a different instance number, even if the command is assigned for
each console and guest OS.
About platforms supporting IPv6
Library and system call for IPv6
RAID Manager uses the following functions of IPv6 library to get and convert from hostname to
IPv6 address.
•IPv6 library to resolve hostname and IPv6 address:
getaddrinfo()◦
◦inet_pton()
◦inet_ntop()
•Socket System call to communicate using UDP/IPv6:
socket(AF_INET6)◦
◦bind(), sendmsg(), sendto(), rcvmsg(), recvfrom()…
If RAID Manager links above function in the object(exe), a core dump may occur if an OLD platform
(for example, Windows NT, HP-UX 10.20, Solaris 5) does not support it. So RAID Manager links
dynamically above functions by resolving the symbol after determining whether the shared library
and function for IPv6 exists. It depends on supporting of the platform whether RAID Manager can
support IPv6 or not. If platform does not support IPv6 library, then RAID Manager uses its own
internal function corresponding to “inet_pton(),inet_ntop()”; in this case, IPv6 address is not allowed
to describe hostname.
Figure 5 Library and system call for IPv6
Environment variable
RAID Manager loads and links the library for IPv6 by specifying a PATH as follows.
For Windows systems: Ws2_32.dll
18 Installation requirements

For HP-UX (PA/IA) systems: /usr/lib/libc.sl
However, RAID Manager may need to specify a different PATH to use the library for IPv6. After
this consideration, RAID Manager also supports the following environment variables for specifying
a PATH:
•$IPV6_DLLPATH (valid for only HP-UX, Windows): This variable is used to change the default
PATH for loading the Library for IPv6. For example:
export IPV6_DLLPATH=/usr/lib/hpux32/lib.so
horcmstart.sh 10
•$IPV6_GET_ADDR: This variable is used to change “AI_PASSIVE” value as default for specifying
to the getaddrinfo() function for IPv6. For example:
export IPV6_GET_ADDR=9
horcmstart.sh 10
HORCM startup log
Support level of IPv6 feature depends on the platform and OS version. In certain OS platform
environments, RAID Manager cannot perform IPv6 communication completely, so RAID Manager
logs the results of whether the OS environment supports the IPv6 feature or not.
/HORCM/log/curlog/horcm_HOST NAME.log
*****************************************************************************
- HORCM STARTUP LOG - Fri Aug 31 19:09:24 2007
*****************************************************************************
19:09:24-cc2ec-02187- horcmgr started on Fri Aug 31 19:09:24 2007
:
:19:09:25-3f3f7-02188- ******** starts Loading library for IPv6 *******[ AF_INET6 = 26, AI_PASSIVE = 1 ]19:09:25-47ca1-02188- dlsym() :
Symbl = 'getaddrinfo' : dlsym: symbol "getaddrinfo" not found in "/etc/horcmgr"getaddrinfo() :
Unlinked on itselfinet_pton() : Linked on itselfinet_ntop() : Linked on itself19:09:25-5ab3e-02188- ********
finished Loading library **************:HORCM set to IPv6 ( INET6 value = 26)
:
Porting notice for OpenVMS
In the OpenVMS, the system call on UNIX is supported as the functions of CRTL (C Run Time Library)
on the user process. Also the CRTL for OpenVMS does not support the POSIX and POSIX Shell fully
as does UNIX. In addition, RAID Manager uses the UNIX domain socket for IPC (Inter Process
Communication), but OpenVMS does not support the AF_UNIX socket. As an alternate method,
RAID Manager accomplishes IPC between RAID Manager and HORCM daemon by using the
Mailbox driver on OpenVMS.
Therefore, RAID Manager has the following restrictions in porting for OpenVMS.
Requirements and restrictions for OpenVMS
(1) Version of OpenVMS
RAID Manager uses the CRTL and needs the following version supported on the ROOT directory
for POSIX.
•OpenVMS Version 7.3-1 or later
•CRTL version must be installed prior to running RAID Manager. (Compaq C V6.5-001 was
used in testing.)
(2) Defining the SYS$POSIX_ROOT
RAID Manager requires that POSIX_ROOT is existing on the system, so you must define the
POSIX_ROOT before running RAID Manager. For example:
$ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT “Device:[directory]”
where Device:[directory] is defined as SYS$POSIX_ROOT
Porting notice for OpenVMS 19

(3) IPC method using MailBox driver
As an alternate method of the UNIX domain socket for IPC (Inter Process Communication), RAID
Manager use the mailbox driver to enable the communication between RAID Manager and HORCM.
Therefore, if RAID Manager and HORCM are executing in different jobs (different terminal), then
you must redefine LNM$TEMPORARY_MAILBOX in the LNM$PROCESS_DIRECTORY table as follows:
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
(4) Startup method for HORCM daemon
HORCM can start as the daemon process from a UNIX Shell. But in the case of ‘vfork’ of CRTL, if
a parent process has exit() then a child process also ends at the same time. In other words it looks
that OpenVMS cannot make a daemon process from the POSIX program. Therefore, horcmstart.exe
has been changed to wait until HORCM has been exiting by horcmshutdown.exe after startup of
the horcmgr. According to the rule for creating process in OpenVMS, to start up the horcmstart.exe
is to create the detached process or Batch JOB by using DCL command, as this method closely
resembles the horcmd process on UNIX.
For example, using the Detached process:
If you want to have the HORCM daemon running in the background, you need to make the
Detached LOGINOUT.EXE Process by using the ‘RUN /DETACHED’ command of the OpenVMS,
and need to make the commands file for LOGINOUT.EXE.
The following are examples of “loginhorcm*.com” file given to SYS$INPUT for LOGINOUT.EXE,
and are examples that “VMS4$DKB100:[SYS0.SYSMGR.]” was defined as SYS$POSIX_ROOT.
loginhorcm0.com
$ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT "VMS4$DKB100:[SYS0.SYSMGR.]"
$ DEFINE DCL$PATH SYS$POSIX_ROOT:[horcm.usr.bin],SYS$POSIX_ROOT:[horcm.etc]
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
$ horcmstart 0
loginhorcm1.com
$ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT "VMS4$DKB100:[SYS0.SYSMGR.]"
$ DEFINE DCL$PATH SYS$POSIX_ROOT:[horcm.usr.bin],SYS$POSIX_ROOT:[horcm.etc]
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
$ horcmstart 1
$ run /DETACHED SYS$SYSTEM:LOGINOUT.EXE /PROCESS_NAME=horcm0 -
_$ /INPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]loginhorcm0.com -
_$ /OUTPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run0.out -
_$ /ERROR=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run0.err
%RUN-S-PROC_ID, identification of created process is 00004160
$
$
$$ run /DETACHED SYS$SYSTEM:LOGINOUT.EXE /PROCESS_NAME=horcm1 -
_$ /INPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]loginhorcm1.com -
_$ /OUTPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run1.out -
_$ /ERROR=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run1.err
%RUN-S-PROC_ID, identification of created process is 00004166
You can also verify that the HORCM daemon is running as Detached Process by using the show
process command.
$ show process horcm0
25-MAR-2003 23:27:27.72 User: SYSTEM Process ID: 00004160
Node: VMS4 Process name: "HORCM0"
Terminal:
User Identifier: [SYSTEM]
Base priority: 4
Default file spec: Not available
Number of Kthreads: 1
Soft CPU Affinity: off
$$ horcmshutdown 0 1
inst 0:
20 Installation requirements