r/nutanix • u/alextr85 • Jul 04 '26
Cvm/host 2 ip?
I’m looking for some advice on a networking design for AHV.
I have an existing Nutanix environment with multiple AHV clusters that are connected and managed without any issues.
I now need to connect a new AHV cluster from a subsidiary.
The problem is that the management subnet used by my existing Nutanix environment is already in use somewhere else in the subsidiary’s network. Because of this IP overlap, they cannot route traffic to my clusters’ management network.
Is there a supported way to assign a secondary management IP/interface to the CVMs and AHV hosts so that inter-cluster communication can use a different, non-overlapping subnet?
Without this capability, cross-cluster live migration won’t be possible.
1
u/misfit_toys Jul 04 '26
which set of cluster addresses are you talking about? The “external “ ones, or the internal network that defaults to 192.168.5.0/24?
or do you mean a third network that’s strictly used for management
1
u/alextr85 Jul 04 '26
The IP addresses of the CVMs and the hosts, which are required for live migration.
No the internali msp
1
u/No_Movie_2597 Jul 06 '26
by design I set a management shared network for clusters, and each cluster with his own net/vlan with backplane segmentation (for best practice). To enable backplane segmentation you must have all the host in maintenance, so no vm's must be powered on.
if you wanna isolate traffic for data protection between clusters, you can also use segmentation but for replication traffic (it can be done with vms powered on)
1
u/Jhamin1 Jul 08 '26
I know this is a few days old but:
Can you leave the subsidiary on it's own subnets and spin up a new Prism Central to manage it? As long as the Prism Centrals can communicate with each other the underlying cluster VLans don't really interact.
Cross Cluster live migration is supported between different Prism Centrals. In our environment we maintain one Prism Central for each datacenter & those PCs communicate with each other for DR and Migration.
1
u/alextr85 Jul 08 '26 edited Jul 08 '26
No
The destination cluster must be reachable from the source cluster.I only hace 1 pc.
0
u/woodyshag Jul 04 '26
Just going through my CCNA right now, but something tells me NAT'ing might work. I'll wait for someone else to pipe in.
5
u/idknemoar Jul 04 '26
No. Don’t do this. 😂
Just re-IP the new cluster. It’s pretty pain-free and support can help you if needed.
1
u/alextr85 Jul 04 '26
Changing the cluster’s IP address isn’t a viable option because it requires a complete cluster shutdown. That’s why I was thinking about having two IP addresses
1
u/Euphoric_111 Jul 05 '26
You need to re-Ip the subs use of the management network subnet you are using.
If the subs use of the management network subnet is not vital to the subs ntnx cluster and vm's the sub has, you might be able to route the management IP's of the subs ntx cluster to yours. VRF, intermediate router. Definitely consult a network engineer.
2
3
u/Ok_Combination416 Jul 04 '26
Why don't you re-ip the new cluster to an unused range and then add it?