I did the same thing a few ago and then gave myself the forehead slap after I found out. The Split/Merge is so quick and easy.
I know what a PITA it was to do what you did!
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at TMACsRack https://tmacsrack.wordpress.com/*
On Sun, Mar 8, 2020 at 8:44 PM tmac tmacmd@gmail.com wrote:
Oh No!
You should have asked!
There is a broadcast-domain merge and a broadcast-domain Split for just such these occasions!
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at TMACsRack https://tmacsrack.wordpress.com/*
On Sun, Mar 8, 2020 at 8:37 PM John Stoffel john@stoffel.org wrote:
Well, just to let you all know that the upgrade went great, and I even did the CN1610 cluster switch upgrade as well, even though the version I was on was still supported with 9.3P17.
The only real gotcha that hit me was having both regular and e0M ports in the same broadcast domain, which since the node_management ports were on e0M made it a *pain* in the ass to get them moved out.
I basically had to do:
- create new node_mgmt interface on another VLAN port.
- delete the one I really wnated,
- remove the e0M port from the broadcast-domain
- create a new new failover group and add e0M to it
- recreate a new node management lif using e0M again
- delete other temp lif.
Across four nodes, this sucked, especially to figure out. Then I found the "broadcast-domain split " command, which might have made this all oh so much easier.
Anyway, the actual upgrade went great, no outage for the VMs still on the ESX cluster, etc. Very very nice. Next time I ask them if I can just do this during the day instead. LOL!
John
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters