Configuring Evertz Mediator-X for Load Balancing
- Last Updated: March 12, 2025
- 1 minute read
- LoadMaster
- LoadMaster GA
- Documentation
Some changes must be made to the Mediator-X back-end servers for them to be correctly load balanced. These changes should be configured by an Evertz Deployment Team. Contact your Evertz representative for further information.
- On the Mediator-X deployment, connect to Node0 and log in as the root user. You can do this by executing the command sudo su and then entering the system-specific shell access password.
- Navigate to the directory /srv/salt/pillar. You can do this by executing the command cd /srv/salt/pillar.
- Edit the file system.sls, for example, using a text editor such as Nano or Vim: nano system.sls.
- Find the virtual_ips parameter and add the virtual IP address that will be used for the load balanced deployment. This is the user-facing IP address that all clients will connect to when accessing the load balanced Mediator-X services.
- The result should look like the following:
virtual_ips : 10.0.1.50# Set the loadbalancer virtual ip or leave blank - Save and exit the system.sls file.
- Run the salt command and call the state.highstate function, which automatically applies the changed configuration across all Mediator-X nodes. The full command to execute is:
sudo salt "*" state.highstate - Run the salt command and call a function to restart the NGINX service across all Mediator-X nodes. The full command to execute is:
sudo salt -G 'is_mediatorx:True' service.restart nginx