HYPER-V AND NETWORK CARDS

Semua Balasan

• 04 Mei 2012 1:46

  Moderator

   

   
  

  0
  Hi,
  
  General speaking, it is recommended that you dedicate one physical network adapter for Hyper-V host management. Then you can use one or more physical network adapters for virtual machines(External Virtual Network).
  
  I am not an active directory professional, however, as far as I know, it is recommended that you only use one network adapter on a domain controller.
  
  In your environment, you can create one External Virtual Network bind to one physical network adapter, and attach all your domain controller virtual machines to the same External Virtual Network, you can also create different External Virtual Networks bind to different physical network adapters, then attach different domain controller virtual machines different External Virtual Networks.
  
  By the way, if there is only one physical machine for your test, you can create Internal Virtual Netowrk or Private Virtual Network for the virtual machines.
  
  
  
  • Balas
  • Kutip

   
• 04 Mei 2012 4:33

   

   
  

  0

  Hi!

  This depends on whether you need the domains to be separated or isolated.

  If they need to be isolated and lead them out to physical clients that recieve IP addresses through DHCP from each domain, then you should consider adding a physical network card for each domain, create external virtual networks for each and connect them to their own switches. If all testing will be done in your virtual environment, then you can create private virtual networks instead like Vincent suggested.

  If they only need to be separated, you should be able to connect them to the same external virtual network, but configured with different IP ranges.

  Note: You might want to double check about putting multiple domains on the same net in an active direcotry forum before doing so.
  
  

  • Diedit oleh Mike_Andrews 04 Mei 2012 5:50
  •  
  • Balas
  • Kutip

   
• 04 Mei 2012 12:12

   

   
  

  0

  thanks for the replies guys.

  I dont want two domains (DCs) in the same subnet as this will cause complication with DHCP etc. I want two subnets with a domain (DC) in each subnet.

  I can then setup sites in AD and child domains etc. So it will be a multiple domain \ multiple site configuration.

  I understand this concept perfectly in terms of physical hardware i just cannot get my head round it in a virtual environment.

  It just seems a bit strange how its looking like each VM will need its own physical NIC. This is almost (but not quite) defeating the object of virtualisation!

  the hyper-v machine will not be a member of any of the domains i create, it is just a hyper-v box much like an ESX box would sit there and do nothing more than host VMs.

  Any other advice would be much appreciated.

  Thanks

  • Balas
  • Kutip

   
• 04 Mei 2012 13:06

   

   
  

  0

  ok . . i have been reading up on the network types in hyper-v and i think this may have answered my question.

  Each external virtual network i setup will require its own physical NIC. This means if i want to create two subnets / sites / domains i am going to need three physical NICs in the hyper-v server. One NIC for the hyper-v server and a NIC for domain A and a NIC for domain B.

  Unless i can do it with internal virtual networks?

  • Balas
  • Kutip

   
• 04 Mei 2012 13:11

   

   
  

  0

  Internal virtual networks connects the host to the virtual networks as well. For pure and isolated VM networking, you should use private virtual networks.

  internal and private virtual networks can not be bound to physical adapters, and will therefor not be able to communicate with your physical LAN. 

  • Balas
  • Kutip

   
• 04 Mei 2012 13:24

   

   
  

  0

  i am not bothered about the VMs being able to communicate with the physical LAN as its only a lab. But what i do want is to be able to communicate between internal virtual networks. For example -

  if i create internal virtual network A and internal virtual network B this will mean i have created two virtual switches. My VMs then connect to the correct respective virtual switch BUT my question is . . will i be able to route from a VM in internal virtual network A to a VM in internal virtual network B?

  • Balas
  • Kutip

   
• 04 Mei 2012 13:35

   

   
  

  0
  Yes, if you add two NICs in the settings of a VM and connect them to each network, that VM can then be configured to act as router. No other connection exists between the two virtual switches.
  • Balas
  • Kutip

   
• 04 Mei 2012 13:56

   

   
  

  0
  so add a third VM with two NICs? Virtual NICs i presume?
  • Balas
  • Kutip

   
• 04 Mei 2012 13:58

   

   
  

  0
  Yes, virtual NIC's.
  • Balas
  • Kutip

   
• 04 Mei 2012 14:33

   

   
  

  0
  and one more question :) virtual NICs can be added without the need for physical NICs? So if i only have a single NIC in the hyper-v server can i still add numerous virtual NICs?
  • Balas
  • Kutip

   
• 04 Mei 2012 15:31

   

   
  

  0
  Yes, if memory serves me right, you can add up to 12 virtual NICs on a virtual machine, 8 network adapters and 4 legacy network adapters. Then you connect them to the desired virtual networks you've created... or not at all.

  • Ditandai sebagai Jawaban oleh hyperNoddy 04 Mei 2012 15:41
  •  
  • Balas
  • Kutip

   
• 04 Mei 2012 15:41

   

   
  

  0

  perfect thank you very much, my question is now answered!

  Thanks for all the help!

  • Balas
  • Kutip