Server Load Balancing Support
About Server Load Balancing
Visit the Server Load Balancing page for more information about this service.
Load Balancing Checklist
- All backend servers are identical in the content being served
- A self-signed certificate shared across the servers that can be trusted by the load balancer is in place on the service
- Service health monitor for the service is defined in documentation (What health check can be used to determine if the service is running?)
- Example: Querying https://servername.txstate.edu/healthcheck will return 200 if the services are running
- It is best to have the service up and configured across the backend servers prior to requesting load balancing so that validation can be completed during configuration
- Limit traffic on backend nodes so it’s only available to the load balancer. (IP’s provided on request)
- This is to ensure all traffic is routed through the load balancer.
- Exceptions to this are permitted if the backend nodes will need to be accessed by the clients.
Note: Any modifications after initial setup will require a change request.
Submit a Server Load Balancing Request.
Need help? Contact us.