Dell Broadcom NetXtreme Family of Adapters - Manual (Page 166)

Troubleshooting: Broadcom NetXtreme BCM57XX User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtreme/English/trouble.htm[9/5/2014 3:32:22 PM]
OemPnpDriversPath=Drivers\Video;Drivers\Net
The Sysprep utility must run with the –pnp switch, which enables the system to rescan for new devices that can be added
during the mini-setup.
A Sample Sysprep.inf file for Windows XP is shown below.
------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\Windows
UnattendedInstall=Yes
OemPnpDriversPath=Drivers\Net
[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=99
OEMSkipRegional=1
OEMDuplicatorstring="XP System"
TimeZone=4
OemSkipWelcome=1
[UserData]
FullName="User"
OrgName="Organization"
ComputerName=*
[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=whistlerdist
[Identification]
JoinDomain=workgroup
[Networking]
InstallDefaultComponents=Yes
------------------------------------------------------------------------
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: 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 more than 2 members on the
system and connecting to an HP2524 switch, with LACP enabled as passive or active. The HP switch shows an LACP channel
being brought up successfully with only 2 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: The teaming changes I made when I modified my team using INETCFG did not take effect.
Solution: When you modify a team using INETCFG, you may need to reboot after reinitialization for the changes to the team
to take effect.
Kernel Debugging over Ethernet
Problem: When attempting to perform kernel debugging over an Ethernet network on a Windows 8.0 or Windows Server
2012 system, the system will not boot. This problem may occur with some adapters on systems where the Windows 8.0 or
Windows Server 2012 OS is configured for UEFI mode. You may see a firmware error on screen, indicating that a Non