What is the purpose of Twinax cables and how does it differ from straight through and cross over cables for the connection of unlike and like devices?

I want to know whether there is any difference between them.

Also, Kindly tell me what type of cabling is used for various connections in the network?


2 Answers 2


Twinax cables are very high-frequency yet bulky cables that most often serve either of two purposes:

  1. very early, low-complexity copper connections for new speed grades
  2. short, low-cost, low-overhead connections

Their reach is usually very low - there's no horizontal or vertical cabling standard for twinax. Structured cabling uses fiber for high performance or high reach.

Twinax has much higher performance (=signal fidelity) than cheap twisted pair cabling - several GHz instead of hundreds of MHz - but it's also more bulky and of much higher cost. Due to the expected low-price nature and better reach of Ethernet, it is only used for early PHYs when a new speed grade is developed or in "niche applications" like short-reach interconnects and stacking.

Twisted pair needs much more complex encoding due to its comparatively inferior frequency performance, so it's only available somewhat later on with a new speed grade - check gigabit or 10 gigabit Ethernet for reference.

The reason why twisted-pair Ethernet came up with the straight-through and crossover variants is that Cat-3 straight cabling already existed when 10BASE-T came up (or StarLAN even earlier) and Ethernet had to find a solution to work with that: nearly all devices use one variant of transmitter and receiver contacts (MDI), except for hubs (and subsequently switches) which use the opposite MDI-X pinout. It doesn't work in all situation, so you'd need crossover cables for connecting like devices.

Twinax (or fiber for that matter) didn't ever have this problem, so there's a signal crossover in every cable, creating an odd number of crossovers in nearly any situation.

Note that the twisted-pair crossover vs straight confusion is mostly a thing of the past as nearly all devices from 1999 on (or so) support Auto MDI-X.


Ethernet supports a wide variety of physical layers, using a variety of different physical mediums. Some standards never see any significant deployment at all. Some are used for early deployments of a new speed but then fall by the wayside as technology improved. Some remain in widespread use for decades.

Twinax cabling is bulky and relatively expensive but can carry high frequencies which means it can support high speeds with relatively simple modulation. Twisted pair cabling tends to have lower bandwidth.

Twinax first came onto the Ethernet scene with 1000BASE-CX. This was the first copper standard for gigabit Ethernet and was used in some early deployments but it was rapidly eclipsed by 1000BASE-T and became essentially a historical footnote.

At 10 gigabit per second things got messier. The first copper standard was 10GBASE-CX4 standardised in 2002 shortly after the initial 10 gigabit fiber standards and using four 2.5Gbps lanes on twinax cabling borrowed from infiniband. Afaict it was used in some early deployments and probablly remained "current" for longer than 1000BASE-CX did but it too has now become a historical footnote.

In 2006 the 10GBASE-T standard was developed promising 10 gigabits per second over up to 100 meters of relatively cheap twisted pair cabling. However it was plagued by power consumption issues.

Also in 2006 the SFP+ standard for modular 10 Gigabit transceivers was introduced. There had been a number of previous standards for modular 10 gigabit transceivers but all of them had been much bulkier, limiting port density.

However this created a bit of a problem, SFP+ was not suited to either 10GBASE-T or 10GBASE-CX4. SFP+ was designed around a single 10Gbps lane while 10GBASE-CX4 and 10GBASE-T were four-lane standards. 10GBASE-T was also too power hungry to accommodate in a SFP+ module, while 10GBASE-CX4 connectors were too physically big.

To mitigate this, "SFP+ direct attach" cables were created. These were designed to plug directly into the SFP+ transceiver sockets. I'm not 100% sure when SFP+ direct attach was first created, I searched the history of the Wikipedia article and that lead me to an Intel article from 2008. As I understand it short direct attach cables are passive twinax, slightly longer ones are twinax but with additional amplification and long was are fibre based. Fibre based direct attach cables can still be cheaper than separate transceivers and fiber because the transceivers only have to be good enough to work with the supplied fiber.

Improvements in signal processing technology meant that 10GBASE-T SFP+ modules did eventually show up, but they were limited to 30 meters rather than the full 100 meters and were initially very expensive. They have come down in price a bit but they are still significantly more expensive than either direct attach cables or fibre transceivers.

The idea of direct attach cables has been carried over to faster variants of the SFP standards and you can now get such cables for speeds as high as 800 gigabit per second.

The downside of direct attach cables is that they must run directly from device to device, they cannot be routed via patch panels. This is not a problem if the devices are in the same rack and may be tolerable for "next rack over" but rapidly becomes a PITA if longer distances are needed.

Twisted pair on the other hand seems to have petered out. The IEEE approved standards for 25GBASE-T and 40GBASE-T in 2016 but nearly 7 years later I still can't find anywhere actually selling them.

how does it differ from straight through and cross over cables for the connection of unlike and like devices?

The existence of straight through cables is really an artefact of the fact that twisted-pair cables used for Ethernet evolved from phone cables.

With cable types designed specifically for high speed symmetric communication it is more common that every cable is "crossed".

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.