100G QSFP28 links are now a standard building block in data center leaf-spine fabrics, high-capacity campus backbones, and storage interconnect. On Fortinet platforms—particularly FortiSwitch data center models and high-end FortiGate appliances—third-party QSFP28 transceivers are frequently considered for cost or supply reasons. However, a 100G optical module that meets IEEE and MSA specifications will not necessarily operate in a Fortinet port. The host must recognize the module, support its application profile, apply the correct Forward Error Correction (FEC) mode, and handle lane mapping and breakout configuration correctly.
Fortinet publishes model-specific compatibility documentation for its transceivers, and the supported 100G QSFP28 combinations vary across FortiSwitch and FortiGate platforms. For network engineers and integrators, qualifying a 100G optic requires checking the exact host model, port capability, module part number, FortiSwitchOS or FortiOS release, and the physical-layer interface type—not just the nominal data rate.
1. Fortinet 100G QSFP28 Compatibility: What Needs to Be Checked?
Fortinet platforms with QSFP28 slots do not support every 100G transceiver profile. Some ports support 100G only, while others support 40G or breakout modes. The supported module list is host-specific and can change between hardware generations and software releases.
Before selecting a 100G QSFP28 module for a Fortinet platform, record the following:
Host model: Complete FortiSwitch or FortiGate model number, including hardware revision.
Port identifier: The exact QSFP28 interface intended for the link.
Port capability: Whether the port supports 100G, 40G, or breakout modes (4×25G, 4×10G, 2×50G).
Software release: FortiSwitchOS version or FortiOS version, plus FortiLink management status if applicable.
Module part number: Fortinet part number or third-party equivalent, including any suffix.
Physical-layer type: 100GBASE-SR4, LR4, DR, CWDM4, FR, BiDi, or ZR4.
FEC requirement: Whether the host port expects FEC to be disabled, set to detect-by-module, or configured for a specific mode.
Remote endpoint: The transceiver type, lane mapping, and FEC configuration at the far end.
Compatibility is host- and interface-specific: A 100G QSFP28 module listed for one FortiSwitch model should not be assumed to work in every Fortinet QSFP28 port. Fortinet’s documentation identifies supported module combinations against individual platforms, and some modules are restricted to specific line cards or port groups.
2. Common 100G QSFP28 Transceiver Types for Fortinet Networks
100G QSFP28 modules use several physical-layer architectures. The correct choice depends on fiber type, reach, connector arrangement, lane count, and FEC behavior.
| Transceiver Type | Typical Wavelength / Lane Structure | Fiber or Cable | Typical Application |
|---|---|---|---|
| 100GBASE-SR4 | 850nm, 4 parallel lanes | Multimode fiber (MPO-12) | Short-reach intra-rack and leaf-spine links up to 70m (OM3) or 100m (OM4) |
| 100GBASE-LR4 | 1310nm LAN-WDM, 4 lanes | Single-mode fiber (duplex LC) | 10km campus and data center interconnect |
| 100GBASE-CWDM4 | 1270–1330nm CWDM, 4 lanes | Single-mode fiber (duplex LC) | 2km single-mode links with lower-cost optics |
| 100GBASE-DR | 1310nm, single lambda, PAM4 | Single-mode fiber (duplex LC) | 500m single-mode links; FEC handled inside the module |
| 100GBASE-FR | 1310nm, single lambda | Single-mode fiber (duplex LC) | 2km single-mode links |
| 100G BiDi QSFP28 | Complementary wavelength pairs | Single-mode or multimode simplex fiber | Bidirectional 100G over one fiber strand |
| 100G ZR4 / Coherent ZR | Coherent or extended-reach DWDM | Single-mode fiber | 80km or longer amplified/unamplified links |
These are physical-layer categories, not interchangeable profiles. A 100GBASE-DR module and a 100GBASE-SR4 module both deliver 100G, but they use different lane structures, FEC models, and fiber interfaces. Matching the nominal data rate alone is insufficient for qualification.
2.1 100GBASE-SR4: 850nm Multimode QSFP28
100GBASE-SR4 is the standard short-reach 100G interface for multimode fiber. It uses four parallel 25G lanes over an MPO-12 connector and is designed for OM3/OM4 fiber in data center leaf-spine deployments.
During testing, verify that the FortiSwitch or FortiGate port supports the SR4 application and that the MPO polarity and lane mapping are correct. SR4 links typically do not require host FEC, but the remote end and the host configuration should be checked against the Fortinet documentation for the specific platform.
2.2 100GBASE-LR4 and CWDM4: Single-Mode 4-Lane QSFP28
100GBASE-LR4 uses four LAN-WDM wavelengths around 1310nm over duplex single-mode fiber for reaches up to 10km. 100GBASE-CWDM4 uses a wider CWDM grid (approximately 1270–1330nm) over duplex single-mode fiber for reaches up to 2km.
Both interfaces use four host electrical lanes and depend on host FEC settings to maintain error performance. The Fortinet port must be configured for the correct mediatype and FEC mode; otherwise, the link may remain down or accumulate errors even when the optical path is clean.
2.3 100GBASE-DR: Single-Lambda 500m QSFP28
100GBASE-DR uses 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. A key operational characteristic is that the module performs FEC internally on the line side and does not require host FEC. In FortiOS, the mediatype dr setting forces forward-error-correction disable by default.
Enabling host FEC on a port operating with a DR module can bring the link down. During qualification, confirm that the host mediatype is set to dr and that FEC remains disabled unless the Fortinet documentation for the specific platform states otherwise.
2.4 100G BiDi and Extended-Reach QSFP28
100G BiDi QSFP28 modules transmit and receive on different wavelength pairs over one fiber strand, using complementary modules at each end. Extended-reach options include 100G ZR4 and coherent ZR modules for 80km and longer spans, with performance dependent on optical budget, dispersion, and amplifier design where applicable.
For BiDi links, verify the wavelength pairing at both endpoints. For ZR and coherent links, verify the received optical power, OSNR, and FEC statistics against the module specification rather than relying only on link-up status.
3. Check the Official Fortinet Transceiver Compatibility Matrix
Fortinet’s transceiver documentation lists supported QSFP28 modules against individual FortiGate and FortiSwitch platforms. The matrix is the primary reference for determining whether a specific module part number is recognized and supported on a given host and software release.
Representative Fortinet 100G QSFP28 families include:
| Fortinet Transceiver Family | Physical-Layer Type | Compatibility Check |
|---|---|---|
| FN-TRAN-QSFP28-SR4 | 100GBASE-SR4, MMF, MPO-12 | Confirm the host model, port, and SR4 application support. |
| FN-TRAN-QSFP28-LR4 / FG-TRAN-QSFP28-LR4 | 100GBASE-LR4, SMF, duplex LC, 10km | Verify the listed part number and host mediatype/FEC requirements. |
| FN-TRAN-QSFP28-DR | 100GBASE-DR, SMF, duplex LC, 500m | Confirm dr mediatype support and FEC disabled. |
| FN-TRAN-QSFP28-CWDM4 | 100GBASE-CWDM4, SMF, duplex LC, 2km | Check the host port and CWDM4 application support. |
| FN-100G-ZR4 / FG-TRAN-QSFP28-ZR4 | 100G extended-reach, SMF, 80km | Verify the host model listing and optical link budget. |
These are examples of families that appear in Fortinet compatibility documentation. The supported host list for each family is model-specific. For example, Fortinet documents FN-TRAN-QSFP28-DR and FN-100G-ZR4 for 100G QSFP28 ports on FortiSwitch 1024E, 1048G, 2048F, and 3032G, among other platforms.
4. Port Configuration: Speed, Breakout, and FEC
Correct port configuration is as important as module selection. FortiSwitch QSFP28 ports can operate in single-port 100G mode, 40G mode, or breakout modes depending on the platform. FEC settings also vary by physical-layer type and module.
4.1 Check the Existing Port Configuration
Before changing settings, inspect the physical port configuration and the module status. The exact commands vary between standalone FortiSwitchOS and FortiLink-managed switches.
config switch physical-port edit port49 show end
Replace port49 with the actual QSFP28 interface name. Review the reported speed, status, and phy-mode.
4.2 Configure Breakout Mode When Required
Some FortiSwitch models support splitting a 100G QSFP28 port into multiple lower-speed subports. For example, the FS-3032E can split QSFP28 ports into 4×25G in 100G mode or 4×10G in 40G mode.
config switch phy-mode set port49-phy-mode 4x25G end
On certain platforms, the auto-module speed setting allows the switch to select the subport speed based on the inserted module. However, breakout capability is platform-specific and should be confirmed against the FortiSwitch model documentation before configuration.
4.3 FEC Configuration for 100G Modules
FEC behavior is one of the most common causes of 100G link failures on Fortinet platforms. Different physical-layer types have different FEC requirements:
100GBASE-DR: FEC is handled inside the module; host FEC must remain disabled. Set
mediatype dron supported FortiOS releases.Certain BiDi or QSFP 100G modules: The port may remain down if the FEC state does not match the module requirement. Fortinet troubleshooting guidance recommends setting
fec-state detect-by-moduleon standalone FortiSwitches for modules such as AFBR-89BDDZ-FN1.FortiLink-managed switches: FEC may need to be configured from the FortiGate switch-controller workflow, and behavior differs by FortiOS release.
config switch physical-port edit port49 set fec-state detect-by-module end
Do not apply FEC settings uniformly across all 100G modules. The correct setting depends on the physical-layer type, the module’s internal architecture, and the Fortinet platform documentation.
4.4 Standalone and FortiLink-Managed Configuration
A FortiSwitch can operate in standalone mode or be managed by a FortiGate through FortiLink. In standalone mode, port speed, breakout, and FEC settings are configured through FortiSwitchOS. In FortiLink mode, administrators should use the FortiGate switch-controller workflow and verify that the settings are applied to the intended managed switch and port.
5. Module Recognition and DDM/DOM Monitoring
After installing the QSFP28 module, confirm that the host recognizes it and can read its identification and diagnostic data. Fortinet platforms provide CLI commands to inspect module details and DDM/DOM status.
5.1 Check Module Identification
get switch modules detail port49
Review the output for:
Transceiver type and connector information.
Vendor name and part number.
Serial number and manufacturing date.
Supported link length and fiber type.
Any recognition alarms or unsupported-module flags.
For a FortiSwitch managed by FortiGate, module details can also be retrieved from the FortiOS CLI:
diagnose switch-controller switch-info modules detail port49
This command returns module identification, vendor details, and diagnostic information from the managed switch.
5.2 Check DDM/DOM Status
get switch modules status port49
Where the QSFP28 module supports DDM/DOM, the output may include:
| Diagnostic Parameter | Purpose |
|---|---|
| Temperature | Module case or internal temperature. |
| Supply Voltage | Module supply voltage. |
| TX Optical Power (per lane) | Transmitter output power for each lane. |
| RX Optical Power (per lane) | Received optical power for each lane. |
| Laser Bias Current | Transmitter laser operating current. |
| Alarm and Warning Flags | Whether monitored parameters have crossed thresholds. |
Not all QSFP28 modules expose per-lane diagnostics, and passive DAC cables do not provide optical DDM data. If diagnostic output is unavailable, confirm that the module supports DDM/DOM and that the host platform can access the diagnostic registers.
DDM is a monitoring aid, not a calibration replacement: DOM/DDM readings are useful for operational checks, but calibrated optical power meters should be used when verifying transmitter output, receiver sensitivity, or link-budget compliance. Measurement uncertainty and module diagnostic accuracy should be considered when evaluating marginal links.
6. Complete 100G QSFP28 Compatibility Testing Procedure
A 100G qualification test should verify the complete link—host recognition, port configuration, optical performance, FEC behavior, and traffic stability—rather than stopping when the module is detected.
| Test Stage | Test Action | Expected Result |
|---|---|---|
| 1. Hardware Installation | Insert the QSFP28 into the designated 100G port. | Module seats correctly and is securely latched. |
| 2. Module Recognition | Read module identifier, vendor, part number, and serial number. | Module is recognized consistently without unsupported-module alarms. |
| 3. Port Configuration | Verify speed, breakout mode, and FEC settings. | Port configuration matches the module physical-layer type and host requirements. |
| 4. Optical Connection | Connect the correct fiber type, connector, and polarity; confirm the remote module. | Transmit and receive paths are correctly connected. |
| 5. Link Establishment | Check the port operational state and lane status. | Interface comes up without repeated transitions or lane failures. |
| 6. DDM/DOM Monitoring | Read temperature, voltage, per-lane TX/RX power, and alarm flags where supported. | Available readings are within module and host limits. |
| 7. Optical Measurement | Measure TX and RX power with calibrated test equipment. | Optical levels meet the module specification and link budget. |
| 8. FEC and Error Counters | Review pre-FEC and post-FEC error statistics where exposed. | Error performance meets the interface and deployment requirements. |
| 9. Network Traffic | Run bidirectional traffic at the intended load. | Traffic passes without unexpected packet loss or errors. |
| 10. Stability Test | Monitor link status, error counters, temperature, and alarms over time. | No unexplained link flapping, resets, or progressive error accumulation. |
6.1 Optical Power and Link Budget
For 100G optical links, per-lane optical power should be checked at both endpoints. The received signal must remain above the receiver sensitivity threshold and below the overload limit for each lane.
The basic per-lane link-loss calculation is:
Optical Link Loss (dB) = Transmitted Power (dBm) − Received Power (dBm)
For 100GBASE-LR4 and CWDM4 links, the loss should be evaluated against the module’s optical budget, connector and splice losses, fiber attenuation, and an engineering margin. For DR and FR single-lambda links, the internal FEC and PAM4 architecture impose different optical and error-performance requirements, and the module specification should be consulted for the applicable limits.
6.2 FEC and Error Performance
A 100G link can report “up” while still failing to pass traffic reliably if FEC is misconfigured or the optical path is marginal. During qualification, record pre-FEC and post-FEC error counters where the platform exposes them. For DR modules, confirm that host FEC is disabled as required. For LR4, CWDM4, and other 4-lane single-mode interfaces, confirm that the host FEC mode matches the Fortinet documentation for the platform and module.
C-LIGHT’s interoperability testing guidance identifies FEC configuration, lane mapping, and electrical interface compatibility as distinct test areas for 100G modules. A module that passes standalone optical measurements may still fail in a specific host because of management or configuration mismatches.
6.3 Breakout and Lane Mapping Verification
When a 100G QSFP28 port is used in breakout mode (for example, 4×25G or 4×10G), verify the lane assignment for every subport and the remote interface configuration. The host’s logical port configuration, the module’s lane mapping, and the remote breakout must be consistent. A breakout link can fail even when the physical optics are good if the lane mapping does not match the host and remote expectations.
7. Common 100G QSFP28 Compatibility Problems on Fortinet Platforms
When a 100G link fails, start with module recognition and port configuration, then inspect FEC, the fiber path, and the remote endpoint.
| Observed Problem | Possible Cause | Recommended Check |
|---|---|---|
| Module not recognized or reported as unsupported | Module profile not supported on the host/software release; incorrect EEPROM coding | Check the Fortinet compatibility matrix and module identification. |
| Port remains down with DR module | Host FEC enabled when module requires FEC disabled | Set mediatype dr and confirm forward-error-correction disable. |
| Port down with 100G BiDi or QSFP module | FEC state mismatch | Try fec-state detect-by-module on standalone FortiSwitch; check FortiLink FEC settings. |
| Link up but traffic errors increase | Marginal optical power, per-lane issue, FEC mismatch, or connector contamination | Review per-lane DDM, FEC counters, and optical measurements at both ends. |
| Breakout subports do not come up | Incorrect phy-mode, unsupported breakout combination, or lane mapping mismatch | Verify the platform breakout capability and subport configuration. |
| Intermittent link flaps | Marginal optical budget, thermal issue, or unstable FEC/configuration | Monitor temperature, optical power, and error counters over time. |
| No DDM/DOM data | Module lacks DDM support, or host cannot access diagnostic registers | Confirm module DDM capability and host CLI output. |
| 4×10G cannot be configured on a 100G QSFP28 | Platform limitation; 4×10G may require 40G QSFP mode | Check the FortiSwitch model’s supported breakout modes in the documentation. |
Fortinet troubleshooting guidance emphasizes that QSFP 100G link failures are often configuration-related rather than purely optical. FEC state, mediatype, and breakout mode should be verified before assuming a hardware fault.
8. C-LIGHT 100G QSFP28 Transceivers for Fortinet Platforms
C-LIGHT offers 100G QSFP28 optical transceivers for data center and enterprise networks. The portfolio includes SR4, LR4, CWDM4, DR, and extended-reach options, with compatibility testing services for multi-vendor environments.
| C-LIGHT Product Family | Fiber Type | Wavelength / Lane Structure | Published Distance | Connector |
|---|---|---|---|---|
| 100G QSFP28 SR4 | MMF | 850nm, 4 parallel lanes | 100m (OM4) | MPO-12 |
| 100G QSFP28 LR4 | SMF | 1310nm LAN-WDM, 4 lanes | 10km | Duplex LC |
| 100G QSFP28 CWDM4 | SMF | 1270–1330nm CWDM, 4 lanes | 2km | Duplex LC |
| 100G QSFP28 DR | SMF | 1310nm, single lambda, PAM4 | 500m | Duplex LC |
| 100G QSFP28 ZR4 / extended reach | SMF | Coherent or DWDM | 80km and longer options | Duplex LC |
Product information: C-LIGHT 100G/40G Multi-Rate QSFP Optical Transceivers | C-LIGHT Optical Transceiver Portfolio
C-LIGHT also provides 100G QSFP28 modules in OTU4 and multi-rate configurations for carrier and data center applications. The published product families include SR4, LR4, ER4, ZR4, and XZR4 variants with different reach and application profiles.
8.1 Compatibility Testing for Fortinet Environments
C-LIGHT performs multi-vendor interoperability testing for optical transceivers, covering module recognition, electrical interface compatibility, optical performance, FEC configuration, lane mapping, and sustained traffic performance. Testing can be aligned with a specific FortiSwitch or FortiGate model, port, software release, and physical-layer type.
For 100G deployments, the relevant test areas include host recognition, per-lane optical power, FEC and error counters, breakout configuration where applicable, and thermal behavior under sustained operation.
Related service: C-LIGHT Optical Transceiver Compatibility Testing
8.2 Information Required for a Fortinet 100G QSFP28 Compatibility Test
Providing accurate equipment details helps C-LIGHT select the correct module profile and prepare a relevant test configuration:
Fortinet host model: Complete FortiSwitch or FortiGate model and hardware revision.
Software release: FortiSwitchOS or FortiOS version, and FortiLink status if applicable.
Port identifier: The exact QSFP28 interface and whether breakout mode is required.
Transceiver specification: Physical-layer type (SR4, LR4, DR, CWDM4, FR, BiDi, ZR4), reach, and part number.
Fiber infrastructure: MMF or SMF, connector type, lane count, and link distance.
Remote endpoint: Connected device model and transceiver specification.
FEC expectation: Whether the host requires FEC disabled, detect-by-module, or a specific mode.
Testing scope: Link establishment, traffic testing, DDM/DOM verification, FEC statistics, or extended stability testing.
These details allow the compatibility evaluation to focus on the actual host and link environment rather than relying only on a generic 100G QSFP28 specification.
9. Conclusion
Deploying 100G QSFP28 transceivers on Fortinet platforms requires more than selecting a module with the correct data rate and reach. The exact FortiSwitch or FortiGate model, supported module part number, port breakout mode, FEC configuration, software release, and remote endpoint all affect whether the link will operate correctly.
A complete qualification process should verify module recognition, port speed and breakout settings, FEC behavior, DDM/DOM data where supported, per-lane optical power, error counters, traffic performance, and sustained stability. Checking Fortinet’s compatibility documentation before installation is particularly important because supported 100G combinations differ across platforms and hardware generations.
C-LIGHT provides 100G QSFP28 optical modules in SR4, LR4, CWDM4, DR, and extended-reach configurations, along with compatibility testing for Fortinet environments. For deployments involving a specific FortiSwitch or FortiGate combination, testing against the actual hardware and software configuration helps reduce installation issues and improve 100G link reliability. Contact C-LIGHT to discuss your 100G QSFP28 requirements and compatibility testing needs.
TEL:+86 132 6656 7067




















































>
>
>
>
>
>
>
>