
Where a network combines several equipment vendors, select this assembly by the NVIDIA/Mellanox MFS1S90-H003E requirement rather than by its connector shape alone. This page covers the 30m (98ft) AOC version at 200G, including its 2x QSFP56 to 2x QSFP56 configuration, related brand identities and factory operating checks.
OEM Part Number: MFS1S90-H003EHT Part Number: MFS1S90-H003E
| HT Part Number | MFS1S90-H003E |
|---|---|
| NVIDIA/Mellanox InfiniBand Compatible | MFS1S90-H030E |
| Manufacturer | HT |
| Form Factor | 2x QSFP56 to 2x QSFP56 |
| Max Data Rate | 200Gbps |
| Cable Length | 30m (98ft) |
| Cable Type | OM3 |
| Wavelength | 850nm |
| Minimum Bend Radius | 30mm |
| Transmitter Type | VCSEL |
| Receiver Type | PIN |
| Power Consumption | ≤4.35W |
| Jacket Material | OFNP |
| CDR (Clock and Data Recovery) | TX & RX Built-in CDR |
| Modulation Format | PAM4 |
| Commercial Temperature Range | 0 to 70°C (32 to 158°F) |
| Protocols | QSFP56 MSA, SFF-8665, SFF-8636, InfiniBand HDR |
The listed modulation format is PAM4. Both host interfaces must be configured for the same aggregate rate and lane arrangement. A connector that fits mechanically does not by itself guarantee that the remote port supports this encoding or breakout mode.
A mixed-vendor link should be documented at both ends, not treated as one generic connection. Confirm which OEM identity each host expects and whether the two ends use the same compatibility requirement. The related brand links below help locate equivalent-length assemblies, while the physical form factor and lane arrangement must still agree across the complete path. For this assembly, the minimum bend radius is 30mm; the stated power consumption is ≤4.35W; the jacket material is OFNP.
The rated power consumption is ≤4.35W. Include this load in the host-port power and thermal budget, especially in densely populated switches. Maintain front-panel clearance and do not bundle the cable so tightly that it obstructs airflow around the connectors.
This assembly uses OFNP jacket, minimum bend radius 30mm. These mechanical characteristics affect how the cable should be dressed behind the equipment. Avoid sharp edges, excessive ties and repeated tight bends close to the connector boots.
The intended application is determined by the host interface and protocol support. Listed interface and protocol references include QSFP56 MSA, SFF-8665, SFF-8636, InfiniBand HDR. Confirm that the host firmware and port configuration support the same operating mode.
The 2x QSFP56 to 2x QSFP56 configuration divides the high-speed interface into multiple lower-speed connections. Verify the upstream lane assignment, downstream port speeds and breakout setting on the host before connecting the assembly. Each branch must attach to the correct remote interface.
The optical engines and fiber are permanently integrated into this AOC. There are no detachable optical modules to clean or exchange. Handle the complete assembly by its connector housings and cable, and keep both ends matched to the same interface specification.
With 30m (98ft) available, the installer has more routing freedom but also more cable to control. Determine where any remaining service loop will be stored, preserve the stated bend radius and keep the loop away from sharp edges and hot exhaust. The integrated optical cable and both optical engines should remain accessible for inspection and removal. The next shorter verified assembly is MFS1S90-H003E at 20m (66ft), which is the better comparison when the managed route leaves substantial unused cable.
MFS1S90-H003E is the longest of 6 verified length options in this family. Compared with MFS1S90-H003E at 20m (66ft), it provides 10m of additional reach for a longer vertical drop, a wider rack or an adjacent-cabinet route. Confirm that the complete path requires this length, because unused slack still needs supported, bend-safe storage.
Testing addresses the brand-specific identification as well as the operating link and available diagnostics. The same physical cable family can require a different host identity for another equipment vendor, so the intended platform should be supplied when a deployment combines multiple brands or unusual hardware revisions. Both connectors are examined before the operating test, which includes receive activity and diagnostic indications.
For mixed-vendor projects, identify the equipment at both ends along with the OEM reference, length and quantity. Order each compatibility version under its own part number. If spare assemblies are required, list them separately so labels and test records remain unambiguous. This page’s fixed configuration is 30m (98ft); another length must be quoted under its corresponding part number.
Both ends are inspected and the complete assembly is powered up for a functional check before packing. Connectors are protected individually and the cable is secured without tight bends. Optional labels can distinguish host brand, OEM reference and length for easier spares management. Neutral packaging and customer-specific packing documentation are available on request.
No. It is an HT-manufactured compatible alternative for equipment that specifies NVIDIA/Mellanox MFS1S90-H003E.
Protect both connector ends, keep the cable in a loose bend-safe coil and retain its part-number label so the length and compatibility identity remain traceable.
Only where both hosts explicitly support the complete interface and compatibility arrangement. Document each end and select the appropriate brand-specific product when required.
No. MFS1S90-H003E refers here to 30m (98ft). Every other verified length has a separate part number and page in the length list.
Available stock is generally dispatched within one to three working days after order confirmation, with production lead times advised for larger quantities. Worldwide courier services are available, with air or sea freight for consolidated shipments; freight-collect delivery and coordination with a customer’s logistics provider can be arranged.