HP StorageWorks XP Remote Web Console Software - Manual (Page 159)

Continuous Access XP Journal user guide 159
To execute the
mkconf.sh
command, the LU constituting the file system to be paired must be attached to
the NAS OS. The LU configuration (size and number) in the file system to be paired must be exactly the
same in the primary and secondary sites.
To create the correct RAID Manager XP configuration definition file, HP recommends creating a file system
to be temporarily paired before executing the
mkconf.sh
command. After creating the RAID Manager XP
configuration definition file using the
mkconf.sh
command, you can continue using the file system in the
primary site. Alternatively, you can delete it and create a file system with the same configuration using the
same LU in ” Create file systems in Continuous Access XP Journal P-VOLs ” on page 168. You must delete
the temporarily created file system in the secondary site before creating a file system pair.
The following explains how to create a RAID Manager XP configuration definition file in the NAS package
in CL1 in the primary site in the sample configuration above. You must create RAID Manager XP
configuration definition files for the other three NAS packages using the previously explained procedure.
Creating a template for a RAID Manager XP configuration definition file
Figure 74 shows an example of how to create a template for a RAID Manager XP configuration definition
file.
Figure 74 Example of
mkconf.sh
execution results (for instance number 16)
Editing the template for the RAID Manager XP configuration definition file
Table 29 lists the values specified for items included in the RAID Manager XP configuration definition file
in the NAS Blade system.
$ cat /home/nasroot/horc_devfile | sudo mkconf.sh -gg VG -i 16 -a
starting HORCM inst 16
HORCM inst 16 starts successfully.
HORCM Shutdown inst 16 !!!
A CONFIG file was successfully completed.
starting HORCM inst 16
HORCM inst 16 starts successfully.
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV
/dev/sdj VG VG_000 CL1-A-1 0 17 - 62486 70
/dev/sdk VG VG_001 CL1-A-1 1 18 - 62486 18
?
?
/dev/sdt VG VG_010 CL1-A-1 0 10 - 62486 10
/dev/sdu VG VG_011 CL1-A-1 0 11 - 62486 64
/dev/sdv VG VG_012 CL1-A-1 0 12 - 62486 12
/dev/sdw VG VG_013 CL1-A-1 0 13 - 62486 66
/dev/sdx VG VG_014 CL1-A-1 0 14 - 62486 14
/dev/sdy VG VG_015 CL1-A-1 0 15 - 62486 68
/dev/sdz VG VG_016 CL1-A-1 0 16 - 62486 16
HORCM Shutdown inst 16 !!!
Please check
'/home/nasroot/horcm16.conf','/home/nasroot/log16/curlog/horcm_*.log', and
modify 'ip
_address & service'.
#
Table 29 Configuration definition file settings (HORCM_MON, HORCM_CMD) and specified values in
NAS Blade system
Section name Item Specified values in NAS Blade system
HORCM_MON ip_address
Unique IP address for eth1 or eth2 in the local NAS package
service
20331 (Instance number 16) or 20332 (Instance number 17)
HORCM_CMD dev_name /dev/sdf