Solved

Nutanix Default Internal Segment

  • 17 May 2016
  • 4 replies
  • 3932 views

Badge +3
Hi All,

I wonder is it possible to change the internal communication IP (192.168.5.x) to different network segment?
The reason being i have my existing server infra, all in 192.168.5.x segment.

Anyone have encounter similar case , can share some thoughts on this?

Thanks,
Jackie
icon

Best answer by PaulR 19 May 2016, 00:36

So far, there are a few ways to approach this. Each could be considered rather extreme.1) The first answer would be "no", Nutanix requires this address space for itself, per the Documentation.2) Adjust the existing server infra network segment.3) NAT the Hypervisor and Nutanix 192.168.5.x addresses to the broader network. Note: The existing server environment should not access the Hypervisor directly.There is internal discussion both pressing for the ability to adjust, and requesting other options for workaround. - Will let you know of any updates or more official statement(s).-Paul
View original

4 replies

Userlevel 7
Badge +35
Thanks for the question 

  you able to add anything to this?
Userlevel 3
Badge +17
So far, there are a few ways to approach this. Each could be considered rather extreme.1) The first answer would be "no", Nutanix requires this address space for itself, per the Documentation.2) Adjust the existing server infra network segment.3) NAT the Hypervisor and Nutanix 192.168.5.x addresses to the broader network. Note: The existing server environment should not access the Hypervisor directly.There is internal discussion both pressing for the ability to adjust, and requesting other options for workaround. - Will let you know of any updates or more official statement(s).-Paul
Badge +3
Thank you Paul for the reply.

I have open a ticket with support team, their reply as follows:

It is not possible to change the IP address of 192.168.5.x on Nutanix because this ip segment is widely use and hardcorded in nutanix file system.

And yes, the only work around will be changing the IP of existing Hosts.
VMs can be continue sitting on 192.168.5.x segment as long as they not crash with ip address for internal communication (192.168.5.1,192.168.5.2,&192.168.5.254) and a different port group (from which CVM locate) should be use for these VMs.

For my case, here is the work around i think of:
i have 4 host of Esxi, i changed the IP for one of the host to another segment where nutanix able to talk to and made it as a medium man for migration and so far everything works fine with minimal impact on existing setup.

It will be good if enduser can choose which segment to use for the internal communication, hopefully Nutanix can come out of something in future =)

Best Regards,
Jackie
Badge
Hi,
we've also had a DMZ in 192.168.5.0/24 but I rather changed the DMZ than Nutanix Configuration. Whenever you have to add a new host or re-install a node it might get problems. So that's my advice. cheers, Claudia

Reply