Users Guide

19–Troubleshooting
Microsoft Virtualization with Hyper-V
286 BC0054508-00 J
Windows Server 2008 R2 and 2012
When configuring a BCM57xx and BCM57xxx network adapter on a Hyper-V
system, be aware of the following:
 An adapter that is to be bound to a virtual network must not be configured for
VLAN tagging through the driver’s advanced properties. Instead, Hyper-V
should manage VLAN tagging exclusively.
 The locally administered address (LAA) set by Hyper-V takes precedence
over the address set in the adapter’s advanced properties.
 The LSO and CO features in the guest OS are independent of the network
adapter properties.
 To allow jumbo frame functionality from the guest OS, both the network
adapter and the virtual adapter must have jumbo frames enabled. Set the
Jumbo MTU property for the network adapter to allow traffic of large MTU
from within the guest OS. Set the jumbo packet of the virtual adapter to
segment the sent and received packets.
Teamed Network Adapters
Table 19-2 identifies Hyper-V supported features that are configurable for
BCM57xx and BCM57xxx teamed network adapters. This table is not an
all-inclusive list of Hyper-V features.
Table 19-2. Configurable Teamed Network Adapter Hyper-V Features
Feature
Supported in Windows
Server Version
Comments and Limitations
2008
2008
R2
2012
and
Later
Smart Load Balancing and
Failover (SLB) team type
Yes Yes Yes Multimember SLB team allowed with
latest QLASP6 version.
NOTE: VM MAC is not presented to
external switches.
Link aggregation (IEEE
802.3ad LACP) team type
Yes Yes Yes —
Generic trunking (FEC/GEC)
802.3ad draft static team type
Yes Yes Yes —
Failover Yes Yes Yes —
LiveLink Yes Yes Yes —