UNSOLVED
Changing server cluster OS from vmware 5.1 to 5.5?
I stumbled on the fact my server mapping cluster on the compellent is still at vmware v5.1 when I have been on 5.5 for year. Rebooted hosts several time and upgraded SCOS 3 times. Everything still works.
Any issues with moving my server mapping cluster to v5.5? And what exactly does that do? mpio settings, etc? I hate to break anything.
Prime_RyanP
9 Posts
1521
0
Posted June 26th, 2015 09:00
In my experience ESXi 5.5 deals with those situations much better than previous versions... Or perhaps it's because I'm using iSCSI...
In an unrelated change I brought one of my ESXi hosts up with NO storage paths visible, however as soon as I reconnected the storage cabling and did a rescan on the iSCSI initiator everything was fine in vSphere....
Actually I had a 5.5U2 cluster(but missing the last couple express patches to prevent hostd from disconnected when it loses datastores)---and we lost 40 compellent volumes due an array failure,,,the other VMs stayed up that were on a different array but those hosts were disconnected from vcenter for hours while the array was fixed. I wish I had that patch one. An interesting note is the new APD settings you can use in vmware 6 that can really save you:
www.yellow-bricks.com/.../conservative-vs-aggressive-for-vmcp-apd-response
Prime_RyanP
9 Posts
1521
0
Posted June 25th, 2015 10:00
I changed my cluster mapping from 5.1 to 5.5 and didn't see any difference... Co-pilot recommend that I do that change during a maintenance slot and a period of low I/O as there is a small risk of APD scenario when switching.