Looks like you created a single node cluster from that node. And then, offcourse, you cannot use that node in another cluster. 

ssh into that cvm on the node (the NEW NODE) and type:

1. cluster stop
2. cluster destroy

That that node is not part of the single node cluster and you can use it in the other cluster. 

​@JeroenTielen 

I tried that, but still getting the same error 


 

I know you can type in the cvm ip during manual discovery. But have you tried it with the ahv (hypervisor) ip as well? So your 172.19.14.43

And are the current nodes (in the working cluster) in the same vlan and subnet? And can those talk to the new node ips? (Your screenshot shows ping from a ubuntu machine and not from the working nodes)

​@JeroenTielen 

172.19.14.43, 53 both are reachable

root@bootnode ~]# ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.14.43  netmask 255.255.255.0  broadcast 172.19.14.255
        ether b4:96:9182:36  txqueuelen 1000  (Ethernet)
        RX packets 208272  bytes 29197363 (27.8 MiB)
        RX errors 0  dropped 28  overruns 0  frame 0
        TX packets 159332  bytes 106151624 (101.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


rroot@bootnode ~]# cat /etc/os-release
NAME="Nutanix AHV"
VERSION="el8.nutanix.20230302.102001"
ID="ahv"
ID_LIKE="centos rhel fedora"
# Plymouth uses '(' to know when PRETTY_NAME ends. Dracut appends a version to PRETTY_NAME when
#   generating its os-release. Without this extra parenthesized name, Plymouth would not display
#   simply 'AHV'
PRETTY_NAME="AHV (Acropolis Hypervisor)"
ANSI_COLOR="0;32"
HOME_URL="https://www.nutanix.com/"
SUPPORT_URL="https://portal.nutanix.com/"
Rroot@bootnode ~]# 


admin@NTNX-74HR6X3-A-CVM:172.19.14.44:~$ ping 172.19.14.43
PING 172.19.14.43 (172.19.14.43) 56(84) bytes of data.
64 bytes from 172.19.14.43: icmp_seq=1 ttl=64 time=0.480 ms
64 bytes from 172.19.14.43: icmp_seq=2 ttl=64 time=0.095 ms
64 bytes from 172.19.14.43: icmp_seq=3 ttl=64 time=0.088 ms
^C
--- 172.19.14.43 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2026ms
rtt min/avg/max/mdev = 0.088/0.221/0.480/0.183 ms
admin@NTNX-74HR6X3-A-CVM:172.19.14.44:~$

 

admin@NTNX-74HR6X3-A-CVM:172.19.14.44:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.14.44  netmask 255.255.255.0  broadcast 172.19.14.255
        inet6 fe80::5054:ff:fe91:878e  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:91:87:8e  txqueuelen 1000  (Ethernet)
        RX packets 111933696  bytes 32372464532 (30.1 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 114589773  bytes 68537546129 (63.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.14.46  netmask 255.255.255.255  broadcast 172.19.255.255
        ether 52:54:00:91:87:8e  txqueuelen 1000  (Ethernet)

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.5.2  netmask 255.255.255.128  broadcast 192.168.5.127
        inet6 fe80::5054:ff:fef8:fb61  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:f8:fb:61  txqueuelen 1000  (Ethernet)
        RX packets 3278871  bytes 35744534219 (33.2 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2670574  bytes 15731975563 (14.6 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


 

All nodes are Dell Poweredge R760


 

Hello ​@Magesh_Kumar_S 
During the re-image or the node deployment you have created a new cluster.

You need to check this option during the cluster extension :
 

​@LMohammed / ​@JeroenTielen 

‘Skip automatic cluster formation’ WORKED.  thanks a lot.  I appreciate that.

Now to automate this whole process, Now I have 2 questions


Also, what’s the foundation VM API ( or if there is something better) to create the initial cluster? , fyi, we used foundation VM UI to create the initial cluster.

To expand an existing cluster, what’s the best way to image and configure a node using a REST API (Prism API?), and eventually include this node into an existing cluster? (expanding cluster).?  fyi, we used Prism UI to expand the cluster, 

The API calls you have to develop yourself. Here is a good starting point with the information: https://www.nutanix.dev

For example Foundation: https://www.nutanix.dev/api_reference/apis/foundation.html#section/Foundation/Terminology