DUPLEX MISMATCH




In Ethernet, a duplex mismatch is a condition where two connected devices operate in different duplex modes, that is, one operates in half duplex while the other one operates in full duplex. The effect of a duplex mismatch is a network that works but is often much slower than its nominal speed. Duplex mismatch may be caused by manually setting two connected network interfaces at different duplex modes or by connecting a device that performs autonegotiation to one that is manually set to a full duplex mode

When a device set to autonegotiation is connected to a device that is not using autonegotiation, the autonegotiation process fails. The autonegotiating end of the connection is still able to correctly detect the speed of the other end, but cannot correct the duplex mode. The standard requires the use of half duplex in these conditions. Therefore, the autonegotiating end of the connection uses half duplex while its peer is locked at full duplex, and this is a duplex mismatch.

The Ethernet standards body, IEEE 802.3, recommends enabling autonegotiation on all connections. Nevertheless network equipment allows autonegotiation to be disabled and on some networks, autonegotiation is disabled on all ports and a fixed modality of 100 Mbit/s and full duplex is used. That was often done by network administrators intentionally upon the introduction of autonegotiation, because of interoperability issues with the initial autonegotiation specification. The fixed mode of operation works well if both ends of a connection are locked to the same settings. However, maintaining such a network and guaranteeing consistency is difficult. Since autonegotiation is generally the manufacturer’s default setting it is almost certain that, in an environment where the policy is to have fixed port settings, someone will sooner or later leave a port set to use autonegotiation by mistake.

Communication is possible over a connection in spite of a duplex mismatch. Single packets are sent and acknowledged without problems. As a result, a simple ping command fails to detect a duplex mismatch because single packets and their resulting acknowledgments at 1-second intervals do not cause any problem on the network. A terminal session which sends data slowly (in very short bursts) can also communicate successfully. However, as soon as either end of the connection attempts to send any significant amount of data, the network suddenly slows to very low speed. Since the network is otherwise working, the cause is not so readily apparent.

A duplex mismatch causes problems when both ends of the connection attempt to transfer data at the same time. This happens even if the channel is used (from a high-level or user’s perspective) in one direction only, in case of large data transfers. Indeed, when a large data transfer is sent over a TCP, data is sent in multiple packets, some of which will trigger an acknowledgment packet back to the sender. This results in packets being sent in both directions at the same time.

In such conditions, the full-duplex end of the connection sends its packets while receiving other packets; this is exactly the point of a full-duplex connection. Meanwhile, the half-duplex end cannot accept the incoming data while it is sending — it will sense it as a collision. The half-duplex device ceases its current transmission and then retries later as per CSMA/CD. As a result, when both devices are attempting to transmit at the same time, packets sent by the full-duplex end will be lost and packets sent by the half duplex device will be delayed or lost.

The lost packets force the TCP protocol to perform error recovery, but the initial (streamlined) recovery attempts fail because the retransmitted packets are lost in exactly the same way as the original packets. Eventually, the TCP transmission window becomes full and the TCP protocol refuses to transmit any further data until the previously-transmitted data is acknowledged. This, in turn, will quiesce the new traffic over the connection, leaving only the retransmissions and acknowledgments. Since the retransmission timer grows progressively longer between attempts, eventually a retransmission will occur when there is no reverse traffic on the connection, and the acknowledgment are finally received. This will restart the TCP traffic, which in turn immediately causes lost packets as streaming resumes.

The end result is a connection that is working but performs extremely poorly because of the duplex mismatch. Symptoms of a duplex mismatch are connections that seem to work fine with a ping command, but “lock up” easily with very low throughput on data transfers; the effective data transfer rate is likely to be asymmetrical, performing much worse in one direction than the other. In normal half-duplex operations late collisions do not occur. However, in a duplex mismatch the collisions seen on the half-duplex side of the link are often late collisions. The full-duplex side usually will register frame check sequence errors, or runt frames. Viewing these standard Ethernet statistics can help diagnose the problem.

Contrary to what one might reasonably expect, both sides of a connection need to be identically configured for proper operation. In other words, setting one side to automatic (either speed or duplex or both) and setting the other to be fixed (either speed or duplex or both) will result in either a speed mismatch, a duplex mismatch or both. A duplex mismatch can be fixed by either enabling autonegotiation (if available and working) on both ends or by forcing the same settings on both ends (availability of a configuration interface permitting). If there is no option but to have a locked setting on one end and autonegotiation the other (for example, an old device with broken autonegotiation connected to an unmanaged switch) half duplex must be used. All modern LAN equipment comes with autonegotiation enabled and the various compatibility issues have been resolved. The best way to avoid duplex mismatches is to use autonegotiation and to replace any legacy equipment that does not use autonegotiation or does not autonegotiate correctly.

UNTANGLING NETWORK PERFORMANCE LINK
explains how bad duplex mismatch can get…

You can set duplexing on the windows os with the following instructions:
In the Device Manager, you should see Network adapters. Select the Properties of your controller. There should be an Advanced tab which shows an property entry for Speed & Duplex.

You can set duplexing on mac os x with the following instructions:
Open Network Utility on the Mac, Info tab, Select the Ethernet Interface, check Link speed… look for Errors or Collisions?

In System Preferences
select Network
select Ethernet
select Advanced
select Ethernet tab, try Manually setting different speeds
sometimes you have to reboot to get it to respect it.

You can check link speed on mac os x with the following instructions:
Open Network Utility on the Mac, Info tab, Select the Ethernet Interface, what Link speed does it show? Any Errors or Collisions?

Follow the link below to find out how to set duplex and speed for linux
DUPLEX AND SPEED CHANGES IN LINUX
DUPLEX AND SPEED CHANGES IN DEBIAN AND UBUNTU

Now lets say you need a utility to see if you have speed duplex issues
DOWNLOAD NDT FROM THIS LINK

Network Diagnostic Tool (NDT) provides a sophisticated speed and diagnostic test. An NDT test reports more than just the upload and download speeds — it also attempts to determine what, if any, problems limited these speeds, differentiating between computer configuration and network infrastructure problems. While the diagnostic messages are most useful for expert users, they can also help novice users by allowing them to provide detailed trouble reports to their network administrator.

LAST RECAP ON PROPER SETTINGS

The rule of thumb for 1000 Mb/s links is to let autonegotiation work by setting the NIC and the switch to autonegotiate If you have Cisco switches you can manually set each side of the link to full duplex and the link will work, but this technically violates the standard.

ANYTHING ELSE WILL CAUSE RESET AND RENEGOTIATE PERIODICALLY CAUSING PERFORMANCE ISSUES

The most important thing to know about setting 100 Mb/s Ethernet links is that autonegotiation often does not work as advertised. The only safe thing to do is to set each side of the connection to half duplex manually.

ANYTHING ELSE WILL CAUSE RESET AND RENEGOTIATE PERIODICALLY CAUSING PERFORMANCE ISSUES

The best way to manage 10 Mb/s Ethernet links is to set each side of the connection to half duplex

ANYTHING ELSE WILL CAUSE RESET AND RENEGOTIATE PERIODICALLY CAUSING PERFORMANCE ISSUES

This entry was posted in Network and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>