Stage 4: Setting options and parameters

What the options do

Options help you maintain various functions of your node, such as security, file access, and network communication. During takeover, the value of an option might be changed by the node doing the takeover. This can cause unexpected behavior during a takeover. To avoid unexpected behavior, specific option values must be the same on both the local and partner node.

Each option performs a specific task or has a specific function. See the na_options(1) man page for a description of available options and the function each performs.

Checking options and parameters with the cluster configuration checker

The easiest way to check options and parameters for your cluster is to run the Cluster Configuration Checker. For more information, see Adding disk shelves to a cluster.

After you correct any errors displayed by the Configuration Checker, proceed to Stage 5: Configuring network interfaces.

About managing options between the nodes

In a cluster, options are one of the following types:

Options that must be the same on both two nodes for the cluster to function correctly
See Options that must be the same on both nodes.
Options that might be overwritten on the node that is failing over
These options must be the same on both nodes to avoid losing system state after a failover. See Options that must be the same on both nodes.
Options that are recommended to be the same on both nodes so that system behavior does not change during failover
See Options that are recommended to be the same.
Options that can be different on each node
Note
You can find out whether an option must be the same on both nodes of a cluster from the comments that accompany the option value when you enter the option command. No comments indicates the option can be different on each node.

Options that must be the same on both nodes

The options that must be the same on both nodes for correct system operation or to avoid losing state after failover are listed in the following table.

Option name	Option name
auditlog.enable	raid.disk.copy.auto.enable
auditlog.max_file_size	ip.tcp.offload.enable
autologout.console.enable	ip.tcp.sack.enable
autologout.console.timeou	ip.v6.enable
autologout.telnet.enable	locking.grace_lease_seconds
autologout.telnet.timeout	lun.use_partner.cc.enable
autosupport.retry.count	ndmpd.preferred_interface
autosupport.retry.interval	pcnfsd.enable
cf.quickloop.enable	raid.media_scrub.enable
coredump.dump.attempts	raid.media_scrub.rate
disk.auto_assign	raid.media_scrub.spares.enable
disk.maint_center.allowed_entries	raid.mirror_read_plex_pref
disk.maint_center.enable	raid.reconstruct.perf_impact
disk.maint_center.max_disks	raid.reconstruct.wafliron.enable
disk.maint_center.spares_check	raid.resync.perf_impact
dns.cache.enable	raid.rpm.ata.enable
dns.domainname	raid.rpm.fcal.enable
dns.enable	raid.scrub.perf_impact
dns.update.enable	raid.timeout
dns.update.ttl	raid.verify.perf_impact
ftpd.idle_timeout	rlm.setup
ftpd.max_connections	rmc.lan.smtp_ip
ftpd.max_connections_threshold	rmc.setup
httpd.log.format	snaplock.autocommit_period
httpd.timeout	snaplock.compliance.write_verify
httpd.timewait.enable	snapmirror.vbn_log_enable
ip.drd.ping_interval	snmp.access
ip.drd.ping_retry	snmp.enable
ip.fastpath.enable	tape.reservations
ip.icmp_ignore_redirect.enable	telnet.access
ip.match_any_ifaddr	telnet.distinct.enable
ip.max_vip	telnet.enable
ip.path_mtu_discovery.enable	trusted.hosts
ip.ping_throttle.alarm_interval	vol.copy.throttle
ip.ping_throttle.drop_level	wafl.group_cp
ip.rip.update_interval	wafl.maxdirsize
ip.tcp.newreno.enable	wafl.root_only_chown

Options that are recommended to be the same

The options that are recommended to be the same to avoid differences in system functionality during failover are listed in the following table.

Option name	Option name
cf.takeover.on_network_interface_failure.policy	timed.proto
timed.enable	timed.sched
timed.log	timed.servers
timed.max_skew	timed.window

Manually setting options

To manually set options, complete the following steps.

Step	Action
1	View and note the values of the options on the local and partner nodes, using the following command on each console: options Result The current option settings for the node are displayed on the console. Output similar to the following is displayed: autosupport.doit DONT autosupport.enable off . . .
2	Verify that the options that have comments in parentheses are set to the same value for both nodes. The comments are as follows: Value might be overwritten in takeover Same value required in local+partner Same value in local+partner recommended
3	Correct any mismatched options using the following command: options option_name option_value Note See the na_options man page for more information about the options.

Step

Action

View and note the values of the options on the local and partner nodes, using the following command on each console:

options

Result

The current option settings for the node are displayed on the console. Output similar to the following is displayed:

autosupport.doit                              DONT

autosupport.enable                            off

.

.

.

Verify that the options that have comments in parentheses are set to the same value for both nodes. The comments are as follows:

Value might be overwritten in takeover
Same value required in local+partner
Same value in local+partner recommended

Correct any mismatched options using the following command:

options option_name option_value

Note
See the na_options man page for more information about the options.

What the parameters do

The parameters help keep each node synchronized and help maintain routing of processes throughout the system.

Parameters that must be the same

The parameters listed in the following table must be the same so that takeover is smooth and data is transferred between the nodes correctly.

Parameter	Setting for...
date	date, rdate
NDMP (on or off)	ndmp (on or off)
route table published	route
routed enabled	routed (on or off)
Time zone	timezone