HP ProLiant Networking Software Release Notes

For RHEL: # service lldpad restart
For SLES11: # rclldpad restart
11) Restart FCoE service to apply new settings.
For RHEL: # service fcoe restart
For SLES11: # rcfcoe restart
12) Check the installation to verify that the driver was correctly installed and that the host port is seen
by the switch.
A. Correct FCoE operation requires proper DCB connectivity.
Proper DCB sync and operational DCB can be confirmed through BACS, BACScli, or by visiting the
directly connected switch interface.
B. Run fcoeadm -i to see all created FCoE interfaces and their status.
If an FCoE interface is not present, then check that the operating system is configured to automatically
enable the required network interfaces.
Linux installation and configuration known issues
---------------------------------------------------
Memory considerations
The Broadcom bnx2x driver uses virtual memory for DMA operations. Normally, the driver requires a
virtual memory size of 8264 kB per physical function at the probe stage. At the open stage, the driver
requires more than 256 kB of virtual memory per physical function. On architectures that the default
vmalloc size is relatively small and not sufficient to load many interfaces, use vmalloc=<size> during boot
to increase the size.
A 32-bit Linux operating system has a limited amount of memory space available for kernel data
structures. You might need to decrease the amount of memory pre-allocated by the driver to use the
Broadcom bnx2x driver on such a platform. To decrease the memory, limit the number of RX queues
with the num_queues driver parameter, or limit the number of RX buffers for each queue with the
ethtool -G option.