toasters

toasters@lists.teaparty.net

13515 discussions

RE: "Wac"-ing the WAFL?
by Anders Ljungberg S (QDT) 30 Dec '99

30 Dec '99

We have 9 F760's in 3 clusters and 3 mirrors. They are all fully populated with shelfs ( 80 shelfs/~8TB in total ). I dont know the wack time because a never had to run a single one. The system was taken into production 9 months ago. So in our case it's not very common. Anders -----Original Message----- From: E Hunter [mailto:eric@gigaton.com] Sent: Thursday, December 30, 1999 4:28 AM To: toasters(a)mathworks.com Subject: Re: "Wac"-ing the WAFL? How long does it take to wack a fully loaded 760? By fully loaded, I mean somewhere in the 1TB range, which I think is the upper limit of the 760.

1 0

RE: "Wac"-ing the WAFL?
by Anders Ljungberg S (QDT) 30 Dec '99

30 Dec '99

This is my personal expirience from a heavy NFS Site. Which lead to replacing 2x7000/600 Auspex Netservers with a F740. To get realy good write performace lets say that you have to use atleast 7 drives/raidgroup.The performance raises up to lets say ~14. 7 drives without parity ( raid 4 or 5 ) is not verry funny considering the risk of a failing drive , restore times etc. So, in the Auspex case i had to go for mirrored stripes. ( Very bad price/performance and i finaly grew out of my cabinets ) On a filer i spend money on one "extra" drive instead of seven. The 740 is just cruising with the load which lead to the fall of the Netservers. Not to even mention the decreased need of administration. Anders Ljungberg As Jeff said, Netapp's RAID-4 implementation is not performance limiting in most cases. Most of the time a filer with RAID-4 will provide better performance than an equivalent product without RAID or with RAID-0. So I'm sure you will be quite pleased in your tests, particularly against a (*snicker*) Auspex. (Be sure to compare the price and number of filesystems in each system configuration as well.) I seem to recall some public talk waay back when about Netapp possibly offering RAID-0 since basically all you have to do is remove the parity drive. You could simulate this yourself by manually failing the parity drive and letting the filer operate in degraded mode with just the data disks. However, I'm not sure that the code is actually optimized for this case, so there might be some other normal RAID-4 checks that get in the way of realizing any performance gains. Bruce

1 0

RE: Some fun things not to try at home
by Priebe, Jason 28 Dec '99

28 Dec '99

> Are you implying that you'd rather use 6 drives per shelf > rather than 7? No -- I'm just assuming that the 7th disk (the hot spare) is drawing little or no power. Perhaps this is a bad assumption. > > Is startup power the power required to "spin up" the > > disks? In that case, isn't that power only delivered once at boot > > time? > > In addition to this, if I remember correctly, the filer spins up disks > sequentially, so there shouldn't be more than one disk drawing startup > power at any one time. That's good to note. Jason Priebe WRAL OnLine http://www.wral-tv.com/

2 1

RE: Some fun things not to try at home
by Priebe, Jason 27 Dec '99

27 Dec '99

Hmmm... that's interesting. I don't want to be foolhardy here, but I just checked the power requirements for the Seagate ST39173W (9GB Barracuda) drives and the ST15150W (4GB Barracuda) drives that are in the filer's shelf now. ST39173W ST15150W 12V startup 1.7 amps 2.18 12V typical 0.5 0.83 5V startup 1.2 amps 1.0 5V typical 0.75 0.75 It appears to me that, except for the 5V startup, the 9GB drives require _less_ power than the 4GB drives. Is the 5V startup the limiting factor? Can the power supply not deliver 1.2 amps at 5V to six drives? Is startup power the power required to "spin up" the disks? In that case, isn't that power only delivered once at boot time? Do the disks ever spin down in an active system? I really don't mean to be confrontational. We're just desperate to get some more life out of our F210 (we bought it new just two years ago). Jason Priebe WRAL OnLine http://www.wral-tv.com/ > -----Original Message----- > From: Bulfer, David [mailto:david.bulfer@netapp.com] > Sent: Wednesday, December 22, 1999 5:30 PM > To: 'Priebe, Jason'; toasters(a)mathworks.com > Subject: RE: Some fun things not to try at home > > > Please be careful. I do not believe that your StorageWorks > shelf has enough > power for 9G drives. Buying a new supply from Compaq would > not solve the > problem either. Your results could be quite unhappy. > > David Bulfer > Director of Platform Engineering > Network Appliance, Inc. > > -----Original Message----- > From: Priebe, Jason [mailto:priebe@wral-tv.com] > Sent: Wednesday, December 22, 1999 1:22 PM > To: toasters(a)mathworks.com > Subject: RE: Some fun things not to try at home > > > > -----Original Message----- > > From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com] > > If you find out something > > useful in your filer experience, plesae pass it along, even > if it's of > > the "I didn't read the manual, so I did this and it > crashed" variety. > > While we're airing dirty laundry -- a couple of months ago, I > mentioned > to the list that we wanted to try to replace our F210's 4GB SCSI disks > with 9GB disks (full shelf, no more shelves available from NetApp). > > I replaced two of the 4GB disks with 9GB ones, and all was well (of > course, the filer only used 4 of the 9GB, but we figured we'd dump > to tape, rebuild the file system, then restore once all the drives > were in place). > > So I'm opening the 3rd disk carrier, removing the flex circuit from > the disk drive (has anyone else ever tried to do this? How the #$%! > do you do it?) by prying with a screwdriver, and the screwdriver goes > right through the circuit. D'oh! > > I did find that I was able to call Compaq and order a new > circuit (only > $96 for that tiny little piece!). Still waiting on delivery, though. > I'll let you know how it goes. Wish I'd known you could still order > these parts -- I could have built a couple of my own carriers and had > them ready to go into the filer instead of failing a drive, > disassembling > the carrier, reassembling the carrier, and reinstalling. > > Jason Priebe > WRAL OnLine > http://www.wral-tv.com/ > >

3 2

NFAS-1400
by Russell Murphy 27 Dec '99

27 Dec '99

I picked up a rack mount cabinet at the local electronic surplus and while looking it over to strip, I discovered it was a toaster. Before I cannibalize it, is there documentation available? Network Appliances' support pages appear to be customer only.

1 0

Spam alert
by Clawson, Simon 27 Dec '99

27 Dec '99

looks like this address has been hit with a spammer. Can you block this? Simon Clawson ---------------------------------------------------------------------------- ------------------------- > -----Original Message----- > From: mbhdkp5(a)hotmail.com > Sent: 26 December 1999 18:44 > To: toasters(a)mathworks.com > Subject: FREE SEX, Free forever, forever free! From: 219.130.141.242 > ---------------------------------------------------------------------------- --------------------

2 1

FREE SEX, Free forever, forever free! From: 219.130.141.242
by mbhdkp5＠hotmail.com 26 Dec '99

26 Dec '99

Ok, I'll keep this short! At the following site... http://www.angelfire.com/la2/coolallforfree/enter.html you can download a program called Sextracker that finds you free sex on the internet, download is forever free, and free forever, no credit cards, no memberships, no hassles!. However, if you feel like spending some money, you can buy a legitimate password that would give you access to over 70,000 high quality adult sites 24/7 for a whole year (or a whole lifetime), your choice! Costs start from $1 A YEAR up to $1.20 a month (for the exact same service), go to http://www.angelfire.com/la2/coolallforfree/enter.html to see for yourself! Also a great Christmas pressent for your friends! ---- I am very sorry if you did not appreciate this email, your address was submitted from : 219.130.141.242 However, rest assured, this is a one time only email and you would never receive it again, have a wonderful year 2000 and don't forget, DRIVE SAFELY ON THE ROADS and DON'T drink and drive, for goodness sake :)! Take care out there and goodbye!

1 0

RE: Some fun things not to try at home
by Bond, Andrew 23 Dec '99

23 Dec '99

Note that some disks are not labelled with WIDE SCSI; however the DEC part number may have "W" in it, eg: SHWHB-GB (but you can't rely on this either!). > -----Original Message----- > From: owner-dl-toasters(a)netapp.com > [mailto:owner-dl-toasters@netapp.com]On Behalf Of Timothy A. McCarthy > Sent: 22 December 1999 22:14 > To: tkaczma(a)gryf.net > Cc: toasters(a)mathworks.com > Subject: Re: Some fun things not to try at home > > > I've had this happen before... a long time ago anyway. > > Check the disk. In my case I tried to put a WIDE > SCSI disk into a narrow shelf. Result, not even recognized. > > Pulled it out, looked at the label, and in the wise > words of Homer Simpson said "Dogh!!" when I > read "4GB WIDE SCSI". > > --tmac > > tkaczma(a)gryf.net wrote: > > > On Wed, 22 Dec 1999, Bruce Sterling Woodcock wrote: > > > > > Some of the older drivers didn't > > > like one version of the StorageWorks container, but did work > > > in another, and we spent the rest of the night scrounging for > > > parts off other containers for the right disk container. :) > > > > Is that right. I just plugged in a brand spanking new > spare (well it's > > been on the shelf for a while) into a 330's shelf and the > disk was not > > detected even after several tries (a defective spare?). I > pop a different > > disk in and it is detected immediately. I wonder whether > that was the > > problem, whether the shelf is becomming flakey, oe whether > it was simply a > > bad spare. > > > > Tom > > -- > ******All New Numbers!!!****** > ************* ************* > > Timothy A. McCarthy --> System Engineer, Eastern Region > Network Appliance http://www.netapp.com > 240-268-2034 Office \ / Page Me at: > 240-268-2002 Fax \/ 888-971-4468 > > > >

3 2

RE: Some fun things not to try at home
by Priebe, Jason 23 Dec '99

23 Dec '99

> -----Original Message----- > From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com] > If you find out something > useful in your filer experience, plesae pass it along, even if it's of > the "I didn't read the manual, so I did this and it crashed" variety. While we're airing dirty laundry -- a couple of months ago, I mentioned to the list that we wanted to try to replace our F210's 4GB SCSI disks with 9GB disks (full shelf, no more shelves available from NetApp). I replaced two of the 4GB disks with 9GB ones, and all was well (of course, the filer only used 4 of the 9GB, but we figured we'd dump to tape, rebuild the file system, then restore once all the drives were in place). So I'm opening the 3rd disk carrier, removing the flex circuit from the disk drive (has anyone else ever tried to do this? How the #$%! do you do it?) by prying with a screwdriver, and the screwdriver goes right through the circuit. D'oh! I did find that I was able to call Compaq and order a new circuit (only $96 for that tiny little piece!). Still waiting on delivery, though. I'll let you know how it goes. Wish I'd known you could still order these parts -- I could have built a couple of my own carriers and had them ready to go into the filer instead of failing a drive, disassembling the carrier, reassembling the carrier, and reinstalling. Jason Priebe WRAL OnLine http://www.wral-tv.com/

3 2

RE: Some fun things not to try at home
by Bulfer, David 22 Dec '99

22 Dec '99

Please be careful. I do not believe that your StorageWorks shelf has enough power for 9G drives. Buying a new supply from Compaq would not solve the problem either. Your results could be quite unhappy. David Bulfer Director of Platform Engineering Network Appliance, Inc. -----Original Message----- From: Priebe, Jason [mailto:priebe@wral-tv.com] Sent: Wednesday, December 22, 1999 1:22 PM To: toasters(a)mathworks.com Subject: RE: Some fun things not to try at home > -----Original Message----- > From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com] > If you find out something > useful in your filer experience, plesae pass it along, even if it's of > the "I didn't read the manual, so I did this and it crashed" variety. While we're airing dirty laundry -- a couple of months ago, I mentioned to the list that we wanted to try to replace our F210's 4GB SCSI disks with 9GB disks (full shelf, no more shelves available from NetApp). I replaced two of the 4GB disks with 9GB ones, and all was well (of course, the filer only used 4 of the 9GB, but we figured we'd dump to tape, rebuild the file system, then restore once all the drives were in place). So I'm opening the 3rd disk carrier, removing the flex circuit from the disk drive (has anyone else ever tried to do this? How the #$%! do you do it?) by prying with a screwdriver, and the screwdriver goes right through the circuit. D'oh! I did find that I was able to call Compaq and order a new circuit (only $96 for that tiny little piece!). Still waiting on delivery, though. I'll let you know how it goes. Wish I'd known you could still order these parts -- I could have built a couple of my own carriers and had them ready to go into the filer instead of failing a drive, disassembling the carrier, reassembling the carrier, and reinstalling. Jason Priebe WRAL OnLine http://www.wral-tv.com/

1 0

Some fun things not to try at home
by Brian Rice 22 Dec '99

22 Dec '99

Here is a tale of woe, which you will find entertaining not only because it offers lotsa useful information about filer management, but also because it makes me look like an idiot. Several weeks ago, some co-workers of mine and I undertook to add a fibre-channel controller and shelf to each of two F630's, each of which previously had only one dual-SCSI adapter. We did the wrong thing, as it turned out (much later). The FC cards are PCI cards with a long edge connector. F630's have two kinds of PCI slots: some long, some short. We naively jumped to the conclusion that long cards go in a long slot, so we installed the FC cards in slot 10, rather than slot 7, which had been our plan before opening the filers. Slot 10, it turns out, was a bad idea. Disk controller cards on F630's are only supported in slots 5-8, inclusive. And, believe it or not, you are supposed to put the card in there in spite of the fact that it is too big...you just leave the extra section of connector hanging in mid-air. So we had just put the filers in an illegal configuration. You may be interested to know the failure mode: None. The filers booted right up, found all the disks, and announced them; we added them to a volume, and we were off to the races. A week later, the regular disk scrubs found bizillions of parity inconsistencies on each filer and fixed them. Then the filers started crashing ("PANIC: Freeing free block"). They would only restart after a run of wackz. Then the next disk scrub would put us on the path to ruin again. After several interactions with several levels of NetApp technical support, eventually all parties came to understand what had happened, and the fact that the FC cards are not supported in slot 10. So we got the FC cards put into the right slots, did a wackz, and breathed easier. Then one of the filers crashed again. The culprit there: wackz and disk scrubs look at two completely different pieces of the puzzle. I had the (once again) mistaken idea that wackz fixed a superset of the problems that a disk scrub fixes. Wrong. Wackz only looks at the file system structure and ignores the parity data; to fix the parity data, you need a disk scrub. Moral of the story: to make sure your disks have happy data on them, do both a wackz and a disk scrub. Yer not done until you do both. With that problem fixed, we breathed a sigh of relief. Then one of the filers crashed again. It turned out that that filer had been in the middle of doing its nightly backup when it crashed the first time, and so it had created a snapshot. Call it "fred". The system came back up, and eventually got fixed, wacked, and scrubbed, but fred was still corrupt. My backup script contained this: rsh toaster snap create fred It did not check to see whether fred exists already; if so, the snap create would just fail, and then the backup would proceed to dump the (existing) fred. Which, if fred is corrupt, would panic the system. I deleted fred. Then the filer was able to back itself up fine. So: make sure your snapshots are fresh. My backup script now starts like this: rsh toaster snap list | grep fred > /dev/null 2>&1 if [ $? -eq 0 ] then echo I refuse to work under these conditions exit 5 fi rsh toaster snap create fred Brian P.S. If you know about PCI, you may know that long PCI cards are 64-bit, and short ones are 32-bit. I've omitted that from the discussion above, since what leaps out at you first when you go to install a PCI card is not its bit-width but its physical width...the latter was what got us started down this awful path in the first place. P.P.S. NetApp Engineering is looking into building checks for illegal configurations into future versions of ONTAP.

7 11

virus detection
by Robert.Ryan＠chase.com 22 Dec '99

22 Dec '99

What are the best strategies for detecting and cleaning virus infected files on a filer. This would include not only file written to/from CIFS .... but also files which are written to shared volumes by UNIX and accessed by CIFS clients. Does anyone have experience with the performance impact of continual scans, and the amount of time required to scan a large volume. Thanks!

1 0

modifiying root volume
by Igor Schein 22 Dec '99

22 Dec '99

Hi, I have 1 root volume with 2 raid groups and 1 spare disk. Can I 1) make it 1 raid group and/or 2) free up another drive for a spare ( the current disk usage is minimal ) without destroying the volume and consequently having to reinstall OS? Thanks Igor

2 1

restore(1) behavior
by Igor Schein 21 Dec '99

21 Dec '99

Hi, I have a 740 filer and a tape library attached to it. When I do 'restore tvf' to see what's on the tape, all the disks start spinning intensively, as if I'm actually extracting from the tape rather then listing tape's contents. I'm not sure I understand why that's happening. Any idea? Thanks Igor

2 1

RE: Files disappear after some random interval
by Barrett,Eric 21 Dec '99

21 Dec '99

Your NFS client most likely has an entry in the crontab to delete all files in the /tmp directory (or all files older than a certain amount of time); this script is probably not smart enough to tell files on local storage from remote storage. Two things jumped out at me immediately: 1) You're mounting the filer on /tmp. 2) The deletions occur at 5:00am Saturday, which is prime cron time. Note also the ascending time of the directories -- as the file-removing script swept through the directories, it updated their modification times. The moral: NEVER, EVER, EVER NFS mount anything on or in /tmp. :) -- Eric Barrett / Technical Support Engineer, Network Appliance Direct: 1-408-822-4779 / Pager: 1-408-939-7945 Get answers NOW! - NetApp On the Web - http://now.netapp.com > -----Original Message----- > From: Dave Toal [mailto:dave_toal@t-t.com] > Sent: Monday, December 20, 1999 4:11 PM > To: jq(a)opensystems.com; toasters(a)mathworks.com; unixgroup(a)t-t.com; > support(a)opensystems.com > Subject: Files disappear after some random interval > > > Folks, > > We have a problem with files disappearing from a filer. > The box is a 520 running 5.2.1. THREE > times now, we've mounted one of its volumes to a production > box, done tar cvf - | ( cd mount_point; > tar xvf -), diff -r with no errors -- and then a day or two > later the files that were copied are > gone. Directories are there still, and symbolic links, but NO FILES. > > Snapshots were turned off after the second time it > happened; snap reserve is set to 0% and snap > sched is 0 0 0 for that volume. There are no remarks in > messages -- nothing besides [statd] time, > up x days. The directories show size but ls returns nothing. > > This is the volume on the netapp, mounted on the sun box: > > idsmajor:root:/mnt/etc>mount -p | grep /tmp/a > sanihome:/vol/nfs_archive - /tmp/a nfs - no rw > idsmajor:root:/mnt/etc>ls -l /tmp/a | head > total 81288 > drwxr-xr-x 2 ids users 344064 Dec 19 05:29 apr_1995 > drwxr-xr-x 2 ids users 393216 Dec 19 05:31 apr_1996 > drwxr-xr-x 2 ids users 3989504 Dec 19 05:51 apr_1997 > drwxr-xr-x 2 ids users 114688 Dec 19 05:52 aug_1994 > drwxr-xr-x 2 ids users 380928 Dec 19 05:53 aug_1995 > drwxr-xr-x 2 ids users 409600 Dec 19 05:55 aug_1996 > drwxr-xr-x 2 ids users 4227072 Dec 19 06:16 aug_1997 > drwxr-xr-x 2 ids users 282624 Dec 19 06:18 dec_1994 > drwxr-xr-x 2 ids users 290816 Dec 19 06:19 dec_1995 > idsmajor:root:/mnt/etc>ls -als /tmp/a/* | head -20 > 0 lrwxrwxrwx 1 ids users 29 Dec 7 16:34 > /tmp/a/dec_1997 -> > /archive/nfs_archive/dec_1997 > 0 lrwxrwxrwx 1 ids users 29 Dec 7 23:37 > /tmp/a/nov_1997 -> > /archive/nfs_archive/nov_1997 > 0 lrwxrwxrwx 1 ids users 29 Dec 8 01:05 > /tmp/a/oct_1997 -> > /archive/nfs_archive/oct_1997 > 0 lrwxrwxrwx 1 ids users 29 Dec 8 01:54 > /tmp/a/sep_1997 -> > /archive/nfs_archive/sep_1997 > > /tmp/a/apr_1995: > total 688 > 680 drwxr-xr-x 2 ids users 344064 Dec 19 05:29 . > 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. > > /tmp/a/apr_1996: > total 784 > 776 drwxr-xr-x 2 ids users 393216 Dec 19 05:31 . > 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. > > /tmp/a/apr_1997: > total 7808 > 7800 drwxr-xr-x 2 ids users 3989504 Dec 19 05:51 . > 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. > > idsmajor:root:/mnt/etc> > > > There were no problems with applications pulling files > from these directories on the netapp on > Friday, Dec 18. This volume is not mounted anywhere else. > This is a production system -- nothing > writes to the mount point. > > What happened Saturday morning at 5 AM? Why did all > these directories get touched? > > > Dave > > > >

4 3

Files disappear after some random interval
by Dave Toal 21 Dec '99

21 Dec '99

Folks, We have a problem with files disappearing from a filer. The box is a 520 running 5.2.1. THREE times now, we've mounted one of its volumes to a production box, done tar cvf - | ( cd mount_point; tar xvf -), diff -r with no errors -- and then a day or two later the files that were copied are gone. Directories are there still, and symbolic links, but NO FILES. Snapshots were turned off after the second time it happened; snap reserve is set to 0% and snap sched is 0 0 0 for that volume. There are no remarks in messages -- nothing besides [statd] time, up x days. The directories show size but ls returns nothing. This is the volume on the netapp, mounted on the sun box: idsmajor:root:/mnt/etc>mount -p | grep /tmp/a sanihome:/vol/nfs_archive - /tmp/a nfs - no rw idsmajor:root:/mnt/etc>ls -l /tmp/a | head total 81288 drwxr-xr-x 2 ids users 344064 Dec 19 05:29 apr_1995 drwxr-xr-x 2 ids users 393216 Dec 19 05:31 apr_1996 drwxr-xr-x 2 ids users 3989504 Dec 19 05:51 apr_1997 drwxr-xr-x 2 ids users 114688 Dec 19 05:52 aug_1994 drwxr-xr-x 2 ids users 380928 Dec 19 05:53 aug_1995 drwxr-xr-x 2 ids users 409600 Dec 19 05:55 aug_1996 drwxr-xr-x 2 ids users 4227072 Dec 19 06:16 aug_1997 drwxr-xr-x 2 ids users 282624 Dec 19 06:18 dec_1994 drwxr-xr-x 2 ids users 290816 Dec 19 06:19 dec_1995 idsmajor:root:/mnt/etc>ls -als /tmp/a/* | head -20 0 lrwxrwxrwx 1 ids users 29 Dec 7 16:34 /tmp/a/dec_1997 -> /archive/nfs_archive/dec_1997 0 lrwxrwxrwx 1 ids users 29 Dec 7 23:37 /tmp/a/nov_1997 -> /archive/nfs_archive/nov_1997 0 lrwxrwxrwx 1 ids users 29 Dec 8 01:05 /tmp/a/oct_1997 -> /archive/nfs_archive/oct_1997 0 lrwxrwxrwx 1 ids users 29 Dec 8 01:54 /tmp/a/sep_1997 -> /archive/nfs_archive/sep_1997 /tmp/a/apr_1995: total 688 680 drwxr-xr-x 2 ids users 344064 Dec 19 05:29 . 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. /tmp/a/apr_1996: total 784 776 drwxr-xr-x 2 ids users 393216 Dec 19 05:31 . 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. /tmp/a/apr_1997: total 7808 7800 drwxr-xr-x 2 ids users 3989504 Dec 19 05:51 . 8 drwxr-xr-x 44 ids users 4096 Dec 20 13:33 .. idsmajor:root:/mnt/etc> There were no problems with applications pulling files from these directories on the netapp on Friday, Dec 18. This volume is not mounted anywhere else. This is a production system -- nothing writes to the mount point. What happened Saturday morning at 5 AM? Why did all these directories get touched? Dave

3 2

tcp stack reset, why; and automating a fix?
by Dave Toal 20 Dec '99

20 Dec '99

Folks, Hey again, Jay. I've got a question about a tcp stack failure on one of the clustered 740's, that happened over the weekend. Gary Andrade sez: > The box would respond to ping (inbound), but any outbound attempts > failed. The outbound TCP stack was toast. Skip and I conferred on > the situation and the box was rebooted (problem resolved). > > The fail over to Wesson did not occur due to the inbound ping working, > the other server sensed Smith as working. I'm wondering: is it possible to configure clustering (smith and wesson are a pair of 740's) to detect tcp failure? There are no cluster-level error messages on smith. messages.0 ... Sat Dec 18 23:52:41 GMT [smith: rc]: DNS server for domain "saegis.com" not responding : Connection timed out. Sun Dec 19 00:00:00 GMT [smith: statd]: 12:00am up 29 days, 21:18 138103986 NFS ops, 0 CIFS ops, 0 HTTP ops And this is the reboot: [appworx@:/smith/spool/etc]$ head messages Sun Dec 19 00:26:45 GMT [smith: rc]: System shut down with "reboot" command. Sun Dec 19 00:26:45 GMT [smith: cf_main]: Cluster monitor: takeover of partner disabled (local halt in progress) The web servers did show nfs failures while smith was having its problem: ... Dec 19 00:01:43 ww5 automountd[235]: server smith not responding Dec 19 00:01:43 ww5 last message repeated 6 times Dec 19 00:08:14 ww5 automountd[235]: server smith not responding Dec 19 00:08:15 ww5 last message repeated 6 times This server was rebooted as well, for the same reason -- stack failure. Can you suggest some possible reasons for the filer's tcp stack failure? We did have an incident last week where both web servers needed to be rebooted for the same reason -- tcp resets from stack overflow; the tentative theory at the moment is syn flood attack. But the netapp isn't exposed to the internet. If it's not possible to configure the filer to fail over on failed ping, then I'll script something. My second question: what do I need to sacrifice to the gods to get complete command-line rsh access? smith> ping ww5 ww5.saegis.com is alive smith> Connection closed by foreign host. [appworx@:/apps/appworxl]$ rsh smith 'sysconfig -r' | grep root Volume spool (root) [appworx@:/apps/appworx]$ rsh smith ping ww5 ping not found. Type '?' for a list of commands [appworx@:/apps/appworx]$ I could set up a test such that if nfs fails but the filer can still be pinged, then [reboot/fail over]. Feels like a kludge, though... not specific enough. I'd prefer to have the filers handle this on their own. Dave

2 1

Re: toasters and auto negotiation (off topic: Cabletron gripe)
by mds＠gbnet.net 18 Dec '99

18 Dec '99

On Fri 17 Dec, 1999, Bruce Walker <bmw(a)visgen.com> wrote: > Did you enjoy the cranky, confusing and decidedly non-orthogonal > telnet UI? That sad piece of work in my ESX1320 switch soured me Oh indeed, a joy. >-- End of excerpt from Bruce Walker -- -Mark ... an Englishman in London ...

1 0

RE: toasters and auto negotiation
by mds＠gbnet.net 18 Dec '99

18 Dec '99

On Fri 17 Dec, 1999, "Walsh, Warren (MN65)" <Walsh_Warren(a)htc.honeywell.com> wrote: > We recently converted our 330 and 540 from FDDI to 100BaseT. We found that > we had to manually force both the 100BaseT card in the toaster and the > specific port on our Cabletron Smart Switch 9000 to 100BaseT-FD. For the > 100BaseT card, it was simply changing the auto to 100tx-fd: > > ifconfig e5 `hostname`-e5 mediatype 100tx-fd netmask 255.255.248.0 > > Funny how that auto-negotiation thing never really works, and how much it > really affects performance. Funny, I was only talking with a friend today about how autonegotiation between Sun's and Ciscos works fine, and how Cabletron kit has such irritatingly non-functional autonegotiation in contrast. In my last job, running any number of Su's, SGI's and NetApp's using Cabletron switches the network guys and I always went hunting for the ports where the collisions were high and the autonegotiation had been left on, or turned back on.. As policy we decided to pin both ends to 100BaseTX-fd no-autonegotiation, because anything else was markedly less effective. This wasn't the only problem we had with Cabletron kit though - there were some horrors with the spanning tree reconfigurations, and pakcet fragmentation, and adjacent switches somehow bollixing sets of ports on other switches. Put me right off Cabletron as a networking equipment vendor I have to say. YMMV. I always quite liked FDDI: most of our filers were on FDDI and, perhaps because of the extra smarts in the cards, the performance was always pretty darned good. We even got our biggest machines their own Gigaswitch ports - though I never figured out if the cards (DEC cards in NetApp, DEC gigaswitch) went into the full-duplex mode that the DEC network engineers though they might be able to do when plugged straight into the Gigaswitch. Sure made cabling in the machine room easier using FDDI too. Until they put decent amounts of structured wiring in. > -warren > > Warren Walsh > Honeywell Technology Center >-- End of excerpt from "Walsh, Warren (MN65)" -- -Mark ... an Englishman in London ...

4 3

RE: toasters and auto negotiation
by Walsh, Warren (MN65) 17 Dec '99

17 Dec '99

Along these lines, we had some very interesting problems when we started migrating from FDDI to Fast Ethernet. Our filers were on FDDI, connected to a FDDI card in a Cabletron SS9000, which had a FDDI-Ethernet bridge. There were a number of SGI and HPs on the Ethernet backbone that had NFS mouting problems with the filers. The Suns and PCs were OK. We finally forced the MTU on the filers' FDDI interface to 1500, and the problem went away. That sure sounds like the Cabletron packet fragmentation problem you described. We've just finished replacing our older FDDI hubs (CTRN MMAC8s) with Fast Ethernet switches (CTRN SS6000), and changing the filers from FDDI to 100BaseT. Everything is now on one switched Ethernet network, and seems OK (knock, knock). -warren -----Original Message----- From: mds(a)gbnet.net [mailto:mds@gbnet.net] Sent: Friday, December 17, 1999 1:22 PM To: Walsh, Warren (MN65); toasters Subject: RE: toasters and auto negotiation On Fri 17 Dec, 1999, "Walsh, Warren (MN65)" <Walsh_Warren(a)htc.honeywell.com> wrote: > We recently converted our 330 and 540 from FDDI to 100BaseT. We found that > we had to manually force both the 100BaseT card in the toaster and the > specific port on our Cabletron Smart Switch 9000 to 100BaseT-FD. For the > 100BaseT card, it was simply changing the auto to 100tx-fd: > > ifconfig e5 `hostname`-e5 mediatype 100tx-fd netmask 255.255.248.0 > > Funny how that auto-negotiation thing never really works, and how much it > really affects performance. Funny, I was only talking with a friend today about how autonegotiation between Sun's and Ciscos works fine, and how Cabletron kit has such irritatingly non-functional autonegotiation in contrast. In my last job, running any number of Su's, SGI's and NetApp's using Cabletron switches the network guys and I always went hunting for the ports where the collisions were high and the autonegotiation had been left on, or turned back on.. As policy we decided to pin both ends to 100BaseTX-fd no-autonegotiation, because anything else was markedly less effective. This wasn't the only problem we had with Cabletron kit though - there were some horrors with the spanning tree reconfigurations, and pakcet fragmentation, and adjacent switches somehow bollixing sets of ports on other switches. Put me right off Cabletron as a networking equipment vendor I have to say. YMMV. I always quite liked FDDI: most of our filers were on FDDI and, perhaps because of the extra smarts in the cards, the performance was always pretty darned good. We even got our biggest machines their own Gigaswitch ports - though I never figured out if the cards (DEC cards in NetApp, DEC gigaswitch) went into the full-duplex mode that the DEC network engineers though they might be able to do when plugged straight into the Gigaswitch. Sure made cabling in the machine room easier using FDDI too. Until they put decent amounts of structured wiring in. > -warren > > Warren Walsh > Honeywell Technology Center >-- End of excerpt from "Walsh, Warren (MN65)" -- -Mark ... an Englishman in London ...

1 0

Re: toasters and auto negotiation
by Steve Armijo 17 Dec '99

17 Dec '99

On Fri, Dec 17, 1999 at 12:07:10PM -0600, Mark D Fowle wrote: > Lee, > > When I set the following: > > ifconfig e7 `hostname`-e7 netmask 255.255.255.0 > ifconfig e7 mediatype auto `hostname`-e7 netmask 255.255.255.0 remove the above line, mediatype shouldn't be needed when configging gigabit. > timezone US/Eastern > rc_toggle_basic > alttune e7 LinkNegotiation 1 > alttune e3 LinkNegotiation 1 remove the above 2 lines > alttune 1 LinkNegotiation 1 > rc_toggle_basic > route add default <mydefaultgateway> 1 > routed on once you make those edits try to reboot and see what happens. if that doesnt work , try removing the last alttune statement. it may be unnecessary and would appear to be the only one with correct syntax. -s -- Cue the music, fade to black, no such thing as no payback. -PWEI [ armijo(a)cs.unm.edu ]

1 0

Re: your mail
by Steve Armijo 17 Dec '99

17 Dec '99

On Thu, Dec 16, 1999 at 06:24:04AM -0600, Mark D Fowle wrote: > come up on line. My work > around at the present time is to pull the gigabit cable out of the flier then > putting it back on. This seems to > "wake-up" the connection. I have not been able to figure our exactly whats > going on and our network > Notice the 0.0.0.0 for adding > the default, "default" stopped working --- hmmm, haven't seen this before, interesting. i prefer to put the actual names in the route statement. the same goes for ifconfig, i really don't like the `hostname` kludge. > ---------rc file ---------- > hostname filer1 > ifconfig e7 `hostname`-e7 netmask 255.255.255.0 > ifconfig e7 mediatype auto `hostname`-e7 netmask 255.255.255.0 you shouldn't need a mediatype for gigabit. this second line seems extraneous. i don't see that it actually accomplishes anything. and if you pull up the man page for ifconfig you'll see something like: "auto" (Auto RJ-45 twisted-pair) which isn't really anything like gigabit. > route add 0.0.0.0 <our gateway> 1 > routed on > rc_toggle_basic > alttune e3 LinkNegotiation 1 how many gigabit cards do you have in this filer? also the format of this i think is wrong. i have found that the filers actually want the number of the card in order starting from 0. e3 would be 0 and e7 would be 1. so it you want to set LinkNegotiation for the gigabit card in slot 3 it would be alttune 0 LinkNegotiation 1. i have only ever seen it work in one situation, but as always YMMV. this could also be what is causing a hang... > rc_toggle_basic > ypset < our dns server> > rc_toggle_basic you leave your filer up in rc_toggle_basic mode? scary. -s -- Cue the music, fade to black, no such thing as no payback. -PWEI [ armijo(a)cs.unm.edu ]

3 2

Re: your mail
by Mark D Fowle 17 Dec '99

17 Dec '99

It does -- I think he didn't see the command in there twice - Mark tkaczma(a)gryf.net on 12/17/99 01:24:00 PM To: toasters@mathworks.com@INTERNET cc: (bcc: Mark D. Fowle/0V/Caterpillar) Subject: Re: your mail Retain Until: 01/16/2000 Retention Category: G90 - Information and Reports On Fri, 17 Dec 1999, Steve Armijo wrote: > this could also be what is causing a hang... > > > rc_toggle_basic > > ypset < our dns server> > > rc_toggle_basic > > you leave your filer up in rc_toggle_basic mode? scary. Is that right? I thought that the second rc_toggle_basic turned off the priviledged mode. Tom

1 0

RE: toasters and auto negotiation
by Walsh, Warren (MN65) 17 Dec '99

17 Dec '99

We recently converted our 330 and 540 from FDDI to 100BaseT. We found that we had to manually force both the 100BaseT card in the toaster and the specific port on our Cabletron Smart Switch 9000 to 100BaseT-FD. For the 100BaseT card, it was simply changing the auto to 100tx-fd: ifconfig e5 `hostname`-e5 mediatype 100tx-fd netmask 255.255.248.0 Funny how that auto-negotiation thing never really works, and how much it really affects performance. -warren Warren Walsh Honeywell Technology Center -----Original Message----- From: Mark D Fowle [mailto:Fowle_Mark_D@CAT.com] Sent: Thursday, December 16, 1999 6:24 AM To: toasters Cc: Bruce A Seelinger Subject: Has anyone experienced the following problem - When my F740 reboots it will not come up on line. My work around at the present time is to pull the gigabit cable out of the flier then putting it back on. This seems to "wake-up" the connection. I have not been able to figure our exactly whats going on and our network administrator has looked at the Cisco 5505 on a wsx5403 (a 3 port gigabit) -- Notice the 0.0.0.0 for adding the default, "default" stopped working --- ---------rc file ---------- #Auto-generated by setup Mon Oct 18 07:53:04 EDT 1999 hostname filer1 ifconfig e7 `hostname`-e7 netmask 255.255.255.0 ifconfig e7 mediatype auto `hostname`-e7 netmask 255.255.255.0 timezone US/Eastern route add 0.0.0.0 <our gateway> 1 routed on rc_toggle_basic alttune e3 LinkNegotiation 1 rc_toggle_basic ypset < our dns server> rc_toggle_basic savecore exportfs -av nfs on

4 4

RE: toasters and auto negotiation
by Mark D Fowle 17 Dec '99

17 Dec '99

I have to use auto for our mediatype with our gigabit -- if we try to force it to 1000tx it wont work ---- Walsh_Warren(a)htc.honeywell.com on 12/17/99 01:00:00 PM To: toasters@mathworks.com@INTERNET cc: (bcc: Mark D. Fowle/0V/Caterpillar) Subject: RE: toasters and auto negotiation Retain Until: 01/16/2000 Retention Category: G90 - Information and Reports We recently converted our 330 and 540 from FDDI to 100BaseT. We found that we had to manually force both the 100BaseT card in the toaster and the specific port on our Cabletron Smart Switch 9000 to 100BaseT-FD. For the 100BaseT card, it was simply changing the auto to 100tx-fd: ifconfig e5 `hostname`-e5 mediatype 100tx-fd netmask 255.255.248.0 Funny how that auto-negotiation thing never really works, and how much it really affects performance. -warren Warren Walsh Honeywell Technology Center -----Original Message----- From: Mark D Fowle [mailto:Fowle_Mark_D@CAT.com] Sent: Thursday, December 16, 1999 6:24 AM To: toasters Cc: Bruce A Seelinger Subject: Has anyone experienced the following problem - When my F740 reboots it will not come up on line. My work around at the present time is to pull the gigabit cable out of the flier then putting it back on. This seems to "wake-up" the connection. I have not been able to figure our exactly whats going on and our network administrator has looked at the Cisco 5505 on a wsx5403 (a 3 port gigabit) -- Notice the 0.0.0.0 for adding the default, "default" stopped working --- ---------rc file ---------- #Auto-generated by setup Mon Oct 18 07:53:04 EDT 1999 hostname filer1 ifconfig e7 `hostname`-e7 netmask 255.255.255.0 ifconfig e7 mediatype auto `hostname`-e7 netmask 255.255.255.0 timezone US/Eastern route add 0.0.0.0 <our gateway> 1 routed on rc_toggle_basic alttune e3 LinkNegotiation 1 rc_toggle_basic ypset < our dns server> rc_toggle_basic savecore exportfs -av nfs on

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