This is the status when i bring down the eth1 interface.but crm resources are still running in cent64asf1 VM. its not getting switchover to cent64asf2.

[root@cent64asf1 ~]# corosync-cfgtool -s
Printing ring status.
Local node ID 281651392
RING ID 0
id = 192.168.201.16
status = ring 0 active with no faults
RING ID 1
id = 10.0.0.16
status = Marking seqid 16979 ringid 1 interface 10.0.0.16 FAULTY
I get the following error when i bring down the eth1 interface.
Sep 08 01:16:07 corosync [TOTEM ] sendmsg(ucast) failed (non-critical): Invalid argument (22)
Sep 08 01:16:08 corosync [TOTEM ] sendmsg(ucast) failed (non-critical): Invalid argument (22)
Sep 08 01:16:09 corosync [TOTEM ] sendmsg(ucast) failed (non-critical): Invalid argument (22)


I have installed DRBD,corosync,pacemaker. what should be the configuration for the failover when eth1 interface going down.

corosync.conf

totem {
version: 2
secauth: on
# threads: 0
rrp_mode: active
interface {
ringnumber: 0
bindnetaddr: 192.168.201.0
mcastaddr: 239.200.200.1
mcastport: 5405
ttl: 1
member {
memberaddr:192.168.201.16
}
member {
memberaddr:192.168.201.17
}
}
interface {
ringnumber: 1
bindnetaddr: 10.0.0.0
mcastaddr: 239.200.200.2
mcastport: 5407
ttl: 1
member {
memberaddr:10.0.0.16
}
member {
memberaddr:10.0.0.17
}



drbd.conf
on cent64asf1 {
address 10.0.0.16:7789;
}
on cent64asf2 {
address 10.0.0.17:7789;



Eth config
eth0 : 192.168.201.16
eth1 : 10.0.0.16