Accton Technology ES3552XA, ES3526XA manual Configuring SNMPv3 Users

Configuring SNMPv3 Management Access 3

configure the remote agent’s SNMP engine ID before you can send proxy requests or informs to it. (See “Specifying Trap Managers and Trap Types” on page 3-41and “Configuring Remote SNMPv3 Users” on page 3-47.)

The engine ID can be specified by entering 1 to 26 hexadecimal characters. If less than 26 characters are specified, trailing zeroes are added to the value. For example, the value “1234” is equivalent to “1234” followed by 22 zeroes.

Web – Click SNMP, SNMPv3, Remote Engine ID. Enter an ID of up to 26 hexadecimal characters and then click Save.

Figure 3-28 Setting an Engine ID

CLI – This example specifies a remote SNMPv3 engine ID.

Console(config)#snmp-server engineID remote 54321 192.168.1.19	4-123
Console(config)#exit
Console#show snmp engine-id	4-124
Local SNMP engineID: 8000002a8000000000e8666672
Local SNMP engineBoots: 1
Remote SNMP engineID	IP address
80000000030004e2b316c54321	192.168.1.19
Console#

Configuring SNMPv3 Users

Each SNMPv3 user is defined by a unique name. Users must be configured with a specific security level and assigned to a group. The SNMPv3 group restricts users to a specific read, write, or notify view.

Command Attributes

•User Name – The name of user connecting to the SNMP agent. (Range: 1-32 characters)

•Group Name – The name of the SNMP group to which the user is assigned. (Range: 1-32 characters)

•Security Model – The user security model; SNMP v1, v2c or v3.

•Security Level – The security level used for the user:

-noAuthNoPriv – There is no authentication or encryption used in SNMP communications. (This is the default for SNMPv3.)

-AuthNoPriv – SNMP communications use authentication, but the data is not encrypted (only available for the SNMPv3 security model).

-AuthPriv – SNMP communications use both authentication and encryption (only

3-45