HOT CROSS-REFERENCE SEARCHES All Products
HR911105A Cisco GLC-LH-SMD Pulse J1011F21PNL LPJG0926HENL TE 2170704-1 SFP-10G-SR
POPULAR CATEGORIES
Matched Parts (Real-time ES) Use ↑ ↓ to select, Enter to open
INFINIBAND NETWORKING

InfiniBand Network Solutions for AI and HPC Fabrics

LINK-PP provides optical and electrical interconnects for InfiniBand AI and HPC fabrics, covering HDR 200G and NDR 400G connectivity with QSFP56, OSFP and QSFP112 optics, DAC, AEC and AOC assemblies for HCA-to-switch and switch-to-switch links.

INFINIBAND SCALE-OUT FABRIC SPINE 01 SPINE 02 IB LEAF 01 IB LEAF 02 IB LEAF 03 COMPUTE NODE HCA / CONNECTX COMPUTE NODE HCA / CONNECTX COMPUTE NODE HCA / CONNECTX HDR / NDR DAC · AEC · AOC · OPTICS
HCA → LEAF → SPINEHDR · NDR
HCA-facing linksLeaf-spine fabric

Quick answer: An InfiniBand network connects compute nodes through HCAs and dedicated InfiniBand switches to create a low-latency RDMA fabric. Modern AI and HPC deployments commonly use HDR- and NDR-class interconnects, with the physical link selected according to host platform, port form factor, reach, FEC, thermal limits and compatibility requirements.

Fabric Type
InfiniBand RDMA
Fabric Generations
HDR · NDR
Link Classes
200G · 400G
Physical Media
DAC · AEC · AOC · Fiber
INFINIBAND ARCHITECTURE

How InfiniBand Networks Are Structured

InfiniBand fabrics connect compute endpoints through HCAs and dedicated switches. The physical interconnect changes by fabric position, generation, port form factor, reach and host-platform requirements.

HCA TO SWITCH HDR / NDR 200G / 400G COMPUTE / HCA IB LEAF IB SPINE PHYSICAL INTERCONNECT QSFP56 · OSFP · QSFP112 · DAC · AOC HOST · PORT · FEC · THERMAL · MEDIA

HCA-to-Switch Components

  • ENDPOINTHCA ConnectivityMatch the HCA generation, InfiniBand mode and physical receptacle before selecting the cable or optical module.
  • MEDIAShort- or Optical-Reach LinkChoose DAC, AEC, AOC or pluggable optics according to reach, routing, serviceability and host support.
  • VALIDATIONProtocol & Host CompatibilityVerify EEPROM recognition, FEC behavior, firmware support, power class and thermal implementation.
FABRIC GENERATIONS

HDR vs NDR InfiniBand Connectivity

HDR- and NDR-class fabrics differ in link rate, host interface and physical-layer constraints. Final compatibility must be verified against the exact switch and HCA rather than inferred from speed alone.

Attribute
HDR-Class Fabric
NDR-Class Fabric
Selection Impact
Link Class
200G
400G
Confirm host-supported InfiniBand mode
Common Host Form Factor
QSFP56
OSFP / QSFP112
Mechanical fit is platform-specific
Electrical Signaling
50G-class PAM4 lanes
100G-class PAM4 lanes
Higher-rate links tighten signal and FEC margins
Typical Interconnect
DAC / AOC / Optics
DAC / AEC / AOC / Optics
Choose by reach and host support
Primary Constraint
Reach / compatibility
Thermal / FEC / compatibility
Validate the complete host-link combination
For the detailed generation comparison, see the InfiniBand NDR vs HDR Guide.
FABRIC POSITIONS

Where High-Speed InfiniBand Interconnects Fit

A single InfiniBand cluster can use different media by network position. The shortest HCA links may favor electrical cables, while fabric-scale switch links may require optical connectivity.

01 · HCA → LEAF

Compute Node Access

Connect GPU or CPU nodes through InfiniBand HCAs to the first switching tier using the host-supported HDR or NDR interface.

02 · LEAF → SPINE

High-Radix Fabric Links

Switch-to-switch links prioritize consistent link rate, port density, reach, FEC margin and thermal behavior across the fabric.

03 · RACK / POD

Rack-to-Rack Connectivity

Cable routing and reach determine whether AOC, pluggable optics or another supported media type is appropriate between racks or pods.

04 · MIGRATION

Mixed HDR / NDR Environments

Breakout or split-link designs can help connect mixed-generation environments where the host platform explicitly supports the required lane and port modes.

MEDIA SELECTION

DAC vs AEC vs AOC vs Optical Transceivers for InfiniBand

Do not select media from distance alone. Host electrical limits, cable routing, serviceability, FEC, module power and thermal behavior can all change the practical choice.

Media
Best Fit
Reach Class
Main Consideration
Passive DAC
HCA → switch, same rack
Very Short
Host channel loss and cable routing
AEC
Dense short NDR links where supported
Short
DSP / host interoperability
AOC
Rack / row optical cable links
Short / Medium
Fixed cable assembly and host coding
Optical Transceiver
Leaf-spine and structured fiber
Medium / Long
Fiber, connector, FEC, EEPROM and thermal profile
FORM FACTOR

QSFP56, OSFP and QSFP112 in InfiniBand Networks

The InfiniBand generation does not by itself determine a universally interchangeable module. The physical receptacle and host electrical implementation must match the actual switch or HCA.

QSFP56

HDR-Class Connectivity

QSFP56-class interfaces are commonly associated with 200G HDR environments and support optical or cable interconnects when validated for the target host.

OSFP

NDR-Class High-Density Fabric

OSFP is widely used in 400G NDR platforms, where module power, heatsink construction and chassis airflow become part of the compatibility decision.

QSFP112

400G 4-Lane Host Interfaces

QSFP112 uses four high-speed electrical lanes and may appear on compatible NDR-class platforms, but it is mechanically different from OSFP and must not be treated as interchangeable.

THERMAL DESIGN

Thermal Design for High-Speed InfiniBand Links

High-density NDR deployments place tighter demands on front-panel cooling and module thermal behavior. A module that is electrically correct can still fail if its mechanical or thermal implementation does not match the host.

POWER BUDGET

Host Power Class

Confirm that the target switch or HCA supports the power class required by the selected optic or active cable.

HEATSINK

OSFP Mechanical Profile

Open-top, closed-top and finned implementations must match the actual host receptacle and cooling architecture.

AIRFLOW

Dense Port Cooling

Evaluate module power together with port density, chassis airflow and sustained fabric utilization rather than treating the optic as an isolated component.

INFINIBAND COMPATIBILITY

InfiniBand Compatibility Goes Beyond the Form Factor

A QSFP56, OSFP or QSFP112 module that physically fits is not automatically suitable for an InfiniBand host. Platform generation, EEPROM behavior, link mode, FEC, power and thermal implementation must be validated together.

HOST PLATFORM

Quantum / ConnectX Generation

Identify the exact switch or HCA model, supported InfiniBand generation, port mode and software or firmware version.

EEPROM / I²C

Host Recognition

Vendor coding, memory-map behavior and host polling expectations can determine whether a compatible module initializes correctly.

FEC / ELECTRICAL

Link Bring-Up

Electrical lane mode, FEC settings and signal integrity must align across the host channel and interconnect.

MECHANICAL / THERMAL

Receptacle & Cooling

OSFP, QSFP112 and QSFP56 are not interchangeable by name or rate; verify receptacle, heatsink and airflow requirements.

Compatibility reference: NVIDIA / Mellanox InfiniBand Optics Guide Use the exact switch and HCA combination for qualification.
VALIDATION WORKFLOW

InfiniBand Link Validation Workflow

A useful qualification starts with the host and protocol, not the transceiver label.

Switch / HCA Model→ HDR / NDR→ Port Form Factor→ EEPROM / Firmware→ FEC / Link Mode→ Thermal Profile→ Media & Reach
HOST → PROTOCOL → PHYSICAL INTERFACE → LINK QUALIFICATION
FABRIC CONTEXT

InfiniBand vs Ethernet / RoCE: Where the Physical Layer Changes

Both fabrics can support RDMA-oriented workloads, but their host ecosystem, port configuration and compatibility requirements differ. This page focuses on InfiniBand physical connectivity rather than ranking one fabric over the other.

INFINIBAND

Purpose-Built RDMA Fabric

Dedicated InfiniBand switches and HCAs use generation- and platform-specific link modes, management behavior and interconnect requirements.

ETHERNET / RoCE

RDMA over Ethernet

RoCE operates within the Ethernet ecosystem and introduces a different host, switch and congestion-management context even when similar physical form factors are used.

TYPICAL BOM

Typical InfiniBand Interconnect BOM

Use the network position and host interface to narrow the physical interconnect family before selecting an exact LINK-PP model.

Network Position
Fabric Class
Host Interface
Media Options
HCA → Leaf
HDR
QSFP56
DAC / AOC / Optics
HCA → Leaf
NDR
OSFP / QSFP112
DAC / AEC / AOC / Optics
Leaf → Spine
HDR
QSFP56
AOC / Optical
Leaf → Spine
NDR
OSFP
Optical / supported active cable
Mixed Generation
HDR / NDR
Platform-Specific
Breakout / split-link architecture where supported
CONNECTIVITY PORTFOLIO

LINK-PP Product Families Relevant to InfiniBand Interconnects

These product families include hardware used across high-speed networking environments. Verify the exact LINK-PP model, protocol support and host compatibility before deployment in an InfiniBand fabric.

200G

200G QSFP56 / QSFP-DD Optics

200G optical modules for compatible high-speed platforms, including QSFP56-class form factors relevant to HDR environments.

Explore 200G Optics →
400G

400G OSFP / QSFP112 / QSFP-DD Optics

400G optical families covering multiple host form factors. Confirm InfiniBand-specific compatibility before selecting an exact model.

Explore 400G Optics →
CABLES

DAC / AOC / AEC Assemblies

Short-reach copper, active electrical and active optical assemblies for compatible server-to-switch and switch-to-switch links.

Explore High-Speed Cables →
COMPATIBILITY

Mellanox / NVIDIA InfiniBand Guide

Review HDR/NDR host, EEPROM, FEC, thermal and cable-selection considerations before mapping a part number.

View Compatibility Guide →
ENGINEERING RFQ

What to Send for an InfiniBand Interconnect Recommendation

“Need 400G InfiniBand modules” is not enough to identify a compatible part. The host model, port implementation and deployment details matter.

Fabric Requirements

  • HDR / NDR generation
  • Target link rate
  • Fabric topology
  • Number of nodes and links per node

Host Platform

  • Switch manufacturer and model
  • HCA manufacturer and model
  • Port form factor
  • Software / firmware version

Physical Link

  • Required distance
  • DAC / AEC / AOC / optics preference
  • Fiber and connector type
  • Breakout or heatsink requirement
ENGINEERING RESOURCES

InfiniBand Networking Technical References

The links below are existing LINK-PP resources selected for the specific engineering question they answer.

FAQ

InfiniBand Network Questions

What is the difference between HDR and NDR InfiniBand?

HDR-class InfiniBand commonly uses 200G links and QSFP56 interfaces, while NDR-class deployments move to 400G connectivity with OSFP or QSFP112 host interfaces. Exact implementation depends on the switch, HCA, port mode and interconnect type.

Can Ethernet optical modules be used in InfiniBand switches?

Not automatically. A module may share the same mechanical form factor but still fail because InfiniBand host recognition, EEPROM coding, electrical mode, FEC behavior, firmware expectations or thermal implementation do not match the target platform.

When should InfiniBand use DAC, AEC, AOC or optical transceivers?

Passive DAC is suited to the shortest electrical links. AEC can extend short electrical connectivity where supported. AOC provides a factory-terminated optical cable assembly, while pluggable optical transceivers are appropriate for structured fiber and longer switch-to-switch connections.

What is the difference between QSFP56, OSFP and QSFP112?

QSFP56 is commonly associated with 200G HDR-class connectivity, while OSFP and QSFP112 are used on compatible 400G NDR-class platforms. They have different mechanical and electrical implementations and are not interchangeable simply because the aggregate rate is similar.

Why does InfiniBand optical compatibility depend on EEPROM coding?

The host reads module identification and management information during initialization. Correct hardware specifications alone do not guarantee that a third-party module will be recognized or configured correctly by a particular switch or HCA firmware release.

What information is required to verify an InfiniBand link?

Provide the InfiniBand generation, switch model, HCA model, port form factor, software or firmware version, link distance, preferred media and any breakout or thermal requirements.

NEXT STEP

Map Your InfiniBand Fabric to the Right Interconnect

Provide the exact switch, HCA, InfiniBand generation, port form factor and reach so LINK-PP can map the physical links to suitable optical or electrical interconnect options.

For Network Architects

Review Your InfiniBand Fabric

Send the HCA-to-leaf and leaf-to-spine topology together with host platform details for link mapping.

Contact Engineering →
For Procurement

Request Compatible InfiniBand Pricing

Provide the required quantities, host models and deployment schedule for compatible-part and lead-time review.

Request a Quote →
For OEM / Integrators

Submit Your InfiniBand BOM

Submit switch, HCA and physical-link requirements for optics, DAC, AEC and AOC alternatives.

Submit BOM →