An architect has just deployed a new NSX Edge cluster in a VMware Cloud Foundation (VCF) fleet. The BGP peer between the NSX Tier-0 gateway and the top-of-rack routers is successfully up and stable…

Question

Options

• ATier-0 gateway community settings are missing on the top-of-rack router configuration.
• BThe top-of-rack router receives a default route from Tier-0 gateway.
• CTier-0 gateway has a limit set too low for how many routes it can accept.
• DThere is no default route configured on the top-of-rack router for the Tier-0 gateway.

• A
  5% (2)
• B
  8% (3)
• C
  15% (6)
• D
  72% (28)

Explanation

In a VMware Cloud Foundation (VCF) deployment, establishing a stable BGP neighborship between the Tier-0 Gateway and the physical Top-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 The primary reason for a lack of external connectivity in this scenario is that no routing information is 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 a default 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

No community discussion yet for this question.