Unable to fetch the ssh-host key for the RFS node and the cluster status showing down: Hi-Unable to fetch the ssh key for the RFS node and the cluster status showing down. Please take a look.admin@ncs% request cluster remote-node rfs-1 ssh fetch-host-keysresult failedinfo Connection to rfs-1 timed outadmin@ncs% run show cluster           LAST  RECEIVEDNAME  NAME STATUS EVENT NOTIFICATIONS-------------------------------------------rfs-1rfs-2REMOTE                 LOCAL REMOTENODE  ADDRESS     PORT CHANNELS USER  USER  STATUS TRACE-------------------------------------------------------------------------rfs-2  172.29.106.133 2022 -     admin admin  down  disabledrfs-1  172.29.106.132 2022 -     admin admin  down  disabledCluster setupCFS - 172.29.106.131RFS1 - 172.29.106.132RFS2 - 172.29.106.133Credentials: admin/Cwork123!
Hello,Please check your netconf ports and network connectivity.Regards,Janaki Duggiralawe are able to ping from CFS to RFS.can you please let us know how to check the netconf ports?setup details are provided below., can you please check ?Thanks,Arun.M.GHello, We tried to log into the setup mentioned here but we were unable to log in. Please give us the correct IPs to CFS/RFS. If these IPs are correct then maybe the network is not stable, so we are unable to troubleshoot.jaduggir@$ ssh admin@172.29.106.132ssh: connect to host 172.29.106.132 port 22: Operation timed out Regards, Janaki DuggiralaHi Janaki,Able to connect the VM's now, Could you please check the setup.nso@gd-arupras2-nso:~$ ssh admin@172.29.106.131The authenticity of host '172.29.106.131 (172.29.106.131)' can't be established.ECDSA key fingerprint is SHA256:DTy6b5qyCA+gJkcw1JjeB7hcPUNlaR3tRGMcSwbGb1c.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added '172.29.106.131' (ECDSA) to the list of known hosts.admin@172.29.106.131's password:Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-29-generic x86_64)Documentation: Management:   Support:    Canonical Livepatch is available for installation.<ul class="alternate" type="square">Reduce system reboots and improve kernel security. Activate at:   674 packages can be updated.459 updates are security updates.Last login: Wed Sep 14 09:46:58 2022 from 10.65.57.218admin@nso-172-29-106-131:~$Thank you. We are checking.Dev Notes: From investigation,Command stuck hereadmin@ncs% request devices fetch-ssh-host-keysadmin@ncs% request devices device rfs-1 connectNext,admin@nso-172-29-106-132:/etc/ncs$ sudo ufw statusStatus: activeTo       Action  From2244      ALLOW  Anywhere22/tcp      ALLOW  Anywhere2244 (v6)     ALLOW  Anywhere (v6)22/tcp (v6)    ALLOW  Anywhere (v6)Customer did not open firewall port for 2022 and 2024We opened those ports on RFS 1From Linh Ly,Able to connect to rfs1 from cfs after open 2022/2024 port on RFS1admin@ncs> request devices device rfs-1 ssh fetch-host-keysresult updatedfingerprint {algorithm ssh-ed25519value 2d:46:b1:ae:4f:a2:06:6f:4a:e8:f8:b9:a0:2a:02:a3}admin@ncs> request devices device rfs-1 sync-fromresult trueRFS 2 ports need to be opened as well:sudo ufw allow from any to any port <port-number> proto tcpAfter opening ports, Cluster is UPadmin@ncs% run show cluster                RECEIVEDNAME NAME     STATUS LAST EVENT     NOTIFICATIONS-------------------------------------------------------------------------------rfs-1 device-notifications up  0000-01-01T00:00:00-00:00 0  ncs-events   up  0000-01-01T00:00:00-00:00 0rfs-2REMOTE         LOCAL REMOTENODE ADDRESS   PORT CHANNELS USER USER STATUS TRACE-------------------------------------------------------------------------rfs-2  2022 -   admin admin down disabledrfs-1  2022 -   admin admin up  disabledThanks Janaki for checking the issue, allowed 2022 port on RFS2 firewall and now the cluster status showing fine for RFS1 and RFS2.admin@ncs% run show cluster                                RECEIVEDNAME  NAME         STATUS LAST EVENT         NOTIFICATIONS-------------------------------------------------------------------------------rfs-1 device-notifications up   0000-01-01T00:00:00-00:00 0    ncs-events      up   0000-01-01T00:00:00-00:00 0rfs-2 device-notifications up   0000-01-01T00:00:00-00:00 0    ncs-events      up   0000-01-01T00:00:00-00:00 0REMOTE                 LOCAL REMOTENODE  ADDRESS     PORT CHANNELS USER  USER  STATUS TRACE-------------------------------------------------------------------------rfs-2  172.29.106.133 2022 -     admin admin  up   disabledrfs-1  172.29.106.132 2022 -     admin admin  up   disabledThank you, closing ticket.Regards,Janaki DuggiralaCustomer did not open firewall port for 2022 and 2024.Assisted customer with enabling ports.Cluster came up successfully.Below command used for allowing the netconf on NSO-VMsudo ufw allow from any to any port 2022 proto tcp