Specifications
Confirm model, interface type, rate, power, airflow and software version before ordering.
Deployment answer
MCX555A-ECAT should be treated as a host-integration project, not as a plug-in upgrade based only on a 100G label. The retained page identifies the ConnectX-5 VPI family, FDR/EDR InfiniBand, 40/50/100GbE, QSFP28, PCIe 3.0 x16 and RDMA support. A deployable design still needs a complete OPN, server slot and airflow check, compatible link media, and a tested driver/firmware combination.
What the current record can support
| Area | Current evidence | Acceptance evidence still needed |
|---|---|---|
| Protocol | VPI with InfiniBand and Ethernet modes | Configured mode on the adapter and peer port |
| Link rates | FDR/EDR and 40/50/100GbE are listed | Negotiated rate, error counters and supported media |
| Connector | QSFP28 | Exact optic, DAC or AOC and link budget |
| Server bus | PCIe 3.0 x16, 8.0 GT/s | Slot lanes, BIOS, NUMA locality and device enumeration |
| Software references | RHEL/CentOS, Windows, FreeBSD, VMware, OFED and WinOF-2 | Exact release matrix and upgrade/rollback procedure |
Where this deployment method fits
- Good fit: a defined HPC, storage or data-center host path with known switches, link media and software owners.
- Validate first: hypervisor pass-through, SR-IOV, RoCE, NVMe-oF or mixed-generation fabrics.
- Do not proceed yet: the server has no confirmed x16 slot, the cable is selected only by connector shape, or the target driver/firmware pair has not been approved.
Replacement and model comparison
MCX555A-ECAT and MCX556A-ECAT share the same high-level fields in the retained records, so those pages cannot establish interchangeability. A replacement review must compare complete OPNs, physical layout, bracket, supported protocol modes, firmware, operating system, cable OPN and the number of required links. Preserve the existing adapter until the new path passes rollback testing.
Six-step commissioning path
- Capture the original adapter, driver, firmware, switch port, cable and application baseline.
- Confirm server power state, slot width, lane allocation, NUMA location and airflow.
- Install the approved driver and firmware pair using a documented change window.
- Validate protocol mode, link rate, MTU, addressing, RDMA settings and monitoring.
- Run representative traffic and record throughput, latency, errors and CPU behavior under declared conditions.
- Test reboot, cable loss, peer-port failure, configuration restore and rollback.
FAQ
Can an InfiniBand link be changed to Ethernet without planning?
No. VPI capability does not replace switch-port, firmware, driver, addressing, lossless-network and application changes.
Should PCIe 3.0 x16 be accepted from the slot label alone?
No. Verify actual lane allocation, BIOS configuration, device enumeration and NUMA placement in the target server.
What should be recorded at handover?
Record the adapter and cable OPNs, firmware, driver, OS, peer port, negotiated mode, test conditions, error counters and rollback package.
Evidence boundary: The listed interface and software families come from the existing record and require model-level confirmation. This page does not promise price, stock, delivery, authorization, certification, warranty, lifecycle or workload gains.
Compare other ConnectX network adapters, review an AI and data-center network design, and use the interconnect acceptance path before handover.
WeChat
Profile