Configuration has yet to be fully verified, Kemp Support will gladly assist if your Graylog traffic is not flowing as expected.
1 Introduction
1.1 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 ensure that your Graylog servers are highly-available, scalable, and secure.
Configuration has yet to be fully verified, Kemp Support will gladly assist if your Graylog traffic is not flowing as expected.
2 Configuration Required
2.1 Global Configuration
No Changes Required
2.2 Virtual Service Configuration:
Two Virtual Services, one UDP and the other TCP both listening on port 9005 will be required.
2.3 GrayLog UDP Virtual Service
> New Virtual Service
> Enter IP Address
> Port = 9005
> Name = Graylog-UDP
> Protocol = UDP
> Add New Virtual Service
2.4 Standard Options
> Force Layer 7
> Disable Transparency
> Persistence = None
> Scheduling Method = Round Robin
> Idle Connection Timeout = 240 seconds
2.5 Real Servers
> Checker Parameter Type =ICMP
> Add New
> Enter Real Server IP Address
> Port = 9005
> Forwarding Method = NAT
2.3 GrayLog TCP Virtual Service
> New Virtual Service
> Enter IP Address
> Port = 9005
> Name = Graylog-TCP
> Protocol = UDP
> Add New Virtual Service
2.4 Standard Options
> Force Layer 7
> Disable Transparency
> Persistence = None
> Scheduling Method = Round Robin
> Idle Connection Timeout = 240 seconds
2.5 Real Servers
> Checker Parameter Type = HTTP
> URL = /system/lbstatus
> Checked Port = 12900 (Recommended by Graylog)
> Add New
> Enter Real Server IP Address
> Port = 9005
> Forwarding Method = NAT
If you have successfully Load Balanced your Graylog 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
0 comments