Hyper V Host - Two subnets - migration.. How to configure NIC's for Location A and then to move to Location B

Romolo
Romolo used Ask the Experts™
on
I am building a server in location A 192.168.x and it will be used to migrate servers onto this as a HyperV host with several VMs doing the work of original physical servers.

The server will then be transported to a different location B 10.0.X and will be where it lives from now on permanently.

My question is:

I want my Server to be able to communicate with 192.168.X so that I can copy data from servers and establish certain roles for SQL servers etc.. and migrate items over but I want the VM's to be tied to the location B network.

What would be the best way to do this so that:

1) it works
2) No performance issues when I move to Location B.

Happy to do a little rework on the Host but not lots.

So potentially I could have on the host:

NIC 1 - 192.168.X so it can communicate with servers and Internet services whilst I get the environment ready.
NIC 2 - 10.0.X configured (however unused until the move and point my VM's to this on a V Switch.

However, will the Host automatically allow traffic to flow for Internet and other servers on NIC 1 without any special setup?

I can see there are lots on this, but they do not answer it for me.. or rather I do not fully understand that they deliver 100% when viewing the posts.
So looking for a simple to the point steps for my scenario.

I have 1 new server (will be Hyper Visor - got 2016 on it now).. Waiting before I build VM's etc...  Will be DC, SQL, Files, DNS etc...
5 other servers to migrate data and db's from etc...

Later 2 switches available at Location A.

Many thanks everyone

R
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
SouljaSr.Net.Eng
Top Expert 2011

Commented:
Are you asking if the HYPERV server will route traffic between it's two NICs?
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
Yes I am...

So when I move the server from Location A to Location B.. all will work and I just need to change IP on NIC1 which I will reserve for the host only

Thanks

R
SouljaSr.Net.Eng
Top Expert 2011

Commented:
I don't believe HyperV itself will route between the nic, but I am pretty positive you could install a virtual router, or window server to perform the routing you are looking for.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
As this is a temporary setup.. what would be the best way forward as it will no longer be required after 2 weeks?

Thanks

R
SouljaSr.Net.Eng
Top Expert 2011

Commented:
If you are familiar with windows server, probably be easiest to install a windows server vm are use it's routing services.
SouljaSr.Net.Eng
Top Expert 2011

Commented:
Monowall is a good option if you want to go the virtual firewall/router direction.
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
If both networks are connected to the host you could multihome the VM. Just add a NIC and connect it to the other subnet.
SouljaSr.Net.Eng
Top Expert 2011

Commented:
@Jeremy

That is the prereq in order for the monowall or windows vm with routing services to work.
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
Right, but why add the router if you can just multihome the VM that needs to communicate and it's only a temporary setup?
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
Well the end result will be

1 host and maybe 4 VMs

And I don't need the routing after 2 weeks..... so I want to go with best option for the server after this in its permanent location B.

So I don't want anything lasting

It really it temp migration and 2nd NIC will NOT be connected unless I plug it into a switch just so it lights up :)

R
SouljaSr.Net.Eng
Top Expert 2011

Commented:
@jeremy

The router is the VM.  The original intent of the author was to try and do this directly with the HyperV host.  Adding a VM that routes is what I stated in my initial comment.
SouljaSr.Net.Eng
Top Expert 2011

Commented:
Once you know longer need the routing in place, just shut down the VM.
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
hmm ok...

so you suggest HyperVHost on NIC1 conforming to 192.168.X

HyperVGuests on NIC2 10.0.X (disconnected)

And then run a VM to route between the NICs?

Thanks

R
SouljaSr.Net.Eng
Top Expert 2011

Commented:
No, I am suggesting a VM that has vnics tied to each of your host's physical nics, but yes, it would route between the two subnets for you.
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
Where will the host be physically? At the destination site or somewhere else?

What will the connectivity setup be between Site A and Site B?
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
end result will be server in location A.. for 2 weeks migrating data and services. NO connectivity to location B as it is not needed. but I can set something up if necessary.

When at location B ... total move, and no connection to location A as it's a close down of the site.

hence I want a temporary solution that disappears in 2 weeks and does not suffer performance in location B as this is permanent rest place.

so 1 physical nic for host NOT in a vswitch. 4 additional NICs one tied to each VM as vswitch separately?

AND would i still need the routing VM? trying to keep the solution simple and temporary.

thanks everyone... it's an urgent behind schedule project with a solid deadline, so really appreciate your guidance.
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
If that's the case, then just configure the NICs for location A. After two week when they're moved, reconfigure the NICs for location B. No need to complicate things.
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
hey

that means I would need to reconfigure IPs on all the VMs meaning services such as DNS, DC etc...
this can cause issues so would rather not go down this road.

hence the routing between networks.
the routing is purely so it works on both locations. not because I need to route between for 2 weeks.

I am avoiding reconfiguring after 2 weeks.

please advise.

R
If there is DHCP at both locations, I would use DHCP to set the address at each location for the initial setup, and set to static is required later.
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
But will this not screw up the VMs as their services will be bound to a different subnet when I move to Location B>

Thanks

R
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
Hey All,

Please advise on this.

Thanks

R
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
If you have DNS and use it to resolve the IP then there will be no problem. If you are pointing applications to the IP address then you'll need to reconfigure them after you update the IP address. I don't really see any way around it without setting up some unnecessary complexity.
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
I thought this would have been easier than it seems to be.

I think I will just build on the Subnet A 192.168.X and change the Location B (Final Destination) to the 192.168.x range as this is a possibility. Just wanted to avoid this.

R
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
Can you not use the fqdn instead of the IP address when connecting to the services? If you use the fqdn, then you just update the IP and DNS and your all set.
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
Yes sure... I totally understand that. Just thought I might come into issues changing servers from 192.168.1.1 to 10.0.0.1 ... figured there was going to be issues here.
Please confirm I will not... services will be DHCP, DNS, DC, SQL, possible Exchange.

R
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
Yeah, shouldn't be an issue. A few steps for a DC. Will have to update the DHCP settings. Everything else should be good.

DC steps: https://www.petri.com/change-ip-address-domain-controller
RomoloIT Pro, Projects, Mentor, Trainer

Author

Commented:
Yes that fine.. all that I expect.
Thanks

R
Jeremy WeisingerSenior Network Consultant / Engineer

Commented:
No problem. :)
IT Pro, Projects, Mentor, Trainer
Commented:
I have chose not to undertake any further routing etc... Just will keep in one location and change destinations IP network.

Thanks everyone, however, not undertaking any of the solutions so I don't think I can award points.

Thanks

R

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial