Interoperability of 400ZR coherent modules: how it works in practice

Where did the interoperability problem come from?

Earlier generations of coherent modules, operating at 100G and 200G speeds in CFP and CFP2 form factors, were based on MSA standard add-ons. While they defined physical interfaces, detailed implementations were left to individual manufacturers. As a result, the module's memory architecture, addressing methods, and commands exchanged between the module and the host were not standardized.

‍
The practical consequence was simple. In many cases, it was impossible to establish a connection between coherent modules from different manufacturers, and often, due to hardware constraints, it was not even possible to use a module outside of the specific network equipment vendor's portfolio. An operator would buy a router from one company and be locked into that same company's modules, at their prices and according to their roadmap.

What the OIF 400ZR standard changed

The 400ZR standard, developed by the Optical Internetworking Forum (OIF), was the first real attempt to standardize coherent pluggable modules at a level that enables genuine interoperability between manufacturers.

OIF 400ZR defines one specific transmission mode: 400G DP-16QAM, C-FEC error correction, and a range of up to 120 km. One mode, no options, no variants, and no room for creative interpretation by the manufacturer. This is a deliberate limitation, because the more narrowly a standard is defined, the easier it is to achieve interoperability.

Just as important as the optical specification itself was the standardization of module management. The emergence of the QSFP-DD standard and the Common Management Interface Specification (CMIS), which defines communication between the network device and the optical module, brought significant progress in module versatility. CMIS specifies how a host queries a module for its status, how it configures the wavelength, and how it reads telemetry. Without a standardized CMIS, management-level interoperability would be impossible even with identical optics.

What 400ZR interoperability means in practice

400ZR interoperability is confirmed and real, but it has a precisely defined scope. It is worth knowing exactly what it covers and what it does not.

A 400ZR module from manufacturer A and a 400ZR module from manufacturer B should establish a 400G DP-16QAM link over a distance of up to 120 km, using the same DWDM channel grid and the same FEC parameters. This is the core of the standard and exactly what the OIF organization certifies. Interoperability also covers basic management via CMIS, such as reading module status, configuring wavelength, and monitoring basic optical parameters like transmit and receive power. This is sufficient to bring up a link and verify that it is working.

However, it is important to know that 400ZR interoperability does not guarantee identical behavior for all advanced parameters and functions. Manufacturers may implement additional features through their own CMIS extensions. Full telemetry, advanced FEC parameters, and support for diagnostic modes are areas where the experience depends on the specific combination of the module manufacturer and the router manufacturer.

OpenZR+, interoperability with greater capabilities

The OpenZR+ MSA standard goes a step further. It maintains compatibility with 400ZR as one of the required modes but adds the ability to operate in multiple transmission modes: speeds from 100G to 400G, QPSK, 8QAM, and 16QAM modulations, and various FEC algorithms. Ranges can reach 600 km and beyond, depending on link parameters.

Interoperability in OpenZR+ adaptive modes is more complex than in 400ZR. The standard defines the required 400G DP-16QAM base mode, identical to 400ZR, as the one that must be interoperable between all manufacturers. Adaptive modes—such as QPSK, 8QAM, and PCS configurations—require verification with specific module pairs before production deployment.

A practical tip for operators in Poland and CEE is this: if you are planning a multivendor environment with OpenZR+ modules from different manufacturers, start with an interoperability test in 400G DP-16QAM mode, as this will always work. For adaptive modes and longer ranges, test the specific pair of modules on the specific link before deploying them into production.

What interoperability looks like from the router's perspective

A module can be 100% compliant with OIF 400ZR and OpenZR+ and still fail to work in a specific router. This is not a paradox, but a result of the complexity of integration on the active hardware side.

The router must support CMIS for coherent modules in the firmware version actually installed, not the one listed on the roadmap. It must correctly execute the CMIS initialization sequence; if it interrupts it or implements it inconsistently with the specification, the module may enter an error state requiring a physical re-insertion. It must also allow configuration of the DWDM channel and modulation mode via the appropriate CMIS registers.

Each major router manufacturer implements CMIS support slightly differently. In older versions of IOS XR, Cisco could use module whitelists, where the router would check the PID and refuse to work with an unknown product. Nokia SR OS, from version 22.x onwards, has robust CMIS support with well-documented telemetry. Huawei VRP can be inconsistent across versions and platforms, so verification for the specific device model is particularly important here. This is precisely why we configure GBC Photonics modules via the SRD environment before installation, setting the module identification to match the specific host. This eliminates the classic problem where the router does not see the module, which is usually a matter of identification rather than actual optical incompatibility.

Output power vs. system interoperability: the hidden trap in the specifications

‍
The OIF 400ZR standard defines the optical parameters of a module, but it does not specify how the module will behave within an existing DWDM system. This is an area where differences between modules from various manufacturers have direct consequences for the project.

Most 400ZR and OpenZR+ modules on the market transmit a signal at -10 dBm, while existing DWDM systems are calibrated for a signal between -3 and 0 dBm at the multiplexer input. The result is that a fully OIF 400ZR-compliant module cannot be plugged directly into an existing DWDM system without an additional EDFA amplifier. Manufacturers try to bypass this problem by adding a miniature EDFA inside the module, but then the module does transmit at 0 dBm, albeit at the cost of higher power consumption and worse transmitter OSNR, because the amplifier adds noise to the signal before it even leaves the module.

GBC Photonics modules are designed with a native 0 dBm output power, without an internal EDFA, and the transmitter OSNR is 43 dB. This is not just a marketing detail, but the difference between a module that integrates directly into an existing system and one that requires infrastructure modifications or degrades link quality.

What to check before buying modules for a multivendor environment

There are three questions whose answers determine the success of an implementation in a multivendor environment.

400ZR interoperability is real and proven, but its scope is precise: one transmission mode, standard CMIS management, and a range of up to 120 km. Anything beyond this scope requires verification for the specific combination of modules, routers, and optical line systems.

‍