The Group Membership and Atomic Broadcast (GAB) logging daemon collects the GAB-related logs during I/O fencing events or when the GAB message sequence fails. The daemon stores the data in a compact binary form. By default, the GAB logging daemon is enabled.
You can tune the gab_ibuf_count parameter (one of the GAB load-time parameters) value to enable or disable the daemon and set the buffer count. The default value of the parameter is 8.
Note: GAB services are used by all Veritas Storage Foundation and High Availability (SFHA) products.
For information on the GAB tunable parameters and tuning the gab_ibuf_count parameter, see:
Using the gabread_ffdc utility to read the GAB binary log files
If GAB encounters some problem, then the First Failure Data Capture (FFDC) logs are generated and dumped by the gablogd daemon.
For information on using the gabread_ffdc utility to read the GAB binary log files, see:
GAB message logging
Overriding the gab_ibuf_count parameter using the gabconfig –k option
The gab_ibuf_count parameter controls whether the GAB logging daemon is enabled or disabled. If you want to override the gab_ibuf_count control parameter, use the gabconfig -k option to disable login to the gab daemon while the cluster is up and running. However, to re-enable the parameter you must restart GAB and all its client processes.
For information on using the gabconfig –k options, see:
gabconfig (1M) 6.0.1 manual pages:
For more information on the GAB logging daemon, see:
Veritas Cluster Server Administrator's Guide
Veritas Cluster Server documentation for other releases and platforms can be found on the SORT website.
For more information on GAB seeding, see:
SFHA Solutions 6.0.1: About GAB seeding and its role in VCS and other SFHA products
