toasters

toasters@lists.teaparty.net

13531 discussions

RE: SNMP Trap Information
by Roufay, Charles 30 May '02

30 May '02

The netapp.mib and the traps.dat files are the only ones needed. Of course it takes a while to get used to the definitions. Charles [Roufay, Charles] -----Original Message----- From: Infantino, Vincent (Exchange) [mailto:vinfantino@bear.com] Sent: Thursday, May 30, 2002 2:15 PM To: 'toasters(a)mathworks.com' Subject: SNMP Trap Information Would anyone have a complete list of SNMP traps sent by the filers that I can use to decide what is relevant to my environment? I have tried requesting this list from different resources at NetApp, but have only come up with a mib and a data file that need to be cross-referenced. The end result does not produce a trap with a clear description. Any help would be appreciated. Vinny Infantino

1 0

SNMP Trap Information
by Infantino, Vincent (Exchange) 30 May '02

30 May '02

Would anyone have a complete list of SNMP traps sent by the filers that I can use to decide what is relevant to my environment? I have tried requesting this list from different resources at NetApp, but have only come up with a mib and a data file that need to be cross-referenced. The end result does not produce a trap with a clear description. Any help would be appreciated. Vinny Infantino *********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***********************************************************************

1 0

RE: OPLOCKS
by Eisler, Alex 29 May '02

29 May '02

From my experience, don't use oplocks - it tends to do more harm than good. Just do 'options cifs.oplocks.enable off' Alex. -----Original Message----- From: stefan.holzwarth(a)zentrale.adac.de [mailto:stefan.holzwarth@zentrale.adac.de] Sent: Wednesday, May 29, 2002 11:54 To: toasters(a)mathworks.com Subject: OPLOCKS Hi, since we have some small instabilities in our network ;-) it sometimes occures that a oplock isn't released by a NT Workstation. I have then to do manually a cifs terminate for that PC. Is there another way to do that? Shorter timeouts for automatic break by the filer? Why does the filer not recognize the situation - the new cifs session from that rebootet NT workstation (we use 6.1.2 R1) Thanks for input Stefan Holzwarth ---------------------------------------------------------------------------- -- Stefan Holzwarth ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste) Am Westpark 8, 81373 München, Tel.: (089) 7676-5212, Fax: (089) 76768924 mailto:stefan.holzwarth@zentrale.adac.de

1 0

OPLOCKS
by stefan.holzwarth＠zentrale.adac.de 29 May '02

29 May '02

Hi, since we have some small instabilities in our network ;-) it sometimes occures that a oplock isn't released by a NT Workstation. I have then to do manually a cifs terminate for that PC. Is there another way to do that? Shorter timeouts for automatic break by the filer? Why does the filer not recognize the situation - the new cifs session from that rebootet NT workstation (we use 6.1.2 R1) Thanks for input Stefan Holzwarth ---------------------------------------------------------------------------- -- Stefan Holzwarth ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste) Am Westpark 8, 81373 München, Tel.: (089) 7676-5212, Fax: (089) 76768924 mailto:stefan.holzwarth@zentrale.adac.de

1 0

RE: True 64 UNIX and Filers
by Ben Rockwood 29 May '02

29 May '02

Absolutely NOT. Toaster's are for Network attached storage, NOT local disk. A quorum device is, as you state, a disk which is connected to both nodes, but must be direct attach via SCSI (whether the medium is SCSI or FC doesn't matter). A network device may not (and SHOULD not) be used for quorum. Your quorum device should be the closest, simplest and most robust disk (preferably) avalible. If you review your documentation for your cluster implementation, you'll find that you need to supply it with a SCSI ID, which a Filer would not be. Ben Rockwood -----Original Message----- From: Uros Lampret [mailto:netapp@ourspace.si] Sent: Tue 5/28/2002 11:42 PM To: Ben Rockwood Cc: toasters(a)mathworks.com Subject: Re: True 64 UNIX and Filers I'm asking because in Cluster configuration there must be a Quorum disk wich is accessible by both UNIX servers. So it must be external storage. Usualy someone would suggest SAN, but i'l like to set it up wit Filer. ----- Original Message ----- From: "Ben Rockwood" <BRockwood(a)homestead-inc.com> To: "Uros Lampret" <netapp(a)ourspace.si> Cc: <toasters(a)mathworks.com> Sent: Wednesday, May 29, 2002 7:50 AM Subject: RE: True 64 UNIX and Filers In what regard? Filers will work with any networked device (one assmumes almost any network device knows one of the filers many protocals). What would be any diffrent in a Tru64 Cluster? A better question is more likely: is it a good idea to use a Filer for a Cluster. Can you explain a bit more what you are looking to do? benr. -----Original Message----- From: Uros Lampret [mailto:netapp@ourspace.si] Sent: Tue 5/28/2002 9:46 PM To: 'Toasters (E-mail)' Cc: Subject: True 64 UNIX and Filers Is it possible to use True 64 unix Cluster with NetApp Filers? regards, Uros _____________________________ Uros Lampret Our Space Appliances d.o.o. Tbilisijska 59 1000 Ljubljana - Slovenia tel. +386 1 2425 372 fax +386 1 2425 382 email: uros.lampret(a)ourspace.si internet: www.ourspace.si _____________________________

1 0

RE: True 64 UNIX and Filers
by Ben Rockwood 29 May '02

29 May '02

In what regard? Filers will work with any networked device (one assmumes almost any network device knows one of the filers many protocals). What would be any diffrent in a Tru64 Cluster? A better question is more likely: is it a good idea to use a Filer for a Cluster. Can you explain a bit more what you are looking to do? benr. -----Original Message----- From: Uros Lampret [mailto:netapp@ourspace.si] Sent: Tue 5/28/2002 9:46 PM To: 'Toasters (E-mail)' Cc: Subject: True 64 UNIX and Filers Is it possible to use True 64 unix Cluster with NetApp Filers? regards, Uros _____________________________ Uros Lampret Our Space Appliances d.o.o. Tbilisijska 59 1000 Ljubljana - Slovenia tel. +386 1 2425 372 fax +386 1 2425 382 email: uros.lampret(a)ourspace.si internet: www.ourspace.si _____________________________

2 1

Re: True 64 UNIX and Filers
by SreeHarsha.V.Kannantha 29 May '02

29 May '02

Yes , if it supports NFS version 2 or 3 Regards SreeHarsha ---------- Original Message ---------------------------------- From: "Uros Lampret" <netapp(a)ourspace.si> Date: Wed, 29 May 2002 06:46:24 +0200 Is it possible to use True 64 unix Cluster with NetApp Filers? regards, Uros _____________________________ Uros Lampret Our Space Appliances d.o.o. Tbilisijska 59 1000 Ljubljana - Slovenia tel. +386 1 2425 372 fax +386 1 2425 382 email: uros.lampret(a)ourspace.si internet: www.ourspace.si _____________________________

1 0

True 64 UNIX and Filers
by Uros Lampret 29 May '02

29 May '02

Is it possible to use True 64 unix Cluster with NetApp Filers? regards, Uros _____________________________ Uros Lampret Our Space Appliances d.o.o. Tbilisijska 59 1000 Ljubljana - Slovenia tel. +386 1 2425 372 fax +386 1 2425 382 email: uros.lampret(a)ourspace.si internet: www.ourspace.si _____________________________

1 0

very serious NFS bug
by Igor Schein 28 May '02

28 May '02

Hi, I came across the following bug. NFS writes from Redhat 7.3 client result in filer giving a lot of RPC timeouts for all other clients on the network. Here's a link describing what's known about this bug so far: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65069 With default wsize value of 15K, tcpdump shows a lot of fragmentation packets. While it's obvious that it's RedHat 7.3 bug, I am still wondering why NFS v3 is vulnerable to such sort of DoS attack. On related note, I looked at registry file on the file, and I found these entries: options.nfs.tcp.recvwindowsize=26280 options.nfs.tcp.xfersize=32768 options.nfs.udp.xfersize=32768 Is the 1st one only applicable to NFS over TCP? Is the last one read-only? Thanks Igor

1 0

RE: Accessing a share from DOS.
by Asbjørn Bjørkelund 28 May '02

28 May '02

It's possible to access the filer from a dos 6.22 boot floppy, but i guess your problem is related to the lan manager version on your boot floppy, it should be at least lan manager ver 2.2c, i had the same problem as you are experiencing now i solved it with downloading boot floppies from either www.bootdisk.com or www.nu2.nu/bootdisk/network/ then i got a lan manger version that was working ok with the filer. Best Regards Asbjorn Bjorkelund -----Original Message----- From: Benny Wiström Sent: 27. mai 2002 12:56 To: 'toasters(a)mathworks.com' Subject: Accessing a share from DOS. Is it possible to access a share on a filer from DOS 6.22? When I try this I get the following error message: "the network has responded incorrectly" Is DOS supported at all? /Benny

1 0

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