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 05-23 - NIC Teaming Policy



Room for improvement:

The first paragraph in the slide notes state:

Default NIC teaming policies are set for the entire standard switch. These default settings can be overridden at the port group level.
Correct:

Once again, the statement above is incomplete: the NIC teaming policy can also be overridden at the single VMkernel port level. This is confirmed by what just explained on a previous slide notes page (number 05-19 "Network Policies" on page 201) in the students' manual, when providing the overview description of the network policies:

These policies are defined for the entire standard switch and can also be defined for a VMkernel port or a virtual machine port group.

Read more...

VSICM55 - Slide 05-22 - Configuring Traffic Shaping



1. Room for improvement:

The first paragraph in the slide notes state:

You can establish a traffic-shaping policy at either the virtual switch level or the port group level.
1. Correct:

The statement above is incomplete: the traffic-shaping policy can also be set at the single VMkernel port level. This is confirmed by what just explained on a previous slide notes page (number 05-19 "Network Policies" on page 201) in the students' manual, when providing the overview description of the network policies:

These policies are defined for the entire standard switch and can also be defined for a VMkernel port or a virtual machine port group.


2. Room for improvement:

A similar consideration goes together with the above when reading the last sentence in the first paragraph in the slide notes:

Settings at the port group level override settings at the virtual switch level.
2. Correct:

The same override also applies when setting the traffic-shaping policy at the VMkernel port level.



3. Wrong:

There is a small typo in the last phrase of the third item, Burst Size, in the bulleted list describing the three traffic-shaping parameters:

This parameter tops the number of kilobytes that have accumulated in the burst bonus and thus transfers at a higher speed.
3. Correct:

This phrase should be corrected as follows:

This parameter tops the number of kilobytes that have accumulated in the burst bonus and thus transfered at a higher speed.

Read more...

VSICM55 - Slide 05-20 - Security Policy



Room for improvement:

The first paragraph in the slide notes state:

Security policies can be defined at both the standard switch level and the port group level.
Correct:

The statement above is incomplete: the security policy can also be set at the single VMkernel port level. This is confirmed by what just explained on the previous slide notes page (number 05-19 "Network Policies" on page 201) in the students' manual, when providing the overview description of the network policies:

These policies are defined for the entire standard switch and can also be defined for a VMkernel port or a virtual machine port group.

Read more...

VSICM55 - Slide 04-71 - Adding a Host to the vCenter Server Inventory



Wrong:

Slide notes incorrectly state that:

To add a host to the vCenter Server inventory, you must be in the Hosts and Clusters inventory view.
Correct:

With the vSphere Web Client shown in the slide graphic, you can also add a Host to the vSphere inventory by using the Inventory Lists for Datacenters, Hosts, and Clusters.


Read more...

VSICM55 - Slide 04-39 - Viewing Truncated Lists



Wrong:

There is a typo in the first paragraph of the slide notes:

A truncated list is a list that never shows more than a specified number of objects. Having a truncated list means return a search will return a certain number of objects initially, but have the capability to return more objects if requested.
Correct:

Just disregard the highlighted typo in the quoted text.


Read more...

VSICM55 - Slide 04-34 - Accessing vSphere Web Client



Room for improvement:

The description of the URL to use for accessing the vSphere Web Client is rather vague. Slide notes state:

Use the browser to navigate to the URL in the example by using the server’s or client’s FQDN or IP address.
Correct:

Personally, I would rather reword the phrase as follows:

Use the browser to navigate to the URL in the example by using vCenter Server or vSphere Web Client FQDN or IP address.

The former case - vCenter Server FQDN or IP address - is to be used when a Windows-based vCenter Server has been deployed using the Simple Install setup type or you are using the vCenter Server Appliance. In this case, vCenter Server and vSphere Web Client FQDNs or IP addresses are the same as they run on the same system.

The latter - vSphere Web Client FQDN or IP address - is to be used when the vSphere Web Client server has been installed on a separate Windows system by leveraging the vSphere Custom Install procedure.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 04-32 - vSphere Web Client Architecture



Room for improvement:

The introduction in the slide notes is somehow confused:

The vSphere Web Client uses the architecture shown. Accessed from a browser run on a machine of the user’s choosing, the vSphere Web Client is accessed from vCenter Server directly.
Correct:

It's the vSphere Web Client that directly accesses, via the network, the vCenter Server:

The vSphere Web Client is a Web application installed on a machine with network access to your vCenter Server installation.
Source:

VMware vSphere 5.5 Documentation Center.

 

And it's the vSphere Web Client that actually pulls data from the vCenter Server DB when users navigate through the various screens and views, not vice-versa. This is further explained in a later sentence within the same slide notes paragraph:

The application server runs a flex client that feeds the user interface data to the browser. This flex client pulls information from the Inventory Service on the vCenter Server system that provides data optimized for the Web UI to the flex client.

Read more...

VSICM55 - Slide 04-23 - Configuring the vCenter Server Appliance Time Zone



Wrong:

The slide notes and graphic refer to a feature that was available in previous vSphere editions. For vSphere 5.5, please, disregard them completely!

Correct:

As previously stated, when correcting slide number 04-22, in the VMware vCenter Server Appliance console, you can use the arrow keys to navigate and select the Timezone option, but you cannot change the Timezone as the console exits the command-line interface immediately and returns back to the VMware vCenter Server Appliance welcome screen.

By design, the Timezone is set to UTC and cannot be changed in the vCenter Server Appliance console.
Source:

VMware Knowledge Base articles.


Read more...

VSICM55 - Slide 04-21 - Importing the vCenter Server Appliance



Room for improvement:

The deployment options description of the vCenter Server Appliance is rather meagre. According to the "vSphere Installation and Setup" guide - "Installing vCenter Server" chapter - "Download and Deploy the VMware vCenter Server Appliance" paragraph:

The vSphere Web Client connects to vSphere through the vCenter Server, but cannot connect directly to an ESXi instance. If your vSphere environment does not already have vCenter Server installed, use the vSphere Client to deploy the vCenter Server Appliance to an ESXi instance. Alternatively, you can use the OVF Tool, which is available, with documentation, from VMware Communities at https://communities.vmware.com/community/vmtn/automationtools/ovf.

In either case, if you want to use a static IP address (which should be the most obvious choice), you have two options to setup the vCenter Server Appliance networking configuration:

  • Log in to the vCenter Server Appliance command-line interface selecting the Login option in the vCenter Server Appliance welcome screen. Then use the vami_config_net tool, located at /opt/vmware/share/vami/vami_config_net to setup the IP configuration and host name.
  • Log in to the vCenter Server Appliance web GUI at https://<VCSA_FQDN_or_IP_Addr>:5480/, tick the Accept license agreement option box in the vCenter Server Setup wizard and click Next. Then cancel the wizard and use the Network tab to configure the Network Address Settings. When finished, go back to the vCenter Server tab and click the Launch button in the Utilities panel to restart the Setup wizard and complete the appliance configuration.
Once your vSphere environment includes a vCenter Server instance, you can use the vSphere Web Client to deploy the vCenter Server Appliance to an ESXi instance through the vCenter Server.

In this case, leveraging the OVF Deployment Options via the Deploy OVF Template wizard in vCenter Server, using the Properties screen in the vSphere Client or the Customize template screen in the vSphere Web Client, you can setup both the appliance IP configuration and host name automatically.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 04-22 - Starting the vCenter Server Appliance



Wrong:

The first sentence in the slide notes states:

After a vCenter Server Appliance is up and running, the console screen allows for configuring the time zone.
Correct:

Actually, in the VMware vCenter Server Appliance console, you can use the arrow keys to navigate and select the Timezone option, but you cannot change the Timezone as the console exits the command-line interface immediately and returns back to the VMware vCenter Server Appliance welcome screen.

By design, the Timezone is set to UTC and cannot be changed in the vCenter Server Appliance console.
Source:

VMware Knowledge Base articles.


Read more...
Subscribe to this RSS feed