This How-To shows you how you configure the (Virtual) Network Adapters of the Hyper-V Servers. This is not really heavy, but to complete the UCS Hyper-V Guide I post this. If you use Microsoft System Center Virtual Machine Manager 2008 R2 you will find later a post about doing this in SCVMM 2008 R2.
- Connect to the Hyper-V Server with the Hyper-V Manager Console
- Now you can configure the Networks under Virtual Network Manager on each Hyper-V Host.
What we did is, we added 7 (Virtual) Network adapters to the UCS Bladenodes in the UCS Manager. We added the same on Configuration on the Blades which are using VMware ESXi and on the Blades with Microsoft Hyper-V and thats why we have a Network called vMotion on the Hyper-V Servers. We use the vMotion network adpater for the private Failover Cluster Heartbeat.
Basically we have the following Networks:
- 1. Network adapter is the Hyper-V Management Network dedicated to the Hyper-V Node
- 2. Network adpater for Hyper-V Cluster Live Migration
- 3. Network adapter for private Failover Cluster Heartbeat
- 4. Network adapter External Network, is used for our main external Network
- 5. Network adapter Internal Network, is used for our internal Management Network for Servers
- 6. and 7. Network adapters are used for VLAN Trunks
To get the best performance we don’t share any Network Adapter with the Hyper-V Host and a Virtual Network.Tags: Blade Center, Blade Server, Bladecenter, Cisco, Cisco Blade Center, Cisco UCS, ESXi, Hyper-V Cluster, Hyper-V Network Configuration, Microsoft, Microsoft Hyper-v, Microsoft Hyper-V 2008 R2, Network, Network Configuration, Networkadapters, Networking, UCS, UCS Blade Server, Virtual Network, Virtual Network Adapters, Virtual Network Manager, VMware Last modified: May 4, 2011