The _netboot files are used for restoring ONTAP under rare situations, and 'noDARE' (for 'no Data At Rest Encryption') is only needed for some nations which may ban encryption or which encryption technologies may not be exported to.
It is necessary to modify failover back on if it has been turned off, but the correct command to actually perform the giveback in the situation where CIFS sessions are open is:
Regarding "It is necessary to modify failover back on". I was told by support when they were onsite setting up our device to have the option turned off just so that when a controller goes bad, you don't want it to attempt to go back online. Anyways, how would I see what the configuration is set?
When we attempted using the cli to get info regarding the open cifs sessions, the command below doesn't work. It doesn't know what the session ID is ( after issuing vserver cifs session show -continuously-available !Yes -instance). We later used a combination of MMC (Microsoft console).
vserver cifs session file show -session-id session_ID
Anyways, we decided to shutdown the CIFS services to end all sessions but restarted back on right after the upgrade. Would it be fine if we had left the CIFS service at a stopped state and perform the upgrade?
Fine to turn off CIFS for the duration of the upgrade.
To show failover status, run "storage failover show". It's an almost religious debate if it should be on or not. Our current recommendation is to turn it on. There is code to detect multiple failures and not giveback if it has been flipping back and forth.