NVIDIA/Mellanox MC2309130-001 Compatible 40G QSFP+ to 1 x 10G SFP+ Ethernet Passive Copper Cable, 1m (3ft)
The assembly listed here is the 1m (3ft) member of the MC2309130-001 product family for NVIDIA/Mellanox equipment. It provides 40G DAC connectivity through QSFP+ to SFP+. Project teams can use the detailed table, related references and documentation-oriented packing information to keep each delivered cable aligned with its planned endpoints.
OEM Part Number: MC2309130-001HT Part Number: MC2309130-001
Product Highlights
- Compatible alternative to NVIDIA/Mellanox MC2309130-001
- 40G connectivity at 40Gbps
- Interface configuration: QSFP+ to SFP+
- Fixed length and part number: 1m (3ft), MC2309130-001
- Cable construction: Passive Twinax
- Conductor specification: 26AWG
- Maximum power consumption: 0.1W Per End
- Minimum bend radius: 28mm
Specifications
| HT Part Number | MC2309130-001 |
|---|---|
| NVIDIA/Mellanox Ethernet Compatible | MC2309130-001 |
| Manufacturer | HT |
| Form Factor | QSFP+ to SFP+ |
| Max. Data Rate | 40Gbps |
| Media | Copper |
| Cable Type | Passive Twinax |
| Cable Length | 1m (3ft) |
| Wire AWG | 26AWG |
| Minimum Bend Radius | 28mm |
| Max. Power Consumption | 0.1W Per End |
| Jacket Material | PVC (OFNR) |
| Commercial Temperature Range | 0℃ to 70℃ (32 to 158°F) |
| Protocols | SFF-8636, SFF-8472 |
Power and Thermal Planning
The rated power consumption is 0.1W 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.
Passive Copper Operation
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.
Length Selection and Installation Planning
At 1m (3ft), MC2309130-001 is a practical choice for direct connections within one rack. Route the cable along the intended management path rather than pulling it diagonally across adjacent connectors, and leave enough clearance for insertion, removal and front-panel airflow.
Position Within the Length Range
MC2309130-001 occupies the middle of this family between MC2309130-00A at 0.5m (2ft) and MC2309130-002 at 2m (7ft). It adds 0.5m over the shorter option for extra routing clearance, while the next longer version adds another 1m. Measure the managed path and choose this version when its reach is sufficient without creating the slack associated with the longer assembly.
Project Documentation and Cable Identification
Large deployments are easier to audit when the order code, physical length and endpoint record agree. Keep the OEM reference in the compatibility document and use the HT part number on the packing list. Where several lengths arrive together, labels and carton groups can be arranged by rack or port plan so installers do not have to identify cables by appearance alone. For this assembly, the listed conductor specification is 26AWG; the minimum bend radius is 28mm; the stated power consumption is 0.1W Per End; the jacket material is PVC (OFNR).
Cable Construction and Routing
This assembly uses 26AWG conductors, PVC (OFNR) jacket, minimum bend radius 28mm. 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.
Network and Protocol Considerations
The intended application is determined by the host interface and protocol support. Listed interface and protocol references include SFF-8636, SFF-8472. Confirm that the host firmware and port configuration support the same operating mode.
NVIDIA/Mellanox Compatibility and Factory Testing
Factory verification links the compatibility identity to the exact physical assembly described on this page. Identification, connector condition and live link behavior are checked before packing. Customers can submit equipment and firmware details with the project documentation for a more specific pre-order compatibility review. Both connectors are examined before the operating test, which includes link stability and diagnostic indications.
Frequently Asked Questions
Is this an original NVIDIA/Mellanox cable?
No. It is an HT-manufactured compatible alternative for equipment that specifies NVIDIA/Mellanox MC2309130-001.
Does this order code cover multiple lengths?
No. MC2309130-001 refers here to 1m (3ft). Every other verified length has a separate part number and page in the length list.
Are separate transceivers or patch leads required?
No. This is one complete direct-attach assembly. The ends are not detachable modules and should not be separated from the cable.
Can excess cable be folded into a compact bundle?
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.
Ordering Information
Use the listed HT part number for ordering and retain the OEM reference as the host-compatibility cross-reference. Send quantities by length, along with any rack-based packing or label instructions. If the project has mixed equipment, include the host model for each group rather than relying only on the aggregate cable rate. This page’s fixed configuration is 1m (3ft); another length must be quoted under its corresponding part number.
Shipping and Lead Time
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.
Quality Assurance and Packaging
Inspection and link testing are completed before the cable enters its protective packaging. Project orders can be packed and labelled by length, rack or customer reference, with packing documentation that makes received quantities straightforward to reconcile against the installation schedule. Standard protective packing is used by default, with project documentation arranged when requested.
