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.