Network Management

Load Balance for Orion Web Console Servers

Using Load Balancer like F5 Load balancing for Additional Web Servers (AWS)

First published date

7/15/2019 4:04 PM

Last published date

3/22/2025 2:36 AM

Overview

A compilation of Thwack Articles with regards to Load Balancing multiple AWS setup in the environment: Please note that Thwack is a community space where users may post any content as a suggestion or recommendations to you for your internal use. The information set forth herein may come from third-party websites or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.


Solarwinds does not have guidelines about setting up load balancing for multiple webservers


 

Product section

Network Performance Monitor

Resolution

Problem 1:
A customer that had this setup and working, the problem they had was the scheduled report was not showing graphs.
Solution:
A possible issue is that the load balancer interferes with the generated graph from AWS1 and the Load Balancer Switches to AWS2, the tables are able to be fetched from either server however the Graph images will only be available on the first server the request was initiated.

A workaround for this is to have the scheduled job run on the main polling engine instead and change the hostname, FQDN, and External URL in the Websites table to the load balancer's URL in case there's an embedded link that requires routed linked to the unified web address.

Problem 2: URL being redirected to Main polling engine URL
Solution: Check the load balancer configuration for hostname and DNS mapping.