Share This:

If you have ever wondered whether the TrueSight SNMP Event adapter can handle multiple SNMP trap versions, then wonder no more. TrueSight SNMP Event Adapter can manage v1, v2, and v3 traps, all it takes is some extra configuration. The SNMP Event Adapter is a part of the Event Adapters service (mcxa) and can handle multiple versions of traps. SNMP v1 and SNMP v2 are enabled by default, but enabling SNMP v3 can allows you to handle all three.


These steps presume you have already configured your environment for working with MIB files and SNMP traps. You would need to be sure you have compiled the MIB files to be used to provide the SNMP v3 traps.


If you have not installed the SNMP Event Adapter, please see the details below for installation details:

You must meet the Event Adapter requirements before configuring the SNMP Event adapter. There are specific requirements for Windows and Solaris/Linux specifically regarding PERL which is need before the traps can be processed.


TrueSight 11.0 Event Adapter Requirements

TrueSight 10.7 Event Adapter Requirements

TrueSight 10.5 Event Adapter Requirements

BMC Event Adapter requirements for Microsoft Windows




Intel-compatible processor (32 bit and 64 bit)

Supported operating systems

  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008 and 2008, R2 (32 bit and 64 bit)
  • Microsoft Windows Vista, SP1 (Impact Explorer and upgrades only)
  • Microsoft Windows XP Professional, SP2 (32 bit and 64 bit)
  • Microsoft Windows Server 2003, SP1 and SP2 (Standard and Enterprise Editions) (32 bit and 64 bit)

BMC Event Adapter requirements for Solaris

  • Sun Solaris 10 (64 bit)
  • Sun Solaris 10 zones (64-bit)
  • Sun Solaris 9
  • Red Hat Enterprise Linux Enterprise Server 6.2 (64 bit)
  • SUSE Linux Enterprise Server 11 SP2 and SP3

BMC Event Adapter requirements for AIX and HP-UX

  • HP-UX 11.23

Perl requirements for BMC Event Adapter

  • Module-Build-0.3607
  • ExtUtils-CBuilder-0.2703
  • Test-Exception-0.29
  • Sub-Uplevel-0.22


On Linux and Solaris systems, you must install the P5NCI library for the SNMPv3 adapter to work. You do not need to install the library on Microsoft Windows systems.


For certain libraries in the SNMPv3 adapter to work, Perl 5.14 must be installed. If you are using the SNMPv3 adapter, ensure that Perl 5.14 is installed. On Linux and Solaris systems,

the SNMPv3 adapter requires the P5NCI package installed on the system in which the SNMPv3 adapter is configured and the P5NCI package is supported in Perl 5.14. As a best practice, configure the SNMP v3 adapter on the remote cell (which is not a part of the BMC TrueSight Infrastructure Management Server) with preinstalled Perl 5.14 and the P5NCI package. By default, the BMC TrueSight Infrastructure Management Server contains Perl 5.16 and the P5NCI package is not available.



TrueSight 11.0 Verifying the SNMP Event Adapter Installation

TrueSight 10.7 Verifying the SNMP Event Adapter Installation

TrueSight 10. 5 Verifying the SNMP Event Adapter Installation




To verify the SNMP event adapter installation

  1. Verify that the files created by the SNMP Adapter Configuration Manager or the MIB2MAPcommand line interface are in the following locations:
    • installationDirectory/pw/server\etc\mcsnmptrapd.dat
    • installationDirectory/pw/server\etc\
    • installationDirectory/pw/server\etc\<cellname>\kb\classes\mcsnmptrapdmibe.baroc
    • installationDirectory/pw/server\etc\<cellname>\kb\classes\ mcsnmptrapdmib.baroc
  2. Verify that the installationDirectory/pw/server\etc\<cell>\kb\classes\.load file has the SNMP BAROC files listed in the correct order to load mcsnmptrapdmibe before mcsnmptrapdmib.
    • mcsnmptrapdmibe
    • mcsnmptrapdmib
  3. Verify the cell KB has been recompiled and the cell restarted after the SNMP files were created and moved to the correct locations.


  4. Verify that the SNMP adapters are not disabled in the mcxa.conf file.


    For example, to enable the adapter, remove DISABLE from the disabled adapter (see the code below) and restart the SNMP Event Adapter.


              Snmp DISABLE


               Engine = MA::ESnmpTrap

               ServerName = pncell_8PFNZK1 (more details below)

  5. Check whether installationDirectory/pw/server\etc\mcell.dir has an entry for all the cells referred to in the mcxa.conf file.

    6. For the SNMPv3 trap adapter, ensure snmptrapd.conf has been configured to include the users sending the SNMPv3 traps.

               For example, createUser -e 0x8000000001020304 traptest SHA mypassword DES mypassword authuser log traptest noAuth (more details below)



SNMP MIB files must be published for the adapter before the SNMP Adapter receives the SNMP traps. This is handled by the SNMP Adapter Configuration Manager or the mib2map command line interface.


When the SNMP trap is received, the SNMP Adapter tries match the OID of the trap to the class defined in and populates slots based on that definition.





Users will need to install the net-snmp utilities to work with the traps as well as specific Perl versions.

You can find the tools here –





A quick guide (after ensuring that prerequisite perl version and modules are installed see the requirements links above):


1) Install net-snmp utilities (to have the cli for testing below)

2) Enable the SnmpV3 adapter in mcxa.conf

3) Add the following line to the pw/server/etc/snmptrapd.conf (this is just a test entry):

createUser -e 0x0102030405 myuser MD5 mypassword DES myotherpassword

Optionally, also add:

authUser log,net myuser noauth

4) Start the adapter

5) In the net-snmp utilities bin directory, run:

snmptrap -e 0x0102030405 -v 3 -u myuser -a MD5 -A mypassword -l authNoPriv coldStart.0

(just modifying the IP Address appropriately to point to where this adapter is installed).  So, we are trying with an extremely basic noauth snmp trap setup. This sample trap and snmptrapd.conf setup is taken from the net-snmp tutorial at

6) Check that it is received (be sure to modify the settings for filtering in the ops console, so that you can see OK events).

Is that crystal clear? I didnt  think so.. as it can get pretty tricky. So let's review it in more detail and with some examples:


Enabling SNMP v3



To enable SNMP version 3 support, you must edit the configuration file to create a user and tie that user to the engine ID sending traps. You must also grant authorization to the user.


1) In the snmptrapd.conf file, located in the MCELL_HOME\etc directory ((\\Program Files\BMC Software\TrueSight\pw\server\etc\), create the following line:

createUser -e ENGINEID myuser authenticationType "my authentication pass" encryptionType "my encryption pass"


2) Save the file.




Granting user authorization

1) In the snmptrapd.conf file, located in the MCELL_HOME\etc directory, create the following line:

authUser log,net myuser


Note: If you want to receive version 3 traps sent with noAuthNoPriv, you'll need to add noauth to the authUser line. For example:

authUser log,net myuser noauth

2) Save the file.


Here is an example of MCELL_HOME/etc/snmptrapd.conf

#createUser -e 0x8000000001020304 netadmin SHA 0x78d611ccc8c0b19a1d782891ce2aaba8b7f2c5fc AES 0x78d611ccc8c0b19a1d782891ce2aaba8

#authuser log netadmin


You must also set the correct SNMP trap adapter settings in the mcxa.conf file. The SNMP trap and SNMPv3 trap adapters are configured in installationDirectory/pw/server/etc/mcxa.conf. When you open the mcxa.conf file, if you want to run v1, v2, and v3 traps, then you will need to disable the settings for SNMP and enable the settings for SNMP v3


So the file will have the following details set if you want to process SNMP v1, v2, v3 traps:


# [Snmp] DISABLE
# Engine  = MA::ESnmpTrap
# --Modify the following value(s) according to your environment--
# Replace by the actual destination cell (if different from the global)
ServerName = smoke



Engine  = MA::ESnmpTrapV3
# --Modify the following value(s) according to your environment--
# Replace by the actual destination cell (if different from the global)

ServerName = clm-aus-123456
SnmpTrapdConf = snmptrapd.conf
SnmpPort = 162
MapFile =
SnmpTraceLevel = 7
SnmpTraceFileCount = 10
SnmpTraceFileSize = 1000000

It is important to disable the SNMP setting and enable the SNMPv3 settings. By default, the file will have the SNMP settings enabled and the SNMPV3 settings disabled, so for our case of wanting to process all three, we must switch the settings.

Once you have setup the mcxa.conf file and the snmptrapd.conf and restarted the adapter, you can send a test trap to see if it gets processed. Send a test trap using the "traptest" user based on your configuration (SNMPv3 is running on the default port 162)

snmptrap -v 3 -n "" -u traptest -e 0x8000000001020304 localhost 0 linkUp.0
snmptrap -v 3 -a SHA -A password -e 0x8000000001020304 -u traptest -x DES -X password localhost 0
snmptrap -v 3 -n "" -a SHA -A password -x DES -X password -u traptest -e 0x8000000001020304 localhost 0 linkUp.0


If the trap goes through properly, you will be able to see the details in the mcxa.trace file where it will report the details in messages similar to the following:

20180104 00:49:28 MC::Poster:359 Vrbse - ...Event sent to $VAR1 = [
'mytestserver-bmc-123456'        ];
20180104 00:49:28 MA::Engine:580 Vrbse - MA::Engine::Send
20180104 00:49:28 MA::Engine:618 Vrbse - MA::Engine::SetDefaultSlots
20180104 00:49:28 MA::Engine:539 Vrbse - MA::Engine::_Send
20180104 00:49:28 MC::Poster:298 Vrbse - MC::Poster::Send
20180104 00:49:28 MC::Poster:330 Vrbse - Sending to $VAR1 = [
adapter_host    = ‘mytestserver-bmc-123456’;
mc_arrival_time = 1515026968;
mc_host         = ‘mytestserver-bmc-123456’;
mc_host_address = "fe80::f148:438f:4083:e2af%15";
mc_object       = mcxa;
mc_object_class = MA::EngineMgr;
mc_origin       = mcxa;
mc_origin_class = MA::EngineMgr;
mc_tool         = mcxa;
mc_tool_class   = MA::EngineMgr;
msg             = "BMC Impact Event Adapter stopped";
20180104 00:49:28 MC::Poster:359 Vrbse - ...Event sent to $VAR1 = [
20180104 00:49:28 MA::EngineMgr:169 Minor - EngineMgr CLASS termination finished
20180104 00:49:28 MA::EngineMgr:288 Vrbse - EngineManager destructor already running (2)
20180104 00:49:28 MA::Core::TimerQ:184 Vrbse - Destroying TimerQ : MA::Core::TimerQ=HASH(0x1918a2c)
20180104 00:49:28 MA::Core::Timers:366 Vrbse - Cancelling timer StopCheck_Timer
20180104 00:49:28 MA::Core::Timers:226 Vrbse - Destruction done
20180104 00:49:28 MC::Poster:135 Vrbse - MC::Poster destruction
20180104 00:49:28 MC::Poster:140 Norml - Terminating msend (cell(s): ‘mytestserver-bmc-123456’)
20180104 00:49:28 MC::Poster:157 Vrbse - Stopping msend: "C:/Program Files/BMC Software/BPPMAgent/Agent/server/bin/msend.exe" -n ‘mytestserver-bmc-123456’ -j "C:/Program Files/BMC Software/BPPMAgent/Agent/server/log/adapters/perl/’mytestserver-bmc-123456’" -k
20180104 00:49:29 MA::Core::Timers:366 Vrbse - Cancelling timer Reconfiguration_Timer
20180104 00:49:29 MA::Core::Timers:226 Vrbse - Destruction done


Success.. you are now able to process SNMP version 3 traps!



Quick SNMP v3 Trap Configuration Q&A


Q: I have a mix of v1 & v2 so the question is can v1, v2 and v3 co-exist together or do I need to do some magic to make it happen?

A: Yes, 1,2, and v3 can co-exist.  You have to enable the SnmpV3 adapter in the mcxa.conf file , and disable the Snmp adapter if not already disabled. The two settings cannot exist together.

Q: Would each tool that sends SNMP v3 traps require a different createuser/authuser line in the snmptrapd.conf file?
A: Only if each tool is using different EngineID , user..etc.  Otherwise if same, just the one entry.


Q: In the snmptrapd.conf file, it shows this line for the authuser: authUser log,net myuser (I’m assuming “myuser” is user)

A: Correct, is the username in your environment. From the snmp trap source.

Q: Also in the snmptrapd.conf file this line authuser log netadmin (I’m assuming “netadmin” is user)  Is the “, net” required or not?

A: Correct, netadmin is a username example. No, net is not required.

Q: So you add the createuser statements and save the file. Then you go back in and add authuser. (Do you comment out createuser at that time?) Does anything need to be recycled for createuser and/or authuser to take effect.

A: Yes, you add the createUser entry, you can also add the authuser at the same time.  You can comment out any entry not being used.Yes, you need to restart the BMC Event Adapter.

Q: When you’re done, it should look like this ?????

#createUser -e 0x8000000001020304 <UserName> SHA 0x78d611ccc8c0b19a1d782891ce2aaba8b7f2c5fc AES 0x78d611ccc8c0b19a1d782891ce2aaba8

authuser log <UserName>

A: Yes,it could look like that if that is the password/phrase being used. 
Here is an example:

createUser -e 0x8000A12F04c341ee29c55f41e689b8b5edf32aefb2 patrol SHA patrolsnmp AES patrolsnmp

authuser log patrol

You can also use noAuthNoPriv

    noAuthNoPriv - This security level simply means that there is no authentication password exchanged and the communications between the agent and the server are not encrypted. The SNMP requests are authorized based on a simple username string match.

Q: Can I use the 64-bit version of Perl?

A: No, you cannot, we only support the 32-bit version of Perl



After reviewing past cases for this topic, I have seen that there are a few  areas which seem to snag us up when configuring the version 3 traps.


  • Perl version -  To use the SNMP v3 Adapter, you must install Perl 5.14 (32-bit), 5.16 (32-bit) with additional modules. It must be a 32 bit version even if running on a 64 bit system. We recommend using the versions above, they are older, but they are tested. You should be able to use a newer 32 bit version of Perl though, so you can attempt to do so.
  • The Perl library is missing for the Perl version for UNIX/Linux/Solaris users,  so please install Perl again from the link below
  • The mcxa.conf file edit to disable SNMP and enable SNMP v3 – many times, both versions are enabled, but that will not work and results in an event with the message "Couldn’t be an UDP server on port 162". You must use either SNMP or SNMPv3 they cannot both be configured. If you want SNMP v3 that’s the one to enable as it can handle v1, v2, and v3. Remember to restart the event adapter after any changes to the mcxa.conf file.




There are other environment specific issues so if you do encounter any, please collect the troubleshooting details below and send them to Support via a Case for further assistance.


Troubleshooting the SNMP v3 adapter


There is additional trace to be enabled to help debug the SNMP v3 adapter issues, this is a special trace for SNMP v3 traps.

Enabling Trace for SNMP Event Adapter in TrueSight 11.0

Enabling Trace for SNMP Event Adapter in TrueSight 10.7

Enabling Trace for SNMP Event Adapter in TrueSight 10.5


1. In the mcxa.conf file uncomment and set the details below .

Trace = Yes
TraceLevel = 7
ServerName = LOR_test
SnmpTraceLevel = 7
SnmpTraceFileCount = 10
SnmpTraceFileSize =  1000000

Note: You may not find the Trace parameter in the mcxa.conf file but TraceLevel should be set to 7 for SNMP v3 adapter.


2. Follow the steps below to clear the buffer and the log files and restart the adapter


a. Stop the BMC Event Adapter

b. Kill msend*.exe and perl.exe process from taskmanager (if any)

c. Backup and Delete buffer files i.e persist.dat from $mcell_home\log\adapters\perl\<cell_name>

d. Delete mcxa.traces from $mcell_home\tmp\adapters

e. Restart the adapter


Now try sending few traps manually with snmptrapgen.exe or snmptrap.exe utility and see if trap is received on event adapter, if issue still persist then kindly collect the details below to send to Support.


1. Screenshot of command executed to send SNMP v3 traps.

2. All instances of mcxa.trace and ESNMP*.log files from $MCELL_HOME\tmp\adapters directory

3. The mcxa.conf and the snmptrapd.conf file from $MCELL_HOME\etc\ directory

4. The following directories <MCELL_HOME>\etc,   <MCELL_HOME>\lib\perl, <MCELL_HOME>\tmp\adapters, <MCELL_HOME>\log

5. Output of the commands below:

a. pw viewhistory > TSVersion.txt

b. Perl.exe -v > PerlVersion.txt

c. mcxa – z

d. mcxa – z

e. mcell - z

Video Highlight - Converting mibs with mib2map




Want more Videos????? -  How-To Videos for TrueSight





The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case, and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.


To get started, please review the details here:


Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.






New Knowledge Added over the last month:


000151061 For firewall purposes, does the TrueSight 11.0 port between the pncell and the ISN need to be bi-directional?

000150434 BPPM email for self-monitoring disk full email alerts is being sent from an invalid email address

000150384 Is there an integration between TrueSight Infrastructure Management and Entuity Network Monitoring

000150289 Launching TSPS shows "An error occurred please contact your administrator or try again later"

000150516 Devices are not visible for selection during the creation of a TSPS 11.0 Dashboard using group level permissions rather than device level permission

000149757 Is it possible to create authorization profiles for TrueSight using the command line?

000151026 TrueSight ReportEngine Performance Issues While Refreshing the Reports

000150972 Cannot reset baseline when logged in as the Admin User

000150589 Users getting Grey screen while trying to access BPPM Operations Console

000150017 Show Graph in TSIM is showing a broken link icon instead of data



Looking for a previous blog posting? Find it here: BMC TrueSight Pulse Blogs



  Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!