Note: Security Director Insights VMs must have the same Security Director Insights software versions. In each Security Director Insights VM, configure the following network interfaces to enable HA:

• Eth0—For Security Director Insights data and management
• Eth1—For HA monitoring

You must ensure that:

• On each node, the IP addresses of the eth0 and eth1 interfaces are in different subnets.
• The IP address of the eth0 interface of the active and standby nodes are in the same subnet.
• The IP address of the eth1 interface of the active and standby nodes are in the same subnet.

A) Use the following procedure to configure IP addresses for the network interfaces:

• Go to Security Director Insights CLI.
• # ssh admin@${security-director-insights_ip}
• Enter the Settings menu.
  # server
• View already configured IP addresses.
  # show ip
• Configure the eth0 IP address.
  # set ip interface management address ${eth0_ip} gateway ${eth0_gateway} netmask ${eth0_netmask}
• Configure the eth1 IP address.
  # set ip interface ha-monitoring address ${eth1_ip} gateway ${eth1_gateway} netmask ${eth1_netmask}
• Verify the configured IP addresses.
  # show ip

B) To enable High Availability on SDI via CLI follow below steps

Step 1: Access the Security Director Insights CLI: bash ssh admin@${security-director-insights_ip}

Step 2: Enable HA: # ha enable ${VIP_data_interface}/netmask} ${VIP_monitoring_interface}/netmask} ${secondary_node_data_interface_ip} ${secondary_node_admin_password} ${IP addresses (separated by comma) for ping test}
Provide the Security Director IP address. x.x.x.x

Example: 
sdi-master:Core#(server)# ha enable x.x.x.x/24 x.x.x.x/24 x.x.x.x password x.x.x.x 
Please provide the SD IP address: x.x.x.x
PING x.x.x.x (x.x.x.x) 56(84) bytes of data.
64 bytes from x.x.x.x: icmp_seq=1 ttl=64 time=0.748 ms
64 bytes from x.x.x.x: icmp_seq=2 ttl=64 time=37.5 ms
64 bytes from x.x.x.x: icmp_seq=3 ttl=64 time=0.302 ms

--- 10.219.87.33 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2020ms
rtt min/avg/max/mdev = 0.302/12.877/37.582/17.470 ms
enable HA: Finished HA configuration

C) To enable SDI High Availability from Security director UI follow steps mentioned under SDI HA config user guide 

Step 3: Once HA enabled verify HA status on SDI master node 

sdi-master:Core#(server)# ha status
Cluster name: lahbkhooysiwmrki
WARNING: corosync and pacemaker node names do not match (IPs used in setup?)
Stack: corosync
Current DC: sdi-standby (version 1.1.18-2b07d5c5a9) - partition with quorum
Last updated: Wed Sep 25 06:36:35 2024
Last change: Wed Sep 25 06:26:39 2024 by root via crm_attribute on sdi-active

2 nodes configured
11 resources configured

Online: [ sdi-active sdi-standby ]

Full list of resources:

 svc_watchdog_s (ocf::heartbeat:script):        Started sdi-standby
 kafka-mirror   (ocf::heartbeat:script):        Started sdi-standby
 active/standby Set: msPostgresql [pgsql]
     actives: [ sdi-active ]
     standbys: [ sdi-standby ]
 post-promotion (ocf::heartbeat:script):        Started sdi-active
 Resource Group: active-group
     vip-data   (ocf::heartbeat:IPaddr2):       Started sdi-active
     vip-rep    (ocf::heartbeat:IPaddr2):       Started sdi-active
     cluster-mon        (ocf::pacemaker:ClusterMon):    Started sdi-active
     svc_watchdog_a     (ocf::heartbeat:script):        Started sdi-active
 Clone Set: ping-check-clone [ping-check]
     Started: [ sdi-active sdi-standby ]

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

Step 4: Also verify HA status on SDI standby node. 

sdi-standby:Core#(server)# ha status
Cluster name: lahbkhooysiwmrki
WARNING: corosync and pacemaker node names do not match (IPs used in setup?)
Stack: corosync
Current DC: sdi-standby (version 1.1.18-2b07d5c5a9) - partition with quorum
Last updated: Wed Sep 25 06:36:39 2024
Last change: Wed Sep 25 06:26:39 2024 by root via crm_attribute on sdi-active

2 nodes configured
11 resources configured

Online: [ sdi-active sdi-standby ]

Full list of resources:

 svc_watchdog_s (ocf::heartbeat:script):        Started sdi-standby
 kafka-mirror   (ocf::heartbeat:script):        Started sdi-standby
 active/standby Set: msPostgresql [pgsql]
     actives: [ sdi-active ]
     standbys: [ sdi-standby ]
 post-promotion (ocf::heartbeat:script):        Started sdi-active
 Resource Group: active-group
     vip-data   (ocf::heartbeat:IPaddr2):       Started sdi-active
     vip-rep    (ocf::heartbeat:IPaddr2):       Started sdi-active
     cluster-mon        (ocf::pacemaker:ClusterMon):    Started sdi-active
     svc_watchdog_a     (ocf::heartbeat:script):        Started sdi-active
 Clone Set: ping-check-clone [ping-check]
     Started: [ sdi-active sdi-standby ]

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

sdi-standby:Core#(server)#

Note : If you face any issues, please contact JUNIPER JTAC Support for assistance.