toasters

toasters@lists.teaparty.net

13514 discussions

iSCSI MPIO Support/Experiences
by Alan.McLachlan＠didata.com.au 28 Oct '04

28 Oct '04

Hi Evan, MPIO is required for load balancing and failover if you are using the Intel iSCSI HBA (TOE card). Intel do not provide their own teaming driver for this card. If you are using the MS software iSCSI initiator with regular 1000BaseT Ethernet NIC's, you can use the regular teaming drivers that come with your NIC's. i.e. for Intel Pro1000 NIC's use the "Adaptive Load Balancing" driver to create a virtual NIC from the two physical NIC's, then bind the Microsoft software iSCSI initiator to the virtual NIC. Using MPIO and the iSCSI HBA's is a more expensive solution (due to the cost of the HBA's), but worth considering if you feel you need to minimise CPU overhead on your application host. regards, Alan McLachlan ___________________________________ Solution Architect - Data Centre Solutions Dimension Data Australia Alan.McLachlan(a)didata.com.au Tel. +61 (0)2 61225123 Fax +61 (0)2 62486346 Mobile 0428 655644 ----- Forwarded by Alan McLachlan on 28/10/2004 09:52 AM ----- "Evan Battle" <ebattle(a)Intellimark-IT.com> Sent by: owner-toasters(a)mathworks.com 27/10/2004 11:49 PM To: <toasters(a)mathworks.com> cc: Subject: iSCSI MPIO Support/Experiences <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />I have seen conflicting information on the site regarding MPIO support. The SnapDrive/Ontap Compatibility Matrix shows iSCSI is not supported for MPIO, however a press release dated August 23, 2004 indicated that NetApp does have an MPIO solution for the MS implementation of iSCSI. Does the SnapDrive MPIO driver now work w/ iSCSI? Is this dependent upon using the MS iSCSI initiator and not an iSCSI HBA? Also, do any of you have any experience implementing a MPIO iSCSI solution? If so, what have been your experiences. Thanks, Evan ****************************************************************************** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ******************************************************************************

1 0

please take me off the toasters email list. Thanks.
by Mukarram Syed 27 Oct '04

27 Oct '04

===== Mukarram Syed muksyed(a)yahoo.com __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

iSCSI MPIO Support/Experiences
by Evan Battle 27 Oct '04

27 Oct '04

1 0

RE: spares disks no more equivalent from one filer to another one
by Derek Lai 26 Oct '04

26 Oct '04

The ability to take spare disks from system to system used to be true but it broke a while ago. There is also the issue of the DS14 MK1 vs. MK2 shelf issue. The old drives that you have in DS14 MK1 system can not be inserted into DS14 MK2 shelves either. But that is progress. I think NetApp in general tries pretty hard to be backward compatible where they can. The new "Universal" keyed drives on the MK2 shelves can be inserted into MK1 shelves as well. Are you saying that you can zero a disk on a 6.5 system to be used in a 6.4 system? I will not work either with just a simple spares_zero command (which only zeros a spare). The problems is DataOntap will refuse to put the drives into the system. You have to completely rewrite the label on the drive. To do so requires that you reboot and drop into the maintenance menu and then pick the option to re-label the drive. Anyone know why this is the case? I can't think of a good reason for doing so. The rationale is suppose to be that once you upgraded the system to 6.5, you need to revert and do extra work to go back to running 6.4. But this is a pain when you maintain a large number of filers and have to now keep track of one other unnecessary thing. I think at a minimum NetApp should do a better job of proactively telling the sys admins so they don't get surprised at the last minute. If we know about these sort of things we can plan ahead and avoid the problems. Derek -----Original Message----- From: Stephane [mailto:stephane.bentebba@fps.fr] Sent: Monday, October 25, 2004 12:41 PM To: toasters(a)mathworks.com Cc: Jean-Jacques ARNOUX Subject: spares disks no more equivalent from one filer to another one for those who want to know about : netapp used to code its Ontapp soft the way it permit any spare from one filer to go to another one, transparently (your hand doing the job though), hot swappable and so on you were able to keep one spare in each filer and one extra disk in a safe place (in case of emergency) now there is a little trick that worth to be known : if a some of your filer are in >= 65 and other filer are in <= 64 you can get a 64 spare disk and put it in one of your 65 filer but you can't do the reverse also if you have putted a disk in 65 (just as like a spare one) you cant put it back in a 64 filer ontap code something - i dont know what - that trigger an error message when you put a 65 spare disk in a 64 filer : "X..._ST... this disk is from a newer version, either remove this disk or upgrade the os" i was told you have 3 possibilities : - ask netapp for a disk as a replacement to this one - put the disk in a 65 ontap which will "write" on the disk a way it could be include in a 64 system - upgrade the dot in 65 i tested the second solution unsuccessfully and in case you don't want to wait for a replacement and do not want to upgrade (for the moment) the only solution i found is to zeroing the disk zeroing the disk mean erasing all data on all disks in order to reinstall a new filesystem from scratch so, do so only if u know what you are doing bye

2 1

RE: cifs.request.overdue:info]: CIFS: Overdue CIFS request from x xx.xxx.xxx.xxx in state 90, duration 4715 seconds, request type 4, uid 20 48, pid 51966, tid 64, mid 59393.
by Ngoh, Clarence 25 Oct '04

25 Oct '04

A quick follow up to this mail. We are in the midst of isolating this fault and our target of suspicion is our AV box. Virus scanning on the filer was disabled for an extended period of time and the error messages did not appear. Trend has provided a hotfix for us which is being tested. Fellow toasters running Trend version, 5.61.0.1025, Engine version 7.100-1003 beware if you are experiencing similar symptoms and error messages. Cheers Clarence. -----Original Message----- From: Phil Dean [mailto:Phil.Dean@aiservices.com.au] Sent: Friday, 22 October 2004 10:23 PM To: Muhlestein, Mark; toasters(a)mathworks.com Subject: RE: cifs.request.overdue:info]: CIFS: Overdue CIFS request from xxx.xxx.xxx.xxx in state 90, duration 4715 seconds, request type 4, uid 2048, pid 51966, tid 64, mid 59393. Mark, Way in the past we have had virus scanning issues and worked closely with Trend to fix them all up. The error's we use to get from that side were CIFS: Virus scanner [scanner] completed scan on [file] but original request was not found. We know quite a bit about that side of things, the ip addresses in the xxx.xxx.xxx.xxx are clients workstations, The clients also have virus scanning enabled but another outsourcing company looks after the desktops. We have sent up packet traces and perfstat's today and hope they do find something. One of the ones I looked at in more details, after getting the user to log out and then terminating the session for her on the filer, it was still active, She logged back on and opened three apps, yet in open files under hyena she had outlook pst and xls's where she had not opened outlook or a file within excel, and there were multiple instances of these files roughly 150 or so. Phil Dean Australian Innovative Services Phone: 0407 478 695 Email: Phil.dean(a)aiservices.com.au Web: www.aiservices.com.au ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Australian Innovative Services CONFIDENTIAL The information, files and contents of this email are confidential to Australian Innovative Services and the intended recipient. Forwarding, copying, reading, or downloading of this email is otherwise prohibited From: Muhlestein, Mark [mailto:mark.muhlestein@netapp.com] Sent: Fri 22/10/2004 2:13 PM To: Phil Dean Subject: RE: cifs.request.overdue:info]: CIFS: Overdue CIFS request from xxx.xxx.xxx.xxx in state 90, duration 4715 seconds, request type 4, uid 2048, pid 51966, tid 64, mid 59393. Are you running virus scanning? Request type 4 is a close, which is only slow when virus scanning is enabled. Maybe what is happening is that you are copying a huge zip file (for example) and the scan is taking a very long time. Mark -----Original Message----- From: Phil Dean [mailto:Phil.Dean@aiservices.com.au] Sent: Thursday, October 21, 2004 8:42 PM To: toasters(a)mathworks.com Subject: cifs.request.overdue:info]: CIFS: Overdue CIFS request from xxx.xxx.xxx.xxx in state 90, duration 4715 seconds, request type 4, uid 2048, pid 51966, tid 64, mid 59393. We currently have the following error messages being generated on two of our Filers. There is current a Bug ID for a similar error message but with the Request Type being 5 instead of 4. We have an open Sev 1 case with NetApp. Has anyone else experienced this particular issue and if so a suggested procedure to follow. Client issues relating from this problem have been anything from unable to map drives, workstations freezes, slowness to access files/folder/shares. This has been occurring for the past two days and there have been no filer changes done on the systems for many weeks. Hardware Filer head has had diags run on it which was 100% successful. Phil Dean Australian Innovative Services Phone: 0407 478 695 Email: Phil.dean(a)aiservices.com.au Web: www.aiservices.com.au ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Australian Innovative Services CONFIDENTIAL The information, files and contents of this email are confidential to Australian Innovative Services and the intended recipient. Forwarding, copying, reading, or downloading of this email is otherwise prohibited ************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************

1 0

Volumes and 144GB drives
by John Breyfogle 25 Oct '04

25 Oct '04

Folks, Just curious as we're probably getting new NetApp boxes with 144GB drives: How are people handling 144GB drives with the tradeoff of volume size, back up windows, parity drive, nested qtree limits, etc. I understand at DOT 7.x there will be a logical volume manager, but in the meantime, using a 3 disk raid group to get a managable volume size will be kind of costly in parity drives, but a 6-8 drive raid group is rather huge for backup and, last I knew, we couldn't have nested qtrees. Thanks in advance John Breyfogle

2 1

RE: Audit Logging?
by Bui, Marcus 25 Oct '04

25 Oct '04

You can do a Windows CIFS audit on the directory or share. 1. Using a Windows Admin account select the folder/share, Properties, Security, Advanced (on Security tab), Auditing. 2. Select Add. The User/Group will appear. Leave the 'Object Type' default. The 'Locations' is the Windows Domain where the user account is located. The 'Object Name' is the group or account you want to audit. Select the group "Everyone" for the 'Object Name' should audit every account to this folder/share. Click 'Ok'. 3. The Audit Object dialog should appear which allows you to select which entry to audit against. Typically, you want "Successful" for each of the events you want to audit. 4. Select 'Apply these auditing entries to objects and/or containers within this container only' if you want apply to any subdirectories. Depending on how many clients are accessing this location and the number of objects you are auditing, the log can get pretty big. You can use a script to save the log and rename for each day. Hope this helps. Marcus Bui -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Stewart, John Sent: Friday, October 22, 2004 2:14 PM To: 'toasters(a)mathworks.com' Subject: Audit Logging? We've got an F740 doing cifs and nfs, with 3 shelves and ~400GB on it. We've got a situation where some critical, sensitive, files were lost. Permissions all look good, so I suspect that one of the people with write access to that directory borked something up (one of them uses Windows briefcases to sync up some files - that could have gone haywire). Anyway, this has brought up the request to do some sort of auditing on this (and perhaps other) directories to record who created/edits/deletes files. Is this possible? With the standard software, or is there some other product we need to purchase? thanks! johnS ----------------------------------------- Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

Undeliverable: Re: Re: Document
by System Administrator 24 Oct '04

24 Oct '04

Your message To: kathleen.ng(a)leehishammuddin.com.my Subject: Re: Re: Document Sent: Mon, 25 Oct 2004 01:46:36 +0800 did not reach the following recipient(s): kathleen.ng(a)leehishammuddin.com.my on Mon, 25 Oct 2004 02:49:20 +0800 The recipient name is not recognized The MTS-ID of the original message is: c=us;a= ;p=leehishammuddin;l=LHKL204102418494721F22B MSEXCH:IMS:LEEHISHAMMUDDIN:HQ:LHKL2 0 (000C05A6) Unknown Recipient

1 0

[Attachment Removed] Re: Re: Document
by MAILER-DAEMON＠leehishammuddin.com.my 24 Oct '04

24 Oct '04

Mail transmission to <kathleen.ng(a)leehishammuddin.com.my> has had attachment "your_document.pif" removed, as attachments of this type are not allowed.

1 0

Audit Logging?
by Stewart, John 24 Oct '04

24 Oct '04

We've got an F740 doing cifs and nfs, with 3 shelves and ~400GB on it. We've got a situation where some critical, sensitive, files were lost. Permissions all look good, so I suspect that one of the people with write access to that directory borked something up (one of them uses Windows briefcases to sync up some files - that could have gone haywire). Anyway, this has brought up the request to do some sort of auditing on this (and perhaps other) directories to record who created/edits/deletes files. Is this possible? With the standard software, or is there some other product we need to purchase? thanks! johnS

2 1

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