Hello,
I have one ESXi 6.0U3 (5050593) and my vCenter is 6.0U3h (9313458)
If I connect my ESXi to my vCenter using the IP everything it´s ok... But if I connect my ESXi to my vCenter using the hostname (not FQDN) apparently connects but after more or less 60 second disconnects from the vCenter.
What´s the issue?
Thanks
Hello,
Have you Firewall beetwen your vCenter and your DNS server ?
Your DNS server are correct in vCenter ?
Do you have vRLI or something monitoring your logging? What does the vCenter & Host logs look like in the time range when it disconnects? Have you tried moving the Host to another Network port or even another Switch? There could be Network collisions or dropped packets or something causing it to drop.
... using the hostname (not FQDN) ...
I've never done it this way myself. I either used the IP address, or the FQDN.
Anyway, it looks like the vCenter Server cannot resolve the host's name (or vice versa). What I could think of, is is either a non-working name resolution, caused by e.g. an incorrect DNS server entry, or a missing search domain.
André
How could a firewall affect this? What firewall?
What VMFS version are you running? If you are running VMFS 6, it will unmap automatically asynchronously during low IO periods and you can specify a maximum unmap throughput in MB/s as well. That way it is taken care of automatically minimizing impact to the array.
If you are VMFS 5, I would recommend upgrading to VMFS 6 to take advantage of the feature above. There is a great article on how to do this somewhat automatically using the Update-Vmfsdatastore powercli cmdlet.
If none of that is possible, I would consult the storage vendor on maximum recommended unmap rate in order to avoid performance degradation and do one datastore at a time to avoid impact.
Hi,
I am aware Intel NUC isn't supported by VMware as a hardware to run on, but it does appear to be used a lot on home labs. I've come across an issue that appears to relate to e1000 network driver (according to Intel), and it involves the inability to wake the NUC machine via WOL (Wake-on-LAN) packet after it has been shutdown (via ESXi console or GUI). It works fine if you wake the machine up just after you switch the power on at the socket. But the minute you use a manual shutdown in ESXi, it will no longer wake up via WOL packet.
It has been raised here with Intel NUC:
https://forums.intel.com/s/question/0D70P000006GX2K/cannot-wol-with-intel-nuc8i7bek-after-shutting-down-esxi-67u1?langua…
But the conclusion by Intel is that it is caused by NE1000 driver VIB used in VMWare.
Anyone else have this issue, or have any ideas how I could potentially solve this?
IP Segments are:
primary vcsa: 188.40.xx.xx
secondary vcsa: 46.225.xx.xx
esxi host: 185.81.xx.xx
-------------------------------------------
version and build numbers:
primary vcsa: 6.00 build 5112529
secondary vcsa: 6.00 but not sure about exact build number, it is something lower than primary vcsa (255xxxxx)
esxi host: 6.00 build 3620759
by the way we also tried to update vcsa and esxi host to other build numbers but nothing changed.
-------------------------------------------------
in this currect state I can directly access to esxi host with vsphere client software without any problem.
---------------------------------------------------
I also attached the last lines of those logs that you wanted. vpxd and hostd
and there is another maybe usefull screenshot of an error when I try ro reconnect the host in primary vcsa
Has anyone had any success figuring out how to get ESXi to run on a ZBook 15 G5? Installation succeeded after setting ignoreHeadless=TRUE, but ESXI startup stops with:
Shutting down firmware services...
Using 'simple offset' UEFI RTS mapping policy
Relocating modules and starting up the kernel...
I did set the ignoreHeadless=TRUE as a boot option for ESXi.
I would suggest opening a SR with VMware and possibly Pure. I mention Pure because they have high quality support with back channels to VMware if need be.
seems like communication problem -- dns server to vcenter and esxi host. best option is add the esxi host in local host file C:\Windows\System32\drivers\etc\host file or appliance vi /etc/hosts.
I will check your recommendation.
Thanks!!!
Is VMware supporting the HPE Dual microSD flash USB stick?
This is a software RAID controller variant, and VMware does not support Software Raid. is that so?
I would like to know if I can install Esxi on it?
Hi 43A8V,
Yes - VMware is supported on HPE Dual-microSD USB device. We stopped using these due to the latency spikes that kept getting generated every minute or so
Its interesting that HPE list this device as mirrored RAID-1 because it doesn't seem to behave like a traditional RAID device, i.e. having a primary device, etc. These documents talks about installing HPE as long as the server supports ESXi:
Kind regards.
From the screenshot and log message in vpxd.log, this is clear that the host cannot send the heartbeat to VC, this could be due to the network as host and VC are in different segments . There could be high latency at the network end which is causing the issue
2019-04-11T07:14:07.458+04:30 error vpxd[7F48EE448700] [Originator@6876 sub=Default] Reading additional bytes from the stream timed out : Read timeout after approximately 305000ms. Closing stream <SSL(<io_obj p:0x00007f4 8cc4b4700, h:171, <TCP '188.40.xx.xx:53482'>, <TCP '185.81.xx.xxx:443'>>)>
2019-04-11T08:03:55.918+04:30 error vpxd[7F490D08E700] [Originator@6876 sub=MoHost opID=0AA8F7F3-000079DA-fc][HostMo::Reconnect] Got unexpected exception: Server closed connection after 0 response bytes read; <SSL(<io_obj p:0x00007f48d876edf0, h:97, <TCP '188.40.xx.xx:34320'>, <TCP '185.81.xx.xxx:443'>>)> while reconnecting to host 185.81.xx.xxx--> reason = "Server closed connection after 0 response bytes read; <SSL(<io_obj p:0x00007f48d876edf0, h:97, <TCP '188.40.xx.xx:34320'>, <TCP '185.81.xx.xxx:443'>>)>",
Any specific reason why you your vCenter and hosts are in different network segments ? Try to bring ESXi and VC on same network if possible. Following article gives some hint on this issue and resolution steps
Hi,
I would avoid running unmap on all 100 LUNs simultaneously since there would be a performance impact on VMs. Also, you will require 100 hosts to run unmap on 100 LUNs simultaneously since you have to wait till unmap finishes on 1 LUN before proceeding with next LUN.
I would recommend scripting this. Run 2-3 instances of same script with different names and different parameters (different ESXi hosts and LUN names/IDs) so the unmap would be running on 2-3 LUNs simultaneously without impacting your Production. Also, do this in 2-3 phases. Make sure you are running these in Off Business hours or at time when the IOs on the LUNs are minimal to ensure optimal performance.
Refer to below links for scripts:. However, please try them at your own risk and test them thoroughly before using in your infrastructure.
Perform VMFS UNMAP using PowerCLI
compwizpro has provided valid points. In addition to them, you need to confirm with your storage team if automatic claiming is supported/enabled on the current version of storage product. Since I have faced this issue where ESXi is trying to auto reclaim space in VMFS 6 but the current storage product version does not support it.
Hello,
I have 2 ESXi hosts (6.5 10719125) that are hosted on HP ProLiant BL 460c Gen9. And I have for both of them this configuration issues message: "Host profile apply failed with error: Unexpected error updating task config spec: Unknown..". There is no host profile attached. I checked logs and founded nothing pointing to this issue . Any idea? Thank you
Unfortunately I do not have an answer, however I face the same issue on HPZ2TowerG4 Workstation.
Please let me know if you find something. :-)
How do I configure esxi 6.7 to send HTTP "Strict-Transport-Security" header? I'm looking online and in the KB but I seem to be finding more definitions than configuration solutions. One thing I'm using ESXI 6.7 the free version so where do i go to get nut and bolts info
TNX
Hi Everyone,
We have just noticed that our datastore is missing and we cannot see it under the ESXi webpage.
Not sure when did this happen, but maybe after we have updated the Esxi to 6.7.
The VMs are running fine.
We can see the Adapter under Storage -> Adapters.
We can see the hard drive under Storage -> Devices.
But the Datastore is empty and we cannot change any settings of the VMs as it throws an error
When I try to browse: "There are no browsable datastores. Currently, only vSAN and local VMFS datastores can be browsed."
I have tried to figure it out and run a few commands under SSH, but I cannot see what could be the issue or how to fix it.
Could you please let me know how to get back the datastore?
esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
----------- ----------------------------------- ------------- ------------------------------------ ---------
datastore1 5c8a7789-1a4c3a5c-0a47-b083fec42bdd 0 naa.6b083fe0cfb8ba002400ee74143fdef7 3
esxcfg-mpath -l
sas.5b083fe0cfb8ba00-sas.6000ee74143fdef7-naa.6b083fe0cfb8ba002400ee74143fdef7
Runtime Name: vmhba0:C2:T0:L0
Device: naa.6b083fe0cfb8ba002400ee74143fdef7
Device Display Name: Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)
Adapter: vmhba0 Channel: 2 Target: 0 LUN: 0
Adapter Identifier: sas.5b083fe0cfb8ba00
Target Identifier: sas.6000ee74143fdef7
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 5b083fe0cfb8ba00
Target Transport Details: 6000ee74143fdef7
esxcfg-scsidevs -c
Device UID Device Type Console Device Size Multipath PluginDisplay Name
naa.6b083fe0cfb8ba002400ee74143fdef7 Direct-Access /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7 3814400MB NMP Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)
esxcli storage vmfs snapshot list
This returns nothing...
esxcli system coredump partition list
Name Path Active Configured
-------------------------------------- ---------------------------------------------------------- ------ ----------
naa.6b083fe0cfb8ba002400ee74143fdef7:7 /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:7 false false
naa.6b083fe0cfb8ba002400ee74143fdef7:9 /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:9 true true
partedUtil getptbl /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7
gpt
486267 255 63 7811891200
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
3 15472640 7811891166 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
If I run a rescan on the device the kernel log shows this:
2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)World: 11943: VC opID 24fae6e5 maps to vmkernel opID b3571b7d
2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)NVDManagement: 1461: No nvdimms found on the system
2019-04-11T16:47:25.437Z cpu2:2097756)ScsiDeviceIO: 3068: Cmd(0x459a41156c40) 0x1a, CmdSN 0x11be from world 0 to dev "naa.6b083fe0cfb8ba002400ee74143fdef7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)World: 11943: VC opID 24fae6ee maps to vmkernel opID bf5b1e18
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4616: Device rescan time 16 msec (total number of devices 5)
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4619: Filesystem probe time 30 msec (devices probed 3 of 5)
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4621: Refresh open volume time 1 msec