A vSphere administrator deployed an NSX Edge Load Balancer in HA mode. What happens in the
event the Load Balancer has a failure?
A.
The secondary NSX Edge Load Balancer assumes the role of primary. Existing Flows will need
to have their connections reestablished.
B.
HA will start the NSX Edge Load Balancer on another ESXi host in the cluster. All existing flows
will need to have their connections reestablished.
C.
HA will start the NSX Edge Load Balancer on another ESXi host in the cluster. The NSX
Controller caches existing flows and hands them to the Load Balancer when it is back up.
D.
The secondary NSX Edge Load Balancer assumes the role of primary. The NSX Controller
caches existing flows and hands them to the Load Balancer when it is back up.
The Standby NSX Edge leverages the expiration of a specific “Declare Dead Time” timer to detect the failure of its
Active peer. This timer is configured by default to 15 seconds and can be tuned down to a minimum value of 6
seconds (via UI or API call) and it is the main factor influencing the traffic outage experienced with this HA model.
• Once the Standby gets activated, it starts all the services that were running on the failed Edge (routing, firewalling,
etc.). While the services are restarting, traffic can still be routed leveraging the information in the NSX Edge
forwarding table that was kept in synch between the Active and the Standby Edge units. The same applies to the
other logical services, since the state is synchronized and available also for FW, LB, NAT, etc.
0
0
I guess that they are missing the word “standalone” from the Design Guide:
” When focusing specifically on the routing functionalities between the logical and physical networks, there are actually three HA models that can be deployed: Active/Standby, Standalone and ECMP with the latter one representing a newer functionality introduced from NSX SW release 6.1 onward.”
0
0
From: https://pubs.vmware.com/NSX-6/topic/com.vmware.nsx.admin.doc/GUID-6C4F0C33-C6DD-432B-AA91-10AD6B449125.html
If a heartbeat is not received from the primary appliance within the specified time (default value is 15 seconds), the primary appliance is declared dead. The standby appliance moves to the active state, takes over the interface configuration of the primary appliance, and starts the NSX Edge services that were running on the primary appliance. When the switch over takes place, a system event is displayed in the System Events tab of Settings & Reports.
Load Balancer and VPN services need to re-establish TCP connection with NSX Edge, so service is disrupted for a short while. Logical switch connections and firewall sessions are synched between the primary and standby appliances, so there is no service disruption during switch over.
“A” looks to be the correct answer
0
0