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]
Upgrading Windows Operating Systems
This section covers Windows upgrades for the following:
From Windows Server 2003 to Windows Server 2008
From Windows Server 2008 to Windows Server 2008 R2
From Windows Server 2008 R2 to Windows Server 2012
Prior to performing an OS upgrade when a Broadcom NetXtreme II adapter is installed on your system, Broadcom
recommends the procedure below.
1. Save all team and adapter IP information.
2. Uninstall all Broadcom drivers using the installer.
3. Perform the Windows upgrade.
4. Reinstall the latest Broadcom adapter drivers and the BACS application.
Broadcom Boot Agent
Problem
: Unable to obtain network settings through DHCP using PXE.
Solution
: For proper operation make sure that the Spanning Tree Protocol (STP) is disabled or that portfast mode (for Cisco)
is enabled on the port to which the PXE client is connected. For instance, set spantree portfast 4/12 enable.
Broadcom Advanced Server Program (BASP)
Problem
: After physically removing a NIC that was part of a team and then rebooting, the team did not perform as
expected.
Solution
: To physically remove a teamed NIC from a system, you must first delete the NIC from the team. Not doing this
before shutting down could result in breaking the team on a subsequent reboot, which may result in unexpected team
behavior.
Problem
: After deleting a team that uses IPv6 addresses and then re-creating the team, the IPv6 addresses from the old
team are used for the re-created team.
Solution
: This is a third-party issue. To remove the old team's IPv6 addresses, locate the General tab for the team's TCP/IP
properties from your system's Network Connections. Either delete the old addresses and type in new IPv6 addresses or select
the option to automatically obtain IP addresses.
Problem
: Adding an NLB-enabled NetXtreme II adapter to a team may cause unpredictable results.
Solution
: Prior to creating the team, unbind NLB from the NetXtreme II adapter, create the team, and then bind NLB 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 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 Gigabit
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 Knowledge Base Article above, 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 is a third-party issue. It is seen only when configuring an 802.3ad team with greater 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 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.
