ESX 4.0 U1 host disconnects the VC

Similar Questions

• 5.1 ESXI host disconnects the vcenter, when reconnected SSL fingerprint has changed.

  I'm having a strange problem with only 1 of the 5 hosts connected to a cluster inside of vcenter. A host disconnects randomly vcenter.

  I right click on the host and select Connect. I get the default value to the warning that 'reconnect a host will replace any change in management of resources that have been made directly on the host... ". ». I select Yes.

  Then, I get an error

  The authenticity of the host SSL certificate is not verified. This option is to close.

  I am taken to the add hosts Wizard. where can I enter the password IP and root to add the host to the cluster.

  Now, I get a security alert:

  "Impossible to verify the authenticity of the host: the SHA1 of the certificate fingerprint is:

  The fingerprint shown is different every time I add this host.

  I worked through vmware following popular KB with no resolution.

  VMware KB: Diagnose an ESXi/ESX host that is disconnected or not responding do not in vCenter Server

  VMware KB: ESXi/ESX host disconnects from the server vCenter Server after you add or connect to the inventor

  VMware KB: Troubleshooting network and TCP/UDP port on ESX/ESXi connectivity problems y

  We have tried, replacing the network card management network is on, replace the cables, the port of the switch, that this machine is connected, completely reinstall esxi switch. Nothing has solved this problem.

  Someone at - it other things to try?

  It turns out that the problem is that our agile took place of the intellectual property that it wasn't supposed to and it's a double that esxi host IP. Very strange behavior. But it's the solution.

• ESX host disconnect the vcenter

  Hi, I have ESX host running over the past decades, I configured vCenter 4 try to manage the ESX host, when I add the host first time I have this message, I continued to try 2 times it is the same but 3 times is connected but just after 10 seconds, he cut himself, I connect to new but even disconnect problem happens again.

  I'm using hostname set in the local host, firewall file network all allow the connetion, the windows firewall is turn off, any idea?

  vCenter Server 4.0 Build 208111

  vSphere Client 4.0 Build 208111

  ESX 4.1.0 260247

  Hello

  Welcome to the communities.

  The vCenter server must be upgraded to be able to manage ESX to vCenter 4.1 / i 4.1 hosts.

  http://PartnerWeb.VMware.com/comp_guide2/SIM/interop_matrix.php

• Need a powercli script to create a new account a local administrator on all ESX and ESXi hosts in the vcenter

  Hi all

  If someone can help me with a powercli script to create a new account a local administrator on all ESX and ESXi hosts in the vcenter, create a role called admin and give all access except the root. This shoulb be past by a virtual centre.

  Very much appreciated to help him.

  Kind regards

  MelLvin

  I suspect that you posted your question to the wrong thread

  This requires only a minor change to the script above actually.

  Something like that

  $groupName = "group"$accountName = "user"$accountPswd = "password"$accountDescription = "A user"
  
  $esxlist = Get-VMHostforeach($esx in $esxlist){    Connect-VIServer -Server $esx -User root -Password "password"
  
      Try {      Get-VMHostAccount -Id $groupName -Group -ErrorAction Stop | Out-Null    }    Catch {      New-VMHostAccount -Id $groupName -GroupAccount | Out-Null    }
  
      $rootFolder = Get-Folder -Name ha-folder-root    Try{        $account = Get-VMHostAccount -Id $accountName -ErrorAction Stop |        Set-VMHostAccount -Password $accountPswd -Description $accountDescription -AssignGroups $groupName    }    Catch{        $account = New-VMHostAccount -Id $accountName -Password $accountPswd -Description $accountDescription -UserAccount -GrantShellAccess -AssignGroups $groupName    }
  
      $rootFolder = Get-Folder -Name ha-folder-root    New-VIPermission -Entity $rootFolder -Principal $account -Role admin
  
      Disconnect-VIServer -Confirm:$false}
  

• Pics of member comments on all hosts on the new esx Server

  Peaks mem comments on all hosts on the new esx server, but the operating system does not use the amount of memory.

  The results are same vm running on the esx servers

  HP DL380 G6

  Dual Core CPU 8

  Xenon E5520 2.27 GHz Intel

  VCA mode Intel Xenon 45 nm Core2

  Guest mem 95% +.

  HP DL380 G5

  Dual Core CPU 8

  Intel Xenon X 5450 3.00 GHz

  VCA mode Intel Xenon 45 nm Core2

  Guest mem typically 25-35%

  The 3 peaks located on the new server.

  The new G6 in the memory market settles after a while if I put manually:

  Use Intel VT-x/AMD-v for virtualization and EPT Intel/AMD virtualization MMU nec training

  If I move G5 servers all right, move them back it culminates on mem. waited for itself if it settles, but no go.

  PS we put in CVS mode on the cluster.

  New servers booted on peak still G6 mem comments.

  Any thoughts?

  You have to refer to this before KB ?

  vcbMC - 1.0.6 Beta

  Lite vcbMC - 1.0.7

  http://www.no-x.org

• Disconnect the Vcenter/Cluster host and addition of new implications of Vcenter.

  All,

  We had to rebuild our vcenter on a separate box, because the database on the old one is completely messed up.  Successfully, we have disconnected hosts stand alone and added to the new Vcenter inventory without problem.  We wanted to know if there are problems with HA/DRS power off and disconnect a host of vcenter which is currently in a cluster.  Then add it to the new vcenter to manage.

  Thank you!

  No problem.

  Simple disable HA, tie your host for the new Victoria Cross, and then reactivate the cluster functions.

  André

• Remove the old host disconnected

  I have a problem with my erusem team disconnected on a server that no longer exist.   I'm not under the datamanagerment or host.  but we continue to get messages from the host disconnected.

  Where can I delete this host?

  If I goto under services-> I see this server name here, but there is no option to remove it.

  You want to return to the Administration-> tools-> Console of Script and paste this into a new script.  Replace the variable name of the host or the part of the army, and then run the script.  He should be back with a simple list of this host to be deleted.  If that is correct, you can then change the force = "" to forice = 'force' and which removes this object from the system.

• Disconnect the vCenter Server host machine

  I get error message after converting physical machine Desktop ESXi 5 using VMware Converter Standalone 5.0 utility whenever I deleted the host of the vCenter Server computer.

  This utility is installed on the desktop computer physics but prompt error on the screen "System Destination of"VMware Converter utility.

  Error.

  "The creation of host resource access is limited to the server"130.0.34.210"who manages the host. Use the destination administration server.

  You can help.

  Know not question, http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012310

  Use vCenter server as a destination and try

• 5.5 ESXi update 2 | Hosts disconnect and reconnect to randomly

  We have 3 HP DL380 x G9 5.5 u2 running ESXi servers.

  They have been in production for about 6-8 months until now without any problem whatsoever, until recently.

  Recently, Vcentre guests will enter a 'disconnected' State and the alarm 'host and connectivity power '. After a few minutes, the host will reconnect and everything continues as usual. This disconnection causes no VMs sign out or restart. During the period where Vcentre shows as disconnected host, we can still SSH and ping on the ESX host without problem.

  I checked through the VPXD logs and found that, at the time of the failure, in this case:

  2015-08-22T01:45:52.952+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:45:52.952+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:45:52.952+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.172, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:46:52.953+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:46:52.953+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:46:52.953+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.172, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:47:05.413+08:00 [09892 info 'commonvpxLro' opID=E83DF74C-00001BE1-18] [VpxLRO] -- BEGIN task-internal-35516 --  -- vmodl.query.PropertyCollector.cancelWaitForUpdates -- 4cb606ef-f3da-9ace-e253-d4c9e9b48bfe(529b4a61-85a4-90fe-ce8c-6361ed144841)
  2015-08-22T01:47:05.414+08:00 [09028 error 'SoapAdapter.HTTPService'] Failed to read request; stream: <io_obj p:0x000000000cc5fd08, h:4656, <TCP '[::1]:8085'>, <TCP '[::1]:56470'>>, error: class Vmacore::SystemException(An established connection was aborted by the software in your host machine)
  2015-08-22T01:47:05.414+08:00 [09892 info 'commonvpxLro' opID=E83DF74C-00001BE1-18] [VpxLRO] -- FINISH task-internal-35516 --  -- vmodl.query.PropertyCollector.cancelWaitForUpdates -- 
  2015-08-22T01:47:52.954+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.172, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:47:52.954+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:47:52.954+08:00 [09988 info 'vpxdvpxdVmomi' opID=SWI-1021c707] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vpxapi.VpxaService.fetchQuickStats)
  2015-08-22T01:48:07.047+08:00 [09916 info 'commonvpxLro' opID=24b2ad7b] [VpxLRO] -- BEGIN task-internal-35517 --  -- vim.LicenseAssignmentManager.queryAssignedLicenses -- ffe39310-e804-b7d6-92d8-61203ec022ce(52008866-be52-bc37-8007-48ec7a383c04)
  2015-08-22T01:48:07.047+08:00 [09916 info 'commonvpxLro' opID=24b2ad7b] [VpxLRO] -- FINISH task-internal-35517 --  -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 
  2015-08-22T01:48:25.450+08:00 [16416 error 'vpxdvpxdVmomi'] [VpxdClientAdapter] Got vmacore exception: Operation timed out
  2015-08-22T01:48:25.450+08:00 [16416 error 'vpxdvpxdVmomi'] [VpxdClientAdapter] Backtrace:
  --> backtrace[00] rip 000000018018b7fa 
  --> backtrace[01] rip 0000000180104c78 
  --> backtrace[02] rip 0000000180105f6e 
  --> backtrace[03] rip 000000018008ff08 
  --> backtrace[04] rip 00000001800418d6 
  --> backtrace[05] rip 00000001800445de 
  --> backtrace[06] rip 0000000180048382 
  --> backtrace[07] rip 00000000004f0ca9 
  --> backtrace[08] rip 00000000004f1399 
  --> backtrace[09] rip 00007ff7689280df 
  --> backtrace[10] rip 00007ff76892f418 
  --> backtrace[11] rip 00007ff768931b9a 
  --> backtrace[12] rip 00007ff768928257 
  --> backtrace[13] rip 00007ff768930d89 
  --> backtrace[14] rip 000000000046157e 
  --> backtrace[15] rip 000000000055a15a 
  --> backtrace[16] rip 00007ff7682b379d 
  --> backtrace[17] rip 00007ff7682b4406 
  --> backtrace[18] rip 0000000180152544 
  --> backtrace[19] rip 00000001801525d1 
  --> backtrace[20] rip 0000000180156eec 
  --> backtrace[21] rip 00000001801587ba 
  --> backtrace[22] rip 0000000180158cfc 
  --> backtrace[23] rip 0000000180158e98 
  --> backtrace[24] rip 0000000180153ab3 
  --> backtrace[25] rip 0000000180154b03 
  --> backtrace[26] rip 0000000180154e43 
  --> backtrace[27] rip 000000018019d62a 
  --> backtrace[28] rip 0000000067642fdf 
  --> backtrace[29] rip 0000000067643080 
  --> backtrace[30] rip 00007ffdbd7e13d2 
  --> backtrace[31] rip 00007ffdbfab5444 
  --> 
  2015-08-22T01:48:25.454+08:00 [21316 info 'vpxdvpxdVmomi' opID=HB-host-42@141303-7d8115aa] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vmodl.query.PropertyCollector.Filter.destroy)
  2015-08-22T01:48:25.454+08:00 [21316 warning 'VpxProfiler' opID=HB-host-42@141303-7d8115aa] [VpxdHostSync] GetChanges host:192.168.101.171 (192.168.101.171) [GetChangesTime] took 1800035 ms
  2015-08-22T01:48:25.454+08:00 [21316 warning 'VpxProfiler' opID=HB-host-42@141303-7d8115aa] [VpxdHostSync] DoHostSync:0000000009D0F6C0 [DoHostSyncTime] took 1800035 ms
  2015-08-22T01:48:25.454+08:00 [21316 warning 'vpxdvpxdInvtHostCnx' opID=HB-host-42@141303-7d8115aa] [VpxdInvtHostSyncHostLRO] DoHostSync failed for host host-42
  2015-08-22T01:48:25.454+08:00 [21316 warning 'vpxdvpxdInvtHostCnx' opID=HB-host-42@141303-7d8115aa] [VpxdInvtHostSyncHostLRO] Host sync failed to host-42
  2015-08-22T01:48:25.454+08:00 [21316 error 'vpxdvpxdInvtHostCnx' opID=HB-host-42@141303-7d8115aa] [VpxdInvtHostSyncHostLRO] FixNotRespondingHost failed for host host-42, marking host as notResponding
  2015-08-22T01:48:25.501+08:00 [21316 warning 'vpxdvpxdMoHost' opID=HB-host-42@141303-7d8115aa] [HostMo] host connection state changed to [NO_RESPONSE] for host-42
  2015-08-22T01:48:25.524+08:00 [21316 warning 'VpxProfiler' opID=HB-host-42@141303-7d8115aa] InvtHostSyncLRO::StartWork [HostSyncTime] took 1800105 ms
  2015-08-22T01:48:25.524+08:00 [21316 warning 'VpxProfiler' opID=HB-host-42@141303-7d8115aa] VpxLro::LroMain [TotalTime] took 1800105 ms
  2015-08-22T01:48:25.524+08:00 [21316 info 'commonvpxLro' opID=HB-host-42@141303-7d8115aa] [VpxLRO] -- FINISH task-internal-35432 -- host-42 -- VpxdInvtHostSyncHostLRO.Synchronize -- 
  2015-08-22T01:48:25.869+08:00 [09292 info 'vpxdvpxdHostUpgrader' opID=SWI-10381aa1] [VpxdHostUpgrader] Preinstalled bundle found: not installing
  2015-08-22T01:48:25.869+08:00 [09292 info 'vpxdvpxdInvtHostCnx' opID=SWI-10381aa1] [VpxdIntHost] Missed 180 heartbeats for host 192.168.101.171
  2015-08-22T01:48:25.869+08:00 [09832 info 'commonvpxLro' opID=HB-host-42@141316-52709f38] [VpxLRO] -- BEGIN task-internal-35518 -- host-42 -- VpxdInvtHostSyncHostLRO.Synchronize -- 
  2015-08-22T01:48:25.870+08:00 [09832 info 'vpxdvpxdInvtHostCnx' opID=HB-host-42@141316-52709f38] [VpxdHostSync] Synchronizing host: host-42 (192.168.101.171, 192.168.101.171)
  2015-08-22T01:48:25.899+08:00 [09832 info 'vpxdvpxdVmomi' opID=HB-host-42@141316-52709f38] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vpxapi.VpxaService.retrieveChanges)
  2015-08-22T01:48:25.901+08:00 [09832 info 'vpxdvpxdVmomi' opID=HB-host-42@141316-52709f38] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vmodl.query.PropertyCollector.createFilter)
  2015-08-22T01:48:25.902+08:00 [10564 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.171, vmodl.query.PropertyCollector.waitForUpdates)
  2015-08-22T01:48:26.402+08:00 [09876 info 'commonvpxLro' opID=task-internal-35519-3cef20c4] [VpxLRO] -- BEGIN task-internal-35519 --  -- ScheduledTaskLRO -- 
  2015-08-22T01:48:26.433+08:00 [17708 info 'commonvpxLro' opID=task-internal-35520-36662076] [VpxLRO] -- BEGIN task-internal-35520 --  -- ScheduledTaskLRO -- 
  2015-08-22T01:48:26.436+08:00 [17708 info 'commonvpxLro' opID=task-internal-35520-36662076] [VpxLRO] -- FINISH task-internal-35520 --  -- ScheduledTaskLRO -- 
  2015-08-22T01:48:31.420+08:00 [09876 info 'commonvpxLro' opID=task-internal-35519-3cef20c4] [VpxLRO] -- FINISH task-internal-35519 --  -- ScheduledTaskLRO -- 
  2015-08-22T01:48:32.009+08:00 [10092 info 'commonvpxLro' opID=HB-host-47@184250-7ea813a6] [VpxLRO] -- BEGIN task-internal-35521 -- host-47 -- VpxdInvtHostSyncHostLRO.Synchronize -- 
  2015-08-22T01:48:32.010+08:00 [10092 info 'vpxdvpxdInvtHostCnx' opID=HB-host-47@184250-7ea813a6] [VpxdHostSync] Synchronizing host: host-47 (192.168.101.173, 192.168.101.173)
  2015-08-22T01:48:32.014+08:00 [10092 info 'vpxdvpxdVmomi' opID=HB-host-47@184250-7ea813a6] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vpxapi.VpxaService.retrieveChanges)
  2015-08-22T01:48:32.016+08:00 [10092 info 'vpxdvpxdVmomi' opID=HB-host-47@184250-7ea813a6] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.createFilter)
  2015-08-22T01:48:32.040+08:00 [19544 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.waitForUpdates)
  2015-08-22T01:48:32.077+08:00 [19544 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.waitForUpdates)
  2015-08-22T01:48:32.080+08:00 [19544 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.waitForUpdates)
  2015-08-22T01:48:32.083+08:00 [10092 info 'vpxdvpxdVmomi' opID=HB-host-47@184250-7ea813a6] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.Filter.destroy)
  2015-08-22T01:48:32.085+08:00 [10092 info 'vpxdvpxdVmomi' opID=HB-host-47@184250-7ea813a6] [ClientAdapterBase::InvokeOnSoap] Invoke done (192.168.101.173, vmodl.query.PropertyCollector.cancelWaitForUpdates)
  2015-08-22T01:48:32.085+08:00 [10092 info 'vpxdvpxdInvtHostCnx' opID=HB-host-47@184250-7ea813a6] [VpxdHostSync] Retrieved host update to 184250 for host-47
  2015-08-22T01:48:32.086+08:00 [10092 info 'vpxdvpxdInvtHostDb' opID=HB-host-47@184250-7ea813a6] [VpxdInvtHost::SaveFieldsToDb] IPMI info of host 192.168.101.173 is not set
  2015-08-22T01:48:32.091+08:00 [10092 info 'vpxdvpxdInvtHostCnx' opID=HB-host-47@184250-7ea813a6] [VpxdHostSync] Completed host synchronization for host-47
  

  It doesn't seem to be a single host that is affected, it could be anything. It does not appear to occur at the same time during the day.

  I have checked for problems known and found some handshake SSL timeout KB articles, but do not believe that the same thing is happening here. I tried increasing the time-out period by that article anyway (KB 2064246) but that does not make a difference.

  All devices are connected to one HP5406ZL2 pass, with management on a vswitch with 2 x 10 GbE interfaces Active / active with route based on the origin of virtual Port ID set.

  The server running vCentre is also the MRS server and our server backup exec.

  Any information anyone can provide would be greatly appreciated.

  This weekend a just disappeared from the servers disconnected completely and don't come not back online.

  To fix that we followed the info in this article:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2037798

  This has now been run on all hosts and disconnects the random disappeared. I will seek to apply the updates that are mentioned in this article as soon as POSSIBLE.

  Cordially for someone else who stumbles across this.

• Hosts disconnect during VMotion

  Hi guys, faced with a difficult problem with a cluster and could use some comments: we had issues where one of the hosts (random) enters a disconnected state. If you let it rest enough long IT will return itself. Restart the vcenter services seems to accelerate the process too. Last night I went to put hosts in maintenance mode (to apply the latest patches) and all sorts of bad things that happened. Got to the point where 2 guests are cranked out. So bad a situation that one of the hosts could not return in the cluster, and we had to stop the machines and save them again on the hosts in the cluster. (Pleasure at 03:00). VMware has been a bit confused last night with what was going on so I have to re - engage the next week. Any help / ideas would be very appreciated.

  Here is the material / details.

  -Execution 5.5 Build 2302651 (ISO specific Dell)

  -3 x Dell PowerEdge R730 [boot from Flash] (firmware completely up to date)

  -1 x Dell Powervault MD3420 12 GB SAS (two controllers) (current firmware) connectivity

  -There is a Dell PowerEdge R730XD directly connected to the MD3420 running Windows 2012R2 / Veeam 8.0 Update 1 for backups

  -We are not sure if Veeam could be the cause for it. Trying to get involved them. At the moment we have completely disabled Veeam.

  -A putty session to one of the disconnected hosts who had locked up for a restart of management agent came back as if by magic when a veeam replication job has been cancelled (a replicate a computer since the backup repository so I have no idea why that would be important)

  -Currently have DRS automation and control applications disabled to mitigate risk

  -Start to move workloads to another cluster to reduce the risk

  Well, after a lot of torture, here is the solution:

  -Drivers that Dell will ship with 5.5U2 latest ESX media are not good. You must use the latest VMWARE drivers for DIS3 12 GB host bus adapters.

  -After the pilot on 2 hosts rotation, I tried vmotion and could not reproduce the problem.

  -For good measure we have updated the MD3420 to 8.20 firmware which was mainly new features

  -VMWARE update latest version

  After this experience, we will make some changes to our deployment strategy in order to eliminate a problem like this before the cluster into production if all goes well. We have made several tests of vmotion and storage vmotion before going to the first time, but us did not grow it is quite difficult. Automated DRS kicks and tried once to spend a lot of things at the same time, it is when we started to see these questions. If we had put a lot of pressure on the cluster and observed the vmkernel logs we have observed the error messages.

  Couple all of this to try to migrate to Veeam, it makes it difficult to isolate. Once Veeam was arrested and the problems continue that it makes it a lot easier to focus our efforts.

  I hope that someone else that this encounter with the LSI solution (HP, Dell, IBM) will benefit from this thread.

• Upgrading ESX when you are connected to the SAN

  Hello. At the time, it was considered preferable to unplug the host SAN during installation or upgrading ESX fram. Is this still the case with ESXi 5.5?

  Hello

  In fact, it is always best practice to disconnect from the SAN, but you could do it on the fly as well using the Manager to update if your upgrade to ESXi ESXI 5.1 to 5.5. I have seen many do

  without any problem. Just make sure that the hardware is compatible in HCL.

  Thank you
  Avinash

• Connection to host and the State of food in ESXi 5.0

  Hello everyone,

  I have a clsuter running in a center of V after that I have created anothere DR cluster in Vcenter even with three guests: VMware ESX 5.0 (three host)

  My problem is: after I add the hosts alarmed "connection server alarm and power status" every 5 Min in newly instlled three welcome only after three host are disconnected to

  I check DNS, IP/mask, gateway, cable, etc... nothing, Iam also capable of these server ping and able to NSlookup, but this error is not gowing. also confuigure HA cluster Again * three times)

  Thank you

  TechExpert

  Do you have firewall between vcenter and DR ESXi may to check you if the required firewall port is open between ESXi and VC/DNS servers, in order to avoid the frequent disconnection of esxi to VC.

  port to open between vc and esxi

  902, 5989, 80,443,623, 8000, 8001, 6500, 514,8080

  port to open between esxi and dns server

  53, 88, 389

  See below for more information:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1012382

• Host disconnected from Vcenter. cannot restart both agents

  Hello

  Following this thread: http://communities.VMware.com/message/1993369#1993369

  After 1:30 the host where the rescan HBAS was issued, became disconnected from Vcenter.

  I tried to restart the agent from the console, but he was hanged.

  I happened to have logged on esx, so I stopped the agents and restarted, but it hung for 1 / 2 h from "usbsarbitrator." I left.

  Looks like I need to restart the server, but I have the feeling that all the virtual machine running (OK for now) on this topic will be off and restarts automatically via DRS at best or not at all, if for some reason any DRS does not work (because of the issue of the host).

  To make matter worse, vcenter is running on this host at the moment.

  Is there a way to 'reconnect' vcenter to host this way can I vmotion all the VM on it before restarting the host?

  Thanks in advance

  Is you are using ESXi version connect the host using putty and run below command

  restart the /sbin/services.sh

• Host disconnected - what to do?

  I just had a host (ESX 3.5) that went into the disconnected state. We do not have all of the virtual machine on the host server. I had to reboot the host which means that all VM went down.

  I tried to check all services etc. to http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003409

  But nothing has worked.

  Anyone got something todo in such cases?

  VMotion failover is not very usable, and VMotion, failover etc to my boss was - well, hard to explain that it did not work.

  What server do you have? What cards you have and which networks are they connected to?

  Have you checked name resolution? in the field and the level of the host between the esx host and the virtualcenter?

  It is also useful to verify that the license server is accessible and functional.

• How to remove a host disconnected?

  I have a Cluster with 6 runing ESX 3.5 hosts and two of these hosts are disconnectd and no longer works (material has disappeared), and I want to remove these two my cluster, so I clicked on delete and I got an error:

  Unable to reach the specified host (host06.domain) this...

  So, I want to know how can I remove a host disconnected from my Virtual Center.

  you have a SQL DB?  If so, perhaps this will help you

  http://sosleepy.TV/2010/02/19/remove-an-VMware-ESX-4-host-from-vCenter-by-directly-deleting-the-host-from-the-SQL-database/

  The host in question no longer exists?  If so, you can also try the source edition licensing and remove your vCenter host.  Then restart your management agents

  service mgmt-vmware restart