Please enter search query.
Search <product_name> all support & community content...
Article: 100018369
Last Published: 2013-09-05
Ratings: 1 0
Product(s): InfoScale & Storage Foundation
Problem
How to use the gabconfig command line.
Solution
NAME
gabconfig - Group Membership and Atomic Broadcast (GAB) con-
figuration utility
SYNOPSIS
gabconfig [-abcjklsuUvx] [-f iofence] [-h interval] [-m
count] [-n count ] [-t stable ]
DESCRIPTION
The gabconfig utility sets up and maintains the configuration
gabconfig - Group Membership and Atomic Broadcast (GAB) con-
figuration utility
SYNOPSIS
gabconfig [-abcjklsuUvx] [-f iofence] [-h interval] [-m
count] [-n count ] [-t stable ]
DESCRIPTION
The gabconfig utility sets up and maintains the configuration
of the GAB driver. The GAB driver is dependent on the
Low Latency Transport (LLT) protocol, which must be configured
Low Latency Transport (LLT) protocol, which must be configured
prior to running gabconfig.
OPTIONS
-a Display GAB driver port memberships.
-b Enable system halt when process heartbeat failed.
When process that requested heartbeat monitoring
fails heartbeat, GAB driver will attempt to kill
process by default. When this option is used, GAB
halts the system.
-c Configure the driver for use. Configuring the GAB
driver enables client registrations and the
joining of an already seeded group.
-j Enable halt on rejoin. By default, GAB kills
processes associated with ports on the systems
connect over the network after running unconnected.
This is common when a network failure creates
a partition and systems form independent
clusters which are joined later when the network
or virtual port connections are restored. When
this option is used, GAB halts the system.
-k Repeat attempts to kill process if it does not
die. By default GAB halts the system after several
(5 in this release) attempts to kill process. When
this option is used, GAB silently repeat attempts
to kill process without halting the system.
-l Display the GAB driver configuration.
-s Single network. This flag enables network
partition arbitration and should be used only to test
configurations. It is required for operating GAB
over one network connection with no alternative
communication path, such as heartbeat disks.
-u Unconfigure the GAB driver. Close the seed control
port (port a) if all client ports are closed.
-U Unconfigure the GAB driver and reinitialize all
configuration states, including disk and seed
configurations.
-v Display GAB version information.
-x Seed control port. This option affords protection
from pre-existing network partitions. The control
port (port a) propagates the seed to all configured
systems. GAB must be seeded to enable
the delivery of membership on client ports.
-f iofence_timeout
Specify a timeout (in milliseconds) for
clients to respond to an IOFENCE message before
the system is halted. When clients receive an
IOFENCE message, they must unregister from the GAB
driver within iofence_timeout milliseconds to
avoid halting the system. The default is 15000ms
or 15 seconds.
-h Heartbeat_interval
Disk heartbeating interval, in
milliseconds. If heartbeat disks are configured,
this parameter monitors connectivity through the
disk. The default is 1000ms or 1 second.
-m disk_heartbeat_miss_count
The number of disk heartbeats that can be missed
before the disk or path is declared unavailable.
The default is 4.
-n system_count
Count of systems in the cluster. A non-zero
system count auto-seeds the cluster when all
systems are present. The default is zero, for no
auto-seeding.
-t stable_timeout
Specify a timeout (in milliseconds) for
GAB to wait for the cluster connectivity to stabilize
before issuing a new group membership. This
timeout applies during membership transitions, and
is related to the LLT peer inactivity timeout.
This timeout should be set to the inactivity
timeout plus the maximum message latency. The
default is 5000ms or 5 seconds, allowing for an
LLT peer inactivity timeout of 4 seconds and 1
second maximum message latency.
SEE ALSO
gabdisk
OPTIONS
-a Display GAB driver port memberships.
-b Enable system halt when process heartbeat failed.
When process that requested heartbeat monitoring
fails heartbeat, GAB driver will attempt to kill
process by default. When this option is used, GAB
halts the system.
-c Configure the driver for use. Configuring the GAB
driver enables client registrations and the
joining of an already seeded group.
-j Enable halt on rejoin. By default, GAB kills
processes associated with ports on the systems
connect over the network after running unconnected.
This is common when a network failure creates
a partition and systems form independent
clusters which are joined later when the network
or virtual port connections are restored. When
this option is used, GAB halts the system.
-k Repeat attempts to kill process if it does not
die. By default GAB halts the system after several
(5 in this release) attempts to kill process. When
this option is used, GAB silently repeat attempts
to kill process without halting the system.
-l Display the GAB driver configuration.
-s Single network. This flag enables network
partition arbitration and should be used only to test
configurations. It is required for operating GAB
over one network connection with no alternative
communication path, such as heartbeat disks.
-u Unconfigure the GAB driver. Close the seed control
port (port a) if all client ports are closed.
-U Unconfigure the GAB driver and reinitialize all
configuration states, including disk and seed
configurations.
-v Display GAB version information.
-x Seed control port. This option affords protection
from pre-existing network partitions. The control
port (port a) propagates the seed to all configured
systems. GAB must be seeded to enable
the delivery of membership on client ports.
-f iofence_timeout
Specify a timeout (in milliseconds) for
clients to respond to an IOFENCE message before
the system is halted. When clients receive an
IOFENCE message, they must unregister from the GAB
driver within iofence_timeout milliseconds to
avoid halting the system. The default is 15000ms
or 15 seconds.
-h Heartbeat_interval
Disk heartbeating interval, in
milliseconds. If heartbeat disks are configured,
this parameter monitors connectivity through the
disk. The default is 1000ms or 1 second.
-m disk_heartbeat_miss_count
The number of disk heartbeats that can be missed
before the disk or path is declared unavailable.
The default is 4.
-n system_count
Count of systems in the cluster. A non-zero
system count auto-seeds the cluster when all
systems are present. The default is zero, for no
auto-seeding.
-t stable_timeout
Specify a timeout (in milliseconds) for
GAB to wait for the cluster connectivity to stabilize
before issuing a new group membership. This
timeout applies during membership transitions, and
is related to the LLT peer inactivity timeout.
This timeout should be set to the inactivity
timeout plus the maximum message latency. The
default is 5000ms or 5 seconds, allowing for an
LLT peer inactivity timeout of 4 seconds and 1
second maximum message latency.
SEE ALSO
gabdisk