OK, it was FW37 which introduced it; I had feeling FW38 was not correct :)
In this case this is the latest version.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Wednesday, February 01, 2012 5:51 AM To: Andrew Werchowiecki Cc: toasters@teaparty.net Subject: Re: NDU from 7.3.5.1P3 to 8.1RC2 with AT-FCX?
http://now.netapp.com/NOW/cgi-bin/shelffwdnld.cgi/download/tools/diskshelf/b... states
"The AT-FCX I/O module can be upgraded nondisruptively if the storage system meets either of these two configuration requirements:"
we have FW38, but what is CPLD v.24 - and how do I query my current rev?
[cid:image001.png@01CCE107.5F8341C0]
thanks
-- Fletcher
On Jan 31, 2012, at 5:43 PM, Andrew Werchowiecki wrote:
They will lose connectivity for, in my experience, at least 40 seconds during a firmware upgrade.
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Wednesday, 1 February 2012 8:24 AM To: Chris Muellner Cc: toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: NDU from 7.3.5.1P3 to 8.1RC2 with AT-FCX?
thanks - I'm reviewing the 8.1 (RC Aug 2011) upgrade guide - will the AT-FCX we have present a disruption to our NDU to 8.1RC2 plan? - ours show up in netapp auto support as fw.38
* You need to update firmware for AT-FC-based or AT-FC2-based disk shelves. ?? Client services might encounter delays accessing data when disk shelf firmware is updated to AT- FC or AT-FC2 modules. To prevent data loss, all session-oriented services must be terminated before you begin an update procedure. For these conditions, disruptive upgrades are recommended.
-- Fletcher
On Jan 31, 2012, at 3:49 PM, Chris Muellner wrote:
Sort of. Use
ifconfig na03-vif0-205 partner na04-vif0-205
instead. That will add the partner interface to the running config without messing with the IP address.
Is your hostname added to the interface twice as “`hostname`-na03-vif0-205” in the ifconfig makes it look? With that statement the host file would have an entry for an interface named na03-na03-vif0-205.
Also, note that in 8.x that vif has been deprecated to ifgrp instead so you’ll want to update your rc files accordingly after the upgrade, otherwise OnTap will complain about it when it boots. It’ll still honor the vif command however.
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu]mailto:[mailto:fcocquyt@stanford.edu] Sent: Tuesday, January 31, 2012 5:03 PM To: Chris Muellner Cc: toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: NDU from 7.3.5.1P3 to 8.1RC2 supported?
I found and corrected the typo in the rc file - now the check passes on the rc files, but not the running config. Is it safe/recommended to reissue the
ifconfig na03-vif0-205 `hostname`-na03-vif0-205 netmask 255.255.255.192 partner na04-vif0-205 up
to update the partner in the running config?
Or is there a better method?
thanks -- Fletcher
On Jan 31, 2012, at 2:48 PM, Chris Muellner wrote:
Verify the RC files on both controllers. You can ignore the c0x interfaces, but the tool is saying you’ll have an issue with this VIF here: NO PARTNER FOR na04-vif0-205 (17.25.104.23) ON na04 in /etc/rc
Make sure the ifconfig statement in both controllers RC files for that interface have the partner interface specified in the statement.
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]mailto:[mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Tuesday, January 31, 2012 1:01 PM To: SW Cc: toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: NDU from 7.3.5.1P3 to 8.1RC2 supported?
Thanks for the feedback Steve,
I'm also running the netapp tool to check HA prior to failover: Are these partner network errors valid? Someone in the community forums said they are bogus
./ha-config-check.cgi -s na03 na04 == NetApp HA Configuration Checker v2.0.0 ==
Checking ssh logins ...
Checking ssh logins ...
OK
Checking Data ONTAP versions...
OK
Checking licenses...
OK
Checking HA configuration identity...
OK
Checking cf status...
OK
Checking fcp cfmode settings...
fcp: FCP is not licensed. N/A
Checking options...
OK
Checking network configuration...
c0a (192.168.1.152) on na03 does not have a partner on na04 c0b (192.168.2.173) on na03 does not have a partner on na04 c0a (192.168.1.84) on na04 does not have a partner on na03 c0b (192.168.2.95) on na04 does not have a partner on na03 na04-vif0-205 (17.25.104.11) on na04 does not have a partner on na03
Checking network config in /etc/rc
NO PARTNER FOR na04-vif0-205 (17.25.104.23) ON na04 in /etc/rc HA configuration issue(s) found above. Please correct them and rerun this script. Done.
-- Fletcher
On Jan 31, 2012, at 10:29 AM, SW wrote:
Hi Fletcher,
I only have a subset of answers relating to your Toasters inquiry, but I thought I’d share what I can...
According to the upgrade guide for 8.1RC2 (attached to this e-mail), a NDU from 7.3.5.1P3 to 8.1RC2 is supported:
From page 15:
“Nondisruptive upgrades to releases in the Data ONTAP 8.1 7-Mode release family are supported from the following releases: • Any 8.0.x release • 7.3.2 and later 7.3.x releases”
Good luck! Steve <upgrade.pdf>
