26IT103065 GSLB Requirements.docx
DOCX document 15 KB Posted
- Contract number
- 26-350SOS-ITSOS-P-88954
- Issued by
- Illinois
About this file
This document is a requirements specification for Global Server Load Balancing (GSLB) equipment or software, identified as GovTribe ID 26IT103065. While the specific contracting state, agency, and vendor information is not included in this excerpt, this appears to be a technical requirements document used in support of a state or local contract award process.
The requirements specify a comprehensive GSLB solution with both appliance and virtual machine deployment options, featuring a configurable graphical user interface and high availability capabilities. The solution must support multiple server preference configuration methods including global availability through topology-based geo-location services, dynamic weighted algorithms, and round-robin distribution. Key technical requirements include the ability to pool multiple IP addresses with preference settings, support for Secure Data Network System (SDNS) compatibility, advanced health check functionality across TCP/UDP, HTTP, and HTTPS protocols, LDAP health check capability, and configurable external health monitoring scripts. The solution must support FQDN configuration independent of server load balancers, specific server IP utilization, CNAME alias management, and HTTP response code validation across 2xx, 3xx, 4xx, and 5xx ranges. URL-specific path checking and page result validation are noted as preferred but non-mandatory features.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Global Server Load Balancing Requirements Must have configurable Graphical User Interface (GUI).
Must have appliance and virtual machine (VM) option.
Must have high availability.
Must have multiple options for setting server preference.
Must have Global Availability, Topology – Geo location (Extension mechanisms for domain name system, EDNS-CS), Dynamic weighted, round-robin.
Must have Ability to pool multiple internet protocols (IPs) and set a preference on those IPs inside the pool as well as being able to set a preference on multiple pools for a single Fully Qualified Domain Name (FQDN).
Must be Secure Data Network System (SDNS) capable.
Must be able to configure FQDN IPs outside of a corresponding server load balancer.
Must have the ability to use specific server IPs and not Virtual Service IPs.
Must have advanced health checks.
Must have health check options must include Transmission Control Protocol(TCP)/User Datagram Protocol(UDP) port, Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS) option.
Must be able to send a monitor string.
-For web apps, it is preferred to have the ability to check specific Uniform Resource Locator (URL) path and to check for page specific results, but this will not be considered a mandatory requirement.
Must be able to check for 2xx, 3xx, 4xx, 5xx return results.
Must have ability to perform Lightweight Directory Access Protocol (LDAP) health checks.
Must have external configurable health monitor. (ie. A health monitor script that can be configured to check multiple items include a username and password.)
Must have ability to add Aliases/Canonical Names (CNAMEs).
File details come from the government source that posted it. Updated .