Understanding SNMP v3 engine-id  

When you create an SNMPv3 user, you provide a username and associated passwords for authentication and encryption. These passwords, along with the engine ID (a unique identifier for the SNMP entity), are used to generate authentication and encryption keys

Here's a breakdown of the terms:

SNMPv3 User: A configuration entry on the Juniper device that defines the settings for SNMPv3 access. This includes the username and the associated authentication and privacy (encryption) passwords.

Authentication Key: A cryptographic key derived from the authentication password and the engine ID. This key is used to create message authentication codes (MACs) for SNMP messages to ensure their integrity and authenticity.

Encryption Key: A cryptographic key derived from the privacy password and the engine ID. This key is used to encrypt and decrypt SNMP messages to ensure their confidentiality.

The process of generating these keys involves using the passwords provided during the SNMPv3 user configuration, along with the unique engine ID assigned to the SNMP entity (which can be different for different SNMP entities in a network).

So, when the document mentions that SNMPv3 authentication and encryption keys are generated based on the associated user passwords and the engine ID, it's referring to the keys that are used to secure SNMPv3 communication for the specific SNMPv3 user you configure on the Juniper device.

 Resources: https://www.juniper.net/documentation/us/en/software/junos/network-mgmt/topics/ref/statement/engine-id-edit-snmp.html

dcole-9/13/2023 created