NEW VC, vSphere Client & VDP Version Releases this week from VMware!!

Well, not only has this week seen the belated by one month Patch Tuesday by Microsoft, VMware followed suit with two releases themselves...

VMware vCenter Server Release 6.5b

Updated on: 14 March 2017
vCenter Server 6.5.0b | 14 MARCH 2017 | ISO Build 5178943
vCenter Server Appliance 6.5.0b | 14 MARCH 2017 | ISO Build 5178943
vCenter Server 6.5.0b on Windows | 14 MARCH 2017 | ISO Build 5178943

http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-vcenter-server-650b-release-notes.html

You can use the link to see everything, but here's What's New:
This release of vCenter Server 6.5.0b delivers a number of bug fixes that have been documented in the Resolved Issues section.

• Updates to time zones in the Linux Guest Operating System customization. vCenter Server Linux guest operating system customization supports latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Linux guest operating systems, see the Time Zone Database by Internet Assigned Numbers Authority (IANA).
• Updates to time zones in the Windows Guest Operating System customization. vCenter Server Windows guest operating systems customization supports the latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Windows guest operating systems, see the Microsoft Knowledge Base article 3162835.
• Updates to JRE package. The Oracle (Sun) JRE package is updated to version 1.8.0_121 to support Turkish timezone.
• Additional functionality to the vSphere Client. This release delivers additional functionality to the HTML5-based vSphere Client. For more information, see Functionality Updates for the vSphere Client.

Here's more detail on the Updates to the vSphere Sphere Client in VC 6.5b:

First vSphere Client (HTML5) update debuts in VC 6.5b

https://blogs.vmware.com/vsphere/2017/03/first-vsphere-client-html5-update-vsphere-6-5-b.html

New Features – Huge Jump

The online documentation for vSphere 6.5.0b is the best source for detailed documentation on what functionality is now available (http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-client-65-html5-functionality-support.html), but for comparison sake, the bits are just after Fling v3.2, plus a few minor things. The only notable addition beyond v3.2 is the “Accept License” page on OVF deploy, which we specifically pushed into this patch to enable OVF deploy.
This is the list of some of the additional functionality included. Note, some of these features are presented in a partially complete manner. For example, OVF deploy in 6.5.0b will only support URL deployment (no local file). The plan is to fill out all of these features, but the more feedback we get from you regarding what is most important will help us deliver faster.

• OVF Deploy
• Deploy VM from Content Library
• Drag and Drop
• VM conversion to/from templates
• Actions on multiple VMs
• Register VMs
• SDRS management
• Dashboard
• Advanced network operations – Distribute switch, Port group creation
• Datastore create, mount and unmount
• Storage overview
• Host configuration (PCI Passthrough)
• Host profiles compliance monitoring
• Roles and permissions
• Create Tags and categories

Some of these flows may have had minor tweaks to make them easier to use and learn. If you have feedback about any of the new behavior, or missing portions of features, of course let us know using the integrated feedback tool by clicking on the smiley face in the upper righthand corner.

vSphere Data Protection Release 6.1.4 (VDP)

http://pubs.vmware.com/Release_Notes/en/vdp/61/data-protection-614-release-notes.html#fixedproblems

List of fixed problems:

Fixed Problems

The following table lists the problems that have been fixed in this release of vSphere Data Protection:

Defect Number	Description
265470	When you perform an FLR, and you browse for a virtual machine, the vSphere Data Protection GUI displays a misleading error.
268134	A replication recovery job that runs on a target vSphere Data Protection appliance publishes the task by specifying the source server as unknown.
274652	Tivoli Java Collections Library is vulnerable that enables exploitation of port 7778 by running a command on a remote client.
	Fix common vulnerabilities and exposures (CVEs) that are found in third-party libraries by updating vSphere Data Protection appliance with Avamar OS rollup version Q4 2016.
	On vSphere Data Protection appliance, update the Java runtime binaries version to 8u121.
	Provide support for vCenter Server 6.0 U3.
	On vSphere Data Protection appliance, enable TLS 1.2.
	Fix the error, System accounting is not in use: System accounting not found in /etc/cron.d/sysstat.

Analyzing Virtualization CPU Performance

There are always many questions around CPU performance. Most individuals I speak with are providing 2 or more vCPUs to the VMs mainly because they feel more is better. Having an extra vCPU cannot hurt performance, right? Well that is not always the case, but lets not limit our discussion to this one topic. What can affect CPU performance? There are primarily 4 of areas of concern:

1. Idle VMs – Due to timer interrupts on idle VMs it can cause more overhead than when the VM is in use.
2. CPU Affinity – You may receive a positive impact on performance for the virtual CPU that is pinned to a physical CPU using affinity, however this can cause a performance issue on the rest of the system as the scheduler must try to work around the affinity in order to balance the load. It is strongly advised to not use CPU affinity.
3. SMP VMs – When using multiple processors there is a co-scheduling overhead
4. Low CPU resources – When there is contention the CPU scheduler will force vCPUs of lower priority to queue their requests, now all VMs are operating slower

Now that you know the 4 items that can affect performance we need to understand the Key Metrics to monitor, they are:

1. Host CPU used – the amount of time that the hosts physical CPU was used erring that sampling period. 
2. irtual machine CPU used – the amount of time that the virtual CPU was actively using the physical CPU during that sampling period. Virtual machines that are utilizing virtual SMP can have their information displayed as an aggregate of all virtual CPUs within the virtual machine or per virtual CPU.
3. Virtual machine CPU ready time – the amount of time the virtual CPU was ready but could not get scheduled to run on the physical CPU. Virtual machines that are utilizing virtual SMP can have their information displayed as an aggregate of all virtual CPUs within the virtual machine or per virtual CPU. 

We can monitor this with many tools both free and not so free tools, the free tools provided by VMware are the vSphere Client and esxtop/resxtop. Here are a couple of screen shots:

vSphere Client Chart Legend - CPU Ready Time in Milliseconds

resxtop Output - CPU Usage per VM

It is important to understand the differences between the information gathered through the vSphere client and esxtop. The vSphere client information is gathered utilizing 20 second intervals where esxtop information is gathered using 5 second intervals. It is always important to normalize the values for comparing the output from these two monitoring tools.

You can use the vSphere client to monitor CPU performance for the hosts, clusters, resource pools, virtual machines and vApps. There are two important items to take notes regarding use of the vSphere client performance charts:

1. Only two counters at a time can be displayed in the chart.
2. The virtual machine object shows aggregate data for all the CPUs within the virtual SMP virtual machine. The numbered objects tracked the performance of the individual virtual CPUs.

If you see a short spike in the CPU used or CPU ready that will normally indicate you are making good use of your host resources. If both values are constantly high the host is probably overcommitted. The values to watch for negative performance would be above a 90% for the CPU used to value and a CPU ready value that is above 20%. 

Do not forget that the time values are different between the different tools used to monitor the CPU values. If you are monitoring a physical number you will need to know the sampling time in order to figure out the percentages involved.

The #1 Warning sign is Ready Time and as expected this latency can affect the performance of the guest operating system. 2000ms or higher indicates contention issue. The below picture shows an example of a VM with inverted usage compared to Ready Time. 

Ready Time and Usage on a single VM

The #2 warning sign is a high used value which can be determined by host CPU used or VM CPU used. This is not always an indication of poor CPU performance. You may wonder why! Keep in mind this is not a physical CPU meaning that what the VM is using does not always indicate that the host is maxed out nor does it always indicate you need more vCPUs. It may just be telling you there is high utilization which is a good thing!

My personal favorite tool for analyzing performance is esxtop/resxtop. You can run esxtop directly on the host and resxtop on the vSphere Management Assistant Appliance. Below are the definitions you need to know in order to analyze what is happening:

• PCPU USED(%) – CPU utilization per physical CPU
• Pre-group statistics
• %USED – Utilization (includes %SYS)
• %SYS – VMkernel system activity
• %RDY – Ready time
• %WAIT – Wait and idling time
• %CSTP – Pending co-schedule
• %MLMTD – Time not running because of a CPU limit
• NWLD – number of worlds associated with a given group

The following commands are the most common when monitoring CPU performance:

• Press spacebar – immediately updates the current screen
• Press s – prompts you for the delay between updates, in seconds. The default value is 5 seconds and the minimum value is 2 seconds.
• Press V – that is a capital “V”. Displays virtual machine instances only. Do not confuse with the lowercase “v”, which is to view the storage virtual machine resource utilization. If you need to switch back to CPU utilization then type the c.
• Press e – toggles whether CPU statistics are displayed expanded or unexpanded. The expanded display includes CPU resource utilization statistics broken down by individual worlds belonging to a virtual machine. All percentages of the individual worlds are percentage of a single physical CPU.

It is important to know what to look for and what tools can help you get that information, we will take a look at more CPU issues in later blog posts. Be sure to post any questions on http://www.vmtraining.net/forum/