MODULE 2: INSTALLATION AND CONFIGURATION

EXERCISE 2: CREATING A TWO-NODE CLUSTER

In this exercise, you create a cluster, configure the first node in the cluster, and then add a second node to the
cluster.

OBJECTIVES
By the end of this exercise, you should be able to:
 Create a cluster
 Add a second node to the cluster

TASK 1: CREATE A CLUSTER AND CONFIGURE THE FIRST NODE IN THE CLUSTER
STEP ACTION

1. From the Windows machine in your lab kit, use PuTTY to open a Secure Shell (SSH) session to
the first storage controller in your lab kit and verify that the preconfigured entry is correct.
It is preconfigured in PuTTY as cluster1_01. Your instructor will provide the IP address.

2. Log in as admin.
The password is provided by your instructor.
You are now logged in to the cluster shell.

E2-1 Clustered Data ONTAP Administration: Installation and Configuration

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 STEP ACTION

3. Enter the cluster setup command to start the cluster setup wizard.
::> cluster setup
NOTE: If you make a mistake during cluster setup, press Ctrl-C to interrupt the wizard. Restart
the wizard by re-entering cluster setup at the cluster shell prompt.

4. At the prompt, enter create to create a new cluster.

Do you want to create a new cluster or join an existing cluster?
{create, join}:
create

5. When prompted about using the node as a single node cluster, reply no because this will be a
multi-node cluster.
Do you intend for this node to be used as a single node cluster? {yes,
no} [no]: no

6. Enter yes to accept the default values for cluster network configuration.
System Defaults:
Private cluster network ports [e0a,e0b].
Cluster port MTU values will be set to 1500.
Cluster interface IP addresses will be automatically generated.

Do you want to use these defaults? {yes, no} [yes]: yes

7. Name the cluster cluster1.

Enter the cluster name: cluster1

8. Enter the base license key that was provided by your instructor.
You can use lowercase letters for the license key.
Enter the cluster base license key: UJBGVLVQJHOJKBAAAAAAAAAAAAAA
Creating cluster cluster1
Starting cluster support services .....
Cluster cluster1 has been created.

9. Do not add additional license keys at this time but press Enter to continue.
Enter an additional license key []:

E2-2 Clustered Data ONTAP Administration: Installation and Configuration

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 STEP ACTION

10. Configure the cluster management resources:

a. Type e0c as the port to host the cluster management interface.
b. Enter the IP address, netmask, and default gateway.
If the addresses are different in your lab environment, they will be provided by your instructor
Enter the cluster management interface port [e0c]: e0c
Enter the cluster management interface IP address: 192.168.0.101
Enter the cluster management interface netmask: 255.255.255.0
Enter the cluster management interface default gateway: 192.168.0.1

11. Enter the domain name and IP address of the DNS server.
Enter the DNS domain names: learn.netapp.local
Enter the name server IP addresses: 192.168.0.11

12. Configure node management:

a. Enter any controller location.
b. Type e0f as the port to host the node management interface.
c. Enter the IP address, netmask, and default gateway provided by your instructor.
d. Press Enter to leave AutoSupport enabled
Where is the controller located []: NetAppU
Enter the node management interface port [e0f]: e0f
Enter the node management interface IP address: 192.168.0.91
Enter the node management interface netmask: 255.255.255.0
Enter the node management interface default gateway: 192.168.0.1
Press enter to continue:

13. If the completion of the cluster setup wizard logs your management session off, log back in as
admin.

14. To check the status of your new cluster, enter the cluster show command at the console.
cluster1::> cluster show
Node Health Eligibility
--------------------- ------- ------------
cluster1_01 true true

TASK 2: ADD A SECOND NODE TO THE CLUSTER

STEP ACTION

1. From the Windows machine in your lab kit, use PuTTY to open an SSH session to the second
storage controller in your lab kit.
It is preconfigured in PuTTY as cluster1_02.

2. Log in as admin.

E2-3 Clustered Data ONTAP Administration: Installation and Configuration

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 STEP ACTION

3. Enter the cluster setup command to start the cluster setup wizard.
::> cluster setup
Do you want to create a new cluster or join an existing cluster?
{create, join}: join

4. Accept the cluster network defaults by entering yes.

System Defaults:
Private cluster network ports [e0a,e0b].
Cluster port MTU values will be set to 1500.
Cluster interface IP addresses will be automatically generated.

Do you want to use these defaults? {yes, no} [yes]: yes

5. Enter cluster1 to join the existing cluster.

Enter the name of the cluster you would like to join [cluster1]:
cluster1

6. Configure node management:

a. Type e0f as the default port to host the node management interface.
b. Enter the IP address, netmask, and default gateway provided by your instructor.
c. Press Enter to leave AutoSupport enabled.
Enter the node management interface port [e0c]: e0f
Enter the node management interface IP address: 192.168.0.92
Enter the node management interface netmask: 255.255.255.0
Enter the node management interface default gateway: 192.168.0.1
Press enter to continue:

7. If the completion of the cluster setup wizard logs your management session off, log back in as
admin.

8. To check the status of your new cluster, enter the cluster show command at the console.
cluster1::> cluster show
Node Health Eligibility
--------------------- ------- ------------
cluster1_01 true true
cluster1_02 true true
2 entries were displayed.

9. Type network interface show and observe the cluster interfaces on both nodes and their
associated IPs, noticing that the IP addresses are in a private network range.
network interface show

E2-4 Clustered Data ONTAP Administration: Installation and Configuration

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
TASK 3: PRESERVE FREE SPACE ON VOL0 VOLUMES
STEP ACTION

1. This step is necessary only when running a virtualized cluster. The virtual disks attached to each
node are small compared to real hard disks, resulting in unrealistic sizes for aggr0 and vol0.

2. Turn off snapshots on vol0 on both nodes.

system node run -node cluster1_01 vol options vol0 nosnap on
system node run -node cluster1_02 vol options vol0 nosnap on

3. Set snap reserve on vol0 to 0%..

cluster1::> system node run -node cluster1_01 snap reserve vol0 0
cluster1::> system node run -node cluster1_02 snap reserve vol0 0

4. From the command line, show the aggregates:

 stor aggr show
You should see only two aggregates, an aggr0 owned by each of the two nodes in the cluster.
NOTE: The #Vols column shows that each aggregate contains one volume. Those are the vol0
volumes for each node. You cannot move them from their respective aggregates as you will be
able to move the volumes that you will create later.

5. Rename the aggr0 aggregates so that they are more easily identifiable.
aggr rename -aggregate aggr0 -newname aggr0_n1
aggr rename -aggregate aggr0_cluster1_02_0 -newname aggr0_n2

6. Verify the new names.

stor aggr show
The aggr0 aggregates have only one data disk each. The size of the data disk is 1GB.

7. Add 3 data disks to each aggr0 aggregate.

aggr add-disk -aggregate aggr0_n1 -diskcount 3
aggr add-disk -aggregate aggr0_n2 -diskcount 3

8. Increase the size of vol0 to 3GB.

system node run -node cluster1_01 vol size vol0 +2g
system node run -node cluster1_02 vol size vol0 +2g

9. Verify the vol0 settings.

volume show -vserver cluster1_01 -volume vol0
volume show -vserver cluster1_02 -volume vol0

END OF EXERCISE

E2-5 Clustered Data ONTAP Administration: Installation and Configuration

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.