CSCvg53159 - percentSNMP-3-RESPONSE_DELAYED processing GetNext of cafSessionEntry.2 seen on catalyst switch - 1

[cslenekes]

Dear Cisco,

We have a Cisco C9500-40X switch with the same problem, but our software version isn't listed on the Known Affected Releases.

Our SW version is:
16.8.1a
CAT9K_IOSXE

Might the problem is in our version too?
Should I open a Cisco TAC Case?

Thank you for your answer!

[michael.burke]

Same here but different MIB objects
16.08.01a
C9300-48P
%SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorType
%SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorScale
%SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision
%SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue
%SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus

[KennyCrumsey29164]

Running a 3 switch stack,

PID: C9300-48UXM...16.8.1a...CAT9K_IOSXE

Sep 25 03:07:02.065 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorType.1121 (5058 msecs)
Sep 25 03:12:18.964 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorScale.2013 (7079 msecs)
Sep 25 03:27:36.390 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5045 msecs)
Sep 25 03:52:27.077 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5199 msecs)
Sep 25 03:52:55.106 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5164 msecs)
Sep 25 03:57:25.170 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5188 msecs)
Sep 25 03:57:53.301 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5019 msecs)
Sep 25 04:07:49.522 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5430 msecs)
Sep 25 04:32:38.201 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5297 msecs)
Sep 25 04:52:02.587 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorType.1121 (5427 msecs)
Sep 25 04:52:30.716 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5265 msecs)
Sep 25 04:57:14.266 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorScale.1121 (5478 msecs)
Sep 25 04:57:42.426 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5185 msecs)
Sep 25 05:42:25.190 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5080 msecs)
Sep 25 05:42:53.677 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5549 msecs)
Sep 25 05:47:37.381 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5588 msecs)
Sep 25 06:07:02.901 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorType.1121 (5598 msecs)
Sep 25 06:07:31.259 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5511 msecs)
Sep 25 06:47:38.937 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5044 msecs)
Sep 25 07:02:02.703 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorType.1121 (5153 msecs)
Sep 25 07:12:25.623 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5396 msecs)
Sep 25 07:12:53.770 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5265 msecs)
Sep 25 07:22:27.606 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5437 msecs)
Sep 25 07:22:55.768 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5272 msecs)
Sep 25 07:47:26.340 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorPrecision.1121 (5359 msecs)
Sep 25 08:02:51.724 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5195 msecs)
Sep 25 09:02:44.403 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorValue.1121 (5196 msecs)
Sep 25 09:08:02.412 PDT: %SNMP-3-RESPONSE_DELAYED: processing GetNext of entSensorStatus.1121 (5099 msecs)

[teljxr1]

This workaround seems to stop these messages on the 9300's:

snmp-server view test internet included
snmp-server view test 1.3.6.1.4.1.9.9.656 excluded
snmp-server community public view test RO

This was recommended per the above bug information.