Library Table of Contents Index Previous Next Comments

Cabling your cluster

Step 5: Completing setup and testing your cluster

Completing clustered system setup  Top

Your cluster is ready to be cabled to the network and to power sources. See the F800 Series Hardware Guide for more information.

If your cluster is in systems cabinets, you must reinstall the front and rear doors of your clustered system cabinets to comply with FCC noise reduction requirements. See the 42U System Cabinet Guide for more information about door installation.

Testing takeover and giveback on your cluster  Top

To test your configured cluster, complete the following steps.

Step

Action

1

Run the cluster configuration checker (cf-config-check.cgi) script, as described in Using the cluster configuration checker.

2

Verify the network addresses by entering the following command from one node:

ifconfig -a
Result

The local node and partner node IP addresses are listed.

3

Verify that you can create and retrieve files on both nodes for each licensed protocol.

4

Enable the clustering licenses on by entering the following command on the local and partner nodes:

license cluster=xxxxx 

xxxxx is the license code for your cluster.

Result

Clustering is enabled on your system.

5

From the same node, enter the following command:

cf enable
Result

Takeover of the partner node is enabled

6

Test communication between the local node and partner node.

For example, you can use the fcadmin device_map command to ensure that one node can access the other node's disks.

Example:

filer-1> fcadmin device_map
Loop Map for channel 8: 
Translated Map: Port Count 32
                  7  16  17  18  19  32  33  34  35  48  
49  50  51  24  26  27 57  61  42  43  44  45  28  29  30  
52  53  54  37  38  21  22 
Shelf mapping: 
                Shelf 2:  22  21 XXX  19  18  17  16 
                Shelf 3:  30  29  28  27  26 XXX  24 
                Shelf 4:  38  37 XXX  35  34  33  32 
                Shelf 5: XXX  45  44  43  42 XXX XXX 
                Shelf 6:  54  53  52  51  50  49  48 
Loop Map for channel 5: 
Translated Map: Port Count 22
                  7  38  35  22  20  19  30  29  28  27  
14  41  42  43  26  25 24  18  16  34  33  32 
Shelf mapping: 
                Shelf 2:  22 XXX  20  19  18 XXX  16 
                Shelf 3:  30  29  28  27  26  25  24 
                Shelf 4:  38 XXX XXX  35  34  33  32 
                Shelf 5: XXX XXX XXX  43  42  41 XXX 
Loop Map for channel 7a: 
Translated Map: Port Count 10
                  7  40  42  43  44  45  46  58  59  60 
Shelf mapping: 
                Shelf 5:  46  45  44  43  42 XXX  40 
                Shelf 7: XXX XXX  60  59  58 XXX XXX 

 
Loop Map for channel 7b: 
Translated Map: Port Count 13
                  7  16  17  18  19  20  32  33  34  35  
36  37  38 
Shelf mapping: 
                Shelf 2: XXX XXX  20  19  18  17  16 
                Shelf 4:  38  37  36  35  34  33  32 
7

From the local node console, enter the following command and verify that the partner node halted:

cf takeover
Result

The local node takes over the partner node. You see a message similar to the following:

takeover completed
8

Make sure that all clients and client applications can access data.

9

From the same node, enter the following command:

cf giveback
Result

The partner node reboots and functions normally. A successful giveback ends with the following message on the local node:

giveback completed
10

Repeat Steps 1 through 8 on the other node.

If takeover or giveback fails  Top

If takeover or giveback fails, complete the following steps.

Step

Action

1

Check the Channel B cabling on your disk shelves, and tighten any loose cables.

2

Check the cabling to your cluster interconnect adapters or VI cluster adapters, making sure that the cabling is correct and that the cables are properly seated in the adapters.

3

Check the communication between the local node and partner node by entering the following command:

cf status
Result

If there is a cabling error or the X or Y link is down, the system displays a message that tells you where the problem is.

4

Check the licenses on the local and partner nodes. Both nodes must have the cluster license enabled.

Add missing licenses.

5

Check the parameters and options on your cluster with the cluster configuration checker script.

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.

Correct any errors you find.

6

Check for network connectivity.

See the System Administrator's Guide for more information.

7

Reboot the cluster and rerun the takeover and giveback tests.

8

If you still do not have clustering enabled, call Customer Support.

Where to go next  Top

After cabling your nodes and disk shelves into a cluster, continue configuring your cluster as described in Chapter 3, Configuring a Cluster. Also see the First-Time Configuration Guide for more detailed information about configuring your new cluster.

Library Table of Contents Index Previous Next Comments