Notice: Choose a passphrase of 8 or more characters. To ensure the authenticity of the peering relationship, use a phrase or sequence of characters that would be hard to guess.
Enter the passphrase: Confirm the passphrase:
Error: command failed: Using peer-address 18.104.22.168: An introductory RPC to the peer address "10.10.10.11" failed to connect: RPC: Remote system error - No route to host. Verify that the peer address is correct and try again.
Network configuration on main site is:
cluster1::> network interface show -role intercluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ---------- ---------- ------------------ ------------- ------- ---- cluster1 cluster1-n1_bck up/up 172.16.1.45/24 cluster1-n1 a1b-20 true cluster1-n1_glbbck1 up/up 22.214.171.124/25 cluster1-n1 a1a-10 true cluster1-n2_bck up/up 172.16.1.48/24 cluster1-n2 a2b-20 true cluster1-n2_glbbck1 up/up 126.96.36.199/25 cluster1-n2 a2a-10 true cluster1-n3_bck up/up 172.16.1.64/24 cluster1-n3 a3b-20 true cluster1-n3_glbbck1 up/up 188.8.131.52/25 cluster1-n3 a3a-10 true cluster1-n4_bck up/up 172.16.1.65/24 cluster1-n4 a4b-20 true cluster1-n4_glbbck1 up/up 184.108.40.206/25 cluster1-n4 a4a-10 true 8 entries were displayed.
I am not able to create a cluster peer because all the IP's are in Default IP space and if that is the case, how can i solve it.
I'd say, "No route to host" is pretty self-explanatory. You need route to remote network (and remote network needs route to local site). It can be default gateway or it can be network/host specific route, but this is standard IP connectivity, nothing specific to cluster peering or cDOT in general.
I am not able to create a cluster peer because all the IP's are in Default IP space
So far there is no indication it is related to IP space. You may need different IP space if different destinations with the same IP addresses are reachable via different gateways. But there is not enough information to speculate about it.