Mellanox ConnectX-5 EN operation manual

Page 1

Exported onDec/16/2020 07:33 PM

https://docs.mellanox.com/x/V4eO

NVIDIA Mellanox ConnectX-5 Ethernet Adapter Cards for OCP Spec 2.0 User Manual

25 and 100 Gb/s Ethernet Adapter Cards; Intelligent RDMA (RoCE) enabled NICs. Supporting OCP Specification 2.0 type 1 and type 2.

Page 2

Table of Contents

Introduction................................................................................................................8

OCP Spec 2.0 Stacking Heights .............................................................................................. 9

OCP Spec 2.0 Type 1 Stacking Height - Single-port Card ............................................... 9

OCP Spec 2.0 Type 1 Stacking Height - Dual-port Card................................................. 10

OCP Spec 2.0 Type 2 Stacking Height - Single-port Card .............................................. 10

OCP Spec 2.0 Type 2 Stacking Height - Dual-port Card................................................. 10

Features and Benefits........................................................................................................... 11

Operating Systems/Distributions ......................................................................................... 12

Connectivity ........................................................................................................................... 13

Interfaces .................................................................................................................14

Ethernet SFP28 and QSFP28 Interfaces .............................................................................. 14

PCI Express Interface ........................................................................................................... 14

LED Interface......................................................................................................................... 14

SMBus Interface.................................................................................................................... 15

Voltage Regulators................................................................................................................ 15

Thermal Sensors................................................................................................................... 15

Hardware Installation ..............................................................................................16

Safety Warnings..................................................................................................................... 16

Installation Procedure Overview........................................................................................... 16

System Requirements........................................................................................................... 16

Hardware Requirements ................................................................................................. 17

Airflow Requirements ................................................................................................. 17

Software Requirements ................................................................................................... 17

Unpacking the Product ......................................................................................................... 17

Adapter Cards Installation Instructions............................................................................... 18

Cables and Modules.............................................................................................................. 19

Identifying the Card in Your System ..................................................................................... 20

Adapter Cards Extraction Instructions................................................................................. 21

Safety Precautions ...........................................................................................................21

Card Extraction................................................................................................................. 22

Driver Installation ....................................................................................................24

Windows Driver Installation.................................................................................................. 24

Page 3

Software Requirements ................................................................................................... 24

Downloading Mellanox WinOF-2 Driver ..........................................................................24

Installing Mellanox WinOF-2 Driver ............................................................................... 25

Attended Installation................................................................................................... 25

Unattended Installation...............................................................................................30

Installation Results ..................................................................................................... 31

Uninstalling Mellanox WinOF-2 Driver............................................................................ 31

Attended Uninstallation ..............................................................................................31

Unattended Uninstallation.......................................................................................... 31

Extracting Files Without Running Installation ................................................................ 32

Firmware Upgrade ........................................................................................................... 34

Linux Driver Installation........................................................................................................ 34

Prerequisites .................................................................................................................... 34

Downloading Mellanox OFED .......................................................................................... 35

Installing Mellanox OFED ................................................................................................ 35

Installation Script ........................................................................................................35

Installation Procedure ................................................................................................37

Installation Results ..................................................................................................... 39

Installation Logs..........................................................................................................39

openibd Script..............................................................................................................39

Driver Load Upon System Boot ..................................................................................40

mlnxofedinstall Return Codes....................................................................................40

Uninstalling MLNX_OFED........................................................................................... 40

Installing MLNX_OFED Using YUM ................................................................................. 40

Setting up MLNX_OFED YUM Repository................................................................... 41

Installing MLNX_OFED Using the YUM Tool ..............................................................41

Uninstalling MLNX_OFED Using the YUM Tool .........................................................43

Installing MLNX_OFED Using apt-get Tool..................................................................... 43

Setting up MLNX_OFED apt-get Repository ..............................................................43

Installing MLNX_OFED Using the apt-get Tool..........................................................43

Uninstalling MLNX_OFED Using the apt-get Tool..................................................... 44

Updating Firmware After Installation.............................................................................. 44

Updating the Device Online......................................................................................... 44

Updating the Device Manually .................................................................................... 44

Page 4

Updating the Device Firmware Automatically upon System Boot ............................ 45

UEFI Secure Boot............................................................................................................. 45

Enrolling Mellanox's x.509 Public Key on Your Systems...........................................45

Removing Signature from kernel Modules ................................................................46

Performance Tuning ........................................................................................................47

VMware Driver Installation ................................................................................................... 47

Hardware and Software Requirements........................................................................... 47

Installing Mellanox NATIVE ESXi Driver for VMware vSphere........................................ 47

Removing Earlier Mellanox Drivers................................................................................. 48

Firmware Programming .................................................................................................. 48

Updating Adapter Firmware ....................................................................................49

Troubleshooting .......................................................................................................50

GeneralTroubleshooting ...................................................................................................... 50

LinuxTroubleshooting .......................................................................................................... 50

WindowsTroubleshooting..................................................................................................... 51

Specifications ...........................................................................................................52

MCX542A-ACANSpecifications ............................................................................................ 52

MCX542B-AC[A/U]NSpecifications...................................................................................... 53

MCX545B-GCUNSpecifications............................................................................................ 54

MCX545B-CCUNSpecifications............................................................................................ 55

MCX545A-CCAN andMCX545A-CCUN Specifications......................................................... 56

MCX546A-BCANSpecifications ............................................................................................ 57

MCX546A-CDANSpecifications ............................................................................................ 58

Board Mechanical Drawing and Dimensions....................................................................... 59

Finding the MAC and Serial Number on the Adapter Card ......................................63

Document Revision History ......................................................................................64

Page 5

About This Manual

This User Manual describes NVIDIA® Mellanox® ConnectX®-5 and ConnectX®-5 Ex Ethernet adapter cards for Open Compute Project (OCP), Spec 2.0. It provides details as to the interfaces of the board, specifications, required software and firmware for operating the board, and relevant documentation.

Ordering Part Numbers

The table below provides the ordering part numbers (OPN) for the available ConnectX-5 Ex and ConnectX-5 Ethernet adapter cards for OCP Spec 2.0.

IC in Use OPN Marketing Description

MCX542A-ACAN ConnectX®-5 EN network interface card for

OCP2.0, Type 1, with host management,

ConnectX®-5

MCX542B-ACAN ConnectX®-5 EN network interface card for

MCX542B-ACUN ConnectX®-5 EN network interface card for

25GbE dual-port SFP28, PCIe3.0 x16, Halogen-free, no bracket

OCP2.0, Type 1, with host management, 25GbE dual-port SFP28, PCIe3.0 x8, Halogenfree, no bracket

OCP2.0, Type 1, with host management, 25GbE dual-port SFP28, PCIe3.0 x8, UEFI Enabled (x86/ARM), Halogen free, no bracket

ConnectX®-5 Ex

MCX545B-GCUN ConnectX®-5 EN network interface card for

OCP2.0, Type 1, with hostmanagement, 50GbE,single-port QSFP28,PCIe3.0x16,UEFI Enabled, no bracket

MCX545B-CCUN ConnectX®-5 EN network interface card for

OCP2.0, Type 1, with host management, 100GbE, single-port QSFP28, PCIe3.0 x16, UEFI Enabled, no bracket

MCX545A-CCAN ConnectX®-5 EN network interface card for

OCP2.0, Type 2, with host management, 100GbE, single-port QSFP28, PCIe3.0 x16, no

bracket

MCX545A-CCUN ConnectX®-5 EN network interface card for

OCP2.0, Type 2, with host management, 100GbE, single-port QSFP28, PCIe3.0 x16, UEFI Enabled, no bracket

MCX546A-BCAN ConnectX®-5 Ex EN network interface card

for OCP2.0, Type 2, 40GbE dual-port QSFP28, PCIe3.0 x16, no bracket

MCX546A-CDAN ConnectX®-5 Ex network interface card for

OCP2.0, Type 2, with host management, 100GbE dual-port QSFP28, PCIe4.0 x16, no

bracket

Intended Audience

This manual is intended for the installer and user of these cards.The manual assumes basic familiarity

with Ethernet network and architecture specifications.

Technical Support

Page 6

Customers who purchased Mellanox products directly from Mellanox are invited to contact usthrough

the following methods:

•

URL:http://www.mellanox.com> Support

•

E-mail:support@mellanox.com

•

Tel: +1.408.916.0055

Customers who purchased Mellanox M-1 Global Support Services, please see your contract fordetails

regarding Technical Support. Customers who purchased Mellanox products through a Mellanox approved reseller should first

seekassistance through their reseller.

Introduction

This is the User Guide for Ethernet adapter cards based on the ConnectX®-5 integrated circuit device for OCP Spec 2.0. These adapters connectivity provide the highest performing low latency and most flexible interconnect solution for PCI Express Gen 3.0/4.0 servers used in Enterprise Data Centers and High-Performance Computing environments.

The following provides the ordering part number, port speed, number of ports, and PCI Express speed.

ConnectX-5 Ex Ethernet Adapter Cards

Model ConnectX-5 Ex Cards for OCP Spec 2.0

Part Number MCX546A-BCAN MCX546A-CDAN

Ethernet Data Rate 10/25/40 Gb/s 10/25/40/50/100 Gb/s

Host Management - √

Network Connector Type Dual-port QSFP28 Dual-port QSFP28

OCP Spec 2.0 Type Type 2 Stacking Height

PCI Express Connectors

Dimensions 3.07 in. x 4.33 in (78.00mm x 110.05mm)

PCIe Gen 3.0 x16 SERDES @ 8.0GT/s

(a), (b)

PCIe Gen 3.0 / 4.0 x16 SERDES @ 8.0GT/s / 16.0GT/s

(a), (b)

RoHS RoHS Compliant

IC Part Number MT28808A0-FCCF-EV

Device ID 4121 for Physical Function (PF)

4122 for Virtual Function (VF)

a. PCIe 4.0 x16 bus can supply a maximum bandwidth of 256Gb/s (=16 *16GT/s, including overhead), and can support 200Gb/s when both network ports of the card run at 100Gb/s.

b.TheGen4.0 cards have been tested and certified with PCIe 3.0 servers. PCIe 4.0 interface will be

tested when servers with Gen 4.0 support become available.

ConnectX-5 Ethernet Adapter Cards

Model ConnectX-5 Cards for OCP Spec 2.0

Part Number

Network Connecto r Type

OCP Spec

2.0 Type

MCX542A-

ACAN

Dual-port SFP28

Type 1

Stacking

Height

MCX542B-

ACAN

(a)

Dual-port

SFP28

Type 1

Stacking

Height

MCX542B-

ACUN

Dual-port

SFP28

Type 1

Stacking

Height

MCX545B-

GCUN

Single-port

QSFP28

Type 1

Stacking

Height

MCX545A-

CCAN

Single-port QSFP28

Type 2

Stacking

Height

MCX545A-

CCUN

Single-port

QSFP28

Type 2

Stacking

Height

MCX545BCCUN

Single-port

QSFP28

Type 1

Stacking

Height

Page 9

Model ConnectX-5 Cards for OCP Spec 2.0

Ethernet Data Rate

PCI Express Connecto rs

Halogen Free

Host Managem ent

UEFI - - √ √ - √ √

Dimensions3.07 in. x

RoHS RoHS Compliant

IC Part Number

Device ID 4119 for Physical Function (PF)

10/25 Gb/s 10/25/40/50

Gb/s

PCIe Gen 3.0 x16 SERDES @

8.0GT/s

√ √ √ - - - -

√ √ √ √ √ √ √

4.33 in (78.00mm x

110.05mm)

4120 for Virtual Function (VF)

PCIe Gen 3.0 x8 SERDES @

8.0GT/s

2.67 in. x

4.33 in (68.00mm x

110.05mm)

PCIe Gen 3.0

SERDES @

8.0GT/s

2.67 in. x

4.33 in

(68.00mm x

110.05mm)

MT28808A0-FCCF-EV

PCIe Gen 3.0

x16

SERDES @

8.0GT/s

2.67 in. x

4.33 in

(68.00mm x

110.05mm)

10/25/40/50/

100 Gb/s

PCIe Gen 3.0 x16 SERDES @

8.0GT/s

3.07 in. x

4.33 in (78.00mm x

110.05mm)

10/25/40/50/

100 Gb/s

PCIe Gen 3.0

x16

SERDES @

8.0GT/s

3.07 in. x

4.33 in

(78.00mm x

110.05mm)

10/25/40/50/

100 Gb/s

PCIe Gen 3.0

x16

SERDES @

8.0GT/s

3.07 in. x

4.33 in

(78.00mm x

110.05mm)

a.Mellanox recommends populating MCX542B-ACAN in a standard PCIe x8 OCP connector which exposes PCIe lanes in a straight manner.

 In case the OCP slot exposes PCIe lanes in a reversed manner, MCX542B-ACAN supports automatic lane reversal withFW image from April 2019 release and above.

For more detailed information seeSpecifications.

OCP Spec 2.0 Stacking Heights

OCP Spec 2.0 Type 1 Stacking Height - Single-port Card

This section applies to MCX545B-CCUN andMCX545B-GCUN.



The single port 100Gb/s Ethernet adapter card complies with OCP Spec 2.0 Type 1 with 8mm stacking height.

Page 10

OCP Spec 2.0 Type 1 Stacking Height - Dual-port Card

This section applies to MCX542A-ACAN and MCX542B-ACAN.



The dual port 10/25Gb/s Ethernet adapter card comply with OCP Spec 2.0 Type 1 with 8mm stacking height.

OCP Spec 2.0 Type 2 Stacking Height - Single-port Card

This section applies to MCX545A-CCAN and MCX545A-CCUN.



The single-port 100Gb/s adapter card follows OCP Spec 2.0 Type 2 with 12mm stacking height.

OCP Spec 2.0 Type 2 Stacking Height - Dual-port Card

This section applies to MCX546A-CDAN and MCX546A-BCAN.



The dual-port 100Gb/s adapter card follows OCP Spec 2.0 Type 2 with 12mm stacking height.

Page 11

Features and Benefits

This section describes hardware features and capabilities. Please refer to the relevant driver



and/or firmware release notes for feature availability.

Feature Description

PCI Express (PCIe) Uses PCIe Gen 3.0 (8GT/s) and Gen 4.0 (16GT/s) through an x8 or x16

edge connector. Gen 1.1 and 2.0 compatible.

Up to 25 Gigabit Ethernet Mellanox adapters comply with the following IEEE 802.3 standards:

• 100GbE/ 50GbE / 40GbE / 25GbE / 10GbE / 1GbE

• IEEE 802.3bj, 802.3bm 100 Gigabit Ethernet

• IEEE 802.3by, Ethernet Consortium25, 50 Gigabit Ethernet, supporting all FEC modes

• IEEE 802.3ba 40 Gigabit Ethernet

• IEEE 802.3by 25 Gigabit Ethernet

• IEEE 802.3ae 10 Gigabit Ethernet

• IEEE 802.3ap based auto-negotiation and KR startup

• Proprietary Ethernet protocols (20/40GBASE-R2, 50GBASE-R4)

• IEEE 802.3ad, 802.1AX Link Aggregation

• IEEE 802.1Q, 802.1P VLAN tags and priority

• IEEE 802.1Qau (QCN)

• Congestion Notification

• IEEE 802.1Qaz (ETS)

• IEEE 802.1Qbb (PFC)

• IEEE 802.1Qbg

• IEEE 1588v2

• Jumbo frame support (9.6KB)

Memory SPI Quad - includes 128Mbit SPI Quad Flash device

Overlay Networks In order to better scale their networks, data center operators often

• (W25Q128FVSIG device by ST Microelectronics).

•

VPD EEPROM - The EEPROM capacity is 128Kbit.

create overlay networks that carry traffic from individual virtual machines over logical tunnels in encapsulated formats such as NVGRE and VXLAN. While this solves network scalability issues, it hides the TCP packet from the hardware offloading engines, placing higher loads on the host CPU. ConnectX-5 effectively addresses this by providing advanced NVGRE and VXLAN hardware offloading engines that encapsulate and de-capsulate the overlay protocol.

Page 12

Feature Description

RDMA and RDMA overConverged Ethernet (RoCE)

Mellanox PeerDirect™ PeerDirect™ communication provides high-efficiency RDMA access

CPU Offload Adapter functionality enabling reduced CPU overhead allowing more

Quality of Service (QoS) Support for port-based Quality of Service enabling various

Hardware-based I/OVirtualization ConnectX-5 provides dedicated adapter resources and guaranteed

Storage Acceleration A consolidated compute and storage network achieves significant

ConnectX-5, utilizing IBTA RDMA (Remote Data Memory Access) and RoCE (RDMA over Converged Ethernet) technology, delivers lowlatency and high-performance over Band and Ethernet networks. Leveraging data center bridging (DCB) capabilities as well as ConnectX-5 advanced congestion control hardware mechanisms, RoCE provides efficient low-latency RDMA services over Layer 2 and Layer 3 networks.

by eliminating unnecessary internal data copies between components on the PCIe bus (for example, from GPU to CPU), and therefore significantly reduces application run time. ConnectX-5 advanced acceleration technology enables higher cluster efficiency and scalability to tens of thousands of nodes.

available CPU for computation tasks. Open vSwitch (OVS) offload using ASAP

• Flexible match-action flow tables

• Tunneling encapsulation/decapsulation

application requirements for latency and SLA.

isolation and protection for virtual machines within the server.

cost-performance advantages over multi-fabric networks. Standard block and file access protocols can leverage RDMA for highperformance storage access.

• NVMe over Fabric offloads for the target machine

• T10-DIF Signature Handover

2(TM)

SR-IOV ConnectX-5 SR-IOV technology provides dedicated adapter

resources and guaranteed isolation and protection for virtual machines (VM) within the server.

NC-SI The adapter supports a Network Controller Sideband Interface (NC-

SI), MCTP over SMBus and MCTP over PCIe - Baseboard Management Controller interface.

High-PerformanceAccelerations • Tag Matching and Rendezvous Offloads

• Adaptive Routing on Reliable Transport

• Burst Buffer Offloads for Background Checkpointing

Operating Systems/Distributions

•

RHEL/CentOS

•

Windows

•

FreeBSD

•

VMware

•

OpenFabrics Enterprise Distribution (OFED)

•

OpenFabrics Windows Distribution (WinOF-2)

Page 13

Connectivity

•

Interoperable with 1/10/25/40/50/100Gb/s Ethernet switches

•

Passive copper cable with ESD protection

•

Powered connectors for optical and active cable support

Page 14

Interfaces

Ethernet SFP28 and QSFP28 Interfaces

The network ports of the ConnectX®-5 adapter card are compliant with the IEEE 802.3 Ethernet

standards listed inFeatures and Benefits. Ethernet traffic is transmitted through the SFP28/QSFP28 connectors on the adaptercard.

The adapter card includes special circuits to protect from ESD shocks to the card/server when



plugging copper cables.

PCI Express Interface

The table below describes the supported PCIe interface in ConnectX-5 and ConnectX-5 Ex adapter cards.

IC Model Supported PCIe Interface Features

ConnectX-5 PCIe Gen 3.0 (1.1 and 2.0 compatible)

through x16 edge connectors

ConnectX-5 Ex PCIe Gen 3.0/4.0 (1.1 and 2.0 compatible)

through x16 edge connectors

Link Rates: 2.5. 5.0 or 8.0GT/s. Auto Negotiation to: x16, x8, x4, x2 or x1. Support for MSI/MSI-X mechanisms.

Link Rates: 2.5. 5.0, 8.0 or 16.0GT/s. Auto Negotiation to: x16, x8, x4, x2 or x1. Support for MSI/MSI-X mechanisms.

LED Interface

There are two I/O LEDs, LED0 and LED1, per port to indicate speed and link status. LED0 is a bicolor (yellow and green) LED and LED1 is a single color (green) LED.

Link Indications

LED and State Description

1Hz blinking Yellow Beacon command for locating the adapter card

Page 15

LED and State Description

4Hz blinking Yellow Indicates an error with the link. The error can be one of the

following:

Error Type Description LED Behavior

Blinks until the error is fixed

LED0 Link Speed

LED1 Activity

I2C I2C access to the

networking ports fails

Over-current Over-current condition

of the networking ports

•

A constant Green indicates a link withthe maximum

networking speed.

•

A constant Yellow indicates a link withless than the

maximum networking speed

•

If LED0 is off, then the link has not been established.

•

A blinking Green indicates a valid link with data transfer.

•

If LED1 is off, then there is no activity

Heatsink Interface

A heatsink is attached to the ConnectX-5 IC in order to dissipate the heat from the ConnectX- 5 IC. It is attached either by using four spring-loaded push pins that insert into four mounting holes or by screws.

ConnectX-5 IC has a thermal shutdown safety mechanism that automatically shuts down the ConnectX-5 card in cases of high-temperature events, improper thermal coupling, or heatsink removal.

SMBus Interface

ConnectX-5 technology maintains support for manageability through a BMC. ConnectX-5 PCIe stand-up adapter can be connected to a BMC using MCTP over SMBus or MCTP over PCIe protocols as if it is a standard Mellanox PCIe stand-up adapter. For configuring the adapter for the specific manageability solution in use by the server, please contact Mellanox Support.

Voltage Regulators

The voltage regulator power is derived from the PCI Express edge connector 12V supply pins. These voltage supply pins feed on-board regulators that provide the necessary power to the various components on the card.

Thermal Sensors

Unable to render include or excerpt-include. Could not retrieve page.

Page 16

Hardware Installation

Installation and initialization of ConnectX-5 adapter cards for OCP Spec 2.0 require attention to the mechanical attributes, power specification, and precautions for electronic equipment.

Safety Warnings

Safety warnings are provided here in the English language. For safety warnings in other



languages, refer to the Adapter Installation Safety Instructions document available on

mellanox.com.

Unable to render include or excerpt-include. Could not retrieve page.

Installation Procedure Overview

The installation procedure of ConnectX-5 adapter cards for OCP Spec 2.0 involves the following steps:

Step Procedure Link

1 Check the system’s hardware and software

requirements.

2 Pay attention to the airflow consideration within

the host system.

3 Unpack the product. Unpacking the Product

4 Install the adapter card in the system. Adapter Card Installation

5 Connect cables or modules to the card. Cables and Modules

6 Identify ConnectX-5 adapter card in the system. Identify the Card in the System

System Requirements

Hardware Requirements

System Requirements

Unless otherwise specified, Mellanox products are designed to work in an environmentally



controlled data center with low levels of gaseous and dust (particulate) contamination.

The operation environment should meet severity level G1 as per ISA 71.04 for gaseous contamination and ISO 14644-1 class 8 for cleanliness level.

Page 17

Hardware Requirements

For proper operation and performance, please make sure to use a PCIe slot with a



corresponding bus width and that can supply sufficient power to your card. Refer to the Specifications section of the manual for more power

A system with a PCI Express x16 slot (two FCI B2B x8 connectors) is required for installing the card. ConnectX-5 cards for OCP are complaint with automatic hosts-count detection per OCP Mezzanine card v2.0 (http://www.opencompute.org/wiki/Server/SpecsAndDesigns).

Mellanox recommends populating MCX542B-ACAN in a standard PCIe x8 OCP connector



which exposes PCIe lanes in a straight manner. In case the OCP slot exposes PCIe lanes in a reversed manner, MCX542B-ACAN supports automatic lane reversal with FW image from April 2019 release and above.

Airflow Requirements

ConnectX-5 adapter cards are offered with two airflow patterns: from the heatsink to the network ports, and vice versa, as shown below.

Please refer to the "Specifications" chapter for airflow numbers for each specific card model.

All cards in the system should be planned with the same airflow direction.



Software Requirements

•

See Operating Systems/Distributions section under the Introduction section.

•

Software Stacks - Mellanox OpenFabric software package MLNX_OFED for Linux, WinOF-2 for Windows, and VMware. See the Driver Installation section.

Unpacking the Product

The adapter is being installed in a system that operates with voltages that can be lethal.



Before opening the case of the system, observe the following precautions to avoid injury and prevent damage to system components.

•

Remove any metallic objects from your hands and wrists.

•

Make sure to use only insulated tools.

•

Verify that the system is powered off and is unplugged.

•

It is strongly recommended to use an ESD strap or other antistatic devices.

Unpack the adapter package and place them on an antistatic surface.

Check the parts for visible damage that may have occurred during shipping.

Page 18

Please note that if the card is removed hastily from the antistatic bag, the plastic



ziplock may harm the EMI fingers on the networking connector. Carefully remove the card from the antistatic bag to avoid damaging the EMI fingers.

Shut down your system if active:

Turn off the power to the system, and disconnect the power cord. Refer to the system documentation for instructions. Before you install the ConnectX-5 card, make sure that the system is disconnected from power.

Adapter Cards Installation Instructions

This section provides detailed instructions on how to install your adapter card in a system.

Please note that the following figures are for illustration purposes only.



Before installing the card, make sure that the system is off and the power cord is not connected to the server. Please follow proper electrical grounding procedures.

Open the system case.

Make sure the adapter clips or screws are open. Place the adapter card on the clips without applying any pressure.

Page 19

4.5.Applying even pressure on four corners of the card (as shown in the below picture), insert the adapter card into the PCI Express slot until firmly seated.

Secure the adapter with the adapter clip or screw.

To uninstall the adapter card, seeUninstalling the Card.

Cables and Modules

To obtain the list of supported Mellanox cables for your adapter, please refer to theCables Reference Tableathttp://www.mellanox.com/products/interconnect/cables-configurator.php.

Cable Installation

Page 20

All cables can be inserted or removed with the unit powered on.

To insert a cable, press the connector into the port receptacle until the connector is firmly seated.

Support the weight of the cable before connecting the cable to the adapter card. Do this by using a cable holder or tying the cable to the rack.

Determine the correct orientation of the connector to the card before inserting the connector. Do not try and insert the connector upside down. This may damage the adapter card.

Insert the connector into the adapter card. Be careful to insert the connector straight into the cage. Do not apply any torque, up or down, to the connector cage in the adapter card.

Make sure that the connector locks in place.

When installing cables make sure that the latches engage.



Always install and remove cables by pushing or pulling the cable and connector



in a straight line with the card.

After inserting a cable into a port, the Yellow or Green LED0 indicator will light when the physical connection is established (that is, when the unit is powered on and a cable is plugged

into the port with the other end of the connector plugged into a functioning port). SeeAdapter

Card LED Operations.

After plugging in a cable, lock the connector using the latching mechanism particular to the cable vendor. When a logical connection is made, Green LED1 will light. When data is being transferred, Green LED1 will blink.

Care should be taken as not to impede the air exhaust flow through the ventilation holes. Use cable lengths which allow for routing horizontally around to the side of the chassis before bending upward or downward in the rack.

To remove a cable, disengage the locks and slowly pull the connector away from the port receptacle. LED indicator will turn off when the cable is unseated.

Identifying the Card in Your System

On Linux

Get the device location on the PCI bus by running lspci and locating lines with the string“Mellanox Technologies”:

lspci |grep -i Mellanox Network controller: Mellanox Technologies MT28800 Family [ConnectX-5]

On Windows

Open Device Manager on the server. ClickStart=>Run, and then enterdevmgmt.msc.

ExpandSystem Devicesand locate your Mellanox ConnectX-5 adapter card.

Right click the mouse on your adapter's row and selectPropertiesto display the adapter card

properties window.

Click theDetailstab and selectHardware Ids(Windows 2012/R2/2016) from thePropertypull-

down menu.

Page 21

PCI Device (Example)



In theValuedisplay box, check the fields VEN and DEV (fields are separated by ‘&’). In the display example above, notice the sub-string “PCI\VEN_15B3&DEV_1003”: VEN is equal to 0x15B3 – this is the Vendor ID of Mellanox Technologies; and DEV is equal to 1018 (for ConnectX-5) – this is a valid Mellanox Technologies PCI Device ID.



If the PCI device does not have a Mellanox adapter ID, return to Step 2 to check another device.

The list of Mellanox Technologies PCI Device IDs can be found in the PCI ID repository at http://pci-ids.ucw.cz/read/PC/15b3.

Adapter Cards Extraction Instructions

Safety Precautions

The adapter is installed in a system that operates with voltages that can be lethal. Before uninstalling the adapter card, please observe the following precautions to avoid injury and prevent damage to system components.

Remove any metallic objects from your hands and wrists.

It is strongly recommended to use an ESD strap or other antistatic devices.

Turn off the system and disconnect the power cord from the server.

Page 22

Card Extraction

Please note that the following images are for illustration purposes only.



Verify that the system is powered off and unplugged.

Wait 30 seconds.

To remove the card, disengage clip 1 and 2 on connector A side.

To disconnect connector A, gently pull the adapter card upwards.

Disengage clip 3 and clip 4 on the adapter card on Connector B side.

Page 23

6. To remove the card, gently pull the adapter card upwards.

Page 24

Driver Installation

echo %PROCESSOR_ARCHITECTURE%

Please use the relevant driver installation section.

•

Windows Driver Installation

•

Linux Driver Installation

•

VMware Driver Installation

Windows Driver Installation

For Windows, download and install the latest Mellanox WinOF-2 for Windows software package

available via the Mellanox web site at:http://www.mellanox.com> Products > Software > Ethernet

Drivers > Download. Follow the installation instructions included in the download package (also available from the download page).

The snapshots in the following sections are presented for illustration purposes only. The



installation interface may slightly vary, depending on the operating system in use.

Software Requirements

Description Package

Windows Server 2012 R2 MLNX_WinOF2-2_10_All_x64.exe

Windows Server 2012

Windows Server 2016

Windows Server 2019

Windows 8.1 Client (64 bit only)

Windows 10 Client (64 bit only)

Note: The Operating System listed above must run with administrator privileges.

Downloading Mellanox WinOF-2 Driver

To download the executable file according to your operating system, please follow the steps below:

Obtain the machine architecture.

To go to theStartmenu, position your mouse in the bottom-right corner of the Remote

Desktop of your screen.

Open a CMD console. (ClickTask Manager>File>Runnew task, and enterCMD.)

Enter the following command.

On an x64 (64-bit) machine, the output will be “AMD64”.



Page 25

MLNX_WinOF2-[Driver/Version]_<revision_version>_All_Arch.exe /v"/l*vx [LogFile]"

MLNX_WinOF2-2_10_50000_All_x64.exe /v"/l*vx MyLog.txt=1"

Go to the Mellanox WinOF-2 web page athttp://www.mellanox.com> Products > Ethernet

Drivers > Windows SW/Drivers.

Download the exe image according to the architecture of your machine (see Step 1).The name of the .exe is in the following format:MLNX_WinOF2-<version>_x<arch>.exe.

Installing the incorrect exe file is prohibited. If you do so, an error message will be displayed.



For example, if you try to install a 64-bit executable file on a 32-bit machine, the wizard will display the following (or a similar) error message: “The installation package is not supported by this processor type. Contact your vendor.”

Installing Mellanox WinOF-2 Driver

The snapshots in the following sections are for illustration purposes only. The installation



interface may slightly vary, depending on the used operating system.

This section provides instructions for two types of installation procedures, and bothrequire

administrator privileges:

•

Attended Installation-An installation procedure that requires frequent user intervention.

•

Unattended Installation-An automated installation procedure that requires no user

intervention.

Both Attended and Unattended installations require administrator privileges.



Attended Installation

The following is an example of an installation session.

Double click the .exe and follow the GUI instructions to install MLNX_WinOF2.

[Optional]Manually configure your setup to contain the logs option (replace “LogFile” with the

relevant directory):

[Optional] If you do not want to upgrade your firmware version. (Note:MT_SKIPFWUPGRD

default value is False.)

Page 26

Click Next in the Welcome screen.

Read and accept the license agreement and click Next.

Select the target folder for the installation.

Page 27

The firmware upgrade screen will be displayed in the following cases:

•

If the user has an OEM card. In this case, the firmware will not be displayed.

•

If the user has a standard Mellanox card with an older firmware version, the firmware will be updated accordingly. However, if the user has both an OEM card and a Mellanox card, only the Mellanox card will be updated.

Page 28

Select a Complete or Custom installation, followStepaonward.

Select the desired feature to install:

•

Performances tools - install the performance tools that are used to measure

performance inuserenvironment

•

Documentation - contains the User Manual and Release Notes

•

Management tools - installation tools used for management, such asmlxstat

•

Diagnostic Tools - installation tools used for diagnostics, such as mlx5cmd

Click Next to install the desired tools.

Page 29

9. Click Install to start the installation.

   

10. In case firmware upgrade option was checked inStep 7, you will be notified if a firmware upgrade is required (see ).

   

11. Click Finish to complete the installation.

Page 30

    1

MLNX_WinOF2-[Driver/Version]_<revision_version>_All_Arch.exe /S /v/qn

_All_Arch.exe /S /v/qn /v”/l*vx [Log- File]"" v:shapes="_x0000_s1026">

MLNX_WinOF2-[Driver/Version]_<revision_version>_All_Arch.exe /vMT_NDPROPERTY=1

MLNX_WinOF2-[Driver/Version]_<revision_version>_All_Arch.exe /vMT_SKIPFWUPGRD=1

Unattended Installation

If no reboot options are specified, the installer restarts the computer whenever necessary



without displaying any prompt or warning to the user. To control the reboots, use the

The following is an example of an unattended installation session.

Open a CMD console->Click Start->Task Manager File->Run new task->and enter CMD.

Install the driver. Run:

[Optional]Manually configure your setup to contain the logs option:

[Optional]if you wish to control whether to install ND provider or not (i.e.,

default value is True

/norestart

/forcerestart

standard command-line options.

MT_NDPROPERTY

[Optional]If you do not wish to upgrade your firmware version (i.e.,

value is False

MT_SKIPFWUPGRDdefault

Page 31

Installation Results

Upon installation completion, you can verify the successful addition of the network card(s) through the

Device Manager. Theinffiles can be located at:

%ProgramFiles%\Mellanox\MLNX_WinOF2\Drivers\

To see the Mellanox network adapters, display the Device Manager and pull down the “Network adapters” menu.

Uninstalling Mellanox WinOF-2 Driver

Attended Uninstallation

To uninstall MLNX_WinOF2 on a single node:

ClickStart>Control Panel>Programs and Features>MLNX_WinOF2>Uninstall. (NOTE: This requires elevated administrator privileges)

Unattended Uninstallation

To uninstall MLNX_WinOF2 in unattended mode:

Page 32

MLNX_WinOF2-2_0_All_x64.exe /S /x /v"/qn"

Open a CMD console.(ClickTask Manager>File>Runnew task, and enterCMD.)

To uninstall the driver, run:

Extracting Files Without Running Installation

To extract the files without running installation, perform the following steps:

Open a CMD console->Click Start->Task Manager->File->Run new task->and enter CMD.

Extract the driver and the tools:

MLNX_WinOF2-2_0_<revision_version>_All_x64 /a

To extract only the driver file

MLNX_WinOF2-2_0_<revision_version>_All_x64 /a /vMT_DRIVERS_ONLY=1

Click Next to create a server image.



Click Change and specify the location in which the files are extracted to.

Page 33

   

Click Install to extract this folder, or click Change to install to a different folder.

Page 34

To complete the extraction, click Finish.

Firmware Upgrade

If the machine has a standard Mellanox card with an older firmware version, the firmware will be automatically updated as part of the WinOF-2 package installation.

For information on how to upgrade firmware manually, please refer to the MFT User Manual atwww.m

ellanox.com>Products > Ethernet Drivers > Firmware Tools.

Linux Driver Installation

This section describes how to install and test the Mellanox OFED for Linux package on a single server with a Mellanox ConnectX-5 adapter card installed.

Prerequisites

Requirements Description

Platforms A server platform with a oneof the following Mellanox

adapters installed:

•

ConnectX®-5 Ex (EN) (firmware: fw-ConnectX5)

•

ConnectX®-5 (EN) (firmware: fw-ConnectX5)

Required Disk Space for Installation 1GB

Page 35

Requirements Description

# lspci -v | grep Mellanox 86:00.0 Network controller [0207]: Mellanox Technologies MT27620 Family Subsystem: Mellanox Technologies Device 0014 86:00.1 Network controller [0207]: Mellanox Technologies MT27620 Family Subsystem: Mellanox Technologies Device 0014

md5sum MLNX_OFED_LINUX-<ver>-<OS label>.iso

Device ID For the latest list of device IDs, please visit the Mellanox

website athttp://www.mellanox.com/page/

firmware_HCA_FW_identification.

Operating System Linux operating system.

For the list of supported operating system distributions and kernels, please refer to the file.

InstallerPrivileges The installation requires administrator (root) privileges on

the target machine.

Mellanox OFED Release Notes

Downloading Mellanox OFED

Verify that the system has a Mellanox network adapter installed. The following example shows a system with an installed Mellanox adapter card:

Download the ISO image to your host.

The image’s name has the formatMLNX_OFED_LINUX-<ver>-<OS label><CPU arch>.iso.

You can download and install the latest OpenFabrics Enterprise Distribution (OFED) software

package available via the Mellanox web site athttp://www.mellanox.com> Products > Software

> Ethernet Drivers > Linux SW/Drivers > Download..

Scroll down to the Download wizard, and click the Download tab.

Choose your relevant package depending on your host operating system.

Click the desired ISO/tgz package.

To obtain the download link, accept the End User License Agreement (EULA).

Use the md5sum utility to confirm the file integrity of your ISO image. Run the following command and compare the result to the value provided on the download page.

Installing Mellanox OFED

Installation Script

The installation script,mlnxofedinstall, performs the following:

•

Discovers the currently installed kernel

•

Uninstalls any software stacks that are part of the standard operating system distributionor

another vendor's commercial stack

•

Installs the MLNX_OFED_LINUX binary RPMs (if they are available for the currentkernel)

•

Identifies the currently installed InfiniBand and Ethernet network adapters and automatically upgrades the firmware.

Note:The firmware will not be updated if you run the install script with the ‘--without-fwupdate’ option. Note: If you wish to perform a firmware upgrade using customized FW binaries, you canprovide

Page 36

a path to the folder that contains the FW binary files, by running--fw-image-dir. Using this

./mlnxofedinstall --fw-image-dir /tmp/my_fw_bin_files

./mnt/mlnxofedinstall [OPTIONS]

# ./MLNX_OFED_LINUX-x.x-x-rhel6.3-x86_64/mlnx_add_kernel_support.sh -m /tmp/MLNX_OFED_LINUX-x.x-x-rhel6.3x86_64/ --make-tgz Note: This program will create MLNX_OFED_LINUX TGZ for rhel6.3 under /tmp directory. All Mellanox, OEM, OFED, or Distribution IB packages will be removed. Do you want to continue?[y/N]:y See log file /tmp/mlnx_ofed_iso.21642.log

Building OFED RPMs. Please wait... Removing OFED RPMs... Created /tmp/MLNX_OFED_LINUX-x.x-x-rhel6.3-x86_64-ext.tgz

option, the FW version embedded in the MLNX_OFED package will beignored.Example:

Usage

Pre-existing configuration files will be saved with the extension “.conf.rpmsave”.



The installation script removes all previously installed Mellanox OFED packages and re-installs from scratch. You will be prompted to acknowledge the deletion of the old packages.

•

If you need to install Mellanox OFED on an entire (homogeneous) cluster, a commonstrategy is to mount the ISO image on one of the cluster nodes and then copy it to ashared file system such as NFS. To install on all the cluster nodes, use cluster-awaretools (such as pdsh).

•

If your kernel version does not match with any of the offered pre-built RPMs, you canadd your kernel version by using the “mlnx_add_kernel_support.sh” script locatedinside the

MLNX_OFED package.

On Redhat and SLES distributions with errata kernel installed there is no need to use



the mlnx_add_kernel_support.sh script. The regular installation can be performed and weak updates mechanism will create symbolic links to the MLNX_OFED kernel modules.

The “mlnx_add_kernel_support.sh” script can be executed directly from the mlnxofedinstall

script. For further information, please see '--add-kernel-support' option below.

On Ubuntu and Debian distributions drivers installation use Dynamic Kernel Module



Support (DKMS) framework. Thus, the drivers' compilation will take place on the host during MLNX_OFED installation. Therefore, using "mlnx_add_kernel_support.sh" is irrelevant on Ubuntu and Debian distributions.

Example

The following command will create a MLNX_OFED_LINUX ISO image for RedHat 6.3 under the / tmp directory.

•

The script adds the following lines to /etc/security/limits.conf for the userspace components such as MPI:

•

* soft memlock unlimited

•

* hard memlock unlimited

•

These settings set the amount of memory that can be pinned by a userspace application to unlimited. If desired, tune the value unlimited to a specific amount of RAM.

Page 37

For your machine to be part of the InfiniBand/VPI fabric, a Subnet Manager must be running on one of

./mlnxofedinstall --h

# mount -o ro,loop MLNX_OFED_LINUX-<ver>-<OS label>-<CPU arch>.iso /mnt

/mnt/mlnxofedinstall Logs dir: /tmp/MLNX_OFED_LINUX-x.x-x.logs This program will install the MLNX_OFED_LINUX package on your machine. Note that all other Mellanox, OEM, OFED, RDMA or Distribution IB packages will be removed. Those packages are removed due to conflicts with MLNX_OFED_LINUX, do not reinstall them. Starting MLNX_OFED_LINUX-x.x.x installation ...

........

Installation finished successfully.

Attempting to perform Firmware update... Querying Mellanox devices firmware ...

the fabric nodes. At this point, Mellanox OFED for Linux has already installed the OpenSM Subnet Manager on your machine. For the list of installation options, run:

The DKMS (on Debian based OS) and the weak-modules (RedHat OS) mechanisms rebuild the



initrd/initramfs for the respective kernel in order to add the MLNX_OFED drivers. When installing MLNX_OFED without DKMS support on Debian based OS, or without KMP support on RedHat or any other distribution, the initramfs will not be changed. Therefore, the inbox drivers may be loaded on boot. In this case, openibd service script will automatically unload them and load the new drivers that come with MLNX_OFED.

Installation Procedure

Mount the ISO image on your machine.

Run the installation script.

For unattended installation, use the --force installation option while running the



MLNX_OFED installation script:

/mnt/mlnxofedinstall --force

MLNX_OFED for Ubuntu should be installed with the following flags in the root



environment:

./mlnxofedinstall --without-dkms --add-kernel-support --kernel <kernel version in chroot> --without-fw-update --force

For example:

./mlnxofedinstall --without-dkms --add-kernel-support --kernel

3.13.0-85-generic --without-fw-update --force

Note that the path to kernel sources (--kernel-sources) should be added if the sources are not in their default location.

Page 38

In case your machine has the latest firmware, no firmware update will occur and the



installation script will print at the end of installation a message similar to the following:

Device #1:

---------Device Type: ConnectX-5 Ex Part Number: MCX546A-CDAN

Description: ConnectX®-5 Ex network interface card for OCP, 100GbE dual-port QSFP28, PCIe4.0 x16, no bracket, ROHS R6

PSID: MT_2190110032

PCI Device Name: 0b:00.0 Base MAC: 0000e41d2d5cf810 Versions: Current Available FW 16.22.0228 16.22.0228 Status: Up to date

In case your machine has an unsupported network adapter device, no firmware update



will occur and one of the following error messages below will be printed. Please contact your hardware vendor for help on firmware updates. Error message 1:

Device #1:

----------

Device Type: ConnectX-5 Ex Part Number: MCX546A-CDAN

Description: ConnectX®-5 Ex network interface card for OCP, 100GbE dual-port QSFP28, PCIe4.0 x16, no bracket, ROHS R6

PSID: MT_2190110032 PCI Device Name: 0b:00.0 Base MAC: 0000e41d2d5cf810 Versions: Current Available FW 16.22.0228 N/A Status: No matching image found

Error message 2:

The firmware for this device is not distributed inside Mellanox driver: 0000:01:00.0 (PSID: IBM2150110033) To obtain firmware for this device, please contact your HW vendor.

4. If the installation script has performed a firmware update on your network adapter,

completethe step relevant to your adapter card type to load the firmware:  •ConnectX-5/ConnectX-5 Ex - perform a standard reboot Otherwise, restart the driver by running:/etc/init.d/openibd restart

After installation completion, information about the Mellanox OFED installation, such as prefix, kernel version, and installation parameters can be retrieved by running the command /etc/infiniband/info.

Most of the Mellanox OFED components can be configured or reconfigured after the installation, by modifying the relevant configuration files. See the relevant chapters in this manual for details.

The list of the modules that will be loaded automatically upon boot can be found in the /etc/infiniband/ openib.conf file.

Page 39

Installation Results

Logs dir: /tmp/MLNX_OFED_LINUX-4.4-1.0.0.0.63414.logs

OPENIBD_PRE_START OPENIBD_POST_START OPENIBD_PRE_STOP OPENIBD_POST_STOP

OPENIBD_POST_START=/sbin/openibd_post_start.sh

Software Most of MLNX_OFED packages are installed under the “/usr” directory

Firmware The firmware of existing network adapter devices will be updated if the

• except for the following packages which are installed under the “/opt” directory:

•

fca and ibutils

•

The kernel modules are installed under

•

/lib/modules/`uname -r`/updates on SLES and Fedora Distributions

•

/lib/modules/`uname -r`/extra/mlnx-ofa_kernel on RHEL and other Red Hat like Distributions

• following two conditions are fulfilled:

•

The installation script is run in default mode; that is, without the option ‘--without-fw-update’

•

The firmware version of the adapter device is older than the firmware version included with the Mellanox OFED ISO image Note: If an adapter’s flash was originally programmed with an Expansion ROM image, the automatic firmware update will also burn an Expansion ROM image.

•

In case that your machine has an unsupported network adapter device, no firmware update will occur and the error message below will be printed.

The firmware for this device is not distributed inside Mellanox driver: 0000:01:00.0 (PSID: IBM2150110033) To obtain firmware for this device, please contact your HW vendor.

Installation Logs

While installing MLNX_OFED, the install log for each selected package will be saved in a separate log

file.The path to the directory containing the log files will be displayed after running the installation

script in the following format: "Logs dir: /tmp/MLNX_OFED_LINUX-<version>.<PD>.logs".

Example:

openibd Script

As of MLNX_OFED v2.2-1.0.0 the openibd script supports pre/post start/stop scripts: This can be controlled by setting the variables below in the /etc/infiniband/openibd.conf file.

Example:

Page 40

blacklist mlx4_core blacklist mlx4_en blacklist mlx5_core blacklist mlx5_ib

An example of OPENIBD_POST_START script for activating all interfaces is provided in the



MLNX_OFED package under the docs/scripts/openibd-post-start-configure-interfaces/ folder.

Driver Load Upon System Boot

Upon system boot, the Mellanox drivers will be loaded automatically.

To prevent the automatic load of the Mellanox drivers upon system boot:

Add the following lines to the "/etc/modprobe.d/mlnx.conf" file.

Set “ONBOOT=no” in the "/etc/infiniband/openib.conf" file.

If the modules exist in the initramfs file, they can automatically be loaded by the kernel.

To prevent this behavior, update the initramfs using the operating systems’ standard tools.

Note: The process of updating the initramfs will add the blacklists from step 1, and will prevent the kernel from loading the modules automatically.

mlnxofedinstall Return Codes

The table below lists the mlnxofedinstall script return codes and their meanings.

Return Code Meaning

0 The installation ended successfully

1 The installation failed

2 No firmware was found for the adapter device

22 Invalid parameter

28 Not enough free space

171 Not applicable to this system configuration. This can occur when the

required hardware is not present on the system.

172 Prerequisites are not met. For example, missing the required software

installed or the hardware is not configured correctly.

173 Failed to start the mst driver

Uninstalling MLNX_OFED

Use the script /usr/sbin/ofed_uninstall.sh to uninstall the Mellanox OFED package. The script is part of the ofed-scripts RPM.

Installing MLNX_OFED Using YUM

This type of installation is applicable to RedHat/OL, Fedora, XenServer Operating Systems.

Page 41

Setting up MLNX_OFED YUM Repository

# mount -o ro,loop MLNX_OFED_LINUX-<ver>-<OS label>-<CPU arch>.iso /mnt

# wget http://www.mellanox.com/downloads/ofed/RPM-GPG-KEY-Mellanox

--2014-04-20 13:52:30-- http://www.mellanox.com/downloads/ofed/RPM-GPG-KEY-Mellanox Resolving www.mellanox.com... 72.3.194.0 Connecting to www.mellanox.com|72.3.194.0|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1354 (1.3K) [text/plain] Saving to: ?RPM-GPG-KEY-Mellanox?

100%[=================================================>] 1,354 --.-K/s in 0s

2014-04-20 13:52:30 (247 MB/s) - ?RPM-GPG-KEY-Mellanox? saved [1354/1354]

# sudo rpm --import RPM-GPG-KEY-Mellanox warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 6224c050: NOKEY Retrieving key from file:///repos/MLNX_OFED/<MLNX_OFED file>/RPM-GPG-KEY-Mellanox Importing GPG key 0x6224C050: Userid: "Mellanox Technologies (Mellanox Technologies - Signing Key v2) <support@mellanox.com>" From : /repos/MLNX_OFED/<MLNX_OFED file>/RPM-GPG-KEY-Mellanox Is this ok [y/N]:

# rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n' | grep Mellanox gpg-pubkey-a9e4b643-520791ba gpg(Mellanox Technologies <support@mellanox.com>)

[mlnx_ofed] name=MLNX_OFED Repository baseurl=file:///<path to extracted MLNX_OFED package>/RPMS enabled=1 gpgkey=file:///<path to the downloaded key RPM-GPG-KEY-Mellanox> gpgcheck=1

# yum repolist Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. repo id repo name status mlnx_ofed MLNX_OFED Repository 108 rpmforge RHEL 6Server - RPMforge.net - dag 4,597

repolist: 8,351

Log into the installation machine as root.

Mount the ISO image on your machine and copy its content to a shared location in your network.

Download and install Mellanox Technologies GPG-KEY:

The key can be downloaded via the following link:http://www.mellanox.com/downloads/ofed/

RPM-GPG-KEY-Mellanox

Install the key.

Check that the key was successfully imported.

Create a yum repository configuration file called "/etc/yum.repos.d/mlnx_ofed.repo"with the

following content:

Check that the repository was successfully added.

Installing MLNX_OFED Using the YUM Tool

After setting up the YUM repository for MLNX_OFED package, perform the following:

View the available package groups by invoking:

Page 42

# yum search mlnx-ofedmlnx-ofed-all.noarch : MLNX_OFED all installer package (with KMP support) mlnx-ofed-basic.noarch : MLNX_OFED basic installer package (with KMP support) mlnx-ofed-guest.noarch : MLNX_OFED guest installer package (with KMP support) mlnx-ofed-hpc.noarch : MLNX_OFED hpc installer package (with KMP support) mlnx-ofed-hypervisor.noarch : MLNX_OFED hypervisor installer package (with KMP support) mlnx-ofed-vma.noarch : MLNX_OFED vma installer package (with KMP support) mlnx-ofed-vma-eth.noarch : MLNX_OFED vma-eth installer package (with KMP support) mlnx-ofed-vma-vpi.noarch : MLNX_OFED vma-vpi installer package (with KMP support)

Where:

mlnx-ofed-all Installs all available packages in MLNX_OFED. mlnx-ofed-basic Installs basic packages required for running Mellanox cards. mlnx-ofed-guest Installs packages required by guest OS. mlnx-ofed-hpc Installs packages required for HPC. mlnx-ofed-hypervisor Installs packages required by hypervisor OS. mlnx-ofed-vma Installs packages required by VMA. mlnx-ofed-vma-eth Installs packages required by VMA to work over Ethernet. mlnx-ofed-vma-vpi Installs packages required by VMA to support VPI.

mlnx-ofed-all-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED all installer package for kernel 3.17.4-301.fc21.x8 6_64 (without KMP support) mlnx-ofed-basic-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED basic installer package for kernel 3.17.4-301.fc2

1.x86_64 (without KMP support) mlnx-ofed-guest-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED guest installer package for kernel 3.17.4-301.fc2

1.x86_64 (without KMP support) mlnx-ofed-hpc-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED hpc installer package for kernel 3.17.4-301.fc21.x8 6_64 (without KMP support) mlnx-ofed-hypervisor-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED hypervisor installer package for kernel 3.17.

4-301.fc21.x86_64 (without KMP support)

mlnx-ofed-vma-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED vma installer package for kernel 3.17.4-301.fc21.x8 6_64 (without KMP support) mlnx-ofed-vma-eth-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED vma-eth installer package for kernel 3.17.4-301. fc21.x86_64 (without KMP support) mlnx-ofed-vma-vpi-3.17.4-301.fc21.x86_64.noarch : MLNX_OFED vma-vpi installer package for kernel 3.17.4-301. fc21.x86_64 (without KMP support)

# yum install mlnx-ofed-all Loaded plugins: langpacks, product-id, subscription-manager Resolving Dependencies

--> Running transaction check

---> Package mlnx-ofed-all.noarch 0:3.1-0.1.2 will be installed

--> Processing Dependency: kmod-isert = 1.0-OFED.3.1.0.1.2.1.g832a737.rhel7u1 for package: mlnx-ofed-all-3.1-0.1.2.noarch

..................

qperf.x86_64 0:0.4.9-9 rds-devel.x86_64 0:2.0.7-1.12 rds-tools.x86_64 0:2.0.7-1.12 sdpnetstat.x86_64 0:1.60-26 srptools.x86_64 0:1.0.2-12

Complete!

Note: MLNX_OFED provides kernel module RPM packages with KMP support for RHEL and SLES. For other operating systems, kernel module RPM packages are provided only for the operating systems' default kernel. In this case, the group RPM packages have the supported kernel version in their package's name.

Example:

If you have an operating system different than RHEL or SLES, or you have installed a kernel that is not supported by default in MLNX_OFED, you can use the mlnx_add_kernel_support.sh script to build MLNX_OFED for your kernel. The script will automatically build the matching group RPM packages for your kernel so that you can still install MLNX_OFED via yum. Please note that the resulting MLNX_OFED repository will contain unsigned RPMs, therefore, you should set 'gpgcheck=0' in the repository configuration file.

Install the desired group.

Page 43

Uninstalling MLNX_OFED Using the YUM Tool

# deb file:/<path to extracted MLNX_OFED package>/DEBS ./

# wget -qO - http://www.mellanox.com/downloads/ofed/RPM-GPG-KEY-Mellanox | sudo apt-key add -

# apt-key list pub 1024D/A9E4B643 2013-08-11 uid Mellanox Technologies <support@mellanox.com> sub 1024g/09FCC269 2013-08-11

# sudo apt-get update

<pre># apt-cache search mlnx-ofedmlnx-ofed-vma-eth - MLNX_OFED vma-eth installer package (with DKMS support) mlnx-ofed-hpc - MLNX_OFED hpc installer package (with DKMS support) mlnx-ofed-vma-vpi - MLNX_OFED vma-vpi installer package (with DKMS support) mlnx-ofed-basic - MLNX_OFED basic installer package (with DKMS support) mlnx-ofed-vma - MLNX_OFED vma installer package (with DKMS support) mlnx-ofed-all - MLNX_OFED all installer package (with DKMS support)

mlnx-ofed-all MLNX_OFED all installer package. mlnx-ofed-basic MLNX_OFED basic installer package. mlnx-ofed-vma MLNX_OFED vma installer package. mlnx-ofed-hpc MLNX_OFED HPC installer package. mlnx-ofed-vma-eth MLNX_OFED vma-eth installer package. mlnx-ofed-vma-vpi MLNX_OFED vma-vpi installer package.

Use the script /usr/sbin/ofed_uninstall.sh to uninstall the Mellanox OFED package. The script is part of the ofed-scripts RPM.

Installing MLNX_OFED Using apt-get Tool

This type of installation is applicable to Debian and Ubuntu operating systems.

Setting up MLNX_OFED apt-get Repository

Log into the installation machine as root.

Extract the MLNX_OFED pacakge on a shared location in your network.

You can download it fromhttp://www.mellanox.com> Products > Software> Ethernet Drivers.

Create an apt-get repository configuration file called"/etc/apt/sources.list.d/mlnx_ofed.list"

with the following content:

Download and install Mellanox Technologies GPG-KEY.

Check that the key was successfully imported.

Update the apt-get cache.

Installing MLNX_OFED Using the apt-get Tool

After setting up the apt-get repository for MLNX_OFED package, perform the following:

View the available package groups by invoking:

Where:

Page 44

2. Install the desired group.

# apt-get install '<group name>'

# apt-get install mlnx-ofed-all

mlxfwmanager --online -u -d <device>

mlxfwmanager --online -u -d 0000:09:00.0 Querying Mellanox devices firmware ... Device #1:

---------Device Type: ConnectX-5 Ex Part Number: MCX546A-CDAN Description: ConnectX®-5 Ex network interface card for OCP, 100GbE dual-port QSFP28, PCIe4.0 x16, no bracket, ROHS R6 PSID: MT_1020120019 PCI Device Name: 0000:09:00.0 Port1 GUID: 0002c9000100d051 Port2 MAC: 0002c9000002 Versions: Current Available FW 2.32.5000 2.33.5000 Status: Update required

--------Found 1 device(s) requiring firmware update. Please use -u flag to perform the update.

Example:

Installing MLNX_OFED using the “apt-get” tool does not automatically update the



firmware. To update the firmware to the version included in MLNX_OFED package, run:

# apt-get install mlnx-fw-updater

Or, update the firmware to the latest version available on Mellanox Technologies’ Web

site as described in Updating Adapter Firmware.

Uninstalling MLNX_OFED Using the apt-get Tool

Use the script /usr/sbin/ofed_uninstall.sh to uninstall the Mellanox OFED package. The script is part of the ofed-scripts package.

Updating Firmware After Installation

The firmware can be updated either manually or automatically (upon system boot), as described in the sections below.

Updating the Device Online

To update the device online on the machine from the Mellanox site, use the following command line:

Example:

Updating the Device Manually

To update the device manually, please refer to theOEM Firmware Download pageathttp://

www.mellanox.com/page/firmware_table_dell?mtag=oem_firmware_download.

Page 45

In case that you ran the mlnxofedinstall script with the ‘--without-fw-update’ option or you are using an

mlxfwmanager_pci | grep PSID PSID: MT_1210110019

mlxfwmanager_pci -i <fw_file.bin>

fw_updater: Firmware was updated. Please reboot your system for the changes to take effect.

fw_updater: Didn't detect new devices with old firmware.

MLNX_EXCLUDE_DEVICES="00:05.0,00:07.0"

OEM card and now you wish to (manually) update firmware on your adapter card(s), you need to perform the steps below. The following steps are also appropriate in case that you wish to burn newer

firmware that you have downloaded from Mellanox Technologies’ Web site (http://www.mellanox.com>

Support > Firmware Download).

Get the device’s PSID.

Download the firmware BIN file from the Mellanox website or the OEM website.

Burn the firmware.

Reboot your machine after the firmware burning is completed.

Updating the Device Firmware Automatically upon System Boot

As of MLNX_OFED v3.1-x.x.x, firmware can be automatically updated upon system boot.The firmware update package (mlnx-fw-updater) is installed in the “/opt/mellanox/mlnx-fw-updater” folder, and

openibd service script can invoke the firmware update process if requested on boot.

If the firmware is updated, the following message is printed to the system’s standard logging file:

Otherwise, the following message is printed:

Please note, this feature is disabled by default. To enable the automatic firmware update upon system

boot, set the following parameter to “yes” “RUN_FW_UPDATER_ONBOOT=yes” in the openibd service configuration file “/etc/infiniband/openib.conf”.

You can opt to exclude a list of devices from the automatic firmware update procedure. To do so, edit

the configurations file “/opt/mellanox/mlnx-fw-updater/mlnx-fw-updater.conf” and provide a comma

separated list of PCI devices to exclude from the firmware update. Example:

UEFI Secure Boot

All kernel modules included in MLNX_OFED for RHEL7 and SLES12 are signed with x.509 key to support loading the modules when Secure Boot is enabled.

Enrolling Mellanox's x.509 Public Key on Your Systems

In order to support loading MLNX_OFED drivers when an OS supporting Secure Boot boots on a UEFIbased system with Secure Boot enabled, the Mellanox x.509 public key should be added to the UEFI

Page 46

Secure Boot key database and loaded onto the system key ring by the kernel.

# wget http://www.mellanox.com/downloads/ofed/mlnx_signing_key_pub.der

# mokutil --import mlnx_signing_key_pub.der

"Request for unknown module key 'Mellanox Technologies signing key: 61feb074fc7292f958419386ffdd9d5ca999e403' err -11"

"my_module: module verification failed: signature and/or required key missing - tainting kernel"

Follow these steps below to add the Mellanox's x.509 public key to your system:

Prior to adding the Mellanox's x.509 public key to your system, please make sure that (1) The



'mokutil' package is installed on your system, and (2) The system is booted in UEFI mode.

Download the x.509 public key.

Add the public key to the MOK list using the mokutil utility.

Reboot the system.

The pending MOK key enrollment request will be noticed by shim.efi and it will launch MokManager.efi to allow you to complete the enrollment from the UEFI console. You will need to enter the password you previously associated with this request and confirm the enrollment. Once done, the public key is added to the MOK list, which is persistent. Once a key is in the MOK list, it will be automatically propagated to the system key ring and subsequent will be booted when the UEFI Secure Boot is enabled.

To see what keys have been added to the system key ring on the current boot, install the



'keyutils' package and run: #keyctl list %:.system_keyring#

Removing Signature from kernel Modules

The signature can be removed from a signed kernel module using the 'strip' utility which is provided by

the 'binutils' package.The strip utility will change the given file without saving a backup. The operation

can be undo only by resigning the kernel module. Hence, we recommend backing up a copy prior to removing the signature.

To remove the signature from the MLNX_OFED kernel modules:

Remove the signature.

After the signature has been removed, a message as the below will no longer be presented upon module loading:

However, please note that a similar message as the following will still be presented:

This message is only presented once, upon first module boot that either has no signature or whose key is not in the kernel key ring. Therefore, this message may go unnoticed. Once the system is rebooted after unloading and reloading a kernel module, the message will appear.

(Note that this message cannot be eliminated.)

Page 47

mkinitrd /boot/initramfs-$(uname -r).img $(uname -r) --force

#> esxcli software vib install –d <path>/<bundle_file>

#> esxcli software vib install -d /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.16.8.8-10EM-650.0.0.4240417.zip

Update the initramfs on RHEL systems with the stripped modules.

Performance Tuning

Depending on the application of the user's system, it may be necessary to modify the default configuration of network adapters based on the ConnectX® adapters. In case that tuning is required,

please refer to thePerformance Tuning Guide for Mellanox Network Adaptersathttps://

community.mellanox.com/docs/DOC-2489.

VMware Driver Installation

This section describes VMware Driver Installation.

Hardware and Software Requirements

Requirement Description

Platforms A server platform with an adapter card based on one of the

following Mellanox Technologies’ devices:

•

ConnectX®-5 (EN) (firmware: fw-ConnectX5)

•

ConnectX®-5 Ex (EN) (firmware: fw-ConnectX5)

Device ID For the latest list of device IDs, please visit Mellanox's website.

Operating System ESXi 6.5

Installer Privileges The installation requires administrator privileges on the target

machine.

Installing Mellanox NATIVE ESXi Driver for VMware vSphere

Please uninstall all previous Mellanox driver packages prior to installing the new version. See



Removing Earlier Mellanox Drivers for further information.

To install the driver:

Log into the ESXi server with root permissions.

Install the driver.

Example:

Reboot the machine.

Page 48

esxcli software vib list | grep nmlx nmlx5-core 4.16.8.8-1OEM.650.0.0.4240417 MEL PartnerSupported 2017-01-31 nmlx5-rdma 4.16.8.8-1OEM.650.0.0.4240417 MEL PartnerSupported 2017-01-31

#> esxcli software vib remove -n nmlx5-rdma #> esxcli software vib remove -n nmlx5-core

Verify the driver was installed successfully.

After the installation process, all kernel modules are loaded automatically upon boot.



Removing Earlier Mellanox Drivers

Please unload the previously installed drivers before removing them.



To remove all the drivers:

Log into the ESXi server with root permissions.

List all the existing NATIVE ESXi driver modules. (See Step 4 inInstalling Mellanox NATIVE ESXi

Driver for VMware vSphere.)

Remove each module:

To remove the modules, you must run the command in the same order as shown in the



example above.

Reboot the server.

Firmware Programming

Download the VMware bootable binary images v4.6.0 from theMellanox Firmware Tools (MFT)

site.

ESXi 6.5 File: mft-4.6.0.48-10EM-650.0.0.4598673.x86_64.vib

MD5SUM: 0804cffe30913a7b4017445a0f0adbe1

Install the image according to the steps described in theMFT User Manual.

The following procedure requires custom boot image downloading, mounting and



booting from a USB device.

Page 49

Updating Adapter Firmware

[server1]# ./mlxup Querying Mellanox devices firmware ... Device Type: ConnectX-5 Part Number: MCX546A-CDAN Description: ConnectX®-5 Ex network interface card for OCP, with host management, 100GbE dual-port QSFP28, PCIe4.0 x16, no bracket PSID: MT_2190110032 PCI Device Name: 0000:06:00.0 Base GUID: e41d2d0300fd8b8a Versions: Current Available FW 16.00.0000 16.00.0000

Status: Up to date

Device Type: ConnectX-5 Part Number: MCX546A-CDAN Description: ConnectX®-5 Ex network interface card for OCP, with host management, 100GbE dual-port QSFP28, PCIe4.0 x16, no bracket PSID: MT_2170110021 PCI Device Name: 0000:07:00.0 Base MAC: 0000e41d2da206d4 Versions: Current Available FW 16.20.1000 16.24.1000

Status: Update required

Perform FW update? [y/N]: y Device #1: Up to date Device #2: Updating FW ... Done

Restart needed for updates to take effect. Log File: /var/log/mlxup/mlxup-yyyymmdd.log

Each adapter card is shipped with the latest version of qualified firmware at the time of manufacturing. However, Mellanox issues firmware updates occasionally that provide new features and bug fixes. To check that your card is programmed with the latest available firmware version, download the mlxup firmware update and query utility. The utility can query for available Mellanox adapters and indicate which adapters require a firmware update. If the user confirms, mlxup upgrades the firmware using

embedded images. The latest mlxup executable and documentation are available fromhttp://

www.mellanox.com> Products > Software > Firmware Tools.

Firmware Update Example

Page 50

Troubleshooting

GeneralTroubleshooting

Server unable to find theadapter Ensure that the adapter is placed correctly

The adapter no longer works Reseat the adapter in its slot or a different slot, if

Adapters stopped working afterinstalling another adapter

Link indicator light is off Try another port on the switch

Link light is on, but with nocommunication established

•

Make sure the adapter slot and the adapter are compatible Install the adapter in a different PCI Express slot

•

Use the drivers that came with the adapter or download the latest

•

Make sure your motherboard has the latest BIOS

•

Try to reboot the server

• necessary

•

Try using another cable

•

Reinstall the drivers for the network driver files may be damaged or deleted

•

Reboot the server

•

Try removing and re-installing all adapters

•

Check that cables are connected properly

•

Make sure your motherboard has the latest BIOS

•

Make sure the cable is securely attached

•

Check you are using the proper cables that do not exceed the recommended lengths

•

Verify that your switch and adapter port are compatible

•

Check that the latest driver is loaded

•

Check that both the adapter and its link are set to the same speed and duplex settings

LinuxTroubleshooting

Environment Information cat /etc/issue

uname -a cat /proc/cupinfo | grep ‘model name’ | uniq ofed_info -s ifconfig -a ip link show ethtool <interface> ethtool -i <interface_of_Mellanox_port_num> ibdev2netdev

Card Detection lspci | grep -i Mellanox

Page 51

Mellanox Firmware Tool (MFT) Download and install MFT:http://www.mellanox.com/

content/pages.php?pg=management_tools&menu_section=34

Refer to the User Manual for installation instructions. Once installed, run: mst start mst status flint -d <mst_device> q

Ports Information ibstat

ibv_devinfo

Firmware Version Upgrade To download the latest firmware version refer tohttp://

www.mellanox.com/supportdownloader

Collect Log File cat /var/log/messages

dmesg >> system.log journalctl (Applicable on new operating systems) cat /var/log/syslog

WindowsTroubleshooting

Environment Information From the Windows desktop choose the Start menu and run:

msinfo32

To export system information to a text file, choose the Export option from the File menu. Assign a file name and save.

Mellanox Firmware Tool (MFT) Download and install MFT:http://www.mellanox.com/content/

pages.php?pg=management_tools&menu_section=34

Refer to the User Manual for installation instructions. Once installed, open a CMD window and run: WinMFT mst start mst status flint –d <mst_device> q

Ports Information vstat

Firmware Version Upgrade Download the latest firmware version using the PSID/board

ID:http://www.mellanox.com/supportdownloader/ flint –d <mst_device> –i <firmware_bin_file> b

Collect Log File Event log viewer

•

MST device logs:

•

mst start

•

mst status

•

flint –d <mst_device> dc > dump_configuration.log

•

mstdump <mst_device> dc > mstdump.log

Page 52

Specifications

MCX542A-ACANSpecifications

Physical

Protocol Support

Power

Environmental

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Dual SFP28 Ethernet (copper and optical)

Ethernet: 25GBASE-CR/CR-S, 25GBASE-SR, 25GBASE-LR, 25G Ethernet Consortium,

10GBASE-SR, 10GBASE-LR, 10GBASE-ER, SGMII / 1000BASE-X

Data Rate: 1/10/25 Gb/s Ethernet

PCI Express Gen3: SERDES @ 8.0GT/s (respectively), 16 lanes (2.0 and 1.1 compatible)

Voltage: 3.3V_PCI, 3.3V_AUX, 5V_AUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 15.55W

Maximum power available through QSFP28 port:1.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 12.95W

1.5W Active Cables 15.95W

1.5W Active Cables 18.55W

Non-operational -40°C to 70°C

90% relative humidity

(b)

Altitude (Operational)

3050m

Cable Type Heatsink to Port Port to Heatsink

(c)

Passive Cable 350LFM 400LFM

Active 1.5W Cable 350LFM 400LFM

Regulatory

Airflow

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

Page 53

MCX542B-AC[A/U]NSpecifications

Mellanox recommends populating MCX542B-ACAN in a standard PCIe x8 OCP connector



which exposes PCIe lanes in a straight manner. In case the OCP slot exposes PCIe lanes in a reversed manner, MCX542B-ACAN supports

automatic lane reversal with FW image from April 2019 release and above.

Please note that in standby mode, only port0 is available.



Physical

Protocol Support

Power

Environmental

Size: 2.67 in. x 4.33 in (68.00mm x 110.05mm)

Connector: Dual SFP28 Ethernet (copper and optical)

Ethernet: 25GBASE-CR/CR-S, 25GBASE-SR, 25GBASE-LR, 25G Ethernet Consortium,

10GBASE-SR, 10GBASE-LR, 10GBASE-ER, SGMII / 1000BASE-X

Data Rate: 1/10/25 Gb/s Ethernet

PCI Express Gen3: SERDES @ 8.0GT/s (respectively), 8 lanes (2.0 and 1.1 compatible)

Voltage: 3.3V_PCI, 3.3V_AUX, 5V_AUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 11.98W

Maximum power available through QSFP28 port:1.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 9.51W

1.5W Active Cables 12.51W

1.5W Active Cables 14.98W

Non-operational -40°C to 70°C

90% relative humidity

(b)

Regulatory

Altitude (Operational)

3050m

Cable Type Heatsink to Port Port to Heatsink

Airflow

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

(c)

Passive Cable 400LFM 400LFM

Active 1.5W Cable NA 1200LFM

(In Mellanox 0.8W Cables only)

Page 54

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

MCX545B-GCUNSpecifications

Physical

Protocol Support

Power

Environme ntal

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Single QSFP28 Ethernet (copper and optical)

Ethernet: 50GBASE-R2, 50GBASE-R4, 40GBASE-CR4, 40GBASE-KR4, 40GBASE-SR4,

40GBASE-LR4, 40GBASE-ER4, 40GBASE-R2, 25GBASE-R, 20GBASE-KR2, 10GBASE-LR, 10GBASE-ER, 10GBASE-CX4, 10GBASE-CR, 10GBASE-KR, SGMII, 1000BASE-CX, 1000BASEKX, 10GBASE-SR

Data Rate: 1/10/25/40/50 Gb/s

PCI Express Gen3: SERDES @ 8.0GT/s (respectively), 16 lanes (2.0 and 1.1 compatible)

Voltage: 3.3VAUX, 5VAUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 16.35W

Maximum power available through QSFP28 port:3.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 13.77W

1.5W Active Cables 17.85W

Non-operational -40°C to 70°C

90% relative humidity

(b)

Altitude (Operational) 3050m

Cable Type Heatsink to

Airflow tested in a

(c)

Passive Cable 400LFM 400LFM

Active 3.5W Cable Not Supported 800LFM

Regulatory

ducted tunnel

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

Port to Heatsink

Port

Page 55

MCX545B-CCUNSpecifications

Physical

Protocol Support

Power

Environment al

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Single QSFP28 Ethernet (copper and optical)

Ethernet: 100GBASE-CR4, 100GBASE-KR4, 100GBASE-SR4, 50GBASE-R2, 50GBASE-R4,

40GBASE-CR4, 40GBASE-KR4, 40GBASE-SR4, 40GBASE-LR4, 40GBASE-ER4, 40GBASE-R2, 25GBASE-R, 20GBASE-KR2, 10GBASE-LR,10GBASE-ER, 10GBASE-CX4, 10GBASE-CR, 10GBASE-KR, SGMII, 1000BASE-CX, 1000BASE-KX, 10GBASE-SR

Data Rate: 1/10/25/40/50/100 Gb/s

PCI Express Gen3: SERDES @ 8.0GT/s (respectively), 16 lanes (2.0 and 1.1 compatible)

Voltage: 3.3VAUX, 5VAUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 17.57W

Maximum power available through QSFP28 port:3.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 14.48W

1.5W Active Cables

Non-operational -40°C to 70°C

90% relative humidity

21.07W

(b)

Altitude (Operational) 3050m

Cable Type Heatsink to Port Port to Heatsink

Regulatory

Airflow tested in a

ducted tunnel

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

Passive Cable 400LFM 800LFM

(c)

Active 1.5W Cable

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

NA 400LFM

Page 56

MCX545A-CCAN andMCX545A-CCUN Specifications

Physical

Protocol Support

Power

Environment al

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Single QSFP28 Ethernet (copper and optical)

Ethernet: 100GBASE-CR4, 100GBASE-KR4, 100GBASE-SR4, 50GBASE-R2, 50GBASE-R4,

Data Rate: 1/10/25/40/50/100 Gb/s

PCI Express Gen3: SERDES @ 8.0GT/s (respectively), 16 lanes (2.0 and 1.1 compatible)

Voltage: 3.3VAUX, 5VAUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 17.57W

Maximum power available through QSFP28 port:3.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 14.48W

1.5W Active Cables

Non-operational -40°C to 70°C

90% relative humidity

21.07W

(b)

Altitude (Operational) 3050m

Cable Type Heatsink to Port Port to Heatsink

Regulatory

Airflow tested in a

ducted tunnel

Airflow tested in Dell’s

PowerEdge Servers (C6420)

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

(c)

Passive Cable 450LFM 400LFM

Active 1.5W Cable

Passive Cable 450LFM NA

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

1200LFM 700LFM

Page 57

MCX546A-BCANSpecifications

Physical

Protocol Support

Power

Environmenta l

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Dual QSFP28 Ethernet (copper and optical)

Ethernet: 40GBASE-CR4, 40GBASE-KR4, 40GBASE-SR4, 40GBASE-LR4, 40GBASE-ER4,

40GBASE-R2, 25GBASE-R, 20GBASE-KR2, 10GBASE-LR,10GBASE-ER, 10GBASE-CX4, 10GBASE-CR, 10GBASE-KR, SGMII, 1000BASE-CX, 1000BASE-KX, 10GBASE-SR

Data Rate: 1/10/25/40 Gb/s

PCI Express Gen3/4: SERDES @ 8.0GT/s / 16.0GT/s (respectively), 16 lanes (2.0 and 1.1

compatible)

Voltage: 3.3VAUX, 5VAUX, 12V

Power Cable Type

Typical Power

Maximum Power Passive Cables 18.1W

Maximum power available through QSFP28 port:3.5W

Temperature Operational 0°C to 55°C

Humidity

(a)

Passive Cables 15.4W

1.5W Active Cables

Non-operational -40°C to 70°C

90% relative humidity

23.2W

25.9W

(b)

Altitude (Operational) 3050m

Regulatory

Airflow tested in a

ducted tunnel

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

(c)

Passive Cable 400LFM 400LFM

Active 1.5W Cable NA 1200LFM

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

Heatsink to Port Port to Heatsink

Page 58

MCX546A-CDANSpecifications

Physical

Protocol Support

Power

Size: 3.07 in. x 4.33 in (78.00mm x 110.05mm)

Connector: Dual QSFP28 Ethernet (copper and optical)

Ethernet: 100GBASE-CR4, 100GBASE-KR4, 100GBASE-SR4, 50GBASE-R2, 50GBASE-R4,

Data Rate: 1/10/25/40/50/100 Gb/s

PCI Express Gen3/4: SERDES @ 8.0GT/s/16Gt/s, 16 lanes (2.0 and 1.1 compatible) Note: PCIe 4.0 x16 bus can supply a maximum bandwidth of 256Gb/s only (=16 * 16GT/s,

including overhead).

Voltage: 3.3VAUX, 5VAUX, 12V

Power Cable Type

(a)

Typical Power

Maximum Power Passive Cables 24.3W

Passive Cables 20.03W

3.5W Active Cables

27.8W

32.11W

Maximum power available through QSFP28 port:3.5W

Environment al

Regulatory

Temperature Operational 0°C to 55°C

Non-operational -40°C to 70°C

Humidity: 90% relative humidity

Altitude (Operational)

Airflow

Safety CB / cTUVus / CE

EMC CE / FCC / VCCI / ICES / RCM

RoHS RoHS compliant

(c)

3050m

Passive Cable 400LFM 400LFM

Mellanox Active Cables

(b)

a. Typical power for ATIS traffic load. b. For both operational and non-operational states. c. Airflow is measured on ambient 55°.

Heatsink to Port Port to Heatsink

Not supported 1200LFM

Page 59

Board Mechanical Drawing and Dimensions

All dimensions are in millimeters. All the mechanical tolerances are +/- 0.1mm.



For the 3D Model of the card, please refer to 3D Models at http://www.mellanox.com/page/



3d_models.

MCX542A-ACAN Mechanical Drawing and Dimensions

MCX542B-ACAN Mechanical Drawing and Dimensions

Page 60

MCX545B-CCUN Mechanical Drawing and Dimensions

MCX545A-CCAN and MCX545A-CCUN Mechanical Drawing and Dimensions

Page 61

MCX546A-CDAN and MCX546A-BCAN Mechanical Drawing and Dimensions

Page 62

Page 63

Finding the MAC and Serial Number on the Adapter Card

Each Mellanox adapter card has a different identifier printed on the label: serial number and the card MAC for the Ethernet protocol.

The product revisions indicated on the labels in the following figures do not necessarily



represent the latest revisions of the card.

MCX542A-ACAN Board Label (Example)

Page 64

Document Revision History

Date Revision Description of Changes

Oct. 2020 2.4 AddedMCX545B-GCUN support across the document.

Jul. 2020 2.3 Added MCX542B-ACUN support across the document.

Apr. 2020 2.2 Added MCX545A-CCUN support across the document.

Feb. 2020 2.1 Added altitude criteria to "Specifications".

Jan. 2020 2.0 Added MCX545B-CCUN support across the document.

Oct. 2019 1.9 Updated the supported Ethernet protocols in

"Specifications".

Oct. 2019 1.8 Updated board labels in "Finding the MAC and Serial

Number on the Adapter Card".

May. 2019 1.7 Added a note to "MCX542B-ACAN Specifications".

Apr. 2019 1.6 Updated comments in "Introduction", "Hardware

Installation" and "Specifications".

Feb. 2019 1.5 Added a comment to "Introduction" and

"Specifications".

Jan. 2019 1.4 Added MCX542B-ACAN and MCX546A-BCAN support

across the document.

Dec. 2018 1.3 Migrated to on-line format; minor reorganization.

Oct. 2018 1.2 Updated MCX542A-ACAN Specification.

Sep. 2018 1.1 Added MCX546A-CDAN and MCX542A-ACAN support

across the document.

Jul. 2017 1.0 First release

Page 65

Mellanox Technologies | 350 Oakmead Parkway Suite 100, Sunnyvale, CA 94085 http://

www.mellanox.com

Notice

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. Neither NVIDIA Corporation nor any of its direct

or indirect subsidiaries (collectively: “NVIDIA”) make any representations or warranties, expressed or

implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality. NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete. NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by

authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects

to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document. NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such

equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It

is customer’s sole responsibility to evaluate and determine the applicability of any information

contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the

application or the product. Weaknesses in customer’s product designs may affect the quality and

reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs. No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA. Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices. THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY,

“MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED,

IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any

damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative

Page 66

Mellanox Technologies | 350 Oakmead Parkway Suite 100, Sunnyvale, CA 94085 http://

www.mellanox.com

liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

Trademarks

NVIDIA, the NVIDIA logo, and Mellanox are trademarks and/or registered trademarks of Mellanox

Technologies Ltd. and/or NVIDIA Corporationin the U.S. and in other countries. Other company and

product names may be trademarks of the respective companies with which they are associated. For the complete and most updated list of Mellanox trademarks, visit http://www.mellanox.com/page/

trademarks