<font size=2 face="sans-serif">Pavlos,</font>
<br>
<br><font size=2 face="sans-serif">Thanks for helping out on this. We
are running on RHEL 5.5 running on the iron and not a VM. We don't
have SELinux turned on and the firewall is disabled. Here is information
in the /etc/modprobe.conf file.</font>
<br>
<br><font size=2 face="sans-serif">alias eth0 bnx2</font>
<br><font size=2 face="sans-serif">alias eth1 bnx2</font>
<br><font size=2 face="sans-serif">alias scsi_hostadapter cciss</font>
<br><font size=2 face="sans-serif">alias scsi_hostadapter1 qla2xxx</font>
<br><font size=2 face="sans-serif">alias scsi_hostadapter2 usb-storage</font>
<br><font size=2 face="sans-serif">alias bond0 bonding</font>
<br><font size=2 face="sans-serif">options bond0 mode=1 miimon=100</font>
<br><font size=2 face="sans-serif">options lpfc lpfc_lun_queue_depth=16
lpfc_nodev_tmo=30 lpfc_discovery_threads=32</font>
<br>
<br>
<br><font size=2 face="sans-serif">We did take off the bond0 as a test
and now only have our IP address assigned to eth0 and still having the
same problem when starting corosync. The problem we are finding in the
/var/log/cluster/corosync.log file is below.</font>
<br>
<br><font size=2 face="sans-serif">Sep 30 07:58:57 e-magdb1.buysub.com
crmd: [28406]: info: crm_timer_popped: Election Trigger (I_DC_TIMEOUT)
just popped!</font>
<br><font size=2 face="sans-serif">Sep 30 07:58:57 e-magdb1.buysub.com
crmd: [28406]: WARN: do_log: FSA: Input I_DC_TIMEOUT from crm_timer_popped()
received in state S_PENDING</font>
<br><font size=2 face="sans-serif">Sep 30 07:58:57 e-magdb1.buysub.com
crmd: [28406]: info: do_state_transition: State transition S_PENDING ->
S_ELECTION [ input=I_DC_TIMEOUT cause=C_TIMER_POPPED origin=crm_timer_popped
]</font>
<br>
<br><font size=2 face="sans-serif">What could this 'just popped' message
mean?</font>
<br>
<br><font size=2 face="sans-serif">Mike</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Pavlos Parissis <pavlos.parissis@gmail.com></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">The Pacemaker cluster resource manager
<pacemaker@oss.clusterlabs.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">09/29/2010 04:01 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [Pacemaker] Does bond0 network interface
work with corosync/pacemaker</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3><br>
</font>
<br><font size=3>On 29 September 2010 21:01, Andreas Hofmeister <</font><a href=mailto:andi@collax.com><font size=3 color=blue><u>andi@collax.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>On 29.09.2010 19:59, Mike A Meyer wrote: </font>
<br><font size=3>We have two nodes that we have the IP address assigned
to a bond0 network interface instead of the usual eth0 network interface.
We are wondering if there are issues with trying to configure corosync/pacemaker
with an IP assigned to a bond0 network interface. We are seeing that
corosync/pacemaker will start on both nodes, but it doesn't detect other
nodes in the cluster. We do have SELinux and the firewall shut off
on both nodes. Any information would be helpful. </font>
<br><font size=3> </font>
<br><font size=3>We run the cluster stuff on bonding devices (actually
on a VLan on top of a bond) and it works well. We use it in a two-node
setup in round-robin mode, the nodes are connected back-to-back (i.e. no
Switch in between).<br>
<br>
If you use bonding over a Switch, check your bonding mode - round-robin
just won't work. Try LACP if you have connected each node to a single
switch or if your Switches support link aggregation over multiple Devices
(the cheaper ones won't). Try "active-backup" with multiple switches.<br>
<br>
To check your configuration, use "ping" and check the "icmp_seq"
in the replies. If some sequence number is missing, your setup is probably
broken.<br>
</font>
<br><font size=3><br>
It is quite common to connect both interfaces of a bond on the same switch
and then face issues.<br>
Mike you need to tell us a bit more on the layer 2 connectivity and how
it does look like.<br>
<br>
We also use active-backup mode on our bond interfaces, but we use 2 switches
and it works without any problem<br>
<br>
Cheers,<br>
Pavlos<br>
</font>
<br><tt><font size=2>_______________________________________________<br>
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
</font></tt><a href=http://oss.clusterlabs.org/mailman/listinfo/pacemaker><tt><font size=2>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</font></tt></a><tt><font size=2><br>
<br>
Project Home: </font></tt><a href=http://www.clusterlabs.org/><tt><font size=2>http://www.clusterlabs.org</font></tt></a><tt><font size=2><br>
Getting started: </font></tt><a href=http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf><tt><font size=2>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</font></tt></a><tt><font size=2><br>
Bugs: </font></tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker"><tt><font size=2>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>