why you are editing corosync.conf, but as cluster stack, you are using cman?
2013/12/9 emmanuel segura <emi2f...@gmail.com> > because in your corosync-cfgtool -s you are using bonding address > > > > > 2013/12/9 Dvorak Andreas <andreas.dvo...@baaderbank.de> > >> Hi >> >> >> >> Here it is >> >> cat /proc/net/bonding/bond0 >> >> Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) >> >> >> >> Bonding Mode: fault-tolerance (active-backup) >> >> Primary Slave: None >> >> Currently Active Slave: em3 >> >> MII Status: up >> >> MII Polling Interval (ms): 100 >> >> Up Delay (ms): 0 >> >> Down Delay (ms): 0 >> >> >> >> Slave Interface: em3 >> >> MII Status: up >> >> Speed: 1000 Mbps >> >> Duplex: full >> >> Link Failure Count: 0 >> >> Permanent HW addr: c8:1f:66:d7:3b:fe >> >> Slave queue ID: 0 >> >> >> >> Slave Interface: p3p3 >> >> MII Status: up >> >> Speed: 1000 Mbps >> >> Duplex: full >> >> Link Failure Count: 0 >> >> Permanent HW addr: 00:0a:f7:3e:ca:8e >> >> Slave queue ID: 0 >> >> >> >> Andreas >> >> >> >> *Von:* emmanuel segura [mailto:emi2f...@gmail.com] >> *Gesendet:* Montag, 9. Dezember 2013 15:50 >> *An:* The Pacemaker cluster resource manager >> *Betreff:* Re: [Pacemaker] cluster heartbeat is not used >> >> >> >> show cat /proc/net/bonding/bond0 >> >> >> >> 2013/12/9 Dvorak Andreas <andreas.dvo...@baaderbank.de> >> >> Dear all, >> >> >> >> during failover tests I found out that I can put down the heartbeat >> interfaces and the cluster ignores that. But if I put down bond0 the >> fencing is running. >> >> Can please somebody help me? >> >> >> >> bond0 Link encap:Ethernet HWaddr C8:1F:66:D7:3B:FE >> >> inet addr:10.15.28.36 Bcast:10.15.255.255 Mask:255.255.0.0 >> >> inet6 addr: fe80::ca1f:66ff:fed7:3bfe/64 Scope:Link >> >> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 >> >> >> >> em4 Link encap:Ethernet HWaddr C8:1F:66:D7:3B:FF >> >> inet addr:192.168.2.36 Bcast:192.168.2.255 Mask:255.255.255.0 >> >> inet6 addr: fe80::ca1f:66ff:fed7:3bff/64 Scope:Link >> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> >> >> >> p3p4 Link encap:Ethernet HWaddr 00:0A:F7:3E:CA:8F >> >> inet addr:192.168.3.36 Bcast:192.168.3.255 Mask:255.255.255.0 >> >> inet6 addr: fe80::20a:f7ff:fe3e:ca8f/64 Scope:Link >> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> >> >> >> I have the following corosync.conf >> >> # Please read the corosync.conf.5 manual page >> >> compatibility: whitetank >> >> totem { >> >> version: 2 >> >> secauth: off >> >> threads: 0 >> >> interface { >> >> ringnumber: 0 >> >> bindnetaddr: 192.168.2.0 >> >> mcastaddr: 226.94.1.1 >> >> mcastport: 5405 >> >> ttl: 1 >> >> } >> >> interface { >> >> ringnumber: 1 >> >> bindnetaddr: 192.168.3.0 >> >> mcastaddr: 226.94.1.2 >> >> mcastport: 5407 >> >> ttl: 1 >> >> } >> >> } >> >> logging { >> >> fileline: off >> >> to_stderr: no >> >> to_logfile: yes >> >> to_syslog: yes >> >> logfile: /var/log/cluster/corosync.log >> >> debug: off >> >> timestamp: on >> >> logger_subsys { >> >> subsys: AMF >> >> debug: off >> >> } >> >> } >> >> amf { >> >> mode: disabled >> >> } >> >> >> >> I have installed >> >> cluster-glue-libs.1.0.5.x86_64.CentOS >> >> corosynclib.1.4.1.x86_64.CentOS >> >> openais.1.1.1.x86_64.CentOS >> >> cman.3.0.12.1.x86_64.CentOS >> >> pacemaker-libs.1.1.8.x86_64.CentOS >> >> resource-agents.3.9.2.x86_64.CentOS >> >> corosync.1.4.1.x86_64.CentOS >> >> modcluster.0.16.2.x86_64.CentOS >> >> openaislib.1.1.1.x86_64.CentOS >> >> pacemaker-cluster-libs.1.1.8.x86_64.CentOS >> >> pacemaker.1.1.8.x86_64.CentOS >> >> pcs.0.9.26.noarch.CentOS >> >> libqb.0.14.2.x86_64.CentOS >> >> clusterlib.3.0.12.1.x86_64.CentOS >> >> ricci.0.16.2.x86_64.CentOS >> >> pacemaker-cli.1.1.8.x86_64.CentOS >> >> fence-virt.0.2.3.x86_64.CentOS >> >> ccs.0.16.2.x86_64.CentOS >> >> >> >> # corosync-cfgtool -s >> >> Printing ring status. >> >> Local node ID 1 >> >> RING ID 0 >> >> id = 10.15.28.36 >> >> status = ring 0 active with no faults >> >> # pcs status corosync >> >> Nodeid Name >> >> 1 sv2836.muc.baag >> >> 2 sv2837.muc.baag >> >> >> >> # crm_mon --one-shot -V >> >> Last updated: Mon Dec 9 14:56:32 2013 >> >> Last change: Mon Dec 9 14:07:03 2013 via cibadmin on sv2836 >> >> Stack: cman >> >> Current DC: sv2836 - partition with quorum >> >> Version: 1.1.10-1.el6_4.4-368c726 >> >> 2 Nodes configured >> >> 4 Resources configured >> >> >> >> Online: [ sv2836 sv2837 ] >> >> >> >> ClusterIP (ocf::heartbeat:IPaddr2): Started sv2836 >> >> FIXRoute (ocf::baader:FIXRoute): Started sv2836 >> >> ipmi-fencing-sv2837 (stonith:fence_ipmilan): Started >> sv2836 >> >> ipmi-fencing-sv2836 (stonith:fence_ipmilan): Started sv2837 >> >> >> >> Best regards >> >> Andreas Dvorak >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> >> >> >> -- >> esta es mi vida e me la vivo hasta que dios quiera >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> > > > -- > esta es mi vida e me la vivo hasta que dios quiera > -- esta es mi vida e me la vivo hasta que dios quiera
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org