Skip to main content

Installing SNMP Trapd v2


The existing -s install currently uses the MoogTrapdLamV1 files - these will be replaced with the v2 files in a future release. If commissioning a LAM server, download and use the file from and untar in the Moogsoft home directory.

To install the SNMP Trapd V2 bundle:

  1. Download the TrapdLamV2 bundle from the following location

    This requires your credentials to Moogsoft Support and can be performed with a cURL command similar to the following:

    curl https://${SPEEDY_USER}:${SPEEDY_PASSWORD} --output Moogsoft-TrapLamV2.tar.gz
  2. Create a “staging” directory (for example, /tmp/traplamv2), copy and un-tar the traplamv2 files into the staging directory.

    mkdir /tmp/trapdlamv2
    cp Moogsoft-TrapLamV2.tar.gz /tmp/trapdlamv2
    cd /tmp/trapdlamv2
    tar -zxvf Moogsoft-TrapLamV2.tar.gz
  3. Create a backup of the existing include files, LAMbot and config (and mib2lam if preferred):


    Your config file (moog_trapd_lam.conf) and LAMbot (MoogTrapdLam.js) may have local file names. Use these instead of the defaults.

    tar -cvzf $MOOGSOFT_HOME/traplamv2_includes.tar.gz -C $MOOGSOFT_HOME bots/lambots/trapModules bots/lambots/MoogTrapdLam.js config/moog_trapd_lam.conf mib2lam 
  4. Copy any locally modified include files from their current location in $MOOGSOFT_HOME/bots/lambots/trapModules to the corresponding path in the staging directory.

    For example, if a custom include was created for “VendorX” and placed in $MOOGSOFT_HOME/bots/lambots/trapModules/vendorx , then the “vendorx” directory and contents would need to be copied to /tmp/trapdlamv2/bots/lambots/trapModules.

    If you are uncertain of the local include files you may have, then using diff may help:

    diff -qr $MOOGSOFT_HOME/bots/lambots/trapModules /tmp/trapdlamv2/bots/lambots/trapModules | sort

    Look for entries like this, which indicate a difference between the new and existing files.

    Files /usr/share/moogsoft/bots/lambots/trapModules/cisco/CiscoEntityExtTraps.include and /tmp/trapdlamv2/bots/lambots/trapModules/cisco/CiscoEntityExtTraps.include differ


    Some of the base GA files were updated, so ignore files that you do not use, or have not modified. Only the files that you have modified need to be copied across.

    And entries like this that show an existing include file that does not exist in the traplamv2 base set.

    Only in /usr/share/moogsoft/bots/lambots/trapModules/<directory> : <filename.include>

    Files referenced in the above entries need to be copied into the trapdlamv2 include set.

  5. Modify the /tmp/trapdlamv2/bots/lambots/trapModules/master.includes to reference any files you may have copied over in step 4. Follow the instructions in the “Including TrapdLamV1 includes in TrapdLamV2” section, below.

  6. Copy the staging files to the correct directories and locations.

    mv $MOOGSOFT_HOME/bots/lambots/trapModules $MOOGSOFT_HOME/bots/lambots/trapModules.v1
    cp -r /tmp/trapdlamv2/bots/lambots $MOOGSOFT_HOME/bots
    cp /tmp/trapdlamv2/contrib/*.js $MOOGSOFT_HOME/contrib
    cp /tmp/trapdlamv2/config/*.conf $MOOGSOFT_HOME/config
    cp -r /tmp/trapdlamv2/mib2lam $MOOGSOFT_HOME
  7. Add any local v1 MoogTrapdLam.js LAMbot modification to the appropriate place in the new MoogTrapdLamV2.js LAMbot. The file contains the following section, and any custom code should be placed there:

    // ------------------------------------------------------------------------------------
      // If customer specific processing is needed, e.g. adding static lookup, add it here.
      // ------------------------------------------------------------------------------------
      // Custom code start: 
      // ------------------------------------------------------------------------------------
      // ------------------------------------------------------------------------------------
      // Custom code end. 
      // ------------------------------------------------------------------------------------  
  8. Modify the /etc/init.d/trapdlam service file to reference the new config file (moog_trapd_lamv2.conf) or alternatively rename the moog_trapd_lamv2.conf file to match your existing configuration file.

  9. If you have made modifications to the LAMbot (MoogTrapdLamV2.js), ensure that it is named appropriately (for example, MoogTrapdLamV2.CUSTOMER.js) and ensure the configuration file is referencing this modified LAMbot and not the default:

    For example, in moog_trapd_lamv2.conf, modify the filter section to point to the modified LAMbot.

                # Specify the default stream this LAM will send events to.
                # If this configuration is not specified then the generic 
                # stream "events" is used, i.e. no specific stream.
                # stream: "myStream",
    			presend: "MoogTrapdLamV2.CUSTOMER.js",
    			modules : []


    If changing the config file, it is strongly recommended to make this customer specific, such as: moog_trapd_lamv2.CUSTOMER.conf, and modify the appropriate /etc/init.d service file accordingly.

  10. Ensure your config file is configured to use the correct precompiled mib file and SNMPv2 usm file if these are being used.

  11. Stop the existing trapdlam, and start the traplam up in debug, logging to the console.

    service trapdlam stop
    trapd_lam --config moog_trapd_lam.TEST.conf --logconsole --loglevel debug

    Look for the line:

    WARN : [main][20220207 11:00:28.105 +0000] [] +|[MoogTrapdLamV2.js]: TrapUtility::loadAllModules: Loaded 471 include files, there were 0 failures.|+

    If there are any loading failures, then some include files have failed to load. Resolve these issues before continuing.

  12. If you rely on trapDebug data as part of filtering, workflows or recipes (custom_info.trapDebug, custom_info.trapDebug.trapInfo, custom_info.trapDebug.trapData) this is on by default in the TrapdLamV2. If you do not use this data, then disable this in the lambot by commenting out the following line:


    Leaving trap debug enabled can result in large event sizes and should be disabled if it is not actively used. If an unknown trap is received, it will always pass through with its full debug payload, allowing an operator to see the trap details.

  13. Restart the trapdlam with the new config file, LAMbot, and include files.

    service trapdlam start