thx Florian. so... if I understood u right... the feature is not realized yet?! I thought or hoped that I only haven't found the right description up to now.
the cluster-communication depends on the bcast/mcast-entries in ha.cf? or did you mean an other entry? My file ha.cf looks so: ************************************ autojoin any mcast br0 239.192.0.211 694 1 0 bcast bond1 bcast bond2 warntime 5 deadtime 15 initdead 30 keepalive 1 crm yes use_logd yes apiauth mgmtd uid=root respawn root /usr/lib64/heartbeat/mgmtd -v ************************************ the migration ... for my case... uses 192.168.250.x (node01 = uname -n). so if i swap the ip-adresses in "/etc/hosts" (as I described) ... I would switch the migration-path to the NIC using ip-adress 10.20.30.4x... right? "Florian Haas" <florian.h...@linbit.com> schrieb im Newsbeitrag news:4b7a8fc7.7070...@linbit.com... > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
