Each SCG instance must be reachable by the eLux devices managed via the SCG. Every VPN subnet from each SCG instance must be routed from the Scout server. Each eLux endpoint receives an OpenVPN configuration file containing a list of SCG instances. When connecting, the device attempts to open a VPN tunnel with the instance that currently has the least load, and if unreachable, it proceeds to the next instance. This setup enables dynamic load balancing, where devices may connect to different SCG instances after reboots depending on availability and load.
Devices may connect only to a single SCG instance if network reachability is incomplete, VPN subnet routing is missing for one or more instances, or eLux devices do not have an updated VPN configuration listing all SCG instances.
Network Accessibility: Each SCG instance must be reachable by the eLux devices that will be managed via the SCG.
VPN Subnet Routing: Ensure that each VPN subnet from every SCG instance is routed from the Scout server:
VPN Configuration on eLux Devices:
Dynamic Load Balancing: This configuration enables load balancing, where:
If onboard devices are using only one SCG (Scout Cloud Gateway) instance in a clustered environment with multiple SCG instances, verify that the setup meets the necessary requirements.
To enable balanced use of multiple SCG instances, ensure network reachability, proper VPN subnet routing, and updated VPN configurations on all eLux devices. This setup dynamically balances load across SCG instances, promoting optimal performance and stable connection distribution within the cluster.