gabdiskhb - GAB Heartbeat Disk Utility
sbin/gabdiskhb [-a name] [-d name] [-m name] [-o] [-p port]
[-s start] [-l] [-r] [-S signature]
The gabdiskhb utility sets up and maintains the configuration of GAB driver heartbeat disk regions. GAB driver heartbeat disk regions provide channels in addition to the network connections for protection from network failures. These resources describe a 64K region that GAB uses to read and write to the disk. This region must be uniquely identified by the block device name and the start location.
Heartbeat disk resources must also be associated with a GAB control port. The heartbeat disk must be attached and accessible by all machines that run applications using the GAB port with which the disk is associated.
-a name -s start -o -p port Add a GAB heartbeat disk resource. The block device name and the start location must be unique and must not overlap the 64K regions described by the GAB heartbeat disk resources already configured. Use the -o option to specify that the heartbeat disk is read only. -d name -s start Delete a GAB heartbeat disk resource. The block device name and the start location identify the GAB disk heartbeat resource to delete. -m name -s start Monitor the GAB heartbeat disk resource. The block device name and the start location identify the GAB disk heartbeat resource to monitor. This option returns an error code if the resource has faulted or if the local system is not actively heartbeating. -r Reset faulted disk heartbeat entities. Faults occur when the disk device driver returns an error or fails to respond to initiated I/O after a heartbeat interval. -l List GAB heartbeat disks. List the currently configured GAB heartbeat disk entities and their states of peer activity. -S signature This option prompts GAB to check for the specified signature every time it reads the region. Refer to the gabdiskconf manual page for more details on signatures. You must have run the gabdiskconf utility to specify a signature before using this option. In case of a signature mismatch, GAB marks the disk as faulted.
The following example commands (shown with platform variations) allocate two disk heartbeating resources, one for port a (the GAB control port) and one for port h (the VCS port):
# /sbin/gabdiskhb -a /dev/dsk/c1t1d0s0 -s 16 -p a # /sbin/gabdiskhb -a /dev/dsk/c1t1d0s0 -s 144 -p h
# /sbin/gabdiskhb -a /dev/hdisk4 -s 0 -p a # /sbin/gabdiskhb -a /dev/hdisk4 -s 128 -p h
# /sbin/gabdiskhb -a /dev/sdg -s 0 -p a # /sbin/gabdiskhb -a /dev/sdh -s 128 -p h
# /sbin/gabdiskhb -a /dev/vg01/lvol1 -s 0 -p a # /sbin/gabdiskhb -a /dev/vg01/lvol1 -s 128 -p h
When LLT and GAB are running under a cluster manager other than VCS, configure LLT and GAB as per the cluster managers supplementary documentation on LLT and GAB.
This command in applicable only in VCS environment.
gabconfig(1m), gabdiskx(1m) gabdiskconf(1m)