#<encrypted seed>:1.0:AUTHPASS,PRIVPASS
128.221.19.8 
SNMPVERSION=V3 
USER=shaAESUser 
AUTHPROTOCOL=SHA 
AUTHPASS=123ABC456#$%123abc456#$%
PRIVPROTOCOL=AES 
PRIVPASS=456123abc456#$%456123ABC456#$%
ENGINEID=0000000902000003E333C440
qa-gwipv6 
SNMPVERSION=V3 
USER=MD5DesUser 
AUTHPROTOCOL=MD5 
AUTHPASS=789ABC456#$%789abc456#$%
PRIVPROTOCOL=DES
PRIVPASS=789123abc456#$%789123ABC456#$%

ENGINEID=000000090200000F134B93C

SNMPv3-related seed file field descriptions lists and describes seed file fields for SNMPv3.

Table 1. SNMPv3-related seed file field descriptions

Field

Description

AUTHPROTOCOL

Specifies the authentication protocol in use by the network device sending the SNMPv3 traps. Valid entries include MD5, NONE, or SHA. For the SNMP trap processor, if no value is specified, it defaults to NONE.

Note:

The default value used in the discovery process by the IP Manager may differ. The VMware Smart Assurance IP Manager Release Notes provide more information.

AUTHPASS

Authentication password. This may be 64 characters long. VMware, Inc. recommends the use of complex passwords (for example, a long string of uppercase or lowercase alpha characters, numbers, and special characters)

ENGINEID

An engineID is a unique string identifying an SNMP engine. It does not uniquely identify a DEVICE, because technically, a device can host multiple SNMP agents. So, the engine ID is assigned to each agent, not device.

If you have VMware Smart Assurance IP Availability Manager running, you can use the sm_tpmgr -s <server name> --dump-agents command to find the engineIDs for those agents generating SNMPv3 traps in your network.

PRIVPASS

Privacy (encryption) password. This may be 64 characters long. VMware, Inc. recommends the use of complex passwords (for example, a long string of uppercase or lowercase alpha characters, numbers, and special characters).

PRIVPROTOCOL

Privacy (encryption) protocol in use by the router sending the SNMPv3 traps. Valid entries include DES, NONE, or AES. If no entry, defaults to NONE.

To simplify debugging of your network device configurations, VMware, Inc. recommends that you first establish that SNMPv3 traps sent from the network device in noAuthNoPriv mode are processed correctly. When you are sure that it works, use authNoPriv and finally authPriv, after verifying correct operation at each step.