Interface speed
khopkins
96 Posts
July 20, 2020, 7:44 pmQuote from khopkins on July 20, 2020, 7:44 pmHello,
I was setting up an NMS and noticed that my interface speed on the node was different than what the NMS was presenting. Read the 3rd line for the Ethernet, all interfaces are like this. This is also true for the LO interface. In the NMS its reading as a 10G SFP. Why didn't the node go to 10G with everything 10G plugged into it? Thanks,
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d633 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)
RX packets 51816417989 bytes 60455053119574 (60.4 TB)
RX errors 0 dropped 1451611 overruns 0 frame 0
TX packets 62564158839 bytes 76004785227908 (76.0 TB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0
bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d636 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:36 txqueuelen 1000 (Ethernet)
RX packets 68257983011 bytes 72773797644622 (72.7 TB)
RX errors 0 dropped 10869707 overruns 0 frame 0
TX packets 62851808152 bytes 63639164246105 (63.6 TB)
TX errors 0 dropped 159 overruns 0 carrier 0 collisions 0
Hello,
I was setting up an NMS and noticed that my interface speed on the node was different than what the NMS was presenting. Read the 3rd line for the Ethernet, all interfaces are like this. This is also true for the LO interface. In the NMS its reading as a 10G SFP. Why didn't the node go to 10G with everything 10G plugged into it? Thanks,
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d633 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)
RX packets 51816417989 bytes 60455053119574 (60.4 TB)
RX errors 0 dropped 1451611 overruns 0 frame 0
TX packets 62564158839 bytes 76004785227908 (76.0 TB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0
bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d636 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:36 txqueuelen 1000 (Ethernet)
RX packets 68257983011 bytes 72773797644622 (72.7 TB)
RX errors 0 dropped 10869707 overruns 0 frame 0
TX packets 62851808152 bytes 63639164246105 (63.6 TB)
TX errors 0 dropped 159 overruns 0 carrier 0 collisions 0
Last edited on July 20, 2020, 7:45 pm by khopkins · #1
admin
2,930 Posts
July 20, 2020, 9:35 pmQuote from admin on July 20, 2020, 9:35 pmwhat do ethtool and dmesg show
what do ethtool and dmesg show
khopkins
96 Posts
July 21, 2020, 9:56 pmQuote from khopkins on July 21, 2020, 9:56 pmBTW, its using DAC's, thanks for the help
Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
Settings for bond1:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
dmesg
4.817400] i40e 0000:05:00.3: MAC address: 00:12:c0:02:d6:36
[ 4.828306] i40e 0000:05:00.3 eth4: NIC Link is Up, 10 Gbps Full Duplex, Flow
Control: None
BTW, its using DAC's, thanks for the help
Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
Settings for bond1:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
dmesg
4.817400] i40e 0000:05:00.3: MAC address: 00:12:c0:02:d6:36
[ 4.828306] i40e 0000:05:00.3 eth4: NIC Link is Up, 10 Gbps Full Duplex, Flow
Control: None
Last edited on July 21, 2020, 10:04 pm by khopkins · #3
admin
2,930 Posts
July 21, 2020, 10:58 pmQuote from admin on July 21, 2020, 10:58 pmThe kernel is reporting 10G on the nics, i do not see where the problem is.
The kernel is reporting 10G on the nics, i do not see where the problem is.
NTmatter
8 Posts
July 24, 2020, 8:37 amQuote from NTmatter on July 24, 2020, 8:37 amJust to provide some extra context, the txqueue 1000 in "ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)" refers to the Transaction Queue Length, or number of packets queued by the interface when large amounts of data are being dumped onto the network.
As per the ethtool output, bond0 and bond1 have 20000Mb/s in each direction. That's 20 Gigabits, or 2*10 Gigabit. If you look at the underlying interfaces with ethtool, you should see that their operating speed as 10000Mb/s as well.
Just for fun, you should also be able to see the underlying transceiver stats for your DAC modules with: ethtool --module-info eth0
Just to provide some extra context, the txqueue 1000 in "ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)" refers to the Transaction Queue Length, or number of packets queued by the interface when large amounts of data are being dumped onto the network.
As per the ethtool output, bond0 and bond1 have 20000Mb/s in each direction. That's 20 Gigabits, or 2*10 Gigabit. If you look at the underlying interfaces with ethtool, you should see that their operating speed as 10000Mb/s as well.
Just for fun, you should also be able to see the underlying transceiver stats for your DAC modules with: ethtool --module-info eth0
Interface speed
khopkins
96 Posts
Quote from khopkins on July 20, 2020, 7:44 pmHello,
I was setting up an NMS and noticed that my interface speed on the node was different than what the NMS was presenting. Read the 3rd line for the Ethernet, all interfaces are like this. This is also true for the LO interface. In the NMS its reading as a 10G SFP. Why didn't the node go to 10G with everything 10G plugged into it? Thanks,
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d633 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)
RX packets 51816417989 bytes 60455053119574 (60.4 TB)
RX errors 0 dropped 1451611 overruns 0 frame 0
TX packets 62564158839 bytes 76004785227908 (76.0 TB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d636 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:36 txqueuelen 1000 (Ethernet)
RX packets 68257983011 bytes 72773797644622 (72.7 TB)
RX errors 0 dropped 10869707 overruns 0 frame 0
TX packets 62851808152 bytes 63639164246105 (63.6 TB)
TX errors 0 dropped 159 overruns 0 carrier 0 collisions 0
Hello,
I was setting up an NMS and noticed that my interface speed on the node was different than what the NMS was presenting. Read the 3rd line for the Ethernet, all interfaces are like this. This is also true for the LO interface. In the NMS its reading as a 10G SFP. Why didn't the node go to 10G with everything 10G plugged into it? Thanks,
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d633 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)
RX packets 51816417989 bytes 60455053119574 (60.4 TB)
RX errors 0 dropped 1451611 overruns 0 frame 0
TX packets 62564158839 bytes 76004785227908 (76.0 TB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0
bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet6 fe80::212:c0ff:fe02:d636 prefixlen 64 scopeid 0x20<link>
ether 00:12:c0:02:d6:36 txqueuelen 1000 (Ethernet)
RX packets 68257983011 bytes 72773797644622 (72.7 TB)
RX errors 0 dropped 10869707 overruns 0 frame 0
TX packets 62851808152 bytes 63639164246105 (63.6 TB)
TX errors 0 dropped 159 overruns 0 carrier 0 collisions 0
admin
2,930 Posts
Quote from admin on July 20, 2020, 9:35 pmwhat do ethtool and dmesg show
what do ethtool and dmesg show
khopkins
96 Posts
Quote from khopkins on July 21, 2020, 9:56 pmBTW, its using DAC's, thanks for the help
Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
Settings for bond1:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
dmesg
4.817400] i40e 0000:05:00.3: MAC address: 00:12:c0:02:d6:36
[ 4.828306] i40e 0000:05:00.3 eth4: NIC Link is Up, 10 Gbps Full Duplex, Flow
Control: None
BTW, its using DAC's, thanks for the help
Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
Settings for bond1:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 20000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes
dmesg
4.817400] i40e 0000:05:00.3: MAC address: 00:12:c0:02:d6:36
[ 4.828306] i40e 0000:05:00.3 eth4: NIC Link is Up, 10 Gbps Full Duplex, Flow
Control: None
admin
2,930 Posts
Quote from admin on July 21, 2020, 10:58 pmThe kernel is reporting 10G on the nics, i do not see where the problem is.
The kernel is reporting 10G on the nics, i do not see where the problem is.
NTmatter
8 Posts
Quote from NTmatter on July 24, 2020, 8:37 amJust to provide some extra context, the txqueue 1000 in "ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)" refers to the Transaction Queue Length, or number of packets queued by the interface when large amounts of data are being dumped onto the network.
As per the ethtool output, bond0 and bond1 have 20000Mb/s in each direction. That's 20 Gigabits, or 2*10 Gigabit. If you look at the underlying interfaces with ethtool, you should see that their operating speed as 10000Mb/s as well.
Just for fun, you should also be able to see the underlying transceiver stats for your DAC modules with: ethtool --module-info eth0
Just to provide some extra context, the txqueue 1000 in "ether 00:12:c0:02:d6:33 txqueuelen 1000 (Ethernet)" refers to the Transaction Queue Length, or number of packets queued by the interface when large amounts of data are being dumped onto the network.
As per the ethtool output, bond0 and bond1 have 20000Mb/s in each direction. That's 20 Gigabits, or 2*10 Gigabit. If you look at the underlying interfaces with ethtool, you should see that their operating speed as 10000Mb/s as well.
Just for fun, you should also be able to see the underlying transceiver stats for your DAC modules with: ethtool --module-info eth0