Generally speaking, it's not a great idea because it extends the blast radius of datastore failures and it makes it more difficult to troubleshoot performance problems should they arise.
Not enough information to go on without seeing the vmkernel logs might have to say as well as iDRAC info/logs. Could be the drives are just dying, especially if they are older SSD technology. They do...
See more...
Not enough information to go on without seeing the vmkernel logs might have to say as well as iDRAC info/logs. Could be the drives are just dying, especially if they are older SSD technology. They do have a life span.
Any time you use an IP network for storage connectivity, I always recommend using dedicated links. This goes for vSAN as well as external storage over NFS/iSCSI.
Most likely Avamar will not work if you do this. The compatibility is listed in terms of vSphere version which is vCenter plus ESXi. For confirmation, you should refer to the Avamar support matrix.
"so even in the esxi host web client name all of my servers with lower cases?" No, I'm talking about the vCSA and not others. "do you know if there is a gen8 installation of esxi/ if so do you have...
See more...
"so even in the esxi host web client name all of my servers with lower cases?" No, I'm talking about the vCSA and not others. "do you know if there is a gen8 installation of esxi/ if so do you have link? or is there a standard install that I could use?" You can get vendor-customized ISOs for ESXi from either the vSphere download page in your My VMware account or, in this case, from HPE downloads.
A couple of things: Do not use a FQDN with mixed cases. Use all lower case, always, everywhere. You need both A and PTR records to exist which correspond to the hostname for vCenter *before* yo...
See more...
A couple of things: Do not use a FQDN with mixed cases. Use all lower case, always, everywhere. You need both A and PTR records to exist which correspond to the hostname for vCenter *before* you begin the installation process. This must exist in local DNS. Have you done this? Please just paste screenshots in and keep responses in a single post as much as possible. We don't like to download attachments and scroll to read single-sentence replies.
You're right, and as I also said, it isn't available on the site any longer. But that doesn't mean that you can volunteer to distribute those bits to other people without an entitlement.
Why not just leave your AD groups entitled in vCenter as they are and manage their membership however you like? That then takes vCenter out of the equation entirely.
Because 5.0 and 5.5 are both now long out of support, unless you have active SnS, you won't be able to get public download links for either. Also, it's "VMware ESXi"
That often means the CIM sensors are picking up something. Check the Monitor tab of the host to see what errors show up. Check events also for this host. If these are Dell, look in your iDRAC to see ...
See more...
That often means the CIM sensors are picking up something. Check the Monitor tab of the host to see what errors show up. Check events also for this host. If these are Dell, look in your iDRAC to see if there are storage events that show.
You cannot use VUM to remediate hosts at a lower version than that of vCenter. If vCenter is 7.0, only 7.0 ISOs will be accepted into VUM's store. Older hosts which you aren't planning on bringing up...
See more...
You cannot use VUM to remediate hosts at a lower version than that of vCenter. If vCenter is 7.0, only 7.0 ISOs will be accepted into VUM's store. Older hosts which you aren't planning on bringing up to 7.0 will have to be upgraded via some other method.
You will sometimes run across this issue if a host has intermittently disconnected from vCenter but later re-connected. You can go and look at the event history for this host and know what exactly tr...
See more...
You will sometimes run across this issue if a host has intermittently disconnected from vCenter but later re-connected. You can go and look at the event history for this host and know what exactly triggered that response.
