
The QSFP112 to QSFP112-400G-AOC-10M33FT compatible assembly is a 400G AOC cable for Generic hosts, built in 10m (33ft) with QSFP112 to QSFP112. It serves as one complete direct-attached link, while the compatibility and diagnostic checks below address the host-specific identification needed in a mixed-equipment environment.
OEM Part Number: QSFP112 to QSFP112-400G-AOC-10M33FTHT Part Number: QSFP112 to QSFP112-400G-AOC-10M33FT
| HT Part Number | QSFP112 to QSFP112-400G-AOC-10M33FT |
|---|---|
| Manufacturer | HT |
| Form Factor | QSFP112 to QSFP112 |
| Max. Data Rate | 400Gbps |
| Cable Length | 10m (33ft) |
| Cable Type | AOC |
| Wavelength | 850nm |
| Minimum Bend Radius | 30mm |
| Transmitter Type | VSCEL |
| Receiver Type | PIN |
| Max. Power Consumption | 10W Per End |
| Jacket Material | OFNP |
| CDR (Clock and Data Recovery) | TX & RX Built-in CDR |
| Modulation Format | 4x 100G-PAM4 |
| DDM/DOM | Supported |
| Commercial Temperature Range | 0 to 70°C (32 to 158°F) |
| Protocols | CMIS 4.0, IEEE 802.3 ck-400GAUI-4, QSFP112 MSA |
The listed modulation format is 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.
At 10m (33ft), QSFP112 to QSFP112-400G-AOC-10M33FT should be planned as an extended equipment-room connection rather than a short in-rack jumper. Mark the complete vertical and horizontal route before installation, including every manager the cable will actually pass through. Support the integrated optical cable and both optical engines along that path and keep both ends free from pull loads. Within this family, QSFP112 to QSFP112-400G-AOC-7M23FT is shorter at 7m (23ft), while QSFP112 to QSFP112-400G-AOC-15M49FT is the next longer choice at 15m (49ft); comparing those two boundaries helps avoid both tension and unnecessary slack.
QSFP112 to QSFP112-400G-AOC-10M33FT occupies the middle of this family between QSFP112 to QSFP112-400G-AOC-7M23FT at 7m (23ft) and QSFP112 to QSFP112-400G-AOC-15M49FT at 15m (49ft). It adds 3m over the shorter option for extra routing clearance, while the next longer version adds another 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 minimum bend radius is 30mm; the stated power consumption is 10W Per End; the jacket material is OFNP.
The rated power consumption is 10W 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 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 CMIS 4.0, IEEE 802.3 ck-400GAUI-4, QSFP112 MSA. 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.
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, receive activity 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. Keep QSFP112 to QSFP112-400G-AOC-10M33FT associated with 10m (33ft) throughout the order and receiving record.
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 manufactured by HT under our own manufacturer identity.
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.
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.