VMware has republished the patch for ESXi 6.0
The update resolves the CBT Bug
I’ve published a new tool that helps to quickly decode SCSI error codes displayed in vmkernel.log when something gone wrong. The tool uses an internal database to translates SCSI codes to human readable status information.
Please do not hesitate to comment when there are any questions, or you’ve encountered an error with the decoder.
How does it work? Let’s assume that your vmkernel.log shows the following error mesage:
2011-04-04T21:07:30.257Z cpu2:2050)ScsiDeviceIO: 2315: Cmd(0x4124003edb00) 0x12, CmdSN 0x51 to dev “naa.[…]” failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
Simply enter the colored hexadecimal numbers to the form and press Submit:
The result and a short description is displayed:
When you’ve entered all information, you can copy the URL for future reference. You can find the above example here.
VMware has republished the patch for ESXi 5.5 (ESXi550-201504002) that has been recalled this week.
The update resolves 41 issues including the following:
VMware ESXi 5.5 Patch Release ESXi550-201504002
(build number: 2702864)
After upgrading to VMware ESXi 5.5 Patch Release ESXi550-201504002 (build number: 2702864) with VMware NSX for vSphere 6.x or Cisco Nexus 1000v, Virtual machines on VXLAN wires are unable to communicate across hosts with their Edges or Distributed Routers.
If you have already upgraded, perform a rollback to the latest version:
You’ve just installed vSphere 6 vCenter Server Appliance (VCSA) and want to use the “Use Windows session authentication/credentials” checkbox like you know it from the vCenter Server running on a Windows Server?
You’ve already added an Active Directory as Identity source, and you can login with AD users, but the “Use Windows session authentication/credentials” still does not work?
You see the following error messages in the vSphere Client:
Windows session credentials cannot be used to log into this server.
Or in the vSphere Web Client (If the checkbox is greyed out, install the Client Integration Plugin from the bottom of the login page):
This post explains how to get the “Use Windows session” checkbox to work
When analysing performance metrics in the vSphere Web Client (Monitor > Performance) or in the vSphere Client (Performance Tab) you might have seen the following messages instead of performance graphs:
“No data available”
“Data is not collected for the current statistics level. Increase the statistics level to view the graph.”
Interval Duration determines the frequency at which statistics are stores:
Statistic Level determines the amount of data gathered and which counters are available for displayed. The default Level 1 stores the fewest metrics, Level 4 stores all metrics supported by the vCenter Server.
With vSphere 6.0, vCenter Server supports 544 metrics but as there are only 4 statistic levels it is not clear what metrics are included in each level. This post helps to understand what metrics are included in each level, and how you can add single metrics to lower levels. This might be helpful if you need single metrics from level 2, but do not want to activate all level 2 metrics.
Please note that changing the collection level beyond level 1 or adding a large number of data counters to collection level 1, might result in a significant reduced performance.
This is a list of all available performance metrics that are available in vSphere vCenter Server 6.0. Performance counters can be views for Virtual Machines, Hosts, Clusters, Resource Pools and other objects by opening Monitor > Performance in the vSphere Web Client.
These performance counters can also be used for performance analysis with esxcfg-perf.pl, or PowerCLI.
VMware has published an update for vCenter Server 5.0 and 5.1 where CVE-2014-6593 (SKIP-TLS) has been fixed.
It was discovered that the SSL/TLS implementation in the JSSE component in OpenJDK failed to properly check whether the ChangeCipherSpec was received during the SSL/TLS connection handshake. A man-in-the-middle attacker could possibly use this flaw to force a connection to be established without encryption being enabled. The update has been already fixed in newer versions of vCenter Server (6.0a, 5.5 Update 2e). More information are available in VMSA-2015-0003.
In the past three years I’ve presented several systems that can be used for VMware Homelabs. Servers for home use are typically not rack based. A good home server is inexpensive, silent and has a low power consumption. In this post I am going to revise the systems presented in previous posts to see how they work with ESXi 6.0: