ONTAP Discussions

FAS8300 cluster convert form switched to switchless

ChiaFu
241 Views

Is it possible to convert cluster form switched to switchless on FAS8300.

I am using FAS8300 switched for volumes move.

After data migration, I need to convert switchless mode.

I don't know how to process cluster network 10GbE *4  to 100GbE *2.

Did any one have experience ?

 

From:

IMG_1.jpg

To:IMG_2.jpg

6 REPLIES 6

Geo_19
219 Views

**** These steps must be on-site cause it requires cable to the platform****


But first, you need to check if the switchless option in the filer is enabled, using the following,

 

::>set adv [jump into the adv mode]

::*> [indicates we're on adv mode]

::*>network options detect-switchless-cluster show [should be displaying true, if not just modify the show instead and type network options detect-switchless-cluster modify -enabled true
::*>net port show, check the e0c and e0d [used as cluster ports], are healthy

::*>net int show [check all clusters lifs are on their home ports]

::*>system autosupport invoke -type all -node * -message MAINT=4h [if the system is under support, with this command we will suppress case creation during 4 hours while you are working on the convertion]

::*>net int migrate -vserver Cluster -lif [ both e0c lifs from both nodes, just on at a time]-destination-node [node 1 or node 2, depends on what you choose before in the lif migration section] -destination-port[e0c,e0d, it varies depending on which lif you select before if you select lif 1 resides on e0c, migrate to e0d node 2]

 make sure all traffic from whatever node you select is running on the destination node and everything is working as expected

 

Example;

 

We migrated both e0c lif to the e0d ports

 

::*>net int migrate -vserver Cluster -lif cluster-lif1 -destination-node node 1 -destination-port e0d
::*>net int migrate -vserver Cluster -lif cluster-lif2 -destination-node node 2 -destination-port e0d


::> net int show [should displaying false on the lifs recently migrated]

something like this;

 

::*> network interface show -vserver Cluster -fields curr-port,is-home vserver lif curr-port is-home - Cluster

node1_clus1 e0b false

Cluster node1_clus2 e0b true

Cluster node2_clus1 e0b false

Cluster node2_clus2 e0b true

4 entries were displayed.

 

then you grab the QSFP28 cable [100Gb] and plug depends on the migration you did before, if you migrate all lifs from e0c, just cable directly to each other, [because the traffic that was there now is running on e0d port ]

 

then after cable, the QSPF28 cable on the e0c port or e0d depending on your selection before, we check the port reachability is up and running, which the following command, 

 

::*> net port show [should be displaying the following]

 

the cluster ports recently connected to each other should be displaying as up and 9000 jumbo, the after checking the port health is good, we migrate the lifs migrated to the home ports [phisically connected e0c to e0c], after that, you check the health of the lif with the command ::*> net int show should displaying as home, then after you do the same with the remaining lifs migrate to the ports physically connected each other and do the same procedure, then after migrating and checking everything is working as expected, you should be good

 

Let's check the doc probably can clear some of the doubts 

https://library.netapp.com/ecm/ecm_download_file/ECMP1157168

EWILTS_SAS
199 Views

The document link quoted above is solid - we've executed this a couple of times to go from switched to switchless.  It's a live migration that does not require downtime - you'll be doing one path at a time so you'll lose redundancy during the window.

ChiaFu
191 Views

There are 4 links for switched.

The lif migrate form e2a -> e0c , e2b -> e0d.

What about lif on e2c & e2d?

Should I delete the *_clus3 & *_clus4 link?

 

FAS8300::> net int show

  (network interface show)

            Logical    Status     Network            Current       Current Is

Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home

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

Cluster

            FAS8300-01_clus1 

                         up/up    169.254.233.125/16 FAS2750-01    e2a     true

            FAS8300-01_clus2 

                         up/up    169.254.163.128/16 FAS2750-01    e2b     true

            FAS8300-01_clus3 

                         up/up    169.254.133.27/16  FAS2750-01    e2c     true                                                                 

            FAS8300-01_clus4

                         up/up    169.254.81.226/16  FAS2750-01    e2d     true

            FAS8300-02_clus1 

                         up/up    169.254.30.100/16  FAS2750-02    e2a     true

            FAS8300-02_clus2 

                         up/up    169.254.196.223/16 FAS2750-02    e2b     true                                                                              

            FAS8300-02_clus3 

                         up/up    169.254.225.120/16 FAS2750-02    e2c     true                                                                   

            FAS8300-02_clus4 

                         up/up    169.254.200.141/16 FAS2750-02    e2d     true

Geo_19
158 Views

Quick question is this a for-node cluster? looks like it is

ChiaFu
144 Views

It's FAS8300 two node.See first picture. 10GbE * 4 to cluster network switch(CN1610).

TMACMD
188 Views

In this case you NEED to open a support case. There are diagnostic commands that should be run to verify. The details are locked into a support only kb article that cannot be shared. 

contact support to be 100% sure you delete the correct cluster lifs 

Public