Объединение двух сетевых карт в одну windows server 2008 r2

Hi,

We have some discussion about Microsoft Support Policy for NIC Teaming with Hyper-V in Windows Server 2008 or Windows Server 2008 R2.

Technically, you can use NIC teaming with Hyper-V in Windows Server 2008 or Windows Server 2008 R2. But since Network Adapter Teaming is only provided by Hardware Vendors in these server OS, Microsoft does not provide any support for this technology
thru Microsoft Product Support Services. As a result, Microsoft may ask that you temporarily disable or remove Network Adapter Teaming software when troubleshooting issues where the teaming software is suspect.

If the problem is resolved by the removal of Network Adapter Teaming software, then further assistance must be obtained thru the Hardware Vendor.

So in Windows server 2008 or 2008 R2, you can use NIC teaming with Hyper-V. But in case the configuration encounters some issues or questions, we should remove NIC teaming for troubleshooting.

Windows Server 2012 has built-in network teaming feature, you can use it with Hyper-V.

> how many NICS should be teamed? I have 4 NICS, what would be the best recommendation on Teaming?

If you are going to configure a Hyper-V cluster, you may refer to following MS articles:

Hyper-V: Live Migration Network Configuration Guide
http://technet.microsoft.com/en-us/library/ff428137(v=WS.10).aspx

For more information please refer to following MS articles:

Microsoft Support Policy for NIC Teaming with Hyper-V
http://support.microsoft.com/kb/968703
NIC Teaming Overview
http://technet.microsoft.com/en-us/library/hh831648.aspx

Lawrence

TechNet Community Support

• Marked as answer by

  Thursday, March 21, 2013 8:34 AM

Hi,

you should first install Hyper-V, reboot, install the NIC Teaming Software and create the Team(s), then create the external Adapter which the Virtual Machines should use.

In Server 2008 (R2), you need to use the NIC Teaming Software of your Hardware Vendor, for example HP is providing the «HP Network Configuration Utility».

For best availability of a standalone (not clustered) Host, create two teams with each two Adapters. One Team for the Virtual Machines, one for the management of the physical Server.

Best Regards,

Jens

• Marked as answer by
  Lawrence,Lu
  Thursday, March 21, 2013 8:34 AM

Hi,

> I have 4 NICS, what would be the best recommendation on Teaming

4 identical 1Gbps NICs?

Since you mentioned this is a standalone server, so you don’t need to consider network bandwidth for Live Migration and Storage (one question forest to ask, does the Hyper-V server use built-in disk or external storage?)

I think it’s better to give more resources for production, so you may create a 3 NICs teaming for Hyper-V guest VMs, use the last NIC for management. In case the management network down, it doesn’t harm guest VM, and you can connect to the Hyper-V host on
site.

For the 3 NICs teaming you can also configure “Allow management operating system to share the network adapter”. This option setting controls whether you can use this physical network adapter to access to the management operating system, which
is operating system that runs the Hyper-V role. Uncheck this option; you isolate the management operating system from communications between virtual machines and other computers on a physical network

For more information please refer to following MS articles;

Hyper-V: Live Migration Network Configuration Guide
http://technet.microsoft.com/en-us/library/ff428137(v=WS.10).aspx
Virtual Network Manager
http://technet.microsoft.com/en-us/library/cc754263.aspx

Lawrence

TechNet Community Support

• Marked as answer by
  Lawrence,Lu
  Thursday, March 21, 2013 8:34 AM

Hi,

We have some discussion about Microsoft Support Policy for NIC Teaming with Hyper-V in Windows Server 2008 or Windows Server 2008 R2.

Technically, you can use NIC teaming with Hyper-V in Windows Server 2008 or Windows Server 2008 R2. But since Network Adapter Teaming is only provided by Hardware Vendors in these server OS, Microsoft does not provide any support for this technology
thru Microsoft Product Support Services. As a result, Microsoft may ask that you temporarily disable or remove Network Adapter Teaming software when troubleshooting issues where the teaming software is suspect.

If the problem is resolved by the removal of Network Adapter Teaming software, then further assistance must be obtained thru the Hardware Vendor.

So in Windows server 2008 or 2008 R2, you can use NIC teaming with Hyper-V. But in case the configuration encounters some issues or questions, we should remove NIC teaming for troubleshooting.

Windows Server 2012 has built-in network teaming feature, you can use it with Hyper-V.

> how many NICS should be teamed? I have 4 NICS, what would be the best recommendation on Teaming?

If you are going to configure a Hyper-V cluster, you may refer to following MS articles:

Hyper-V: Live Migration Network Configuration Guide
http://technet.microsoft.com/en-us/library/ff428137(v=WS.10).aspx

For more information please refer to following MS articles:

Microsoft Support Policy for NIC Teaming with Hyper-V
http://support.microsoft.com/kb/968703
NIC Teaming Overview
http://technet.microsoft.com/en-us/library/hh831648.aspx

Lawrence

TechNet Community Support

• Marked as answer by

  Thursday, March 21, 2013 8:34 AM

Hi,

you should first install Hyper-V, reboot, install the NIC Teaming Software and create the Team(s), then create the external Adapter which the Virtual Machines should use.

In Server 2008 (R2), you need to use the NIC Teaming Software of your Hardware Vendor, for example HP is providing the «HP Network Configuration Utility».

For best availability of a standalone (not clustered) Host, create two teams with each two Adapters. One Team for the Virtual Machines, one for the management of the physical Server.

Best Regards,

Jens

• Marked as answer by
  Lawrence,Lu
  Thursday, March 21, 2013 8:34 AM

Hi,

> I have 4 NICS, what would be the best recommendation on Teaming

4 identical 1Gbps NICs?

Since you mentioned this is a standalone server, so you don’t need to consider network bandwidth for Live Migration and Storage (one question forest to ask, does the Hyper-V server use built-in disk or external storage?)

I think it’s better to give more resources for production, so you may create a 3 NICs teaming for Hyper-V guest VMs, use the last NIC for management. In case the management network down, it doesn’t harm guest VM, and you can connect to the Hyper-V host on
site.

For the 3 NICs teaming you can also configure “Allow management operating system to share the network adapter”. This option setting controls whether you can use this physical network adapter to access to the management operating system, which
is operating system that runs the Hyper-V role. Uncheck this option; you isolate the management operating system from communications between virtual machines and other computers on a physical network

For more information please refer to following MS articles;

Hyper-V: Live Migration Network Configuration Guide
http://technet.microsoft.com/en-us/library/ff428137(v=WS.10).aspx
Virtual Network Manager
http://technet.microsoft.com/en-us/library/cc754263.aspx

Lawrence

TechNet Community Support

• Marked as answer by
  Lawrence,Lu
  Thursday, March 21, 2013 8:34 AM

Добрый день.

Статические маршруты настроить не пробовали.

Route add ip mask metric

Я не волшебник, я только учусь MCTS Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции работодателя. Вся информация предоставляется как есть без каких-либо гарантий Мой Блог http://www.ru-technet.com/

• Предложено в качестве ответа

  17 февраля 2015 г. 10:51

• Помечено в качестве ответа
  Petko KrushevMicrosoft contingent staff
  27 февраля 2015 г. 8:03

только маршрутов мало, надо еще в подсетях шлюзы выставить на серверные адреса…

… и route add команда будет чуть иначе выглядеть … и заканчиваться -р для запоминания

• Помечено в качестве ответа
  Petko KrushevMicrosoft contingent staff
  27 февраля 2015 г. 8:03