toasters

toasters@lists.teaparty.net

13515 discussions

small clarification on adding NTP servers to netapp 7 mode and c-mode
by Yuvaraja Shivaram 27 Sep '18

27 Sep '18

Hi all, Can we add new NTP servers to 7 mode and C-mode on Fly without disrupting any protocols... infact NTP servers are being decommissioned in future, so wanted to add the new NTP servers before decommissioned...so what is the best practise to add the same.... is there any disconnects happens to cifs protocols...? Regards Yuvaraja

2 1

Copying NTFS Data with Orphaned SIDs
by Stephen Stocke 12 Sep '18

12 Sep '18

Hi We’re migrating some data from Windows file servers to CIFS shares on a 9.1p13 cluster (NTFS security style on the vols). We’re getting errors on some files and folders using Robocopy and the common thread seems to be objects with orphaned SIDs for the owner or DACL entries. We’ve tried other tools with the same results. Robocopy to another Windows file share works fine. Has anyone else seen this behaviour? We’re assuming that the CIFS server is stopping the copy because it can’t resolve the SID. Is there any way to control that behaviour and just wrtie the DACL with the unresolved SID? Thanks Steve

3 3

CIFS Access Based Enumeration for Volume in Namespace
by Vanderyt, Jeff 10 Sep '18

10 Sep '18

Replying to an old post; I am just now hitting the same issue. Steve - did you ever find a solution to this issue? (ABE not working on junction paths). 9.1P14 here. -jeff ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Dec 2017 12:50:05 +0000 From: Stephen Stocke <scstocke(a)gmail.com> To: "<Toasters(a)teaparty.net>" <toasters(a)teaparty.net> Subject: CIFS Access Based Enumeration for Volume in Namespace Message-ID: <CAEGA2qbHgFzNEvKpLa688Syt-197quPEJNz941eYvar3PHKgZg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello I have a need to use access-based enumeration within a CIFS share that contains volumes mounted as junction paths within the share volume. ABE is working for normal files and folders but volumes mounted as junction paths are visible even if the user does not have permissions to see the folder representing the junction. Has anyone done this? Or can anyone point to any documentation on whether this is possible? ONTAP 9.1p5, ntfs security style on all volumes. Many thanks Steve

2 1

9.4 oddness
by Peter D. Gray 10 Sep '18

10 Sep '18

Hi toasters We recently upgraded all our netapps to 9.4, from 9.3 Now we see something. The volumes we previously flagged as unprotected under SVM-DR are now displaying as "protected". The only volumes which show as "unprotected" are the root volumes. In reality, the volumes we had previously flagged as "unprotected" still seem to be unprotected, that is they are not being snapmirrored to the destination SVM. This is causing a few issues with our monitoring of our protection status. Has anybody seen this or know something about it? Also, the "volume show" man page does not mention the protection flag, but does display it when asked. I do not know if the man page on 9.3 documented the flag or not. I assume it did else I would not know about it. Regards, pdg Peter Gray Ph (direct): +61 2 4221 3770 Information Management & Technology Services Ph (switch): +61 2 4221 3555 University of Wollongong Fax: +61 2 4229 1958 Wollongong NSW 2522 Email: pdg(a)uow.edu.au Australia URL: http://pdg.uow.edu.au

1 0

Ocum alerts showing as Localhost instead of Ocum Name
by Yuvaraja Shivaram 05 Sep '18

05 Sep '18

Hi All, i have configured new alert setup through OCUM 7.2p1, we are receiving alerts but it is not showing OCUM host name , instead it shows as Local host whenever we receive alerts to our email id's, is anyone aware how to resolve this issue.. here in below statement itstead of localhost , it should reflect OCUM name(oncommand unified manager) "An incident was generated by localhost that requires your attention" Regards Yuvaraj

4 4

Related to New Cmode filer Setup
by Yuvaraja Shivaram 28 Aug '18

28 Aug '18

Hi Everyone, Any one has got all the commands to setup new cluster in Dataontap C-mode environment...9.xx version... if it is in Best Standard would be fine.... Example steps: Cluster mode setup Joining cluster Creating Vlan Creating Interface Groups Creating Lifs Creating all the roles of cluster , data , node-mgmt ,intercluster cluster-mgmt Creating aggregates (both DP and Raidtec) Creating Vservers (NFS, CIFS, ISCSI) Creating failovergroups Creating volumes Creating Export-policy and rule set... Regards Yuvaraj

3 2

Be careful about snaplock
by Basil 22 Aug '18

22 Aug '18

Just going through an experience I figured I would share with the list: we ordered a small Snaplock cluster, sized so that all disks would be used for the Snaplock aggregate. Well, as it turns out, you must always size enough disk for one regular aggregate: SVM root volumes are not supported on root aggregates nor on Snaplock aggregates.

2 2

revert status
by Alexander Griesser 21 Aug '18

21 Aug '18

Hey toasters, is there any way to see the status of a node-shell revert_to command? I just had to revert one of our systems and unfortunately the SSH connection broke and I'm not seeing any progress here anymore :-/ ::> run local revert_to 9.1 You are about to revert the system to work with Data ONTAP 9.1 The system will be rebooted immediately after the conversion process completes. Make sure that you have installed Data ONTAP 9.1 onto the boot device, or you will have to run "revert_to" again. Are you sure you want to proceed? [yes/no]? yes debug.nodewatchdog.level: 2 -> 2 FlexScale PCS is not active and cannot be configured. The management gateway server restarted. Waiting to see if the connection can be reestablished I can connect to the system fine again now and I can not run the revert_to again (it says that 9.1 is not supported, only 8.3) - so I guess it's either done already or still in progress. I couldn't find any command that would show me if this task is still running - any ideas? Thanks, Alexander Griesser Head of Systems Operations ANEXIA Internetdienstleistungs GmbH E-Mail: AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://www.anexia-it.com/> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

2 3

Netapp C-Mode:- how to covert Global export policy into individual users access
by Yuvaraja Shivaram 20 Aug '18

20 Aug '18

Hi Team, Is there any way to convert global access users to convert into individual access. Say for example if any of the policy is having global access of client...like 0.0.0.0/0 and we would like to convert this into individual host access by removing this global entry "0.0.0.0\0". then how can we achieve this without disruptive activity... can we add all the individual hosts one by one which are accessing through this global access and then disable the global access parameter from export-policy rule or do we need to shutdown the application/databases and then modify the global parameter.... Please let us know if any of them worked on these kind of activity, my goal is to modify this parameter without bringing down the hosts.... Regards Yuvaraja

2 5

Re: Failed Aggregate 0
by tmac 20 Aug '18

20 Aug '18

Ok, I have seen the last ASUP via this EMAIL and the current disk layout. Here they are for everyone: Last known ASUP: Aggregate aggr0 (online, raid_dp, degraded) (block checksums) Plex /aggr0/plex0 (online, normal, active) RAID group /aggr0/plex0/rg0 (double degraded, block checksums) RAID Disk Device Model Number Serial Number VBN Start VBN End --------- ------ ------------ ------------- --------- ------- dparity 0a.44 X279_HVPBP288F15 JLVBYWVC - - parity 0a.48 X279_S15K5288F15 3LM42GHN00009839N66A - - data 0a.49 X279_S15K5288F15 3LM1TA6C000098080J6N 0 69626751 data 0a.16 X279_HVPBP288F15 JLVJV9TC 69626752 139253503 data 0a.50 X279_HVIPB288F15 J8YMUD4C 139253504 208880255 data 0a.45 X279_S15K7288F15 6SJ5HVVK0000B24505C9 208880256 278507007 data 0a.51 X279_S15K5288F15 3LM1T7DZ00009808S8XF 348133760 417760511 data 0a.18 X279_HVPBP288F15 JLVJVENC 417760512 487387263 data 0a.52 X279_HVPBP288F15 JLVHYUNC 487387264 557014015 data 0a.19 X279_HVPBP288F15 JLVJWUUC 557014016 626640767 data 0a.20 X279_HVPBP288F15 JLVJWJ3C 626640768 696267519 data 0a.22 X279_HVPBP288F15 JLVK7NJC 765894272 835521023 data 0a.23 X279_HVPBP288F15 JLVJUE9C 835521024 905147775 data 0a.25 X279_HVPBP288F15 JLVJWKRC 905147776 974774527 RAID group /aggr0/plex0/rg1 (double degraded, block checksums) RAID Disk Device Model Number Serial Number VBN Start VBN End --------- ------ ------------ ------------- --------- ------- data 0a.33 X279_HVPBP288F15 JLVJUENC 974774528 1044401279 data 0a.26 X279_HVPBP288F15 JLVKVL7C 1044401280 1114028031 data 0a.34 X279_HVPBP288F15 JLVBYUWC 1114028032 1183654783 data 0a.27 X279_HVPBP288F15 JLVBZL3C 1183654784 1253281535 data 0a.35 X279_HVPBP288F15 JLVBYVYC 1253281536 1322908287 data 0a.28 X279_HVPBP288F15 JLVJV9RC 1322908288 1392535039 data 0a.36 X279_HVPBP288F15 JLVBYSBC 1392535040 1462161791 data 0a.29 X279_HVPBP288F15 JLVJWP5C 1462161792 1531788543 data 0a.37 X279_HVPBP288F15 JLVBYS1C 1531788544 1601415295 data 0a.38 X279_HVPBP288F15 JLVBYW7C 1601415296 1671042047 data 0a.39 X279_HVPBP288F15 JLVBYWWC 1671042048 1740668799 data 0a.40 X279_HVPBP288F15 JLVBYRRC 1740668800 1810295551 data 0a.41 X279_HVPBP288F15 JLVBYPWC 1810295552 1879922303 data 0a.60 X279_HVPBP288F15 JLVJ6YZC 1879922304 1949549055 RAID group /aggr0/plex0/rg2 (normal, block checksums) RAID Disk Device Model Number Serial Number VBN Start VBN End --------- ------ ------------ ------------- --------- ------- dparity 0a.54 X279_S15K5288F15 3LM42HL100009839NXS7 - - parity 0a.55 X279_S15K5288F15 3LM45JAD00009839N5JZ - - data 0a.56 X279_S15K5288F15 3LM47SPT00009840R2EL 1949549056 2019175807 data 0a.57 X279_HVIPB288F15 J8YT82MC 2019175808 2088802559 data 0a.58 X279_HVPBP288F15 JLVGNHKC 2088802560 2158429311 data 0a.59 X279_HVPBP288F15 JLVJGJVC 2158429312 2228056063 And here is the "aggr status -r" output from MAINT mode: Aggregate aggr0 (failed, Aug 19 22:47:17 [localhost:disk.failmsg:error]: Disk 0a.21 (JLVKV9SC): non-persistent message received. 0 [NETAPP X279_HVPBP288F15 NA02] S/N [JLVKV9SC] raid_dp, partial) (block checksums) Aug 19 22:47:17 [localhost:disk.failmsg:error]: Disk 0a.32 (J8VYJBHC): non-persistent message received. 0 [NETAPP X279_HVIPB288F15 NA01] S/N [J8VYJBHC] Plex /aggr0/plex0 (offline, failed, inactive) Aug 19 22:47:17 [localhost:raid.fdr.failed.ok:info]: Disk 0a.21 Shelf 1 Bay 5 [NETAPP X279_HVPBP288F15 NA02] S/N [JLVKV9SC] successfully deleted from spare pool RAID group /aggr0/plex0/rg0 (partial, block checksums) Aug 19 22:47:17 [localhost:raid.fdr.failed.ok:info]: Disk 0a.32 Shelf 2 Bay 0 [NETAPP X279_HVIPB288F15 NA01] S/N [J8VYJBHC] successfully deleted from spare pool RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- dparity FAILED N/A 272000/ - parity 0a.48 0a 3 0 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 data 0a.49 0a 3 1 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 data 0a.16 0a 1 0 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.50 0a 3 2 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.45 0a 2 13 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 data FAILED N/A 272000/ - data 0a.51 0a 3 3 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 data 0a.18 0a 1 2 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.52 0a 3 4 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.19 0a 1 3 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.20 0a 1 4 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data FAILED N/A 272000/ - data 0a.22 0a 1 6 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.23 0a 1 7 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.25 0a 1 9 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 Raid group is missing 3 disks. RAID group /aggr0/plex0/rg1 (double degraded, block checksums) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- dparity FAILED N/A 272000/ - parity FAILED N/A 272000/ - data 0a.33 0a 2 1 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.26 0a 1 10 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.34 0a 2 2 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.27 0a 1 11 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.35 0a 2 3 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.28 0a 1 12 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.36 0a 2 4 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.29 0a 1 13 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.37 0a 2 5 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.38 0a 2 6 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.39 0a 2 7 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.40 0a 2 8 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.41 0a 2 9 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.60 0a 3 12 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 RAID group /aggr0/plex0/rg2 (degraded, block checksums) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- dparity 0a.54 0a 3 6 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 parity FAILED N/A 272000/ - data 0a.56 0a 3 8 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 data 0a.57 0a 3 9 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.58 0a 3 10 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 data 0a.59 0a 3 11 FC:A 0 FCAL 15000 272000/557056000 274845/562884296 Unassimilated aggr0 disks RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- orphaned 0a.72 0a 4 8 FC:A 0 FCAL 15000 272000/557056000 280104/573653840 What is seemingly ODD to me is the FAILED disks and they way they are displayed. See the Highlighted entries above. >From the ASUP message we know that 0a.33 and 0a.26 are dparity and parity but they are shifted and showing as data. In the last RIAD GROUP 0a.55 is failed and showing. Weird. My GUT is telling me some sort of disk enumeration bug is being encountered on this version of ONTAP. Unless someone has actually been through this before, this is going to require opening a case with NetApp in some form or fashion. There may need to be some lower level disk label corrections that need to occur but I am not 100% sure on this. Did the drives all fail at once? Was it one at a time and never replaced? just curious. You *might* be able to get a one-time support call. If you are willing to pony up the $$ to re-enable support, they might help you out now for free. OR you can purchase a one-time support. I think I have heard is like $5k-$10k or something. --tmac

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