toasters

toasters@lists.teaparty.net

3 participants
13523 discussions

Re: ops/second
by Jim Ripley (49er Fan) 27 Jul '99

27 Jul '99

Hi, Checkout the following for this information: http://www.netapp.com/products/level3/f700series_ds.html#F760 Jim -->>From: "David Midgett" <dmidgett(a)about.com> -->>To: <toasters(a)mathworks.com> -->>Subject: ops/second -->>Date: Tue, 27 Jul 1999 11:35:27 -0400 -->>MIME-Version: 1.0 -->>Content-Transfer-Encoding: 7bit -->>X-Priority: 3 (Normal) -->>X-MSMail-Priority: Normal -->>X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 -->>Importance: Normal -->> -->>How many ops/second can the F760 handle? -->>............................................................................ -->>................... -->>David Midgett -->>Manager, Server Operations -->>About.com, Inc. (formerly MiningCo.com, Inc.) -->>http://About.com -->>............................................................................ -->>................. -->> -->> -->> ************************************************************ JIM RIPLEY Escalation Engineer -------------------------- Email: jamesr(a)netapp.com Tech Support Hotline: 1-888-4-NETAPP HQ Address Network Appliance 2770, San Tomas Expressway Santa Clara, CA 95051 bugs, faqs, docs, = http://now.netapp.com/ OS upgrades, etc. ************************************************************

1 0

ops/second
by David Midgett 27 Jul '99

27 Jul '99

How many ops/second can the F760 handle? ............................................................................ ................... David Midgett Manager, Server Operations About.com, Inc. (formerly MiningCo.com, Inc.) http://About.com ............................................................................ .................

2 1

RE: Strange routing problem.
by Mohler, Jeff 26 Jul '99

26 Jul '99

^C# ifconfig -a lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 151.142.223.53 netmask ffffff00 broadcast 151.142.223.255 ether 8:0:20:9f:61:a6 qfe0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.118.23 netmask ffffff00 broadcast 10.16.118.255 ether 8:0:20:9f:61:a7 qfe1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.119.23 netmask ffffff00 broadcast 10.16.119.255 ether 8:0:20:9f:61:a8 qfe2: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 0.0.0.0 netmask 0 ether 8:0:20:9f:61:a9 qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.3.117 netmask ffffff00 broadcast 10.16.3.255 ether 8:0:20:9f:61:a0 -----Original Message----- From: Rajeev Agrawala [mailto:rajeeva@research.bell-labs.com] Sent: Monday, July 26, 1999 3:37 PM To: Mohler, Jeff Cc: Tim McCarthy; toasters(a)mathworks.com Subject: Re: Strange routing problem. What is the output of ifconfig -a on sun machine. Please send that. rajeev "Mohler, Jeff" wrote: > Ok, Ive double checked /etc/netmasks (already was there) /etc/notrouter, > /etc/defaultrouter (already was there) > changed mac addresses on qfe0-qfe3 so the switch doesnt look at all five > interfaces on the machine as one MAC, dbl checked VLAN configs on the Cat > 5505 ports.. > > Still, the Sun wants BADLY to route 10.16.118.0 traffic across the public > hme0 interface, instead of the up/configured/plugged-in 10.16.118.23 > interface. > > Darnit.. > > --- > Did you make a /etc/notrouter file on your solaris box? > This prevents the Solaris box from becoming a router > at boot time. > > And how about /etc/netmasks? > > I would put two entries in just to be safe: > 10.16.118.0 255.255.255.0 > 10.16.119.0 255.255.255.0 > > --tmac > > Timothy A. McCarthy --> System Engineer, Eastern Region. > Network Appliance http://www.netapp.com > 301-230-5847 Office \ / Page Me at:@@ > 301-230-5852 Fax \/ 800-654-9619 > > On Mon, 26 Jul 1999, Mohler, Jeff wrote: > > > Greetings: > > > > I have a routing problem on a 2.6 box, here is the detail. > > > > I want to send traffic out to 10.16.118.20 on qfe0, which will be a > private > > 10/100 segment to the NetApp for NFS traffic. I am only using 10.16.118.0 > > in this message, because 119.0 does the same thing on qfe1. > > > > This is a prototype box to configure and test first, then deploy to the > > field installed Solaris machines. > > > > The network is like this: > > > > > > NETAPP-F760:e0 public interface connected to 3/1 on a Cat 5505 > Switch, on > > VLAN 223 (public addressed traffic) > > NETAPP-F760:ech1 channel of e1a and e1b on 10.16.118.0 on 5/1-2 > > (channel) on VLAN 118 - 10.16.118.10 > > NETAPP-F760:ech2 channel of e1c and e1d on 10.16.119.0 on 5/3-4 > > (channel) on VLAN 119 - 10.16.119.10 > > > > On the sun box I have: > > > > Sun:e0 public interface connected to 3/2 on Cat 5505 on > VLAN 223 > > Sun:qfe0 10.16.118.23 connected to 3/15 on Cat 5505 on VLAN 118 > > Sun:qfe1 10.16.119.23 connected to 3/16 on Cat 5505 on VLAN 119 > > Sun:qfe2 10.16.254.23 not yet connected for ADSM traffic > > Sun:qfe3 10.16.3.117 connected to management LAN > > > > > > The interface is up, here is netstat output: > > > > Routing Table: > > Destination Gateway Flags Ref Use Interface > > -------------------- -------------------- ----- ----- ------ --------- > > 151.142.223.0 151.142.223.53 U 2 282 hme0 > > 10.16.118.0 10.16.118.23 U 2 5351 qfe0 > > 10.16.119.0 10.16.119.23 U 2 0 qfe1 > > 10.16.3.0 10.16.3.117 U 2 3 qfe3 > > default 151.142.223.1 UG 0 129 > > 127.0.0.1 127.0.0.1 UH 0 4 lo0 > > > > A traceroute to 10.16.118.10 shows the machine choosing hme0 for a > > route...why? > > > > # traceroute 10.16.118.10 > > traceroute: Warning: ckecksums disabled > > traceroute: Warning: Multiple interfaces found; using 151.142.223.53 @ > hme0 > > > > > > I have an NFS mount on the Sun box to the filer using the 10.16.118.10 > > address, and it even shows up as the propler hostname:/<path> in the 'df' > > output. > > > > I can blow large amounts of dd traffic to/from the mount, and I see NO > > traffic on the correct Channel (ech1) on the Filer. > > > >

3 2

Strange routing problem.
by Mohler, Jeff 26 Jul '99

26 Jul '99

Greetings: I have a routing problem on a 2.6 box, here is the detail. I want to send traffic out to 10.16.118.20 on qfe0, which will be a private 10/100 segment to the NetApp for NFS traffic. I am only using 10.16.118.0 in this message, because 119.0 does the same thing on qfe1. This is a prototype box to configure and test first, then deploy to the field installed Solaris machines. The network is like this: NETAPP-F760:e0 public interface connected to 3/1 on a Cat 5505 Switch, on VLAN 223 (public addressed traffic) NETAPP-F760:ech1 channel of e1a and e1b on 10.16.118.0 on 5/1-2 (channel) on VLAN 118 - 10.16.118.10 NETAPP-F760:ech2 channel of e1c and e1d on 10.16.119.0 on 5/3-4 (channel) on VLAN 119 - 10.16.119.10 On the sun box I have: Sun:e0 public interface connected to 3/2 on Cat 5505 on VLAN 223 Sun:qfe0 10.16.118.23 connected to 3/15 on Cat 5505 on VLAN 118 Sun:qfe1 10.16.119.23 connected to 3/16 on Cat 5505 on VLAN 119 Sun:qfe2 10.16.254.23 not yet connected for ADSM traffic Sun:qfe3 10.16.3.117 connected to management LAN The interface is up, here is netstat output: Routing Table: Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 151.142.223.0 151.142.223.53 U 2 282 hme0 10.16.118.0 10.16.118.23 U 2 5351 qfe0 10.16.119.0 10.16.119.23 U 2 0 qfe1 10.16.3.0 10.16.3.117 U 2 3 qfe3 default 151.142.223.1 UG 0 129 127.0.0.1 127.0.0.1 UH 0 4 lo0 A traceroute to 10.16.118.10 shows the machine choosing hme0 for a route...why? # traceroute 10.16.118.10 traceroute: Warning: ckecksums disabled traceroute: Warning: Multiple interfaces found; using 151.142.223.53 @ hme0 I have an NFS mount on the Sun box to the filer using the 10.16.118.10 address, and it even shows up as the propler hostname:/<path> in the 'df' output. I can blow large amounts of dd traffic to/from the mount, and I see NO traffic on the correct Channel (ech1) on the Filer.

2 1

Shelf2 SCSI Drives
by John Tatar 25 Jul '99

25 Jul '99

Does anyone know where I can get shelf2 SCSI drives (And don't say netapps;-)? I didn't realize when Netapp announced that they were discontinuing some products that they were discontinuing their entire line of SCSI products. Now I can't add disks to the shelf2 that I bought partially filled with disks last year. TIA JT -- =================================================================== John J. Tatar Systems & Network Engineering Section Advanced Computer Applications Group Decision & Information Sciences Division Argonne National Laboratory mailto:tatar@dis.anl.gov or john(a)tatar.com Office: 630-252-3242 Fax: 630-252-5128 Pager: 630-266-1063 ===================================================================

2 1

Id'ing stale NFS file handle - solaris mounting netapp?
by Elizabeth Schwartz 23 Jul '99

23 Jul '99

We have a solaris 2.6 server with MANY users, that is getting regular "NFS stale file handle" errors. We have the file handle from /var/adm/messages but we do not know which process is generating the error. Is there anything we can do to get a file name from the file handle, to help identify which process is the source? Rebooting this machine is a last resort option since it is a primary user server (meaning we'd have to do it in the wee hours) thanks Betsy (new to the list, hello all!)

3 6

Re: restore from dlt is failing
by Stephen C Woods 23 Jul '99

23 Jul '99

Hmmm, ARG b is specifying a blocksize of 1 KB, it looks to me as though you should specify 63. I presume that you know what you are doing with ARG s (File 33 of n on the tape). #ifdef PARANOID_MODE Also, unless you are planning to write on the tape, it should be write protected, just to protect against fumble fingers or other errors. #endif /*PARANOID_MODE*/ <scw> > > I'm trying to do a restore from tapes where the netbackup images have expired. (I did a "phase > > 1 import" which reads image headers, so I know which files I'd like off the tape; "phase 2 import" > > which reads files and rebuilds netbackup database info is failing -- this may be a separate issue.) > > The correct tape is loaded in the dlt. I'm seeing "RESTORE: Could not initialize media." > > > > inbox1> mt -f nrst0a rewind > > inbox1> mt -f nrst0a status > > Tape drive: Digital DLT7000 > > Status: ready, write enabled > > Format: 85937 bpi 70 GB (w/comp) > > fileno = 0 blockno = 0 resid = 0 > > inbox1> mt -f nrst0a rewind > > inbox1> restore tvf nrst0a b 1 s 33 > > RESTORE: Tape Block size should be 1024, not 64512. > > RESTORE: Could not initialize media. > > inbox1> mt -f nrst0a rewind > > inbox1> restore tvf nrst0a s33 > > RESTORE: Tape Block size should be 1024, not 64512. > > RESTORE: Could not initialize media. > > inbox1> mt -f nrst0a status > > Tape drive: Digital DLT7000 > > Status: ready, write enabled > > Format: 85937 bpi 70 GB (w/comp) > > fileno = 0 blockno = 1 resid = 31744 > > inbox1> > > > > Any ideas or suggestions? > > > > Dave Toal > > Thomson & Thomson > > ----- 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

2 1

Unusual request
by Sitzkrieg Redundus 23 Jul '99

23 Jul '99

Hi! I'm fairly new to the list, so here we go. I've got a 630 sitting in a rack happily serving up webpages to 12 front end machines via NFS. The NetApp needs to be Y2k tested, however I can not test a live machine. Yes, I know NetApp has certified ONTAP and the head unit itself. Doesn't matter, I work for an ISP, and we trust nothing. :) Does anyone have/know of someone who has a 630 head unit that I could buy outright or borrow/lease for a couple of weeks (at most, I should think) to do some testing? My NetApp salesdude has informed me that NetApp doesn't have a single 630 anywhere in the company, so my options are somewhat limited. I can a) scrounge a 630 or b) buy a 760 (which while an option, isn't all that high on my list of happy things). Thanks. Noah Robin

1 0

strange sysstat output
by Graham C. Knight 23 Jul '99

23 Jul '99

This is an F540 running 5.2.1P2D14 The filer is basically doing nothing - but every 5 seconds or so the CPU goes up to 80 or 90% and stays there for 6 or 7 seconds. We've been having trouble with systems that have NFS mount to this filer hanging. The only solution (thus far) has been to reboot the filer. I'm not too worried about it because this system was due to be replaced this Sunday, but it'd be a good one for the data banks if anyone knew what caused this type of behaviour. sysstat is below. Thanks, Graham sysstat 1: CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 1% 3 0 0 1 0 0 0 0 0 2 1% 2 0 0 0 0 0 0 0 0 2 2% 30 0 0 59 109 0 0 0 0 2 81% 26 12 0 16 148 0 0 0 0 2 90% 5 12 0 5 2 0 0 0 0 2 90% 3 12 0 4 2 0 0 0 0 2 92% 3 9 0 3 2 800 136 0 0 2 89% 2 11 0 4 2 16 732 0 0 2 90% 3 12 0 13 2 0 0 0 0 2 90% 2 13 0 4 2 0 0 0 0 2 13% 2 1 0 0 0 0 0 0 0 2 1% 10 1 0 2 2 0 0 0 0 2 1% 2 0 0 0 0 0 0 0 0 2 1% 4 0 0 9 1 0 0 0 0 2 1% 2 0 0 0 0 0 0 0 0 2 80% 3 12 0 4 2 0 0 0 0 2 90% 2 12 0 4 2 0 0 0 0 2 92% 1 12 0 4 2 312 0 0 0 2 93% 2 12 0 4 2 16 668 0 0 2 90% 4 12 0 4 2 0 0 0 0 2 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 89% 4 11 0 4 2 0 0 0 0 2 92% 5 10 0 4 2 0 0 0 0 2 1% 10 0 0 2 2 0 0 0 0 2 1% 2 0 0 0 0 0 0 0 0 2 1% 9 0 0 1 1 0 0 0 0 2

4 5

Re: strange sysstat output
by Graham C. Knight 23 Jul '99

23 Jul '99

Thanks to everyone for the responses. It turns out that this system had a bad network card. On a hunch i replaced the card and everything went back to normal, and the hangs seem to have stopped. Graham

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