[AGENT++] GET request with bad IOR
Frank Fock
fock at agentpp.com
Mon Jun 18 23:35:27 CEST 2012
Hi,
If the message processing protocol was SNMPv2c or v3
then the agent should have returned a variable exception
syntax "noSuchObject" instead an error status.
Then the other objects values should have been returned
by the agent.
With SNMPv1, the agent can/must return an error status.
Best regards,
Frank
Am 18.06.2012 21:28, schrieb Jochen Katz:
> Hello,
>
>> Sorry, -6 is the callback reason. The error status is 2, Variable
>> does not exist.
> -6 is SNMP_CLASS_ASYNC_RESPONSE, so the agent has answered the request.
>
>>> we are using SNMP++ V3.2 (SNMPv2 only) with GET PDUs containing many
>>> IORs. We noticed that the entire GET request fails with status -6 if
>>> only a single IOR is unknown and rejected by the agent. Is this intended
>>> behaviour or are we missing something? Is it not possible to get the
>>> existing parameters in spite of single erroneous IORs?
> As the PDU can hold only one error status and error index, an agent has
> nochance to return more than one error to the manager. So it stops
> processing the request at the first error and returns error status and
> the index. The manager should remove the Vb with the returned index and
> try again.
>
> Regards,
> Jochen
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
More information about the AGENTPP
mailing list