Practical tools for system, network, security, and operations administrators.

NET-C0180 · Physical Layer, Cabling & Data Center

RJ45 Wiring: T568A vs T568B

Choose T568A or T568B and use it on both ends of the cable you are making.

Updated 25 October 2026 · Comparison

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

T568A and T568B are two pinouts. A straight cable uses the same one at both ends. A crossover uses a pair swapped, and modern ports often remove the need. The generator drafts a pinout. You still hold the connector the same way up when you read it.

Pick one standard for the site and write it. Mixing them on a straight run makes a cable that is not straight. Write which end you are looking at.

This page does not ask you to tap a live pair. Punch a lab patch, or plan one.

A cable tester you trust is the proof. A link light is a hint.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Write A or B for the site.
  2. Draft the pinout.
  3. Use the same standard at both ends for a straight cable.
  4. Say if you truly need a crossover.
  5. Test a lab patch if you make one.
  6. Do not mix standards on one straight run.

Mistakes that outlive the command

RJ45 Wiring: T568A vs T568B goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for RJ45 Wiring: T568A vs T568B: The site standard is one letter. Both ends match for a straight run. A crossover is explicit or absent. And no live pair was the practice.

Checks before you call it done

Confirm this before you call the change done: The letter is in the ticket. The pinout was read with the clip in a stated direction. A tester result is written if a cable was made. No live circuit was punched. And the next cable uses the same letter. If one of those fails, stop.

One standard for the site.
Both ends match on a straight cable.

Before you leave the device

RJ45 Wiring: T568A vs T568B ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.