Moving the local cluster connections

Contributors netapp-martyh netapp-ranuk Download PDF of this page

You must move the MetroCluster FC configuration’s cluster interfaces to the IP switches.

Moving the cluster connections on the MetroCluster FC nodes

You must move the cluster connections on the MetroCluster FC nodes to the IP switches. The steps depend on whether you are using the existing IP switches or you are using new IP switches.

You must perform this task on both MetroCluster sites.

The following task assumes a controller module using two ports for the cluster connections. Some controller module models use four or more ports for the cluster connection. In that case, for the purposes of this example, the ports are divided into two groups, alternating ports between the two groups

The following table shows the example ports used in this task.

Number of cluster connections on the controller module Group A ports Group B ports

Two

e0a

e0b

Four

e0a, e0c

e0b, e0d

  • Group A ports connect to local switch switch_x_1-IP.

  • Group B ports connect to local switch switch_x_2-IP.

The following table shows which switch ports the FC nodes connect to. For the Broadcom BES-53248 switch, the port usage depends on the model of the MetroCluster IP nodes.

Switch model MetroCluster IP node model Switch port(s) Connects to

Cisco 3132Q-V or 3232C

Any

5

node_x_1-FC

6

node_x_2-FC

Broadcom BES-53248

FAS2750/A220

1, 2, 3

node_x_1-FC

FAS8200 / A300

1, 2, 3, 7, 8, 9

node_x_1-FC

FAS2750/A220

4, 5, 6

node_x_2-FC

FAS8200 / A300

4, 5, 6, 10, 11, 12

node_x_2-FC

Moving the local cluster connections when using new IP switches

If you are using new IP switches, you must physically move the existing MetroCluster FC nodes' cluster connections to the new switches.

  1. Move the MetroCluster FC node group A cluster connections to the new IP switches.

    1. Disconnect all the group A ports from the switch, or, if the MetroCluster FC configuration was a switchless cluster, disconnect them from the partner node.

    2. Disconnect the group A ports from node_A_1-FC and node_A_2-FC.

    3. Connect the group A ports of node_A_1-FC to the switch ports for the FC node on switch_A_1-IP

    4. Connect the group A ports of node_A_2-FC to the switch ports for the FC node on switch_A_1-IP

  2. Verify that all cluster ports are up: network port show -ipspace Cluster

    cluster_A::*> network port show -ipspace Cluster
    
    Node: node_A_1-FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    Node: node_A_2-FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    4 entries were displayed.
    
    cluster_A::*>
  3. Verify that all interfaces display true in the Is Home column: network interface show -vserver cluster

    This might take several minutes to complete.

    cluster_A::*> network interface show -vserver cluster
    
                Logical      Status     Network          Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- -----
    Cluster
                node_A_1_FC_clus1
                           up/up      169.254.209.69/16  node_A_1_FC   e0a     true
                node_A_1-FC_clus2
                           up/up      169.254.49.125/16  node_A_1-FC   e0b     true
                node_A_2-FC_clus1
                           up/up      169.254.47.194/16  node_A_2-FC   e0a     true
                node_A_2-FC_clus2
                           up/up      169.254.19.183/16  node_A_2-FC   e0b     true
    
    4 entries were displayed.
    
    cluster_A::*>
  4. Perform the above steps on both nodes (node_A_1-FC and node_A_2-FC) to move the group B ports of the cluster interfaces.

  5. Repeat the above steps on the partner cluster "cluster_B".

Moving the local cluster connections when reusing existing IP switches

If you are reusing existing IP switches, you must update firmware, reconfigure the switches with the correct Reference Configure Files (RCFs) and move the connections to the correct ports one switch at a time.

This task is required only if the FC nodes are connected to existing IP switches and you are reusing the switches.

  1. Disconnect the local cluster connections that connect to switch_A_1_IP

    1. Disconnect the group A ports from the existing IP switch.

    2. Disconnect the ISL ports on switch_A_1_IP.

      You can see the Installation and Setup instructions for the platform to see the cluster port usage.

  2. Reconfigure switch_A_1_IP using RCF files generated for your platform combination and transition.

    Follow the steps in the section for your switch vendor from the MetroCluster IP Installation and Configuration guide, as given in the links below.

    1. If required, download and install the new switch firmware.

      You should use the latest firmware that the MetroCluster IP nodes support.

    2. Prepare the IP switches for the application of the new RCF files.

    3. Download and install the IP RCF file depending on your switch vendor.

  3. Reconnect the group A ports to switch_A_1_IP.

  4. Verify that all cluster ports are up: network port show -ipspace cluster

    Cluster-A::*> network port show -ipspace cluster
    
    Node: node_A_1_FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    Node: node_A_2_FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    4 entries were displayed.
    
    Cluster-A::*>
  5. Verify that all interfaces are on their home port: network interface show -vserver Cluster

    Cluster-A::*> network interface show -vserver Cluster
    
                Logical      Status     Network          Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- -----
    Cluster
                node_A_1_FC_clus1
                           up/up      169.254.209.69/16  node_A_1_FC   e0a     true
                node_A_1_FC_clus2
                           up/up      169.254.49.125/16  node_A_1_FC   e0b     true
                node_A_2_FC_clus1
                           up/up      169.254.47.194/16  node_A_2_FC   e0a     true
                node_A_2_FC_clus2
                           up/up      169.254.19.183/16  node_A_2_FC   e0b     true
    
    4 entries were displayed.
    
    Cluster-A::*>
  6. Repeat all the previous steps on switch_A_2_IP.

  7. Reconnect the local cluster ISL ports.

  8. Repeat the above steps at site_B for switch B_1_IP and switch B_2_IP.

  9. Connect the remote ISLs between the sites.

Verifying that the cluster connections are moved and the cluster is healthy

To ensure that there is proper connectivity and that the configuration is ready to proceed with the transition process, you must verify that the cluster connections are moved correctly, the cluster switches are recognized and the cluster is healthy.

  1. Verify that all cluster ports are up and running: network port show -ipspace Cluster

    Cluster-A::*> network port show -ipspace Cluster
    
    Node: Node-A-1-FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    Node: Node-A-2-FC
    
                                                      Speed(Mbps) Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
    --------- ------------ ---------------- ---- ---- ----------- --------
    e0a       Cluster      Cluster          up   9000  auto/10000 healthy
    e0b       Cluster      Cluster          up   9000  auto/10000 healthy
    
    4 entries were displayed.
    
    Cluster-A::*>
  2. Verify that all interfaces are on their home port: network interface show -vserver Cluster

    This might take several minutes to complete.

    The following example shows that all interfaces show true in the Is Home column.

    Cluster-A::*> network interface show -vserver Cluster
    
                Logical      Status     Network          Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- -----
    Cluster
                Node-A-1_FC_clus1
                           up/up      169.254.209.69/16  Node-A-1_FC   e0a     true
                Node-A-1-FC_clus2
                           up/up      169.254.49.125/16  Node-A-1-FC   e0b     true
                Node-A-2-FC_clus1
                           up/up      169.254.47.194/16  Node-A-2-FC   e0a     true
                Node-A-2-FC_clus2
                           up/up      169.254.19.183/16  Node-A-2-FC   e0b     true
    
    4 entries were displayed.
    
    Cluster-A::*>
  3. Verify that both the local IP switches are discovered by the nodes: network device-discovery show -protocol cdp

    Cluster-A::*> network device-discovery show -protocol cdp
    
    Node/       Local  Discovered
    Protocol    Port   Device (LLDP: ChassisID)  Interface         Platform
    ----------- ------ ------------------------- ----------------  ----------------
    Node-A-1-FC
               /cdp
                e0a    Switch-A-3-IP             1/5/1             N3K-C3232C
                e0b    Switch-A-4-IP             0/5/1             N3K-C3232C
    Node-A-2-FC
               /cdp
                e0a    Switch-A-3-IP             1/6/1             N3K-C3232C
                e0b    Switch-A-4-IP             0/6/1             N3K-C3232C
    
    4 entries were displayed.
    
    Cluster-A::*>
  4. On the IP switch, verify that the MetroCluster IP nodes have been discovered by both local IP switches: show cdp neighbors

    You must perform this step on each switch.

    This example shows how to verify the nodes are discovered on Switch-A-3-IP.

    (Switch-A-3-IP)# show cdp neighbors
    
    Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater,
                      V - VoIP-Phone, D - Remotely-Managed-Device,
                      s - Supports-STP-Dispute
    
    Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
    Node-A-1-FC         Eth1/5/1       133    H         FAS8200       e0a
    Node-A-2-FC         Eth1/6/1       133    H         FAS8200       e0a
    Switch-A-4-IP(FDO220329A4)
                        Eth1/7         175    R S I s   N3K-C3232C    Eth1/7
    Switch-A-4-IP(FDO220329A4)
                        Eth1/8         175    R S I s   N3K-C3232C    Eth1/8
    Switch-B-3-IP(FDO220329B3)
                        Eth1/20        173    R S I s   N3K-C3232C    Eth1/20
    Switch-B-3-IP(FDO220329B3)
                        Eth1/21        173    R S I s   N3K-C3232C    Eth1/21
    
    Total entries displayed: 4
    
    (Switch-A-3-IP)#

    This example shows how to verify that the nodes are discovered on Switch-A-4-IP.

    (Switch-A-4-IP)# show cdp neighbors
    
    Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater,
                      V - VoIP-Phone, D - Remotely-Managed-Device,
                      s - Supports-STP-Dispute
    
    Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
    Node-A-1-FC         Eth1/5/1       133    H         FAS8200       e0b
    Node-A-2-FC         Eth1/6/1       133    H         FAS8200       e0b
    Switch-A-3-IP(FDO220329A3)
                        Eth1/7         175    R S I s   N3K-C3232C    Eth1/7
    Switch-A-3-IP(FDO220329A3)
                        Eth1/8         175    R S I s   N3K-C3232C    Eth1/8
    Switch-B-4-IP(FDO220329B4)
                        Eth1/20        169    R S I s   N3K-C3232C    Eth1/20
    Switch-B-4-IP(FDO220329B4)
                        Eth1/21        169    R S I s   N3K-C3232C    Eth1/21
    
    Total entries displayed: 4
    
    (Switch-A-4-IP)#