Main menu

VSICM55 - Slide 11-22 - Removing a Host from the DRS Cluster



Wrong:

When describing the side effects of removing a host from a cluster, the second item if the bulleted list in the slide notes states:

Virtual machines with disks on local storage must be powered off, suspended, or migrated to another host and datastore by using EVC.
Correct:

EVC - Enhanced vMotion Compatibility - is something completely different from what you need here to migrate virtual machines either to a different host or to another datastore.

This is a typo, likely caused by a "search & replace" task with the text editor. The author, here, very likely wanted to say Enhanced vMotion (hence the typo while shortening the term), which has been now renamed into Cross-Host vMotion in vSphere 5.5.


Read more...

VSICM55 - Slide 11-19 - Viewing DRS Recommendations



Wrong:

When describing the vSphere DRS tab, the first paragraph in the slide notes states:

The DRS tab displays information about the DRS recommendations made for the cluster, the faults that have occurred in applying such recommendations, and the history of DRS actions. You can access three views from the DRS tab: Recommendations, Faults, and History.
Correct:

If you look at the vSphere Web Client, which is show in the slide graphic, elements names in the GUI are different than those mentioned above. Hence, the paragraph should be amended as follows:

The vSphere DRS link under the Monitor tab for the cluster displays information about the DRS recommendations made for the cluster, the faults that have occurred in applying such recommendations, and the history of DRS actions. You can access three views from the vSphere DRS tab: Recommendations, Faults, and History.

Read more...

VSICM55 - Slide 11-12 - DRS Cluster Settings: DRS Groups



Wrong:

The last sentence in the second paragraph of the slide notes states:

On the slide, Blade Chassis A, Blade Chassis B, and ISV-Licensed are host DRS groups.
Correct:

This description refers to something that is actually not displayed anywhere in the slide. This sentence is a leftover from previous editions of this course.


Read more...

VSICM55 - Slide 11-09 - EVC Cluster Requirements



Room for improvement:

While describing the CPU vendors' supporting technologies for EVC, the second sentence in the slide notes states:

EVC automatically configures hosts whose CPUs feature Intel FlexMigration and AMD-V Extended Migration technologies to be compatible with vSphere vMotion with hosts that use older CPUs.
Correct:

The actual complete Intel's marketing name for the technology is Intel VT FlexMigration.

Source:

VMware White Papers.


Read more...

VSICM55 - Slide 11-07 - Other Cluster Settings: EVC for DRS



Wrong:

While describing how to enable EVC, the first sentence in the slide notes states:

In the VMware EVC section of the New Cluster dialog box, you can enable Enhanced vMotion Compatibility (EVC).
Correct:

In the vSphere Web Client, shown in the slide graphic, the mentioned section is actually called EVC only.


Read more...

VSICM55 - Slide 11-06 - DRS Cluster Settings: Automation Level



Wrong:

While describing how to enable vSphere DRS, the first paragraph in the slide notes states:

Type a descriptive name for your cluster and select the Turn On VMware DRS check box.
Correct:

In the vSphere Web Client, shown in the slide graphic, the mentioned check box is actually called Turn On only and is available within the DRS section.


Read more...

VSICM51 - Slide 12-25 - Using vSphere HA and DRS Together



Wrong:

The first sentence in the "NOTE" section of the slide notes is incomplete and dies abruptly.

For more information about resource pools and using DRS to manage operations such as virtual machine placement and providing dynamic resource allocation for virtual machines running on VMware cluster hosts.
Incomplete:

The phrase construct seems to suggest a URL to visit for more information, yet the text doesn't provide one.


Read more...

VSICM51 - Slide 12-23 - Removing a Host from the DRS Cluster



1. Wrong:

The last sentence in the first paragraph in slide notes states:

Right-click the host and select Remove.
1. Correct:

This sentence is out of the context: if you right-click a host and select Remove, you remove it from the vCenter Server, not the cluster. To remove a host from a cluster, instead, you need to:

  • Right-click the host in the inventory and select Enter Maintenance Mode.
  • When the host is in maintenance mode, drag it to a different inventory location, either the top-level datacenter or to a different cluster.
1. Source:

vSphere 5.1 Documentation Center.



2. Wrong:

The second bullet in slide notes state:

Because a host must be in maintenance mode before you can remove it, virtual machines with disks on local storage must be powered off or migrated to shared storage with vMotion. Virtual machines on shared storage will be migrated.
2. Correct:

vMotion migrates only the virtual machines execution context from one host to another; it is instead Storage vMotion that migrates virtual machines files to a shared storage.

2. Info:

The above quoted sentence is rather confused and should be revised as it might give students a wrong idea about the process. Basically, to remove a host from a cluster, you need put it into maintenance mode. In order to do so, all of its virtual machines must be either shutdown, suspended or evacuated.

  • Shutting down or suspending all virtual machines in the host will be enough to let it enter the maintenance mode, regardless where virtual machines files are located.
  • If virtual machines are instead to be evacuated whilst they're still up and running, then:
    • If virtual machines are stored on a shared storage, they can be evacuated from the host either manually with vMotion or automatically by DRS, if set to "Fully automated" automation level.
    • If virtual machines are stored on a local storage, they have to be - first of all - manually migrated to a shared storage using Storage vMotion, then evacuated from the host either manually with vMotion or automatically by DRS, if set to "Fully automated" automation level. Alternatively, Enhanced vMotion - introduced in vSphere 5.1 - can be leveraged to combine vMotion and Storage vMotion into a single operation to manually evacuate all virtual machines.

Read more...

VSICM51 - Slide 12-19 - Viewing DRS Cluster Information



Wrong:

First sentence in slide notes states:

The VMware DRS pane in the cluster’s Summary tab appears only when DRS is enabled.
Correct:

The new name for the Distributed Resource Scheduler feature in vSphere 5.x is vSphere DRS. Additionally the same is true for the "VMware DRS" pane in the outdated screenshot in the slide graphic, which instead should now read "vSphere DRS".


Read more...
Subscribe to this RSS feed