The NSX-T Controller must be configured as a cluster in active/active mode to preserve any information necessary to determine cause of a system failure and to maintain network operations with least disruption to workload processes and flows.
An XCCDF Rule
Description
<VulnDiscussion>Failure in a known state can address safety or security in accordance with the mission needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the SDN controller. Preserving network element state information helps to facilitate continuous network operations minimal or no disruption to mission-essential workload processes and flows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-251734r810060_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
To add additional NSX-T Manager appliances do the following:
From the NSX-T Manager web interface, go to System >>Appliances, and then click "Add NSX Appliance". Supply the required information to add additional nodes as needed, up to three total.
To configure NSX-T with a cluster VIP or external load balancer do the following: