Users Guide

18–Troubleshooting
QLASP
298 BC0054508-00 M
Problem: Adding an Network Load Balancing-enabled BCM57xx and BCM57xxx
adapter to a team may cause unpredictable results.
Solution: Prior to creating the team, unbind Network Load Balancing from the
BCM57xx and BCM57xxx adapter, create the team, and then bind Network Load
Balancing to the team.
Problem: A system containing an 802.3ad team causes a Netlogon service failure
in the system event log and prevents it from communicating with the domain
controller during boot up.
Solution: Microsoft Knowledge Base Article 326152
(http://support.microsoft.com/kb/326152/en-us
) indicates that Gigabit Ethernet
(GbE) adapters may experience problems with connectivity to a domain controller
due to link fluctuation while the driver initializes and negotiates link with the
network infrastructure. The link negotiation is further affected when the GbE
adapters are participating in an 802.3ad team due to the additional negotiation
with a switch required for this team type. As suggested in the preceding
Knowledge Base Article, disabling media sense as described in a separate
Knowledge Base Article 938449 (http://support.microsoft.com/kb/938449
) has
shown to be a valid workaround when this problem occurs.
Problem: The 802.3ad team member links disconnect and reconnect
continuously (applies to all operating systems).
Solution: This problem is a third-party issue. It is seen only when configuring an
802.3ad team with more than two members on the server and connecting an
HP2524 switch, with LACP enabled as passive or active. The HP switch shows an
LACP channel being brought up successfully with only two team members. All
other team member links disconnect and reconnect. This problem does not occur
with a Cisco Catalyst 6500.
Problem: A generic trunking (GEC/FEC) 802.3ad-draft static type of team may
lose some network connectivity if the driver to a team member is disabled.
Solution: If a team member supports underlying management software (ASF or
UMP) or wake on LAN, the link may be maintained on the switch for the adapter
despite its driver being disabled. This link may result in the switch continuing to
pass traffic to the attached port rather than route the traffic to an active team
member port. Disconnect the disabled adapter from the switch to allow traffic to
resume to the other active team members.
Problem: Large send offload (LSO) and checksum offload are not working on a
team.
Solution: If one of the adapters on a team does not support LSO, LSO does not
function for the team. Remove the adapter that does not support LSO from the
team, or replace it with one that does. The same applies to checksum offload.