what kick out one node from failover cluster ?
hi :)
failover cluster have 3 node (node majority) , connected netapp storage via fc.
this morning 1 node stops see storage, cluster, other nodes.. failover cluster manager console did not saw cluster, can not connect vm running on node (from hyper-v console), live migration not possible. vm's goes offline onto node.
first error 5120: cluster shared volume 'volume1' ('aggr0-vol-boot_win-vm_boot') no longer available on node because of 'status_bad_network_path(c00000be)'. i/o temporarily queued until path volume reestablished.
after i've reviewed event log i've noticed error 5719 netlogon occured 12 minutes before 5120 error.
my team member started manualy vm's after time again "crashed" , goes offline. after perform quick migration other 2 nodes , restarted problematic node1 , run ok.
i wondering goes wrong ? i've never saw such behaivour 1 node "kicked out" , locked vm's can lm them problematic node other nodes because node not see other nodes... also, dc's available time, nothing in dc's event log show node1 not establish secure channell connection. network team i've got response on network not problems also.
hi,
can please share cluster logs detailed analysis.
thanks
sudhir
Windows Server > High Availability (Clustering)
Comments
Post a Comment