2012 R2 Networking
Hi,
We are a small/medium business and are currently migrating from a mixed 2003/2003r2/2008r2 environment to a full 2012r2 environment. This is my first time working with server 2012 of any flavor. This will also be the first time we have instituted VMs in our server environment. We will be upgrading multiple servers, but I will give the example of 1 for the sake of this post. I will be configuring the server like this:
Install Server 2012r2 with the Hyper-V role
Create 2 VMs to run over it (DC and File server)
Server has 4 physical 1GB Ethernet ports, I plan to team the 4 ports
For each VM I will create a virtual ethernet adapter and statically assign those for the servers that the VMs represent.
With the above in mind?
1. I feel that I should statically assign the NIC team to be able to access the server like we would normally do, is this correct or am I missing something?
2. Anything in the above approach that seems wrong or out of place?
3. Have I missed anything?
4. General thoughts?
Thanks in advance!
We are a small/medium business and are currently migrating from a mixed 2003/2003r2/2008r2 environment to a full 2012r2 environment. This is my first time working with server 2012 of any flavor. This will also be the first time we have instituted VMs in our server environment. We will be upgrading multiple servers, but I will give the example of 1 for the sake of this post. I will be configuring the server like this:
Install Server 2012r2 with the Hyper-V role
Create 2 VMs to run over it (DC and File server)
Server has 4 physical 1GB Ethernet ports, I plan to team the 4 ports
For each VM I will create a virtual ethernet adapter and statically assign those for the servers that the VMs represent.
With the above in mind?
1. I feel that I should statically assign the NIC team to be able to access the server like we would normally do, is this correct or am I missing something?
2. Anything in the above approach that seems wrong or out of place?
3. Have I missed anything?
4. General thoughts?
Thanks in advance!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cliff,
I'm not sure I follow. Do you have a specific example? Are you referring to QOS and min/max bandwidth usage or something deeper?
Thanks.
I'm not sure I follow. Do you have a specific example? Are you referring to QOS and min/max bandwidth usage or something deeper?
Thanks.
Server has 4 physical 1GB Ethernet ports, I plan to team the 4 ports Depends upon the manufacturer of the NIC's, Intel NIC's work fine, Broadcom NIC's are buggy.
A fair bit deeper. Enough that I can't even begin to sum it up in a response. Hyper-V networking is easy to mess up. I'd encourage you to buy a book and read the networking chapters before proceeding. Aidan Finn has a good book (and a food blog to follow) as a food starting point.
You mention that you will have multiple servers and that you will be installing Hyper-V on all of them. Will each of these servers run as a standalone server or is there some kind of backend infrastructure? What about storage/networking components? It's not just a question about teaming yes/no since there are different types of teaming also which depend on the backend network setup and the HA requirements.
ASKER
After doing a little more research, I found that I do need to delve a little deeper. Thanks.
Good Luck!