AWS evs documentation change
Summary
Updated terminology from 'ESXi' to 'ESX' throughout the document and changed VCF version requirement from 5.2.1 to 5.2.x
Security assessment
Changes are terminological updates (ESXi to ESX) and version range adjustments without any security context. No evidence of security vulnerabilities, fixes, or security features being documented.
Diff
diff --git a/evs/latest/userguide/troubleshooting.md b/evs/latest/userguide/troubleshooting.md index 43fabf67e..4279e8893 100644 --- a//evs/latest/userguide/troubleshooting.md +++ b//evs/latest/userguide/troubleshooting.md @@ -5 +5 @@ -Troubleshoot failed environment status checksvSphere HA agent on this host could not reach isolation addressvSAN upgrade prechecks fail for ESXi host clusterAdd host failure due to incompatible cluster imageSDDC Manager fails VCF host validation during host commissioning +Troubleshoot failed environment status checksvSphere HA agent on this host could not reach isolation addressvSAN upgrade prechecks fail for ESX host clusterAdd host failure due to incompatible cluster imageSDDC Manager fails VCF host validation during host commissioning @@ -57 +57 @@ If you are still unable to resolve the issue after following this guidance, we r -This check verifies that your environment has a minimum of four hosts, which is a requirement for VCF 5.2.1. +This check verifies that your environment has a minimum of four hosts, which is a requirement for VCF 5.2.x. @@ -92 +92 @@ Use the SDDC Manager user interface to manage VCF solution and vSAN license keys -In the vCenter user interface, with the ESXi host selected, you see the message "vSphere HA agent on this host could not reach isolation address <IPv6 address>". +In the vCenter user interface, with the ESX host selected, you see the message "vSphere HA agent on this host could not reach isolation address <IPv6 address>". @@ -96 +96 @@ This error message indicates that the vSphere HA agent on a host is unable to re -## vSAN upgrade prechecks fail for ESXi host cluster +## vSAN upgrade prechecks fail for ESX host cluster @@ -98 +98 @@ This error message indicates that the vSphere HA agent on a host is unable to re -When attempting to upgrade the ESXi host cluster using SDDC Manager, vSAN disk-related prechecks may fail. This is because Amazon EVS uses vSAN Express Storage Architecture (ESA), and the upgrade prechecks do not apply to vSAN ESA. For more information, see [the Broadcom knowledge base article on this topic](https://knowledge.broadcom.com/external/article/369423/upgrade-prechecks-fails-with-esxi-cluste.html). +When attempting to upgrade the ESX host cluster using SDDC Manager, vSAN disk-related prechecks may fail. This is because Amazon EVS uses vSAN Express Storage Architecture (ESA), and the upgrade prechecks do not apply to vSAN ESA. For more information, see [the Broadcom knowledge base article on this topic](https://knowledge.broadcom.com/external/article/369423/upgrade-prechecks-fails-with-esxi-cluste.html). @@ -133 +133 @@ Follow these steps. -If you have updated your ESXi version after the Amazon EVS environment deployment, SDDC manager may fail during VCF host validation in the commission hosts step. To fix this issue, you will have to use vSphere Lifecyle Manager to upgrade ESXi on the newly added host. +If you have updated your ESX version after the Amazon EVS environment deployment, SDDC manager may fail during VCF host validation in the commission hosts step. To fix this issue, you will have to use vSphere Lifecyle Manager to upgrade ESX on the newly added host. @@ -141 +141 @@ Follow these steps. -These steps require temporarily adding the host to vCenter outside of SDDC Manager. Using vSphere Lifecyle Manager for any operations other than ESXi upgrades may render your host unusable, and require you to delete and create a new Amazon EVS host. +These steps require temporarily adding the host to vCenter outside of SDDC Manager. Using vSphere Lifecyle Manager for any operations other than ESX upgrades may render your host unusable, and require you to delete and create a new Amazon EVS host. @@ -145 +145 @@ These steps require temporarily adding the host to vCenter outside of SDDC Manag - 2. Add the host temporarily to your virtual data center, ensuring to select **manage host with an image**. The host will be removed in a later step after the ESXi upgrade is complete. For more information, see [How to Add a Host to Your vSphere Data Center or Folder](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/organizing-your-inventory-host-management/add-a-host-to-a-folder-or-a-data-center-host-management.html) in the vSphere documentation. + 2. Add the host temporarily to your virtual data center, ensuring to select **manage host with an image**. The host will be removed in a later step after the ESX upgrade is complete. For more information, see [How to Add a Host to Your vSphere Data Center or Folder](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/organizing-your-inventory-host-management/add-a-host-to-a-folder-or-a-data-center-host-management.html) in the vSphere documentation. @@ -149 +149 @@ These steps require temporarily adding the host to vCenter outside of SDDC Manag - 4. After the upgrade has completed, remove the host from your vCenter inventory. For more information, see [How to Remove an ESXi Host from Your vCenter Server Instance](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/managing-hosts-in-vcenter-server-host-management/remove-a-host-from-vcenter-server-host-management.html) in the vSphere documentation. + 4. After the upgrade has completed, remove the host from your vCenter inventory. For more information, see [How to Remove an ESX Host from Your vCenter Server Instance](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/managing-hosts-in-vcenter-server-host-management/remove-a-host-from-vcenter-server-host-management.html) in the vSphere documentation.