Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.4 Administrator Guide > High Availability in SRM > SolarWinds High Availability requirements

SolarWinds High Availability requirements

Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 11 Votes: 0 Revisions: 1

High Availability is provided for SolarWinds products released on Orion Platform version 2016.2 and later. You cannot enable an HA pool for a server that includes non-supported products.

Visit SolarWinds KB MT6886 to build an upgrade path.

Supported products

  • Network Performance Monitor 12.0.1 and later
  • Server & Application Monitor 6.3 and later
  • NetFlow Traffic Analyzer 4.2.1 and later
  • Network Configuration Manager 7.5.1 and later
  • IP Address Manager 4.3.2 and later
  • User Device Tracker 3.2.4 and later
  • VoIP & Network Quality Manager 4.2.4 and later
  • Storage Resource Monitor 6.3 and later
  • Web Performance Monitor 2.2.1 and later

The following products can be integrated with your Orion Platform-based product. The integration module between products is supported under SolarWinds High Availability, but the stand-alone product is not supported.

  • Storage Manager 6.2.3
  • Virtualization Manager 6.3.2 and later
  • Firewall Security Manager 6.6.8
  • Engineers Toolset 11.0.3 and later
  • Database Performance Analyzer on Orion 10.2 and later
  • Patch Manager 2.1.3 and later

Software and Hardware requirements

SolarWinds strongly recommends that the hardware and software of the standby server matches the primary server. Using matching system specifications and installed software ensures the same performance in the event of a failover.

  • Both servers must be installed on Windows Server 2008 R2 or later.
  • Both servers must also meet or closely match the minimum hardware and software requirements for the products you have installed on the primary server.
  • Both servers must be able to connect to your SolarWinds Orion database.
  • If protecting an NTA environment, both servers must be able to connect to the separate NTA Flow Storage database.
  • SolarWinds does not provide failover support for any database.
  • Some SNMP trap, syslog message, and flow data is lost while waiting for the secondary server to become active.

Port requirements

Port Protocol Service/
Process
Direction Description
4369 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.
5671 TCP

SolarWinds High Availability

bidirectional Port 5671 must be open into the HA pool with the main Orion server from all Orion servers.
25672 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.

Networking requirements

SolarWinds High Availability does not support IPv6 addresses.

  • Both your primary and secondary servers must be on the same subnet.
  • Both pool members must have static IPv4 addresses set on the network adapter. You do not need dedicated NICs.
  • All pool members must be able to resolve the host names of all additional pollers, additional websites, and the main Orion server. Pool members must also be able to resolve the host names of members in the same pool.
  • A virtual IP address must be available on the same subnet as the primary and secondary servers.
  • Devices must be able to accept inbound connections from the source IP and VIP addresses.
  • Devices sending syslogs, SNMP traps, and NetFlow information to your Orion server must be configured to send the information to the VIP address and receive requests from the pool.

You may need to modify firewall rules to allow traffic from pool members and to the VIP address. For example, you may need to modify the NetFlow firewall rules to allow incoming TCP traffic on port 2055 to go to the VIP address.

Depending on your network, you may have additional requirements. Up to three IP addresses per pool may be in use among the VIP, primary, and secondary servers because of how Windows calculates the source IP address from the HA pool. You can modify your devices to receive requests from all IP addresses or determine which IP address is used as the source IP address.

 
Last modified
08:56, 14 Mar 2017

Tags

Classifications

Public