usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

"Connection refused" error with 100G ports on X440

D
danielmay83@gmail.com
Fri, Apr 25, 2025 2:46 PM

Hello,

I recently received an X440 and am having trouble with the 100G ethernet connections.

I'm using UHD 4.8.0, and the CG_400 firmware image.

I'm connected to both 100G ports and the 1G management port.  All ports come up fine and seem to be connected.

I can ping and ssh from my host machine to the X440 using the 100G ports just fine.

I can run "uhd_find_devices" from any of the ports just fine.

Using the 1G management port, I can run "uhd_usrp_probe" just fine.

However, I cannot run "uhd_usrp_probe" or any other utilities from any of the 100G ports.  I get the following error:

./uhd_usrp_probe --args "addr=192.168.10.2,type=x4xx"
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_106700; DPDK_24.11; UHD_4.8.0.0-0-unknown
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: addr=192.168.10.2,mgmt_addr=192.168.10.2,type=x4xx,product=x440,serial=3425978,name=ni-x4xx-3425978,fpga=CG_400,claimed=False
[INFO] [MPM.PeriphManager] init() called with device args `fpga=CG_400,mgmt_addr=192.168.10.2,name=ni-x4xx-3425978,product=x440,clock_source=internal,time_source=internal,initializing=True'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.

Any idea what could be causing this?

Additional info:

Host UHD version:
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_106700; DPDK_24.11; UHD_4.8.0.0-0-unknown

Device UHD version:
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107800; UHD_4.8.0.0-0-g308126a4

Thanks,
Daniel

Hello, I recently received an X440 and am having trouble with the 100G ethernet connections.\ \ I'm using UHD 4.8.0, and the CG_400 firmware image.\ \ I'm connected to both 100G ports and the 1G management port.  All ports come up fine and seem to be connected.\ \ I can ping and ssh from my host machine to the X440 using the 100G ports just fine.\ \ I can run "uhd_find_devices" from any of the ports just fine.\ \ Using the 1G management port, I can run "uhd_usrp_probe" just fine.\ \ However, I cannot run "uhd_usrp_probe" or any other utilities from any of the 100G ports.  I get the following error:\ \ ./uhd_usrp_probe --args "addr=192.168.10.2,type=x4xx"\ \[INFO\] \[UHD\] linux; GNU C++ version 13.3.0; Boost_106700; DPDK_24.11; UHD_4.8.0.0-0-unknown\ \[INFO\] \[MPMD\] Initializing 1 device(s) in parallel with args: addr=192.168.10.2,mgmt_addr=192.168.10.2,type=x4xx,product=x440,serial=3425978,name=ni-x4xx-3425978,fpga=CG_400,claimed=False\ \[INFO\] \[MPM.PeriphManager\] init() called with device args \`fpga=CG_400,mgmt_addr=192.168.10.2,name=ni-x4xx-3425978,product=x440,clock_source=internal,time_source=internal,initializing=True'.\ \[ERROR\] \[RFNOC::MGMT\] EnvironmentError: IOError: recv error on socket: Connection refused\ \[ERROR\] \[RFNOC::GRAPH\] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused\ \[ERROR\] \[RFNOC::GRAPH\] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused\ Error: RuntimeError: Failure to create rfnoc_graph.\ \ Any idea what could be causing this?\ \ Additional info:\ \ Host UHD version:\ \[INFO\] \[UHD\] linux; GNU C++ version 13.3.0; Boost_106700; DPDK_24.11; UHD_4.8.0.0-0-unknown\ \ Device UHD version:\ \[INFO\] \[UHD\] linux; GNU C++ version 11.4.0; Boost_107800; UHD_4.8.0.0-0-g308126a4\ \ Thanks,\ Daniel
D
danielmay83@gmail.com
Fri, Apr 25, 2025 5:10 PM

This was a user error on my part.  My QSFP’s were swapped.

My host machine was routing traffic to the correct port, which allowed pings and SSH to work over the swapped ports.  This fooled me into thinking it was connected correctly initially.

This was a user error on my part. My QSFP’s were swapped. My host machine was routing traffic to the correct port, which allowed pings and SSH to work over the swapped ports. This fooled me into thinking it was connected correctly initially.