
Where a network combines several equipment vendors, select this assembly by the NVIDIA/Mellanox MCP7Y10-N01A requirement rather than by its connector shape alone. This page covers the 1.5m (5ft) DAC version at 800G, including its OSFP (IHS/Finned Top) to 2x QSFP112 configuration, related brand identities and factory operating checks.
OEM Part Number: MCP7Y10-N01AHT Part Number: MCP7Y10-N01A
| HT Part Number | MCP7Y10-N01A |
|---|---|
| NVIDIA/Mellanox InfiniBand Compatible | MCP7Y10-N01A |
| Manufacturer | HT |
| Form Factor | OSFP (IHS/Finned Top) to 2x QSFP112 |
| Max. Data Rate | 800Gbps |
| Media | Copper |
| Cable Type | Passive Breakout DAC |
| Cable Length | 1.5m (5ft) |
| Jacket Material | PVC |
| Minimum Bend Radius | 40.5mm |
| Wire AWG | 28AWG |
| Max. Power Consumption | 0.1W (OSFP End)0.1W (QSFP112 Per End) |
| Modulation Format | OSFP-8x 100G-PAM4QSFP112-4x 100G-PAM4 |
| Commercial Temperature Range | 0 to 70°C (32 to 158°F) |
| Application | 800G/400G InfiniBand |
| Protocols | OSFP MSA, QSFP112 MSA, IEEE 802.3ck, CMIS v5.0 |
The listed modulation format is OSFP-8x 100G-PAM4QSFP112-4x 100G-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.
The OSFP (IHS/Finned Top) to 2x QSFP112 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.
A passive DAC has no separate optical conversion stage. Its low-power, low-latency operation is useful for short equipment links, but the assembly must remain within the length and signaling mode accepted by both hosts.
The additional half metre beyond a one-metre assembly gives MCP7Y10-N01A useful routing flexibility when the ports are not directly aligned. It can accommodate a different rack unit or a short service loop, but excess cable should be dressed loosely rather than folded into a tight coil.
MCP7Y10-N01A occupies the middle of this family between MCP7Y10-N001 at 1m (3ft) and MCP7Y10-N002 at 2m (7ft). It adds 0.5m over the shorter option for extra routing clearance, while the next longer version adds another 0.5m. Measure the managed path and choose this version when its reach is sufficient without creating the slack associated with the longer assembly.
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 listed conductor specification is 28AWG; the minimum bend radius is 40.5mm; the stated power consumption is 0.1W (OSFP End)0.1W (QSFP112 Per End); the jacket material is PVC.
The rated power consumption is 0.1W (OSFP End)0.1W (QSFP112 Per End). 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 28AWG conductors, PVC jacket, minimum bend radius 40.5mm. 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 800G/400G InfiniBand. Listed interface and protocol references include OSFP MSA, QSFP112 MSA, IEEE 802.3ck, CMIS v5.0. Confirm that the host firmware and port configuration support the same operating mode.
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. Where supported by the host, link stability and diagnostic indications are reviewed together with the established link.
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 1.5m (5ft); 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. Standard protective packing is used by default, with project documentation arranged when requested.
No. It is an HT-manufactured compatible alternative for equipment that specifies NVIDIA/Mellanox MCP7Y10-N01A.
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.
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.
Standard configurations normally ship within one to three working days, while production quantities are confirmed with the order. Delivery can be arranged by courier, air freight or sea freight, and goods may instead be handed to an appointed forwarder or shipped on the customer’s courier account.