Unsolved
This post is more than 5 years old
4 Posts
0
4123
October 13th, 2010 13:00
Getting full duplex for bonded interface
Hello to all
My Bond(bond0) file comprise of 2 ethernet interfaces.
But when I am running the below command it gives....
#mii-tool bond0
bond0: 10 Mbit, half duplex, link ok
Why I am getting half duplex and 10 Mbit when the individual eth interfaces comprising the bond are having 1000Mbps and Full Duplex.
# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbag
Wake-on: d
Current message level: 0x00000001 (1)
Link detected: yes
how i can force the bond interface to full duplex 1000Mbps
Thanks and best regards.


Avamar Exorcist
462 Posts
1
October 21st, 2010 07:00
It seems this is expected behaviour for mii-tool in that it's not reporting an accurate link status for bond0. You can find examples on the web.
My test system is reporting the same output as yours in response to "mii-tool bond0" but what we can do is perform a ‘real’ test to learn the actual throughput between Avamar nodes by using the ‘iperf’ tool.
See the following KB article for a short example of how to run iperf between two Avamar nodes.
esg106463 How to run iperf between two Avamar systems to test network throughput performance
Typical output seen on a system which is working correctly is shown below. If you're getting something like this then we can be sure that there is Gigabit ethernet connectivity between the Avamar nodes.
Client connecting to avamar1, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 10.xxx.xxx.xxx port 36734 connected with 10.xxx.xxx.xxx port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 112 MBytes 941 Mbits/sec
[ 3] 1.0- 2.0 sec 112 MBytes 941 Mbits/sec
[ 3] 2.0- 3.0 sec 112 MBytes 941 Mbits/sec
[ 3] 3.0- 4.0 sec 112 MBytes 941 Mbits/sec
[ 3] 4.0- 5.0 sec 112 MBytes 941 Mbits/sec
[ 3] 5.0- 6.0 sec 112 MBytes 941 Mbits/sec
[ 3] 6.0- 7.0 sec 112 MBytes 941 Mbits/sec
[ 3] 7.0- 8.0 sec 112 MBytes 941 Mbits/sec
[ 3] 8.0- 9.0 sec 112 MBytes 941 Mbits/sec
[ 3] 0.0- 9.8 sec 1.07 GBytes 941 Mbits/sec
This is a useful test to bear in mind since Gigabit ethernet connectivity between all Avamar nodes is critical.
cscheib522
1 Message
1
October 25th, 2010 11:00
I believe mii-tool is semi-deprecated, ethtool is what you probably should be using to check your speed/duplex settings. mii-tool doesn't understand gigabit, it's only useful up to 100mbit.
Not all EMC Linux loads have ethtool (or mii-tool for that matter), but the Avamars most certainly have it.
Also, as was noted before, the bond interfaces are virtual, so don't always reflect reality. You can check the speeds of the individual ports assigned to the bonding group using ethtool.
Ferrom1
4 Posts
0
October 27th, 2010 14:00
I'm more comfortable knowing that it is normal for all systems, I also tried it on some other systems in production and the result is the same
best regards.
dugans1
2 Intern
•
186 Posts
0
October 27th, 2010 14:00
Hi Guys,
I tried this and on Node B i get a "Connect Failed: Connection Refused. Could anyone explain Why. orry bit of a noob at unix. I followed this tech article.
http://solutions.emc.com/emcsolutionview.asp?id=esg106463
Goal
How to run iperf between two Avamar systems to test network throughout the performance
Resolution
1) From Avamar system A (We use dpn09s for this example. Substitute your server name.).
2) Start a putty session and log in as admin.
3) Run the iperf -s -i 1 command.
4) Leave the previous command running and go to Avamar system B.
5) Start a putty session from Avamar system B and log in as admin.
6) Run the iperf -c dpn09s.avamar.com -i 1 command.
7) Let this run. After it stops send the output.
8) End the sessions with Ctrl/C.
Avamar Exorcist
462 Posts
0
October 28th, 2010 02:00
I've improved the support solution. Below is a copy of the new text.
Goal
How to run iperf between two Avamar systems to test network throughput performance
Resolution
Login to the first Avamar system with the admin user (the hostname is avamarA for this example)
1) Start a putty session and log in as admin.
2) Run the command "iperf -s -i 1".
Leave the previous command running and go to the other Avamar system (whose hostname is avamarB in this example).
3) Start a putty session from Avamar system B (avamarB in this example) and log in as admin.
4) Run the command "iperf -c avamarA -i 1".
5) Let the command run for 10 seconds.
6) End the sessions with Ctrl/C.
Example output seen on avamarA
admin@avamarA:~/>: iperf -s -i 1 command
iperf: ignoring extra argument -- command
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
Example output seen on avamarB
admin@avamarB:~/>: iperf -c avamarA -i 1
------------------------------------------------------------
Client connecting to avmtest1, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 10.x.x.163 port 32829 connected with 10.x.x.161 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 112 MBytes 940 Mbits/sec
[ 3] 1.0- 2.0 sec 112 MBytes 939 Mbits/sec
[ 3] 2.0- 3.0 sec 112 MBytes 937 Mbits/sec
[ 3] 3.0- 4.0 sec 110 MBytes 920 Mbits/sec
[ 3] 4.0- 5.0 sec 111 MBytes 931 Mbits/sec
[ 3] 5.0- 6.0 sec 112 MBytes 941 Mbits/sec
[ 3] 6.0- 7.0 sec 111 MBytes 931 Mbits/sec
[ 3] 7.0- 8.0 sec 111 MBytes 928 Mbits/sec
[ 3] 8.0- 9.0 sec 110 MBytes 926 Mbits/sec
[ 3] 9.0-10.0 sec 111 MBytes 927 Mbits/sec
[ 3] 0.0-10.0 sec 1.08 GBytes 932 Mbits/sec
============================================
If you're still having difficulty after that then...
From the client (avamarB) run "telnet avamarA 5001" to check that port 5001 is reachable on the server
admin@avamarB:~/>: telnet avmtest1 5001
Trying 10.x.x.161...
Connected to avmtest1.emcvmw.ctc (10.x.x.161).
Escape character is '^]'.
On the server, confirm that it is listening on port 5001
admin@avamarA:~/>: netstat -an | grep 5001
tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN