Black Friday discounts on VMware software, courses, and exam vouchers are already available on its Online Store in Australia (as well as in other countries).
Perfect time to save on certification offerings!
It was a great surprise for many virtualisation specialists to see an error message saying ‘Shockwave Flash has crashed’ immediately after authenticating in the vSphere Web Client 6.x earlier this week.
Most of the reports came from those who were using the latest version of Google Chrome (61.0.3163.100). However, there were similar issues with other web-browsers and Adobe Flash version 188.8.131.52.
This is a classic example of how dependency on a third-party technology can affect your solution. I hope that VMware accelerates the development of vSphere Client (HTML5) and provides feature parity between it and the Flash one.
For those who have plans upgrading their environment from vSphere 6.0 to 6.5 Update 1, I would suggest postponing this until VMware resolves issue documented in KB 2151749.
Hosts will be affected if they equipped with 10 Gbps NICs.
The only workaround that the vendor has at the moment is to downgrade ESXi to 6.0 Update 2.
17/10/2017 – Update 1: According to VMware GSS, this issue is going to be “resolved in ESXi 6.5 Patch 02, which is schedule to release this month (The release date may change without notice).” Please refer to the SR #17599111410 when contacting GSS for more information.
08/02/2018 – Update 2: This issue is resolved in VMware ESXi 6.5 P02 (ESXi-6.5.0-20171204001-standard).
This subject is not directly related to virtualisation. However, it can be useful when you are not going to utilise Group Policy, and still need to automate drive mapping.
The old school
net use <drive_letter:> <UNC_path_to_the_network_drive> /persistent:[yes|no]
Pros: simple command that works.
Cons: not native to PowerShell; can be deprecated in the future.
New-PSDrive -Name <drive_name> -Root <UNC_path_to_the_network_drive> -PSProvider FileSystem -Scope [Global|Local] -Persist:[$true|$false]
New-PSDrive creates temporary and persistent mapped network drives. The scope should be set to allow other applications properly use mapped drives.
Pros: native to PowerShell.
Cons: require PowerShell 3.0+ to be fully functional.
New-SmbMapping -LocalPath <drive_letter:> -RemotePath <UNC_path_to_the_network_drive> -Persistent:[$true|$false]
New-SmbMapping creates a Server Message Block (SMB) mapping on the SMB client to an SMB share.
Pros: native to PowerShell.
Cons: this cmdlet had some issues before PowerShell 5.0.
VMware has just released a new hotfix for ESXi and vSAN (KB 2151081) urging customers with all-flash configuration with deduplication enabled to upgrade their environment as soon as possible. This patch resolves data corruption issue which might appear in rare circumstances.
The affected versions of vSAN include 6.5, 6.6, and 6.6.1.
06-10-2017 – Update 1: As listed in KB 2151042, similar issue has been fixed for ESXi 6.0.
As you might already know, vSAN 6.6.1 is the first release with automated build recommendations for vSAN clusters for vSphere Update Manager, which should help to keep your hardware in a supported state by comparing information from the VMware Compatibility Guide and vSAN Release Catalog with information about the installed ESXi releases.
Obviously, this feature requires vSAN to have Internet access to update release metadata, as well as valid My VMware credentials to download ISO images for upgrades.
To help customers with enabling vSAN build recommendations, VMware embedded some health checks into vSAN 6.6.x that contribute to resolve configuration issues. The build recommendation engine health check detects the following states:
If the virtual environment seats behind the proxy, you should configure proxy settings in the Internet Connectivity option in vSAN_Cluster > Configure > vSAN > General.
Those parameters are kept in /etc/vmware-vsan-health/config.conf. Be careful with the user password, as it is added to this file without any encryption.
To test access through the proxy, you can click on the Get latest version online button in vSAN_Cluster > Configure > Health and Performance to update the HCL Database. If everything setup correctly, it will generate the following lines in /var/log/vmware/vsan-health/vmware-vsan-health-service.log:
INFO vsan-health[ID] [<user_name> op=UpdateHclDbFromWeb obj=VsanHealthService] Update HCL database from Web
INFO vsan-health[ID] [VsanHclUtil::_getHttpResponse] Download via proxy
However, even if the Internet connection works, the vSAN Build Recommendation Engine Health test will produce a warning message as follows:
In the log file you will see lines like these:
WARNING vsan-health[healthThread-c3ad57ea-a3f1-11e7] [VsanCloudHealthUtil::checkNetworkConnection] Internet is not connected.
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py”, line 337, in run
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py”, line 279, in collectedResults
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py”, line 230, in updateManifestWithPerCluster
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py”, line 190, in _updateManifest
manifestVersion = cls._queryManifestVersion()
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthDaemon.py”, line 174, in _queryManifestVersion
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py”, line 209, in getClusterHealth
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py”, line 247, in getObject
responseBody = self._getPhoneHomeResultsWithRetries(urlParams)
File “/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanCloudHealthConnector.py”, line 279, in _getPhoneHomeResultsWithRetries
VsanCloudHealthConnectionException: <urlopen error [Errno 110] Connection timed out>
Apparently, it is a bug in the current version of vSAN that is documented in the VMware KB 2151692. Neither fix nor workaround is available at the time of writing this blog post.
07/02/2018 – Update 1: A workaround to resolve this issue has been found.
After all exiting news from VMworld 2017, it is time to prepare my own list of questions, call friends and collegues, and be ready for vForum 2017 in Sydney!
The registration is open here.