Configuration has yet to be fully verified, Kemp Support will gladly assist if your RabbitMQ traffic is not flowing as expected.
1 Introduction
RabbitMQ is an open source application that allows robust messaging for applications, that implements the Advanced Message Queuing Protocol.
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 RabbitMQ servers are highly-available, scalable, and secure.
Configuration has yet to be fully verified, Kemp Support will gladly assist if your RabbitMQ traffic is not flowing as expected.
2 Configuration Required
2.1 Global Configuration
No Changes Required
2.2 Virtual Service Configuration:
One Layer 4 Virtual Service required, listening on port 5672. This service will be automatically "Transparent", please see prerequisites for Transparency to function. https://support.kemptechnologies.com/hc/en-us/articles/360003142651-Understanding-Transparency
It is important to note the AMQP heartbeats as we will need to match our idle timeout with the setting for the application server. This will prevent us from closing the connection abruptly. Idle timeout for this VS is 10 mins.
More details on this can be found here. https://www.rabbitmq.com/configure.html#config-items
2.3 Virtual Services
> New Virtual Service
> Enter IP Address
> Port = 5672
> Name = RabbitMQ
> Add New Virtual Service
2.4 Standard Options
> Disable "Force L7"
> Persistence = Source IP
> Scheduling Method = Round Robin
2.5 Real Servers
> Checker Parameter Type = TCP
> Check Port = 5672
> Add New
> Enter Real Server IP Address
> Port = 5672
> Forwarding Method = NAT
If you have successfully Load Balanced your RabbitMQ 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