Here I am going to discuss on how to do a ontap upgrade for cluster mode with the steps.
Run the upgrade advisor from the Suppport.netapp.com site and you will get the document with the steps and caution points. Here, I would be discussing with the logs on how to do the firmware upgrade for Cdot clusters. Please note here I’m doing the firmware upgrade from 8.3.1p1 to 8.3.1p2.
Note: On cluster modes we do no have option to copy paste the ontap image to the software folder which we used to do in 7 mode, we will have to user either FTP or HTTP to copy the firmware to the filers. Here im doing a FTP from from my FTP server //10.xx.xx.xx as below.
filer1::> system image update -node * -package ftp://10.xx.xx.xx/831P2_q_image.tgz -replace image2
The below command checks for the current version of the SP firmwawre installed on the cluster.
While we upgrade the ontap we will also do the SP firmware.
filer1::> system service-preprocessor show
IP Firmware
Node Type Status Configured Version IP Address
————- —- ———– ———— ——— ————————-
filer1-01 SP online true 2.3.1 x.x.x.1
filer1-02 SP online true 2.3.1 x.x.x.2
2 entries were displayed.
filer1::>
The Below command checks for the current image of the ontap installed on the filer.
We could see that we have already done a FTP of the Image to the filer and its shows a default image false, which means that it will not be in effect even after reboot of the nodes.
filer1::> system image show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
filer1-01
image1 false false 8.3.1P2 9/20/2016 23:57:58
image2 true true 8.3.1P1 7/20/2016 05:55:34
filer1-02
image1 false false 8.3.1P2 6/9/2016 00:05:42
image2 true true 8.3.1P1 7/20/2016 05:56:26
4 entries were displayed.
The below command will modify the default version to the newly added image for node 1 and then to node 2 respectively.
filer1::> system image modify -node filer1-01 -image image1 -isdefault true
After a clean shutdown, image1 will be set as the default boot image on node filer1-01.
filer1::> system image modify -node filer1-02 -image image1 -isdefault true
After a clean shutdown, image1 will be set as the default boot image on node filer1-02.
filer1::> system image show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
filer1-01
image1 true false 8.3.1P2 9/20/2016 23:57:58
image2 true true 8.3.1P1 7/20/2016 05:55:34
filer1-02
image1 true false 8.3.1P2 6/9/2016 00:05:42
image2 true true 8.3.1P1 7/20/2016 05:56:26
filer1::> storage failover takeover -ofnode filer1-01
The above command will reboot node01 of the cluster( rebooting node 1).
Warning: A takeover will be initiated. Once the partner node reboots, a giveback will be automatically initiated. Do you want to continue? {y|n}: y
filer1::> storage failover show ( Checks the current storage failover status)
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 – Waiting for giveback
filer1-02 filer1-01 false In takeover, Auto giveback will be
initiated in 367 seconds
2 entries were displayed.
filer1::> storage failover giveback -ofnode filer1-01
Info: Run the storage failover show-giveback command to check giveback status.
filer1::> strorage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02. Waiting
for cluster applications to come
online on the local node. Offline
applications: vifmgr, vldb, bcomd,
crs.
filer1-02 filer1-01 true Connected to filer1-01, Partial
giveback
2 entries were displayed.
filer1::> system image show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
filer1-01
image1 true true 8.3.1P2 9/20/2016 23:57:58
image2 false false 8.3.1P1 7/20/2016 05:55:34
filer1-02
image1 true false 8.3.1P2 6/9/2016 00:05:42
image2 false true 8.3.1P1 7/20/2016 05:56:26
we could see the ontap 8.3.1P2 is applied for node1.
filer1::> storage faiolover takeover -ofnode filer1-02
Warning: A takeover will be initiated. Once the partner node reboots, a giveback will be automatically initiated. Do you want to continue? {y|n}: y
filer1::> storage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 false In takeover, Auto giveback will be
initiated in 404 seconds
filer1-02 filer1-01 – Waiting for giveback
2 entries were displayed.
filer1::> storage failover giveback -ofnode filer1-02
Info: Run the storage failover show-giveback command to check giveback status.
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Partial
giveback
filer1-02 filer1-01 true Connected to filer1-01. Waiting
for cluster applications to come
online on the local node. Offline
applications: vifmgr, vldb, bcomd,
crs.
2 entries were displayed.
filer1::> storage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Partial
giveback
filer1-02 filer1-01 true Connected to filer1-01. Waiting
for cluster applications to come
online on the local node.
2 entries were displayed.
filer1::> storage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Giveback
of one or more SFO aggregates failed
filer1-02 filer1-01 true Connected to filer1-01
2 entries were displayed.
filer1::> storage failover showgiveback -ofnode filer1-02
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Giveback
of one or more SFO aggregates failed
filer1-02 filer1-01 true Connected to filer1-01
2 entries were displayed.
filer1::> storage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Giveback
of one or more SFO aggregates failed
filer1-02 filer1-01 true Connected to filer1-01
2 entries were displayed.
filer1::> version
NetApp Release 8.3.1P2: Wed Dec 09 03:10:24 UTC 2015
filer1::> system image show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
filer1-01
image1 true true 8.3.1P2 9/20/2016 23:57:58
image2 false false 8.3.1P1 7/20/2016 05:55:34
filer1-02
image1 true true 8.3.1P2 6/9/2016 00:05:42
image2 false false 8.3.1P1 7/20/2016 05:56:26
4 entries were displayed.
filer1::> storage failover show -node filer1-02
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02, Giveback
of one or more SFO aggregates failed
filer1-02 filer1-01 true Connected to filer1-01
2 entries were displayed.
filer1::storage failover> show-giveback -node filer1-02
Partner
Node Aggregate Giveback Status
————– —————– ———————————————
filer1-01
CFO Aggregates Done
filer1_02_sas_ag01
Failed: Operation was vetoed by
lock_manager. Giveback vetoed: Giveback
cannot proceed because non-continuously
available (non-CA) CIFS locks are present on
the volume. Gracefully close the CIFS
sessions over which non-CA locks are
established. Use the “vserver cifs session
file show -hosting-aggregate <aggregate
list> -continuously-available No” command to
view the open files that have CIFS sessions
with non-CA locks established. <aggregate
list> is the list of aggregates sent home as
a result of the giveback operation. If lock
state disruption for all existing non-CA
locks is acceptable, retry the giveback
operation by specifying “-override-vetoes
true”. Warning: Overriding vetoes to
perform a giveback can be disruptive.
2 entries were displayed.
This is one of the most command issues we face when we do a ontap upgrade, this could be possibly be because the cifs sessions were active during the ontap upgrade.
we can override this by giving the below mentioned command.
filer1::> storage failover giveback -ofnode filer1-02 -override-vetoes true
Warning: Initiating a giveback with vetoes overridden will result in giveback proceeding even if the node detects outstanding issues that would make a giveback dangerous
or disruptive. Do you want to continue? {y|n}: y
Info: Run the storage failover show-giveback command to check giveback status.
filer1::> storage failover show
Takeover
Node Partner Possible State Description
————– ————– ——– ————————————-
filer1-01 filer1-02 true Connected to filer1-02
filer1-02 filer1-01 true Connected to filer1-01
2 entries were displayed.
filer1::> system image show
Is Is Install
Node Default Current Version Date
——– ——- ——- ——- ————————- ——————-
filer1-01
image1 true true 8.3.1P2 9/20/2016 23:57:58
image2 false false 8.3.1P1 7/20/2016 05:55:34
filer1-02
image1 true true 8.3.1P2 6/9/2016 00:05:42
image2 false false 8.3.1P1 7/20/2016 05:56:26
with the above command we could see that the firmware is applied as 8.3.1P2 which is highlighted as default version true, and this completes the upgrade, let me know if you have any questions and comments.
SAN bits 