Hi,
The NMS should be fixed. That is the only way to fix it standard conform.
For SNMPv3 messages, the msgId is the only lookup key for responses.
Engine ID and security name must also match, but the lookup is done by
the message ID only (not with the IP address).
Thus, the command responder may send its response from a different IP
address. Nevertheless, the engine ID in the response (which typically
contains also an
IP address to make it unique) must match the authoritative engine ID used
in the request.
Best regards,
Frank
Am 30.11.2015 um 20:32 schrieb Pradipmaya Maharana:
Our server has multiple NICs (and hence multiple IPs). We present user with
a management IP to support high availability, just in case one of the NIC
goes down.
So, lets say the NIC ips are: 10.10.10.11 (primary) and 10.10.10.22
(secondary) and the management IP is 10.10.10.55.
When the user sends SNMP GET request to the management IP, 10.10.10.55, the
request goes to the primary NIC, and so the response is returned from the
10.10.10.11.
Which is fine most of the time, but in some cases, as the response IP is
different from the request IP, the management software (NMS), which made
the GET request, fails the operation saying "no response".
Basically the NMS does get a response but as the response ip is different,
NMS ignores it and fails the operation.
How can this be resolved?
_______________________________________________
SNMP4J mailing list
[email protected]
https://oosnmp.net/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
[email protected]
https://oosnmp.net/mailman/listinfo/snmp4j
