Verifying the installation

Follow these instructions to verify whether the installation of your geo-redundant Netcool® Operations Insight® on Red Hat® OpenShift® deployment was successful.

1. Verify the connection between the primary and backup Web GUI.
   1. Log in to the primary Web GUI container by running the following command on the primary cluster:

      oc exec -ti <release_name>-webgui-primary-0 -- bash

      Where <release_name> is the name of your Netcool Operations Insight on Red Hat OpenShift deployment on the primary cluster.
   2. Run the following command from within the primary Web GUI container:

      curl -kv https://<release_name>-webgui-backup-0:16311/ibm/console

      Where <release_name> is the name of your Netcool Operations Insight on Red Hat OpenShift deployment on the primary cluster.
   The curl command runs successfully without any connection issues.
2. Verify that the openshift-service-serving-signer was imported correctly by updating a Web GUI filter in the primary Web GUI.
   The update is reflected in the backup Web GUI node.
3. Verify the connection between backup and primary Web GUI.
   1. Log in to the backup Web GUI container by running the following command on the backup cluster:

      oc exec -ti <release_name>-webgui-backup-0 -- bash

      Where <release_name> is the name of your Netcool Operations Insight on Red Hat OpenShift deployment on the backup cluster.
   2. Run the following command from within the backup Web GUI container:

      curl -kv https://<release_name>-webgui-primary-0:16311/ibm/console

      Where <release_name> is the name of your Netcool Operations Insight on Red Hat OpenShift deployment on the backup cluster.
   The curl command runs successfully without any connection issues.
4. Verify that the openshift-service-serving-signer was imported correctly by updating a Web GUI filter in the backup Web GUI.
   The update is reflected in the primary Web GUI node.
5. On the primary cluster, verify whether the Kafka brokers are exposed successfully. Check whether the new service with the name <release_name>-kafka-*-ext exists, where <release_name> is the name of your Netcool Operations Insight on Red Hat OpenShift deployment on the primary cluster.

   oc get svc | grep kafka.*ext

6. The new service maps the advertised port to the port used by the Kafka broker. To validate the secured connection, use the Kafka tool, as in the following example:

   kafkacat -b <FQDN-of-the-primary-load-balancer>:19093 -X ssl.ca.location=./myCertificate.crt -X security.protocol=SASL_SSL -X sasl.mechanisms=PLAIN -X sasl.username=<kafka-client-username> -X sasl.password=<kafka-client-password> -L

   Where:

   • <FQDN-of-the-primary-load-balancer> is fully qualified domain name of the primary load balancer.
   • myCertificate.crt is the CA certificate that you generated when you created the Kafka TLS secret.
   • <kafka-client-username> and <kafka-client-password> are the values that you generated when you created the Kafka credentials secret.
   Repeat for all exposed ports, for example, 19093, 19095 and 19097, to confirm complete access to the cluster. If you see the topic list with no error message, the broker is exposed successfully.