toasters

toasters@lists.teaparty.net

13531 discussions

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

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

17 Dec '99

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 timezone US/Eastern rc_toggle_basic alttune e7 LinkNegotiation 1 alttune e3 LinkNegotiation 1 alttune 1 LinkNegotiation 1 rc_toggle_basic route add default <mydefaultgateway> 1 routed on What this does during boot is it locks up (no data or link light on the gigabit) If I manually remove the cable and then reconnect it (A manual force) it appears that everything is ok then. Is the problem the alteon (sp?) card doing negotiation or something entirely different ? Mark Fowle IS/CAT-BCP Metahpase/Oracle/Unix Administration lrazo(a)netapp.com on 12/17/99 12:54:00 PM To: Walsh_Warren@htc.honeywell.com@INTERNET cc: toasters@mathworks.com@INTERNET (bcc: Mark D. Fowle/0V/Caterpillar) Subject: RE: toasters and auto negotiation Retain Until: 01/16/2000 Retention Category: G90 - Information and Reports Hi Warren, Were you using autonegotiation against full duplex? If so, that isn't going to work by the specs for auto-negotiation. I think the designers of the protocol assumed if your nic (or switch port) was too old to support autonegotiation, then it was to old to support full duplex. So auto <--> half works and auto <--> auto works but auto <--> full won't by specification. That is my understanding, at least. Feel free to correct me if I am wrong. --Lee On Fri, 17 Dec 1999, Walsh, Warren (MN65) 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. > > -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 > --- Lee Razo (lrazo(a)netapp.com) Network Appliance Europe Hoofddorp, Netherlands "We are going to thank our bottoms tonight just for being there" -Femi Kuti

1 0

RE:
by John Gaines 17 Dec '99

17 Dec '99

If you are using a CISCO switch, this may be the cause. You have your media type set to auto. Netapp and Cisco do not negotiate well together. My suggestion would be to force the NIC to full duplex and force the port on the switch also. Also, i have never used 0.0.0.0 to specify "default" before. I am also curious as to what LinkNegotiation does? John Gaines I2 > -----Original Message----- > From: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com]On Behalf Of Mark D Fowle > 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 >

3 2

RE:
by johnj.sasso＠ps.ge.com 17 Dec '99

17 Dec '99

We've had the same problem as well with our F740s w/ 100BT. This problem with autonegotiation is neither particular to NetApp nor Cisco. We have SGIs, Suns, and HPs that also have had problems with autonegotiation, and I've heard from others having similar problems with other non-Cisco network devices. The problem is that the autonegotation standard in IEEE (Cl. 28 of IEEE 802.3u, based on NWay scheme) is a bit vague, which results in vendors implementing autonegotiation in such a way that it tends to be incompatible with how other vendors implement it. An unfortunate fact of life. A good into to autonegotiation can be found at: http://cesdis.gsfc.nasa.gov/linux/misc/NWay.html As for using 0.0.0.0 for the default gateway, that should be perfectly acceptable. --john -----Original Message----- From: Dane Jasper [mailto:dane@sonic.net] Sent: Thursday, December 16, 1999 6:48 PM To: John Gaines; Mark D Fowle; toasters Subject: Re: On Thu, Dec 16, 1999 at 03:18:52PM -0600, John Gaines wrote: > If you are using a CISCO switch, this may be the cause. You have your media > type set to auto. Netapp and Cisco do not negotiate well together. My > suggestion would be to force the NIC to full duplex and force the port on > the switch also. Also, i have never used 0.0.0.0 to specify "default" > before. I am also curious as to what LinkNegotiation does? I've got an Extreme Networks Black Diamond switch, and our F230 won't auto-negotiate 100-BT-fd with that either. Of course, neither will our Cisco 7507. It's ironic that the two more important bits on my network won't negotiate their connection speeds, but lots of irrelevant little workstations will. -- Dane Jasper Sonic.net, Inc. (707)522-1000 mailto:dane@sonic.net http://www.sonic.net/ Key fingerprint = A5 D6 6E 16 D8 81 BA E9 CB BD A9 77 B3 AF 45 53

1 0

Thanks for the backup help
by Alan R. White 16 Dec '99

16 Dec '99

Many thanks to all those who responded to my questions about backup. In summary it would seem that if I'm going to have 500GB filesystems then nothing hokey is going to cut it - I need something to either manage a locally attached bunch of tape drives and an autoloader. The only viable alternative seems to be either dumps across rmt (or rsh) or NDMP to a host with a large bunch of tape drives in a larger library. Our enterprise backup product doesn't support any of scenarios yet. I need something cheap and cheerful to manage this for me. The dumps to tape are only for a complete filesystem recovery, we would run snapmirror to keep the users going while rebuilding a broken box. File level stuff I'll handle through a CIFS mount on an NT box where our backup client will run. This leads to 2 questions 1) Which cheap and cheerful product to take care of the dumps and which of the ways above? Remember the dumps are only for volume recovery. 2) Has anyone worked out what the right way to failback after cutting over to a snap mirror replica? I understand netapp are working to make it easier but right now it looks close to unworkable with large volumes of data. If there are clever answers here then would anyone take the risk of not having a volume level dump? TIA, Al

1 0

RE:
by Mark D Fowle 16 Dec '99

16 Dec '99

All negotiation is off (both filer and switch) - We did think of that first though. Mark Fowle Caterpillar/BCP anders.s.ljungberg(a)edt.ericsson.se on 12/16/99 08:11:00 AM To: Fowle_Mark_D@cat.com@INTERNET cc: (bcc: Mark D. Fowle/0V/Caterpillar) Subject: RE: Retain Until: 01/15/2000 Retention Category: G90 - Information and Reports Hi! Turn all negotiation off. ( filer and switch ( the switch has two types negotiation, flow control and negotiation, type "show neg" on the switch). On the filer use 1000fx ( or whatever media ) e5: flags=300043<UP,BROADCAST,RUNNING,TCPCKSUM,IPHDRCKSUM> mtu 1500 inet 147.214.9.21 netmask 0xffffff00 broadcast 147.214.9.255 ether 00:60:cf:20:18:3a (1000fx)<----- Godd luck Anders Ljungberg -----Original Message----- From: Mark D Fowle [mailto:Fowle_Mark_D@CAT.com] Sent: Thursday, December 16, 1999 1:24 PM 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

None
by Mark D Fowle 16 Dec '99

16 Dec '99

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

Fastest way to remove files
by Jeff Krueger 15 Dec '99

15 Dec '99

Does anyone know of a fast, safe way of deleting a large qtree on a NetApp? Has anyone tried the rc_toggle_basic command "rm" from the console? Will it remove files recursively? Do they go into snapshots? Is it a "good thing(tm)" to do? It seems like a waste to do a "rm -rf" over NFS... -- Jeff -- ---------------------------------------------------------------------------- Jeff Krueger E-Mail: jeff(a)qualcomm.com NetApp File Server Lead Phone: 858-651-6709 IT Engineering and Support Fax: 858-651-6627 QUALCOMM, Incorporated Web: www.qualcomm.com

8 9

Nfs or CIFS-problem
by Öberg Mats 14 Dec '99

14 Dec '99

Hi, we're currantly experiencing some very annoying problems with our netapp, apparently it's having a hard time mapping cifs-accounts against the nis-accounts. The errors we get are the following: Sun Dec 12 08:18:32 CET [mountd]: yp_next: clnt_call: RPC: Timed out Sun Dec 12 19:02:55 CET [CIFSPasswordCache]: yp_next: clnt_call: RPC: Timed out Mon Dec 13 09:22:18 CET [rc]: CIFS terminated with 255 open files from 1167 CIFS users Mon Dec 13 09:24:23 CET [rc]: CIFS terminate aborted due to a hung CIFS I/O operation. Shutdown the system using halt -d and report this incident to NetApp Anybody know what the problem is? I read a bug report on the now-site saying something about problems with more than 1000 entries in the yp-group-database, could this be it ??? Best regards Mats Oberg TietoEnator

2 1

Saves using Legato ClientPak for Netapp
by Scott Mikusko 14 Dec '99

14 Dec '99

Howdy, Question for anyone out there using Legato's Netapp ClientPak. I have installed the client software on an F760 filer and trying to run some backup tests to see how this all works. I have created some test filesystems on the filer, and set a client entry on the Networker server. When I go to run the group that has the filer client, it starts up rather slowly, tell me it's starting to do a full save, then seems to just sit there for ages. I have about 10 savesets configured in the client setup, but the server appears to try to start only a couple savesets one at a time. It doesn't load any tapes, or any other activity. It appears to create the initial db entries, but no savesets start up. Just seems to idle there doing nothing, and repeat the same messages: Dec 13 15:33:16 obsidian root: NetWorker Savegroup: (info) hyades:/vol/vol0/ivpn/system.rt/proxy.cluster no cycles found in media db; doing full save Dec 13 15:36:08 obsidian root: NetWorker Savegroup: (info) hyades:/vol/vol0/ivpn/system.rt/www.cluster no cycles found in media db; doing full save Anyone have any experience with the ClientPak? The tech_dialog at Legato appears to have nothing about this type of error, nor does NOW. I'm opening a ticket with Legato tomorrow (once they sort out my support contract). Any input appreciated. -Scott -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Scott T. Mikusko Scrape the clouds of rouge from his face, Systems Engineer and he's white as noise Concentric Network Corporation Internet Guerilla -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

2 1

Jump to page:

2026

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