Third-Party 800G Transceivers for NVIDIA Mellanox Networks: What to Check Before You Buy

Short answer

Yes — third-party 800G optics can be used in many NVIDIA Mellanox environments, but only after you match the host and confirm coding. Compatibility is not automatic: it depends on the platform family (InfiniBand vs Ethernet), the physical cage (OSFP vs QSFP-DD800), software / firmware, module type, link distance, and fiber plant.

YYGL Optical (毅远光联), also known as Yiyuan Guanglian or Yiyuan Optical Link, supplies third-party 800G OSFP and QSFP-DD modules for AI and data-center networks. We are an independent optics supplier; we are not NVIDIA, Mellanox, or any switch brand, and we do not claim affiliation with them.

Compatibility depends on the host platform. Please share your switch model, software version, module type, link distance and fiber type so we can check coding and compatibility before you order.

Prepared by the YYGL Optical Technical Team.

InfiniBand vs Ethernet: why the platform family matters

NVIDIA Mellanox networking products span more than one fabric family. Buyers often search for “compatible 800G for NVIDIA Mellanox” as if every host behaved the same. In practice, InfiniBand-oriented hosts and Ethernet-oriented hosts can differ in how they treat pluggable optics:

• Port and fabric expectations. The cage type, lane mapping, and management interface must match the module you insert. An OSFP 800G optic will not fit a QSFP-DD800 cage, and the reverse is also true.
• Software and firmware. Host software releases can change which EEPROM / CMIS fields are checked, which module identifiers are accepted, and which DOM fields are exposed.
• Coding. Third-party modules are typically coded for a named host profile. The same physical SR8-class optic may need different coding for different brands — including different NVIDIA Mellanox platforms.

This article does not claim support for any specific chassis, NIC, or software build. Treat “NVIDIA Mellanox” as the compatibility target you name in the RFQ, then let us check coding against the five items below.

For a supplier-oriented walkthrough aimed at Cisco / Arista OSFP SR8 RFQs (same five-item check), see our live page: 800G OSFP SR8 Compatible Transceiver Supplier.

800G form factors and reach types you will meet

Start from the physical port, then the reach and fiber. Background: What Is an 800G Transceiver?.

Form factor

Do not assume a 400G QSFP-DD cage can run an 800G module. Confirm the port type in your platform documentation first.

Reach class (after form factor is fixed)

Browse related AI / hyperscale SKUs in AI & hyperscale optical transceivers and the 800G OSFP collection.

What to check before you buy third-party 800G

Use this checklist whether the host is NVIDIA Mellanox, or one of the other brands we discuss for coding checks on this site: Cisco, Arista, Juniper, and Dell.

1. Coding / EEPROM identity

Hosts often read vendor and part-identity fields from the module EEPROM. Third-party optics are coded for a stated host profile. Send the exact switch or NIC model so coding can be checked before shipment. We do not publish a universal “works in every NVIDIA Mellanox 800G port” claim.

2. CMIS revision and management

Modern 800G modules use CMIS (not the older SFF-8636-only model). Our listed OSFP SR8 / VR8 and QSFP-DD SR8 pages name CMIS Rev 5.2 with DOM/DDM. Confirm that your host software expects a CMIS revision compatible with the module you order.

3. Host software / firmware version

A module that was accepted on one software build may be rejected or partially managed on another. Always include the software or firmware version as shown on the device in the RFQ.

4. FEC and host port settings

800G PAM4 links rely on host-side FEC and correct port configuration. After the optic is recognized, verify that the port comes up at the intended rate and that both ends agree on breakout vs native 800G (when your SKU and host support a split). We do not publish link-margin or error-rate targets or “guaranteed link margin” figures on this page — validate on a pilot link.

5. Fiber type, connector, and polarity

Match the listing connector to the patch plant:

• OSFP SR8 / VR8 / DR8+ listings above use dual MPO-12/APC
• QSFP-DD SR8 listing uses single MPO-16/APC

Confirm MPO polarity, APC polish, and OM3 vs OM4 (or OS2 for DR8+) across the complete trunk. A coding match will not fix the wrong connector or fiber grade.

6. Far-end optic

Both ends of the link must speak the same optical class (for example SR8-to-SR8 on multimode, or DR8+-class on parallel single-mode). Mixing reach classes or connector families is a common install-day failure even when each module is coded correctly for its own host.

The five items to send us

1. Switch (or NIC) model
2. Software / firmware version
3. Module type you need (for example 800G OSFP SR8)
4. Link distance
5. Fiber type (OM3 / OM4, or single-mode)

Optional but helpful: quantity, finned-top vs flat-top OSFP if applicable, and any OEM part number you are replacing (see next section).

Compatibility depends on the host platform. Please share your switch model, software version, module type, link distance and fiber type so we can check coding and compatibility before you order.

Referencing an OEM part number in your RFQ

Many buyers replace an existing optic and quote the OEM part number they see on the label or in a BOM. That is useful context for an RFQ.

• Send the OEM part number as a reference together with the five items above.
• We confirm what we can supply in writing for your named host.
• We make no equivalence or “same as” claims beyond what is confirmed in that written reply.
• Do not assume that a part number from one platform family applies to another (InfiniBand vs Ethernet, or OSFP vs QSFP-DD800).

If you are still on 400G multimode QSFP-DD and need an enhanced short-reach option while planning an 800G move, see our 400G QSFP-DD SR4+ listing (facts on that page only — confirm reach and far-end optic with us before mixing with standard SR4).

Testing before rollout: pilot links and DOM

Before you scale a third-party 800G SKU across a fabric:

1. Pilot a small number of links on the exact host model and software version you will use in production.
2. Confirm the module is recognized, the port comes up at the intended rate, and DOM fields are readable.
3. Watch temperature, supply voltage, and Tx/Rx optical power over a representative traffic window.
4. Only then expand to the full quantity in the RFQ.

Ask us for whatever test evidence you need for your internal process. This article does not publish pass rates, error-rate figures, or named-platform validation claims.

YYGL Optical 800G options for NVIDIA Mellanox RFQs

Specs below are taken from each product listing. Coding is confirmed per host after you send the five items.

Lead time, MOQ, stock, and sample availability vary by project — ask us when you send the RFQ.

Further reading

• What Is an 800G Transceiver? A Complete Guide for Data Center Networks
• 800G OSFP SR8 Compatible Transceiver Supplier
• OEM vs Third-Party 800G OSFP SR8 Optics for AI Data Centers: How to Compare Suppliers

Request a quote

Tell us the five items above, the quantity you need, and (optional) any OEM part number you are replacing.

• RFQ form: Request a Quote
• Email: yygl@yiyuanguanglian.cn
• Company LinkedIn: Wuhan Yiyuan Guanglian Information Technology Co., Ltd.

Primary starting SKU for many short multimode OSFP RFQs: 800G OSFP SR8 (YY-OSFP-SR8-100M).