Red Hat Bugzilla – Bug 187952
cman attempts wrong broadcast domain for port 6809 traffic
Last modified: 2007-11-30 17:11:29 EST
Description of problem:
When cman starts (either via the cman service or through 'cman_tool -t 120 -w
join') it will broadcast on the wrong network (on a box with more than one NIC.)
The computer is directly connected to a network (172.19.0.0/32) that another
cluster node is also on. When parsing the file (/etc/cluster/cluster.conf) and
in subsequent communication attempts, this node only attemptes to contact other
cluster members on its OTHER network (192.168.0.0/32) (ifconfig output,
/etc/sysconfig/network-scripts/ifcfg-eth* and cluster.conf provided as
attachments.) Computer t2 is on networks: 172.16.0.0/16 and 172.19.0.0/16.
Computer t3 is on networks: 192.168.0.0/16 and 172.19.0.0/16. DNS resolution is
complete for both forward and reverse look-ups on both t2 and t3.
Version-Release number of selected component (if applicable):
always (from the same side of the cluster - t3)
Steps to Reproduce:
1. start cman
cman reports quorum but only after timing out past its 120 second limit.
Tcpdump reports broadcast messages on port 6809 to 192.168.255.255 (rather than
on its configured cluster.conf network)
broadcast messages on port 6809 to 172.19.255.255
I can provide strace info if required...
Created attachment 127312 [details]
attachments as described in Description (ifcfg-eth*, cluster.conf, route, etc)
in original description networks labeled as 172.19.0.0/32 and 192.168.0.0/32
should have both been /16's not /32's.
Can you tell me what t3.m_clust & t2.m_clust resolve to?
It's those names that cman will use when it determines which interface to bind to.
Is this still a problem or shall I close this bug ?