#

#NOTE: The Raid Manager command device (RORCM_CMD) cannot be used for

#data storage (it is reserved for private Raid Manager usage).

#/************************ HORCM_MON *************************************/

#

#The HORCM_MON parameter is used for monitoring and control of device groups

#by the Raid Manager.

#It is used to define the IP address, port number, and paired volume error

#monitoring interval for the local host.

#<ip_address>

#Defines a network address used by the local host. This can be a host name

#or an IP address.

#<service>

#Specifies the port name assigned to the Raid Manager communication path,

#which is must also be defined in /etc/services. If a port number, rather

#than a port name is specified, the port number will be used.

#<poll_interval>

#Specifies the interval used for monitoring the paired volumes. By

#increasing this interval, the Raid Manager daemon load is reduced.

#If this interval is set to -1, the paired volumes are not monitored.

#<timeout>

#Specifies the time-out period for communication with the Raid Manager

#server.

HORCM_MON

 

 

 

#ip_address

service

poll_interval(10ms)

timeout(10ms)

ftsys1

horcm0

1000

3000

#/************************* HORCM_CMD *************************************/

#

#The HORCM_CMD parameter is used to define the special files (raw device

#file names) of the Raid Manager command devices used for the monitoring

#and control of Raid Manager device groups.

#Define the special device files corresponding to two or more command devices

#in order to use the Raid Manager alternate command device feature. An

#alternate command device must be configured, otherwise a failure of a

#single command device could prevent access to the device group.

#Each command device must have alternate links (PVLinks). The first command

#device is the primary command device. The second command device is a

#redundant command device and is used only upon failure of the primary

#command device. The command devices must be mapped to the various host

#interfaces by using the SVP (disk array console) or a remote console.

HORCM_CMD

 

 

 

#Primary

Primary Alt-Link

Secondary

Secondary Alt-link

#dev_name

dev_name

dev_name

dev_name

/dev/rdsk/c4t1d0

/dev/rdsk/c5t1d0

/dev/rdsk/c4t0d1

/dev/rdsk/c5t0d1

#/************************* HORCM_DEV *************************************/

#

#The HORCM_DEV parameter is used to define the addresses of the physical

#volumes corresponding to the paired logical volume names. Each group

#name is a unique name used by the hosts which will access the volumes.

#The group and paired logical volume names defined here must be the same for

#all other (remote) hosts that will access this device group.

#The hardware SCSI bus, SCSI-ID, and LUNs for the device groups do not need

#to be the same on remote hosts.

#

#<dev_group>

#This parameter is used to define the device group name for paired logical

#volumes. The device group name is used by all Raid Manager commands for

#accessing these paired logical volumes.

#<dev_name>

#This parameter is used to define the names of the paired logical volumes

#in the device group.

#<port#>

#This parameter is used to define the XP256 port number used to access the

#physical volumes in the XP256 connected to the "dev_name". Consult your

#XP256 for valid Port numbers to specify here.

168 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP