Use VNETs in multi-locale organizations

The following example demonstrates the use of virtual networks (VNETs) in an organization with multiple locations.

In this example:
  • LocationA has SwitchA, ComputeA and StorageA. Migration-ZoneA, virtual-DatacenterA and Storage-PoolA are only allocated hardware from LocationA

  • LocationB has SwitchB, ComputeB and StorageB. Migration-ZoneB, virtual-DatacenterB and Storage-PoolB are only allocated hardware from LocationB.

The core router is configured to send 10.1.1.1-10.1.1.254 traffic to SwitchA, and 10.2.1.1-10.2.1.254 traffic to SwitchB.

A VNET (vnetA) using the range 10.1.1.1-10.1.1.254 can only work properly if the VNET services application is deployed on hardware associated with SwitchA. That is, when creating the VNET, Migration-ZoneA, virtual-DatacenterA and Storage-PoolA should be selected.

A VNET (vnetB) using the range 10.2.1.1-10.2.1.254 can only work properly if the VNET services application is deployed on hardware associated with SwitchB. That is, when creating the vnet Migration-ZoneB, virtual-DatacenterB and Storage-PoolB should be selected.

An instance using vnetA must be deployed on hardware associated with SwitchA for its networking to function properly. That is, when creating the instance Migration-ZoneA, virtual-DatacenterA and Storage-PoolA should be selected.

An instance using vnetB must be deployed on hardware associated with SwitchB for its networking to function properly. That is, when creating the instance Migration-ZoneB, virtual-DatacenterB and Storage-PoolB should be selected.