A seed file is used to load the SNMPv3 User Security Model (USM) data into the Local Credentials Database (LCD). The SNMP Trap Adapter recognizes SNMPv3 device entries by the engineID/userName pair for a given device listed in the seed file.

A sample seed file is shipped with the Service Assurance Manager software in the InCharge/SAM/smarts/conf/icoi path. The format (syntax) of the seed file used for the SNMP Trap Adapter is the same as it is for an IP domain manager; however, there may be slight variations in field values when used for IP discovery. The VMware Smart Assurance IP Manager User Guide provides specific seed file values required for the discovery process.

Editing seed files on page 50 provides more details about editing seed file entries for use by the SNMP Trap Adapter.

If you plan to use the seed file for both IP discovery and for the SNMP Trap Adapter Scenario 1 (single trap receiver only), then ensure the seed file resides in two places:

  • InCharge/IP/smarts/conf

  • InCharge/SAM/smarts/conf/icoi

    If you plan to use the seed file for the SNMP Trap Adapter Scenario 2 (trap exploder), then ensure the seed file is in the following path (not in the InCharge/SAM/smarts/conf/icoi path mentioned above):

  • BASEDIR/smarts/conf/trapd (where BASEDIR may be either InCharge/SAM/ or InCharge/IP/)

    Be sure to use the sm_edit utility to edit the seed file so that passwords will be encrypted.

    Verify that the secret phrase used to re-encrypt the seed file matches for all products receiving traps from the SNMP Trap Adapter. The VMware Smart Assurance System Administration Guide provides more information about configuring the secret phrase used to encrypt seed files.

    Note:

    Although the SNMP Trap Adapter can parse plain text passwords from unencrypted seed files, VMware strongly recommends that all seed files be encrypted by using the sm_edit utility. The VMware Smart Assurance System Administration Guide provides more information.