toasters

toasters@lists.teaparty.net

13520 discussions

RE: FC9 & DS14 on same FC-AL adapter...
by Waters, G Scott (DSTI) 25 Apr '03

25 Apr '03

I am curious about the 56 disk rule. To what does it apply. I ask that because I currently have a filer with 63 disk in one loop and no *known* problems. Please enlighten me. Thanks. - Scott W. -----Original Message----- From: Clawson, Simon [mailto:simon_clawson@mentorg.com] Sent: Wednesday, April 16, 2003 11:26 AM To: 'jeff.mery(a)ni.com'; toasters(a)mathworks.com Subject: RE: FC9 & DS14 on same FC-AL adapter... Yes. We have FC7, FC9 and DS14 on the same loop. The rules are - the shelves must be linked in order of oldest to newest - FC7 -> FC9 -> DS14. You cannot have more than 56 disks on one loop. Simon -----Original Message----- From: jeff.mery(a)ni.com [mailto:jeff.mery@ni.com] Sent: 16 April 2003 16:16 To: toasters(a)mathworks.com Subject: FC9 & DS14 on same FC-AL adapter... Fellow Toasters, Does anyone know if FC9 and DS14 shelves can co-exist on the same FC-AL adapter? If so, are there any special rules that must be followed (i.e. DS14s at beginning/end/certain shelf IDs etc.)? Thanks in advance, Jeff Mery, MCP National Instruments ------------------------------------------------------------------------ - "Allow me to extol the virtues of the Net Fairy, and of all the fantastic dorks that make the nice packets go from here to there. Amen." TB - Penny Arcade ------------------------------------------------------------------------ -

2 1

Duplicating filers
by Michael Homa 25 Apr '03

25 Apr '03

Hi. My name is Michael Homa and I'm a member of the Systems Group at the University of Illinois at Chicago. Some background --------------- We have two F740 filers: netapp1 and netapp2. o Both of them are at ONTAP 6.2.1. o Each has a different admin host. o Both have two FC9 data shelves. On netapp1, one shelf contains 18GB drives; the other shelf, 36GB drives. On netapp2, both shelves have 36GB drives. o Netapp1 has one volume, vol0, and two raid groups, rg0 and rg1. o Netapp2 has two volumes, volboot and vol0, and each volume has a single raid group, rg0. Netapp1 is the "center of our universe" and is NFS-mounted to almost all of our production servers. Netapp2 currently functions solely as the recipient of the snapmirroring of netapp1. I've been asked to undertake a project in which I make netapp2 be a duplicate of netapp1. In the event that netapp1 becomes unavailable (maybe a catastrophic hardware failure), we want to re-cable netapp2 to the network, monkey with DNS, and reboot the box. In effect, for all intents and purposes, make it netapp1. It's a good idea in theory but maybe in practice it won't work out. Nope. Now that I think about it, it doesn't even sound like a good idea in theory but my boss has asked me to try it so what the heck. Has anyone attempted this? I'm looking for suggestions, ideas, "gotchas." I don't need to reinvent the wheel; I'm more than willing to learn (borrow, steal) from others. Thanks. Michael Homa Academic Computing and Communication Center University of Illinois at Chicago email: mhoma(a)uic.edu

3 2

size/weight of filer head and shelves?
by Bill Bradford 25 Apr '03

25 Apr '03

Anybody know what the approximate dimensions and weight of a F520 head and one of the second-generation SCSI drive shelves are? I'm also looking for a *picture* of a 520, but cant seem to find one anywhere. Bill -- bill bradford mrbill(a)mrbill.net austin, texas

2 1

RE: Upgrading ONTAP
by Dorfner, Richard 23 Apr '03

23 Apr '03

It is okay to say bye, but we prefer that you use a power cycle after a firmware upgrade. The REASON we ask folks to power cycle was to put the fear of god in them that things would not go right if they didn't power cycle. This was due to the fact that we had gotten an inordinate number of bug reports about "ontap doesn't run after an OFW upgrade" well.. turns out they allways forgot to do the "bye" thing, so power cycling was written into the methodology... Rick Firmware weenie Network appliance.

1 0

RE: Upgrading ONTAP
by Alan McLachlan 23 Apr '03

23 Apr '03

hmmm.... Do it this way: 1. Download new version of OnTap (extract from setup.exe or sysfiles.tar). Execute "download" instruction to update bootblocks. 2. "Halt" to firmware prompt, flash the new firmware. 3. Power cycle the filer (required after firmware upgrade). This way, you only have 2-3 minutes of actual downtime. Remember, downloading the new OS only takes effect after a reboot - so you don't actually have to do the system firmware first, you can do it during the OS upgrade. If new firmware is not required you don't need to power cycle, a reboot is sufficient. -----Original Message----- From: Sam Schorr [mailto:sschorr@homestead-inc.com] Sent: Wednesday, 23 April 2003 3:44 AM To: Steve Evans; toasters(a)mathworks.com Subject: RE: Upgrading ONTAP Steve, Step 1 is separate and should be done first. Step 3 happens automatically upon rebooting under 6.3.1R1 (or any other OnTap version). The annoyance is doing a hard down, a system 'halt' for the firmware so that you are at the ? prompt. The system then reboots to your current version, then you do the OnTap upgrade. Depending on the number of disks, this could take up to 20 minutes for a fully loaded (we have 12 disk shelves with 36 gb drives) F840. Hope this helps. --sam -----Original Message----- From: Steve Evans [mailto:sevans@foundation.sdsu.edu] Sent: Tuesday, April 22, 2003 10:14 AM To: toasters(a)mathworks.com Subject: Upgrading ONTAP I'm going to upgrade to 6.3.1 R1. This is my first upgrade so I have a few questions. As I see it there are three steps. 1. Upgrade System Firmware 2. Upgrade ONTAP 3. Upgrade Disk Firmware Is that the order I should do it in and should I do it all at the same time or spread them out say one per week? Steve Evans SDSU Foundation (619) 594-0653 **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

2 1

RE: Upgrading ONTAP
by Sam Schorr 22 Apr '03

22 Apr '03

Steve, Step 1 is separate and should be done first. Step 3 happens automatically upon rebooting under 6.3.1R1 (or any other OnTap version). The annoyance is doing a hard down, a system 'halt' for the firmware so that you are at the ? prompt. The system then reboots to your current version, then you do the OnTap upgrade. Depending on the number of disks, this could take up to 20 minutes for a fully loaded (we have 12 disk shelves with 36 gb drives) F840. Hope this helps. --sam -----Original Message----- From: Steve Evans [mailto:sevans@foundation.sdsu.edu] Sent: Tuesday, April 22, 2003 10:14 AM To: toasters(a)mathworks.com Subject: Upgrading ONTAP I'm going to upgrade to 6.3.1 R1. This is my first upgrade so I have a few questions. As I see it there are three steps. 1. Upgrade System Firmware 2. Upgrade ONTAP 3. Upgrade Disk Firmware Is that the order I should do it in and should I do it all at the same time or spread them out say one per week? Steve Evans SDSU Foundation (619) 594-0653

1 0

Upgrading ONTAP
by Steve Evans 22 Apr '03

22 Apr '03

I'm going to upgrade to 6.3.1 R1. This is my first upgrade so I have a few questions. As I see it there are three steps. 1. Upgrade System Firmware 2. Upgrade ONTAP 3. Upgrade Disk Firmware Is that the order I should do it in and should I do it all at the same time or spread them out say one per week? Steve Evans SDSU Foundation (619) 594-0653

1 0

Question on ndmpcopy and restore_symboltable
by kyle 22 Apr '03

22 Apr '03

I run multiple ndmpcopies daily, and want to know if after each successful copy should the restore_symboltable be removed or should I always leave it around? There is no space issue, I just want to know what the correct way to handle this is. Thanks.

3 2

ndmpdlog no more obscure
by Stephane Bentebba 22 Apr '03

22 Apr '03

Hi all, here is a sed script to make ndmpdlog.yyymmdd log easier to read. it generate an html output with background color to quick identify errors recorded in the log. have a try _______________________________________________________________________ #! /bin/sed -f # DESCRIPTION # - This script convert a plain ndmpdlog.YYYYMMDD comming from a Netapp Filer (or compatible) to a nice html report. # - It write the result on stdout. # - For Un*x system or compatible. # SYNOPSIS # ndmpdlog2html.sed ndmpdlog.20030422 > anyfilename4output # OPTIONS # - you can focus the report only on error messages by uncomenting a line # - you can change enlight colors by modifying #hhhhhh fields # - you can uncomment the last line to enable very long reports # TODO # - embed this sed script in shell to incorpore as a title, the name of the log and the date in a more readable way # - add a java applet link that would mail the log to the Netapp support # - make coffee # HISTORY # - 22/04/2003 (europe date convention) version 1.0 # AUTHOR # - stephane bentebba # COPYRIGHT # - no copyright # - not supported # - feel free to enhance and distribute # SEE ALSO # - http://www.ndmp.org/download/ for the NDMP specifications # - http://www.netapp.com for Netapp products # #### set up the HTML header 1i\ <HTML><HEAD><TITLE>Enlighted NDMP logs</TITLE></HEAD>\ <BODY><body bgcolor="#FFFFFF">\ <br><br> # #### filter warnings : 'Error NDMP_*' /\(.*[Ee]rror.*NDMP_NO_ERR.*\)/{ s//<table border=0 cellpadding=0 cellspacing=0 width=600 bgcolor=#ddb422><tr><td><font color=black size=2>\1<br><\/td><\/tr><\/table>/ # #### comment out this line to ignore warning lines # d;n p;d } # #### filter Errors : 'Error code: NDMP_*' lines (in fact all remaining lines containing '[Ee]rror' /\(.*[Ee]rror.*\)/{ s//<table border=0 cellpadding=0 cellspacing=0 width=700 bgcolor=#ff0000><tr><td><font color=black size=2>\1<br><\/td><\/tr><\/table>/ p;d } # #### filter 'NDMP message' and 'Message NDMP_*' lines (avoiding '[Mm]essage replysequence | header' lines) /\(.*[Mm]essage replysequence.*\)/!{ /\(.*[Mm]essage Header.*\)/!{ /\(.*[Mm]essage.*\)/{ s//<table border=0 cellpadding=0 cellspacing=0 width=500 bgcolor=#32cd32><tr><td><font color=black size=2>\1<br><\/td><\/tr><\/table>/ # #### comment out this line to ignore message lines # d;n p;d } } } # #### uncomment the single 'd' line to focus on Message, Warning and Error messages only /\(.*\)/{ s//<table border=0 cellpadding=0 cellspacing=0 width=400 bgcolor=#008080><tr><td><font color=black size=1>\1<br><\/td><\/tr><\/table>/ # d } # #### to avoid output files being bigger than 16M (!) 100000q # EXAMPLE # You can try it with that sample of an authentic ndmpdlog : # # Apr 22 02:43:48 [ndmpd:72]: Method 264 # Apr 22 02:43:48 [ndmpd:72]: ReplySequence 5 # Apr 22 02:43:48 [ndmpd:72]: Error NDMP_NO_ERR # Apr 22 02:43:48 [ndmpd:72]: Error code: NDMP_NO_ERR # Apr 22 02:43:48 [ndmpd:72]: Vendor: Network Appliance # Apr 22 02:43:48 [ndmpd:72]: Product: Network Appliance NDMP server # Apr 22 02:43:50 [ndmpd:72]: Revision: 3.0 # Apr 22 02:43:50 [ndmpd:72]: NDMP message type: NDMP_TAPE_OPEN # Apr 22 02:43:50 [ndmpd:72]: NDMP message replysequence: 6 # Apr 22 02:43:50 [ndmpd:72]: Message Header: # Apr 22 02:43:50 [ndmpd:72]: Sequence 0 # Apr 22 02:43:50 [ndmpd:72]: Timestamp 0 # Apr 22 02:43:50 [ndmpd:72]: Msgtype 1 # Apr 22 02:43:50 [ndmpd:72]: Method 768 # Apr 22 02:43:50 [ndmpd:72]: ReplySequence 6 # Apr 22 02:43:50 [ndmpd:72]: Error NDMP_NO_ERR # Apr 22 02:43:50 [ndmpd:72]: Error code: NDMP_IO_ERR # Apr 22 02:43:50 [ndmpd:72]: Device name: nrst0a # Apr 22 02:43:50 [ndmpd:72]: Mode: 0 # Apr 22 02:43:50 [ndmpd:72]: IOException: Input/output error # Apr 22 02:43:50 [ndmpd:72]: NDMP message type: NDMP_TAPE_OPEN # Apr 22 02:43:50 [ndmpd:72]: NDMP message replysequence: 7 # Apr 22 02:43:50 [ndmpd:72]: Message Header: # Apr 22 02:43:50 [ndmpd:72]: Sequence 0 # Apr 22 02:43:50 [ndmpd:72]: Timestamp 0 _______________________________________________________________________ -- jetez un oeil ici http://www.sensiva.com/ -- -- have a look here http://www.sensiva.com/ --

1 0

RE: Question on ndmpcopy and restore_symboltable
by Melvin, Grant 21 Apr '03

21 Apr '03

Hi, As Lance points out if you intend to do incremental restores then you need to leave the restore_symboltable file in place. However, if the transfer is complete then you can remove it. Cheers, Grant -----Original Message----- From: Lance R Bailey To: kyle Cc: toasters(a)mathworks.com Sent: 4/19/03 9:32 PM Subject: Re: Question on ndmpcopy and restore_symboltable the restore_symboltable is used by successive ndmpcopy commands -- Lance I'm a vegetarian. Not because I love animals. It's because I hate plants. Saturday Night Live On Sat, Apr 19, 2003 at 08:57:18PM -0400, kyle wrote: > I run multiple ndmpcopies daily, and want to know if after each successful > copy should the restore_symboltable be removed or should I always leave it > around? There is no space issue, I just want to know what the correct way > to handle this is. > > Thanks.

1 0

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