I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
Step 3.5 perform a download from the console.
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Brent Ellis Sent: Thursday, March 08, 2007 9:49 AM To: toasters@mathworks.com Subject: Upgrading Data OnTap
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
Personally, I would:
copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer.
Then from the console of each filer:
options raid.background_disk_fw_update.enable off (turns off auto updating of disk firmware) software install filename (the filename from above)
While at it, get and extract the latest all.zip and all_fw.zip files (disk and shelf FW) into the /etc dir on each filer.
Optionally, with cluster still enabled, run disk_fw_update to update all disk firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. storage download shelf to update shelf firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. options raid.background_disk_fw_update.enable on (turns the auto updating of disk firmware back on)
When these are both finished, run download on both heads. Verify with "version -b" to make sure you have the correct ONTAP on the flash card
Lastly, disable cluster:
cf disable
Reboot each head, one at a time. You will see errors on each about ONTAP version mismatches. They will be corrected when both heads have the same/similar versions.
There are also notes about a Non-Disruptive upgrade on NOW Since you are using CIFS, this is basically impossible right now due to the statefulness of the protocol.
This method here will give you a single outage on each head, likely less than 2 minutes each.
If you decide not to do the disk/shelf firmware before reboot, it could add up to 10 or 15 minutes while it completes.
--tmac
Regarding the disk_fw_update: If you have RAID_DP, it may be doing one disk at a time. That is fine. I will On 3/8/07, Brent Ellis interi@bu.edu wrote:
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
- disable the cluster
- mount the c$ share as a drive
- run the 7.1.2 installer
- reboot
- repeat with the other cluster partner
- enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
On 3/8/07, tmac tmacmd@gmail.com wrote:
Personally, I would:
copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer.
Then from the console of each filer:
options raid.background_disk_fw_update.enable off (turns off auto updating of disk firmware) software install filename (the filename from above)
While at it, get and extract the latest all.zip and all_fw.zip files (disk and shelf FW) into the /etc dir on each filer.
Optionally, with cluster still enabled, run disk_fw_update to update all disk firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. storage download shelf to update shelf firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. options raid.background_disk_fw_update.enable on (turns the auto updating of disk firmware back on)
I'm preparing to do a NDU 7.0 -> 7.1 and was wondering: When you do the storage download shelf on one head, will it update the firmware on both the A-loop and B-loop ?
I would expect not, since one head is only connected to one loop in a plain cluster config. AFAIK, downloading shelf firmware takes a quiesce of a loop and a controller reboot, and my customer really would like to have a functional system during this NDU.
Greets,
Nils
Actually, it downloads the FW to the shelf, then the shelf will copy it to both ESH or LRC or whatever modules.
So, yes, even in a cluster, upgrading the shelf firmware from one head should take care of all shelves...as long as that one head can see all the shelves on at least one loop.
--tmac
On 3/9/07, Nils Vogels bacardicoke@gmail.com wrote:
On 3/8/07, tmac tmacmd@gmail.com wrote:
Personally, I would:
copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer.
Then from the console of each filer:
options raid.background_disk_fw_update.enable off (turns off auto updating of disk firmware) software install filename (the filename from above)
While at it, get and extract the latest all.zip and all_fw.zip files (disk and shelf FW) into the /etc dir on each filer.
Optionally, with cluster still enabled, run disk_fw_update to update all disk firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. storage download shelf to update shelf firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. options raid.background_disk_fw_update.enable on (turns the auto updating of disk firmware back on)
I'm preparing to do a NDU 7.0 -> 7.1 and was wondering: When you do the storage download shelf on one head, will it update the firmware on both the A-loop and B-loop ?
I would expect not, since one head is only connected to one loop in a plain cluster config. AFAIK, downloading shelf firmware takes a quiesce of a loop and a controller reboot, and my customer really would like to have a functional system during this NDU.
Greets,
Nils
-- Simple guidelines to happiness: Work like you don't need the money, Love like your heart has never been broken and Dance like no one can see you.
on the fibre channel drive shelves it updates the firmware on both the a/b loop. if you run the shelf firmware updater on one side of the cluster you do not need to do it on the other side. it is also non disruptive and does not interfere with data access.
on the SATA shelves it is disruptive, the download command will tell you if it is disruptive or not before you proceed.
-- Daniel Leeds Senior Systems Administrator Edmunds.com
-----Original Message----- From: owner-toasters@mathworks.com on behalf of Nils Vogels Sent: Fri 3/9/2007 12:45 AM To: tmac Cc: toasters@mathworks.com Subject: Re: Upgrading Data OnTap
On 3/8/07, tmac tmacmd@gmail.com wrote:
Personally, I would:
copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer.
Then from the console of each filer:
options raid.background_disk_fw_update.enable off (turns off auto updating of disk firmware) software install filename (the filename from above)
While at it, get and extract the latest all.zip and all_fw.zip files (disk and shelf FW) into the /etc dir on each filer.
Optionally, with cluster still enabled, run disk_fw_update to update all disk firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. storage download shelf to update shelf firmware (lessens downtime at reboot) usually only needed on one head. When complete, run on other head to be sure. options raid.background_disk_fw_update.enable on (turns the auto updating of disk firmware back on)
I'm preparing to do a NDU 7.0 -> 7.1 and was wondering: When you do the storage download shelf on one head, will it update the firmware on both the A-loop and B-loop ?
I would expect not, since one head is only connected to one loop in a plain cluster config. AFAIK, downloading shelf firmware takes a quiesce of a loop and a controller reboot, and my customer really would like to have a functional system during this NDU.
Greets,
Nils
Thanks for everyone's responses, it sounds like the really important thing I was missing was the download part. I may setup a web folder with upgrades however to facilitate this process in the future. The main thing I was worried about is that my configuration will be the same after I am done upgrading.
If anyone is curious, I am upgrading because while we were testing Wista we found that name resolution doesn't work to access the filer for the version of Data Ontap we have installed. According to the NOW website this problem was fixed in subsequent 7.1.x releases.
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
On Mar 8, 2007, at 11:49 AM, Brent Ellis wrote:
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
- disable the cluster
- mount the c$ share as a drive
- run the 7.1.2 installer
- reboot
- repeat with the other cluster partner
- enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
I have had a couple of occasions in the past (though not recently) where some of my configuration options were changed after an upgrade. As long as you have valid snapshots of your vol0 volume available, you can refer back to them to check and compare old versions of config files vs new if something has unexpectedly changed.
If you're going to do a web folder, then instead of mapping a CIFS share, etc. you might find it easier to do filer> software install http://mywebserver.bu.edu/folder/712setup.exe
You might need a -f at the end if there's already an ONTAP archive with the same name.
This tells the fielr to pull the upgrade from your server, put it in /etc/software, and extract the files into their homes in /etc.
Then download etc.
Share and enjoy!
Peter
________________________________
From: Brent Ellis [mailto:interi@bu.edu] Sent: Thursday, March 08, 2007 10:26 AM To: Brent Ellis Cc: toasters@mathworks.com Subject: Re: Upgrading Data OnTap
Thanks for everyone's responses, it sounds like the really important thing I was missing was the download part. I may setup a web folder with upgrades however to facilitate this process in the future. The main thing I was worried about is that my configuration will be the same after I am done upgrading.
If anyone is curious, I am upgrading because while we were testing Wista we found that name resolution doesn't work to access the filer for the version of Data Ontap we have installed. According to the NOW website this problem was fixed in subsequent 7.1.x releases.
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
On Mar 8, 2007, at 11:49 AM, Brent Ellis wrote:
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
Use this link as a guide...
http://now.netapp.com/NOW/knowledge/docs/ontap/rel712/html/ontap/upgrade /4ug_sw.htm
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Brent Ellis Sent: Thursday, March 08, 2007 1:26 PM To: Brent Ellis Cc: toasters@mathworks.com Subject: Re: Upgrading Data OnTap
Thanks for everyone's responses, it sounds like the really important thing I was missing was the download part. I may setup a web folder with upgrades however to facilitate this process in the future. The main thing I was worried about is that my configuration will be the same after I am done upgrading.
If anyone is curious, I am upgrading because while we were testing Wista we found that name resolution doesn't work to access the filer for the version of Data Ontap we have installed. According to the NOW website this problem was fixed in subsequent 7.1.x releases.
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
On Mar 8, 2007, at 11:49 AM, Brent Ellis wrote:
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
Also, if your system has a support contract and sends regular ASUPs to NetApp, you can open a case and request an filer upgrade plan. They can generate one based on your filer's config.
-- Adam Fox adamfox@netapp.com
________________________________
From: owner-dl-toasters@jhereg.corp.netapp.com [mailto:owner-dl-toasters@jhereg.corp.netapp.com] On Behalf Of Parisi, Justin Sent: Thursday, March 08, 2007 2:40 PM To: Brent Ellis Cc: toasters@mathworks.com Subject: RE: Upgrading Data OnTap
Use this link as a guide...
http://now.netapp.com/NOW/knowledge/docs/ontap/rel712/html/ontap/upgrade /4ug_sw.htm
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Brent Ellis Sent: Thursday, March 08, 2007 1:26 PM To: Brent Ellis Cc: toasters@mathworks.com Subject: Re: Upgrading Data OnTap
Thanks for everyone's responses, it sounds like the really important thing I was missing was the download part. I may setup a web folder with upgrades however to facilitate this process in the future. The main thing I was worried about is that my configuration will be the same after I am done upgrading.
If anyone is curious, I am upgrading because while we were testing Wista we found that name resolution doesn't work to access the filer for the version of Data Ontap we have installed. According to the NOW website this problem was fixed in subsequent 7.1.x releases.
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
On Mar 8, 2007, at 11:49 AM, Brent Ellis wrote:
I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write.
I plan on doing the following:
1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster.
Does that sound right? It seems a little to easy to me
Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu
-
Brent Ellis -
Fox, Adam -
Learmonth, Peter -
Leeds, Daniel -
Nils Vogels -
Parisi, Justin -
Sphar, Mike -
tmac -
Wilkinson, Brent