This release resolves the following issues related to vCloud Automation Center:
Attempts to perform vCloud Automation Center tenant administration operation fail with an error
When you attempt to perform any vCloud Automation Center tenant administration operations such as removing an administrator from the default tenant (vsphere.local), the operation fails with a System Exception error.
Attempts to log in to vCloud Automation Center fail if the SAMAccountName contains extra trailing spaces
When you attempt to log in to vCloud Automation Center, the login attempt fails if the SAMAccountName attribute contains extra spaces trailing at the end of the name.
Attempts to log in to vCloud Automation Center fail if the password contains the colon (:) character
While attempting to log in to vCloud Automation Center, if you use a password that contains the colon (:) character, the login attempt fails.
Attempts to use the Windows Session Authentication feature might fail
When you log in to vCloud Automation Center by using Windows Session Authentication on browsers such as Internet Explorer, Google Chrome, and Mozilla Firefox might fail due to an error in the VMware Client Integration Plug-in. An error message similar to the following is displayed:
Windows Session Authentication login has failed as a result of an error caused by the VMware Client Integration Plugin
Attempts to log in to vCloud Automation Center fail if a custom UPN suffix is configured in the alias field for AD over LDAP
When you attempt to log in to the vCloud Automation Center where the custom UPN suffix is configured in the alias field for Active Directory (AD) over Lightweight Directory Access Protocol (LDAP), the login attempt fails.
This issue is resolved in this release.
Attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error
If you specify the Global Catalog (GC) port in the AD over LDAP Identity Provider’s (IDP) connection string, attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error message similar to the following:
Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 10
You can also see log messages similar to the following in the vmware-sts-idmd.log file:
2014-04-09 14:18:16,564 ERROR [ServerUtils] Exception
LDAP error '
The vCenter Server 5.5 Update 1c can be downloaded here and the release notes can be found here.
Few months ago I ‘ve upgrade our vCenter appliance from version 5.1 to 5.5, here are the installation steps
A customer asked me to repair their Veeam Backup & Replication 7.0 backup job, some virtual machines were showing this warning message in the backup log:
Failed to index guest file system. Veeam Guest Agent is not started
The default Domain Administrator (Veeam Service Account) credentials are not working at the standalone / workgroup virtual machine that is running in the DMZ VLAN.
Note: Make sure the virtual machine has the latest version of VMware Tools installed
To configure specific credentials:
- Edit the backup job
- Navigate to: Guest Processing > click: Advanced
Going Hyper-Converged with Software Defined Storage
|| Featured Speakers:
Chris M Evans,
Independent Consultant, Langton Blue Ltd.
Product Manager, StarWind Software 23July 11am PT / 2pm ET
As the concept of hyper-convergence (combining compute, networking and storage) continues to gain acceptance and adoption, this webinar discusses what features to expect from hyper-converged solutions and how they can be delivered exclusively through software. As well as a technical discussion of the issues, the webinar will look at vendor implementations from VMware’s VSAN to StarWind Virtual SAN platform.
During the webinar, you will learn:
- What defines and differentiates hyper-converged and how these solutions fit in with software defined storage
- Essential features to look out for in hyper-converged products
- Vendor roundup – market players and features of their products
- Technical feature comparison of VMware and StarWind Virtual SAN offerings
Last week I had some issues with unmounting some old datastores in a vSphere 5.5 environment. In the GUI it look like:
When I tried to unmount / detach the datastore I received this error message::
Call “HostDatastoreSystem.RemoveDatastore” for object “datastoreSystem-330″ on vCenter Server “itvvca01.domain.local” failed.
Operation failed, diagnostics report: Unable to query live VMFS state of volume.: No such file or directory
SAN01_VMFS04 datastore state accessible: false….
You can easy detach the inaccessible datastores with the following command:
Get-Datastore SAN01_VMFS0* | Unmount-Datastore
Or per specific datastore:
Get-Datastore SAN01_VMFS01 | Unmount-Datastore
Get-Datastore SAN01_VMFS02 | Unmount-Datastore
More information: VMware
After installation of VMware vSphere 5.5 Update 1 connectivity to NFS storage could be randomly lost with volumes reporting All Paths Down state. This issue was noticed around mid April and reported here.VMware documented the issue in KB article 2076392 Intermittent NFS APDs on VMware ESXi 5.5 U1
At June 10 VMware released a patch for this issue as described in KB 2077360. The patch can be downloaded using VMware Update Manager or using VMware download page
Last week I installed some new vSphere hosts with flash disk storage. Some hosts has a yellow caution icon and a message stating:
Configuration Issues – System logs on host [hostname] are stored on non-persistent storage.
Verify the location of System logs:
- In vSphere Client, select the host in the inventory panel.
- Click the Configuration tab, then click Advanced Settings under Software.
- Ensure that Syslog.global.logDir points to a persistent location.
The directory should be specified as [datastorename] path_to_file where the path is relative to the datastore. For example, [datastore1] /systemlogs.
- If the Syslog.global.logDir field is empty or explicitly points to a scratch partition, make sure that the field ScratchConfig.CurrentScratchLocation shows a location on persistent storage.
After a few minutes the logs are stored at the new location (in this case I used central storage):
More information: VMware
This year’s vExperts 2014 were announced! Check it out. I’ve been honored again (2010, 2011, 2012, 2013) as a vExpert this year. Great thanks to VMware and vExpert team behind the program!
It’s Correy Romero who announced the news on the VMTN blog. This year over 700 vExperts (exactly 754 vExperts this year) were named. Here is the full list of lucky people for 2014 – vExperts 2014.
vExpert program allows greater recognition between your coworkers, clients and in the overall professional life.
Source: VMTN blog
During the network configuration at the VMware Data Protection (VDP) appliance I received this warning message:
IP/DNS could not be resolved. Please check the hostname, domain, and DNS values for forward and reverse lookup validation
VMware VDP whitepaper: Before you deploy vSphere Data Protection, an entry needs to be added to the DNS Server for the appliance IP address and FQDN. This DNS Server must support forward and reverse lookup. Failure to have DNS set up properly can cause many runtime or configuration issues.
As you can see, the nslookup failed:
Add the domain and search domain in the /etc/resolv.conf file
And make sure you’ve created a correct PTR record at the DNS server for reverse DNS functionality, at the DNS server:
Select: Create associated pointer (PTR) record
More information: VMware