Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
For a few weeks now, our MC Eventlog gets "spammed" by these events:
notice audit.log.event Auditing error (Audit messages transmission resumed.) occurred at notice audit.log.event Auditing error (Audit messages started to drop. Reason = No buffer space available) occurred at
This "eventflood" happens several times a week and goes on for about two hours, with a total of ~2000 events during this time.
So far we've found that the process for this is "MGWD", but that's it. No further info on how to identify the source of this.
Has anyone else seen this?
Any hint would be much appreciated.
5 REPLIES 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Can you check the
node run * ifstat -A
To see if it aligns with the following KB?
https://kb.netapp.com/app/answers/answer_view/a_id/1041333
Do you have some syslog you sending audit messages to? What version of ONTAP you are running ?
Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
We're running Ontap 9.6P3 and "yes" we send the Ontap events to an elstac cluster, thats actually where we found out first about these events.
From your command, what counter would be of interest?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe "Transmit Queue Overflows" but need somehow to validate it's also increasing in times corresponding to the error. You can maybe dig it from ASUP emails or MyASUP site (https://mysupport.netapp.com/myautosupport/)
If you are using the e0M to send the traffic to the syslog and see that counter grow, try disable/enable the port as the article suggest, and for the long term you might need to add a node-mgmt LIF or move the existing one to more powerful port...
Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Gidon, The KB is not there anymore, any idea what the fix was reported on it exactly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Ravisagar I'm afraid I can't recall the content or what keywords I used to find it (couldn't find it again), sorry.
Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
