Versions Compared

Key

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

...

  • The individual performing this installation has 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 installed on the same server that opHA is being installed on.
  • You will need a license for opHA ( CONTACT US for an evaluation license ).
  • opHA has to be installed onto the Master and each Slave Poller NMIS server.

Preparation

...

Transfer the opHA tarball onto all servers in question, the Master and all the Slavespollers; 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:

...

  • An opHA user and password, by default this is an Apache htpasswd file, defined in /usr/local/omk/conf/users.dat.
  • The opHA user to use for the authentication, defined per Server in /usr/local/nmis8/conf/Servers.nmis (on the master if they are pulling, for the slaves pollers 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 poller or the same credentials for each slavepoller, providing for simple configuration, and more secure configuration if required.

...

Add Servers to Servers.nmis

opHA supports slaves pollers pushing updates or masters pulling updates (or both).  If you want a slave 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 masters to be able to pull they need to have the slaves 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 master and slavepoller.

In addtion: each server (master and slavepoller) 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!

...

  • the name (key) cannot contain / or . and must match what is in the key (which is the first line opening each settings bracket 'key' => {
  • if the name refers to an NMIS Slave Poller server, it should match the setting in 'server_name' mentioned above.
  • host must be a FQDN if it is not an IP (try using 127.0.0.1 if localhost does not work)

...

Code Block
themeEmacs
'key' => {   ### this must match the server_name in Config.nmis on the slavepoller
  'name' => 'key',
 # The name of the server- must match server_name in it's Config.nmis file it also what is displayed in the GUI, MUST match key in line above also
  'config' => 'Config.nmis', 
  'protocol' => 'http', # only HTTP is supported at this time
  'port' => '8042', # this should be the port that omkd runs on, set in opCommon, 'omkd_listen_port'  UNLESS CHANGED IT IS 8042
  'host' => 'example.domain.com', 
# the hostname used by the opHA process to connect to the server and retreve node and summary data, it will match the nmis_host field in Config.nmis.  It must be FQDN or IP and should match the one in Config.nmis, hostname.local might work
 
  'user' => 'nmismst', # user omkd will connect to this server with
  'passwd' => 'C00kb00k' # password omkd will connect to this server with
  'portal_host' => 'example.domain.com',  
## This is the FQDN used to make links to the slave it will match the 'host' entry above UNLESS you are using a proxy service to reach the slave in which case it is the FQDN used to refer to the slave through the proxy.
  'portal_port' => '80',
  'portal_protocol' => 'http',
  'cgi_url_base' => '/cgi-nmis8'  
}

Edit the entry to look like this, in this example the hostname of the slave poller is "vali":

Code Block
themeEmacs
 'localhost' => {
   'name' => 'localhost',
   'config' => 'Config.nmis',
   'protocol' => 'http', 
   'host' => '127.0.0.1',   
   'port' => '8042',
   'user' => 'nmis',
   'passwd' => 'nm1888'
 },
 'vali' => {
   'name' => 'vali',
   'config' => 'Config.nmis',
   'protocol' => 'http',
   'port' => '8042',
   'host' => 'vali.opmantek.com',
   'user' => 'nmismst',
   'passwd' => 'C00kb00k',
   'portal_host' => 'vali.opmantek.com',
   'portal_port' => '80',
   'portal_protocol' => 'http',
   'cgi_url_base' => '/cgi-nmis8'  
 }

...

If you were presenting the Slave poller and needed to use an alternate connection, e.g. through a reverse proxy for presenting a portal, you would modify the portal_protocol, portal_port and portal_host accordingly.

...

By default, an NMIS server operates in standalone mode (which is also slave poller mode), to have NMIS behave in a masterly fashion, you will need to modify the configuration, so you can edit the NMIS Configuration item "sever_master" using your favourite text editor, edit this line and change from "false" to "true".

Code Block
themeEmacs
'server_master' => 'true',
'nmis_master_poll_cycle' => 'false' # this must be false 

Adding

...

Poller Groups to Master

On each slave poller you will need to determine which groups are currently in use.

...

You can also use the admin script /usr/local/nmis8/admin/grouplist.pl on the master to find and patch all groups used by all devices imported from the slavespollers, it can even be added to cron to automate group updates.

Once opHA has succesfully pulled/pushed the devices from slave poller to master you can analyse and patch the groups list by using the following.

...

opHA supports Multi-Master, that means you can have several masters collecting information from the same slaves pollers if required.  This could be especially useful if you wanted to have one master with all groups on a slavepoller, and another master with different groups from different slavespollers, effectively sharing some information between groups.

...

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