• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Is a crossover cable needed for vSAN 2-Node Direct Connect?

Duncan Epping · Jan 8, 2021 · 3 Comments

I had this question last week around vSAN 2-node direct connect and whether using a crossover cable is still required to be used or if a regular CAT6 cable (CAT 5E works as well) can be used. I knew the answer and figured this would be documented somewhere, but it doesn’t appear to be. To be honest, many websites when talking about the need for crossover cables are blatantly wrong. And yes, I also spotted some incorrect recommendations in VMware’s own documentation, so I requested those entries to be updated. Just to be clear, with vSAN 2-Node Direct Connect, or vMotion, or any other service for that matter, you can use a regular CAT6 cable. I can’t recall having seen a NIC in the past 10 years that does not have Auto MDI/MDI-X implemented, even though it was an optional feature in the 1000Base-T standard. In other words, there’s no need to buy a crossover cable, or make one, just use a regular cable.

Share it:

  • Tweet

Related

Server 2-node, networking, VMware, vsan, vSphere

Reader Interactions

Comments

  1. Carlos says

    8 January, 2021 at 12:14

    Duncan, AFAIK there is no such thing as a crossover cable need for gigabit or ten gigabit.
    The phy of those use all 4 pairs in full duplex, there is no TX/RX pair you can “cross”. The standard needs all pairs to be identified at each end…
    We still have courses talking about half duplex and full duplex too. It’s just magic sauce, it seems.

    Reply
    • Duncan Epping says

      8 January, 2021 at 13:24

      That is what the post discusses?

      Reply
    • Jim says

      8 January, 2021 at 18:57

      Ok, but there is still such a thing as a crossover cable, for typical ports are not just 1000BaseT but also support compatibility with legacy standards – E.g. the ports are usually 10/100/1000 BaseT, not just Gigabit. And there is still theoretically legacy support for half-duplex in the standard. So MDIX still exists…. It is just in practice as described in the original post.. every Gigabit port has the Auto MDI/MDI-X support.

      Auto MDI/MDI-X maybe unnecessary when both sides are Gigabit and auto-negotiating, but it is necessary, and Auto MDI/MDI-X will not work in the event that port at one end of the cable or the other is configured to a manual or forced Speed and Duplex, e.g. Hard set to 100 Megabits-FD the other end will not be able to auto-negotiate not only Speed and Duplex, but also MDI/MDI-X cannot be negotiated, even if they are Gigabit ports.

      Reply

Leave a Reply Cancel reply

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the HCI BU at VMware. He is a VCDX (# 007) and the author of multiple books including "vSAN Deep Dive" and the “vSphere Clustering Technical Deep Dive” series.

Upcoming Events

04-Feb-21 | Czech VMUG – Roadshow
25-Feb-21 | Swiss VMUG – Roadshow
04-Mar-21 | Polish VMUG – Roadshow
09-Mar-21 | Austrian VMUG – Roadshow
18-Mar-21 | St Louis Usercon Keynote

Recommended reads

Sponsors

Want to support us? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2021 · Log in