You can try pushing Microsoft to fix this particular bug, but in my view the odds of success are very low, and even then you'd still have to support the older implementation. Unfortunately you seem to have found one of them. When writing an SNMP agent or manager you have to be aware of all manner of in-practice deviations from the expected behaviour.

Any existing solution or workaround for this problem?Īs Lex indicated in his/her comment, the SNMP ecosystem enjoys remarkable noncompliance across implementations despite a wonderfully precise 'standard' (via RFCs).

Is there any Microsoft forum to get further support for this?ģ. RFC mentions in the particular scenario response variable binding’s value field shall to set to “noSuchInstance”Ģ. Please Wireshark log (windows agent and cisco switch)refer the attached wireshark snapshot for the windows agent and cisco agent. Whereas we tried getting the same list of oids from an agent running in a cisco switch, there the error code is set for the specific variable binding and it is returning values for all the other oids which are present. In the requested object ids, if any object id is not present in the agent, then the entire response message is set with the errorcode 'noSuchObject' and all the requested object id values are returning with null even if there are some valid object id's present in the agent. I am sending a request for all the object id's in a single request pdu message. Have an observation the way SNMP get-response values are populated for Microsoft snmp agent and an agent which is running in the switch.

Wireshark windows snmp