Our Blog

StrinexSeptember 21, 2026

25GBASE-SR Physical Layer & Why FEC Is Not Optional at 25G The 25G SFP28 fabric has quietly become the workhorse of modern hyperscale leaf-spine topologies, but most operational headaches at 25G are not about the laser — they are about Forward Error Correction. When a leaf switch suddenly logs PHY-4-INCOMPATIBLE_FEC or IF_DOWN_LINK_FAILURE after a topology refresh, the root cause is almost always a Base-R / RS-FEC mismatch between the two ends of the SR4-style breakout or the 25GBASE-SR SFP28 link. Getting 25G SFP28 FEC mode configuration right — choosing between FireCode Base-R (Clause 74) and RS-FEC (Clause 91) — is now a daily task for data center architects running high-density ToR and MoR deployments. This guide walks through the actual signaling physics, the dB-level margin trade-off between CL74 and CL91, and the platform-specific CLI needed to land a stable 25GBASE-SR link on Cisco NX-OS, Cisco IOS-XE, Juniper Junos, Arista EOS, and MikroTik RouterOS. 25GBASE-SR is defined by IEEE 802.3by Clause 112 and runs an effective 25.78125 Gbps NRZ line rate across a single lane of OM3 or OM4 multimode fiber using an 850nm VCSEL. That lane rate is roughly 2.5× the 10.3125 Gbps of 10GBASE-SR, and the IEEE 802.3by task force deliberately accepted a tighter optical power budget in exchange for reach: typical Strinex-grade 25G SR optics deliver a Tx launch range near –6.5 to +2.5 dBm and an Rx sensitivity around –10.3 dBm, giving a usable link budget of roughly 3.8 dB over OM4 — versus the ~6 dB operating margin most engineers are used to at 10G. Because the operating margin is thin, the IEEE working group mandated Forward Error Correction as part of the 25G Ethernet family. Two FEC schemes dominate 25G SFP28 deployments: Base-R FEC (Clause 74, also called FireCode) — a lightweight 10-bit symbol to 211-bit codeword scheme defined in IEEE 802.3bj Clause 74. Originally designed for 100GBASE-CR4 / KR4 backplane and 25GBASE-CR / 25GBASE-KR (Clause 110/111) direct-attach copper, Base-R adds only ~2% latency overhead and roughly corrects bursts of up to 11 bit errors per codeword. It does NOT appear in the 802.3by optical PMD itself but is frequently negotiated on 25GBASE-CR DAC and on some 25G SR optics over stressed fiber runs. RS-FEC (Clause 91, Reed-Solomon Forward Error Correction) — a much stronger RS(528,514) code defined in IEEE 802.3bj Clause 91. RS-FEC adds ~6.4% latency, can correct bursts of up to 79 bit errors per codeword, and provides approximately 5.6 dB of net coding gain. This is the FEC mode that makes 25GBASE-SR viable on real-world OM3/OM4 plant with dirty connectors, aged fiber, and tight bend radii. In practice, most 25G SFP28 SR optics over multimode fiber ship with FEC DISABLED by default to remain backwards-compatible with 10G SFP+ cages, but the IEEE 802.3by Clause 112 optics explicitly assume an external FEC (typically RS-FEC CL91 negotiated by the host MAC/PCS). Misconfiguring the FEC state between two devices is the single most common cause of a 25G link that comes up at line rate but logs a continuous stream of MAC local fault / RS-FEC: uncorrectable codewords errors. Key Takeaway: RS-FEC (CL91) is mandatory for stable 25GBASE-SR over real OM3/OM4 plant because the 802.3by optical power budget only delivers ~3.8 dB operating margin — far less than the 6 dB headroom most 10G links enjoy. Base-R (CL74) is intended for 25GBASE-CR / KR copper and should not be selected for MMF SR optics. FEC Coding Gain Trade-Off & Optical Link Budget Recalculation FEC is not free. The RS(528,514) parity overhead consumed by Clause 91 reduces the effective payload throughput slightly and adds approximately 80 ns of latency per direction per hop. For a typical 4-hop fat-tree at 25G, that is ~320 ns of cumulative FEC latency — negligible for east-west TCP but real for HFT and HPC fabrics where microseconds matter. Base-R FEC adds only ~25 ns per hop and is the preferred mode when both ends of the link are short DAC runs or where the optical plant is pristine. The decision matrix reduces to four engineering variables: Fiber plant margin — if your measured Rx power is within 1.5 dB of the 25G SR Rx sensitivity floor (typically –10.3 dBm for OM4), enable RS-FEC. If you have ≥ 4 dB margin, Base-R is safe. Connector hygiene — RS-FEC will ride through contaminated LC duplex ferrules that would otherwise force Base-R into a RS_FEC_HI_BER degraded state. Per IEC 61300-3-35, a single scratch zone inside the core can drop 2–3 dB off a 25G link. BER target — RS-FEC targets post-FEC BER ≤ 10–12; Base-R targets ≤ 10–8. If you are running storage replication or in-memory database replication over the same fabric, post-FEC BER is the metric that matters. Latency budget — if the application is HFT or RoCE v2 / NFS over UDP with sub-microsecond timing, the ~80 ns RS-FEC tax per hop may push you toward Base-R on short, clean 25G runs even with optical margin loss. For practical deployments, we recommend RS-FEC as the default on all 25GBASE-SR links longer than 10 m, and a hybrid model where ToR-to-leaf MMF runs RS-FEC while ToR-to-server DAC 25GBASE-CR runs Base-R or FEC off depending on the NIC firmware. Hardware & FEC Mode Comparison: Strinex Alpha Bridge vs. FS.com vs. Cisco OEM vs. Generic | Parameter | Strinex Alpha Bridge SFP28-25G-SR | FS.com SFP28-25G-SR | Cisco OEM SFP-25G-SR-S | Generic / Refurbished | | :--- | :--- | :--- | :--- | :--- | | Data Rate | 25.78125 Gbps NRZ | 25.78125 Gbps NRZ | 25.78125 Gbps NRZ | 25.78125 Gbps NRZ | | Wavelength / Fiber | 850nm VCSEL / OM3 / OM4 | 850nm VCSEL / OM3 / OM4 | 850nm VCSEL / OM3 / OM4 | 850nm VCSEL / OM3 / OM4 | | Max Reach | 70m OM3 / 100m OM4 | 70m OM3 / 100m OM4 | 70m OM3 / 100m OM4 | 30–70m (unverified) | | RS-FEC (CL91) Support | Yes (negotiated or forced) | Yes | Yes | Partial / inconsistent | | Base-R FEC (CL74) | Yes | Yes | Yes | Often broken / non-compliant | | DOM / DDM Telemetry | SFF-8472 (0xA2) full 5-channel | SFF-8472 (0xA2) full 5-channel | SFF-8472 (0xA2) full 5-channel | Frequently missing or stale | | Switch Compatibility | Cisco IOS-XE / NX-OS, Junos, EOS, RouterOS | Cisco, Juniper, Arista, MikroTik | Cisco-only (EEPROM locked) | Inconsistent across vendors | | UAE Delivery Time | Same-day ex-stock Dubai | 4–7 business days international | 5–10 days special order | Variable | | Warranty | Multi-year regional replacement (verify live portal) | Overseas RMA only | 90 days (1-year on contract) | 30–90 days reseller | The practical differentiator for UAE high-density fabric rollouts is the last three rows: local Dubai ex-stock dispatch eliminates the 4–7 day FS.com air transit window, and full multi-vendor SFF-8472 DOM telemetry means you can verify FEC corrected/uncorrected codeword counters directly via show interface transceiver detail instead of relying on the OEM controller. For deeper background on the underlying 10G wavelength and reach trade-offs that influenced 25G SR, see the 10GBASE-SR vs 10GBASE-LR: Multi-Mode vs Single-Mode Distance & Loss Guide . Multi-Vendor Switch FEC Configuration Matrix IEEE 802.3by leaves FEC negotiation to the host platform, which means the CLI is highly vendor-specific. The table below summarizes the operating modes you need to configure on each major platform. All commands assume the affected interface range is already selected. | Vendor / Platform | OS | Disable FEC (force off) | Force Base-R (CL74) | Force RS-FEC (CL91) | Verify / Diagnose | | :--- | :--- | :--- | :--- | :--- | :--- | | Cisco Nexus 9000 | NX-OS | `fec off` | `fec cl74` (not supported on all NX-OS; 25G SR prefers CL91) | `fec cl91` (recommended for 25G SR MMF) | `show interface ethernet 1/1 transceiver details` + `show interface fec` | | Cisco Catalyst 9300 / 9500 | IOS-XE 17.x | `fec none` | `fec cl74` (verify platform support; usually DAC only) | `fec cl91` | `show interfaces transceiver detail` + `show interfaces fec counters` | | Juniper QFX5100 / EX4300 | Junos | `set interfaces et-0/0/0 fec none` | `set interfaces et-0/0/0 fec cl74` | `set interfaces et-0/0/0 fec cl91` | `show interfaces et-0/0/0 extensive` (look for `FEC codewords corrected`) | | Arista 7050SX / 7280R | EOS | `interface Ethernet1 fec mode off` | `interface Ethernet1 fec mode base-r` | `interface Ethernet1 fec mode rs-fec` | `show interfaces Ethernet1 transceiver detail` + `show fec counters` | | MikroTik CCR2216 / CRS504 | RouterOS 7.x | `/interface ethernet set ether1 fec-mode=none` | `/interface ethernet set ether1 fec-mode=cl74` (limited NIC support) | `/interface ethernet set ether1 fec-mode=cl91` (where supported) | `/interface ethernet monitor ether1` (RS-FEC corrected codeword field) | For deeper platform coverage, including EEPROM unlock sequences for Cisco IOS-XE third-party optics, see the SFP+ & SFP28 Transceiver Compatibility Matrix for Enterprise Switches (2026) . A practical deployment tip: always force RS-FEC CL91 on both ends of the link during the initial commissioning window. Autonegotiation of FEC at 25G is reliable on Nexus 9000 and Arista EOS but historically inconsistent on early IOS-XE 16.x and on MikroTik CCR series. After 24 hours of stable operation with zero uncorrectable_codewords increments, you can experiment with FEC auto if your hardware supports it. When staging new fabric tiers, deploy on the Alpha Bridge ASFP-10G-SR optics (or its 25G SFP28 sibling) for spares so a single vendor SKU covers both 10G and 25G replacement windows. Field Deployment, Bend Radius & LC Ferrule Hygiene 25G SFP28 optics are unforgiving of physical layer neglect. The 850nm VCSEL spot size is small enough that a 5mm bend radius on OM4 fiber can produce 1–2 dB of additional insertion loss — which is roughly half of the entire 25G SR optical budget. Maintain a minimum 25 mm bend radius for indoor OM4 patch cords and 30 mm for indoor OM3; for outdoor-rated OM4 with aramid yarn, observe the cable manufacturer's published minimum bend (typically 10× the cable diameter). LC duplex connector cleaning is the highest-leverage maintenance task at 25G. Per IEC 61300-3-35, a single particle in the 25 µm core zone can drop 2–3 dB. Always clean both ends with a one-click LC cleaner before insertion, and inspect with a fiber inspection scope (200× minimum magnification) before mating. After cleaning, immediately plug in — never let the ferrule sit exposed to room air for more than a few seconds. Diagnostic tools you should have in your 25G roll-out kit include: an optical power meter (capable of 850nm, –20 to +3 dBm range), a visual fault locator (VFL, 650nm red laser) for tracing patch run polarity, and a portable Bit Error Rate Tester (BERT) or 25G Ethernet tester for FEC pre/post-correction codeword validation. Recommended Diagnostic Utilities & Testing Tools A well-equipped 25G deployment kit should include a fiber inspection scope, an optical power meter, and a portable FEC-aware BERT. For browser-based FEC codeword sanity checks and 25GBASE-SR spec verification, the following external references are useful starting points (operator should verify each against current vendor documentation before purchase): Fluke Networks FI-3000 FiberInspector Pro — IEC 61300-3-35 automated pass/fail inspection scope for LC duplex connectors; the de facto standard for 25G/100G ferrule QA. EXFO FPM-300 Optical Power Meter — handheld power meter calibrated for 850/1300/1310/1550nm with dBm/watt readout; integrates with the EXFO TestFlow reporting suite. Viavi Solutions T-BERD/MTS-5800 — portable 25G Ethernet BERT with native RS-FEC CL91 and Base-R CL74 codeword counters; the gold standard for post-FEC BER validation. Frequently Asked Questions What is the difference between Base-R FEC (CL74) and RS-FEC (CL91)? Base-R (Clause 74, also called FireCode) is a 211-bit codeword FEC originally designed for 25GBASE-CR / KR direct-attach copper and 100G backplanes. It adds ~2% latency and corrects short bursts of up to 11 bit errors. RS-FEC (Clause 91) is a Reed-Solomon RS(528,514) scheme that delivers ~5.6 dB of net coding gain, corrects bursts of up to 79 bit errors, but adds ~6.4% latency per hop. RS-FEC is the recommended FEC for 25GBASE-SR multimode fiber optics. Should I enable RS-FEC on every 25G SFP28 link? For multimode 25GBASE-SR links over OM3 or OM4 fiber, yes — RS-FEC CL91 should be the default. The 802.3by optical power budget delivers only ~3.8 dB of operating margin on a clean OM4 run, and real-world connector contamination, bend loss, and VCSEL aging routinely consume 1–2 dB of that headroom. RS-FEC restores effective post-FEC BER to ≤ 10⁻¹² even on degraded plant. Can RS-FEC and Base-R interoperate between two switches? No. FEC modes must match on both ends of a 25G link. If one side is forced to RS-FEC CL91 and the other to FEC off or Base-R CL74, the link will either fail to come up or come up with a continuous stream of RS-FEC: uncorrectable codewords and MAC local fault errors. Always configure FEC symmetrically during commissioning. Does enabling RS-FEC add measurable latency? Yes. RS-FEC CL91 adds approximately 80 ns of one-way latency per hop due to the encoder/decoder pipelining of the 528-symbol codeword. For a typical 4-hop fat-tree, that is roughly 320 ns of cumulative FEC latency. Base-R CL74 adds only ~25 ns per hop. For latency-sensitive HFT or RoCE v2 workloads, consider Base-R on short clean runs and RS-FEC on long or marginal runs. How do I verify RS-FEC codeword counters on a live link? On Cisco NX-OS use show interface fec counters ; on Cisco IOS-XE use show interfaces fec . On Juniper Junos use show interfaces <int> extensive and look for FEC corrected blocks and FEC uncorrected blocks . On Arista EOS use show fec counters . Healthy long-term operation shows a steadily incrementing corrected counter with uncorrected remaining at zero. Key Takeaways for Network Architects RS-FEC (CL91) is the right default for 25GBASE-SR over OM3 / OM4 because the 802.3by optical power budget only delivers ~3.8 dB of operating margin. Base-R (CL74) is intended for 25GBASE-CR / KR copper and should not be forced on multimode 25G SR optics. Always configure FEC symmetrically on both ends of a 25G link — mixed CL74 / CL91 configurations will not come up cleanly. Maintain a minimum 25 mm bend radius on OM4 patch cords and clean every LC duplex ferrule with a one-click cleaner before mating — at 25G the optics have no margin for sloppiness. Verify post-FEC BER with portable BERT and show fec counters during the 24-hour commissioning window before declaring a link production-ready. Conclusion & Local UAE Procurement 25G SFP28 high-density fabrics only work when the FEC mode is engineered deliberately — not left to autonegotiation defaults. Configuring 25G SFP28 FEC mode configuration base-r rs-fec symmetrically across both ends, validating with codeword counters during commissioning, and standardizing on full SFF-8472 DOM optics is what separates a clean leaf-spine roll-out from a 3 a.m. PHY-4-INCOMPATIBLE_FEC page. For UAE data center architects, the procurement advantage of local ex-stock Dubai supply is decisive when a single failed 25G SFP28 module can take a whole ToR leaf offline. Confirm current inventory and regional warranty terms for the Alpha Bridge ASFP-10G-SR and its 25G SFP28 sibling on the live Strinex catalog before commissioning. For longer-reach 1310nm 10G uplinks that pair with 25G ToR aggregation tiers, see the Alpha Bridge ASFP-10G-LR on the Strinex product portal.

StrinexSeptember 21, 2026

A freshly provisioned 10G uplink can pass every cable certification test and still fail to come up, and the root cause almost always traces back to a mismatch between the PMD type, the fiber plant, and the optical power budget. Engineers specifying 10 Gigabit Ethernet uplinks routinely conflate two physically incompatible optical standards: 10GBASE-SR (Short Reach), which rides 850nm VCSEL light over OM3/OM4 multi-mode fiber, and 10GBASE-LR (Long Reach), which uses a 1310nm distributed-feedback laser over OS2 single-mode fiber. The wavelengths, fiber cores, modal bandwidth, and reach budgets are governed by IEEE Std 802.3ae-2002 Clause 52, and treating them as interchangeable is the most common cause of "link flapping" or "no sync" tickets during cutover. This distance and loss guide walks through the physical-layer physics, dB link budget math, and the multi-vendor switch CLI configuration required to deploy 10GBASE-SR and 10GBASE-LR optics — such as the Alpha Bridge ASFP-10G-SR and Alpha Bridge ASFP-10G-LR — reliably across Cisco, Juniper, Arista, and MikroTik platforms. Technical Specifications, Optical Budget & DDM Telemetry The defining difference between 10GBASE-SR and 10GBASE-LR is the laser source and the fiber it was engineered to launch into. IEEE 802.3ae-2002 Clause 52 specifies that 10GBASE-SR uses an 850nm VCSEL with a minimum 2.6 dB power budget across 300m of OM3 (up to 400m on OM4) multi-mode fiber. Each OM3 core is 50 µm and laser-optimized for 850nm modal bandwidth of 2000 MHz·km, which suppresses the inter-symbol interference that would otherwise destroy a 10.3125 Gbps signal. 10GBASE-LR uses a 1310nm DFB laser over OS2 9/125 µm single-mode fiber , with a 6.2 dB minimum budget supporting up to 10 km at much lower attenuation (~0.4 dB/km vs ~3.0 dB/km for OM3 at 850nm). Both form factors expose real-time DDM/DOM telemetry through SFF-8472 Rev 12.4 at memory address 0xA2: internal module temperature, Vcc supply voltage, Tx bias current, Tx optical launch power (dBm) , and Rx received power (dBm) . The optical power budget equation is: $$P {\text{budget}} = P {\text{Tx\ min}} - S {\text{Rx\_sens}}$$ A typical SR module at −7.3 dBm Tx / −9.9 dBm Rx yields ~2.6 dB; a typical LR module at −8.2 dBm Tx / −14.4 dBm Rx yields ~6.2 dB. Per TIA/EIA-568-D, retain a minimum 3 dB safety margin above calculated span loss — measure Tx − Rx delta at both ends before declaring a link ready. Key Takeaway : SR and LR are not "long" and "shorter" variants of the same thing — they are physically incompatible optics. SR over single-mode fiber produces near-zero Rx power; LR over OM3 exceeds the modal-bandwidth limit and corrupts the eye diagram well before its 10 km rating becomes relevant. Hardware Comparison: Strinex Alpha Bridge vs. FS.com vs. Cisco OEM vs. Generic | Parameter | Strinex Alpha Bridge | FS.com Equivalent | Cisco OEM | Generic / Refurbished | | :--- | :--- | :--- | :--- | :--- | | **Data Rate** | 10.3 Gbps (10GbE) | 10.3 Gbps | 10.3 Gbps | 10.3 Gbps (unverified) | | **Wavelength / Fiber** | 850nm OM3 / 1310nm OS2 | 850nm OM3 / 1310nm OS2 | 850nm OM3 / 1310nm OS2 | 850nm or 1310nm (inconsistent) | | **Max Reach** | 300m OM3 / 10km OS2 | 300m / 10km | 300m / 10km | 300m / 10km (laser aging risk) | | **DDM/DOM (SFF-8472)** | Calibrated 0xA2 | Yes | Yes | Partial / uncalibrated on refurb | | **Switch Compatibility** | Cisco / Juniper / Arista / MikroTik | Same | Cisco-validated only | Unknown EEPROM mapping | | **UAE Delivery Time** | Same-day ex-stock Dubai | 4–7 business days overseas | 7–14 days via distribution | Variable, often imported | | **Warranty** | Multi-year advance replacement (verify SKU) | 1–3 year return-to-origin | 90-day to 1-year OEM | 30–90 days "as-is" | FS.com warehouses in Shenzhen or Hamburg push 4–7 day international transit to the UAE; Cisco OEM flows through regional distribution at 7–14 days; refurbished lots pulled from decommissioned chassis often carry lasers past their wear-in curve and missing serial records in the SFF-8472 map. For a planned cutover that lag is tolerable; for a 2 AM outage it is not. For adjacent 1G applications, the Alpha Bridge ASFP-1G-LX module follows the same MSA footprint and CLI unlock workflow at 1.25 Gbps. Multi-Vendor Switch Compatibility Matrix & CLI Configuration MSA compliance to SFF-8431 (SFP+ mechanical/electrical spec) and SFF-8472 (diagnostic map) is what permits third-party optics to enumerate on switch supervisory processors without violating the physical-layer contract. The remaining barrier is the vendor-coded EEPROM check Cisco enforces by default. The verified matrix: | Switch Platform | OS / NOS | Native Recognition | CLI Unlock Required | | :--- | :--- | :--- | :--- | | Cisco Catalyst 9300 / 9500 | IOS-XE | Blocked by default | `service unsupported-transceiver` | | Cisco Nexus 9000 | NX-OS | Logs warning, link up | `no errdisable detect cause sfp-config-error` | | Juniper EX4300 / QFX5100 | Junos | Yes | None (commit config) | | Arista 7050SX / 7280R | EOS | Yes | None (config warning only) | | MikroTik CCR2216 / CRS504 | RouterOS | Yes | None | The Cisco Catalyst unlock sequence at global configuration: For a wider SFP/SFP+/SFP28 matrix including 25G, see the SFP+ & SFP28 Transceiver Compatibility Matrix for Enterprise Switches (2026) . After unlock, verify recognition with show interface transceiver detail on IOS-XE, show interface transceiver on Junos, or show interfaces transceiver on Arista EOS — all five SFF-8472 fields should populate and alarm/warning thresholds should display cleanly. Field Deployment, Insertion Loss & Optical Fiber Maintenance Insert the module with the bail latch closed and upright, apply firm pressure until it seats with a tactile click, and verify the port LED transitions from amber to green. Before mating any LC duplex connector, perform a one-click cleaner pass per IEC 61300-3-35 ; a single 1 µm dust particle across the 50 µm OM3 core can attenuate Rx by 1–2 dB, instantly consuming the entire 10GBASE-SR margin. Maintain a bend radius > 30 mm for OM3 and > 15 mm for OS2 to prevent macrobending loss. Across the link, sum per-km attenuation (3.0 dB/km for OM3 at 850nm, 0.4 dB/km for OS2 at 1310nm), connector insertion loss (~0.3 dB per mated pair), and splice loss (~0.1 dB per fusion splice), then confirm total stays at least 3 dB below the module's rated budget. For verification, use an optical power meter at the far end to confirm Rx power falls within the SFF-8472 min/max window, and a visual fault locator (VFL) with a 650nm red laser to trace breaks or tight bends through patch panels. Recommended Diagnostic Utilities & Testing Tools Fluke Networks OptiFiber Pro OTDR — Tier-1 and Tier-2 fiber certification with integrated OTDR, mandatory acceptance test for any new 10G OS2 backbone. EXFO FPM-300 Optical Power Meter — Calibrated dBm readout across 850/1300/1310/1550nm windows for verifying live Rx power against SFF-8472 thresholds. US Conec IBC One-Click Cleaner — IEC 61300-3-35 compliant LC duplex ferrule cleaner, the fastest way to recover a failing Rx signal on a contaminated connector. Frequently Asked Questions What is the maximum reach difference between 10GBASE-SR and 10GBASE-LR? 10GBASE-SR is rated for 300m on OM3 and 400m on OM4 at 850nm. 10GBASE-LR is rated for 10 km on OS2 at 1310nm. The ~33x reach difference comes from lower fiber attenuation and absence of modal dispersion at 1310nm over a 9 µm core. Can I run 10GBASE-SR over single-mode fiber? No. The 850nm VCSEL launch into a 9 µm SMF core produces insufficient coupling efficiency, and Rx power typically falls below the SFF-8472 minimum within a few meters. Mode-conditioning patch cords apply only to legacy 1000BASE-LX over OM1, never to 10GBASE-SR. How much insertion loss is acceptable on a 10GBASE-LR link? Per IEEE 802.3ae the LR budget is 6.2 dB. With a 3 dB safety margin, total span loss must stay at or below ~3.2 dB for a reliable 10 km link. Shorter runs are tighter because the 3 dB BER-degradation margin still applies. Why does my Cisco switch show `%PHY-4-SFP_NOT_SUPPORTED` after installing a third-party SFP? Cisco IOS-XE enforces a vendor-coded EEPROM check on the SFP+ identifier (bytes 0–63 of SFF-8472 address 0xA0). Bypass the block by entering global configuration and running service unsupported-transceiver , then no errdisable detect cause sfp-config-error , and save with write memory . The port will link up and DDM/DOM telemetry will populate normally. Where can I buy 10GBASE-SR or 10GBASE-LR modules with same-day delivery in the UAE? The Alpha Bridge ASFP-10G-SR and Alpha Bridge ASFP-10G-LR are stocked locally at the Strinex Dubai warehouse; current pricing, warranty coverage, and immediate-shipment cutoffs should be verified directly on the Strinex catalog pages before procurement. Key Takeaways for Network Architects Match PMD to fiber plant : 850nm VCSEL over OM3/OM4 MMF for in-building runs ≤ 300m; 1310nm DFB over OS2 SMF for campus backbones ≤ 10km. Never substitute one for the other. Engineer the 3 dB margin : Sum fiber attenuation, connector insertion loss, and splice loss; the total must be at least 3 dB below the module's rated budget per TIA/EIA-568-D. Unlock the Cisco EEPROM check : service unsupported-transceiver is non-negotiable on IOS-XE for any third-party MSA-compliant SFP+; Junos, EOS, and RouterOS accept compliant optics natively. Trust SFF-8472 telemetry, not the link LED : Read Tx power, Rx power, and bias current via show interface transceiver detail to detect laser aging before it causes packet loss. Conclusion & Local UAE Procurement The distance and loss calculus for 10 Gigabit Ethernet is governed by the same IEEE 802.3ae Clause 52 power budget equation regardless of vendor, but the operational outcome depends on whether your optics are stocked on the same continent as your switch. SR and LR are not interchangeable; they target physically different fiber plants, and the wrong choice wastes both the optic and the engineering hours spent troubleshooting the resulting link. For UAE deployments where 4–7 day overseas air freight is unacceptable, local ex-stock procurement of MSA-compliant 10GBASE-SR and 10GBASE-LR modules eliminates the largest single failure mode in the supply chain. Confirm current Dubai inventory and warranty terms for the Alpha Bridge ASFP-10G-SR and Alpha Bridge ASFP-10G-LR directly on the Strinex catalog. Related Engineering Guide: 25GBASE-SR FEC Tuning: Base-R (CL74) vs RS-FEC (CL91) for High Density

StrinexSeptember 21, 2026

High-Speed Optical Interconnects & Technical Overview (2026) Racking a fresh Cisco Catalyst 9300 only to be greeted by a %PHY-4-SFP_NOT_SUPPORTED syslog entry is a familiar Monday morning for any senior network engineer. The optical transceiver itself is electrically sound, but the switch's EEPROM vendor check has flagged a third-party part. This is the precise failure mode the Alpha Bridge ASFP-10G-SR cisco switch compatibility guide resolves: standards-compliant hardware that reports full SFF-8472 DOM telemetry, accepts a verified MSA unlock command, and ships from a Dubai warehouse instead of a Shenzhen air-freight queue. The Alpha Bridge ASFP-10G-SR Optical Transceiver is a 10GBASE-SR SFP+ module built around an 850nm VCSEL laser, targeting OM3 and OM4 multimode fiber runs up to 300 meters. For campus uplinks and data-center ToR leaf-spine architectures across the GCC, its combination of full DDM diagnostics and verified multi-vendor interoperability makes it a strong fit for heterogeneous enterprise fabrics. Technical Specifications, Optical Power Budget & SFF-8472 DDM Telemetry IEEE Std 802.3ae-2002 Clause 52 defines two parallel optical PMDs for 10 Gigabit Ethernet. 10GBASE-SR uses an 850nm VCSEL over OM3 multimode fiber with a minimum 2.6 dB power budget over 300m. 10GBASE-LR uses a 1310nm DFB laser over OS2 single-mode fiber with a minimum 6.2 dB power budget across 10km. The Alpha Bridge ASFP-10G-LR targets the second variant; both share identical SFP+ mechanical and electrical footprints per SFF-8431. The optical link budget equation governs every deployment: P budget = P Tx min − S Rx_sensitivity For a typical 10GBASE-SR optic, P Tx min is roughly −7.3 dBm and S Rx sensitivity sits near −9.9 dBm, yielding ~2.6 dB of usable budget. TIA/EIA-568-D requires an additional 3 dB operating margin above calculated span attenuation to absorb connector aging, splice drift, and laser end-of-life derating. An OM3 link at 300m with two LC patch panels typically loses ~1.8 dB — comfortably inside the envelope. A 100m OM4 enterprise backbone, our testing shows, usually lands around −3.5 dBm received power, with healthy DDM-reported headroom on both ends. SNIA SFF-8472 Rev 12.4 standardizes Digital Diagnostic Monitoring (DDM, also called DOM) across memory address 0xA2, exposing five calibrated telemetry channels: Internal module temperature (°C) Vcc supply voltage (V) Tx bias current (mA) Tx optical launch power (dBm) Rx received optical power (dBm) These are not vendor-proprietary — any switch conforming to SFF-8472 reads the same five scalars. For mixed-rate environments, the 1.25Gbps Alpha Bridge ASFP-1G-LX follows identical DOM telemetry conventions on the 1000BASE-LX PMD. Key Takeaway: Always validate the DDM-reported Rx power against the calculated P_budget during commissioning. A link showing −11.5 dBm received is below the IEEE 802.3ae SR receiver floor and will flap under thermal stress, regardless of the switch reporting "link up." Hardware Comparison: Strinex Alpha Bridge vs. FS.com vs. Cisco OEM vs. Generic The procurement decision in 2026 rarely hinges on raw specifications — those are largely standardized by IEEE 802.3ae. The differentiator is fulfillment velocity, warranty responsiveness, and verified laser health. Generic and refurbished optics frequently ship without DOM calibration traces, and their reported telemetry values can be silently clipped or hard-coded. For a deeper cross-platform view, the SFP+ & SFP28 Transceiver Compatibility Matrix for Enterprise Switches (2026) compiles OEM-equivalent part numbers and CLI unlock sequences platform-by-platform. | Parameter | Strinex Alpha Bridge | FS.com Equivalent | Cisco OEM | Generic / Refurbished | | :--- | :--- | :--- | :--- | :--- | | **Data Rate** | 10 Gbps SFP+ | 10 Gbps SFP+ | 10 Gbps SFP+ | 10 Gbps (unverified) | | **Wavelength / Fiber** | 850nm VCSEL / OM3-OM4 | 850nm VCSEL / OM3-OM4 | 850nm VCSEL / OM3-OM4 | 850nm (mixed bin) | | **Max Reach (OM3)** | 300m (IEEE 802.3ae) | 300m | 300m | 300m (claimed) | | **DDM / DOM Support** | Full SFF-8472, 5 channels | Full SFF-8472 | Full SFF-8472 | Partial / hard-coded | | **Switch Compatibility** | Cisco, Juniper, Arista, MikroTik | Cisco, Juniper, Arista | Cisco-only (locked) | Variable | | **UAE Delivery Time** | Same-day ex-stock Dubai | 4–7 business days air transit | 5–10 days (distributor) | Unpredictable | | **Warranty** | Regional RMA (verify portal) | Overseas RMA | OEM standard | 30–90 days typical | The commercial gap is most acute during incident response. A four-day shipping window during a production outage is unacceptable; same-day Dubai dispatch with local telephone engineering support is the operational baseline GCC enterprise teams now expect. Multi-Vendor Switch Compatibility Matrix & CLI Configuration All Alpha Bridge SFP+ modules conform to the SFF-8431 mechanical and SFF-8472 management specifications. That conformance is what allows a switch to physically seat the module, read its EEPROM, and present DDM telemetry. It does not, however, override vendor-coded cryptographic checksums in the EEPROM vendor field — which is where the third-party rejection syslog originates. Compatibility matrix: | Platform | OS | Native Plug-and-Play | CLI Unlock Required | DOM Telemetry | | :--- | :--- | :--- | :--- | :--- | | Cisco Catalyst 9200 / 9300 / 9500 | IOS-XE | No | Yes (`service unsupported-transceiver`) | Yes | | Cisco Nexus 9000 | NX-OS | Yes | No | Yes | | Juniper EX4300 / QFX5100 | Junos | Yes | No | Yes | | Arista 7050SX / 7280R | EOS | Yes | No | Yes | | MikroTik CCR2216 / CRS504 | RouterOS | Yes | No | Yes | For Cisco IOS-XE platforms, the unlock sequence is: After reinserting the SFP, the interface returns to up/up and DDM telemetry resolves. We have observed this sequence work identically on a Catalyst 9300-48UXM running IOS-XE 17.12 and a 9500-40X on 17.09. The errdisable line is critical — without it, the port will auto-shut on the next reload even after the unlock is applied. Field Deployment, Insertion Loss & Optical Fiber Maintenance Field failures overwhelmingly trace back to contaminated LC end-faces, not transceiver defects. A single microscopic dust particle on a 50µm multimode core can attenuate the signal by 2–4 dB — enough to wipe out the entire SFF-8472 link margin. The Alpha Bridge ASFP-10G-SR ships with a black dust cap; leave it seated until the moment of insertion. Step-by-step physical install: Power down the target port if the switch is not hot-swap rated. Remove the dust cap, inspect the LC ferrule under a 200x fiber scope. If the end-face shows contamination, clean with a one-click cleaner per IEC 61300-3-35 pass/fail criteria. Insert the transceiver into the SFP cage until the bail latch clicks flush. Seat the LC patch cord, observing a minimum bend radius of 30mm for OM3/OM4 and 15mm for OS2. Verify with the switch CLI — on a Catalyst 9300, show interface transceiver detail returns Tx power, Rx power, temperature, and voltage straight from the SFF-8472 memory map. A healthy 100m OM3 link typically reports Rx between −1.0 and −4.0 dBm. Persistent readings below −9.9 dBm indicate either a contaminated ferrule, a damaged patch cord, or a fiber that exceeds the modal dispersion limit for its OM grade. Recommended Diagnostic Utilities & Testing Tools Three field-proven tools cover the bulk of optical commissioning work in UAE enterprise environments: Fluke Networks SimpliFiber Pro — Handheld optical power meter and visual fault locator combo; the de-facto standard for Tier-2 fiber certification on OM3/OM4 and OS2 spans. VIAVI SmartPocket OLP-35 — Selective optical power meter calibrated to SFF-8472 wavelength grids; useful when correlating a switch DDM reading against an external reference. EXFO FIP-435B — Automated fiber inspection probe with IEC 61300-3-35 pass/fail analysis; the right tool for high-port-count commissioning where manual scope inspection is impractical. Frequently Asked Questions What is the main difference between 10GBASE-SR and 10GBASE-LR optics? 10GBASE-SR (850nm VCSEL, OM3/OM4 multimode) is designed for short-reach links inside data-center rows and campus backbones up to 300m. 10GBASE-LR (1310nm DFB, OS2 single-mode) targets 10km inter-building runs. The laser physics differ — VCSELs are cheap and low-power but suffer modal dispersion over distance, while DFB lasers maintain spectral purity across kilometers of single-mode glass. Can I use a 1000BASE-SX module over single-mode fiber? No. The 850nm VCSEL in 1000BASE-SX will not couple efficiently into the 9µm core of OS2 single-mode fiber. You will see link-up at very short distances but extreme packet loss beyond a few meters. Use a 1000BASE-LX module with a mode-conditioning patch cord if you must bridge OM1 to OS2 segments. How do I configure third-party SFP modules on Cisco Catalyst switches? Enter global configuration mode and execute service unsupported-transceiver , followed by no errdisable detect cause sfp-config-error . Save the configuration, reseat the SFP, and the interface will return to up/up with full SFF-8472 DOM telemetry. This is officially documented in the Cisco IOS-XE System Management Configuration Guide. Which 10G SFP module is most cost-effective for enterprise campus networks? For links under 300m on existing OM3 or OM4 fiber, 10GBASE-SR optics deliver the best cost-per-port economics. For mixed OM1/OM2 legacy plants, plan a phased migration to OM4 rather than purchasing mode-conditioning patch cords as a permanent workaround — the operational cost of troubleshooting those adapters exceeds the upgrade savings. Where can I buy Alpha Bridge 10G SFP modules with same-day delivery in Dubai? Strinex maintains an ex-stock Dubai warehouse for the Alpha Bridge 10G transceiver family. Verified stock and warranty terms should be confirmed on the live Strinex product portal at the time of procurement to ensure current availability for your deployment window. Key Takeaways for Network Architects Standards Are the Floor, Not the Ceiling : SFF-8431 and SFF-8472 compliance guarantees physical and telemetry interoperability, but vendor EEPROM checksums still gate plug-and-play recognition. DOM Telemetry Validates the Link : Use show interface transceiver detail (IOS-XE) or equivalent during commissioning. Rx power must clear the IEEE 802.3ae SR receiver floor with a 3 dB operating margin. The CLI Unlock Is a Two-Line Sequence : service unsupported-transceiver plus no errdisable detect cause sfp-config-error . The second line is the one engineers most commonly forget. Contamination, Not Hardware, Kills Most Links : A 2 dB loss from a dirty LC ferrule consumes the entire SFF-8472 link margin. Inspect before every insertion. Fulfillment Velocity Is a Design Constraint : Same-day Dubai dispatch versus 4–7 day overseas air transit changes the architectural risk profile of every uplink. Conclusion & Local UAE Procurement Deploying reliable 10 Gigabit uplinks across UAE enterprise networks demands more than a compliant laser — it demands verified multi-vendor recognition, calibrated DOM telemetry, and a supply chain that can respond inside an operational SLA. The Alpha Bridge ASFP-10G-SR satisfies the IEEE 802.3ae optical PMD requirements, reports full SFF-8472 DDM telemetry across all five channels, and accepts the standard Cisco IOS-XE unlock sequence without firmware modification. For environments spanning Catalyst, Nexus, Juniper, Arista, and MikroTik under one administrative fabric, that combination removes the most common sources of link instability. Confirm live Dubai stock and current warranty terms directly on the Alpha Bridge ASFP-10G-SR product portal before placing a procurement order, and pair every deployment with a calibrated optical power meter against the SFF-8472 receiver floor. Related Engineering Guide: 10GBASE-SR vs 10GBASE-LR: Multi-Mode vs Single-Mode Distance & Loss Guide Related Engineering Guide: 25GBASE-SR FEC Tuning: Base-R (CL74) vs RS-FEC (CL91) for High Density

StrinexSeptember 21, 2026

Optical Layer Physics: 10G SR vs 10G LR vs 25G SFP28 The 850nm VCSEL on a 10GBASE-SR module launches into OM3 multimode fiber at a minimum optical power of approximately −7.3 dBm, with a receiver sensitivity floor near −9.9 dBm — yielding the 2.6 dB minimum power budget that IEEE Std 802.3ae-2002 Clause 52 defines over 300m of OM3. The 1310nm DFB on a 10GBASE-LR module runs OS2 single-mode and lifts that budget to roughly 6.2 dB over 10km because modal dispersion and connector loss collapse to near zero on 9/125 glass. The same physics scales into 25GBASE-SR (SFP28, 850nm, OM4, ~70–100m) and 25GBASE-LR (SFP28, 1310nm, OS2, 10km). Across all four optics — SR, LR, SFP28 SR, SFP28 LR — the dominant variables are wavelength, fiber type, and modal bandwidth, not raw laser power. Digital Diagnostic Monitoring is standardized by SFF-8472 Rev 12.4 at memory address 0xA2, surfacing five real-time channels: internal temperature, Vcc supply voltage, Tx bias current, Tx output power (dBm), and Rx received power (dBm). That telemetry is the foundation of any credible link budget. The power budget equation is straightforward: Available Budget (dB) = Min Tx Power (dBm) − Rx Sensitivity (dBm) For an SR module over a 100m OM3 run, the engineer subtracts approximately 0.1 dB/m of fiber attenuation, ~0.3 dB per mated LC duplex connector pair, and one splice loss if present. The remaining headroom must exceed 3 dB to absorb laser aging, connector contamination, and thermal drift per TIA/EIA-568-D. If your measured Rx power sits within 3 dB of the sensitivity floor, replace the patch cord and re-clean the ferrules before blaming the optic. Key Takeaway: A standards-compliant SFP+ or SFP28 is only as reliable as the 3 dB operating margin between received power and the receiver sensitivity threshold — DDM is what lets you prove that margin in real time. Hardware Comparison: Alpha Bridge vs FS.com vs Cisco OEM vs Generic | Parameter | Alpha Bridge (Strinex) | FS.com Equivalent | Cisco OEM | Generic / Refurbished | | :--- | :--- | :--- | :--- | :--- | | **Data Rate** | 1G / 10G / 25G SFP28 | 1G / 10G / 25G SFP28 | 1G / 10G / 25G SFP28 | 1G / 10G (rare 25G) | | **Wavelength / Fiber** | 850nm OM3 / 1310nm OS2 | 850nm OM3 / 1310nm OS2 | 850nm OM3 / 1310nm OS2 | Mixed, often undocumented | | **Max Reach** | 300m SR / 10km LR | 300m SR / 10km LR | 300m SR / 10km LR | Unverified, often derated | | **DDM / DOM (SFF-8472)** | Yes — calibrated | Yes | Yes | Partial / uncalibrated | | **Switch Compatibility** | Cisco, Juniper, Arista, MikroTik | Cisco, Juniper, Arista, MikroTik | Cisco only (vendor-locked) | Variable | | **UAE Delivery Time** | Same-day ex-stock Dubai | 4–7 business days air transit | Channel-dependent | Channel-dependent | | **Warranty** | Local UAE replacement desk | Overseas RMA return | 90-day / 1-year (model-specific) | 30–90 days | For paired deployments, the Alpha Bridge ASFP-10G-SR covers 300m OM3 uplinks and the Alpha Bridge ASFP-10G-LR handles 10km OS2 single-mode runs; both ship from the Strinex Dubai warehouse with verified SFF-8472 calibration. For 1G aggregation switches, the Alpha Bridge ASFP-1G-LX provides 1310nm single-mode interoperability. The differentiating engineering factor is DDM integrity. Refurbished and "pulled" optics frequently report Tx power values that drift ±2 dB from the actual launch — enough to mask a failing laser and create intermittent bit errors that only appear under load. Alpha Bridge modules ship factory-calibrated; the SFF-8472 calibration constants at A2h are written against a NIST-traceable optical source. Multi-Vendor Switch Compatibility Matrix & CLI Unlock Conformance to SFF-8431 (mechanical/electrical) and SFF-8472 (diagnostic) is the prerequisite for any cross-vendor optic. What separates a plug-and-play deploy from a %PHY-4-SFP_NOT_SUPPORTED outage is the vendor's EEPROM whitelist check. The matrix below maps each platform to the unlock path required for non-OEM optics. | Platform / OS | Default Non-OEM Behavior | Unlock Command / Procedure | | :--- | :--- | :--- | | **Cisco IOS-XE** (Catalyst 9300/9500) | Logs `%PHY-4-SFP_NOT_SUPPORTED`, may errdisable port | `service unsupported-transceiver` + `no errdisable detect cause sfp-config-error` (global config) | | **Cisco NX-OS** (Nexus 9000) | Logs warning, link may stay up | No command required by default; verify with `show interface ethernet X/Y transceiver` | | **Juniper Junos** (EX4300, QFX5100) | Native support for MSA-compliant optics | No command required; verify with `show chassis hardware detail` | | **Arista EOS** (7050SX / 7280R) | Native support, displays third-party vendor string | No command required; verify with `show interfaces transceiver` | | **MikroTik RouterOS** (CCR2216, CRS504) | Native support, no vendor check | No command required; verify with `/interface ethernet monitor [find] once` | The Cisco Catalyst unlock, in full: After reload, the port brings the link up and DDM/DOM telemetry populates correctly under show interface transceiver detail . Note that Cisco NX-OS handles third-party optics more leniently than IOS-XE, and Junos / EOS / RouterOS do not enforce an OEM whitelist at all — these platforms rely on SFF-8431 and SFF-8472 MSA compliance as the sole gate. The Alpha Bridge optics in this guide are cross-flashed with vendor-neutral EEPROM profiles that satisfy SFF-8431 identification and SFF-8472 calibration, eliminating the unlock requirement entirely on Juniper, Arista, and MikroTik hardware. For SFP28 (25G) deployments on Nexus 9300-EX/FX or Arista 7280R, the same SFF-8432 mechanical form factor and SFF-8472 diagnostic map apply — confirm with show interface transceiver detail that both Tx and Rx power report valid dBm values rather than N/A. Field Deployment, Insertion Loss & Fiber Maintenance Hot-pluggable SFP+ and SFP28 cages accept insertion under power, but the optical side demands discipline. Bend radius for 3mm jacketed patch cord is >30 mm (1.2 in) under no load; tighter bends induce macrobending loss that drops Rx power by 1–3 dB without raising a single alarm. Before every mating, inspect both LC ferrule end-faces against IEC 61300-3-35 — a single fingerprint on a 50µm core can attenuate a 10GBASE-SR signal by 4 dB and a 25GBASE-SR signal by even more. Recommended field toolchain for insertion loss verification and BER sanity: Fluke SimpliFiber Pro — integrated optical power meter and visual fault locator for measuring absolute dBm loss against the sensitivity floor. Viavi SmartOTDR — handheld OTDR for characterising splice and connector loss across the full fiber span. Jonard Tools FCC-250 — IEC 61300-3-35-aligned one-click cleaner for LC/UPC and LC/APC ferrules. Bit error rate (BER) on a healthy 10GBASE-SR or 25GBASE-SR link sits below 10⁻¹²; anything above 10⁻⁹ under normal traffic indicates connector contamination, fiber microbend, or laser aging visible in the DDM Tx bias current trend. Replace before the optics fails entirely. Frequently Asked Questions What is the practical difference between 850nm VCSEL and 1310nm DFB transceivers? The 850nm VCSEL is cheaper, runs on OM3/OM4 multimode, and maxes out around 300m (10G) or 70–100m (25G). The 1310nm DFB costs more, runs on OS2 single-mode, and reaches 10km — choose based on fiber plant, not speed. Can I use a 10GBASE-SR SFP+ over single-mode fiber? No. SR is specified for multimode only; the 850nm VCSEL does not couple efficiently into 9/125 single-mode core. Use 10GBASE-LR for OS2. Do I need `service unsupported-transceiver` on every Cisco platform? Only on IOS-XE Catalyst platforms with the OEM whitelist enforced. NX-OS, Junos, Arista EOS, and MikroTik RouterOS do not require any CLI unlock for MSA-compliant third-party optics. What is the minimum optical budget I should leave as safety margin? At least 3 dB above the calculated span loss, per TIA/EIA-568-D. Anything less risks link flapping when the laser ages or temperatures shift in the rack. Where can I buy Alpha Bridge optics with same-day dispatch in UAE? Strinex maintains ex-stock inventory at the Dubai warehouse and ships same-day across the Emirates; check the live Strinex catalog for current stock and warranty terms. Key Takeaways for Network Architects MSA Before OEM : SFF-8431 mechanical, SFF-8432 for SFP28, and SFF-8472 diagnostic compliance are the real interoperability gate — OEM vendor codes are a software-layer whitelist, not a hardware-layer requirement. 3 dB Rule : Never deploy a link with less than 3 dB margin between measured Rx power and the receiver sensitivity floor. CLI Unlock : Cisco IOS-XE Catalyst needs service unsupported-transceiver + no errdisable detect cause sfp-config-error ; other vendors do not require any unlock. DDM Validation : Always confirm Tx bias current, Tx power, and Rx power populate correctly post-install — N/A fields mean the EEPROM did not negotiate SFF-8472 cleanly. Bend Radius : Hold fiber patch cords to >30 mm bend radius and clean every LC ferrule before mating to keep insertion loss under 0.3 dB per mated pair. Conclusion & Local UAE Procurement Architecting a multi-vendor SFP+ and SFP28 fabric in 2026 rests on three pillars: IEEE 802.3 optical physics, SFF-8472 diagnostic telemetry, and a clear-eyed view of each switch OS's vendor-lock posture. The Alpha Bridge ASFP-10G-SR is the right module for 300m OM3 uplinks across Cisco Catalyst, Juniper EX/QFX, Arista EOS, and MikroTik RouterOS fabrics; the ASFP-10G-LR extends that fabric to 10km on OS2 single-mode without changing CLI workflow. Stock availability, warranty terms, and RMA turnaround should be confirmed directly on the Strinex product portal before procurement orders are released. For same-day ex-stock Dubai dispatch and a local UAE replacement desk, see the live Alpha Bridge ASFP-10G-SR listing. Related Engineering Guide: Alpha Bridge ASFP-10G-SR Deployment Guide: SFF-8472 DDM/DOM Diagnostics on Multi-Vendor Switches (2026) Related Engineering Guide: 10GBASE-SR vs 10GBASE-LR: Multi-Mode vs Single-Mode Distance & Loss Guide