Microsoft virtualization with hyper-v, Single network adapter – Dell Broadcom NetXtreme Family of Adapters User Manual
Page 258
Troubleshooting: Broadcom NetXtreme II® Network Adapter User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtremeII/English/trouble.htm[9/5/2014 3:45:23 PM]
From the command line, type ping IP address, and then press ENTER.
The ping statistics that are displayed indicate whether or not the network connection is working.
Microsoft Virtualization with Hyper-V
Microsoft Virtualization is a hypervisor virtualization system for Windows Server 2008 and Windows Server 2008 R2. This
section is intended for those who are familiar with Hyper-V, and it addresses issues that affect the configuration of
NetXtreme II network adapters and teamed network adapters when Hyper-V is used. For more information on Hyper-V, see
http://www.microsoft.com/windowsserver2008/en/us/hyperv.aspx.
identifies Hyper-V supported features that are configurable for NetXtreme II network adapters. This table is not an all-
inclusive list of Hyper-V features.
Table 1: Configurable Network Adapter Hyper-V Features
Feature
Supported in Windows
Server
Comments/Limitation
2008
2008 R2
2012
IPv4
Yes
Yes
Yes
–
IPv6
Yes
Yes
Yes
–
IPv4 Large Send Offload (LSO) (parent and child
partition)
Yes
Yes
Yes
–
IPv4 Checksum Offload (CO) (parent and child
partition)
Yes
Yes
Yes
–
IPv4 TCP Offload Engine (TOE)
No*
No*
No*
*OS limitation.
IPv6 LSO (parent and child partition)
No*
Yes
Yes
*When bound to a virtual network, OS
limitation.
IPv6 CO (parent and child partition)
No*
Yes
Yes
*When bound to a virtual network, OS
limitation.
IPv6 TOE
No
No
No
OS limitation.
Jumbo frames
No*
Yes
Yes
*OS limitation.
RSS
No*
No*
Yes
*OS limitation.
RSC
No*
No*
Yes
*OS limitation.
SRIOV
No*
No*
Yes
*OS limitation.
NOTE: Ensure that Integrated Services, which is a component of Hyper-V, is installed in the guest operating system (child
partition) for full functionality.
Single Network Adapter
Windows Server 2008
When configuring a NetXtreme II network adapter on a Hyper-V system, be aware of the following:
An adapter that is to be bound to a virtual network should not be configured for VLAN tagging through the driver's
advanced properties. Instead, Hyper-V should manage VLAN tagging exclusively.
Since Hyper-V does not support Jumbo Frames, it is recommended that this feature not be used or connectivity issues
may occur with the child partition.
The Locally Administered Address (LAA) set by Hyper-V takes precedence over the address set in the adapter's
advanced properties.
A TOE-enabled network adapter that is bound to a Hyper-V virtual network will report TOE as an offload capability in
BACS; however, TOE will not work. This is a limitation of Hyper-V. Hyper-V does not support TOE.
In an IPv6 network, a team that supports CO and/or LSO and is bound to a Hyper-V virtual network will report CO and
LSO as an offload capability in BACS; however, CO and LSO will not work. This is a limitation of Hyper-V. Hyper-V does
not support CO and LSO in an IPv6 network.