ESXi 3.5 - inadvertently disconnected SAS connector

Similar Questions

• 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.

• ESXi 5.0 U3 disconnects randomly vCenter

  Hello

  I have 'ESXi 5.0 U3 HP custom"installed on the servers of HP DL580 G7.

  my version of vCenter is 5.0 U1

  Every 2 or 3 days, around 12:00 to 01:00 AM (midnight), one of the hosts, disconnects (almost randomly) vcenter, the ping of the host is available, virtual machines are ok, and after about 10 minutes, it gets automatically connected again.

  In fact, I have not checked if I could connect directly to the host through the VI Client or not?

  There is no special event in vCenter events at the moment where the host disconnects.

  Any body help on this issue?

  P.S
  It seems that this happens after the upgrade to ESXi ESXi U3 U1 5.0 5.0... but I'm not sure that I will also install version 5.0 U3 vCenter. but I don't know if this will solve the problem, as U1 is also in the matrix of interoperability with ESXi 5.0 U3.

  Hello

  The problem was related to violation of CPU by VMs in a host.

  It seems the CPU limit has solved my problem.

• ESXi 5.5U2 host disconnects a few seconds added to vCenter

  Hi all, as a subject, really. I have been troubleshooting a problem where, when adding a remote host to vCenter, who host their product to unplug a few seconds.

  At first I thought it was my firewall rules, but I've sorted which and I don't no ACL denies more on them.

  I can connect to the host very well using the vSphere Windows-based client, so I do not understand it.

  Should what kind of information I add to this post to help the guy to help me?

  P.S., relatively new to VMware.

  Thank you, Mark

  Thanks for the advice... He led me to the correction, which was that VMware KB: NAT between the vCenter Server system and ESXi/ESX host using

  My vCenter was behind a NAT firewall that was causing the problem.

  Hope this helps others.

• ESXi host running 6 VCSA disconnected from the vCenter

  Hi guys,.

  I have a weird problem with my vCenter build 6. Single cluster of ESXi hosts. Running VCSA 6.0 and 6.0 ESXI. Making a storage of the vCenter vMotion initially got stuck at 77% and the ESXi host running the disconnected from vCenter vCenter. But I can connect directly to the ESXi host with vsphere client and see the vCenter VM works perfectly well. If I try to manually connect host ESXi and vCenter, I get the error "Failed to contact the host specified") both are in the same subnet and VLAN. I can migrate to other virtual machines without problem. I even restarted the host and yet I am not able to connect to vCenter. The host connects to vCenter if I reboot vCenter, but after a few minutes, disconnects again (even if no task does run on this topic.) I have no HA or DRS enabled at this point that I build this new environment and only presented a single LUN as a store of test data to the cluster.

  Any ideas?

  OK, I think I fixed that or have at least a work around. So the underlying question was hiding ID mode/CPU EVC. I'm under the cluster to a level of EVC to reduce until I have migrate workloads from old environment and I think that this created a problem for the unit vCenter. To resolve this problem, I turned off the unit, directly connected to the ESXi host that had the camera running, edited the virtual machine and reset the masking of CPUID. Also, I've hidden the flag NX/XD of the guest. It's temporary (I hope) as once I increase the EVC to the Haswell, I will expose the NX/XD comments and test. For the moment, it is of the workaround I did. It may be of some use to someone.

• ESXi 3.5 on Dell Poweredge 2950 and Dell 6 GB/s card SAS HBA?

  Hello.

  I'm under ESXi 3.5 u4 on a Dell poweredge 2950 machine.

  I recently bought a Dell Powervault 124 t. autoloader with a HBA SAS 6 GB/s card.

  I installed the card SAS in the PE 2950, but now I can't seem to see in ESXi.

  Can someone help me with this?

  Thank you very much.

  I'm afraid that the Dell technician is correct.

  Someone at - it a link on ESX support not directly connected devices?

  This isn't the issue. The question is: do you have a link that shows devices supported?

  Reference Dell does support the autoloader Powervault 124 t. on ESXi 3.5?

  Have you checked the VMware HCL already, if the SAS controller is included/supported for ESXi version, you are running?

  There are a few articles which have tape readers running with Adaptec SCSI controllers, I don't see anything for ESXi 3.5 with a SAS controller still...

  Maybe there's a better chance to make this work with ESX 4.x with VMDirectPath

  André

• Cannot add host ESXi 5.5 to vCenter for a routed network - cannot communicate with the specified host

  I was wondering if anyone has come across this problem before, who could give advice how to fix them:

  Host of pre-production UCS ESXi migration of a Production vCenter on another network (routing in place)

  Can ping both directions successfully - from vCenter Prod to the host of the pre-production

  no firewall between the two.

  902 port is open on the host

  Host connects to the pre-production vCenter on the subnet even fine

  VCenter production can add different hosts on the same network end

  Even with the various guests of ESXi UCS.

  ESXi host was completely disconnected and removed from vCenter inherited before attempting to add. No dvswitch physical or virtual.

  Then try and add, enter the user name and password and get cannot communicate with the specified host.

  Thank you

  The solution to this. Used ESX host 5.5 3B (3248547) update that disables SSLv3. (Ref: VMware ESXi 5.5 updated Notes version 3B) one of the consequences of this is that older versions of vCenter (such as trying to move the host) can not add/connect host.

  Enable SSLv3 to spend (port 443) on the resolved host (virtuallyPeculiar: connection A ESXi 5.5 U3b host to vCenter with a lower Version A.)

  Note: should not enable SSLv3 to Port 902.

  Ref:

  The SSLv3 Protocol on vSphere 5.x configuration (2139396) | VMware KB

  Many thanks to Suhas Savkoor of virtuallyPeculiar for resolution for this on his website display

• Change the name of the logfile refelect esxi host name

  Hello

  I'm changing the name of the log file to reflect the name of each host name in listed in a file text How would I have done that?

  Thank you

  CODE

  --------

  ##Load VimAutomation PSSnapin...
  If ((Get - PSSnapin - name VMware.VimAutomation.Core - ErrorAction SilentlyContinue) - eq $null)
  {Add-PSsnapin VMware.VimAutomation.Core - ErrorAction SilentlyContinue}
  
  ##Set server Mode...
  SetPowerCLIConfiguration - Multiple DefaultVIServerMode - confirm: $false

  #Get # hosts.txt file ESXi host list...
  $varHost = get-Content "S:\Get-Logs\hosts.txt".

  The cluster name #Enter...
  $Cluster = Read-Host "enter the cluster name.

  
  ##Path to clear the logs...
  $FilePath = "S:\Get-Logs\Logs\" + $Cluster + "\".

  Cluster ##Create folder...
  If ((New-Item - path $FilePath ItemType - directory - ErrorAction SilentlyContinue) - eq $null)
  {- New - path $FilePath ItemType - directory - ErrorAction SilentlyContinue}

  
  Password ##Root
  #Convert to ensure the chain...
  $varGetPassword = Read-Host "enter the ESX Root Password" - AsSecureString
  $ESXRootPassword = [Runtime.InteropServices.Marshal]: PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($varGetPassword)))
  
  ESXi hosts ##Connect
  Write-Host "" connection to the ESXi host: ', $varHost ' "»
  SE connect-VIserver $varHost - user 'root' - password $ESXRootPassword - WarningAction SilentlyContinue
  
  ##Do something useful here...
  ##------------------------------------------------------------------------------
  {foreach ($ESX to $varHost)
  
  Get - Log - VMHost (Get-VMHost-name $ESX) - Bundle - DestinationPath $FilePath
  }
  ##------------------------------------------------------------------------------

  
  
  ##Disconnect Esxi host
  Write-Host "" disconnect from ESXi host: ', $varHost ' "»
  Disconnect-VIServer $varHost - confirm: $false
  
  The script ##End

  End CODE

  ---------------

  The cmdlet Get - Log do not create the destination folder if it does not exist, so you will need to test for this condition.

  AFAIK, you don't need to connect to each ESXi individually when you are connected to the vCenter.

  Since the discharge of generated log file name is rather cryptic, I rename the file normally and add a timestamp.

  You could do something like that

  $clusterName = "mycluster.

  $FilePath = 'S:\Get-Logs\Logs\$($clusterName) ".

  If (!) ((Test-Path-path $FilePath)))

  {

  Novelty - ItemType Directory - Path $FilePath

  }

  $varHost = get-Cluster-name $cluserName | Get-VMHost

  {foreach ($ESX to $varHost)

  $destPath = "$($FilePath)-$($ESX.). Name.Split('.') [0])"

  If (!) ((Test-Path-path $destPath)))

  {

  Novelty - ItemType Directory - Path $destPath

  }

  $logName = get - Log - VMHost $ESX - Bundle - DestinationPath $destPath

  If ($LogName)

  {

  Rename-Item - Path $logName - NewName "$($destPath)-$($ESX.). Name.Split('.') [0])-$((Get-Date).) ToString('yyyy-MM-dd-hh-mm')).

  }

  }

• disconnect hosts to vCenter Server 5.1.0 Build 947673 and appear as does not not after 45 seconds (always)

  I have a very strange installation, it has been stable for 6 months, I don't know if it's conciendence after the implementation of POS, but now after 45 seconds, the hosts to build 799733 ESXi 5.1.0 disconnect from vCenter Server 5.1.0 build 947673 and appear as does not.

  I can right-click on each host and deliver a Connect and servers are re-connected and then after 45 seconds, appear as the not responding again.

  The vCenter is a virtual machine, on the cluster of two hosts, use VMXNET3 interface, fully patched.

  Since the vCenter server at the time of her disconnects or does not, I do not see timeouts ping to vCenter VM guests hosts, I can also connect directly to the ESXi servers with vSphere Client and there, no problem, I still connected.

  DNS is correct, default gateway is correct, used data base is installed by default with vCenter (simple installation), SQL Express, database is not full or has reached its limit.

  nothing to the Windows event log.

  things tried

  1 rebooted ESXi hosts

  2. restart network management officers

  3 upgrade vCenter Server to build build 947673

  4 restarted vCenter Server

  5. stop all virtual machines, except vCenter Server including POS.

  is already done guest!

  the newspaper of vpxd I can see the following:- so I can see I think that disconnection, but no idea why!

  2013 01-17 T 13: 08:37.741Z [06164 'vpxdvpxdVmomi' opID = SWI-6e140ec8 info] [ClientAdapterBase::InvokeOnSoap] Invoke fact (esx003.domain.ac.uk, vpxapi. VpxaService.fetchQuickStats)
  2013 01-17 T 13: 08:37.741Z [06164 'vpxdvpxdVmomi' opID = SWI-6e140ec8 info] [ClientAdapterBase::InvokeOnSoap] Invoke fact (esx004.domain.ac.uk, vpxapi. VpxaService.fetchQuickStats)
  2013 01-17 T 13: 08:39.659Z [06292 'vpxdvpxdHostCnx' opID = SWI-7a1cb616 info] [VpxdHostCnx] no heartbeat from host 5203136b-c37d-c238-69c3-7101151dae9b in 4398798518000 ms
  2013 01-17 T 13: 08:39.659Z [06292 'vpxdvpxdHostCnx' opID = SWI-7a1cb616 info] [VpxdHostCnx] no heartbeat from host 5274675a-2fb6-a9ae-7787-9f24c69ff6e5 in 4398798518000 ms
  2013 01-17 T 13: 08:39.659Z [info 06620 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost] Got lost connection to the host-28 reminder
  2013 01-17 T 13: 08:39.659Z [info 04264 'commonvpxLro'] [VpxLRO] - tache-interne-212--hote-28--vpxdinvthostsynchostlro.synchronize--BEGIN
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-28
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost::FixNotRespondingHost] returning false because the host is already fixed!
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] was not able to repair unresponsive host host-28
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-28
  2013 01-17 T 13: [04264 error "vpxdvpxdInvtHostCnx"] 08:39.659Z FixNotRespondingHost [VpxdInvtHostSyncHostLRO] has failed for the host-28, marking host as notResponding
  2013 01-17 T 13: 08:39.659Z [info 06620 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost] Got lost login reminder 24 / host
  2013 01-17 T 13: 08:39.659Z [info 06620 'commonvpxLro'] [VpxLRO] - tache-interne-213--hote-24--vpxdinvthostsynchostlro.synchronize--BEGIN
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-24
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost::FixNotRespondingHost] returning false because the host is already fixed!
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] was not able to repair unresponsive host host-24
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-24
  2013 01-17 T 13: [06620 error "vpxdvpxdInvtHostCnx"] 08:39.659Z FixNotRespondingHost [VpxdInvtHostSyncHostLRO] failed for the host-24, marking host as notResponding
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdMoHost'] [HostMo] host connection state changed to [NO_RESPONSE] for the host-28
  2013 01-17 T 13: 08:39.784Z [info 04264 'vpxdvpxdMoHost'] [HostMo::SetComputeCompatibilityDirty] 28 marked as dirty host.
  2013 01-17 T 13: 08:39.784Z [info 04264 'clustervpxdMoCluster'] [ClusterMo::SetDasCompatDirty] marked area-c37 as dirty.
  2013 01-17 T 13: 08:39.800Z [info 04264 'commonvpxLro'] [VpxLRO] - speciale-interne-212--hote-28--vpxdinvthostsynchostlro.synchronize--FINISH
  2013 01-17 T 13: 08:39.831Z [06620 WARNING 'vpxdvpxdMoHost'] [HostMo] host connection state changed to [NO_RESPONSE] 24 / host
  2013 01-17 T 13: 08:39.987Z [info 06620 'vpxdvpxdMoHost'] [HostMo::SetComputeCompatibilityDirty] 24 host marked as dirty.
  2013 01-17 T 13: 08:39.987Z [info 06620 'clustervpxdMoCluster'] [ClusterMo::SetDasCompatDirty] marked area-c37 as dirty.
  2013 01-17 T 13: 08:40.003Z [info 06620 'commonvpxLro'] [VpxLRO] - speciale-interne-213--hote-24--vpxdinvthostsynchostlro.synchronize--FINISH

  any ideas?

  Hello

  Looks like a level of port problem. Can you please make KB:http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2031843 is followed correctly.

• Network down ESXi management.

  Hi all

  Well, my problem is because of my attitude adventerous ... After the discussion with one of my friends I have installed a switch distributed and selected link rising adapter an ESXi vmnic0, it served the vswitch more vmk0 group of ports deal with traffic management, to my surprise, the operation succeeded! (I thought it would give me an error similar to what we get in ESX cannot remove the last adapter to uplink of the vSwitch having the service console). This eliminated my ESXi off the grid. I can't ping and all I have is the mode of tech support. Here, I can't use vicfg because they are not available in ESXi

  Is it possible that I can change the settings and connect vmnic0 return to vSwitch0? Would be great as well if I can be explained why ESXi allows same to disconnect the last map uplink connected to the vswitch (containing vmk0), which is very destructive and not allowed in ESX?

  Thanks a lot for your answer in advance.

  MAK

  You can fix with the esxcfg-vswitch command command line:

  http://www.jume.nl/esx4man/man8/esxcfg-vswitch.8.html

  But you need access to the console.

  André

• Is it possible to add the ESXi 4.1 host to vCenter 4.0

  Hello

  When I try to add ESXi 4.1 hot to vCenter 4.0, after a few seconds, esxi 4.1 is disconnecting to form vCenter 4.0.

  I have two blades, one blade server has ESXi 4.0 and another has ESXi 4.1. Can I manage the two hosts to vCenter 4.0.

  Note: I can not upgrade my ESXi 4.0 to 4.1, I need to test my product on both versions.

  Thanks in advance.

  Concerning

  Deva

  You must have a vCenter license registered on your account in order to download it.

  Concerning

• Help Setup RAID SATA for ESXi 4.1

  Hello

  It is the first time that you try to use vmware.  Any help is greatly appreciate!

  I just built a server around the Intel s5500hcvr mother. I have 6 SATA HDD I want to set up in a RAID. The integrated RAID controller seems to be very limited and does not seem to be supported by ESXi 4.1 (when I run ESXi 4.1 installation and it asks for a location for installation, all my discs are individually listed instead of virtual drives that I created with the RAID controller)

  My questions:

  (1) what is the suggested configuration of HDD (RAID levels / number of berries) for ESXi 4.1?  Can I create 1 RAID 10 array and set everything up to that?  or take one of my disks and install esxi 4.1 on it and then create a RAID with the rest of my discs and use it to store data?

  (2) anyone can provide links to some SATA RAID controllers that are known to work with ESXi 4.1 (and is the supposed to recognize virtual readers created by the RAID controller setup ESXi 4.1)

  Your motherboard has a RAID controller software which, as you have discovered, is completely not taken in charge by ESX/ESXi... You will need to get a RAID controller that is on the HCL for SAS and SATA hard drives (not one with battery backup write cache) so you can use any type of RAID configuration.

  My preference for Internal RAID configurations (on the host) are two drives mirrored for ESX/ESXi to reside (preferably being SAS 10 k or 15 k RPM, 73 GB or 146 GB in size) and then another table for the data store. You'll want to keep the data slot store table 2 TB-512 b size in order to present to ESX/ESXi as a LUN. Or you will need to get a RAID card this split of the support to the top of the table in the smaller of the virtual drives that can be presented for ESX/ESXi and LUNS.

  Search for controllers using the LSI MegaRAID chip as a good first lap. Some Adaptec cards should work, but I've seen people post questions on those recent (more recent than in the past). MANY manufacturers rebrand/efficiency the LSI MegaRAID Controllers server, such as the Dell PERC 6 series cards.

  For the use of 4 disks SATA, RAID 10 (on a BBWC, fully supported, controller) will give you the best performance. It will compare with SAS drives however. IF you do not plan on any virtual machine running with anything beyond light IOPS / s then you should be ok (or with very light loads)... If this is going to be a production server, then get the SAS drives all around.

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• ESXi 4.1 HA set up error!

  I have 2 hosts esxi 4.1, when configure the AP, the error apears below:

  HA agent on xx.xx.xx.xx clustered xx xx has an error:

  AddNode cmd failed for the primary node: error of creation of the virtual disk for the configuration of the HA agent: unknown error of HA

  but the other 2 4.1 esx host is allowed in this cluster

  Sever the host to vcenter-

  SSH to the server and run: (technical support mode)

  service mgmt-vmware stop

  stopping service vmware-aam

  stopping vmware-vpxa service

  Join the host back to vCenter - it must be reinstalled agents.  I had this problem today and it fixed.  If it becomes more difficult there are alternatives.

  Stop the services see:

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

  Worst case scenario:

  Right-click on the ESXi host and click Disconnect.  This disconnects the VirtualCenter inventory ESXi host.

  Connect to ESXi troubleshooting Mode.  For more information, see Mode of Support emergency support Tech (1003677).

  Uninstall components vpxa and Mao from the VMware ESXi host using the following commands:

  /opt/VMware/uninstallers/VMware-vpxa-uninstall.sh

  /opt/VMware/uninstallers/VMware-AAM-HA-uninstall.sh

  Right-click on the ESXi host and click on connect. This triggers a re-vpxa agent installation.

  Add the host to the appropriate cluster. This triggers a re-installation of the agent of the Mao.

  Join the cluster.

  See you soon,.

  Chad King

  VCP-410. Server +.

  Twitter: http://twitter.com/cwjking

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Airport extreme will reconnect not extended wireless network

  The power to my Airport Express (2nd version; 802.11n) has been inadvertently disconnected and it does not now restore for extended wireless network.  I have an Airport Extreme (802.11ac) that hosts the network.  I have soft, hard, and factory resets to the Express.  Airport utility says that an "unexpected error occurred, try again."  I have, over and over again.  Airport utility finds the Express after a reset.  After initial connect failure, I brought the two devices in the same room.  Should I reset the extreme as well and start over?  V10.11.3 OS X, v. 6.3.6 Airport utility.  Thanks for your help.

  At this point, I would say that you make the Express in the same room as the extreme. Go ahead and perform a reset on the only default Express. Wait for it to finish.

  You should now be able to 'see' the Express in the list menu drop-down airport the two OS X menu bar and on your Mac AirPort Utility. In the menu bar is should appear as something like Apple network NNNNNN. It should appear as a Terminal AirPort Express, AirPort Utility.

  If you get the message "unexpected error", check the following on your Mac:

  • Make sure that IPv6 is configured for: link-local only. You can find this setting in system preferences > network > advanced > Ethernet or Wi - Fi (according to your Mac is connected to the network) > configure IPv6
  • If your Mac is connected to the extreme by Ethernet, activate the Wi - Fi connector in system preferences > network

• Dell external DAS doesn't format disk space

  I have a PE of 1950 with a Perc6 double 73 GB drives running. Then I have a dual card Perc5 w / external SAS connector. its connection to a 15 multi-plate 1 TB sas. I have install the array with raid 0 to 15TB, I bootup VSphere and analyze the bus and he finds the table to 15. When I goto add storage, it shows the LUN and the 15 TB of space, but when I get to the box format, it shows that there are only 932 GB available. If I format in any case one of my records in the table disconnects!

  I went back and created a new RAID5 volume this time, initialized, entered the Vsphere and I see 13 available to, which is the same as that reported by the RAID configuration. I goto format it and again, 932GB available, I format and another player goes into offline mode in the table.

  Basically, it seems that vsphere ignores the virtual disk created by the raid card. I have seen this in boxes from the bottom white with sata controllers when he ignores the raid configuration, but it is a complete dell configuration and everything should not have a problem.

  My only guess is that something with having 2 controllers perc could be the problem... anyone else think what anyone would be appreciated.

  ESX (i) currently has a limit of 2 TB LUN (specifically it's 2 TB - 512b).   If the controller is supported, you can create several bays on the disks.  Once you present for ESX (i) you can join them with extensions.  You will always be limited to 2 TB VMDK files (assuming that you choose a block size of 8 MB when formatting the data store).   What you plan to do with storage?

  Dave

  VMware communities user moderator

  New book in town - Start Guide quick vSphere -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

  You have a system or a PCI with VMDirectPath?  Submit your specifications to the unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.