[ZBXNEXT-1789] improve duplicate snmpv3 engineid detection and documentation Created: 2013 Jun 11  Updated: 2017 Apr 26  Resolved: 2017 Apr 26

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Documentation (D), Proxy (P), Server (S)
Affects Version/s: 2.0.6
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: richlv Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: snmp, snmpv3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBX-8385 snmpV3 report (response) "usmStatsNot... Closed

 Description   

split out from ZBX-2152.

a) we should document a bit more about duplicate engineids, how to debug that etc;
b) we could try to detect such a problem and provide better error messages, too. quoting asaveljevs :

My research shows that NET-SNMP provides information about the discovered snmpEngineID. I propose to remember what snmpEngineID sits on what IP:port, and if we discover a collision, we provide a good log and NOTSUPPORTED message to help identify the problem. I do not think we should do anything beyond that.

 Comments   
Comment by Oleksii Zagorskyi [ 2014 Jun 23 ]

I'd close this one in favor to ZBX-8385
I've described there arguments why it should be considered as a bug, not a feature request.

Closed.

Comment by Oleksii Zagorskyi [ 2017 Apr 26 ]

Reopened and closed with more proper resolution.

Generated at Sat Apr 20 01:32:38 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.