
Use this 100m (328ft) AOC cable for hosts expecting NVIDIA/Mellanox MFA1A00-E100 and a 100G direct-attached interface. The assembly uses QSFP28 to QSFP28; lane, protocol and breakout considerations are documented alongside the verified table. Every alternative length remains a separate order code with its own technical page.
OEM Part Number: MFA1A00-E100HT Part Number: MFA1A00-E100
| HT Part Number | MFA1A00-E100 |
|---|---|
| NVIDIA/Mellanox Infiniband Compatible | MFA1A00-E100 |
| Manufacturer | HT |
| Form Factor | QSFP28 to QSFP28 |
| Max Data Rate | 100Gbps |
| Minimum Bend Radius | 30mm |
| Cable Length | 100m (328ft) |
| Jacket Material | OFNP |
| Cable Type | Optical Cable |
| Receiver Type | PIN |
| Transmitter Type | VCSEL |
| Wavelength | 850nm |
| Power Consumption | <2.2W |
| MTBF | ≈50 Million Hours |
| Power supply | 3.3V |
| Modulation Format | NRZ |
| DDM/DOM | Supported |
| Commercial Temperature Range | 0 to 70°C (32 to 158°F) |
| Protocols | IEEE 802.3 bm, SFF-8665 |
| CDR (Clock and Data Recovery) | TX & RX Built-in CDR |
| Modulation Format | 4x 25G-NRZ to 4x 25G-NRZ |
| Application | InfiniBand EDR |
The listed modulation format is NRZ. 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.
The intended application is InfiniBand EDR. Listed interface and protocol references include IEEE 802.3 bm, SFF-8665. Confirm that the host firmware and port configuration support the same operating mode.
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.
Measure twice before deploying this 100m (328ft) cable: once along the planned route and again after accounting for service access. The objective is adequate reach without a concealed surplus. Support the integrated optical cable and both optical engines, preserve front-panel clearance and check that nearby power cords or sharp hardware cannot damage the jacket. The next shorter verified assembly is MFA1A00-E050 at 50m (164ft), which is the better comparison when the managed route leaves substantial unused cable.
MFA1A00-E100 is the longest of 11 verified length options in this family. Compared with MFA1A00-E050 at 50m (164ft), it provides 50m 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.
Check three layers before deployment: the host must accept the cable identification, the port must support the stated aggregate rate, and the lane configuration must match the attached interfaces. On breakout hardware, also confirm channelization and the mapping of every branch. These checks are particularly important when similar-looking ports operate at different speeds or under different firmware settings. For this assembly, the minimum bend radius is 30mm; the stated power consumption is <2.2W; the jacket material is OFNP.
The rated power consumption is <2.2W. 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.
Specify the OEM part number and fixed length, then provide the intended host configuration if the link uses channelized or breakout ports. Separate part numbers should be used for separate lengths. This gives the compatibility review enough information to check both the physical assembly and the intended operating mode. This page’s fixed configuration is 100m (328ft); another length must be quoted under its corresponding part number.
The verification process combines digital identification with a live link test and diagnostic observation. Host model, hardware revision and software release are useful inputs because qualification behavior can change between platform generations; those details allow platform-specific requirements to be reviewed before the cable is packed. The check includes receive activity and diagnostic indications, followed by a final inspection of both ends.
Standard configurations normally ship within one to three working days, while production quantities are confirmed with the order. 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.
Functional inspection covers identification, link establishment and the condition of both connector assemblies. The cable is then protected against dust and connector damage and packed without sharp bends. Labels can include the customer reference and host-platform note when requested for a controlled deployment. Volume orders can include customer references on the labels and carton list.
No. It is an HT-manufactured compatible alternative for equipment that specifies NVIDIA/Mellanox MFA1A00-E100.
No. Use a supported, bend-safe service loop and observe the listed minimum bend radius. Do not crease the cable or tighten ties around the connector boots.
Not necessarily. Both hosts must support the stated rate, identification, lane mapping and any required breakout configuration; mechanical compatibility alone is insufficient.
Provide the equipment manufacturer, model, port type, hardware revision and software release, together with the OEM reference, required length and quantity.