toasters

toasters@lists.teaparty.net

13520 discussions

Jumbo Frames on a Toaster
by John Coke 07 Sep '01

07 Sep '01

I am about to deploy a 740 as the content store for a www server farm and also as storage for a farm of windows media encoders. The idea popped into my head that jumbo frames on a gig link might be what I need to help keep the load on the filer down. Does anyone have any experiences with jumbo frames on a toaster or just jumbo frames in general (a little OT I know)? Thank you. John Coke PGP fingerprint: A8D1 4CBD 88CF 1B37 8008 2F79 3081 2108 8F45 E846 PGP key ID 0x8F45E846 (pgp.mit.edu)

1 0

RE: Upgrade to 6.1R1
by Mohler, Jeff 07 Sep '01

07 Sep '01

*nods* The confusion is my fault. I was testing on a system that was -once- 6.1.1 but was reverted by someone in the Lab this AM that I didnt catch. NOW is correct. -----Original Message----- From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] Sent: Friday, September 07, 2001 11:16 AM To: jeff.mohler(a)netapp.com Cc: mcope(a)isisph.com; toasters(a)mathworks.com Subject: Re: Upgrade to 6.1R1 jeff.mohler(a)netapp.com (Jeff Mohler) writes: > > These are normal messages that are usually supressed by ONTAP. > Its the software querying the FCAL & SCSI loops for devices at bootup. > > 6.1.1 did not supress these messages as all previous versions have, and > all later versions will. The messages are harmless and "normal" although > you usually will not see them. Ummm... some confusion about ONTAP release numbers here? The bug database at NOW seems to indicate that bug 41100 was present in 6.1 and 6.1R1 but fixed in 6.1.1. Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.

1 0

RE: Upgrade to 6.1R1
by Mohler, Jeff 07 Sep '01

07 Sep '01

These are normal messages that are usually supressed by ONTAP. Its the software querying the FCAL & SCSI loops for devices at bootup. 6.1.1 did not supress these messages as all previous versions have, and all later versions will. The messages are harmless and "normal" although you usually will not see them. Please see http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs2266&resource= for additional background information. -----Original Message----- From: mcope(a)isisph.com [mailto:mcope@isisph.com] Sent: Friday, September 07, 2001 7:05 AM To: owner-toasters(a)mathworks.com Cc: toasters(a)mathworks.com Subject: Re: Upgrade to 6.1R1 I have 4 filers running DOT 6.1R1 and they all say this on boot-up. I want to say it has something to do with putting anything in NVRAM to disk and possibly to perform check for any disk problems. I've accepted it as a normal part of the boot process. Michael Cope UNIX/Linux Systems Administrator ISIS Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH! On 9/7/2001 12:38:28 AM, "Uros Lampret" <uros.lampret(a)ourspace.si>@mathworks.com wrote: > After upgrade to DOT 6.1R1 I've got a warning that I don't understand. > After every reboot filer displays: > > Starting Press CTRL-C for special boot menu > ...................................................................... > .......... > ................................ > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.10(0xfffffc00012d73a0, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.11(0xfffffc00012d7600, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.12(0xfffffc00012d7860, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.13(0xfffffc00012d7ac0, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.14(0xfffffc00012d7d20, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.15(0xfffffc00012d7f80, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > > NetApp Release 6.1R1: Fri Apr 20 03:08:22 PDT 2001 > Copyright (c) 1992-2001 Network Appliance, Inc. > Starting boot on Fri Sep 7 05:52:34 GMT 2001 > > Somebody eles saw this? > > Uros > - att1.htm

2 1

CIFS performancs problems: small files and WinNT
by mcope＠isisph.com 07 Sep '01

07 Sep '01

My company recently migrated about 500GB of files from our NetWare server onto a Filer. We're experiencing a performance problem with opening, copying, or moving multiple (more than 2) small files between the Filer and our users on NT Workstation. Each file has a latency of almost a full second to get processed (open, copy, move). This happens for files between 1K up to 1MB. Large files (over 5MB) don't display this latency. We've played with the CIFS options for TCP on the Filer and making registry changes on the NT workstations and still haven't seen a significant reduction in latency. We think we've narrowed the problem down to the TCP/IP stack in NT. A Win2K workstation with a 100Mb NIC experiences zero latency while an NT Server with a Gigabit NIC is painfully slow while working with the exact same small files. Most of my experience is with Unix and NFS connections to Filers but I've been using CIFS to connect my NT workstation to our Filers for a couple of years and never really noticed this. Has anyone else experienced this latency issue with CIFS, NT and small files or have any suggestions on how to resolve it? My network administrator would like to see a Filer fix rather than have to touch 600+ PCs but I'll entertain any suggestions. TIA, Michael Cope UNIX/Linux Systems Administrator ISIS Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH!

1 0

RE: How to know which qualified tape drive I can emulate?
by Cormier, Darleen 07 Sep '01

07 Sep '01

Hi Nick, If I'm understanding your question correctly, you do not need to emulate anything. The DLT7000s have been fully supported since DataONTAP 5.1.1. Regards, Darleen -----Original Message----- From: nick.mayrath(a)webmd.net [mailto:nick.mayrath@webmd.net] Sent: Thursday, September 06, 2001 4:49 PM To: toasters(a)mathworks.com Subject: How to know which qualified tape drive I can emulate? How do I know which qualified tape drive I can emulate? I have a Sun Microsystems L280 Autoloader (6 slots, DLT7000). I'm running Ontap 5.3.6r2 and will be upgrading to 6.1r1 soon. Thanks in advance Nick Mayrath Network Administrator ExpressBill, Inc. 800-453-8439 ext. 216

1 0

Re: Upgrade to 6.1R1
by mcope＠isisph.com 07 Sep '01

07 Sep '01

I have 4 filers running DOT 6.1R1 and they all say this on boot-up. I want to say it has something to do with putting anything in NVRAM to disk and possibly to perform check for any disk problems. I've accepted it as a normal part of the boot process. Michael Cope UNIX/Linux Systems Administrator ISIS Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH! On 9/7/2001 12:38:28 AM, "Uros Lampret" <uros.lampret(a)ourspace.si>@mathworks.com wrote: > After upgrade to DOT 6.1R1 I've got a warning that I don't understand. > After every reboot filer displays: > > Starting Press CTRL-C for special boot menu > ...................................................................... > .......... > ................................ > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.10(0xfffffc00012d73a0, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.11(0xfffffc00012d7600, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.12(0xfffffc00012d7860, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.13(0xfffffc00012d7ac0, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.14(0xfffffc00012d7d20, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: > 0b.15(0xfffffc00012d7f80, 0x12): > command timeout, quiescing bus to allow outstanding I/O to complete. > > NetApp Release 6.1R1: Fri Apr 20 03:08:22 PDT 2001 > Copyright (c) 1992-2001 Network Appliance, Inc. > Starting boot on Fri Sep 7 05:52:34 GMT 2001 > > Somebody eles saw this? > > Uros > - att1.htm

1 0

Upgrade to 6.1R1
by Uros Lampret 07 Sep '01

07 Sep '01

After upgrade to DOT 6.1R1 I've got a warning that I don't understand. After every reboot filer displays: Starting Press CTRL-C for special boot menu ................................................................................ ................................ Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.10(0xfffffc00012d73a0, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.11(0xfffffc00012d7600, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.12(0xfffffc00012d7860, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.13(0xfffffc00012d7ac0, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.14(0xfffffc00012d7d20, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. Thu Jan 1 00:00:00 GMT [isp_timeout:warning]: 0b.15(0xfffffc00012d7f80, 0x12): command timeout, quiescing bus to allow outstanding I/O to complete. NetApp Release 6.1R1: Fri Apr 20 03:08:22 PDT 2001 Copyright (c) 1992-2001 Network Appliance, Inc. Starting boot on Fri Sep 7 05:52:34 GMT 2001 Somebody eles saw this? Uros

2 1

FW: Quantum ATL M1500 LTO Drives?
by Joe Luchtenberg 07 Sep '01

07 Sep '01

Got some info from ATL: - since you refer to multiple systems, I presume you're interested in an OSN Fibre Channel solution; the M1500 is not yet certified under that program, but ATL is pursuing it and we *may* likely see the M1500 with FC310 FC to SCSI bridge certified under NetApp's OSN program in the OCT/NOV timeframe. - if instead you are looking for a SCSI solution, then your issue is with the LTO drives; here's what ATL had to say there: <<snip>> NetApp now offers support in Data ONTAP for IBM LTO only. We expect HP support around November 1st. So until then we are dead in the water on M1500 with LTO for NetApp, though P Series libraries with IBM drives are okay. <<end snip>> Hope this helps. Joe Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg(a)data-line.com www.data-line.com -----Original Message----- From: Joe Luchtenberg Sent: Wednesday, August 29, 2001 10:08 AM To: Vicki Bilyeu (E-mail) Subject: FW: Quantum ATL M1500 LTO Drives? Email address indicates this guy is in Malaysia, maybe? Don't know if you have a channel partner who can help this guy, but perhaps you can forward to the appropriate Program Manager who can speak to the status of NetApp OSN certification for the M1500 (I'm only familiar with certified configs for P1K/2K/3K/6K). Hope all is well. Joe Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg(a)data-line.com www.data-line.com -----Original Message----- From: NicholosC [mailto:NicholosC@maxis.net.my] Sent: Wednesday, August 29, 2001 1:25 AM To: toasters(a)mathworks.com Subject: Quantum ATL M1500 LTO Drives? Check the NOW site and it is not listed as supported library. Currently looking into the M1500 LTO Drives for a few systems. Has anybody got any success in implementing this library for the filer? Nic

2 2

How to know which qualified tape drive I can emulate?
by nick.mayrath＠webmd.net 06 Sep '01

06 Sep '01

How do I know which qualified tape drive I can emulate? I have a Sun Microsystems L280 Autoloader (6 slots, DLT7000). I'm running Ontap 5.3.6r2 and will be upgrading to 6.1r1 soon. Thanks in advance Nick Mayrath Network Administrator ExpressBill, Inc. 800-453-8439 ext. 216

1 0

RE: CIFS terminate for WTS
by Nail, Larry 06 Sep '01

06 Sep '01

Yes, I used to use Hyena for that & other things, but it's too slow vs. some of the native W2K tools. -----Original Message----- From: neil lehrer [mailto:nlehrer@ibb.gov] Sent: Thursday, September 06, 2001 4:02 PM To: Nail, Larry Cc: 'Jeffrey Krueger'; toasters(a)mathworks.com Subject: Re: CIFS terminate for WTS or a tool like hyena will show you all the sessions open on a server and let you mark the ones you want to disconnect. "Nail, Larry" wrote: > > I have to agree with the CLI part of it... I abhor the mouse. However > for mouse jockies, an alternative is: > > An alternative is to use the Computer Management MMC for Windows 2000 > (right click my computer, manage, action, connect to another computer, > expand shared folders, Sessions) to view the sessions. Limited to > screen size if you hide the left pane. You can also sort by column. > > I customized an MMC to include the Shared Folders & Local Users and > Groups snap-ins for quick access. > > Larry > ______________________________________ > Lawrence D. Nail > Microsoft Certified Systems Engineer > NT Infrastructure and Strategy > SC Design Systems > Texas Instruments Incorporated > > -----Original Message----- > From: Jeffrey Krueger [mailto:jkrueger@qualcomm.com] > Sent: Thursday, September 06, 2001 1:54 PM > To: Jeffrey Krueger > Cc: toasters(a)mathworks.com > Subject: Re: CIFS terminate for WTS > > Thanks for all the responses! For the lists benefit, the conclusion > was that this has to be done through the Server Manager but that an > ONTAP RFE for a "cifs terminate" style command exists. > > Since a few folks asked "If it works, why not just use Server > Manager?" I'll give a public response. While Server Manager works, it > is not very practical when you have a good number of connections. For > instance, on the machine in question, there were 2,448 sessions open > when I was trying to kill a few. I could easily pick them out via the > command line "rsh filer cifs sessions" and some creative regex's. In > server manager, I have a four-line view of this list. Just finding > the connections in question was a chore of scrolling and manually > reading each line. It was a pain. > > I'm not dogging GUI's - they're great for a number of things. This is > one task they are not well suited for. Personally, I prefer grep to > do my pattern matching for me since it is abundantly more accurate and > lightning fast in comparison to me manually reading each line. > > So, a CLI alternative would be great! =) > > -- Jeff > > On Wed, Sep 05, 2001 at 11:52:38AM -0700, Jeffrey Krueger wrote: > > Does anyone know how to terminate one connection of a multiplexed > > CIFS session from an NT workstation (such as a WTS server)? That > > is, many users are logged into a WTS server, but I only want to > > terminate one. > > > > This can be done "fairly easily" from the NT Server Manager console; > > however, I'm looking for a "rsh filer cifs terminate ..." varient. > > > > Any ideas? > > > > -- Jeff > > > > -- regards

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