Managing Serviceguard Fifteenth Edition, reprinted May 2008

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5208
Adjust these parameters with care.
If you experience problems, return the parameters to their default
values. When contacting HP support for any issues regarding
Serviceguard and networking, please be sure to mention any parameters
that were changed from the defaults.
Third-party applications that are running in a Serviceguard
environment may require tuning of network and kernel parameters:
• ndd is the network tuning utility. For more information, see the man
page for ndd(1M)
• kmtune is the system tuning utility. For more information, see the
man page for kmtune(1M).
Serviceguard has also been tested with non-default values for these two
network parameters:
• ip6_nd_dad_solicit_count - This network parameter enables the
Duplicate Address Detection feature for IPv6 address. For more
information, see “IPv6 Relocatable Address and Duplicate Address
Detection Feature” on page 530 of this manual.
• tcp_keepalive_interval - This network parameter controls the
length of time the node will allow an unused network socket to exist
before reclaiming its resources so they can be reused.
The following requirements must be met:
— The maximum value for tcp_keepalive_interval is 7200000 (2
hours, the HP-UX default value).
— The minimum value for tcp_keepalive_interval is 60000 (60
seconds).
—The tcp_keepalive_interval value must be set on a node
before Serviceguard is started on that node. This can be done by
configuring the new tcp_keepalive_interval in the
/etc/rc.config.d/nddconf file, which will automatically set
any ndd parameters at system boot time.
—The tcp_keepalive_interval value must be the same for all
nodes in the cluster.