Skip to main content
Cluster and storage switches

Prepare for migration from CN1610 switches 3232C switches

Contributors netapp-yvonneo

Follow these steps to prepare your CN1610 switch migration to a Cisco Nexus 3232C switch.

Steps
  1. If AutoSupport is enabled on this cluster, suppress automatic case creation by invoking an AutoSupport message:

    system node autosupport invoke -node * -type all -message MAINT=xh

    x is the duration of the maintenance window in hours.

    Note

    The message notifies technical support of this maintenance task so that automatic case creation is suppressed during the maintenance window.

  2. Display information about the devices in your configuration:

    network device-discovery show

    Show example

    The following example displays how many cluster interconnect interfaces have been configured in each node for each cluster interconnect switch:

    cluster::> network device-discovery show
    
           Local  Discovered
    Node   Port   Device       Interface   Platform
    ------ ------ ------------ ----------- ----------
    n1     /cdp
            e0a   CL1          0/1         CN1610
            e0b   CL2          0/1         CN1610
            e0c   CL2          0/2         CN1610
            e0d   CL1          0/2         CN1610
    n2     /cdp
            e0a   CL1          0/3         CN1610
            e0b   CL2          0/3         CN1610
            e0c   CL2          0/4         CN1610
            e0d   CL1          0/4         CN1610
    
    8 entries were displayed.
  3. Determine the administrative or operational status for each cluster interface.

    1. Display the cluster network port attributes:

      network port show -role cluster

      Show example
      cluster::*> network port show -role cluster
             (network port show)
      
      Node: n1
                      Broadcast              Speed (Mbps) Health Ignore
      Port  IPspace   Domain     Link  MTU   Admin/Open   Status Health Status
      ----- --------- ---------- ----- ----- ------------ ------ -------------
      e0a   cluster   cluster    up    9000  auto/10000     -
      e0b   cluster   cluster    up    9000  auto/10000     -
      e0c   cluster   cluster    up    9000  auto/10000     -        -
      e0d   cluster   cluster    up    9000  auto/10000     -        -
      Node: n2
                      Broadcast              Speed (Mbps) Health Ignore
      Port  IPspace   Domain     Link  MTU   Admin/Open   Status Health Status
      ----- --------- ---------- ----- ----- ------------ ------ -------------
      e0a   cluster   cluster    up    9000  auto/10000     -
      e0b   cluster   cluster    up    9000  auto/10000     -
      e0c   cluster   cluster    up    9000  auto/10000     -
      e0d   cluster   cluster    up    9000  auto/10000     -
      
      8 entries were displayed.
    2. Display information about the logical interfaces:

      network interface show -role cluster

      Show example
      cluster::*> network interface show -role cluster
      (network interface show)
               Logical    Status      Network        Current  Current  Is
      Vserver  Interface  Admin/Oper  Address/Mask   Node     Port     Home
      -------- ---------- ----------- -------------- -------- -------- -----
      Cluster
               n1_clus1   up/up       10.10.0.1/24   n1       e0a      true
               n1_clus2   up/up       10.10.0.2/24   n1       e0b      true
               n1_clus3   up/up       10.10.0.3/24   n1       e0c      true
               n1_clus4   up/up       10.10.0.4/24   n1       e0d      true
               n2_clus1   up/up       10.10.0.5/24   n2       e0a      true
               n2_clus2   up/up       10.10.0.6/24   n2       e0b      true
               n2_clus3   up/up       10.10.0.7/24   n2       e0c      true
               n2_clus4   up/up       10.10.0.8/24   n2       e0d      true
      
       8 entries were displayed.
    3. Display information about the discovered cluster switches:

      system cluster-switch show

      Show example

      The following example displays the cluster switches that are known to the cluster along with their management IP addresses:

      cluster::> system cluster-switch show
      Switch                        Type             Address       Model
      ----------------------------- ---------------- ------------- --------
      CL1                           cluster-network  10.10.1.101   CN1610
           Serial Number: 01234567
            Is Monitored: true
                  Reason:
        Software Version: 1.2.0.7
          Version Source: ISDP
      CL2                           cluster-network  10.10.1.102   CN1610
           Serial Number: 01234568
            Is Monitored: true
                  Reason:
        Software Version: 1.2.0.7
          Version Source: ISDP
      
      2	entries displayed.
  4. Verify that the appropriate RCF and image are installed on the new 3232C switches as necessary for your requirements, and make any essential site customizations.

    You should prepare both switches at this time. If you need to upgrade the RCF and image, you must complete the following procedure:

    1. See the Cisco Ethernet Switch page on the NetApp Support Site.

    2. Note your switch and the required software versions in the table on that page.

    3. Download the appropriate version of the RCF.

    4. Select CONTINUE on the Description page, accept the license agreement, and then follow the instructions on the Download page to download the RCF.

    5. Download the appropriate version of the image software at Cisco® Cluster and Management Network Switch Reference Configuration File Download.

  5. Migrate the LIFs associated with the second CN1610 switch that you plan to replace:

    network interface migrate -vserver vserver-name -lif lif-name -source-node source-node-name destination-node destination-node-name -destination-port destination-port-name

    Show example

    You must migrate each LIF individually as shown in the following example:

    cluster::*> network interface migrate -vserver cluster -lif n1_clus2 -source-node n1
    -destination-node  n1  -destination-port  e0a
    cluster::*> network interface migrate -vserver cluster -lif n1_clus3 -source-node n1
    -destination-node  n1  -destination-port  e0d
    cluster::*> network interface migrate -vserver cluster -lif n2_clus2 -source-node n2
    -destination-node  n2  -destination-port  e0a
    cluster::*> network interface migrate -vserver cluster -lif n2_clus3 -source-node n2
    -destination-node  n2  -destination-port  e0d
  6. Verify the cluster's health:

    network interface show -role cluster

    Show example
    cluster::*> network interface show -role cluster
    (network interface show)
             Logical    Status      Network         Current  Current  Is
    Vserver  Interface  Admin/Oper  Address/Mask    Node     Port     Home
    -------- ---------- ----------- --------------- -------- -------- -----
    Cluster
             n1_clus1   up/up       10.10.0.1/24    n1        e0a     true
             n1_clus2   up/up       10.10.0.2/24    n1        e0a     false
             n1_clus3   up/up       10.10.0.3/24    n1        e0d     false
             n1_clus4   up/up       10.10.0.4/24    n1        e0d     true
             n2_clus1   up/up       10.10.0.5/24    n2        e0a     true
             n2_clus2   up/up       10.10.0.6/24    n2        e0a     false
             n2_clus3   up/up       10.10.0.7/24    n2        e0d     false
             n2_clus4   up/up       10.10.0.8/24    n2        e0d     true
    
    8 entries were displayed.