Page History

...

sudo service nmis9d stop
sudo service omkd stop
sudo service opeventsd stop
sudo service opchartsd stop
sudo service opconfigd stop

Step 2. Move and adapt NMIS

...

files

Configuration Files

Copy

Copy the configuration directory from the source server.

...

rsync -r root@uburnto.opmantek.net:/usr/local/nmis8/conf /usr/local/nmis9/conf

Configure

We need to make some adjustments to the file. This is:

...

  'database' => {
    'db_name' => 'nmisng',
    'db_password' => 'op42flow42',
    'db_port' => '27017',
    'db_query_timeout' => 5000,
    'db_server' => 'localhost',
    'db_username' => 'opUserRW',
    'db_never_remove_indices' => [ 'nodes' ],
  },
...
 '<nmis_base>' => '/usr/local/nmis9',
 '<url_base>' => '/nmis9',
 '<cgi_url_base>' => '/cgi-nmis9',

• Review important parameters, as the number of workers (workers parameter in config). We can use this rule to get a starter number, but this will depend on the server resources, the amount of data collected by the node, etc. If the server is too slow we would need to decrease the number. If there are nodes with more than 3x late collects (Check the polling summary), the number should be increased: 

(Number of nodes x AVG Collect time) / 300

300 _ Default polling time.

• Then, fix files permissions:

/usr/local/nmis9/bin/nmis-cli act=fixperms

...

Here you can find further information.

Step 3. Move and adapt OMK

...

files

Configuration Files

Copy

Copy the configuration directory from the source server.

Create a conf backup first:

mv /usr/local/omk/conf /tmp/omk/conf

This can be done really easy with rsync:

rsync -r root@uburnto.opmantek.net:/usr/local/omk/conf /usr/local/omk

Convert to JSON

Configure

Step 4. Copy RRDs

...

Run script to adapt names

...