toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

issues with 10G Ethernet.
by James Beal 29 Sep '08

29 Sep '08

I have a call open with netapp about this however I thought I would ask the list if anyone else has had similar issues. We have a cluster which is connected to our core via TOE-10G Ethernet (T320E-XFP). The problem we see is that the sometimes the netapp appears stop receiving any packets. I haven't done a packet trace while the problem is in effect as I have been a bit of a Muppet when I have noticed the problem as I had forgotten the rlm user name but I have made notes so next time it happens I will do a trace.. This has happened on both units in our cluster. We have replaced one of the 10gig cards and that has made no difference. Our networking people show no errors on the line cards. Power cycling the units brings the network card back. We have turned toe off on the cards and that appears not to make any difference to the reliability of the system. This has so far occurred 3 times which is really very poor. sysconfig -v 4 slot 4: Dual TOE-10G Ethernet Controller (T320E-XFP) Device Type: CT-31-1 Version Number: T3-SRAM1.1.0-BR1040-20-C0-FW4.6.0-DR03 Serial Number: PT3807035 e4a MAC Address: 00:07:43:05:13:ac (auto-10g_sr-fd-up) e4b MAC Address: 00:07:43:05:13:ad (auto-10g_sr-fd-cfg_down) ifconfig e4a e4a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 172.17.66.26 netmask 0xffffff00 broadcast 172.17.66.255 partner inet 172.17.66.27 (not in use) ether 00:07:43:05:13:ac (auto-10g_sr-fd-up) flowcontrol full

4 7

network is slooooow on new 2020 model (ceiving an excessive number of packets receiving an excessive number of packets or protocols not supported this system
by Linux Admin 26 Sep '08

26 Sep '08

Just unwrapped it and connected it 2020 to switch: telnet and http is very very slow following message from netdiag l2s-na01> netdiag Performing physical layer diagnostics..... The interface e0a seems to be receiving an excessive number of packets for protocols not supported this system. If this problem persists, please contact your network administrator. Press enter to continue The interface e0b seems to be receiving an excessive number of packets for protocols not supported this system. If this problem persists, please contact your network administrator. Press enter to continue Performing network layer diagnostics.....OK Performing transport layer diagnostics.....OK l2s-na01> netdiag

3 2

AIX Power/VIOS Flex clones
by Ken Williams 25 Sep '08

25 Sep '08

Anyone doing flex clones on IBM power5/6 PowerVM platform? I've created a clone of a LUN and presented it to the VIOS servers. The system doesn't see the new device. From my understanding its because they share the same PVID. My question is how can I use flexclone technology without taking down the LPAR to make a clone. __________________________________________________________ Ken Williams Storage Administrator, Business Technology Operations Sacramento Municipal Utility District E-Mail: kwillia(a)smud.org Phone: (916) 732-6744 Cell: (916) 240-4213

1 0

Monitor volume space via Nagios?
by Page, Jeremy 25 Sep '08

25 Sep '08

Is anyone doing this? I'm trying to figure out how to get notified if one of my volumes gets below a certain % of free space. This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

9 9

bad raid label version
by Christian Mikovits 25 Sep '08

25 Sep '08

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

4 5

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

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