Versions Compared

Old Version 5

changes.mady.by.user yihui wang

Saved on

compared with

New Version 6

changes.mady.by.user yihui wang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

this document is used to guide how to install the OVS-DPDK into SmartNIC and integrate it with the server

Deployment Architecture

The following diagram shows the physical configuration between the BlueField SmartNIC and the ConnectX-5 6 NIC. 

Image Removed

yihui wang change the image information

Image Added

Pre-Installation Requirements

...

Minimum Hardware Requirements


2x86 servers running CentOS 8.2

 Intel(R) Xeon(R) Gold 5115 CPU @ 2.40GHz/ 20 cores / 2 numa / 64G memory

Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz/ 12 cores/ 2 numa / 32G memory

1ConnectX-6 Dx NIC (FW: 22.29.1016) -
1BlueField2 25GbE SmartNIC with Arm processor (FW: 24.29.1016) ARM A72  8 cores / single numa / 16G memory/ 25G bandwidth
 125GB/s SFP28 networking cable -
 1QSA28 Adapter (100GB-to-25GB Adapter) -
 1UART-to-USB cableFor SmartNIC USB console access 
 1Mini USB Type B cableFor SmartNIC USB Console Access
 1bfb image to be loaded on the BlueField SmartNIC Arm. Image contains:
  • CentOS 7.6 over Arm architecture
  • MLNX_OFED_LINUX-5.2-1.0.4 (compiled with DPDK and BlueField flags)
  • DPDK libraries version 20.11
  • Pre-configured network settings for easy SmartNIC management
  1. Insert ConnectX-6 NIC into Server A
  2. Insert BlueField SmartNIC into Server B
  3. Connect the SmartNIC UART cable from SmartNIC to its hosting Server B USB port #1
  4. Connect Mini USB cable from SmartNIC to its hosting Server B USB port #2
  5. Insert QSA28 Adapter into Server B 100GB port
  6. Connect one of the SmartNIC ports to the ConnectX-6 using 25GB cable
  7. Connect both servers to a management LAN

...

  1. Use automatic FM update during MLNX_OFED installation ONLY if the current BlueField FW version is 1824.24.1000 (GA) o29.1016 or above. In case its older, manually burn the FW after MLNX_OFED installation.
  2. In case you plan to run DPDK on the host itself, install MLNX_OFED with "--dpdk --upstream-libs" flags
  3. The "BlueField" flag is not required in some of the MLNX_OFED versions and OS releases

OVS-DPDK

  1. In R3, We've open-sourced a fork of DPDK based Open vSwitch, which supports the VXLAN decap/encap full offload: https://github.com/bytedance/ovs-dpdk, and In R4, we used the Mellanox version which is in the process of open source
  2. The code is fully compatible with upstream Open vSwitch, you can follow the same procedures to build them from the source. See the link: http://docs.openvswitch.org/en/latest/intro/install/
  3. Or you can use the ansible scripts in the Akaino Gerrit to install both BlueField BlueField2 Card and OVS-DPDK. Currently, the scripts are not available, as the scripts work by relying on many company's internal services. We are refactoring the code that you can use it in your own SmartNIC setups.

...

  1. Use an automatic FM update during MLNX_OFED installation ONLY if the current BlueField BlueField2 FW version is 18is 24.24.1000 (GA) 29.1016 or above. In case its older, manually burn the FW after MLNX_OFED installation.
  2. In case you plan to run DPDK on the host itself, install MLNX_OFED with "--dpdk --upstream-libs" flags
  3. The "BlueField" flag is not required in some of the MLNX_OFED versions and OS releases

...

           To manage the SmartNIC from the hosting server, use one of the following methods yihui wang change the 8.2

Image AddedImage Removed
Access Credentials: root\centos

...

In this mode, the x86 hosting server communicates with the outer world only through the SmartNIC Arm. yihui wang change CX5 TO CX6 DX


Image AddedImage Removed


Note

In order to identify the SmartNIC current mode, issue the following commands on the x86 hosting server:

...