Main menu
Fabrizio de Luca

Fabrizio de Luca

Italian freelance VMware Certified Instructor (VCI) and VMware Certified Mentor (VCM) based in Milano, teaching official VMware courses for the major VMware Authorized Training Centers (VATC) in EMEA. Website URL:

VSICM55 - Slide 10-26 - vSphere HA Settings: VM Monitoring



Room for improvement:

When describing VM and application monitoring, slide notes forget to mention that - starting with vSphere 5.5 - VMware now offers a much better application monitoring option for users purchasing the Enterprise Plus license.

On top of the default vSphere HA cluster capabilities to monitor for application heartbeat signaling, a new appliance vSphere App HA can offer a much better service.

vSphere App HA leverages VMware vFabric® to monitor applications. Deploying two virtual appliances per vCenter Server - App HA and Hyperic - vSphere App HA is a new feature that complements the functionality of VMware vSphere® High Availability with application-level monitoring and automated remediation.
 
App HA improves application uptime through:
  • Policy-based application monitoring and remediation.
  • Integration with vSphere HA to provide multiple recovery options, e.g. restart the application service or restart the virtual machine.
Source:

VMware vSphere App HA product pages.


Read more...

VSICM55 - Slide 10-25 - Admission Control Policy Selections



Wrong:

When describing the various Admission Control policies, the second bulleted list item in slide notes state:

Define failover capacity by reserving a percentage of the cluster resources (the default).
Correct:

The above mentioned Admission Control policy is not the one selected by default when you click the Turn ON vSphere HA checkbox. Instead, the default selected Admission Control policy is Define failover capacity by static number of hosts.

Info:

For best practices about configuring vSphere HA Admission Control policy, see the "vSphere Availability" guide - "Creating and Using vSphere HA Clusters" chapter - "Best Practices for vSphere HA Clusters" paragraph and related topics.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 10-23 - vSphere HA Settings: Host Monitoring



Wrong:

When describing the VM restart priority and Host isolation response options, slide notes state:

Possible values are Disabled, Low, Medium, High, or Use cluster setting.

And, later on:

The values for the host isolation response setting are Leave powered on, Power off, Shut down, and Use cluster setting.
Correct:

The Use cluster setting value is not an option when configuring either the VM restart priority or the Host isolation response features at cluster level. They can be instead configured for each and every virtual machine in the VM Overrides panel, available within the Configuration section of the cluster settings.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 10-22 - Enabling vSphere HA



Wrong:

The ordered list in the slide notes describing the required steps to activate and configure vSphere HA states:

  1. Right-click the cluster in the inventory and select Settings.
  2. In the Edit Cluster Settings dialog box, select the Turn On vSphere HA check box.
  3. Configure vSphere HA settings.
Correct:

There is a missing step in the above list before you can get to the Edit Cluster Settings wizard page as shown in the slide graphic. Hence, the list should be better amended as follows:

  1. Right-click the cluster in the inventory and select Settings.
  2. [Missing step] Select vSphere HA under the Services section and then click the Edit button.
  3. In the Edit Cluster Settings dialog box, select the Turn On vSphere HA check box.
  4. Configure vSphere HA settings.

Read more...

VSICM55 - Slide 09-74 - Viewing and Acknowledging Triggered Alarms



Wrong:

The second item in the ordered list within the slide notes states:

The Triggered Alarms view is displayed. The Definitions view shows a list of all alarms that are enabled for this object.
Correct:

The Alarm Definitions view is not located within the Monitor tab, but it can be found in the Manage tab.


Read more...

VSICM55 - Slide 09-33 - Resource Pool Summary Tab



Wrong:

The last bulleted list item at the end of the slide notes states:

The Commands pane (not shown) allows you to perform actions like creating a virtual machine, creating a resource pool, and editing a resource pool’s settings.
Correct:

In the vSphere Web Client (shown in the slide graphic) there is no Commands pane in the Summary tab of a resource pool object. The mentioned pane is available in the Windows-based vSphere Client only.

In the vSphere Web Client, instead, an equivalent feature con be found in the Actions menu, which opens a contextual menu showing all the available tasks that can be executed for the selected object.


Read more...

VSICM55 - Slide 08-11 - Integrating ESXi with Active Directory



1. Wrong:

First sentence of the third paragraph in the slide notes states:

You can configure the host to join an AD domain so that a user trying to access the host is authenticated against the centralized vCenter Single Sign-On user directory.
1. Correct:

Joining an ESXi host to an Active Directory domain eliminates the need to create and maintain local user accounts, simplifies the ESXi host configuration and reduces the risk for configuration issues that could lead to unauthorized access.

However, this process does not involve vCenter Single Sign-On server, rather, the host actually queries the AD domain directly. Additionally, provided you've been granted appropriate permissions, once an ESXi host has been configured to use an Active Directory service, you can login directly to the host - either via the vSphere Client or the direct console user interface (DCUI) - using an AD user account even when vCenter Single Sign-On is not available.

Hence, the above sentence should be better reworded as follows:

You can configure the host to join an AD domain so that a user trying to access the host is authenticated against the centralized AD user directory.
1. Source:

VMware vSphere 5.5 Documentation Center.



2. Wrong:

Second sentence of the third paragraph in the slide notes states:

Whenever you are asked to provide credentials (for example, when using vSphere Web Client to log in directly to the ESXi host), you can enter the user name and password of a user in the domain to which the host is joined.
2. Correct:

As of vSphere 5.5, you cannot use the vSphere Web Client to log in directly to an ESXi host, only the Windows-based vSphere Client - a.k.a. vSphere C# Client - can!


Read more...

VSICM55 - Slide 08-10 - Enabling and Disabling Lockdown Mode



Wrong:

Whilst describing how enable or disable the lockdown mode from the host direct console user interface (DCUI), last sentence in the slide notes states:

To enable or disable lockdown mode, select Configure Lockdown Mode from the Host Properties page and press Enter. Choose to enable or disable.
Correct:

Besides being a somehow logically acceptable description, there is no page called Host Properties. The actual page, this sentence is referring to, is named System Customization.


Read more...
Subscribe to this RSS feed