Fast Lane Support with MyVMware Mobile App – Overview of VMware BCS and MCS Support


If you are responsible for any running Mission critical or Business critical workloads in your VMware Virtual datacenter you better to have Fast Lane support with Mission Critical or Business Critical support from VMware. It reduces the amount of time for your support request escalation along with the personalized reactive and proactive support services. It’s a separated subscription service and depend on the company requirement. I will discuss the features later in this post.

MyVMware Mobile App is a great tool to log High Priority support request without using your computer and web browser. You can download this app from itunes for your iPhone/iPad and Google play store for Android mobiles and tabs.

You need to have the corporate MyVMware account to operate this application. Once you installed the App on your device login using the corporate MyVMware username and password. Read More

A Server error occurred. [500] SSO error:null


Previously, I wrote a post about re-pointing the PSC and after a while I logged in to the same environment and I ended up with this error message on my screen. I was so frustrated as I have done few changes to this environment and thought something went wrong while I was doing these changes. See below error message that I received from my vCenter Server appliance.

So , I started to troubleshoot this issue. Simply it says check the vSphere Web Client logs for more details, that is the simplest way which we can start this. so I opened a ssh session to my vCenter server appliance and enabled the shell. I used below command to check the vSphere client log

Read More

Nested Virtualization: VCSA 6.5 deployment on Oracle Ravello Cloud


I was building a lab on Oracle Ravello Cloud and I wanted to install VMware vCenter Virtual Appliance 6.5 on a deployed ESXi host. I started the deployment as usual and the deployment failed in the middle of the VCSA configuration. It was not able to power on and below error message deployed in the ESXi host client. “Failed to power on virtual machine <VM_NAME>. You are running VMware ESXi through an incompatible hypervisor. You cannot power on virtual machine until this hypervisor disabled“. See below error message.

So I tried to manually Power on the Virtual Machine and was not able to do that and ended up with the same error message again and again. Read More

Installation of component VCSServiceManager failed with error code ‘1603’. Check the logs for more details.


I was deploying a vCenter 6.x with a separate Platform Service Controller and a database, installation was not successful due to the below error messages. In the middle of the installation it gave me an error message saying “An error occurred while starting the service ‘invsvc'” and rolled back the installation at the end.

At the end gave me the below error message

Read More

vCenter 6.5 High Availability – Possible Configuration Issues

Hope you read my previous post with related to the VCSA 6.5 HA configuration. Again!, this is a new feature came with VMware vCenter 6.5 to minimize the down time of the vCenter server. That is one of the cool feature so far. 
Here, I would like to share something that I experienced while I was deploying and configuring the vCenter HA feature. I believe, this will make your life more easier if you are configuring the “HA” feature.

SSH should be enabled …

First of all, I mentioned that SSH should be enabled on the appliance if you are deploying the nodes, otherwise you will get a notification and deployment get failed. 
So, what you have to do is just enable the SSH on the appliance and start the deployment again. Please follow the below steps to enable the SSH on the appliance. 
Login to the Appliance Management console, use “https://<FQDN or the IP of the VCSA>:5480 to access the web console
You will get the management console
Go to “Access” option, you can see the status of the SSH and the Bash shell. Click on “Edit” to change the status. 
Select the Login you want to enable, here we need to enable the SSH, Click “Ok” to continue 


“Failed to get the Management information….”

Ok, now we have enabled the SSH which is a primary requirement for this feature. But I got the below error at the second attempt of my installation.
Error appeared in the configuration Wizard 
So I started to looking for a solution as I was not able to find any issues with my NIC0. I was able to find this KB article and I was able to fix it after following the steps. I found that this caused due to the upper case letters in the hostname. So, it’s a good point and if you are deploying this feature make sure to use the lowercase hostname for the appliance and you won’t get this error.
Logged to the Appliance using SSH with the root credentials
Grant the shell access to the root. Executed “shell.set –enabled true” command and hit enter. Logged to the shell using “shell” command
Typed this command to check the hostname of the appliance “cat /etc/vmware/systemname_info.json | grep -i vCenter_hostname”
See my output highlighted in red, it was in the upper case letters
I wanted to update the “systemname_info.json” file, so took the snapshot of the VM as in many scenarios and took the backup of the “systemname_info.json” file using the “cp” command
Checked the backup file (I’m normally doing this step)
Updated the “systemname_info.json” file using the vi editor 
Updated the file (hit “insert” to enable the editing mode)

From this

To this 

Verified the updated name using “cat” command 
So I rebooted the Appliance and started to configure the HA feature, it was successful. 

Addition to this …..

In any case if you configured the HA feature and it was not successfully configured, getting the the invalid configuration warning as stated in below, remove it and proceed again.
Click “Yes” to remove the HA cluster 
So that’s the way to remove the vCenter HA Cluster. So this is my experience in HA feature deployment. Thank you for reading my post.

VMware vSphere Performance Data Query Limitation

There are couple of applications are in place to get the resource utilization, operations handling, capacity review and for some other tasks in my day to day activities, we came up with few issues after we upgrade our old vCenters to vSphere 5.5 and we were not able to get the performance data of my VMware clusters through the vSphere APIs.
After doing some researches we found that there is a small parameter configuration to over come with this issue. Basically, my blog post is about VMware KB article 2107096. Here, I’m explaining the steps which we did the parameter configuration to fix my API issue.
 This issue came in to the play as it is setting the limit of maximum performance metric database queries to a threshold of 64 in the vCenter. Symptom of this issue was when we were querying the data it was throwing an error saying “Request processing is restricted by administrator”. Let me show you the way of fixing this step by step, as I mentioned earlier this is following the VMware KB article 2107096.
Login to the vCenter, select the vCenter server and go to the “Manage” tab. Select the “Advanced Settings”. Add the parameter config.vpxd.stats.maxQueryMetrics and set the Value as -1. If this is already added you can see the parameter in the list. 
Note: If you added the parameter incorrectly, you can remove the parameter form this file. 

Once you correctly added the parameter you can see it like this.

Edit the web.xml file

Navigate to the web.xml file located in C:ProgramFilesVMwareInfrastructureTomcatwebappsstatsreportWEB-INF
Find the maxQuerySize Parameter and Change the value from 64 to 0.

That’s all and I was able to pull the performance data through the APIs.

VMware vSphere Update Manager had an unknown error. Check the events and log files for details – ERROR after the Upgrade

I came across with this error after upgrading the VMware vSphere Upgrade Manager 5.0 to 5.5. Let me give you the background of the issues first.

We had to upgrade the VMware vSphere 5.0 environment to 5.5 and we have successfully upgraded the vCenter and next step was to upgrade the ESXi hosts to 5.5. I will write another article on the vCenter upgrade process in my blog later. Once we upgraded the Update Manager we were able to upgrade the ESXi server base to 5.5, but we were not able to scan the hosts to apply the patches.

We were getting the below error message all the time when we were scanning the hosts.

I was searching a solution in the internet and was not able to find a proper solution or suggestion for my error, that’s where I forced to write this article. Finally, we decided to create a new database for Update Manager and reinstall the Update Manager on the same server with the new database. That’s how we fixed this error and we were able to scan the hosts and apply the patches.

The Update Manager logs were not throwing the errors during the scanning process, this was the logs output during the error.

This was the error displayed in the Update Manager tab

I think this will help someone to overcome with similar issues, there can be some other ways to fix the same issue and I really appreciate if you can share them with me if you fix this in a different and easy way.


Detected an invalid snapshot configuration : msg.snapshot.error-NOTFOUND.

I was informed this issue as an unexpected Powered off situation of the Virtual Machine and it was requesting a disk consolidation in the summery tab. When I was trying to Consolidate the VMDKs it was throwing the below error message.

After checking the recent Tasks and Events I was able to identified that there was a Virtual Machine level backup and it was closed due to an error. There was no proper reason other than saying the “Backup failed” error message. 

Good thing was there was no any pending or created snapshot in the Snapshot Manager. I had a thought of creating a new snapshot and perform the “Delete All” task as it was helping me to fix most of the Snapshot related backup issues. Bad luck.. it didn’t help me either at this time. I can confirm that offline Storage vMotion also got failed after throwing the same error message. 
I identified the Datastores which were keeping the VMDKs and the Configuration files and it was similar to this. I’m really sorry I had to blur the image details. 
Then I checked the configuration file of the Virtual Machine as it gave me a clue saying “NOTFOUND” and I wanted to find out what was the not found item of the Virtual Machine? I opened the .vmx configuration file from the Notepad. Luckily, I was easily identify the missing items. See my below output. 
It was pointing to  vmdks which contain “<virtual_machine_disk_name>-000002.vmdk (snapshot delta vmdks)” for each and every disks, there were no actual VMDKs as it was pointing in the .vmx file.
Then I had to manually edit the .vmx file as I had no other choice, we were not able to restore this Virtual Machine at that time.
Note: Manually editing the .vmx file can be lead to a Virtual Machine corruption or data loss, edit it at your own risk. 
I have removed the “virtual_machine_disk_name>-000002.vmdk” entries and added the existing disks to the configuration file. Virtual Machine Powering on was successful and I got the confirmation as there was no data loss. In my case,luckily there were no actual delta vmdks and I did not end up with a data loss. If you are removing the Existing delta file entries, definitely you will end up with a data loss which was in the removed delta disk. 
Again, Do it at your own Risk!

Warning: This host currently has no management network redundancy

This is a common Warning message when you are working with Management vmkernels, VMware confirmed that this message can be safely ignored and issued a KB Article to fix the warning.

Even though you can ignore the Warning message, you can see this as a Configuration issue of your ESXi Hosts.

I’m creating this Article following up the above VMware KB and overcome with this warning message.

  • Right-Click on your Cluster and select “Edit” to edit the cluster settings. Once you get the cluster settings window, select the “vSphere HA” section and select the “Advanced Options…” button to add a advanced parameter 
  • Once you get the “Advanced Options” window add the “das.ignoreRedundantNetWarning” as the advanced Option and set the value as “true” and click “OK” to continue
  • Now Right-Click on the ESXi Host and select ” Reconfigure for HA” then you can see that the cleared Warning in your Host.
Thank you for viewing my post ……

Warning:System logs are stored on non-persistent storage

When you are booting up an ESXi host using a USB or SD card you might commonly get this “System logs are stored on non-persistent storage” Warning message on your ESXi Hosts.

I came across with this when I’m implementing a Cluster with Dell Power Edge servers and Hypervisor OS was installed on the SD cards.

When OS uses the USB or SD card to boot up it’s OS the logs are stored in a non-persistent storage such as “/tem” directory and it throws the ” esx.problem.syslog.nonpersistent” error message. The impact of this warning is ,host keeps it’s logs as a temporary files and will be deleted after a reboot, these logs might need for further troubleshooting ,identify issues and auditing tasks of your environment.

To over come with this error simply you need to specify a storage directory  to keep these log files. You can specify this under your “Advanced Settings” in the “Software” section of the host.

Go to the “Advanced Settings” , expand the “Syslog” and select “global” parameter. Then you can simply identify “,logDir” Parameter

Specify a Datastore which can store these log files with a folder (simply you can put one of the datastores name within the square brackets) “[<datastore_name>]/scratch/log” as the parameter and click “OK”.

Then you need to restart the host to take the effect of the change.