At 100GbE, the choice between DR, FR and LR4 optics affects more than the distance a fiber link can cover. These QSFP28 transceivers use different optical channel architectures, modulation formats and link budgets. A data center connection across a short single-mode fiber run may use 100GBASE-DR, an inter-rack or campus data center link may favor 100G-FR1, while 100GBASE-LR4 remains a widely deployed option for 10km single-mode fiber connections.
For Cisco Catalyst, Nexus and other network platforms, successful deployment depends on several conditions working together: QSFP28 port support, transceiver identification, optical interoperability, host-side FEC configuration and stable traffic performance. Even when two modules share a duplex LC connector, they are not necessarily interchangeable.
This article examines the technical differences between 100GBASE-DR, 100G-FR1 and 100GBASE-LR4, then outlines a practical compatibility evaluation framework for Cisco network equipment and third-party QSFP28 transceivers.
1. Understanding 100GBASE-DR, 100G-FR1 and 100GBASE-LR4
The three optical interfaces are designed for different link distances and use different approaches to transmitting 100Gbps Ethernet signals.
| Characteristic | 100GBASE-DR | 100G-FR1 | 100GBASE-LR4 |
|---|---|---|---|
| Optical architecture | Single-lambda | Single-lambda | Four-wavelength LAN-WDM |
| Modulation | PAM4 | PAM4 | NRZ across four optical lanes |
| Optical channels | 1 × 100G | 1 × 100G | 4 × approximately 25G |
| Typical wavelength | 1311nm region | 1311nm region | Four LAN-WDM wavelengths around 1295–1309nm |
| Fiber type | SMF | SMF | SMF |
| Standard reach | 500m | 2km | 10km |
| Connector | Duplex LC | Duplex LC | Duplex LC |
| Common application | Short-reach data center links | Data center and campus interconnects | Longer-reach enterprise and data center links |
The table describes the common Ethernet implementations. Individual product specifications, host requirements and optical budgets must still be checked before deployment.
100GBASE-DR: 500m single-mode connectivity
100GBASE-DR uses one optical wavelength to carry a 100Gbps Ethernet signal over single-mode fiber. PAM4 modulation enables the required data rate on a single optical lane, reducing the number of optical channels compared with traditional four-lane designs.
Its standardized reach is 500m, making it suitable for short single-mode fiber connections inside data centers and between nearby network equipment areas. The duplex LC interface also allows it to use conventional two-fiber single-mode cabling.
100G-FR1: 2km single-lambda transmission
100G-FR1 extends single-lambda PAM4 connectivity to 2km over single-mode fiber. It is designed for applications where the 500m reach of DR is insufficient but a 10km LR-class link is unnecessary.
FR1 and DR share a single-lambda architecture, but their reach specifications and optical operating requirements differ. A DR module should not be treated as a substitute for FR1 simply because both use a 1310nm-region wavelength and duplex LC connector.
100GBASE-LR4: Four-channel LAN-WDM transmission
100GBASE-LR4 uses four optical wavelengths multiplexed onto a single fiber pair. Each optical lane carries approximately 25Gbps, producing an aggregate 100Gbps Ethernet connection over single-mode fiber.
The four LAN-WDM channels operate around 1295nm, 1300nm, 1304nm and 1309nm. The interface supports a reach of up to 10km and is commonly used for building-to-building links, campus networks and data center interconnections.
Although LR4 and single-lambda DR or FR1 modules may all use duplex LC connectors, their optical channel structures are different. They cannot be directly substituted without matching the optical interface at both ends.
2. Optical Standards and Technical Differences
Standards compliance is a central part of 100G transceiver interoperability. A QSFP28 module can fit into a port while still using an optical interface that the remote endpoint does not support.
| Technical Item | DR | FR1 | LR4 |
|---|---|---|---|
| Ethernet specification | IEEE 100GBASE-DR | 100G-FR1 specification under 100G Lambda MSA / applicable IEEE implementation | IEEE 100GBASE-LR4 |
| Optical signaling | PAM4 | PAM4 | NRZ |
| Electrical host interface | CAUI-4 | CAUI-4 | CAUI-4 |
| Fiber connection | Duplex SMF | Duplex SMF | Duplex SMF |
| Optical channel count | One | One | Four |
| FEC evaluation | Verify applicable KP4/RS-FEC requirements and implementation | Verify applicable KP4/RS-FEC requirements and implementation | Verify host and module requirements for the specific LR4 implementation |
DR and FR1 use PAM4 signaling, which carries more information per symbol than NRZ. This higher signaling efficiency requires careful consideration of signal quality and forward error correction. LR4 uses four optical lanes with a different modulation architecture.
3. Cisco Platforms and QSFP28 Port Compatibility
Cisco supports different 100G transceiver combinations across its Catalyst, Nexus and other product families. The availability of a QSFP28 cage does not mean that every DR, FR1 or LR4 module is supported on that device.
| Cisco Platform | Typical Role | Compatibility Checks |
|---|---|---|
| Catalyst 9300X | Enterprise access and aggregation | Exact switch model, uplink configuration, IOS XE release and supported 100G optics |
| Catalyst 9500 | Campus core and distribution | Chassis SKU, interface type, software release and transceiver support |
| Catalyst 9600 | Modular campus core | Supervisor, line card, port configuration and supported optical modules |
| Nexus 9300 | Data center leaf and spine | Exact hardware model, NX-OS release, port mode and optical product ID |
| Nexus 9500 | Data center modular switching | Line card, port speed, module support and software requirements |
| Nexus 7000 | Data center core and aggregation | Supervisor, line card and platform-specific transceiver list |
Compatibility varies within each product family. For example, Cisco's compatibility matrix lists 100G-FR support on certain Catalyst 9300X configurations with IOS XE 17.11.1, while LR4 and other optical types have different platform and software requirements. These entries should not be generalized to every Catalyst or Nexus switch.
Use the Cisco Optics-to-Device Compatibility Matrix to identify supported Cisco transceiver and device combinations. Search by the exact network device product ID and optical module product ID, then check the minimum software release and any notes.
Cisco documentation identifies products such as QSFP-100G-DR-S, QSFP-100G-FR-S and QSFP-100G-LR4-S as distinct optical products. Their individual compatibility entries should be checked rather than relying on the QSFP28 form factor alone.
4. Why DR, FR1 and LR4 Are Not Interchangeable
Several physical characteristics appear similar across these products, but their optical signals and operating specifications are not the same.
| Potential Confusion | Technical Difference | Deployment Impact |
|---|---|---|
| Same QSFP28 form factor | Different optical standards and channel architectures | Host support must be checked for the exact product type. |
| Same duplex LC connector | Different wavelength and modulation requirements | Connector fit does not establish optical interoperability. |
| Same 1310nm region | DR and FR1 have different reach specifications; LR4 uses four LAN-WDM channels | Wavelength labels alone cannot determine compatibility. |
| Same 100GbE data rate | Different optical lane arrangements and signaling | Both endpoints must support the same Ethernet optical interface. |
| Same single-mode fiber type | Different optical power budgets and reach limits | Link attenuation and receiver operating range must be verified. |
A DR-to-FR1 connection is not automatically supported just because both modules use single-lambda PAM4. Likewise, an LR4 module cannot be paired with a DR or FR1 module simply because the fiber patch cord and connectors are physically compatible.
For a standard point-to-point Ethernet link, use matching optical interface types at both ends unless the manufacturer explicitly documents a supported interoperability combination.
5. Cisco 100G QSFP28 Compatibility Testing Procedure
A repeatable test should separate host recognition, optical link establishment and traffic performance. These are different stages, and each provides different evidence about compatibility.
Step 1: Record the device and transceiver information
Before installing a module, record:
Cisco switch model and product ID.
Hardware revision and installed line card, where applicable.
IOS XE or NX-OS software version.
QSFP28 interface number and configured port speed.
Transceiver manufacturer, part number and serial number.
Optical standard: DR, FR1 or LR4.
Fiber type, connector type and intended link distance.
Remote endpoint model and optical module information.
For third-party module evaluation, preserve the exact module part number and coding information. Results from one product revision should not automatically be applied to a different revision.
Step 2: Verify module recognition
Use the commands supported by the specific Cisco platform to inspect the installed transceiver and interface state.
show version show inventory show interfaces status show logging
On supported IOS XE platforms, an interface-specific transceiver command may be available in this form:
show interfaces HundredGigE1/0/1 transceiver detail
On Nexus platforms, the interface name and command syntax may differ:
show interface ethernet 1/1 transceiver details
These are platform-dependent examples. Confirm the correct interface naming and command syntax in the documentation for the exact switch and software release.
Record whether the device detects the module, displays its identification information and reports any unsupported-transceiver warning. A recognized module has passed an initial host-identification check, but this alone does not prove that the optical link is fully compatible.
Step 3: Verify port configuration and FEC
Confirm that the QSFP28 interface is configured for the intended 100GbE operation. Check whether the platform supports the selected optical type and whether the required FEC mode is available.
For DR and FR1, pay particular attention to the PAM4 and RS-FEC/KP4 requirements specified by the module and host implementation. For LR4, verify the requirements of the exact module and Cisco interface. Do not apply a single FEC configuration to every 100G optical interface.
Step 4: Establish the optical connection
Connect matching optical interfaces at both ends using suitable single-mode fiber. Inspect the duplex LC connectors and ensure that the fiber path meets the distance and attenuation requirements.
After connecting the link, inspect interface state and system logs. If the port remains down, verify the remote module type, port configuration, fiber polarity, connector condition and FEC settings before treating the transceiver itself as defective.
Step 5: Inspect optical diagnostics
Where Digital Optical Monitoring is supported, record the following information:
| Parameter | Purpose | Evaluation |
|---|---|---|
| Module temperature | Monitors operating temperature | Compare with the module's specified operating range. |
| Supply voltage | Checks electrical supply conditions | Compare with the datasheet limits. |
| Laser bias current | Provides transmitter operating information | Review against module-specific thresholds. |
| Transmit optical power | Measures outgoing optical power | Check that output is within the specified range. |
| Receive optical power | Measures incoming optical power | Check receiver sensitivity and overload limits. |
| Alarm and warning flags | Indicate threshold violations | Investigate the affected parameter and link conditions. |
For LR4, the module internally multiplexes four optical channels. Diagnostic information may expose channel-specific values depending on the module implementation and host support. For single-lambda DR and FR1, the diagnostic presentation may differ. Record the actual fields reported by the tested product rather than assuming all modules expose identical telemetry.
Step 6: Validate traffic performance
Once the physical link is operational, run a controlled traffic test between the endpoints. Record throughput, packet loss, interface errors and link transitions under a defined traffic profile.
Useful checks include:
Basic connectivity between the two endpoints.
Traffic throughput at the intended line rate.
Packet loss under the selected test profile.
CRC and input error counters.
Link stability during sustained traffic.
System logs and transceiver alarms during operation.
A test report should include the traffic profile and test duration. A port that remains up without carrying a representative traffic load has not completed a full operational evaluation.
6. Common Compatibility Problems and Troubleshooting
When a 100G QSFP28 link fails to establish or shows abnormal behavior, the cause may be in the host platform, optical interface, fiber path or port configuration.
| Observed Problem | Possible Cause | Recommended Check |
|---|---|---|
| Transceiver not recognized | Unsupported module coding or platform limitation | Check the exact product ID against Cisco compatibility documentation. |
| Port remains down | Optical mismatch, FEC configuration or fiber issue | Verify both endpoints, interface settings and fiber continuity. |
| DR and FR1 link mismatch | Different reach specifications or host requirements | Use matching optical interfaces and verify the documented interoperability conditions. |
| LR4 link fails | Wavelength mismatch, fiber issue or unsupported module | Verify LR4 channel specifications and both endpoint modules. |
| Low receive power | Excessive attenuation, dirty connector or damaged fiber | Inspect connectors and measure the optical path. |
| High receive power | Receiver overload or unsuitable optical path | Compare receive power with the module's maximum input specification. |
| CRC errors increase | Physical-layer issue, signal quality or configuration problem | Review optical diagnostics, FEC status and interface counters. |
| Intermittent link transitions | Marginal optical conditions, thermal issue or host behavior | Review event logs, temperature and optical readings over time. |
Changing the optical module without checking the link architecture can make troubleshooting more difficult. First confirm the exact standard at both endpoints, then investigate host recognition, configuration, fiber conditions and measured optical power.
7. C-LIGHT 100G QSFP28 DR, FR1 and LR4 Solutions
C-LIGHT's 100G QSFP28 portfolio includes both single-lambda PAM4 products and traditional multi-lane optical transceivers. These product categories support different data center and enterprise network distances.
Single-lambda DR, FR1 and LR1 modules
The C-LIGHT 100G QSFP28 Single Lambda portfolio lists the following products:
| Model | Optical Standard | Fiber | Wavelength | Distance | Connector |
|---|---|---|---|---|---|
| CL100GQSFPDR1 | 100GBASE-DR | SMF | 1310nm region | 500m | Duplex LC |
| CL100GQSFPFR1 | 100G-FR1 | SMF | 1310nm region | 2km | Duplex LC |
| CL100GQSFPLR1 | 100G-LR1 | SMF | 1310nm region | 10km | Duplex LC |
The DR1 datasheet identifies IEEE 802.3cu-2021 100GBASE-DR compliance, a QSFP28 MSA package, CAUI-4 electrical interface, 1311nm typical wavelength, duplex LC connector, 500m single-mode reach and a 0–70°C case operating temperature range.
The LR1 datasheet identifies IEEE 802.3cu-2021 100GBASE-LR compliance, 1311nm typical wavelength, duplex LC connectivity and 10km single-mode reach. These are single-lambda products and should not be confused with four-channel LR4 transceivers.
Traditional 100G QSFP28 LR4 modules
For conventional four-channel 100G LR4 applications, C-LIGHT's 100G QSFP28 optical transceiver portfolio lists the CL100GQSFPLR4 model as a 10km single-mode product using four LAN-WDM channels and a duplex LC interface.
This is the relevant product category for networks designed around the traditional 100GBASE-LR4 optical interface. Before ordering, confirm the detailed datasheet's channel wavelengths, optical power limits, electrical interface and FEC requirements against the target Cisco equipment.
Compatibility evaluation for Cisco equipment
C-LIGHT DR, FR1 and LR4 products can be included in independent Cisco platform evaluation projects. Each test should be tied to the exact module model, Cisco switch product ID, software release, port configuration and remote endpoint.
Testing can cover module recognition, optical link establishment, diagnostic monitoring, FEC behavior and sustained traffic performance. The results should describe the actual tested configuration and should not be represented as Cisco certification or universal support across all Cisco devices.
8. Building a Cisco 100G QSFP28 Test Matrix
For system integrators and network operators working with multiple Cisco switch models, a structured test matrix makes the results easier to reproduce and maintain.
| Test Item | DR | FR1 | LR4 |
|---|---|---|---|
| Host recognition | Record module identification and warnings | Record module identification and warnings | Record module identification and warnings |
| Port support | Verify exact Cisco model and software | Verify exact Cisco model and software | Verify exact Cisco model and software |
| Optical interface | Confirm DR at both ends | Confirm FR1 at both ends | Confirm LR4 at both ends |
| Fiber path | SMF, up to 500m | SMF, up to 2km | SMF, up to 10km |
| FEC behavior | Verify applicable host and module requirements | Verify applicable host and module requirements | Verify implementation-specific requirements |
| DOM monitoring | Record available diagnostic fields | Record available diagnostic fields | Record available diagnostic fields |
| Traffic validation | Throughput, loss and error counters | Throughput, loss and error counters | Throughput, loss and error counters |
| Long-term operation | Link stability and alarms | Link stability and alarms | Link stability and alarms |
Each test record should preserve the following information:
Cisco device model and hardware revision.
IOS XE or NX-OS software version.
Port number and operating configuration.
Optical module model, serial number and vendor identification.
Optical standard and remote-end module type.
Fiber type, length and connector configuration.
FEC configuration and link status.
DOM readings and alarm status where available.
Traffic test profile, duration and measured results.
Classify the final result into three levels:
Host recognition: The Cisco device detects and initializes the module.
Optical interoperability: The two endpoints establish a stable physical link using the intended optical standard.
Operational validation: The link carries the required traffic without unacceptable errors or instability under the recorded test conditions.
9. Conclusion
100GBASE-DR, 100G-FR1 and 100GBASE-LR4 address different 100GbE single-mode fiber requirements. DR provides 500m single-lambda connectivity, FR1 extends the same general architecture to 2km, and LR4 uses four LAN-WDM channels to support 10km links.
For Cisco Catalyst and Nexus deployments, compatibility depends on more than the QSFP28 form factor. The exact switch model, software release, transceiver identification, optical standard, FEC behavior, fiber path and traffic performance all need to be considered.
C-LIGHT provides 100G QSFP28 single-lambda and multi-channel optical solutions for different network applications. A product-specific compatibility evaluation can help identify the appropriate module and document its operation on the intended Cisco platform.
Planning a 100G QSFP28 DR, FR1 or LR4 deployment?
C-LIGHT can assist with optical product selection, technical specifications, compatibility evaluation and customized 100G connectivity requirements.
TEL:+86 132 6656 7067




















































>
>
>
>
>
>
>
>