1. The trapd.conf file used to configure the trap exploder is included in all VMwareproducts installed into the BASEDIR/smarts path. Use sm_edit to modify BASEDIR/smarts/conf/trapd/trapd.conf. Specify the port to forward traps to as well as the hostnames of the Domain Managers. If some of the traps should be converted to notifications, complete a forwarding entry to send those traps to the trap receiver associated with the Adapter Platform. Configuring trapd.conf (trap exploder and trap receiver) provides an example.

  2. (Optional: for SNMPv3 traps only.) If you plan to receive SNMPv3 traps from the network, you must edit a seed file as explained in “Editing seed files” on page 96in order to load SNMPv3 agent credentials.

  3. (Optional: for SNMPv3 traps only. ) Copy this seed file to the BASEDIR/smarts/conf/trapd path in the product suite (IP or SAM) where the trap exploder is running. For example, to start the trap exploder from the Service Assurance Manager: 

    tIncharge/SAM/smarts/bin>sm_trapd --port=162 --rules=default --name=TRAP_EXPLODER --seed=seedfiles

  4. You may wish to start the trap exploder as a service. Use the sm_service command to manually register this adapter as a service and ensure the name is unique. (This name must differ from the service name (ic-trapd-receiver) used in Scenario 1). For example: 

    /InCharge/SAM/smarts/bin/sm_service install --force --unmanaged
--startmode=runonce 
--description="VMware 
					VMwareSNMP Trap Exploder Server"
--name=trap_exp
 /InCharge/SAM/smarts/bin/sm_trapd                                                 
    --name=TRAP_EXPLODER 
    --config=trapd 
    --port=162
    --sport=9180
    --seed=seedfile
    --rules=default 
    --output