Need steps to configure NSO HA L3 BGP : For 6.0 release, we have a requirement to test NSO HA with L3 mode and bgp configs.QA needs sequence of pre-requisite steps and few other configs for deploying NSO HA with L3 mode. Hence, we request to provide some point of contact for troubleshooting issues and support when needed. 
Customer was helped by Thomas in an email thread and was provided the following:1.NSO Admin guide (and pointed out the Tailf HCC overview)2.NSO HA guide3.Demo recording of Thomas setting up L3 HAGetting below errors when configuring NSO HA L3 bgp settings on NSO Primary VM:admin@ncs% set hcc bgp node primary-node neighbor 192.168.20.4 as 65131admin@ncs% commitAborted: application communication failureadmin@ncs% set hcc bgp node primary-node enabledValue for 'gobgp-bin-dir' (<string>): /usr/binValue for 'as' (<unsignedInt>): 65132Value for 'router-id' (<IP address>): 192.168.20.5admin@ncs% commitAborted: application communication failureNeed someone to troubleshoot this issue and provide resolution for it.Hello, please provide us setup details so we may investigate.unicasted the setup detailsRetried the steps as discussed on webex session with CFP team, but still getting application communication failure error while committing hcc bgp configs. Need to wait for Van Pham to check into this issue till Monday.Checked with Van, unable to log into NSO 1 and NSO 2 is missing config.>> need gobgp config on all nso and routerScreenshots attached.Requesting additional information.gobgp config/package was already installed on both NSO1 and NSO2 VMs. Below is the output on the VMs.nso-vm1-sa:/home/admin# apt install gobgpdReading package lists... DoneBuilding dependency tree... DoneReading state information... Donegobgpd is already the newest version (2.25.0-3build1).0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.root@nso-vm2-sa:/home/admin# apt install gobgpdReading package lists... DoneBuilding dependency tree... DoneReading state information... Donegobgpd is already the newest version (2.25.0-3build1).0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.However, executing the below command gives no file error on both VMs.root@nso-vm1-sa:/home/admin# cat /etc/gobgpd.ymlcat: /etc/gobgpd.yml: No such file or directoryon router, below are the bgp configs that were configured:csr-vm5#router bgp 65131 bgp log-neighbor-changes neighbor 192.168.5.26 remote-as 65132 neighbor 192.168.6.59 remote-as 65133 ! address-family ipv4 redistribute connected neighbor 192.168.5.26 activate neighbor 192.168.6.59 activate exit-address-familyI followed the steps suggested by Thomas in webex recording for installing gobgpd.Can we get the missing configs or install steps that need to be configured on both NSO VMs and router as well? Hi Gomathi,It looks like gobgp config in NSO is missing:admin@ncs% show hcc bgpNo entries found.Please try the following config with correct router interface IP addresses, AS, and router id:Primary NSO:set hcc bgp node master enabled as 65132 router-id 192.168.5.26 gobgp-bin-dir /usr/bin neighbor 192.168.5.x as 65131Secondary NSO:set hcc bgp node standby enabled as 65133 router-id 192.168.6.59 gobgp-bin-dir /usr/bin neighbor 192.168.6.x as 65131On both nodes, do: request high-availability disableThen after bgp config, do:request high-availability enableHi Van,Can we look into this issue on webex meeting? I tried below configs with "primary-node" changed to "master" and "secondary-node" changed to "standby" with corresponding IP, AS and router-id values. But, still getting same error.admin@ncs% commitAborted: application communication failureThanks,Gomathi.Hi Gomathi,After updated to latest gobgp version 3.16.0, bgp is functional and high-availability is up.admin@ncs> show high-availabilityhigh-availability enabledhigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS ------------------------standby 192.168.5.252admin@ncs> show hccNODE BGPD BGPD ID PID STATUS ADDRESS STATE CONNECTED --------------------------------------------------------------master 39514 running 192.168.5.29 ESTABLISHED true1. wget 2. scp gobgp_3.16.0_linux_amd64.tar.gz to NSO node3. tar zxf gobgp_3.16.0_linux_amd64.tar.gz4. sudo mv gobgp* /usr/local/bin/Note that "gobgp-bin-dir /usr/local/bin" as the new gobgp was installed under/usr/local/bin directory.admin@nso-vm1-sa:~$ which gobgp/usr/local/bin/gobgp<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">For reference, below is config on primary node. hcc config should be changed accordingly on secondary node.admin@ncs% show high-availability token $9$UHHL5OHfYJg3iCyjJGIl90gE2Lv5VMM3trHMEUqHUWc=;ha-node master {  address   192.168.5.26;  nominal-role primary;}ha-node standby {  address     192.168.6.59;  nominal-role   secondary;  failover-primary ;}settings {  enable-failover  ;  start-up {    assume-nominal-role ;    join-ha       ;  }  reconnect-interval 15;  reconnect-attempts 3;}[ok][2023-08-01 00:20:29][edit]admin@ncs% show hccenabled;vip-address [ 192.168.5.27 ];bgp {  node master {    enabled;    gobgp-bin-dir /usr/local/bin;    as      65132;    router-id   192.168.5.26;    neighbor 192.168.5.29 {      as 65131;    }  }}[ok][2023-08-01 00:20:36]</pre></div></div>Switchover is working as expected with changes made to NSO host default route and added route reflector in the CSR1000V.Setup is working, Gomathi agreed to close this case.