toasters

toasters@lists.teaparty.net

13514 discussions

Crossovers cable to NetApp
by Robert Borowicz 25 Apr '03

25 Apr '03

Does anybody do a direct connect from a Sun or whatever to the NetApp via a crossover 100Bt cable? If so what considerations did you make when ifconfig'ing the Sun? Did you use static routes? TIA -Rob --- Robert K. Borowicz Mgr. Infrastructure Support Railroad Commission ITS O: 512-936-2401 C: 512-576-2300

2 1

Looking for 220V powers for Shelf...
by John Enger 25 Apr '03

25 Apr '03

I am looking for 2 powermodules for Netapp-shelf (FC6?). The powers I have are 110V, and thus unusable here in Norway. The part code of my 110V powermodules are XLPSU-NA1. I need the 220V version. Does anyone have any spares? This is for home-experimentation, and I do not wish to pay like 2-300 $ for each power... Can anyone help? John Enger

2 1

(no subject)
by John Enger 25 Apr '03

25 Apr '03

1 0

RE: Duplicating filers
by Waters, G Scott DSTI 25 Apr '03

25 Apr '03

Why not just look at clustering the two filers?? ... or am I missing something? - Scott W. -----Original Message----- From: Hunter Wylie [mailto:hwylie@stpaultel.com] Sent: Thursday, April 24, 2003 2:36 PM To: 'Michael Homa'; toasters(a)mathworks.com Subject: RE: Duplicating filers Michael, In theory it might work on a "perfect" day "but" the number and type of simple failure scenarios would make the perfect day highly improbable. I suggest you take a simpler approach that many of my very large customers use to achieve very high availability, very short mean time to repair, simplicity and low cost. Buy a used F740 (head) configured like the biggest one you have, a spare 36 and 18 GB disk and a FC9 disk shelf. When something breaks and you have an idea it's "head associated - down the dying F740 and power it off, unhook LAN connections, FC disk cable, etc. and attach them to the spare F740 racked between the original two heads. Cable lengths can get you if you are not careful. Watch your power load on the rack/circuit. If it is shelf associated, shut down the system, power it down, remove the old shelf cable and attach the new one, move all the drives and power up. In both cases the system will comeback on line with all the old identities re-established, no DNS hacks. This technique is used by one of the largest on-line retailers in the world. They love it. No software licenses are needed on the spare system as long as it is "NEVER" used in parallel production with the two other systems. In this mode it is strictly a replacement spare part. If you want to use it in any other mode you must acquire software licenses with it. The nice thing about this solution is it is simple to test. Send me an email if you want to figure out the exact parts you will need. Hunter M. Wylie 21193 French Prairie Rd St. Paul, Oregon 97137 Bus: 503-633-8900 FAX: 503-633-8901 Cell: 503-880-1947 http://www.itmls.com/ -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Michael Homa Sent: Thursday, April 24, 2003 10:24 AM To: toasters(a)mathworks.com Subject: Duplicating filers 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

4 3

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

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