3V0-25.25: Advanced VMware Cloud Foundation 9.0 NetworkingDemo

By Broadcom · Question Mode

QuestionQ41

Unknown / not found in official Broadcom sources

An administrator is investigating a BGP connectivity problem on a Tier-0 Gateway (Active/Active).

The Tier-0 is configured as follows:

  • Uplink VLAN 2711 → 172.25.100.0/24
  • Uplink VLAN 2712 → 172.25.101.0/24
  • Configured BGP neighbors: 172.25.100.1 and 172.25.101.1
  • One static default route (0.0.0.0/0) with next hop 172.25.100.1

The following symptoms appear on both Edge Nodes:

  • Get BGP neighbors → both neighbors remain in Idle (Connect) – "No route to peer"
  • Ping to 172.25.100.1 and 172.25.101.1 succeeds from the Edge nodes
  • Get route shows the default route only on the VLAN 2712 interface (fp-eth1), and it is absent from VLAN 2711 (fp-eth0)

What is causing both BGP sessions to stay in the Idle state?

  • A Multi-hop eBGP is required when using two VLANs.
  • B The static default route Scope is set only to the uplink VLAN 2712 segment.
  • C BGP authentication mismatch between Tier-0 and ToR routers.
  • D The ToR routers do not have routes back to the Edge uplink interfaces.
Explanation

A static route must be scoped to the uplink segment that contains its next-hop address. The next hop 172.25.100.1 is on VLAN 2711, but the default route is installed only on VLAN 2712. As a result, the Tier-0 lacks the correctly scoped route required to reach that BGP peer, producing the “No route to peer” condition and leaving the BGP sessions in Idle/Connect.

Community Discussion

No comments yet. Be the first to start the discussion!