Latest Posts



Translate

Total Pageviews

Monday, 30 April 2012

An internal error has occurred: Failed to serialize response.

This is known issue and listed in the Vmware Vsphere Release Notes also this error An internal error has occurred: Failed to serialize response is occured when you will try to access the Storage maps from the vSphere Client by connecting it to vCenter Server for a Software iSCSI/FCoE Initiator.
if you are getting this error and if it is possible to remove the esxi from vCenter Server then you can apply this solution:-
1. Disable the iSCSI initiator on ESXi.
2. Remove the ESXi from vCenter Server.
3. Directly connect ESXi from vSphere Client then enable software iSCSI initiator and configure it.
4. Then Add host in to vCenter Server. Now you will not face any issue with the storage maps from datastore and datastores clusters inventory view.

Note:- One more thing if same LUNs are shared by multiple ESXi hosts and one esxi host storage is configured prior to add in the vCenter then Storage Maps problem will not occured for this esxi host as well as for that esxi host that is sharing same LUN even no Software iSCSI Initiator is added by you on that host before adding that on the vCenter Server. 

With software FCoE enabled, attempts to display Storage Maps fail with an error messageThis problem affects only those ESXi hosts that have been added to vCenter Server without any previous software FCoE configuration. After you enable software FCoE adapters on these hosts, attempts to display Storage Maps in the vSphere Client fail. The following error message appears: An internal error has occurred: Failed to serialize response.

for more information check this link:-
https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-50-release-notes.html#storageissues

Vmware Communities FAQ

Here is link given below for the vmware communities Info:-
http://communities.vmware.com/docs/DOC-12285

Thursday, 19 April 2012

vMA Permission Denied Issue....

Sometimes this is the problem with the vMA that it's not possible to create file or folder in the vMA. So here is the solution that how to give the read and write permissions to vi-admin in vMA :-

Boot the vMA 5.
In the Grub bootloader window, select the first option “SUSE linux Enterprise Server 11 SP1 for VMware” and press ‘e’ to edit this line.
Go to the second line, that starts with “kernel /vmlinuz..” and again press ‘e’ to edit. Move to the end of the line and add the following:init=/bin/bash and press [Enter].
At this point, the difference with previous versions. I was used to add “single” at the end of this line. Doing this, the vMA 5 will ask for a root password. Adding “init=bin/bash”, will start a bash shell and allow you to start the passwd command.
After pressing [Enter], you will return to the previous window. Now press ‘b’ to boot the vMA. The vMA will boot and ends up with a command prompt.
and then run the follwing command:-
 
mount -o remount,rw /
and reboot the machine after that. Now it's possible for the vi-admin to create files and folders in vMA.

Wednesday, 18 April 2012

VMware Acronyms


·  FDM = Fault Domain Manager

·  CSI = Clustering Services Infrastructure

·  PAE = Propero Application Environment

·  ESX = Elastic Sky X

·  GSX = Ground Storm X or Ground Swell X

·  VPX = Virtual Provisioning X

·  VPXA = Virtual Provisioning X Agent

·  VPXD = Virtual Provisioning X Daemon

·  VMX = Virtual Machine eXecutable

·  AAM = Automated Availability Manager

·  VIX = Virtual Infrastructure eXtension

·  VIM = Virtual Infrastructure Management

·  DAS = Distributed Availability Service

·  ccagent = Control Center agent

·  vswif = Virtual Switch Interface