8. Multi-Site Considerations : 8.1 Scenario #1 – Multi-Site Common User Interface : 8.1.3 Multi-Site Common User Interface Design Implications : 8.1.3.1. Using Routed Organization Networks
   
8.1.3.1. Using Routed Organization Networks
When copying vApps across sites, it is very efficient and effective to use routed organization virtual datacenter networks for these vApps. In this way, the network can be replicated in each organization on each site, and the vApp can be attached to this network without guest customization changing the networking information. Routed organization virtual datacenter networks benefit the design and management of the vCloud environment regardless of whether stretched VLANs are used across the sites. Try and accommodate routed networks within the organizations to help the vApps to be more easily mobile (between organizations, sites, external networks, or even between vCloud environments).
The organization virtual datacenter network should be created in each organization so that the virtual machines in the vApp automatically become assigned to the correct network after a copy between organizations.
This has the following implications: In the event of copied vApps when not using guest customization, it is good practice to create all vApps in the same site, in the same organization, and on the same organization virtual datacenter network pool. Even if these vApps will only be used in one other organization, creating all vApps from the same network pool helps avoid IP conflicts. The reason for this is because if the same network pool exists in multiple locations, the same IP addresses could be given out to multiple different vApps.
For example, if virtual machine “VM A,” built in the master organization, gets built on the 192.168.0.xxx network, it is assigned the first IP address from that network’s pool. Assume that 192.169.0.100, is the first IP of this pool. If "VM B" gets created in a different organization (User Org 1) but on the same network pool (192.168.0.xxx to accommodate for the multisite environment), VM B will also receive the IP address of 192.168.0.100. Then, if you copy “VM A” to the “User Org 1,” it will need to be customized (using guest customization) so as not to conflict with VM B that already exists in that same organization with the same IP address.