SR4 stands for Short Range, 4 lanes. The module splits 100G across four parallel transmit and four parallel receive lanes, each running at 25 Gbps, over OM3 or OM4 multimode fiber. The connector is MPO-12 (also called MTP), with a maximum reach of 70 meters over OM3 or 100 meters over OM4.
That reach profile makes SR4 the natural default for top-of-rack to spine connections inside a single data center hall. Runs longer than 100 meters call for a different variant — PSM4 for single-mode parallel, or LR4 for longer single-mode reach. Under 100 meters on multimode, SR4 is the right call.
The QSFP28 form factor carries 100G as four 25G NRZ lanes. It fits the same cage as QSFP+, but the two are not electrically interchangeable at 100G speeds.
Arista EOS validates transceivers against an internal compatibility database. Insert a module that isn't in that database, and EOS logs a warning — and depending on the platform and software version, may disable the port entirely. The warning looks like this:
%XCVR-6-UNSUPPORTED_OPTIC: Transceiver in port Et1/1 is not an Arista-qualified optic
This doesn't mean the module is defective. It means EOS doesn't recognize the vendor ID encoded in the module's EEPROM. Third-party modules programmed with the correct Arista vendor string and part number won't trigger this warning at all.
If your module hasn't been pre-programmed with Arista vendor data, you can override the check with a single global command:
switch(config)# service unsupported-transceiver
The key is a license string provided by Arista. Without it, the command is rejected. Arista's current policy requires you to contact them or your reseller to obtain this key before deploying non-qualified optics.
Modules factory-programmed to report as Arista-compatible bypass this step entirely. The port comes up clean — no override, no license key required.
Once the port is up, confirm the module is reading correctly:
switch# show interfaces Et1/1 transceiver
switch# show interfaces Et1/1 transceiver detail
The output should show:
If Rx power reads as N/A or the lane count is wrong, check that the MPO-12 cable is fully seated and that fiber polarity matches the expected type — Type B for most SR4 deployments.
SR4 modules are supported across Arista's main switching families:
QSFP28 cages are standard across all of these. If you're running a 7050CX3 or 7060CX2, the front-panel ports are QSFP28 and will accept SR4 modules directly.
Always cross-reference your specific EOS version against Arista's hardware compatibility matrix. Some older EOS builds apply stricter transceiver validation than current releases.
Third-party compatible modules are widely deployed in production environments, and the economics are hard to ignore. In the optical transceiver segment, third-party compatible alternatives commonly deliver 70 to 90 percent cost savings versus OEM pricing — a gap that compounds quickly when you're deploying dozens or hundreds of ports.
When evaluating a third-party SR4 module for Arista, four things matter:
EEPROM programming: The module needs to report the correct vendor name, part number, and serial number format that Arista EOS expects. This is what determines whether the unsupported-transceiver warning fires.
DOM support: Digital Optical Monitoring lets you read Tx/Rx power, temperature, and voltage per lane directly from EOS. Without it, you lose visibility into link health.
Fiber type: Confirm OM3 or OM4 compatibility and verify the MPO-12 connector is polished to the correct specification. APC finish is not used on SR4 — UPC or PC is standard.
Test documentation: A reputable supplier backs compatibility claims with evidence. Compatibility test videos or downloadable reports showing the module running on specific Arista platforms are far more useful than a generic compatibility statement.
HYTOPTODEVICE stocks Arista-compatible modules across the full 1.25G to 800G range, with compatibility test videos and product downloads available before you commit to a purchase. The catalog covers QSFP28 SR4 and extends into QSFP-DD and OSFP form factors for higher-speed deployments — useful if a 400G or 800G upgrade is on the roadmap for the same platform family.
SR4 is a parallel optics standard. A single 100G link uses eight fibers: four transmit and four receive. The MPO-12 connector carries 12 fibers total — positions 1 through 4 for Tx, positions 9 through 12 for Rx, and positions 5 through 8 unused.
Fiber type: OM3 for runs up to 70 meters, OM4 for runs up to 100 meters. OM2 or OM1 will cause signal degradation and unreliable links.
Polarity: SR4 uses Type B polarity (TIA-568 Method B) — a straight-through MPO trunk cable with no pin flip. Back-to-back SR4 connections need a Type B cable. If you're routing through a patch panel, verify the polarity scheme across the entire link before you start troubleshooting.
Cleanliness: Parallel fiber connectors are more contamination-sensitive than duplex LC connectors because a single dirty fiber degrades one lane. Inspect and clean MPO connectors before insertion, even on new cables.
Start with show interfaces Et1/1 transceiver. If the module isn't detected, reseat it. If it's detected but the port is in errdisabled state, run show interfaces Et1/1 status and check the reason code. An unsupported-transceiver error requires either the service command with a valid key or a pre-programmed module.
SR4 links report per-lane status in show interfaces transceiver detail. A single dead lane points to a fiber problem, not the module. Swap the MPO cable or check individual fiber continuity with an OTDR or visual fault locator.
Low Rx power across all four lanes simultaneously usually means the cable run exceeds the fiber type's rated distance, the connectors are dirty, or there's insertion loss in the patch panel. Low power on one or two lanes points to a specific fiber strand.
Almost always a connector cleanliness or seating issue on parallel fiber. Contamination on a single MPO fiber can cause one lane to drop intermittently — and some platforms interpret that as a full link failure.
SR4 isn't the only 100G QSFP28 variant. Here's a quick decision guide:
| Variant | Fiber Type | Max Reach | Connector | Use Case |
|---|---|---|---|---|
| SR4 | OM3/OM4 MMF | 100m | MPO-12 | Short in-building runs |
| PSM4 | OS2 SMF | 500m | MPO-12 | Campus or longer runs |
| LR4 | OS2 SMF | 10km | LC duplex | Inter-building or WAN edge |
| CWDM4 | OS2 SMF | 2km | LC duplex | Mid-range data center |
If your infrastructure already has OM4 multimode deployed and your runs are under 100 meters, SR4 is the most cost-effective choice. On single-mode, or when you need more than 100 meters, PSM4 or CWDM4 are the logical next steps before moving to LR4.
Before placing an order, confirm three things with your supplier:
A supplier that provides compatibility test videos and downloadable technical documentation gives you a way to validate the module before it touches your network. That matters more than price alone when the alternative is a production outage during a maintenance window.
For procurement teams evaluating options across multiple form factors and speeds, hytoptodevice.com covers the full range from SFP to QSFP-DD and OSFP, with Arista, Cisco, and Juniper compatible options and OEM/ODM services for larger or custom deployments.
Q1:What does QSFP-100G-SR4 Arista compatible mean?
A:It means the module is a QSFP28 SR4 transceiver that has been programmed and tested to work with Arista EOS switches without triggering unsupported-transceiver warnings. The EEPROM data matches what Arista's compatibility database expects.
Q2:Do I need a license key to use a third-party SR4 module on Arista?
A:Only if the module isn't pre-programmed with Arista vendor data. Modules that report the correct Arista vendor string and part number come up without any override. If the module isn't recognized, you'll need to run the service unsupported-transceiver command with a key obtained from Arista.
Q3:What fiber type does QSFP-100G-SR4 require?
A:OM3 multimode fiber for runs up to 70 meters, or OM4 multimode fiber for runs up to 100 meters. The connector is MPO-12. Single-mode fiber is not compatible with SR4.
Q4:Can I use a QSFP-100G-SR4 module in a QSFP+ port?
A:No. QSFP28 and QSFP+ share the same physical form factor but are not electrically interchangeable at 100G speeds. QSFP+ ports run at 40G. SR4 operation requires a QSFP28-capable port.
Q5:How do I check transceiver status on Arista EOS?
A:Use show interfaces Et for a summary and show interfaces Et for per-lane power readings, temperature, and voltage. DOM must be supported by the module for detailed output to appear.
Q6:What is the polarity type for SR4 cabling?
A:SR4 uses Type B polarity (TIA-568 Method B) — a straight-through MPO cable with no pin flip. The wrong polarity type will cross Tx and Rx lanes, and the link won't come up.
Q7:What should I ask a supplier before buying a third-party Arista SR4 module?
A:Ask whether the module is programmed specifically for Arista compatibility, whether it supports DOM, and whether the supplier has compatibility test documentation for your specific Arista platform and EOS version. Test videos or downloadable reports are the most reliable form of evidence.
Q8: How much does an Arista compatible QSFP-100G-SR4 module cost vs OEM?
A: A compatible QSFP-100G-SR4 module typically costs 70–90% less than Arista OEM pricing. At dozens or hundreds of ports, that saving compounds fast. Verify EEPROM programming and test documentation before ordering — suppliers like HYTOPTODEVICE publish compatibility evidence upfront.
Q9: How do I fix an Arista unsupported-transceiver warning on a QSFP28 SR4 module?
A: Pre-programmed modules insert clean, with no warning and no license key. Unrecognized modules trigger %XCVR-6-UNSUPPORTED_OPTIC and need the EOS command service unsupported-transceiver plus a key from Arista. Factory-programmed Arista-compatible modules skip the override step entirely.
Q10: Does a third-party transceiver void my Arista warranty?
A: Third-party optics do not void the Arista hardware warranty, but Arista TAC may not troubleshoot optic issues on non-qualified modules. Choose modules programmed with Arista vendor data to stay off the unsupported path. Confirm vendor-programmed EEPROM before purchase.
Q11: Will a 100G QSFP28 SR4 module work on an Arista 7050X3?
A: Yes — QSFP28 SR4 modules fit the 7050X3, 7060X, 7280R, and 7500R families. The 7050CX3 and 7060CX2 front panels accept SR4 directly. Cross-check your EOS version against Arista's compatibility matrix before ordering.
Q12: Is a third-party QSFP-100G-SR4 module reliable enough for production?
A: Yes, with the right evidence. Third-party SR4 modules carry production workloads when the supplier shows compatibility test videos or reports for your exact platform. DOM support is mandatory for per-lane visibility.HYTOPTODEVICE provides downloadable test documentation before you commit.
Q13: What fiber and distance does a 100G QSFP28 SR4 link need?
A: OM3 up to 70 meters, OM4 up to 100 meters, with MPO-12 Type B polarity. OM2 or OM1 will not hold a reliable link. A single dirty fiber drops one lane — clean and inspect MPO connectors before insertion.
Q14: Can I buy QSFP-100G-SR4 Arista compatible modules in bulk with OEM options?
A: Yes — compatible modules scale from single units to full deployments. Confirm Arista-specific EEPROM programming, DOM support, and platform test documentation. HYTOPTODEVICE covers 1.25G–800G with OEM/ODM for custom or large orders.
Q15: What warranty and DOA cover should I expect for an Arista compatible 100G SR4 module?
A: Agree on warranty, DOA, and return terms before you pay. Documented compatibility beats a generic compatibility list. Confirm your platform and EOS version with the supplier in writing, and keep test evidence on file.
Buying a QSFP-100G-SR4 Arista compatible module is straightforward once you know what to verify. Confirm the EEPROM programming, check DOM support, use the right fiber and polarity, and run the EOS show commands after insertion. Most issues that look like module problems turn out to be cabling or configuration.
For larger deployments — or when you need Arista-compatible options alongside Cisco or Juniper platforms — HYTOPTODEVICE provides compatibility documentation and test resources to support pre-purchase validation across its full catalog.
