Hi @luismendez85, yes, exactly. While our documentation says you can update vCenter HA with vCenter 7.0, it doesn't work unfortunately as of today - assuming the docs were just copied from 6.7 and j...
See more...
Hi @luismendez85, yes, exactly. While our documentation says you can update vCenter HA with vCenter 7.0, it doesn't work unfortunately as of today - assuming the docs were just copied from 6.7 and just some things not adjusted properly. We had some cases in GS where customers were asking the same. - Patrik
Hi Alex, PSOSDs are very, very complex and relatively hard to diagnose (especially without a clear stacktrace like in your screenshot), hence time-consuming and might need engineering involvement. C...
See more...
Hi Alex, PSOSDs are very, very complex and relatively hard to diagnose (especially without a clear stacktrace like in your screenshot), hence time-consuming and might need engineering involvement. Collect the dump with a log bundle and file a SR as Fabio recommended for further analysis. And iLO not reporting errors doesn't necessarily mean there're no hardware faults. Regards, Patrik
Hi all, I got an update from a colleague, stating that HPE told that this is a known issue and has been introduced in the latest firmware of the P408i controller with release 3.53 (as @MythenIT corr...
See more...
Hi all, I got an update from a colleague, stating that HPE told that this is a known issue and has been introduced in the latest firmware of the P408i controller with release 3.53 (as @MythenIT correctly stated). It's known to exist in ESXi 6.7 and 7.0. The only workaround (known so far) seems to downgrade to firmware version 3.00. But as the firmware is up to HPE, please consult HPE in case you have further questions, if instructions for the downgrade are needed or when a written statement is required. I'd recommend reaching out to HPE for clarification or next steps. (Please note that this is just a cosmetic issue.) Kind regards, Patrik
One vmkernel adapter with vMotion tagged should only use one corresponding network uplink. If you want multiple network uplinks to be utilized (e.g. for redundancy, better performance) you'll need to...
See more...
One vmkernel adapter with vMotion tagged should only use one corresponding network uplink. If you want multiple network uplinks to be utilized (e.g. for redundancy, better performance) you'll need to do special configuration to be supported: see KB https://kb.vmware.com/s/article/2007467. (If not doing it this way, it could cause some strange issues with vMotion connectivity) Also, the more vmkernel adapter you have with vMotion, you get more vMotion processes in parallel (each 1 GBe gives you 4 concurrenet vMotions, 10 GBe 8 vMotions). Could speed up things. Regards, Patrik
Hi, the qlnativefc driver allows to use the Fiber-Channel HBAs made by QLogic. If you don't have any storage devices requiring this driver (you can verify by checking it with "esxcli storage core ad...
See more...
Hi, the qlnativefc driver allows to use the Fiber-Channel HBAs made by QLogic. If you don't have any storage devices requiring this driver (you can verify by checking it with "esxcli storage core adapter list") you can just remove this driver via "esxcli software vib remove -n qlnativefc". However, when there's no device using this driver, the driver isn't used and hence shouldn't cause any issues. So you could also just ignore or silence this alert too. Regards, Patrik
Hi, you can find further information and steps how vCenter HA can be patched over here: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vcenter.upgrade.doc/GUID-C27CD7DF-AB52-4A77-A6A6-A966...
See more...
Hi, you can find further information and steps how vCenter HA can be patched over here: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vcenter.upgrade.doc/GUID-C27CD7DF-AB52-4A77-A6A6-A966498D5CA0.html In case you're using vCenter 7.0, you currently can't patch vCenter HA environments in this major release. Based on my information this is something being worked on to be possible again. So you need to unconfigure vCenter HA, patch the vCenter and then re-enable vCenter HA afterwards. Hope this helps! - Patrik
Hi, can you please try updating to the latest ESXi 7.0 U2a release? (Released a few weeks ago: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2a-release-notes.html) Does this chan...
See more...
Hi, can you please try updating to the latest ESXi 7.0 U2a release? (Released a few weeks ago: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2a-release-notes.html) Does this change the behavior? If not and if the server is supported, I'd suggest opening a SR. Kind regards, Patrik
Hi, are you running ESXi 7.0 GA by any chance? If so, it could be: https://kb.vmware.com/s/article/83243. The first thing that came into my mind based on your description. Regards, Patrik
When you're on the HTML5 WebUI of vCenter you can e.g. right-click on a datacenter to add a host there. Then enter the credentials of the ESXi host which has enough permission to add the host to the ...
See more...
When you're on the HTML5 WebUI of vCenter you can e.g. right-click on a datacenter to add a host there. Then enter the credentials of the ESXi host which has enough permission to add the host to the vCenter - in most cases simply the root credentials. vCenter then takes care adding the host to vCenter and creates its own customer user (vpxuser) to interact with the host from this point on. When deploying vCenter you specify the SSO admin - by default administrator@vsphere.local. Use this to logon in your vCenter HTML5 Client.
VMware vSphere is the virtualization platform as a whole, including the vSphere Hypervisor (ESXi) and vCenter Server. (VMware vSphere Hypervisor is the new/official name for ESXi.) So both terms can'...
See more...
VMware vSphere is the virtualization platform as a whole, including the vSphere Hypervisor (ESXi) and vCenter Server. (VMware vSphere Hypervisor is the new/official name for ESXi.) So both terms can't be really compared. vCenter is deployed on a already existing ESXi host by mounting the ISO and starting the installer - see docs for more information: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.install.doc/GUID-F06BA415-66D8-42CD-9151-701BBBCE8D65.html Hope this helps!
As you correctly noticed the KB you've mentioned is just for enabling it on the ESXi host. On vCenter the MOB is enabled by default and can directly be accessed via https://VCSA_IP/mob/. Browse to th...
See more...
As you correctly noticed the KB you've mentioned is just for enabling it on the ESXi host. On vCenter the MOB is enabled by default and can directly be accessed via https://VCSA_IP/mob/. Browse to the URL and logon using your credentials.