toasters

toasters@lists.teaparty.net

13520 discussions

Start a nNew thread

(Kein Betreff)
by Gerd Froschermeier 26 Apr '99

26 Apr '99

unsubscribe gerd.froschermeier(a)bmw.de

1 0

remote support issues
by Richard L. Rhodes 25 Apr '99

25 Apr '99

Hi List, I don't own a Netapp, but joined this list a couple weeks ago when we decided to take a closer look at and possibly eval one. I must say it's refreshing to see a list where the vendor allows their people to help out. The comment below by Oliver gets to my biggest concern: remote support. I've made very clear to the sales and tech reps that my biggest concerns with a netapp (or anything I would purchase) is remote support. I would need to put netapps at remote sites locked in phone closets with our other networking equipment and servers. Everything is interconnected by a wan and support would be by myself from a central, but remote site. May I ask a couple of question? 1) How effectively can you support a netapp from a remote site? 2) I would be interested in hearing from anyone using a netapp for a oracle database on rs/6k computers. Thanks Rick On 22 Apr 99, at 12:49, Oliver Krause wrote: > Hello Brian, > > also from me a big thank you for this feature. Without it remote support > would be very hard. And a command to change to firmware variables from a > running system would be really valuable. > > Oliver > ---------------------------------------------------------------------- Richard L. Rhodes e: rhodesr(a)firstenergycorp.com Ohio Edison Co. p: 330-384-4904 f: 330-384-2514

7 11

RE: Anybody using 3com switches with NetAPP?
by Garrett Burke 25 Apr '99

25 Apr '99

Hi Jaye, You don't say what model of filer you are using. I have a F230 running 5.2.1 connected to a 3COM 3900 and I see output errors (but not input errors) on the filer interface and these show up as CRC (or FCS as 3COM call them) errors on the switch port. I'm seeing about 0.03% errors. Netapp support says not to worry about this level of errors. Both are 100Mbps full duplex with no auto negotiate. I moved the filer to a Extreme Summit S48 and a different cable run and I still see the CRC errors. GB > ---------- > From: Jaye Mathisen[SMTP:mrcpu@internetcds.com] > Sent: 16 April 1999 08:49 > To: toasters(a)mathworks.com > Subject: Anybody using 3com switches with NetAPP? > > > > I have both my ports on a linkswitch 3000, at 100mb, full-duplex. > >

2 1

Re: NetApp Cache Appliance secutity issue ??
by jrg＠acm.org 25 Apr '99

25 Apr '99

On Fri 23 Apr, 1999, Colin Johnston <colinj(a)uk.psi.com> wrote: >I understand the need to distribute pdf docs as there are useful for >administration but password info in clear text could be overcome by >encrypting the pdf's stored online(and in the binary distrib) and doing >decryption of pdf info if required. Much better to be so open about default passwords that no one mistakenly believes it could be kept secret, then people *will* change the default passwords. I almost feel compelled to go and compile a list of all default passwords for all software and hardware known to mankind (but someone has probably already beaten me to it.) James.

5 5

Re: That Darn NAC
by sirbruce＠ix.netcom.com 24 Apr '99

24 Apr '99

On 04/24/99 00:23:33 you wrote: > > >On Fri, 23 Apr 1999 sirbruce(a)ix.netcom.com wrote: > >> I'd just like to point out, once again, that Netapp >> isn't NAC anymore, having changed from "Corporation" >> to "Inc." years ago. > >Are there any significant differences between corps. and incorps.? I never really heard a reason. They did it just before going public so I would speculate there is some odd legal/investment reason why having "Incorporated" in their name was preferred. You'd have to ask someone on the Board or executive staff. Bruce

1 0

That Darn NAC
by sirbruce＠ix.netcom.com 24 Apr '99

24 Apr '99

I'd just like to point out, once again, that Netapp isn't NAC anymore, having changed from "Corporation" to "Inc." years ago. Of course, a lot of us were in the habit of calling the boxes "nacs" so it was hard to change to "nais" or "netapps." I guess you can still call them NACs if you have a suitable acronym. "Network Appliance Computer" is fine but a little generic; "Network Appliance Cache" works fine for one product but not the other. :) Me, I just call them "filers." Bruce

2 1

Re: Console Break (was Y2K...)
by Ketil Kirkerud Elgethun 23 Apr '99

23 Apr '99

jrg(a)acm.org (James R Grinter) writes: > For Solaris 2, I've been told that there exists modified serial driver > that - when the OS is running - will prevent that happening. This is in fact the standard serial/console driver in Solaris 2.6 (and 7). You'll have to set a variable in /etc/default/kbd - basically you have the option to either -react to BREAK (or L1-A, if you have a keyboard attached) - this is the default -ignore the BREAK (or L1-A). We're running quite a few (50ish) Suns, all connected to a linux box running conserver (serial hardware being Stallion cards). We've had no problems with this so far - and we _do_ have breaks enabled, to be able to reset a machine that won't let us in for some reason. Another thing : I'm thinking of attending the Netapp202 course (it fits nicely in with my plans for Usenix Tech.'99) - I've been running Netapps for a few years now, but wouldn't mind some more "inside" information on the secret bits. Is anyone willing to recommend this course ? Finally, a small tidbit for those among you who get a thrill out of (large) numbers: We've got an F540 (current uptime: 404 days) - this box has sustained 9900 (!) NFSops/sec for 20 hours. Id' say that on average it has sustained approx 3000 NFSops/sec over the last 6 months... NetApp needs to do something about the "total nfs ops counter" - it's rolled 15 times since the last reboot - nfsstat -l gives some really interesting output : [output snipped] 195.225.3.37 www2.sol.no NFSOPS = 1385724634 (4294966978%) :-) -- ---Ketil Kirkerud Elgethun, SOL System

2 1

Console Break (was Y2K...)
by scw＠seas.ucla.edu 23 Apr '99

23 Apr '99

> > I just wish there was a way to enable breaks from console. > > By "enable breaks" do you mean the "BREAK causes the OS to jump to the > PROM monitor" stuff that SunOS (including 5.x) does? > > We don't detect BREAK or respond to it, but there's probably no reason > we couldn't do that. ARGGG! NO! NO! NO! Disaster waiting to happen. A failed terminal, or one that is turned off or has its power line unplugged generates a BREAK -well strictly speaking it's not really a BREAK but most implimentations of UART see it as a break. This used to happen to our Admin folks every once in a while with their SUN. Remember the users with their torches and pitchforks. > I don't know if our serial port is set up so that unplugging a terminal > (or terminal server) and plugging it back in looks like a BREAK; that's > one of the suckages on at least some Suns. > ----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Finger for public key scw(a)cirrus.seas.ucla.edu,Internet mail:scw@SEAS.UCLA.EDU

4 4

Re: Console Break (was Y2K...)
by tkaczma＠gryf.net 23 Apr '99

23 Apr '99

On Fri, 23 Apr 1999 scw(a)seas.ucla.edu wrote: > Clearly you don't work at a university, where faculty members walk > into the machine room and grab any old piece of equipment that they want No, I work in an environment where dumb tubes are a greatly coveted pieces of equipment, since we don't have too many to go around. Still, pulling a serial cable doesn't cause the machine to halt in our environment. I don't care that you want this functionality disabled. If you do you'll never enable it in the variable. I have roughly 15 NACs in 6 different buildings, some of them 12 miles away. > In any case OUR machine room is protected against faculty intrusion, > and AIX doesn't have that problem anyway. But Sun's implementation of > BREAK detection is severly broken ( 0v != SPACE ) or is it MARK? Like I said, pulling the cable off doesn't do it, plugging the cable in doesn't do it. Turning the tube on while connected to a Sun does it. Hence, the tube is the broken piece not the Sun. Tom

1 0

size of NFS ops counters (was RE: Console Break (was Y2K...))
by Hackworth, Brian 23 Apr '99

23 Apr '99

: From: Ketil Kirkerud Elgethun [mailto:ketilk@a.sol.no] : NetApp needs to do something about the "total nfs ops counter" - it's : rolled 15 times since the last reboot - nfsstat -l gives some really : interesting output : : : [output snipped] : 195.225.3.37 www2.sol.no NFSOPS = 1385724634 (4294966978%) For the next major release of ONTAP, we'll be increasing the size of many of the internal counters, including the NFSOPS counters, to 64 bits. This should help for a while. - Brian Hackworth

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters