Library Table of Contents  Previous Next Comments

Determining the current configuration for clustered filers

How you check your cluster configuration  Top

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

Checking options with the Cluster Configuration Checker  Top

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:

You can download this 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 script from the NOW 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 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 options and license settings  Top

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 these options for the local filer, and repeat Step 1 on the partner filer.

3

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

  • Value might be overwritten in takeover
  • Same value required in local+partner
  • Same value in local+partner recommended
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

Library Table of Contents  Previous Next Comments