Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.01.00.00

6. If the Raid Manager protection facility is enabled, set the HORCPERM environment variable to
the pathname of the HORCM permission file, then export the variable.
For example:
# export HORCMPERM=/etc/horcmperm0.conf
The RAID Manager protection facility restricts volume control operations to volumes that the
host is allowed to see, with or without host-based LUN security and to volumes that are listed
in the configuration file.
For more information about RAID Manager protection facility, see HP StorageWorks P9000
RAID Manager User's Guide or HP StorageWorks XP RAID Manager User's Guide available
at http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp.
If the Raid Manager protection facility is not used or disabled, export the HORCPERM
environment variable to MGRNOINST.
For example:
# export HORCMPERM=MGRNOINST
7. Start the Raid Manager instance by using horcmstart.sh <instance-#>
# horcmstart.sh 0
8. Export the environment variable that specifies the Raid Manager instance number to be used
by the Raid Manager commands.
For example:
# export HORCMINST=0
Now, use Raid Manager commands to get further information from the disk arrays. To verify
the software revision of the Raid Manager and the firmware revision of the XP or P9000 disk
array, run the following command:
# raidqry -l
NOTE: Verify for the minimum requirement level for XP or P9000, Raid Manager software,
and firmware for your version listed in the Metrocluster with Continuous Access XP P9000 for
Linux Release Notes.
Identifying Linux device files
Before you create volume groups or disk groups, you must determine the device files of the
corresponding LUNs used in the P9000 array. To determine the device files corresponding
to the LUNs in the P9000 array, run the following command:
# ls /dev/sd* | raidscan -find -fx
The following output is displayed
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
/dev/sdb 0 F CL1-B 0 493 10058 250 OPEN-V
This output displays the mapping between the device files and the CU:LDEVs. In this output
the value for LDEV specifies the CU:LDEV without the : mark.
NOTE: There must also be alternate links for every device, and these alternate links must be
on different buses inside the XP or P9000 disk array. For Example, these alternate links might
be CL2-E and CL2-F.
Unless the devices have been previously paired either on this or another host, the devices will
show up as SMPL (simplex). Paired devices will show up as PVOL (primary volume) or
SVOL(secondary volume).
XP arrays and P9000 arrays support external attached storage devices to be configured as
either PVOL or SVOL or both of a Continuous Access pair. From a Continuous Access
Setting up the replication 17