[ZBX-6206] We do not mention in documentation why EngineID must be unique Created: 2013 Feb 01  Updated: 2019 Mar 13  Resolved: 2014 Sep 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: documentation, snmpv3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-11090 SNMPv3 fails when more than one host Closed

 Description   

Information about why "Engine ID" must be unique should be placed on: https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/snmp

Look comment below for getting more information (details and links).



 Comments   
Comment by Alexey Pustovalov [ 2013 Feb 01 ]

1. RFC 2571: http://www.ietf.org/rfc/rfc2571.txt

3.1.1.1. snmpEngineID

Within an administrative domain, an snmpEngineID is the unique and unambiguous identifier of an SNMP engine. Since there is a one-to-one association between SNMP engines and SNMP entities, it also uniquely and unambiguously identifies the SNMP entity within that administrative domain. Note that it is possible for SNMP entities in different administrative domains to have the same value for snmpEngineID. Federation of administrative domains may necessitate assignment of new values.

2. net-snmp library: http://net-snmp.sourceforge.net/docs/man/snmpd.conf.html

SNMPv3 requires an SNMP agent to define a unique "engine ID" in order to respond to SNMPv3 requests.

3. Cisco IOS: http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_20.html

The SNMP engine ID is a unique string used to identify the device for administration purposes.

zalex_ua Added the RFC hyper link to all documentation branches.
Diff is here https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/snmp?do=diff&rev2%5B0%5D=1397223343&rev2%5B1%5D=&difftype=sidebyside
RESOLVED.

asaveljevs RFC 2571 is a long document. Perhaps we should mention that the relevant information is in section 3.1.1.1 specifically?

zalex_ua weeeeel, done

asaveljevs Looks good to me. Can be copied to documentation pages for other versions, too.

zalex_ua it was copied to all branches initially.
Ok, CLOSED.

Generated at Fri Apr 26 07:27:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.