Preparing cluster ports on an existing controller module

Before installing a new controller module, you must configure cluster ports on the existing controller module so that the cluster ports can provide cluster communication with the new controller module.

About this task

If you are creating a two-node switchless cluster (with no cluster network switches), you must enable the switchless cluster networking mode.

For detailed information about port, LIF, and network configuration in ONTAP, see the Clustered Data ONTAP Network Management Guide.

ONTAP 9 Network Management Guide

Steps

  1. Determine which ports should be used as the node's cluster ports.
    For a list of the default port roles for your platform, see the Hardware Universe at hwu.netapp.com

    The Installation and Setup Instructions for your platform on the NetApp Support Site contains information about the ports for cluster network connections.

  2. For each cluster port, identify the port roles: network port show
    Example

    In the following example, ports e0a, e0b, e0c, and e0d must be changed to cluster ports:

    cluster_A::> network port show
    
    Node: controller_A_1
    Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link  MTU    Admin/Oper  Status
    --------- ------------ ---------------- ----  ----   ----------- --------
    e0M       Default      mgmt_bd_1500     up    1500   auto/1000   healthy
    e0a       Default      Default          up    1500   auto/10000  healthy
    e0b       Default      Default          up    1500   auto/10000  healthy
    e0c       Default      Default          up    1500   auto/10000  healthy
    e0d       Default      Default          up    1500   auto/10000  healthy
    e0i       Default      Default          down  1500   auto/10     -
    e0j       Default      Default          down  1500   auto/10     -
    e0k       Default      Default          down  1500   auto/10     -
    e0l       Default      Default          down  1500   auto/10     -
    e2a       Default      Default          up    1500   auto/10000  healthy
    e2b       Default      Default          up    1500   auto/10000  healthy
    e4a       Default      Default          up    1500   auto/10000  healthy
    e4b       Default      Default          up    1500   auto/10000  healthy
    13 entries were displayed.
    
  3. Based on the version of ONTAP your system is running, set the port roles to the cluster:
    If your system is running... Then...
    Data ONTAP 8.2.x or earlier For each port that you identified as a cluster port, modify the role to cluster, and then set the MTU to the default value of 9000: network port modify -node local -port port_name -role cluster -mtu 9000 -ipspace Cluster
    ONTAP 8.3 or later If the port roles are not set to cluster:
    1. You must change each incorrect port role to the correct role: network port broadcast-domain remove-ports -ipspace Default -broadcast-domain Default -ports node_name:port_name
      Note: Your domain name might be different from the name that is shown in the example.
    2. You must add the port to the cluster domain: network port broadcast-domain add-ports -ipspace Cluster -broadcast-domain Cluster -ports node_name:port_name
    3. You must modify the MTU of the cluster broadcast domain: network port broadcast-domain modify -broadcast-domain Cluster -ipspace Cluster -mtu Cluster 9000
  4. Verify that the port roles have changed: network port show
    Example

    The following example shows that ports e0a, e0b, e0c, and e0d are now cluster ports:

    Node: controller_A_1
    Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link  MTU    Admin/Oper  Status
    --------- ------------ ---------------- ----  ----   ----------- --------
    e0M       Default      mgmt_bd_1500     up    1500   auto/1000   healthy
    e0a       Cluster      Cluster          up    9000   auto/10000  healthy
    e0b       Cluster      Cluster          up    9000   auto/10000  healthy
    e0c       Cluster      Cluster          up    9000   auto/10000  healthy
    e0d       Cluster      Cluster          up    9000   auto/10000  healthy
    e0i       Default      Default          down  1500   auto/10 -
    e0j       Default      Default          down  1500   auto/10 -
    e0k       Default      Default          down  1500   auto/10 -
    e0l       Default      Default          down  1500   auto/10 -
    e2a       Default      Default          up    1500   auto/10000  healthy
    e2b       Default      Default          up    1500   auto/10000  healthy
    e4a       Default      Default          up    1500   auto/10000  healthy
    e4b       Default      Default          up    1500   auto/10000  healthy
    13 entries were displayed.
    
  5. For each cluster port, change the home port of any of the data LIFs on that port to a data port: network interface modify
    Example

    The following example changes the home port of a data LIF to a data port:

    cluster1::> network interface modify -lif datalif1 -vserver vs1 -home-port e1b
  6. For each LIF that you modified, revert the LIF to its new home port: network interface revert
    Example

    The following example reverts the LIF datalif1 to its new home port e1b:

    cluster1::> network interface revert -lif datalif1 -vserver vs1 
  7. If your system is part of a switched cluster, create cluster LIFs on the cluster ports: network interface create
    Example

    The following example creates a cluster LIF on one of the node's cluster ports. The -auto parameter configures the LIF to use a link-local IP address.

    cluster1::> network interface create -vserver Cluster -lif clus1 -role cluster -home-node node0 -home-port e1a -auto true
  8. If you are creating a two-node switchless cluster, enable the switchless cluster networking mode:
    1. Change to the advanced privilege level from either node: set -privilege advanced
      You can respond y when prompted whether you want to continue into advanced mode. The advanced mode prompt appears (*>).
    2. Enable the switchless cluster networking mode: network options switchless-cluster modify -enabled true
    3. Return to the admin privilege level: set -privilege admin
    Important: Cluster interface creation for the existing node in a two-node switchless cluster system is completed after cluster setup is completed through a netboot on the new controller module.