Npar, Kernel debugging over ethernet, Miscellaneous – Dell Broadcom NetXtreme Family of Adapters User Manual
Page 263
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]
NPAR
Problem: The following error message displays if the storage configurations are not consistent for all four ports of the device
in NPAR mode:
PXE-M1234: NPAR block contains invalid configuration during boot.
A software defect can cause the system to be unable to BFS boot to an iSCSI or FCoE target if an iSCSI personality is enabled
on the first partition of one port, whereas an FCoE personality is enabled on the first partition of another port. The MBA driver
performs a check for this configuration and prompts the user when it is found.
Solution: If using the 7.6.x firmware and driver, to workaround this error, configure the NPAR block such that if iSCSI or
FCoE is enabled on the first partition, the same must be enabled on all partitions of all four ports of that device.
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
Maskable Interrupt exception was encountered during the UEFI pre-boot environment.
Solution: Refer to the Microsoft knowledge base topic number 2920163, "
Miscellaneous
Problem: The BCM57810 10 GbE NIC does not support 10 Gbps or 1 Gbps WOL link speed.
Solution: The BCM57810 10 GbE NIC can only support 100 Mbps WOL link speed due to power consumption limitations.
Problem: When setting the Jumbo MTU property to 5000 bytes or greater and forcing Flow Control on network adapters
that support a link speed of 10 Gbps, the system performance performs at less than optimal levels.
Solution: If Jumbo MTU is set to 5000 bytes or greater, ensure that Flow Control is set to Auto.
Problem: iSCSI Crash Dump is not working in Windows.
Solution: After upgrading the device drivers using the installer, the iSCSI crash dump driver is also upgraded, and iSCSI
Crash Dump must be re-enabled from the Advanced section of the BACS Configuration tab.
Problem: In Windows Server 2008 R2, if the OS is running as an iSCSI boot OS, the VolMgr error, "The system could not
successfully load the crash dump driver," appears in the event log.
Solution: Enable iSCSI Crash Dump from the Advanced section of the BACS Configuration tab.
Problem: The Broadcom NetXtreme II adapter may not perform at optimal level 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: Cannot configure Resource Reservations in BACS 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
Configuring Resource Reservations
). If NDIS is disabled and SNP is removed, there is no access to re-enable the device.
Problem: The TOE status in the Vital Sign area of the BACS Information tab is inconsistent with the TOE status in the
Resource Reservations tab when the TOE key is physically removed.
Solution: Reinstall the TOE key and navigate to the Resource Configuration screen from the Resource Reservations tab.
Disable TOE from the Resource Configuration screen prior to removing the TOE key. The TOE status should be consistent in
both the Vital Sign tab and the Resource Reservations tab.
Problem: TOE performance is more susceptible to packet loss when flow control is disabled.