I found following message spamming my switch log
[...]
000897: Oct 27 20:56:12.577 CET: %SNMP-3-RESPONSE_DELAYED: processing GetNext of ciscoFlashFileEntry.x (5264 msecs)
000898: Oct 27 20:57:19.077 CET: %SNMP-3-RESPONSE_DELAYED: processing GetNext of ciscoFlashFileEntry.x (5379 msecs)
000899: Oct 28 20:59:08.209 CET: %SNMP-3-RESPONSE_DELAYED: processing GetNext of ciscoFlashFileEntry.x (5273 msecs)
000900: Oct 28 21:00:06.227 CET: %SNMP-3-RESPONSE_DELAYED: processing GetNext of ciscoFlashFileEntry.x.xx.x.xx (5228 msecs)
000901: Oct 28 21:00:13.511 CET: %SNMP-3-RESPONSE_DELAYED: processing GetNext of ciscoFlashFileEntry.x (5567 msecs)
[...]
The workaround says:
And this response threshold can also modified to a higher time interval through this config command ?snmp monitor response ?.
This is not very helpful, because we are only allowed to set the threshold to 5k msecs
<1000-5000> provide the threshold limit in msecs
The 2nd option in the workaround is to suppress the messages at all:
And if we configure ?no snmp monitor response? , the mechanism to compare response time [...]
Well. Yes but no.
This message is a nice indicator if something is starting to get wrong on the switch. If a switch, all of the sudden, throws those messages it may indicates high CPU load or else. Then we have the opportunity to react, i.e. to create a TAC case.
Just hiding things don´t make them go away. Putting the dirt under the carpet makes the room look nice. But the dirt is still there.
If anyone finds a solution, please let me know
