Showing posts with label Client. Show all posts
Showing posts with label Client. Show all posts

Monday, May 18, 2015

Adding an uplink to VDS fails with an error "Call "HostNetworkSystem.UpdateNetworkConfig" failed

Hi,

I was just working on VDS and found out that while adding an additional Uplink to the existing VDS failed with the following error.

The environment consists of ESXi/VC 5.5 U2 and I have tried configuring the same using the vSphere client and also the Web Client and getting the same error using both methods. ESXi using Cisco UCS B-200 M3.

"Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-416016" on vCenter Server "esxhostname" failed"





Now I tried finding out the KB site of VMware and found out only few KBs related to the same error.

First one is KB 2081478 which I worked on at some time and mostly talks about the IBM 3650 M2 or M3 servers and the other one is KB 2013558 which is discussing the issue when migrating the vmkernel interface to VDS fails. My issue was not following in either of the categories.

So I started looking in to the issue further from VDS perspective and found out that the existing VDS is using two uplinks and I was trying to add 3rd uplink.

I looked at the properties of the VDS by going into  Home -> Inventory -> Networking and right click the VDS in question and hit Edit Settings and I saw the following.



As you can see the configured number of uplink ports are only 2 and I cant add more than that.

Now this simply very obvious that there are lot of factors / situations which can play the part here e.g. You forgot what you have setup initially when you built the environment for the first time or you are working on a pre-configured environment by someone else and you never know such configuration was done by whom and how long ago or there is no documentation available for such configuration.

Either of the cases will lead back to the troubleshooting process which was just to find out where things are wrong based on the error. But at the same time as the error itself if not do descriptive, you are in hands of your own knowledge and experience for the product or you need to engage the Support.

By now you might have already figured out the resolution, which was nothing else but just to increase the number of dvuplinks for that VDS. Once I increased to 3 I was able to add the 3rd pNIC as an uplink to that VDS.

Hopefully this will help to the readers.

Please share and care.

Cheers !!



Thursday, November 21, 2013

Changing Language of vSphere Client for ESXi host

Hi,

I was recently part of a discussion where there was a requirement on the customer's end to change the Language on DCUI of ESXi server as by default its using English.

Not sure about the exact reason to change the language but there is a file you can edit to change the Language of vSphere Client (C#) so here comes the bad NEWS. Technically its NOT possible to change the Language of DCUI. It will be English only.

You can connect to ESXi host with any of the following 6 Languages.

English: /?locale=en_US
German: /?locale=de_DE
French: /?locale=fr_FR
Japanese: /?locale=ja_JP
Korean: /?locale=ko_KR
Chinese: /?locale=zh_CN

In order to select the language, you need to append the language to the end of the vpxclient executable (vpxclient.exe) which is shown in the following example through command line French is selected:

"C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" -locale fr_FR


There are few articles published around the same subject matter so refer them according to your requirements.

Forcing a localized vSphere Client or vSphere Web Client installation to launch in a localized language/English


Why does my vSphere Client on French Operating System display in English when I connect to vCenter 

Hope you find this useful !!

Share and care !

Thanks for your time.

Sunday, April 29, 2012

Device or Resource Busy Error on vSphere client

I can hardly count the instances where anyone working with VMware vSphere environment has not encountered this error "Device or Resource Busy"

There are  some reasons why this error coming up.

Few instances mainly can be listed as follows

  • When you browse a datastore, it does not have any files or folders.
  • Under /vmfs/volumes/ there are no files or directories.
  • While deleting a datastore, you see the error:

    Device or Resource Busy
     
  • Deleting the partition table of this datastore does not resolve the issue.
  • Deleting a vmdk fails for the VM which is not longer in use 
There are few articles you can find here which discusses all these conditions and how to resolve them.


http://kb.vmware.com/kb/1015791   and  http://kb.vmware.com/kb/1039362

If you have encountered other instances which are not documented then you can always provide the feedback to the article and it will be updated accordingly.

If you search http://kb.vmware.com/ you may find other articles which highlights other issues apart from the listed above.

Hope you will find this information useful.