Verifying the configuration for clustered filers

How you check your cluster configuration

There are two ways you can check your cluster configuration prior to placing your cluster online:

Running the Cluster Configuration Checker script
Manually, through the command line

Values that need to match between clustered filers

When you configure your clustered filers, the following configuration information needs to match.

Parameters
Network interfaces
Configuration files
Licenses and option settings
Note
The values for domain controllers and WINS servers no longer need to be identical on both filers in a cluster. You can have each filer in a cluster exist in a different domain or a different workgroup, or both. However, if you have a multiprotocol environment and use UID-to-SID mapping, the UNIX security information must be compatible between the two domains. For example, if you have a UID of 119, it must map to the same Windows account for both filers.

Checking options with the Cluster Configuration Checker

The Cluster Configuration Checker is a script that runs under UNIX or as a Common Gateway Interface (CGI) script from a UNIX Web server. It detects the following configuration problems:

Different versions of Data ONTAP on the local and partner filers
Incorrectly configured network interfaces
Mismatched licenses and option settings
Note
The Cluster Configuration Checker script does not verify matching configuration files. To verify matching configuration files, see Matching configuration files.

You can download the Cluster Configuration Checker script from the NetApp on the Web (NOW) 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 the local and partner filers.
2	Download the Cluster Configuration Checker script ZIP archive file from the NetApp on the Web site at (http://now.netapp.com) site and extract the script file.
3	Run the script, as described in the online instructions on the script Web page. You can run the script either from the command line or through a Web browser that can access both filers.
4	Examine the script output and correct any errors or differences identified in the output.

Manually checking clustered filer settings

The following sections provide information required to manually verify clustered filer configurations.

Matching network interfaces

The network interfaces must have identical values on both filers in a cluster.

To manually check the network interfaces, see the Data ONTAP command reference information for the ifconfig command.

Matching filer options and licenses

To check options on the local and partner filers, complete the following steps.

Step	Action
1	View the options set on the local filer by entering the following command at the filer's console: options Result The current option settings on the filer are listed. You should see output similar to the following: autosupport.doit DONT autosupport.enable on . . dns.domainname filer1 (might be overwritten in takeover) dns.enable off (might be overwritten in takeover) ftpd.enable off . .
2	Note the values of filer options with comments. (Comments appear in parentheses.) The comments for filer options are: `(value might be overwritten in takeover)` `(same value required in local+partner)` `(Same value in local+partner recommended)`
3	Verify that options with comments are set to the same value for both filers.
4	Correct any mismatched options using the following command: options option_name option_value
5	Check the license settings on both filers using the following command: license
6	Correct mismatched license settings using the following command: license option=code

Matching configuration files

Certain configuration files in the root volume of the filer (not the UNIX administration host) need to be identical on clustered filers. Verify that the contents of the configuration files shown in the following table are identical for the clustered filers.

File	Filer 1	Filer 2
/etc/resolv.conf
/etc/httpd.mimetypes
/etc/dgateways
/etc/nsswitch.conf

Matching parameters

Ensure that the parameters shown in the following table have identical values on both clustered filers.

Parameter	Filer 1	Filer 2
ARP table
date
ndmp
nfs
route table
routed
timezone