Booting your cluster for the first time

Complete the system setup worksheet for each node, as described in System setup information worksheet.

Complete the disk ownership worksheet as described in Disk reservation and ownership.

Check that the disk shelf IDs and terminate switches are properly set, and confirm that the system is properly grounded.

For more information, see Connecting additional disk shelves.

Turn on the power first to the disk shelves, if applicable, and then to the FAS270c.

Result

The system begins to boot and stops at the first installation question, which is displayed on each node's console window:

Please enter the new hostname []: 

Go to the system console for Node B, the bottom node, and answer the installation questions for that node, using the information you collected in the System setup information worksheet. When asked for the takeover address, make sure that you enter the IP address for Node A.

Go to the system console for Node A, the top node, and answer the installation questions for that node, using the information you collected in the System setup information worksheet. When asked for the takeover address, make sure that you enter the IP address for Node B.

Note
When you encounter the Timezone question, you can press Enter to accept the default setting if you do not know how to set the timezone. You can then set the timezone after you complete initial setup. See the Timezone Man page for more information.

Assign disks to Node B by completing the following steps, using the disk ownership worksheet:

1. Determine disk ownership by entering the following command from either console:

   disk show -v
   

2. Assign the disk or disks to this node by entering the following command:

   disk assign 0b.NN
   

In similar fashion, assign disks to Node A by completing the following steps:

1. Determine disk ownership.
2. Assign disks to this node using the disk assign command.

1. Check the licenses on the node by entering the following command:

   license
   

   Note
   Clustering must be licensed on both nodes.

2. Add any missing licenses by entering the following command for each missing license:

   license add xxxx
   

   xxxx is the license code for the product.

1. Check the licenses on the node using the license command.
2. Add any missing licenses using the license add command.

Reboot the node by entering the following command:

reboot

Reboot the node using the reboot command.

Enable clustering by entering the following command on a console:

cf enable

N/A

Check node status by entering the following command:

cf status

Check node status using the cf status command.

Test takeover and giveback on this node by completing the following steps:

1. Initiate takeover by entering the following command:

   cf takeover
   

Result

Takeover succeeds. If not, run the Cluster Configuration Checker, fix any errors, reboot the node, and repeat the test.

1. Check the status of the takeover using the cf status command.
2. Give back the node by entering the following command:

   cf giveback
   

3. Check the status of the cluster using the cf status command.

Test takeover and giveback on this node by completing the following steps:

1. Initiate takeover on the node using the cf takeover command.
2. Check the status of the takeover using the cf status command.
3. Give back the node using the cf giveback command.
4. Check the status of the cluster using the cf status command.

If you are setting up a NAS cluster, Go to the Software Setup Guide for advanced system setup.

If you are setting up a SAN cluster, complete the following steps:

1. License FCP services.
2. Set up LUNs, as described in the Block Management Guide.