Chapter 11: Troubleshooting
154
Solving Miscellaneous Issues
This section presents issues and provides solutions for a variety of driver
software issues.
Problem: Although installed, the Broadcom Advanced Control Suite 3
(BACS) application does not start and an error message appears.
Solution: NET Framework 2.0 is required for BACS 3 to operate. Install
.NET Framework 2.0.
Problem: Broadcom Advanced Control Suite 3 takes a long time to start
up.
Solution: This is a limitation of .NET Framework 2.0. Apply .NET
Framework 2.0 SP1 and reboot your system.
Problem: The Broadcom NetXtreme II adapter may not perform at optimal
levels on some systems if it is added after the system has booted.
Solution: The system BIOS in some systems does not set the cache line
size and the latency timer if the adapter is added after the system has
booted. Reboot the system after the adapter has been added.
Problem: Intelligent Platform Management Interface (IPMI) is not
functioning properly.
Solution: IPMI works only when LiveLink™ is disabled. See “Configuring
LiveLink for a Smart Load Balancing and Failover and SLB (Auto-Fallback
Disable) Team” in the Broadcom Advanced Control Suite 3 User Guide.
Problem: Cannot configure Resource Reservations in BACS 3 after SNP
is uninstalled.
Solution: Reinstall SNP. Prior to uninstalling SNP from the system,
ensure that NDIS is enabled via the checkbox on the Resource
Configuration screen, available from the Resource Reservations section of
the Configurations tab (see Viewing Resource Reservations in the
Broadcom Advanced Control Suite 3 User Guide). If NDIS is disabled and
SNP is removed, there is no access to re-enable the device.
Problem: TOE performance is more susceptible to packet loss when flow
control is disabled.
Solution: Enable flow control to reduce the number of packets lost.
Problem: A DCOM error message (event ID 10016) appears in the
System Even Log during the installation of the Broadcom adapter drivers.