483 reputation
31130
bio website SeanKilleen.com
location District of Columbia Metro area
age 28
visits member for 4 years, 5 months
seen yesterday

Dec
19
comment What is the correct way to remediate an HA Cluster?
@ewwhite, We're on ESXi 5.1 -- have 2 standalone hosts and two in the HA cluster. We have an older academic license on the standalone hosts and an Enteprise license on the HA cluster hosts (can do storage vMotion, etc.)
Dec
19
comment What is the correct way to remediate an HA Cluster?
Thanks, both of you. If I have two hosts in an HA configuration of say, server 1 and 2, can I manually force the VMs to migrate to server 2 and then take down server 1 for maintenance, or will this still cause the VMs to enter a failover scenario? Wondering if I can migrate to a specific host within a cluster or whether I'd have to migrate them onto a host outside of the cluster, essentially.
Dec
19
asked What is the correct way to remediate an HA Cluster?
Dec
14
comment ESXi 5.1 on Poweredge 510 freezes after base-esx update
That's correct. Looks like it was just a temporary bug at this point. I updated 3 other hosts just fine. Thank you for the additional tip on the OpenManage; I was able to attach it as a host extension which I didn't know was possible previously. Lots of great advice in this answer!
Dec
14
accepted ESXi 5.1 on Poweredge 510 freezes after base-esx update
Dec
13
comment ESXi 5.1 on Poweredge 510 freezes after base-esx update
I'll open a ticket soon, to be sure. Regarding the CIM agents, if using the Dell custom ISO for ESXi 5.1, that would have included the CIM agent update, correct? Or would I still need to create the extension baseline for the CIM to be updated? Was under the impression I wouldn't need that second step, but I could be wrong.
Dec
13
comment ESXi 5.1 on Poweredge 510 freezes after base-esx update
I'm not sure; I have a question in to some fellow admins to see if DRAC is enabled and if so, what the IP would be (I believe we're using a separate subnet for management access but it may not have been configured). I'm hoping so!
Dec
13
asked ESXi 5.1 on Poweredge 510 freezes after base-esx update
Dec
13
accepted vCenter Server: This host currently has no management network redundancy
Dec
12
accepted Potential VMWare 5.1 Fault Tolerance bug/issue?
Dec
7
comment vCenter 5.1 — adding v5.0 host doesn't bring in templates
Perfect, thanks! Didn't realize that these were actually kept along with vCenter Server. A quick browse fixed it!
Dec
7
accepted vCenter 5.1 — adding v5.0 host doesn't bring in templates
Dec
4
asked vCenter 5.1 — adding v5.0 host doesn't bring in templates
Dec
4
answered Potential VMWare 5.1 Fault Tolerance bug/issue?
Dec
4
comment Potential VMWare 5.1 Fault Tolerance bug/issue?
Interestingly enough, it appears that powering down the VM before applying FT was what I needed to do this. I may have done it differently initially. After confirming, I'll post the answer. Thanks for your help!
Dec
4
comment Potential VMWare 5.1 Fault Tolerance bug/issue?
@TheCleaner thanks for suggesting the additional options to explore. I read in a a support article that Automatic sometimes doesn't work. We're using intel Xeon processors. Our main system is a Dell R720 and the second is a Dell R520. Both have Xeon E5s (E5-2640 in the R720 vs E5-2430 in the R520). I will attempt to power cycle the VM as well.
Dec
4
comment Potential VMWare 5.1 Fault Tolerance bug/issue?
@TheCleaner also, please see updated question. I reset the VM to the same settings that worked the first time but it still won't turn FT on. My guess is it's already on still (from the first time) but vCenter is confused somehow. No idea how to verify that, though.
Dec
4
revised Potential VMWare 5.1 Fault Tolerance bug/issue?
Added more information and steps
Dec
4
comment Potential VMWare 5.1 Fault Tolerance bug/issue?
Normally I would, except that now the only option in the fault tolerance menu is "turn fault tolerance on". It was already previously turned on, and I executed the test without using this option (which I will consider next time). It appears VMWare thinks it is no longer fault tolerant. And I can't change the CPU/MMU options without restarting. Which means 2 restarts for a VM whenever a fault occurs to reconfigure FT. Seems like a bug / issue.
Dec
4
revised Potential VMWare 5.1 Fault Tolerance bug/issue?
edited tags