Content Comparison

...

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

2. Add NATS Cluster Configuration: Ensure the following configuration is included in opCommon.json on all servers. In the below example we have added the Main Primary, arbiter and Secondary Primary FQDNs and port/s to be utilized in the nats_cluster attribute, you can find this in the database section.

   Code Block
   language json
   "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ]

3. Ensure "nats_num_replicas": 3 instead of 1 in /usr/local/omk/conf/opCommon.json.
   Ensure there is only one instance of “nats_num_replicas” and "nats_cluster" in opCommon.json

   Code Block
   "database" : { "nats_num_replicas": 3, "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ] }​

If there are more than one instance of these 2 parameters there could be issues

shankarn@opha-dev7:/usr/local/omk/bin$ grep nats_cluster /usr/local/omk/conf/opCommon.json
      "nats_cluster" : [ "opha-dev4.opmantek.net", "opha-dev5.opmantek.net", "opha-dev7.opmantek.net" ],
shankarn@opha-dev7:~$ grep nats_num_replicas /usr/local/omk/conf/opCommon.json
      "nats_num_replicas" : 3,
shankarn@opha-dev7:~$

...

systemctl restart nmis9d opchartsd opeventsd omkd ophad

Discover the Peers

Click on Peers in opHA-MB portal on the Main Primary (http://<fqdn of Main Primary>/en/omk/opHA/peers)

...

cd /usr/local/omk/bin
sudo systemctl restart ophad # if ophad is not running
./ophad cmd producer start

Final Steps

...

If the target_dir is not /usr/local/omk but different, say /data/omk please suffix the command with the cli option
--opha-cli-path /data/omk/bin/opha-cli.pl

cd /usr/local/omk/bin
sudo /data/omk/bin/ophad cmd producer start --opha-cli-path /data/omk/bin/opha-cli.pl

Please run through opHA-MB 5.0 User Guide to find any config issues thats been missed.

Final Steps

1. Accept EULAs: Make sure when you login to each server to confirm that all End User License Agreements (EULAs) are accepted.

...

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

2. Add NATS Cluster Configuration: Ensure the following configuration is included in opCommon.json on all servers. In the below example we have added the Main Primary, arbiter and Secondary Primary FQDNs and port/s to be utilized in the nats_cluster attribute, you can find this in the database section.

   Code Block
   language json
   "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ]

   
   Ensure "nats_num_replicas": 3 instead of 1 in /usr/local/omk/conf/opCommon.json.
   Ensure there is only one instance of “nats_num_replicas” and "nats_cluster" in opCommon.json

   Code Block
   "database" : { "nats_num_replicas": 3, "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ] }​

   If there are more than one instance of these 2 parameters there could be issues

   Code Block
   shankarn@opha-dev7:/usr/local/omk/bin$ grep nats_cluster /usr/local/omk/conf/opCommon.json "nats_cluster" : [ "opha-dev4.opmantek.net", "opha-dev5.opmantek.net", "opha-dev7.opmantek.net" ], shankarn@opha-dev7:~$ grep nats_num_replicas /usr/local/omk/conf/opCommon.json "nats_num_replicas" : 3, shankarn@opha-dev7:~$

4. Main Primary and Secondary Primary only: Ensure there is only one instance of “db_replica_set” and "db_mongo_cluster" in opCommon.json. And these 2 vars are as set below.

   Code Block
   "database" : { "db_replica_set": "rs1", "db_mongo_cluster": [ "opha-dev1.opmantek.net", "opha-dev6.opmantek.net" ], }​

   If there are more than one instance of these 2 parameters there could be issues

   Code Block
   shankarn@opha-dev7:/usr/local/omk/bin$ grep db_mongo_cluster /usr/local/omk/conf/opCommon.json "db_mongo_cluster" : [ "opha-dev4.opmantek.net", "opha-dev7.opmantek.net" ], shankarn@opha-dev7:~$ grep nats_num_replicas /usr/local/omk/conf/opCommon.json "nats_num_replicas" : 3, shankarn@opha-dev7:~$

Server-Specific Configuration

...

For all the opHA Peers, go to opHA Peers page click on “Sync all nodes” followed by “Pull Peer Data”. Please refer to https://docs.community.firstwave.com/wiki/spaces/opHA/pages/3272605706/opHA-MB+5.0+User+Guide#Scenario-1-%3A-Using-opHA4-‘Pull’-on-Primary-to-synchronize-nmisng-collections for more details.

...

Restart opHA service on all the

...

VMs

sudo systemctl restart ophad

Start the Poller and Mirrors

...

the Poller and Mirrors

Execute the following command on the poller and mirror servers.

cd /usr/local/omk/bin
./ophad cmd producer start

If the target_dir is not /usr/local/omk but different, say /data/omk please suffix the command with the cli option
--opha-cli-path /data/omk/bin/opha-cli.pl

cd /usr/local/omk/bin
.sudo /data/omk/bin/ophad cmd producer start

...

 --opha-cli-path /data/omk/bin/opha-cli.pl

Please run through opHA-MB 5.0 User Guide to find any config issues thats been missed.

Final Steps

1. Accept EULAs: Make sure when you login to each server to confirm that all End User License Agreements (EULAs) are accepted.