- Joined
- Feb 8, 2005
- Messages
- 13,308
Backstory:
At work, we've got a production cluster of 6 hosts, labeled esx2-7. (1 is the vCenter Server). This cluster has DRS set to "Fully Automated" and HA enabled. The cluster was basically full. We were between 96GB and 128GB of RAM short should one of the boxes fail - Our needs exceeded our capacity. Well, one of the boxes showed an amber light - DIMM warning. We need to pull it, reseat it, and keep an eye on it. This obviously means bringing one of the hosts down. Thankfully, an identical box was freed up by another project. We tossed ESXi on it, added it to the cluster, and waited for DRS to start relieving pressure on the other hosts.
Well, we're still waiting. Not a single migration has occurred to the new host. I can see the VMs being moved around to the other hosts, but the new, unused host is sitting there without a single freaking VM on it.
I intended to put the host which needs maintenance into maintenance mode, and let DRS vMotion the VMs off it, but right now I'm wondering if DRS is even working right. Isn't it supposed to perform load balancing? Why would it ignore the new host? Will I need to go through and manually move every VM off esx3 onto esx8? If I do, how do I tell DRS not to consider esx3 as a host that it can move VMs to?
At work, we've got a production cluster of 6 hosts, labeled esx2-7. (1 is the vCenter Server). This cluster has DRS set to "Fully Automated" and HA enabled. The cluster was basically full. We were between 96GB and 128GB of RAM short should one of the boxes fail - Our needs exceeded our capacity. Well, one of the boxes showed an amber light - DIMM warning. We need to pull it, reseat it, and keep an eye on it. This obviously means bringing one of the hosts down. Thankfully, an identical box was freed up by another project. We tossed ESXi on it, added it to the cluster, and waited for DRS to start relieving pressure on the other hosts.
Well, we're still waiting. Not a single migration has occurred to the new host. I can see the VMs being moved around to the other hosts, but the new, unused host is sitting there without a single freaking VM on it.
I intended to put the host which needs maintenance into maintenance mode, and let DRS vMotion the VMs off it, but right now I'm wondering if DRS is even working right. Isn't it supposed to perform load balancing? Why would it ignore the new host? Will I need to go through and manually move every VM off esx3 onto esx8? If I do, how do I tell DRS not to consider esx3 as a host that it can move VMs to?