Auto MDI/MDIX lets a copper Ethernet port detect whether transmit and receive pairs need to be crossed and adjusts the port automatically. On compatible ports, a normal straight-through patch cable usually works for switch-to-switch, switch-to-PC and similar links. A crossover cable is still relevant when both endpoints lack or disable the feature.
A link LED that stays dark often leads to the same question: is the wrong Ethernet cable being used?
On most modern copper Ethernet ports, the answer is no. Auto MDI/MDIX can identify the transmit and receive pair orientation and correct it inside the port. That is why a straight-through cable now works in many connections that once required a crossover cable.
However, Auto MDI/MDIX is not a cable-repair function. It cannot fix an open pair, a split pair, excessive cable length, electromagnetic interference, a disabled port or a speed and duplex mismatch. Understanding that boundary is more useful than simply knowing the definition.
The Wiring Problem Auto MDI/MDIX Solves
MDI stands for Medium Dependent Interface. MDIX stands for Medium Dependent Interface Crossover. In classic 10BASE-T and 100BASE-TX Ethernet, the two interface types assign transmit and receive signals to different RJ45 pin pairs.
| RJ45 pin | MDI port | MDIX port |
|---|---|---|
| 1 | Transmit positive — TX+ | Receive positive — RX+ |
| 2 | Transmit negative — TX− | Receive negative — RX− |
| 3 | Receive positive — RX+ | Transmit positive — TX+ |
| 6 | Receive negative — RX− | Transmit negative — TX− |
The basic requirement is simple: the transmitter at one end must reach the receiver at the other end. A traditional MDI-to-MDIX connection already aligns the pair functions, so it uses a straight-through cable. A connection between two ports of the same type requires the pairs to cross.
Traditional 10/100BASE-T pair orientation
MDI to MDIX with a straight-through cable
MDI TX pins 1/2 ─────────────────── MDIX RX pins 1/2
MDI RX pins 3/6 ─────────────────── MDIX TX pins 3/6
MDI to MDI with a crossover cable
MDI TX pins 1/2 ────────────────┐ MDI RX pins 3/6
MDI RX pins 3/6 ────────────────┴── MDI TX pins 1/2
Auto MDI/MDIX detects the required orientation and swaps the pairs inside the port.Important: this diagram explains pair orientation; it is not a complete cabling specification. Field installation still requires the correct cable category, connector termination, shielding strategy and maximum channel length for the required Ethernet speed.
Straight-Through vs Crossover Cable: What Actually Changes?
A straight-through cable keeps the same transmit and receive pin positions from one connector to the other. A crossover cable exchanges the 1/2 and 3/6 pairs used by 10/100BASE-T.
| Cable type | Relevant pin mapping | Traditional use without Auto MDI/MDIX | Use with Auto MDI/MDIX |
|---|---|---|---|
| Straight-through | 1→1, 2→2, 3→3, 6→6 | MDI to MDIX, such as PC-to-switch | Usually suitable for either port orientation |
| Crossover | 1→3, 2→6, 3→1, 6→2 | MDI to MDI or MDIX to MDIX, such as legacy switch-to-switch | Usually also works, but is rarely necessary |
Cisco’s Auto-MDIX configuration guidance describes the same practical rule: without Auto-MDIX, unlike device types normally use a straight-through cable and like device types use a crossover cable; with Auto-MDIX enabled, either cable type can establish the connection.
Do You Still Need a Crossover Cable?
For most new networks, no. If at least one copper Ethernet endpoint correctly supports and enables Auto MDI/MDIX, the port can normally compensate for either straight-through or crossover wiring.
A crossover cable may still be needed, or at least worth testing, in four situations:
- Two legacy endpoints: neither port supports automatic pair correction.
- Auto MDI/MDIX is disabled: a device setting, fixed port configuration or implementation limitation prevents automatic crossover.
- Special-purpose or pre-standard equipment: the port does not behave like a normal standards-based Ethernet PHY.
- Controlled troubleshooting: a technician is validating an old point-to-point link and needs to eliminate pair orientation as a variable.
Do not make crossover cables the first response to every link failure. A known-good straight-through patch cable is usually the better baseline for troubleshooting a modern network.
Auto-Negotiation and Auto MDI/MDIX Are Related, but Not the Same
The two functions are often discussed together because many Ethernet PHYs perform them during the same link-start process. They solve different problems.
| Function | What it determines | What it does not determine |
|---|---|---|
| Auto-negotiation | Compatible link parameters such as speed and duplex, depending on the Ethernet standard and device | Whether a damaged or incorrectly terminated cable can carry the signal |
| Auto MDI/MDIX | Whether the transmit and receive pair orientation must be crossed inside the port | Speed, duplex, VLAN configuration, PoE budget or application connectivity |
Implementation details matter. Cisco documents that on certain switch ports, Auto-MDIX remains available when speed or duplex is left on auto, but is disabled when both are forced. That is an implementation example, not a rule that should be assumed for every PHY. Check the device manual when a fixed-speed or fixed-duplex link behaves differently from an automatically negotiated link. The relationship is explained in Cisco’s Auto-MDI/MDIX feature documentation.
For a new installation, leaving both ends on compatible auto-negotiation settings is normally the cleanest starting point. If the application requires fixed parameters, verify Auto MDI/MDIX behavior on both endpoints rather than assuming the pair correction remains active.
What Auto MDI/MDIX Cannot Fix
Auto MDI/MDIX only corrects pair orientation. It does not compensate for other physical, electrical or configuration problems.
- Open, shorted or split pairs: the cable may look correctly pinned but fail electrical testing.
- Excessive cable length or wrong cable category: the signal may not meet the link budget at the target speed.
- Poor terminations: loose contacts, damaged plugs and excessive untwist can degrade the channel.
- EMI, grounding or surge damage: industrial noise and potential differences require appropriate cabling, bonding, protection or fiber isolation.
- Speed or duplex mismatch: the pair orientation can be correct while link parameters remain incompatible.
- Disabled or blocked ports: an administratively disabled interface, port security, STP state or switch configuration can stop traffic.
- PoE power problems: an Ethernet link and a powered-device startup are related but separate checks. Auto MDI/MDIX does not increase the PoE budget or repair power wiring.
- Fiber interface problems: MDI/MDIX applies to copper twisted-pair ports, not optical SFP links.
If the Ethernet Link Is Down, Troubleshoot in This Order
The fastest diagnosis comes from changing one variable at a time. Repeatedly swapping random cables, ports and settings can hide the actual cause.
- Confirm power and port status. Verify that both devices are powered, the correct copper ports are being used and neither interface is administratively disabled.
- Use a known-good straight-through patch cable. This creates a consistent baseline and avoids an unknown field termination.
- Inspect and test the cable. Check the plug latch, contact damage, pin sequence, continuity, pair integrity and channel length. A continuity-only tester may not detect every performance problem.
- Return speed and duplex to auto on both ends. If Auto MDI/MDIX is configurable, enable it. Wait for the ports to renegotiate.
- Check the port LEDs and interface status. Confirm negotiated speed and duplex. Review CRC, alignment, late-collision or link-flap counters where management data is available.
- Test another known-good port. Keep the same cable and endpoint where possible. This helps separate a damaged port from a cable or configuration issue.
- For two legacy fixed ports, test the correct crossover cable. Do this only after confirming that neither endpoint provides active Auto MDI/MDIX.
- Separate data and PoE diagnosis. If a camera or access point does not power up, test PoE class, switch power budget, cable resistance and the powered device independently of the Ethernet pair-orientation question.
- Investigate the industrial environment. If the link fails only during motor starts, welding or storms, inspect shielding, grounding, routing, surge protection and the case for a fiber uplink.
If the link LED comes up but the application still cannot communicate, stop changing the cable. Move to IP addressing, VLAN membership, routing, firewall, protocol and device-configuration checks.
Which Maisvch Products Explicitly Document Auto MDI/MDIX?
Auto MDI/MDIX support should be verified by model and port. Do not assume that every RJ45 interface in a broad product category has the same behavior.
The following current product pages explicitly document MDI/MDIX self-adaptation or automatic crossover for the listed copper interfaces:
| Model | Product type | Documented Ethernet-port statement | What the buyer should confirm |
|---|---|---|---|
| MIEN2205 | DIN-rail unmanaged industrial Ethernet switch | 10/100M RJ45 ports with MDI/MDIX self-adaptation | Required copper-port count, fiber variant and environmental specification |
| Mport3108-RJ / Mport3108-232 | 8-port serial device server | 10/100M RJ45 Ethernet interface with Auto MDI/MDIX | Serial interface type, connector, serial-port count and operating mode |
| MIR655R | industrial 4G router | 10/100M auto-sensing RJ45 interfaces with Auto MDI/MDIX documented on the product page | WAN/LAN role, regional cellular bands, antenna and power requirements |
| MW-CANET200 | CAN-to-Ethernet gateway | 100M RJ45 interface with automatic MDI/MDIX cross/direct adaptation | CAN channel count, protocol mode, isolation and network architecture |
Specifications can differ by hardware revision, port type and product configuration. Before placing an order, match the exact model and datasheet to the project rather than treating category-level support as a guarantee.
What to Put in an Industrial Ethernet RFQ
“Supports Auto MDI/MDIX” is useful, but it is not enough to select an industrial network device. A clear request for quotation should define the operating conditions around the port.
- Number of copper RJ45, SFP and PoE ports
- Required port speeds and whether fixed speed or duplex is mandatory
- Auto-negotiation and Auto MDI/MDIX requirements by port
- Cable category, estimated channel length and connector environment
- PoE standard, per-port load and total power budget where applicable
- Input voltage, redundant power requirement and power connector
- Operating temperature, humidity, vibration and mounting method
- EMC, ESD, surge and isolation requirements for the installation
- Managed features such as VLAN, redundancy, diagnostics and remote monitoring
- Required approvals, labeling, firmware behavior and OEM/ODM changes
This information allows an industrial Ethernet switch manufacturer to review the complete link instead of answering only whether an RJ45 port can swap pairs. Maisvch can evaluate standard model selection and application-specific requirements against the port mix, enclosure, power input and communication environment supplied by the buyer.
Frequently Asked Questions
Is Auto MDI/MDIX the same as auto-negotiation?
No. Auto-negotiation establishes compatible link parameters such as speed and duplex. Auto MDI/MDIX detects whether the transmit and receive pairs need to be crossed. The functions may run together in the Ethernet PHY, but they solve different problems.
Will Auto MDI/MDIX work if only one end supports it?
Normally, yes. One active Auto MDI/MDIX port can usually detect and correct the pair orientation for the link. Device-specific restrictions still apply, especially when speed and duplex are forced.
Can I use a crossover cable on an Auto MDI/MDIX port?
Usually, yes. The port should detect the crossover orientation and compensate for it. A straight-through cable is still the simpler standard choice for new installations.
Why is the link still down when both ports support Auto MDI/MDIX?
Check power, port enable state, cable integrity, channel length, speed and duplex settings, connector quality and port damage. In an industrial environment, also investigate EMI, grounding and surge exposure. Auto MDI/MDIX only corrects pair orientation.
Does Auto MDI/MDIX work on fiber ports?
No. MDI/MDIX concerns transmit and receive pair orientation on copper twisted-pair Ethernet. Optical links have separate transmit and receive paths and require the correct fiber, wavelength, module and polarity.
Does Auto MDI/MDIX improve network speed?
No. It simplifies cable selection and link establishment. The actual speed depends on the Ethernet interfaces, cable channel, negotiation result and network design.
Does every industrial Ethernet switch support Auto MDI/MDIX?
No universal assumption should be made. Verify the exact model, hardware revision and copper-port specification. Fiber ports do not use MDI/MDIX, and some legacy or fixed-configuration copper ports may behave differently.
Can Auto MDI/MDIX fix a badly crimped Ethernet cable?
No. It can correct transmit and receive pair orientation, but it cannot repair an open conductor, short circuit, split pair, excessive untwist or poor contact. Test and reterminate the cable when physical quality is in doubt.
The Practical Decision
Use a known-good straight-through cable as the default for a modern copper Ethernet link. If the endpoints support Auto MDI/MDIX, the port should handle the pair orientation automatically. Keep crossover wiring for verified legacy requirements, not as a substitute for systematic troubleshooting.
For industrial projects, confirm Auto MDI/MDIX together with speed, duplex, PoE, environmental protection, EMC performance and the exact port configuration. That is the difference between selecting a convenient feature and engineering a reliable link.
