Hi,
Guest
usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threads10 GigE on X300
EC
Eddie Carle
Thu, Mar 5, 2015 11:07 PM
I've been trying to get the 10 GigE card supplied by Ettus working with
our X300 and have had zero luck. Using the 1 GigE SFP provided with the
X300 straight into the onboard LAN on my motherboard through a patch
cord works effortlessly. Stepping up to 10gig not so much. The patch
cord I'm using is this:
http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
These are my steps:
1. I connect port 0 on the X300 with the "first" port on the
ethernet card
2. I turn on the X300
3. I turn on the computer with my ixbge kernel logs showing the
following:
Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
4. I execute the following commands:
ip link set dev enp2s0f0 up
ip addr add 192.168.10.1/24 dev enp2s0f0
ip link set dev enp2s0f0 mtu 9000
5. The result of `ip addr` then shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
valid_lft 41863sec preferred_lft 41863sec
inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
valid_lft forever preferred_lft forever
3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 scope global enp2s0f0
valid_lft forever preferred_lft forever
4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
obviously doesn't work either.
I must confess that this is my first flirtation with 10 gig ethernet and
SFP+ connectors. Looking at the kernel logs it appears that the card is
recognizing an SFP+ thingy inserted into the first port. When I look at
the results of ip addr, the "state DOWN" on enp2s0f0 stands out as
something not working quite right. I should also mention that the left
hand LED above the SFP+ port on the back of the X300 does light up
solid. The right, however, does not. Also the link LED on the front
seems to blink every so often. Can anybody see some obvious step I might
be missing? Suggestions?
Eddie Carle
I've been trying to get the 10 GigE card supplied by Ettus working with
our X300 and have had zero luck. Using the 1 GigE SFP provided with the
X300 straight into the onboard LAN on my motherboard through a patch
cord works effortlessly. Stepping up to 10gig not so much. The patch
cord I'm using is this:
http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
These are my steps:
1. I connect port 0 on the X300 with the "first" port on the
ethernet card
2. I turn on the X300
3. I turn on the computer with my ixbge kernel logs showing the
following:
Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
4. I execute the following commands:
ip link set dev enp2s0f0 up
ip addr add 192.168.10.1/24 dev enp2s0f0
ip link set dev enp2s0f0 mtu 9000
5. The result of `ip addr` then shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
valid_lft 41863sec preferred_lft 41863sec
inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
valid_lft forever preferred_lft forever
3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 scope global enp2s0f0
valid_lft forever preferred_lft forever
4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
obviously doesn't work either.
I must confess that this is my first flirtation with 10 gig ethernet and
SFP+ connectors. Looking at the kernel logs it appears that the card is
recognizing an SFP+ thingy inserted into the first port. When I look at
the results of `ip addr`, the "state DOWN" on enp2s0f0 stands out as
something not working quite right. I should also mention that the left
hand LED above the SFP+ port on the back of the X300 does light up
solid. The right, however, does not. Also the link LED on the front
seems to blink every so often. Can anybody see some obvious step I might
be missing? Suggestions?
--
Eddie Carle
TS
Timothy Schaffer
Thu, Mar 5, 2015 11:17 PM
Curious what operating system your using? Also, take a look at
http://files.ettus.com/manual/page_usrp_x3x0.html the IP address for the
10G interface is 192.168.30.2 not 10.2
On Thu, Mar 5, 2015 at 6:07 PM, Eddie Carle via USRP-users <
usrp-users@lists.ettus.com> wrote:
I've been trying to get the 10 GigE card supplied by Ettus working with
our X300 and have had zero luck. Using the 1 GigE SFP provided with the
X300 straight into the onboard LAN on my motherboard through a patch cord
works effortlessly. Stepping up to 10gig not so much. The patch cord I'm
using is this:
http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
These are my steps:
1. I connect port 0 on the X300 with the "first" port on the ethernet
card
2. I turn on the X300
3. I turn on the computer with my ixbge kernel logs showing the
following:
Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
4. I execute the following commands:
ip link set dev enp2s0f0 up
ip addr add 192.168.10.1/24 dev enp2s0f0
ip link set dev enp2s0f0 mtu 9000
5. The result of `ip addr` then shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
valid_lft 41863sec preferred_lft 41863sec
inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
valid_lft forever preferred_lft forever
3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 scope global enp2s0f0
valid_lft forever preferred_lft forever
4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
obviously doesn't work either.
I must confess that this is my first flirtation with 10 gig ethernet and
SFP+ connectors. Looking at the kernel logs it appears that the card is
recognizing an SFP+ thingy inserted into the first port. When I look at the
results of ip addr, the "state DOWN" on enp2s0f0 stands out as something
not working quite right. I should also mention that the left hand LED above
the SFP+ port on the back of the X300 does light up solid. The right,
however, does not. Also the link LED on the front seems to blink every so
often. Can anybody see some obvious step I might be missing? Suggestions?
Eddie Carle
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Curious what operating system your using? Also, take a look at
http://files.ettus.com/manual/page_usrp_x3x0.html the IP address for the
10G interface is 192.168.30.2 not 10.2
On Thu, Mar 5, 2015 at 6:07 PM, Eddie Carle via USRP-users <
usrp-users@lists.ettus.com> wrote:
> I've been trying to get the 10 GigE card supplied by Ettus working with
> our X300 and have had zero luck. Using the 1 GigE SFP provided with the
> X300 straight into the onboard LAN on my motherboard through a patch cord
> works effortlessly. Stepping up to 10gig not so much. The patch cord I'm
> using is this:
>
> http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
>
> These are my steps:
>
> 1. I connect port 0 on the X300 with the "first" port on the ethernet
> card
> 2. I turn on the X300
> 3. I turn on the computer with my ixbge kernel logs showing the
> following:
>
> Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
> Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
> Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
> Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
>
> 4. I execute the following commands:
>
> ip link set dev enp2s0f0 up
> ip addr add 192.168.10.1/24 dev enp2s0f0
> ip link set dev enp2s0f0 mtu 9000
>
> 5. The result of `ip addr` then shows:
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
> link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
> inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
> valid_lft 41863sec preferred_lft 41863sec
> inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
> valid_lft forever preferred_lft forever
> 3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
> link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
> inet 192.168.10.1/24 scope global enp2s0f0
> valid_lft forever preferred_lft forever
> 4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
> 5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
> link/sit 0.0.0.0 brd 0.0.0.0
>
> 6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
> obviously doesn't work either.
>
>
> I must confess that this is my first flirtation with 10 gig ethernet and
> SFP+ connectors. Looking at the kernel logs it appears that the card is
> recognizing an SFP+ thingy inserted into the first port. When I look at the
> results of `ip addr`, the "state DOWN" on enp2s0f0 stands out as something
> not working quite right. I should also mention that the left hand LED above
> the SFP+ port on the back of the X300 does light up solid. The right,
> however, does not. Also the link LED on the front seems to blink every so
> often. Can anybody see some obvious step I might be missing? Suggestions?
> --
>
> *Eddie Carle*
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
ME
Matt Ettus
Thu, Mar 5, 2015 11:23 PM
Eddie,
When you are using 10G, are you connecting to the port marked 0 or 1 on the
USRP? Because only port 1 is set up for 10G in the default FPGA image.
Port 0 is 1G only in that image. It does not autodetect.
Matt
On Thu, Mar 5, 2015 at 3:07 PM, Eddie Carle via USRP-users <
usrp-users@lists.ettus.com> wrote:
I've been trying to get the 10 GigE card supplied by Ettus working with
our X300 and have had zero luck. Using the 1 GigE SFP provided with the
X300 straight into the onboard LAN on my motherboard through a patch cord
works effortlessly. Stepping up to 10gig not so much. The patch cord I'm
using is this:
http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
These are my steps:
1. I connect port 0 on the X300 with the "first" port on the ethernet
card
2. I turn on the X300
3. I turn on the computer with my ixbge kernel logs showing the
following:
Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
4. I execute the following commands:
ip link set dev enp2s0f0 up
ip addr add 192.168.10.1/24 dev enp2s0f0
ip link set dev enp2s0f0 mtu 9000
5. The result of `ip addr` then shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
valid_lft 41863sec preferred_lft 41863sec
inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
valid_lft forever preferred_lft forever
3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 scope global enp2s0f0
valid_lft forever preferred_lft forever
4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
obviously doesn't work either.
I must confess that this is my first flirtation with 10 gig ethernet and
SFP+ connectors. Looking at the kernel logs it appears that the card is
recognizing an SFP+ thingy inserted into the first port. When I look at the
results of ip addr, the "state DOWN" on enp2s0f0 stands out as something
not working quite right. I should also mention that the left hand LED above
the SFP+ port on the back of the X300 does light up solid. The right,
however, does not. Also the link LED on the front seems to blink every so
often. Can anybody see some obvious step I might be missing? Suggestions?
Eddie Carle
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Eddie,
When you are using 10G, are you connecting to the port marked 0 or 1 on the
USRP? Because only port 1 is set up for 10G in the default FPGA image.
Port 0 is 1G only in that image. It does not autodetect.
Matt
On Thu, Mar 5, 2015 at 3:07 PM, Eddie Carle via USRP-users <
usrp-users@lists.ettus.com> wrote:
> I've been trying to get the 10 GigE card supplied by Ettus working with
> our X300 and have had zero luck. Using the 1 GigE SFP provided with the
> X300 straight into the onboard LAN on my motherboard through a patch cord
> works effortlessly. Stepping up to 10gig not so much. The patch cord I'm
> using is this:
>
> http://www.newegg.ca/Product/Product.aspx?Item=N82E16812791639
>
> These are my steps:
>
> 1. I connect port 0 on the X300 with the "first" port on the ethernet
> card
> 2. I turn on the X300
> 3. I turn on the computer with my ixbge kernel logs showing the
> following:
>
> Mar 05 15:29:11 juliet kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.19.1-k
> Mar 05 15:29:11 juliet kernel: ixgbe: Copyright (c) 1999-2014 Intel Corporation.
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 29 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 30 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 31 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 32 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 33 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 34 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 35 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 36 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: irq 37 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: PCI Express bandwidth of 32GT/s available
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: MAC: 2, PHY: 9, SFP+: 3, PBA No: E68793-006
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: 90:e2:ba:7c:1d:f8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 38 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 39 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 40 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 41 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 42 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 43 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 44 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 45 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: irq 46 for MSI/MSI-X
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 8, Tx Queue count = 8
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: PCI Express bandwidth of 32GT/s available
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: MAC: 2, PHY: 1, PBA No: E68793-006
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: 90:e2:ba:7c:1d:f9
> Mar 05 15:29:11 juliet kernel: ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
> Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.0 enp2s0f0: renamed from eth1
> Mar 05 15:29:12 juliet kernel: ixgbe 0000:02:00.1 enp2s0f1: renamed from eth2
>
> 4. I execute the following commands:
>
> ip link set dev enp2s0f0 up
> ip addr add 192.168.10.1/24 dev enp2s0f0
> ip link set dev enp2s0f0 mtu 9000
>
> 5. The result of `ip addr` then shows:
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
> link/ether 38:2c:4a:70:2f:9b brd ff:ff:ff:ff:ff:ff
> inet 10.64.0.2/26 brd 10.64.0.63 scope global dynamic eno1
> valid_lft 41863sec preferred_lft 41863sec
> inet6 fe80::3a2c:4aff:fe70:2f9b/64 scope link
> valid_lft forever preferred_lft forever
> 3: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc mq state DOWN group default qlen 1000
> link/ether 90:e2:ba:7c:1d:f8 brd ff:ff:ff:ff:ff:ff
> inet 192.168.10.1/24 scope global enp2s0f0
> valid_lft forever preferred_lft forever
> 4: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> link/ether 90:e2:ba:7c:1d:f9 brd ff:ff:ff:ff:ff:ff
> 5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
> link/sit 0.0.0.0 brd 0.0.0.0
>
> 6. I then try to ping 192.168.10.2 with no luck. uhd_find_devices
> obviously doesn't work either.
>
>
> I must confess that this is my first flirtation with 10 gig ethernet and
> SFP+ connectors. Looking at the kernel logs it appears that the card is
> recognizing an SFP+ thingy inserted into the first port. When I look at the
> results of `ip addr`, the "state DOWN" on enp2s0f0 stands out as something
> not working quite right. I should also mention that the left hand LED above
> the SFP+ port on the back of the X300 does light up solid. The right,
> however, does not. Also the link LED on the front seems to blink every so
> often. Can anybody see some obvious step I might be missing? Suggestions?
> --
>
> *Eddie Carle*
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
EC
Eddie Carle
Thu, Mar 5, 2015 11:29 PM
On Thu, 2015-03-05 at 18:17 -0500, Timothy Schaffer via USRP-users
wrote:
Curious what operating system your using? Also, take a look
at http://files.ettus.com/manual/page_usrp_x3x0.html the IP address
for the 10G interface is 192.168.30.2 not 10.2
Bingo, I neglected to read that table of IP addresses. Thanks you very
much.
Eddie Carle
On Thu, 2015-03-05 at 18:17 -0500, Timothy Schaffer via USRP-users
wrote:
> Curious what operating system your using? Also, take a look
> at http://files.ettus.com/manual/page_usrp_x3x0.html the IP address
> for the 10G interface is 192.168.30.2 not 10.2
Bingo, I neglected to read that table of IP addresses. Thanks you very
much.
--
Eddie Carle
Replying to:
Empathy v1.0
2026 ©emwd.com