Understand 10GBASE-T in Depth

Today, the Ethernet cabling system market is dominated by 10G links. Although fiber optic cables become popular with the advantages of high data transmission rate and low latency, many IT departments still use copper cabling for switch-to-switch or switch-to-server connections in 10G Ethernet applications. As one major copper cabling technology applied for 10GbE, 10GBASE-T was released by IEEE 802.3an in 2006 which specifies 10Gbps data transmission over four-pair copper cabling. Then, how much do you know about it? This article will guide you to understand 10GBASE-T in depth from five aspects—reach, backward compatibility, power consumption, latency and cost.

Reach

10GBASE-T is able to reach transmission distances up to 100 meters, and Cat6, Cat6a, Cat7, these three types of copper cables are commonly used with the 10GBASE-T standard. Cat6 bulk cable can perform at the bandwidth of up to 250 MHz, but it may reach only 55 meters at the speed of 10Gbps and 33 meters in high crosstalk conditions; Cat6a bulk cable is defined at frequencies up to 500MHz, and it can support the transmission distance over 100 meters at the speed of 10Gbps; Cat7 bulk cable can deliver 10G performance up to 600 MHz and at a distance of up to 100 meters. Here is a figure of a roll of cat6 cable.

roll-of-cat6-cable
Backward Compatibility

We know that Cat6 bulk cable, Cat6a bulk cable and Cat7 bulk cable are backward compatible with the Cat5 and Cat5e bulk cable standards, so these three types of cables can also be used for 10BASE-T, 100BASE-T and 1000BASE-T applications, though a little overqualified. Moreover, 10GBASE-T is backward compatible with 1000BAE-T. Therefore, 10GBASE-T can be deployed in preceding 1GbE switch infrastructures in data centers that are cabled with Cat6, Cat6a or Cat7 cabling. This enables data center managers to save costs while upgrading the network to 10GbE.

Power Consumption

According to the study, the early physical layer interface chips (PHYs) consumed too much power for widespread adoption. The original gigabit chips were roughly 6.5 Warts per port. With the process of improvements, the chips are now under 1 Wart per port. In addition, the PHYs benefit a lot from the latest manufacturing processes in 10GBASE-T. And the technology will continue to reduce the power consumption of PHYs.

Latency

Depending on Ethernet packet size, the latency for 1000BASE-T ranges from below 1μs to over 12μs, while 10GBASE-T’s latency ranges from just 1μs to less than 4μs—a much tighten latency range. And with a larger packet size, 10GBASE-T’s overall throughput offers an advantage over 1000BASE-T, and the latency for 10GBASE-T is more than three times lower than that of 1000BASE-T. The 1μs latency of 10GBASE-T is of no consequence to most users. Only the most latent-sensitive applications such as High Performance Computer (HPC) or high frequency trading systems would be affected by normal 10GbE latency.

Cost

As for cost, copper cables are cheaper, which is one reason for their wide applications. Take cables of FS.COM for example, Cat6 cable 1000 ft is about US$ 130.00; Cat6a cable 1000 ft is about US$ 180.00; Cat7 cable 305m is about US$ 600.00. Though 10G SFP+ DAC Twinax Cable is about US$ 42.00, from the perspective of structured cabling, it has a limited distance (up to 10m), and is not as flexible or cost-effective as 10GBASE-T.

Conclusion

From the above content, we can learn that 10GBASE-T offers the lowest cost media, and is backward compatible with preceding 1GbE networks. It can not only satisfy the increased bandwidth needs, but also greatly simplify the network and lower power consumption by replacing multiple gigabit connections with a single or dual-port 10GbE connection. Hence, it is an idea choice for 10G Ethernet copper cabling. And I hope after reading this article, you can have a better understanding on 10GBASE-T. 

Write a comment

Comments: 58
  • #1

    oglądaj anons (Monday, 04 September 2017 07:18)

    iskrownikowy

  • #2

    ogłoszenia erotyczne (Monday, 04 September 2017 11:11)

    albityzacja

  • #3

    tanie kurwy (Tuesday, 05 September 2017 06:46)

    przepiękniej

  • #4

    portal erotyczny (Friday, 08 September 2017 08:40)

    apoliński

  • #5

    http://sextelefon.org.pl/ (Saturday, 09 September 2017 06:17)

    konsulostwo

  • #6

    sex dziwki na telefon (Saturday, 09 September 2017 10:29)

    nieobłupianie

  • #7

    portal gejowski (Wednesday, 13 September 2017 08:51)

    niezgrywający

  • #8

    szukam na sex (Thursday, 14 September 2017 10:31)

    rozłączenie

  • #9

    zobacz szczegóły (Thursday, 14 September 2017 13:44)

    Fiodor

  • #10

    sex telefony (Friday, 13 October 2017 10:22)

    foniczny

  • #11

    Cat6 Cable (Wednesday, 20 December 2017 23:58)

    Admiring the time and effort you put into your blog and detailed information you offer!..

  • #12

    zbdrariI (Monday, 19 July 2021 19:01)

    20

  • #13

    zbdrariI (Monday, 19 July 2021 19:03)

    20

  • #14

    zbdrariI (Monday, 19 July 2021 19:03)

    20

  • #15

    zbdrariI (Monday, 19 July 2021 19:03)

    20

  • #16

    zbdrariI (Monday, 19 July 2021 19:03)

    20

  • #17

    zbdrariI (Monday, 19 July 2021 19:10)

    20

  • #18

    QlqzzNwr (Sunday, 21 November 2021 09:55)

    20

  • #19

    QlqzzNwr (Sunday, 21 November 2021 09:56)

    20

  • #20

    QlqzzNwr (Sunday, 21 November 2021 09:57)

    20

  • #21

    QlqzzNwr (Sunday, 21 November 2021 09:58)

    20

  • #22

    QlqzzNwr (Sunday, 21 November 2021)

    20

  • #23

    QlqzzNwr (Sunday, 21 November 2021 10:00)

    20

  • #24

    QlqzzNwr (Sunday, 21 November 2021 10:01)

    20

  • #25

    QlqzzNwr (Sunday, 21 November 2021 10:01)

    20

  • #26

    QlqzzNwr9280404 (Sunday, 21 November 2021 10:01)

    20

  • #27

    QlqzzNwr (Sunday, 21 November 2021 10:02)

    20

  • #28

    QlqzzNwr (Sunday, 21 November 2021 10:02)

    20

  • #29

    QlqzzNwr (Sunday, 21 November 2021 10:03)

    20

  • #30

    QlqzzNwr (Sunday, 21 November 2021 10:04)

    if(now()=sysdate(),sleep(15),0)

  • #31

    QlqzzNwr (Sunday, 21 November 2021 10:04)

    -1; waitfor delay '0:0:15' --

  • #32

    QlqzzNwr (Sunday, 21 November 2021 10:05)

    -5) OR 790=(SELECT 790 FROM PG_SLEEP(15))--

  • #33

    QlqzzNwr (Sunday, 21 November 2021 10:05)

    20*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)

  • #34

    QlqzzNwr (Sunday, 21 November 2021 10:06)

    20

  • #35

    QlqzzNwr (Sunday, 21 November 2021 10:06)

    20

  • #36

    QlqzzNwr (Sunday, 21 November 2021 10:07)

    20

  • #37

    QlqzzNwr (Sunday, 21 November 2021 10:07)

    20

  • #38

    QlqzzNwr (Sunday, 21 November 2021 10:08)

    20

  • #39

    QlqzzNwr (Sunday, 21 November 2021 10:09)

    20

  • #40

    QlqzzNwr (Sunday, 21 November 2021 10:09)

    20

  • #41

    QlqzzNwr (Sunday, 21 November 2021 10:10)

    20

  • #42

    QlqzzNwr (Sunday, 21 November 2021 10:13)

    20

  • #43

    0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z (Sunday, 21 November 2021 10:13)

    20

  • #44

    guxDew0F' OR 21=(SELECT 21 FROM PG_SLEEP(15))-- (Sunday, 21 November 2021 10:14)

    20

  • #45

    QlqzzNwr (Sunday, 21 November 2021 10:15)

    20

  • #46

    QlqzzNwr (Sunday, 21 November 2021 10:15)

    20

  • #47

    QlqzzNwr (Sunday, 21 November 2021 10:16)

    20

  • #48

    QlqzzNwr (Sunday, 21 November 2021 10:16)

    20

  • #49

    QlqzzNwr (Sunday, 21 November 2021 10:17)

    20

  • #50

    QlqzzNwr (Sunday, 21 November 2021 10:20)

    20

  • #51

    QlqzzNwr (Sunday, 21 November 2021 10:20)

    20

  • #52

    QlqzzNwr (Sunday, 21 November 2021 10:21)

    20

  • #53

    QlqzzNwr (Sunday, 21 November 2021 10:21)

    20

  • #54

    QlqzzNwr (Sunday, 21 November 2021 10:22)

    20

  • #55

    QlqzzNwr (Sunday, 21 November 2021 10:23)

    20

  • #56

    QlqzzNwr (Sunday, 21 November 2021 10:23)

    20

  • #57

    QlqzzNwr (Sunday, 21 November 2021 10:24)

    20

  • #58

    QlqzzNwr (Sunday, 21 November 2021 11:14)

    20