Has anyone meet the error below,

An error occurred while removing port group ONTAP-CC from host 192.168.10.10. Verify the configuration of port group ONTAP-CC on host 192.168.10.10, and then try again. If a cluster has been deployed and subsequently reconfigured outside of ONTAP Select Deploy, run a refresh operation on the cluster, and then try again.

We have two clusters running ONTAP 9.5P9. Currently, there is a volume level replication between two SVMs which are in each clusters.

We would like to transition from Volume Level DR -> SVM DR but without preserving the configuration of the source SVM ("identity-preserve=false").

Following the instructions of this article: https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-dap%2FGUID-3D8765BC-2ECC-4704-8F57-4767E98C3203.html  , we have created in step 2 the relationship between the two SVMs with the option "identity-preserve=false".

When we try to resync the relationship we get the following error:

cluster2::*> snapmirror resync -source-path svm1: -destination-path svm1_dst: 

Error: command failed: The Vserver DR relationship selected for the operation has "identity-preserve" set to "false" and has FlexVol SnapMirror relationships within. This command is allowed only when the Vserver DR relationship has "identity-preserve" set to "true".

Is this a normal behavior? Is this option not supported?

Thank you.

Has anyone run ONTAP Select on server(s) with AMD EPYC processors?  Would that be a supported configuration?  I don't see any AMD references in the IMT...

Is there any way to remove failed CIFS events out of the event logs ?

when i run event log show i get a lof of CIFS login errors.

ERROR secd.cifsAuth.problem: vserver (vs1) General CIFS authentication problem. Error: User authentication procedure failed

CIFS SMB2 Share mapping - Client Ip = 10.xx.xx.xx
[ 0 ms] Login attempt by domain user 'Lxxxxxxxxx3\Administrator' using NTLMv2 style security
[ 0] Using a cached connection to lxxxxxxxx3.ap.xxxxx.com
[ 2] Authentication failed with DC LXXXXXXXX3. Not retriable. (Status: 0xc0000064)
[ 2] Login attempt by local user 'LXXXXXXXXX3\Administrator' using NTLMv2 style security
**[ 2] FAILURE: CIFS authentication failed

Details
Event:
secd.cifsAuth.problem: vserver (vs1) General CIFS authentication problem. Error: User authentication procedure failed CIFS SMB2 Share mapping - Client Ip = 10.xx.xx.xx [ 0 ms] Login attempt by domain user 'LXXXXXXXX3\Administrator' using NTLMv2 style security [ 0] Using a cached connection to lxxxxxxx3.ap.xxx.xxx [ 2] Authentication failed with DC Lxxxxxxxx3. Not retriable. (Status: 0xc0000064) [ 2] Login attempt by local user 'LXXXXXXXX3\Administrator' using NTLMv2 style security **[ 2] FAILURE: CIFS authentication failed
Message Name:
secd.cifsAuth.problem
Sequence Number:
273996
Description:
This message occurs when a CIFS authentication attempt fails for any reason other than an unknown user name or bad password.
Action:
Examine the failure details to determine corrective action. Common failures include the inability to communicate with domain controllers, NIS servers, or LDAP servers due to connectivity or configuration problems.

We get our support desk to login and check of there are errors and there are lots of these

Any ideas how to remove these ?

can i edit the event catalog and change this to an Alert ?

Message Name: secd.cifsAuth.problem
Severity: ERROR
Description: This message occurs when a CIFS authentication attempt fails for any reason other than an unknown user name or bad password.
Corrective Action: Examine the failure details to determine corrective action. Common failures include the inability to communicate with domain controllers, NIS servers, or LDAP servers due to connectivity or configuration problems.
SNMP Trap Type: Severity-based
Is Deprecated: false

Hello

I would like to get performance data from weekly PERFORMANCE DATA autosupport message. I found files with ccma extension in the asup but I don't know how to open it. Is it even possible for a user to get something from this asup messages?

Thank you

Jan

Hello,

        We have 2 contrillers namely Ctrl1 and Ctrl2 both are FAS3240 connected to DS4243 and DS224 in HA Pair. 

1) I would like to know which controller is the primary node. ?

2) If ctrl2 is the primary node then how can i let ctrl1 act as a primary node.

when I do a cf giback 

ctrl2 is is giving back and ctrl1 show me takeover mode.

I want ctrl1 to be primary node and in case the problem occurs ctrl2 should take over.

Thanks

Running ONtap9.1 here, we have a testing NetApp that hasnt been turned on for about a year, i just recently bought a HA cable from online so figured ill connect the FAS2240-4 and try and create a HA pair.

I connected the cable and created a cluster from scratch, i used the GUI after giving e0M an IP and it said it could only detect one node.

After connecting the HA cable, is tehre something i have to do so i can add the secondary node to the cluster?

Any help would be more than appreiciated!

I have a FAS2240-4 in eval environment and the storage have been turned off for the good part of a year. 

I just recently turned it back on to create a cluster and when i went to the system console via SP, it said the "the battery is unfit to retain data during a power outage"

Figured its only a test so i ignored it and went to create the cluster anyway, but now i am worried when looking at the result from system battery show (below)

------------------

chemistry : LION
device-name : bq20z80
expected-load-mw : 133
id : 27100029
manufacturer : EnergySales
manufacturer-date : 11/22/2012
rev_cell : 0x0000
rev_firmware : 0x0100
rev_hardware : 0x00a3
TI_fw_version : 0x0110
TI_hw_version : 0xa2
serial : 0x6fe1
status : charging

------------------

When i ran the list-sensors from the created node, it said the following in the "Bat Run Time"

------------------

VL-FS01_1> environment status chassis list-sensors
Sensor Name State Current Critical Warning Warning Critical
Reading Low Low High High
-------------------------------------------------------------------------------------------------
Power Good OK
AC Power Fail OK
Bat 1.5V normal 1522 mV 1277 mV 1341 mV 1651 mV 1728 mV
Bat 8.0V normal 7600 mV -- -- 8600 mV 8700 mV
Bat Curr normal 500 mA -- -- 800 mA 900 mA
Bat Run Time critlow 36 hr 76 hr 78 hr -- --
Bat Temp normal 36 C 0 C 10 C 55 C 64 C
Charger Curr normal 500 mA -- -- 2200 mA 2300 mA
Charger Volt normal 8200 mV -- -- 8600 mV 8700 mV
SP Status IPMI_HB_OK

------------------

does this mean that the battery thats having a "problem" is charging? like is it matter of waitning and itll fix it self? is this going to have a major impact on the cluster that i created?

Any help would be more than appreicated!

thanks!

Hello;

I have a FAS 2240-4 Single Head with one DS4246, and want to add the next DS4246.

My Plan tooks like this:

1. Cabling of the ACP correct (picture i found ihe forum)

2. Cabling the SAS, connect the Controller with the new Shelf firt, then connect Shelf 3 with Shelf 2.

Is this a way to do it with no ninterruprion?

What do you recommend?

Many Thanks, Thomas

Per the following announcement, the NetApp CN1610 switch won't be supported past 12/31/2020. We have been using it since we moved to Cluster Mode and need to determine which model to replace this with. Is there a KB article or other resource that lists the supported replacement models? I couldn't find a section of the IMT with this information.

https://mysupport.netapp.com/info/communications/ECMLP2859128.html

Hi guys,

Has anyone experienced the following problem with 7MTT at the Pre-Cutover phase?

https://kb.netapp.com/app/answers/answer_view/a_id/1008069/~/7mtt-error-01061-job-failed.-reason%3A-a-technical-error-has-occurred.-contact

The problem is that I couldn't find any invalid character in configuration mentioned in the above KB (the possible reason).

Source:     8.2.5 - 7-Mode 

Destination: Ontap 9.1P19

The only usable log I found is the following:

java.lang.IllegalArgumentException: Illegal group reference: group index is missing
at java.util.regex.Matcher.appendReplacement(Unknown Source) ~[na:1.8.0_144]
at java.util.regex.Matcher.replaceFirst(Unknown Source) ~[na:1.8.0_144]
at java.lang.String.replaceFirst(Unknown Source) ~[na:1.8.0_144]
at com.netapp.transition.operations.AbstractOp.getClusterPathFor7ModePath(AbstractOp.java:350) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.apply.CifsVolumeConfigApplyHandler.applyShareConfig(CifsVolumeConfigApplyHandler.java:203) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.apply.CifsVolumeConfigApplyHandler.execute(CifsVolumeConfigApplyHandler.java:128) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.TransitionApplyOp.applyCifsConfigurations(TransitionApplyOp.java:164) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.TransitionApplyOp.execute(TransitionApplyOp.java:103) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.complete.CTAHelper.apply(CTAHelper.java:102) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.complete.TransitionPrecutoverHandler.doCTA(TransitionPrecutoverHandler.java:343) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.complete.TransitionPrecutoverHandler.execute(TransitionPrecutoverHandler.java:129) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.TransitionPrecutoverOp.performPreCutover(TransitionPrecutoverOp.java:290) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.operations.TransitionPrecutoverOp.execute(TransitionPrecutoverOp.java:160) ~[transition-operations.jar:3.3.1]
at com.netapp.transition.jobmanager.PrecutoverJob.performPreCutover(PrecutoverJob.java:141) ~[transition-job-manager.jar:3.3.1]
at com.netapp.transition.jobmanager.PrecutoverJob.execute(PrecutoverJob.java:97) ~[transition-job-manager.jar:3.3.1]
at com.netapp.transition.jobmanager.AbstractJob.run(AbstractJob.java:203) ~[transition-job-manager.jar:3.3.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_144]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_144]

Any ideas about what is happening here?

Thanks a lot!!!

I am trying to find all volumes on a cluster that do not have efficiencies enabled, but can't seem to get my syntax correct.  What am I missing?

Running the code below returns all the volumes that DO have SIS enabled on them:

$Vols = Get-NcVol
$Vols | Get-NcSis | Where-Object {($_.State)}

But, I can't seem to get it to return the volumes that do not have any SIS settings at all.  I've tried each of the following with the assumption that the property doesn't exist for any volumes that do not have SIS enabled:

$Vols | Get-NcSis | Where-Object {(!$_.State)}
$Vols | Get-NcSis | Where-Object {($_.State -eq $NULL)}
$Vols | Get-NcSis | Where-Object {($_.State -notcontains $NULL)}

All of them return nothing, even though there is at least one volume that does not have SIS enabled.

This is OnTap 9.5P3 and PSTK 4.7.

Thanks for any suggestions!

Hello,

        I have Snapmanager for exchange and my backup are working good but and show consistent. Last few days back one of my coleague deleted lot of snapshot copies manually ro reclaim the space of volume, I am afraid if we deleted the base snapshot.

how do I know the base snapshot is in good health.

Also in snap drive I see snapshots with only GUIDS  please see the attached what are those ??  becasue the usual snapshots are with generic name and date 

hello, with the helps of everyone last night, i was able to create my eval netapp cluster, i have come across yet another problem...

i created an CIFS SVM and i was able to create a LIF for the svm but cannot join the SVM to a domain with the below error

Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
12/10/2019 14:55:24 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:55:18 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:55:11 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:55:04 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:54:56 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:51:52 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:51:46 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:51:43 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:51:40 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:51:39 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:49:40 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:49:34 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:49:31 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:49:28 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:49:27 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:47:50 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:47:44 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:47:41 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:47:38 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:45:48 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:45:42 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:45:39 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:45:36 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:45:35 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:41:09 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:41:03 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:41:00 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:40:57 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:40:56 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:35:35 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:35:29 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:35:26 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:35:23 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:35:22 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:33:22 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:33:16 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:33:13 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:33:10 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-SVM-FS01) with error (Operation timed out).
12/10/2019 14:33:09 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-SVM-FS01 within timeout interval.
12/10/2019 14:27:17 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:27:11 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:27:08 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:27:05 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:27:04 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-FS01-CIFS within timeout interval.
12/10/2019 14:21:31 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:21:25 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:21:22 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:21:19 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:21:18 EVL-FS01_1       ERROR         secd.dns.server.timed.out: DNS server 10.152.0.5 did not respond to vserver = EVL-FS01-CIFS within timeout interval.
12/10/2019 14:16:26 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_kerberos._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:16:20 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).
12/10/2019 14:16:17 EVL-FS01_1       ERROR         secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.SV-AD.NBN.LOCAL) for vserver (EVL-FS01-CIFS) with error (Operation timed out).

on the GUI it has the following error

Failed to create the Active Directory machine account "EVL-FS01-CIFS". Reason: SecD Error: no server available Details: Error: Machine account creation procedure failed [ 0 ms] Trying to create machine account 'EVL-FS01-CIFS' in domain 'SV-AD.NBN.LOCAL' for Vserver 'EVL-FS01-CIFS' [ 2006] Failed to connect to 10.152.0.5 for DNS via Source Address 10.156.100.24: Operation timed out [ 3008] Failed to connect to 10.152.0.6 for DNS via Source Address 10.156.100.24: Operation timed out [ 5016] Failed to connect to 10.152.0.5 for DNS via Source Address 10.156.100.24: Operation timed out [ 6017] Failed to connect to 10.152.0.6 for DNS via Source Address 10.156.100.24: Operation timed out **[ 6017] FAILURE: Unable to contact DNS to discover domain ** controllers. [ 6017] Unable to connect to any (0) domain controllers. [ 6018] 'NisDomain' configuration not available [ 6018] NIS configuration not found for Vserver 3 [ 8024] Failed to connect to 10.152.0.5 for DNS via Source Address 10.156.100.24: Operation timed out [ 9026] Failed to connect to 10.152.0.6 for DNS via Source Address 10.156.100.24: Operation timed out [ 9026] Unable to contact DNS to discover domain controllers. [ 11034] Failed to connect to 10.152.0.5 for DNS via Source Address 10.156.100.24: Operation timed out [ 12036] Failed to connect to 10.152.0.6 for DNS via Source Address 10.156.100.24: Operation timed out [ 12036] Unable to contact DNS to discover domain controllers. [ 14044] Failed to connect to 10.152.0.5 for DNS via Source Address 10.156.100.24: Operation timed out [ 15045] Failed to connect to 10.152.0.6 for DNS via Source Address 10.156.100.24: Operation timed out [ 15046] Unable to contact DNS to discover domain controllers. [ 15046] No servers available for MS_LDAP_AD, vserver: 3, domain: SV-AD.NBN.LOCAL. [ 15046] Failed to find a domain controller .

i have looked on numerous previous discussions and i reconfigured the DNS settings on my cluster and my SVM, the time zones are set complete fine in sync with the DC, but still cannot join the domain.

any help would be much appreicated

I have weird spanshot called  {9ec98bf7-fd19-4471-9b95-b15a52abbeb7} in the snapdrive and its in the consistent state if I compare it with the other snapshot they have the server name, date and time but the above name is diffrent.

1) Why the name is generated like this and why it takes so much space if compared with the other snapshots

2) can I delete it ? if yes what will be the impact ? 

Please see the attadched to understand completely

Hi all,

I give up, I'll never be a Windows guy.

Please enlighten me: With no SnapDrive on board, how is it possible to identify the name of an iSCSI LUN on an ONTAP 9 filer?

I tried to match any sort of number from the outputs of

::> lun mapping show

::> lun show

and

::> iscsi session show

with the outputs of

PS C:\Users\admin> iscsicli

and

PS C:\Users\admin> Get-IscsiConnection

to no avail.

All I want is to find the name of the LUN/volume on Windows to find the corresponding object on the filer to modify.

Any clues?

Thanks and best regards

Peter

Hey,

I have two CN1610 switches serving a 4 node cluster.

Can I connect to these switches another 4 nodes for a different cluster?

Is this supported? will this work but will not be supported?

thanks!

Hello everyone,

I can't figure out the issue why my snapmirror over 10Gbps network not exceeding 370Mbps.

I've created a snapmirror between two clusters FAS2750 and FAS2552

Both have SAS disks, they're conncted to the same Juniper 10GbE switch.

FAS2750 have LACP configured for two ports, FAS2552 have one dedicated port for replication.

1. disabled Flow-Control on Juniper and Netapp

Juniper = set interfaces xe-0/1/6 ether-options no-flow-control

ONTAP = network port modify -node <node> -port e0d -flowcontrol-admin none

2. increased TCP windows size (both clusters)

options snapmirror.window_size (8,388,608 bytes for 10GbE network)

https://library.netapp.com/ecmdocs/ECMM1278318/html/onlinebk/protecting/task/t_oc_prot_sm-adjust-tcp-window-size.html

3. Throttle disabled (both clusters)

replication.throttle.enable off -
replication.throttle.incoming.max_kbs unlimited -
replication.throttle.outgoing.max_kbs unlimited -

Juniper interface transfer rate 387315168 bps rate

monitor interface xe-0/1/6

ONTAP interface transfer rate 38.9 MB

statistics show -object nic_common -instance e0d -counter rx_bytes -node <node> 

node run -node <node> sysstat -c 10 -x shows

Source 30% CPU and 80% Disk Utilization

Target 90% CPU and 90% Disk Utilization

i'm lost and made too many changes to find the root cause, any advices ?

I'm already install tibreaker for metrocluster, but failed to start, it supposed to open CLI 

NetApp MetroCluster Tiebreaker :>

does anyone have the same issue in the past? access is already "root" an remains on root  

We had a working setup running Oracle DNFS on a 7-mode FC MetroCluster. After transistion to C-Dot with ONTAP 9.5 DNFS produces strange behavior, slowness and Oracle errors. We don't find any reason. At the end we disabled DNFS and switched to NFS. We search for anyone who has a working C-Dot setup with DNFS to compare configurations (perhaps we missed something).

Best regards

Uwe