bnx2fc.txt 3.1 KB

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