[Attention] Additional checks for installs of clusters containing FAS3210, FAS3240, FAS3270 running Data ONTAP 8.1.1 and lower

by Frequent Contributor on ‎2012-11-14 11:59 PM - edited on ‎2014-09-26 11:46 AM by Community Manager

It has been recently reported that certain hardware platforms (FAS3210, FAS3240, FAS3260) running ONTAP 8.1.1 and lower have incorrect definitions for cluster ports as defined by Data ONTAP. The official guidance of these platforms is to have e1a and e2a as the Ethernet ports with the role of 'cluster'. However, by default, Data ONTAP sets e1a and e1b as the 'cluster' ports. As a result of this the following behaviour has been noticed.

 

Scenario 1

When setting up the node for clustered ONTAP the customer looks up documentation and cables e1a and e2a to the cluster network switches. At this time e1b and e2b are not connected to any network component. When 'cluster setup' is run with factory-default settings the process completes with a single cluster LIF on the node.

 

System Defaults:

Private cluster network ports [e1a].

Cluster port MTU values will be set to 9000.

Cluster interface IP addresses will be automatically generated.

 

c-mode::> net int show

  (network interface show)

Logical    Status Network Current       Current Is

Vserver     Interface Admin/Oper Address/Mask Node Port    Home

----------- ---------- ---------- ------------------ ------------- ------- ----

c-mode

cluster_mgmt up/up    10.11.21.30/24 atxcluster01-01 e0a   true

c-mode-01

clus1        up/up 169.254.217.107/16 c-mode-01 e1a   true

mgmt1        up/up 10.11.21.41/24    c-mode-01 e0M   true

c-mode-02

clus1        up/up 169.254.17.160/16  c-mode-02 e1a   true

mgmt1        up/up 10.11.21.42/24    c-mode-02 e0M   true

c-mode-03

clus1        up/up 169.254.250.134/16 c-mode-03 e1a   true

mgmt1        up/up 10.11.21.43/24    c-mode-03 e0M   true

c-mode-04

clus1        up/up 169.254.133.195/16 c-mode-04 e1a   true

mgmt1        up/up 10.11.21.44/24    c-mode-04 e0M   true

9 entries were displayed.

 

Scenario 2

When setting up the node for clustered ONTAP the customer looks up documentation and cables e1a and e2a to the cluster network switches. At this time e1b and e2b are connected to the customers’ data network. When 'cluster setup' is run with factory-default settings the process does not complete as the defined cluster ports (e1a and e1b) are not on the same Ethernet network.

 

One of the following workarounds can be implemented to remedy the situation. The choice of workaround will depend on the current state of the cluster.

 

Workaround 1

When the node has entered the 'cluster setup' menu follow the actions highlighted in red below.

 

System Defaults:

Private cluster network ports [e1a].

Cluster port MTU values will be set to 9000.

Cluster interface IP addresses will be automatically generated.

 

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

 

Step 1 of 5: Create a Cluster

You can type "back", "exit", or "help" at any question.

 

List the private cluster network ports [e1a]: e1a,e2a

Enter the cluster ports' MTU size [9000]:

Enter the cluster network netmask [255.255.0.0]:

 

Workaround 2

When a node is powered on for the first time, exit the 'cluster setup' prompt. Check the role of the Ethernet ports on the controller against published standards on the NetApp Support site. Modify roles of the Ethernet ports as appropriate and resume the process of setting up the node for clustered ONTAP.

 

Post Setup Check / Modification

This workaround applies to a cluster that has been setup and is noticed to have a single cluster LIF on each node of the cluster. The workaround is to create a new cluster LIF on each node of the cluster as per port recommendations on the NetApp Support site. The node will be wired using the reference configuration and the values in the documentation and cluster configuration guide have been reviewed for redundancy and performance. Modify the second port that was missing during setup to make it a cluster port and add the second cluster lif on that port.

 

::> network port modify -node [nodename] -port [port] -role cluster

::> network interface create -vserver [nodename] -role cluster -home-node [nodename] -home-port [port]  -auto true – mtu 9000

 

 

Always

Collect a Config Advisor report at the of the install to verify the accuracy of the setup

 

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.