Step 3: 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 System Administrator's Guide for a description of available options and the function each performs.

Options that must be the same

The options listed in the following table must be the same for a takeover to be successfully completed.

Option name	Option name
cifs.show_snapshot	nfs.v2.df.3gb.lim
dns.domainname	nis.domainname
dns.enable	nis.enable
http.admin.enable	pcnfsd.enable
httpd.timeout	raid.reconstruct_speed
httpd.timewait.enable	raid.timeout
ip.path_mtu_discovery.enable	wafl.maxdirsize
nfs.per_client_stats.enable	wafl.root_only_chown
nfs.v2.df.2gb.lim	vol.vopy.throttle

What the parameters do

The parameters help keep the individual 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	Parameter
date	date, rdate
NDMP (on or off)	ndmp (on or off)
route table published	route
routed enabled	routed (on or off)
Time zone	timezone

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

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

Manually setting parameters

To manually set parameters, complete the following steps.

Step	Action
1	View the individual parameter settings on both the local and partner nodes, similar to the following example: routed status Result The default gateway list status is displayed.
2	Verify that the parameters on both nodes are set to the same value.
3	Correct any mismatched values.
4	Go to Step 4: Configuring networking interfaces.

Setting options and parameters with the cluster configuration checker

The cluster configuration checker is a script that runs under UNIX or as a CGI script from a UNIX Web server. It detects the following configuration problems:

Mismatched licenses
Mismatched option settings
Incorrectly configured network interfaces
Different versions of Data ONTAP on the local and partner nodes

The script is available through download from the NOW Web site at http://now.netapp.com/NOW/tools. Look for the cluster configuration checker (cf-config-check.cgi) file.

To run this script from the command line, complete the following steps.

Step	Action
1	Collect the IP addresses and login information for both nodes.
2	Download the script from the NOW Web site, then unzip the script.
3	Run the script, as described in the online instructions on the script Web page. You can run the script from either the command line or through a Web browser that can access both nodes.
4	Examine the script output and correct any errors or differences.
5	Go to Step 4: Configuring networking interfaces.