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

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
LVL 7
RomoloIT Pro, Projects, Mentor, TrainerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Soulja53 6F 75 6C 6A 61 Commented:
Are you asking if the HYPERV server will route traffic between it's two NICs?
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Soulja53 6F 75 6C 6A 61 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.
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Soulja53 6F 75 6C 6A 61 Commented:
If you are familiar with windows server, probably be easiest to install a windows server vm are use it's routing services.
0
Soulja53 6F 75 6C 6A 61 Commented:
Monowall is a good option if you want to go the virtual firewall/router direction.
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
If both networks are connected to the host you could multihome the VM. Just add a NIC and connect it to the other subnet.
0
Soulja53 6F 75 6C 6A 61 Commented:
@Jeremy

That is the prereq in order for the monowall or windows vm with routing services to work.
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Right, but why add the router if you can just multihome the VM that needs to communicate and it's only a temporary setup?
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Soulja53 6F 75 6C 6A 61 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.
0
Soulja53 6F 75 6C 6A 61 Commented:
Once you know longer need the routing in place, just shut down the VM.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Soulja53 6F 75 6C 6A 61 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.
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
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?
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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.
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
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.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
ArneLoviusCommented:
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.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Hey All,

Please advise on this.

Thanks

R
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
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.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
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.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
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
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Yes that fine.. all that I expect.
Thanks

R
0
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
No problem. :)
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor 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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.