Page History

Installation Steps

• Download opTrend from the Opmantek website.
  Copy the opTrend tarball to the server in question, using scp or sftp or similar. Make a record of where you put the tarball (likely root's home directory).

• Become root and unpack the tarball:

  Code Block
  # asbecome root cd /usr/localsudo sh # if the tarball was saved in a different location, adjust the ~ in the following command cd /tmp tar xzf ~/opTrend-Linux-x86_64-1.04.0.tgz

• Start the interactive installer and follow its instructions:

  Code Block

  sudo sh cd opTrend-1.4.0 ./installer ++++++++++++++++++++++++++++++++++++++++++++++++++++++ opTrend (1.4.0) Installation script ++++++++++++++++++++++++++++++++++++++++++++++++++++++ This installer will install opTrend into /usr/local/omk. To select a different installation location please rerun the cp install/opCommon.nmis conf/ cp -r install/trend conf cp install/users.dat conf/installer with the -t option. ...

• The installer will interactively guide you through the steps of installing opTrend. Please make sure to read the on-screen prompts carefully.
• When the installer finishes, opTrend is installed opTrend is now unpacked into /usr/local/omk, and the default configuration files are in /usr/local/omk/conf, ready for your initial config adjustments.

  Integrate opTrend with the web server
  become root and run the following commands:

  Code Block# as root # non-debian: cp
• A detailed log of the installation process is saved as /usr/local/omk/conf/04omk-proxy.conf /etc/httpd/conf.d/ apachectl restart # debian/ubuntu: cp /usr/local/omk/conf/04omk-proxy.conf /etc/apache2/conf.d/ /etc/init.d/apache2 restart

  Note: If this step is not taken, then the opTrend web GUI will only be available on port 8042 and you'll need to adjust your web browser accordingly.

  Adjust NMIS Access list to include opTrend 

  Code Blockcd install.log, and subsequent upgrades or installations of other Opmantek products will add to that logfile.

• For detailed information about the interactive installer please check the Opmantek Installer page.

Post Installation Steps

1. The opTrend installer will create cron entries to keep the opTrend database up-to-date but an initial "update" is required to prime the database for the current week. Run the following command to do this: 

   Code Block
   /usr/local/omk/

Make the opTrend service daemons start automatically with the system
become root, then run the  following commands:

1. bin/optrend.pl

1. act=update

2. The wiredTiger storageEngine is suggested for opTrend to improve performance.

3. The opTrend installer will attempt to "cap" the "seds" collection to limit the database size somewhat (asking first).  This only happens if the wiredTiger storageEngine setting is set because not all versions of Mongo support collection updates that opTrend requires.  The "seds_ev" and "ev_billboard" collections are not capped.  Capping can be done post-install by running optrend.pl act=setup-db

4. History can be created if your NMIS installation has the data, to do this run the updates for the weeks you have.  I suggest doing this oldest to newest so that the Billboard information can be calculated correctly: 

   Code Block

1. /usr/local/omk/

service omkd start 

Setup the cron jobs to run data collections, create a file /etc/cron.d/optrend

1. bin/optrend.pl act=update date="4 weeks ago" force_end_of_week=1 force=1 /usr/local/omk/bin/optrend.pl act=update date="3 weeks ago" force_end_of_week=1 force=1 /usr/local/omk/bin/optrend.

1. pl act=

1. update date="2 weeks ago" force_end_of_week=1 force=1 /usr/local/omk/bin/optrend.

1. pl act=update

1. date="1 week ago" force_end_of_week=1 force=1

Post Installation Upgrade Steps

1. New datasets have been introduced that the GUI will not show unless the config is updated, update opConfig.nmis with this setting:

   Code Block
   'optrend_topn_sections' => [ {"Node Health" => [{ 'cpuLoad' =>'cpu' }, { 'MemoryUtil' =>'memory' },{ 'tcpCurrEstab' => 'tcp'},{'hrSystemProcesses' => 'processes'} ]}, {'Interface Trend' => [{ 'ifInUtil' =>'interface' }, { 'ifOutUtil' =>'interface' },{ 'ifInErrors' =>'packets' },{ 'ifOutErrors' =>'packets' },{ 'ifInDiscards' =>'packets' },{ 'ifOutDiscards' =>'packets' }]}],

2. You may also want to set the control settings to: 'optrend_exceptions_to_make_condition' => 3,