An administrator has observed an NSX Local Manager (LM) outage at the secondary Site. However, the NSX Global Manager (GM) in secondary Site remains operational. What happens to data plane…

Question

Options

• AAll traffic is blocked until secondary site LM recovers.
• BOnly local policies work; global policies cease to apply on the secondary site.
• CThe data plane operates normally until LM recovery and reconnection.
• DSecondary site must failover all workloads to Primary site.

• A
  20% (6)
• B
  3% (1)
• C
  70% (21)
• D
  7% (2)

Explanation

The architecture of NSX Federation within a VCF Multi-Site design is built upon a separation of the Control Plane and the Data Plane. This "decoupled" architecture ensures high availability and resiliency even when management components become unavailable. In NSX Federation, the Global Manager (GM) handles the configuration of objects that span multiple locations, while the Local Manager (LM) is responsible for pushing those configurations down to the local Transport Nodes (ESXi hosts and Edges) within its specific site. When a configuration is pushed, the Local Manager communicates with the Central Control Plane (CCP) and subsequently the Local Control Plane (LCP) on the hosts. If an NSX Local Manager goes offline, the "Management Plane" for that site is lost. This means no new segments, routers, or firewall rules can be created or modified at that site. However, the existing configuration is already programmed into the Data Plane (the kernels of the ESXi hosts and the DPDK process of the Edge nodes). According to VMware's "NSX Multi-Location Design Guide," the data plane remains fully operational during a Management Plane outage. Existing VMs will continue to communicate, BGP sessions on the Edges will remain established, and Distributed Firewall (DFW) rules will continue to be enforced based on the last known good configuration state cached on the hosts. The data plane does not require constant heartbeats from the Local Manager to forward traffic. Therefore, operations continue normally "headless" until the LM is restored and can resume synchronization with the Global Manager and local hosts. Failover to a primary site (Option D) is only necessary if the actual data plane (hosts/storage) fails, not just the management components.

No community discussion yet for this question.