Step 5: Configuring the local node

Boot the node and disk shelves, then configure the local plexes, as described in the Data Protection Guide.

Enable clustering and other licenses on the node by entering the following command from the node console:

license add xxxxx

xxxxx is the license code you received for the cluster feature.

Note
If you are using a version of Data ONTAP earlier than 6.4, the command is license option=code.

View the options set on the node by entering the following command at the node console:

options

Result

The current option settings on the node are listed. You should see output similar to the following:

autosupport.doit       DONT       

autosupport.enable     off        

.

.

dns.domainname        filer1   (might be overwritten in

                                 takeover)

dns.enable            off      (might be overwritten in

                                 takeover)

ftpd.enable            off        

.

.

Set the node options by entering the following command on the node console:

options option_name option_value

Note
Make sure to set the cf.quickloop.enable variable to True when setting variables on the node.

Check the configuration by entering the following command on the node console:

sysconfig -v

Example

metro1> sysconfig -v

NetApp Release Data ONTAP 6.4.1: Wed Apr 30 13:36:54 PST 
2002

	 System ID: 0033586696 (metro1); partner ID: 0033582111 
(metro2)

	 System Serial Number: 6112 (metro1)

	 System Rev: A0

.

.

.

	 	 	 slot 5: FC Host Adapter 5a (Dual-channel, QLogic 2312 
rev. 2, 64-bit, L-port, <UP>)	 	 Firmware rev:	 	 	 2.1.32

	 	 .

.

.	 	 

61: NETAPP   X235_SCHT5073F10 NA04  68.0GB 
(140174232520B/sect) 

slot 7: FC Host Adapter 7a (Dual-channel, QLogic 2312 
rev. 2, 64-bit, L-port, <OFFLINE (hard)>)

    Firmware rev:   3.1.15

    Host Loop Id:   0 FC Node Name:   2:000:00e08b:07a1a8

    Cacheline size: 8 FC Packet size: 2048

    SRAM parity:    Yes     External GBIC:  No

    Link Data Rate: 1 Gbit

.

.

.

	 slot 11: NVRAM (NetApp NVRAM III)

.

.

.

Result

The configuration is correct if you see the following information:

• Local node and local disks
• Partner node disks
• Any empty adapters

Check the switch configuration by entering the following command on the switch console:

switchshow

Example

The example display shows the output for the command for the only cabled components of the MetroCluster:

metro1:admin> switchshow

switchName:     metro1

switchType:     16.2

switchState:    Online 

switchMode:     Native

switchRole:     Principal

switchDomain:   111

switchId:       fffcde

switchWwn:      10:00:00:60:69:00:60:11

switchBeacon:   OFF

Zoning:         ON (metro1_metro2)

port  0: id N2              L-Port No Module

port  1: id N1 Online       L-Port 12 private

port  2: id 1G Online       L-Port 1 private

port  3: id 1G Online       L-Port 1 private

port  4: id N1 Online       L-Port 12 private

port  5: id N1 Online       L-Port 1 private

port 14: id N1 Online        E-Port 1 
10:00:00:60:69:00:60:11 "Metro1" 

port 15: id N1 Online        E-Port 1 
10:00:00:60:69:00:60:12 "Metro2" (upstream)

Result

The configuration is correct if you see the following information:

• ISL ports, labeled E-Port, showing the switch address
• Two or more disk ports, labeled L-Port, followed by the number of disks in the disk shelf attached to the port
• VI cluster adapter port, labeled L-Port

Shut down the node to the OK prompt from the node console.

Go to the remote site and complete Step 6: Setting up and configuring the remote part of the cluster.