Skip to main content
Cluster and storage switches

Configure your ports for migration from CN1610 switches to 3132Q-V switches

Contributors netapp-yvonneo

Follow these steps to configure your ports for migration from the CN1610 switches to the new Nexus 3132Q-V switches.

Steps
  1. On all nodes, remove the cables that are attached to the CN1610 switch CL2.

    With supported cabling, you must reconnect the disconnected ports on all of the nodes to the Nexus 3132Q-V switch C2.

  2. Remove four ISL cables from ports 13 to 16 on the CN1610 switch CL1.

    You must attach appropriate Cisco QSFP to SFP+ breakout cables connecting port 1/24 on the new Cisco 3132Q-V switch C2, to ports 13 to 16 on existing CN1610 switch CL1.

    Note When reconnecting any cables to the new Cisco 3132Q-V switch, you must use either optical fiber or Cisco twinax cables.
  3. To make the ISL dynamic, configure the ISL interface 3/1 on the active CN1610 switch to disable the static mode: no port-channel static

    This configuration matches with the ISL configuration on the 3132Q-V switch C2 when the ISLs are brought up on both switches in step 11.

    Show example

    The following example shows the configuration of the ISL interface 3/1 using the no port-channel static command to make the ISL dynamic:

    (CL1)# configure
    (CL1)(Config)# interface 3/1
    (CL1)(Interface 3/1)# no port-channel static
    (CL1)(Interface 3/1)# exit
    (CL1)(Config)# exit
    (CL1)#
  4. Bring up ISLs 13 through 16 on the active CN1610 switch CL1.

    Show example

    The following example illustrates the process of bringing up ISL ports 13 through 16 on the port-channel interface 3/1:

    (CL1)# configure
    (CL1)(Config)# interface 0/13-0/16,3/1
    (CL1)(Interface 0/13-0/16,3/1)# no shutdown
    (CL1)(Interface 0/13-0/16,3/1)# exit
    (CL1)(Config)# exit
    (CL1)#
  5. Verify that the ISLs are up on the CN1610 switch CL1:

    show port-channel

    The "Link State" should be Up, "Type" should be Dynamic, and the "Port Active" column should be True for ports 0/13 to 0/16:

    Show example
    (CL1)# show port-channel 3/1
    Local Interface................................ 3/1
    Channel Name................................... ISL-LAG
    Link State..................................... Up
    Admin Mode..................................... Enabled
    Type........................................... Dynamic
    Load Balance Option............................ 7
    (Enhanced hashing mode)
    
    Mbr    Device/       Port        Port
    Ports  Timeout       Speed       Active
    ------ ------------- ----------  -------
    0/13   actor/long    10 Gb Full  True
           partner/long
    0/14   actor/long    10 Gb Full  True
           partner/long
    0/15   actor/long    10 Gb Full  True
           partner/long
    0/16   actor/long    10 Gb Full  True
           partner/long
  6. Verify that the ISLs are up on the 3132Q-V switch C2:

    show port-channel summary

    Show example

    Ports Eth1/24/1 through Eth1/24/4 should indicate (P), meaning that all four ISL ports are up in the port-channel. Eth1/31 and Eth1/32 should indicate (D) as they are not connected:

    C2# show port-channel summary
    
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    ------------------------------------------------------------------------------
    Group Port-       Type     Protocol  Member Ports
          Channel
    ------------------------------------------------------------------------------
    1     Po1(SU)     Eth      LACP      Eth1/31(D)   Eth1/32(D)
    2     Po2(SU)     Eth      LACP      Eth1/24/1(P) Eth1/24/2(P) Eth1/24/3(P)
                                         Eth1/24/4(P)
  7. Bring up all of the cluster interconnect ports that are connected to the 3132Q-V switch C2 on all of the nodes:

    network port modify

    Show example

    The following example shows how to bring up the cluster interconnect ports connected to the 3132Q-V switch C2:

    cluster::*> network port modify -node n1 -port e0b -up-admin true
    cluster::*> network port modify -node n1 -port e0c -up-admin true
    cluster::*> network port modify -node n2 -port e0b -up-admin true
    cluster::*> network port modify -node n2 -port e0c -up-admin true
  8. Revert all of the migrated cluster interconnect LIFs that are connected to C2 on all of the nodes:

    network interface revert

    Show example
    cluster::*> network interface revert -vserver Cluster -lif n1_clus2
    cluster::*> network interface revert -vserver Cluster -lif n1_clus3
    cluster::*> network interface revert -vserver Cluster -lif n2_clus2
    cluster::*> network interface revert -vserver Cluster -lif n2_clus3
  9. Verify that all of the cluster interconnect ports are reverted to their home ports:

    network interface show

    Show example

    The following example shows that the LIFs on clus2 are reverted to their home ports, and shows that the LIFs are successfully reverted if the ports in the "Current Port" column have a status of true in the "Is Home" column. If the Is Home value is false, then the LIF is not reverted.

    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.
  10. Verify that all of the cluster ports are connected:

    network port show

    Show example

    The following example shows the result of the previous network port modify command, verifying that all of the cluster interconnects are up:

    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.
  11. Verify the connectivity of the remote cluster interfaces:

ONTAP 9.9.1 and later

You can use the network interface check cluster-connectivity command to start an accessibility check for cluster connectivity and then display the details:

network interface check cluster-connectivity start and network interface check cluster-connectivity show

cluster1::*> network interface check cluster-connectivity start

NOTE: Wait for a number of seconds before running the show command to display the details.

cluster1::*> network interface check cluster-connectivity show
                                  Source      Destination   Packet
Node   Date                       LIF         LIF           Loss
------ -------------------------- ---------- -------------- -----------
n1
       3/5/2022 19:21:18 -06:00   n1_clus2   n1_clus1       none
       3/5/2022 19:21:20 -06:00   n1_clus2   n2_clus2       none

n2
       3/5/2022 19:21:18 -06:00   n2_clus2   n1_clus1       none
       3/5/2022 19:21:20 -06:00   n2_clus2   n1_clus2       none
All ONTAP releases

For all ONTAP releases, you can also use the cluster ping-cluster -node <name> command to check the connectivity:

cluster ping-cluster -node <name>

cluster::*> cluster ping-cluster -node n1
Host is n1
Getting addresses from network interface table...
Cluster n1_clus1 n1       e0a    10.10.0.1
Cluster n1_clus2 n1       e0b    10.10.0.2
Cluster n1_clus3 n1       e0c    10.10.0.3
Cluster n1_clus4 n1       e0d    10.10.0.4
Cluster n2_clus1 n2       e0a    10.10.0.5
Cluster n2_clus2 n2       e0b    10.10.0.6
Cluster n2_clus3 n2       e0c    10.10.0.7
Cluster n2_clus4 n2       e0d    10.10.0.8

Local = 10.10.0.1 10.10.0.2 10.10.0.3 10.10.0.4
Remote = 10.10.0.5 10.10.0.6 10.10.0.7 10.10.0.8
Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 16 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 1500 byte MTU on 16 path(s):
    Local 10.10.0.1 to Remote 10.10.0.5
    Local 10.10.0.1 to Remote 10.10.0.6
    Local 10.10.0.1 to Remote 10.10.0.7
    Local 10.10.0.1 to Remote 10.10.0.8
    Local 10.10.0.2 to Remote 10.10.0.5
    Local 10.10.0.2 to Remote 10.10.0.6
    Local 10.10.0.2 to Remote 10.10.0.7
    Local 10.10.0.2 to Remote 10.10.0.8
    Local 10.10.0.3 to Remote 10.10.0.5
    Local 10.10.0.3 to Remote 10.10.0.6
    Local 10.10.0.3 to Remote 10.10.0.7
    Local 10.10.0.3 to Remote 10.10.0.8
    Local 10.10.0.4 to Remote 10.10.0.5
    Local 10.10.0.4 to Remote 10.10.0.6
    Local 10.10.0.4 to Remote 10.10.0.7
    Local 10.10.0.4 to Remote 10.10.0.8

Larger than PMTU communication succeeds on 16 path(s)
RPC status:
4 paths up, 0 paths down (tcp check)
4 paths up, 0 paths down (udp check)
  1. On each node in the cluster, migrate the interfaces that are associated with the first CN1610 switch CL1, to be replaced:

    network interface migrate

    Show example

    The following example shows the ports or LIFs being migrated on nodes n1 and n2:

    cluster::*> network interface migrate -vserver Cluster -lif n1_clus1 -destination-node n1 -destination-port e0b
    cluster::*> network interface migrate -vserver Cluster -lif n1_clus4 -destination-node n1 -destination-port e0c
    cluster::*> network interface migrate -vserver Cluster -lif n2_clus1 -destination-node n2 -destination-port e0b
    cluster::*> network interface migrate -vserver Cluster -lif n2_clus4 -destination-node n2 -destination-port e0c
  2. Verify the cluster status:

    network interface show

    Show example

    The following example shows that the required cluster LIFs have been migrated to the appropriate cluster ports hosted on cluster switch C2:

    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       e0b      false
             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       e0c      false
             n2_clus1   up/up       10.10.0.5/24   n2       e0b      false
             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       e0c      false
    
    8 entries were displayed.
  3. Shut down the node ports that are connected to CL1 on all of the nodes:

    network port modify

    Show example

    The following example shows how to shut down the specified ports on nodes n1 and n2:

    cluster::*> network port modify -node n1 -port e0a -up-admin false
    cluster::*> network port modify -node n1 -port e0d -up-admin false
    cluster::*> network port modify -node n2 -port e0a -up-admin false
    cluster::*> network port modify -node n2 -port e0d -up-admin false
  4. Shut down the ISL ports 24, 31, and 32 on the active 3132Q-V switch C2:

    shutdown

    Show example

    The following example shows how to shut down ISLs 24, 31, and 32 on the active 3132Q-V switch C2:

    C2# configure
    C2(config)# interface ethernet 1/24/1-4
    C2(config-if-range)# shutdown
    C2(config-if-range)# exit
    C2(config)# interface ethernet 1/31-32
    C2(config-if-range)# shutdown
    C2(config-if-range)# exit
    C2(config)# exit
    C2#
  5. Remove the cables that are attached to the CN1610 switch CL1 on all of the nodes.

    With supported cabling, you must reconnect the disconnected ports on all of the nodes to the Nexus 3132Q-V switch C1.

  6. Remove the QSFP cables from Nexus 3132Q-V C2 port e1/24.

    You must connect ports e1/31 and e1/32 on C1 to ports e1/31 and e1/32 on C2 using supported Cisco QSFP optical fiber or direct-attach cables.

  7. Restore the configuration on port 24 and remove the temporary port-channel 2 on C2, by copying the running-configuration file to the startup-configuration file.

    Show example

    The following example copies the running-configuration file to the startup-configuration file:

    C2# configure
    C2(config)# no interface breakout module 1 port 24 map 10g-4x
    C2(config)# no interface port-channel 2
    C2(config-if)# interface e1/24
    C2(config-if)# description 40GbE Node Port
    C2(config-if)# spanning-tree port type edge
    C2(config-if)# spanning-tree bpduguard enable
    C2(config-if)# mtu 9216
    C2(config-if-range)# exit
    C2(config)# exit
    C2# copy running-config startup-config
    [########################################] 100%
    Copy Complete.
  8. Bring up ISL ports 31 and 32 on C2, the active 3132Q-V switch:

    no shutdown

    Show example

    The following example shows how to bring up ISLs 31 and 32 on the 3132Q-V switch C2:

    C2# configure
    C2(config)# interface ethernet 1/31-32
    C2(config-if-range)# no shutdown
    C2(config-if-range)# exit
    C2(config)# exit
    C2# copy running-config startup-config
    [########################################] 100%
    Copy Complete.
What's next?

Complete your migration.