toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

where to find man pages
by Josef Radinger 21 Apr '08

21 Apr '08

hi, i seek now for around 3 hours in several places (i even looked at the source of the html-pages na_admin.mm[l|i]) the link to download the man-pages for ontap (7.2.3). can someone send me that link? thanks ps.: those mml and mmi files look very interesting (and potential dangerous). -- MfG Josef Radinger it-services Medizinische Universitaet Innsbruck

1 0

Re: RJ45 Serial
by Webster, Stetson 21 Apr '08

21 Apr '08

For a second, I was thinking that you used a filer to login to a cisco serial console ;-) Pardon brevity, typos, etc; sent from mobile. -----Original Message----- From: Steve Rikli [mailto:sr@genyosha.net] Sent: Sunday, April 20, 2008 09:05 PM Pacific Standard Time To: Peter Rosenthal Cc: toasters(a)mathworks.com Subject: Re: RJ45 Serial On Mon, Apr 21, 2008 at 04:29:28AM +0100, Peter Rosenthal wrote: > Hi Folks, > > RJ45 console serial pinouts look the same as cisco. Has anyone tried using a > cisco serial cable on a filer with an RJ45 serial console? We have done the reverse -- e.g. use the FAS250/270/3050/etc. RJ45:DB9 console cable on Cisco gear with RJ45 serial console, and it worked fine. So I assume it would work in the other direction too. sr.

1 0

CIFS: Error on named pipe
by Alexander Schalek 21 Apr '08

21 Apr '08

Hi, one of our customers is geting this error constatly: Tue Apr 15 14:20:19 GST [abcfas01: cifs.pipe.errorMsg:error]: CIFS: Error on named pipe with ADS10: Error connecting to server, open pipe failed Tue Apr 15 14:20:19 GST [abcfas01: smbrpc.pipeCreate.fail:error]: CIFSRPC: Attempt to create pipe LSA for LsarLookupNames failed with error 0xc000005e. When I ran cifs domaininfo, everything looks fine: abcfas01> cifs domaininfo NetBios Domain: ABCNET Windows 2000 Domain Name: abcnet.com Type: Windows 2000 Filer AD Site: abc-def Current Connected DCs: \\ADS10<file:///\\ADS10> Total DC addresses found: 14 Preferred Addresses: X.X.X.X ADS10 PDC Favored Addresses: X.X.X.X PDC Other Addresses: Y.Y.Y.Y PDC Z.Z.Z.Z PDC Not currently connected to any AD LDAP server Preferred Addresses: None Favored Addresses: None Other Addresses: None I couldn't find any information on the now site or google search regarding this error. Any ideas? Thanks in advance! Regards, alex

2 1

Re: Upgrade 900 series to 3000 series filer
by Davin Milun 19 Apr '08

19 Apr '08

Strangely, the doc that NetApp pointed me to, when I opened a support case for upgrading a pair fo 960's and 3040's, does not include the mailbox destroy commands: http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS90… I've asked if they're needed - hopefully I'll get a meaningful response back (rather than a suggestion that I go pay for some NetApp Professional Services to get upgrade help - which was the other half of the response that pointed me to that doc). Davin. At 8:36, on Mar 18, 2008, tmac wrote: > Thanks Steve. > > I knew it was little more involved these days... > > And if you forget the "mailbox destroy local" you will have a > panic-reboot loop that can only be fixed by running said command. > > --tmac > > On Tue, Mar 18, 2008 at 7:26 AM, Stephen C. Losen > <scl(a)sasha.acc.virginia.edu> wrote: > > > > > we need to replace an older 900 series cluster with a new 3070 cluster. i > > > want to make sure i dont miss anything or gotchas etc, looked on NOW but > > > didnt find a complete guide or maybe i searched wrong. > > > > > > > > > we have 2 new 3070 heads and cables in the box and here is the current plan > > > > > > 1) shutdown and unmount storage nfs/iscsi > > > 2) update to current ontap 7.2.4 (currently at 7.2.3) > > > 3) reboot and allow shelf/disk firmware updates to complete > > > 4) shutdown and remove 9XX heads and cabling > > > 5) install 3070 heads, recable primary and secondary loops > > > 6) power on heads, ensure licenses are current and installed and verify > > > volumes > > > 7) reload ontap with 3000 series architecture release 7.2.4 > > > 7) update rc file with new interface names > > > > > > any major gaps in the above or comments from folks who have done this > > > recently? > > > > > > i went over this with the netapp tech rep and it seems pretty > > > straightforward but always want peer review :) > > > > > > > We recently upgraded a 960 pair to a 6040 pair. We had to switch > > to software disk ownership. Before removing the 960 heads, we halted > > them, unplugged the cluster interconnect cables, and unplugged the > > "B" shelf loops from both 960 heads (so that each head could see > > only its own disks, no partner disks). Then we booted the 960s > > to maintenance mode and ran: > > > > disk upgrade_ownership > > > > We halted the 960 heads, powered them off and removed them. > > > > We installed the 6040 heads, but did not connect the cluster > > interconnect cables and did not attach any of the shelf "B" loops > > to either head. (Each 6040 head could only see its own disks, > > no partner disks.) We booted the 6040 heads to maintenance mode > > and ran this on both heads: > > > > disk remove_ownership all > > disk assign all > > disk show -v > > > > and on one head we ran > > > > storage release disks > > mailbox destroy local > > > > Then we shut down, connected the "B" loops and cluster > > interconnects and booted up normally. > > > > If the 3070 uses software disk ownership, then you'll want to > > get the proper procedure from Netapp. Don't take my word on > > magic maintenance mode commands. > > > > > > Steve Losen scl(a)virginia.edu phone: 434-924-0640 > > > > University of Virginia ITC Unix Support > > > > > > > > > > -- > --tmac > > RedHat Certified Engineer #804006984323821 (RHEL4) > RedHat Certified Engineer #805007643429572 (RHEL5) > > Principal Consultant, RABA Technologies

1 0

"nfs_hist" and "lun hist" output questions
by Pascal Dukers 17 Apr '08

17 Apr '08

The nfs_hist command shows e.g. the number of reads that get serviced with a specific response time: v3 read: 4817066 (blocking requests) - millisecond units 0 1 2 3 4 5 6 7 4144583 475420 86036 25125 16078 11301 9468 6301 What is the exact range for e.g. "0"? I would expect it to be between 0 and 1 ms and not exactly 0 ms. Can someone confirm this? And another question about the "lun hist" command. What is the difference between scsi_write and scsi_write_extended? -- View this message in context: http://www.nabble.com/%22nfs_hist%22-and-%22lun-hist%22-output-questions-tp… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

3 2

AW: CIFS: Error on named pipe
by Alexander Schalek 16 Apr '08

16 Apr '08

That's not a specific user problem. This error also occurs when there is no user accessing the filer. Von: George, Andrew [mailto:Andrew.George@anz.com] Gesendet: Mittwoch, 16. April 2008 02:17 An: Alexander Schalek; toasters(a)mathworks.com Betreff: RE: CIFS: Error on named pipe If its working for everyone else I'd be asking what's different about that user. do a cifs lookup <domain>\<Userid> to make sure the user account is resolvable from the filer get the user to try a different PC (to see if its a problem with the connection settings in the client registry) Check the user and computer account in AD for weirdness ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Alexander Schalek Sent: Wednesday, 16 April 2008 3:54 AM To: toasters(a)mathworks.com Cc: Alexander Schalek Subject: CIFS: Error on named pipe Hi, one of our customers is geting this error constatly: Tue Apr 15 14:20:19 GST [abcfas01: cifs.pipe.errorMsg:error]: CIFS: Error on named pipe with ADS10: Error connecting to server, open pipe failed Tue Apr 15 14:20:19 GST [abcfas01: smbrpc.pipeCreate.fail:error]: CIFSRPC: Attempt to create pipe LSA for LsarLookupNames failed with error 0xc000005e. When I ran cifs domaininfo, everything looks fine: abcfas01> cifs domaininfo NetBios Domain: ABCNET Windows 2000 Domain Name: abcnet.com Type: Windows 2000 Filer AD Site: abc-def Current Connected DCs: \\ADS10<file:///\\ADS10> Total DC addresses found: 14 Preferred Addresses: X.X.X.X ADS10 PDC Favored Addresses: X.X.X.X PDC Other Addresses: Y.Y.Y.Y PDC Z.Z.Z.Z PDC Not currently connected to any AD LDAP server Preferred Addresses: None Favored Addresses: None Other Addresses: None I couldn't find any information on the now site or google search regarding this error. Any ideas? Thanks in advance! Regards, alex "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

2 2

Serious A-sis bugs
by Darragh, Stephen J (CSC) (US SSA) 16 Apr '08

16 Apr '08

If you are running a-sis with 7.2.3 or 7.2.3, there are a few bugs that can cause the filer to panic and mark that volume offline forcing a wafl_check on the containing aggregate. Not only that, but we had to netboot a developer release and had extensive outages. We have been told that 7.2.4 had fixed these bugs, but if you have run asis on an old version, the bug may be there dormant. I believe these were the bugs that were identified in our incident report. bug 256799 Bug 266312 Bug 276084 bug 266312 bug 251673 The bug hit our primary storage, and it also his the VSM volumes on our DR filer, and it would is in the ACL/directory of the backup tapes as well.

6 6

Oddball SnapManager for SQL retention issue
by Raj Patel 16 Apr '08

16 Apr '08

Hi all, Is there a definitive command for snapshot deletion/retention - we've been struggling with this for awhile now and no combination of the '-D' or '-R' flag seems to do what we'd like it to do. For most our our SQL servers this isn't a real issue - once every few months we can manually remove old snaps; however we have a server that has a big database and a high-rate of change so we'd like to take snaps more often but lower the retention time - unfortunately as the deletions don't occur we fill the volume fairly quickly. The string we're using as a SQL 2005 agent job is similar to this - C:\Program Files\NetApp\SnapManager for SQL Server\SmSqlBi.exe -H "INFSQL1" -D 4 -R -G -S "INFSQL1" -C 8 "ArchiveManager" -Q "INFSQL1" -UM Has anyone else had similar issues or is there something I'm missing in the command string ? Alternatively is there a sdcli.exe / smsqlbi.execommand I can schedule to remove x number of old snaps ? Thanks in advance, Raj.

1 0

Wafl susp in a sim
by Nicholas Bernstein 15 Apr '08

15 Apr '08

I'm running the command "wafl_susp" and am getting the error: "found zero suspended messages" -- has anyone seen this before? Very strange. I tried this on a sim and a filer. Ontap 7.2.1. -- Nicholas Bernstein Technologist, Consultant, Instructor http://nicholasbernstein.com

6 5

FW: Serious A-sis bugs
by Freeman, Larry 14 Apr '08

14 Apr '08

Hi Stephan, regarding the issue you've described below, we are in the process of writing a Customer Service Bulletin and notifying users that all dedupe (A-SIS) systems require a mandatory upgrade to 7.2.4. I don't want to diminish the severity of this issue, but I think its important to point out that very few users have experienced panics as a result of this, but of course if you are one of those few that has...that is of little consolation. I apologize for the aggravation this issue caused you. NetApp felt it was very important to first identify the root cause and then define a corrective action plan before notifying our dedupe users. The corrective action plan will include the above mentioned upgrade to 7.2.4 and also tools for users to scan and repair any inconsistencies in their ACL or directory metadata without having to live through the kind of experience you were faced with. I'd also like to mention that no file data corruption occurs as a result of this issue, only inconsistencies between metadata and data blocks which can be detected and repaired with the maintenance tools we will provide. Again, not trying to diminish the seriousness of this issue, believe me it has a very high priority at NetApp. Notifications will begin next week. If anyone else on toasters has questions about this issue or would like more info, please contact NetApp Customer Support. Thanks, Larry Freeman NetApp > From: "Darragh, Stephen J \(CSC\) \(US SSA\)" > <stephen.j.darragh(a)baesystems.com> > Date: April 10, 2008 8:04:33 AM PDT > To: <toasters(a)mathworks.com> > Subject: Serious A-sis bugs > > If you are running a-sis with 7.2.3 or 7.2.3, there are a few bugs > that can cause the filer to panic and mark that volume offline forcing > a wafl_check on the containing aggregate. > Not only that, but we had to netboot a developer release and had > extensive outages. > > We have been told that 7.2.4 had fixed these bugs, but if > you have run > asis on an old version, the bug may be there dormant. > > I believe these were the bugs that were identified in our incident > report. > > bug 256799 > Bug 266312 > Bug 276084 > bug 266312 > bug 251673 > > The bug hit our primary storage, and it also his the VSM volumes on > our DR filer, and it would is in the ACL/directory of the backup tapes > as well. > > > > >

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