toasters

toasters@lists.teaparty.net

1 participants
13515 discussions

Metrics!
by Ray Van Dolson 27 Aug '13

27 Aug '13

We have a growing deployment with ~25 filers and about 750TB of usable space. Most of it is VMware datastore space exposed via NFS, but some is general purpose NAS file sharing. We've been using OnCommand Core (formerly DFM) to handle reporting and such, and for the most part it's worked pretty well. I need to start pulling together some metrics for the environment as a whole, both to benefit the Storage Team who manages the devices, but also to be able to pass along to my bosses so they can get a basic grasp of how things are going. I'm curious how those of you with deployments similar to mine or larger hvae dealt with this? What sort of things are you reporting on, and how do you handle the "roll-ups" to summarize many (in our case 200+) volumes into something meaningful? Are you generating reports natively from OnCommand Core, or pulling the data out into another tool? Do you find the OnCommand DataSets feature useful? We haven't really leveraged it properly I think. My thought is to present a sort of physical view of our environment showing roll-ups of storage capacity and performance (probably CPU, IOPS and latency). How to give a snapshot overview of the whole environment is what I'm not sure on. I'm thinking using the DataSets will help me organize our various types of data and then I can report on that. I'm not sure, however, if I should spend my time trying to get the right reports out of OnCommand Core directly or if I should just start extracting the data to another tool (which?) or into a database where I can home-brew up what I'm after. Thoughts/experiences? Thanks, Ray

9 15

Mapping CIFS user to Unix user
by Iluhes 22 Aug '13

22 Aug '13

I have a very strange issue. The share are exported via CIFS and NFS. System is connect to AD domain and NIS Sometime Windows user creates a file with correct UNIX id, sometime it create a file that is owned by nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/: I see where it is coming from, first it is matched to correct Unix ID and the right away it is matched to pcuser.... On filer /etc/password pcuser::65534:65534::/: This is waht I see in the messegaes file... Thu Aug 22 13:47:11 CDT [netapp1:auth.trace.authenticateUser.loginTraceMsg:info]: AUTH: User from 1.1.1.8 authenticated by DC. Thu Aug 22 13:47:11 CDT [netapp1:auth.trace.mapNTToUnix:info]: AUTH: Mapping Windows user test_user to Unix user test_user. Thu Aug 22 13:47:11 CDT [netapp1:auth.trace.mapNTToUnix:info]: AUTH: Mapping Windows user test_user to Unix user pcuser. I dont get why it first matches it to correct it and then to pcuser

2 2

configAdvisor question for CM
by Klise, Steve 22 Aug '13

22 Aug '13

* 6250's * DOT 8.2p2 CM; 2 node <FCP> * 3 stacks Is there a way to determine the port a stack is plugged into on the IO modules on the back of the shelves? I know I can trace them, but that's not so sexy. I have the in and out on the node side, but wanted to identify the other side of the stack. This is what I tried from each node, but the output was the same. FILER001::> run -node FILER001C1 -command acpadmin list_all IP MAC Reset Last Contact Protocol Assigner Shelf Current Inband IOM Address Address Cnt (seconds ago) Version ACPA ID S/N State ID Type ---------------------------------------------------------------------------------------------------------------------- 192.168.0.27 00:a0:98:41:ec:1a 000 303 1.2.2.6 1874380650 6000626000 0x5 5b.13.A IOM6 192.168.0.63 00:50:cc:74:18:3e 000 393 1.1.1.31 1874380650 SHJ00000000A4D7 0x5 3d.35.A IOM3 192.168.0.85 00:a0:98:41:ec:54 000 448 1.2.2.6 1874380650 6000625991 0x5 5b.14.A IOM6 192.168.0.141 00:50:cc:74:30:8c 000 237 1.1.1.31 1874380650 SHJ00000000A4B0 0x5 3d.34.B IOM3 192.168.0.165 00:50:cc:74:34:a5 000 447 1.1.1.31 1874380650 SHJ00000000A518 0x5 3d.32.A IOM3 192.168.0.213 00:50:cc:74:34:d5 000 369 1.1.1.31 1874380650 SHJ00000000A518 0x5 3d.32.B IOM3 192.168.1.25 00:50:cc:74:35:18 000 446 1.1.1.31 1874380650 SHJ00000000A514 0x5 3d.30.A IOM3 192.168.1.29 00:50:cc:74:31:1c 000 432 1.1.1.31 1874380650 SHJ00000000A4D7 0x5 3d.35.B IOM3 192.168.1.30 00:50:cc:74:35:1d 000 450 1.1.1.31 1874380650 SHJ00000000A514 0x5 3d.30.B IOM3 192.168.1.41 00:50:cc:74:35:28 000 410 1.1.1.31 1874380650 SHJ00000000A510 0x5 3d.31.B IOM3 192.168.1.69 00:a0:98:41:69:44 000 545 1.2.2.6 1874380650 6000587242 0x5 5b.10.B IOM6 192.168.1.109 00:50:cc:74:35:6d 000 357 1.1.1.31 1874380650 SHJ00000000A4FA 0x5 3d.33.B IOM3 192.168.1.141 00:a0:98:41:dd:8c 000 469 1.2.2.6 1874380650 SHJ000000017644 0x5 5a.20.B IOM6 192.168.1.157 00:a0:98:41:4d:9c 000 320 1.2.2.6 1874380650 6000584783 0x5 5b.12.B IOM6 192.168.1.179 00:a0:98:41:35:b2 000 498 1.2.2.6 1874380650 6000584783 0x5 5b.12.A IOM6 192.168.1.197 00:a0:98:41:dd:c4 000 370 1.2.2.6 1874380650 SHJ000000017644 0x5 5a.20.A IOM6 192.168.2.103 00:50:cc:74:2a:67 000 386 1.1.1.31 1874380650 SHJ00000000A510 0x5 3d.31.A IOM3 192.168.3.67 00:a0:98:42:17:42 000 350 1.2.2.6 1874380650 6000625991 0x5 5b.14.B IOM6 192.168.3.113 00:50:cc:74:33:70 000 440 1.1.1.31 1874380650 SHJ00000000A4FA 0x5 3d.33.A IOM3 192.168.3.175 00:50:cc:74:2f:af 000 406 1.1.1.31 1874380650 SHJ00000000A4B0 0x5 3d.34.A IOM3 192.168.3.197 00:a0:98:41:6b:c4 000 294 1.2.2.6 1874380650 6000587357 0x5 5b.11.A IOM6 192.168.3.223 00:a0:98:41:6b:de 000 147 1.2.2.6 1874380650 6000587357 0x5 5b.11.B IOM6 192.168.3.227 00:a0:98:41:6b:e2 000 319 1.2.2.6 1874380650 6000587242 0x5 5b.10.A IOM6 192.168.3.237 00:a0:98:42:17:ec 000 194 1.2.2.6 1874380650 6000626000 0x5 5b.13.B IOM6 FILER001::> run -node FILER001C2 -command acpadmin list_all IP MAC Reset Last Contact Protocol Assigner Shelf Current Inband IOM Address Address Cnt (seconds ago) Version ACPA ID S/N State ID Type ---------------------------------------------------------------------------------------------------------------------- 192.168.0.27 00:a0:98:41:ec:1a 000 370 1.2.2.6 1874380650 6000626000 0x5 5b.13.A IOM6 192.168.0.63 00:50:cc:74:18:3e 000 417 1.1.1.31 1874380650 SHJ00000000A4D7 0x5 3d.35.A IOM3 192.168.0.85 00:a0:98:41:ec:54 000 511 1.2.2.6 1874380650 6000625991 0x5 5b.14.A IOM6 192.168.0.141 00:50:cc:74:30:8c 000 327 1.1.1.31 1874380650 SHJ00000000A4B0 0x5 3d.34.B IOM3 192.168.0.165 00:50:cc:74:34:a5 000 523 1.1.1.31 1874380650 SHJ00000000A518 0x5 3d.32.A IOM3 192.168.0.213 00:50:cc:74:34:d5 000 453 1.1.1.31 1874380650 SHJ00000000A518 0x5 3d.32.B IOM3 192.168.1.25 00:50:cc:74:35:18 000 515 1.1.1.31 1874380650 SHJ00000000A514 0x5 3d.30.A IOM3 192.168.1.29 00:50:cc:74:31:1c 000 511 1.1.1.31 1874380650 SHJ00000000A4D7 0x5 3d.35.B IOM3 192.168.1.30 00:50:cc:74:35:1d 000 509 1.1.1.31 1874380650 SHJ00000000A514 0x5 3d.30.B IOM3 192.168.1.41 00:50:cc:74:35:28 000 432 1.1.1.31 1874380650 SHJ00000000A510 0x5 3d.31.B IOM3 192.168.1.69 00:a0:98:41:69:44 000 9 1.2.2.6 1874380650 6000587242 0x5 5b.10.B IOM6 192.168.1.109 00:50:cc:74:35:6d 000 423 1.1.1.31 1874380650 SHJ00000000A4FA 0x5 3d.33.B IOM3 192.168.1.141 00:a0:98:41:dd:8c 000 492 1.2.2.6 1874380650 SHJ000000017644 0x5 5a.20.B IOM6 192.168.1.157 00:a0:98:41:4d:9c 000 379 1.2.2.6 1874380650 6000584783 0x5 5b.12.B IOM6 192.168.1.179 00:a0:98:41:35:b2 000 599 1.2.2.6 1874380650 6000584783 0x5 5b.12.A IOM6 192.168.1.197 00:a0:98:41:dd:c4 000 471 1.2.2.6 1874380650 SHJ000000017644 0x5 5a.20.A IOM6 192.168.2.103 00:50:cc:74:2a:67 000 421 1.1.1.31 1874380650 SHJ00000000A510 0x5 3d.31.A IOM3 192.168.3.67 00:a0:98:42:17:42 000 432 1.2.2.6 1874380650 6000625991 0x5 5b.14.B IOM6 192.168.3.113 00:50:cc:74:33:70 000 512 1.1.1.31 1874380650 SHJ00000000A4FA 0x5 3d.33.A IOM3 192.168.3.175 00:50:cc:74:2f:af 000 476 1.1.1.31 1874380650 SHJ00000000A4B0 0x5 3d.34.A IOM3 192.168.3.197 00:a0:98:41:6b:c4 000 395 1.2.2.6 1874380650 6000587357 0x5 5b.11.A IOM6 192.168.3.223 00:a0:98:41:6b:de 000 200 1.2.2.6 1874380650 6000587357 0x5 5b.11.B IOM6 192.168.3.227 00:a0:98:41:6b:e2 000 408 1.2.2.6 1874380650 6000587242 0x5 5b.10.A IOM6 192.168.3.237 00:a0:98:42:17:ec 000 241 1.2.2.6 1874380650 6000626000 0x5 5b.13.B IOM6 Any help is appreciated..

3 7

sis start -s causing system slowdown
by Chris Picton 21 Aug '13

21 Aug '13

Hi all One of the volumes exported via NFS from my fas3210 didn't have dedup enabled when comissioned. It is 250GB, and hosts ploop backed openvz vms. It is currently using about 210GB, and hourly snapshot size is about 6GB. When I run sis start -s on this volume, the entire system slows down to a crawl. My snmp monitoring start timing out, ssh access to the system is hit and miss, taking over a minute to log in, and when logged on, command response is sluggish. I also get the following error in the logs for all snapmirror pairs SnapMirror: source transfer from TEST_TESTVOL to xx.yy.zz:TEST_TESTVOL : request denied, previous request still processing. Fortunately, disk access from clients on this and other volumes are not detrimentally affected, but IO response times do go up by about 100ms. After running overnight for 11 hours, sis status reports Progress: 19333120 KB Scanned Change Log Usage: 88% Logical Data: 151 GB/49 TB (0%) At this rate, it will take about 5 days to finish scanning, leaving me barely able to manage the system effectively while this is happening. Is this normal behaviour - do I just have to wait through it, or can I stop it and correct something before trying again. Also, is the change log filling up towards 100% something to worry about? Regards Chris

9 16

need advice on using old FAS3140 for snapvault
by Scott Classen 21 Aug '13

21 Aug '13

Hello fellow toaster, We are contemplating an upgrade from our existing FAS3140 to a new FAS3220. The 3140 has served us very well and been unbelievably reliable, but is now 5 years old. We would like to move to a newer filer and more storage. What do to with the old filer and it's three associated shelves (DS14Mk4)? Could it be used as some sort of snapvault device? Currently we back up to LTO-4 tapes via NDMP, which is a bit painful, but we deal with it. I like the idea of having a set of backups on disk, ready to go, and easily accessible. We only use NFS and iSCSI functionality of the filer and have no extra licenses so I'm not very familiar with the day-to-day use of snapvault. Is it feasible to use the retired FAS3140 as a snapvault "container" without having it under an annual service contract? If we pay for a snapvault license on our new FAS3220 does that allow us to use an older filer as the actual storage space? I guess the other option is to mothball the FAS3140, but I hate to put down a good piece of equipment. Any thoughts or advice would be greatly appreciated. Thanks, Scott

3 3

SQL Server - NFS or CIFS which is better
by Joseph Bishop 21 Aug '13

21 Aug '13

Hello Toasters, We have a new NetApp and are going to migrate our SQL Servers onto it. For many reasons, I would like to avoid LUN provisioning and would prefer NFS or CIFS. Can I get feedback on which works better in practice? Best Regards, Joe

3 2

Filer joining samba4 domain ?
by Frank Bonnet 20 Aug '13

20 Aug '13

Hello Does anyone succeeded in joining a samba 4 domain with a filer ? thank you

1 0

System status degraded after hot adding 2 DS4243 shelves
by Alexander Griesser 19 Aug '13

19 Aug '13

Hey there, the second question today, sorry for that :) I did attach two DS4243 shelves to a FAS3240HA system today and followed all the instructions, the shelf firmware has been updated in this process and everything looks good as far as I can tell, I can see the 6 shelves now on both controllers, all shelves are multi path ready, disks are visible, etc. One controller shows its health status as OK but the other one shows degraded: robin> system health status show Status --------------- Degraded The reason for that seems to be: Node: robin Resource: Disk 0a.06.10 Severity: Major Probable Cause: Disk 0a.06.10 does not have two paths to controller robin but the containing disk shelf 6 does have two paths. Disk 0a.06.10 may be faulty. Possible Effect: Access to disk 0a.06.10 via controller robin will be lost with a single hardware component failure (e.g. cable, HBA, or IOM failure). Corrective Actions: 1. Reseat disk 0a.06.10 following the rules in the Installation and Service Guide. 2. Wait six minutes for the alert condition to clear. 3. If reseating disk 0a.06.10 fails to clear the alert condition, replace disk 0a.06.10. 4. Wait six minutes for the alert condition to clear. 5. Contact support personnel if the alert persists. 48 entries were displayed. There are exactly 48 entries in the log for all the new 48 disks I added to the systems. If it would really be a disk or shelf fault, I guess I should see these errors on the second controller too, but I cannot see them there. Any ideas what I could to now to diagnose this issue further? I think the usual problems like broken cables, etc. can be ruled out since the second controller is not showing these issues, right? Thanks in advance, bye, Alexander Griesser System-Administrator ANEXIA Internetdienstleistungs GmbH Telefon: +43-463-208501-320 Telefax: +43-463-208501-500 E-Mail: ag(a)anexia.at<mailto:ag@anexia.at> Web: http://www.anexia.at Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

4 19

Identifying Heavily Accessed Files / Clients
by Ray Van Dolson 13 Aug '13

13 Aug '13

Dear Lazyweb; Wondering if there's a sysstat/nfsstat type command that will show me which "files" (or which initiating NFS clients) are absorbing or generating the most traffic? Trying to figure out which VMDK files or ESX clients are to blame for a recent spike in activity. Ray

4 3

options weirdness
by Peter D. Gray 13 Aug '13

13 Aug '13

Can someone who knows tell me whats going on here? We recently discovered a security issue with our netapp filers when using NFS. The netapps where allowing NFS mounts and operations from non-privilaged client ports. Investigation found the options nfs.nfs_rootonly and nfs.mount_rootonly options. nfs.mount_rootonly was true, but nfs.nfs_rootonly was false. I was kind of surprized by this, since I had no recollection of ever altering either of these options yet the settings were identical across all our filers. The environment is: 3170A running 8.2 3240 running 8.2 3240 running 8.1 (reverted from 8.2) Ok, so I asked another nearby site to check there filers for me and they tell me their filers have no such setting, all on 8.1 So, I guess my questions are: 1) has ONTAP always allowed NFS from non-privilaged ports? 2) was nfs.nfs_rootonly introduced in 8.2 and why is the default off? 3) why does this setting stay around after revert to 8.1? It would seem to me that allowing NFS from non-privilages ports is kind of bad. Any help appreciated. Regards, pdg

4 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