In keeping with the existing vCloud DR solution there is a requirement to consider automation. While this solution offers additional simplicity and reduced configuration it is still necessary to update the configuration of multiple vCloud Networking and Security Edge Gateway (Edge Gateway) devices, which in turn can have multiple NAT or firewall rules defined. In this example, the approach to automating steps 3.b and 3.c is considered. Step 3.a is excluded because this is only a case of identifying vCloud Networking and Security Edge devices (easily identified by their location in the system virtual datacenter resource pools) and issuing a Power On request. (This is covered previously in the automation examples for the existing vCloud DR solution.)

In vCloud Director 1.x, the network services such as firewall, static routing, DHCP, and so on, were all associated with the organization network. However, in vCloud Director 5.1 all network services are associated with the Edge Gateway instead of the organization virtual datacenter network.