toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Re: How to re-fail a disk to trigger autosupport?
by Adam McDougall 23 Sep '08

23 Sep '08

Thanks! I got some progress with that. I was able to priv set advanced and 'disk unfail' while the system was up. I should have searched NOW. Webster, Stetson wrote: > > > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=185042 > <http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=185042> > > > > *Stetson M. Webster** > *Professional Services Engineer - NCDA, NCIE-SAN > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com <mailto:Stetson.Webster@netapp.com> > > netapp.com/accelerate > <http://www.netapp.com/us/company/events/accelerate/?ref_source=eSig> > > http://media.netapp.com/images/accelerate-sig2.jpg > <http://www.netapp.com/us/company/events/accelerate/?ref_source=eSig> > > -----Original Message----- > From: Adam McDougall [mailto:mcdouga9@egr.msu.edu] > Sent: Tuesday, September 23, 2008 12:28 PM > To: toasters(a)mathworks.com > Subject: How to re-fail a disk to trigger autosupport? > > > > We had a disk fail in a shelf on a filer with expired support, which > > created a case at the time but it was closed without replacement due to > > lack of support on the filer. However, as part of the support agreement > > on a new cluster, it was in a shelf that would be covered when attached > > to one of the new filers. Now that we have that shelf attached to the > > new filer, all I get is: > > Mon Sep 22 17:18:22 EDT [hostname: disk.init.failureBytes:error]: Disk > > 0b.23 failed due to failure byte setting. I tried replugging the disk > > and all I got was the same message in the log. After the message in the > > log, the filer acts like the disk isn't present as per commands below. > > How can I trick it intro triggering an autosupport so my bad disk gets > > replaced? Thanks. > > > > > disk fail 0b.23 > > disk fail: Disk 0b.23 not found > > > > > disk show 0b.23 > > DISK OWNER POOL SERIAL NUMBER > > ------------ ------------- ----- ------------- > > >

1 0

How to re-fail a disk to trigger autosupport?
by Adam McDougall 23 Sep '08

23 Sep '08

We had a disk fail in a shelf on a filer with expired support, which created a case at the time but it was closed without replacement due to lack of support on the filer. However, as part of the support agreement on a new cluster, it was in a shelf that would be covered when attached to one of the new filers. Now that we have that shelf attached to the new filer, all I get is: Mon Sep 22 17:18:22 EDT [hostname: disk.init.failureBytes:error]: Disk 0b.23 failed due to failure byte setting. I tried replugging the disk and all I got was the same message in the log. After the message in the log, the filer acts like the disk isn't present as per commands below. How can I trick it intro triggering an autosupport so my bad disk gets replaced? Thanks. > disk fail 0b.23 disk fail: Disk 0b.23 not found > disk show 0b.23 DISK OWNER POOL SERIAL NUMBER ------------ ------------- ----- -------------

1 0

Serial Connection to NetApp FAS - Command Line Documentation
by Zeeshan 22 Sep '08

22 Sep '08

Dear all hi... does anyone have a guide/reference for the commands used, when we connect to the filer through serial connection...i am more interested in things/commands to do when connecting to the filer through serial IO port for the FIRST TIME... thanx

3 2

Re: Identify traffic per IP address without using pktt
by Filip Sneppe 21 Sep '08

21 Sep '08

Thanks for all the answers. Most of these methods of obtaining information I as already familiar with, but it's good to know that I shouldn't be looking for a one-size-fits-all command at this moment. Best regards, Filip

1 0

Re: bad raid label version
by Cristian Rojas 21 Sep '08

21 Sep '08

Just out of curiosity, why do you want to revert to 7.2? Cris ----- Original Message ---- From: "Strickland, Michael" <Michael.Strickland(a)netapp.com> To: Stefan Funke <bundy(a)usage.de>; Michael Schipp <mschipp(a)asi.com.au> Cc: Christian Mikovits <christian.mikovits(a)cubit.at>; toasters(a)mathworks.com Sent: Saturday, September 20, 2008 3:12:14 AM Subject: RE: bad raid label version From Ontap, "disk unfail -s <disk>" should work in this situation. If the disks are "label broken" I believe. Assuming that there is no needed data on said disks. - Michael NGS -----Original Message----- From: Stefan Funke [mailto:bundy@usage.de] Sent: Thursday, September 18, 2008 11:26 AM To: Michael Schipp Cc: Christian Mikovits; toasters(a)mathworks.com Subject: Re: bad raid label version Hi! I've had the same problem. NetApp suggests: - Lookup the disks which show the error, - Reboot the filer and press ctrlC, - From the 1-5 menu, choose option 5 to boot into maintenance mode, - Clear the label on those disks by typing: label wipe <disk_ID> Note: For Data ONTAP 7.2, use label makespare instead of label wipe for new disks. Example: *> label makespare 6b.69 label makespare: Disk 6b.69 forced to be a SPARE disk Michael Schipp schrieb: > "Label wipe" I think > > From diag mode > > -----Original Message----- > From: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] On Behalf Of Christian Mikovits > Sent: Wednesday, 17 September 2008 7:19 AM > To: toasters(a)mathworks.com > Subject: bad raid label version > > hey guys. > > i've setup a filer with 7.3 but now i want to revert to 7.2; > > everythings fine, but 2 disks remain with "raid label" 9 an are > unusable. > > revert_to isn't working; disk fail/unfail is impossible (is not a file > system disk); > > scsi format isn't working either... > > any suggestions? > > greets, > > chris > > > > > > ********************************************************************** > ************** This footnote confirms that this email message has been > scanned by PineApp Mail-SeCure for the presence of malicious code, > vandals & computer viruses. > ********************************************************************** > ************** > > > >

1 0

Test tape read speed
by A Darren Dunham 19 Sep '08

19 Sep '08

I'm trying to restore a file on a filer (via NetBackup) and the restore is *crawling* (a few KB/s on avg). One test I'd normally do would be to simply mount this tape up on the system and test that I could read it quickly. Is there any way to do this directly on the filer? I see 'dd', but I don't see how to read from the tape device. I don't think I can run a 'restore' because the data on the tape will be wrapped with NetBackup header information. I just want to test that the data can be read quickly. So actually interpreting the data isn't important at this point. Thanks. Background: Directly attached LTO3 drive. Backups are normally nice and speedy (50+ MB/s). ndmpd probe suggests that it's read 15GB of data in over 24 hours. *way* too slow. -- Darren

6 9

Identify traffic per IP address without using pktt
by Filip Sneppe 18 Sep '08

18 Sep '08

Hi, When using "sysstat" from the command line, it's very easy to get an idea of the network throughput that is currently being handled by the filer, and with commands like "vif stat" it's easy to get an idea on the interfaces that are transmitting or receiving this traffic. However, I am wondering if is it possible to get an idea on the client IP addresses that are generating most of the network traffic without having to resort to pktt every time, then copying over the capture file and analyzing it afterwards ? Are there any counters availble from a command that show how much traffic a particular IP address has sent/received ? I tried various commands (eg. netstat has a few interesting options) but couldn't find anything that solved my problem. At the moment, if I need to determine the hosts that are using most of the iSCSI or NFS bandwidth, I have to resort to pktt, and I am looking for a easier way to achieve what I want. Ideally, I'd like to get information on the protocols and ports involved too, but having IP addresses would already be very useful. Best regards, Filip

5 4

Re: Identify traffic per IP address without using pktt
by Bernardoff, Michael 18 Sep '08

18 Sep '08

Hi Smart switches can do that for you usually (if they're smart enought) so I would rather look here. Greetings _________________ Michael Bernardoff FSE@netapp +33 679 028 224 ________________________________ De : Fox, Adam À : ggwalker(a)mindspring.com ; gtchen(a)yahoo-inc.com ; filip.sneppe(a)gmail.com ; toasters(a)mathworks.com Envoyé : Thu Sep 18 02:56:41 2008 Objet : Re: Identify traffic per IP address without using pktt And there's a lun_top tool on the NOW Toolchest for SAN configs. FYI -- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard. ----- Original Message ----- From: Glenn Walker <ggwalker(a)mindspring.com> To: George T Chen <gtchen(a)yahoo-inc.com>; Filip Sneppe <filip.sneppe(a)gmail.com>; Toasters <toasters(a)mathworks.com> Sent: Wed Sep 17 21:22:38 2008 Subject: RE: Identify traffic per IP address without using pktt Similar is 'cifs top' if you have cifs.per_client_stats.enable set to 'on'. However, it gives you top talkers based on username (you'd have to use 'cifs sessions' to get the machine name\IP) and only for the last 3 second rolling average (though there are other options). Not really a way to get what you're looking for, to my knowledge... Glenn -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George T Chen Sent: Wednesday, September 17, 2008 5:49 PM To: Filip Sneppe; Toasters Subject: RE: Identify traffic per IP address without using pktt If the traffic is nfs, and you have nfs.per_client_stats.enable, then nfsstats -l gives the number of nfs requests per host. -George > -----Original Message----- > From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] > On Behalf Of Filip Sneppe > Sent: Wednesday, September 17, 2008 2:21 PM > To: Toasters > Subject: Identify traffic per IP address without using pktt > > Hi, > > When using "sysstat" from the command line, it's very easy to get an > idea of the network > throughput that is currently being handled by the filer, and with > commands like "vif stat" > it's easy to get an idea on the interfaces that are transmitting or > receiving this traffic. > > However, I am wondering if is it possible to get an idea on the client > IP addresses that > are generating most of the network traffic without having to resort to > pktt every time, > then copying over the capture file and analyzing it afterwards ? > > Are there any counters availble from a command that show how much traffic > a > particular IP address has sent/received ? I tried various commands > (eg. netstat has a > few interesting options) but couldn't find anything that solved my problem. > > At the moment, if I need to determine the hosts that are using most of the > iSCSI > or NFS bandwidth, I have to resort to pktt, and I am looking for a easier > way to > achieve what I want. Ideally, I'd like to get information on the > protocols and ports > involved too, but having IP addresses would already be very useful. > > Best regards, > Filip

2 1

Re: Identify traffic per IP address without using pktt
by Fox, Adam 18 Sep '08

18 Sep '08

And there's a lun_top tool on the NOW Toolchest for SAN configs. FYI -- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard. ----- Original Message ----- From: Glenn Walker <ggwalker(a)mindspring.com> To: George T Chen <gtchen(a)yahoo-inc.com>; Filip Sneppe <filip.sneppe(a)gmail.com>; Toasters <toasters(a)mathworks.com> Sent: Wed Sep 17 21:22:38 2008 Subject: RE: Identify traffic per IP address without using pktt Similar is 'cifs top' if you have cifs.per_client_stats.enable set to 'on'. However, it gives you top talkers based on username (you'd have to use 'cifs sessions' to get the machine name\IP) and only for the last 3 second rolling average (though there are other options). Not really a way to get what you're looking for, to my knowledge... Glenn -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George T Chen Sent: Wednesday, September 17, 2008 5:49 PM To: Filip Sneppe; Toasters Subject: RE: Identify traffic per IP address without using pktt If the traffic is nfs, and you have nfs.per_client_stats.enable, then nfsstats -l gives the number of nfs requests per host. -George > -----Original Message----- > From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] > On Behalf Of Filip Sneppe > Sent: Wednesday, September 17, 2008 2:21 PM > To: Toasters > Subject: Identify traffic per IP address without using pktt > > Hi, > > When using "sysstat" from the command line, it's very easy to get an > idea of the network > throughput that is currently being handled by the filer, and with > commands like "vif stat" > it's easy to get an idea on the interfaces that are transmitting or > receiving this traffic. > > However, I am wondering if is it possible to get an idea on the client > IP addresses that > are generating most of the network traffic without having to resort to > pktt every time, > then copying over the capture file and analyzing it afterwards ? > > Are there any counters availble from a command that show how much traffic > a > particular IP address has sent/received ? I tried various commands > (eg. netstat has a > few interesting options) but couldn't find anything that solved my problem. > > At the moment, if I need to determine the hosts that are using most of the > iSCSI > or NFS bandwidth, I have to resort to pktt, and I am looking for a easier > way to > achieve what I want. Ideally, I'd like to get information on the > protocols and ports > involved too, but having IP addresses would already be very useful. > > Best regards, > Filip

1 0

Inconsistent ndmpcopy performance on a 3020 cluster
by Nathan Patwardhan 17 Sep '08

17 Sep '08

Hello, We've got a 3020 cluster that's running OnTap 7.2.3; each node in the cluster is connected to DS14 and DS14MK2 shelves. We recently added some shelves (DS14 MK2) and as part of this maintenance we decided to migrate data off the existing traditional volumes to new flexible volumes since we're not interested in having traditional volumes anymore. For this purpose we used ndmpcopy -- to migrate data between shelves *local* to each node in the cluster, e.g.: filer> ndmpcopy -l 0 /vol/oldtradvol /vol/newflexvol Since we'd done this kind of maintenance on our other 3020s before, we'd expected throughput of ~18-20g/hr as this hardware is identical to filers we'd worked on in the past. Unfortunately results were totally inconsistent: node A performed as we'd expected and I was able to migrate 300g of data overnight. node B has consistently transferred 3-6g/hr. I'm not seeing any errors on node B and I've rechecked my cabling to make sure nothing is amiss. Why might I see such disparity in results on node A and node B? -- Nathan Patwardhan "But the album's biggest setback, other than the fact that its title sounds like a Neutrogena product, ..." -- review of Jewels' latest album

5 7

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