Create LAMbots from MIBs (DEPRECATED)

Add any required MIBs to the existing base set in the MIBs directory.

Run the Mibparser utility to create a JSON file of parsed MIBs, for example:

./mibparser -c unparsed_mibs.json -i <MIBS_directory_filepath>

Run the Mib2lam utility, defining the path of the parsed MIBS and your filename with configuration options. For example:

./mib2lam --config /filepath/mib2lam.conf --mibfile
<MIBS_directory_filepath>/parsed_mibs.json --oid <oid_starting_point> --module <module> --class <class>

Specify the configuration file using the -c or --config argument and define the JSON file that Mibparser creates using –mibfile. See Mib2lam Command Reference for all available arguments.Mib2lam Command Reference

If there are any conflicts such as duplicate MIBs, OIDs or duplicate names, remove or rename the duplicates before parsing the MIBs again and running the Mib2lam utility once more. If there are no issues, a new module is created.

Create a directory under $MOOGSOFT_HOME/bots/lambots/trapModules and move the module into it. If necessary, merge the module into any existing generic modules, transferring over any enumerations and trap-specific functions.

Add the module to the MoogTrapdLam.js LAMbot file contained in the Mib2lam .zip file and add lines the following to the global section:

LamBot.loadModule("trapModules/generic/test.include");
      var generic = new test(botUtil);

Alternatively, add the following line to the 'modules' section of moog_trapd_lam.confcontained in Mib2lam:

"trapModules/generic/test.include"

Also, add the following line to the top of the Trap LAMbot file:

var generic = new test(botUtil);

Add routing to allow generic traps to be sent to this module. By default, non-enterprise traps are defined and routed as follows:

var genericTraps=new GenericTraps(botUtil);
    ...
    case "generictrap"  :   genericTraps.processTrap(moogEvent,trapData,trapInfo); break;