toasters

toasters@lists.teaparty.net

13520 discussions

Exports file
by Conner, Neil 08 May '08

08 May '08

I want configure an exports file to grant a client ro access when I¹ve excluded the subnet the client belongs to from rw access. The man page reads: ³You cannot exclude an NFS client identifier from the ro= or rw= option and include the same NFS client identifier in the other option², but I¹m wondering if that restriction applies to subnets. This is what I have now: /vol/vol0/dir1 -sec=sys,rw=-123.123.4.0/24:123.123.0.0/16,root=adminhost And I want something like this: /vol/vol0/dir1 -sec=sys,ro=123.123.4.4,rw=-123.123.4.0/24:123.123.0.0/16,root=adminhost Is this possible?

1 0

can not create incemental snapshot
by Chaim Rieger 08 May '08

08 May '08

trying to snapmirror /qryndbcore/ from irnetapp1 to irfl1 here are the space stats of the volume and general filer IRNetApp1> df -h qryndbcore Filesystem total used avail capacity Mounted on /vol/qryndbcore/ 1500GB 1361GB 138GB 91% /vol/qryndbcore/.snapshot 0TB 0TB 0TB ---% IRNetApp1> df -Ah Aggregate total used avail capacity aggr 3537GB 2461GB 1075GB 70% aggr/.snapshot 884GB 146GB 737GB 17% IRNetApp1> Thu May 8 09:44:25 PDT [IRNetApp1: snapmirror.src.err:error]: SnapMirror source transfer from qryndbcore to irfl2:qryndbcore : cannot create incremental snapshot. snap reserve is set to 0, however i think that 700gb (on the volume level) should be enough to create a snapshot.

2 1

cannot create incremental snapshot
by Chaim Rieger 08 May '08

08 May '08

2 2

Re: SnapDrive for Windows & CIFS
by Nils Vogels 08 May '08

08 May '08

On Thu, May 8, 2008 at 10:24 AM, De Wit Tom (Consultant) < tom.de.wit(a)volvo.com> wrote: > >Use the 'software install' or 'software upgrade' command to upgrade in > this way, that way you won't get any errors about CIFS being limited, and > the 'software upgrade' command adds in a package verification so that you > know everything actually downloaded correctly before beginning the actual > upgrade. > > I completely agree ! > As an added plus, it also eliminates pesky permissions problems that could result in weird errors *after* upgrading, when you unpack the exe as a user that doesn't have quite the right permissions in the ETC$ share. I've seen for instance java going horribly wrong in that way. This is because when running the 'software install' / 'software upgrade' commands, you are sure the commands are run as the local admin on the filer (=root). When using CIFS to place/unpack the files, you usually are performing that action with the permissions of "whoever is currently running explorer.exe", which might be the cause of spending some extra after-office hours, and (most importantly) might cause you to miss dinner @ home. Actually, I don't quite understand why NetApp still uses this method in their upgrade advisors, IMHO, they have developed far better alternatives by now by way of the 'software *' commands. Gr, Nils -- Simple guidelines to happiness: Work like you don't need the money, Love like your heart has never been broken and Dance like no one can see you.

1 0

SnapDrive for Windows & CIFS
by Milazzo Giacomo 08 May '08

08 May '08

Hi, this is a good question: must CIFS be licensed to use SnapDrive for Windows? I've never had the chance to perform some test but I think that the answer is "yes". And you know why: because SnapDrive for Windows needs to 'see' and 'reach' the volume where you create the LUN(s) by CIFS using a UNC path. It's also true that there a limited CIFS that permit to access to the administrative share C$ but, as example, when I've tried to upgrade a DataOntap using the windows package, without a full CIFS license, the unzip of data failed! So. Why customer ha sto spend money for an unused license if he needs only SAN functions. Regards

3 2

filer fail over times
by Page, Jeremy 06 May '08

06 May '08

How long should it take a filer to fail over from one head to another? When I force a failover (cf forcetakeover) from one head the other goes down for minutes. Here's what I see on the console. This is a new filer with very little traffic going to it and FC is not even set up yet, all NFS/CIFS. array01> cf forcetakeover cf forcetakeover may lead to data corruption; really force a takeover? yes cf: forcetakeover initiated by operator array01> Mon May 5 12:27:48 EST [array01: cf.misc.operatorForcedTakeover:warning]: Cluster monitor: forced takeover initiated by operator Mon May 5 12:27:48 EST [array01: cf.fsm.takeover.forced:info]: Cluster monitor: takeover attempted after cf forcetakeover command Mon May 5 12:27:48 EST [array01: cf.fsm.stateTransit:warning]: Cluster monitor: UP --> TAKEOVER Mon May 5 12:27:48 EST [array01: cf.fm.takeoverStarted:warning]: Cluster monitor: takeover started Mon May 5 12:27:48 EST [array02/array01: coredump.spare.none:info]: No sparecore disk was found. Mon May 5 12:27:51 EST [array01: raid.vol.replay.nvram:info]: Performing raid replay on volume(s) Mon May 5 12:27:51 EST [array01: raid.cksum.replay.summary:info]: Replayed 0 checksum blocks. Mon May 5 12:27:51 EST [array01: raid.stripe.replay.summary:info]: Replayed 0 stripes. Mon May 5 12:27:54 EST [array02/array01: wafl.replay.done:info]: WAFL log replay completed, 2 seconds ifconfig: no such media type <xxx> media type options are: <tp> <tp-fd> <100tx> <100tx-fd> <1000fx> <auto> <10g-sr> ifconfig: Unable to determine primary for interface e0a. ifconfig: e0a: no such interface ifconfig: Unable to determine primary for interface e0b. ifconfig: e0b: no such interface ifconfig: Unable to determine primary for interface e0c. ifconfig: e0c: no such interface ifconfig: Unable to determine primary for interface e0d. ifconfig: e0d: no such interface ifconfig: Unable to determine primary for interface e2a. ifconfig: e2a: no such interface ifconfig: Unable to determine primary for interface e2b. ifconfig: e2b: no such interface add net default: gateway 10.28.17.1: network unreachable Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e0a. Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e0b. Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e0c. Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e0d. Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e2a. Mon May 5 12:27:55 EST [array02/array01: net.ifconfig.noLocal:error]: ifconfig: Unable to determine primary for interface e2b. Mon May 5 12:27:55 EST [array02/array01: nis.servers.not.available:error]: NIS server(s) not available. Mon May 5 12:27:55 EST [array02/array01: cf_takeover:info]: relog syslog Mon May 5 12:26:00 EST [array02: monitor.globalStatus.ok:info]: The system's global status is normal. Mon May 5 12:27:55 EST [array02/array01: cf_takeover:info]: relog syslog Mon May 5 12:27:47 EST [array02: cf.fsm.takeoverOfPartnerDisabled:notice]: Cluster monitor: takeover of array There are 68 spare disks; you may want to use the vol or aggr command to create new volumes or aggregates or add disks to the existing aggregate. FCP service stopped. Mon May 5 12:27:55 EST [array01: net.ifconfig.takeoverError:warning]: WARNING: 6 errors detected during network takeover processing WARNING: Some network clients may not be able to access the cluster during takeover Mon May 5 12:27:55 EST [array01: cf.rsrc.takeoverOpFail:error]: Cluster monitor: takeover during ifconfig_2 failed; takeover continuing... CIFS partner server is running. Mon May 5 12:27:55 EST [array01 (takeover): cf.rsrc.transitTime:notice]: Top Takeover transit times wafl_replay=2383 {replay_log=2353, mark_replaying=29}, raid=832, rc=410 {hostname=51, ifconfig=46, options=23, options=14, options=10, options=9, ifconfig=1, ifconfig=1, ifconfig=1, route=1}, wafl=405, registry_postrc_phase1=227, raid_replay=179, registry_prerc=115, wafl_sync=74, fmdisk_reserve=70, cifs=70 Mon May 5 12:27:55 EST [array01 (takeover): cf.fm.takeoverComplete:warning]: Cluster monitor: takeover completed Mon May 5 12:27:55 EST [array01 (takeover): cf.fm.takeoverDuration:warning]: Cluster monitor: takeover duration time is 7 seconds Mon May 5 12:27:58 EST [array02/array01: asup.smtp.host:info]: Autosupport cannot connect to host smtp.danahermail.com (Network comm problem) for message: REBOOT (CLUSTER TAKEOVER) Mon May 5 12:27:58 EST [array02/array01: asup.smtp.unreach:error]: Autosupport mail was not sent because the system cannot reach any of the mail hosts from the autosupport.mailhost option. (REBOOT (CLUSTER TAKEOVER)) Mon May 5 12:28:00 EST [array01 (takeover): monitor.globalStatus.critical:CRITICAL]: This node has taken over array02. Mon May 5 12:28:00 EST [array02/array01: monitor.globalStatus.critical:CRITICAL]: array01 has taken over this node. Mon May 5 12:28:05 EST [array02/array01: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the partner server. Mon May 5 12:28:07 EST [array01 (takeover): asup.post.sent:notice]: Cluster Notification message posted to IBM: Cluster Notification from array01 (CLUSTER TAKEOVER COMPLETE MANUAL) INFO Mon May 5 12:32:07 EST [array02/array01: asup.smtp.host:info]: Autosupport cannot connect to host smtp.danahermail.com (Network comm problem) for message: REBOOT (CLUSTER TAKEOVER) Mon May 5 12:32:07 EST [array02/array01: asup.smtp.unreach:error]: Autosupport mail was not sent because the system cannot reach any of the mail hosts from the autosupport.mailhost option. (REBOOT (CLUSTER TAKEOVER)) Here is the ifconfig -a from the node that stayed up: array01(takeover)> ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b6 (auto-unknown-cfg_down) flowcontrol full e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b4 (auto-unknown-cfg_down) flowcontrol full e2a: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:07:43:05:16:98 (auto-10g_sr-fd-cfg_down) flowcontrol full e2b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:07:43:05:16:99 (auto-10g_sr-fd-cfg_down) flowcontrol full lo: flags=19e8049<UP,LOOPBACK,RUNNING,MULTICAST,MULTIHOST,PARTNER_UP,TCPCKSU M> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) lan0: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.28.17.213 netmask 0xffffff00 broadcast 10.28.17.255 partner lan0 (not in use) ether 02:a0:98:08:22:b7 (Enabled virtual interface) 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.

5 4

toasterview_rrd -create fails - duplicate DS name error.
by chrisb1961＠comcast.net 05 May '08

05 May '08

Using RHEL Server 5.1 with: net-snmp-5.3.1-19.el5_1.4 Perl v5.8.8 built for i386-linux-thread-multi Connecting to a Netapp FAS3050 running 7.2.1 which is part of a cluster. ./toasterview_rrd -create fails with a duplicate DS name error. The output from the command shows a duplicate DS name for every one of our volumes. The command fails on vol0 because it is the first volume processed (I think that's why). See sample output below. Does anybody know why this is happening or more importantly what needs to be done to correct this error? Also, #./toasterview_rrd.pl -create myfiler2 -p /var/rrds fails exactly the same way using the other Filer head in the cluster. Interstingly, it doesn't report duplicate aggregate names, only volume names. And no.... there aren't duplicate volume names for every volume we have. Just thought I would head that question off now :-) --Thanks, Chris #./toasterview_rrd.pl -create myfiler1 -p /var/rrds *** ToasterView RRD Creation Selected *** Looking for NetApp Volumes on myfiler1 Found volume named: vol0 Found volume named: vol0 Found volume named: sql2 Found volume named: sql2 Found volume named: rtb Found volume named: rtb <snip> Creating Tosterview RRD Going to use command: /usr/local/bin/rrdtool create /var/rrds/myfiler1.rrd --start N --step 1200 DS:vol0:GAUGE:2400:U:U DS:vol0:GAUGE:2400:U:U DS:sql2:GAUGE:2400:U:U DS:sql2:GAUGE:2400:U:U DS:rtb:GAUGE:2400:U:U DS:rtb:GAUGE:2400:U:U <snip> ERROR: Duplicate DS name: vol0 An error has occured: Return Value 256

1 0

Re: ONTAP as nfs client
by Mike Eisler 05 May '08

05 May '08

> Any ideas...??? Very few, since I still don't understand your problem. My literal interpretation is that you want to use Data ONTAP to manage your hsv200. I don't see how, if NetApp added an NFS client this would allow you to manage the hsv200. --- Xishan <xischaune(a)yahoo.com> wrote: > ok > the actual problem is that i have an HP SAN (hsv200) running > comandview EVA software on HP DL380 Storage server. The operating sys > on storage server is Win2003 server r2. > I am trying to integrate the HP SAN with ONTAP. i want to maintain > ONTAP as a single admin point and not talk to HP SAN through > commandview EVA. > So one of the solutions that came to my mind was to make a qtree in > ONTAP and mount it through NFS onto the HP SAN. So it will be a NFS > Client (ONTAP) - NFS Server (commandview EVA) environment. > > Any ideas...??? > Thanx in advance > > Mike Eisler <email2mre-toasters(a)yahoo.com> wrote: > --- Xishan wrote: > > > Hello... > > Is there any way to configure ONTAP as an NFS client...through web > > interface or command line...??? > > No. > > > > > i want to mount a SUN SOLARIS system (as NFS client) on ONTAP ABC > > qtree (using the mount command on SUN SOLARIS)...and then further > > mount the ABC volume/qtree of the filer (as NFS client) onto a > UNIX > > system...any ideas or suggestions... > > I'm intrigued. What problem are you trying to solve? > > > Thanx > > > > > > > > --------------------------------- > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. > > Try it now. > > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. > Try it now.

6 6

RE: [BULK] Re: Autosupport messages triggered by UPS SNMP trap
by Christopher Mende 02 May '08

02 May '08

Probably any head ... Those features are there, just undocumented and very likely unsupported. My info is probably a year or two out of date. Christopher Mende Sr Solutions Architect Peak UpTime +1 913 523 4263 -----Original Message----- From: Mike <ginguy_2000(a)yahoo.com> Sent: Friday, May 02, 2008 12:34 To: joelk(a)encs.concordia.ca <joelk(a)encs.concordia.ca> Cc: toasters(a)mathworks.com <toasters(a)mathworks.com> Subject: [BULK] Re: Autosupport messages triggered by UPS SNMP trap Har! I lol'd. What kind of head, haven't seen that before..... Still sounds like it's related (architecturally, at least) to the code that says "lose 1 PS for 2 mins = shutdown". Behavior sounds similar. --- Joel Krajden <joelk(a)encs.concordia.ca> wrote: > Good to know there are doubters out there. > > >> Our filers monitor their UPSs. > > > > This seems unlikely ;) > > ups status > ups: global status is Enabled. > ups: status for 192.168.6.15 UPS/SNMP is Enabled. > ups: status for 192.168.6.16 UPS/SNMP is Enabled. > > ;) > > > ... sample message... opening a case ... > This AutoSupport email indicates that the line power to your UPS has > failed. Your Network Appliance system is currently serving data but > will eventually shut down if the UPS continues to run without line > power. Please check your environment and restore the line power to > your UPS as soon as possible. > > > > Joel > > > Mike wrote: > > --- Joel Krajden <joelk(a)encs.concordia.ca> wrote: > > > >> Our filers monitor their UPSs. > > > > This seems unlikely ;) > > > > > > > > > >> Anyone know of a way to stop autosupport from sending the > tarballs > >> every time our ups experiences a flicker or does a self-test. > > > > Sounds like an autosupport is being triggered with a Power Fault / > > Shelf Fault type of error? > > > > > > > >> Anyone else that would like the filers to be smarter when > monitoring > >> two > >> or more UPS so that if one UPS fails but the other still is > >> providing > >> juice not to perform a halt. > >> > > > > If I understand this correctly, you're losing power to one power > > supply, and the system is halting? Is this correct? > > > > If so, this might explain the reasons: > > > > https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb7734 > > > > > > > ____________________________________________________________________________________ > > Be a better friend, newshound, and > > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > -- > | Joel Krajden | Rm: EV-7105, Tel: 514 848-2424 3052 | > | Core Technologies Mgr | | > | Engineering & | Email: joelk(a)encs.concordia.ca | > | Computer Science | | > | Concordia University | In a circus, the clowns are supposed | > | Montreal, Canada | to make you laugh, not cry. | > "It's like Azathoth designed a role-playing game." - Darren MacLennan, World of Synnibarr Review: http://www.rpg.net/news+reviews/reviews/rev_4762.html "But the situation of the Oompa-Loompas is real; it could not be more so, and it is anything but funny." - Eleanor Cameron, A Reply to Roald Dahl. Horn Book Magazine, April 1973: http://www.hbook.com/exhibit/dahlresponse_2.html ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Autosupport messages triggered by UPS SNMP trap
by Joel Krajden 02 May '08

02 May '08

Our filers monitor their UPSs. Anyone know of a way to stop autosupport from sending the tarballs every time our ups experiences a flicker or does a self-test. Anyone else that would like the filers to be smarter when monitoring two or more UPS so that if one UPS fails but the other still is providing juice not to perform a halt. -- | Joel Krajden | Rm: EV-7105, Tel: 514 848-2424 3052 | | Core Technologies Mgr | | | Engineering & | Email: joelk(a)encs.concordia.ca | | Computer Science | | | Concordia University | In a circus, the clowns are supposed | | Montreal, Canada | to make you laugh, not cry. |

2 3

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