toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

Re: clarification about reboots during NDU
by Fletcher Cocquyt 03 Feb '12

03 Feb '12

Justin, thanks for the feedback What makes step 13 (cf giveback) triggering another reboot of the SAME node A is step 12 reads like that has already been accomplished for node A so does node A reboot twice, then when you repeat the procedure, node B reboots twice? thanks -- Fletcher On Feb 2, 2012, at 11:20 AM, Parisi, Justin wrote: > In a takeover/giveback scenario, there are two reboots. > > The first reboot is the takeover. The second reboot is the giveback. > > From: toasters-bounces(a)teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt > Sent: Thursday, February 02, 2012 1:52 PM > To: toasters(a)teaparty.net > Subject: clarification about reboots during NDU > > Hi - can someone clarify this from pg 56 of the upgrade guide - > > for instance, if step 12 causes A to "reboot the system using the new firmware and software" > > WHY in step 13 does the cf giveback ALSO "cause system A to reboot with the new system configuration?" > > Are there really 2 reboots ? > > thanks > > > 12. Enter the following command to reboot the system using the new firmware and software: > > bye > > 13. Choose the option that describes your configuration. > > <image001.png> > <image002.png> > If FCP or iSCSI... > > Is not in use in system A > > Is in use in system A > > Then when the "Waiting for giveback" message appears on the console of system A... > > Enter the following command at the console of system B: > > cf giveback > > Wait for at least eight minutes to allow host multipathing software to stabilize, then enter the following command at the console of system B: > > cf giveback > > <image001.png> > <image002.png> > <image001.png> > <image002.png> > <image001.png> > <image002.png> > Attention: The cf giveback command can fail because of open client sessions (such as CIFS sessions), long-running operations, or operations that cannot be restarted (such as tape backup or SyncMirror resynchronization). If the cf givebackcommand fails, terminate any CIFS session or long-running operations gracefully (because the -f option will immediately terminate any CIFS sessions or long-running operations) and then enter the following command (with the -f option): > > cf giveback -f > For more information about the behavior of the -f option, see the cf(1) man page. > > The command causes system A to reboot with the new system configuration—a Data ONTAP version and any new system firmware and hardware changes—and resume normal operation as a high-availability partner. > > -- > Fletcher Cocquyt > Principal Engineer > Information Resources and Technology (IRT) > Stanford University School of Medicine > <image003.jpg> > > Email: fcocquyt(a)stanford.edu > Phone: (650) 724-7485 > > > >

5 8

clarification about reboots during NDU
by Fletcher Cocquyt 02 Feb '12

02 Feb '12

Hi - can someone clarify this from pg 56 of the upgrade guide - for instance, if step 12 causes A to "reboot the system using the new firmware and software" WHY in step 13 does the cf giveback ALSO "cause system A to reboot with the new system configuration?" Are there really 2 reboots ? thanks 12. Enter the following command to reboot the system using the new firmware and software: bye 13. Choose the option that describes your configuration. If FCP or iSCSI... Is not in use in system A Is in use in system A Then when the "Waiting for giveback" message appears on the console of system A... Enter the following command at the console of system B: cf giveback Wait for at least eight minutes to allow host multipathing software to stabilize, then enter the following command at the console of system B: cf giveback Attention: The cf giveback command can fail because of open client sessions (such as CIFS sessions), long-running operations, or operations that cannot be restarted (such as tape backup or SyncMirror resynchronization). If the cf giveback command fails, terminate any CIFS session or long-running operations gracefully (because the -f option will immediately terminate any CIFS sessions or long-running operations) and then enter the following command (with the -f option): cf giveback -f For more information about the behavior of the -f option, see the cf(1) man page. The command causes system A to reboot with the new system configuration—a Data ONTAP version and any new system firmware and hardware changes—and resume normal operation as a high-availability partner. -- Fletcher Cocquyt Principal Engineer Information Resources and Technology (IRT) Stanford University School of Medicine Email: fcocquyt(a)stanford.edu Phone: (650) 724-7485

2 1

NetApp recommends upgrading disk firmware the day before upgrading Data ONTAP
by Fletcher Cocquyt 02 Feb '12

02 Feb '12

I have downloaded the X410_HVIPC288A15 firmware - is this one truly non-disruptive? The online docs seem overly verbose - what is the short user test version for applying the disk firmware prior to 7.3.5.1P2->8.1RC2 NDU? thanks Upgrade These 96 disks will have firmware updates if the latest disk firmware is loaded on the filer: 96 disks of Model X410_HVIPC288A15. This firmware is not included in 8.1RC2 and must be downloaded separately. When performing a nondisruptive upgrade, NetApp recommends upgrading disk firmware the day before upgrading Data ONTAP. -- Fletcher

2 1

7.3.5.1P2 -> 8.1RC2 NDU - update_flash needed?
by Fletcher Cocquyt 02 Feb '12

02 Feb '12

pg 55 - upgrade guide says to check for this warning and do an 'update_flash' manually - how do I tell AHEAD of time if I need to do this for my 7.3.5.1P2 -> 8.1RC2 NDU plan? After halting the node, check the Boot Loader messages for a warning similar to the following: Warning: The CompactFlash contains newer firmware image (1.6.0). Please run 'update_flash' at Loader prompt to update your system firmware (1.5X3). If you... Do not see this warning. then.. BIOS firmware is updated automatically if needed; go to Step 12. thanks -- Fletcher

2 1

download process for Data ONTAP 8..x usually takes 20 to 60 minutes
by Fletcher Cocquyt 02 Feb '12

02 Feb '12

from pg 54 of the NDU guide: Note: Activating Data ONTAP 8..x software images with the download process takes significantly longer than in earlier releases. The download process for Data ONTAP 8..x usually takes 20 to 60 minutes. Q: Is it safe to issue the download command a few days ahead of the planned maintenance window (to save time in the actual maintenance window?) thanks -- Fletcher Cocquyt Principal Engineer Information Resources and Technology (IRT) Stanford University School of Medicine Email: fcocquyt(a)stanford.edu Phone: (650) 724-7485

3 2

Service Processor / syslog
by Stuart Kendrick 01 Feb '12

01 Feb '12

Is there a way to configure the Service Processor to log via syslog? I like solving problems using syslog ... for forensics, I want to see each box logging its view of the incident as it unfolds ... yeah, precise time-stamping is an issue ... but still, the basic flow works well, and I can build a picture of what happened via the resulting correlation between various devices. But it seems like the SP can only log via e-mail (and only intermittently at that) http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/sysadmin/G… ? --sk Stuart Kendrick FHCRC

2 2

NDU from 7.3.5.1P3 to 8.1RC2 supported?
by Fletcher Cocquyt 01 Feb '12

01 Feb '12

Hi, Is NDU from 7.3.5.1P3 to 8.1RC2 supported? we are planning to hot swap out the 8.1RC2 incompatible ESH2 modules in our 3270 cluster (8 of them) then proceed with a Non-disruptive Upgrade (NDU) from the current 7.3.5.1P3 to 8.1RC2. What will the clients see during cluster head failover? Should we shutdown virtualmachines? Oracle? Where is the current NDU doc? Any other gotchas for this kind of upgrade? thanks -- Fletcher

2 1

Re: NDU from 7.3.5.1P3 to 8.1RC2 supported?
by Fletcher Cocquyt 01 Feb '12

01 Feb '12

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>

2 1

Re: NDU from 7.3.5.1P3 to 8.1RC2 supported?
by Fletcher Cocquyt 31 Jan '12

31 Jan '12

Bill, thanks for the feedback Do you have any BugIDs associated with the issue you mention? I'm working with our SE and using the bug tool http://now.netapp.com/NOW/cgi-bin/bol?Type=AdvSearch&relselect=ONTAP&rel=8.… to review known 8.1RC2 issues A bit more background: We have a standby cluster (fresh 8.1RC2 install NOT an upgrade) and once the prod cluster is NDU'ed to 8.1RC2 we plan to data motion off prod vfilers to it so we can do tray upgrades (including a fresh install of 8.1RC2 since our root vol0 is on old trays we are getting rid of) thanks -- Fletcher On Jan 31, 2012, at 10:02 AM, Bill Holland wrote: > Unless it's a non-production environment I wouldn't go to 8.1RC2. Still issues with 64 bit conversion. Bad enough to crash a filer. > > Sent from my Galaxy Nexus > > Fletcher Cocquyt <fcocquyt(a)stanford.edu> wrote: > > Hi, > Is NDU from 7.3.5.1P3 to 8.1RC2 supported? > we are planning to hot swap out the 8.1RC2 incompatible ESH2 modules in our 3270 cluster (8 of them) > then proceed with a Non-disruptive Upgrade (NDU) from the current 7.3.5.1P3 to 8.1RC2. > > What will the clients see during cluster head failover? > Should we shutdown virtualmachines? Oracle? > > Where is the current NDU doc? > Any other gotchas for this kind of upgrade? > > thanks > -- > Fletcher > > > >

2 1

EMS Events in syslog
by Stuart Kendrick 29 Jan '12

29 Jan '12

Some EMS Events show up in syslog: cf.fm.takeoverComplete:WARN 10Jan2012 12:58:22 cf.fsm.releasingReservations:INFO 10Jan2012 12:58:24 loghost> grep -e cf.fm.takeoverComplete -e cf.fsm.releasingReservations syslog Jan 10 12:58:22 toaster-b-svif1 [toaster-b (takeover): cf.fm.takeoverComplete:warning]: Cluster monitor: takeover completed Jan 10 12:58:24 toaster-b-svif1 [toaster-b (takeover): cf.fsm.releasingReservations:info]: Cluster monitor: Releasing disk reservations in preparation for giveback But others do not: fci.device.timeout:ERR 10Jan2012 12:52:36 fci.device.quiesce:INFO 10Jan2012 13:00:16 loghost> grep -e fc.device syslog loghost> syslog.conf: *.info /etc/messages *.info @loghost.company.com In fact, examining my toaster logs for the last two years: loghost> ls 20* toaster-logs-from-2010.txt toaster-logs-from-2011.txt loghost> grep cf.fm.takeover toaster-logs-from* | wc -l 70 loghost> grep fc.device toaster-logs-from-* | wc -l 0 loghost> How do I persuade EMS to send /everything/ to syslog? --sk Stuart Kendrick FHCRC

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters