also always best to update the firmware on the disks if it hasn't already been mentioned. This happens in the background, or you can do manually if you want. I was a wussy and did them manually as it states in BOLD could be disruptive on the firmware download page. I downloaded the whole zip or rar file and dumped in the proper location.. Its small and dosent take up much space... Should be ok..

Going straight to 8.1.. your a brave man.. Thanks for paving way@@!! flush those bugs out!!

From: andrey.borzenkov@ts.fujitsu.com To: fcocquyt@stanford.edu; chris@northlandusa.com Date: Wed, 1 Feb 2012 03:59:13 +0100 Subject: RE: NDU from 7.3.5.1P3 to 8.1RC2 with AT-FCX? CC: toasters@teaparty.net

AT-FCX FW update is non-disruptive if you update *from* v38 onward :) (there are some additional requirements). So if you would need to update *to* v38, it will be disruptive.

---

From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Wednesday, February 01, 2012 04:23 To: Chris Muellner Cc: 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] 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>

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

Hi,

we'll use VAAI, too (especially for cloning). I'm not sure, but i read that VAAI works with Ontap 8.01, so there is no reason for me to update to 8.1 (excepting Support for LTO4/5). It would be great if you report some 8.1 Bugs on the toaster list.

Thanks and greets

Steffen

Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Fletcher Cocquyt Gesendet: Mittwoch, 8. Februar 2012 20:06 An: steve klise Cc: toasters@teaparty.net Betreff: Re: NDU from 7.3.5.1P3 to 8.1RC2 completed

We completed the NDU upgrade last night without incident (100s of running VMs including Oracle did not log any issues)

Many thanks to those who provided feedback - with 8.1RC2 are enjoying VAAI in our vmware env and having data motion back.

I will write up some of the doc discrepancies / issues I found with the planning of the NDU

thanks

Fletcher

On Jan 31, 2012, at 8:33 PM, steve klise wrote:

also always best to update the firmware on the disks if it hasn't already been mentioned. This happens in the background, or you can do manually if you want. I was a wussy and did them manually as it states in BOLD could be disruptive on the firmware download page. I downloaded the whole zip or rar file and dumped in the proper location.. Its small and dosent take up much space... Should be ok..

Going straight to 8.1.. your a brave man.. Thanks for paving way@@!! flush those bugs out!!

From: andrey.borzenkov@ts.fujitsu.com To: fcocquyt@stanford.edu; chris@northlandusa.com Date: Wed, 1 Feb 2012 03:59:13 +0100 Subject: RE: NDU from 7.3.5.1P3 to 8.1RC2 with AT-FCX? CC: toasters@teaparty.net

AT-FCX FW update is non-disruptive if you update *from* v38 onward :)

(there are some additional requirements). So if you would need to update *to* v38, it will be disruptive.

---

From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On

Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu]

Sent: Wednesday, February 01, 2012 04:23 To: Chris Muellner Cc: 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] 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@teapa rty.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>

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters