Modifications to kill_ntries, by modifying /etc/sysconfig/gab, are lost after a reboot
Article ID: 100033305
Updated On:
Description
Applies to
- Storage Foundation HA 6.0.5
- Red Hat Enterprise Linux (RHEL) 6.5
Description
Veritas Cluster Server (VCS) is unable to set the kill_ntries permanently, even though a user modified the /etc/sysconfig/gab file, as shown below. # tail -4 /etc/sysconfig/gab
GAB_START=1
GAB_STOP=1
GAB_ISOLATE_TIME=240000
GAB_KILL_NTRIES=10 After rebooting the system, the kill_ntries parameter is unchanged.
# gabconfig -e
GAB Kernel Tunables:
============================
numnids : 64
numports : 32
flowctrl : 128
logbufsize : 48100
msglogsize : 256
logflag : 53
isolate_time : 240000
kill_ntries : 5
conn_wait : 12
ibuf_count : 8 Workaround
Add the following, new entry to the /etc/gabtab file: /sbin/gabconfig -S kill_ntries:10
Resolution
The new value of gab_kill_ntries is not reflected after a reboot because the GAB_KILL_NTRIES entry, from /etc/sysconfig/gab, is being excluded while the module is being initialized.
Issue/Introduction
Applies to
- Storage Foundation HA 6.0.5
- Red Hat Enterprise Linux (RHEL) 6.5
Description
Veritas Cluster Server (VCS) is unable to set the kill_ntries permanently, even though a user modified the /etc/sysconfig/gab file, as shown below. # tail -4 /etc/sysconfig/gab
GAB_START=1
GAB_STOP=1
GAB_ISOLATE_TIME=240000
GAB_KILL_NTRIES=10 After rebooting the system, the kill_ntries parameter is unchanged.
# gabconfig -e
GAB Kernel Tunables:
============================
numnids : 64
numports : 32
flowctrl : 128
logbufsize : 48100
msglogsize : 256
logflag : 53
isolate_time : 240000
kill_ntries : 5
conn_wait : 12
ibuf_count : 8 Additional Information
ETrack: 3905314
Was this article helpful?
Yes
No
Powered by
