Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme II Network Adapt - Page 222

Troubleshooting: Broadcom NetXtreme II Network Adapter User Guide 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 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. Solution: If a team member supports underlying management software (ASF/IPMI/UMP) or Wake-On-LAN, the link may be maintained on the switch for the adapter despite its driver being disabled. This may result in the switch continuing to pass traffic to the attached port rather than route the traffic to an active team member port. Disconnecting the disabled adapter from the switch will allow traffic to resume to the other active team members. Problem: Large Send Offload (LSO) and Checksum Offload are not working on my 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. Problem: The advanced properties of a team do not change after changing the advanced properties of an adapter that is a member of the team. Solution: If an adapter is included as a member of a team and you change any advanced property, then you must rebuild the team to ensure that the team's advanced properties are properly set. Problem: The TOE offload capabilities of a team do not change after removing the TOE key from an adapter that is a member of the team. Solution: If an adapter with a TOE key is included as a member of a team and you remove the TOE key, then you must rebuild the team to ensure that the team does not appear to be TOE-enabled. Linux Problem: On kernels older than 2.6.16 when 16 partitions are created on a server containing two BCM57711 network adapters, not all partitions would come up and an error indicating a shortage of space would display. Solution: On architectures where the default vmalloc size is relatively small and not sufficient to load many interfaces, use vmalloc= during boot to increase the size. file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/trouble.htm[9/26/2012 3:30:19 PM]