Check vCenter Server inventory size

Similar Questions

• can restore us a vcenter Server inventory using vpxd.cfg only

  can restore us a vcenter Server inventory using vpxd.cfg only

  problem: restoring Vcenter server using vpxd.cfg file only

  No, you can't, vCenter inventory information is saved in vCenter database and not in vpxd.cfg.

  vpxd.cfg is the only configuration file for vCenter

• vCenter Server

  In case the server vCenter Server has encountered a problem and needs to re-setup of vCenter, what happens to what follows? They will always work?

  1. high availability

  2 DRS (automatic)

  3. distributed switch connectivity

  4 vSphere replication

  5. Advanced vSphere of data protection

  6 site Recovery Manager

  7 cluster VSAN

  During the time where the vCenter server is unavailable.

  1. high availability - Yes, but the management of Cluster HA is possible only when your vCenter gets online

  2 DRS (automatic) - No.

  3. distributed communication switch connectivity - Yes, the VMs will not face questions, data flow is managed completely by ESXi hosts, but your DVS control plan is not available to change the Setup in it.

  4 vSphere replication - work should, don't know if.

  5 vSphere Data Protection advanced - should work, not too sure.

  6 site Recovery Manager - no.

  7 cluster VSAN - Yes, but the handling of the VSAN that we are using vSphere Web Client is going to be affected.

  and if you need to re - install server vCenter completely. so in this case, you need to take action based on how you re - install your vCenter. For example, if you have fresh installation complete you vCenter server then you need to start building your vCenter Server inventory and take steps to add your ESXi hosts in this new inventory.

  many different references

  Distributed failure vSwitches and vCenter, what's the problem?

  VMware KB: Spend an ESX/ESXi host with vDS to a vCenter Server to another

  VMware KB: Move a managed ESX ESXi host to a vCenter Server to a different Server vCenter

• The upgrade of our guests 5.0 ESXi and vCenter Server 5 and 5.5 Enterprise Plus

  We are the 4 upgrade hosts of ESXi 5 to 5.5

  We add 4 more guests with own ESXi 5.5 installed

  We are also upgrading our vCS 5 in the vCSA 5.5

  Using Enterprise + licenses

  Question: I'm trying to understand the best way to achieve this transition.  4 guests run about 100 virtual machines and 4 guests we add are clean slates.

  That's what I think... Please help me guys

  1. once the 4 new hosts are installed in the Datacenter clean running ESXi 5.5 I will deploy the vCSA ovf and register 4 guests with the Linux-based device.

  2. now, I have 4 new 5.5 ESXi hosts registered and running with vCSA 5.5 but I still have my old 4 guests with ESXi 5 and registered to the old vCS about 100 virtual machines running WIndows

  3. at this point I think stop on my older hosts 4 virtual machines and remove them from the vCenter Server inventory Windows and everything just their registration with the new vCSA

  4. Will be all my virtual machines or transferred with the hosts if I close them and put the hosts in maintenance mode?

  5. now, I should have all 8 guests registered with my new vCSA.  But the original 4 hosts have yet to be upgraded to ESXi 5.5

  6 move 100 virtual machines to the new 4 hosts running ESXi 5.5 and upgraded the 4 former hosts.

  7. now, I should have 8 guests with ESXi 5.5 using the vCSA

  See you soon!

  Pretty much.

  To make things easier, you can deploy the EGGS for vCSA in your current vCenter (if I remember correctly import an OVA using vCenter allows you to set certain options that should be set to the vCSA shell). After making sure that the vCSA online & configured, you can then install ESXi on all your new hosts, add them to a cluster in the vCSA and put a few trials of virtual machines on there to confirm the network setting is configured correctly. Once it's done (and assuming that the old and the new hosts use the same shared storage) you can stop the vCSA, remove it stock Windows vCS, please write it on one of your new hosts and turn on. You have now two environments (5.0 and 5.5). Next if you disconnect a host from 5.0 vCS (with virtual machines running on it), you can then connect it to the vCSA 5.5. Assuming that the vSwitchs standard networking of the exchanges that are the same name in both environments, you now can vMotion VMs between host 5.0 and 5.5 cluster. At this time, you can repeat with all remaining hosts until everything has been made the transition without service interruption. This will leave a lot of old objects in your old 5.0 vCS, but if that is getting trashed it isn't a big deal.

• Impossible to connect to vCenter Server 5.5 using the vSphere Client

  Hello

  
  

  I'm trying to configure VMware Lab home using the link below and I have reached a stage where I need to connect to vCenter Server using the vSphere client.

  
  http://boerlowie.WordPress.com/2011/12/13/building-the-ultimate-vSphere-lab-part-9-ESXi/

  
  

  I installed the package of 5.5 full vCenter server using the simple installation option and it includes vCenter server, single sign - on, Webclient vSphere, vCenter server and vCenter Server inventory service. All the the latter is installed on a virtual machine that is running Windows server 2008 R2 guest OS.

  
  

  Whenever I try to open a session on the vCenter Server uses the vSphere client, one of the following error is displayed.

  
  

  1. you do not have the permissions to connect to the server 'vCenter server IP address.

  2. cannot complete the connection incorrect username or password-, this error is visible when I do not specify domain\username domain user name and simply enter the user name.

  
  

  For the details of the error, please see the screenshots - vSphere_client_1, vSphere_client_2 and vSphere_client_3.

  
  

  As suggested in the link below, I tried to create an SPN and then set the SPN (Principal of Service name) and the UPN (User Principal name) in the Active Directory identity Source using the web of vSphere client (please see screenshot vSphere_Webclient_2)

  
  

  http://vinfrastructure.it/2014/01/issue-in-logging-into-vCenter-server-using-Windows-ad-credentials/

  
  

  To fix the permission error, I tried to add the domain user to the Administrators group on the server vCenter (see screenshot vSphere_Webclient_1).

  
  

  However, none of the above-mentioned resolution has worked.

  
  

  So can someone please help? I am stuck because of this problem and badly need help to move forward.

  
  

  Thank you

  AJMAL
  

  Able to connect to the vSphere Client do you use the [email protected] account?

  Have you already set up permissions on the server vCenter object?

  André

• We get an error when I try to collect data from vCenter Server. But the Collection of Cluster works!

  Hello

  I m getting a strange errormessage when he tries to load my vCenter Server inventory.

  I have configured my vCenter Server as the endpoint server and I was able to load the Clusters. When I klick collection of data in a Cluster (Cluster of EQL 1) I can load all the data and the State is 'successful', but when I try to load the inventory FRO the vCenter Server (to get the models) im getting this error message:

  The treatment [inventory], error details error: illegal managed object reference type, folder.

  The same schows Agent logs:

  [26.08.2014 16:48:16] [Info]: start: treatment Workitem ID [2e38598e-4385-4b2d-bc88-fd2b773d1f98] [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.Admin.Hostname = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] VirtualMachine.Admin.ParentIdentity = [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.ManagementEndpoint.Name = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] VirtualMachine.ManagementEndpoint.Identity = [inventory]

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.ManagementEndpoint.Endpoint0 = vCenter

  [26.08.2014 16:48:16] [Debug]: [[inventory]] [inventory] VirtualMachine.Admin.Name = inventory

  [26.08.2014 16:48:16] [Error]: <? XML version = "1.0" encoding = "utf-16"? >

  < Boolean > false < / Boolean >

  Error parsing [inventory], details of the error:

  System.ArgumentException: Illegal managed object reference type, folder.

  at DynamicOps.Vrm.Agent.vSphere.VSphereGetHostsRequest.ExecuteImpl)

  at DynamicOps.Vrm.Agent.vSphere.VSphereHypervisorServiceProvider.GetHosts (ManagementEndpoint managementEndpoint)

  to DynamicOps.Vrm.Agent.Collector'3.get_Hosts)

  to DynamicOps.Vrm.Agent.Collector'3.CollectManagementEndpoints)

  to DynamicOps.Vrm.Agent.CollectInventory'3.Collect)

  to DynamicOps.Vrm.Agent.BaseHypervisorAgent'3.EnumerateHypervisorResources (collector collector 3, WorkItem workItem, PropertyBagHelper propertyBagHelper)

  to DynamicOps.Vrm.Agent.BaseHypervisorAgent'3.ProcessWorkitem (WorkItem workItem, task of the chain, PropertyBagHelper propertyBag)

  to DynamicOps.Vrm.Agent.vSphere.VSphereAgentService.ProcessWorkitem (WorkItem workItem, task of the chain, PropertyBagHelper propertyBag)

  to DynamicOps.Vrm.Agent.BaseAgent.ProcessWorkitem (WorkItem workItem)

  I hope that someone had an idea, im out of ideas.

  THX Steven

  There is no data for the endpoint collection... And I'm not entirely sure of how you added the vCenter object it... y at - it a calculation object named "vCenter? To answer your specific questions about the models, however, they must be stored on a cluster that is part of the tissue group for data collection to pick them up... They are not considered as a global entity (as a resource calculation). Add models to one of the clusters and then to collect data on it, and you should be fine.

• Having problems setting up a 5.5 vCenter Server VM in a domain configuration...

  I'm trying to implement a vCenter Server VM (new installation, no upgrade) without an Active Directory domain that is available.  I was able to do this successfully in the past with 5.0 and 5.1, but now with 5.5 I have problems.

  Installing SSO works fine and displays warnings expected that the server is not on a domain and the certificate will be bound to the INVESTIGATION period.

  When I then try to run Setup from the inventory Service, it fails when you try to connect to the SSO:

  "Could not connect to vCenter Single Sign On.  Make sure that the Search Service URL points correctly to the vCenter Single Sign On the instance that you installed.  If vCenter Single Sign-On is installed with an IP address, make sure that the IP address is specified in the URL.

  5.0 and 5.1, in order to get this installation runs correctly, I would like to enter the IP address in the URL (as it says in the error), and he'd be fine.  So the address provided for the Research Service URL is https://< ip_address >: 7444/lookupservice/sdk

  I tried several variants for the fields of FULL domain name and URL of the Service search without success.

  Can someone confirm a successful for 5.5 off-field installation?  And if so, try to direct me in the right direction?

  I end up doing work, it turned out to be an order of operations issue.

  I tried to install SSO, then service inventory, then Web Service, then vcenter Server.  And on a domain, this order actually worked well.  For some reason any, when not on a domain, they must go SSO-> Web Service-> Service-> vCenter Server inventory (this command works in both scenarios, just to be clear).

• VCenter Server 5.1 SSL certificate update - error

  Hi all

  We set up a new Windows 2008 R2 server as a vCenter Server 5.1

  Now, I try to install the new certificates for all parts of vCenter (server, inventory, web client service,...) with the Windows certification authority.

  I'm stuck at the update server certificate SSL vCenter with the 'Certificate SSL Automation Tool'.

  This is part 5. in this guide (5. the cmd screen shot):

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2041600 #updatestepsplanner

  All credentials are correct, but I still get the same error (vc-update - ssl.log):

  [26.04.2013 - 10:42:54, 99]: copy the new certificates and keys 'C:\ProgramData\VMware\VMware VirtualCenter\SSL. '... »
  [26.04.2013 - 10:42:55: 00]: creating the PKCS certificate file...
  Could not reload vCenter SSL certificates
  [26.04.2013 - 10:42:56: 22]: ""cannot reload the server vCenter SSL certificates. " The certificate could not be unique. » »
  [26.04.2013 - 10:42:56, 24]: new certificates and keys deleting...
  [26.04.2013 - 10:42:56: 25]: restoration of the certificates and the original keys...
  1 Datei () kopiert.
  1 Datei () kopiert.
  1 Datei () kopiert.
  [26.04.2013 - 10:42:56: 25]: attempt to restore...
  Could not reload vCenter SSL certificates
  [26.04.2013 - 10:42:57, 08]: ""cannot reload the server vCenter SSL certificates. " The certificate could not be unique. » »
  [26.04.2013 - 10:42:57: 10]: new certificates and keys deleting...
  [26.04.2013 - 10:42:57: 10]: restoration of the certificates and the original keys...
  1 Datei () kopiert.
  1 Datei () kopiert.
  1 Datei () kopiert.
  [10: 42:57, 13 - 26.04.2013]: failure of the update of the certificate of vCenter.
  
  
  So I tried the manual way, as it is mentioned in this guide:
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2035005

  I'm stuck here too, get a 'result of Method Invocation: vpx.fault.SecurityConfigFault ' after ""Invoke method ': "

  1. Go to https://localhost/mob/?moid=vpxd-securitymanager & vmodl = 1 on the server vCenter Server and load the certificates for the configuration using the managed object browser.
  2. Click continue if you are prompted with a warning on this certificate.
  3. Enter a vCenter Server administrator user name and password when prompted.
  4. Click reloadSslCertificate.
  5. Click the calling method. If successful, the window displays this message: result of Invocation of method: Sub.

  
  

  I tried to fix this, but there is not really a solution for this:

  http://communities.VMware.com/thread/429035

  so, I need help with this question

  SOLVED!

  Steps to follow:

  1. stop the vCenter service

  2. search for your ID in LS_ServiceID.prop in the folder C:\ProgramData\VMware\VMware VirtualCenter

  3. copy this ID (e.g. {C4672589-9258-42B1-90E2-1EF268BBD402}: 5 )

  4. change your vpxd.cfg in the same folder and replace

  vCenterService

  with

  your ID

  5. start vCenter Service

  Then, the SSL automation tool works!

  You need to undo changes.

• vCenter Server Upgrade version 5.0 to 5.1

  I have 3 vCenter servers (VM) who manage the 3 environments across different sites (Dev/Test/QA, Prod1 and Prod2).

  I intend to first upgrade in Dev/Test/QA environment. My Server, DB & MUV vCenter vCenter server resides on the unique virtual computer.

  1. I need to create separate VMS for vCenter Server Inventory Service & MUV.

  2. in a large environment, I have to separate the Server DB & consolidate all instances here? Best practices please.

  3. create separate SSO VM.

  To do this, how will be my approach? Can I restore my backups of DB and can be used in the new environment?

  Or everything will be totally new configuration?

  It will work. Like other components, you have the choice to use SQL Express or a dedicated DB for the SSO server.

• Problem migrating Vcenter server from the old cluster to the new cluster?

  Hey guys,.

  Just came across this situation, and I don't know what to do. I pass my vcenter server older glomerulus with hosts of esx4.0, to a more recent cluster with hosts of esxi4.1. The material of host machines are different generations, and vmotion don't migrate vcenter because of the cpu sets between cluster mismatch. If I could turn off the virtual machine and migrate it would work, but since it's my vcenter Server I can't do.

  Should I restore it on the new cluster?

  Thanks for the suggestions/tips

  Kevin

  Connect directly to the ESX host using your client vsphere, vCenter vm shutdown, vCenter remove inventory, then go to the new host, browse the data store on the vCenter vm is, and add the vCenter Server inventory.

  This assumes that the same storage is presented to both hosts.  If this isn't the case, you will need to use winscp or something similar to copy the files from the virtual machine.

  -KjB

• Relocation of the unusable VCenter Server after data store

  I needed to move the VCenter server only US planes of the DataStore has located on SAN1 to B data store located on SAN2 because we were retiring SAN1. After connecting directly to the VMhost which housed the vCenter Server VM, closing the vCenter Server and remove the vCenter Server inventory, I scoured data store A and moved the server vCenter to B data store directory. "After the copy is completed, I added the back inot inventory of vCenter Server, it works, toldi it"I moved"and received an error message indicating the file vCentersrvr.vmdk ' was absent.

  A review of the content directory for vCenter data store b shows no vCentersrvr.vmdk, but rather lists a file called vCentersrvr - flat hard. The type of file, the file is listed as "file". I tried to rename this gall and turn on/off the VM, but still no luck. Here are my questions:

  1. Can I save this installation? The original directory no longer exists (it was deleted automatically after the copy of the file).
  2. If I can't save this installation, can I just rebuild a new vCenter Server and Add (2) hosts that are currently managed by the vCenter Server server has failed?

  There is another method to recreate the descriptor VMDK files. http://www.phdvirtual.com/VMDKstubgenerator

• Check if virtual machines exist in a vCenter Server

  I would like to do the following with PowerCLI:

  -Import a text file with a list of virtual machines

  -Check if the virtual machines exist in vCenter Server

  -If yes, return to another file export

  How would I do this in PowerCLI?

  Thank you!

  It seems ok, I just did a reformatting to make it a little more readable.

  Your CSV file is correct?

  1st line of the column heading "VMname",.

  on the following lines, the names of the virtual machines you want to check.

• vCenter Server Component install hangs on the installation directory services

  Hello

  I'm on a 64-bit OS of Windows 2008. I update vCenter 5.5 Update 2 and 5.5 updated 3d.  I can install the SSO, WebClient and Inventory Service very well without any problems.  I get to the vCenter server component and it hangs on "Install Directory Services".  I checked the vminst.log and I get:

  "Try to start ["C:\Windows\system32\cmd.exe"/c start /w C:\Windows\system32\ocsetup.exe DirectoryServices-ADAM/passive /norestart].

  
  

  I Googled that and of course a dozen connections to users having problems with installing the server vCenter on Windows 2012R2 lack the ocsetup.exe. As I said, I'm still on Win2008.  I have not ran sfc/scannow - no chance.  I tried to copy the ocsetup.exe from a Win2008 well-known to vCenter box - same thing.  Tried different accounts thinking I have a bad profile - no luck.  Anyone have a similar problem?
  

  well, too bad.  I guess I wasn't be patient.  This time I let it "hang" and it finally finished after almost an hour.  At least see the progress bar move would have been useful.

• PowerCLI Script to migrate virtual machines with the same network Source for the new vCenter Server.

  Hi all

  I checked a few posts on the migration to the new vCenter Server virtual machine. But I'm not very good with Powercli and need some help here.

  We have a new vCenter server where we migrate virtual machines from one source vCenter server. Here are two things that I don't know how to connect together to make sure that bwfore we turn on the virtual machine to the virtual machine is connected to its source network.

  Part 1 - this script works well but do not get any network on the vCenter destination.

  cluster = Get-Cluster "clusterA.

  $inventory = get-Cluster $cluster | Get - VM | Add-Member - MemberType ScriptProperty-name "VMXPath" - value {$this.extensiondata.config.files.vmpathname}-Passthru-Force | Select-Object Name ResourcePool, folder, VMXPath |

  $inventory | Export-Csv c:\file.csv

  $inventory = import-csv c:\file.csv

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  Part 2 - I want to preserve the Portgroup macaddress and the Ip of the virtual computers and connect them to the new vCenter. How can I do this with the script below. Or how can I combine them together?

  $vm_list = get-Cluster-name "clustera | Get - VM test * | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  Step 2

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-RunAsync Verbose - confirm: $false

  Step 3

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool.Name

  New-VM - ResourcePool (ResourcePool-Get-name $resource_pool) VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  Step 4

  # Put the network cards

  foreach ($info in $inventory)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose-RunAsync-confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null}

  }

  Thanks in advance for any help.

  Hi all

  I made some changes to the script and it worked for me. We have added a host on the destination with all exchanges and storage mapped vCenter.

  $vm_list = get-Cluster-name 'Site B - b | Get - VM | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-Verbose - confirm: $false

  $cluster = get-Cluster "Site A - clustera.

  {foreach ($vm to $information)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm.path - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool

  New-VM - ResourcePool (ResourcePool-Get-name "test1") VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  # Put the network cards

  .

  foreach ($info in $information)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose - confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null

  }

  Hope this will help many of you.

• vCenter Server displays the error message: unable to connect to the host

  vCenter Server displays the error message: unable to connect to the host

  Symptoms

  • vCenter Server cannot connect to a host when you perform operations such as:

  •

  o Storage vMotion

  o cold migration

  o cloning a virtual machine

  o the model deployment

  • Newspapers vpxd that contains an entry similar to:

  [2009-06-04 19:27:16.326 error "App" 4444] [VpxdInvtHost] IP address change for 10.223.122.143 to 10.223.127.197 unhandled, verification of the SSL certificate is not enabled.

  • You see errors similar to:

  Unable to connect to the host o

  o [2009-06-04 19:27:09.952 'Libs' 3902384 WARNING] [NFC ERROR] NfcNewAuthdConnectionEx: unable to connect to peer (numRetries = 2). Error: Unable to connect to the host 10.223.122.143: connection timed out

  • vCenter Server shows the VMS as being disconnected then connected.

  Hello

  Resolution

  Cause

  This problem can occur if an ESX host's IP address is changed while being managed by vCenter Server.

  Check the cause

  To check the cause of the problem:

  1. Log in as root to the ESX host using a SSH client.
  1. In the file etc/opt/vmware/vpxa/vpxa.cfg, find the IP address of the host. The entry looks like:

     
     10.21.48.121
     

     Note: for more information about editing the files, see installation in VMware ESX configuration files (1017022).

  Troubleshooting

  If the IP address is incorrect, perform the following steps in order. If the operation does not resolve the problem, continue to the next step. Don't skip a step.

  1. Disconnect and then reconnect the host:
  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Reconnect the ESX host in vCenter Server.
  1. Restart the VirtualCenter agent on the ESX host:
  1. Stop the service of vpxa with the command:

     # service vmware-vpxa stop

  1. Open the /etc/opt/vmware/vpxa/vpxa.cfg file in a text editor and correct the IP address of the ESX host.
  1. Start the service of vpxa with the command:

     # service vmware-vpxa start

     Note: for VMware ESXi, you may have to restart all the management agents. For more information, see restart the agents on an ESX or ESXi Server (1003490) management .

  1. Rebuild the VirtualCenter agent on the ESX host configuration file:

     Attention: this step removes all the Statistics counters historical host and the virtual machine. If VMware ESX host is running in virtual machines that starts in a permitted CVS environment, you maybe won't be able to add the host without stopping the virtual machines first.

  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Remove the ESX host disconnected from vCenter Server.
  1. Backup the file vpxa.cfg with the command:

     # mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.oldcfg

  1. Add the ESX host disconnected to the server vCenter inventory.
  1. Run the following command to view the contents of /etc/opt/vmware/vpxa/vpxa.cfg and confirm that the host IP address is correct:

     # cat /etc/opt/vmware/vpxa/vpxa.cfg