shutdown and start up procedure for Netapp FAS6280

[ekashpureff]

Joseph -

For Shutdown:

Log on to a mgt LIF on the second node.

Do

'system node halt -node node1 -reason 'disaster coming' -inhibit-takeover true

Then

system node halt -node node2 -reason 'disaster coming'

Turn off controllers, disk shelves and switches.

Startup:

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/

[SURESMILE]

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.

Joseph

[ekashpureff]

Joseph -

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 ...

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/

[SURESMILE]

Eugene

Thanks for your response.

After reboot and FCP services restarted the luns became visible to the Vio servers

Thanks.

Joseph

[ekashpureff]

Joseph -

You're very welcome.

I'd be thankful if you marked my responses as 'helpful' or mark the question 'answered' ...

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/