Simplifies IP addressing for management VMs by using the same VLAN and subnet.

Provides simplified secure access to management VMs in the same VLAN network.

The VIP address feature provides high availability only. It does not load-balance requests across the cluster.

When using the VIP address feature, all NSX Manager nodes must be deployed on the same Layer 2 network.

NSX Manager implements the control plane for virtual network segments. vSphere HA restarts the NSX Manager appliances first so that other virtual machines that are being powered on or migrated by using vSphere vMotion while the control plane is offline lose connectivity only until the control plane quorum is re-established.

Setting the restart priority to high reserves the highest priority for flexibility for adding services that must be started before NSX Manager.

Simplifies IP addressing for management VMs.

Provides simplified secure access to all management VMs in the same VLAN network.

The VIP address feature provides high availability only. It does not load-balance requests across the cluster.

When using the VIP address feature, all NSX Global Manager nodes must be deployed on the same Layer 2 network.

NSX Global Manager implements the management plane for global segments and firewalls.

NSX Global Manager is not required for control plane and data plane connectivity.

Setting the restart priority to medium reserves the high priority for services that impact the NSX control or data planes.

Management of NSX global components will be unavailable until the NSX Global Manager virtual machines restart.

The NSX Global Manager cluster is deployed in the management domain, where the total number of virtual machines is limited and where it competes with other management components for restart priority.

Connect the

fp-eth0

interface of each NSX Edge appliance to a VLAN trunk port group pinned to physical NIC 0 of the host, with the ability to failover to physical NIC 1.

Connect the

fp-eth1

interface of each NSX Edge appliance to a VLAN trunk port group pinned to physical NIC 1 of the host, with the ability to failover to physical NIC 0.

Leave the

fp-eth2

interface of each NSX Edge appliance unused.

Because VLAN trunk port groups pass traffic for all VLANs, VLAN tagging can occur in the NSX Edge node itself for easy post-deployment configuration.

By using two separate VLAN trunk port groups, you can direct traffic from the edge node to a particular host network interface and top of rack switch as needed.

In the event of failure of the top of rack switch, the VLAN trunk port group will failover to the other physical NIC and to ensure both

fp-eth0

and

fp-eth1

are available.

You must have routing between the VLANs for edge overlay and host overlay.

You must allocate another VLAN in the data center infrastructure for edge overlay.

Default teaming policy of load balance source with both active uplinks

uplink1

and

uplink2

.

Named teaming policy of failover order with a single active uplink

uplink1

without standby uplinks.

Named teaming policy of failover order with a single active uplink

uplink2

without standby uplinks.

An NSX Edge node that uses a single N-VDS can have only one uplink profile.

For increased resiliency and performance, supports the concurrent use of both edge uplinks through both physical NICs on the ESXi hosts.

The default teaming policy increases overlay performance and availability by using multiple TEPs, and balancing of overlay traffic.

By using named teaming policies, you can connect an edge uplink to a specific host uplink and from there to a specific top of rack switch in the data center.

Enables ECMP because the NSX Edge nodes can uplink to the physical network over two different VLANs.

The NSX Edge nodes are part of the north-south data path for overlay segments. vSphere HA restarts the NSX Edge appliances first to minimise the time an edge VM is offline.

Setting the restart priority to high reserves highest for future needs.

Satisfies the availability requirements by default.

Edge nodes must remain available to create services such as NAT, routing to physical networks, and load balancing.

Simplifies deployment of the edge nodes.

The same N-VDS switch design can be used regardless of edge form factor.

Supports multiple TEP interfaces in the edge node.

vSphere Distributed Switch is not supported in the edge node.

In the second availability zone, configure the top of rack switches or upstream Layer 3 devices with an SVI on each of the two uplink VLANs.

Make the top of rack switch SVI in both availability zones part of a common stretched Layer 2 network between the availability zones.

Use two VLANs to enable ECMP between the Tier-0 gateway and the Layer 3 devices (top of rack switches or Leaf switches).

The ToR switches or upstream Layer 3 devices have an SVI to one of the two VLANS and each NSX Edge node has an interface to each VLAN.

Extra VLANs are required.

Requires stretching uplink VLANs between availability zones

Used for configuring neighbor relationships with the Layer 3 devices in the second availability zone.

Ensures that all ingress traffic passes through the first availability zone.

Used for configuring neighbor relationships with the Layer 3 devices in the second availability zone.

Ensures that all egress traffic passes through the first availability zone.

Supports ECMP north-south routing on all nodes in the NSX Edge cluster.

Enables support for cross-instance Tier-1 gateways and cross-instance network segments.

In NSX Federation, a Tier-0 gateway lets egress traffic from connected Tier-1 gateways only in its primary locations.

Local ingress and egress traffic is controlled independently at the Tier-1 level. No segments are provisioned directly to the Tier-0 gateway.

A mixture of network spans (local to a VMware Cloud Foundation instance or spanning multiple instances) is enabled without requiring additional Tier-0 gateways and hence edge nodes.

If a failure in a VMware Cloud Foundation instance occurs, the local-instance networking in the other instance remains available without manual intervention.

Enables the learning and advertising of routes in the second

instance.

Facilitates a potential automated failover of networks from the first to the second

instance.

Enables network span between the

instances because NSX network segments follow the span of the gateway they are attached to.

Creates a two-tier routing architecture.

Enables cross-instance network span between the first and second

instances.

Enables deterministic ingress and egress traffic for the cross-instance network.

If a

instance failure occurs, enables deterministic failover of the Tier-1 traffic flow.

During the recovery of the inaccessible

instance, enables deterministic failback of the Tier-1 traffic flow, preventing unintended asymmetrical routing.

Eliminates the need to use BGP attributes in the first and second

instances to influence location preference and failover.

Enables instance-specific networks to be isolated to their specific instances.

Enables deterministic flow of ingress and egress traffic for the instance-specific networks.

Creates a two-tier routing architecture.

Enables local-instance networks that are not to span between the

instances.

Guarantees that local-instance networks remain available if a failure occurs in another

instance.

Enables the participation of ESXi hosts and the virtual machines running on them in NSX overlay and VLAN networks.

Transport node profiles can only be applied at the cluster level.

Creates isolated, multi-tenant broadcast domains across data center fabrics to deploy elastic, logical networks that span physical network boundaries.

Enables advanced deployment topologies by introducing Layer 2 abstraction from the data center networks.

Ensures that overlay segments are connected to an NSX Edge node for services and north-south routing.

Ensures that all segments are available to all ESXi hosts and NSX Edge nodes configured as transport nodes.

Removes the need for an external DHCP server for the host overlay VLANs.

You can use NSX Manager to verify static IP pool configurations.

You can use static IP pools for the host TEPs in each availability zone.

The NSX transport node profile can remain attached when using two separate VLANs for host TEPs at each availability zone as required for clusters that are based on vSphere Lifecycle Manager images.

Using an external DHCP server for the host overlay VLANs in both availability zones is not required.

Supports expansion to deployment topologies for multiple

instances.

Limits the number of VLANs required for the data center fabric.

You must add a separate Tier-1 gateway.

You must manually configure any services and synchronize them between the non-global service router instances in the first and second

instances.

To avoid a network conflict between the two

instances, make sure that the primary and standby networking services are not both active at the same time.

Because of incorrect configuration between the

instances, the load balancer service in the second instance might come online with an invalid or incomplete configuration.

If both

instances are online and active at the same time, a conflict between services could occur resulting in a potential outage.

The administrator must establish and follow an operational practice by using a runbook or automated process to ensure that configuration changes are reproduced in each

instance.