Page Comparison

...

1.2 Download Software

Download the required opHA 5 software onto each server.

...

Run the installation commands on each server as neededin the opHA cluster.

All the following setup commands in this setup should be run as the root user

...

1. Edit Configuration: Update the /etc/nats-server.conf file with the following settings:

   1. Change the server_name to the name of your Main Primary server.

   2. Remove or comment out the cluster section, so that this remains:

server_name: "opha-primary1.opmantek.net"  #The local server  
http_port: 8222 
listen: 4222 
jetstream: enabled 
accounts { 
  $SYS { 
    users = [ 
      { user: "admin",
        pass: "password" 
      } 
    ] 
  } 
  ophad: { 
    users: [ 
        { user: "omkadmin", password: "op42opha42" } 
    ] 
    jetstream: enabled 
  } 
} 

jetstream { 
  store_dir: "/opt/nats/storage" 
  max_memory_store: 1028M 
  max_file_store: 1028M 
} 

3. Common Configuration for All Servers

...

1. Backup Configuration: Make a backup copy of the opCommon.json file before making any changes.

2. Add NATS Server Configuration: Ensure the following configuration is included in opCommon.json on all servers. In the below example we have added the Main Primary FQDN and port to be utilized in the nats_server attribute, you can find this in the database section.

   Code Block
   language json
   "nats_server": "opha-primary1.opmantek.net:4222"

   IMPORTANT

   Delete the following line from the opCommon.json file.

3. Code Block
   language json
   "db_mongo_cluster": [],

...

The following steps should be performed only on the Main Primary MongoDB instance.

4.1 Initialize MongoDB Replica Set

Connect to MongoDB using the mongosh command:

...

mongosh --username opUserRW --password op42flow42 admin

Then run the following commandcommands, to initiate a MongoDB Replica Set for streaming database changes.

rs.initiate()
exit

Restart mongod

systemctl restart mongod

5. Starting Services

5.1 Start NATS (on Main Primary Only)

Start the NATS service on the Main Primary server ONLY:

...

sudo systemctl restart nmis9d opchartsd opeventsd omkd ophad

Note: after you restart the daemons, opHA MB will not be licensed on the Main Primary, so the ophad daemon will show as an Error:

...

Proceed to the next step.

6. Update License

Install the opHA-MB for NMIS & opCharts license on the Main Primary server only.

To obtain a license please contact FirstWave Sales.

Currently there are 2 available licenses and Message Bus will not run without a license.

• opHA-MB for NMIS & opCharts (This license is required for Message Bus to run).

NMIS and opCharts data are synced from all poller/mirrors to the Main Primary using Message Bus. In replication mode, If the Main Primary were to go down the Secondary Primary will retain the NMIS and opCharts data.

...

• opHA-MB for opEvents (This license is an add-on for opEvents).

With this add-on opEvents will use Message Bus to sync opEvents data from each poller/mirror to the Main Primary and in replication mode opEvents data is synced to the Secondary Primary. In replication mode, If the Main Primary were to go down the Secondary Primary will retain the opEvents data.

...

You need to enter a License Key in the Modules → opLicensing as below on the Main Primary.

...

7. Restart opHA service on the Main Primary

sudo systemctl restart ophad

...