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
$ DEFINE DECC$ARGV_PARSE_STYLE ENABLE
$ SET PROCESS/PARSE_STYLE=EXTENDED
where Device:[directory] is defined as SYS$POSIX_ROOT
For Installing:
$ PRODUCT INSTALL RM /source=Device:[directory]/LOG -
_$ /destination=SYS$POSIX_ROOT:[000000]
Device:[directory] where HITACHI-ARMVMS-RM-V0122-2-1.PCSI exists
:
:
$ PRODUCT SHOW PRODUCT RM
----------------------------------------- ----------- ------------
PRODUCT KIT TYPE STATE
----------------------------------------- ----------- ------------
HITACHI ARMVMS RM V1.22-2 Full LP Installed
----------------------------------------- ----------- ------------
$ raidqry -h
Model : RAID-Manager/OpenVMS
Ver&Rev: 01-22-03/06
:
:
For Installation history:
$ PRODUCT SHOW HISTORY RM /FULL
For removing :
$ PRODUCT REMOVE RM /LOG
(13) About exit code of the command on DCL
RAID Manager return codes are the same for all platforms. However, if the process was invoked
by the DCL, the status is interpreted by DCL and a message appears as below.
-------------------------on DCL of OpenVMS------------------------
$ pairdisplay jjj
PAIRDISPLAY: requires '-jjj' or '/jjj' as argument
PAIRDISPLAY: [EX_REQARG] Required Arg list
Refer to the command log(SYS$POSIX_ROOT:[HORCM.LOG]HORCC_RMOVMS.LOG (/HORCM/log/horcc_rmovms.log))
for details.
$ sh sym $status
$STATUS == "%X0035A7F1"
$
$ pairdisplay -g aaa
PAIRDISPLAY: [EX_ATTHOR] Can't be attached to HORC manager
Refer to the command log(SYS$POSIX_ROOT:[HORCM.LOG]HORCC_RMOVMS.LOG (/HORCM/log/horcc_rmovms.log))
for details.
$ sh sym $status
$STATUS == "%X0035A7D9"
------------------------on DCL of OpenVMS-------------------------
You can calculate the RAID Manager "Exit code" from $status of DCL using the formula below.
Exit code of RM command = ( $status % 2048 ) / 8
Known issues
Rebooting on PAIR state (Writing disable)
OpenVMS does not show the volumes of writing disable (for example, SVOL_PAIR) at start-up of
system, therefore the S-VOLs are hidden when rebooting in PAIR state or SUSPEND(read only)
mode. You are able to verify that the "show device" and "inqraid"command does not show the
S-VOLs after reboot as below (notice that DGA148 and DGA150 devices are SVOL_PAIR).
$ sh dev dg
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DGA145: (VMS4) Online 0
$1$DGA146: (VMS4) Online 0
$1$DGA147: (VMS4) Online 0
Porting notice for OpenVMS 23