topic Re: Log spammed with "secd.authsys.lookup.failed" in ONTAP Discussions

Log spammed with "secd.authsys.lookup.failed"

gfz-marco — Wed, 04 Jun 2025 13:20:22 GMT

Hello

Recently our logs get spammed with "secd.authsys.lookup.failed" events on one of our nfs svms.

We can see that that an invalid UID is used but we can't see from which client.

How can we find the culprit, is this done by activating a security audit or is it hidden somewhere inside the logs?

Any tip would be appreciated.

Cheers

Marco

Re: Log spammed with "secd.authsys.lookup.failed"

gfz-marco — Tue, 18 Sep 2018 11:53:43 GMT

Since we get around 1500-2000 events per day, i've opened a case now.

Lets wait and see about the outcome...

Re: Log spammed with "secd.authsys.lookup.failed"

moep — Fri, 28 Sep 2018 08:42:21 GMT

I have seen similar events in the past and opened a case as well. NetApp is unable to identify the source because there is no logging of the client address. Also there is no auditing for NFSv3 access available. The log messages are completely useless this way. I complained about it, but as usual nobody cares at NetApp.

Re: Log spammed with "secd.authsys.lookup.failed"

gfz-marco — Fri, 16 Nov 2018 13:34:03 GMT

After working for many days on this case with a netapp supporter, we could not find an "easy" way to identify these uids but i was presented with a workaround.

This involves a tcpdump on a node and filtering through the tracefile with wireshark.

Not really what i was looking for but this works for now and the supporter even created a feature request from our findings.

We'll see how that comes out...

I would say that they care at netapp, but it involves work on both sides.