topic Re: Problem after ontap upgrade 7.32 - 7.351 in ONTAP Discussions

Problem after ontap upgrade 7.32 - 7.351

mhellberg — Thu, 05 Jun 2025 06:59:50 GMT

Hi All,

Was helping a customer with a ontap upgrade.

The installation went fine, no errors. Before the reboot,disk firmware etc. was upgraded.

I rebooted the system, waited 10 minutes but the system did´nt come back up.

Went down to the serverroom, connected thru serial and the system had stoped at the boot menu:

(1) Normal boot.

(2) Boot without /etc/rc.

(3) Change password.

(4) Initialize all disks.

No errros before that what i could see. i choosed nr:1 and the system booted fine.

So i run version:

NetApp Release 7.3.2: Thu Oct 15 04:17:39 PDT 2009

Still the old version?

If i run version -b:

1:/x86_elf/kernel/primary.krn: OS 7.3.5.1

Rebooted the filer again. Same problem. The boot menu first, then if choosing number one, the old version.

Any one got a clue?

Re: Problem after ontap upgrade 7.32 - 7.351

cobham_rich — Tue, 22 Feb 2011 11:19:02 GMT

Hi,

I am planning this same upgrade. Did you get a resolution to your problem, or anything I need to observe to avoid the same issue?

Thanks,

Rich.

Re: Problem after ontap upgrade 7.32 - 7.351

mhellberg — Tue, 22 Feb 2011 18:37:13 GMT

Hi,

No resolution, have opened a case with netapp but nothing yet...

Re: Problem after ontap upgrade 7.32 - 7.351

cobham_rich — Wed, 23 Feb 2011 08:36:32 GMT

I better make sure the RLM interface is up then as I'm doing mine remotley!! I'll let you know if it works or ends up the same.

Cheers.

Re: Problem after ontap upgrade 7.32 - 7.351

mhellberg — Wed, 23 Feb 2011 08:39:29 GMT

The sugestion from netapp was to run the software download command again.

I´ll going to try that in a couple of days.

Good luck!

Re: Problem after ontap upgrade 7.32 - 7.351

chriszurich — Wed, 23 Feb 2011 13:42:09 GMT

After the download command completed and upon reboot did you run "update_flash" from the Loader prompt?

Link to 7.3.5.1 upgrade guide. If step 11 is not executed the kernel will not be upgraded and the version command will always display the previous version.

https://now.netapp.com/NOW/knowledge/docs/ontap/rel7351/html/ontap/upgrade/frameset.html

Re: Problem after ontap upgrade 7.32 - 7.351

michelvankessel — Sun, 27 Feb 2011 09:50:03 GMT

I had this problem before. Just do the update again. Via RLM/CONSOLE that way you can observe the boot process Kind regards, Michel van Kessel

Re: Problem after ontap upgrade 7.32 - 7.351

scottgelb — Sun, 27 Feb 2011 19:26:42 GMT

has to be an enviroment option like autoboot... I would push the latest controller/diags (extract tar from now site, priv set advanced ; download -d, halt, update-flash, set-defaults, bye)... set-defaults should fix a change in the boot option that might be causing this...run by support too. If firmware/diags are all up to date, just do the set-defaults and bye to change the variables.

Re: Problem after ontap upgrade 7.32 - 7.351

thomas_glodde — Sun, 27 Feb 2011 21:16:47 GMT

set-defaults might reset your onboard target san ports to initiator, be careful.

Re: Problem after ontap upgrade 7.32 - 7.351

scottgelb — Sun, 27 Feb 2011 21:18:14 GMT

Without fcadmin config -t initiator, I have never seen that happen.

Typos Sent on Blackberry Wireless

Re: Problem after ontap upgrade 7.32 - 7.351

mhellberg — Mon, 28 Feb 2011 13:07:34 GMT

Hi,

I run the download command again and then halted the system.

The LOADER boot environment gives me the message: Warning: The CompactFlash contains newer firmware image..

I run update_flash and then bye.

The system boots to the same startmenu as before. When choosing "normal boot" , the system boots 7.32

Re: Problem after ontap upgrade 7.32 - 7.351

thomas_glodde — Mon, 28 Feb 2011 13:22:48 GMT

FAS3140 MetroCluster, i did NDU ontap update as well as update_flash, issued a set-defaults and my onboard 0b and 0d ports went to initiator again (as shipped from factory). had to offline them in maintenance mode and reset them to target.

offtopic: have you noticed that after a power outage filers wont boot up again although autoboot = true is configured??

Re: Problem after ontap upgrade 7.32 - 7.351

scottgelb — Mon, 28 Feb 2011 14:56:14 GMT

Never have seen that or heard of that.

Typos Sent on Blackberry Wireless

Re: Problem after ontap upgrade 7.32 - 7.351

michelvankessel — Mon, 28 Feb 2011 14:58:28 GMT

Which filer do you have? FAS31xx series? if that is true, you shouldn't HALT the filer, but REBOOT it. The FAS31xx series auto upgrade flash and ontap on reboot! Important is to follow the boot process via RLM or CONSOLE. It will show you any error messages I would execute the "software update" command again with the -r switch and then reboot the filer. hope it helps

Re: Problem after ontap upgrade 7.32 - 7.351

scottgelb — Mon, 28 Feb 2011 14:58:47 GMT

Did you printenv to check environment? Did you run set-defaults ?

Typos Sent on Blackberry Wireless

Re: Problem after ontap upgrade 7.32 - 7.351

mhellberg — Mon, 28 Feb 2011 16:43:27 GMT

Fas2040

Re: Problem after ontap upgrade 7.32 - 7.351

mhellberg — Mon, 28 Feb 2011 16:47:55 GMT

Was a little worried to run set-defaults, what exactly does it reset ?

Missed printenv, its on the checklist for next window.

Re: Problem after ontap upgrade 7.32 - 7.351

scottgelb — Mon, 28 Feb 2011 16:56:16 GMT

It resets the factory environment options. After set-defaults, you have to run bye to restart. You could also "printenv" on both controllers in a cluster and compare to the one that works...then see the environment options to modify "setenv" or remove "unsetenv" manually.

Thomas - For the fc ports...there is a note in the fcadmin admin page..looks like the wrong driver came up to cause the onboard fc ports change. If the logs show the ems error below, then that was the cause. I have never seen it but shows up on the man page, so others defintely have had it happen.

http://now.netapp.com/NOW/knowledge/docs/ontap/rel80/html/ontap/cmdref/man1/na_fcadmin.1.htm

Automatic Reconfiguration
Under some circumstances, the filer may boot with the wrong driver attached. When this happens the embedded adapters are reprogrammed to their proper type and state and the filer is automatically rebooted to attach the correct driver. Before rebooting, the fci.config.autoReboot EMS message displays on the console. Events that can cause this problem include maintenance head swaps, use of the console set-defaults command, and other operations that affect the filer's boot environment state.

Re: Problem after ontap upgrade 7.32 - 7.351

thomas_glodde — Mon, 28 Feb 2011 17:10:54 GMT

Scott, thanks for the info, yep, that was the case.

as for non-proper boot, customers sometimes experience an unplaned power outage so a fully clustered system gets completaly shutdown. upon boot, single heads as well as cluster nodes stay on LOADER prompt although printenv autoboot true, boot primary, whatever, everything fine on all nodes. its just that some boot, others doesnt.

or you have a planed maintenance, you "halt" the filers, mess around with power, then power them back on again (actualy using the real power switches, not some RLM stuff or just pulling cables, and some boot, some dont ; (

Re: Problem after ontap upgrade 7.32 - 7.351

michelvankessel — Mon, 28 Feb 2011 17:26:03 GMT

same for the FAS2040