The most common use case is to install the Hybrid Cloud Manager, then install a single-path configuration.

A single path architecture uses the Cloud Gateway for migration, network extension, and network communication. This single-path architecture is sometimes called a "fleet" installation. Minimum Requirements for Single Path Use Cases summarizes the possible use cases, and what the minimal installation entails.

In addition to the fleet configuration, your architecture can include Layer 2 Concentrators that create alternate paths used to extend networks into the cloud, or to handle communication among virtual machines. The Cloud Gateway handles all migration and any network traffic for appliances in the fleet, while the independent Layer 2 Concentrators handle communication among virtual machines. By separating the migration path from the data path, you minimize the chance of migration workloads interfering with communication between VMs.

Network extension with either concentrator requires a virtual distributed switch.

A standard Layer 2 Concentrator can create multiple connections.

A high-throughput Layer 2 Concentrator can connect to only one vLAN. vMotion requires a high-throughput L2C and a stretched network.

Networking bandwidth is limited by your purchased hybrid networking option or your native bandwidth, whichever is smaller. Layer 2 extension speeds listed in Minimum Requirements for Single Path Use Cases and Minimum Requirements for Separate Path Use Cases are maximums and may vary based on factors beyond our control. For best results, use the vCloud Air Direct Connect service.

Minimum Requirements for Single Path Use Cases

#

Use Cases

HCM

Cloud Gateway

WAN Opt

Std L2C

HT L2C

Comments

S

A

E

1

Migration, up to 100 Mbps

X

 

 

X

O

O

 

L

2

Migration, 100+ Mbps

 

X

 

X

1 Gbps

O

 

L

3

Extension, up to 100 Mbps

X

O

 

X

100 Mbps

X

 

L

4

Extension and migration, up to 1 GB

 

X

X

X

1 Gbps

X

X

L, Z, DC

5

Extension and migration, up to 4 GB

 

 

X

X

1 Gbps

X

X

L, Z, DC

S | A | E: Standard | Advanced | Enterprise. Minimum Requirement: X. Optional: O.

WAN Opt enhances processing speed for workloads passing through the Cloud Gateway. WAN Opt speed is unrelated to network speed.

L: Low downtime migration, Z: Zero downtime migration (vMotion), DC: Direct Connect.

Minimum Requirements for Separate Path Use Cases

#

Use Cases

HCM

Cloud Gateway

WAN Opt

Std L2C

HT L2C

Comments

S

A

E

6

Network extension, up to 1 GB

 

X

X

X

1 Gbps

X

O

L, Z, DC

7

Network extensions, up to 4 GB

 

 

X

X

1 Gbps

O

X

L, Z, DC

S | A | E: Standard | Advanced | Enterprise. Minimum Requirement: X. Optional: O.

WAN Opt enhances processing speed for workloads passing through the Cloud Gateway. WAN Opt speed is unrelated to network speed.

L: Low downtime migration, Z: Zero downtime migration (vMotion), DC: Direct Connect.

The remainder of this chapter discusses specific Hybrid Cloud Manager features. Some features require a specific configuration, so determine your feature requirements when planning your architecture.

You can perform migration with a minimal configuration. Other than the Hybrid Cloud Manager, only the Hybrid Cloud Gateway appliance is required.

You can extend a network using either of the Layer 2 concentrators.

To deploy the Hybrid Cloud Manager, you must have the proper number of IP addresses available both on-premises and in your target vCloud Air data center.

Proximity Routing is a networking feature you can enable when you configure the Cloud Gateway.

The option to retain the MAC address is a check box in the migration wizard. It is only visible for replication-based migration.

The Policy Migration feature enables NSX distributed firewall rules to be moved from an on-premises vCenter to a vCloud Air virtual data center.