Solved

Xtract, converstion from ESX Static to AHV Static doesn't work, end up with DHCP VM

  • 16 March 2018
  • 2 replies
  • 769 views

Badge +3
First, we had to do something a bit different from the main design of Xtract, we had to dual home the applliance so we had one nic connected to our ESX console network and the other to our CVM network. I've made the proper changes to iptables and all, it work fine, but we've noticed with a set of Windows 2016 servers we try to migrate which have STATIC IP addresses, after conversion, the IP's are dynamic.

Tried to seach the logs for for something but havent' found anything obvious. I will cut a ticket soon, but before I did, wanted to check to see if anyone else have run into this problem.

Thanks in advanced for any feedback or advice.

Alex
icon

Best answer by alexanderpy 23 March 2018, 02:27

Yes, cut a ticket and we worked it out. This was interesting, ended up being the iptables, even though we were dual homed and I duplicated the rules, when we disabled iptables it worked without a problem.

This wasn’t an issue since we own and isolate both the networks, having those limit/controls in place weren’t really needed.

Thanks for following up and thanks for reminding me to update this post, maybe it will benefit someone else that was in our crazy situation.

Alex
View original

2 replies

Userlevel 1
Badge +5
Hi Alex - did you open a Support ticket and manage to get this resolved?

Please do share the results if resolved, so others understand what fixed the issue. Thanks!
Badge +3
Yes, cut a ticket and we worked it out. This was interesting, ended up being the iptables, even though we were dual homed and I duplicated the rules, when we disabled iptables it worked without a problem.

This wasn’t an issue since we own and isolate both the networks, having those limit/controls in place weren’t really needed.

Thanks for following up and thanks for reminding me to update this post, maybe it will benefit someone else that was in our crazy situation.

Alex

Reply