Adding a SNMPv3 device or updating a device from SNMPv2 to SNMPv3 using a seedfile

Products

• VMware Smart Assurance

Issue/Introduction

Format and structure of a seedfile for Smarts SNMPv3 Discovery in IP and for trap adapter processing.

Environment

Smarts 10.1.x
Smarts 2.x

Resolution

• The following information is required for SNMPv3 discovery in IP domain seedfile:
  <IP address>
SNMPVERSION=V3
USER=<user>
AUTHPROTOCOL=<select one NONE/MD5/SHA>*
AUTHPASS=<password>
PRIVPROTOCOL=<select one NONE/DES/AES/3DES/AES192/AES256>
PRIVPASS=<password>
ENGINEID=<engineID value>

 

• Smarts 10.1.7 has added support for SHA256 for AUTHPROTOCOL

 

• So an example would be as follows, (please note that each entry for a host IP, and the following details are to be all in one line):
  
  x.x.x.x SNMPVERSION=V3 USER=user1 AUTHPROTOCOL=MD5 AUTHPASS=password1 PRIVPROTOCOL=DES PRIVPASS=despassword ENGINEID=xxxxxxxxxxxxxx

 

• Users can also export the seedfile from the IP domain, by running the following from the command line:

        <basedir>/IP/smarts/bin/sm_tpmgr -s <server> --dump-agents > <seedfile>

Additional Information

EngineID is not necessary for device discovery.  However, if seedfile is used to populate sm_trapd with snmp v3 credentials for trap processing, then the EngineID is needed.

If updating a device from SNMPv2 to SNMPv3, the device does not need to be deleted, a rediscover from seedfile is all that is needed.