...
Become root and unpack the tarball:
Code Block # become rootsudo sh#root sudo sh # if the tarball was saved in a different location, adjust the following command cdtar cd # extract the tarball tar xzf opHA-x86_64-2.1.0.tgz
Start the interactive installer and follow its instructions:
Code Block sudo sh cd opHA-2.1.0/ ./installer ++++++++++++++++++++++++++++++++++++++++++++++++++++++ opHA (2.1.0) Installation script ++++++++++++++++++++++++++++++++++++++++++++++++++++++ This installer will install opHA into /usr/local/omk. To select a different installation location please rerun the installer with the -t option. ...
- The installer will interactively guide you through the steps of installing opHA. Please make sure to read the on-screen prompts carefully.
- When the installer finishes, opHA is installed into
/usr/local/omk, and the default configuration files are in/usr/local/omk/conf, ready for your initial config adjustments. - A detailed log of the installation process is saved as
/usr/local/omk/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.
- a small warning: the installer may warn about two "incorrect checksum detected" for two files, if you install this version on top of the Opmantek Virtual Appliance version 8.5.6G or after other Opmantek applications that were released since opHA 2.1.1. These warnings are benign and you can safely confirm that the installer is allowed to 'overwrite' those files.
...
opHA supports pollers pushing updates or Primaries pulling updates (or both). If you want a poller to have the ability to push, it needs to have the servers it should push to in it's Servers.nmis file. Conversely if you want Primaries to be able to pull they need to have the pollers they should pull from in their Servers.nmis file. At this point it is good to draw yourself a diagram (if you have not already) to aid you in configuring each Primary and poller.
In addtionaddition: each server (Primary and poller) needs to have a localhost entry in Servers.nmis which tells the server how to log in to itself. NB: it must be 'localhost' in both the key and name portions, 127.0.0.1 will not work!
...
By default, an NMIS server operates in standalone mode (which is also poller mode), to have NMIS behave in a Primary fashionPrimary fashion, you will need to modify the configuration, so you can edit the NMIS Configuration item "severserver_master" using your favourite text editor, edit this line and change from "false" to "true".
...
There are two options to run opHA, using Cron or a as a post process after a NMIS does a collect. Pushes and pulls can be requested from anywhere, if they are requested from the localhost no authentication is required, if they are requested from elsewhere authentication is required.
...