ed, Jun 26, 2013 at 10:03 AM, Jesse Pretorius wrote:
> On 26 June 2013 15:42, Brent Roskos wrote:
>
>> I've also used keepalived for services that did not scale laterally. In
>> this case I put two horizon servers behind an active/passive virtual IP.
>> This was als
Thus we
> are reviewing our network topology design again. At the same time we knew
> from the docs of rabbmit needs broadcast. And in the first try we made a
> wrong configuration for rabbitmq thus it did not work. We will have a
> detailed test on both of that.
>
> Best,
>
n wrote:
> Hi Brent,
>
> Thanks for your reply! But we are afraid that Rabbitmq needs broadcast to
> work correctly and usually broadcast is not available in cross-subnets
> deployments. That is what we are worrying about...
>
> Best,
>
> Kylin CG
>
>
>
>
>
By default rabbit uses tcp port 5672 for communication.. tcp can certainly
cross subnet boundaries and be routed without issue.
I suggest you do some network troubleshooting; ping your rabbit server
then telnet to port 5672 on the rabbit server from hosts on the other
subnets.
Check your router
