Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM: How to configure a Trap Receiver to Process Snmp v3 Traps (336084)

Last Updated: 12/8/2020Categories: TroubleshootingTotal Views: 3405Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The current documentation to create a seedfile for the Smarts Trap Adapter, for use with snmp v3 traps does not specify the fact that each seedfile entry must be on a single line.

If you use the seedfile created from the IP domain as documented this seedfile works without issue.  However example in the document attached here in this KB article and also provided in the current Smarts Portfolios indicates multi-line entries, and this causes the trap adapter not to process the seedfile properly.

Purpose

How to setup a trap receiver for accepting snmp V3 traps when creating a new seedfile manually for use specifically for the Smarts Trap Adapter.

Cause

SNMP v3 requires authentication and to process traps sent with snmp v3 require additional steps to process traps.  The document shows a multi-line entry in the seedfile in the example for readability, however the trap adapter requires each seedfile entry to be on a single line to avoid parsing the seedfile incorrectly

Resolution

These are the steps to use when setting up the trap exploder and adapter to receive and process SNMP v3 traps.

Step 1.  Check seedfile in <SAMBase>/smarts/conf/icoi and add the example from the user guide and encrypted via sm_edit:
(IP Address)
SNMPVERSION=V3
USER=incharge
AUTHPROTOCOL=SHA
AUTHPASS=
PRIVPROTOCOL=AES
PRIVPASS=
ENGINEID=

Please note:  the format of the seed file must have a host IP, or Name and and the information above as needed on a single line,

Opening the seed file with sm_edit, the seed file should look like this example before saving, after saving the AUTHPASS and the PRIVPASS will be encrypted as a function of the first line in the seed file that is required for encryption.

#<encrypted seed>:1.0:AUTHPASS,PRIVPASS
172.155.100.148 USER=CISCO16 SNMPVERSION=V3 AUTHPROTOCOL=SHA AUTHPASS=ovb+14u PRIVPROTOCOL=DES PRIVPASS=cisco200k ENGINEID=0000A3D10864C000386DED7F
172.155.101.134 SER=CISCO10 SNMPVERSION=V3 AUTHPROTOCOL=SHA AUTHPASS=ovb+24u PRIVPROTOCOL=DES PRIVPASS=cisco201k ENGINEID=0000A3D10864C000386DAAAF

Please note, you cannot use the "=" in the password field, currently testing what special characters are allow in the password field,
Also, the seedfile uses the colon ' : " as a a delimiter for specifying multiple host IP/ host names, so this should not be in your password field as well.

Step 2. Create a trap definition base and enable DEBUG and LOGGING (for confirmation) in trap_mgr.conf::
BEGIN_TRAP .1.3.6.1.4.1.41263.1 6 1
EventName: TestTrap
ClassName: Host
InstanceName: $SYS$
SysNameOrAddr: $SYS$
Expiration: 60
State: NOTIFY
UnknownAgent: CREATE
EventType: MOMENTARY
ClearOnAcknowledge: TRUE
LogFile: TestTrap.log
EventText: $V1$, $V2$, $V3$
END_TRAP

Step 3. Adjust the /conf/trapd/trapd.conf file to forward traps to trap adapter
FORWARD: * .1.3.6.1.4.1.41263.* * * -nosmtrapaddr localhost:9101

Optional - (Force seed file to be loaded)
Step 4. Start OI and Trap Receiver/Exploder and subscribe SAM to OI
./sm_trapd --name=TRAP94-REC --server= OI94 --config=icoi --port=9101 --model=sm_actions --daemon
--output=TRAP-REC.log --rules=icoi-trapd/trap_mgr_parse.asl --seed=seedfile
./sm_trapd --name=TRAP94-EXP --config=trapd --port=1602 --rules=default --output=TM-TRAP-EXP.log --daemon
--loglevel=Critical --loglevel=Alert --seed=seedfile

Step 5. Import the seedfile into the Local Credentials Database:
./sm_adapter -s TRAP94-EXP -D seed=seedfile trapd/importSeedFile.asl
./sm_adapter -s TRAP94-REC -D seed=seedfile trapd/importSeedFile.asl

Step 6. Send test trap:
sm_snmp -d (TE IP address) -p 1602 -s 3 -u incharge -e 1234567890ABCDEF -E 1234567890ABCDEF -a SHA -b
AES -x (authpass password) -y (privpass password) trap (IP address of source device as in step 1)
.1.3.6.1.4.1.41263.1 6 1 0 .1.3.6.1.4.1.41263.1.1.1 s
"Varbind_1" .1.3.6.1.4.1.41263.1.1.2 s "Varbind_2" .1.3.6.1.4.1.41263.1.1.3 s "Varbind_3"

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

SAM Patform adapter guide.pdf

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant