Optical Transceivers & Direct-Attach Cables

Host platform first, because it decides the coding. A module coded for one vendor's switch may simply not be recognized by another's, and the same vendor sometimes needs different coding across product families. Give us the exact switch, router, NIC or storage controller model at each end of the link and the coding question stops being a risk.

Then form factor and speed — SFP for gigabit, SFP+ for 10, SFP28 for 25, QSFP+ for 40, QSFP28 for 100 — followed by reach and the fiber it runs on. Short-reach multimode over the wrong fiber grade is the classic distance failure; long-reach singlemode on a run that never left the rack is the classic waste. Both are avoided by measuring rather than assuming.

Connector type and duplex versus breakout finish it. A high-speed port broken out into multiple lower-speed links is a common and cost-effective pattern, and it needs the right cable assembly rather than an adapter improvised on site. Our cable length guide is built for exactly this measuring step.

Third-party optics are a commercial decision as well as a technical one. Some OEM support organizations will ask you to reproduce a fault using their own optics before they progress a case, and a few maintenance agreements address third-party components explicitly. This is rarely a practical obstacle and it is not a quality question, but it is a real consideration and we would rather raise it than let it surprise you during an incident.

Where a program's policy is to stay on OEM optics for supported platforms, we will quote those — including through our sister catalogs for Cisco, Aruba and Juniper platforms — and use third-party modules where the policy allows. A mixed estate is common and perfectly workable.

One catalog quirk worth knowing if you search yourself: a structured-cabling brand called Siemon surfaces on searches that look like they should return security-information tooling. It is a naming collision, not a mis-categorization.