Configuring the IPU

Use this information to configure the packet processor (PP) on the FPGA of the IPU.

Before you begin

Make sure that you have:

Installed a Napatech IPU in a server. See Installing a Napatech IPU.
Programmed the IPU with an appropriate FPGA image. See Napatech Link-Security™ Software FPGA Images.
Remote SSH access to the SoC on the IPU via the management port or the USB Port. See DN-1385.
Installed required tools and built the kernel driver on the IPU. See Installing Napatech Link-Security™ Software on the IPU.

About this task

Note: The following prompt is used to indicate which part of the system to run the provided commands on.

soc#: The SoC on the IPU.

Procedure

On the IPU, initialize the packet processor (PP) on the FPGA.

soc# cd /opt/ipu_tools/bin
soc# ./csc_mngmt --dev 15:00.0 --flush --all
soc# ./csc_mngmt --dev 15:00.0 --sync
soc# ./csc_mngmt --dev 15:00.0 --ppcfg fastpath

An output example:

soc# ./csc_mngmt --dev 15:00.0 --flush --all
Turning on 'memory address space enable bit' in the PCIe command registern
soc# ./csc_mngmt --dev 15:00.0 --sync
soc# ./csc_mngmt --dev 15:00.0 --ppcfg fastpath
PP Fastpath Configuration was SUCCESSFUL!

The packet processor is configured to function as an L2 switch.

Note: If the following error messages are generated, reboot the IPU.

** Error: Unable to parse file '/var/csc-config.json'. Error code: 1003. Regenerating...
*** Error: Invalid Action Group Entry for Sys IF 0 Broadcast whilst trying to configure PP fastpath default config
*** Error: Invalid Action Group Entry for Sys IF 1 Broadcast whilst trying to configure PP fastpath default config
*** Error: Invalid Action Group Entry for Sys IF 0 Broadcast whilst trying to configure PP fastpath default config
*** Error: Invalid Action Group Entry for Sys IF 1 Broadcast whilst trying to configure PP fastpath default config
PP Fastpath Configuration contained at least one ERROR

After reboot, run the commands again.

soc# reboot

On the IPU, load the drivers.

soc# modprobe uio
soc# rmmod ifc_uio.ko 2>/dev/null
soc# cd /opt/ipu_tools/src/
soc# insmod ipu_mngmnt_tools/software/csc_lek-0.0.0.5/driver/kmod/ifc_uio.ko
soc# modprobe virtio_pci
soc# modprobe virtio_net

Verify that the virtio network devices are recognized as network interfaces.

For example:

soc# ip a

An output example:

…
…
3: ens6f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:7f brd ff:ff:ff:ff:ff:ff
    altname enp21s0f1
4: ens6f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:7e brd ff:ff:ff:ff:ff:ff
    altname enp21s0f2
5: ens6f4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:7c brd ff:ff:ff:ff:ff:ff
    altname enp21s0f4
6: ens6f5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:7b brd ff:ff:ff:ff:ff:ff
    altname enp21s0f5
7: ens6f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:7a brd ff:ff:ff:ff:ff:ff
    altname enp21s0f6
8: ens6f7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e8:ca:11:bf:79 brd ff:ff:ff:ff:ff:ff
    altname enp21s0f7

In the output example, 6 network interfaces for the virtio network devices of the IPU are presented.