Home » Networking » Backup and Storage » [solved] how to upgrade the code and perform a NETAPP controller fail over step by step

[solved] how to upgrade the code and perform a NETAPP controller fail over step by step

How to upgrade the NETAPP code and perform a NETAPP controller fail over step by step.

Few things you will need to consider  before you are ready to update the code and performing fail over to reduce downtime during the NETAPP code upgrade.

The code can be uploaded to the NetApp by using http. you can you software called “mangoose” to host http connection.

1. login and set the privileged level 

test_san::> set advanced

Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y

2. turn off the automatic failover 

test_san::*> storage failover modify -node * -auto-giveback false

Warning: Disabling auto-giveback under cluster HA configuration will prevent the management cluster services from automatically going
online under alternating-failure scenarios. Do you want to disable auto-giveback? {y|n}: y
2 entries were modified.

3. download the software code by specifying the host which is running  an http server:

test_san::*> 96P5_q_image.tgz system node image update -node * -package http://x.x.x.x:8080/96P5_q_image.tgz -setdefault true -replace-package true

Warning: The recommended best-practice is to use the automated non-disruptive update procedure if you are attempting an upgrade or a
minor version downgrade. Refer to the Clustered Data ONTAP Upgrade and Revert/Downgrade Guide for details.
Do you want to continue? {y|n}: y

Software update started on node test_san1. Updating image2 with package http://…/96P5_q_image.tgz.
Downloading package. This may take up to 10 minutes.
3% downloaded
6% downloaded

4.  Once the upload is complete you will see the following message

Boot recovery files installed on recovery partition
Installation complete. image2 updated on node test_san-02.
After a clean shutdown, image2 will be set as the default boot image on node
test_san- 02.
2 entries were acted on.

At this point dynamic fail over is set to false and now we can check what interfaces needs to be re-homed

Leave a Reply

Your email address will not be published. Required fields are marked *