[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Help configuring Hyper V to see two different subnets

Posted on 2013-06-24
8
Medium Priority
?
921 Views
Last Modified: 2016-11-24
My new Dell PE R270 sever has 4 NICs
We have two CISCO switches that use two VLANS.  

VLan10 ( for 169.2.71.x subnet) and VLan 100 (for 169.2.72.x subnet) whose ports are divided up between both switches.

The new Hyper V server will hold my DHCP server which serves up IPs to the 71 subnet for desktops as well as some scanning servers for the same subnet.

The other servers will be on the 72 subnet.

Will my host's NICs route the DHCP servers traffic or do i need to assign one of the NICs on the host a 71 address and then create a Hyper V virtual network and assign that NIC.  Then add the DHCP to that Virtual Network?

Or do i simply create a Hyper V Virtual Network as external and assign it any host NIC?

please advise
thanks
0
Comment
Question by:lgarza
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
8 Comments
 
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 39272920
DHCP is initiated by the client by broadcasting to all and then await a response so just using an configuring the dhcp virtual machine to external network and bind it to a network adapter.
0
 

Author Comment

by:lgarza
ID: 39272953
that is what I thought.  but, i get a 169.254.x.x ip on the newly created virtual.     never picks up an IP from my dhcp.
0
 
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 39273000
Have you told the DHCP virtual machine to use the proper VLAN?
You understand that a vlan is a method of having two networks use the same ip address range and be isolated from each other.
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:lgarza
ID: 39273031
No, I haven't.  Sorry, we have been on VM Ware, where I never needed to specify a VLAN ID.  So, "telling the DHCP virtual machine" is by typing in the VLAN ID when I configure the Hyper V virtual network?
0
 
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 39273038
you should probably set up a virtual network switch as well
http://blogs.msdn.com/b/adamfazio/archive/2008/11/14/understanding-hyper-v-vlans.aspx
0
 
LVL 20

Expert Comment

by:Svet Paperov
ID: 39273245
Configuring the network on Hyper-V is relatively easy task. However, I have to ask some questions:
- Why do you need DHCP on the Hyper-V host? First – DHCP is always a security risk, second – by adding an additional service to the host, you cannot use the free Windows Server licence for it (for example when you install Windows Server 2012 as a host, you are able to install 2 virtual machines, but you can't use your host for any other purpose but for virtualization)
- Do you need VLAN trunking over a single NIC or you will plug each NIC in its own IP subnet (no need of VLAN)?

The best design, in my opinion, will be:
- Put the host server in its own segment and in its own domain (or leave it as Workgroup): keep NIC 1 only for the management traffic to the host
- Set one of the virtual servers as DHCP and attach a virtual NIC in 169.2.71.x subnet: NIC 2
- Use NIC 3 to create a virtual NIC (virtual switch) for 169.2.72.x subnet and use it to the other servers (optionally, you can team NIC 3 and 4 and then create a virtual NIC to better performance)
- Disable “Allow management operating system to share this network adapter” on both virtual NICs
- You will need a router to route between both subnets and, eventually, the management one
No VLAN IDs are used in this scenario
0
 

Accepted Solution

by:
lgarza earned 0 total points
ID: 39285350
Solution:  Was to simply change the switch port i'm attached to from an access port to a trunk port.

I can now access both VLANs
0
 

Author Closing Comment

by:lgarza
ID: 39296012
this was  a self resolved issue.    i changed the cisco switch port to be a trunk port.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question