Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The individual performing this installation has some Linux experience.
  • NMIS8 is installed on the same server where opHA will be installed
  • NMIS8 is installed in /usr/local/nmis8
  • opHA will be installed into /usr/local/nmis8
  • Root access is available (not always needed but much easier)
  • Perl 5.10 
  • RRDtool 1.4.7
  • NMIS 8.3.24G or later
  • opHA will be installed onto the Master and each Slave Poller NMIS server

Installation Steps

...

This step will be repeated for each NMIS master and slave poller server

  • Copy the opHA tarball to the slave poller or master NMIS server (a tarball is a GZIP'd tar file, e.g. opHA-1.1.tar.gz)
    1. You may need to use SCP or FTP to get the file onto the server.
  • The file will now likely be in the users home directory.
  • If the installation directory does not already exist
  • Change into the directory where the tarball was copied
  • Untar the file

...

Supported in opHA is having NMIS use JSON for its database, this will require NMIS 8.4.8g or greater.  This should be enabled on all servers running in an opHA cluster.  The following needs to be run on every master and slave poller server in a cluster and this should be co-ordinated to run very close together.

...

opHA has a simple yet strong authentication model, to prevent unwanted access to NMIS data.

The slave poller is configured with:

  • An NMIS user and password, by default this is an Apache htpasswd file, defined in /usr/local/nmis8/conf/users.dat
  • An NMIS user, with associated privileges, defined in /usr/local/nmis8/conf/Users.nmis
  • An NMIS user to use for the authentication policy enforcement, defined in /usr/local/nmis8/conf/Config.nmis
  • Server Community, which the server must use to request data.

The master is configured with (for each slavepoller):

  • An NMIS user and password, which needs to match the slave poller configuration
  • A slavepoller/server community, which needs to match the slave poller configuration.

This model enables you to use separate credentials for each slave poller or the same credentials for each slavepoller, providing for simple configuration, and more secure configuration if required.

All communications between master and slave poller can be done over SSL if required, this is supported by configuring your server HTTPD to support SSL and then configuring the master, slave poller communications to use HTTPS.

opHA

...

Poller Configuration

This configuration will be done on each NMIS Slave Poller Server.  By default, the shared community for a slave poller is "secret" if you want to change this to something specific you can edit the NMIS Configuration item "slave_community" using your favourite text editor, edit this line and change secret to your desired opHA community string.

...

After refreshing the web pages on the NMIS Master server you will see the data from the slavespollers.