In my history, VIP address is very unreliable feature - it moves in 50 - 70% of all possible scenarios (moreover, when cluster reconfigure back into 2 node system, after node-2 reboots, CRS moves VIP on new node (which have not any services running yet) and then (only) starts services. So, I'd better forget about VIP (rac cluster works fine no matter if VIP is moved properly or not).
-- -- Original Message -- -- From: "Silviu Marin-Caea" <silviu_marin-caea@(protected)> To: <suse-oracle@(protected)> Sent: Tuesday, February 07, 2006 7:17 AM Subject: [suse-oracle] When should a VIP address move to other node?
> We are testing the cluster to see how it behaves. > > If we unplug a node out of the interconnect switch, OCFS2 provokes kernel > panic. The VIP address of the panicked node moves to the surviving node. > This is fine, shows that the cluster is working. > > If we shutdown a node properly from Linux, its VIP is not moved to the > remaining node. Is this the intended, normal behaviour of Clusterware? > > > -- > To unsubscribe, email: suse-oracle-unsubscribe@(protected) > For additional commands, email: suse-oracle-help@(protected) > Please see http://www.suse.com/oracle/ before posting > >
-- To unsubscribe, email: suse-oracle-unsubscribe@(protected) For additional commands, email: suse-oracle-help@(protected) Please see http://www.suse.com/oracle/ before posting
