I have a Fujitsu RX 300 S7 with ESXi 6.0 U3 and a Synology RS2416+ containing a RAID 10 with 4x 4 TB WD Red HDDs. I have created a file-based LUN on the Synology and I have connected the Target to the ESXi over 3 NICs via round-robin. This means, that all of the 3 NICs are used for the connection between the ESXi and the Synology (I have followed this tutorial).
I have made several tests with WMware IOMeter and CrystalDiskMark and the results are great (350 Mb/s and ~50k IOPS read), but during the tests, the ESXi hypervisor freezes. If I disable the Target on the Synology and enable it back again, the ESXi and the test VMs start working as if nothing had happened.
In the vmkernel.log I can find find several entries containing this line: “Waiting for timed out HB” (please find a screenshot attached)
Whan is the cause of the error? How can I fix the timeouts? I really need the higher throughput (=3 NICs) for better performance.
Thank you in advance!
I am still at learning level so this my sound stupid, but here it goes.
I have an HP server with 4 nics. the default vmnic0 is attached to vSwitch0 and everything works great. I created another virtual switch (switch2) and configured vmnic1 as upload link. Any VM attached to switch2 won’t connect to network. If i change the properties of the VM and connect to vSwitch0 everything work so the problem isn’t in the VM operating system. I changed the uplink link for vSwitch0 from vmnic0 to vmnic1 and everything work ok, so it’s not an hardware problem. I jumped to the conclusion that my created “switch2” is the problem but i can’t seem to pinpoint it; properties of the switches (vSwitch0 and switch2) are the same but maybe i am missing something. Any help is greatly appreciated.
Last week we had strange situation. Before 3 months we upgraded vcenter and cluster to 6.5 (using HP image). And it with some issues (with migration and PSOD later fixed with hot patch), it worked well.
But last week we upgraded first vcenter to 6.5 U1 and than two hosts in cluster, and everything was fine. After few minutes hosts started to crash PSOD, but I’m talking about hosts what were not upgraded, upgraded worked well.
After that we found that upgraded have new ILO drivers 650.10.1.x and old have 650.10.0.x, after that vmware confirmed problem with ILO.
Here I want to determinate what was the trigger of crash, as I said before vsphere 6.5 with old friver worked well for 3 months, and after upgrade part of infrastructure to 6.5U1 it started to crash?
Does anyone have exploitation of situation?
One of the most effective methods you can use to protect kids online is to talk to them. The younger you start talking to them, and they to you, the better. Hold regular conversations about online safety issues, even going so far as to show them actual negative events that have taken place. If you don’t know what your kids are doing, simply ask. Play the clueless parent and ask them to show you what the latest technologies are and how they use them. Quite often, kids love the idea of being the teacher and will open up.
We are using VmWare Vsphere Version 6.5.0 (Build 4887370). Every Sunday our host server is mysteriously shutting down. We get a message from our USV that the host is shut down, however it is the only message we get, so we have looked into the preferences of the USV and of the Vcenter. As usual we have not found anything. Do you have any idea or could you help us? If you need more information feel free to ask.