Re: Upgrade thoughts: 8.3 -> 9.1 -> 9.3
tmac <[email protected]>
| Newsgroups | gmane.comp.hardware.netapp |
|---|---|
| Message-ID | <CAL9X-_EXakTk=DP9zPgpcBtW-_KBKNz8Nv-wEouyq+Ys2rWtJQ@mail.gmail.com> |
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 <[email protected]> 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 > [email protected] > http://www.teaparty.net/mailman/listinfo/toasters > _______________________________________________ Toasters mailing list [email protected] http://www.teaparty.net/mailman/listinfo/toasters