HA systems must be configured to talk to each other across both a Public interface, which is the network connection that is visible to the log sources, as well as a Private Interface. The Private Interface is the network that has no visibility other than the two members of the cluster.
It is recommended that the Public interface for each node be connected to a different switch to avoid the switch becoming a single point of failure in the configuration.
Failure to do so results in both nodes going out of service when the switch goes down, and user intervention will be required to restore services.
Repeat the following steps on each HA system.
Set Static IP Addresses and Rename NICs
NIC1 on each system should be connected to the production network, and NIC4 on each system to each other using the provided crossover cable in a single site setup.
- Crossover cable connecting Private interfaces on each
- Use IP Addresses that are not used in the customer’s environment
The NICs should also be labeled Public or Private accordingly.
Set the Binding Order
If you are on a Gen5 appliance with Server 2016, 2019, or later, this procedure does not apply and can be skipped. The installation script sets the configures the order or network interfaces automatically. There are no manual steps to take, as long as the network interfaces are named correctly. If you encounter problems, see the Microsoft documentation, Configure the Order of Network Interfaces.
NIC binding order MUST be set so that the Public NIC is the first one bound, and the Private NIC is the second one bound. To display the menu bar, press Alt.
Security Policy Considerations
If you encounter issues with the SIOS software not installing properly, you may need to add Debug permissions to the Administrator account. To do this:
- Click Start, Administrative Tools, and then Local Security Policy.
- Expand Local Policies.
- Select User Rights Assignment.
- Double-click Debug Programs and add the local administrator account.