County finance needs to confirm which Edge VMs form the HA pair that serves tax-portal NAT. Where in NSX Manager does the operator inspect Edge cluster membership?
Select an answer to reveal the explanation.
Short Explanation
An Edge cluster is the firehouse that groups the trucks, not a street (segment) and not a smoke alarm (firewall section). Membership lives under System > Fabric > Nodes > Edge Clusters.
Full Explanation
County finance needs the HA pair that hosts tax-portal NAT, and that pairing is an Edge cluster—a System/Fabric object that groups Edge transport nodes for high availability and for attaching centralized services. Operators inspect or change membership at System > Fabric > Nodes > Edge Clusters, which is the firehouse roster for which trucks share SNAT, load balancing, and north-south duties for the civic tax portal. Networking > Segments is wrong because segments are L2 networks (overlay or VLAN); they do not enumerate Edge cluster membership as port groups. Security > Gateway Firewall fails by concept: firewall sections enforce policy; they are not the inventory object that defines which Edge VMs form an HA cluster. Plan & Troubleshoot > Traceflow is a packet-path diagnostic; it does not store or display cluster membership. Exam caveat: an Edge transport node can exist without being in a cluster useful for services, and a cluster can exist with members that are not yet ready—membership and node health are separate checks. Operational check: open Edge Clusters, confirm both tax-portal Edges are members of the intended cluster, verify the cluster is referenced by the Tier-0/Tier-1 that owns the NAT, and record cluster name plus member node names in the county runbook before the next failover test.