Enable NSO HA on IPv6 setup: Configured an NSO HA, follow this wiki link on an IPv6 setup:"show high-availability status" on primary node is OK, but not on secondary node. Is there any configuration missing for IPv6?Primary:admin@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseSecondary:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status read-only-mode falseHere are the HA configuration on both nodes:Primary:admin@ncs% show high-availability token $9$a5bEJW74JrgYUlTImS7p4Fj3gvN/kxwhwVBGFmBjJok=;ha-node master {  address   fded:1bc1:fc3e:96d0:192:168:5:41;  nominal-role primary;}ha-node standby {  address     fded:1bc1:fc3e:96d0:192:168:5:42;  nominal-role   secondary;  failover-primary true;}settings {  enable-failover  true;  start-up {    assume-nominal-role true;    join-ha       true;  }  reconnect-interval 15;  reconnect-attempts 3;}Secondary:admin@ncs% show high-availability token $9$9Kw3nWwqYpFjnk2FlX+8dr41rA3SUQ5cb02x3u+ZHPo=;ha-node master {  address   fded:1bc1:fc3e:96d0:192:168:5:41;  nominal-role primary;}ha-node standby {  address     fded:1bc1:fc3e:96d0:192:168:5:42;  nominal-role   secondary;  failover-primary true;}settings {  enable-failover  true;  start-up {    assume-nominal-role true;    join-ha       true;  }  reconnect-interval 15;  reconnect-attempts 3;}
Hi Crystal,Can you provide access to the nodes so we can take a look?Thanks,AbeHi Abe,The NSO is using private subnet. You will need to reach it from jump host. NSO has been configured with dual-stack. Jump host: 172.20.111.162id: pw: root/Cwork123!NSO 41: 192.168.5.41 NSO 42: 192.168.5.42id/pw: root/Vtsisco@123!Thanks.-CrystalHi Crystal,Show high availability status on both nodes now shows HA has been stablished.Primary_node:root@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS-------------------------------------------standby fded:1bc1:fc3e:96d0:192:168:5:42Secondary_node:root@ncs> show high-availability statushigh-availability status mode secondaryhigh-availability status current-id standbyhigh-availability status assigned-role secondaryhigh-availability status be-secondary-result initializedhigh-availability status primary-id masterhigh-availability status read-only-mode falsePer NSO admin guide (attached, ), to support ipv4 and ipv6 access simultaneously, we need to configure extra-listen for each agent and transport, where additional IP address and port pairs can be configured. (for ipv4 0.0.0.0, for ipv6 "::")example:<!-- Use the built-in SSH server --><ssh> <enabled>true</enabled> <ip>0.0.0.0</ip>  <port>2024</port> <extra-listen> <ip>::</ip>  <port>2024</port> </extra-listen></ssh>Please let me know if you have any other questions. Designating the issue resolved and ticket will be closed now.Thanks,AbeHi Crystal,Show high availability status on both nodes now shows HA has been stablished.Primary_node:root@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS-------------------------------------------standby fded:1bc1:fc3e:96d0:192:168:5:42Secondary_node:root@ncs> show high-availability statushigh-availability status mode secondaryhigh-availability status current-id standbyhigh-availability status assigned-role secondaryhigh-availability status be-secondary-result initializedhigh-availability status primary-id masterhigh-availability status read-only-mode falsePer NSO admin guide (attached, ), to support ipv4 and ipv6 access simultaneously, we need to configure extra-listen for each agent and transport, where additional IP address and port pairs can be configured. (for ipv4 0.0.0.0, for ipv6 "::")example:<!-- Use the built-in SSH server --><ssh><enabled>true</enabled><ip>0.0.0.0</ip><port>2024</port><extra-listen><ip>::</ip><port>2024</port></extra-listen> </ssh>Please let me know if you have any other questions. Designating the issue resolved and ticket will be closed now.Thanks,AbeIncluding more information Abe shared here for future reference. Add "extra-listen" for <ha> section in ncs.conf. <ha>   <enabled>true</enabled>   <ip>0.0.0.0</ip>   <port>4570</port>   <extra-listen>    <ip>::</ip>    <port>4570</port>   </extra-listen>   <tick-timeout>PT20S</tick-timeout> </ha>Attached are other info. Abe shared.