100G QSFP28 links have moved from data center spines into Fortinet campus cores, FortiLink aggregation tiers, and FortiGate perimeter handoffs. The interface is no longer exotic, but interoperability testing on Fortinet platforms remains more configuration-sensitive than on 10G or 1G. The optical module can be MSA-compliant, the fiber can be clean, and both ends can report good light levels—and the link still will not come up. The cause is usually not the optic itself, but a mismatch between the module’s internal FEC architecture, the host port’s FEC and mediatype settings, and the remote device’s expectations.
This guide treats 100G interoperability as a layered validation problem. It covers the FEC and mediatype boundaries that define whether a 100G link can establish, the FortiSwitch and FortiGate configuration levers that must be set deliberately rather than left at defaults, the per-lane diagnostic data used to confirm optical margin, and a structured procedure that separates configuration faults from module faults and physical-layer faults. The focus is on the configuration logic that applies across FortiSwitch data center models and FortiGate platforms with 100G QSFP28 ports, including the third-party module cases where FEC mismatch is the dominant failure mode.
1. FEC Is the Primary 100G Interoperability Variable
Forward Error Correction is not optional background behavior at 100G. It is the single most frequent cause of a 100G link that reports optical power but never reaches an up state, or that comes up and then accumulates errors under traffic. The difficulty is that different 100G QSFP28 physical-layer types handle FEC in different places, and Fortinet platforms apply FEC defaults that are correct for some module families and wrong for others.
| QSFP28 Type | Where FEC Sits | Host FEC Expectation | Typical Fortinet Behavior |
|---|---|---|---|
| 100GBASE-DR | Line-side FEC inside the module; host interface is 4-lane NRZ via internal gearbox | Host FEC must be disabled | mediatype dr forces forward-error-correction disable; this is the only selectable FEC value in that mode |
| 100GBASE-FR | RS-FEC runs inside the module | Host FEC left off or on auto; forcing RS-FEC on the port brings the link down | Do not force host FEC when an FR module is installed |
| 100GBASE-LR4 / CWDM4 | 4-lane NRZ host interface; host FEC is part of the link budget | Host FEC typically enabled (cl91-rs-fec is the common 100G mode) | Host FEC should match the platform default or the documented mode for the module and remote end |
| 100G BiDi / cross-vendor | Depends on module design; FEC family mismatch is a frequent failure | May require explicit host FEC disable when the remote device does not use a compatible FEC family | FortiGate defaults to cl91-rs-fec on 100G ports; this can conflict with third-party peers |
1.1 100GBASE-DR: Host FEC Must Be Off, and mediatype dr Enforces It
100GBASE-DR QSFP28 transceivers use a single 1310nm PAM4 optical lane and an internal gearbox to convert between the 4-lane NRZ host interface and the 1-lane line side. The module implements FEC internally on the line side; no FEC is required on the host interface. Starting with FortiOS 7.6.1 GA, dr was added as a valid mediatype option for 100G interfaces, and setting mediatype dr automatically sets forward-error-correction to disable. That is not a convenience—it is mandatory, because the DR architecture does not support host-level FEC[reference:0].
config system interface edit port34 set mediatype dr end
The CLI confirms the FEC change: changing FEC to disable because of a mediatype change to dr. If host FEC is enabled while a DR module is installed, the link stays down. DR transceivers also do not support 40G operation because of the gearbox architecture, so a port configured for 40G will not link with a DR module regardless of FEC settings[reference:1].
1.2 100GBASE-FR: Leave Host FEC Alone
FR modules similarly run RS-FEC inside the module. The host FEC should remain off or on auto. Forcing RS-FEC on the switch port with an FR module installed will bring the link down. The far end must also be a compatible single-lambda optic with onboard FEC; an FR module will not interoperate with an LR4 module even though both are nominally 100G single-mode interfaces.
1.3 LR4 and CWDM4: Host FEC Is Part of the Link
LR4 and CWDM4 modules use a 4-lane NRZ host interface, and host FEC is part of the link budget. FortiGate and FortiSwitch platforms commonly default to cl91-rs-fec on 100G ports, and this is the appropriate mode for many LR4 deployments. The validation question is not whether FEC should exist, but whether the host FEC mode matches what the remote device expects. A FortiGate-to-FortiGate LR4 link may work with the default, while a FortiGate-to-third-party-switch LR4 link can fail if the third-party switch uses a different FEC mode or disables FEC by default.
1.4 Cross-Vendor BiDi: When “Good Light, No Link” Means FEC Mismatch
The most instructive 100G interoperability case is a FortiGate 100G port with a BiDi QSFP28 connected to a Juniper QFX switch. Both ends report good optical power, but the link never comes up. FortiGate enables cl91-rs-fec by default on 100G ports; Juniper does not enable FEC by default, and the FEC families available on the two platforms do not overlap in a compatible way. Disabling FEC on the FortiGate side is what allows the link to establish in that mixed environment[reference:2].
config system interface edit portXX set speed 100Gfull set mediatype sr4 set forward-error-correction disable end
This is not a universal prescription for all BiDi links, but it establishes the validation principle: when a 100G link reports optical power but no link, compare the FEC state and FEC family on both ends before replacing the module. A module that “fails” in a FEC-mismatched link may be fully functional once the host configuration is aligned.
FEC is a per-port and per-module decision, not a global policy: A FEC setting that is correct for an LR4 module can bring down a DR link on the same platform. A FortiGate default that works for FortiGate-to-FortiGate links can prevent a FortiGate-to-third-party link from coming up. Validate FEC against the specific module type and the specific remote device, not against a template or a previous deployment.
2. FortiSwitch fec-state: Options, Defaults, and Model Dependencies
FortiSwitch exposes FEC per physical port through the fec-state setting. The available values vary by model and port type, and the default behavior has changed across FortiSwitchOS releases.
fec-state Value | Applies To | Behavior |
|---|---|---|
cl91 | 25G and 100G ports | Clause 91 RS-FEC. Historically the default for 100G ports starting in FortiSwitchOS 6.4.0. |
cl74 | 25G ports | Clause 74 Fire-Code FEC. Default for 25G ports starting in FortiSwitchOS 6.4.0. |
cl108 | 25G ports on FS-3032G | Clause 108 RS-FEC, model-specific. |
detect-by-module | 25G and 100G ports; split ports from FortiSwitchOS 7.0.1 | Automatically detects whether FEC is supported by the inserted module. Default on FS-1048E and FS-3032E 25G/100G ports starting in FortiSwitchOS 7.0.0. |
disabled | 25G and 100G ports | Turns FEC off on the port. |
The 100G ports of the FS-1048E, FS-3032E, FS-3032G, and FS-2048F support cl91, detect-by-module, and disabled. The FEC state can be verified with diagnose switch physical-ports list [reference:3].
config switch physical-port edit port49 set fec-state detect-by-module end
2.1 detect-by-module and Third-Party Module Cases
detect-by-module is the practical starting point for third-party 100G modules on FortiSwitch, because it allows the port to adapt to the module’s FEC capability rather than imposing a fixed clause mode. For modules such as the AFBR-89BDDZ-FN1, Fortinet documents that the port remains down without the correct FEC configuration, and setting fec-state detect-by-module on both standalone FortiSwitches is the documented fix[reference:4].
For FortiSwitches managed by FortiGate, the workflow differs by firmware version. Below FortiOS 7.4.2, FEC must be disabled on both sides. Starting in 7.4.2, detect-by-module becomes available for managed FortiSwitches through the switch-controller workflow[reference:5]. The validation step is to confirm which firmware path applies before assuming that a standalone fix will translate directly to a FortiLink-managed environment.
2.2 When detect-by-module Is Not Enough
Some third-party modules present FEC capability data that detect-by-module interprets in a way that still does not match the remote endpoint. In those cases, explicitly setting disabled or a specific clause mode may be required. The decision should be based on the module datasheet, the remote device’s FEC configuration, and the observed link behavior—not on a default that worked for a different module family.
3. Port Speed and Mediatype Boundaries at 100G
FEC is the first gate, but speed and mediatype are the second. A 100G port will not present the expected mediatype options until the speed is set to 100Gfull.
3.1 100Gfull Unlocks SR4, LR4, and CR4
On FortiGate platforms, the sr4, lr4, and cr4 mediatype options become selectable only when the interface speed is set to 100Gfull. To see LR4, SR4, and CR4 media types on a FortiSwitch port, the port speed must likewise be set to 100Gfull.
config system interface edit port49 set speed 100Gfull set mediatype lr4 end
For an SR4 module, set mediatype sr4 is used. For a copper 100G DAC, set mediatype cr4 applies. The mediatype must match the physical-layer type of the installed module. A DR module requires the dr mediatype and does not use the sr4/lr4/cr4 selection.
3.2 The Missing 100Gauto Option on Some Platforms
Not every 100G port supports auto-negotiation at 100G. On FortiGate 2600F series ports 33–36 running FortiOS 7.2.x, the 100Gauto speed option is missing, and the port must be configured with set speed 100Gfull. The issue was resolved in FortiOS 7.2.9, 7.4.4, and 7.6.0. On platforms or firmware releases where 100Gauto is unavailable, validation must proceed with the explicit 100Gfull setting rather than expecting auto-negotiation to select the correct speed[reference:7].
3.3 Speed and Mediatype Consistency Across the Link
A 100G link requires both ends to agree on speed and FEC, and—where the mediatype affects the physical-layer encoding—on a compatible mediatype. A FortiGate port configured for sr4 connected to a remote LR4 interface will not link, even if the fiber were compatible, because the two ends are not using the same physical-layer standard. The validation sequence should confirm module type at both ends before any optical measurement is interpreted.
4. Module Recognition and Per-Lane DDM Verification
Once FEC, speed, and mediatype are aligned, the next validation layer is confirming that the host recognizes the module and that per-lane optical data is available and meaningful.
4.1 Module Identification
get switch modules detail port49
On FortiSwitch, this command returns the module identifier, connector, transceiver type, encoding, vendor name, vendor part number, serial number, and manufacturing date. For a 100G module, the transceiver type should reflect the actual physical-layer family—SR4, LR4, DR, or CWDM4—rather than a generic “100G” label. A mismatch between the reported type and the label points to EEPROM coding or module-selection issues rather than an optical fault[reference:8].
4.2 Per-Lane DDM Status
get switch modules status port49
For a 100G QSFP28 module, DDM output includes per-lane temperature, voltage, laser bias, TX power, RX power, and alarm/warning flags. A representative 4-lane 100G output shows four sets of tx_power[n] and rx_power[n] values, one for each lane[reference:9]. This per-lane view is essential: a link can report overall “up” while one lane is marginal, and traffic errors may appear only under load or after thermal drift.
DDM readings are monitoring values, not calibrated measurements. When evaluating a marginal 100G link, the per-lane RX power should be compared against the module’s receiver sensitivity and overload limits, and a calibrated optical power meter should be used when a decision depends on precise link-budget verification.
4.3 DMI Enablement and Availability
If DDM output is unavailable, confirm that DMI is enabled on the port. The dmi-status setting accepts disable, enable, or global; global inherits the system-wide DMI behavior. DMI is supported on most FortiSwitch models, but not all, and the module itself must support the diagnostic registers[reference:10].
5. Structured 100G Interoperability Validation Procedure
A reproducible 100G validation sequence should separate FEC configuration, speed/mediatype configuration, module recognition, optical performance, and traffic stability, so that a failure at each stage is attributed to the correct layer.
| Stage | Validation Action | Expected Result |
|---|---|---|
| 1. Module identification | Read get switch modules detail and compare transceiver type with the label. | Reported type matches the physical module (SR4, LR4, DR, CWDM4). |
| 2. Speed and mediatype | Set speed 100Gfull and the matching mediatype (sr4, lr4, cr4, or dr). | Mediatype options are selectable and consistent with the module and remote end. |
| 3. FEC alignment | For DR/FR: confirm host FEC disabled. For LR4/CWDM4: confirm host FEC mode matches the remote. For BiDi/cross-vendor: compare FEC families and disable if necessary. | Host FEC state matches the module architecture and the remote endpoint’s FEC expectation. |
| 4. Link establishment | Check operational state and confirm the link comes up without repeated transitions. | Interface reaches stable up state. |
| 5. Per-lane DDM | Read get switch modules status and record per-lane TX/RX power, temperature, and alarm flags. | All lanes are within module limits; RX power has margin above sensitivity on every lane. |
| 6. Error counters | Review FEC and pre-FEC/post-FEC error statistics where exposed. | Error performance meets deployment requirements. |
| 7. Traffic verification | Run bidirectional traffic at the intended load. | Traffic passes without unexpected loss or errors. |
| 8. Stability monitoring | Monitor link state, per-lane DDM, error counters, and temperature over time. | No link flapping, lane degradation, or progressive error accumulation. |
5.1 Optical Power and Per-Lane Margin
For 100G optical links, RX power should be checked at both endpoints on every lane. The basic relationship remains:
Optical Link Loss (dB) = Transmitted Power (dBm) − Received Power (dBm)
For LR4 and CWDM4 links, splice loss, connector quality, and the multiplexing architecture dominate the loss budget. For DR and FR single-lambda links, the internal FEC and PAM4 line side impose different optical and error-performance requirements, and the module specification should be used for the applicable per-lane limits. A link that is up but has one lane near sensitivity is not a validated link, even if the other three lanes have margin.
5.2 Traffic and FEC Error Verification
A 100G link can report “up” while still failing to pass traffic reliably if FEC is misconfigured or the optical path is marginal. Pre-FEC and post-FEC error counters should be recorded where the platform exposes them. For DR modules, confirm that host FEC is disabled as required. For cross-vendor BiDi or CWDM4 links, confirm that the FEC state on both ends is compatible before concluding that the module is defective. A link that comes up but accumulates errors under load is a configuration or margin problem, not necessarily a hardware failure.
6. Common 100G Interoperability Problems and Diagnostic Checks
| Observed Symptom | Likely Cause | Diagnostic Check |
|---|---|---|
| Link down with DR module; good optical power | Host FEC enabled when DR requires FEC disabled | Set mediatype dr; confirm forward-error-correction disable in running config. |
| Link down with FR module | Host RS-FEC forced on the port | Leave host FEC off or on auto; do not force RS-FEC with FR. |
| Link down with good light on cross-vendor BiDi | FEC family mismatch (FortiGate cl91-rs-fec vs peer no-FEC or different FEC) | Disable FEC on the FortiGate side; compare FEC capabilities on both ends. |
| Port down with third-party 100G module on FortiSwitch | fec-state not matching module requirement | Set fec-state detect-by-module; if unresolved, test disabled. |
Mediatype sr4/lr4/cr4 unavailable | Speed not set to 100Gfull | Set speed 100Gfull first; then configure mediatype. |
| Link up but errors under traffic | Marginal per-lane RX power, FEC mismatch, or connector contamination | Review per-lane DDM, FEC counters, and optical measurements at both ends. |
| Breakout subports do not come up | phy-mode mismatch or unsupported breakout combination | Verify platform breakout capability and lane mapping against the module and remote end. |
Fortinet troubleshooting guidance for 100G link failures consistently prioritizes FEC and mediatype configuration before hardware replacement. On FortiSwitch, detect-by-module resolves many third-party module cases; on FortiGate, mediatype dr or explicit forward-error-correction disable is required for modules that handle FEC internally. The diagnostic order matters: FEC first, speed/mediatype second, module recognition third, optical measurement fourth, traffic verification last.
7. C-LIGHT 100G QSFP28 Modules and Interoperability Testing
C-LIGHT provides 100G QSFP28 optical transceivers covering SR4, LR4, CWDM4, ER4, and extended-reach variants, along with multi-rate QSFP options for 100G/40G dual-rate applications. The portfolio includes modules designed for data center, enterprise, and carrier environments, with DDM/DOM support on applicable models.
| C-LIGHT QSFP28 Product | Interface | Fiber Type | Wavelength / Structure | Typical Reach | Connector |
|---|---|---|---|---|---|
| 100G QSFP28 SR4 | 100GBASE-SR4 | MMF | 850nm, 4 parallel lanes | 100m (OM4) | MPO-12 |
| 100G QSFP28 LR4 | 100GBASE-LR4 | SMF | 1310nm LAN-WDM, 4 lanes | 10km | Duplex LC |
| 100G QSFP28 CWDM4 | 100GBASE-CWDM4 | SMF | 1270–1330nm CWDM, 4 lanes | 2km | Duplex LC |
| 100G QSFP28 ER4 | 100GBASE-ER4 | SMF | 1310nm LAN-WDM, 4 lanes | 40km | Duplex LC |
| 100G/40G Multi-Rate QSFP | 100G / 40G dual-rate | SMF / MMF (model-dependent) | Model-dependent | Model-dependent | LC / MPO |
Product information: C-LIGHT 100G/40G Multi-Rate QSFP Optical Transceivers
C-LIGHT’s interoperability testing for multi-vendor optical transceivers covers physical compatibility, electrical interfaces, optical performance, module management, FEC behavior, link stability, and sustained data transmission. For 100G specifically, the test scope includes the exact physical-layer interface, lane mapping, modulation format, FEC requirements, optical reach, fiber type, and thermal conditions—the same layers that determine whether a third-party QSFP28 will operate reliably on a Fortinet host[reference:11]. Testing can be aligned to the exact FortiSwitch or FortiGate model, port, FortiSwitchOS/FortiOS release, module part number, and remote endpoint.
Related service: C-LIGHT Optical Transceiver Compatibility Testing
When requesting a Fortinet 100G interoperability test, providing the host model and hardware revision, software release, port identifier, module physical-layer type, FEC expectation, fiber type and link distance, breakout requirement if any, and remote device type allows the evaluation to reproduce the actual deployment conditions rather than relying on a generic 100G QSFP28 specification.
8. Conclusion
100G optical interoperability on Fortinet platforms is governed less by the optic than by the configuration logic around it. FEC is the primary gate: DR and FR modules require host FEC to be disabled, LR4 and CWDM4 links depend on host FEC matching the remote end, and cross-vendor BiDi links can report good light while never coming up because the FEC families do not match. FortiSwitch fec-state options and FortiGate mediatype settings are the levers that must be set deliberately, not left at defaults that were designed for a different module family.
Speed and mediatype form the second gate. 100Gfull unlocks the sr4, lr4, and cr4 options, and the mediatype must match the physical module rather than a generic 100G expectation. Per-lane DDM and traffic verification form the third gate: a link that is up on all lanes but marginal on one is not a validated link, and a link that passes light traffic but accumulates errors under load is not ready for production.
C-LIGHT provides 100G QSFP28 modules across SR4, LR4, CWDM4, ER4, and multi-rate families, along with interoperability testing that covers FEC behavior, lane mapping, optical performance, and sustained traffic against the actual Fortinet host and remote environment. Contact C-LIGHT to discuss your 100G interoperability testing requirements for Fortinet platforms.
TEL:+86 132 6656 7067




















































>
>
>
>
>
>
>
>