toasters

toasters@lists.teaparty.net

13513 discussions

Re: Firmware and such...
by tjt＠netapp.com 03 Apr '98

03 Apr '98

> | Also again.. Why does the book say that you don't have to have the http > | license to do http admin and all I can get on our 230 is http man pages? > > This threw me off at first. What they mean by that is that you can load the > FilerView software on your filer and do admin of it via a web interface. > It is kinda cool. Not the speediest thing over a T1 frame relay cloud. > Go to now.netapp.com and get filerview for your OS. It does not require In ONTAP 5.0, FilerView is included by default, no separate install needed. Just point your browser at http://{filername}/na_admin ...Tim Thompson...tjt(a)netapp.com...

1 0

RE: Firmware and such...
by Weeks, Thomas 03 Apr '98

03 Apr '98

Hi all.. I'm new here... No I havn't read any FAQ's yet.. My config: FS230 (FIDDI and e0) 4.2.aD9 128M DRAM 4M SRAM NFS access with mount privs via host/netgroup and client NFS authentication CIFS (to test file space area) Right now it looks like the best way to give my customers both NFS anf CIFS access to the same file space is by using the /etc/passwd file... <sigh>.. this is a real pain... Has anyone been using OnTap 5.0? Any comments about CIFS access/shares via ACLs? Rigth now we're having to relate users to UNIX file permissions and it's a real pain becuase we have to merge over 27 different /etc/passwd files down to the 230's single passwd file... If there is a conflicting UID... we have to do the UID shuffle and go back and change them on the UNIX box to refelct what the NetApp has them down as. (BTW.. our UNIX servers are Solaris boxes and use NIS+, but they were configured wrong and all have their OWN NIS+ domain (stupid eh?))... Also... I am NOT using the CIFS.GUEST setting.. does anyone have good/bad experienve with this? Can the whole homedir thing still be used if this is implimented? Also again.. Why does the book say that you don't have to have the http license to do http admin and all I can get on our 230 is http man pages? Sorry for all the Q's at once... Thanx... Tom D Tek

2 1

Firmware and such...
by Alexei Rodriguez 03 Apr '98

03 Apr '98

I think some of these issues have been raised before, but I thought I would raise them again :) We just upgraded our filer from 4.2a to 4.3.3 this morning. When we got the 4.3.3 files from NOW, we read the firmware docs. They state that you must have firmware 1.6 and above to run 4.2a and above. So, we thought "no problem; we are running 4.2a so we must have 1.6 on the box". Wrong. We had version 1.4a of the firmware on our f540. So, I had to get someone at the NOC to do all the floppy shuffling (our site is 2500 miles away). No problem. I just get scared whenever I do a firmware upgrade. Some scars never heal :) Ok, the firmware upgrade goes well. We then proceed to do the DataONTAP upgrade. No problem. There should be a note in the docs that warn of the time delay when doing a "download". I had not done one in a while and had forgotten all about it. might be nice to let folks know that this may take a few minutes. Ok, so I now have a f540 filer with firmware 1.6 and ONTAP 4.3.3. Whoohoo. Now, my concerns: - there should be a better way of looking at the firmware rev, other than having to halt the filer. - the system boot should be logged (all of it, including the firmware banner, like a Sun) - a CHANGELOG for firmware revs would be nice I think these changes would be nice. We have been having some odd issues with our FDDI (at around midnight the filer stops doing NFS on the FDDI interface; we down and up the interface and all is good). I wonder if this would have anything to do with an incorrect firmware rev... we have swapped the card and pci slot it is in. I am hoping that the new firmware/os will perhaps clear the problem. Alexei

3 3

First posting test.... Ignore please
by Weeks, Thomas 02 Apr '98

02 Apr '98

Test test..1..2..3.. No Reply needed if this is really working... Tom D Tek

1 0

Re: 4GB/9GB shelf migration from toaster A to toaster B.
by Daniel Quinlan 31 Mar '98

31 Mar '98

Daniel Quinlan wrote: >> You can get back your 4GB spare, since you only need one spare. The >> spare only has to be the same size of the largest data disk in the >> system. If you have a 9GB spare and a 4GB disk fails, you end up >> adding 5 GB to the filesystem when the spare replaces the failed >> disk. kls(a)netapp.com (Karl Swartz) writes: > No, you end up putting 4GB on a 9GB drive and getting no more space in > the file system than you had before. (If there are multiple spares in > the system, the smallest one which is large enough to replace the > failed drive will be used.) That's a shame. Is this information documented somewhere? - Dan

2 1

Re: 4GB/9GB shelf migration from toaster A to toaster B.
by Daniel Quinlan 31 Mar '98

31 Mar '98

Jim Davis <jdavis(a)CS.Arizona.EDU> writes: > Potential plan: buy a shelf of 9GB disks, put it on toaster A, move a > shelf of 4GB disks to toaster B, keeping all of the toaster A data on > toaster A. Toaster B ends up with an empty file system on its 4GB disk > shelf. > > Now the mechanics of the move are a little unclear to me. Presumably we > hook up the 9GB shelf to toaster A and 'raid fail' each 4GB disk in the > shelf we want to move? But there will be 5 9GB data disks, since we have > to burn one as a hot spare and one becomes the new parity disk. Will > there be a problem with having 7 disks to move data from, but only 5 disks > to move data to? There would be enough GBs on the 5 9GB disks, but... Yes, it won't work as you suspect (unless, of course, you do a backup-restore cycle) because the total number of disks in a NetApp RAID group can't be reduced, even if the capacity is increased. You can get back your 4GB spare, since you only need one spare. The spare only has to be the same size of the largest data disk in the system. If you have a 9GB spare and a 4GB disk fails, you end up adding 5 GB to the filesystem when the spare replaces the failed disk. Dan

4 3

Netapp Announces F630 Cluster
by sirbruce＠ix.netcom.com 31 Mar '98

31 Mar '98

So, who wants to get one of the new F630 clusters, aka the F6300? The announcement was out today. Has anyone here had any experience with Tandem's ServerNet technology and can comment on it's strengths and weaknesses? And on a side note, how about that stock price. :) Bruce

4 3

Re: shares
by Keith Brown 28 Mar '98

28 Mar '98

>what the largest number of any shares anyone's currently exporting from a >toaster? In ONTAP releases prior to 4.3, we had an upper limit that amounted to about a thousand shares in a typical configuration. The actual limit was "fuzzy", because it wasn't defined by any hard, static configuration that directly limited the number of shares to a certain specific number. It was defined by an internal buffer pool and some semantics that were specific to the algorithms that managed the use of those buffers when Windows clients attempted to enumerate a filers shares. To give you an idea of what I mean, you could actually create quite a few more than 1000 shares using these older versions of ONTAP, as long as you kept the comments you placed on those shares to a minimum (making them either short or non-existent). The up-to-32-character share comments that Windows allows you to associate with shares used up space in these buffers that would otherwise have been usable to define more shares in! :-) However, as of ONTAP 4.3.3 and beyond, this way of doing things ceased to exist. The upper limit on the number of shares a filer can export is currently a function of the amount of memory you have installed. On the F5XX and F6XX filers, you're looking at a limit of: 2400 + 2000*(# of 64MB chunks above 128MB) and on the F2XX and F3XX the numbers are ironically even higher due to a difference in the size of memory addresses used by the CPU's we use in the lower end filers versus the CPU's we embed in the higher end filers. Bottom line, we're talking about a veritable truckload of shares here. When the limit used to be around a thousand, I only knew of two customers who "discovered" it. Oh... I should probably mention that these limits are not inclusive of the automatic shares that are generated on the fly for individual users when you set the: options cifs.home_dir /wherever/whatever option. In other words, these *don't* count towards the total, and these could potentially amount to thousands more shares than just the statically defined ones. > are there performance penalties associated with too many shares, No, unless you count the amount of time it takes to enumerate the things (that's the amount of time you have to stare at the torch (flashlight) scanning backwards and forwards after you have double clicked the filer under "Network Neighborhood"). However, whatever amount you've created, I think it's a pretty safe bet that Data ONTAP will spit 'em back at you more rapidly than NT would given the same number. ONTAP has a rather tight focus on the such matters. :-) Keith

1 0

Anyone using DEC TZ88 DLT drive with their NetApp?
by Bill Bradford 27 Mar '98

27 Mar '98

Anybody out there using a DEC TZ88 (DLT 4000) drive with their Netapp? I asked support about it being a supported drive (its basically hardware identical to a Quantum DLT4000, just returns a different ID string) and they said "you'll have to change the string it returns to match another DLT drive, sorry." I'd *really* like to get this to work without modifying it. Bill -- Bill Bradford Systems Engineer, Texas.Net http://www.texas.net mrbill(a)texas.net BeOS Developer #9630 ICQ: 1864511 --------------------------------------------------------------------- Called up the Bureau of Alcohol, Tobacco, and Firearms regional office and asked, "What wine goes best with an M-16?" The guy who answered did his best to be helpful: "That depends. What are you smoking?"

1 0

Re: first experience with RAID groups
by Daniel Quinlan 27 Mar '98

27 Mar '98

Timothy A. McCarthy <tmac(a)netapp.com> writes: > If you want a "neat" looking raid group, you can use the vol command: > vol add volname ndisks -d diskname > volname=volume name > ndisks=num of disks to add > diskname= a space separated list of drives that you want to use > > vol add vol0 10 -d 8b.0 8b.1 8b.2 8b.3 8b.4 8b.5 8b.8 8b.9 8b.10 8b.11 I think that's the wrong syntax to specify a list of disks to add. Everything after the "10" is ignored. This is actually the same exact mistake I made, illustrating how confusing the vol documentation is. What I tried was: vol add vol0 2 -d 8b.0 8b.1 And the system proceeded to add 8b.13 and 8b.14. I think this is the right syntax: vol add vol0 -d 8b.0 8b.1 8b.2 8b.3 8b.4 8b.5 8b.8 8b.9 8b.10 8b.11 I would guess that even with the above syntax for specifying a list of disks to be added, disks are still added in a random order. - Dan

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