Versions Compared

Key

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

...

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

minicom -D /dev/ttyUSB0

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

                            

minicom -D /dev/rshim0/console

SSH (rshim_net)

ssh root@192.168.100.2

  

...

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:

 echo "SW_RESET 1" > /dev/rshim0/misc


Follow the boot process using console access:

minicom -D /dev/ttyUSB0

  

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:

 cat <image>.bfb > /dev/rshim0/boot


Follow the installation and boot process using the console access:

minicom -D /dev/ttyUSB0

  

...

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.


Image Modified

Note

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

x86_host#mst start
x86_host#mlxconfig -d /dev/mst/mt41682_pciconf0 q | grep -i model


Switching to EMBEDDED Mode from SEPERATED_HOST Mode

On the x86 host:

Enable EMBEDDED mode:

x86_host #mst start
x86_host #mlxconfig -d /dev/mst/mt41682_pciconf0 s INTERNAL_CPU_MODEL=1


 Reboot.


Verify:

x86_host#mst start
x86_host#mlxconfig -d /dev/mst/mt41682_pciconf0 q | grep -i model


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.

  

Snic#mst start
Snic#mst status -v
Snic#mlxconfig -d /dev/mst/mt41682_pciconf0 s ECPF_ESWITCH_MANAGER=1 ECPF_PAGE_SUPPLIER=1
Snic#mlxconfig -d /dev/mst/mt41682_pciconf0.1 s ECPF_ESWITCH_MANAGER=1 ECPF_PAGE_SUPPLIER=1

  

Reboot the x86 host.

Verify configuration:

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

/opt/mellanox/iproute2/sbin/rdma link

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

1/1: mlx5_0/1: state ACTIVE physical_state LINK_UP netdev ens1f0
2/1: mlx5_1/1: state DOWN physical_state DISABLED netdev ens1f1

 
On Arm: the output should list four representors:

1/1: mlx5_0/1: state ACTIVE physical_state LINK_UP netdev rep0-ffff
2/1: mlx5_1/1: state ACTIVE physical_state LINK_UP netdev rep0-0
3/1: mlx5_2/1: state DOWN physical_state DISABLED netdev rep1-ffff
4/1: mlx5_3/1: state DOWN physical_state DISABLED netdev rep1-0

  

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

mst start
mst status -v
 
 
PCI devices:
------------
DEVICE_TYPE MST PCI RDMA NET NUMA
BlueField(rev:0) NA 03:00.1 mlx5_3,mlx5_2 net-eth2,net-rep1-ffff -1
BlueField(rev:0) NA 03:00.0 mlx5_1,mlx5_0 net-rep0-ffff,net-eth1 -1


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:

x86_host #mst start
x86_host #mlxconfig -d /dev/mst/mt41682_pciconf0 s INTERNAL_CPU_MODEL=0


Reboot.

Verify:

x86_host#mst start
x86_host#mlxconfig -d /dev/mst/mt41682_pciconf0 q | grep -i model


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:

systemctl stop openvswitch


Verify hugetlbfs is mounted:

mount | grep -i hugetlbfs

if not, mount it:

mount -t hugetlbfs nodev /dev/hugepages


Set Hugepages:

echo 4 > /sys/kernel/mm/hugepages/hugepages-524288kB/nr_hugepages


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

cat /proc/meminfo | grep -i huge


Identify the SmartNIC PCI device ID:

lspci | grep -i mellanox


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

cd /usr/bin/
./testpmd -w 03:00.0,representor=[0,65535] – -i
testpmd> start


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:

iperf -s


On the x86 host, start iperf client:

iperf -c 172.16.0.2 -P12


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

testpmd> show port stats all


Install Bare Metal Jump Host

...

N/A

Creating a Node Inventory File

...

N/A

Creating the Settings Files

...

N/A

Running

...

N/A

Bare Metal Deployment Guide

...

N/A

Virtual Deployment Guide

N/A

Standard Deployment Overview

...

N/A

Snapshot Deployment Overview

...

N/A

Special Requirements for Virtual Deployments

...

N/A

Install Jump Host

...

N/A

Verifying the Setup - VMsNA

Upstream Deployment Guide

Upstream Deployment Key Features

...

N/A

Special Requirements for Upstream Deployments

...

N/A 

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