# lines start with '#' are comments.
# $Header: HORCM_CONF 1.00 25/05/2000 RM Copyright (c) 2000-2016, Hitachi, Ltd.
# $Header: HORCM_CONF 1.00 25/05/2000 RM (C) Copyright 2000-2016 Hewlett Packard Enterprise Development LP.
#
# NAME   : A sample HORCM_CONF file for the Raid Manager.
#
#/********************* NOTE for System Operation *****************************/
#
# 1.Configuration definition file changes
#   If a system configuration changes or a RAID configuration change cause this
#   file to change,(e.g. cache size change or microcode change),these changes 
#   will not take effect until you stop HORCM (horcmshutdowm) and restart 
#   HORCM (horcmstart).  Use the "-c" option to pairdisplay command to 
#   verify that there are no configuration errors.
#
# 2.Usable range of command devices 
#   A command device is identified via "-CM"(e.g. OPEN-3-CVS-CM) in the
#   ProductID field of the SCSI standard inquiry data.
#   Each Raid Manager command is executed by issuing a specific command to  
#   a command device. Such a control command is only recognized as such 
#   when it is read from or written to a specific block area of the
#   command device LDEV.  Therefore, a command device can't be used for user 
#   data or be part of an LDM Volume Group.
#   In order to prevent user access, do not assign a drive letter to 
#   a command device.
#
#/************************* For HORCM_MON *************************************/

HORCM_MON
#ip_address        service         poll(10ms)     timeout(10ms)
HSTA                horcm          1000              3000

# HORCM_MON is a parameter which is used for monitoring and communicating.
# It describes the IP address, port number, and paired volume error monitoring
# interval of the local host.
#
# <ip_address>
# Describes a network address used by the local host. When HORCM has two or 
# more network addresses on different subnets, enter "NONE" here.
# For binding as IPv6 including IPv4, enter "NONE6" here.
#
# <service>
# Specifies the UDP port name assigned to the HORCM communication path 
# which is registered in "\WINNT\system32\drivers\etc\services".
# A port number or a port name can be specified. 
# 
# <poll>
# Specifies the interval for monitoring volume pairs. By making this interval 
# longer, the HORCM daemon load on the host is reduced.  If this interval is 
# set to -1, the paired volumes are not monitored. A value of -1 should be 
# specified when two or more HORCMs run on the same  host (i.e. volumes 
# are already monitored by another instance). 
# 
# <timeout>
# Specifies the maximum time-out period for communication with the remote 
# host.
#
#/************************** For HORCM_CMD ************************************/

HORCM_CMD
#dev_name                dev_name                dev_name
\\.\PHYSICALDRIVE5
 
# The HORCM_CMD is used to describe the physicaldrive name or Volume{GUID} 
# used to access the command devices. The command devices must be mapped to 
# a SCSI/Fibre port (path) using the RAID SVP. Up to 16 instances can share 
# one command device using the same SCSI port. Beyond 16 instances, you could 
# still utilize the same command device as long as its via a different 
# SCSI/Fibre port(path).
# 
# HORCM_CMD
# dev_name                dev_name                dev_name
# \\.\Volume{b9b31c79-240a-11d5-a37f-00c00d003b1e}
# [NOTE] 
# The "\\.\Volume{GUID}" must be made by setting a parttion used the disk 
# management without filesystem format, and you will be able to know 
# "\\.\Volume{GUID}" for the command device using "inqraid $Volume -CLI -fv" 
# or "raidscan -x findcmddev 0,X". 
# The "\\.\Volume{GUID}" will be keep as the same command device even though 
# the physicaldrive numbers are changed on every reboot in a SAN environment, 
# and HORCM will convert to "\\.\PhysicalDriveX" by finding the PhysicalDrive 
# number through "\\.\Volume{GUID}" if "\\.\Volume{GUID}" is specified to 
# HORCM_CMD. 
# 
# List two or more command devices on the same line in order to use the command
# device alternating function for a particular array. 
# The '-C' and '-D' options to the horcctl command can be used to display the
# current command device or switch to a different one.
# The protection mode command device is shown by adding '*' to the device file.
# [Example]
# horcctl -D
# Current control device = \\.\PHYSICALDRIVE5*
# 
# <dev_name>
# Specifies the raw special files to be used as command device.  
# Commands are issued to the array through these command devices. 
# [Example]
# dev_name                 dev_name                dev_name
# \\.\PHYSICALDRIVE5       \\.\PHYSICALDRIVE6
#
# [Note]:
# Handling of multiple command devices at HORCM startup:
# If only one (of several) command devices is available at HORCM startup,
# the startup log ($HORCM_LOG/horcm_HOST.log) will contain a warning.
# You needs to confirm that HORCM has started without warnings in the startup
# log (and that "horcctl -C" has successfully changed the command device).
#
# When one Raid Manager (host) connects to more than one array, the
# HORC Manager identifies each RAID by using its unitID as an additional
# identifier. The unitIDs are used in ascending order.
#
#           [HSTA]                                    [HSTB]
#             ||___PHYSICALDRIVE6___________________    ||
#             |     ________________PHYSICALDRIVE6_|____||
#             |     |                              |     | 
#     PHYSICALDRIVE5|                              |  PHYSICALDRIVE5 
#             |     |                              |     | 
#          _CL1-A_CL1-B_                        _CL1-A_CL1-B_ 
#          |    -CM    |                        |    -CM    |
#          |           |                        |           |
#          |   P(S)VOL |---------ESCON--------->|  P(S)VOL  |
#          |   (T2L1)  |<--------ESCON----------|  (T2L1)   | 
#          |           |                        |           |
#          | seq#30014 |_____              _____| seq#30015 |
#          |___________|     |             |    |___________|
#           [unitID 0]       |             |     [unitID 1]
#                          ESCON         ESCON 
#                            |             |   
# 
# [Example entry on HSTA]
# HORCM_CMD
# dev_name                dev_name                dev_name
# The unitID 0 <-> (seq#30014)
# \\.\PHYSICALDRIVE5 
# The unitID 1 <-> (seq#30015)
# \\.\PHYSICALDRIVE6 
# 
# [Example entry on HSTB]
# HORCM_CMD
# dev_name                dev_name                dev_name
# The unitID 0 <-> (seq#30014)
# \\.\PHYSICALDRIVE6 
# The unitID 1 <-> (seq#30015)
# \\.\PHYSICALDRIVE5 
# 
# The intended array is specified by appending the unitID to the port.
# [Example on HSTA]
# CL1-A1 -> The port is 'CL1-A' in the unitID 1(seq#30015) array.
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG00             oradb           CL1-A                2          1
# VG01             oradb1          CL1-A1               2          1
# 
# How to confirm for the multiple RAID connections:
# You will be able to confirm using the raidscan command as shown below.
# [Example on HSTA]
# raidscan -p CL1-A1  or raidscan -p CL1-A  -s 30015
#
# [Note]:
# When a RAID is shared by two or more hosts, each host must be consistent
# in its use of unitID and Serial# (Seq#). This can be verified by using the 
# raidqry command.
# 
#/************************** For HORCM_DEV ************************************/

HORCM_DEV
#dev_group        dev_name        port#          TargetID        LU#       MU#
VG01              oradb1          CL1-A                1          1
#VG02             oradb2          CL1-A                1          1         0
 
# The HORCM_DEV parameters are used to describe the relationship between 
# physical volumes (which represent half of a pair) and their logical names.
# Each group name and volume name is unique within this file and should give 
# a hint as to its use (e.g. VG01). The group and paired logical volume names 
# described in this file must be the same in the remote host version of this 
# file. The designated SCSI/Fibre bus, port#,Target-ID, and LUN need not 
# be the same. 
#  
#   [horcm.conf on HSTA]                         [horcm.conf on HSTB] 
# 
#         _CL1-A_                                       _CL1-B_
#         |     |                                       |     |
#         |     | PVOL<------------VG01------------>SVOL|     |
#         |     |(S)             (oradb1)          (P)  |     | 
#         |T1L1 |                                       |T1L2 |
#         |_____|                                       |_____|
#
# [Example entry for horcm.conf on HSTA]
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-A                1          1
# HORCM_INST
# dev_group        ip_address      service
# VG01             HSTB            horcm
#
# [Example entry for horcm.conf on HSTB (or another instance on HSTA)]
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-B                1          2
# HORCM_INST
# dev_group        ip_address      service
# VG01             HSTA            horcm
# 
# <dev_group>
# This parameter is used to identify the name of a group of paired logical 
# volumes. A command directed towards a group is executed for all 
# corresponding volumes within that group. 
# 
# <dev_name>
# This parameter is used to identify the name of the paired logical volume 
# within a group. The commands executed for a volume within a group effect
# only that volume.
# [Note]:
# The name of a paired logical volume must be unique within its own group 
# as well as other groups in the same configuration file.
# 
# <port#>
# This parameter is used to designate the RAID port number associated with the 
# physical volume. Port numbers which can be specified are: 
# CL1-A to CL1-R (excluding CL1-I and CL1-O)
# CL2-A to CL2-R (excluding CL2-I and CL2-O)
# CL3-A to CL3-R (excluding CL3-I and CL3-O) for the extended Lower ports.
# CL4-A to CL4-R (excluding CL4-I and CL4-O) for the extended Lower ports.
# For USP ports
# CL5-A to CL5-R (excluding CL5-I and CL5-O) for the Lower Upper ports.
# CL6-A to CL6-R (excluding CL6-I and CL6-O) for the Lower Upper ports.
# CL7-A to CL7-R (excluding CL7-I and CL7-O) for the Lower Lower ports.
# CL8-A to CL8-R (excluding CL8-I and CL8-O) for the Lower Lower ports.
# CL9-A to CL9-R (excluding CL9-I and CL9-O) for the Upper Upper ports.
# CLA-A to CLA-R (excluding CLA-I and CLA-O) for the Upper Upper ports.
# CLB-A to CLB-R (excluding CLB-I and CLB-O) for the Upper Lower ports.
# CLC-A to CLC-R (excluding CLC-I and CLC-O) for the Upper Lower ports.
# CLD-A to CLD-R (excluding CLD-I and CLD-O) for the Lower Upper ports.
# CLE-A to CLE-R (excluding CLE-I and CLE-O) for the Lower Upper ports.
# CLF-A to CLF-R (excluding CLF-I and CLF-O) for the Lower Lower ports.
# CLG-A to CLG-R (excluding CLG-I and CLG-O) for the Lower Lower ports.
# 
# For multiple RAID configurations:
# When a host is connected to two or more RAIDs, the unitID of each RAID is 
# expressed as a postfix to the port#.
# In the following, "n" is the unitId. If the "n" option is omitted, the 
# unitId is assumed to be 0.
# CL1-An to CL1-Rn (excluding CL1-I and CL1-O)
# CL2-An to CL2-Rn (excluding CL2-I and CL2-O)
# CL3-An to CL3-Rn (excluding CL3-i and CL3-o) for the extended Lower ports.
# CL4-An to CL4-Rn (excluding CL4-i and CL4-o) for the extended Lower ports.
# For USP ports
# CL5-An to CL5-Rn (excluding CL5-I and CL5-O) for the Lower Upper ports.
# CL6-An to CL6-Rn (excluding CL6-I and CL6-O) for the Lower Upper ports.
# CL7-An to CL7-Rn (excluding CL7-I and CL7-O) for the Lower Lower ports.
# CL8-An to CL8-Rn (excluding CL8-I and CL8-O) for the Lower Lower ports.
# CL9-An to CL9-Rn (excluding CL9-I and CL9-O) for the Upper Upper ports.
# CLA-An to CLA-Rn (excluding CLA-I and CLA-O) for the Upper Upper ports.
# CLB-An to CLB-Rn (excluding CLB-I and CLB-O) for the Upper Lower ports.
# CLC-An to CLC-Rn (excluding CLC-I and CLC-O) for the Upper Lower ports.
# CLD-An to CLD-Rn (excluding CLD-I and CLD-O) for the Lower Upper ports.
# CLE-An to CLE-Rn (excluding CLE-I and CLE-O) for the Lower Upper ports.
# CLF-An to CLF-Rn (excluding CLF-I and CLF-O) for the Lower Lower ports.
# CLG-An to CLG-Rn (excluding CLG-I and CLG-O) for the Lower Lower ports.
# [Example]
# CL1-A1 -> Designates port "CL1-A" in array the unitID 1.
# 
# <TargetID>
# This parameter is used to designate the SCSI/Fibre target ID.
# 
# <LU#>
# This parameter is used to designate the SCSI/Fibre logical unit number (LU#). 
# 
# [Note]:
# In case of fibre channel, if the target ID & LU# displayed on the host system
# is different from the target ID in which is indicated by the raidscan command,
# then the target ID & LU# indicated by the raidscan command should be used.
# Also, if the fibre channel adapter is different (e.g. Emulex, Qlogic),
# then the target ID which is indicated by the raidscan command may be
# different from the target ID shown by WindowsNT/2000.
# In this case,you have two configuration options:
# - Utilize the TID#,LU# which is returned by the raidscan command as the  
#   target ID in this file.
# - Change the default fibre conversion table the following way to match 
#   WindowsNT/2000.
#   set HORCMFCTBL=X  /*  'X' is Fibre conversion table Number  */
#   horcmstart ...    /*   Start HORCM  */
# You have to start HORCM without a description for HORCM_DEV,
# and HORCM_INST because target ID & Lun are Unknown,and should be described
# the shown the Port, tagetID, Lun by 'raidscan -find' for HORCM_DEV.
# 
# <MU#>
# RAID Manager is capable of keeping track of up to 7 pair associations
# per LDEV.
#                                ______
#      <---oradb------>CA/UR_PVOL|    |UR_PVOL(MU1-MU3)--oradb4-6->
#                           (S)  |    |  (S)
#      <---oradb1--->(MU0)BC_PVOL|    |BC_PVOL(MU1)----oradb2---->
#                           (S)  |LDEV|
#                                |____|BC_PVOL(MU2)----oradb3---->
# 
# The mirror descriptor column (MU#) is often the key to deciphering the intent
# of the user. Whereas a blank MU# can imply either CA (HORC) or BC (HOMRCF),
# a "0" MU# explicitly implies BC (HOMRCF). If the BC (HOMRCF) mirroring
# (identical LU) descriptor (MU#0-2) is omitted, it is assumed to be MU#0.
# SVOL cascading (second tier) mirrors are expressed as virtual volumes using
# the mirror descriptors (MU#1-2). MU#0 is reserved for a first tier pvol/svol.
# MU# for HORC/UR
# MU#(0-3) identifies one of 4 possible HORC/UR bitmap associations for an LDEV.
# UR mirror description is described in the MU# column by adding "h" in order to
# identify identical LU as the mirror descriptor for UR. If omitted,
# it is assumed to be MU#0 for HORC/UR, MU# for HORC must be specified as "0".
# For description of the group:
# 'HORCM_DEV' and 'HORCM_INST' keys are usable in groups:
# [Example]
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb11         CL1-A                1          1        0
# VG01             oradb12         CL1-A                1          2        0
# HORCM_INST
# dev_group        ip_address      service
# VG01             HSTB            horcm
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG02             oradb21         CL1-A                2          1        0
# VG02             oradb22         CL1-A                2          2        0
# HORCM_INST
# dev_group        ip_address      service
# VG02             HSTC            horcm
# 
#/************************** For HORCM_LDEV ***********************************/

HORCM_LDEV
#dev_group        dev_name        Serial#   CU:LDEV(LDEV#)   MU#
VG01              oradb3            60095   01:04              0
#VG01             oradb3            60095     260              0
#VG01             oradb3            60095   0x104              0

# The HORCM_LDEV parameters are used to describe stable LDEV# and Serial#
# as another way of HORCM_DEV used 'port#,Target-ID,LUN'.
# [Note]:
# This feature depends on the micro version of RAID or kind of RAID.
#
# <Serial#>
# This parameter is used to describe the Serial number of RAID box.
#
# <CU:LDEV(LDEV#)>
# This parameter is used to describe the LDEV number in the RAID box,
# and is supported three kind of formats as LDEV# as below.
# - Specifying "CU:LDEV" in hex used by SVP or Web console
#   Example for LDEV# 260
#   01:04
#
# - Specifying "LDEV" in decimal used by inqraid command
#   Example for LDEV# 260
#   260
#
# - Specifying "LDEV" in hex used by inqraid -fx command
#   Example for LDEV# 260
#   0x104
#
#/************************* For HORCM_INST ************************************/

HORCM_INST
#dev_group        ip_address      service
VG01              HSTB            horcm
#VG02             HSTC            horcm
 
# 'HORCM_INST' is also usable in groups.
# This parameter is used to describe the network address (IP address or Host 
# name) of the (possibly remote) host which services the other half 
# of these pairs (under identical group/volume names).
# Communication with the host serving the other half of these pairs allows for
# coordinated pair control/status operations.Refer to HORCM_DEV for an example.
# For HA configuration:
# When a mirrored primary volume is shared by two or more hosts,
# there are often two or more remote hosts using the secondary volume. 
# It is necessary to describe the IP addresses of all these hosts.
#  
#   [horcm.conf on HSTA]                         [horcm.conf on HSTC] 
#   [horcm.conf on HSTB]                         [horcm.conf on HSTD] 
# 
#         _CL1-A_                                       _CL1-B_
#         |     |                                       |     |
#         |     | PVOL<------------VG01------------>SVOL|     |
#         |     |(S)             (oradb1)          (P)  |     | 
#         |T1L1 |                                       |T1L2 |
#         |_____|                                       |_____|
#
# 
# [Example entry on HSTA for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# HSTA             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-A                1          1
# dev_group        ip_address      service
# VG01             HSTC            horcm
# VG01             HSTD            horcm
#
# [Example entry on HSTB for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# HSTB             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-A                1          1
# dev_group        ip_address      service
# VG01             HSTC            horcm
# VG01             HSTD            horcm
#
# [Example entry on HSTC for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# HSTC             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-B                1          2
# dev_group        ip_address      service
# VG01             HSTA            horcm
# VG01             HSTB            horcm
# 
# [Example entry on HSTD for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# HSTD             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-B                1          2
# dev_group        ip_address      service
# VG01             HSTA            horcm
# VG01             HSTB            horcm
# 
# The current network address and port name being used by HORCM can be changed 
# via the horcctl command's -NC and -ND options, which displays the changed 
# network address.
# 
# <dev_group>
# This is the group that this host needs to know about (because it services 
# the other half of this group's volume pairs).
# 
# <ip_address>
# This parameter is used to describe the network address of the remote host 
# associated with the group name. 
# In case of binding IPv6, it is possible to specify IPv6 and IPv4 address, 
# and then IPv4 address is converted as IPv4 mapped IPv6. 
# 
# [Example] 
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# NONE6            horcm           1000              3000
# 
# HORCM_INST
# dev_group        ip_address                  service
# VG01             158.214.127.64              horcm
# VG02             fe80::209:6bff:febe:3c17    horcm
# 
# <service>
# This parameter is used to specify the port name assigned to the HORCM 
# daemon communication path which is registered in
# "\WINNT\system32\drivers\etc\services". A port number or a port name 
# can be specified. 
# [Example] 
# HORCM_INST
# dev_group        ip_address      service
# VG01             HSTB            horcm
# VG02             HSTC            horcm
# 
# When HORCM can use two or more network addresses on different subnets.
# Use "NONE" for the HORCM_MON ip_address as shown.
#  
#      __________________________subnet-1_________________________
#      ________|_______|_________subnet-2___________|_______|_____
#           |  |    |  |                         |  |    |  | 
#          [HSTA]  [HSTB]                       [HSTC]  [HSTD]
#             |      |                             |      | 
#          _CL1-A__CL1-B_                       _CL1-C__CL1-D_ 
#          |           |                        |           |
#          |           | PVOL<----VG01----->SVOL|           |
#          |           |(S)     (oradb1)   (P)  |           | 
#          |   T1L1    |                        |   T1L2    |
#          |___________|                        |___________|
# 
# [Example entry on HSTA for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# NONE             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-A                1          1
# dev_group        ip_address      service
# VG01             HSTC_IP1        horcm
# VG01             HSTD_IP1        horcm
# VG01             HSTC_IP2        horcm
# VG01             HSTD_IP2        horcm
#
# [Example entry on HSTB for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# NONE             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-B                1          1
# dev_group        ip_address      service
# VG01             HSTC_IP1        horcm
# VG01             HSTD_IP1        horcm
# VG01             HSTC_IP2        horcm
# VG01             HSTD_IP2        horcm
#
# [Example entry on HSTC for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# NONE             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-C                1          2
# dev_group        ip_address      service
# VG01             HSTA_IP1        horcm
# VG01             HSTB_IP1        horcm
# VG01             HSTA_IP2        horcm
# VG01             HSTB_IP2        horcm
# 
# [Example entry on HSTD for one or more hosts]
# HORCM_MON
# ip_address       service         poll(10ms)     timeout(10ms)
# NONE             horcm           1000              3000
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# VG01             oradb1          CL1-D                1          2
# dev_group        ip_address      service
# VG01             HSTA_IP1        horcm
# VG01             HSTB_IP1        horcm
# VG01             HSTA_IP2        horcm
# VG01             HSTB_IP2        horcm
# 
# For confirmation of multiple networks:
# The "raidqry -r <group>" command executed on each host will allow you 
# to examine the multiple network configuration. You will be able to 
# change the current network address by using the "horcctl -NC <group>" 
# command from each Host.
# 
#/********************** For parameter limits *********************************/
# 
# The parameters defined in the configuration definition file must not exceed
# the limits shown. Default values are used for unspecified parameters. 
# 
# HORCM_CONF Parameter Limits: 
# Parameter(Unit)  Default value   Type                      Limit
# ip_address       None            strings                   63 characters
# service          None            string or numeric value   15 characters
# poll (10ms)      1000            Numeric value             None
# timeout (10ms)   3000            Numeric value             None
# For HORCM_DEV 
# dev_name         None            strings                   31 characters
# dev_group        None            strings                   31 characters
# port#            None            strings                   31 characters
# targetID         None            Numeric value              7 characters
# LU#              None            Numeric value              7 characters
# MU#              0               Numeric value              7 characters
# Serial#          None            Numeric value             12 characters
# CU:LDEV(LDEV#)#  None            Numeric value              6 characters
# For HORCM_CMD 
# dev_name         None            strings                   63 characters
# 
# [Note]:
# Numeric values are decimal characters. Group names and device names 
# in the configuration file should be 8 characters or less.
# 
#/********************* For BC (HOMRCF) cascading volumes *********************/
# 
# When a cascaded (tiered) BC (HOMRCF) configuration is involved, 
# a two configuration file (folded over) description is recommended.
# Notice that instance 0 describes the root (and all leaf) volumes, 
# while instance 1 describes the intermediate s/pvols.
#  
#        [horcm0.conf]                  [horcm1.conf] 
#                                               ______
#         PVOL(MU0)<------oradb------->(MU0)SVOL|    |
#        (S)                               (P)  |    | 
#         SVOL(MU0)<------oradb1-------(MU1)PVOL|T3L2|
#                                               |    |
#         SVOL(MU0)<------oradb2-------(MU2)PVOL|____|
#
# 
# [Example entry for horcm0.conf on HST1]
# The instance 0 configuration file (below) specifies: 
# "You know about 3 BC (HOMRCF) pairs, because each has a different tgt/LUN, 
# you know that none are intermediate s/pvols in a cascade". 
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# oradb            oradev1         CL1-D                3          0        0
# oradb1           oradev11        CL1-D                3          4        0
# oradb2           oradev21        CL1-D                3          6        0
# 
# HORCM_INST
# dev_group        ip_address      service
# oradb            HST1            horcm1
# oradb1           HST1            horcm1
# oradb2           HST1            horcm1
# 
# [Example entry for horcm1.conf on HST1 or HST2]
# The instance 1 configuration file (below) specifies: 
# "You know about 3 BC (HOMRCF) pairs. Since the tgt/LUN is the same, 
# you assume this is the intermediate s/pvol". 
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# oradb            oradev1         CL1-D                3          2        0
# oradb1           oradev11        CL1-D                3          2        1
# oradb2           oradev21        CL1-D                3          2        2
# 
# HORCM_INST
# dev_group        ip_address      service
# oradb            HST1            horcm0
# oradb1           HST1            horcm0
# oradb2           HST1            horcm0
# 
# The '-m cas' option to the pairdisplay command can be used to display 
# a cascaded BC (HOMRCF) configuration.
#
#/******************** For CA(HORC)/BC(HOMRCF) cascading volumes **************/
# 
# For connecting CA (HORC) and BC (HOMRCF) Together:
# You can use 3 configuration files to describe a CA(HORC)/BC(HOMRCF) cascaded 
# configuration as shown. The middle configuration file on HST2 can be 
# interpreted as follows:
#
#  
# [horcm.conf on HST1]     [horcm.conf on HST2]       [horcm.conf0 on HST2]
#                               ______
#   CA_PVOL----oradb---->CA_SVOL|    |
#                               |    | 
#                               |T3L2|BC_PVOL(MU0)----oradb1--->(MU0)BC_SVOL
#                               |    |
#                               |____|BC_PVOL(MU1)----oradb2--->(MU0)BC_SVOL
#
# 
# [Example entry for horcm.conf on HST1] 
# The first line is ambiguous as to whether the pair is CA(HORC) or BC(HOMRCF)
# because the MU# is blank.
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# oradb            oradev1         CL1-D                3          0
# 
# HORCM_INST
# dev_group        ip_address      service
# oradb            HST2            horcm
# oradb            HST2            horcm0
# 
# [Example entry for horcm.conf on HST2]
# The first line is ambiguous as to whether the pair is CA (HORC) or BC (HOMRCF)
# because the MU# is blank. The second line uses MU#0 explicitly 
# (meaning BC (HOMRCF)) with the same port/tgt/LUN so you know the top line 
# refers to a CA (HORC) pair. Since all 3 lines use the same port/tgt/LUN, you
# know it's the middle part of a CA (HORC), cascaded BC (HOMRCF) configuration.
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# oradb            oradev1         CL1-D                3          2
# oradb1           oradev11        CL1-D                3          2        0
# oradb2           oradev21        CL1-D                3          2        1
# 
# HORCM_INST
# dev_group        ip_address      service
# oradb            HST1            horcm
# oradb1           HST2            horcm0
# oradb2           HST2            horcm0
# 
# [Example entry for horcm0.conf on HST2 or HST3]
# The other "give away" that oradb is a CA (HORC) pair is that its remote 
# pair-serving host is a different host than "HST2" which serves this 
# RM instance.
# 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# oradb            oradev1         CL1-D                3          2
# oradb1           oradev11        CL1-D                3          4        0
# oradb2           oradev21        CL1-D                3          6        0
# 
# HORCM_INST
# dev_group        ip_address      service
# oradb            HST1            horcm
# oradb1           HST2            horcm
# oradb2           HST2            horcm
# 
# The '-m cas' option to the pairdisplay command can be used to display 
# a CA (HORC), cascaded BC (HOMRCF) configuration.
#
#/************** Configuration for NO multiplatform supported *****************/
# Two Raid Managers on a single host are able to operate the BC(HORCM) volumes 
# for all ports through only a one command device.
# Thus, a host type currently supporting Raid Manager(e.g. Linux) can manipulate
# the BC pairs owned by host types not currently supporting Raid Manager.
#  
#     ___________rsh(remsh) or other network commands_________
#           |        |           |        |           |
#        [HOST_X]    |        [HOST_X]    |     [horcm0/1.conf on HOST_SUP]
#           |     [HOST_Y]       |     [HOST_Y]       |
#           |        |           |        |           |
#     ____CL1-A____CL1-C______ CL1-B____CL1-D_________|_______ 
#     |     |        |           |        |           |      |
#     |    PVOL------|----------SVOL      |      <----CM     |
#     |              |                    |           |      |
#     |             PVOL-----------------SVOL    <----|      |
#     |                                                      |
#     |________________________RAID__________________________|
# 
# [Meaning of symbols]:
# HOST_X and HOST_Y ... Raid Manager doesn't have support yet.
# HOST_SUP ............ Raid Manager on Linux or HP-UX,Solaris,AIX,etc.
#
# [Example for horcm0.conf on HOST_SUP] 
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# HOST_X           ora1_X          CL1-A                3          0        0
# HORCM_INST
# dev_group        ip_address      service
# HOST_X           localhost       horcm1
#
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# HOST_Y           ora1_Y          CL1-C                3          0        0
# HORCM_INST
# dev_group        ip_address      service
# HOST_Y           localhost       horcm1
# 
# [Example for horcm1.conf on HOST_SUP]  
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# HOST_X           ora1_X          CL1-B                3          1        0
# HORCM_INST
# dev_group        ip_address      service
# HOST_X           localhost       horcm0
#
# HORCM_DEV
# dev_group        dev_name        port#          TargetID        LU#      MU#
# HOST_Y           ora1_Y          CL1-D                3          1        0
# HORCM_INST
# dev_group        ip_address      service
# HOST_Y           localhost       horcm0
# 
# [Note]:
# This configuration must be used in Non-protection mode.
# If the fibre channel adapter is used on HOST_X (HOST_Y), then the target ID
# which is indicated by the raidscan command may be different from the target
# ID shown by HOST_X (HOST_Y).
# In this case, the target ID & LU# indicated by the raidscan command should
# be used.
# Also, you will be able to change the fibre conversion table the following
# way to match the OS on HOST_X (HOST_Y). 
# [Example on HST_SUP]
# HORCMFCTBL=X          /*  'X' is Fibre conversion table Number  */
# export HORCMFCTBL
# horcmstart.sh 0 1     /*  Start HORCM  */
#
#/************************* For the first start-up ****************************/
# Please use your horcm.conf without comment lines for the first start-up 
# of HORCM !!
