background preloader

Networking

Facebook Twitter

Windows Server 2012 NIC Teaming Part 1 – Back To Basics. Last year I did a series of posts on converged fabrics.

Windows Server 2012 NIC Teaming Part 1 – Back To Basics

At the time, it was still early days and we had very little information from Microsoft in the public domain. A key piece of the puzzle is the NIC team. It’s clear that NIC teaming is confusing people. I’m seeing loads of questions about bandwidth not being used, concerns about architectures and so on. Hyper-V 3.0 and Converged Networks on 12th Generation Dell PowerEdge Servers. DCB, iSCSI, and Hyper-V 3.0 on Windows Server 2012 With the current trend toward converged data centers and networks, there are many new technologies in play that are driving, and at the same time, enabling storage and network convergence. 10 Gig Ethernet (10GbE), Data Center Bridging (DCB), and Network Partitioning (nPAR) are some underlying technologies that are combined with enabling features and functions like bandwidth shaping, Network Teaming, and Server and network virtualization.

Hyper-V 3.0 and Converged Networks on 12th Generation Dell PowerEdge Servers

Storage data encapsulation and transport protocols like iSCSI or Fibre Channel over Ethernet (FCoE) provide the storage interface that enables block level data to traverse Ethernet. These technologies, features, and functions work together to provide a comprehensive, fault-tolerant and resilient converged data center solution.

Hyper-V 3.0 - Hyper-v Network Virtualization on Windows 2012 - Can we use "Internal Network" Virtual Switch. Hi Mike, The aim of an external virtual switch is to allow the communication between your VMs, your Hyper-v host(s) and the rest of your LAN network.

Hyper-V 3.0 - Hyper-v Network Virtualization on Windows 2012 - Can we use "Internal Network" Virtual Switch

If you want that your virtual machines "talk" with your others computers / servers, you will have to create an external virtual switch with 1 or more NICs. If you only want to allow communication between your VMs and your Hyper-v host (running these VMs), you will have to create an internal virtual switch (it doesn't need to be binded to a NIC). Here is a link that will explain the virtual network under Hyper-v. Hyper-V 3.0 - Network Configuration Settings on Windows 2012.