Term
|
Definition
* Check all host licenses (Standard and up). 3.5 hosts need a patch applied
* Min. 2 hosts/cluster
* Static IP address. If using DHCP, be sure to use reservations so the hosts IP will not change after reboot
* Common management network across all hosts (best practice is to have at least 2)
* Hosts must have access to all the same VM NWs
* VMs on shared storage
* VMware tools (for VM Monitoring)
* Host Certificate Checking
* Don't mix IPv4 and IPv6 cluster as you will be more likely to have a network partition |
|
|
Term
| Identify DRS Requriements |
|
Definition
* Hosts have access to shared storage
* Processors from same processor family (e.g. Intel Xeon) |
|
|
Term
| Identify vMotion Requirements |
|
Definition
* Shared storage requirements for vMotion in 5.0 (not necessary in 5.1) - datastores must be available to all hosts participating in the migration
* Each host to meet the networking requirements for vMotion - hosts to have a vmkernel port assigned to vMotion. This Network must reside on the same subnet on both hosts, named identically. Also, the nws that the VMs are attached to must also reside on both hosts and be named the same.
* Cannot vMotion VMs that are using RDMs for clustering purposes
* Cannot vMotion VMs that are backed by a device that isn't accessible to the target host. I.e. A CDROM connected to local storage on a host. You must disconnect these devices first. USB is supported as longa s the device is enabled for vMotion
* Cannot vmotion a VM that is connected or backed by a device on the client. You must also disconnect these first. |
|
|
Term
| Identify Storage vMotion Requirements and Limitations |
|
Definition
* VM disks must be VMDKs or RDMs in virtual compatibility mode (migrate the mapping file or convert to thick or thin provisioned disks as long as destination is not an NFS datastore).
* No migration during VMware Tools installation
* Licensing - Standard and above
* ESX(i) 3.x must be configured for vMotion
* Hosts need access to source and target datastores |
|
|
Term
| To check vMotion/storage vMotion configuration, you can look at vSphere maps. What should you check on the map? |
|
Definition
* Networks your VM is attached to and which hosts are in turn attached to that network
* The datastores your VM resides on and which hosts in turn have access to that datastore
* The current CPU usage of the hosts
* Hosts marked with a red X are not suitable and violate one of the vMotion requirements
* Hosts enclosed with a green circle are compatible for vMotion but still do not guarantee that it will complete |
|
|
Term
| What network do legacy ESX hosts use for HA? |
|
Definition
| Legacy HA hosts use service console networks for HA communications. |
|
|
Term
| What networks do HA communications travel on by default in ESXi? |
|
Definition
| On ESXi hosts in the cluster, vSphere HA communications travel over vmkernel networks, except those marked for use with vMotion. If there is only one vmkernel network, HA shares it with vMotion if necessary. |
|
|
Term
| What HA information can be found in the HA section on the 'Summary' tab of a cluster? |
|
Definition
Admission control settings, current and configured failover capacity, as well as the status of Host, VM, and Application monitoring. The runtime info link gives you your slot information (sizes, total slots available and overall, as well has counts of good and bad hosts.). The cluster status will show you who the master host is, the number of slaves connected to it, as well as which datastores are used for datastore heart beating and a count of protected VMs. The configuration Issues link will show you a list of all issues that have been detected on the cluster.
Source: blog.mwpreston.net |
|
|
Term
| What DRS information can be found in the HA section on the 'Summary' tab of a cluster? |
|
Definition
| The DRS section will show you your selected automation level, DPM status, DRS recommendations and faults, your configured threshold and your current and standard load deviation. The resource distribution chart will show you a stacked graph showing VMs memory and CPU usage statistics across the hosts in the cluster. |
|
|
