Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
Romeo,
In general, when I perform head upgrades and am going to different processor family, I perform a tftp boot to the latest version of OnTap for the new controller that is being installed. I then immediately perform a software upgrade of that same OnTap version so it is on the disks and flash card. This leaves no doubt that when the system boots up normally that it will have the correct OS for the correct controller. It may seem like extra unnecessary steps but the customers that I support expect this level of service and affirmation that the job is done correctly.
Regards, Andre M. Clark
On 4/30/09 8:42 AM, "Romeo Theriault" romeotheriault@gmail.com wrote:
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
Thanks for the note, I'll keep it for future reference. Also, I don't mind the extra steps, I'd just like it to be documented so people can do it correctly.
On Thu, Apr 30, 2009 at 10:14 PM, André M. Clark Andre.Clark@earthlink.netwrote:
Romeo,
In general, when I perform head upgrades and am going to different processor family, I perform a tftp boot to the latest version of OnTap for the new controller that is being installed. I then immediately perform a software upgrade of that same OnTap version so it is on the disks and flash card. This leaves no doubt that when the system boots up normally that it will have the correct OS for the correct controller. It may seem like extra unnecessary steps but the customers that I support expect this level of service and affirmation that the job is done correctly.
Regards, Andre M. Clark
On 4/30/09 8:42 AM, "Romeo Theriault" romeotheriault@gmail.com wrote:
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
I had a similar problem when I upgraded a 960 to a 3040. I didn't see the info in the OnTap download matrix that showed the heads required a different build version. It was there, just not obvious. Never had any problems other than lots of the mapfile log entries. Once I loaded the correct version (q or e versus m, I also have a 3020) all was well.
Mike Miller Site Lead General Dynamics Information Technology mailto:Michael.Miller.ctr@ustranscom.mil Michael.Miller.ctr@ustranscom.mil mailto:Michael.Miller@gdit.com Michael.Miller@gdit.com
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Romeo Theriault Sent: Thursday, April 30, 2009 7:43 AM To: toasters@mathworks.com Subject: Warning for people doing a head upgrade from a 3050 to a 3170
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
Thanks for the note. It's good to know that you didn't have any kernel panics or such. I'll have to take a look at the OnTap download matrix. But if anyone at Netapp is listening this, the doc that could really could use the updating to say something about this is:
http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS3xx...
This doc is called "Upgrading from a FAS3020 or FAS3050 System in an Active/Active Configuration to a FAS31xx System in an Active/Active Configuration" so you would think that is would say something about this wouldn't you?
Romeo
On Thu, Apr 30, 2009 at 10:28 PM, Miller, Michael CTR USTRANSCOM J2 < michael.miller.ctr@ustranscom.mil> wrote:
I had a similar problem when I upgraded a 960 to a 3040. I didn’t see the info in the OnTap download matrix that showed the heads required a different build version. It was there, just not obvious. Never had any problems other than lots of the mapfile log entries. Once I loaded the correct version (q or e versus m, I also have a 3020) all was well.
Mike Miller Site Lead General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com
*From:* owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] *On Behalf Of *Romeo Theriault *Sent:* Thursday, April 30, 2009 7:43 AM *To:* toasters@mathworks.com *Subject:* Warning for people doing a head upgrade from a 3050 to a 3170
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
-- Romeo Theriault System Administrator Information Technology Services
Hi Romeo
You'll also see this error with a filer that has been flattened and reloaded using special boot 4/4a or netbooted to a new version without extracting the full ONTAP bundle. I've had systems run for months this way and not care - you just get the annoy-o-gram.
I've fwded your message to our doc comments DL. (Yes, we listen to Toasters!)
Enjoy!
Peter
________________________________
From: Romeo Theriault [mailto:romeotheriault@gmail.com] Sent: Thursday, April 30, 2009 6:56 AM To: Miller, Michael CTR USTRANSCOM J2; toasters@mathworks.com Subject: Re: Warning for people doing a head upgrade from a 3050 to a 3170
Thanks for the note. It's good to know that you didn't have any kernel panics or such. I'll have to take a look at the OnTap download matrix. But if anyone at Netapp is listening this, the doc that could really could use the updating to say something about this is:
http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FA S3xxx/FAS3020_FAS3050_to_FAS31xx_active.htm
This doc is called "Upgrading from a FAS3020 or FAS3050 System in an Active/Active Configuration to a FAS31xx System in an Active/Active Configuration" so you would think that is would say something about this wouldn't you?
Romeo
On Thu, Apr 30, 2009 at 10:28 PM, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I had a similar problem when I upgraded a 960 to a 3040. I didn't see the info in the OnTap download matrix that showed the heads required a different build version. It was there, just not obvious. Never had any problems other than lots of the mapfile log entries. Once I loaded the correct version (q or e versus m, I also have a 3020) all was well.
Mike Miller Site Lead General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil mailto:Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com mailto:Michael.Miller@gdit.com
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Romeo Theriault Sent: Thursday, April 30, 2009 7:43 AM To: toasters@mathworks.com Subject: Warning for people doing a head upgrade from a 3050 to a 3170
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's. So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog: na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed. -- Romeo Theriault System Administrator Information Technology Services
Thanks for the info and the forward to the docs team.
On Thu, Apr 30, 2009 at 11:15 PM, Learmonth, Peter < Peter.Learmonth@netapp.com> wrote:
Hi Romeo
You'll also see this error with a filer that has been flattened and reloaded using special boot 4/4a or netbooted to a new version without extracting the full ONTAP bundle. I've had systems run for months this way and not care - you just get the annoy-o-gram.
I've fwded your message to our doc comments DL. (Yes, we listen to Toasters!)
Enjoy!
Peter
*From:* Romeo Theriault [mailto:romeotheriault@gmail.com] *Sent:* Thursday, April 30, 2009 6:56 AM *To:* Miller, Michael CTR USTRANSCOM J2; toasters@mathworks.com *Subject:* Re: Warning for people doing a head upgrade from a 3050 to a 3170
Thanks for the note. It's good to know that you didn't have any kernel panics or such. I'll have to take a look at the OnTap download matrix. But if anyone at Netapp is listening this, the doc that could really could use the updating to say something about this is:
http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS3xx...
This doc is called "Upgrading from a FAS3020 or FAS3050 System in an Active/Active Configuration to a FAS31xx System in an Active/Active Configuration" so you would think that is would say something about this wouldn't you?
Romeo
On Thu, Apr 30, 2009 at 10:28 PM, Miller, Michael CTR USTRANSCOM J2 < michael.miller.ctr@ustranscom.mil> wrote:
I had a similar problem when I upgraded a 960 to a 3040. I didn’t see the info in the OnTap download matrix that showed the heads required a different build version. It was there, just not obvious. Never had any problems other than lots of the mapfile log entries. Once I loaded the correct version (q or e versus m, I also have a 3020) all was well.
Mike Miller Site Lead General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com
*From:* owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] *On Behalf Of *Romeo Theriault *Sent:* Thursday, April 30, 2009 7:43 AM *To:* toasters@mathworks.com *Subject:* Warning for people doing a head upgrade from a 3050 to a 3170
Here is a warning for people that might be doing a head upgrade from a 3050 to a 3170 (and possibly other heads). The documentation states that you need to bring the 3050 heads up-to the same software level as the 3170 heads. This may very well be the case but they fail to mention that the 3170 uses a different build of OnTap and that you need to upgrade OnTap on the 3170's immediately after the upgrade with the build for the 3170's.
So right now we are running 3170's with a build of OnTap 7.2.6.1 built for the 3050's and getting these errors in syslog:
na1-u-e0a [na1-u: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.6.1.2O: No such file or directory
Netapp Supports response is: "Upgrade or you'll probably get Kernel Panics." and "We'll try to update the documentation." Needless to say I'm not impressed.
-- Romeo Theriault System Administrator Information Technology Services
-- Romeo Theriault System Administrator Information Technology Services