Log on to a mgt LIF on the second node.
'system node halt -node node1 -reason 'disaster coming' -inhibit-takeover true
system node halt -node node2 -reason 'disaster coming'
Turn off controllers, disk shelves and switches.
Turn on switches, then shelves, then controllers.
If autoboot isn't set then 'boot_ontap' from the sp or console.
See also 'System Administration Guide' portion of the documentation.
I hope this response has been helpful to you.
At your service,
Eugene E. Kashpureff
Senior Consultant, K&H Research http://www.khresear.ch/
Senior Instructor, Unitek Education http://www.unitek.com/training/netapp/
Thanks for your response, I have followed the steps you have giving but on start up the the vio servers couldn,t see their luns, I have restarted FCP services still luns are not visible. what do you think is the problem. thank you.
I'll hope you didn't reboot just to try and fix LUN connectivity.
The only time I'd want to shut the cluster down would be if a disaster was about to hit.
LUN connectivity issues are often caused by errors in igroup or LUN mapping ...
Thanks for your response.
After reboot and FCP services restarted the luns became visible to the Vio servers
You're very welcome.
I'd be thankful if you marked my responses as 'helpful' or mark the question 'answered' ...
Live Chat, Watch Parties, and More!
Engage digitally throughout the sales process, from product discovery to conﬁguration, and handle all your post-purchase needs.