The SDI standby nodes shows the status NA on the UI.

Under Security Director >> Administration >> Insights Nodes, we see that the SDI standby node shows the status NA.

On the CLI, both the nodes are in ONLINE mode and Healthy.

You can verify this from the CLI using the admin user to run the command "ha status" in the server mode:

Example:

Primary Node:

primary:Core#(server)# ha status

Cluster name: ezhdlkzdcocmvboy

WARNING: corosync and pacemaker node names do not match (IPs used in setup?)

Stack: corosync

Current DC: primary (version 1.1.18-2b07d5c5a9) - partition with quorum

Last updated: Fri Mar 15 09:27:32 2024

Last change: Fri Mar 15 02:42:23 2024 by root via crm_attribute on primary

2 nodes configured

9 resources configured

Online: [ primary standby ]

Full list of resources:

 svc_watchdog_s (ocf::heartbeat:script): Started standby

 kafka-mirror (ocf::heartbeat:script): Started standby

 active/standby Set: msPostgresql [pgsql]

   actives: [ primary ]

   standbys: [ standby ]

 post-promotion (ocf::heartbeat:script): Started primary

 Resource Group: active-group

   vip-data (ocf::heartbeat:IPaddr2): Started primary

   vip-rep (ocf::heartbeat:IPaddr2): Started primary

   cluster-mon (ocf::pacemaker:ClusterMon): Started primary

   svc_watchdog_a (ocf::heartbeat:script): Started primary


Daemon Status:

 corosync: active/enabled

 pacemaker: active/enabled

 pcsd: active/enabled

Standby Node:

standby:Core#(server)# ha status

Cluster name: ezhdlkzdcocmvboy

WARNING: corosync and pacemaker node names do not match (IPs used in setup?)

Stack: corosync

Current DC: primary (version 1.1.18-2b07d5c5a9) - partition with quorum

Last updated: Fri Mar 15 09:30:18 2024

Last change: Fri Mar 15 02:42:19 2024 by root via crm_attribute on primary

2 nodes configured

9 resources configured

Online: [ primary standby ]

Full list of resources:

 svc_watchdog_s (ocf::heartbeat:script): Started standby

 kafka-mirror (ocf::heartbeat:script): Started standby

 active/standby Set: msPostgresql [pgsql]

   actives: [ primary ]

   standbys: [ standby ]

 post-promotion (ocf::heartbeat:script): Started primary

 Resource Group: active-group

   vip-data (ocf::heartbeat:IPaddr2): Started primary

   vip-rep (ocf::heartbeat:IPaddr2): Started primary

   cluster-mon (ocf::pacemaker:ClusterMon): Started primary

   svc_watchdog_a (ocf::heartbeat:script): Started primary


Daemon Status:

 corosync: active/enabled

 pacemaker: active/enabled

 pcsd: active/enabled

Still, the UI shows the Standby node is in NA state.

This issue usually occurs when for some reason, the Security Director believes that it needs to connect only to the Primary SDI node. This happens when the webProxy.conf file in the Space server has only the IP of the primary SDI node.

We need to add the VIP IP of the SDI and the standby node IP in this file to resolve the issue.

Please follow the steps mentioned below to resolve this.

• Login to the Space CLI using the admin user.
• Navigate to the path /etc/httpd/conf.d with the command

cd /etc/httpd/conf.d/

• Edit the file webProxy.conf and look for the ProxyPass parameter.
• Here, add the IP of the SDI VIP and the standby node like mentioned below:

ProxyPass /cyadmin1/ https://<IP of the SDI IP>/cyadmin/
ProxyPass /cyadmin2/ https://<IP of the SDI standby Node>/cyadmin/

Example

ProxyPass /cyadmin/ https://10.0.0.1/cyadmin/

ProxyPass /cyadmin1/ https://10.0.0.3/cyadmin/

ProxyPass /cyadmin2/ https://10.0.0.2/cyadmin/

Where 10.0.0.1 is the primary SDI server, 10.0.0.2 is the standby server and 10.0.0.3 is the SDI VIP IP.
 

• Once done, save the changes.
• Restart the httpd service:

systemctl restart httpd

After this, the UI should show both the nodes are UP on the SD UI.