toasters

toasters@lists.teaparty.net

13531 discussions

RE: Netware on a Filer???
by Benn, Paul 26 Sep '01

26 Sep '01

Hello Todd, NetWare can not be run on a filer nor does the filer support NCP. You can, however, integrate the filer into a NetWare environment by configuring the client machines with dual redirectors (NetWare and CIFS). Read more here: http://www.netapp.com/tech_library/3053.html <http://www.netapp.com/tech_library/3053.html> Cheers, Paul Benn Network Appliance -----Original Message----- From: Todd Phillips [mailto:toddp@iarchive.com] Sent: Tuesday, September 25, 2001 7:46 PM To: 'toasters(a)mathworks.com' Subject: Netware on a Filer??? Who's done it? How'd you do it? How's it work?? Thanks. Todd

2 1

Filer Problem
by Rahul Kumar 26 Sep '01

26 Sep '01

Hi All, I have a little problem here wherin i can use your help.. 1. Solaris systems in the one of the offices office can NFS mount the NetApp Filer filer1 and work properly. No problems are seen. 2. Irix machines cannot. The can mount exports from filer1 and traverse directory trees, i.e: cd unix/tools/local, etc. Thay can do an ls or 'ls -l' or many directories, but cannot do an 'ls' or 'ls -l' in others. The difference is believed to be the the directories posing problems contain symbolic links. This has not been completely demonstrated. This happens both when the Irix clients are forced to use NFSv2 via the mount option "vers=2" and when they are allowed to default to NFSv3. 3. These same Irix machine can mount a Other offices NetApp filer and have no problems. The symptoms descibed above are not seen. In turn, a other offices Irix system (there are about 500 Irix systems who are active and happy NetApp clients in other office) will see the same same probems when mounting filer1 accross the WAN. 4. The problem between Irix and NetApp centers account the filer1. There are two observed differences betwenn the filer1 and a other filer3, 4.1 Other office is runnig NetApp Release 5.3.5R2P2 while here the filer1 is running NetApp Release 6.0.3 4.2 Other office has "nfs.tcp.enable off" while here filer1 has it set to "nfs.tcp.enable on". 5. We set "nfs.tcp.enable off" in Munich and the Solaris clients hung (they evidently preferred to use TCP over UDP). A reboot of Filer1 and the Solaris systems did not fix them. We turned NFS over TCP back on. 6. We then forced a single Irix NFS mount to use NFSv3 and use TCP via the client mount option "proto=tcp". It worked. 7. Does this symtom of "UDP not working" match a common NetApp misconfiguation? 8. Are there any know issues with UPD under NetApp Release 6.0.3?

1 0

Netware on a Filer???
by Todd Phillips 26 Sep '01

26 Sep '01

Who's done it? How'd you do it? How's it work?? Thanks. Todd

1 0

benchmarking
by Mark Bentley 26 Sep '01

26 Sep '01

I'm evaluating a NetApp F840C and an EMC Celerra. I'm using a benchmark program called Iozone (http://www.iozone.org/) to test NFS throughput. Are there any other benchmark programs out there anyone would suggest I try? I'm using iozone like this: iozone -a -e -f /emc/foo -U /emc or iozone -a -e -f /netapp/foo -U /netapp on a Sun E4500, and the numbers I'm getting are about 30 MB/sec read/write for the F840 and 20 MB/sec write and 25 MB/sec read on the Celerra. Both are connected with Gigabit Ethernet. The -e option does an fsync/fsflush after every write, and the -U does an unmount/mount of the filesystem between every test. This seems to eliminate the huge throughput numbers I was seeing before, due to filesystem cache. (The E4500 has 4 GB of memory.) Any suggestions would be appreciated! Mark -- Mark A Bentley Technology Development Group AT&T Wireless Services Phone: (425) 580-1667

3 4

RE: Sun Stordge L1000, Veritas Netbackup
by Fayek, Ahmed 25 Sep '01

25 Sep '01

Hi, thanks a lot for all the responses i received. About using the TapeAlert in NetBackup, i have thought about it, but the problem is that the cleaning status report contains info about only one of the 2 tape drives while both are used. DRIVE INFO: Drv Type Mount Time Frequency Last Cleaned Comment *** **** ********** ********* **************** ******* 0 dlt* 0.0 0 N/A 1 dlt* 134.2 0 N/A Ever seen such problem ? How can i make it sense and report info about drive 0 ? Best Regards -----Original Message----- From: Fayek, Ahmed [mailto:ahmed_fayek] Sent: Thursday, September 20, 2001 1:41 PM To: Veritas mailing list (E-mail); toasters (NetApp) mailing list (E-mail); NDMP mailing list (E-mail) Subject: Sun Stordge L1000, Veritas Netbackup Hi All Is anybody here using Sun Storedge L1000 library? I'm using it with Veritas Netbackup 3.4 What i'm asking about is the cleaning of the tape drives in the library. there is a note about automatic drive cleaning enabeling in the L1000. Did anyone use it? And if so, How to get a notice that cleaning has been done ? Best Regards Ahmed

1 0

FW: FTP don't work!
by Maglinger, Paul 25 Sep '01

25 Sep '01

If you're an NT shop, you can set up an IIS server (with all the patches) and point your folders to your filer shares. -----Original Message----- From: Kennard, Dave M SITI-ISEL-31 [mailto:Dave.M.Kennard@is.shell.com] Sent: Tuesday, September 25, 2001 05:37 To: toasters(a)mathworks.com Subject: FTP don't work! List, I have a CIFS only filer (NO NFS installed) does anyone know how to get FTP working? I have looked at the archives and added a user to the filer but still cant get in via FTP. Dave Kennard - SITI - NT Administration.

1 0

FTP don't work!
by Kennard, Dave M SITI-ISEL-31 25 Sep '01

25 Sep '01

List, I have a CIFS only filer (NO NFS installed) does anyone know how to get FTP working? I have looked at the archives and added a user to the filer but still cant get in via FTP. Dave Kennard - SITI - NT Administration.

1 0

RE: port 80 answers tcp
by Mike Sphar 24 Sep '01

24 Sep '01

Presuming you have your filers connected to the network via good-quality switches, you could enable ACLs on the switch to block port 80. We did some of that with other servers on our network during the nimda outbreak. I'm increasingly becoming of the opinion that the best defense against new viruses is a network where everything is fully switched, and every switch supports ACLS and stateful packet inspection. Speaking of which, I know there was some discussion of this a while back, but has anyone else had some real-world experience with the virus-scanning support in 6.x? We're looking into it now and still need to make the decision between Symantec and Trend Micro, and I'm wondering what other's recent experiences have been. (My gut instinct is to go with Trend Micro, only because they seem to have definitions up for new viruses long before Symantec does during these sudden outbreak situations.) -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Klinkner, Steve [mailto:Steve.Klinkner@netapp.com] Sent: Thursday, September 20, 2001 1:24 AM To: 'leigh(a)ai.mit.edu'; toasters(a)mathworks.com Subject: RE: port 80 answers tcp Short answer is: No, there isn't currently a way to prevent the filer from listening and accepting socket connections on port 80. Some additional details might be helpful. The httpd.enable option toggles HTTP access to the web hierarchy on the filer, in the case that HTTP is licensed on the filer. Port 80 is left open for purposes of administrative access - for example FilerView and SecureShare Quota Manager, even if HTTP is not licensed on the filer. Access to administrative areas can be toggled using the httpd.admin.enable option. If httpd.enable and httpd.admin.enable are both off, and HTTP is not licensed, then the server will immediately close incoming connections without reading any HTTP headers (this feature appears in 6.0 and higher). We are not currently aware of any flaws in the HTTP server which allow exploitation in the manner of the worms mentioned. Hope that helps, Steve Klinkner > -----Original Message----- > From: Leigh David Heyman [mailto:leigh@ai.mit.edu] > Sent: Wednesday, September 19, 2001 8:34 AM > To: toasters(a)mathworks.com > Subject: port 80 answers tcp > > > Hi, > I've noticed that in DoT, the filer still has tcp port 80 > open and listening > even with "options httpd.enable off." > > Since the nimda and code red worms send attack traffic to any > hosts which > respond on port 80, regardless of whether it's a vulnerable > windows webserver, > is there any way to actually prevent the filer from having > tcp port 80 open > and listening? > > Thanks, > > -Leigh > > > ===================================================================== > Leigh Heyman,GCIA Artificial Intelligence Lab > Systems Administrator Massachusetts Institute of Technology > leigh(a)ai.mit.edu 617-253-1729 > > >

1 0

RE: Net boot Linux SUSE 7.2 from a filer F840 or F230
by Buchmann, Manfred 24 Sep '01

24 Sep '01

Hi to all we set up SUSE Linux automated Installation , using , PXE , ETHERBOOT , Bootprom for SAP Aplication Servers the only thing that you must do is make the entry at the DHCP Server a detailed Technical Report is comming soon , if somebody needs more information , please send me a mail . You can use this installation method for other Aplications Regards Manfred Buchmann Network Appliance SAP Competence Center -----Original Message----- From: Fox, Adam [mailto:Adam.Fox@netapp.com] Sent: Mittwoch, 19. September 2001 20:38 To: 'Oye'; McCarthy, Tim Cc: toasters(a)mathworks.com Subject: RE: Net boot Linux SUSE 7.2 from a filer F840 or F230 >From my 6.1.1 machine: f880-rtp> options tftpd tftpd.enable off tftpd.logging off tftpd.rootdir /etc/tftpboot So set the tftpd.enable options to on. Set the tftpd.rootdir option to where ever you like and turn on logging if you want to log all of the gets. That's about it. Just be aware..at this time it only goes gets, no puts. You'll have to write data to that area via an NFS/CIFS client. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Oye [mailto:Oyegbemi.Akintan@oracle.com] > Sent: Wednesday, September 19, 2001 1:48 PM > To: McCarthy, Tim > Cc: toasters(a)mathworks.com > Subject: Re: Net boot Linux SUSE 7.2 from a filer F840 or F230 > > > This is definitely helpful. I'm going to resolve to using > this solution but > I need more info on setting u p the tftp server. Also I fond > a documentation > on how to do it at > http://cui.unige.ch/info/pc/remote-boot/howto.html . > Thanks > > -Oye > > "McCarthy, Tim" wrote: > > > Well, with the F230 you are almost out of luck. > > The F820, which can run 6.0.3 or later or 6.1.1 or later > > has a tftp server on it! > > > > Enable it, point your clients to use tftp to boot from > > and it may just work!!! > > > > The F230, cannot run 6.0 or higher software. So you could > > take one of your linux boxes, make a dir on the F230, mount it > > and then use said linux box as the tftp server to boot from. > > > > Does this help? > > > > --tmac > > > > -----Original Message----- > > From: Oye [mailto:Oyegbemi.Akintan@oracle.com] > > Sent: Monday, September 17, 2001 12:40 PM > > To: toasters(a)mathworks.com > > Subject: Net boot Linux SUSE 7.2 from a filer F840 or F230 > > > > Does anyone have any idea on how to set up net boot of Suse > Linux 7.2 or > > RedHat on a filer F840 or F230? > > > > Thanks, > > Oye >

1 0

(no subject)
by Jordan Share 21 Sep '01

21 Sep '01

We have gotten several messages of the following type: Mon Sep 17 10:25:59 PDT [raid_xor_server:CRITICAL]: 206 CORR SYS ERR 201 eia:1146dc058b20000 fs:254f400 eis:0 isr:80000001 SYS ECC error on DIMM J27 at address=0x1146dc0, bit=31. Mon Sep 17 10:37:28 PDT [idle_thread0:CRITICAL]: 207 CORR SYS ERR 201 eia:f71874058b20000 fs:2b1f400 eis:0 isr:80000001 SYS ECC error on DIMM J27 at address=0xf718740, bit=31.Wed Sep 19 01:03:53 PDT [GbE-II/e8:CRITICAL]: 212 CORR SYS ERR 201 eia:1dc7590058b20000 fs:256f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x1dc75900, bit=31. Wed Sep 19 01:25:09 PDT [idle_thread0:CRITICAL]: 213 CORR SYS ERR 201 eia:11149bc058b20000 fs:2b4f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x11149bc0, bit=31. Wed Sep 19 01:40:22 PDT [idle_thread0:CRITICAL]: 214 CORR SYS ERR 201 eia:19c54f8058b30000 fs:2b0f400 eis:0 isr:80010001 SYS ECC error on DIMM J30 at address=0x19c54f80, bit=31. Wed Sep 19 07:01:22 PDT [ispfc_main:CRITICAL]: 216 CORR SYS ERR 201 eia:1ecda80058b20000 fs:2d7f400 eis:0 isr:80000001 SYS ECC error on DIMM J30 at address=0x1ecda800, bit=31. As near as I can tell, this indicates that a DIMM (or 2) has gone bad. Is that the case? Or is some level of these errors considered to be normal? Here's the output of "grep -c "CORR SYS ERR" over the last few messages files: messages.5:0 messages.4:3 messages.3:6 messages.2:16 messages.1:160 messages.0:17 messages:14 So, it looks to me like this developed somewhat recently. Should I be worried about this? Thanks, Jordan

2 2

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