An administrator must provide North/South connectivity for a VPC. The fabric exposes a distributed external VLAN across all ESX hosts. But, the only BGP peer to the core is on a VLAN only accessible…

Question

Options

• AUse a VPC Tier-0 Gateway in active/active mode with distributed eBGP peering.
• BDistributed Transit Gateway with an EVPN route reflector on the transport nodes.
• CCentralized Transit Gateway on the Edge Cluster.
• DDeploy a Provider Tier-1 with BGP and connect the VPC Transit Gateway via route leaking.

• A
  4% (2)
• B
  2% (1)
• C
  83% (40)
• D
  10% (5)

Explanation

In a VMware Cloud Foundation (VCF) environment utilizing the Virtual Private Cloud (VPC) model, North/South connectivity is managed by the Transit Gateway (TGW). The TGW acts as the bridge between the VPC-internal networks and the provider-level physical network. The scenario presents a specific constraint: while an external VLAN exists across all hosts, the actual BGP peering point (the interface to the physical core routers) is restricted to the NSX Edge Cluster. In NSX terminology, when a gateway or service must be anchored to specific Edge Nodes to access physical network services--such as BGP peering, NAT, or stateful firewalls--it must be configured as a Centralized component. A Centralized Transit Gateway (Option C) is instantiated on the Edge nodes. This allows the TGW to participate in the BGP session with the core routers on the VLAN that is only accessible to those Edges. The TGW then handles the routing for the VPC's internal segments. Traffic from the ESXi transport nodes (East-West) travels via the Geneve overlay to the Edge nodes, where it is then routed North-South by the Centralized TGW using the physical BGP peer.

No community discussion yet for this question.