Trap adapter not processing or receiving some traps in Smarts or the formats are incorrect from Varbind
search cancel

Trap adapter not processing or receiving some traps in Smarts or the formats are incorrect from Varbind

book

Article ID: 303871

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:




Traps received by Trap Exploder containing varbinds are not properly formatted.
After applying a SmartPack or Rolling Patch for SAM, I'm not receiving any traps from my Trap Adapter

Unable to process multiple varbind traps when generated by sm_snmp in Smarts

Trap adapter not processing or receiving some traps in Smarts
 
When generating traps with the below command, sm_trapd trap receiver will not process traps that contains any varbind.
 
./sm_snmp -d <trap receiver> -p <SNMP port> trap <IP address of device sending trap>
 
./sm_snmp -d 128.222.217.38 -p 162 trap 10.9.1.1 .1.3.6.1.4.1.9.1.17 1 0 0 .1.3.6.1.6.3.3.2.1.1.1.11.1.3.6.1.4.1.9.11.1.1.5 i 300


Environment

VMware Smart Assurance - SMARTS

Cause

This is most likely due to a fix that was included in 6.2 SP3 RP12 and 6.5 SP1 RP38 (and subsequent RP's and SP's) which requires that the --ascii flag be removed from the service starup command for the Trap Adapter.

Resolution

As of 6.5 SmartPack 2 and beyond, "--ascii" should no longer be used during service install or manuall startup for sm_trapd.   Resolution is to manually re-install the service for the SNMP trap adapter without the --ascii option.  Use the sm_service install command with the --force option to overwrite the existing service and do not specify the --ascii parameter in it.
Example:
/opt/InCharge6/SAM/smarts/bin/sm_service install --force
--startmode=runonce
--description="SMARTS SNMP Trap Adapter" ic-trapd-receiver
/opt/InCharge6/SAM/smarts/bin/sm_trapd
--name=TRAP-INCHARGE-OI
--server=INCHARGE-OI
--config=icoi
--port=162
--model=sm_actions
--output
--rules=icoi-trapd/trap_mgr_parse.asl