On 01/18/2011 12:41 PM, Gerry Reno wrote:

On secondary:

     # tcpdump -i eth0 'port 24007'
     tcpdump: verbose output suppressed, use -v or -vv for full protocol
     decode
     listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
     ^C
     0 packets captured
     0 packets received by filter
     0 packets dropped by kernel

This is the acid test. If no packets are getting between the units on this port, then something is firewalling them.

and see if you can get anything when you telnet into that port?
On secondary:

     # telnet 10.XXX.58.95 24007
     Trying 10.XXX.58.95...
     Connected to 10.XXX.58.95.
     Escape character is '^]'.

Can you telnet into the secondary on this port from the primary, and let us know what you see when you tcpdump that port on the secondary

If you get a connection, and see no packets, then something is badly broken in assumptions about network connectivity.

You shouldn't get a connected message if it didn't connect. tcpdump won't lie (as long as the options are correct).

--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: [email protected]
web  : http://scalableinformatics.com
       http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Reply via email to