Configuration has yet to be fully verified, Kemp Support will gladly assist if your Splunk traffic is not flowing as expected.
Splunk allows an organization to capture, index and correlate real-time data stored in a searchable database from which it can then generate graphs, reports, alerts, dashboards and visualizations.
By implementing a Kemp Load balancing solution you will facilitate Splunk in horizontal scaling, enable High Availability, perform health checks at the application layer to ensure persistence and efficient work flows to your cluster.
1.2 Document Purpose
This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.
This specific configuration will enable your Splunk Search Page to be Load Balanced.
Configuration has yet to be fully verified, but Kemp Support will gladly assist if Splunk traffic is not flowing as expected.
2 Configuration Required
2.1 Global Configuration
>No Changes Required
2.2 Virtual Service Configuration:
2.3 Virtual Services
> New Virtual Service
> Enter IP Address
> Port = 443
> Name = Splunk
> Add New Virtual Service
2.4 Standard Options
> Disable Transparency
> Persistence = Active Cookie = Splunk (SSL Acceleration Required)
> Persistence Time = 1hr
> Scheduling Method = Least Connection
> Idle Connection Timeout = 660 (Default)
2.5 Enable SSL Acceleration (Enable Re-encryption if Server Requires)
> Assign Certificate
2.6 Real Servers
> Checker Parameter Type = HTTP (HTTPS If Re-Encrypting)
> Check Port = 8000
> Add New
> Enter IP Address
> Port = 8000
If you have successfully Load Balanced your Splunk Search Page environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you