Page History

...

• The individual performing this installation has some a small bit of Linux experience.
• Root access is available.
• Internet access is required for installing any missing but required software packages.
• NMIS must be NMIS8 is installed on the same server where that opHA will be installedNMIS8 is installed in /usr/local/nmis8
• opHA will be installed into /usr/local/omk
• Root access is available (not always needed but much easier)
• Perl 5.10 
• RRDtool 1.4.7
• NMIS 8.3.24G or later
• being installed on.
• You will need a license for opHA (evaluation licenses available here ).
• opHA has to opHA will be installed onto the Master and each Slave NMIS server.

Installation Steps

Install opHA Software

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

• Copy the opHA tarball to the slave or master NMIS server (a tarball is a GZIP'd tar file, e.g. opHA-2.0.2.tgz)
  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.
• opHA will be installed into /usr/local/omk

unalias cp
cd /usr/local
tar xvf ~/opHA-<version>.tgz
# NB! If you get a message about timestamps in the future be sure to fix the clock on the server 
cd omk/

cp install/nmis/Access.opha.nmis/usr/local/nmis8/install
cp install/nmis/Tables.opha.nmis /usr/local/nmis8/install
cp install/nmis/Table-Nodes.opha.nmis /usr/local/nmis8/conf/Table-Nodes.nmis

cp install/nmis/BusinessServices.nmis /usr/local/nmis8/conf
cp install/nmis/Servers.nmis /usr/local/nmis8/conf
cp install/nmis/Customers.nmis /usr/local/nmis8/conf
cp install/nmis/ServiceStatus.nmis /usr/local/nmis8/conf
cp install/nmis/Tenants.nmis /usr/local/nmis8/conf
cp install/nmis/Table-* /usr/local/nmis8/conf
 
# Merge your current Access configuration with the opHA access configuration
/usr/local/nmis8/admin/updateconfig.pl /usr/local/omk/install/nmis/Access.nmis.opha /usr/local/nmis8/conf/Access.nmis 
/usr/local/nmis8/admin/updateconfig.pl /usr/local/omk/install/nmis/Tables.nmis.opha /usr/local/nmis8/conf/Tables.nmis 

/usr/local/nmis8/admin/fixperms.pl

cp install/omkd.init.d /etc/init.d/omkd
cp install/omk-rotate.conf /etc/logrotate.d/
cp install/opCommon.nmis conf/
cp install/users.dat conf/

chown -R nmis:nmis /usr/local/omk
  
chkconfig --add omkd
service omkd start 

Verify that the daemon is running:

root@nmis64 script]# service omkd start
Starting omk daemon: 
[root@nmis64 script]# ps aux | grep opmantek
root 14949 1.1 3.0 213880 63504 pts/0 S 07:43 0:00 ./opmantek.pl daemon
root 14952 0.0 0.0 103224 864 pts/0 S+ 07:43 0:00 grep opmantek
[root@nmis64 script]# 

If you do not see the daemon running, try this and look for the reason it is not working (skip this if everything above is fine)

cd script
./opmantek.pl daemon
# if that does not give you any errors and runs, CTRL+C and then run
./opmantek.sh
# now grep for the opmantek process again, also check the log files in /usr/local/omk/log     

Verify that the date/time are correct 

date
# if they are not make sure the timezone is correct and run ntpdate
/etc/init.d/ntpdate start  

...

Preparation

• If you do not yet have a working installation of NMIS in your server, please follow the procedure in the NMIS 8 Installation Guide.
• Download opHA from the Opmantek website.

Installation Steps

Transfer the opHA tarball onto all servers in question, the Master and all the Slaves; either by direct download from the Opmantek website, or from your desktop with scp or sftp or a similar file transfer tool. Repeat the following steps for each involved server:

• Become root and unpack the tarball:

  Code Block
  # become rootsudo sh# if the tarball was saved in a different location, adjust the following command cdtar 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.

Enter License and accept EULA

If the daemon is loaded and the installation has gone well you should now be able to load the opHA GUI, from http://server_name:8042/omk/opHA. This URL should present you with a webpage that allows you to enter a license key and accept a EULA.  This step will need to be completed on each opHA instance.  After successful license key and EULA acceptance you will be presented with a dashboard that looks like this:

...

• An opHA user and password, by default this is an Apache htpasswd file, defined in in /usr/local/omk/conf/users.dat.
• The opHA user to use for the authentication, defined per Server in in /usr/local/nmis8/conf/Servers.nmis (on the master if they are pulling, for the slaves if they are pushing)
• An IP address list that defines who is allowed to connect to the daemon (depending on the operation a combination of ip address and login credentials is required)

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

opHA Configuration

Server Name for opHA

...

Logs can be found in /usr/local/omk/log or also viewed from the GUI at at http://server_name:8042/omk/opHA/logs

Troubleshooting

• check the logs in /usr/local/omk/logs/.
• restart the daemon (required after any config changes)

• run daemon from command line and see if the terminal has any helpful errors:

  Code Block
  /usr/local/omk/script/opmantek.pl daemon

...