High Availability deployment walk-through
This topic applies to all Orion Platform products except for SolarWinds ETS.
The following provides a high-level walk-through of how to set up high availability protection on your main server or additional polling engines.
- Build a standby server. SolarWinds recommends that your standby server has similar or the same specifications as the primary server.
- Open port 5671 (TCP) on the primary (incoming) and standby (outgoing) servers.
- Open ports 4369 and 25672 (TCP) on the main Orion server and its standby server. These ports are not required when protecting additional polling engines.
- Download and install the secondary server software.
- Activate your HA pool licenses.
- Create your HA pool using either a VIP or virtual hostname.
To use an AlwaysOn SQL Availability Group as the Orion database, the Orion server must be configured to use the SQL listener. For information on creating and configuring the SQL listener, please refer to this Microsoft documentation (© Microsoft 2018, available at http://www.microsoft.com/, obtained on March 6, 2018).
Optional deployment steps
Depending on your network and device configuration, you may need to perform some of the following steps.
- Modify the firewall settings to allow communication to and from the VIP address or virtual hostname and the primary and secondary servers.
- For single subnet deployment, modify your DNS to point your Orion Web Console's host name to the VIP.
- Modify where devices send data to and receive data from.
- Route all traffic to and from the VIP or virtual hostname.
You cannot use a VIP in multi-subnet deployments.
Depending on your network setup, you may be able to change your primary server's IP address to another address in the subnet and use the already established SolarWinds IP address as the VIP address. See When do I use a VIP or a virtual hostname? for more information.
- Route all traffic to and from the IP addresses of the primary and secondary IP addresses. This can be done for both single and multi-subnet deployments.
- Route all traffic to and from the VIP or virtual hostname. You cannot use a VIP in multi-subnet deployments.
- Modify additional SolarWinds components to communicate to the HA pool.