Perhaps open up a case and get a product enhancement request raised. Or, there may be a way to bypass those alerts that I am unaware of.

From: Alexander Griesser [mailto:AGriesser@anexia-it.com]
Sent: Tuesday, September 5, 2017 10:34 AM
To: Parisi, Justin <Justin.Parisi@netapp.com>; toasters@teaparty.net
Subject: AW: DNS Configured Check - High Impact on ConfigAdvisor

Hey Justin,

yah, I’m aware about that change and people doing things like that which break after upgrading to 8.3; but ConfigAdvisor should (in my opinion) be smarter about that.

It’s easy for CA to check if DNS is active inside a SVM and alert for the absence of DNS _ONLY_ if there are export policies configured for hostnames; otherwise, the way it is now, all my install reports need additional explanation when there’s so much red in CA J

Maybe I’m just to stupid to find the setting for configuring individual alerting levels based on the findings of CA, but so far, I’ve not been successful in at least converting them to info notices or anything like that.

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: 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

Von: Parisi, Justin [mailto:Justin.Parisi@netapp.com]
Gesendet: Dienstag, 5. September 2017 16:02
An: Alexander Griesser <AGriesser@anexia-it.com>; toasters@teaparty.net
Betreff: RE: DNS Configured Check - High Impact on ConfigAdvisor

The config check for DNS was added around 8.3.x because we moved where DNS was handled from the cluster scope to the SVM scope. Many customers had DNS configured for the cluster, but not the SVM. This would break export policies and other services and cause outages, which is why it’s rated as “high impact.”

TR-4379 covers the DNS changes regarding upgrades:

www.netapp.com/us/media/tr-4379.pdf

Not sure how you can tell config advisor to ignore those things.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Alexander Griesser
Sent: Saturday, September 2, 2017 5:46 AM
To: toasters@teaparty.net
Subject: DNS Configured Check - High Impact on ConfigAdvisor

Hey,

can anyone explain to me why „DNS Configured Check“ is rated as high impact on SVMs in ConfigAdvisor 5? I’m not using DNS at all in any of my SVMs, all connections are IP-based and all my reports now look pretty bad with x High Impact Issues where x is the number of SVMs.

Also, the Management LIF configurations are rated as Low Impact and in my point of view it’s also not necessary to have separate management LIFs for SVMs if I do not give access to them to my tenants or require any Snapmanager integrations.

Any idea how I can tell ConfigAdvisor to just ignore those things?

Thanks,