toasters April 2019

toasters@lists.teaparty.net

15 participants
9 discussions

DNS woes
by Scott Classen 25 Apr '19

25 Apr '19

Hello, Can anyone help me with this before I open a case with NetApp? dns check on one of my sververs fails (see below where I get an “Operation timed out” error), but I can ping and traceroute from the vserver to the gateway and the DNS servers. sibyls2::*> dns show -vserver als-enable-ds1 Vserver: als-enable-ds1 Domains: als.lbl.gov, lbl.gov Name Servers: 131.243.5.1, 131.243.5.2 Timeout (secs): 2 Maximum Attempts: 1 Is TLD Query Enabled?: true Require Source and Reply IPs to Match: true Require Packet Queries to Match: true sibyls2::*> dns check -vserver als-enable-ds1 Name Server Vserver Name Server Status Status Details ------------- --------------- ------------ -------------------------- als-enable-ds1 down Operation timed out. 131.243.5.1 als-enable-ds1 down Operation timed out. 131.243.5.2 2 entries were displayed. sibyls2::*> ping -node sibyls2-03 -destination 131.243.78.1 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.78.1 is alive sibyls2::*> ping -node sibyls2-03 -destination 131.243.5.1 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.5.1 is alive sibyls2::*> ping -node sibyls2-03 -destination 131.243.5.2 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.5.2 is alive sibyls2::*> ping -node sibyls2-04 -destination 131.243.78.1 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.78.1 is alive sibyls2::*> ping -node sibyls2-04 -destination 131.243.5.1 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.5.1 is alive sibyls2::*> ping -node sibyls2-04 -destination 131.243.5.2 -vserver als-enable-ds1 -wait-response 2000 -count 3 131.243.5.2 is alive sibyls2::*> traceroute -node sibyls2-03 -vserver als-enable-ds1 -destination 131.243.78.1 traceroute to 131.243.78.1 (131.243.78.1), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 0.521 ms * 0.484 ms sibyls2::*> traceroute -node sibyls2-03 -vserver als-enable-ds1 -destination 131.243.5.1 traceroute to 131.243.5.1 (131.243.5.1), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 0.478 ms 0.369 ms 0.376 ms 2 xe-2-2-1.er1-n1.lbl.gov (131.243.244.140) 0.411 ms 0.391 ms 0.330 ms 3 t5-4.ir1-n1.lbl.gov (131.243.244.131) 0.796 ms 1.365 ms 0.524 ms 4 ns.lbl.gov (131.243.5.1) 0.402 ms 0.765 ms 0.936 ms sibyls2::*> traceroute -node sibyls2-03 -vserver als-enable-ds1 -destination 131.243.5.2 traceroute to 131.243.5.2 (131.243.5.2), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 0.446 ms 0.409 ms 0.375 ms 2 nsals.lbl.gov (131.243.5.2) 0.649 ms 1.047 ms 1.080 ms sibyls2::*> traceroute -node sibyls2-04 -vserver als-enable-ds1 -destination 131.243.78.1 traceroute to 131.243.78.1 (131.243.78.1), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 0.443 ms * 0.502 ms sibyls2::*> traceroute -node sibyls2-04 -vserver als-enable-ds1 -destination 131.243.5.1 traceroute to 131.243.5.1 (131.243.5.1), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 0.515 ms 0.402 ms 0.388 ms 2 xe-2-2-1.er1-n1.lbl.gov (131.243.244.140) 0.513 ms 0.344 ms 0.326 ms 3 t5-4.ir3-n2.lbl.gov (131.243.244.129) 1.737 ms 1.618 ms t5-4.ir4-n3.lbl.gov (131.243.244.133) 0.582 ms 4 ns.lbl.gov (131.243.5.1) 0.898 ms 1.213 ms 0.517 ms sibyls2::*> traceroute -node sibyls2-04 -vserver als-enable-ds1 -destination 131.243.5.2 traceroute to 131.243.5.2 (131.243.5.2), 64 hops max, 40 byte packets 1 vlan3078.irals.lbl.gov (131.243.78.1) 2.075 ms 1.451 ms 0.403 ms 2 nsals.lbl.gov (131.243.5.2) 1.198 ms 0.410 ms 0.911 ms

4 10

Per port stats for a particular LIF
by David McWilliams 25 Apr '19

25 Apr '19

I'm looking for stats for each individual port of an IFGRP, I know this was straightforward in 7-mode, but does anyone know how to do this in cDOT? Sláinte, David "Build a man a fire he'll be warm for a day, set a man on fire and he'll be warm for the rest of his life" Terry Pratchett

1 0

ONTAP compatibility with Windows 2019 domains
by Filip Sneppe 24 Apr '19

24 Apr '19

Hi, A customer of ours is planning to upgrade his Active Directory to Windows 2019, and is asking what the minimum required ONTAP version is with support for 2019 domains. >From the IMT I get that only ONTAP 9.4 and 9.5 are (officially) supported, but this seems a bit drastic: just doing a bit of research on new AD features in Windows 2019 shows that there no real changes to the domain and forrest functional levels, and that they are functionally equivalent to 2016 domains. Can anyone provide a little more insight or thoughts on this? Thanks in advance! Filip

2 1

XDP transfer already existing snapshots
by Alexander Griesser 22 Apr '19

22 Apr '19

Hi toasters, I've setup an XDP snapmirror relation on one of our customer systems yesterday with the default MirrorAndVault policy (which includes daily and weekly snapmirror labels). After the baseline transfer, I recognized that no daily and weekly snapshots have been transferred to the destination and after deeper investigation I found out that the customer did set up a custom snapshot policy which was missing the snapmirror labels: Custom-policy 3 true - Schedule Count Prefix SnapMirror Label ---------------------- ----- ---------------------- ------------------- daily 7 daily - weekly 4 weekly - I've now modifed the policy (for all future snapshots) and did also modify all existing snapshots to add the labels: snap modify -vserver vserver -snapshot weekly.* -snapmirror-label weekly -volume * snap modify -vserver vserver -snapshot daily.* -snapmirror-label daily -volume * All snapshots do now show the correct snapmirror label, so I ran `snapmirror update` on the destination, but the old snapshots have not been transferred, which is most likely because they've been created "before" the XDP snapshot on the source volume. Newly created snapshots though, the one which got created overnight now with the new sm "daily" prefix, got transferred with the most recent update. What are my options now to also bring all the old snapshots to the destination? Do I need to reinitialize the relation? 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 1

SAS Connectivity Monitor: DualPathToDiskShelf_Alert
by John Stoffel 17 Apr '19

17 Apr '19

Hi guys, My out of support FAS3120 running 8.1.2 7-Mode has suddenly had two instances of the following message sent via autosupport notifications. SAS Connectivity Monitor: DualPathToDiskShelf_Alert[50:05:0c:c1:02:04:db:ad] on mafs1a at Mon Apr 15 20:04:00 PDT 2019 But I'm not seeing anything in the event or alert logs, nor do I see any problems via sysconfig, storage shelf show, etc. I know the cables haven't been touched since I was just at the site this past weekend and the rack doors are closed and locked. Thanks, John P.S. And yes, this sucker should have been upgraded two years ago, but management won't let us...

4 5

dedup and svm dr with xdp
by Peter D. Gray 17 Apr '19

17 Apr '19

I hope I can explain this clearly. We use svm dr for all our backups using XDP (identity preserve). We have many volumes with dedup enabled (not inline). We have many volumes with dedup not enabled. SVMs have volumes with dedup and no dedup. What is supposed to happen on the destination SVM's? It appears that it is running dedup as well even though I cannot figure out what schedule it is using. Some volumes appear to have the same schedule as the source (auto@10). Other volumes appear to have no schedule at all. You cannot disable dedup on a destination volume while the destination svm is a target. You can after you break the snapmirror relationship. But when you resync, it turns it back on I think. My understanding is that XDP preserves deduplication across the mirror, so no dedup should be required or do anything useful on the target but how to stop it? Any ideas on how this is supposed to work or what I am doing wrong? Regards, pdg

1 0

SnapVault and Exchange logs
by SE 16 Apr '19

16 Apr '19

Hi, Is anyone on this list vaulting backups of Exchange? If so, have you found a way to *NOT* SnapVault the logs from Exchange? Our Exchange admins don't want the logs archived as they do restores via SMBR and have dozens of replicas, so they aren't concerned that they'll ever have to replay log files to do a restore from months ago. They do, however, want a year's worth of mailboxes. I know there's a way to force SME not to vault logs, but doing so makes validation of mail DB's mandatory. Our DB's are TB's large and the validations of all the DB's we vault would probably take a week each time. Meanwhile, the exchange log vaults are chewing through aggr space at alarming rates. Does anyone know of a way to vault the Exchange DB's w/o vaulting the logs and forcing validation of the DB's? - Scott

3 2

Re: XDP v DP mirrors
by John Clear 11 Apr '19

11 Apr '19

On Thu, Apr 11, 2019 at 01:56:05PM +0100, S. Eno via Toasters wrote: > > Has anyone seen benefits to using XDP mirrors? Faster? Slower? > Better or worse network compression? We've converted all our snapmirrors to XDP. It is slighltly slower but the benefit of not having to worry about source/destination versions is worth it for us since we have a bunch of clusters cross mirroring different volumes and with DP we had to upgrade a dozen clusters at the same in order to not break snapmirror. John

5 5

XDP v DP mirrors
by S. Eno 11 Apr '19

11 Apr '19

I realize this may be an over discussed topic, but I’m in the process of migrating a bunch of snapmirror relationships and am wondering about real-world impressions / results from anyone on whether it’s better to stay with the “old” snapmirror technology DP, or convert these mirrors to XDP. We’ve just upgraded to 9.3P11 and I already see that “DP” mirrors have been deprecated and have to be re-enabled via CLI. That seems to be a clear message from NetApp on where DP snapmirror is going. Has anyone seen benefits to using XDP mirrors? Faster? Slower? Better or worse network compression? Thanks! Scott

1 0

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 April 2019