You can upgrade to Cloud Foundation 3.10.1.2 with a sequential or skip level upgrade.

For a sequential upgrade to VMware Cloud Foundation 3.10.1.2, your environment must be at VMware Cloud Foundation 3.10.1.1. You can perform a skip-level upgrade from VMware Cloud Foundation 3.5 or later. See Skip-Level Upgrade.

Upgrades are applied on a workload domain basis. The management domain contains the core infrastructure, so you must upgrade the management domain before upgrading the other workload domains. You must upgrade all required components to keep your system in an optimum state.

Upgrade NSX-T Workload Domains

Within an NSX-T workload domain, components must be upgraded in the following order.
  1. NSX-T. See Upgrade NSX-T Data Center.
  2. vCenter Server and Platform Services Controllers. See Upgrade vCenter Server and Platform Services Controllers.
  3. ESXi. See Upgrade ESXi.

Upgrade NSX for vSphere Workload Domains

If you performed a skip-level upgrade, you may also need to upgrade NSX for vSphere workload domains.
  1. NSX for vSphere. See Upgrade NSX for vSphere.
  2. vCenter Server and Platform Services Controllers. See Upgrade vCenter Server and Platform Services Controllers.
  3. ESXi. See Upgrade ESXi.

Post Upgrade Steps for NFS-Based Workload Domains

After upgrading workload domains, you must add a static route for hosts to access NFS storage over the NFS gateway. This process must be completed before expanding the workload domain.
  1. Identify the IP address NFS server for the workload domain.
  2. Identify the network pool associated with the hosts in the cluster and the NFS gateway for the network pool.
    1. Log in to SDDC Manager.
    2. Click Inventory > Workload Domains and then click the workload domain you are performing the post upgrade steps on.
    3. Click the Clusters tab and then click an NFS-based cluster.
    4. Click the Hosts tab and note down the network pool for the hosts.
    5. Click the Info icon next to the network pool name and note down the NFS gateway.
  3. Ensure that the NFS server is reachable from the NFS gateway. If a gateway does not exist, create it.
  4. Identify the vmknic on each host in the cluster that is configured for NFS traffic.
  5. Configure a static route on each host to reach the NFS server from the NFS gateway.

    esxcli network ip route ipv4 add -g NFS-gateway-IP -n NFS-gateway

  6. Verify that the new route is added to the host using the NFS vmknic

    esxcli network ip route ipv4 list

  7. Ensure that the hosts in the NFS cluster (nfs-cluster-1) can reach the NFS gateway (10.0.24.1) through the NFS vmkernel (vmk2) using the vmkping command.

    vmkping -4 -I vmk2 -s 1470 -d -W 5 10.0.22.250

  8. Repeat steps 2 through 7 for each cluster using NFS storage.