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

NET-C0184 · Physical Layer, Cabling & Data Center

SFP vs SFP+ vs QSFP vs OSFP

Name the cage and the module for one port, and check that they are the same generation.

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

SFP, SFP+, QSFP, and OSFP are cage families. A module fits a cage. A faster family is not a universal plug. The reference and the compatibility finder draft a match from names you type. They do not see your switch.

A breakout turns one port into several. It is a plan for the far ends as well. Write all of them. A breakout you cannot patch is a dark port.

Distance and fiber type still apply. The fiber page is the glass. This page is the cage.

Buy one lab module if you must prove the fit. Do not order a row of switches from a finder result.

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. Name the switch port and the cage.
  2. Name the module.
  3. Check the family match.
  4. If it is a breakout, list every far end.
  5. Match fiber type in a sentence.
  6. Do not order a fleet.

Mistakes that outlive the command

SFP vs SFP+ vs QSFP vs OSFP 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 SFP vs SFP+ vs QSFP vs OSFP: Cage and module families match. Breakout ends are listed or there is no breakout. Fiber type is named. One port is the example. And no fleet was ordered.

Checks before you call it done

Confirm this before you call the change done: The port is named. The module is named. The match was checked. Far ends are written if split. And nothing was purchased beyond a lab module, or nothing was purchased. If one of those fails, stop.

Match the cage and the module.
Name every breakout end.

Before you leave the device

SFP vs SFP+ vs QSFP vs OSFP 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.