Page History

...

cd ~
tar xvf ~/opHA-<version>.tar.gz
cd opHA/
cp install/Servers.nmis /usr/local/nmis8/conf/
cp cgi-bin/connect.pl /usr/local/nmis8/cgi-bin/ 
cp lib/NMIS/Connect.pm /usr/local/nmis8/lib/NMIS

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

...

'slave_community' => 'secret',
'auth_src_ip' => '192.168.88.11', 

Verify that the Apache user has been configured for master functions.  The default userid is "nmismst" and the file /usr/local/nmis8/conf/users.dat should include an entry like

nmismst:vnnFthCKoHsps

opHA Master Configuration

...

Once the slaves have been setup, you can configure the master with each of its slaves.  This is done by editing the file /usr/local/nmis8/conf/Servers.nmis, and adding a section for each server.

A The default entry looks entries look like this:

 'nmis2nmis1' => {
   'community' => 'secret',
   'name' => 'nmis1',
   'config' => 'Config.nmis',
   'secureprotocol' => 'falsehttps',
   'nameport' => 'NMIS2443',
   'confighost' => 'Config.nmisnmis1.domain.com',
   'portal_protocol' => 'http',
   'portal_port' => '80',
   'portal_host' => '10nmis1.3.2.1'
 }

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

 'valialternate.com',
   'cgi_url_base' => '/cgi-nmis8',
   'url_base' => '/nmis8',
   'user' => {'nmismst',
   'communitypasswd' => 'YOURNAMEHEREC00kb00k'
 },
 'nmis2' => {
   'securecommunity' => 'falsesecret',
   'name' => 'valinmis2',
   'config' => 'Config.nmis',
   'protocol' => 'http',
   'port' => '80',
   'host' => '192.168.1.42',
   'portal_protocol' => 'http',
   'portal_port' => '80',
   'portal_host' => 'nmis2',
   'cgi_url_base' => '/cgi-nmis8',
   'url_base' => '/nmis8',
   'user' => 'nmismst',
   'passwd' => 'valiC00kb00k'  
 },

Edit the entry to Multiple entries would look like this, note the comma between entries.in this example the hostname of the slave is "vali":

 'nmis2vali' => {
   'community' => 'secretYOURNAMEHERE',
   'securename' => 'falsevali',
   'nameconfig' => 'NMIS2Config.nmis',
   'configprotocol' => 'Config.nmishttp',
   'port' => '80',
   'host' => '10.3.2.1'
 },
 'nmis3vali',
   'portal_protocol' => {'http',
   'communityportal_port' => 'secret80',
   'secureportal_host' => 'falsevali',
   'namecgi_url_base' => 'NMIS3/cgi-nmis8',
   'configurl_base' => 'Config.nmis/nmis8',
   'portuser' => '80nmismst',
   'hostpasswd' => '10.4.5.6'
 }

C00kb00k' 
 }

There are many options in this configuration but unless you are wanting to change the defaults considerably most of them will not matter.  If you wanted to use HTTPS to connect between the master and the slave, you could use https as the protocol and update the port accordingly.  You can use different user and passwd permissions here.

If you were presenting the Slave 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.

Promoting NMIS to be a Master

By default, an NMIS server operates in standalone mode (which is also slave 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".

'server_master' => 'true', 
'auth_src_ip' => '192.168.88.11', 

Access opMaps Web Page

The default URL to access opMaps is http://nmis.domain.com/cgi-omk/opMaps

...