bnx2fc.rst 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. .. SPDX-License-Identifier: GPL-2.0
  2. ===========================
  3. Operating FCoE using bnx2fc
  4. ===========================
  5. Broadcom FCoE offload through bnx2fc is full stateful hardware offload that
  6. cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
  7. SCSI controllers. As such, FCoE functionality, once enabled is largely
  8. transparent. Devices discovered on the SAN will be registered and unregistered
  9. automatically with the upper storage layers.
  10. Despite the fact that the Broadcom's FCoE offload is fully offloaded, it does
  11. depend on the state of the network interfaces to operate. As such, the network
  12. interface (e.g. eth0) associated with the FCoE offload initiator must be 'up'.
  13. It is recommended that the network interfaces be configured to be brought up
  14. automatically at boot time.
  15. Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
  16. support the VLANs that have been discovered for FCoE operation (e.g.
  17. eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
  18. will be disrupted.
  19. Driver Usage Model:
  20. ===================
  21. 1. Ensure that fcoe-utils package is installed.
  22. 2. Configure the interfaces on which bnx2fc driver has to operate on.
  23. Here are the steps to configure:
  24. a. cd /etc/fcoe
  25. b. copy cfg-ethx to cfg-eth5 if FCoE has to be enabled on eth5.
  26. c. Repeat this for all the interfaces where FCoE has to be enabled.
  27. d. Edit all the cfg-eth files to set "no" for DCB_REQUIRED** field, and
  28. "yes" for AUTO_VLAN.
  29. e. Other configuration parameters should be left as default
  30. 3. Ensure that "bnx2fc" is in SUPPORTED_DRIVERS list in /etc/fcoe/config.
  31. 4. Start fcoe service. (service fcoe start). If Broadcom devices are present in
  32. the system, bnx2fc driver would automatically claim the interfaces, starts vlan
  33. discovery and log into the targets.
  34. 5. "Symbolic Name" in 'fcoeadm -i' output would display if bnx2fc has claimed
  35. the interface.
  36. Eg::
  37. [root@bh2 ~]# fcoeadm -i
  38. Description: NetXtreme II BCM57712 10 Gigabit Ethernet
  39. Revision: 01
  40. Manufacturer: Broadcom Corporation
  41. Serial Number: 0010186FD558
  42. Driver: bnx2x 1.70.00-0
  43. Number of Ports: 2
  44. Symbolic Name: bnx2fc v1.0.5 over eth5.4
  45. OS Device Name: host11
  46. Node Name: 0x10000010186FD559
  47. Port Name: 0x20000010186FD559
  48. FabricName: 0x2001000DECB3B681
  49. Speed: 10 Gbit
  50. Supported Speed: 10 Gbit
  51. MaxFrameSize: 2048
  52. FC-ID (Port ID): 0x0F0377
  53. State: Online
  54. 6. Verify the vlan discovery is performed by running ifconfig and notice
  55. <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
  56. Refer to fcoeadm manpage for more information on fcoeadm operations to
  57. create/destroy interfaces or to display lun/target information.
  58. NOTE
  59. ====
  60. ** Broadcom FCoE capable devices implement a DCBX/LLDP client on-chip. Only one
  61. LLDP client is allowed per interface. For proper operation all host software
  62. based DCBX/LLDP clients (e.g. lldpad) must be disabled. To disable lldpad on a
  63. given interface, run the following command::
  64. lldptool set-lldp -i <interface_name> adminStatus=disabled