Virtual land using hype-rv

My goal is to set up three of my existing servers in a virtual environment. They must have the exact same IPs they do in the real environment and yet not conflict with the production servers. They also need to have access to the Internet. Is there a way to set this up with hyper-V?
JohnMan777Asked:
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
How would you do this physically?  You'd do it the same way in Hyper-V.  

You're not saying if they need the same public IP, but you could just use a different public IP and then a separate NIC on the server.

Why must they have the same IPs?
JohnMan777Author Commented:
They must have the same IP address because this test environment is being set up to diagnose and active directory issue. The public IP doesn't matter. I would have to call the ISP to have another ip Assigned though.

The system does have a second Nic. How would this be set up? Do I build a VLAN?
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Set up a Private network in Hyper-V.

P2V or V2V your servers into VMs with vNICs connected to that Private network.

We use a 2008 R2 OS VM set up with RRAS and two vNICs as NAT for the private network to the production network/Internet. SOPHOS and Untangle are freebie products that can do similar.

In your case a VLAN should be set up in your switches to edge for a different subnet than your production network.

The "WAN" vNIC on your NAT VM should have its vNIC properties set to that VLAN with an IP on that subnet. That will allow traffic from the Private network to traverse the production network to the Internet.

Rules on the physical edge could be set up for inbound services with RRAS having inbound rules set up too.

We do the above for many labs and sandboxes for client projects.

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
JohnMan777Author Commented:
Phillip,

Setting up RRAS and programming the switches turns this into a bigger project than I was hoping for. I found an unused 2nd internet connection in the server room. If I used this for the public access, could this setup be simplified?

Thank you,

John
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
That makes it simple.

ISP --> Modem --> Edge --> Rules for IP --> Port # --> Cable --> Separate Switch

Team a couple of NIC ports on the host and plug them in to the above Separate Switch.

Create an External vSwitch in Hyper-V Management on those two ports.

P2V/V2V your servers into VMs with vNICs bound to that vSwitch.

Done.
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
Hyper-V

From novice to tech pro — start learning today.