An architect has just deployed a new NSX Edge cluster in a VMware Cloud Foundation...

Comprehensive and Detailed 250 to 350 words of Explanation From VMware Cloud Foundation (VCF) documents:

In aVMware Cloud Foundation (VCF)deployment, establishing a stable BGP neighborship between theTier-0 Gatewayand the physicalTop-of-Rack (ToR)switches is only the first step in enabling North-South connectivity. While the BGP state may show as "Established," this only confirms that the control plane handshake is complete and the peers are ready to exchange prefixes.

The primary reason for a lack of external connectivity in this scenario is that norouting informationis being shared. For workloads within the SDDC to reach the internet, the Tier-0 Gateway must have a path to external networks. In most enterprise VCF designs, the physical network (ToR) is expected to provide adefault route (0.0.0.0/0)to the Tier-0 Gateway.

If the Tier-0 is not receiving this route, the issue typically lies in the physical router's configuration. BGP does not automatically "originate" or "redistribute" a default route unless explicitly commanded to do so. On most physical network platforms (like Cisco, Arista, or Juniper), the administrator must specifically configure a "default-originate" command or ensure a static default route exists in the physical RIB and is allowed to be advertised into the BGP session with the NSX Edge nodes.

Options A and C are unlikely to be the primary cause of a completely missing default route in a fresh deployment. Option B describes the inverse—where the virtual network tells the physical network how to find the internet—which is incorrect for a standard VCF consumer model. Therefore, verifying and enabling thedefault route advertisement on the physical ToR switchesis the verified solution to provide the Tier-0 with the necessary egress path for internet-bound workload traffic.

===========