- To take over partner node, we have to make sure there will be 1-2 minutes connectivity lost (CIFS/NFS)
-
2. Release ASUP before giveback options autosupport.doit per-takeovernode13. node2> cf takeover –f (node1 is takeover by node2)4. node2> cf: takeover initiated by operator5. node2 (takeover)> – Which means takeover completed.6. node2 (takeover)> partner (To see partner status )7. node2 /node1>8. To do giveback follow from step 99. When the system isn’t in partner context and if prompt shows as “ node1/node2>”, follow from step 4, if prompt shows as “node2(takeover)>” follow from step 510. node1/node2> partner11. node2(takeover)> cf statusnode2 has taken over node1.node1 is ready for giveback.12. Release ASUP before giveback options autosupport.doit per-giveback1node13. node2(takeover)> cf giveback14. If cf giveback is unsuccessful, try forcegiveback..15. node2(takeover)> cf giveback –f16. once the giveback completes, login to node1 and do health check17. node1> sysconfig –r18. node1> sysconfig –v19. node1> storage show disk –p20. node1> vfiler status –r21. node1> vfiler run vfilername exportfs22. node1> vfiler run vfilername cifs shares23. node1> vol status –s24. node1> vif status25. node1> ifconfig –a26. node1> options autosupport.doit post givenback1node
Popular Posts
-
After you scan the SAN for the currently presented LUNs, the service console needs to be made aware of the LUN changes. If your ESX Server ...
Sunday, September 21, 2014
NetApp - Cluster takeover and giveback procedure.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment