Before deploying RabbitMQ, you must meet all deployment prerequisites.

Table 1. Routing
From To Description
VMware Cloud Provider Lifecycle Manager vCenter infra server VMware Cloud Provider Lifecycle Manager need access to the management vCenter Server to deploy the RabbitMQ instances.
RabbitMQ RabbitMQ Used for communication between all RabbitMQ instances.
RabbitMQ Load Balancer RabbitMQ The Load Balancer accesses the RabbitMQ instances on port 5671.

You can configure the load balancer to use the RabbitMQ management port 15671.

VMware Cloud Director RabbitMQ Load Balancer Used for communication from VMware Cloud Director to the RabbitMQ instance and RabbitMQ load balancer by using AMQP on the configured port.

The default port is 5671.

vRealize Operations Manager Tenant App RabbitMQ Load Balancer Used from vRealize Operations Manager Tenant App to access the RabbitMQ AMQP service.
RabbitMQ NTP The NTP server must be accessible by all RabbitMQ instances.
RabbitMQ DNS The DNS server must be accessible by all RabbitMQ instances.
Table 2. Network Ports
Port Protocol Description
53 TCP/ UDP DNS
123 TCP/ UDP NTP
4369 TCP A peer discovery service used by RabbitMQ instances and CLO tools.
5671 TCP AMQP SSL
5672 TCP/ UDP AMQP non-SSL (where non-SSL is required)
15671 Used from the RabbitMQ management interface.
25672 RabbitMQ inter-node and CLI tools communication
35672 CLI Tools for communication with the nodes.
35673 CLI Tools for communication with the nodes.
Table 3. Service Accounts
System Usage
Management VC Used to deploy the RabbitMQ instances in the management vCenter Server domain.

Additional Prerequisites

To provide access to all RabbitMQ instances, you must configure the RabbitMQ load balancer. DNS – DNS A and PTR records must exist for each RabbitMQ instance and the load balancer to enable forward and reverse lookup of IP addresses and hostnames.