# | Component | Consideration | Resource |
1 | vCloud Director Cells |  Suspend vCloud Director scheduler and stop the vCloud Director service.Repeat for subsequent cells.Perform Red Hat patches.Un-mount the NFS transfer share on each cell.Run the vCloud Director installer but do not start the services.Run the database upgrade script on the first cell only. Do not repeat this on the other cells.Run the vCloud Director installer on the other cells.Reboot each vCloud Director cell one at a time to make sure that all services start up correctly and that the NFS transfer volume is successfully mounted on the first cell before rebooting subsequent cells.Validate that vCloud Director has started by checking /opt/vmware/vcloud-director/logs/cell.log.Validate that the portal is working on each cell by connecting directly to the cell’s HTTP interface.Do not redirect the load balancer or allow users back onto the system yet. | vCloud administrator Linux administrator vCloud administrator |
2 | Update vCloud Director Agent on vSphere hosts | Update the host agent on all connected hosts. Check that connected hosts are still showing Available and Prepared. | vCloud administrator |
3 | vCloud Director Validation 1 | Validate basic functionality of vCloud Director by deploying a new vApp.Validate basic functionality by deploying a NAT routed network (either a routed organization network or fence a vApp that is deployed).Troubleshoot any issues before moving on.Rollback is possible at this stage by restoring the vCloud Director database and restoring the vCloud Director cells virtual machine backup or deleting the virtual machine snapshot. | vCloud administrator vCloud administrator vSphere administrator or database administrator |
4 | vCloud Networking and Security Manager Server | Upgrade of the vCloud Networking and Security Manager Server requires the use of an upgrade package. This file is usually named VMware--Manager-upgrade-bundle-5.1.0-.tar.gz. Do not deploy a new Service Manager appliance (OVA). Removing the existing Service Manager appliance breaks all connections and management to any deployed vCloud Networking and Security Manager Edge devices, resulting in errors. After a Service Manager is deployed, upgrade it only using a tar.gz file (in place upgrade). This preserves the local Service Manager database. | vCloud administrator |
5 | Edge devices | After vCloud Networking and Security Manager is upgraded, wait at least 15 minutes for it to update information with vCloud Director. Upgrade any organization vCloud Networking and Security Manager devices that are connected to an organization network that is routed. These devices are identified in vCloud Director 5.1 as edge gateways and can be upgraded by performing Re-Deploy. Upgrade any vApp network vCloud Networking and Security Manager devices connected to an vApp network that is routed. These devices are identified in vCloud Director 5.1 as edge gateways and can be upgraded by performing Re-Deploy. | vCloud administrator vCloud administrator or organization administrator |
6 | vCloud Director Validation 2 | Validate basic functionality of vCloud Director by deploying a new vApp.Validate basic functionality by deploying a NAT-routed network (either a routed organization network or fence a vApp that is deployed).Troubleshoot any issues before proceeding.Rollback is not possible at this stage as VSEs have been upgraded to the latest compatible versions. | vCloud administrator vCloud administrator |
7 | Chargeback Managers | The installer requires uninstallation of the previous version. Select Do not empty the database. | vCloud administrator |