You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

How to get opConfig operating for the first time once you have the Opmantek VM operating or once you have the opConfig software and mongoDB installed on your own OS. 

Prerequisites

  • Root access is available.
  • NMIS, opConfig sofrware and MongoDB must already be installed and integrated (which they are on the Opmantek VM)
  • You will need a license for opConfig (evaluation licenses are available here).


  1. Access the opConfig GUI and enter your license.

  • The opConfig GUI is accessible at http://<yourservername or ip address>/omk/opConfig/,  or via the NMIS Modules dropdown.  Paste the valid license text string into the box and then read and accept the End User Licence Agreement,

    neither the opConfig GUI nor the CLI tools will operate until the license is added and End User Licence Agreement is accepeted.

  • Setup Cron to perform the desired opConfig data collection periodically.  

    Here is the default cron snippet we recommend, save this as a text file in  /etc/cron.d/opConfig:

     

    # opConfig: hourly command set running
    1 * * * *   root    /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=run_command_sets tags=HOURLY
    # and the daily ones
    7 7 * * * * root    /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=run_command_sets tags=DAILY
    # and a daily import from open-audit enterprise
    21 4 * * * root     /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=import_audit
    # and a daily purge of old revisions
    40 3 * * *     root /usr/local/omk/bin/opconfig-cli.pl act=purge_revisions quiet=1

    To save this you can either copy

  •  

Configuration and Use

At this point opConfig should be ready for operation, but won't have any knowledge of which nodes to manage.

  • No labels