Thanks Tim and Matthias for helping me out.<br><br>Clearing firewall rules and having the nodes address each other by hostnames instead of IP Addresses resolved the issue.<br><br>- Aravindh.<br><br><br><div class="gmail_quote">
On Mon, Jul 2, 2012 at 10:09 PM, Matthias Radestock <span dir="ltr">&lt;<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/07/12 03:06, Tim Watson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&quot;Error: unable to connect to node rabbit@rabbit3: nodedown&quot;<br>
<br>
Saying that rabbitmqctl cannot connect to rabbit@rabbit3, which is the<br>
local node!?<br>
</blockquote>
<br></div>
Correct. But that doesn&#39;t mean the node isn&#39;t running. &#39;nodedown&#39; is the reason Erlang gives, and it covers a multitude of failures, hence we show the diagnostics info in order to help narrowing down the cause.<span class="HOEnZb"><font color="#888888"><br>

<br>
Matthias.</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><font style="color:rgb(51,0,51);font-family:garamond,serif" size="4">Aravindh</font><br><br>