Hello....everything I have read, has stated that multiple phyiscal NICS in a hyper-v host, is a good idea. Spread the VM's over the physical NICs. I got off the phone with MS yesterday(overseas, keep in mind), and they tell me that it is not necessary. Quite frankly, they were not helpful in the least bit, and this is support for which you pay.
Scenario:
Remote office, physical host running hyper-v. Multiple VM's on this host, one of which, is the remote office's DC(which is running DHCP)
What is confusing to me is how to configure(do you give them static ip addresses?) the PHYSICAL nics on the host machine. At first, I did not give them IP addressing. I then thought I was doing it wrong, and I gave each physical nic a static IP(bad idea). When I created a VM, I bound the vm to one of the virtual NIC's, and gave the VM a static ip address. The confusing part, is when I did an IPCONFIG, on the VM, I see the static address I assigned, but I also see a 169.x.x.x address added to an adapter as well. I thought MAYBE I did something wrong creating the VM, so I did another one, and it turned out exactly the same.
I then decided to REMOVE the static IP addresses from the physical NICs on the VM Host and set them back to DHCP(and the IP addressing is grayed out, but there IS a Default gateway show, although not editable).
Here's the confusing part to me.....the VM's were now working just fine, when I do an ipconfig on the VM I only see the static address assigned to each VM, BUT the physical NICs are getting DHCP addresses now from the VM which is running as a DC/DHCP.
Is this normal? HOW are the PHYSICAL nics supposed to be configured(if at all) on a hyper-v host? Are they supposed to get an IP address? If so, should it be static or DHCP?
To add insult to injury, the last physical NIC on my machine is attached to a upstream router(I am running ISA as a VM). THAT nic, I did not assign it ANY ip address, but the ISA is getting out to the internet just fine.
Very confusing, very frustrating and little, clear, step-by-step documentation. Calling MS was even more frustrating by getting someone saying "let me research this answer...." or "it depends on how you want to configure it..."
Does ANYONE have a clear, concise answer?
VMware isn't this difficult.
Scenario:
Remote office, physical host running hyper-v. Multiple VM's on this host, one of which, is the remote office's DC(which is running DHCP)
What is confusing to me is how to configure(do you give them static ip addresses?) the PHYSICAL nics on the host machine. At first, I did not give them IP addressing. I then thought I was doing it wrong, and I gave each physical nic a static IP(bad idea). When I created a VM, I bound the vm to one of the virtual NIC's, and gave the VM a static ip address. The confusing part, is when I did an IPCONFIG, on the VM, I see the static address I assigned, but I also see a 169.x.x.x address added to an adapter as well. I thought MAYBE I did something wrong creating the VM, so I did another one, and it turned out exactly the same.
I then decided to REMOVE the static IP addresses from the physical NICs on the VM Host and set them back to DHCP(and the IP addressing is grayed out, but there IS a Default gateway show, although not editable).
Here's the confusing part to me.....the VM's were now working just fine, when I do an ipconfig on the VM I only see the static address assigned to each VM, BUT the physical NICs are getting DHCP addresses now from the VM which is running as a DC/DHCP.
Is this normal? HOW are the PHYSICAL nics supposed to be configured(if at all) on a hyper-v host? Are they supposed to get an IP address? If so, should it be static or DHCP?
To add insult to injury, the last physical NIC on my machine is attached to a upstream router(I am running ISA as a VM). THAT nic, I did not assign it ANY ip address, but the ISA is getting out to the internet just fine.
Very confusing, very frustrating and little, clear, step-by-step documentation. Calling MS was even more frustrating by getting someone saying "let me research this answer...." or "it depends on how you want to configure it..."
Does ANYONE have a clear, concise answer?
VMware isn't this difficult.
