Introduction

BlueField's Ethernet SmartNIC solutions combine Arm® processing power with advanced network offloads to accelerate a multitude of security, networking and storage applications.
Based on the BlueField system-on-chip (SoC) programmable network engine, BlueField SmartNICs integrate Mellanox ConnectX®-5 network controller with Arm multicore processors and cryptology options to deliver an innovative and high-performance programmable platform.Through this article you will be able to quickly set up a simple test lab which will allow you to experiment and explore BlueField SmartNIC capabilities. The setup includes a bare metal server hosting BlueField 25GbE SmartNIC connected back-to-back to another bare metal server with ConnectX-5 NIC.

License

N/A

How to use this document

N/A

Deployment Architecture

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

Pre-Installation Requirements

Minimum Hardware Requirements

1. Insert ConnectX-5 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-5 using 25GB cable
7. Connect both servers to a management LAN

Recommended Hardware Requirements

NA

• Schema scriptsNA

• Jump Host RequirementsNA

• Network RequirementsNA

• Bare Metal Node RequirementsNA

• Execution Requirements (Bare Metal Only)NA

• • Hardware RequirementsNA

  • Software Prerequisites

    • MLNX_OFED

    • Note

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

  • Database PrerequisitesNA

  • Other Installation RequirementsNA

  •    Installation High-Level Overview      

    • SmartNIC Server Preparations

      • Install useful packages:

        yum install -y screen minicom net-tools tcpdump usbutils net-utils sshpass iptables-services fio epel-release iperf wget git unzip perl pciutils lsof tcl libxml2-python tk unbound gtk2 atk cairo gcc-gfortran tcsh nvme-cli

          

      • Install MLNX_OFED with the mentioned flags below.

        tar -xzvf MLNX_OFED_LINUX-4.4-2.5.11.0-rhel7.5-x86_64.tgz cd MLNX_OFED_LINUX-4.4-2.5.11.0-rhel7.5-x86_64 ./mlnxofedinstall --with-nvmf --bluefield --without-fw-update

            Note

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

      • 
        

         Enable SR-IOV on FW (Optional):

        mlxconfig -y -d /dev/mst/mt41682_pciconf0 s SRIOV_EN=1 mlxconfig -y -d /dev/mst/mt41682_pciconf0 s NUM_OF_VFS=8

      • Uncomment the following line in /etc/modprobe.d/rshim.conf to set the default RShim access method to the SmartNIC:

        options rshim backend_driver=rshim_usb

        
        

        Note

        1. When this line is commented, the first available driver will be used.
        2. When the mini USB cable is not used, the driver should be rshim_pcie

        
        

      • Create a file named ifcfg-tmfifo_net0 under /etc/sysconfig/network-scripts/ directory, with the following content:

        NAME="tmfifo_net0" HWADDR="00:1a:ca:ff:ff:02" ONBOOT=yes NETBOOT=yes IPV6INIT=yes BOOTPROTO=static TYPE=Ethernet IPADDR=192.168.100.1 NETMASK=255.255.255.0

          

      • ifcfg-tmfifo_net0 is the network interface used for IP communication between the x86 host and the SmartNIC with rshim_net driver.

      • Enable ip forwarding and set a NAT rule to allow the SmartNIC OS to communicate with the outer world via the host management interface:

        sysctl -w net.ipv4.ip_forward=1 systemctl enable iptables systemctl start iptables iptables -F iptables -t nat -A POSTROUTING -o <host_mgmt_interfac> -j MASQUERADE service iptables save

      • Disable Firewall and Network Manager services

        systemctl disable firewalld.service systemctl disable NetworkManager

      • Reboot the server. Once server is up again, run some configuration sanity tests:
        

        To verify BlueField FW version:

        mlxfwmanager --query

         To verify RShim modules are loaded:

        lsmod | grep -i rshim

        To identify the backend active RShim driver:

        cat /dev/rshim0/misc

        To verify the NAT rule for SmartNIC communication with the outer world:

        iptables -L -n -t nat

Download the BlueField Quick Start bfb image:  https://mellanox.box.com/s/q44f501xq1e29yb1bjpsb9vzgqs89a76

Place the bfb image on the host and load it on the BlueField SmartNIC using the following command:

                                             Use one of the console access methods described in the "SmartNIC Management Methods" section below to follow the image installation process.

                                             When bfb image installation process is completed, connect to the SmartNIC with the console or SSH, as described below, and test connectivity from the SmarNIC OS to the outer world.

•           SmartNIC Management Methods 

                       To manage the SmartNIC from the hosting server, use one of the following methods.

Access Credentials: root\centos

Console over USB-Serial / Serial Port properties: Rate 115200, HW Flow Control OFF.

Console over USB (rshim_usb) / Serial Port properties: Rate 115200, HW Flow Control OFF

minicom -D /dev/rshim0/console

SSH (rshim_net)

                     Note
                           SmartNIC OS is configured to obtain internet access via its hosting server.

•  Basic SmartNIC Management Operations

How-to soft reset the SmartNIC via host server:

Issue the following command on the server:

Follow the boot process using console access:

Note

This is not a power cycle of the SmartNIC.

  How-to load BlueField SmartNIC OS image from hosting server:

Place bfb image on the server

Issue the following command on the server:

Follow the installation and boot process using the console access:

•  SmartNIC Modes

BlueField SmartNIC can operate in two modes:

SEPERATED_HOST (default mode)

In this mode, both the x86 hosting server and the SmartNIC Arm OS act as separated entities; Both can use and communicate with each other or the network via the ConnectX-5 module of the SmartNIC.

EMBEDDED

In this mode, the x86 hosting server communicates with the outer world only through the SmartNIC Arm.

Note

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

Switching to EMBEDDED Mode from SEPERATED_HOST Mode

On the x86 host:

Enable EMBEDDED mode:

 Reboot.

Verify:

On the Arm:

Issue the following commands to enable ECPF parameters (applied per port):

Note
The ECPF parameters will be available for setting only after completing the previous steps.

Reboot the x86 host.

Verify configuration:

Once the procedure is completed, issue the following command on both the x86 host and the Arm:

 
On x86 host: the output should list two net devices.

 
On Arm: the output should list four representors:

Issue the following commands on the Arm to see the correlation between PCI device and its representors:

Note
The rep0-0 / rep1-0 are the representors facing the x86 host and the rep0-ffff / rep1-ffff are the representors facing the network.

Switching to SEPERATED_HOST Mode from EMBEDDED Mode

On the x86 host:

Enable SEPERATED_HOST mode:

Reboot.

Verify:

Testing Traffic in EMBEDDED Mode using DPDK

In Embedded mode, traffic from the x86 server hosting the SmartNIC to the remote x86 server hosting the ConnectX-5 is going via the SmartNIC Arm.

DPDK application is used to forward the traffic and bypass Arm OS kernel. Follow the configuration steps below to test it.

On the Arm

Stop OVS:

Verify hugetlbfs is mounted:

if not, mount it:

Set Hugepages:

Verify hugepages were allocated (look for HugePages_Total and Free):

Identify the SmartNIC PCI device ID:

Start testPMD application  while probing the representors  (pci device is 03:00.0):

Set IPs on both x86 host and ConnectX-5 host and test connectivity with ping (it will be forwarded by the Arm DPDK)

On the ConnectX-5 external host start iperf server:

On the x86 host, start iperf client:

While the test is running, you can check traffic statistics on Arm testPMD:

• • • • Install Bare Metal Jump HostNA

      • Creating a Node Inventory FileNA

      • Creating the Settings FilesNA

      • RunningNA

  • Bare Metal Deployment GuideNA

  • Virtual Deployment Guide

    • Standard Deployment OverviewNA

    • Snapshot Deployment OverviewNA

    • Special Requirements for Virtual DeploymentsNA

    • Install Jump HostNA

    • Verifying the Setup - VMsNA

• • Upstream Deployment Guide

  • • Upstream Deployment Key FeaturesNA

    • Special Requirements for Upstream Deployments

  •            NA 

    • Scenarios and Deploy Settings for Upstream DeploymentsNA

    • Including Upstream Patches with DeploymentNA

    • RunningNA

    • Interacting with Containerized OvercloudNA

• Verifying the Setup as defined the Akraino validation feature project plus any additional testing specific to the blue printNA

• Developer Guide and Troubleshooting

• Utilization of ImagesNA

• Post-deployment ConfigurationNA

• Debugging FailuresNA

• Reporting a BugNA

• Uninstall GuideNA

• Troubleshooting

• Error Message GuideNA

• Maintenance

  • Blue Print Package Maintenance

    • Software maintenance
•                                    NA 
  • • Hardware maintenance
•                                    NA
  • Blue Print Deployment Maintenance
•                        NA

• Frequently Asked Questions

•             NA

• License

•            NA

• References

•            NA

• Definitions, acronyms and abbreviations/* End of Template */

•            NA