"tmac" == tmac tmacmd@gmail.com writes:
tmac> The biggest gotcha from 8.2 -> 8.3 is the MGMT LIFs.
Yeah, this has been one of the big things I needed to address, as well as updating routing groups for said management LIFs.
tmac> To be sure to catch this, you could also upgrade to the highest tmac> 8.2 release available for your platform. They have checks in tmac> there to catch it as well.
I've been using both the pre-check script in the "system node image update ..." commmand to check this, as well as the PowerShell script 83UpgradeCheck.ps1 which I found on the Netapp site. A very very useful script.
It should actually be used for general auditing as well, since it's found a few systems using iSCSI which are only logged in via one path on one node. Not good for failover!
tmac> Pre-8.3, MGMT info all went out the cluster managent LIF.
Which kinda made sense, but not when you wanted to have complete VServer independence for re-seller situations.
tmac> 8.3+ -> all SVMs must have their own MGMT LIF if the SVM need to communicate tmac> outside (like DNS, Active Directory, NIS, etc)
tmac> A SAN-only SVM does not require the MGMT LIF, but why not...;put a MGMT LIF on tmac> every SVM.
And now we all know why IPv4 space is running out, SVM management IPs! *grin*
tmac> Best to create a MGMT-only LIF while you are at it (no tmac> data-protocols on the LIF) Make MGMT LIFs for management and tmac> data LIFSs for data
tmac> Go to the support site and run upgrade advisor for your systems!
Already did, and I'm neck deep in the 8.2 -> 8.3 planning. I'm really looking forward to the more automatic upgrades in the future. Though it will still be an issue for CIFS users.
Thanks for all the comments! John