toasters

toasters@lists.teaparty.net

13515 discussions

I'm OK
by Tom Reingold 11 Sep '01

11 Sep '01

I'm OK, and I believe so is everyone I know. Thank God. (Sorry for the mass email. If you don't know me, sorry for bothering you.)

1 0

max capacity
by Matt Graham 10 Sep '01

10 Sep '01

I was reading one of the NOW documents to get some background on expanding our filer. I'm a bit confused as to what the max capacity limit is based on. I found a table for the 740. From looking at the table it would appear that the max capacity is limited to 1,008 GB regardless of the size of the disks used. However, the text indicates that the limitation is a function of the number of disks supported (which is contradictory to the table). The table shows that I could have 28 disks x 36 GB. Does the fact that I have 36GB disks installed limit me to a total of 28 disks? I have seven 18GB disks that I plan to keep using as well. Thx, Matt -- __________________________________________________________ If you can remain calm, you just don't have all the facts¿

1 0

NDMP backups and tape retention
by Jay Newton 10 Sep '01

10 Sep '01

I am trying to find information on how other companies are backing up their Filers and how long tapes are retained. We are using a F840 Filer for Oracle databases and CIFS file services. We use CommVault Galaxy to back up the data. However, it is impossible to set up a GFS-type of rotation in Galaxy for NDMP clients. Do other products also have this limitation? If so, how do you get around it. Is a GFS-style rotation needed any more with the Filer? Any help would be greatly appreciated. Jay Newton Systems Engineer - Chesapeake Operating (405)810-2683 (405)879-9578 fax

1 0

Re: scsi.cmd.checkCondition:error when switching tapes during backup
by Steven Boyer 10 Sep '01

10 Sep '01

I am seeing the same error when doing a snapmirror to tape. When I contacted NetApp thay said the following: ------------------------------------------------------------------------ Hello Steven, About the [scsi.cmd.checkCondition:error]:...Check Condition:...: Sense Data no error - (0x0 - 0x0 0x2), An application or process accessing the tape device has made an attempt to write file marks past the end of tape. This one's pretty harmless.. It's a condition that usually arises when it finds an EOM marker on the tape. It's important to note that everything should be working as expected. This message is just "informational". There is a KB article on the http://now.netapp.com site, ntapcs1891. You could see this on an ordinary, non-NDMP dump or other tape operation as well as any NDMP-initiated tape operation. I hope this explanation helps. Let me know if there is anything else that i can help you with. Thanks Parag Patel Technical Support Engineer. Network Appliance Inc. Direct: 408-822-4776 Support and Upgrades: http://now.netapp.com/ ------------------------------------------------------------------------ ---------- Original Message ---------------------------------- From: Moshe Linzer <Moshe.Linzer(a)nsc.com> Date: Mon, 10 Sep 2001 10:46:53 +0300 >We are running 6.1R1, and we are seeing the following symptoms ever >since installing Veritas Netbackup and a new Qualstart AIT tape >library. The errors occur when a tape change occurs in the middle of a >backup. The 'solution' below seems to say that Veritas is timing out >waiting for NDMP to load the new tape. Does anyone know how to increase >this timeout in NetBackup? > >Thanks, > >Moshe > > Solution ID: ntapcs1891 > > Title: NDMP backup error message: Device 0b.4: Sense Data no error - >(0x0 - 0x0 0x2) - NetApp filer > > Problem Environment: > NetApp filer > F85 > F800 series > F700 series > F600 series > Data ONTAP 6.x > NDMP backup software > ONTAP 5.3 and earlier versions returned a 'SCSI bus reset' then retried >the command > > Problem Description: > Error message: [scsi.cmd.checkCondition:error]: Device 0b.4: Check >Condition: CDB 0x10: > Sense Data no error - (0x0 - 0x0 0x2) > Error message: Device 0b.4: Sense Data no error - (0x0 - 0x0 0x2) > > Fix: > 1. Check that a tape is loaded and ready (ONLINE). > 2. Check the configuration of the NDMP backup software. If using a >robotic tape library, then > make sure that the backup software is configured correctly to work with >the library. > > This symptom can also be seen when a dump or restore spans multiple >tapes, and the NDMP > software times out waiting for the tape change. Legato's default >timeout is 30 seconds, and > Veritas' default is zero seconds. In this case, the fix is to increase >the timeout in the NDMP > software. > Last updated: JUL 2001 > > Cause of this problem: > An application or process accessing the tape device has made an attempt >to write file marks > past the end of tape. > NDMP backup software is not configured correctly to work with the tape >device or library. > > > > ©Copyright 1996-2000 Primus Knowledge Solutions, Inc. All Rights >Reserved. > >-- >----------------------------------------------------------------------------- >Moshe Linzer | On the Internet, >IT Manager | >National Semiconductor, Israel | nobody knows you're a moron. >Phone: 972-9-970-2247 | >Fax: 972-9-970-2001 | - Network Magazine >Email: moshel(a)nsc.com | >----------------------------------------------------------------------------- > > > > > -- Steven N. Boyer UNIX/NT/NetApp Support HQUSCENTCOM General Dynamics --

1 0

Registry entries
by Chuck Ross 10 Sep '01

10 Sep '01

Hello, I have a filer (740) running 6.1R1. In my /etc/registry file I have entries for options.if.e0.dhcp.* I can find no info in the documentation relating to DHCP. I can also not find where these values get set. Any ideas? I ask because the dhcp.ip and dhcp.dns_servers have bogus ip values. It is not impacting the filer as far as I can tell but I would like to know the deal. Thanks Chuck Ross SIGNIANT Inc. Trusted Data Transfer Services www.signiant.com Email: Chuck.Ross(a)signiant.com

1 0

Filers and SCO Unix
by Uros Lampret 10 Sep '01

10 Sep '01

Any body using this combination? I have some issues with locking and openig files under SCO Unix using Filer DOT 6.0.1R3. _____________________________ 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

scsi.cmd.checkCondition:error when switching tapes during backup
by Moshe Linzer 10 Sep '01

10 Sep '01

We are running 6.1R1, and we are seeing the following symptoms ever since installing Veritas Netbackup and a new Qualstart AIT tape library. The errors occur when a tape change occurs in the middle of a backup. The 'solution' below seems to say that Veritas is timing out waiting for NDMP to load the new tape. Does anyone know how to increase this timeout in NetBackup? Thanks, Moshe Solution ID: ntapcs1891 Title: NDMP backup error message: Device 0b.4: Sense Data no error - (0x0 - 0x0 0x2) - NetApp filer Problem Environment: NetApp filer F85 F800 series F700 series F600 series Data ONTAP 6.x NDMP backup software ONTAP 5.3 and earlier versions returned a 'SCSI bus reset' then retried the command Problem Description: Error message: [scsi.cmd.checkCondition:error]: Device 0b.4: Check Condition: CDB 0x10: Sense Data no error - (0x0 - 0x0 0x2) Error message: Device 0b.4: Sense Data no error - (0x0 - 0x0 0x2) Fix: 1. Check that a tape is loaded and ready (ONLINE). 2. Check the configuration of the NDMP backup software. If using a robotic tape library, then make sure that the backup software is configured correctly to work with the library. This symptom can also be seen when a dump or restore spans multiple tapes, and the NDMP software times out waiting for the tape change. Legato's default timeout is 30 seconds, and Veritas' default is zero seconds. In this case, the fix is to increase the timeout in the NDMP software. Last updated: JUL 2001 Cause of this problem: An application or process accessing the tape device has made an attempt to write file marks past the end of tape. NDMP backup software is not configured correctly to work with the tape device or library. ©Copyright 1996-2000 Primus Knowledge Solutions, Inc. All Rights Reserved. -- ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, IT Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel(a)nsc.com | -----------------------------------------------------------------------------

1 0

sysstat giving bogus results if >2GB read in interval
by Chris Thompson 09 Sep '01

09 Sep '01

The NOW database suggests that bug 2689 ("sysstat output is inaccurate if displayed at a long interval") is fixed in recent versions of ONTAP, e.g. 6.1.1. I don't think so. See the start of the disk scrub tonight on an F740... ["sysstat -u 60" is running] CPU Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk ops/s in out read write read write age hit time ty util 1% 21 14 84 35 87 0 0 >60 100% 2% T 1% 1% 7 8 11 38 88 0 0 >60 100% 2% T 2% Sun Sep 9 01:00:00 BST [kern.uptime.filer:info]: 1:00am up 43 days, 6:54 194462270 NFS ops, 0 CIFS ops, 0 HTTP ops 16% 17 57 126 10546 141 0 0 >60 100% 3% T 18% 54% 40 572 520 1887065754 824 0 0 >60 100% 11% 5 62% 49% 13 44 56 3537004865 135 0 0 >60 99% 5% T 57% 51% 30 40 233 547830010 129 0 0 >60 99% 5% T 59% The unreasonable reported disk read rates are apparently due to more than 2^31 bytes being read during the recording interval. "sysstat -u 45" gets the numbers back in range: CPU Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk ops/s in out read write read write age hit time ty util 50% 9 15 65 37010 91 0 0 >60 100% 4% T 59% 51% 18 87 100 37068 188 0 0 >60 100% 4% T 59% 50% 5 10 9 37586 78 0 0 >60 100% 3% T 59% 51% 28 218 247 36076 327 0 0 >60 100% 5% T 58% 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: Jumbo Frames on a Toaster
by lkaptan＠pro-link.net 08 Sep '01

08 Sep '01

My company is a reseller of NetApp.I will deploy an F740 (6.1R1) for SAP , Lotus environment at a customer. Firstly I did the demo there and connected an RS6000 to the filer directly via gigabit interface. For better performance I wanted to enable jumbo frames and enabled it as manuals described and the customer did the configuration on the IBM side. But it did not work. because of the performance over gigabit(1500) and the functionality of the filer (snaprestore indeed) they decided to buy the filer. I will install it to their live environment where the servers will be connected to the filer via cisco gigabit switch. If anybody enabled jumbo frames in such environment the configuration of IBM will be very helpful. I dont think the problem is the Filer. thanks Original Message: ----------------- From: John Coke jcoke(a)ibeam.com Date: Fri, 7 Sep 2001 12:30:55 -0700 To: Toasters(a)mathworks.com Subject: Jumbo Frames on a Toaster 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) -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

1 0

multi volume dump fails
by Daniel Oxenhandler 07 Sep '01

07 Sep '01

Toasters, We are backing up an F-740, running ONTAP 5.3.6R2, with dump commands executed from a Solaris host using rsh. There is a Sun L9 stacker (DLT8000) directly attached to the filer. Recently, one of the qtrees exceeded the capacity of one tape. We are attempting to do a multi tape backup using the following syntax: rsh filer dump 0ubf 63 urst0a,urst0a /vol/vol0/home but the backup still fails at around 50GB when the first tape fills up: DUMP: Thu Sep 6 15:35:15 2001 : We have written 51991386 KB to tape. DUMP: Thu Sep 6 15:40:15 2001 : We have written 54129100 KB to tape. DUMP: Dumping tape file 2 on urst0a DUMP: Thu Sep 6 15:45:34 2001 : We have written 54896885 KB to tape. DUMP: Tape file 2 begins with blocks from inode 5777316 DUMP: Tape write failed. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/vol0/../snapshot_for_backup.381" snapshot. Any ideas? Daniel Oxenhandler Senior Network Engineer Sprint Laboratories 650-375-4281

2 1

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

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

06 Sep '01

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 > >

2 1

CIFS terminate for WTS
by Jeffrey Krueger 06 Sep '01

06 Sep '01

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

1 1

console connexion to F740 kibbled
by Lance R Bailey 06 Sep '01

06 Sep '01

we have a new F740 that i cannot use on the console of my lightwave CS800 terminal server. i am using the same CS800 to front a pair of F720 without problems but the F740 seems to put out text with the high bit set - completely unreadable. the F720's are fine. CS800 _| | |_ | | | F720 F720 F740 the connexion from the filers to the cs800 is a cat5 cable that plugs into the back of the CS800, and then into an RJ-db9 adapter which in turn plugs into the back of a filer. if i unplug the adapter from the working 720 and plug it into the 740, then i get gibberish on that port. if i unplug the adapter from the gibberish 740 and plug it into the 720, suddenly that connexion works. ie, if i do this: CS800 _| \/ | /\ F720 F720 F740 the problem stays with the 740. we swapped out the motherboard - no good. we swapped out the entire head - no good. we changed cables, adapters - no good. we changed ports on the CS800 - no good. both ports on the CS800 are 9600 8N1. we attached a laptop directly to the F740 with a filer supplied cable and that worked. for some reason, it seems that the CS800 and the F740 (but not the F720) have a high order bit problem. has anyone seen this? even better, has anyone seen a solution to this? -- email: lance_bailey(a)pmc-sierra.com box: Lance R. Bailey, unix Administrator vox: +1 604 415 6646 PMC-Sierra, Inc fax: +1 604 415 6151 105-8555 Baxter Place http://www.lydia.org/~zaphod Burnaby BC, V5A 4V7 Everywhere is walking distance if you have the time -- Steven Wright

3 2

Permissions
by Jennifer Armenta 06 Sep '01

06 Sep '01

Having issues with permissions. When trying to mount to 2 different SUN servers (Unix mode /vol/vol2/backup) It doesn't appear the id's are being picked up correctly any advice?

1 0

RE: Unexplainable unresponsiveness of F820
by Ehrhart, Rick 06 Sep '01

06 Sep '01

The problem is fixed in 6.1.1 with bug 40350 which also covers disconnecting telnet while there is pending output. - Rick - ----------------------------------------------------------------- Rick Ehrhart Network Appliance "Give me bandwidth or give me death" > -----Original Message----- > From: Kerry Schwab [mailto:Kerry.Schwab@wnco.com] > Sent: Wednesday, September 05, 2001 3:33 PM > To: mcope(a)isisph.com > Cc: toasters(a)mathworks.com > Subject: Re: Unexplainable unresponsiveness of F820 > > > When I have run into the bug, it didn't seem to have anything > to do with how busy the filer was. > > It *did* seem to be related to pending output on the telnet > connection. So, if you connected, ran a command, and > then closed the telnet connection while the filer was still > sending results, the filer would freeze. > > Another scenario is when "console log" messages randomly > stream from the telnet conneciton. Closing the connection > while the console logs message is being written triggers it also. > > It interesting that you mentioned "Big Brother", because I never > hit the bug while actually typing interactively via telnet. > It was always > via some automated telnet connection ( Expect, Perl, etc). I guess > a human typing always tends to wait before sending the <ctrl-D>, while > the scripted connections aren't anticipating "extra output". > > == > Kerry > > > >>> <mcope(a)isisph.com> 09/05/01 04:46PM >>> > > > Kerry, > > Thanks for the info. I use Big Brother (bb4.com) to monitor > the Filers. One of > the things it does every 5 minutes is open and close a telnet > session to test > telnet. It's a pretty ugly method because it just kills the > telnet session as > opposed to closing it. The problems on the previous Filer > only manifested when > it was getting hammered. I've been using Big Brother for a > number of months now > and haven't had any problems keeping telnet sessions open to > a Filer. However, > I can imagine where this could be a problem if the Filer is > really busy and then > one of these ugly telnet checks occurred and pushed it over the edge. > > Thanks again, > > Michael > > On 9/5/2001 2:16:07 PM, "Kerry Schwab" <Kerry.Schwab(a)wnco.com> wrote: > > I've run into a bug with the telnetd daemon on the F820. > > Closing a telnet session to the filer while it has pending > > output sometimes causes the whole filer to "hang". > > > > This is occuring on 6.0.1R3. > > > > I did find some related bugs in the knowledge base, > > but I've resorted to not using the telnet interface for now. > > > > == > > Kerry > > > > > > > > > > >>> <mcope(a)isisph.com> 09/05/01 10:46AM >>> > > > > > > I've recently moved files from a F740 onto a new F820. > This happened > > on Monday > > and on Tuesday morning the F820 suddenly stopped serving data. It > > became so > > unresponsive that I was unable to even get in thru the console. I > > got prompted > > for a password but it never got to a command line prompt. The Filer > > didn't > > appear to be excessively busy beforehand and the network connection > > (Gigabit) > > still appeared to be fine. Basically, the Filer appeared fine > > externally and > > the LCD panel showed that there were 0 ops a second. The only way I > > could get > > the Filer "running" again was to cycle power. > > > > The Filer has been fine since then. There were no messages in the > > syslog and it > > didn't dump a core file (I know now how to force it to dump > a core for > > diagnosis), so NetApp tech support hasn't been able to provide much > > assistance > > or explanation. > > > > I've seen this same behavior twice on the the F740 in the last 2 > > months but that > > had been diagnosed as a faulty Fibre Channel controller seizing up > > when the > > workload got too high. Other than the actual data files, the only > > thing these > > two Filers have in common is Data ONTAP 6.1R1. I'm running 6.1R1 on > > two other > > Filers and have had no problems. It just seems very coincidental > > that I didn't > > experience this on the F740 until after I installed this version of > > ONTAP. > > > > Anyone else seen this behavior before or noticed any irregularities > > with 6.1R1 > > (I'm not running in a cluster so the latest updates/bug fixes don't > > appear > > helpful) > > > > Thanx, > > > > > > 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

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