toasters

toasters@lists.teaparty.net

13531 discussions

RE: adding second LRC to FC7 FC-AL shelves
by Norman, Paul 04 May '99

04 May '99

> -----Original Message----- > From: Jay Soffian [mailto:jay@cimedia.com] > Sent: Tuesday, May 04, 1999 9:40 AM > To: toasters(a)mathworks.com > Subject: adding second LRC to FC7 FC-AL shelves > > > Can someone from Netapp give me the run down on upgrading FC-AL > shelves for clustering. I've heard conflicting information. > > We have three FC-AL FC7 shelves that only have a single LRC card in > them. I know that for clustering, the shelves will need an additional > LRC card (for the second FC-AL loop). > > It is not clear to me what is involved in adding the LRC card. I don't > see this documented in the cluster conversion guide nor in the shelf > hardware guide. I have heard that this is a field procedure that > Netapp needs to perform and that after it is done, the shelves need to > be calibrated. I heard the down time for all of this is supposed to be > several hours. Try looking at the Fibre Channel StorageShelf Hardware Installation Guide, page 56, "Installing a Second LRC Card" http://now.netapp.com/knowledge/docs/hardware/fcshelf.pdf It is field installable. We prefer that NetApp SE does the install as the card is sometimes hard to seat properly. There is no calibration, but we have a recipe for the SEs to follow which calls out checking that all disks are visible from both "a" and "b" loop. This is really critical to do BEFORE you attempt any takeovers/givebacks. We prefer that NetApp SEs perform the Cluster conversion to insure that everything is set up correctly. The procedure takes 10 minutes per shelf. You should probably expect about 30 to 45 minutes for the upgrade to include time to add Cluster Interconnect and FC-AL adapters to each filer, then cable up the interconnect & "b" loops. We usually double estimates, so 1.5 to 2 hours should be set aside for this. Paul Norman, Product Manager Direct: (408) 367-3756 Network Appliance E-Mail: pnorman(a)netapp.com 2770 San Tomas Expressway Corp: (408) 367-3100 Santa Clara, CA 95051 Web: WWW.NetApp.Com

1 0

Re: Hardware for F330
by George Kahler 04 May '99

04 May '99

Greetings... sthaug(a)nethelp.no writes: -- snip -- snip -- > Questions: > > - Does anybody know of narrow disks that can be purchased today and which > will work with 4.3.3D2? (I have come to point that I no longer care if the > disks are Netapp approved - I just want to have a reasonable chance of the > disks working.) When Seagate discontinued the ST15230N drives, NetApp replaced them with Fujitsu Alegro M2954E. See if you can get these from your local dealer. I have few running in my F330 with NetApp Release 4.3.5D4. George UNIX Systems Administrator humans: (416) 736-5257 x.22699 Computing Services, York University machines: (416) 736-5830 Ontario, Canada, M3J-1P3 > > - We have a number of (used) DEC RZ29B 4 GB disks, fw revision 0007. Will > these work? > > - We feel that the F330 is more or less abandoned, and any kind of upgrade > with new disk shelves etc. is going to extremely expensive. Is this a > correct assessment? > > Steinar Haug, Nethelp consulting, sthaug(a)nethelp.no

1 0

snap trace
by Jay Soffian 03 May '99

03 May '99

Okay, this is on an F630 running a pretty old DOT (NetApp Release 4.3.4D5: Tue May 26 14:05:43 PDT 1998), so I don't expect any answers, but I thought I'd ask anyway. We just had this box stop passing traffic on it 1000fdx interface. I logged in on console and tried to cycle the 1000fdx interface and got a pretty strange message: whirlpool> ifconfig -a e2: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:f8:2f:6d (Twisted pair) f3: flags=43<UP,BROADCAST,RUNNING> mtu 4352 inet 192.168.254.250 netmask ffffff00 broadcast 192.168.254.255 ether 00:00:f8:bd:c6:04 (Dual Attach Fiber) e10: flags=60043<UP,BROADCAST,RUNNING,TCPCKSUM,IPHDRCKSUM> mtu 1500 inet 192.168.250.250 netmask ffffff00 broadcast 192.168.250.255 ether 00:60:cf:20:48:61 (1000fx) lo: flags=9<UP,LOOPBACK> mtu 1536 inet 127.0.0.1 netmask ff000000 broadcast 127.0.0.1 whirlpool> ifconfig e10 down Couldn't do snap trace, one already active We ended up rebooting the box and it came back up okay. There was no snapshot running. The filer wasn't doing anything out of the ordinary or under heavy load. Nothing in the logs either. It looked fine, except it just stopped passing traffic. The interface was not pingable. I did not try cycling the port on the the switch it's plugged into (a Lucent Cajun P550). The box had been up for over 183 days w/o a single problem. Any idea what that message means? Anyone seen a NetApp just stop passing traffic like this on an 1000fdx interface? Thanks. j. -- Jay Soffian <jay(a)cimedia.com> UNIX Systems Administrator 404.572.1941 Cox Interactive Media

2 1

Re: Problems with CIFS and 5.3.1
by Joan Pearson 03 May '99

03 May '99

In 5.3 support for Unicode was added. CIFS can only access directories that have been converted to the new Unicode format. Directories that are not in Unicode format are converted automatically to Unicode format when first accessed by CIFS. But since snapshots are read only, directories in snapshots cannot be converted and are not accessible from CIFS. Before 5.3, there were two directory formats: those accessed by CIFS (cifs format) and those never accessed by CIFS(non-cifs format). The first time CIFS accessed a directory it would be converted to CIFS format. Non-cifs format directories in snapshots were not accessible from CIFS. In 5.3, both cifs-format and non-cifs format directories are converted to unicode format when accessed by CIFS. Directories created by CIFS are created in unicode format. There is an option wafl.create_ucode that can be used to create unicode directories by default from NFS. Refer to the System Administration Guide for more information. Joan Pearson At 11:08 AM 5/3/99 , you wrote: >I upgraded to 5.3.1 this morning. After the upgrade I noticed I was unable >to access any snapshots via CIFS. The snapshots would show up in Explorer >but when I tried to access the snapshots, even logged in as root, I received >a error message "Access is Denied". > >I tried several ideas to resolve the issue without any luck. I then ran >"cifs testdc" and received the following message: > >_______________________________________________________________ >Using Established configuration >Current Mode of NBT is H Mode > >Netbios scope "" >Registered names... > NEWTOASTER < 0> WINS Broadcast > NEWTOASTER < 3> WINS Broadcast > NEWTOASTER <20> WINS Broadcast > OSSRTPPROD < 0> WINS Broadcast > OSSRTPPROD < 3> WINS Broadcast > OSSRTPPROD <20> WINS Broadcast > >Testing Primary Domain Controller >found 1 addresses > >Testing all Domain Controllers >found 3 addresses >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.14...192.168.255.14 is alive >found DC OSSRTPNT40 at 192.168.255.4 >Not able to communicate with DC 192.168.255.4 >found DC OSSRTPBDC at 192.168.255.14 >______________________________________________________ > >Thinking the problem was on my end, I terminated CIFS, deleted the filer on >my PDC and readded the filer. I rebooted the filer and reran "cifs setup" >and kept receiving a error message stating "PDC is not active" and cifs >setup would terminate. > > I finally dropped back to 5.21. > >I reran "cifs testdc" and received the following: >____________________________________________________________________________ >____ >testfiler> cifs testdc >Using Established configuration >Current Mode of NBT is H Mode > >Netbios scope "" >Registered names... > TESTINGFILER < 0> WINS > TESTINGFILER < 3> WINS > TESTINGFILER <20> WINS > OSSRTPPROD < 0> WINS > OSSRTPPROD < 3> WINS > OSSRTPPROD <20> WINS > >Testing Primary Domain Controller >found 1 addresses >trying 192.168.255.4...192.168.255.4 is alive >found PDC OSSRTPNT40 > >Testing all Domain Controllers >found 3 addresses >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.14...192.168.255.14 is alive >found DC OSSRTPBDC >found DC OSSRTPNT40 >found DC OSSRTPBDC >____________________________________________________________________________ >____________ > > >Finally, I reran cifs setup without a problem. I was able to get back into >the snapshots. Has anyone else came across a similar issue with 5.3.1 and if >so how did you resolve? >

1 0

Problems with CIFS and 5.3.1
by Mike Ball 03 May '99

03 May '99

I upgraded to 5.3.1 this morning. After the upgrade I noticed I was unable to access any snapshots via CIFS. The snapshots would show up in Explorer but when I tried to access the snapshots, even logged in as root, I received a error message "Access is Denied". I tried several ideas to resolve the issue without any luck. I then ran "cifs testdc" and received the following message: _______________________________________________________________ Using Established configuration Current Mode of NBT is H Mode Netbios scope "" Registered names... NEWTOASTER < 0> WINS Broadcast NEWTOASTER < 3> WINS Broadcast NEWTOASTER <20> WINS Broadcast OSSRTPPROD < 0> WINS Broadcast OSSRTPPROD < 3> WINS Broadcast OSSRTPPROD <20> WINS Broadcast Testing Primary Domain Controller found 1 addresses Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPNT40 at 192.168.255.4 Not able to communicate with DC 192.168.255.4 found DC OSSRTPBDC at 192.168.255.14 ______________________________________________________ Thinking the problem was on my end, I terminated CIFS, deleted the filer on my PDC and readded the filer. I rebooted the filer and reran "cifs setup" and kept receiving a error message stating "PDC is not active" and cifs setup would terminate. I finally dropped back to 5.21. I reran "cifs testdc" and received the following: ____________________________________________________________________________ ____ testfiler> cifs testdc Using Established configuration Current Mode of NBT is H Mode Netbios scope "" Registered names... TESTINGFILER < 0> WINS TESTINGFILER < 3> WINS TESTINGFILER <20> WINS OSSRTPPROD < 0> WINS OSSRTPPROD < 3> WINS OSSRTPPROD <20> WINS Testing Primary Domain Controller found 1 addresses trying 192.168.255.4...192.168.255.4 is alive found PDC OSSRTPNT40 Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPBDC found DC OSSRTPNT40 found DC OSSRTPBDC ____________________________________________________________________________ ____________ Finally, I reran cifs setup without a problem. I was able to get back into the snapshots. Has anyone else came across a similar issue with 5.3.1 and if so how did you resolve?

1 0

Re: Bypassing rc
by Jason D. Kelleher 03 May '99

03 May '99

In message <Pine.BSF.4.10.9905011132060.249-100000(a)schizo.cdsnet.net>, Jaye Mathisen writes: > > >While I sit on hold at netapp, I'm just wondering if anybody's out there. > >I have a filer running 5.3, and I was trying one of the tips on the Netapp >web page about making one of the interfaces a primary for CIFS, by >rearranging things in /etc/rc, and while all I did was move one of >the 2 ifconfig lines, something is boobered up now, and the filer dies >with: > >Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. >Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. >Sat May 1 11:27:52 PDT [rc]: timed: time daemon started >Sat May 1 11:27:52 PDT [Java Thread]: TimeDaemon: Can't connect to time se >rver >'10.0.1.3' >NFS server is running. >timed not found. Type '?' for a list of commands >quota: vol0: run 'quota off' before 'quota on'. > >PANIC: ../common/nbt/nbns_receive.c:207: Assertion failure. on Sat May 1 1 >8:27: >53 1999 > >version: NetApp Release 5.3: Thu Apr 1 11:18:39 PST 1999 >cc flags: 1 >dumping core: ..................................................Old core pr >esent > on disk --- not dumped. > > > >Anyway, I guess I'll try some floppies, and see how far I get while I >wait... > >Any tips appreciated. Stay away from 5.3 w/out speaking to tech support first. Not sure about 5.3.1, but it took three "D" releases to get 5.3 working properly for me. And since the "Closed Bugs by fix release" for 5.3.1 on NOW looks shorter than the list of bugs fixed in my 5.3Dx release, I'd be real careful. The "Bugs" section in NOW has gotten alot more usable. (In fact, all of NOW has gotten better recently.) But I still want a "Known Bugs by release". jason

1 0

Hardware for F330
by Jay Orr 02 May '99

02 May '99

Hi all! I was wondering if anyone can help. We are a small shop with 2 F330's with 2 disk cabinets on each one. We were looking into adding another tray on each, but were told by NetApps that they are no longer available. All I'm looking for is to upgrade the memory, add another scsi controller, and another tray (is that asking TOO MUCH???). Questions: Can I use off the shelf memory (and what kind)? What about SCSI controllers? Where can I get disk trays? Could we instead replace the drives with 9G or 18G drives (and what model would we use)? NetApps solution is to spend $60k+ to upgrade, and all we need is another 10G - 20G. The current system works fine, isn't overused, and could handle the expansion IF WE CAN FIND THE COMPONENTS... Thanks for the help. By the by, I've been looking for a toaster FAQ, is there one? ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

6 5

restore annoyance
by kg 01 May '99

01 May '99

Anyone notice that restore operations will fail if there isn't a /etc/tmp on the destination volume? Fine most of the time, but rather annoying to have to create a /etc on non-root volumes.... ..kg..

1 0

Bypassing rc
by Jaye Mathisen 01 May '99

01 May '99

While I sit on hold at netapp, I'm just wondering if anybody's out there. I have a filer running 5.3, and I was trying one of the tips on the Netapp web page about making one of the interfaces a primary for CIFS, by rearranging things in /etc/rc, and while all I did was move one of the 2 ifconfig lines, something is boobered up now, and the filer dies with: Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. Sat May 1 11:27:52 PDT [rc]: timed: time daemon started Sat May 1 11:27:52 PDT [Java Thread]: TimeDaemon: Can't connect to time server '10.0.1.3' NFS server is running. timed not found. Type '?' for a list of commands quota: vol0: run 'quota off' before 'quota on'. PANIC: ../common/nbt/nbns_receive.c:207: Assertion failure. on Sat May 1 18:27: 53 1999 version: NetApp Release 5.3: Thu Apr 1 11:18:39 PST 1999 cc flags: 1 dumping core: ..................................................Old core present on disk --- not dumped. Anyway, I guess I'll try some floppies, and see how far I get while I wait... Any tips appreciated.

1 0

NOW profile 'Protocol Licenses'
by kg 01 May '99

01 May '99

Any chance that cluster licenses could get listed as well? http://now.netapp.com/cgi-bin/profile/protlicenses ..kg..

2 1

Re: Hardware for F330
by Jay Orr 01 May '99

01 May '99

Ok, so if you can humor a newbie for a few more questions I'd appreciate it. I have a similar configuration with a tray off each slot. I can dasy-chain on more trays? Also, could I use a generic hot-swap SCSI cabinet? And if I put 9 gig drives in them, any special ones? Also, I notice on the sysconfig that both slot0 and 9 use Qlogic ISP 1020A scsi controllers. As best as I can see those are discontinued, but they're standard PCI scsi controllers -- anyone dropped in another PCI scsi controller and see what it does? And what's with your CPU speed? On Fri, 30 Apr 1999, Luke Gain wrote: > I think the scsi card was made by netapp. so your only option may be the > slot0 controller. > > Here is my 330 config fwiw.. > (check out the cpu speed :) > -Luke > > > sysconfig -v > NetApp Release 4.3.4: Wed Apr 22 16:25:06 PDT 1998 > System ID: 0016781651 > slot 0: System Board 192 MHz (NetApp System Board I rev-b) > Firmware release: 1.6_i > Memory Size: 256 MB > slot 0: SCSI Host Adapter 0 (QLogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > slot 0: Ethernet Controller e0 > MAC Address: 00:a0:98:00:08:ce (100tx-fd) > slot 6: NVRAM (NetApp NVRAM I) > Revision: D1 > Serial Number: 4435 > Memory Size: 8 MB > Battery 1 Status: 100% (3.18v) > Battery 2 Status: 100% (3.18v) > slot 9: Dual SCSI Host Adapter (NetApp SCSI Adapter I) > SCSI Host Adapter 9a (Qlogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > SCSI Host Adapter 9b (Qlogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > > > > > > Yes, that helps alot! Any idea on adding another scsi card? > > > > > > On Fri, 30 Apr 1999, Luke Gain wrote: > > > > > Jay, > > > > > > I have found that standard Kingston 72pin parity memory works fine in > > > both my 220 and 330. You should be able to string a 3rd shelf > > > off of the controller on the motherboard. Don't know where to obtain the > > > Digital Storageworks shelf (Tech Data used to sell them). > > > Corprate Systems is normally a good source for drives. (www.corpsys.com) > > > > > > Hope this helps. > > > > > > -Luke > > > > > > > > > > > > > > Hi all! > > > > > > > > I was wondering if anyone can help. We are a small shop with 2 F330's with > > > > 2 disk cabinets on each one. We were looking into adding another tray on > > > > each, but were told by NetApps that they are no longer available. > > > > > > > > All I'm looking for is to upgrade the memory, add another scsi controller, > > > > and another tray (is that asking TOO MUCH???). Questions: Can I use off > > > > the shelf memory (and what kind)? What about SCSI controllers? Where can I > > > > get disk trays? Could we instead replace the drives with 9G or 18G drives > > > > (and what model would we use)? > > > > > > > > NetApps solution is to spend $60k+ to upgrade, and all we need is another > > > > 10G - 20G. The current system works fine, isn't overused, and could handle > > > > the expansion IF WE CAN FIND THE COMPONENTS... > > > > > > > > Thanks for the help. By the by, I've been looking for a toaster FAQ, is > > > > there one? > > > > > > > > ----------- > > > > Fujitsu - Nexion, St. Louis, MO > > > > Jay Orr (314) 579-6517 > > > > > > > > > > > > > > > > > > ----------- > > Fujitsu - Nexion, St. Louis, MO > > Jay Orr (314) 579-6517 > > > > > > ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

4 4

Re: Hardware for F330
by sirbruce＠ix.netcom.com 01 May '99

01 May '99

On 04/30/99 18:53:15 you wrote: > >On Fri, Apr 30, 1999 at 12:34:30PM -0500, Jay Orr wrote: >> And what's with your CPU speed? > >Luke has bumped up his CPU speed using an overdrive processor. This is >pretty simple to do, but NetApp claims that bus bandwidth, not CPU speed is >the limiting factor in the F330/230/220 series of filers. It's not simply a claim; it's true. >NetApp says that >there is no benefit to an overdrive, I don't think they would claim _no_ benefit. Just that the benefit will be very minor in the majority of cases, and not worth the extra cost. Plus, since there are all sorts of reliability and timing issues that are changed by changing the processor speed, there configuration is likely to be less reliable. That being said, if your environment frequently experiences an NFS ops mix that is CPU-heavy and bus-light, a faster CPU could provide slightly better response times and peak operations. But this is a very unlikely situation. I suppose RAID reconstruction in the event of failure is probably noticeably faster, although you're probably hitting limits on the bus bandwidth as well once you exceed 90-120 MHz. The extra CPU might help the filer be a little more responsive to regular ops during reconstruction. >and I suspect that support is likely to >blame it for any trouble you have in the future. I suspect you're right. I'm surprised there haven't been any firmware problems already. Bruce

1 0

netapp meets bugtraq. again.
by fubar＠mathworks.com 01 May '99

01 May '99

Ok, so I don't have the docs handy.. but if you have an "-access" options, it just seems kinda intuitive to me that you might actually *USE IT*. But maybe it's just me. ------- Start of forwarded message (RFC 934 encapsulation) ------- From: pashdown(a)XMISSION.COM (Pete Ashdown) Subject: Network Appliance NFS filer root hole Date: 28 Apr 1999 15:58:45 -0400 Organization: Bugtraq List Message-ID: <199904281658.KAA14944(a)slack.xmission.com> Reply-To: Pete Ashdown <pashdown(a)XMISSION.COM> For Network Appliance NFS filer release: NetApp Release 5.2.1: Thu Dec 31 12:56:45 PST 1998 Following "Example 1" on page 136 of the "System Administrator's Guide" for the Network Appliance results in a gaping hole. In this example, they explain that "the following line exports the root directory of the default filter volume to the administration host with root privileges." /vol/vol0 -root=adminhost This is all fine and good, but it also exports to the WORLD with root privileges. You have to specify either "-access", or "-rw", or "-ro" in addition to "-root" for this not to happen. When I mentioned this to my NetApp SE, I was met with quizzical looks, but no code-update or patch. Thusly, I sent it to bugtraq. ------- End -------

4 6

RE: Digital UNIX clients -- no non-root access
by Muhlestein, Mark 01 May '99

01 May '99

I'm not sure what your problem is, but I can verify that internally here at NetApp we use DU 4.0D (rev 878) extensively on several Alpha machines against multiple filers with no issues. We have also run with 4.0E. What version of the filer software are you running? Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: sirbruce(a)ix.netcom.com [mailto:sirbruce@ix.netcom.com] Sent: Monday, April 26, 1999 6:39 PM To: jgaski(a)WPI.EDU; toasters(a)mathworks.com Subject: Re: Digital UNIX clients -- no non-root access On 04/26/99 21:11:27 you wrote: >I have an open call with Network Appliance, but they have said that >there must be something strange in Compaq's implementation of the NFS >client. The same error occurs on Digital UNIX 4.0D pl3, 4.0E pl1, and >5.0 beta. It occurs whether the mount is soft or hard, udp or tcp, >nfsv3 or nfsv2. > >It seems like such a large, ubiquitous error that I can't believe >noone would have seen it before. I thought that Digital UNIX support >was standard, and I can't imagine how all of our Alpha clients could >be non-standard in such a way. You'd be surprised. Lots of vendors have little quirks in their implementation that, while they happen to work okay with one server, are really out of spec and may not work with another. However, I know that Digital Unix *used* to work, but the last I ever saw personally work was 4.0C. So either they've changed something, or something in the new Netapp release fixed/broke something. Bruce

4 5

Re: Hardware for F330
by Jason D. Kelleher 30 Apr '99

30 Apr '99

In message <3729EEE9.AB4CD895(a)netapp.com>, Jerry Talkington writes: >Jay Orr wrote: >> >> Hi all! >> >> I was wondering if anyone can help. We are a small shop with 2 F330's wit >h >> 2 disk cabinets on each one. We were looking into adding another tray on >> each, but were told by NetApps that they are no longer available. > >I can't comment on the availability, but the F330 only supports two >shelves... Try again. That might be what it "officially" supports now, but we bought ours w/ two shelves and NetApp sold us two more. It's running w/ 4 shelves full of 4GB drives just fine. jason

2 1

Unable to log onto NetApp machine
by michael＠applix.com 30 Apr '99

30 Apr '99

We've got a NetApp machine at our site (F330, NetApp Release 4.3.1: Wed Jan 21 02:57:32 PST 1998) that we can't log in to. It's up and running fine, and we can use rsh to run commands (like version or exportfs), but if I try to telnet to the box all the passwords I try don't work. On the system that's controling that particular server (Digital Unix), the etc directory that's mounted from the filer had no password file in it, and even after copying the passwd file from another NetApp box into the etc directory I'm still unable to get in. Do I need to reboot the filer, or is there some magic I can perform to set the password? There doesn't appear to be a passwd command, and checking the options command doesn't show anything that looks like it might apply.... Thanks in advance, -Mike -- Michael Steeves, System and Network Administrator (msteeves(a)applix.com) "I've got to start listening to those quiet, nagging doubts." -- Calvin and Hobbes

5 6

Re: Hardware for F330
by Jay Orr 30 Apr '99

30 Apr '99

Yes, that helps alot! Any idea on adding another scsi card? On Fri, 30 Apr 1999, Luke Gain wrote: > Jay, > > I have found that standard Kingston 72pin parity memory works fine in > both my 220 and 330. You should be able to string a 3rd shelf > off of the controller on the motherboard. Don't know where to obtain the > Digital Storageworks shelf (Tech Data used to sell them). > Corprate Systems is normally a good source for drives. (www.corpsys.com) > > Hope this helps. > > -Luke > > > > > > Hi all! > > > > I was wondering if anyone can help. We are a small shop with 2 F330's with > > 2 disk cabinets on each one. We were looking into adding another tray on > > each, but were told by NetApps that they are no longer available. > > > > All I'm looking for is to upgrade the memory, add another scsi controller, > > and another tray (is that asking TOO MUCH???). Questions: Can I use off > > the shelf memory (and what kind)? What about SCSI controllers? Where can I > > get disk trays? Could we instead replace the drives with 9G or 18G drives > > (and what model would we use)? > > > > NetApps solution is to spend $60k+ to upgrade, and all we need is another > > 10G - 20G. The current system works fine, isn't overused, and could handle > > the expansion IF WE CAN FIND THE COMPONENTS... > > > > Thanks for the help. By the by, I've been looking for a toaster FAQ, is > > there one? > > > > ----------- > > Fujitsu - Nexion, St. Louis, MO > > Jay Orr (314) 579-6517 > > > > > > ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

1 0

Re: netapp meets bugtraq. again.
by Jason D. Kelleher 30 Apr '99

30 Apr '99

In message <Pine.LNX.4.04.9904291507120.12868-100000(a)phaeton.cebaf.gov>, Bry an Hess writes: > >On Thu, 29 Apr 1999 tkaczma(a)gryf.net wrote: >> >> On Wed, 28 Apr 1999, Kendall Libby wrote: >> >> > ------- Start of forwarded message (RFC 934 encapsulation) ------- >> > From: pashdown(a)XMISSION.COM (Pete Ashdown) >> > >> > /vol/vol0 -root=adminhost >> > >> > This is all fine and good, but it also exports to the WORLD with root >> > privileges. >> >> Are you sure it exports to all with root priviledges or does it just >> export to all read/write but as root only to adminhost? > > >It doesn't export root privs to all, but just exporting read/write to all >machines is scary enough. If I am a malicious user, I can find the mount >points easily enough, mount the filesystems, and create user accounts on >my machine to match any uid on the filer. After that, who needs root privs >except for files owner by uid 0? > >--Bryan This is not a "netapp meets bugtraq" issue. It's an "every NFS server configured by someone who doesn't know what he's doing meets bugtraq" issue. Security is dependent on the competence of the administrator. Of course, here in the USA, no one is responsible for their own actions. So we should report Linux, SunOS, Solaris, HP-UX, AIX, Free BSD, NetBSD, etc... to bugtraq right away!!! And we'll all sue too!!! Ooops, got way too sarcastic at the end there... jason

2 1

Re: Unable to log onto NetApp machine
by sirbruce＠ix.netcom.com 30 Apr '99

30 Apr '99

On 04/29/99 15:39:16 you wrote: >Hmm, this is what I thought of at first, but when I tried it in the lab, >it did not work. I did get it to work (sort of) bye doing #rsh filer >rc_toggle_basic; passwd . You should not use rsh to rc_toggle_basic to get at commands that are normally not accessible via rsh. There are reasons why they aren't rsh-able. Bruce

1 0

RE: How to use CIFS if PDC not on same lan?
by Muhlestein, Mark 30 Apr '99

30 Apr '99

NT requires you to see the PDC in certain cases, because the BDCs are basically read-only replicas of the PDC. One of those cases is setting the machine password, which is done when the server (NT or filer) is installed, then once a week (Sunday morning at 2 or so). You will have to make the PDC visible at least temporarily to install the filer. After that, it will keep pestering you because it won't be able to do the periodic machine account password update. This is really an issue with NT networking. You would have the same problem trying to install an NT member server in the same situation. There are probably some reasonable ways around this problem; your situation is not that unusual. The details depend on what you are trying to accomplish. You should probably work with customer support to see what makes most sense. You will also probably want 5.3, since it preferentially connects to domain controllers based on the IP address, which would mean it would always use the local BDC except for changing the passwords. By the way, you'll find that if your Windows clients cannot see the PDC they will not be able to change their login passwords from their workstations for the same reason: they have to be able to contact the PDC to do that. Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 29, 1999 1:20 PM To: Puneet Anand Cc: toasters(a)mathworks.com Subject: Re: How to use CIFS if PDC not on same lan? The PDC is not IP reachable from the filer. The filer is on a private backbone, serving NFS/CIFS clients off secondary ethernet interfaces. The BDC happens to be one of those clients. And it has 2 interfaces... On Thu, 29 Apr 1999, Puneet Anand wrote: > Is the PDC registering with the same WINS ? Hopefully yes. > We do need PDC for installation.If this is ONTAP 5.1 or later ,you can > run cifs testdc command with the following options to troubleshoot. > > cifs testdc <wins_ip> <domain_name> <filer_name> > > > -Puneet > __________________ > > > Jaye Mathisen wrote: > > > > I have 2 sites. Site B has a BDC for a domain, and the Netapp. > > Site A connected via T1 has the PDC. > > > > When I try to run CIFS setup, it gets to the part about needing to reach > > the PDC and can't find it, so it aborts. > > > > I'm not sure why it can't just do whatever it needs to do with the BDC > > right there (running WINS)... > > > > Perhaps I need to add some key to WINS for the netapp to see it? >

1 0

Procom Netforce
by Kevin W. Brown 30 Apr '99

30 Apr '99

I just got back from ISPCon, where I saw the Procom Netforce filer, and I was wondering if anyone here has experience with this product. Specifically, they have a 100G fault-tolerant version for around $30K. It has two host "controllers", which are basically Pentium II/III machines that load balance and automatically fail over. It has a journaling file system and snapshot backup capability. We are looking to purchase some new network attached (NFS) storage, and this looks like it just might fit the bill. Thganks! -------------------------------------------------------------------------- Kevin W. Brown | 4080 Water Tank Rd. | E-Mail: kevin(a)qis.net Quantum Internet Services | Manchester, MD 21102 | Voice: 410-239-6920 --------------------------------------------------------------------------

1 0

RE: How to use CIFS if PDC not on same lan?
by Sam Schorr 29 Apr '99

29 Apr '99

The fun question is, what if there is no domain controller available due exactly to the configuration Jaye is trying to install - a separate, "back channel" subnet that is not part of the domain. How would the filers use CIFS then? Install as workstation and do authentication with every file request off a local pwd file? -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 29, 1999 1:20 PM To: Puneet Anand Cc: toasters(a)mathworks.com Subject: Re: How to use CIFS if PDC not on same lan? The PDC is not IP reachable from the filer. The filer is on a private backbone, serving NFS/CIFS clients off secondary ethernet interfaces. The BDC happens to be one of those clients. And it has 2 interfaces... On Thu, 29 Apr 1999, Puneet Anand wrote: > Is the PDC registering with the same WINS ? Hopefully yes. > We do need PDC for installation.If this is ONTAP 5.1 or later ,you can > run cifs testdc command with the following options to troubleshoot. > > cifs testdc <wins_ip> <domain_name> <filer_name> > > > -Puneet > __________________ > > > Jaye Mathisen wrote: > > > > I have 2 sites. Site B has a BDC for a domain, and the Netapp. > > Site A connected via T1 has the PDC. > > > > When I try to run CIFS setup, it gets to the part about needing to reach > > the PDC and can't find it, so it aborts. > > > > I'm not sure why it can't just do whatever it needs to do with the BDC > > right there (running WINS)... > > > > Perhaps I need to add some key to WINS for the netapp to see it? >

1 0

The great online RMA experiment
by Graham C. Knight 29 Apr '99

29 Apr '99

I had a few failed disks hanging around that I needed to get RMA's for. So I decided to experiment and use the online RMA feautre on the NOW page: http://now.netapp.com/products/rma/rma.shtml Within 5 minutes of submitting 2 RMA's I had an email with the RMA number in my box. I'd call the experiment a great success! :-) Very impressive. Graham

1 0

How to use CIFS if PDC not on same lan?
by Jaye Mathisen 29 Apr '99

29 Apr '99

I have 2 sites. Site B has a BDC for a domain, and the Netapp. Site A connected via T1 has the PDC. When I try to run CIFS setup, it gets to the part about needing to reach the PDC and can't find it, so it aborts. I'm not sure why it can't just do whatever it needs to do with the BDC right there (running WINS)... Perhaps I need to add some key to WINS for the netapp to see it?

2 2

RE: SNMP traps (+ other monitoring issues)
by Richard Moore 29 Apr '99

29 Apr '99

Keith, We have currently set up to trap on 'miscGlobalStatus' as it seemed a reasonable starter - The MIB description is a little woolly however : "This indicates the overall status of the appliance. The algorithm to determine the value uses both hardware status (e.g. the number of failed fans) and volume status (e.g. number of volumes that are full). This may change...etc" This has values of other(1) unknown(2) ok(3) nonCritical(4) critical(5) nonRecoverable(6) Is there a more detailed explanation of what event will trigger what status ? We are considering configuring our notification system to respond according to the value; i.e. email/phone on (4), 24hr page(5), print CV(6). On testing, when we switch off 1 power supply out of 2, we get a 'critical'(5) trap. ( is 'nonCritical' more appropriate ?) Other traps to possibly have set up as a 'starter' set : OverTemperature, FailedFanCount, FailedPowerSupplyCount, dfPerCentKBytesCapacity. Other monitoring issues : We have configured syslog.conf to send message errors to 'messages.err', critical to 'messages.crit' etc. hoping to be able to parse these files to enable an appropriate response according to severity. However, when doing the same power supply pull, we only get a message in the 'info' file. (This is deemed of sufficient importance however to trigger autosupport email.) So it appears we have to match on the message wording itself - an incremental approach of matching on all known potential error messages - time consuming. In lieu of better classification of messages, has anybody got a list of known filer error messages, with severity level ? How do other users monitor filers ? Regards, Richard Moore NortelNetworks Harlow UK

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