OCuLink storage cables: choose the destination and wiring

First identify what the OCuLink port is carrying

OCuLink is a compact cable interconnect used in PCIe and storage systems. To select an OCuLink cable, identify the host port’s function, the destination connector and the required wiring. Matching two housings is only the mechanical part of the decision.

An internal server cable may connect a board to an NVMe backplane or directly to a U.2 drive. An external graphics setup has a different endpoint and power arrangement. This guide focuses on internal storage cabling and four Renhotec 4i configurations.

The PCI-SIG OCuLink specification descriptions cover internal and external small-form-factor PCIe connectors and cables. Different revisions and implementations have their own electrical requirements. A family name is therefore insufficient evidence for a particular cable’s PCIe generation, reach or transfer performance.

SFF-8611, SFF-8612 and “4i”

The titles can be checked in the SNIA SFF specification index. Keep the number written on the equipment or assembly drawing when requesting a replacement; supplier listing conventions can vary.

The Renhotec products in this guide are listed as 4i. Do not order an 8i cable as an automatic performance upgrade: connector width, port implementation and the endpoint’s supported links have to agree. For comparison with other connector families, use the server and storage interface guide.

One host family, several destination connectors

The other end of the cable often tells you more about the installation than the OCuLink name alone. Supermicro’s FAQ for two X11 motherboard variants lists OCuLink, Mini-SAS HD and U.2 alternatives according to the backplane or drive-side arrangement. That is a platform-specific example, not permission to substitute these cables freely.

An OCuLink-to-Mini-SAS HD cable can be used in a documented PCIe route even though “SAS” appears in the connector name. Conversely, plugging it into a SAS-only port does not create a PCIe controller. Treat a mixed-end cable as a defined set of connections, not as a protocol converter.

Four Renhotec cable configurations

These entries compare the confirmed endpoint arrangement. The SKU links lead to Renhotec’s OCuLink family section. Host/target suitability and performance qualification must be matched to the application.

For 4003, measure both the host-side run and the power branch. The power lead may need to reach a different part of the chassis from the signal cable. The U.2 cable guide explains how to read a drive-side power assignment and compare mounting configurations.

When considering 4001 or 4002, include the destination board drawing with the request. A photograph identifies the connector family and exit direction, but cannot show the port’s protocol, sideband assignments or clock arrangement.

Example: choose by the destination you can identify

For a board-to-board route with two documented OCuLink 4i ports, RHT-726-4004 supplies the same-family physical arrangement. For a direct U.2 SSD connection, RHT-726-4003 changes the far end to SFF-8639 and adds the 15-pin power branch. A 4002 cable instead ends in SFF-8643, so it belongs to a route terminating at that board or backplane port. These endpoint choices narrow the cable list before the model-specific electrical match is reviewed.

Read the pair mapping before interpreting “straight”

In the 4004 configuration, “straight to straight” describes the connector exits. It does not mean every electrical contact keeps the same letter designation at the other end.

For example, the drawing connects P1 A15 to P2 B15 and labels those contacts Rx2+ and Tx2+. That correspondence can be checked without guessing which physical contact is on the left of an angled product photograph.

Ground, reserved and sideband entries also appear in the complete drawing. The excerpt does not replace them. A system-specific replacement review must include those connections, the viewing direction of each connector drawing and the required revision. Do not borrow the 4004 map for a mixed-end 4001, 4002 or 4003 assembly.

Specify performance as a channel requirement

“PCIe compatible” leaves several practical questions open. Specify the generation, usable lane width, cable length, connector arrangement and any adapter or backplane in the route. Ask what evidence qualifies that exact assembly under those conditions.

1. Confirm the port configuration

   Record the controller or CPU-connected port and its mode. Check shared-lane restrictions and any settings required by the equipment manual.

2. Account for the complete route

   Include adapters, backplane traces and intermediate connectors. A short cable does not eliminate losses or compatibility requirements elsewhere in the channel.

3. Check fit without loading the plug

   Leave access to the latch and support the cable independently. Measure the real chassis route and request the assembly’s bend limits; do not choose a bend radius from the sleeve’s appearance.

4. Verify the negotiated link

   After installation under the equipment’s service procedure, check device enumeration and reported link width/speed. Keep the result separate from an application benchmark, which also depends on workload and the storage device.

A continuity test answers whether specified contacts are connected. It does not establish signal integrity at the requested generation. Likewise, a successful test with one short sample does not qualify every available cable length.

For intermittent detection, record whether the fault follows movement, a particular port or a particular drive before changing another variable. Use the equipment’s service procedure for reseating; latch access does not establish support for unplugging a live link.

Does this storage cable selection apply to an eGPU?

An eGPU setup requires a supported host PCIe route, adapter or dock, graphics card and its specified power system. The four Renhotec storage configurations above do not establish graphics compatibility. Select against the host and dock’s cable requirements; drive-side U.2 power guidance cannot qualify an external graphics connection.

Send the port labels with your cable request

Provide the host and destination models, connector labels, port mode, required generation and lane width, routed length, exit direction and power arrangement. For an existing cable replacement, include its part number and drawing revision.

For a board-to-backplane route, include both port names and any sideband or clock requirements. For a direct U.2 connection, add the SSD model and available power input. These details distinguish assemblies that can look similar in a product photograph.