After reading through the documentation again, I learned I should only specify 
the NIC ports used in the UHD arguments in my conf file, I believe  this was 
able to resolve some of my issues, it still does not successfully begin the 
benchmarking. For example, if I specify 1 management_address/mgmt_addr and 1 
address/addr I get an error that says not devices could be found. However, the 
errors are slightly different depending on if I set the management address to 
either the QSFP port or the RJ-45.

In the scenario where I set the mgmt_addr to the QSFP port, I get an error that 
says no devices were found, but I also get the warning “No link entry in rx 
table”

`./benchmark_rate --rx_rate 491.52e6 --rx_channels 0 --tx_rate 491.52e6 
--tx_channels 0 --args 
"addr=192.168.10.2,mgmt_addr=192.168.10.2,use_dpdk=1,type=x4xx,product=x410,fpga=CG_400"`

`[INFO] [UHD] linux; GNU C++ version 9.4.0; Boost_107100; DPDK_19.11; 
UHD_4.5.0.main-2-ga7657c80`

`[WARNING] [PREFS] Loaded config from /root/.uhd. This location is considered 
deprecated, consider moving your config file to /root/.config instead.`

`EAL: Detected 32 lcore(s)`

`EAL: Detected 1 NUMA nodes`

`EAL: Multi-process socket /var/run/dpdk/rte/mp_socket`

`EAL: Selected IOVA mode 'PA'`

`EAL: No available hugepages reported in hugepages-1048576kB`

`EAL: Probing VFIO support...`

`EAL: VFIO support initialized`

`EAL: PCI device 0000:06:00.0 on NUMA socket -1`

`EAL:   probe driver: 15b3:1017 net_mlx5`

`EAL: PCI device 0000:06:00.1 on NUMA socket -1`

`EAL:   probe driver: 15b3:1017 net_mlx5`

`[WARNING] [DPDK::IO_SERVICE] Dropping packet: No link entry in rx table`

`[00:00:00.000041] Creating the usrp device with: 
addr=192.168.10.2,mgmt_addr=192.168.10.2,use_dpdk=1,type=x4xx,product=x410,fpga=CG_400...`

`[WARNING] [DPDK::IO_SERVICE] Dropping packet: No link entry in rx table`

`Error: LookupError: KeyError: No devices found for ----->`

`Device Address:`

`    addr: 192.168.10.2`

`    mgmt_addr: 192.168.10.2`

`    use_dpdk: 1`

`    type: x4xx`

`    product: x410`

`    fpga: CG_400`

In the scenario where I set the mgmt_addr to the RJ-45 port, I still get the 
device not found error, but the warning goes away.

`./benchmark_rate --rx_rate 491.52e6 --rx_channels 0 --tx_rate 491.52e6 
--tx_channels 0 --args 
"addr=192.168.10.2,mgmt_addr=192.168.1.184,use_dpdk=1,type=x4xx,product=x410"`

`[INFO] [UHD] linux; GNU C++ version 9.4.0; Boost_107100; DPDK_19.11; 
UHD_4.5.0.main-2-ga7657c80`

`[WARNING] [PREFS] Loaded config from /root/.uhd. This location is considered 
deprecated, consider moving your config file to /root/.config instead.`

`EAL: Detected 32 lcore(s)`

`EAL: Detected 1 NUMA nodes`

`EAL: Multi-process socket /var/run/dpdk/rte/mp_socket`

`EAL: Selected IOVA mode 'PA'`

`EAL: No available hugepages reported in hugepages-1048576kB`

`EAL: Probing VFIO support...`

`EAL: VFIO support initialized`

`EAL: PCI device 0000:06:00.0 on NUMA socket -1`

`EAL:   probe driver: 15b3:1017 net_mlx5`

`EAL: PCI device 0000:06:00.1 on NUMA socket -1`

`EAL:   probe driver: 15b3:1017 net_mlx5`

`[00:00:00.000037] Creating the usrp device with: 
addr=192.168.10.2,mgmt_addr=192.168.1.184,use_dpdk=1,type=x4xx,product=x410...`

`Error: LookupError: KeyError: No devices found for ----->`

`Device Address:`

`    addr: 192.168.10.2`

`    mgmt_addr: 192.168.1.184`

`    use_dpdk: 1`

`    type: x4xx`

`    product: x410`

if I use uhd_find devices, the command returns successfully if I specify the 
address to the QSFP port, however, if I specify the address as RJ-45 port, it 
returns unsuccessfully. 

`uhd_find_devices --args="addr=192.168.10.2"`

`[INFO] [UHD] linux; GNU C++ version 9.4.0; Boost_107100; DPDK_19.11; 
UHD_4.5.0.main-2-ga7657c80`

`--------------------------------------------------`

`-- UHD Device 0`

`--------------------------------------------------`

`Device Address:`

`    serial: 328AACC`

`    claimed: False`

`    fpga: CG_400`

`    mgmt_addr: 192.168.10.2`

`    name: ni-x4xx-328AACC`

`    product: x410`

`    type: x4xx`
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to