run show cluster "NAME field is empty" in NSO: 1) Started installing Drop4 on NSO - LSA setup2) Installed two RFS with the procedure mentioned in the below link3) While creating CFS, we see that run show cluster command :so@ncs% run show cluster           LAST  RECEIVED    NAME  NAME STATUS EVENT NOTIFICATIONS -------------------------------------------rfs-1                   rfs-2                   REMOTE                 LOCAL REMOTE          NODE  ADDRESS    PORT CHANNELS USER  USER  STATUS TRACE   ------------------------------------------------------------------------rfs-2  10.56.116.153 2022 -     nso  nso   down  disabled rfs-1  10.56.116.152 2022 -     nso  nso   down  disabled tried : root@sareddyd-esxi-01-vm1:~# ssh nso@10.56.116.152 -p 2022The authenticity of host ':2022 (:2022)' can't be established.ED25519 key fingerprint is SHA256:ouHxfF8+vBaAqXyOnKIyOV7H8KHRCSmfyNTrhTMv0Gg.Are you sure you want to continue connecting (yes/no/)? yesWarning: Permanently added ':2022' (ED25519) to the list of known hosts.nso@10.56.116.152's password: Connection to 10.56.116.152 closed.but my ncs.conf : 2022 is enabled. 4) we dont have ./ nso-<NSO-VERSION><del>ron</del><RON-RELEASE-VERSION> /get_technical_support_data.sh. script in the folder, so not able to generate the logs.CFS: 10.56.116.151RFS-1: 10.56.116.152RFS-2: 10.56.116.153for above three VM's, creds: nso/Public1234!
Hi Sampath,I checked your LSA setup. The cluster is up finenso@ncs% run show cluster                           RECEIVEDNAME  NAME    STATUS LAST EVENT         NOTIFICATIONS---------------------------------------------------------------------rfs-1 ncs-events up   0000-01-01T00:00:00-00:00 0rfs-2 ncs-events up   0000-01-01T00:00:00-00:00 0REMOTE                 LOCAL REMOTENODE  ADDRESS    PORT CHANNELS USER  USER  STATUS TRACE------------------------------------------------------------------------rfs-2  10.56.116.153 2022 -     nso  nso   up   disabledrfs-1  10.56.116.152 2022 -     nso  nso   up   disabledAbout get_technical_support_data.sh, it is missing in the drop 4. It is fixed in the coming drop 5Thanks,LinhUpdate: Actually Van Pham did have a 1:1 with the reporter and fixed the issue. I am going to close the case.Van helped here, thanks