Hi Blaine,
The RFC states:
A non-authoritative SNMP engine must keep local notions of these
values (snmpEngineBoots, snmpEngineTime and latestReceivedEngineTime)
for each authoritative SNMP engine with which it wishes to
communicate. Since each authoritative SNMP engine is uniquely and
unambiguously identified by its value of snmpEngineID, the
non-authoritative SNMP engine may use this value as a key in order to
cache its local notions of these values.
As you noted, vendors are in violation of this. As Spectrum is the non authoritative SNMP engine, Spectrum isn’t in violation of the RFC as the RFC doesn’t state the non authoritative SNMP engine needs to maintain a unique engine id for the authoritative SNMP engine.
Spectrum still uses the engineid as a part of the key for the cache, but with the patch we also add the IP to the key. This allows Spectrum to uniquely identify the agent, even though there are duplicate engineIDs.
We have received so many cases from customers that are unable to model devices because of the same engineids and they are unable to change them for various reasons. We kept Spectrum within compliance of the RFC and now allow customers to be able to manage those devices appropriately.
I understand your concern about the alarms. The alarms were removed due to feedback by the customers that tested the solution for us.
Please let me know if you have any questions.
Thank you!
Jay