title: Inconsistency in variable binding response value - Windows SNMP agent
body: <p>Have an observation the way SNMP get-response values are populated for Microsoft snmp agent and an agent which is running in the switch.</p>
  <p>I am trying to query some object id's. I am sending a request for all the object id's in a single request pdu message.</p>
  <p><strong>Behavior in Windows SNMP agent:</strong></p>
  <p>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 &quot;noSuchObject&quot; and all the requested object id values are returning with null even if there are some valid object id's present in the agent.</p>
  <p>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.</p>
  <p><strong>Please <a href="https://i.stack.imgur.com/UzwBn.png" rel="nofollow noreferrer">Wireshark log (windows agent and cisco switch)</a>refer the attached wireshark snapshot for the windows agent and cisco agent.</strong></p>
  <p>RFC <a href="https://www.rfc-editor.org/rfc/rfc3416#section-4.2.1" rel="nofollow noreferrer">https://www.rfc-editor.org/rfc/rfc3416#section-4.2.1</a>  mentions in the particular scenario response variable binding’s value field shall to set to “noSuchInstance”
  Additional Information:<br />
  Microsoft OS: Windows server 2016</p>
  <p><strong>Questions:</strong></p>
  <p><strong>1.    Why this behavior of Microsoft?</strong></p>
  <p><strong>2.    Is there any Microsoft forum to get further support for this?</strong></p>
  <p><strong>3.    Any existing solution or workaround for this problem?</strong></p>