Home

Mellanox OFED Linux User`s Manual

1. To specify a topology file to a diagnostic tool use one of the following two options Mellanox Technologies Confidential InfiniBand Fabric Diagnostic Utilities Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 1 On the command line specify the file name using the option t lt topology file name gt 2 Define the environment variable IBDIAG TOPO FILE To specify the local system name to an diagnostic tool use one of the following two options 6 I On the command line specify the system name using the option s lt local system name gt 2 Define the environment variable IBDIAG SYS NAME 8 2 2 IB Interface Definition The diagnostic tools installed on a machine connect to the IB fabric by means of an HCA port through which they send MADs To specify this port to an IB diagnostic tool use one of the follow ing options I On the command line specify the port number using the option p lt local port number gt see below 2 Define the environment variable IBDIAG PORT NUM In case more than one HCA device 1s installed on the local machine it is necessary to specify the device s index to the tool as well For this use on of the following options 1 On the command line specify the index of the local device using the following option 1 lt index of local device gt 2 Define the environment variable IBDIAG DEV IDX 8 2 3 Addressing S This section applies to the ibdiagpath tool o
2. 94 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 SRP Service ID is defined by the SRP target I O Controller it also complies with IBTA Service ID rules The Service ID is reported by the I O Controller in the ServiceEntries DMA attribute and should be used in the PR MPR if the SA reports its ability to handle QoS PR MPRs 3 8 5 OpenSM Features The QoS related functionality that is provided by OpenSM the Subnet Manager described in Chapter 7 can be split into two main parts I Fabric Setup During fabric initialization the Subnet Manager parses the policy and apply its settings to the dis covered fabric elements II PR MPR Query Handling OpenSM enforces the provided policy on client request The overall flow for such requests is first the request is matched against the defined match rules such that the target QoS Level definition is found Given the QoS Level a path s search is performed with the given restrictions imposed by that level 3 9 Atomic Operations 3 9 1 Enhanced Atomic Operations ConnectX implements a set of Extended Atomic Operations beyond those defined by the IB spec Atomicity guarantees Atomic Ack generation ordering rules and error behavior for this set of extended Atomic operations 1s the same as that for IB standard Atomic operations as defined in section 9 4 5 of the IB spec 3 9 1 1 Masked Compare and Swap MskCmp
3. Installation e Installation Summary e Perform Installation Configuration e Root Password e Hostname e Network e Customer Center Incoming Authentication e Online Update Username Password e Service e Users e Clean Up e Release Notes e Hardware Configuration X No Authentication Outgoing Authentication Username Password Help Back Abort Next Step 6 The iSCSI Initiator Discovery window will show the iSCSI target that got connected to Note that the Connected column must indicate True for this target Click Next See figure below Preparation Y Language Y License Agreement gt Disk Activation c e System Analysis Portal Address Target Name Connected e Time Zone 10 4 3 7 3260 1 iqn 2007 08 7 3 4 10 iscsiboot True iSCSI Initiator Discovery I Installation e Installation Summary e Perform Installation Configuration e Root Password e Hostname e Network e Customer Center e Online Update e Service e Users e Clean Up e Release Notes e Hardware Configuration Help Back Abort Next Mellanox Technologies 223 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 7 The iSCSI Initiator Overview window will pop up Click Toggle Start Up to change start up from manual to automatic Click Finish Preparation Y Language Y License Agreement Disk Activation iSCSI Initiator Overview e System Analysis
4. Show Release Notes Heip AD ort Mellanox Technologies 225 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 11 Your hard disks have been checked The partition setup displayed is proposed for your hard drive To acceptthese suggestions and continue select Accept Proposal Ifthe suggestion does not fit your needs create your own partition setup starting with the partitions as currently present on the disks Forthis select Custom Partition Setup This is also the option to choose for advanced options like RAID and LVM Step 12 Partition your hard a disks This is intended for experts If you are not familiar with the concepts of hard disk partitions and how to use them you might wantto go back and select automatic partitioning Please note that nothing will be written to your hard disk until you confirm the entire installation in the last installation dialog Until that point you can safely abort the installation For LVM setup using a non LVM root device and a non LVM swap device is recommended Other than the root and swap devices you should have partitions managed by LVM The table to the right shows the current partitions on all your hard disks KI Hard disks are Mellanox Technologies Select Base Partition Setup on This Proposal then click Next Suggested Partitioning Creat
5. 12 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 2 Abbreviations and Acronyms Sheet 2 of 2 Abbreviation Acronym Whole Word Description Small b is used to indicate size in bits or multiples of bits e g 1Kb 1024 bits vr T O gt T Le DI lt vo Y az m Q n Cla nm iii Mellanox Technologies 13 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Glossary The following is a list of concepts and terms related to InfiniBand in general and to Subnet Manag ers in particular It is included here for ease of reference but the main reference remains the InfiniBand Architecture Specification Table 3 Clossary Channel Adapter CA An IB device that terminates an IB link and executes transport functions Host Channel Adapter This may be an HCA Host CA or a TCA Target CA HCA HCA Card A network adapter card based on an InfiniBand channel adapter device IB Devices Integrated circuit implementing InfiniBand compliant communication IB Cluster Fabric A set of IB devices connected by IB cables Subnet A term assigned to administration activities traversing the IB connectivity only LID An address assigned to a port data sink or source point by the Subnet Man ager unique within the subnet used for directing packets within the subnet Local Devi
6. 7 9 2 Running OpenSM with Congestion Control Manager nnana anaana aaaea nnn aa 159 6 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 9 2 1 Congestion Control Manager Options File o ooooooooooooo 160 Chapter 8 InfiniBand Fabric Diagnostic UtilitieS oooooooooooo eens 162 8 1 Overview 162 8 2 Utilities Usage 162 8 2 1 Common Configuration Interface and Addressing rr rr 162 8 22 JB Intenace Deftones OE siede 163 Sd Addeen il ii i da cd id 163 8 3 ibdiagnet of ibutils2 IB Net Diagnostic 164 Sid SYINOPSYS tdci sd ESSI LR arenas 164 SI Diputada 165 Sd REMM COdeS 6 siii AA AA Ai ei 166 8 4 ibdiagnet of ibutils IB Net Diagnostic 166 Beek N 2167 ES 6 dre eee beat S A NA RAR ae Bete r r 166 0 42 SOUP PIGS ranas da ee dle ts ld 168 843 ERROR CECODES bobo id a 169 8 5 ibdiagpath IB diagnostic path 169 Sol SYNOPSY 5 2 seus Uitte eee ees eee hee ee ee dee ees 169 A OU 1 A A settee bute rten gin Gh 170 So ERROR CODES tlc AS tole a Maine e ne Nie E ards A Gee a ae 170 8 6 ibv_devices 171 8 7 i
7. Also note that FCoE can run only on a port configured as eth and the m1x4 en driver must be loaded The port link type can be configured for each device in the system at run time using the sbin connectx port config script This utility will prompt for the PCI device to be modified if there is only one it will be selected automatically In the next stage the user will be prompted for the desired mode for each port The desired port configuration will then be set for the selected device This utility also has a non interactive mode Mellanox Technologies 97 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Working With VPI Pon SOS cios POr eolie E ae eine Oo Za 4 2 InfiniBand Driver The InfiniBand driver m1x4 ib handles InfiniBand specific functions and plugs into the InfiniBand midlayer 4 3 Ethernet Driver 4 3 1 Overview MLNX EN driver is composed from mlx4_core and mlx4_en kernel modules and exposes the following ConnectX ConnectX 2 capabilities Single Dual port Up to 16 Rx queues per port 5 Tx queues per port Rx steering mode Receive Core Affinity RCA Tx arbitration mode VLAN user priority off by default MSI X or INTx Adaptive interrupt moderation HW Tx Rx checksum calculation Large Send Offload 1 e TCP Segmentation Offload Large Receive Offload IP Reassembly Offload Multi core NAPI support VLAN Tx Rx acceleration HW VLAN stripping insertion HW VLAN filtering
8. DEVICE An optional field The name of the interface that is displayed when running ifconfig If it is not present the trailer of the configuration file name e g ifefg eth47 gt eth47 is used instead HWADDR The mac address to assign the vNic BXADDR The BridgeX box system GUID or system name string BXEPORT The string describing the eport name VNICVLAN An optional field If it exists the vNic will be assigned the VLAN ID specified This value must be between 0 and 4095 VNICIBPORT The device name and port number in the form device name port number The device name can be retrieved by running ibv devinfo and using the output of hca id filed The port number can have a value of 1 or 2 Other fields available for regular eth interfaces in the ifefg ethX files may also be used mlx4_vnic_confd Once the configuration files are updated the host administered vNics can be created To manage the host administrated vNics run the following script Usage etc init d mlx4 vnic confd start stop restart reload status To retrieve general information about the vNics on the system including network administrated vNics refer to Section 3 6 3 1 mlx4 vnic_info on page 79 3 6 2 2 EolB Network Administered vNic In network administered mode the configuration of the vNic is done by the BridgeX If a vNic is configured for a specific host it will appear on that host once a connection is established b
9. HW multicast filtering ifconfig up down mtu changes up to 10K Ethtool support Net device statistics CX4 QSFP and SFP connectors 4 3 2 Loading the Ethernet Driver By default the Mellanox OFED stack loads m1x4 en Run ifconfig a to verify that the module is listed 98 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 4 3 3 Unloading the Driver If etc infiniband openib conf had MLX4 EN LOAD yes at driver start up then you can unload the m1x4 en driver by running etc init d openibd stop Otherwise unload m1x4 en by running AMO oe mie en 4 3 4 Ethernet Driver Usage and Configuration e To assign an IP address to the interface run H gt CEfconfig eth 0 lt p gt where x 1s the OS assigned interface number e To check driver and device information run PANICO in Example gt ethtool i eth2 driver mix4 en MI 04201400059 vers ton 1 5 1 March 2010 Eir mwar o Vers ron LEER DIS Mio USOS e To query stateless offload status run a D E e To set stateless offload status run foro ee Ok m Keowee Don Omni Whee ton Ou ml so Omi Min es o L al e To query interrupt coalescing settings run i gt ebhtool sc eh By default the driver uses adaptive interrupt moderation for the receive path which adjusts the moderation time to the traffic pattern To enable disable adaptive interrupt moderation use the follow
10. Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 qos ulps default 20 default SL for MPI sn e SE Or io OST OSI OS STI Ll a Sih oi OSE Sid eee oot pouco MIDS dl MIOS 2 A A SS ds MIOS end qos ulps e OpenSM options file Gos Mex ve 6 gos acia alo 20 gos vlaro high gos V laro Low sO Oea SI E drone Sio 7 7 2 EDC SOA 2 tier IPolB and SRP The following is an example of QoS configuration for a typical enterprise data center EDC with service oriented architecture SOA with IPoIB carrying all application traffic and SRP used for storage QoS Levels e Application traffic IPoIB UD and CM and SDP Isolated from storage Min BW of 50 e SRP Min BW 50 Bottleneck at storage nodes Administration e OpenSM QoS policy file 4 In the following policy file example replace SRPT with the real SRP Target port E GUIDs gt qos ulps Mellanox Technologies 155 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager default 40 ipoib ali sdp sull SO E OS port US IS RZ RPT oz end qos ulps e OpenSM options file goc maz Ass eos Inacio Mime estero oa geco A A SS oy poy oy boy SAS Ss a eo 7 7 3 EDC 3 tier IPoIB RDS SRP The following is an example of QoS configuration for an enterprise data center EDC with IPoIB carrying all application traffic RDS for database traffic and SRP used for storage QoS Levels e Management tr
11. Restarting openibd does no keep the bonding configuration via Network Scripts You S have to restart the network service in order to bring up the bonding master After the configuration is saved restart the network service by running etc init d network da restart 3 8 Quality of Service 3 8 1 Quality of Service Overview Quality of Service QoS requirements stem from the realization of I O consolidation over an IB network As multiple applications and ULPs share the same fabric a means is needed to control their use of network resources Mellanox Technologies 91 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features Figure 2 I O Consolidation Over InfiniBand Servers J J Unified I O I w i f Ja D QoS Filer e AG IB Ethernet 5 Gateway IB Fibre Block Storage Channel Gateway QoS over Mellanox OFED for Linux is discussed in Chapter 7 OpenSM Subnet Manager The basic need is to differentiate the service levels provided to different traffic flows such that a policy can be enforced and can control each flow utilization of fabric resources The InfiniBand Architecture Specification defines several hardware features and management interfaces for supporting QoS e Upto 15 Virtual Lanes VL carry traffic in a non blocking manner e Arbitration between traffic of different YLS is performed by a two priority level weighted round robin arbiter The arbiter is pr
12. Rev 1 5 1 April 22 2010 e Added Section 5 1 7 Reading Port Counters Statistics the section A Detailed Example was moved to become Section 5 1 8 Rev 1 5 March 29 2010 e Updated Figure 1 Mellanox OFED Stack e Added support for ConnectX 2 devices e Added support for ROMA over Converged Ethernet RoCE see Chapter 5 RoCE e Modified Section 7 3 3 1 How to Know SDP Is Working e Added Section 7 3 7 Using RDMA for Small Buffers e Added support for NFS over ROMA NFSoRDMA Chapter 10 NFSoRDMA e Added Section 11 5 2 Important Note on RoCE Support on page 114 in Chapter 6 MPI Message Passing Interface e Modified Section 7 2 1 opensm Syntax on page 113 e Added Chapter 5 Mellanox Technologies 9 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 e Added ibdiagnet of ibutils2 and ibdump to Chapter 8 InfiniBand Fabric Diagnostic Utilities e Appendix B is now called Mellanox FlexBoot instead of BoIB FlexBoot supports Virtual Protocol Interconnect VPI e Added Section 5 3 3 System Performance Troubleshooting e Added the parameter setting VIADEV RENDEZVOUS THRESHOLD 8 192 Sec tion 11 2 3 MPI Performance Tuning Rev 1 40 1 Changes from 1 40 March 19 2009 e Correction to text in Section 9 3 3 IPoIB Configuration on page 93 10 Mellanox Technologies Mellanox Technologies Confidential
13. e Section 8 8 ibdev2netdev on page 173 e Section 8 9 ibstatus on page 174 e Section 8 10 ibportstate on page 176 e Section 8 11 ibroute on page 180 e Section 8 12 smpquery on page 184 e Section 8 13 perfquery on page 188 e Section 8 14 ibcheckerrs on page 191 e Section 8 15 mstflint on page 193 e Section 8 16 ibv_asyncwatch on page 197 e Section 8 17 ibdump on page 197 Utilities Usage This section first describes common configuration interface and addressing for all the tools in the package Then it provides detailed descriptions of the tools themselves including operation syn opsis and options descriptions error codes and examples Common Configuration Interface and Addressing Topology File Optional An InfiniBand fabric is composed of switches and channel adapter HCA TCA devices To iden tify devices in a fabric or even in one switch system each device is given a GUID a MAC equivalent Since a GUID is a non user friendly string of characters it is better to alias it to a meaningful user given name For this objective the IB Diagnostic Tools can be provided with a topology file which is an optional configuration file specifying the IB fabric topology in user given names For diagnostic tools to fully support the topology file the user may need to provide the local sys tem name if the local hostname is not used in the topology file
14. el gora ONS CLAN Cue me One a ewes E O NN E SONE ps 8 11 ibroute Applicable Hardware InfiniBand switches Description Uses SMPs to display the forwarding tables unicast LinearForwardingTable or LFT or multi cast MulticastForwardingTable or MFT for the specified switch LID and the optional lid mlid range The default range is all valid entries in the range 1 to FDBTop Synopsis ipogeo Sad Sita A el Sa eb SG aie ee lt eillige Se Seen gente Iai cere or aad HT GI dal TET lt startlid gt lt endlick gt Table 17 lists the various flags of the command Table 17 ibportstate Flags and Options l Default SO If Not Description y Specified Optional Raise the IB debug level May be used several times for higher debug levels ddd or d d d a 11 Optional Show all LIDs in range including invalid entries v erbose Optional Increase verbosity level May be used several times for additional verbosity vvv or v v v Pr Omi DO Seo o a 11 Optional Show all LIDs in range including invalid entries 180 Mellanox Technologies Mellanox Technologies Confidential InfiniBand Fabric Diagnostic Utilities Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 17 ibportstate Flags and Options Optional Pera Flag Re or If Not Description 7 Specified Use directed path address arguments The path is a comma separated list of out ports Examples 0 self port 0 1 2 1 4
15. me a COMMIG TE ale Example of the configuration file can be found under docs e network config file gt Example of the network configuration file can be found under docs se va ts Print available packages for the current jolatiorm ancl create a Corresponding Ored cont file Ihe Installa tion script exits after creating ofed conr Wacom Skip Dit libraries Installa on without depcheck Skip Distro so libraries check without fw update Skip firmware update force fw update Force firmware update force Force installation without querying the user a 11 Install all kernel modules libibverbs libibumad Tror dmacm mii ela Clielcimios eee ib bonding MVAPICH Open MPI MPI tests MPI selec tor per Lect sdpnetstattanddilibsdp osrtptocols j Tds EDO ES static and ynamie libraries salse Insiel sd erre modules libibverbs libibumad oro mii moer LINE oe ios ale oo ls peas ED ERO Rd MYAETCH Open MEM AMT tor dynamic libraries basic Install all kernel mod ules libibverbs libibumad eni een ae EE R Mellanox Technologies 20 od Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation msm Install all kernel modules libibverbs libibumad Mae misil dragon R ke Open MA 00 O Trad dynamic libraries NOTES Wah MSM flag the OpenSM daemon is config ured to run upon boot y vy vvy Set verbosity level Z BI E ike EA O cdot o nero pols TCA SIOE TI cec qui
16. mstflint Switches Sheet 2 of 2 Affected Relevant Description Commands byte_mode burn write Shift address when accessing Flash internal registers May be required for burn write commands when accessing certain Flash types Non interactive mode Assume the answer is yes to all questions e pooo Non interactive mode Assume the answer is no to all questions vsd lt string gt bum Write this string of up to 208 characters to VSD upon a burn command bend a Burn vsd as it appears in the given image do not keep existing VSD on Flash dual image Make the burn process burn two images on Flash The current default fail safe burn process burns a single image in alternating locations Table 22 mstflint Commands Ca Burn Block Burn the given image as is without running any checks dc lt out file gt Dump Configuration Print a firmware configuration file for the given image to the specified output file wbne lt addr gt lt s1ze gt Write a data block to Flash without sector erase lt data gt rb lt addr gt lt size gt out Read a data block from Flash file swreset SW reset the target InfniScale IV device This command is supported only in the In Band access method Mellanox Technologies 195 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities Possible command return values are 0 successful completion 1 error has occurred 7
17. out via port 1 then 2 Use GUID address argument In most cases 1t is the Port GUID Example 0x08 1040023 Show multicast forwarding tables The parameters lt star tlid gt and lt endlid gt specify the MLID range t Optional lt timeout ms gt lt dest dr path Optional lid guid gt Examples Use the specified channel adapter or router Use the specified port Override the default timeout for the solicited MADs msec Destination s directed path LID or GUID Starting LID in an MLID range Ending LID in an MLID range 1 Dump all Lids with valid out ports of the switch with Lid 2 MO O One Unie as Tas Os OS Moo H meo ada Ud DAS OM tease tae O Mr So Infiniscale 111 Mellanox Technologies LIC OUT Destination BOE Info A E Seco gear rO Oa MTA NS eno see ue T Me Nanos Tecno logras Ux00US 207 Is W T Ea T U ERE OONO e mr rm OOO EO VR rn a III Mellanox Technologies OLOGO RELE n e hanne e A apren E E Ura OOOO OUT O Ss Oe an ACA IR oO FARO A C hanne Adapter oe ua OO OA Sa HC A 1E OP ATION 300 0 E RS e E o pres q Se uta a O O e 0700S SO delie E DE Mellanox Technologies 181 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 oo Valid leds DEC 2 Dump all Lids with valid out ports of the switch with Lid 2 SO en baie T 0x0 US enc Swap ESOO DAS SO EEEE OOT iit E calle II Ved Lanes Technologies Lie Our Destination Pore LALO InfiniBand Fabric Diag
18. screen default 3 Placed default var tmp ibdiagnet2 alii Peint ciTe help meso Je V vers Lion Print the version of the tool 8 3 2 Output Files Table 11 lists the ibdiagnet output files that are placed under var tmp ibdiagnet2 Table 11 ibdiagnet of ibutils2 Output Files An ibdiagnet run performs the following stages e Fabric discovery Mellanox Technologies 165 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities e Duplicated GUIDs detection e Links in INIT state and unresponsive links detection e Counters fetch e Error counters check e Routing checks e Link width and speed checks 8 3 3 Return Codes ON Success l railure wiih description 8 4 ibdiagnet of ibutils IB Net Diagnostic S This version of ibdiagnet is included in the ibutils package and it is run by default after installing Mellanox OFED To use this ibdiagnet version run ibdiagnet ha ibdiagnet scans the fabric using directed route packets and extracts all the available information regarding its connectivity and devices It then produces the following files in the output directory which is defined by the o option described below 8 4 1 SYNOPSYS Dh agnet i e count Rezia edo eo eye mame a de ce A o ore mune A AE emmy pelil Pe PM vale IT ive ee aa Ls MO joie odia dolo iso 166 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for
19. 3 4 4 Environment Variables For the transparent integration with SDP the following two environment variables are required I LD PRELOAD this environment variable is used to preload libsdp so and it should point to the 1ibsdp so library The variable should be set by the system administrator to usr lib libsdp so or usr lib64 libspd so 2 LIBSDP CONFIG FILE this environment variable is used to configure the policy for replacing TCP sockets with SDP sockets By default it points to etc libsdp conf 3 SIMPLE LIBSDP ignore libsdp conf and always use SDP 3 4 5 Converting Socket based Applications You can convert a socket based application to use SDP instead of TCP in an automatic also called transparent mode or in an explicit also called non transparent mode Automatic Transparent Conversion The libsdp conf configuration policy file is used to control the automatic transparent replacement of TCP sockets with SDP sockets In this mode socket streams are converted based upon a destination port a listening port or a program name Socket control statements in libsdp conf allow the user to specify when 1ibsdp should replace AF INET SOCK STREAM sockets with AF SDP SOCK STREAM sockets Each con trol statement specifies a matching rule that applies if all its subexpressions must evaluate as true logical and The use statement controls which type of sockets to open The format of a use statement is as follows mse
20. Default Flag SUONA If Not Description Mandatory Specified Destination s directed path LID or GUID lt op gt Mandatory Supported operations nodeinfo lt addr gt nodedesc lt addr gt portinfo lt addr gt lt portnum gt switchinfo lt addr gt pkeys lt addr gt lt portnum gt sl2vl lt addr gt lt portnum gt vlarb lt addr gt lt portnum gt guids lt addr gt lt dest dr path Optional lid guid gt Examples I Query PortInfo by LID with port modifier gt SMpquenLy Portinto dal ESB RO lisa dl e T VISAE E Ca I RI 0x0000000000000000 A SS edan eo ai sari Oxfe80000000000000 VE A RE A a Re N AR a 0x0001 E A RIA A 0x0001 PUR O O Ox251086a ISSM IsTrapSupported RETZ tbteMigtatbtonsuwpported IsSLMappingSupported IsSystemImageGUIDsupported IsCommunicatonManagementSupported IsVendorClassSupported IsCapabilityMaskNoticeSupported ToC lient Regustratronsupported TO CCS MEE A a E A E cis 0x0000 MK Sy Te as Seo o ona 0 Ore E Ro de il ao lalo odo dl A E O em E O OS Mellanox Technologies 185 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities 186 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 2 Query SwitchInfo by GUID 3 Query Nodelnfo by direct route Mellanox Technologies 187 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic
21. ET UP 4X DDR Port State of Port fe on HCA ZR AENA EN INIT Error Counter Check on HCA 0 Ende I PASS Kernel Syslog Check SR A ASA RI I PASS Node GUID on HCA 0 EE i NE n AE OI Lt ERE do OUT 0850 000400 prefix kernel version and installation parameters can be retrieved by running the com 74 After the installer completes information about the Mellanox OFED installation such as A mand etc infiniband info 2 3 4 Installation Results Software e The OFED and MFT packages are installed under the usr directory e The kernel modules are installed under InfiniBand subsystem lib modules uname r updates kernel drivers infiniband mlx4 driver Under lib modules uname r updates kernel drivers net mlx4 you willfind mlx4_core ko mlx4 cn Ko mlx4 1b ko mlx4 vnic ko and mlx4_fc ko Mellanox Technologies 35 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation IPoIB lib modules uname r updates kernel drivers infiniband ulp ipoib SR SO ALO e des SDP lib modules uname r updates kernel drivers infiniband ulp sdp os cl ISS SRP lib modules uname r updates kernel drivers infiniband ulp srp SR GS CO AC 1ib modules uname r updates kernel drivers infiniband ulp srpt sr eso RDS lib modules uname r updates kernel net rds rds ko Lido mie cudles tners r Wpdaces mermel mel clay oe Tone ko Lis medules Mace vy useless kernel m
22. It also inter faces with Generic SCSI target mid level driver SCST http scst sourceforge net By interfacing with an SCST driver it is possiblee to work with and support a lot of IO modes on real or virtual devices in the backend I scst_vdisk fileio and blockio modes This allows turning software raid volumes LVM vol umes IDE disks block devices and normal files into SRP luns 2 NULLIO mode allows measuring the performance without sending IOs to real devices B 1 Prerequisites and Installation I For the supported distributions please see the Mellanox OFED release notes On distribution default kernels you can run scst_vdisk blockio mode to obtain good performance dai 2 Download and install the SCST driver The supported version is 1 0 1 1 a Download scst 1 0 1 1 tar gz from http scst sourceforge net downloads html b Untar scst 1 0 1 1 O A 56 cel sest 1 0 1 1 c Install scst 1 0 1 1 as follows S make amp amp make install B 2 How to run A On an SRP Target machine I Please refer to SCST s README for loading scst driver and its dev handlers drivers sest_vdisk block or file IO mode nullio Then you can have any lun number following lun 0 it is not required to have the lun Regardless of the mode you always need to have lun 0 in any group s device list numbers in ascending order except that the first lun must always be 0 di Mellanox Technologies 233 Mellanox Technol
23. It heavily depends on the chipset memory and CPU Nevertheless the full wire speed should be achieved by the host With IB SDR the expected unidirectional full wire speed bandwidth is 900MB sec With IB DDR and PCI Express Gen 1 the expected unidirectional full wire speed bandwidth is 1400MB sec With IB DDR and PCI Express Gen 2 the expected unidirectional full wire speed bandwidth is 1800MB sec With IB Y QDR and PCI Express Gen 2 the expected unidirectional full wire speed bandwidth is 3000MB sec To check the adapter s maximum bandwidth use the ib write bw utility To check the adapter s latency use the ib write lat utility S The utilities ib write bw and ib write lat are installed as part of Mellanox OFED hai 5 3 3 System Performance Troubleshooting On some systems it is recommended to change the power saving configuration in order to achieve better performance This configuration is usually handled by the BIOS Please contact the system vendor for more information 108 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 6 MPI Message Passing Interface 6 1 Overview S PGI compiler does not support RHEL6 0 thus MLNX_OFED v1 5 2 will not include openmpi and mvapich with PGI compiler on RHEL6 dai Mellanox OFED for Linux includes the following MPI implementations over InfiniBand and RoCE e Open MPI an open source
24. any Sie any lps hb SIR Pore US 0000 O it it GTR nen LOUD R HEL EDD O 1 T 2 T pkey 0x0001 O it 4 T SS io 0x62 34 6 T it pkey 0x0ABC 6 T TR GUTAR T T target Port JUL 8 AR E E E C T end qos ulps default SL SIRO ao AAC at om aca ON POO Of SDP nhen a des nation a old so 000 default cuor any OENEr PPTA Eton DR ERGE DER Common TE S Oi ROOTS rar E S E I ET T pkey 0x0001 det AE Pole E T pkey 0x7FFF match any PR MPR query with a Spc Crane eae vaa AD match any PR MPR guery with a specific PKey SIE T ORP Taree mro MOS ae dl ON a specified IB port GUID 6 match any PR MPR query Wiese ETTER reeling elo Oe UA Similar to the advanced policy definition matching of PR MPR queries is done in order of appear ance in the QoS policy file such as the first match takes precedence except for the default rule which is applied only if the query didn t match any other rule All other sections of the QoS policy file take precedence over the qos ulps section That is if a policy file has both qos match rules and qos ulps sections then any query is matched first against the rules in the qos match rules section and only if there was no match the query is matched against the rules in qos ulps section Note that some of these match rules may overlap so in order to use the simple QoS definition effectively it is important to understand how each of the ULPs is matched 150 Mellanox T
25. it is connected to the InfiniBand fabric by one or more links On the other side usually referred to as the external side it 1s connected to the Ethernet subnet by one or more ports The Ethernet connections on the BridgeX s external side are called external ports or eports Every BridgeX that is in use with EoIB needs to have one or more eports connected 3 6 1 1 External Ports eports and Gateway The combination of a specific BridgeX box and a specific eport is referred to as a gateway The gateway is an entity that is visible to the EoIB host driver and is used in the configuration of the network interfaces on the host side For example in the host administered vNics the user will request to open an interface on a specific gateway identifying it by the BridgeX box and eport name Distinguishing between gateways is essential because they determine the network topology and affect the path that a packet traverses between hosts A packet that is sent from the host on a spe cific EoIB interface will be routed to the Ethernet subnet through a specific external port connec tion on the BridgeX box 3 6 1 2 Virtual Hubs vHubs Virtual hubs connect zero or more EoIB interfaces on internal hosts and an eport through a vir tual hub Each vHub has a unique virtual LAN VLAN ID Virtual hub participants can send packets to one another directly without the assistance of the Ethernet subnet external side rout 14 Mellanox Technologies Mell
26. lt address famvly gt lt role gt lt program mame gt lt address gt lt port rangel gt where Mellanox Technologies 57 I Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 58 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 number lt 1200 pss omo 2 ar sine Sado lt 32 A PLe hae Engen fono eo ZONA ANOS yee Ten aio E Micia ee Spoon start port end port where port numbers are gt 0 and lt 65536 Note that rules are evaluated in the order of definition So the first match wins If no match is made libsdp will default to both Examples e Use SDP by clients connecting to machines that belongs to subnet 192 168 1 Us es deco ne I E ZA e Use SDP by ttcp when it connects to port 5001 of any machine use sdp E ro ST HRE e Use TCP for any program with name starting with ttcp serving ports 22 to 25 use tcp server ttcp E O e Listen on both TCP and SDP by any server that listen on port 8080 use both server who von e Connect ssh through SDP and fallback to TCP to hosts on 11 4 8 port 22 use both connect 11 4 8 0 24g322 Explicit Non transparent Conversion Use explicit conversion if you need to maintain full control from your application while using SDP To configure an explicit conversion to use SDP simply recompile the application replacing PF INET or PF INET with AF
27. proc img TO suine ina mask 1 fi done echo irgs were set OK 5 2 5 Preserving Your Performance Settings After A Reboot To preserve your performance settings after a reboot you need to add them to the file etc sysctl conf as follows lt sysctl namel gt lt valuel gt lt sysctl name2 gt lt value2 gt lt sysctl name3 gt lt value3 gt lt sysctl name4 gt lt value4 gt For example Section 5 2 1 Tuning the Network Adapter for Improved IPv4 Traffic Perfor mance listed the following setting to disable the TCP timestamps option societa eee mimes tas 0 In order to keep the TCP timestamps option disabled after a reboot add the following line to etc sysctl conf Netas peines tan 0 5 3 Performance Troubleshooting 5 3 1 PCI Express Performance Troubleshooting For the best performance on the PCI Express interface the adapter card should be installed in an x8 slot with the following BIOS configuration parameters e Max Read Req the maximum read request size is 512 or higher e MaxPayloadSize the maximum payload size is 128 or higher 106 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 4 A Max Read Reg of 128 and or installing the card in an x4 slot will significantly limit bandwidth ha To obtain the current setting for Max Read Reg enter seipel ob To obtain the PCI Express slot link width and speed enter se
28. should all match for the rule to apply The matching expressions are defined for the following fields e SRC and DST to lists of port groups Service ID to a list of Service ID values or ranges e QoS Class to a list of QoS Class values or ranges 3 8 4 CMA Features The CMA interface supports Service ID through the notion of port space as a prefix to the port number which is part of the sockaddr provided to rdma resolve add The CMA also allows the ULP like SDP to propagate a request for a specific QoS Class The CMA uses the provided QoS Class and Service ID in the sent PR MPR 3 8 4 1 IPolB IPoIB queries the SA for its broadcast group information and uses the SL MTU RATE and Packet Lifetime available on the multicast group which forms this broadcast group 3 8 4 2 SDP SDP uses CMA for building its connections The Service ID for SDP is 0x000000000001PPPP where PPPP are 4 hexadecimal digits holding the remote TCP IP Port Number to connect to 3 8 4 3 RDS RDS uses CMA and thus it is very close to SDP The Service ID for RDS is 0x000000000106PPPP where PPPP are 4 hexadecimal digits holding the TCP IP Port Number that the protocol connects to The default port number for RDS is 0x48CA which makes a default Service ID 0x00000000010648CA 3 8 4 4 SRP The current SRP implementation uses its own CM callbacks not CMA So SRP fills in the Ser vice ID in the PR MPR by itself and use that information in setting up the QP
29. the burn command was aborted because firmware is current Examples I Find Mellanox Technologies s ConnectX VPI cards with PCI Express running at 2 5GT s and InfiniBand ports at DDR or Ethernet ports at 10GigE elia ee 04 00 0 InfiniBand Mellanox Technologies MT25418 ConnectX IB DDR PCIe E i E NEN In the example above 15b3 is Mellanox Technologies s vendor number in hexadecimal and 634a is the device s PCI Device ID in hexadecimal The number string 04 00 0 identifies the device in the form bus dev fn 4 The PCI Device IDs of Mellanox Technologies devices can be obtained from the PCI ID Repository Website at http pci 1ds ucw cz read PC 15b3 As 2 Verify the ConnectX firmware using its ID using the results of the example above gt msrilint AO Connectx fallsate image Start address 20000 Chumk size 80000 NOTE The addresses below are contiguous logical addresses Physical addresses on flash may be different based on the image start address and chunk size 000000027 0x000010db OA BOOT mOr 100000 od E RRR HRE R O00 e BOOT EE TOK OO SAS AOS OOO SO Congo Ol USOS O 00 S20 03000 0 4 ACUTI OR 0000053000000 Z7 0000120 INO 00 0 0105 13 0295 00006 34 Ox000EZ0 DDR Of 0000 0106 SS O AO lo R RRR 00 OSO he 0000A A Slo OPO SAIC DDR ON 196 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 E O e OST Olite a
30. 0 dropped 0 overruns 0 frame 0 ae keres O0 errors 0 dropped 0 overruns e camera 0 colna ions Equ ete AZ RX bytes DO T pyres E 00 D Step 3 Repeat Step 1 and Step 2 on the remaining interface s Subinterfaces You can create subinterfaces for a primary IPoIB interface to provide traffic isolation Each such subinterface also called a child interface has a different IP and network addresses from the pri mary parent interface The default Partition Key PKey ff ff applies to the primary parent interface This section describes how to e Create a subinterface Section 3 7 4 1 e Remove a subinterface Section 3 7 4 2 Creating a Subinterface S In the following procedure 1b0 is used as an example of an IB subinterface ha 88 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 To create a child interface subinterface follow this procedure Step1 Decide on the PKey to be used in the subnet valid values can be 0 or any 16 bit unsigned value The actual PKey used is a 16 bit number with the most significant bit set For example a value of 0 will give a PKey with the value 0x8000 Step 2 Create a child interface by running mosti echo Plor sy ys less mer IB sulbbimieriace gt cxeace emi el Fxample host1 echo 0 gt sys class net ib0 create child This will create the interface 1b0 8000 Step 3 Verify the configuration of th
31. 2 8 0000 MHGH28 XTC A4 A7 ini PSID MT 04A0140005 I Generating image Current BW version on flash 2 7 0 New FW version 2 8 0 Burano EN image without signaturest OK Restoring signature OK I Image burn completed successfully Please reboot your system for the changes to take effect warning etc infiniband openib conf saved as etc infiniband openib conf rpmsave In case your machine has the latest firmware no firmware update will occur and the 74 installation script will print at the end of installation a message similar to the following A Installation finished successfully The firmware version 2 8 0600 is up to date Note To force firmware update use force fw update flag Mellanox Technologies 33 od Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation Step 4 Step 5 Step 6 Step 7 Note In case your machine has an unsupported network adapter device no firmware update will occur and the error message below will be printed Please contact your hardware vendor for help on firmware updates Error message I Querying device E Can t auto detect fw configuration file In case the installation script performed firmware updates to your network adapter hardware it will ask you to reboot your machine The script adds the following lines to etc security limits conf for the userspace components such as MPI x soft memlock unlimited x hard memlock unlimited These
32. 3 3 1 IPoIB Configura tion Based on DHCP and is connected to the client machine An initrd file To add an IB driver into init rd you need to copy the IB modules to the diskless image Your machine needs to be pre installed with a Mellanox OFED for Linux ISO image that is appropriate for the kernel version the diskless image will run 212 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Adding the IB Driver to the initrd File Step 1 Step 2 Step 3 The following procedure modifies critical files used in the boot procedure It must be executed by users with expertise in the boot process Improper application of this pro cedure may prevent the diskless machine from booting Back up your current initrd file Make a new working directory and change to it Hest find feno nio INOS eS CCl anto aude a e Normally the initrd image is zipped Extract it using the following command Rosalio ZP ee net sera E Oo The initrd files should now be found under tmp initrd ib Step 4 Create a directory for the InfiniBand modules and copy them hesitate Ellie dado deo io die ale hostla cd lib modules uname r updates kernel drivers Roc Spo rio hacer ed deo dep fn go do ne dell dlo Rosi eo cias ayao come als sore o amo alii oy Lilo modes als aesti GR ae Mosa some we are amo aba crol 9 do mos les aus Nos o nd Oeics sa o Ae ec
33. A Hee AEE AEE aE aaa aaa libm1x4 iat ae at at ae ae aE He A Ae He A Hee AE a aE aE a APE aE Ea aE aaa I E E He ILE IEEE E IE IIE E IEEE libibmad EEE A ae ae aE ae Hee A AEE A AE EA tt tt tot tott rt te tt tt tt ios do EE TE TE AE tt ft tt tt f rt MEE dapl EE IAE TT dapl ERROR ft ae TE tt tt tt tt tt r TEE T nh POLE TIS FEAR ae ae ae ae A Hee A AEE A Hee AEE AEE Ea aE aaa libmverbs iat ae aE at ae aE aE ae A Hee A Hee A He eA AE a AEE a aE aaa aaa ofed scripts it at TE ae at ae ae aE ae TE Ae eA Ae eA E E TE E EAE EE E E E E E E E E E E E E E E EEEE RE libibverbs devel i TE ae T AE EAE a AEE aa aa aaa libibverbs devel static iat ae aE at ae at Hee AE He eA HEE A AE E AE EAE aa aaa aa aaa aaa libibverbs devel static iat ae aE at ae at He He E HE eA HE EA HEE aE a AEE L aa aaa lib1bverbs ut1ls iat ae ae at ae at He He AE Hee A HEE A Hee AE EAE a aE aa aaa aaa aaa libmthca iat ae ae at ae ae ae ae A Ae eA He EA AE EAE EAE stata aaa libmthca devel static iat ae a at ae at He UE Hee A AE EA HE TEA libmthca devel static iat ae ae at ae a Ae He A Ae eA Hee A He EA ETE 30 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 libmlx4 itt ae at at ae aE at ae Ae Hee A RARA libmlx4 devel it at Ht Ht a Ai HANN I I rtfFEt ttI r r TT libmlx4 devel tat Ht ae a at 0 mm Aa tb amp libmverbs devel iat ae at at OOOO libmverbs devel iat
34. Default 0 base on the CCT cal culation on the current subnet size Table 8 Congestion Control Manager Switch Options File threshold Indicates how aggressive the congestion mark 0 0xf ing should be e 0 no packet marking e Oxf very aggressive Default Oxf marking rate The mean number of packets between marking eligible Values 0 Oxffff packets with a FECN Default Oxa packet size Any packet less than this size bytes will not be marked Values 0 0x3 fc0 with FECN Default 0x200 Table 9 Congestion Control Manager CA Options File port control Specifies the Congestion Control attribute for this port Values e 0 QP based congestion control e 1 SL Port based congestion con trol Default 0 ca control map An array of sixteen bits one for each SL Each bit indicates Values Oxffff whether or not the corresponding SL entry is to be modi fied Sets the CC Table Index CCTI increase Default 1 trigger threshold Sets the trigger threshold Default 2 Sets the CC Table Index CCTI minimum Default 0 cct Sets all the CC table entries to a specified value The first Values lt comma separated list gt entry will remain 0 whereas last value will be set to the rest Default 0 of the table When the value is set to 0 the CCT calculation is based on the number of nodes 160 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Tab
35. E OK OR NOS S TTI a L SANT DERI OK OU AO nO a e DR Oi REER HER R R O SA 0030070980 DDR st OK OASIS A a On O OK 0x0007f0b0 0x0007f0fb 0x00004c Jump addresses OK AVRO 0007207030000 Nn tau ae tony nok FW image verification succeeded Image is bootable 8 16 ibv_asyncwatch Applicable Hardware All InfiniBand devices Description Display asynchronous events forwarded to userspace for an InfiniBand device Synopsis HOY as ynewat h Examples 1 Display asynchronous events gt lbv asyncwatch mAT O aS yne eront RD 8 17 ibdump Applicable Hardware Mellanox ConnectX ConnectX 2 adapter devices Description Dump InfiniBand traffic that flows to and from Mellanox Technologies ConnectX ConnectX 2 adapters InfiniBand ports The dump file can be loaded by the Wireshark tool for graphical traffic analysis The following describes a work flow for local HCA adapter sniffing e Run ibdump with the desired options Mellanox Technologies 197 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities e Run the application that you wish its traffic to be analyzed e Stop ibdump CTRL c or wait for the data buffer to fill in mem mode e Open Wireshark and load the generated file How to Get Wireshark Download the current release from www wireshark org for a Linux or Windows environment See the ibdump release notes txt file for more details 7 4 Although ibdump
36. Flags and Options sarai at 174 ibportstate Flags and Options 10 Ai eh e 176 ibportstate Flags and Options 180 smpquery Flags and Options 3 rai EI 184 pertquery Flagsand ODIOS 44444 K 6 delat er ahh IT ALTA 188 ibeheckerrs Flagsand Options 34 423 EE 191 RTE 8 HLT ii AS A A AAA AA AA age 194 MSH Command asada ta ns eae 195 des siriaca Sine a ek ee at dk ww ii he andes 198 Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Revision History Rev 1 5 2 2 1 0 March 03 2011 e New version of MLNX_OFED no changes to this document Rev 1 5 2 October 16 2010 e Complete reorganization of the document s chapters e Removed section Section 10 NFSoRDMA on page 86 e Added Section 3 9 Atomic Operations on page 95 and its subsections e Updated Section 2 3 Installing Mellanox OFED on page 25 e Removed ibspark tool e Added Section 7 5 7 Torus 2QoS Routing Algorithm on page 136 Rev 1 5 1 3 September 16 2010 e Added Section 5 1 2 Firmware Dependencies on page 61 e Updated Section 5 1 7 Reading Port Counters Statistics on page 63 e Updated Section 4 1 Port Type Management on page 97 e Added Section 3 2 2 4 Enabling Disabling FCoE Services on page 51 Rev 1 5 1 2 July 04 2010 e Updated Figure 1 Mellanox OFED Stack on page 19 Rev 1 5 1 1 May 18 2010 e Added Section 5 1 9 Configuring DAPL over RoCE on page 69
37. For the Mellanox OFED for Linux package it is recommended to have IPoIB use the same format that FlexBoot uses for this client identifier see Section A 2 4 Configuring the DHCP Server on page 203 DHCP Server In order for the DHCP server to provide configuration records for clients an appropriate configu ration file needs to be created By default the DHCP server looks for a configuration file called dhcpd conf under etc You can either edit this file or create a new one and provide its full path to the DHCP server using the cf flag See a file example at docs dhcpd conf of The DHCP server must run on a machine which has loaded the IPoIB module To run the DHCP server from the command line enter dhcpd lt IB network interface name gt d Example Mellanox Technologies 85 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features Roselle paia Udi DHCP Client Optional 7 4 A DHCP client can be used if you need to prepare a diskless machine with an 7 IB driver See Step 8 under Example Adding an IB Driver to initrd Linux ha In order to use a DHCP client identifier you need to first create a configuration file that defines the DHCP client identifier Then run the DHCP client with this file using the following command aliciente lt elient Coni nile IB network inmnteriace name gt Example of a configuration file for the ConnectX PCI Device ID 26428 called ahelrent con
38. IT Managers the choice to boot from a remote storage target iSCSI target or a LAN target Ethernet Remote Boot Server using a single ROM image on Mellanox ConnectX products FlexBoot is based on the open source project Etherboot gP XE available at http www etherboot org FlexBoot first initializes the adapter device senses the port protocol Ethernet or InfiniBand and brings up the port Then it connects to a DHCP server to obtain its assigned IP address and net work parameters and also to obtain the source location of the kernel OS to boot from The DHCP server instructs FlexBoot to access the kernel OS through a TFTP server an iSCSI target or some other service For an InfiniBand port Mellanox FlexBoot implements a network driver with IP over IB acting as the transport layer IP over IB is part of the Mellanox OFED for Linux software package see www mellanox com gt Products gt InfiniBand VPI SW Drivers The binary code is exported by the device as an expansion ROM image A 1 1 Supported Mellanox Adapter Devices and Firmware The package supports all ConnectX ConnectX 2 network adapter devices and cards It also supports the InfiniHost HI Ex and InfiniHost Lx adapter devices and cards Specifically adapter products responding to the following PCI Device IDs are supported ConnectX Connectx 2 devices e Decimal 25408 Hexadecimal 6340 e Decimal 25418 Hexadecimal 634a e Decimal 26418 Hexadecimal 6
39. LLink down TK 0 TXE 0 RK 0 RXE 0 Link status Not connected 0x38086001 aiting for link up on net ok Placing Client Identifiers in etc dhcpd conf The following is an excerpt of a etc dhcpd conf example file showing the format of represent ing a client machine for the DHCP server host hostl next server 11 14 31 filename pxelinux 0 fixed address AS 130 option dhcp client identifier fro 00 00 00 00 02 00 00 022 69 00 00 02 c9 03 00 00510 3957 A 2 4 2 For InfiniHost Ill Family Devices PCI Device IDs 25204 25218 When a FlexBoot client boots it sends the DHCP server various information including its DHCP client identifier This identifier is used to distinguish between the various DHCP sessions The value of the client identifier is composed of 21 bytes separated by colons having the follow ing components 20 lt QP Number 4 bytes gt lt GID 16 bytes gt 7 4 Bytes are represented as two hexadecimal digits di Extracting the Client Identifier Method The following steps describe one method for extracting the client identifier Step1 QP Number equals 00 55 04 01 for InfiniHost III Ex and InfiniHost II Lx HCAs Step 2 GID is composed of an 8 byte subnet prefix and an 8 byte Port GUID The subnet prefix is fixed for the supported Mellanox HCAs and is equal to fe 80 00 00 00 00 00 00 The next steps explains how to obtain the Port GUID Step 3 To obtain the Port GUID run the fo
40. Lato moc kets alle Os WS eyo bado sel Geis uo ein las es fee Rockstar oem Coie alo Sic Iho y amo eee la ls Ao cule als OSTs 9 airada come als Len iso Glia baie io dio mo Les aus Bocce ep taa loreh come aus ina emis alado Lo Tudo merce te 5 Nee Ua a a o sie eos an Si lso Ploy vate alo o e des Us MOSS co HHE EH SHG come ema Cm so moy WMI doy ile meses aus os Ce ta alo epa come asia teu Ino tame deo Ido eee Nestle eo Meu ie ll core les Emp die eo ao modules us Rocce 69 aloe a ll bed do les emo e T more Les Te IMOEIIES Cj ta oral day le lo Mie leo go see ads as Ole alls Rosi eyo tado slao ho ayas como slo sie lso duo Lai eo alo Ius meet ules ib MOSS OS uta TR mul o aysicuds Aus gola o lso culo viale eS uo Mellanox Technologies 213 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 5 Step 6 Step 7 Step 8 IB requires loading an IPv6 module If you do not have it in your initrd please add it using the following command host1 cp lib modules uname r kernel net ipv6 ipv6e6 ko AG ie eo lado mo Cute To load the modules you need the insmod executable If you do not have it in your initrd please add it using the following command Boce mepa LA MOE Ajo aan TO E If you plan to give your IB device a static IP address then copy ifconfig Otherwise skip this step Mo cor alcoi ale eo mol ico alle bi If you plan to obtain an IP address for the IB device t
41. Linux User s Manual Rev 1 5 2 2 1 0 OPTIONS G lt COUNT gt Mim mumberm of packets tO be sent across each Nk derault 10 SV Enable verbose mode F Provides a report of the fabric qualities t lt topo file gt Specifies the topology file name s lt sys name gt Specifies the local system name Meaningful only if a EODOLOGy title Asics pecuaria i lt dev index gt Specifies the index of the device of the port used to conmest EO the IB fab ONNIN Case ROT MUl TIP e devices orm the local system O lt port num Specialties the Local devices port num used to Connect Eo ERE LETAT re Ohne OIE elaine Species the directory where Reno mau ale ra placed default tmp Ww linn Pasay SP SET ES Ene expected Janik a Ela ZA oA Seems pece denied IL Dump ca ilove pare es OMA O Res acl ghee DO gna SPE Reset all the fabric links pmCounters e PM oheeshh gt Lr any ok Ene Proy bided pm ro greater then TES Provided valne ROIs ate LOS Orea SEKT PS kI pP Opt omiso the eoxeCurLonc OF Eme se ese a T Skip Opere nino Nieves Cis Is ts pe cite 8 Velho uo AZIO Cori Tem los pies eee aso As IL ll SWE lic name We mee Out ehe Quisco yered terpology Into the Given eme sala re Se hil alt E mami to Enea EOL changes Erom the Curent Stacey Or ene D E adire Meme ao da o eS oe reirte Reit nen holds BN ak see qui dor load EAS Opa log ya ho use these tiles vou will mesa to Sel the enyi ronment wae ents ORS aie e TEDO EENT Zoe Ea The di
42. Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Preface This Preface provides general information concerning the scope and organization of this User s Manual It includes the following sections e Section Intended Audience on page 11 e Section Documentation Conventions on page 12 e Section Related Documentation on page 15 e Section Support and Updates Webpage on page 15 Intended Audience This manual is intended for system administrators responsible for the installation configuration management and maintenance of the software and hardware of VPI InfiniBand Ethernet FCoE adapter cards It is also intended for application developers Mellanox Technologies 11 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Documentation Conventions Typographical Conventions Table 1 Typographical Conventions sem pers I Variables for which users supply specific val Italic font ues Emphasized words Italic font These are emphasized words Pop up menu sequences menul gt menu2 gt gt item Note lt text gt This is a note be Warning May result in system f instability Common Abbreviations and Acronyms p f if Table 2 Abbreviations and Acronyms Sheet 1 of 2 Abbreviation Acronym Whole Word Description Capital B is used to indicate size in bytes or multiples of bytes e g IKB 1024 bytes and 1MB 1048576 bytes
43. NIC ES Markets DS Linux GEE OF ED in Linux Currently not supported by Mellanox OFED Applications MO OFED The following sub sections briefly describe the various components of the Mellanox OFED stack 1 4 1 mthca HCA IB Driver mthca is the low level driver implementation for the following Mellanox Technologies HCA InfiniBand devices InfiniHost InfiniHost III Ex and InfiniHost III Lx 1 4 2 mlx4 VPI Driver mlx4 is the low level driver implementation for the ConnectX and ConnectX 2 adapters designed by Mellanox Technologies ConnectX ConnectX 2 can operate as an InfiniBand adapter as an Ethernet NIC or as a Fibre Channel HBA The OFED driver supports InfiniBand and Ether Mellanox Technologies 19 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Mellanox OFED Overview net NIC configurations To accommodate the supported configurations the driver is split into four modules mlx4_core Handles low level functions like device initialization and firmware commands processing Also controls resource allocation so that the InfiniBand and Ethernet functions can share the device without interfering with each other mix4_ib Handles InfiniBand specific functions and plugs into the InfiniBand midlayer mlx4_en A 10GigE driver under drivers net mlx4 that handles Ethernet specific functions and plugs into the netdev mid layer mlx4_fc Handles the FCoE functions using ConnectX ConnectX 2 Fibre Channel hardware
44. OOO ZARGA ZI Vendor TD 000Zc9 device ID 005a44 TORE SAO IRR LSI Storage Systems SRP Driver 200400a0b81146a1 service entries 1 senato 0200400008141 RESTO 2 00 400 061 b To detect all the SRP Targets reachable by the SRP Initiator via another umad device use the fol lowing command ibsrpdm d lt umad device gt 2 Assistance in creating an SRP connection a To generate output suitable for utilization in the echo command of Section 3 5 2 2 add the c option to ibsrpdm TO TEONE E Sample output IOTER 200100 AUB o MA A METO C e EIT H oA S O OOE O E 21 RE O A H esere 00700203 TIS al 68 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 b To establish a connection with an SRP Target using the output from the libsrpdm c exam ple above execute the following command SOMA MO A O ET o ei Ze E RT dgid fe800000000000000002c90200402bd5 pkey ffff sis eo eS Eee ET iene ao toe The SRP connection should now be up the newly created SCSI devices should appear in the listing obtained from the fdisk 1 command srp_daemon The srp daemon utility is based on ibsrpdm and extends its functionality In addition to the ibsrpdm functionality described above srp daemon can also e Establish an SRP connection by itself without the need to issue the echo command described in Section 3 5 2 2 e Continue running in bac
45. OpenSM may be run on the same host running the DHCP server but it is not manda tory For details on OpenSM see OpenSM Subnet Manager on page 113 A 4 TFTP Server When you set the filename parameter in your DHCP configuration file to a non empty filename the client will ask for this file to be passed through TFTP For this reason you need to install a TFTP server Mellanox Technologies 207 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 A S A 6 A 6 1 A 6 2 BIOS Configuration The expansion ROM image presents itself to the BIOS as a boot device As a result the BIOS will add to the list of boot devices MLNX FlexBoot lt ver gt for a ConnectX device or gPXE for an InfiniHost III device The priority of this list can be modified through BIOS setup Operation Prerequisites e Make sure that your client is connected to the server s e The FlexBoot image is already programmed on the adapter card see Section A 2 e Start the Subnet Manager as described in Section A 3 e The DHCP server should be configured and started see Section 9 3 3 1 IPoIB Con figuration Based on DHCP on page 93 e Configure and start at least one of the services iSCSI Target see Section A 9 and or TFTP see Section A 4 Starting Boot Boot the client machine and enter BIOS setup to configure MLNX FlexBoot for ConnectX family or gPXE for InfiniHost III family to be the first on th
46. Requirements Platforms e A server platform with an adapter card based on one of the following Mellanox Tech nologies InfiniBand HCA devices MT25408 ConnectXe 2 VPI IB EN FCoE firmware fw ConnectX2 MT25408 ConnectX VPI IB EN FCoE firmware fw 25408 MT25208 InfiniHoste III Ex firmware fw 25218 for Mem Free cards and fw 25208 for cards with memory MT25204 InfiniHost II Lx firmware fw 25204 MT23108 InfiniHost firmware fw 23108 7 4 For the list of supported architecture platforms please refer to the Mellanox OFED Release Notes file Ad Required Disk Space for Installation e 400 MB 24 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Device ID 4 For the latest list of device IDs please visit Mellanox website ha 2 1 2 Software Requirements Operating System e Linux operating system S For the list of supported operating system distributions and kernels please refer to the Mellanox OFED Release Notes file ha Installer Privileges e The installation requires administrator privileges on the target machine 2 2 Downloading Mellanox OFED Step 1 Verify that the system has a Mellanox network adapter HCA NIC installed by ensuring that you can see ConnectX or InfiniHost entries in the display The following example shows a system with an installed Mellanox HCA hostel lspci v orep Mellanox 02 0
47. Service Connected Targets e Time Zone n Portal Address Target Name Start Up Installation 10 4 3 7 3260 1 qn 2007 08 7 3 4 10 iscsiboot manual e Installation Summary e Perform Installation Configuration Root Password e Hostname e Network e Customer Center e Online Update e Service e Users e Clean Up Release Notes e Hardware Configuration Log Out Toggle StartUp Help Abort Finish Step 8 Select New Installation then click Finish in the Installation Mode window Preparation Y Language Y License Agreement Disk Activation gt System Analysis e Time Zone Installation Mode Installation e Installation Summary e Perform Installation Select Mode Configuration s 0 New Installation e Root Password e Hostname e Network e Customer Center e Online Update e Service e Users e Clean Up e Release Notes e Hardware Configuration Help Abort 224 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Step 9 Select the appropriate Region and Time Zone in the Clock and Time Zone window then click Finish Preparation Language w License Agreement Disk Activation E Clock and Time Zone Release Notes Hardware Configuration System Analysis Region Time Zone Time Zone Furope Alaska Aleutian Installa
48. Utilities DERE A T 0x634a A Re A A ER REA St 0x000000a0 A eni Ra IL MEM A RR a Cp CLOG ZO 8 13 perfquery Applicable Hardware All InfiniBand devices Description Queries InfiniBand ports performance and error counters Optionally it displays aggregated coun ters for all ports of a node It can also reset counters after reading them or simply reset them Synopsys pese csi ER Mea AS R e cas gt A a L RS e S T HSH EI Table 19 lists the various flags of the command Table 19 perfquery Flags and Options Default Specified h help Optional Print the help menu d ebug Optional Raise the IB debug level May be used several times for higher debug levels ddd or d d d G uid Optional Use GUID address argument In most cases it is the Port GUID Example 0x08f1040023 Optional Apply query to all ports t Optional Override the default timeout for the solicited MADs lt timeout_ms gt msec Optional Show version info 188 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 19 perfquery Flags and Options Optional Perant P If Not Description Mandatory i Specified lt lid guid gt Optional LID or GUID port reset_ma sk Examples periquery 32 1 read performance counters and reset perfquery e r 32 1 read extended performance counters and reset perrgquery R 0x20 1 recet pertormance co
49. aa aa opensm devel iat ae aE at ae ae ae ae Ae eA Hee AEE AE ter ETE opensm static itt ae ae at ae ae aE ae A He ae A HEE A He EA AEE AEE AE a aE aaa E Mellanox Technologies 31 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation opensm static iat ar at at ae ae aE ae a Hee E ARIE compat dapl ERRORI RIA A A AIR compat dapl AE at ae ae ae ae a Ae eA HE eA AEE AE EAE EE TEA compat dapl devel itt Ht tt tt tot ee Ht at ae ae He OH eee HE aE RR EA a rr tr H H compat dapl devel itt Ht tt Hote He Ht Ht aE ae He HO Hee HEHE aE ao RO a a SESE EE Ea dapl devel iat at ae at ae ae ae ae Ae He A Ae eA AE EAE EAE EE aa aaa dapl devel iat at ae at ae ae ae ae Ae He A Ae EA AEE AE EAE EAE aaa aaa dapl d vel stat ic HEE HH HH HH HH EEE HH HE HH EE EE HH HE HEE EH EE HE HEE EH HE H dapl devel statiuc HEE HH HH HH HH EE EH HH HH EE EH HH EH EE EH EE EE HEE HH HEHH dopi ut 16 gs itt ae at at ae ae at ae a Hee A Hee A Ae EA a aa aa eee perftest iit at a at ae ae ae ae tet EA AE EAE AEE EEE aaa me th em iat ae ae at ae ae aE ae Ae He A tr He EA AEE AEE aE aaa Tete iat ae at at ae ae at ae A Hee A AEE A Ae E a aE Ea aE aaa aaa eee sdpnetstat it at Ht ae at ae ae ae ae a Ae eA Hee A RE EAE EE a aE aaa srptools it at He at at ae ae ae ae a Hee A Hee A Ae EA AEE A AEE Ea aE aaa ae mas tools iat ae aE tr aE ae A He Z Hee A Ae EA AE a EEE TORELL ke iat ae at at ae aE aE ae a He eA AEE A AE a aE aE a AEE aaa E tott a a a E SS
50. add a call to the DHCP client in the init file after loading the IB modules For example sbin dhelient cf sbin dhclient conf ibl Save the init file Close initrd MOSSO Acito H E e ale Moct e T EO ah vinta O O e EE alloy sling NO Sie Won Zor E rig At this stage the modified initrd including the IB driver is ready and located at tmp new init ib img gz Copy it to the original initrd location and rename it prop erly A 8 2 Case ll Ethernet Ports The Ethernet driver requires loading the following modules in the specified order see the exam ple below e mlx4 core ko e mlx4 en ko A 8 2 1 Example Adding an Ethernet Driver to initrd Linux Prerequisites I The FlexBoot image is already programmed on the adapter card 2 The DHCP server is installed and configured as described in Section 9 3 3 1 on page 93 and connected to the client machine 3 Aninitrd file 4 To add an Ethernet driver into initrd you need to copy the Ethernet modules to the disk less image Your machine needs to be pre installed with a MLNX EN Linux Driver that is appropriate for the kernel version the diskless image will run 216 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Adding the Ethernet Driver to the initrd File The following procedure modifies critical files used in the boot procedure It must be executed by users with expertise in th
51. adpater ports 14 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Related Documentation Table 4 Reference Documents InfiniBand Architecture Specification Vol 1 Release 1 2 1 IEEE Std 802 3ae 2002 Amendment to IEEE Std 802 3 2002 Document PDF SS94996 Fibre Channel BackBone 5 standard for Fibre Channel over Ethernet Document INCITS xxx 200x Fibre Channel Backbone Firmware Release Notes for Mellanox adapter devices MFT User s Manual MFT Release Notes The InfiniBand Architecture Specification that is provided by IBTA Part 3 Carrier Sense Multiple Access with Collision Detec tion CSMA CD Access Method and Physical Layer Spec ifications Amendment Media Access Control MAC Parameters Physical Layers and Management Parameters for 10 Gb s Operation http www t11 org draft See the Release Notes PDF file relevant to your adapter device under docs folder of installed package Mellanox Firmware Tools User s Manual See under docs folder of installed package Release Notes for the Mellanox Firmware Tools See under docs folder of installed package Support and Updates Webpage Please visit http www mellanox com gt Products gt IB VPI SW Drivers for downloads FAQ trou bleshooting future updates to this manual etc Mellanox Technologies 15 Mellanox Technologies Confidential R
52. ae A ae at Hee AE AE rr tt A HE EAE EAE aa aaa aa tt tt aaa libmge EEE tt ae ae Ae tt tt tt at ret tt tt tt tet tt dt libmge iat EE tr tt tt tt A AE EA tet mo Ett aa tr tt istort seg FEAT libibcm devel tat Ht He eat HE HE E ae ae E HE TE ae E E HE r aE EE eae oe libibcm devel iit Ht Ht a at He He a ae ae ae Ae ae aE Ae aE mn I aE libibumad devel Ht Ht H Ht Ht Ht HH tH tH EH EH EH tH EH HE HE HT HF HE HE HE HE HH FH TTT libibumad static Et OOOO libibumad static tat ae ae at ae dt He He A He He tt EAE EAE a EE aE aaa aaa libibmad devel at Ht Ht a at He He a Ae ae ae Ae ae ae ae ae a AEE aE EAE PoE ae libibmad devel iat Ht Ht a at He He ae ae ae ae Ae ae aE AEE aE AEE aE EAE aE aoe libibmad static Ht HH OR HH FH tH FE HE HE HE HF HE OO EE tH EE libibmad static ROR Or HH FH HH FE tH FF HE HF HE HF HE HEF OO tH HF ibsim iat ae aE at ae ae ae ae Ae He A Hee A Hee tet AEE Ea aE aaa eee librdmacm utils ERIE Ae Hee AE Hee A HEE A AE EAE a AEE TEE librdmacm devel itt ae ae at ae a Ae He A He eA Hee A Ae eA AE EAE T librdmacm devel it at ae ae at ae at He EE Hee A Ae EAE EAE a aE aaa aaa aaa IS dj EE at ae ae ae ae a Hee Ae eA AE EA AE EAE EE aa aaa libsdp devel iit ae ae at ae ae ae ae A Hee tt A AE EA AE EAE EE aa aaa aa libsdp devel iit ae ae at ae ae ae ae A Ae eA Ae HE A Ae EAE EAE EEE opensm tat ae ae at ae ae ae ae A Ae eA Hee A He eA AEE AEE aE aaa aE opensm devel iat at ae a ae a Hee A He eA He EA AEE A AE EE a aE aa
53. authorized keys2 Simio e O OZ e Step 5 Test hostl1 ssh host2 uname LINUX 6 3 MPI Selector Which MPI Runs Mellanox OFED contains a simple mechanism for system administrators and end users to select which MPI implementation they want to use The MPI selector functionality is not specific to any MPI implementation it can be used with any implementation that provides shell startup files that correctly set the environment for that MPI The Mellanox OFED installer will automatically add MPI selector support for each MPI that it installs Additional MPI s not known by the Mellanox OFED installer can be listed in the MPI selector see the mpi selector 1 man page for details Note that MPI selector only affects the default MPI environment for future shells Specifically 1f you use MPI selector to select MPI implementation ABC this default selection will not take effect until you start a new shell e g logout and login again Other packages such as environment modules provide functionality that allows changing your environment to point to a new MPI implementation in the current shell The MPI selector was not meant to duplicate or replace that functionality The MPI selector functionality can be invoked in one of two ways 1 The mpi selector menu command This command is a simple menu based program that allows the selection of the system wide MPI usually only settable by root and a per user MPI selection It also shows what t
54. configure and manage one or more PXE port network interfaces Each port is assigned a network interface called neti where i is 0 1 2 lt of interface gt Some commands are general and are applied to all network inter faces Other commands are port specific therefore the relevant network interface is specified in the command A 7 3 Command Reference A 7 3 1 ifstat Displays the available network interfaces in a similar manner to Linux s ifconfig gPXE gt ifstat nett 00 02 c9 00 00 060 aa bc on PC102 00 0 closed Link down TK 0 THE RX B RXE 0 Link status Unknown neti 00 02 c9 001 12 35 on PCIOZ 90 0 closed Link down TX 0 TKE 5 RxX 0 RXE 0 Link status Unknown Ox1a066001 J qPxE gt A 7 3 2 ifopen Opens the network interface net lt x gt The list of network interfaces is available via the ifstat com mand Example 210 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 gPXE gt ifopen netl A 7 3 3 ifclose Closes the network interface net lt x gt The list of network interfaces is available via the ifstat com mand Example gPXE gt ifclose netl A 7 3 4 autoboot Starts the boot process from the device s A 7 3 5 sanboot Starts the boot process of an iSCSI target Example Siae SS QU SOLO SOS is O AA OI BE I oa KD LR ESTE A 7 3 6 echo Echoes an environment variable Example
55. errors All errors reported in this second file should be treated as indicators of IB fabric health issues Note that when a fatal and non recoverable error occurs opensm will exit Both log files should include the message SUBNET UP if opensm was able to setup the subnet correctly 7 2 1 opensm Syntax opensm OPTIONS where OPTIONS are version Prints OpenSM version and exits a CORE po ea rae The Mame ot the OpensM contig file When hot specified etc opensm opensm conf will be used if exists Mellanox Technologies 113 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 114 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Note that OpenoM version 3 2 5 and below used the default valus Ir Tm a host BYTE cider it ls shied now ut you May Need Ends OLEON Eo dmberoperare wich old OpenSM running on a little endian machine nola ie TRS RO EOS RE SM IEC rea sua R E end nodes Specifying r on a running subnet IRIS BUE SSD LIE Wrehout r Open oM attempres to preserve existing LID assignments resolving multiple use of same LID SS OME INS Skokie a SIN Ce mc TS aie iS LMS COPEN Chooses routing engines Lo ruse as teca or era lr Min Hop algorithm Multiple routing engines can be specified Separate by Commas SO Blick pee mios regio eno algorithms willie be tried anioni engines fall i ose O near a
56. eth0 LAN INTERFACE ib0 eth0 IPADDR ib0 11 4 NEO 5 255050 NETWORK ib0 11 4 0 0 DROADOASIE Y A ASS CE COL Tote I Based on the first eth lt n gt interface that is found for n 0 1 tea ne replaced niih a Corresponding octet rom G E LAN INTERFACE ib0 IPADDR ib0 11 4 x NENAS O A SO NETWORK ib0 11 4 0 0 PROADCA OTE A A ONBOOT_ib0 1 3 7 3 3 Manually Configuring IPoIB 4 This manual configuration persists only until the next reboot or driver restart Ai To manually configure IPoIB for the default IB partition VLAN perform the following steps Mellanox Technologies Sf Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 3 7 4 3 7 4 1 Step 1 To configure the interface enter the ifconfig command with the following items x The appropriate IB interface 1b0 1b1 etc H The IP address that you want to assign to the interface X The netmask keyword X The subnet mask that you want to assign to the interface The following example shows how to configure an IB interface Mos SAR E O mato o AS ne me 2s AS 00 Step 2 Optional Verify the configuration by entering the ifconfig command with the appropriate interface identifier ib argument The following example shows how to verify the configuration nos elote onto 100 DO ine ne apSUNSEECOEN ddr 30 00014204 RESSE 00300 002000000 ELE 90 00 pei eee E SZ Ml O UP BROADCAST MULTICAST MTU 65520 Metric 1 RX packets 0 errors
57. existent switches will be skipped Multicast is not affected by file routing engine this uses min hop tables Mellanox Technologies 131 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 7 5 2 Min Hop Algorithm The Min Hop algorithm is invoked by default if no routing algorithm is specified It can also be invoked by specifying R minhop The Min Hop algorithm is divided into two stages computation of min hop tables on every switch and LFT output port assignment Link subscription is also equalized with the ability to override based on port GUID The latter is supplied by 1 equalize 1gnore guias t1le gt ignore guids lt equalize ignore guids file gt This option provides the means to define a set of ports by quias that will be ignored by the link load equalization algorithm LMC awareness routes based on remote system or switch basis 7 5 3 UPDN Algorithm The UPDN algorithm is designed to prevent deadlocks from occurring in loops of the subnet A loop deadlock is a situation in which it is no longer possible to send data between any two hosts connected through the loop As such the UPDN routing algorithm should be used if the subnet is not a pure Fat Tree and one of its loops may experience a deadlock due for example to high pressure The UPDN algorithm is based on the following main stages I Auto detect root nodes based on the CA hop length from any switch in the sub
58. fabric health Both log files should include the message SUBNET UP if opensm was able to setup the subnet correctly 4 If a fatal non recoverable error occurs opensm exits di 7 2 4 1 Running OpenSM As Daemon OpenSM can also run as daemon To run OpenSM in this mode enter hostl etc init d opensmd start Mellanox Technologies 123 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 1 3 1 3 1 osmtest Description osmtest is a test program for validating the InfiniBand Subnet Manager and Subnet Administrator osmtest provides a test suite for opensm It can create an inventory file of all available nodes ports and PathRecords including all their fields It can also verify the existing inventory with all the object fields and matches it to a pre saved one See Section 7 3 2 osmtest has the following test flows e Multicast Compliancy test e Event Forwarding test e Service Record registration test e RMPP stress test e Small SA Queries stress test Syntax osmtest OPTIONS where OPTIONS are erano TES E ELON falce STO SMECSEREO RIT Pe E Rao atto conan c create an inventory file with all nodes ports and paths ane run adorna nese MPEG EE inventory v only validate the given inventory file SKA TURN Service egusturtron dercgistratton amd lease TEST e run event forwarding test idro odierne pepe Emo de m milercast flow ef US oO io Ano EUR H
59. full advantage of the protocol offload and RDMA features provided by the InfiniBand architecture SRP allows a large body of SCSI software to be readily used on InfiniBand architecture The SRP Initiator con trols the connection to an SRP Target in order to provide access to remote storage devices across an InfiniBand fabric The SRP Target resides in an IO unit and provides storage services Section 3 5 2 describes the SRP Initiator included in Mellanox OFED for Linux This package however does not include an SRP Target 3 5 2 SRP Initiator This SRP Initiator is based on open source from OpenFabrics www openfabrics org that imple ments the SCSI RDMA Protocol 2 SRP 2 SRP 2 is described in Document T10 1524 D avail able from http www t10 org The SRP Initiator supports e Basic SCSI Primary Commands 3 SPC 3 www t10 org ftp t10 drafts spe3 spe3r21b pdf e Basic SCSI Block Commands 2 SBC 2 www t10 org ftp t10 drafts sbc2 sbc2r16 pdf e Basic functionality task management and limited error handling 3 5 2 1 Loading SRP Initiator To load the SRP module either execute the modprobe ib srp command after the OFED driver is up or change the value of SRP LOAD in etc infiniband openib conf to yes 7 4 For the changes to take effect run etc init d openibd restart srp sg tablesize This is the maximum number of gather scatter entries per I O S When loading the ib srp module it is possible to set the module param
60. is a Linux application the generated pcap file may be analyzed on either operating system Synopsis To dump oro e ETH Table 23 lists the various flags of the command Table 23 ibdump Options Optional Su TEER If Not Description 9 Specified d ib dev lt dev gt Optional First device Use IB device lt dev gt found b max burst lt log2 Optional 12 4096 entries log2 of the maximal burst size that can be captured with burst gt no packet loss Each entry takes MTU bytes of memory mem mode lt size gt Optional When specified packets are written to the dump file only after the capture is stopped It is faster than the default mode less chance for packet loss but it uses more memory In this mode ibdump stops after lt size gt bytes are cap tured e Examples Decapsulate port mirroring headers Should be used when capturing RSPAN traffic I Run ibdump gt 1bdump 198 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 199 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Appendix A Mellanox FlexBoot A 1 Overview Mellanox FlexBoot is a multiprotocol remote boot technology FlexBoot supports remote boot over InfiniBand BoIB and Boot over Ethernet BoE Using Mellanox Virtual Protocol Interconnect VPI technologies available in ConnectX adapt ers FlexBoot gives
61. iu a te dea da de zi 93 IS MCIVER e sirio pirolisi oi alare 94 FSAL TPOTB eo kar bd itei A er Sie Delio 94 A I D calciatori 94 S A A mie eee dle Lilo ced au du 94 co A tiara 94 Oo OPS VE FEAS atar ia 95 3 9 Atomic Operations 95 59 1 Enhanced Atomic Operations case otite a ee e 95 3 9 1 1 Masked Compare and Swap MskCmpSwap LL 95 3 9 1 2 Masked Fetch and Add MFetchAdd rss eee 96 Chapters Workitie With VP Lasarte dado 97 4 1 Port Type Management 97 4 2 InfiniBand Driver 98 4 3 Ethernet Driver 98 Fl A lee g pated Sand AN 98 432 doadine the FP ihemet DAVE sacello bol pelea ara 98 45 3 Unldadine the DIVER essa Se ete dee ee deed eo moses acess ds labs 99 4 3 4 Ethernet Driver Usage and Configuration nanana anaana aeaee 99 Chapters Peri Mmmance sisi paid 102 5 1 General System Configurations 102 SEL PCLExpress PCle Capabilities istalla is een det boa wha ph 102 5 1 2 BIOS Power Management Settings 2 4 2 w4s ia ii Sia wan 102 5 1 3 Intel Hyper Threading Technology n a annann n nananana 102 5 2 Performance Tuning for Linux 102 5 2 1 Tuning the Network Adapter for Improved IP
62. max reverse hops With the proper max reverse hops and io guid file values you can ensure full connectivity in the Fat Tree In the scheme above with a max reverse hop of 1 routes will be instanciated between N1 lt gt N2 and N2 lt gt N3 With a max reverse hops value of 2 N1 N2 and N3 will all have routes between them 1 List of compute nodes CNs can be specified by u or cn_guid file OpenSM options 134 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Using max reverse hops creates routes that use the switch in a counter stream way 7 4 This option should never be used to connect nodes with high bandwidth traffic between them It should only be used to allow connectivity for HA purposes or similar AR Also having routes the other way around can cause credit loops 7 5 4 2 Activation through OpenSM e Use R ftree option to activate the fat tree algorithm 4 LMC gt 0 is not supported by fat tree routing If this is specified the default routing algorithm is invoked instead ha 7 5 5 LASH Routing Algorithm LASH is an acronym for LAyered SHortest Path Routing It is a deterministic shortest path routing algorithm that enables topology agnostic deadlock free routing within communication networks When computing the routing function LASH analyzes the network topology for the shortest path routes between all pairs of sources de
63. np ache Alea as we vet ORRO leave alele Jann DIE LZ Phye port ene port 1 SEEN ANTONIA max miu 2048 4 active mtu 20494 S 0 pe ses re 0 pore ime 0 lt 00 als dass de Dort states ZORO max mtu 2048 4 active O o sm los 0 ponle 0 por H EE Mak E H e Notes regarding the command output I The InfiniBand port port 1 is in PORT INIT state and the Ethernet port port 2 is in PORT ACTIVE state You can also run the following commands to obtain the port state Mellanox Technologies 43 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features Cat sve class ion O porre etare LNE Cat Sive class intinivand mlx4 0 7 pores 2 state s ACTLYEK SEN 2 Look at the link layer parameter of each port In this case port 1 is IB and port 2 is Ethernet Nevertheless port 2 appears in the list of the HCA s ports You can also run the following commands to obtain the link layer of the two ports ie lene ee oe Or e ileso Sie EAE POLE vote fica ele nno nea pes 2 nana Ethernet T 3 The firmware version is 2 7 700 appears at the top You can also run the following com mand to obtain the firmware version cat sys class infiniband mlx4 0 fw ver 2o lo TOQ it 4 The IB over Ethernet s Port MTU is 2K byte at maximum however the actual MTU cannot exceed the mlx4 en interface s MTU Since the mlx4 en interface s MTU is 1560 port 2 will run with MTU of 1K Please note that RoCE s MT
64. oS Selo Siae one Cae lal A 7 3 7 dhcp A network interface attempts to open the network interface and then tries to connect to and com municate with the DHCP server to obtain the IP address and filepath from which the boot will occur Example gGPXE gt dahep merl A 7 3 8 help Displays the available list of commands A 7 3 9 exit Exits from the command line interface Mellanox Technologies 211 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 A 8 Diskless Machines Mellanox FlexBoot supports booting diskless machines To enable using an IB ETH driver the remote kernel or initrd image must include and be configured to load that driver This can be achieved either by compiling the HCA driver into the kernel or by adding the device driver module into the initra image and loading it A 8 1 Case l InfiniBand Ports The IB driver requires loading the following modules in the specified order see Section A 8 1 1 for an example ib_addr ko 1b_core ko 1b_mad ko 1b_sa ko 1b_cm ko 1b_uverbs ko 1b_ucm ko 1b_umad ko 1w_cm ko rdma cm ko rdma ucm ko mlx4_ core ko mlx4_ib ko ib_mthca ko ipoib_helper ko this module is not required for all OS kernels Please check the release notes ib ipoib ko A 8 1 1 Example Adding an IB Driver to initrd Linux Prerequisites 1 The FlexBoot image is already programmed on the HCA card 2 The DHCP server is installed and configured as described in Section 9
65. on the same Target HCA there is need for a different initiator ext value on each path The conventions is to use the Target port GUID as the initiator ext value for the relevant path If you use srp daemon with n flag it automatically assigns initiator ext values according to this convention For example id ext 200500A0B81146A1 io0c guid 0002c90200402bec dgid fe800000000000000002c90200402bed pkey fffFf Senvuce TO 700500 A083 Ion TEO rel 400007670700 Notes I It is recommended to use the n flag for all ssp daemon invocations 2 ibsrpdm does not have a corresponding option 3 srp daemon sh always uses the n option whether invoked manually by the user or auto matically at startup by setting SRPHA ENABLE to yes 3 5 2 6 High Availability HA Overview High Availability works using the Device Mapper DM multipath and the SRP daemon Each 1n1 tiator is connected to the same target from several ports HCAs The DM multipath is responsible for joining together different paths to the same target and for fail over between paths when one of them goes offline Multipath will be executed on newly joined SCSI devices Fach initiator should execute several instances of the SRP daemon one for each port At startup each SRP daemon detects the SRP Targets in the fabric and sends requests to the ib srp module to connect to each of them These SRP daemons also detect targets that subsequently join the fabric and send the ib srp mod
66. only effective for large block transfers By setting the sys parameter sdp zcopy thresh toa non zero value a non standard SDP speedup is enabled Messages longer than sdp zcopy thresh bytes in length cause the user space buffer to be pinned and the data to be sent directly from the original buffer This results in less CPU usage and on many systems much higher bandwidth Note that the default value of sdp zcopy thresh is 64KB but is may be too low for some systems You will need to experiment with your hardware to find the best value 3 4 7 Using RDMA for Small Buffers For smaller buffers the overhead of preparing a user buffer to be RDMA ed is too big therefore it is more efficient to use BCopy Large buffers can also be sent using RDMA but they lower CPU utilization This mode is called ZCopy combined mode The sendmsg syscall is blocked until Mellanox Technologies 65 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features the buffer is transfered to the socket s peer and the data is copied directly from the user buffer at the source side to the user buffer at the sink side To set the threshold use the module parameter sdp zcopy thresh This parameter can be accessed through sysfs sys module 1b_sdp parameters sdp zcopy thresh Setting it to 0 disables ZCopy 3 5 SCSI RDMA Protocol 3 5 1 Overview As described in Section 1 4 5 the SCSI RDMA Protocol SRP is designed to take
67. reduce to Dimension Order Routing in certain topologies it is topology agnostic and fares well in the face of faults Mellanox Technologies 135 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager It has been shown that for both regular and irregular topologies LASH outperforms Up Down The reason for this is that LASH distributes the traffic more evenly through a network avoiding the bottleneck issues related to a root node and always routes shortest path The algorithm was developed by Simula Research Laboratory Use R lash Q option to activate the LASH algorithm S QoS support has to be turned on in order that SL VL mappings are used Aa S LMC gt 0 is not supported by the LASH routing If this is specified the default routing algorithm is invoked instead hai For open regular cartesian meshes the DOR algorithm is the ideal routing algorithm For toroidal meshes on the other hand there are routing loops that can cause deadlocks LASH can be used to route these cases The performance of LASH can be improved by preconditioning the mesh in cases where there are multiple links connecting switches and also in cases where the switches are not cabled consistently To invoke this use R lash Q do mesh _analysis This will add an addi tional phase that analyses the mesh to try to determine the dimension and size of a mesh If it deter mines that the mesh looks like an open or closed cartesian
68. settings unlimit the amount of memory that can be pinned by a user space application If desired tune the value unlimited to a specific amount of RAM For your machine to be part of the InfiniBand VPI fabric a Subnet Manager must be running on one of the fabric nodes At this point Mellanox OFED for Linux has already installed the OpenSM Subnet Manager on your machine For details on starting OpenSM see Chapter 7 OpenSM Subnet Manager InfiniBand only Run the hca self test ofed utility to verify whether or not the InfiniBand link is up The utility also checks for and displays additional information such as HCA firmware version Kernel architecture Driver version Number of active HCA ports along with their states Node GUID DH HH H For more details on hca self test ofed see the file hca self test readme under docs hostel USE OL es sell Cesc Oiled SES Per forming InfiniBand HCA Self Test gt Number of HCAs Detected PCI Device Check Kernel Arch 34 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Host Driver Version NAT RO re ean NA LIENS OLE DELL See US OFED 1 5 2 20101014 eZ EA e Host Driver REM Check T oa ae PASS HCA Firmware on HCA 0 T RON LS COO HCA Firmware Check on HCA 0 O NA DA PASS H st Driver Inicialization A AT REI PASS Number of ACA Ports Active AE DITA IE IE all Pore State of Port Fl on HCA PO
69. that uses BridgeX bridge01 eport A10 and VLAN tag 8 all incoming and outgoing traffic on eth23 will use a VLAN tag of 8 This will be enforced by both BridgeX and destination hosts When a packet is passed from the internal fabric to the Ethernet subnet through the BridgeX it will have a true Ethernet VLAN tag of 8 The VLAN implementation used by EoIB uses operating systems unaware of VLANs This is in many ways similar to switch tagging in which an external Ethernet switch adds strips tags on traf fic preventing the need of OS intervention EoIB does not support OS aware VLANS in the form of vconfig Configuring VLANs To configure VLAN tag for a vNic add the VLAN tag property to the configuration file in host administrated mode or configure the vNic on the appropriate vHub in network administered mode In the host administered mode when a vHub with the requested VLAN tag is not available the vNIC s login request will be rejected e Host administered VLAN configuration in centralized configuration file can be modi fied as follow Add vid lt VLAN tag gt or remove vid property for no VLAN e Host administered VLAN configuration with ifcfg ethX configuration files can be modified as follow Add VNICVLAN lt VLAN tag gt or remove VNICVLAN property for no VLAN S Using a VLAN tag value of 0 is not recommended because the traffic using it would not be separated from non VLAN traffic For Host administered vNics VLAN entr
70. the switch at 3 2 1 e the root for a pristine fabric fails Torus 2QoS will generate the following master spanning tree for that case l l 3 2 l I 1 4 K l l y 0 0 1 Z 3 4 5 Assuming the y dateline was between y 4 and y 0 this spanning tree has a branch that crosses a dateline However again this cannot contribute to credit loops as it occurs on a 1D ring the ring for x 3 that is broken by a failure as in the above example 7 5 7 3 Torus Topology Discovery The algorithm used by torus 2QoS to construct the torus topology from the undirected graph repre senting the fabric requires that the radix of each dimension be configured via torus 2QoS conf It also requires that the torus topology be seeded for a 3D torus this requires configuring four switches that define the three coordinate directions of the torus Given this starting information the algorithm is to examine the cube formed by the eight switch locations bounded by the corners x y z and x 1 y 1 z 1 Based on switches already placed into the torus topology at some of these locations the algorithm examines 4 loops of interswitch links to find the one that is consis tent with a face of the cube of switch locations and adds its swiches to the discovered topology in the correct locations Because the algorithm is based on examining the topology of 4 loops o
71. torus while preventing credit loops In the presence of link or switch failures that result in a fabric for which torus 2QoS can generate credit loop free unicast routes it is also possible to generate a master spanning tree for multicast that retains the required properties For example consider that same 2D 6x5 torus with the link from 2 2 to 3 2 failed Torus 2QoS will generate the following master spanning tree 4 3 2 x 1 v 0 x 0 1 2 3 4 5 140 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Two things are notable about this master spanning tree First assuming the x dateline was between x 5 and x 0 this spanning tree has a branch that crosses the dateline However just as for uni cast crossing a dateline on a 1D ring here the ring for y 2 that is broken by a failure cannot con tribute to a torus credit loop Second this spanning tree is no longer optimal even for multicast groups that encompass the entire fabric That unfortunately is a compromise that must be made to retain the other desirable properties of torus 2QoS routing In the event that a single switch fails torus 2QoS will generate a master spanning tree that has no extra turns by appropriately select ing a root switch In the 2D 6x5 torus example assume now that
72. up to the InfiniBand limit of 4K bytes The default Maximum Trans mit Unit MTU for EoIB driver is 1500 bytes To configure EoIB to work with jumbo frames Mellanox Technologies 81 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features I Make sure that the IB HCA and Switches hardware support 4K MTU 2 Configure Mellanox low level driver to support 4K MTU Add bes RCOM du le par amet io Serk 3 Change the MTU value of the vNic for example run itcontig eth meu 4038 S Due to EoIB protocol overhead the maximum MTU value that can be set for the vNic interface is 4038 bytes dai 3 6 4 Advanced EolB Settings 3 6 4 1 Module Parameters The mlx4_vnic driver supports the following module parameters These parameters are intended to enable more specific configuration of the mlx4 vnic driver to customer needs The mlx4 vnic is also effected by module parameters of other modules such as set 4k mtu of mlx4 core This mod ules are not addressed in this section The available module parameters include e tx rings num Number of TX rings use 0 for cores default 0 max 16 e tx rings len Length of TX rings must be power of two default 1024 max 8K e rx rings num Number of RX rings use 0 for cores default 0 max 16 e rx rings len Length of RX rings must be power of two default 2048 max 8K e vnic net admin Network administration enabled default 1 e eport state enforce Bring vNic u
73. use the same Linux Network Scripts semantics with the following exceptions additions e In the bonding master configuration file e g ifcfg bond0 in addition to Linux bond ing semantics use the following parameter MTU 65520 65520 is a valid MTU value only if all IPoIB slaves operate in Connected mode See Section 3 7 2 IPoIB Mode Setting on page 84 and are configured with the same S value For IPoIB slaves that work in datagram mode use MTU 2044 If you do not Al set the correct MTU or do not set MTU at all performance of the interface might decrease e In the bonding slave configuration file e g 1fcfg 1b0 use the same Linux Network Scripts semantics In particular DEVICE 1b0 e In the bonding slave configuration file e g ifcfg ib0 8003 the line TY PE InfiniBand is necessary when using bonding over devices configured with par titions p_key e For RHEL users In etc modprobe conf add the following lines alias bond0 bonding e For SLES users It is necessary to update the MANDATORY DEVICES environment variable in etc sysconfig network config with the names of the IPoIB slave devices e g 1b0 1b1 etc Otherwise bond ing master may be created before IPoIB slave interfaces at boot time It is possible to have multiple IPoIB bonding masters and a mix of IPoIB bonding master and Ethernet bonding master However It is NOT possible to mix Ethernet and IPoIB slaves under the same bonding master
74. validate the port s link width and speed against the peer port Synopsis Ngaere er TS SS lA lao fab es ae sen C col o IN eect o a O o a lt dest Gio jocusin Place uta renta o ae al Table 16 lists the various flags of the command Table 16 ibportstate Flags and Options Default If Not Description Specified Optional Mandatory Optional Raise the IB debug level May be used several times for higher debug levels ddd or d d d Optional Show send and receive errors timeouts and others v erbose Optional Increase verbosity level May be used several times for additional verbosity vvv or v v v EN E Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 16 ibportstate Flags and Options Continued Optional Pera Flag Mandatory If Not Description Specified D irect Optional Use directed path address arguments The path is a comma separated list of out ports Examples 0 self port 0 1 2 1 4 out via port 1 then 2 G uid Optional Use GUID address argument In most cases 1t is the Port GUID Example 0x08 1040023 Optional Use lt smlid gt as the target lid for SM SA queries Optional Use the specified channel adapter or router Optional Use the specified port t Optional Override the default timeout for the solicited MADs lt timeout_ms gt msec lt dest dr path Optional Des
75. which contains entries for the DAPL devices does not contain entries for the DAPL over ROMA CM over RoCE devices To add the missing entries perform the following Step1 Run the ibdev2netdev utility to see all the associations between the Ethernet devices and the IB devices ports Step 2 Add a new entry line according to the format below to the dat conf file for each output line of the ibdev2netdev utility lt IA Name gt u2 0 nonthreadsafe default libdaplofa so 2 dapl 2 0 lt ethX gt lt port gt Parameter Description Example lt IA Name gt The device s IA name The name must ofa v2 ethx be unique lt ethX gt The associated Ethernet device used by eth3 RoCE lt port gt The port number I 48 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 The following is an example of the ibdev2netdev utility s output and the entries added per each output line Example sw419 ibdev2netdev mit OM OE gt gt gt Sua ulss Oh sone Suns Ofa ve eth2 u2 0 nonthreadsare default libdaplofa so 2 dapl 2 0 erh 2 wry Ora v2 eth 702 O nonthreadsare default libdaplofa so 2 dapl 2 0 Terho IT 11 11 3 2 Fibre Channel over Ethernet gt Fibre Channel over Ethernet FCoE is still at beta level in this release ha 3 2 1 FCoE Overview The FCOE feature provided by Mellanox OFED allows connecting to Fibre Channel FC targ
76. while VL4 is effectively turned off 7 6 8 Deployment Example Figure 4 shows an example of an InfiniBand subnet that has been configured by a QoS manager to provide different service levels for various ULPs Mellanox Technologies 153 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager Figure 4 Example QoS Deployment on Traffic class SDP Traffic class Partition A Service level 2 Service level 0 s Policy min 20 BW Policy min 40 ORAZIO gals App A Server App B man N App B Server Service Access Points Traffic class SRP Service Level 1 Traffic class IPoIB Policy min 30 BW Service Level 3 Policy min 10 BW Pa App A Server Virtual Server 7 7 QoS Configuration Examples The following are examples of QoS configuration for different cluster deployments Each example provides the QoS level assignment and their administration via OpenSM configuration files 7 1 1 Typical HPC Example MPI and Lustre Assignment of QoS Levels e MPI Separate from I O load Min BW of 70 e Storage Control Lustre MDS Low latency e Storage Data Lustre OST Min BW 30 Administration e MPI is assigned an SL via the command line hostl mpirun sl 0 e OpenSM QoS policy file 4 In the following policy file example replace OST and MDS with the real port GUIDs hall 154 Mellanox Technologies Mellanox Technologies Confidential
77. 0 Contiourme DAPL over ROCE anteriore etici ee 48 3 2 Fibre Channel over Ethernet 49 SZ HRC OR MOV CVC errado E rra e aer dc 49 322 COR Basic USD es les cree ea Be a dd e e ie 49 S221 FCoE Configuration cerdo e ea 50 32 22 Starine ECOB SEVICE ra dann f rse noga ea aloe Er 50 32 2 3 StOppimo HF COP Service iret daa at heh aos Bae ee eee 51 3 2 2 4 Enabling Disabling FCoE Services rer reser eens 51 Var FCOE Advanceed WUsase er iii ll ili tr Ba tr ae levee hohe ad SI Jad Manta vHBA Controla iia Aaa ei 51 323 2 CreatmevHBAs That Use PPC ia elia ani 52 3 2 3 3 Creating VHBAs That Use Link Pause rr rr ee 52 3 3 Reliable Datagram Sockets 53 Doel SON CIVIC Wit Wise etern etn ba arena 53 3327 RDS ConmouranOnuet nla do a heal piani de eee a 53 3 4 Sockets Direct Protocol 53 IRE EIO a A A A ha Stic Jan ch nes dh Uh Ath 53 3 42 libsdpisodubrani steli a a eae kc E 54 3453 COMMeUrINe SID Ps Lilia ies hee A es he hee ee ee ke ek ee eed 54 3 4 3 1 How to Know SDP Is Working LL 54 3 4 3 2 Monitoring and Troubleshooting Tools o ooooooooooooooooooo 55 344 Environment Variables ci cri alora dialer 57 3 4 5 Converting Socket based Applications n o oana annaa eee 57 346 BZCOPY L Copy Send arta a eve dl ae bra ed oh ahd i a A 65 3 47 Usin
78. 0 PORT 1 and 1s connected to the GW PORT ID 3 without VLAN its unique name will be Moie os ee eth2 ceri You can add your own custom udev rule to use the output of the script and to rename the vNic interfaces automatically To create a new udev rule file under etc udev rules d 61 vnic net rules include the line SUBSYSTEM net PROGRAM sbin mlx4 vnic info u k NAME c 2 UDEV service is active by default however if it is not active run Sia E el When vNic MAC address is consistent you can statically name each interface using the UDEV following rule SUBSYSTEM net SYSFS address aa bb cc dd ee ff NAME ethX For further information on the UDEV rules syntax please refer to udev man pages 3 7 IP over InfiniBand 3 7 1 Introduction The IP over IB IPoIB driver is a network interface implementation over InfiniBand IPoIB encapsulates IP datagrams over an InfiniBand Connected or Datagram transport service The IPoIB driver ib ipoib exploits the following ConnectX ConnectX 2 capabilities e Uses any CX IB ports one or two e Inserts IP UDP TCP checksum on outgoing packets Mellanox Technologies 83 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 3 7 2 3 7 3 e Calculates checksum on received packets e Support net device TSO through CX LSO capability to defragment large datagrams to MTU quantas e Dual operation mode datagram and connected e Large MTU su
79. 020 InfiniBand Mellanox Technologies MT25418 ConnectX 1B DDR PCIe DO ASES TTI Step 2 Download the ISO image to your host The image s name has the format MLNX OFED LINUX lt ver gt lt OS label gt iso You can download it from http www mellanox com gt Products gt IB SW Drivers Step 3 Use the mdSsum utility to confirm the file integrity of your ISO image Run the following com mand and compare the result to the value provided on the download page Rosie mie Ss ian WIND OID JUNO e a 308 Aalst so 2 3 Installing Mellanox OFED The installation script mlnxofedinstall performs the following e Discovers the currently installed kernel e Uninstalls any software stacks that are part of the standard operating system distribu tion or another vendor s commercial stack Mellanox Technologies 29 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation e Installs the MLNX OFED LINUX binary RPMs if they are available for the current kernel e Identifies the currently installed InfiniBand and Ethernet network adapters and auto matically upgrades the firmware 2 3 1 Pre installation Notes e 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 a 74 Pre existing configuration files will be saved with the extension conf saverpm ha e If you need to install Mellanox
80. 0xdc800000 size 0x800000 4 Your InfiniBand device is the one with the postfix pci cr0 In the example listed above this will be dev mst mt 25418 pci cro Step 3 Burn firmware 1 Burning a firmware binary image using mstflint that is already installed on your machine Please refer to MSTFLINT README txt under docs 2 Burning a firmware image from a mlx file using the m1xburn utility that is already installed on your machine 38 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 The following command burns firmware onto the ConnectX device with the device name obtained in the example of Step 2 Pocenia AS QD A II Step 4 Reboot your machine after the firmware burning is completed 2 5 Uninstalling Mellanox OFED Use the script usr sbin ofed uninstall sh to uninstall the Mellanox OFED package The script is part of the ofed scripts RPM Mellanox Technologies 39 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 3 Driver Features 3 1 RDMA over Converged Ethernet 3 1 1 RoCE Overview RDMA over Converged Ethernet RoCE allows InfiniBand IB transport over Ethernet net works It encapsulates IB transport and GRH headers in Ethernet packets bearing a dedicated ether type While the use of GRH is optional within IB subnets it is mandatory when using RoCE Verbs applications written over IB verb
81. 1 x4 parameters C 1 mlx4_core Parameters See Lie Gt ports Lar Globo Tevel 0 Drock locprack 0 default e 1 oe log num mac porse US Std BLH Sae E S bo 0 T T OI Tl TH sere Attempt to set 4K MTU to all Connectx Bnabike debug tracing ii gt 0 default Bilockimu ltaicast loopback Packers ai gt Peete CO USE MSIL log maximum number Enable steering by log maximum number XENO nNZ4ErO of MACs per ETH MEAN Er IOCA ON of QPs per HCA 238 Mellanox Technologies ae Pati is 177 max is 20 Tog numera default is 16 max is 20 E peo default is 4 max is 7 VOGUE default is 16 max is 19 log maximum number of SROs per HCA log log maximum number of COs per HCA Mellanox Technologies Confidential number of RDMARC buffers per QP Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 e o I groups per HCA default us 13 log num mpt tion table entries per HCA OUT tion table segments per HCA Og maximum TUmDer or MULECECaSE maso is 21 log Maxamum number Or Memory prole de ones 173 mex is 20 log maximum number of memory transla default Te 20 max is 20 Ieee mee Pers lo IAS o e es My se Sen ione enable qos the HCA if gt 0 default 0 enc lote cous IM Oe zero default 0 eS Tela ges nee ee None eco detault 1 C 2 mlx4_ ib Parameters depod skewer 0 C 3 mlx4_en Parameters M
82. 2 Either enterthe path io and file name directly Vga Mode or choose by using 0x332 Browse Root Device sets the device topasstothe S kernel as root device 7 Back Abort ok Step 17 If you wish to change additional settings click the appropriate item and perform the changes and click Accept when done Mellanox Technologies 229 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 18 In the Confirm Installation window click Install to start the installation See image below Preparation F Installation Settings Language a 9 w License Agreement Disk Activation l i n an E T E Click any headline to make changes or use the Change menu below Time Zone verve Expert Installation s Installation Sum e Perform Installatii Confirm Installation Configuration Hostname Root Password All information required forthe base installation isnow complete Network Customer Center Online Update If you continue now partitions on your hard disk will be formatted erasing any existing data in those partitions according to the installation settings in the previous dialogs Service Go back and check the settings if you are unsure Users Clean Up Release Notes Hardware Configi E Back install 7 Show Release Mi L A Enea H bs Change PRE e ST Step 19 At the end of the file copying s
83. 2 2 1 0 Driver Features 3 6 Ethernet over IB EolB vNic The Ethernet over IB EoIB mlx4 vnic module is a network interface implementation over InfiniBand EoIB encapsulates Layer 2 datagrams over an InfiniBand Datagram UD transport service The InfiniBand UD datagrams encapsulates the entire Ethernet L2 datagram and its pay load To perform this operation the module performs an address translation from Ethernet layer 2 MAC addresses 48 bits long to InfiniBand layer 2 addresses made of LID GID and QPN This transla tion is totally invisible to the OS and user Thus differentiating EoIB from IPoIB which exposes a 20 Bytes HW address to the OS The mlx4 vnic module is designed for Mellanox s ConnectX family of HCAs and intended to be used with Mellanox s BridgeX gateway family Having a BridgeX gateway is a requirement for using EoIB It performs the following operations e Enables the layer 2 address translation required by the mlx4 vnic module e Enables routing of packets from the InfiniBand fabric to a 1 or 10 GigE Ethernet sub net 3 6 1 Ethernet over IB Topology EoIB is designed to work over an InfiniBand fabric and requires the presence of two entities e Subnet Manager SM The required subnet manager configuration is not unique to EoIB but rather similar to other InfiniBand applications and ULPs e BridgeX gateway The BridgeX gateway is at the heart of EoIB On one side usually referred to as the internal side
84. 2 4 Interrupt Affinity The affinity of an interrupt is defined as the set of processor cores that service that interrupt To improve application scalability and latency it is recommended to distribute interrupt requests IRQs between the available processor cores To prevent the Linux IRQ balancer application from interfering with the interrupt affinity scheme the IRQ balancer must be turned off The following command turns off the IRQ balancer in RedHat gt etc init d irqbalance stop The following command turns off the IRQ balancer in SLES ete ode el Lie los dans stro The following command assigns the affinity of a single interrupt vector gt cino SS cs mesi OO Ao Gite ECCO ay where bit i in lt hexadecimal bit mask gt indicates whether processor core 7 1s in lt irq vector gt s affinity or not 5 2 4 1 Example Script for Setting Interrupt Affinity 7 4 On systems that support NUMA it is recommended to set IRQs from different net work devices to processor cores that reside on different physical CPU sockets Iban CORES S cus Puros cui More processor stelle a 1 srl Il wale GCORES 0 do eo ezio FOREST COREA done Sia Os gt ea proce Areces ae ee aa o sedie Mellanox Technologies 105 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Performance alse IRO O Cae proc neer eoe arep Sl awk need E E Schon Discovered Trden v1 ROS mac kL ARR OS ROS LE ox temes 2
85. 2 Environment Variables The following environment variables control opensm behavior e OSM TMP DIR Controls the directory in which the temporary files generated by opensm are created These files are opensm subnet lst opensm fdbs and opensm mc fdbs By default this directory is var log e OSM CACHE DIR opensm stores certain data to the disk such that subsequent runs are consistent The default directory used is var cache opensm The following file is included in it guid2lid stores the LID range assigned to each GUID 7 2 3 Signaling When opensm receives a HUP signal it starts a new heavy sweep as if a trap has been received or a topology change has been found Also SIGUSRI can be used to trigger a reopen of var log opensm log for logrotate pur poses 7 2 4 Running opensm The defaults of opensm were designed to meet the common case usage on clusters with up to a few hundred nodes Thus in this default mode opensm will scan the IB fabric initialize it and sweep occasionally for changes To run opensm in the default mode simply enter hostl opensm Note that opensm needs to be run on at least one machine in an IB subnet By default an opensm run is logged to two files var log messages and var log opensm log The first file nessage registers only general major events the second file opensm log includes details of reported errors All errors reported in opensm log should be treated as indicators of IB
86. 202 C95 tele cio il RE eee ana T ceg0 0000 0000 0000 0202 6900 0708 66811 According to the output we now have two entries Run the Example Again Now on VLAN On Server a e A POL Local address LID 0500007 OPN Ox0O4QQ4E PSN STG Oe Z G GID KSS UZ 3202 2900 70826799 remote address LID 0x0000 OPN OSOS ODA Pen xe 30s OU CID EES OE N co00 7 03723 Wil S20 E orn Uh seconds e 42 50 Moises UNO thers sm tO Ole seconds ls 56 wsec 1 ver 46 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 On Client CO eolici e L LE local acdcress LID 00000 0 ENO ODA ERE NEO Feste 2025090057108 ses remote address LID 0x0000 OPN 0x04004f PSN 0zbdde2c GITD ISU 2 9 ZU AR STONES EE D TET LT ER T MOCO E in 00l seconds D3 EE ILE Defining Ethernet Priority PCP in 802 1q Headers On Server eD seas CISA ONS CLOR SUC eg al Local address lt LID 0x0000 OPN Ox TL DOT aE PSN Ox9dart6ec GID redd AU OSO remote address LID 0900007 OPN JUS e004 PSN Oxb0a4 oo GID BES Oe S202 O 0s seal 8192000 bytes in 0 01 seconds 4840 89 Mbit sec LOCO ters In GUE seconds 63754 see ker On Client fa ONE COMA eno op len lee e O Local address LID 020000 OPN Ox TL DU st PSN Oxo0a4 Mo GID Peo 9 IDT COU Ty Oe 40 remote address LID Ox0000 OPN ss T DOT aE PSN lt a Eee GID RSS UI 2 TDS 2 6 TSS SHE EHS O bytes am Oi seconds LSO SO Mole S
87. 4 fc Parameters 240 Appendix D ib bonding Driver for Systems using SLES10 SP3 241 D 1 Using the ib bonding Driver 241 Mellanox Technologies T Mellanox Technologies Confidential Rev 1 5 2 2 1 0 List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 8 Mellanox Technologies Typographical Conventions iis ieri lap ea 12 Abbreviations and ACTONYMS 55 423 ii Gace hee AA 12 AN A E H EA EA 14 Referente DOCUS iaa ads te ra re bn ria 15 minxotedinstall Refur Codes 21 A ela ewe es 28 mix4 yme cont KH Toma Ii T ENA 76 Red Hat Linux mlx4 vnic conf file format FI Supported ConnectX Port Configurations onson anaana aeaaaee 97 Recommended PCIe Configuration 23 2244 rita T ra da its 102 USE RTT BO HOR Er sora alert 109 Congestion Control Manager General Options File sees 160 Congestion Control Manager Switch Options File rss rna 160 Congestion Control Manager CA Options File 160 Congestion Control Manager CC MGR Options File o o ooooooo o 161 ibdiagnet of ibutils2 Output Files 165 ibdiagnet of ibutils Output Files ic 34535 4ede Lio aperta pelare 168 Ibdiagpath Ouipul Piles anterio 170 ibv_devinfo Flags and Options 172 ibstatus
88. 6 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 e Two levels of QoS assuming switches support 8 data VLs e Ability to route around a single failed switch and or multiple failed links without introducing credit loops changing path SL values e Very short run times with good scaling properties as fabric size increases 7 5 7 1 Unicast Routing Torus 2QoS is a DOR based algorithm that avoids deadlocks that would otherwise occur in a torus using the concept of a dateline for each torus dimension It encodes into a path SL which datelines the path crosses as follows sl 0 for d 0 nen en n ein Gil neta cos a lt lt el For a 3D torus that leaves one SL bit free which torus 2QoS uses to implement two QoS levels Torus 2QoS also makes use of the output port dependence of switch SL2VL maps to encode into one VL bit the information encoded in three SL bits It computes in which torus coordinate direc tion each inter switch link points and writes SL2VL maps for such ports as follows cor st 0 s1 lt 167 si t7 TE r POr e repor Ea Which aore COO date dre donna SWECON wort AOS ande S S a SIDO OO E UA SS e T R E 4 Thus on a pristine 3D torus 1 e in the absence of failed fabric switches torus 2QoS consumes 8 SL values SL bits 0 2 and 2 VL values VL bit 0 per QoS level to provide deadlock free routing on a 3D torus Torus 2QoS rout
89. 732 e Decimal 26428 Hexadecimal 673c e Decimal 26438 Hexadecimal 6746 e Decimal 26488 Hexadecimal 6778 InfiniHost III Ex devices e Decimal 25218 Hexadecimal 6282 InfiniHost III Lx devices e Decimal 25204 Hexadecimal 6274 200 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 A 1 2 Tested Platforms See the Mellanox FlexBoot Release Notes FlexBoot release notes txt A 1 3 FlexBoot in Mellanox OFED The FlexBoot binary files are provided as part of Mellaox OFED for Linux The following binary files are included I A PXE ROM image file for each of the supported Mellanox network adapter devices Specif ically the following images are included ConnectX ConnectX 2 images ConnectX FlexBoot 25408 ROM lt version gt rom ConnectX FlexBoot 25418 ROM lt version gt rom ConnectX FlexBoot 26418 ROM lt version gt rom ConnectX FlexBoot 26428 ROM lt version gt rom ConnectX FlexBoot 26438 ROM lt version gt rom ConnectX FlexBoot 26488 ROM lt version gt rom where the number after the ConnectX_ FlexBoot_ prefix indicates the corresponding PCI Device ID of the ConnectX ConnectX 2 device InfiniHost III Ex images IHOST3EX PORTI ROM lt version gt rom IB Port 1 HOST3EX PORT2 ROM lt version gt rom IB Port 2 InfiniHost III Lx image HOST3LX ROM lt version gt rom 2 Additional documents under docs d
90. B port or node and reports errors in counters above threshold Check specified port or node and report errors that surpassed their predefined threshold Port address is lid unless G option is used to specify a GUID address The predefined thresholds can be dumped using the s option and a user defined threshold file using the same format as the dump can be specified using the t lt file gt option Synopsis Sener OA Sl ie Rei Nociones Ol RE ST Table 20 lists the various flags of the command Table 20 ibcheckerrs Flags and Options Default Optional If Not Description nae Mandatory Specified Mellanox Technologies 191 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities Table 20 ibcheckerrs Flags and Options Optional Pera Flag Re or If Not Description 7 Specified O ail Print in brief mode Reduce the output to show only if errors are present not what they are Increase verbosity level May be used several times for additional verbosity vvv or v v v Use specified threshold file Optional lt threshold file gt t Optional Override the default timeout for the solicited MADs lt timeout_ms gt G uid Optional Use GUID address argument In most cases 1t is the Port GUID Example 0x08f1040023 msec lt lid guid gt Mandatory with Use the specified port s or node s LID GUID with G G flag option M
91. B ratio In addition to this although the algorithm allows leaf switches to have any number of CAs the closer the tree is to be fully populated the more effective the shift communication pattern will be In general even if the root list is pro vided the closer the topology to a pure and symmetrical fat tree the more optimal the routing will be The algorithm also dumps compute node ordering file opensm ftree ca order dump in the same directory where the OpenSM log resides This ordering file provides the CN order that may be used to create efficient communication pattern that will match the routing tables 7 5 4 1 Routing between non CN Nodes The use of the cn guid file option allows non CN nodes to be located on different levels in the fat tree In such case it is not guaranteed that the Fat Tree algorithm will route between two non CN nodes In the scheme below N1 N2 and N3 are non CN nodes Although all the CN have routes to and from them there will not necessarily be a route between N1 N2 and N3 Such routes would require to use at least one of the switches the wrong way around Spinel Spine2 Spine 3 Fo F le N L ko 7 NI Switch NZ EK e eal N3 FIA AIA cla Sdi A Going down to compute nodes To solve this problem a list of non CN nodes can be specified by G or Y 10 guid file option Theses nodes will be allowed to use switches the wrong way around a specific number of times specified by H or
92. E LOCO atera Inr econas ls uses ter Using rdma cm Tests On Server ucmatose cmatose starting server era tina data he rane completing sends receiving data transters data transfers complete cmatose disconnecting disconnected test complete return status O T Mellanox Technologies 47 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features On Client ucmatose s 20 4 3 219 cmatose starting client cmatose connecting receiving deta transtrers sending replies data transfers complete test complete return Status 0 T This server client run is without PCP or VLAN because the IP address used does not belong to a VLAN interface If you specify a VLAN IP address then traffic should go over VLAN Type Of Service TOS The TOS field for rdma cm sockets can be set using the rdma set option API just as it is set for regular sockets If the user does not set a TOS the default value 0 will be used Within the rdma cm kernel driver the TOS field is converted into an SL field The conversion formula is as follows SL TOS gt gt 5 e g take the 3 most significant bits of the TOS field In the hardware driver the SL field is converted into PCP by the following formula PCP SL amp 7 take the 3 least significant bits of the TOS field Note SL affects the PCP only when the traffic goes over tagged VLAN frames 3 1 10 Configuring DAPL over RoCE The default dat conf file
93. EA e aig gina ken Seas his es sions ici ne Sao ces Enter passphrase empty for no passphrase Enter same passphrase again ie pio asia ae sao Ja Desa seves dd dame Us scenes y Esla ol ese Suns jgptolite ley lacis cossa sense alin Hace seras y Sl wel ieee ole The key fingerprint is 383 L s dd 3083 0034a r0 ea 50 Ota dle Ot Olan lt usernamne gt Nosti Step 2 Check that the public and private keys have been generated HOS tho cc home lt usercname gt ssh hosts 18 hostils ls la oO Gr WS ST Zogno ee Yu CENAS IS AE OO Tock 4006 Mar E a S a a LOC BOSE E o a RR a gt EDO E OO AM ES Ao oo Step 3 Check the public key os loe as lO SiS Eo el AAAAB3NzaC1yc2EAAAABIWAAAQEA1zVY8VBHOhn90kZN70A11bUO74RXm4zHeczyVxpYHaDPy PMI ZEME eC IVZ d ODHAK COTEI VI UOOUR ds IN OGC GIOS ys UE FAR alo O 6mkHLGGqVutfEMmABZ3wNCUg6J2X3G uiuSWXeubZmbXcMrP w4IWByfH8ajwo6A5WioNDFZElbYeeNfPZf4UNcgMOAMWp64sL58tkt32F RGmyLXQOWZL27Sy nsn6dHpxMqBorXNC0ZBe4kTnUgm63n02z1qgVMdL9IFrCmalxI0u9 SQJA wONevaMzFKEHe7Y Hg6YrNfXunfdbEurzB524TpPcrodZ1fC0 lt username gt hostl Step 4 Now you need to add the public key to the authorized keys2 file on the target machine GIS oe nu al UNE T Aeron Eke n 2 lt username gt host2 s pass word Enter password Mos Els 110 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 For a local machine simply add the key to
94. H NE ERROR ft ft tt tt tt tt TE ibdump iit He at at ae ae ae ae Ae eA Hee AE EA AEE AEE Ea aE aaa ick ene hi Gl drags it at ae at at ae at He eA He ae A Hee A Hee A Ae EAE a AEE aaa aaa aaa aperf iat at ae at ae ae ae ae Ae eA Ae eA Hee AE EAE Ea aE aaa mlnxofed docs itt ae at at ae ae aE ae A Hee ARIA AIR mvapich gcc iat ae ae at ae ae ae ae Ae eA AEE A AE EAE EAE EAE a aE aaa aaa mvapich pgi Uh tti openmpi gcc F RR tt ft tt tt tt t tt TEA openmpi pgi it at RN OOOO VINES iat ae ae at ae at Ae He A Hee A HEE A HE EA AEE AE a aE aaa aaa aoe PLS vano TE iat ae ae at ae at He He A AE He A HEE A HEE A AE EA aE aaa aaa aaa ae Io Ree sas ani pe a E E at ae Ae eA Hee A Hee A HE EAE eA aE a AEE aaa aaa aaa 32 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Moe e T o a gee E ae at Hee AE Hee AE Hee A HE eA AE EAE a aE a aE aaa aaa MOLESSES COS RL iat at ae at ae a He He At Hee I o a a oa MONESSES COS Rupees HH HH HHH HEH HE HE EH HE HE OR HEH HF HE FH HF HE FH HEH FF HEH HF HE FF HF HF Device 15b3 634a C2 00r Omini niBand Mellanox Technologies M2534112 TC Connect NVPI Pore O LE DRT LE aE R L aa Link Width 8x Link Speed 2 5Gb s Installation finished successfully Programming A AN muan o dew lst eil Rui crostini den mis e EE ene ate ASIS 230000 i cele tego Zou eo I Querying device 15 Ws altivo oc ea ie ana EI
95. INET SDP or AF INET SDP when calling the socket system call in the source code The value of AF INET SDP is defined in the file sdp _socket h or you can define it inline define AF INET SDP 27 define PF INET SDP AF INET SDP Mellanox Technologies 59 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features You can compile and execute the following very simple TCP application that has been converted explicitly to SDP Compilation Example Server Client 60 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 61 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 62 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 63 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 64 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 printf accepted connection from s u n merino le ento dere enna Rechte neo ese SS E Gio SO O RUE LE pes lt 0 4 Le eros read lec So IRE Eh else if nr 0 printf socket was closed by remote host n prin wre TT pura Mendaro resta Gioele GOS sd SLUTA 0 3 4 6 BZCopy Zero Copy Send BZCOPY mode is
96. MPI 2 implementation by the Open MPI Project e OSU MVAPICH an MPI 1 implementation by Ohio State University These MPI implementations along with MPI benchmark tests such as OSU BW LAT Intel MPI Benchmark and Presta are installed on your machine as part of the Mellanox OFED for Linux installation Table 6 lists some useful MPI links Table 6 Useful MPI Links MPI Standard http www unix mes anl gov mpi Open MPI http www open mp1 org MVAPICH MPI http mvapich cse ohio state edu MPI Forum http www mpi forum org This chapter includes the following sections e Prerequisites for Running MPI page 109 e MPI Selector Which MPI Runs page 111 e Compiling MPI Applications page 111 6 2 Prerequisites for Running MPI For launching multiple MPI processes on multiple remote machines the MPI standard provides a launcher program that requires automatic login 1 e password less onto the remote machines SSH Secure Shell is both a computer program and a network protocol that can be used for log ging and running commands on remote computers and or servers 6 2 1 SSH Configuration The following steps describe how to configure password less access over SSH Mellanox Technologies 109 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 MPI Message Passing Interface Step 1 Generate an ssh key on the initiator machine host1 hostio Sohn keyen E red Generating public private rsa key pair E M
97. Mellanox TECHNOLOGIES Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Last Modified June 02 2011 www mellanox com Mellanox Technologies Confidential NOTE THIS HARDWARE SOFTWARE OR TEST SUITE PRODUCT PRODUCT S AND ITS RELATED DOCUMENTATION ARE PRO VIDED BY MELLANOX TECHNOLOGIES AS IS WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS THE CUS TOMER S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO S AND OR THE SYSTEM USING IT THEREFORE MELLANOX TECHNOLOGIES CAN NOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MER CHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT INDIRECT SPECIAL EXEM PLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT LIMITED TO PAYMENT FOR PROCURE MENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY FROM THE USE OF THE PRODUCT S AND RELATED DOCUMENTATION EVEN IF ADVISED OF
98. O To set the map of skb priority 0 to the requested vlan priority e g 6 run io CONT Ser Sio Majo Sais o 1 16 To create the vHBA enter t gt echo e io o OS SOS aI 3 2 3 3 Creating vHBAs That Use Link Pause The m1x4_ en Ethernet driver supports link pause by default To change this setting you can use the following command eo e o o ari o al To create a vHBA run r gt echo al gt SFPFCSYSES Crearte 52 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 3 Reliable Datagram Sockets 3 3 1 Overview Reliable Datagram Sockets RDS is a socket API that provides reliable in order datagram deliv ery between sockets over RC or TCP IP RDS is intended for use with Oracle RAC 11g For programming details enter host1 man rds 3 3 2 RDS Configuration The RDS ULP is installed as part of Mellanox OFED for Linux To load the RDS module upon boot edit the file etc infiniband openib conf and set RDS LOAD yes 4 For the changes to take effect run etc init d openibd restart hai 3 4 Sockets Direct Protocol 3 4 1 Overview Sockets Direct Protocol SDP is an InfiniBand byte stream transport protocol that provides TCP stream semantics Capable of utilizing InfiniBand s advanced protocol offload capabilities SDP can provide lower latency higher bandwidth and lower CPU utilization than IPoIB or Ethernet running some sockets bas
99. 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 e 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 under the docs directory Usage mea ss ne SUS e Is A localo dir gt v verbose Example The following command will create a MLNX OFED LINUX ISO image for RedHat 5 4 under the tmp directory MILIND IO HAD NAS Se Ls 4 clos uba ace Ikewael suo sla Lacie MINX ORED LINUX 1 5 1 rhel5 4 iso All Mellanox OEM OFED or Distribution IR packages will be removed Do vou want tO oon inue ly NI y Removing OFED RPMs F RR gate H S Oro Created tmp MLNX OFED LINUX 1 5 1 rhel5 4 iso 1 The firmware will not be updated if you run the install script with the without fw update option 26 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 2 3 2 Installation Script Mellanox OFED includes an installation script called minxofedinstall Its usage is described below You will use it during the installation procedure described in Section 2 3 3 Installation Pro cedure on page 29 Usage nn minxerecdunst alien OP MlOnsS Options
100. QoS can only support two quality of service levels so only the high order bit of any SL value used for unicast QoS configuration will be honored by torus 2QoS For multicast QoS con figuration only SL values 0 and 8 should be used with torus 2QoS Since SL to VL map configuration must be under the complete control of torus 2QoS any config uration via qos sl2vl qos swe sl2vl etc must and will be ignored and a warning will be gener ated Torus 2QoS uses VL values 0 3 to implement one of its supported QoS levels and VL values 4 7 to implement the other Hard to diagnose application issues may arise if traffic is not deliv ered fairly across each of these two VL ranges Torus 2QoS will detect and warn if VL arbitration is configured unfairly across VLs in the range 0 3 and also in the range 4 7 Note that the default OpenSM VL arbitration configuration does not meet this constraint so all torus 2QoS users should configure VL arbitration via qos vlarb high gos vlarb low etc 7 5 7 5 Operational Considerations Any routing algorithm for a torus IB fabric must employ path SL values to avoid credit loops As a result all applications run over such fabrics must perform a path record query to obtain the correct path SL for connection setup Applications that use rdma cm for connection setup will automati cally meet this requirement If a change in fabric topology causes changes in path SL values required to route without credit loops in gener
101. RAGE low eni lo ne quines runa ot external tool Default all flows except QoS W ca This option specifies the wait time for trap 64 65 in 124 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 SE Loa e MEE awe e a A uan ERS ey hy 65 flow Default 10 sec iz DUI patio pese NI Sp er IES L ERE opEton Tnese options are not normally needed The number following d galecto the debug option co enable as tollows ORT Description Sdo Ignore other SM nodes al Force single threaded dispatching AE Force Log fiushing atter each og message d9 Diseble multicast suppone SNe Sieve ate Mira CONE SSR RIME gullincre a EO slo seor ehed Cor diria vento iene Jago Tirs ope ien Species the lo alo GU whieh OpensMo Ss nou td bard OpenSM may be bound to DOTE sled tim EUA Ae ns 0 O pene Meda plis Tal Ss Or Possible port Uds and waves Eo CETTE Without g Open M crier to use the det aqii port Oy oO me Tirs Op Eon di plays a ment OF Doss tole local ports GUD values with which osmtest could bind i inventory This option specifies the name of the inventory file Normally Osmeest Expec to to ting an Tnventory Tilo which osmtest uses to validate real time information received from the SA Juring testing de L iS not SpecrrLed OomMtest derul tS to Ehe mrle CSMESSE delo ce aa ODEON tor reae mn om mae mon Saia Ser hast opt won wane Ene specitmed stre
102. Swap The MskCmpSwap atomic operation is an extension to the CmpSwap operation defined in the IB spec MskCmpSwap allows the user to select a portion of the 64 bit target data for the compare check as well as to restrict the swap to a possibly different portion The pseudocode below describes the operation Maroto ns Sia a CE COM is ario yal Om ais OS Ae Te eo ue Ae eo mask Mesta one es one The additional operands are carried in the Extended Transport Header Atomic response generation and packet format for MskCmpSwap is as for standard IB Atomic operations Mellanox Technologies 95 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 3 9 1 2 Masked Fetch and Add MFetchAdd The MFetchAdd Atomic operation extends the functionality of the standard IB FetchAdd by allowing the user to split the target into multiple fields of selectable length The atomic add is done independently on each one of this fields A bit set in the field boundary parameter specifies the field boundaries The pseudocode below describes the operation E E S deo A value i bl b2 xco value amp 2 return value amp I ide AE SR Mese mask amp attr Momo seo i cares Matton response as f r 1 0 tO 63 A DT OS ito MOS AO a iS a O Si MESI SRI DERE MASK So hl compare aaa TADOS telo E eee CES ENOSMUEC MOSS SCS okie seo Salic stoi CAY ewe ea
103. THE POSSIBILITY OF SUCH DAMAGE Mellanox TECHNOLOGIES Mellanox Technologies Mellanox Technologies Ltd 350 Oakmead Parkway PO Box 586 Hermon Building Sunnyvale CA 94085 Yokneam 20692 U S A Israel www mellanox com Tel 972 4 909 7200 Tel 408 970 3400 Fax 972 4 959 3245 Fax 408 970 3403 Copyright 2011 Mellanox Technologies All rights reserved Mellanox BridgeX ConnectX CORE Direct InfiniBlast InfmiBridge InfiniHost InfiniRISC InfiniScale InfiniPCI PhyX Virtual Protocol Interconnect and Voltaire are registered trademarks of Mellanox Technologies Ltd FabricIT and SwitchX are trademarks of Mellanox Technologies Ltd All other marks and names mentioned herein may be trademarks of their respective companies 2 Mellanox Technologies Document Number 2877 Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table of Contents Table of Content erener RATE eparina E a 3 Listof LADIES cid A E a RA RARAS ani dead 8 Reylsion History is da a ba a eine lee 9 Preta ia ii 11 intended Andine rd o e a a dd 11 Documentation Conventions a a a RR eh seb ete ent AA 12 Typo eraphical Conventions Lt on eGo ke wet ewer ees 12 Common Abbreviations and Acronyms saasaa esera nearer 12 CI SSALVS y lalo ea iodo oat ane eee Mee ee eee hob nee hae eh ea il 14 Related DOCU menta E E a e dok t r biti ik eh acne E 15 supportand Updates W ebpac
104. U are subject to IB MTU restrictions The RoCE s MTU values are 256 byte 512 byte 1024 byte and 2K Association of IB Ports to Ethernet Ports It is useful to know how IB ports associate to network ports ibdev2netdev Ia Ze Sila AA ee oxen ER it Since both RoCE and mlx4 en use the Ethernet port of the adapter one of the drivers must carry the task of controlling the port state In this implementation it is the task of the mlx4 en driver The mlx4 ib driver holds a reference to the mlx4 en net device for getting notifications about the state of the port as well as using the mlx4 en driver to resolve IP addresses to MAC that are required for address vector creation However RoCE traffic does not go through the mlx4 en driver it is completely offloaded by the hardware Configre an IP Address to md en Interface Run the following on both sides of the link 44 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Econo i A ON ifconfig eth2 eth2 link encap ethernet HWaddr 0 07022Co 08 Bol Mea E AS O a iO o es O UP BROADCAST MUETLTE ASE MTU T500 Metro RX packets O errors 0 dropped 0 overruns 0 Framer 0 Me packers se errors Uo arop a 0 OVS rUn lt 0 aE Tere Collins rons O tx ene Lem s00 0 BX bytes oO GE LT R H Bx bytes 0 107 008 Make sure that ping is working ig ping AO a Se de PENSADAS oo Oh ZIO OGG E OF data Cove Renee Ae
105. a default QoS Level Here s an example of the shortest policy file gos levels gos level name DEFAULT Salento end qos level end qos levels Port groups section is missing because there are no match rules which means that port groups are not referred anywhere and there 1s no need defining them And since this policy file doesn t have any matching rules PR MPR query will not match any rule and OpenSM will enforce default QoS level Essentially the above example is equivalent to not having a QoS policy file at all The following example shows all the possible options and keywords in the policy file and their syntax Mellanox Technologies 145 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 146 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 147 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 148 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 gos match rule use match by all parameters dossi ana source Virtual Servers destination Storage Sersale Fico OO 0100 010000 00 00 10 0520000000000 ILE 1 ah pkey 0x0E00 0x0 EEE gos level name WholeSet end qos match rule end qos match rules 7 6 6 Simple QoS Policy Details and Examples Simple QoS policy match rules are tailored for
106. ab ric setup Part of this policy defines the default QoS Level of each partition The SA is enhanced to match the requested Source Destination QoS Class Service ID PKey against the policy so clients ULPs programs can obtain a policy enforced QoS The SM may also set up partitions with appropriate IPoIB broadcast group This broadcast group carries its QoS attributes SL MTU RATE and Packet Lifetime 3 IPoIB is being setup IPoIB uses the SL MTU RATE and Packet Lifetime available on the multicast group which forms the broadcast group of this partition 4 MPI which provides non IB based connection management should be configured to run using hard coded SLs It uses these SLs for every QP being opened 5 ULPs that use CM interface like SRP have their own pre assigned Service ID and use it while obtaining PathRecord MultiPathRecord PR MPR for establishing connections The SA receiving the PR MPR matches it against the policy and returns the appropriate PR MPR including SL MTU RATE and Lifetime 6 ULPs and programs e g SDP use CMA to establish RC connection provide the CMA the target IP and port number ULPs might also provide QoS Class The CMA then creates Ser vice ID for the ULP and passes this ID and optional QoS Class in the PR MPR request The resulting PR MPR is used for configuring the connection QP PathRecord and MultiPathRecord Enhancement for QoS As mentioned above the PathRecord and MultiPathRecord attributes a
107. aded automatically upon boot can be found in the etc infiniband openib conf file 2 4 Updating Firmware After Installation In case you ran themlnxofedinsta1ll script with the without fw update option and now you wish to manually update firmware on you adapter card s you need to perform the fol lowing steps 7 4 If you need to burn an Expansion ROM image please refer to Burning the Expansion ROM Image on page 201 ha you have downloaded from Mellanox Technologies Web site http www mella The following steps are also appropriate in case you wish to burn newer firmware that all nox com gt Downloads gt Firmware Mellanox Technologies 37 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation Step 1 Start mst NOSE MSL STACE Step 2 Identify your target InfiniBand device for firmware update 3 Get the list of InfiniBand device names on your machine lanes eles MSE status MST modules MST PCI module loaded Mol Pel Conr gurat Ion Mode loaded MST Calibre 12C module is not loaded MST devices de mot mE oE pere one EEE TEI a a e e a access bus dev fn 02 00 0 addr reg 88 data reg 92 CRIP TE VIS BON TSn A0 de mise me 54 NS percal Cd cionci SS bus dev fn 02 00 0 bar 0xdef00000 size 0x100000 Chalo Reval STO ESR AD VAST mot me ovens pere isc ICI cessa aes bus dev fn 02 00 0 bar 0xdeefe000 size 0x2000 den met mezo E pel ueno Riese bus dev fn 02 00 0 bar
108. affic ssh IPoIB management VLAN partition A Min BW 10 e Application traffic IPoIB application VLAN partition B Isolated from storage and database Min BW of 30 e Database Cluster traffic RDS Min BW of 30 e SRP Min BW 30 Bottleneck at storage nodes Administration e OpenSM QoS policy file S In the following policy file example replace SRPT with the real SRP Initiator port k GUIDs 156 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 qos ulps default 200 poro pkey 0UxS00d S pomo E SSI D rds RES Skip target Port guld SERI RS REINER end qos ulps e OpenSM options file ADS ME AS e ces Macia le 0 dq ula o O SE ONG lO ges vta roto 10 1 cos Sl AWN 0 Mp epee ep Aer i lag oy Mop Woes lop Nop NS e Partition configuration file Default Ox7ffE ooo KATTIS ao Panta ISO oo ib FU 7 8 Adaptive Routing 7 8 1 Overview 4 Adaptive Routing is at beta stage T Adaptive Routing AR enables the switch to select the output port based on the ports load AR supports two routing modes e Free AR No constraints on output port selection Bounded AR The switch does not change the output port during the same transmission burst This mode minimizes the appearance of out of order packets 7 8 2 Running OpenSM With AR Manager To enable AR Manager in OpenSM run Mellanox Technologies 157 Mellanox Te
109. ages ConnectX fw 254087 InfiniHost III Ex fw 25208 and or InfiniHost III Lx fw 25204 can be downloaded from Mellanox Technologies Web site see www mellanox com gt Downloads gt Firmware gt Customized Firmware 2 Firmware Configuration in1 Files For standard Mellanox products ini files are included in the firmware mlx packages For help in identifying the correct ini file of your adapter hardware please refer to MFT User s Manual which 1s provided in Mellanox OFED for Linux 3 Expansion ROM Image The expansion ROM images are provided as part ofthe SW package and are listed in the release notes file FlexBoot release notes txt 4 Firmware Burning Tools 1 Depending on the OS the device name may be superceded with a prefix 2 Relevant only if your ConnectX EN devices are currently burnt with a firmware version earlier than 2 7 000 202 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 You need to install the Mellanox Firmware Tools MFT package version 2 6 0 or later in order to burn the PXE ROM image To download MFT see Firmware Tools under www mellanox com gt Downloads Specifically you will be using the mlxburn tool to create and burn a composite image from an adapter device s firmware and the PXE ROM image onto the same Flash device of the adapter Image Burning Procedure To burn the composite image perform the followi
110. al all applications would need to repath to avoid message deadlock Since torus 2005 has the ability to reroute after a single switch failure without changing path SL values repa thing by running applications is not required when the fabric is routed with torus 2QoS Torus 2QoS can provide unchanging path SL values in the presence of subnet manager failover provided that all OpenSM instances have the same idea of dateline location See torus 2QoS conf 5 for details Torus 2QoS will detect configurations of failed switches and links that prevent routing that is free of credit loops and will log warnings and refuse to route If no fallback was configured in the list of OpenSM routing engines then no other routing engine will attempt to route the fabric In that case all paths that do not transit the failed components will continue to work and the subset of paths that are still operational will continue to remain free of credit loops OpenSM will continue to attempt to route the fabric after every sweep interval and after any change such as a link up in the fabric topology When the fabric components are repaired full functionality will be restored In the event OpenSM was configured to allow some other engine to route the fabric if torus 2QoS fails then credit loops and message deadlock are 142 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 likely if torus 2QoS had
111. and how to use them you might wantto go back and select automatic partitioning F Linux native Ext2 boot 7 4 GB F Linux native Reiser 73 1045 Please note that nothing will be written to your hard disk until you confirm the entire installation in the last installation You have not assigned a swap partition There is nothing wrong with that but in most cases it is highly recommended to create and assign a swap partition dialog Until that point Swap partitions on your system are listed inthe main window with the you can safely abort type Linux Swap An assigned swap partition has the mount point swap the installation You can assign more than one swap partition if desired For LVM setup using a non LVM root device and a non LVM swap device is recommended Other than the root and swap devices you should have partitions managed by LVM Do you want to change this The table to the right shows the current partitions on all your Create Edit Delete Resize hard disks A i fa lt eae o LYM EVMS BAID v CryptFile v Expert Back Abor Mellanox Technologies 221 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 14 Select the Expert tab and click Booting Preparation Y Language License Agreement Disk Activation y System Analysis R Installation Settings Click any headline to make change
112. andatory without G flag Use the specified port Examples I Check aggregated node counter for LID 0x2 gt ibcheckerrs 2 Walken Counter Symbol Errors 60930 ire sold TO iO OS warn counter LinkRecovers 255 Mareen o Ee L E E E Enn warn counter LinkDowned 12 arec RO Je 10 auch 2 coca 255 Mae he ole FeRRo Fwarn counter XmtDiscards 441 irte Sho OG late pore 7 oo EMO ME com Lra A MTA O TAEI ocal e rI Me ano x Le ciao lo gine Si POr te Gala FAILED 2 Check port counters for LID 2 Port 1 gt ibcheckerrs w 2 1 Error check Or hid 2 UMAT ans coke Md Mediano esca ollo L WO rr tls Seen GO Ke 192 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 Check the LID2 Port 1 using the specified threshold file ie Messico SymbolErrors 10 LinkRecovers 10 LinkDowned 10 Revisori 10 RcvRemotePhysErrors 100 RcvSwRelayErrors 100 XmtDiscards 100 Eto rc eno s 1010 REV COn CEINE ore 100 LinkIntegrityErrors 10 ExcBufOverrunErrors 10 VL15Dropped 100 gt ibcheckerrs v T threshl 2 1 Error check on 11d 2 LISCA ino Technologies port Ls OM 8 15 mstflint Applicable Hardware Mellanox InfiniBand and Ethernet devices and network adapter cards Description Queries and burns a binary firmware image file on non volatile Flash memories of Mellanox InfiniBand and Ethernet network adapters The tool requires root privileges for Fla
113. anox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 ing This means that two EoIB interfaces on the same vHub will communicate solely using the InfiniBand fabric EoIB interfaces residing on two different vHubs whether on the same gateway or not cannot communicate directly There are two types of vHubs e a default vHub one per gateway without a VLAN ID e vHubs with unique different VLAN IDs Each vHub belongs to a specific gateway BridgeX eport and each gateway has one default vHub and zero or more VLAN associated vHubs A specific gateway can have multiple vHubs distinguishable by their unique VLAN ID Traffic coming from the Ethernet side on a specific eport will be routed to the relevant vHub group based on its VLAN tag or to the default vHub for that GW if no vLan ID is present 3 6 1 3 Virtual NIC vNic A virtual NIC is a network interface instance on the host side which belongs to a single vHub on a specific GW The vNic behaves similar to any regular hardware network interface The host can have multiple interfaces that belong to the same vHub 3 6 2 EolB Configuration mlx4 vnic module supports two different modes of configuration which is passed to the host mlx4 vnic driver using the EoIB protocol e host administration where the vNic is configured on the host side e network administration where the configuration is done by the BridgeX Both modes of operation require the
114. appears Preparation Language W License Agreement sp Disk Activation e System Analysis Service Connected Targets iSCSI Initiator Overview a Time Zone Portal Address TargetName Start Up Installation i j Installation Summary Perform Installation Configuration Root Password Hostname a Network Customer Center Online Update a Service a Users Clean Up a Release Notes Hardware Configuration 220 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Step 3 Click the Add tab in the iSCSI Initiator Overview window An iSCSI Initiator Discovery win dow will pop up Enter the IP Address of your iSCSI target and click Next Preparation y Language y License Agreement sp Disk Activation System Analysis Time Zone iSCSI Initiator Discovery Installation Installation Summary ii aa e Perform Installation S a a 10 4 3 7 3260 Configuration Root Password Hostname a Network B No Authentication Customer Center Online Update a Service Sie rai l Incoming Authentication Users e Clean Up Username Password Release Notes Hardware Configuration Outgoing Authentication Username Password Help Back Abort Next Mellanox Technologies 221 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 4 Details
115. are All InfiniBand devices Description Queries InfiniBand devices and prints about them information that is available for use from user space Synopsis MO SO E SR eee Ie Mellanox Technologies 171 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Table 14 lists the various flags of the command Table 14 ibv_devinfo Flags and Options Default If Not Specified Optional First found device Optional Mandatory d lt device gt jb dev lt device gt 1 lt port gt ib port lt port gt All device ports verbose Examples InfiniBand Fabric Diagnostic Utilities Description Run the command for the provided IB device device Query the specified device port lt port gt Only list the names of InfiniBand devices Print all available information about the InfiniBand device s 1 List the names of all available InfiniBand devices NEAR Ol 2 HCAS rouno mthca0 mlx4 0 2 Query the device mlx4_ 0 and print user available information for its Port 2 SS OO Mz ez Leo EEE Node rue Sy e ias e tua Vendor id nE ee IAA Er ST ST E CNE POr Z Stace Siete Saree eave DOLO SOUTO sos 00 0 0510 00 08 00073398 OO 25418 OXAO MT 04A0140005 2 PORT ACEITE 2 CATA RARO e Me 172 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 MOT 2048 4 Sio il POr il p
116. at have that property For the 2D 6x5 torus example above here is the full fabric spanning tree that torus 2QoS will construct where x is the root switch and each is a non root switch 4 3 2 ho K 1 y 0 x 0 1 2 3 4 G For multicast traffic routed from root to tip every turn in the above spanning tree is a legal DOR turn For traffic routed from tip to root and some traffic routed through the root turns are not legal DOR turns However to construct a credit loop the union of multicast routing on this spanning tree with DOR unicast routing can only provide 3 of the 4 turns needed for the loop In addition if none of the above spanning tree branches crosses a dateline used for unicast credit loop avoidance on a torus and if multicast traffic is confined to SL 0 or SL 8 recall that torus 2QoS uses SL bit 3 to differentiate QoS level then multicast traffic also cannot contribute to the ring credit loops that are otherwise possible in a torus Torus 2QoS uses these ideas to create a master spanning tree Every multicast group spanning tree will be constructed as a subset of the master tree with the same root as the master tree Such multicast group spanning trees will in general not be optimal for groups which are a subset of the full fabric However this compromise must be made to enable support for two QoS levels on a
117. b bonding package run rpm qi ib bonding to get the package information The ib bonding driver can be loaded manually or automatically Manual Operation Use the utility ib bond to start query or stop the driver For details on this utility please read the documentation for the ib bonding package under Use Shame dos Mo bondin EE EEE SI TEE on Reda and Wer share dos paoka ae a monda 00 o Donda e on suck Automatic Operation Automatic ib bonding operation can be configured as follow 1 Using a standard OS bonding configuration For details on this please read the documenta tion for the ib bonding package under is eaae dos o Lon dina 0650 07 55 ET Eo S el Ue Share doc packages 1b gt bonding 0 9 0 Te Ponda txt On SuSE Notes e If the bondX name is defined but one of bondX SLAVES or bondX IPs is missing then that specific bond will not be created e The bondX name must not contain characters which are disallowed for bash variable names such as and 4 All the newer OSes Bonding can be done with the inbox bonding module Mellanox Technologies 241 Mellanox Technologies Confidential
118. ble qos_ lt type gt _high limit indicates the number of high priority packets that can be transmitted without an opportunity to send a low priority packet Specifically the number of bytes that can be sent is high limit times 4K bytes A high limit value of 255 indicates that the byte limit is unbounded S If the 255 value is used the low priority VLs may be starved hai A value of 0 indicates that only a single packet from the high priority table may be sent before an opportunity is given to the low priority table Keep in mind that ports usually transmit packets of size equal to MTU For instance for 4KB MTU a single packet will require 64 credits so in order to achieve effective VL arbitration for packets of 4KB MTU the weighting values for each VL should be multiples of 64 Below is an example of SL2VL and VL Arbitration configuration on subnet qoc tea fills s Jos me gio AO ds ds eee Gos veal varb low O 0 od 221267 3319274 50 5264 6 04 od ques tears a 47 27 67 IAS qos owe max vls ls COs sis Join Wine qos swe vlarb high 0 4 gos swe lar RR CTZ Ze RZ Re 1204 FE O A a O o A In this example there are 8 VLs configured on subnet VLO to VL7 VLO is defined as a high pri ority VL and it is limited to 6 x 4KB 24KB in a single transmission burst Such configuration would suilt VL that needs low latency and uses small MTU when transmitting packets Rest of VLs are defined as low priority VLs with different weights
119. but then they PKey should be explicitly specified otherwise different PKey values will be generated for those definitions Examples Default 0x7fff ALL SELF full NEWEST TE TGN poro aa UI US GO TEST NE 0 x2134af2306 YetAnotherOne 0x300 SELF full YertrAnortherone 0x300 ALL limircec s ShareIO 0x80 defmember full 0x123451 0x123452 SS O 3 ASA O Minas ee Shared Or Oxon Ox SAS cz od O Soo EQ EAS USOS A na oe wana ec ShareIO 0x80 gt defmember limited 0x123456 0x123457 Orly S453 f Shearer 0x80 T p T E BI OS AS SO Oxl2345aF ShareIO 0x80 defmember full Ox DZ 34513 0x12345c lim Ded FRAS ET The following rule is equivalent to how OpenSM used to run prior to the partition manager Mellanox Technologies 129 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager Default Oxf E RARI IE 7 5 Routing Algorithms OpenSM offers six routing engines 1 Min Hop Algorithm Based on the minimum hops to each node where the path length is optimized 2 UPDN Algorithm Based on the minimum hops to each node but it is constrained to ranking rules This algorithm should be chosen 1f the subnet is not a pure Fat Tree and a deadlock may occur due to a loop in the subnet 3 Fat tree Routing Algorithm This algorithm optimizes routing for a congestion free shift communication pattern It should be chosen if a subnet is a symme
120. bv_devinfo 171 8 8 ibdev2netdev 173 Sd SYINOPS TY Sr iosa are a 173 8 9 ibstatus 174 8 10 ibportstate 176 8 11 ibroute 180 8 12 smpquery 184 8 13 perfquery 188 8 14 ibcheckerrs 19 8 15 mstflint 193 8 16 ibv_asyncewatch 197 8 17 ibdump 197 Appendix A Mellanox FlexBoot 200 A 1 Overview 200 A 2 Burning the Expansion ROM Image 201 A 3 Subnet Manager OpenSM 207 A 4 TFTP Server 207 A 5 BIOS Configuration 208 A 6 Operation 208 A 7 Command Line Interface CLI 210 A 8 Diskless Machines 212 A 9 iSCSI Boot 218 A 10 WinPE 232 Appendix B SRP Target Driver 233 B 1 Prerequisites and Installation 233 B 2 How to run 233 B 3 How to Unload Shutdown 236 Appendix C mlx4 Module Parameters 238 C 1 mlx4 core Parameters 238 C 2 mlx4 ib Parameters 239 C 3 mlx4 en Parameters 239 C 4 mlx
121. ce e Disable the TCP timestamps option for better CPU utilization SSC IN air eee e Disable the TCP selective acks option for better CPU utilization SASS EIN Sipe Mee sah Ona ae CONS ac 0 Mellanox Technologies 103 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Performance 5 2 3 Interrupt Moderation Interrupt moderation is used to decrease the frequency of network adapter interrupts to the CPU Mellanox network adapters use an adaptive interrupt moderation algorithm by default The algo rithm checks the transmission Tx and receive Rx packet rates and modifies the Rx interrupt moderation settings accordingly To manually set Tx and or Rx interrupt moderation use the ethtool utility For example the fol lowing commands first show the current default setting of interrupt moderation on the interface ethl then turns off Rx interrupt moderation and last shows the new setting gt ethtool c ethl Coalesce parameters for ethl Adapter Ve ROR HE pkt rate low 400000 pkt rate htgh 450000 rx usecs 16 rx frames 88 CMSs Ses a O rx trames td U SO SO Sl adapt ve Ts ONE ra Ds O LET le N ethtool c eini Coalesce parameters for ethl SS O E A OT E pkt rate low 400000 PRE rate Nighe 450000 rx usecs O rx frames 0 PX US SES KIT rx Trkames a E 104 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 5
122. ce Node Sys The IB Host Channel Adapter HCA Card installed on the machine running tem IBDIAG tools The IB port of the HCA through which IBDIAG tools connect to the IB fab ric Master Subnet Man The Subnet Manager that is authoritative that has the reference configura ager tion information for the subnet See Subnet Manager Multicast Forward A table that exists in every switch providing the list of ports to forward ing Tables received multicast packet The table is organized by MLID Network Interface A network adapter card that plugs into the PCI Express slot and provides one Card NIC or more ports to an Ethernet network Standby Subnet Man A Subnet Manager that is currently quiescent and not in the role of a Master ager Subnet Manager by agency of the master SM See Subnet Manager Subnet Administra An application normally part of the Subnet Manager that implements the tor SA interface for querying and manipulating subnet management data Subnet Manager SM One of several entities involved in the configuration and control of the sub net Unicast Linear For A table that exists in every switch providing the port through which packets warding Tables LFT should be sent to each LID Virtual Protocol A Mellanox Technologies technology that allows Mellanox channel adapter Interconnet VPI devices ConnectX to simultaneously connect to an InfiniBand subnet and a 10GigE subnet each subnet connects to one of the
123. ces along the path The way ibdiagpath operates depends on the addressing mode used on the command line If directed route addressing is used d flag the local node is the source node and the route to the destination port is known apriori On the other hand if LID route or by name addressing is employed then the source and destination ports of a route are specified by their LIDs or by the names defined in the topology file In this case the actual path from the local port to the source port and from the source port to the destination port is defined by means of Subnet Management Linear Forwarding Table queries of the switch nodes along that path Therefore the path cannot be predicted as it may change ibdiagpath should not be supplied with contradicting local ports by the p and d flags see synopsis descriptions below In other words when ibdiagpath is provided with the options p and d together the first port in the direct route must be equal to the one specified in the p option Otherwise an error is reported When ibdiagpath queries for the performance counters along the path between the S source and destination ports it always traverses the LID route even if a directed route is specified If along the LID route one or more links are not in the ACTIVE state ibdi agpath reports an error Moreover the tool allows omitting the source node in LID route addressing in which case the local port on the machine ru
124. chnologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager opensm ar AR Manager scans all the fabric switches figures out which switches support AR and configures the AR functionality on these switches Note that if some switches do not support AR they will slow down the AR Manager as it may get timeouts on the AR related queries to these switches To run AR Manager with an AR configuration file enter Miocene SS O ie OA e Currently there are two options in the config file I Enable disable AR on fabric switches by including the following line to the AR configura tion file enable lt truelfalse gt where the default value is true which is also valid for cases when the AR config file is not pro vided This option 1s different from the OpenSM command line option ar The former controls AR on fabric switches while the latter specifies whether AR Manager in OpenSM should be launched or not Note that once AR is enabled you will need to actively turn it off in order to disable it To turn it off set enable to false in the AR configuration file and run OpenSM as follows O SS e O e Oe 2 AR Mode In the configuration file set ak mode Dolmae el pese where the default value is bounded 7 8 2 1 AR Configuration File Example The following is an example of AR configuration file content Begin AR configuration file Se le ine ar mode bounded 7 Bnd AR Contagquration
125. ck oslo mes sages will be printed 2 3 2 1 minxofedinstall Return Codes Table 1 lists the nlnxofedinstall script return codes and their meanings Table 1 mlinxofedinstall Return Codes The Installation ended successfully No firmware was found for the adapter device The installation failed Failed to start the ms t driver 28 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 2 3 3 Installation Procedure Step1 Login to the installation machine as root Step 2 Mount the ISO image on your machine UN Op ME CIEE DY LIMI a OS lo a ine Step 3 Run the installation script host ia minty minxofedinstall Ta pr oge a E a ENS MENO BE PINOS de a eo ota chine Nowe thar oU other Me ano EE EDO DiS oo I B PECK ages wa be removed Do You want to continue y Nity Unas ola the Previous verson OF O REID Starr NA ELE Installing kernel ib RPM Preparing dd kernel ib HEE HH HHH HH HE EE HH HH HH EE EH HH EH EE EE EH OH Ep EEE HH HEHH Installing kernel ib devel RPM Preparing HEHE HH HH HH HE EE HH HH HH EE EH HH EE HEE EH EOE EH r r r HEHH kernel ib devel it it it it Ht Ht ROR RR RR Ht RR ET r RR r r EEE EEE rt EE EEE Installing kernel mft RPM Preparing it it it Ht Ht Ht HH HH HH HH HH HH HE ET EE EE EEE EEE EE EEE EEE EEE EEE EEE kernel mft it it it Ht Ht Ht HH HH HH HH HH HH EE EEE EE EEE EEE EEE EE EEE EEE EEE EE EE Installing m
126. d ed rate lt val gt Peores rate Tor thio bol IMO croup Jerall ses 10GBps mtu lt val gt specities MIU Tor tenis Bole MC group detalles 4 2048 sl lt val gt Species hom sels NES EB OE ome de E 4355 000 scope lt val gt Species scope mos has POIRE Me B E EE EE 15002 Link l cal Note that values for rate mtu and scope should be specified as defined in the IBTA specifica tion for example mtu 4 for 2048 PortGUIDs list 128 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 PoreG DP GUID of partition member EndPort Hexadecimal numbers should stark From 0s decimal numbers tete ac cepred ESO na en dee Seo ami demente o esoo Mier omitted or unrecognized limited membership is assumed There are two useful keywords for PortGUID definition e ALL means all end ports in this subnet e SELF means subnet manager s port An empty list means that there are no ports in this partition Notes e White space is permitted between delimiters e The line can be wrapped after after a Partition Definition and between e A PartitionName does not need to be unique but PKey does need to be unique e Ifa PKey is repeated then the associated partition configurations will be merged and the first PartitionName will be used see also next note e Itis possible to split a partition configuration in more than one definition
127. destroying vHBAs and signaling link up and link down to existing VHBAs This is done using sysfs operations When using the pre T11 stack the sysfs directory is located at sys class mlx4 fc When using the T11 stack the sysfs directory is located at sys module fcoe Both directories contain the same entries In the following the sysfs directory will be referred to as SFCSYSES To create a new vHBA on an Ethernet interface e g eth3 run echo tetas gt SFCSYSFS cecreate To destroy a previously created vHBA on an interface e g eth3 run gt echo eth3 gt SFCSYSFS destroy Mellanox Technologies 51 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features To signal link up to an existing vHBA e g on eth3 run techo tetas EES ORo AA ak sue To signal link down to an existing vHBA e g on eth3 run ET S E a sera 3 2 3 2 Creating vHBAs That Use PFC To create a vHBA that uses the PFC feature it is required to configure the Ethernet driver to sup port PFC create a VLAN Ethernet interface assign it a priority and start a vHBA on the interface The following steps demonstrate the creation of such a vHBA To configure the mlx4 en Ethernet driver to support PFC add the following line to the file etc modprobe conf and restart the network driver NAS e eee eee To create a VLAN with an ID e g 55 on interface e g eth3 run NAO LO LASER oe A OS ae SUS SO UL
128. e the simple policy file syntax enables the administrator to match PR MPR requests by various ULPs and applications running on top of these ULPs 7 6 2 Advanced QoS Policy File The QoS policy file has the following sections I Port Groups denoted by port groups This section defines zero or more port groups that can be referred later by matching rules see below Port group lists ports by e Port GUID e Port name which is a combination of NodeDescription and IB port number e PKey which means that all the ports in the subnet that belong to partition with a given PKey belong to this port group Mellanox Technologies 143 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager e Partition name which means that all the ports in the subnet that belong to partition with a given name belong to this port group e Node type where possible node types are CA SWITCH ROUTER ALL and SELF SM s port II QoS Setup denoted by qos setup This section describes how to set up SL2VL and VL Arbitration tables on various nodes in the fab ric However this is not supported in OFED SL2VL and VLArb tables should be configured in the OpenSM options file default location var cache opensm opensm opts III QoS Levels denoted by qos levels Fach QoS Level defines Service Level SL and a few optional fields e MIU limit e Rate limit e PKey e Packet lifetime When path s search is performed it i
129. e leval Arb lags field must follow the D option A bit set clear in the flags enables disables a specific log level as follows BIT LOG LEVEL ENABLED 0x01 ERROR error messages 0x02 INFO basic messages low volume 126 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 0x04 VERBOSE interesting stuff moderate volume 0x02 DEBUG diagnoctie Niga volumne 0x10 FUNCS function entry exit very high volume 020 FRAMES dumps all SMP and GMP frames 0x40 ROUTING dump FDB routing information 0x80 currently unused Without vf osmtest defaults to ERROR INFO 0x3 Specifying vt 0 disables all messages 5pecifying vf OxFF enables all messages see V High verbosity levels may require increasing the transaction timeout poiche he eo prioni e lo Display this usage info then exit 7 3 2 Running osmtest To run osmtest in the default mode simply enter hostl osmtest The default mode runs all the flows except for the Quality of Service flow see Section 7 6 After installing opensm and if the InfiniBand fabric is stable it is recommended to run the fol lowing command in order to generate the inventory file Rosal osmtest E C Immediately afterwards run the following command to test opensm hostl osmtest f a Finally it is recommended to occasionally run osmtest v with verbosity to verify that noth ing in th
130. e reported as the vNic interface link state If the connection between the vNic and the BridgeX is broken hence the external port state is unknown the link will be reported as down e the link state of the external port associated with the vNic interface 80 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 A link state is down on a host administrated vNic when the BridgeX is connected and y the InfiniBand fabric appears to be functional The issue might result from a miscon Ai figuration of either BXADDR or and BXEPORT configuration file To query the link state run the following command and look for Link detected ethtool lt interface name gt Example ethtool eth10 Settings rom sean Supported pores I Supported link modes Supports auto negotiation Ne Advertised link modes Not reported Advertised auto negotiation No Speed Unknown 10000 Duplex Full Port Twisted Pair Pig OAD 0 Transceiver internal ATEO heder ion Supports Wake on d Wake on d Current message level 0x00000000 0 Link detected yes 3 6 3 4 Bonding Driver EoIB uses the standard Linux bonding driver For more information on the Linux Bonding driver please refer to lt kernel source gt Documentation networking bonding txt Currently not all bonding modes are supported e g LACP is not supported 3 6 3 5 Jumbo Frames EoIB supports jumbo frames
131. e 15 ibstatus Flags and Options Optional DELI Flag RR dator If Not Description y Specified lt device gt Optional All devices Print information for the specified device May specify more than one device lt port gt Optional but All ports of the Print information for the specified port only of the spec requires specify specified device ified device ing a device name Examples I List the status of all available InfiniBand devices and their ports gt ibstatus Hylan e e ao o OS R Ne E detalle FEUDO OOOO ODO OOOO ODIO So base lid 0x3 su lola 0x3 S E A ACTIVE phys state co rate 20 Gb sec 4X DDR IMA a eya Ot default gid PESO UU AUTO US 174 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 2 List the status of specific ports of specific devices Mellanox Technologies 1 5 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities base lid Oxl Siig gle inal Usa state AN A E phys state TERROR rate 20 Gb sec 4X DDR 8 10 ibportstate Applicable Hardware All InfiniBand devices Description Enables querying the logical link and physical port states of an InfiniBand port It also allows adjusting the link speed that is enabled on any InfiniBand port If the queried port is a swich port then ibportstate can be used to e disable enable or reset the port e
132. e 2 4 4 23 62 da Coi ee a sol oe ES ie See ke 15 Chapter 1 Mellanox OFED Overview oooooooooooccccrrorcccccnroor soso 16 1 1 Introduction to Mellanox OFED 16 1 2 Introduction to Mellanox VPI Adapters 16 1 3 Mellanox OFED Package 16 ESal ISO TITO ros te al Meena Pe OY SOEs aia Soe eee ee eee Eas 16 13 2 SO Ware Components te vada sli aree bee eye ded Oke tentare be 17 edo WMI WANS ed act ated dak a ot od ood se ah aha SN eats Ie Se eens ee ed eka eee ork Teeter See 18 E34 Decio SUUCIhe 2 2 sa roi Sob E pico ih OR Be te LO Aon Ge ee ee Abe 18 1 4 Architecture 18 LAL mica ICA Diver os fs b let nb E A ii 19 kaz tan AY PI IDTV Cis iatale dt egret dle 19 1 43 Midday 0 ticino ei iii BE ohne 20 IAA Open a sibili isla 20 lisr Cb leslie Sicani 20 Lar NPI coreani ella 21 1 47 InfiniBand Subnet Manager d bor di di preda hl paesi 22 4587 Diagnosi Uii S ieee Bes on Ser parli ilaele SE 22 L S Mellanox Firmware Tools icaro ce meee ke RR M R ci 22 1 5 Quality of Service 23 Chapter2 Installation ca daa 24 2 1 Hardware and Software Requirements 24 Zell Hardware Requirements tale tales 24 222 Sotwarce Regquireme
133. e ME asain species the directory where the output files will be placed default tmp Species the expected LInk wLdERN Specifies the expected link speed Pump cali sone sera ro Anos pc OU rS neo SEI granel OM Reset all the fabric links pmCounters If any of the provided pm is greater then its provided value print it to screen Pernes her rhel page ino ema acom ERES Re ems ono L 1 eIC o ub Printo the R E ata coles and Chessa eS A dump of all the application reports generated according to the provided flags A dump of the Performance Counters values of the fabric links 8 5 3 ERROR CODES L The path traced 19s un healthy 2 Failed to parse command line options 3 More then 64 hops are required for traversing the local port to the LoOuLree POrhi and tiene toque Destination Wort 4 Unable to traverse the LFT data from source to destination 5 gt Failed f use Topology File 6 Hamiled to lead required Package 170 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 8 6 ibv devices Applicable Hardware All InfiniBand devices Description Lists InfiniBand devices available for use from userspace including node GUIDs Synopsis MEN Che Ces Examples 1 List the names of all available InfiniBand devices gt SW CSN me es device node GUID mthca0 000290001016150 mlx4 0 0000000000073895 8 7 bv_devinfo Applicable Hardw
134. e ROMA tor Small BUCKS 0 dia ii falce ode 65 3 5 SCSI RDMA Protocol 66 S E R velate ehe e i 66 F ARONA boa iena AED dc AA a N AE 66 Silo R eT TT SRP 511 ST O si e i 66 3 5 2 2 Manually Establishing an SRP Connection anaana 000 cee eee 67 3 5 2 3 SRP Tools ibsrpdm and srp daemon 67 3 5 2 4 Automatic Discovery and Connection to TargetS oooooooooooo 70 3 5 2 5 Multiple Connections from Initiator IB Port to the Target 71 3 3 220 High Availability HA eil A ae 71 E muta DOWN SRP ss 640445 dada ots ihe ee ee Sele ues a eee 73 3 6 Ethernet over IB EoIB vNic 74 Soul Ethernet over IB TOpOIO 2 V s dal 74 3 6 1 1 External Ports eports and Gateway nannan annann enenu 74 3 0 1 2 Aral UD S VHS usar rd bt Sl ee aad 74 E D Ad NGCONO iraniano ete ess 75 562 FoB CONO OM da AN LAI IL ei 75 3 6 2 1 EoIB Host Administered VNIC LL 13 3 6 2 2 EoIB Network Administered VNIC 00 ccc eee nes 77 3 6 2 3 VLAN Configuration o TI 3 6 2 4 EoIB Multicast Configuration 0 0 00 cee eens 78 5 06 25 BOIB and Quallly 0L Service natiche lei Be oh oe ae ed weeds 79 3 6 2 6 IP Configuration Based on DHCP 79 3 6 2 7 gt Static EoIB Conhistrafioni sal ek eee ee y Gee Mee i rela 79 302 9 Sub IntertaceS VAAN Jaso cr Pack sou cated te end at Abe eee dre ews oe 79 3 6 3 Ret
135. e boot device priority list see Section A 5 On dual port network adapters the client first attempts to boot from Port 1 If this fails 4 it switches to boot from Port 2 Note also that the driver waits up to 90 seconds for af each port to come up If MLNX FlexBoot gPXE was selected through BIOS setup the client will boot from FlexBoot The client will display FlexBoot attributes sense the port protocol Ethernet or InfiniBand In case of an InfiniBand port the client will also wait for port configuration by the Subnet Manager S In case sensing the port protocol fails the port will be configured as an InfiniBand port hai 208 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 For ConnectX Me llanos Connects FlexBoot v3 0 000 PXE 0 9 9 Open Source Boot Firmware neth Hd 02 09 00 HE9 H S aa bc on PEII 00 0 open LLink down TK 9 TKE 0 RX 0 RXE 6 Link status Not connected 0x38086001 Jaiting for link up on net ok For InfiniHost III Ex Starting lellanox Boot over IB for InfiniHost III Ex ver Loading via IB Fort 2 Waiting for Infiniband link up ok 5 After configuring the IB ETH port the client attempts connecting to the DHCP server to obtain an IP address and the source location of the kernel OS to boot from For ConnectX InfiniBand Mellanox Connect FlexBoot gPXE 0 9 9 Open Source B
136. e boot partition dev sdal 70 5 MB with ext2 Create swap partition dev sda2 502 0 MB Create root partition dev sda3 7 4 GB with reiserfs Partitioning Accept Proposal Base Partition Setup on This Proposal DO Create Custom Partition Setup In the Expert Partitioner window select from the IET VIRTUAL DISK device the row that has its Mount column indicating swap then click Delete Confirm the delete operation and click Finish Expert Partitioner Device Size F Type Mount Mount By Start End Used By Label Devi dev sda 8 0 GB IET VIRTUAL DISK O 1045 scsi dev sdal 70 5 MB F Linux native Ext2 boot K 0 8 scsi dev sda2 502 0 MB F Linux swap swap K 9 72 scsi dev sda3 7 4 GB F Linux native Reiser K scsi Really delete device dev sda2 Create Edit Delete Resize evms RAID cryptrile y Expert y Back Abort Finish Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Step 13 In the pop up window click No to approve deleting the swap partition You will be returned to Installation Settings window See image below Partition your hard Expert Partitioner disks This is intended for experts If you are not i Mount Mount By Start End Used By Label Devi familiar with the 0 1045 concepts of hard disk partitions
137. e boot process Improper application of this pro cedure may prevent the diskless machine from booting Step1 Back up your current initrd file Step 2 Make a new working directory and change to it INCE CIS finds feno e most CCl amo Lane Step 3 Normally the initrd image is zipped Extract it using the following command MOS Ace BE a cae Eero The initrd files should now be found under tmp initrd en Step 4 Create a directory for the ConnectX EN modules and copy them Rosi muscle ag emis alejas sl ald mocul s mua en host1 cd lib modules uname r updates kernel drivers ies bite 69 mer muller nb core les amo a SA Ilo moss ima Sa moss ce mete mile lo ei les emis ae esi ads mec ts Mulas Sa Step 5 To load the modules you need the insmod executable If you do not have it in your initrd please add it using the following command osti eo soa aya soe cmo vara sia a Step 6 If you plan to give your Ethernet device a static IP address then copy ifconfig Otherwise skip this step MOSS a coi fenice eno te e Step 7 Now you can add the commands for loading the copied modules into the file init Edit the file tmp initrd en init and add the following lines at the point you wish the Ethernet driver to be loaded The order of the following commands for loading modules is critical echo lo dino Mellanexiconmecix EN driver Faiano ka mo cis iio se ooo Mellanox Technologies 217 Mellanox Technologi
138. e de use ge gie H N Open Mo ea MO een ao ene Slide din ehe obo EROI E Supported Eni CUR Eres KANN O Us 24003 NO Sia ONO This option prevents OpensM from falling back to default routing if none of the provided engines was able to configure the subnet OMS Menos des K TE Ton enables additional tanada Sis for the lash routing engine tO PECCOnd EE Lom Switch Port assvonments in regular cartesian meshes which may reduce the number Of Sls required do give sa deadlock ree cour amg lose ee ino Mellanox Technologies 115 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 116 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 117 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 118 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 119 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 120 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 121 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 122 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 2
139. e fabric has changed 7 4 Partitions OpenSM enables the configuration of partitions PKeys in an InfiniBand fabric By default OpenSM searches for the partitions configuration file under the name usr etc opensm partitions conf To change this filename you can use opensm with the Pconfig or P flags The default partition is created by OpenSM unconditionally even when a partition configuration file does not exist or cannot be accessed Mellanox Technologies 127 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager The default partition has a P Key value of 0x7fff The port out of which runs OpenSM is assigned full membership in the default partition All other end ports are assigned partial membership 7 4 1 File Format Notes e Line content followed after character is comment and ignored by parser General File Format lt ParcrcicLon Deriniclon gt s lt PorcCUIDs H 5 Partition Definition PartitionName PKey flag value defmember full limited where PartitionName string will be used with logging When omitted an empty string will be used PKey Pokey va esto ies Pats mit One Only lowes pies EI lS VS Solas eones ESA Sao gen SS flag WS SEO Moto ares RD ao Dat OE mts O dana defmember full limited species de Ramis menber lipidi LS E uE el Currently recognized flags are TED CIO Indesit EM ud MB OIE anta Test EE RIE pablo MC oreup mal bet cre
140. e heavy sweep or when the topology change does not require new routing calculation e g when one or more CAs RTRs leaf switches going down or one or more of these nodes coming back after being down A very com mon case that is handled by the unicast routing cache is host reboot which otherwise would 130 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 cause two full routing recalculations one when the host goes down and the other when the host comes back online OpenSM also supports a file method which can load routes from a table see Modular Routing Engine below The basic routing algorithm is comprised of two stages 1 MinHop matrix calculation How many hops are required to get from each port to each LID The algorithm to fill these tables is different if you run standard min hop or Up Down For standard routing a relaxation algorithm is used to propagate min hop from every destina tion LID through neighbor switches For Up Down routing a BFS from every target is used The BFS tracks link direction up or down and avoid steps that will perform up after a down step was used 2 Once MinHop matrices exist each switch is visited and for each target LID a decision is made as to what port should be used to get to that LID This step is common to standard and Up Down routing Each port has a counter counting the number of target LIDs going through it W
141. ec cls ds Ep Ike e The package kernel ib devel include files are placed under usr src ofa kernel include These include files should be used when building kernel modules that use the stack Note that the include files 1f needed are backported to your kernel e The raw package un backported source files are placed under usr src ofa kernel lt ver gt e The script openibd is installed under etc init d This script can be used to load and unload the software stack e The script connectx port config is installed under sbin This script can be used to configure the ports of ConnectX network adapter cards to Ethernet and or InfiniBand For details on this script please see Section 4 1 Port Type Management e The directory etc infiniband is created with the files info and openib conf and connectx conf The info script can be used to retrieve Mellanox OFED installation information The openib conf file contains the list of modules that are loaded when the openibd script is used The connectx conf file saves the ConnectX adapter card s ports configuration to Ethernet and or InfiniBand This file is used at driver start restart etc init d openibd start e The file 90 ib rules is installed under etc udev rules d e If OpenSM is installed the daemon opensmd is installed under etc init d and opensm conf is installed under etc e If IPoIB configuration files are included ifcfg ib lt n gt files will be installed u
142. echnologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 6 6 1 IPolB IPoIB query is matched by PKey or by destination GID in which case this is the GID of the multi cast group that OpenSM creates for each IPoIB partition Default PKey for IPoIB partition is 0x7fff so the following three match rules are equivalent JOOS eco PO les NO ig i se Ollie any PRE US eo 7 6 6 2 SDP SDP PR query is matched by Service ID The Service ID for SDP is 0x000000000001PPPP where PPPP are 4 hex digits holding the remote TCP IP Port Number to connect to The following two match rules are equivalent sdp SS any service ia 10200 0 0 0 0 0 9 0 005150 0 00 0 0 900 0 0 0 0 OO LE EEE fo EE 7 6 6 3 RDS Similar to SDP RDS PR query is matched by Service ID The Service ID for RDS is 0x000000000106PPPP where PPPP are 4 hex digits holding the remote TCP IP Port Number to connect to Default port number for RDS is 0x48CA which makes a default Service ID 0x00000000010648CA The following two match rules are equivalent rds SSI any senvice id 2000 000000 TSCA ST 7 6 6 4 SRP Service ID for SRP varies from storage vendor to vendor thus SRP query is matched by the target IB port GUID The following two match rules are equivalent Sip target Cort umd alzi an Cardet Pogue Note that any of the above ULPs might contain target port GUID in the PR query so in order for these querie
143. ed applications SDP can be used by applications and improve their performance transparently that is without any recompilation Since SDP has the same socket semantics as TCP an existing application is able to run using SDP the difference is that the applications TCP socket gets replaced with an SDP socket It is also possible to configure the driver to automatically translate TCP to SDP based on the source IP port the destination or the application name See Section 3 4 5 The SDP protocol is composed of a kernel module that implements the SDP as a new address fam ily protocol family and a library see Section 3 4 2 that is used for replacing the TCP address family with SDP according to a policy This chapter includes the following sections e Section 3 4 2 libsdp so Library on page 54 e Section 3 4 3 Configuring SDP on page 54 e Section 3 4 4 Environment Variables on page 57 e Section 3 4 5 Converting Socket based Applications on page 57 e Section 3 4 6 BZCopy Zero Copy Send on page 65 e Section 3 4 7 Using RDMA for Small Buffers on page 65 Mellanox Technologies 53 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features 3 4 2 libsdp so Library libsdp so is a dynamically linked library which is used for transparent integration of applica tions with SDP The library is preloaded and therefore takes precedence over glibc for certain socket calls Th
144. ein city te EH E 2 MOS BE ileeks iis A a O A A SO odiano AS AO US ais aro SE a packets transmite red S recelyed UD packer loss came 2000ms AM pana mens made o OA OS SZ aio Inspecting the GID Table cat sys class infiniband mlx4 0 ports 2 gids 0 Ree OOOO OC Oe OOOO TZ is Ue call T d T TE T POD TONG ONO E RE NO G HEHE RIE 0000000000000 T According to the output we currently have one entry only Run an Example Test ibv rc pingpong Start the server first E RA eZ Local address LID Ox0000 OPN OxO0004E PSN Ox3315f6 GID AO RG Bak O LOS RIE remote address LID 0x0000 OPN Ox0 40047 PSN Uxcedede GID PEU Z ID Ore tie SOULS L 8192000 bytes in 0 01 seconds 4730 13 Mbit sec Cortes in O 0l secon S Use ter Then start the client Mellanox Technologies 45 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features Ar E O E 10h o Local address LID 200000 OPN Osx04004E PSN Ox2cdede GID essre ze Sii Seal Tenore address LID 0x0000 OPN Ox00004E PSN Ox3315f6 GID he US 202389 3 tre08 6799 ee raO tes uni CONERO 1OC0 aters In 001 seconds 15 069 use Iter Add VLANs Make sure that the 8021 q module is loaded modprobe 8021q Add the VLAN device vconfig add eth2 7 Added VLAN with VID 7 to IF eth2 it Configure an IP address for it perbene IZ Sa Examine the GID table cats clase IMEtnioanc Mix4 0 porus DTE te80 0000 0000 0000 0
145. ellanox Firmware Tools MFT package has been installed on the client machine hosti mst start hose MSE STATUS The device name will be of the form dev mst mt lt dev 1d gt pcif cr0 conf0 Use this device name to obtain the Port GUID via the following query command flint d lt MST DEVICE NAME gt q Example with ConnectX 2 QDR MHJH29B XTR Dual 4X IB QDR Port PCIe Gen2 x8 Tall Bracket ROHS R6 HCA Card CX4 Connectors as the adapter device Rogi wile de ms milo de pesa Image type Connectx FW Version LO Device ID 26428 Chip Revision BO Description Node E oral Por Sys image GUIDES 000 Ze BOS COO CES S 000700309 0010550007450 COO Rose CO0 CO0 Oi E MACs COO Ze ET BL RL SS 0O07 MOS mono ID ia UE OZ AO MOD aya E IL De MESO DZ OT ONOG Assuming that FlexBoot is connected via Port 1 then the Port GUID is 00 02 c9 03 00 00 10 39 Extracting the Port GUID Method Il An alternative method for obtaining the port GUID involves booting the client machine via Flex Boot This requires having a Subnet Manager running on one of the machines in the InfiniBand subnet The 8 bytes can be captured from the boot session as shown in the figure below 204 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 lellanox Connects FlexBoot v3 6 00 PXE 0 9 9 Open Source Boot Firmware nette 90 52 09 59 90 90 aa bc on PELIH O00 0 open
146. es Confidential Rev 1 5 2 2 1 0 A 9 A 9 1 bi eno co mo eaa a T Step 8 Now you can assign a static or dynamic IP address to your Mellanox ConnectX EN network interface Step 9 Save the init file Step 10 Close initrd Hesse ito are Sa Roc eat Ei eee o me G nos epalo SSE ae aio At this stage the modified initrd including the Ethernet driver is ready and located at tmp new init ib img gz Copy it to the original initrd location and rename it prop erly ISCSI Boot Mellanox FlexBoot enables an ISCSI boot of an OS located on a remote iSCSI Target It has a built in iSCSI Initiator which can connect to the remote iSCSI Target and load from it the kernel and initrd There are two instances of connection to the remote iSCSI Target the first is for get ting the kernel and initrd via FlexBoot and the second is for loading other parts of the OS via Loro Linux distributions such as SuSE Linux Enterprise Server 10 SPx and Red Hat Enter this direct installation initrd is capable to continue loading other parts of the OS on the be iSCSI target Other distributions may also be suitable for direct installation on iSCSI targets S prise Linux 5 1 or above can be directly installed on an iSCSI target At the end of If you choose to continue loading the OS after boot through the HCA device driver please verify that the initrd image includes the HCA driver as described in Section A 7 Configuring an iSCSI Targe
147. es around link failure by taking the long way around any 1D ring interrupted by a link failure For example consider the 2D 6x5 torus below where switches are denoted by a zA Z Mellanox Technologies 137 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 4 Ho Ho Ho ooo 3 D 2 I r S AS ALA 22 SS p y 0 Ho Ho Ho ooo x 0 1 2 3 4 5 For a pristine fabric the path from S to D would be S n T r D In the event that either link S n or n T has failed torus 2QoS would use the path S m p o T r D Note that it can do this without changing the path SL value once the 1D ring m S n T o p m has been broken by failure path segments using it cannot contribute to deadlock and the x direction dateline between say x 5 and x 0 can be ignored for path segments on that ring One result of this is that torus 2QoS can route around many simultaneous link failures as long as no ID ring is broken into disjoint segments For example if links n T and T o have both failed that ring has been broken into two disjoint segments T and o p m S n Torus 2QoS checks for such issues reports if they are found and refuses to route such fabrics Note that in the case where there are multiple parallel links between a pair of switches torus 2Q0S will allocate
148. eter AG default 12 66 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 5 2 2 Manually Establishing an SRP Connection The following steps describe how to manually load an SRP connection between the Initiator and an SRP Target Section 3 5 2 4 explains how to do this automatically e Make sure that the ib srp module is loaded the SRP Initiator is reachable by the SRP Target and that an SM is running e To establish a connection with an SRP Target and create an SRP SCSI device for that target under dev use the following command SOMO iero T vel Lb E toe puo CT a elo RE value ey LIL services H 0 value A eya Class amas o sua sido sigo las Paca vino Soja ati aio e o ei See Section 3 5 2 3 for instructions on how the parameters in this echo command may be obtained Notes Execution of the above echo command may take some time The SM must be running while the command executes Itis possible to include additional parameters in the echo command max cmd per lun Default 63 max sect short for max sectors sets the request size of a command 10 class Default 0x100 as in rev 16A of the specification In rev 10 the default was Oxff00 initiator ext Please refer to Section 9 Multiple Connections e To list the new SCSI devices that have been added by the echo command you may use either of the fol
149. ets on an FC fabric using an FCoE capable switch or gateway Key features include e TIl and pre T11 frame format e Complete hardware offload of SCSI operations in pre T11 format e Hardware offload of FC CRC calculations in pre T11 format e Zero copy FC stack in pre T11 format e VLANs and PFC Priority flow control that is PPP The FCoE feature is based on and interacts with the Open FCoE project The m1x4 fc module is designed to replace the original fcoe module and to allow using ConnectX hardware offloads Mellanox OFED also includes the following open fcoe org modules e libfc Used by the m1x4 fc module to handle FC logic such as fabric login and logout remote port login and logout fc ns transactions etc e fcoe Implements FCoE fully in software Will load instead of mlx4 fc to support T11 frame format Works on top of standard Ethernet NICs including m1x4 en See http www open fcoe org for further information on the Open FCoE project 3 2 2 FCoE Basic Usage After loading the driver userspace operations should create destroy vHBAs on required Ethernet interfaces This can be done manually by issuing commands to the driver using simple sysfs oper Mellanox Technologies 49 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features ations Alternatively it can be handled automatically by the debxd daemon if the interface is con nected to an FCoE switch supporting DCBX negotiation of the FCoE fea
150. etter to omit a Itis recommended to use the n option This option adds the initiator ext to the connect ing string See Section 3 5 2 5 for more details srp daemon has a configuration file that can be set where the default is etc srp daemon conf Use the f to supply a different configuration file that configures the targets srp_daemon is allowed to connect to The configuration file can also be used to set values for additional parameters e g max cmd per lun max sect A continuous background daemon operation providing an automatic ongoing detection and connection capability See Section 3 5 2 4 3 5 2 4 Automatic Discovery and Connection to Targets Make sure that the ib_srp module is loaded the SRP Initiator can reach an SRP Target and that an SM is running To connect to all the existing Targets in the fabric run srp_daemon e o This util ity will scan the fabric once connect to every Target it detects and then exit gt srp_ daemon will follow the configuration it finds in etc srp_daemon conf Thus it will ignore a target that is disallowed in the configuration file hai To connect to all the existing Targets in the fabric and to connect to new targets that will join the fabric execute srp daemon e This utility continues to execute until it is either killed by the user or encounters connection errors such as no SM in the fabric To execute SRP daemon as a daemon you may run run srp dae
151. etween the BridgeX and the mlx4 vnic module This connection between the mlx4_vnic modules and all available BridgeX boxes is established automatically when the mlx4 vnic module is loaded If the BridgeX is configured to remove the vNic or if the connection between the host and BridgeX is lost the vNic interface will disappear running ifconfig will not display the interface Similar to host administered vNics a network administered vNic resides on a specific vHub For further information on how to configure a network administered vNic please refer to BridgeX documentation To disable network administered vNics on the host side load mlx4 vnic module with the net_admin module parameter set to 0 3 6 2 3 VLAN Configuration A vNic instance is associated with a specific vHub group This vHub group is connected to a BridgeX external port and has a VLAN tag attribute When creating configuring a vNic you define the VLAN tag it will use via the vid or the VNICVLAN fields if these fields are absent the vNic will not have a VLAN tag The vNic s VLAN tag will be present in all EoIB packets sent by the Mellanox Technologies Tf Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features vNics and will be verified on all packets received on the vNic When passed from the InfiniBand to Ethernet the EoIB encapsulation will be disassembled but the VLAN tag will remain For example if the vNic eth23 is associated with a vHub
152. ev 1 5 2 2 1 0 Mellanox OFED Overview 1 Mellanox OFED Overview 1 1 introduction to Mellanox OFED Mellanox OFED is a single Virtual Protocol Internconnect VPI software stack based on the OpenFabrics OFED Linux stack and operates across all Mellanox network adapter solutions supporting 10 20 and 40Gb s InfiniBand IB 10Gb s Ethernet 10GigE Fibre Channel over Ethernet FCoE and 2 5 or 5 0 GT s PCI Express 2 0 uplinks to servers All Mellanox network adapter cards are compatible with OpenFabrics based RDMA protocols and software and are supported with major operating system distributions 1 2 Introduction to Mellanox VPI Adapters Mellanox VPI adapters which are based on Mellanox ConnectX and ConnectX 2 adapter devices provide leading server and storage I O performance with flexibility to support the myriad of communication protocols and network fabrics over a single device without sacrificing func tionality when consolidating I O For example VPI enabled adapters can support e Connectivity to 10 20 and 40Gb s InfiniBand switches Ethernet switches emerging Data Center Ethernet switches InfiniBand to Ethernet and Fibre Channel Gateways and Ethernet to Fibre Channel gateways e Fibre Channel over Ethernet and Fibre Channel over InfiniBand e A single firmware image for dual port ConnectX ConnectX 2 adapters that supports independent access to different convergence networks InfiniBand Ethernet or Data Center Ether
153. f links a torus with one or more radix 4 dimensions requires extra initial seed configuration See torus 2QoS conf 5 for details Torus 2QoS will detect and report when it has insufficient configuration for a torus with radix 4 dimensions Mellanox Technologies 141 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager In the event the torus is significantly degraded 1 e there are many missing switches or links it may happen that torus 2QoS is unable to place into the torus some switches and or links that were discovered in the fabric and will generate a warning in that case A similar condition occurs if torus 2QoS is misconfigured 1 e the radix of a torus dimension as configured does not match the radix of that torus dimension as wired and many switches links in the fabric will not be placed into the torus 7 5 7 4 Quality Of Service Configuration OpenSM will not program switchs and channel adapters with SL2VL maps or VL arbitration con figuration unless it is invoked with Q Since torus 2QoS depends on such functionality for cor rect operation always invoke OpenSM with Q when torus 20Q0S is in the list of routing engines Any quality of service configuration method supported by OpenSM will work with torus 2QoS subject to the following limitations and considerations For all routing engines supported by OpenSM except torus 2QoS there is a one to one correspondence between QoS level and SL Torus 2
154. hcpd conf sample DHCP configuration file dhcp patch patch file for DHCP v3 1 3 A 2 Burning the Expansion ROM Image A 2 1 Burning the Image on ConnectX ConnectX 2 4 2 7 000 or later For earlier firmware versions please follow the instructions in Sec This section is valid for ConnectX ConnectX 2 devices with firmware versions as tion A 2 2 on page 202 Prerequisites I Expansion ROM Image Mellanox Technologies 201 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 The expansion ROM images are provided as part of the Mellanox FlexBoot package and are listed in the release notes file FlexBoot release notes txt 2 Firmware Burning Tools You need to install the Mellanox Firmware Tools MFT package version 2 6 0 or later in order to burn the PXE ROM image To download MFT see Firmware Tools under www mellanox com gt Downloads Image Burning Procedure To burn the composite image perform the following steps 1 Obtain the MST device name Run FAm statt mST status The device name will be of the form mt lt dev id gt pci cr0 conf0 2 Create and burn the composite image Run flint dev msi device name brom expansion ROM amage Example on Linux do e mM A SO i Ciel loro Coira ZO ZI RONDE Om Example on Windows re Clee ae Ae an Oo A DVI A 2 2 Burning the Image on InfiniHost Ill Ex Lx Products Prerequisites I Firmware packages The appropriate firmware mlx pack
155. he current selections are This com mand is recommended for all users 2 The mpi selector command This command is a CLI equivalent of the mpi selector menu allowing for the same functionality as mpi selector menu but without the interactive menus and prompts It is suitable for scripting 6 4 Compiling MPI Applications A A valid Fortran compiler must be present in order to build the MVAPICH MPI stack and tests ha The following compilers are supported by Mellanox OFED s MVAPICH and Open MPI packages Gcc Intel and PGI The install script prompts the user to choose the compiler with which to install Mellanox Technologies 111 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 MPI Message Passing Interface the MVAPICH and Open MPI RPMs Note that more than one compiler can be selected simultane ously if desired Compiling MVAPICH Applications Please refer to http mvapich cse ohio state edu support mvapich user guide html To review the default configuration of the installation check the default configuration file usr mpi lt compiler gt mvapich lt mvapich ver gt etc mvapich conf Compiling Open MPI Applications Please refer to http www open mpi org faq category mpi apps 112 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 OpenSM Subnet Manager 7 1 Overview OpenSM is an InfiniBand compliant Subnet Manager SM It is pr
156. he following software components e Mellanox Host Channel Adapter Drivers mthca IB only mlx4 VPI which is split into multiple modules mlx4 core low level helper mlx4 ib IB mlx4 en Ethernet mlx4 fe FCoE mlx4 vnic EoIB e Mid layer core Verbs MADs SA CM CMA uVerbs uMA Ds e Upper Layer Protocols ULPs IPoIB RDS SDP SRP Initiator e MPI Open MPI stack supporting the InfiniBand RoCE and Ethernet interfaces OSU MVAPICH stack supporting the InfiniBand and RoCE interfaces MPI benchmark tests OSU BW LAT Intel MPI Benchmark Presta e OpenSM InfiniBand Subnet Manager e Utilities Diagnostic tools Performance tests e Firmware tools MFT e Source code for all the OFED software modules for use under the conditions men tioned in the modules LICENSE files e QIB Low level driver implementation for all QLogic InfiniPath PCI Express HCAs This driver was not tested by Mellanox Technologies e CXGB3 Provide RDMA and NIC support for the Chelsio S series adapters This driver was not tested by Mellanox Technologies e NES Support for the NetEffect Ethernet Cluster Server Adapters This driver was not tested by Mellanox Technologies Mellanox Technologies 17 e Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Mellanox OFED Overview e Documentation 1 3 3 Firmware The ISO image includes the following firmware items e Firmware images mlx format for all Mellanox
157. hen the When SRPHA ENABLE is set to yes see Automatic Activation of High Availabil sl driver is unloaded Manual Activation of High Availability Initialization Execute after each boot of the driver I Execute modprobe dm multipath 2 Execute modprobe 1b srp 3 Make sure you have created file etc udev rules d 91 srp rules as described above 4 Execute for each port and each HCA SN GR SO art A die IO MI This step can be performed by executing srp_daemon sh which sends its log to var log srp_daemon log Now it is possible to access the SRP LUNs on dev mapper identified by their names You can configure the etc multipath conf file to change It is possible for regular non SRP LUNSs to also be present the SRP LUNs may be af multipath behavior 72 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 occur if the SRP LUNs are in the black list of multipath Edit the blacklist section in 7 It is also possible that the SRP LUNs will not appear under dev mapper This can af etc multipath conf and make sure the SRP LUNs are not black listed Automatic Activation of High Availability e Set the value of SRPHA ENABLE in etc infiniband openib conf to yes For the changes in openib conf to take effect run etc init d openibd restart e From the next loading of the driver it will be possible to access the SRP LUNs on de
158. hen there are multiple alternative ports with same MinHop to a LID the one with less previously assigned ports is selected If LMC gt 0 more checks are added Within each group of LIDs assigned to same target port a Use only ports which have same MinHop b First prefer the ones that go to different systemImageGuid then the previous LID of the same LMC group c Ifnone prefer those which go through another NodeGuid d Fall back to the number of paths method if all go to same node 7 5 1 Effect of Topology Changes OpenSM will preserve existing routing in any case where there is no change in the fabric switches unless the r reassign lids option is specified EER T EAS option Causes Opens to reas siga ins bo all send Nodes Spec ero nas ping supneh May dass riph submek Ei Without r OpenSM attempts to preserve existing LID assignments resolv ing multiple use of same LID If a link is added or removed OpenSM does not recalculate the routes that do not have to change A route has to change if the port is no longer UP or no longer the MinHop When routing changes are performed the same algorithm for balancing the routes is invoked In the case of using the file based routing any topology changes are currently ignored The file routing engine just loads the LFTs from the file specified with no reaction to real topology Obvi ously this will not be able to recheck LIDs by GUID for disconnected nodes and LFTs for non
159. hrough DHCP then you need to copy the DHCP client which was compiled specifically to support IB Otherwise skip this step To continue with this step DHCP client v3 1 3 needs to be already installed on the machine you are working with Copy the DHCP client v3 1 3 file and all the relevant files as described below Sitio o Opio Sto Ica ao Maeda 0 Mos TRE Por o IB e o o OS elos aida Sica ro saga io seel sado sbin msi ole y Winhey ada pae reo ao ei SKOR sia roue a do lao Ecol US sue sica olaa Colas ley Lee ses MSc as y dotar bua vsti Mao ine DO do bd MS o sia opa pre E aseo ads ential ROSE ep VER EG ONE IE NETGEAR POST co O no Spee A Create a configuration file for the DHCP client as described in Section 9 3 3 1 and place 1t under tmp initrd ib sbin The following is an example of such a file called dEeLlent cont dhclient conf The value indicates a hexadecimal number 214 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 P ror a ConnectX device interlace 100 send dhcp client identifier EE AO AO O OOOO 7 eo e OS OOO OS Forio Ir Exs dovioco noe us CMG mole EE iden vit 20300 55 043 0131fe 80 00300 00 3 00300 3 00 00 023E9 02 003233133 92 Step 9 Now you can add the commands for loading the copied modules into the file init Edit the file tmp initrd ib init and add the following lines at the point you wish the IB driver t
160. in the PR MPR component mask that is on it will not match any rule that has other matching criteria besides Service ID 7 6 3 Simple QoS Policy Definition Simple QoS policy definition comprises of a single section denoted by qos ulps Similar to the advanced QoS policy it has a list of match rules and their QoS Level but in this case a match rule has only one criterion its goal is to match a certain ULP or a certain application on top of this ULP PR MPR request and QoS Level has only one constraint Service Level SL The simple policy section may appear in the policy file in combine with the advanced policy or as a stand alone policy definition See more details and list of match rule criteria below 7 6 4 Policy File Syntax Guidelines e Leading and trailing blanks as well as empty lines are ignored so the indentation in the example is just for better readability e Comments are started with the pound sign and terminated by EOL e Any keyword should be the first non blank in the line unless it s a comment e Keywords that denote section subsection start have matching closing keywords e Having a QoS Level named DEFAULT is a must it is applied to PR MPR requests that didn t match any of the matching rules e Any section subsection of the policy file is optional 7 6 5 Examples of Advanced Policy File As mentioned earlier any section of the policy file is optional and the only mandatory part of the policy file is
161. ine eno e ECP ESS WOO ESS num Leo pEr eaS PESOS DECIS Mellanox Technologies 239 Enable Quality of Service support in For FCoXX enable pre t11 mode if non Reser oevice on internal errors Li Hama Medea eran qa RO Threshold For Sao Aniline data Siani e Eo Enobi ks storno gere e E E default 1 enabled Enar oS R ETH T H erae default 1 enabled Number of LRO sessions per ring or disabled 0 default is 32 Allow the assembly of fragmented IP packets default 1 enabled Break o ans lo ee Sick e Wi O aa CAS O o si el iad ge Ole Ber priority bit mask detalle as 10 Prata SO ona cal oO Om BES Pere prrori yv Dit mask detal Ie 0 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 C 4 mlx4 fc Parameters kog exe por Viba Max outstanding FC exchanges per vir cud PEREBA tod DeF a O ENE Mak dal IE Max vHBAs allowed per port Default 2 int 240 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Appendix D ib bonding Driver for Systems using SLES10 SP3 D 1 Using the ib bonding Driver The ib bonding driver is a High Availability solution for IPoIB interfaces It is based on the Linux Ethernet Bonding Driver and was adapted to work with IPoIB The ib bonding package contains a bonding driver and a utility called ib bond to manage and control the driver operation The ib bonding driver comes with the i
162. ing command gt ethtool C eth lt x gt adaptive rx on off e Above an upper limit of packet rate adaptive moderation will set the moderation time to its highest value Below a lower limit of packet rate the moderation time will be set Mellanox Technologies 99 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Working With VPI to its lowest value To set the values for packet rate limits and for moderation time high and low values use the following command to eihtool C eths pkt rate low N Ipk rate high N Irx usecs low N rx secs hig N e To set interrupt coalescing settings when adaptive moderation is disabled use fet a a Ss NI eun NI S usec settings correspond to the time to wait after the last packet is sent received before triggering an interrupt ha e To query pause frame settings run gt DT a eth lt x gt e To set pause frame settings run lo o A Siac rox como e cm oir e To query ring size values run gt ethtool g eth lt x gt e To modify rings size run o Sao 6 Sele ee Ae e To obtain additional device statistics run ethos e To perform a self diagnostics test run i gt ethtool t elma e The mlx4 en parameters can be found under sys module mlx4 en or sys module mlx4 en parameters depending on the OS and can be listed using the command gt mo danno mlx4 en To set non default values to module parameters the following line should be added t
163. irected route packets are sent multiple times according to the c option to detect possible problematic paths on which packets may be lost Such paths are explored and a report of the suspected bad links is displayed on the standard output After scanning the fabric if the r option is provided a full report of the fabric qualities is dis played This report includes e SM report e Number of nodes and systems e Hop count information maximal hop count an example path and a hop count histo gram e All CA to CA paths traced e Credit loop report e mgid mlid HCAs multicast group and report e Partitions report e IPoIB report Furthermore if a topology file is provided ibdiagnet uses the names defined in it for In case the IB fabric includes only one CA then CA to CA paths are not reported af the output reports 168 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 8 4 3 ERROR CODES Failed to fully discover che fabric Failed to parse command line opttons Bob diro inir SES mit lie is Ta rie Failed to use local device or local porr Palled to use Topology File Failed to load regquierd Package Yok WBN E I 8 5 Ibdiagpath IB diagnostic path ibdiagpath traces a path between two end points and provides information regarding the nodes and ports traversed along the path It utilizes device specific health queries for the different devi
164. is interface by running nos ote O nio sin peta Voice Using the example of Step 2 hos als Eonia sO do O00 batas enap UNS RE Oo oO 00 A A OOO 2002002902 TORO 00 00 BROADCAST MULTICAST MTU 2044 Meerie 1 RX packets 0 errors 0 dropped 0 overruns 0 frame 0 Tx packers O errors 0 dropped 0 overruns U Carrier 0 colision sE qUe teclea l 72 Eyes UMATA RI yes UNA Step 4 AS can be seen the interface does not have IP or network addresses To configure those you should follow the manual configuration procedure described in Section 3 7 3 3 Step 5 To be able to use this interface a configuration of the Subnet Manager is needed so that the PKey chosen which defines a broadcast address be recognized see Chapter 7 OpenSM Sub net Manager 3 7 4 2 Removing a Subinterface To remove a child interface subinterface run S KS au Laveno Elis sve class nor cib mtertecs deleije cailel Using the example of Step 2 scio Uxe 000 gt sys class inec we clelece ell Le Mellanox Technologies 89 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features Note that when deleting the interface you must use the PKey value with the most significant bit set e g 0x8000 in the example above 3 7 5 Verifying IPoIB Functionality To verify your configuration and your IPoIB functionality perform the following steps Step 1 Verify the IPoIB functionality by using the ifconfig command The fo
165. kets using the same format as the traditional net stat program Without the S option it shows all the information that netstat does plus SDP data mosis sdpnetstat S Assuming that the SDP kernel module is loaded and is being used then the output of the command will be as follows hostilo sdpnetstat gt Proto Recv Q Send Q Local Address Foreign Address sdp 0 OS O as BAAS ISA 065 sdp CESSA ao Sl o AA ZIA ROSS O a ie The example output above shows two active SDP sockets and contains details about the connec tions 54 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 If the SDP kernel module is not loaded then the output of the command will be something like the following hostii o odpret Stake gt Proto Recv Q Send Q Local Address Foreign Address Met stamos ups FOr Ar INET EOD ON ass votem To verify whether the module is loaded or not you can use the 1 smod command ib_sdp1250200 The example output above shows that the SDP module is loaded If the SDP module is loaded and the sdpnetstat command did not show SDP sockets then SDP is not being used by any application 3 4 3 2 Monitoring and Troubleshooting Tools SDP has debug support for both the user space 1ibsdp so library and the ib sdp kernel mod ule Both can be useful to understand why a TCP socket was not redirected over SDP and to help find problems in the SDP implementatio
166. kground detecting new targets and establishing SRP connec tions with them daemon mode e Discover reachable SRP Targets given an infiniband HCA name and port rather than just by dev umad lt N gt where lt N gt 1s a digit e Enable High Availability operation together with Device Mapper Multipath e Have a configuration file that determines the targets to connect to l srp daemon commands equivalent to ibsrpdm UENO Clement a DO 18 equivalent to io sepan SA OI O A e UI leo o 7 4 These srp daemon commands can behave differently than the equivalent ibsrpdm command when etc srp_daemon conf is not empty ha 2 srp daemon extensions to ibsrpdm To discover SRP Targets reachable from the HCA device lt InfiniBand HCA name gt and the port lt port num gt and to generate output suitable for echo you may execute INOS el sup cessioni C Se coito HICH meme 9 Soci Mudd 7 4 To obtain the list of InfiniBand HCA device names you can either use the ibstat tool or run ls sys class infiniband ha Mellanox Technologies 69 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features To both discover the SRP Targets and establish connections with them just add the e option to the above command Executing srp daemon over a port without the a option will only display the reachable targets via the port and to which the initiator is not connected If executing with the e option it is b
167. lanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 in the InfiniBand subnet The 20 bytes can be captured from the boot session as shown in the fig ure below starting Mellanox Boot over 1B for InfiniHost 111 Ex ver 1 0 0 Loading via IB Port 2 Waiting for Infiniband link up ok oPXE 0 9 3 Open Source Boot Firmware Features iSCSI AoE FXE PXEXT weti 00550401 fe800000 00000000 00020902 00231392 o PCIOS 00 0 open TX 0 TXE 0 RA UE HCP netO 00550401 TesO0000 H 00000000 00020902 00231392 ok 1et0 11 4 3 130 255 255 255 0 Concatenate the byte 20 to the left of the captured 20 bytes then separate every byte two hexa decimal digits with a colon You should obtain the same result shown in Step 4 above Placing Client Identifiers in etc dhcpd conf The following is an excerpt of a etc dhcpd conf example file showing the format of represent ing a client machine for the DHCP server host hostel next server 11 4 3 7 filename pxelinux 0 falce died diesis Re T0 option dep client dentale e 203003 55 II te SO OO CO NOOO OO O00 00 02 eo 07 00233 13 9275 A 3 Subnet Manager OpenSM Note This section applies to ports configured as InfiniBand only FlexBoot requires a Subnet Manager to be running on one of the machines in the IB network OpenSM is part of the Mellanox OFED for Linux software package and can be used to accomplish this Note that
168. le 9 Congestion Control Manager CA Options File ceti timer Sets for all SL s the given ccti timer Default 0 When the value 1s set to 0 the CCT calculation is based on the number of nodes Table 10 Congestion Control Manager CC MGR Options File max errors 5 When number of errors exceeds max errors of send Values error window 5 receive errors or timeouts in less than error_window sec e max errors 0 zero tollerance onds the CC MGR will abort and will allow OpenSM to abort configuration on first error proceed e error window 0 mechanism dis abled no error checking cc statistics cycle 20 Enables CC MGR to collect statistics from all nodes every Default 0 cc statistics cycle seconds When the value is set to 0 no sta tistics are collected Mellanox Technologies 161 Mellanox Technologies Confidential 8 8 1 8 2 8 2 1 162 Mellanox Technologies Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities Overview The diagnostic utilities described in this chapter provide means for debugging the connectivity and status of InfiniBand IB devices in a fabric The tools are e Section 8 3 ibdiagnet of ibutils2 IB Net Diagnostic on page 164 e Section 8 4 ibdiagnet of ibutils IB Net Diagnostic on page 166 e Section 8 5 ibdiagpath IB diagnostic path on page 169 e Section 8 6 ibv devices on page 171 e Section 8 7 ibv_devinfo on page 171
169. les To print SDP usage per connect and listern to STDERR include the following statement log min level 7 destination stderr A non root user can configure libsdp so to record function calls and return values in the file tmp libsdp log lt pid gt root log goes to var log libsdp log for this example by including the following statement in 1ibsdp conf Woa mi eve 116820 Sao ME RS TETE To print errors only to syslog include the following statement lege min Level de Situation Syslog To print maximum output to the file tmp sdp debug log lt pid gt include the following statement loggn ale e ledono a Lio Kernel Space SDP Debug The SDP kernel module can log detailed trace information if you enable it using the debug level variable in the sysfs filesystem The following command performs this 56 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 host1 echo 1 gt sys module ib sdp debug level extra level parameters in the directory structure so you may need to direct the 7 Depending on the operating system distribution on your machine you may need an af echo command to sys module ib_sdp parameters debug level Turning off kernel debug is done by setting the sysfs variable to zero using the following com mand Mogli cino 0 gt sy imecmile wis sclo celous level To display debug information use the dmesg command host1 dmesg
170. les e Tree rank should be between two and eight inclusively e Switches of the same rank should have the same number of UP going port groups unless they are root switches in which case the shouldn t have UP going ports at all e Switches of the same rank should have the same number of DOWN going port groups unless they are leaf switches e Switches of the same rank should have the same number of ports in each UP going port group e Switches of the same rank should have the same number of ports in each DOWN going port group 1 Ports that are connected to the same remote switch are referenced as port group Mellanox Technologies 133 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager e All the CAs have to be at the same tree level rank If the root guid file is provided the topology does not have to be pure fat tree and it should only comply with the following rules e Tree rank should be between two and eight inclusively e All the Compute Nodes have to be at the same tree level rank Note that non com pute node CAs are allowed here to be at different tree ranks Topologies that do not comply cause a fallback to min hop routing Note that this can also occur on link failures which cause the topology to no longer be a pure fat tree Note that although fat tree algorithm supports trees with non integer CBB ratio the routing will not be as balanced as in case of integer CB
171. llanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 POISON ROS O e soto S a E oE ea UN enes HT o ees Pones stes OE O MS O esoo ne Si se sue POE ae UNS ans is eee TOS Cee Ome i e pec SUS Soano eee ae MOS TE UND yl eS Ps gi peto get ren loe B On Initiator Machines On Initiator machines manually perform the following steps 1 Run MOE rO LEAD rE 2 Run 100 Sp de ed to discover a new SRP target Prado re om es as we sheet uma dis pore O lies HOA nad por od thee Ssceome Ha 3 echo new target info gt sys class infiniband srp srp mthca0 1 add target 4 fdisk 1 will show the newly discovered scsi disks Example Assume that you use port 1 of first HCA in the system 1 e mthca0 root lab104 ibsrpdm c d dev infiniband umad0 le 000290 2002 260410 quid DIOSA cd dallo E 30 0000000000000 00250700770 Pe OZ 4 root echo rate 00209020022 ene aero Jopbiake I T dgid fe800000000000000002c90200226c 5 pkey ffff service id 0002c90200226c ETA aaa mea OR Mellanox Technologies 235 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 e You can edit etc infiniband openib conf to load the SRP driver and SRP High Avail ability HA daemon automatically that is set SRP LOAD yes and SRPHA ENABLE yes e To set up and use the HA feature you need the dm multipath driver and multipath tool e Please refer to OFED 1 x SRP s user man
172. llowing commands Mellanox Technologies 205 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 4 The following MFT commands assume that the Mellanox Firmware Tools MFT package has been installed on the client machine ha hosti mst start hostl mst status The device name will be of the form dev mst mt lt dev_id gt _pci _cr0 conf0 Use this device name to obtain the Port GUID via a query command E E TE sc Example with InfiniHost III Ex as the HCA device wee a he mia Lis ee Image type Failsafe FW Version oe 0 Romi Minor tye GCE version MO Odevy d a 18 port Z T S Version I Device ID LLO Chip Revision AO Description Node Pore POTT Sys image CUTDS OO R G SOA ONES 02007 sks 000 Ze RO ONE E T OZ SOIL SL Ss Board ID MIOS EEE VODE ED MEO TOT 9 Assuming that FlexBoot is connected via Port 2 then the Port GUID is 00 02 c9 02 00 23 13 92 Step 4 The resulting client identifier is the concatenation from left to right of 20 the QP Number the subnet prefix and the Port GUID In the example above this yields the following DHCP client identifier 20 00 55 04 0L be CO 00 00 00 00 00 00 070 AS 02 00 25513 92 Extracting the Client Identifier Method Il An alternative method for obtaining the 20 bytes of QP Number and GID involves booting the cli ent machine via FlexBoot This requires having a Subnet Manager running on one of the machines 206 Mellanox Technologies Mel
173. llowing example shows how two IB nodes are used to verify IPoIB functionality In the following example IB node 1 is at 11 4 3 175 and IB node 2 is at 11 4 3 176 icone TI e nas ZOO MO SiO o mio MA nas a os RAD Step 2 Enter the ping command from 11 4 3 175 to 11 4 3 176 The following example shows how to enter the ping command Rosta ndo o AS IAS INE SO O OANA O Bes Ok dara sia o MAS OS ts N E E ERE SS H iene gen city Te PA Shik Wome SO EE Oe US SS C7 OV tes ro A Seo oy tesi AS teles ode asi SS ge arena rr 5 packets transmitted 5 received 0 packet loss time 3999ms rtt min avg Max y UNA AVO DAS 0 soa pp 3 7 6 Bonding IPoIB To create an interface configuration script for the ibX and bondX interfaces you should use the standard syntax depending on your OS Bonding of IPoIB interfaces is accomplished in the same manner as would bonding of Ethernet interfaces via the Linux Bonding Driver e Network Script files for IPoIB slaves are named after the IPoIB interfaces e g ifcfg 1b0 e The only meaningful bonding policy in IPoIB is High Availability bonding mode number 1 or active backup e Bonding parameter fail over mac is meaningless in IPoIB interfaces hence the only supported value is the default 0 or none in SLES11 90 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 For a persistent bonding IPoIB Network configuration
174. lowing two methods Execute fdisk 1 This command lists all devices the new devices are included in this listing Execute dmesg or look at var log messages to find messages with the names of the new devices 3 5 2 3 SRP Tools ibsrpdm and srp daemon To assist in performing the steps in Section 6 the OFED distribution provides two utilities ibsrpdm and srp daemon which e Detect targets on the fabric reachable by the Initiator for Step 1 e Output target attributes in a format suitable for use in the above echo command Step 2 The utilities can be found under usr sbin and are part of the srptools RPM that may be installed using the Mellanox OFED installation Detailed information regarding the various options for these utilities are provided by their man pages Below several usage scenarios for these utilities are presented Mellanox Technologies 67 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features ibsrpdm ibsrpdm is using for the following tasks 1 Detecting reachable targets a To detect all targets reachable by the SRP initiator via the default umad device dev umad0 exe cute the following command ibsrpdm This command will output information on each SRP Target detected in human readable form Sample output TO SUDA MEROS Pork AD OTOS port GID fe800000000000000002c90200402bd5 change ID 0002 max Cone rollers 0x0 contro ie Il GUIDE
175. matching ULPs or some application on top of a ULP PR MPR requests This section has a list of per ULP or per application match rules and the SL that should be enforced on the matched PR MPR query Match rules include e Default match rule that is applied to PR MPR query that didn t match any of the other match rules e SDP e SDP application with a specific target TCP IP port range e SRP with a specific target IB port GUID e RDS e IPoIB with a default PKey e IPoIB with a specific PKey e Any ULP application with a specific Service ID in the PR MPR query e Any ULP application with a specific PKey in the PR MPR query e Any ULP application with a specific target IB port GUID in the PR MPR query Since any section of the policy file is optional as long as basic rules of the file are kept such as no referring to nonexisting port group having default QoS Level etc the simple policy section qos ulps can serve as a complete QoS policy file The shortest policy file in this case would be as follows qos ulps default 0 default SL Mellanox Technologies 149 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager end qos ulps It is equivalent to the previous example of the shortest policy file and it is also equivalent to not having policy file at all Below is an example of simple QoS policy with all the possible keywords Oss defau sdp sdp sdp rds TRONI IOS any
176. mesh it reorders the ports in dimension order before the rest of the LASH algorithm runs 7 5 6 DOR Routing Algorithm The Dimension Order Routing algorithm is based on the Min Hop algorithm and so uses shortest paths Instead of spreading traffic out across different paths with the same shortest distance it chooses among the available shortest paths based on an ordering of dimensions Each port must be consistently cabled to represent a hypercube dimension or a mesh dimension Paths are grown from a destination back to a source using the lowest dimension port of available paths at each step This provides the ordering necessary to avoid deadlock When there are multiple links between any two switches they still represent only one dimension and traffic is balanced across them unless port equalization is turned off In the case of hypercubes the same port must be used throughout the fabric to represent the hypercube dimension and match on both ends of the cable In the case of meshes the dimension should consistently use the same pair of ports one port on one end of the cable and the other port on the other end continuing along the mesh dimen sion Use R dor option to activate the DOR algorithm 7 5 7 Torus 2QoS Routing Algorithm Torus 2Q0S is a routing algorithm designed for large scale 2D 3D torus fabrics The torus 2QoS routing engine can provide the following functionality on a 2D 3D torus e Free of credit loops routing 13
177. mon found under usr sbin providing it with the same options used for running srp daemon 7 4 Make sure only one instance of run srp daemon runs per port hai To execute SRP daemon as a daemon on all the ports run srp_daemon sh found under usr sbin srp daemon sh sends its log to var log srp daemon Log It is possible to configure this script to execute automatically when the InfiniBand driver starts by changing the value of SRPHA ENABLE in etc infiniband openib conf to yes However this option also enables SRP High Availability that has some more features see Section 3 5 2 6 For the changes in openib conf to take effect run fete initt d openiba restart 70 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 5 2 5 Multiple Connections from Initiator IB Port to the Target Some system configurations may need multiple SRP connections from the SRP Initiator to the same SRP Target to the same Target IB port or to different IB ports on the same Target HCA In case of a single Target IB port i e SRP connections use the same path the configuration is enabled using a different initiator_ext value for each SRP connection The initiator_ext value is a 16 hexadecimal digit value specified in the connection command Also in case of two physical connections 1 e network paths from a single initiator IB port to two different IB ports
178. mpatible interface or via vendor specific MADs over the InfiniBand fabric In Band tool Debug utilities A set of debug utilities e g itrace mstdump isw and 12c 1 OpenSM is disabled by default See Chapter 7 OpenSM Subnet Manager for details on enabling it 22 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 For additional details please refer to the MFT User s Manual docs 1 5 Quality of Service Quality of Service QoS requirements stem from the realization of I O consolidation over an IB network As multiple applications and ULPs share the same fabric a means is needed to control their use of network resources QoS over Mellanox OFED for Linux is discussed in Chapter 7 OpenSM Subnet Manager Mellanox Technologies 23 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation 2 Installation This chapter describes how to install and test the Mellanox OFED for Linux package on a single host machine with Mellanox InfiniBand and or Ethernet adapter hardware installed The chapter includes the following sections e Section 2 1 Hardware and Software Requirements on page 24 e Section 2 2 Downloading Mellanox OFED on page 25 e Section 2 3 Installing Mellanox OFED on page 25 e Section 2 5 Uninstalling Mellanox OFED on page 39 2 1 Hardware and Software Requirements 2 1 1 Hardware
179. n User Space SDP Debug User space SDP debug is controlled by options in the 1ibsdp conf file You can also have a local version and point to it explicitly using the following command host1 export LIBSDP CONFIG FILE lt path gt libsdp conf To obtain extensive debug information you can modify libsdp conf to have the log directive produce maximum debug output provide the min level flag with the value 1 The log statement enables the user to specify the debug and error messages that are to be sent and their destination The syntax of log is as follows log destinat ron src ISSO Series aten ames i imin Level iS where options are Mellanox Technologies Do I Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features destination send log messages to the specified destination stderr forward messages to the STDERR Syslog send messages to the syslog service File asili name write messages to tne rule Var Mog ELLename kor roots HOM sa regular user write to tmp lt filename gt lt uid gt if filename is not specified as a full path otherwise write to lt path gt lt filename gt lt uid gt min level verbosity levo ior the log Seo rie SEO Ny SO EM EAS PIES connect and broter summary Useful TOn Cracking SDP usage i OELE postas Maten Summary userul ror conti Prle debug gt n Print negative matches uma ss au For contro file debug 2 prin FUNCT nc las a re Urn I lp eine EE sas Examp
180. n and known issues ibdiagnet scans the fabric using directed route packets and extracts all the available information regarding its connectivity and devices It then produces the following files in the output directory which is defined by the o option described below 8 3 1 SYNOPSYS ibdiagnet 1 dav name Pp port num Pa e Se PM Sei line fede L ER bere lbs lt 2 51 5 10 TI TTT co Sout 0Lr gt I n v 164 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 OPTIONS i device lt dev name gt Spec y the manero E Ene deceo the port used EO connect to The 1B Ten LLC damn case Of multiple devices on the local system Plm pOr e POr num Spec Phe loca det ss POr t EET oedi tO connect CEO Thee Taoro EA an pao Counters values into ibdiagnet pm p fesserie P counter lt lt PM gt lt Value gt gt Print any provided pm that is greater than its provided value able TOMO Provide a Tepo Ot the tabr ua tas i eee Indicate that UpDown credit loop checking should be done against automatically determined roots nile Specie expected dank wader se Specify the expected tank speed Skip lt IDA Check okip cher oxe Uton O ehe iris ade Applicable to the following stages due Ea Mos Ss e e dee default None SO SUE USA Species whic dies momo Che Oo Eres will be placed SS ES en NUI oie Specie Cee o ce OA Si OS clo
181. nder etc sysconfig network scripts ona RedHat machine etc sysconfig network ona SuSE machine e The installation process unlimits the amount of memory that can be pinned by a user space application See Step 5 36 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 e Man pages will be installed under usr share man Firmware e The firmware of existing network adapter devices will be updated if the following two conditions are fullfilled 1 You run the installation script in default mode that is without the option without fw update 2 The firmware version of the adapter device is older than the firmware version included with the Mellanox OFED ISO image 4 If an adapter s Flash was originially programmed with an Expansion ROM image the automatic firmware update will also burn an Expansion ROM image ha e Incase your machine has an unsupported network adapter device no firmware update will occur and the error message below will be printed Please contact your hardware vendor for help on firmware updates Error message 15 QOuerying device os Riconosci 2 3 5 Post installation Notes e 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 e The list of the modules that will be lo
182. ne option dhcp client identifier AO OA AO AO O 00 O0 202 CE 03 OOOO HOt a Connie ex devi e wen ports Configured as Ethernet comment outs the following line hardware ethernet 00 02 c9 00 00 bb Bor an fnfiniH st III Ex Comment out the following line option dhcp client identifier 162 00 55 00 41 re 80 00 00 00 00 00 00 00 02 9 03 00 00 0c 41 Qpr onleroote porh amp oreste A Ao Es OS oo Mellanox Technologies 219 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 A 9 2 iSCSI Boot Example of SLES 10 SP2 OS This section provides an example of installing the SLES 10 SP2 operating system on an iSCSI tar get and booting from a diskless machine via FlexBoot Note that the procedure described below assumes the following e The client s LAN card is recognized during installation e The iSCSI target can be connected to the client via LAN and InfiniBand Prerequisites See Section A 6 1 on page 208 executed by users with expertise in the boot process Improper application of this pro F The following procedure modifies critical files used in the boot procedure It must be A cedure may prevent the diskless machine from booting Procedure Step1 Load the SLES 10 SP2 installation disk and enter the following parameters as boot options n etsetup l WICHhISCST T Step 2 Continue with the procedure as instructed by the installation program until the SCSI Initiator Overview window
183. net a sta tistical histogram is built for each switch hop num vs number of occurrences If the histo gram reflects a specific column higher than others for a certain node then it is marked as a root node Since the algorithm is statistical it may not find any root nodes The list of the root nodes found by this auto detect stage is used by the ranking process stage S The user can override the node list manually gt S If this stage cannot find any root nodes and the user did not specify a guid list file OpenSM defaults back to the Min Hop routing algorithm ha 2 Ranking process All root switch nodes found in stage 1 are assigned a rank of 0 Using the BFS algorithm the rest of the switch nodes in the subnet are ranked incrementally This ranking aids in the process of enforcing rules that ensure loop free paths 3 Min Hop Table setting after ranking is done a BFS algorithm is run from each CA or switch node in the subnet During the BFS process the FDB table of each switch node tra 132 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 versed by BFS is updated in reference to the starting node based on the ranking rules and guid values At the end of the process the updated FDB tables ensure loop free paths through the subnet Up Down routing does not allow LID routing communication between switches that S are located inside spine
184. net per port e A unified application programming interface with access to communication protocols including Networking TCP IP UDP sockets Storage NFS CIFS iSCSI SRP Fibre Channel Clustered Storage and FCoE Clustering MPI DAPL RDS sockets and Management SNMP SMI S e Communication protocol acceleration engines including networking storage cluster ing virtualization and RDMA with enhanced quality of service e RDMA over Converged Ethernet RoCE The following ULPs can be used over RoCE uDAPL SDP RDS MPI 1 3 Mellanox OFED Package 1 3 1 ISO Image Mellanox OFED for Linux MLNX OFED LINUX is provided as ISO images one per a sup ported Linux distribution that includes source code and binary RPMs firmware utilities and doc umentation The ISO image contains an installation script called mlnxofedinstall that performs the necessary steps to accomplish the following e Discover the currently installed kernel e Uninstall any InfiniBand stacks that are part of the standard operating system distribu tion or another vendor s commercial stack 16 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 e Install the MLNX OFED LINUX binary RPMs if they are available for the current kernel e Identify the currently installed InfiniBand HCAs and perform the required firmware updates 1 3 2 Software Components MLNX OFED LINUX contains t
185. nfiniBand ports The information is available from the sysfs at sys class infiniband lt device gt ports lt port number gt counters and the supported counters are port rev packets port xmit packets port rcv data and port xmit data These counters count InfiniBand data only and do not account for Ethernet traffic For example to read the number of transmited packets run gt cat sys class infiniband lt device gt ports lt port number gt counters PORT xmi packets S RoCE traffic is not shown in the associated Etherent device s counters since it is offloaded by the hardware and does not go through Ethernet network driver hai 42 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 1 9 A Detailed Example This section provides a step by step example of using InfiniBand over Ethernet RoCE Installation and Driver Loading The MLNX OFED installation script installs RoCE as part of mlx4 and mlx4 en and other mod ules See Section 2 3 Installing Mellanox OFED for details on installation 4 The list of the modules that will be loaded automatically upon boot can be found in the configuration file etc infiniband openib conf Enter the following command to display the current run of MLNX OFED ibv devinfo Dea id lO transport InfiniBand 0 fw ver 2 7 700 giogo Gite O00 OS 0000 Syo image Jur 0002C SUE tests venele telo 7 ee Ende
186. ng ifconfig mac The mac address to assign to the vNic ib port The device name and port number in the form device name port number The device name can be retrieved by running ibv_devinfo and using the output of hca_id field The port number can have a value of 1 or 2 vid VLAN ID an optional field If it exists the vNic will be assigned the VLAN ID specified This value must be between 0 and 4095 If no vid is specified or value 1 is set the vNic will be assigned to the default vHub associated with the GW vnic_id A unique number per vNic between 0 and 32K bx The BridgeX box system GUID or system name string eport The string describing the eport name vNic Specific Configuration Files ifcfg ethX EoIB configuration can use the ifcfg ethX files used by the network service to derive the needed configuration In such case a separate file is required per vNic Additionally you need to update the ifcfg ethX file and add some new attributes to it On Red Hat Linux the new file will be of the form DEVICE eth2 HWADDR 00 30 48 7d de e4 BOOTPROTO dhcp ONBOOT yes BXADDR BX001 BXEPORT A10 INTERES VNICVLAN 3 ptr ronal Ere fd 76 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 The fields used in the file for vNic configuration have the following meaning Table 3 Red Hat Linux mIx4 vnic conf file format Field Description
187. ng steps 1 Obtain the MST device name Run Ss ESE se pais The device name will be of the form mt lt dev id gt pci crO0 con 0 2 Create and burn the composite image Run mlxourn 0 lt mst device name gt Rei Cp Tom expan olon ROMI mage Example on Linux ile de met mile a o cie SAO HEE MASAS Sa OM AS AS SO A Example on Windows da CS MS SA A ie E OC e OE ES CAS IIA One EN od TO IRON OS A 2 3 Preparing the DHCP Server in Linux Environment The DHCP server plays a major role in the boot process by assigning IP addresses for FlexBoot clients and instructing the clients where to boot from FlexBoot requires that the DHCP server run on a machine which supports IP over IB A 2 4 Configuring the DHCP Server A 2 4 1 For ConnectX Family Devices When a FlexBoot client boots it sends the DHCP server various information including its DHCP client identifier This identifier 1s used to distinguish between the various DHCP sessions The value of the client identifier is composed of a prefix ff 00 00 00 00 00 02 00 00 02 c9 00 and an 8 byte port GUID all separated by colons and represented in hexadecimal digits 1 Depending on the OS the device name may be superceded by a prefix Mellanox Technologies 203 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Extracting the Port GUID Method I To obtain the port GUID run the following commands The following MFT commands assume that the M
188. nis users telai Bot Boule fy yor oes 25 2 2 Downloading Mellanox OFED 25 2 3 Installing Mellanox OFED 25 23 Preainstallation Notes 24 ita tc ete ee EA nd ra 26 PESAN a A TE NR eee ta BARN Z 27 2 3 2 1 mInxofedinstall Return Codes 28 23 0 Installanon Procedbife sogno storni delete eni ie a 29 2 54 sinstallavion KR esulss thet ews e y ta hi aaa 35 2 35 ROstainstallation NOLES sig oot at es bee eins nr ede ed AD Sted 37 2 4 Updating Firmware After Installation 37 2 5 Uninstalling Mellanox OFED 39 Chapters Driver Features nessa ena ow Gour ee Caan iii 40 3 1 RDMA over Converged Ethernet 40 doll ROCE OVNEN sierra rei OLDE DOS KE oh rn dela 40 3 27 S MWIre Dependencias tae oo ete e a ee da ee 40 51 3 Farm ware Dependencies sorsero Pre o did 40 Fel GeneralGiidelinos te y a a dela Li police ida ee e e 40 SS Pored AD PIGG NS 20d E SIA 40 Mellanox Technologies 3 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 REOS GID TIBS ad aa al o belle dos 41 LLEOL Priority Pause Frames idad wh ee luana 41 Sai IST OSV LAN S castell ke id dit al dico eat 41 3 18 Reading Port Counters StatistiCS is pad ai btt a As de 42 SO A R E Te example eo a teatre 43 3 1
189. nly A tool command may require defining the destination device or port to which it applies dai The following addressing modes can be used to define the IB ports e Using a Directed Route to the destination Tool option d This option defines a directed route of output port numbers from the local port to the destination e Using port LIDs Tool option 1 In this mode the source and destination ports are defined by means of their LIDs If the fabric is configured to allow multiple LIDs per port then using any of them is valid for defining a port e Using port names defined in the topology file Tool option n This option refers to the source and destination ports by the names defined in the topology file Therefore this option is relevant only if a topology file is specified to the tool In this mode the tool uses the names to extract the port LIDs from the matched topology then the tool operates as in the l option Mellanox Technologies 163 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities 8 3 ibdiagnet of ibutils2 IB Net Diagnostic This version of ibdiagnet is included in the ibutils2 package and it is not run by default after installing Mellanox OFED To use this ibdiagnet version and not that of the ibu af tils package you need to specify the full path opt bin ibdiagnet Please see ibutils2_ release notes txt for additional informatio
190. nning the tool 1s assumed to be the source 8 5 1 SYNOPSYS ibdiagpath n lt sre mame lds name lt lre lid da sel E2 P AS Count gt MA ea opa a se oye name me dev nnde e p Dome aam oro a A ES oO on cl P lt lt PM counter gt lt Trash Limit gt gt OPTIONS Mellanox Technologies 169 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities lt She rane els gt name Names or tne sources ano destination pores les define den elie Eo polo gy mike SOME E may HI ced local port To raono umed Cto be Ene source dee OA pn e SCURE 2 Sie Oo E S lt sys name gt i lt dev index gt TOR pork ai R SOME dite lly I A ee 18 lt 2 5 5S 103 P lt PM lt Trash gt gt chil hedp V version sales 8 5 2 Output Files Table 13 ibdiagpath Output Files Souseckandidc stando De Sour Mays ioc omre tedio Ene Moca ore as assumed Lo T ene source Directed route from the local node which is the source and the destination node The minemal number Or packets to b s nt across each link default 100 Enable verbose mode Specifies the topology file name Specifies the local system name Meaningful only if a topology file is specified Specifies the index of the device of the port uced to Connect Lo the UB fabric anicase or multiple devices on the local system Species the local device S port number usal uo COMMSSE toO th
191. nostic Utilities MT47396 AUS Ss oggetti ik L Manos Technologues Ux00US OLI A Sutton ua OO Osetia Ai SMTA T OG Mensa Mel III Mellanox Technologies OOOO hanne MA apre OE Utd SA HDR REES OA SA Do 00000 ZIE ne dao ter om eau UA UA aca cee EH 135 AS la ae TARAS TAR OS quad OS A Soo a Vowihe gt E IG T E H 3 Dump all Lids in the range 3 to 7 with valid out ports of the switch with Lid 2 gt Llorourte 2 3 7 Unicast ads O Ope sl OE SWE Eeoa a ci ESO Ae SO a a intimi ocale LI Mellano Technologres intel Our Destination POET Info LEI 73 AG OOOO T SES peri qund Ox00Ub SEE TERO UMA So nas cole ih Me Nanos pre clio llo Sas en BEGE e OO O anna cra dare Seu OSOS OUR 10s Oe sil EH SS AMIA Ranne RE ER TE e LE O SO ASIA Dea Ss valid ids dumped 4 Dump all Lids with valid out ports of the switch with portguid 0x000b8cffff004016 ARDORE RIO Serr ney O42 06 Unire Ss El EROS ANG H mee vob iS O G TES S E Melano Techno logres LIC OUT Destination MTA OG 182 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 5 Dump all non empty mlids of switch with Lid 3 Mellanox Technologies 183 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 8 12 smpquery 1 8 4 Applicable Hardware All InfiniBand devices Description Provides a basic subset of standard SMP queries to quer
192. nsider a case that torus 2QoS cannot route without deadlock two failed switches adjacent in a dimension that is not the last dimension routed by DOR here the failed switches are O and T 5 boo l I l I I I 4 boo I I I I 3 D I I I I I 2 I G E l I l l I 1 0m 5 p 0 T mT I I I I I y 0 Ho boo I I l I I I x 1 2 3 4 5 In a pristine fabric torus 2QoS would generate the path from S to D as S n O T r D With failed switches O and T torus 2QoS will generate the path S n I q r D with illegal turn at switch I and with hop I q using a VL with bit 1 set In contrast to the earlier examples the second hop after the illegal turn q r can be used to construct a credit loop encircling the failed switches 7 5 7 2 Multicast Routing Since torus 2QoS uses all four available SL bits and the three data VL bits that are typically avail able in current switches there is no way to use SL VL values to separate multicast traffic from uni cast traffic Thus torus 2QoS must generate multicast routing such that credit loops cannot arise from a combination of multicast and unicast path segments It turns out that it is possible to con Mellanox Technologies 139 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager struct spanning trees for multicast routing th
193. o be loaded The order of the following commands for loading modules is critical echo loading oi sbin insmod lib modu les ipvo ko echo loading IB driver soa vaso sbin insmod oDin insmod On fimo Sin inc mod slo ay asi sbin insmod Scan MISMO O T n mod Dna AS mod sbin insmod sbin insmod Si ine mod sbin insmod A sus mo mee do ia e Lilo modu e aus le come a io modules Ws o mere iso o mocos Woy alos o Lado modu bco aus aus emo lso US neces Wey alo UIC oon We ol is cule s uo do tem xe Ao modue ey o Uda is modules do anaemia S io modules o rama vem ko us nociles ilo ema em Ie e moduk c To me cons go lib modules ib mlx4 ib ko us Tike Gunna alley alo laca les The following command loading ipoib_helper ko is not required for all OS kernels Please check the release notes Ba a soja ido T H dio pelo ned oeie LaS Mellanox Technologies 215 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 10 Step 11 Step 12 Step 13 eoa a a E deo o IE us Foo ORO In case of interoperability issues between iSCSI and Large Receive Offload LRO change the last command above as follows to disable LRO Soto ncmod y iby modules mo oooO 0 Now you can assign an IP address to your IB device by adding a call to ifconfig or to the DHCP client in the init file after loading the modules If you wish to use the DHCP client then you need to
194. o the file etc modprobe conf DOPE ron musa En eni lt We een AI 100 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Mellanox Technologies 101 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Performance D 5 1 5 2 Performance General System Configurations The following sections describe recommended configurations for system components and or inter faces Different systems may have different features thus some recommendations below may not be applicable PCI Express PCle Capabilities Table 5 Recommended PCle Configuration PCIe Generation Speed Width Max Payload size Max Read Request Note For VPI Ethernet adapters with ports configured to run 40Gb s or above it is recom mended to use an x16 PCIe slot to benefit from the additional buffers allocated by the system BIOS Power Management Settings e Set BIOS power management to Maximum Performance e On Intel Processors Only Disable C states of PCI Express Note that these performance optimizations may result in higher power consumption Intel Hyper Threading Technology 7 4 This section applies to Intel processors only supporting Hyper Threading hai For latency and message rate sensitive applications it is recommended to disable Hyper Thread Ing Performance Tuning for Linux You can use the Linux sysctl command to modify default system net
195. of the discovered iSCSI target s will be displayed in the iSCSI Initiator Discovery win dow Select the target that you wish to connect to and click Connect Preparation y Language y License Agreement sp Disk Activation m e System Analysis Portal Address Target Name Connected a Time Zone 10 4 3 7 3260 1 iqn 2007 08 7 3 4 10 iscsibootFalse iSCSI Initiator Discovery Installation Installation Summary e Perform Installation Configuration Root Password Hostname Network Customer Center Online Update a Service a Users a Clean Up a Release Notes Hardware Configuration Connect z If no iSCSI target was recognized then either the target was not properly installed or 4 no connection was found between the client and the iSCSI target Open a shell to ping the iSCSI target you can use CTRL ALT F2 and verify that the target is or is not accessible To return to the graphical installation screen press CTRL ALT F7 222 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Step 5 The iSCSI Initiator Discovery window will now request authentication to access the SCSI tar get Click Next to continue without authentication unless authentication is required Preparation Y Language License Agreement gt Disk Activation e System Analysis e Time Zone iSCSI Initiator Discovery
196. offloads 1 4 3 Mid layer Core Core services include management interface MAD connection manager CM interface and Subnet Administrator SA interface The stack includes components for both user mode and ker nel applications The core services run in the kernel and expose an interface to user mode for verbs CM and management 1 4 4 Open FCoE The FCoE feature is based on and interacts with the Open FCoE project Mellanox OFED includes the following open fcoe org modules libfc and fcoe See Section 3 2 Fibre Channel over Ethernet 1 4 5 ULPs IPoIB The IP over IB IPoIB driver is a network interface implementation over InfiniBand IPoIB encapsulates IP datagrams over an InfiniBand connected or datagram transport service IPoIB pre appends the IP datagrams with an encapsulation header and sends the outcome over the InfiniBand transport service The transport service is Reliable Connected RC by default but it may also be configured to be Unreliable Datagram UD The interface supports unicast multicast and broadcast For details see Chapter 3 7 IP over InfiniBand RoCE RDMA over Converged Ethernet RoCE allows InfiniBand IB transport over Ethernet net works It encapsulates IB transport and GRH headers in Ethernet packets bearing a dedicated ether type 20 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 RDS Reliable Datag
197. ogies Confidential Rev 1 5 2 2 1 0 S Setting SRPT_LOAD yes in etc infiniband openib conf is not enough as it only loads the ib srpt module but does not load scst not its dev_handlers The sest disk module pass thru mode of SCST is not supported by Mellanox OFED Example 1 Working with VDISK BLOCKIO mode Using the md0 device sda and cciss c1d0 a FT fa gt ye th o modprobe scst modprobe scst_vdisk echo open vdisk0 dev md0 BLOCKIO gt proc scsi_tgt vdisk vdisk echo open vdisk1 dev sda BLOCKIO gt proc scsi_ tgt vdisk vdisk echo open vdisk2 dev cciss c1d0 BLOCKIO gt proc scsi_tgt vdisk vdisk echo add vdisk0 0 gt proc scsi_tgt groups Default devices echo add vdisk1 1 gt proc scsi tgt groups Default devices echo add vdisk2 2 gt proc scsi tgt groups Default devices Example 2 working with scst_vdisk FILEIO mode Using md0 device and file 10G file a b modprobe scst modprobe scst_vdisk echo open vdisk0 dev md0 gt proc scsi_tgt vdisk vdisk echo open vdisk1 10G file gt proc scsi tgt vdisk vdisk echo add vdisk0 0 gt proc scsi tgt groups Default devices echo add vdisk1 1 gt proc scsi tgt groups Default devices 2 Run Hor acicate tone dec peste AO o eo e F r SLES T1 MOSTO E O aio For SLES 11 please ignore the following error messages in var log messages when loading ib srpt to SLES 11 distribution s kernel 234 Mellanox Technologies Me
198. ogrammable with a sequence of VL weight pairs and a maximal number of high priority credits to be processed before low priority is served e Packets carry class of service marking in the range 0 to 15 in their header SL field e Each switch can map the incoming packet by its SL to a particular output VL based on a programmable table VL SL to VL MAP in port out port SL e The Subnet Administrator controls the parameters of each communication flow by pro viding them as a response to Path Record PR or MultiPathRecord MPR queries DiffServ architecture IETF RFC 2474 amp 2475 is widely used in highly dynamic fabrics The fol lowing subsections provide the functional definition of the various software elements that enable a DiffServ like architecture over the Mellanox OFED software stack 3 8 2 QoS Architecture QoS functionality is split between the SM SA CMA and the various ULPs We take the chronol ogy approach to describe how the overall system works 1 The network manager human provides a set of rules policy that define how the network is being configured and how its resources are split to different QoS Levels The policy also define how to decide which QoS Level each application or ULP or service use 92 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 2 The SM analyzes the provided policy to see 1f 1t 1s realizable and performs the necessary f
199. on unes 0x00 8 8 ibdev2netdev ibdev2netdev enables association between IB devices and ports and the associated net device Additionally it reports the state of the net device link 8 8 1 SYNOPSYS ela Wes well lal OPTIONS v Enable verbose mode Adds additional information such as Device ID Pare Number Card Nane Pirmware version 1B pore States h Print help messages Example NESTOR EE IN loo de one de Mi O MT CA o VUE ZE CONIODR T Ie ACTIVE gt eth5 Down Il RON ASAS O IS ECONMODR E Ze Ona ah ACTIVE gt 1b0 Down mlx4 0 MT26428 MT1006X00034 FALCON QDR ZI oO OE EA DONN gt ibl Down Mixa ML ds METODO as Duel Pore e e 9200 pore i DOWN T DON mA MAG de OZ SAUNA awk Duel Pore iw 24000 iS 2 iON gt eth3 Down sw417 BXOFED 1 5 2 20101128 1524 ibdev2netdev MENO tet gt eines O wins Xp ee ooo IEA OZ gt ibl Down Il V nix pore eth2 Down NO Il V Moe deporre eth3 Down Mellanox Technologies 173 Mellanox Technologies Confidential 8 9 Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities ibstatus Applicable Hardware All InfiniBand devices Description Displays basic information obtained from the local InfiniBand driver Output includes LID SMLID port state port physical state port width and port rate Synopsis Los talus Ascer Te nane R sue ES Table 15 lists the various flags of the command Tabl
200. oot Firmware net 00 02 c9 00 00 060 aa bc on PCIO2 00 0 open LLink down TX TXE 0 RX 0 RXE 0 Link status Not connected 0x38086001 3 Waiting for link up on netO ok DHCP netO 00 02 c9 00 001 060 aa bc ok neto 11 4 3 130 255 255 255 0 gw 0 0 0 0 Booting from filename pxelinux 0 tftp 11 4 3 7 pxelinux 0O For InfiniHost III Ex PXE 0 9 3 Open Source Boot Firmware Features TFIP iSCSI AoE PXE PXEXT leto 11 4 3 130 255 255 255 0 Next FlexBoot attempts to boot as directed by the DHCP server Mellanox Technologies 209 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 A 7 Command Line Interface CLI A 7 1 Invoking the CLI When the boot process begins the computer starts its Power On Self Test POST sequence Shortly after completion of the POST the user will be prompted to press CTRL B to invoke Mel lanox FlexBoot CLI The user has few seconds to press CTRL B before the message disappears see figure Mellanox ConnectX FlexBoot v3 0 000 gPXE http etherboot org HZ EI 0 COU PCI3 O9 PnP BES PMMOC4O0BZO CHOO Press Ctrl B to configure MLN FlexBoot 33 60 000 PCI O2 00 60 _ Alternatively you may skip invoking CLI right after POST and invoke it instead right after Flex Boot starts booting Once the CLI is invoked you will see the following prompt gPXE gt A 7 2 Operation The CLI resembles a Linux shell where the user can run commands to
201. ostic Utilities Mellanox OFED includes the following two diagnostic packages for use by network and data cen ter managers e ibutils Mellanox Technologies diagnostic utilities e infiniband diags OpenFabrics Alliance InfiniBand diagnostic tools 1 4 9 Mellanox Firmware Tools The Mellanox Firmware Tools MFT package is a set of firmware management tools for a single InfiniBand node MFT can be used for e Generating a standard or customized Mellanox firmware image e Querying for firmware information e Burning a firmware image to a single InfiniBand node MFT includes the following tools mlxburn This tool provides the following functions e Generation of a standard or customized Mellanox firmware image for burning in bin binary or img format e Burning an image to the Flash EEPROM attached to a Mellanox HCA or switch device e Querying the firmware version loaded on an HCA board e Displaying the VPD Vital Product Data of an HCA board flint This tool burns a firmware binary image or an expansion ROM image to the Flash device of a Mellanox network adapter bridge switch device It includes query functions to the burnt firm ware image and to the binary image file spark This tool burns a firmware binary image to the EEPROM s attached to an InfiniScaleIII switch device It includes query functions to the burnt firmware image and to the binary image file The tool accesses the EEPROM and or switch device via an I2C co
202. ovided as a fixed flow execut able called opensm accompanied by a testing application called osmtest OpenSM implements an InfiniBand compliant SM according to the InfiniBand Architecture Specification chapters Man agement Model 13 Subnet Management 14 and Subnet Administration 15 7 2 opensm Description opensm 1s an InfiniBand compliant Subnet Manager and Subnet Administrator that runs on top of the Mellanox OFED stack opensm performs the InfiniBand specification s required tasks for 1n1 tializing InfiniBand hardware One SM must be running for each InfiniBand subnet opensm also provides an experimental version of a performance manager opensm defaults were designed to meet the common case usage on clusters with up to a few hun dred nodes Thus in this default mode opensm will scan the IB fabric initialize it and sweep occasionally for changes opensm attaches to a specific IB port on the local machine and configures only the fabric con nected to it If the local machine has other IB ports opensm will ignore the fabrics connected to those other ports If no port is specified opensm will select the first best available port opensm can also present the available ports and prompt for a port number to attach to By default the opensm run is logged to two files var log messages and var log opensm log The first file will register only general major events whereas the second file will include details of reported
203. p only when corresponding External Port is up default 0 For all module parameters list and description run di AS O I To check the current module parameters run Mixa vie into P 3 6 4 2 vNic Interface Naming The mlx4 vnic driver enables the kernel to determine the name of the registered vNic By default the Linux kernel assigns each vNic interface the name eth lt N gt where lt N gt is an incremental num ber that keeps the interface name unique in the system The vNic interface name may not remain consistent among hosts or BridgeX reboots as the vNic creation can happen in a different order 82 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 each time Therefore the interface name may change because of a first come first served kernel policy In automatic network administered mode the vNic MAC address may also change which makes it difficult to keep the interface configuration persistent To control the interface name you can use standard Linux utilities such as IFRENAME 8 IP 8 or UDEV 7 For example to change the interface eth2 name to eth bx01 a10 run 1frename 1 eth2 n eth bx01 al0 To generate a unique vNic interface name use the mlx4 vnic_info script with the u flag The script will generate a new name based on the scheme SER pe pene aa For example if vNic eth2 resides on an InfiniBand card on the PCI BUS ID 0a 00
204. pi selector RPM Preparing it it it Ht Ht Ht HH HH HH HH THEE EEE EE EEE EE EE EEE EE EEE EEE EEE EEE mpi selector it it it Ht Ht Ht Ht HH HH HH HH HEHE EE EEE E EEE EEE EEE EEE EE EE Install user level RPMs Preparing iat ae at at ae ae ae ae A Hee A Hee A He EA AEE AEE Ea aE aa aaa libibverbs iat He aE at ae ae aE ae a Ae eA Hee A Ae EAE EAE EE a a libibumad iat ae at at ae aE aE ae A Hee A Hee A He EA AE a AEE a St aaa ae Mellanox Technologies 29 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Installation libibverbs iat ae at at ae ae aE ae A He eA HEE A He eA AEE ASAE EE aaa aaa libibumad iat ae ae at ae ae aE ae A He EA Hee RR tt rt aaa libibumad devel Ht Hit Ht Ht HH tH tH tH tH EH EH EH HE HE HE HE HE HE HE HH HH FH HE SF HF HF librdmacm iit He at at ae ae at ae A Ae eA Hee A AEE EEE opensm libs tat ae ae at ae ae ae ae Hee A Hee A Ae tt tt tt E aa aaa aaa librdmacm itt ae at a ae A Hee A HEE A E AE a APE a AEE aaa aaa eee libibmad iit at ae A ae ae ae Ae He A Hee SAE eee AE EAE aa aaa mvapich intel iat ae ae at ae aE at ae A Hee A AEE A AE EAE EAE EAE rt aaa libibverbs devel itt ae a Ae He a Ae eA Ae eA Ae a tt a APE aaa aaa aaa openmpi intel iat ae ae at ae ae ae ae a Ae eA Hee A AEE A AE tt EAE a aaa libmverbs iat ae aE at ae ae aE He At tt A HE EA HE a APE a APE aaa aaa eee opensm libs iat ae ae at ae ae ae ae A He eA Hee A Ae eA AE EAE EE aaa aaa aaa libmthca iat ae ae at ae ae ae ae Ae He A Hee
205. pport through connected mode IPoIB also supports the following software based enhancements e Large Receive Offload e NAPI e Ethtool support This chapter describes the following e IPoIB mode setting Section 3 7 2 e IPoIB configuration Section 3 7 3 e How to create and remove subinterfaces Section 3 7 4 e Howto verify IPoIB functionality Section 3 7 5 e The ib bonding driver Section 3 7 6 IPoIB Mode Setting IPoIB can run in two modes of operation Connected mode and Datagram mode By default IPoIB is set to work in Connected mode This can be changed to become Datagram mode by editing the file etc infiniband openib conf and setting SET IPOIB CM no After changing the mode you need to restart the driver by running Ste edi nio JM rE To check the current mode used for out going connections enter cat sys class net ib lt n gt mode IPolB Configuration Unless you have run the installation scriptmlnxofedinstall with the flag n then IPoIB has not been configured by the installation The configuration of IPoIB requires assigning an IP address and a subnet mask to each HCA port like any other network adapter card 1 e you need to prepare a file called 1fcfg 1b lt n gt for each port The first port on the first HCA in the host is called interface 1b0 the second port is called 1b1 and so on An IPoIB configuration can be based on DHCP Section 3 7 3 1 or on a static configuration Sec tion 3 7 3 2
206. presence of a BridgeX gateway in order to work properly The EoIB driver supports a mixture of host and network administered vNics 3 6 2 1 EolB Host Administered vNic In the host administered mode vNics are configured using static configuration files located on the host side These configuration files define the number of vNics and the vHub that each host administered vNic will belong to i e the vNic s BridgeX box eport and VLAN id properties The mlx4_vnic_confd service is used to read these configuration files and pass the relevant data to the mlx4 vnic module EoIB Host Administered vNic supports two forms of configuration files e Central Configuration File etc infiniband mlx4 vnic conf e vNic Specific Configuration Files 1fcfg ethX Both forms of configuration supply the same functionality If both forms of configuration files exist the central configuration file has precedence and only this file will be used Central Configuration File etc infiniband mlx4_vnic conf The mlx4 vnic conf file consists of lines each describing one vNic The following file format is used Mellanox Technologies 15 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features alle Sd E Velo eee E ES O Saleh 4 bx BX001 eport A11 The fields used in the file have the following meaning Table 2 mlx4_vnic conf file format Field Description name The name of the interface that is displayed when runni
207. previously routed the fabric successfully Even if the other engine is capa ble of routing a torus without credit loops applications that built connections with path SL values granted under torus 2QoS will likely experience message deadlock under routing generated by a different engine unless they repath To verify that a torus fabric is routed free of credit loops use ibdmchk to analyze data collected via ibdiagnet vlr 7 6 Quality of Service Management in OpenSM 7 6 1 Overview When Quality of Service QoS in OpenSM is enabled using the Q or qos flags OpenSM looks for a QoS Policy file During fabric initialization and at every heavy sweep OpenSM parses the QoS policy file applies its settings to the discovered fabric elements and enforces the pro vided policy on client requests The overall flow for such requests is as follows e The request is matched against the defined matching rules such that the QoS Level def inition is found e Given the QoS Level a path s search is performed with the given restrictions imposed by that level Figure 3 QoS Manager 7 QoS Policy Config File InfiniBand subnet with QOS OFED 1 3 osm 7 based nodes OSM There are two ways to define QoS policy e Advanced the advanced policy file syntax provides the administrator various ways to match a PathRecord MultiPathRecord PR MPR request and to enforce various QoS constraints on the requested PR MPR e Simpl
208. protocol for the FCoE feature availability vHBAs are automatically created on these interfaces if the FCoE switch is configured for automatic FCoE negotiation e MTU if MIU of the Ethernet device is changed from the default 1500 put the cor rect value here Configure the mlx4 en Ethernet driver to support PFC Add the following line to the file etc modprobe conf and restart the network driver Pe oa ml lO O O Ee 3 2 2 2 Starting FCoE Service Make sure the network is up modprobe mlx4 en Then run oe aaa start 50 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 vHBAs will be instantiated on DCBX monitored interfaces and SCSI LUNs will get mapped For Manual instantiation of VHBAs please see Section 3 2 3 1 Manual vHBA Control 3 2 2 3 Stopping FCoE Service Run gt etc init d mlxfe stop 4 Only when the mlxfc service is stopped and the mlx4_en module is removed can the mlx4 core module be removed as well ha 3 2 2 4 Enabling Disabling FCoE Services To enable disable FCoE upon boot please edit the file etc mlxfc mlxfc conf andsetthe following variables to either YES or NO Start ECOE FCOE Yes No 3 2 3 FCoE Advanced Usage Advanced usage will probably be needed when connected to FCoE switches that do not support the Cisco like FCoE DCBX auto negotiation 3 2 3 1 Manual vHBA Control Manual control allows creating and
209. ram Sockets RDS is a socket API that provides reliable in order datagram deliv ery between sockets over RC or TCP IP For more details see Chapter 3 3 Reliable Datagram Sockets SDP Sockets Direct Protocol SDP is a byte stream transport protocol that provides TCP stream semantics SDP utilizes InfiniBand s advanced protocol offload capabilities Because of this SDP can have lower CPU and memory bandwidth utilization when compared to conventional imple mentations of TCP while preserving the TCP APIs and semantics upon which most current net work applications depend For more details see Chapter 3 4 Sockets Direct Protocol SRP SRP SCSI RDMA Protocol is designed to take full advantage of the protocol offload and RDMA features provided by the InfiniBand architecture SRP allows a large body of SCSI software to be readily used on InfiniBand architecture The SRP driver known as the SRP Initiator differs from traditional low level SCSI drivers in Linux The SRP Initiator does not control a local HBA instead it controls a connection to an I O controller known as the SRP Target to provide access to remote storage devices across an InfiniBand fabric The SRP Target resides in an I O unit and provides storage services See Chapter 3 5 SCSI RDMA Protocol and Appendix B SRP Target Driver uDAPL User Direct Access Programming Library uDAPL is a standard API that promotes data center application data mes
210. re enhanced to carry the Service ID which is a 64bit value A new field QoS Class is also provided A new capability bit describes the SM QoS support in the SA class port info This approach pro vides an easy migration path for existing access layer and ULPs by not introducing new set of PR MPR attributes 3 8 3 Supported Policy The QoS policy which is specified in a stand alone file is divided into the following four subsec tions I Port Group A set of CAs Routers or Switches that share the same settings A port group might be a partition defined by the partition manager policy list of GUIDs or list of port names based on NodeDe scription II Fabric Setup Defines how the SL2VL and VLArb tables should be setup 7 4 In OFED this part of the policy is ignored SL2VL and VLArb tables should be config ured in the OpenSM options file opensm opts Mellanox Technologies 93 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features III QoS Levels Definition This section defines the possible sets of parameters for QoS that a client might be mapped to Each set holds SL and optionally Max MTU Max Rate Packet Lifetime and Path Bits 7 4 Path Bits are not implemented in OFED di IV Matching Rules A list of rules that match an incoming PR MPR request to a QoS Level The rules are processed in order such as the first match is applied Each rule is built out of a set of match expressions which
211. rectory elos ed an MPN tin he OLE directory provided by the o flag ade chilo o ns MOON SiS Su oleo ent date Opa also lo E eo subnet discovery stage Note Some of the checks require actual subnet discovery avide orco idonei eri pese ae These checks are Duplicated zero guids link state SMs STATUS o he SRS Prints the help page information V yersion Prints the version of the tool vars Printe the tools environment varladoles and tnerr values Mellanox Technologies 167 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities 8 4 2 Output Files Table 12 ibdiagnet of ibutils Output Files ibdiagnet log A dump of all the application reports generate according to the provided flags ibdiagnet Ist List of all the nodes ports and links in the fabric ibdiagnet fdbs A dump of the unicast forwarding tables of the fabric switches ibdiag A dump of the multicast forwarding tables of the fabric switches net mcfdbs ibdiagnet masks In case of duplicate port node Guids these file include the map between masked Guid and real Guids ibdiagnet db A dump of the internal subnet database This file can be loaded in later runs using the load db option In addition to generating the files above the discovery phase also checks for duplicate node port GUIDs in the IB fabric If such an error is detected it is displayed on the standard output After the discovery phase is completed d
212. rieving EoIB Information 0 0 00 0c ce eee REA 79 o male SVING MAIO Sct sheen e id oe atk ate Rae alee SE eae eet 79 920 952 TELMO SE Sateen A A DAR Cee are 80 So Ste Cast La Ge pe dues dedos Pore eee lan ti 80 50 54 Bondad Lee Rh GRE eae eas 81 4 Mellanox Technologies J Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 26 3 JUMDO PrE S e asea Saa ees 81 3 6 4 Advanced BOB CUINA ne ede Peete Ia 82 22641 Module Parame psi ale ail ariani era st 82 30427 ANG Interface Naminis cra ed dre lol i heed 82 3 7 IP over InfiniBand 83 SL TOG UCONN een Beate e AS Wit acta ae rta ag 83 lia TPB Mode Seno 23h oh tebe eee hee o Se ee Aine 84 K IPoIB CONN SUPA Ol ss ssi ontario ee ae She ee eee es anes 84 3 7 3 1 IPoIB Configuration Based on DHCP naaa e eenn 85 3 7 3 2 Static IPoIB Configuration LL 86 3 7 3 3 Manually Configuring IPoIB LL 87 Dale SUONEN ES A TE R E EIA Bee as 88 SAL Creatine a Subntedac ii iL delie 88 AZ Removing a SUDNICE sir cotas al dirt See iris 89 37 VertymoTPolB Funcional ti a ai 90 355 0 Bondino TROTE ets o id a da 90 3 8 Quality of Service 91 01 Quality or Senice OVEIMICW 14 os bol big zacatecas oeease teeta hoses 91 I S OOS ATB nta sesso bad OSTRA CERRO RS ea i 92 5 629 SUP POned PONCYsc2us if
213. rise Server 10 SP2 Image append showopts ide n your disk If you have multiple Linux systems installed YaST can try to find them and merge their menus Add Edit Delete Set as Default ra Era 228 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Step 16 In the Optional Kernel Command Line Parameter field append the following string to the end of the line ibft mode off include a space before the string Click OK and then Finish to apply the change Section Name al Boot Loader Settings Section Management Use Section Name to specify the boot loader section name The section name must be unique Section Editor Section Settings Selecting Do not Section Name SUSE Linux Enterprise Server 10 SP2 verify Filesystem before Booting will skip all file system checks Optional Kernel Section Settings Command Line Parameter lets you define additional Optional Kernel Command Line Parameter parametersto passto the kernel _ Do not verify Filesystem before Booting resume dev sdal splash silent showopts ibft mode off Kernel Image defines Kernel Image the kernel to boot boot vmlinuz v Browse Either enter the name i directly or choose via Initial RAM Disk Browse bootlinitrd Y Browse Initial RAM Disk if H st Device not empty defines the ai initial ramdisk to use dev sda
214. routes across such links in a round robin fashion based on ports at the path destina tion switch that are active and not used for inter switch links Should a link that is one of several such parallel links fail routes are redistributed across the remaining links When the last of such a set of parallel links fails traffic is rerouted as described above Handling a failed switch under DOR requires introducing into a path at least one turn that would be otherwise illegal i e not allowed by DOR rules Torus 2QoS will introduce such a turn as close as possible to the failed switch in order to route around it n the above example suppose switch T has failed and consider the path from S to D Torus 2QoS will produce the path S n I r D rather than the S n T r D path for a pristine torus by introducing an early turn at n Normal DOR rules will cause traffic arriving at switch I to be forwarded to switch r for traffic arriving from I due to the early turn at n this will generate an illegal turn at I Torus 2QoS will also use the input port dependence of SL2VL maps to set VL bit 1 which would be otherwise unused for y x z x and z y turns 1 e those turns that are illegal under DOR This causes the first hop after any such turn to use a separate set of VL values and prevents deadlock in the presence of a single failed switch For any given path only the hops after a turn that is illegal under DOR can contribute to a credit loop that leads
215. ry 0 000 cee eee eens 141 7 5 7 4 Quality Of Service Configuration LL 142 7 5 7 5 Operational Considerations LL 142 7 6 Quality of Service Management in OpenSM 143 T CONCE Wal EDS A alta an ea 143 Pos Advanced Jos Foley tiles add oe oe los A a ie 143 63 Simple OOS Policy Delito roster el des aa 145 ROA Poley Fille Syntax Guidelines iia a adds 145 765 Examples of Advanced Poliey File i si oinline aa 145 7 6 6 Simple QoS Policy Details and Examples 0 0 0 0 00 ccc ees 149 cool IPoIB i ica sio ad alle Liar 151 H E et 151 TOO ID Sd st Baren A srt RAN RS ee ate SE 151 cop 2 tiri A i ii ni ll ech eens ee eh aes 151 ROOS MPA A re aren ene AA 151 7 6 7 SL2VL Mapping and VL Arbitration LL 152 08 Deployment Example it eta lalla ila debe iste 153 7 7 QoS Configuration Examples 154 JaA Typical HPC Example MPL and Lustre 2 Licio pratica dks 154 ll BDC SOA tier e b and SRP esiliati need MES 155 TI EDC E ET IPoIB RDS SRP ts oe aloe he ae ky 156 7 8 Adaptive Routing 157 Lol SOV STATEN infon e inedita denota 157 7 8 2 Running OpenSM With AR Manager LL 157 7 8 2 1 AR Configuration File Example LL 158 7 9 Congestion Control 159 7 9 1 Congestion Control Overview LL 159
216. s applications which run over IB verbs should work on RoCE links as long as they use GRH headers that 1s as long as they specify use of GRH in their address vector 3 1 5 Ported Applications The following applications are ported with RoCE 40 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 e ibv pingpong examples are ported The user must specify the GID of the remote peer using the new g option The GID has the same format as that in sys class infiniband mlx4 0 ports 1 gids 0 A which is likely to exceed the MTU of the RoCE link Use ibv devinfo to inspect the Care should be taken when using ibv ud pingpong The default message size is 2K af link MTU and specify an appropriate message size e All rdma cm applications should work seamlessly without any change e libsdp works without any change e Performance tests 3 1 6 GID Tables With RoCE there may be several entries in a port s GID table The first entry always contains the IPv6 link s local address of the corresponding Ethernet interface The link s local address is formed in the following way pre O ee 000000000000 gidio RE EE a sao Si lee gidi Ol mac gid a e S gidil Te eje es ee Le gid 14 mac 4 gie Se al If VLAN is supported by the kernel and there are VLAN interfaces on the main Ethernet interface the interface that the IB port is tied to then each
217. s done with regards to restriction that these QoS Level parameters impose One QoS level that is mandatory to define is a DEFAULT QoS level It is applied to a PR MPR query that does not match any existing match rule Similar to any other QoS Level 1t can also be explicitly referred by any match rule IV QoS Matching Rules denoted by gos match rules Each PathRecord MultiPathRecord query that OpenSM receives is matched against the set of matching rules Rules are scanned in order of appearance in the QoS policy file such as the first match takes precedence Each rule has a name of QoS level that will be applied to the matching query A default QoS level is applied to a query that did not match any rule Queries can be matched by e Source port group whether a source port is a member of a specified group e Destination port group same as above only for destination port e PKey e QoS class e Service ID To match a certain matching rule PR MPR query has to match ALL the rule s criteria However not all the fields of the PR MPR query have to appear in the matching rule For instance if the rule has a single criterion Service ID it will match any query that has this Ser vice ID disregarding rest of the query fields However if a certain query has only Service ID 144 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 which means that this is the only bit
218. s file to fine tune Congestion Control mechanism and Congestion Control Manager behavior To do so perform the following 1 Find the event plugin options option in the file and add the following contrate suso iones enne ODL ons string that would Le passed to the plugins event Plugin option Smee Con hat WS e Sie eo SOE MOMS Bee Side nie 2 Run the SM with the new options file opensm F lt options file name gt For a list of examples of CC Manager options file with all the default values See Congestion Con trol Manager Options File on page 160 Once the Congestion Control is enabled on the fabric nodes to completely turn off Congestion Control you will need to actively turn 1t off Running the SM w o the CC S Manager is not sufficient as the hardware still continues to function in accordance to yo the previous CC configuration To turn 1t off set enable to FALSE in the Congestion Control Manager configuration file and run OpenSM ones with this configuration Mellanox Technologies 159 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 7 9 2 1 Congestion Control Manager Options File Table 7 Congestion Control Manager General Options File enable Enables disables Congestion Control mechanism on the Values lt TRUE FALSE gt fabric nodes Default True num hosts O FN the number of nodes The CC table values are cal Values 0 48K culated based on this number
219. s not to be recognized by the QoS manager as SRP the SRP match rule or any match rule that refers to the target port guid only should be placed at the end of the qos ulps match rules 7 6 6 5 MPI SL for MPI is manually configured by MPI admin OpenSM is not forcing any SL on the MPI traf fic and that s why it is the only ULP that did not appear in the qos ulps section Mellanox Technologies 151 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager 7 6 7 SL2VL Mapping and VL Arbitration OpenSM cached options file has a set of QoS related configuration parameters that are used to configure SL2VL mapping and VL arbitration on IB ports These parameters are e Max VLs the maximum number of VLs that will be on the subnet e High limit the limit of High Priority component of VL Arbitration table IBA 7 6 9 e VLArb low table Low priority VL Arbitration table IBA 7 6 9 template e VLArb high table High priority VL Arbitration table IBA 7 6 9 template e SL2VL SL2VL Mapping table IBA 7 6 6 template It is a list of VLs corresponding to SLs 0 15 Note that VL15 used here means drop this SL There are separate QoS configuration parameters sets for various target types CAs routers switch external ports and switch s enhanced port 0 The names of such parameters are prefixed by qos lt type gt string Here is a full list of the currently supported sets e gos ca QoS configuration parameters se
220. s or use the Change menu below y Time Zone Overview Installation gt Installation Summary Keyboard Layout Perfurin Inslallalivri English US Configuration SEEDA e Root Password Partitioning e Hostname Create swap partition dev sdal 502 0 MB e Network Create root partition dev sda2 7 5 GB with reiserfs e Customer Center e Online Update Add On Products e Service e Users No add on product selected for installation e Clean U Software e Release Notes e Hardware Configuration SUSE Linux Enterprise Server 10 SP2 Server Base System KDE Desktop Environment for Server C C Compiler and Tools X Window System Size of Packages to Install 1 6 GB Booting Boot Loader Type GRUB Location dev sda2 boot Sections SUSE Linux Enterprise Server 10 SP2 default Floppy Failsafe SUSE Linux Enterprise Show Release Notes Server 10 SP2 Help Back Abort Step 15 Click Edit in the Boot Loader Settings window Section List Boot Loader Settings From Other you can manually editthe boot Section Management Boot Loader Installation loader configuration files clearthe current configuration and propose a new T Label Section Summary configuration start from ii SUSE Linux Enterprise Server 10 SP2 Image append resume dev scratch or reread the Floppy Other chainloader dev fd0 configuration saved on Failsafe SUSE Linux Enterp
221. s should work seamlessly but they require provisioning of GRH information when creating address vectors The library and driver are modified to provide for mapping from GID to MAC addresses required by the hardware 3 1 2 Software Dependencies In order to use RoCE over Mellanox ConnectX R hardware the mlx4 en driver must be loaded Please refer to MLNX EN README txt for further details 3 1 3 Firmware Dependencies In order to use RoCE over Mellanox ConnectX R hardware RoCE requires ConnectX firm ware version 2 7 000 or higher Features such as loopback require higher firmware versions 3 1 4 General Guidelines Since ROCE encapsulates InfiniBand traffic in Ethernet frames the corresponding net device must be up and running In case of Mellanox hardware mlx4 en must be loaded and the corresponding interface configured e Makesurethatmlx4 en ko is loaded To verify the module is loaded run the folow ing command Ismod grep mlx4 en If the module is loaded the mInx4_en should be displayed as shown in the example below lsmod grep mlx4 en dea a OO e Run ibv devinfo There is a new field named link layer which can be either Ethernet or IB If the value is IB then you need to use connectx port config to change the ConnectX ConnectX 2 ports designation to eth see mlx4 release notes txt for details e Configure the IP address of the interface so that the link will become active e All IB verb
222. sable The above file has options with default values which is equivalent to not having the AR configuration file at all partB 0x8002 s1 2 ipoib ALL full 158 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 7 9 Congestion Control 7 9 1 Congestion Control Overview Congestion Control Manager is a Subnet Manager SM plug in 1 e it is a shared library libec mgr so that is dynamically loaded by the Subnet Manager Congestion Control Manager is installed as part of Mellanox OFED installation The Congestion Control mechanism controls traffic entry into a network and attempts to avoid oversubscription of any of the processing or link capabilities of the intermediate nodes and net works Additionally is takes resource reducing steps by reducing the rate of sending packets Con gestion Control Manager enables and configures Congestion Control mechanism on fabric nodes HCAs and switches 7 9 2 Running OpenSM with Congestion Control Manager Congestion Control CC Manager can be enabled disabled through SM options file To do so per form the following 1 Create the file Run Opensmi c lt operons rile name gt 2 Find the event plugin name option in the file and add ccmer to it Event plugin name s Sven apli Dea 3 Run the SM with the new options file opensm F lt options file name gt Congestion Control Manager can provide option
223. saging performance scalability and reliability over RDMA interconnects InfiniBand and RoCE The uDAPL interface is defined by the DAT collaborative This release of the uDAPL reference implementation package for both DAT 1 2 and 2 0 specifica tion is timed to coincide with OFED release of the Open Fabrics www openfabrics org software stack For more information about the DAT collaborative go to the following site http www datcollaborative org 1 4 6 MPI Message Passing Interface MPI is a library specification that enables the development of parallel software libraries to utilize parallel computers clusters and heterogeneous networks Mellanox OFED includes the following MPI implementations over InfiniBand e Open MPI an open source MPI 2 implementation by the Open MPI Project e OSU MVAPICH an MPI 1 implementation by Ohio State University Mellanox OFED also includes MPI benchmark tests such as OSU BW LAT Intel MPI Bench mark and Presta Mellanox Technologies 21 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Mellanox OFED Overview 1 4 7 InfiniBand Subnet Manager All InfiniBand compliant ULPs require a proper operation of a Subnet Manager SM running on the InfiniBand fabric at all times An SM can run on any node or on an IB switch OpenSM is an InfiniBand compliant Subnet Manager and it is installed as part of Mellanox OFED See Chapter 7 OpenSM Subnet Manager 1 4 8 Diagn
224. sconfig network on sl a SuSE machine DHCP Server Using a DHCP server with EoIB does not require special configuration The DHCP server can run on a server located on the Ethernet side using any Ethernet hardware or on a server located on the InfiniBand side and running EoIB module 3 6 2 7 Static EolB Configuration To configure a static EoIB you can use an EoIB configuration that is not based on DHCP Static configuration is similar to a typical Ethernet device configuration For further information on how to configure IP addresses please refer to your Linux distribution documentation S Ethernet configuration files are located at etc sysconfig network scripts on a RedHat machine and at etc sysconfig network on a SuSE machine hai 3 6 2 8 Sub Interfaces VLAN EoIB interfaces do not support creating sub interfaces via the vconfig command To create inter faces with VLAN refer to Section Configuring VLANs on page 78 3 6 3 Retrieving EolB Information 3 6 3 1 mlx4_vnic_info To retrieve information regarding EoIB interfaces use the script mlx4_vnic_info This script pro vides detailed information about a specific vNic or all EoIB vNic interfaces such as BX info IOA Mellanox Technologies 719 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features info SL PKEY Link state and interface features If network administered vNics are enabled this script can also be used to discover
225. sh access If you purchased a standard Mellanox Technologies network adapter card please down load the firmware image from www mellanox com gt Downloads gt Firmware If you gt purchased a non standard card from a vendor other than Mellanox Technologies please contact your vendor To run mstflint you must know the device location on the PCI bus See Example 1 for details Synopsis mescita switches conmand gt parameters Mellanox Technologies 193 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities Table 21 lists the various switches of the utility and Table 22 lists its commands Table 21 mstflint Switches Sheet 1 of 2 Affected Relevant Description Commands Print the help menu Print an extended help menu Specify the device to which the Flash is connected Switch d evice lt device gt guid lt GUID gt GUID base value 4 GUIDs are automatically assigned to the following val ues guid gt node GUID guid 1 gt portl guid 2 gt port2 guid 3 gt system image GUID Note Port2 guid will be assigned even for a single port HCA the HCA ignores this value ignores this value It can be set to 0x0 MAC address base value Two MACS are automatically assigned to the fol lowing values mac gt portl mac l gt port2 Note This switch is applicable only for Mellanox Technologies Ethernet products blank_g
226. ss Leste imestead or the Pormal test Sue stress est OPL ON are dls Eolo wSs ODI Description SAL Single MAD response SA queries Sou M ller MAD RMPP response SA querres SS MELENA EMP ARE CO rd Sl eres WEEROUE So Stress Eestang ms MOm per omend Mellanox Technologies 125 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 OpenSM Subnet Manager te os PO HHE OR COn peca eno cone aE ip esa ANS O MA E ade E OET Description M1 Short Mulbeicast Blow default sing le mode M2 Short Multicast Elow Eo Me mode MS Long Multicast Flow single mode M4 Long Multicast Flow multiple mode SINGLE mode 0smrest us tested alone wel no other apps that interact with OpenSM MC Multiple mode Could be run with other apps using MEW Open MEMO Ut M default Ao testing To PSr formed This option specifies the time in milliseconds used for Erans acu fom rime use pe E T disabile ES EE Watchoukd tr _0pensMige aut to a time value ias T Thro optron de tines the log to be tine miyen Eile By defunto gifgo seo Aero gio mig Bor Ener log to go to standard output use f stdout This opto inerte ases LIC loo veros level MiS operon ma DeepCore Mones the verbot leval ee the OO Tor mores Mr OPN tom KOO hoo Weise A This option sets the maximum verbosity level and FORCES Log ELUS han ge ine eek quarantotto ER CREO VOM MESA MO 26 MA E O MMS ao Aa O UE loa Wie O S Ae yor TRIS Option setro ihe fog verbos
227. standard network adapter devices e Firmware configuration INI files for Mellanox standard network adapter cards and custom cards e FlexBoot for ConnectX ConnectX 2 InfiniHost III Ex in Mem free mode and InfiniHost III Lx HCA devices e ConnectX EN PXE gPXE boot for ConnectX EN and ConnectX 2 EN devices 1 3 4 Directory Structure The ISO image of MLNX OFED LINUX contains the following files and directories e milnxofedinstallThis is the MLNX OFED LINUX installation script e uninstall shThis is the MLNX OFED LINUX un installation script e lt CPU architecture folders gt Directory of binary RPMs for a specific CPU architecture e firmware Directory of the Mellanox IB HCA firmware images including Boot over IB e src Directory of the OFED source tarball and the Mellanox Firmware Tools MFT tarball e docs Directory of Mellanox OFED related documentation 1 4 Architecture Figure I shows a diagram of the Mellanox OFED stack and how upper layer protocols ULPs interface with the hardware and with the kernel and user spaces The application level also shows the versatility of markets that Mellanox OFED applies to 18 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Figure 1 Mellanox OFED Stack Back end App Life Sciences Eth Cluster Block Storage HPC Application Application Midd gen Front Config Mgmnt Mellanox VPI Device HCA
228. stinations and groups these paths into virtual layers in such a way as to avoid deadlock LASH analyzes routes and ensures deadlock freedom between switch pairs The link A from HCA between and switch does not need virtual layers as deadlock will not arise af between switch and HCA In more detail the algorithm works as follows 1 LASH determines the shortest path between all pairs of source destination switches Note LASH ensures the same SL is used for all SRC DST DST SRC pairs and there is no guar antee that the return path for a given DST SRC will be the reverse of the route SRC DST 2 LASH then begins an SL assignment process where a route is assigned to a layer SL if the addition of that route does not cause deadlock within that layer This is achieved by maintaining and analysing a channel dependency graph for each layer Once the potential addition of a path could lead to deadlock LASH opens a new layer and continues the pro cess 3 Once this stage has been completed it is highly likely that the first layers processed will contain more paths than the latter ones To better balance the use of layers LASH moves paths from one layer to another so that the number of paths in each layer averages out Note that the implementation of LASH in opensm attempts to use as few layers as possible This number can be less than the number of actual layers available In general LASH is a very flexible algorithm It can for example
229. such VLAN will appear as a new GID in the port s GID table The format of the GID entry will be identical to the one described above except for the following change gidi VLAN ID high byte 4 MS bite opie I VLAN ID low byte Please note that VLAN ID is 12 bits wide 3 1 6 1 Priority Pause Frames Tagged Ethernet frames carry a 3 bit priority field The value of this field is derived from the IB SL field by taking the 3 least significant bits of the SL field 3 1 7 Using VLANs In order for RoCE traffic to use VLAN tagged frames the user needs to specify GID table entries that are derived from VLAN devices when creating address vectors Consider the example below e Make sure VLAN support is enabled by the kernel Usually this requires loading the 802 1q module Mellanox Technologies 41 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features gt modprobe 8021q e Adda VLAN device gt vconfig add eth2 7 e Assign an IP address to the VLAN interface This should create a new entry in the GID table as index 1 gt ifconfig eth2 7 7 10 11 12 e Verbs test On server gt 1bv rc _ pingpong g I On client gt ibv_rc_pingpongs g I server e For rdma cm applications the user needs only to specify an IP address of a VLAN device for the traffic to go with the VLAN tagged frames 3 1 8 Reading Port Counters Statistics It is possible to read port statistics in the same way it is done for regular I
230. switch systems The reason is that there is no way to allow a LID route between them that does not break the Up Down rule One ramification of this is that you cannot run SM on switches other than the leaf switches of the fabric 7 5 3 1 UPDN Algorithm Usage Activation through OpenSM s Use R updn option instead of old u to activate the UPDN algorithm e Use a lt root guid file gt for adding an UPDN guid file that contains the root nodes for ranking If the a option is not used OpenSM uses its auto detect root nodes algorithm Notes on the guid list file I A valid guid file specifies one guid in each line Lines with an invalid format will be dis carded 2 The user should specify the root switch guids However it is also possible to specify CA guids OpenSM will use the guid of the switch if it exists that connects the CA to the subnet as a root node 7 9 4 Fat tree Routing Algorithm The fat tree algorithm optimizes routing for shift communication pattern It should be chosen if a subnet is a symmetrical or almost symmetrical fat tree of various types It supports not just K ary N Trees by handling for non constant K cases where not all leafs CAs are present any Constant Bisectional Ratio CBB ratio As in UPDN fat tree also prevents credit loop dead locks If the root guid file is not provided a or root guid file options the topology has to be pure fat tree that complies with the following ru
231. t The value indicates a hexadecimal number interface ibl send dhcp client identifier 1 1 00 00 00 00 00 02 00 00 02 E 9 00 00 02 s 9 03 00 00 10 5395 Fxample of a configuration file for InfiniHost III Ex PCI Device ID 25218 called dhclient conf The value indicates a hexadecimal number interface ibl send dhep client identifier 20 00 55 04 0L OOO A 02300 233 92 In order to use the configuration file run nosti Gib T Lemm cri diel tent comm Lol 3 7 3 2 Static IPoIB Configuration If you wish to use an IPoIB configuration that is not based on DHCP you need to supply the instal lation script with a configuration file using the n option containing the full IP configuration The IPoIB configuration file can specify either or both of the following data for an IPoIB interface e A static IPoIB configuration e An IPoIB configuration based on an Ethernet configuration 86 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 See your Linux distribution documentation for additional information about configuring IP addresses The following code lines are an excerpt from a sample IPoIB configuration file E Sa age fees aa lues provided yemas le IPADDR ib0 11 4 3 175 NUS oo D O NETWORK ib0 11 4 0 0 BROAD SAS TRDO IS OS ONEOO IAS t Based on ceihO each e will be replaced wiih a CO respondio octe from
232. t for CAs e qos rtr parameters set for routers e qos sw0 parameters set for switches port 0 e qos swe parameters set for switches external ports Here s the example of typical default values for CAs and switches external ports hard coded in OpenSM initialization Gosmea iS FOSTERS SAN OS SEC noia ds E ROZZANO o Q dos ica villar Dow 0380 IA dl A e OM TAr ara I IA Ba el Ha H PA LA FA queste I a oO sd aus Es Wwenman vists os Weno eO dos nella oa MR od o USO all oa als ta Gos swe E Low Ou Oo Me 254 Od e 4 TI sa 1234 1534 LAGA Gos swe isla lwp T pee VL arbitration tables both high and low are lists of VL Weight pairs Each list entry contains a VL number values from 0 14 and a weighting value values 0 255 indicating the number of 64 byte units credits which may be transmitted from that VL when its turn in the arbitration occurs A weight of 0 indicates that this entry should be skipped If a list entry is programmed for VL15 or for a VL that is not supported or is not currently configured by the port the port may either skip that entry or send from any supported VL for that entry 152 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Note that the same VLs may be listed multiple times in the High or Low priority arbitration tables and further it can be listed in both tables The limit of high priority VLArb ta
233. t in Linux Environment Prerequisites Step1 Make sure that an iSCSI Target is installed on your server side You can download and install an iSCSI Target from the following location http sourceforge net projects iscsitarget files iscsitarget Step 2 Dedicate a partition on your iSCSI Target on which you will later install the operating system Step 3 Configure your iSCSI Target to work with the partition you dedicated If for example you choose partition dev sda5 then edit the iSCSI Target configuration file etc ietd conf to include the following line under the iSCSI Target iqn line Lun 0 Path dev sda5 Type fileio Example of an iSCSI Target ign line 218 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Target qna Us eo Step 4 Start your iSCSI Target Fxample hostli v ete init cd iliscesit rget start Configuring the DHCP Server to Boot From an iSCSI Target Configure DHCP as described in Section 9 3 3 1 IPoIB Configuration Based on DHCP Edit your DHCP configuration file etc dhcpd conf and add the following lines for the machine s you wish to boot from the iSCSI target Filename CONE MO OC ET SI Vee ie es e E The following is an example for configuring an IB ETH device to boot from an iSCSI target In sie si filename t EREor a Connect device with ports Configured as Iniiniband comment out the following li
234. tage the Finishing Basic Installation window will pop up and ask for confirming a reboot You can click OK to skip count down See image below Note Assuming that the machine has been correctly configured to boot from FlexBoot via its connection to the iSCSI target make sure that MLNX IB for ConnectX family or gPXE for InfiniHost III family has the highest priority in the BIOS boot sequence 230 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Preparation Language w License Agreement w System Analysis w R Finishing Basic Installation Tirne Zone Copy files to installed system Installation w Installation Summary Save configuration p Perform Installation Install boot manager Configuration Save installation settings Hostname Root Password Network Customer Center Online Update Service Users Clean Up Release Notet The system will reboot now Prepare system for initial boot Hardware Configuration Finished Ers Mex Step 20 Once the boot is complete the Startup Options window will pop up Select SUSE Linux Enter prise Server 10 SP2 then press Enter SUSE Linux Enterprise Server 10 Floppu SUSE Linux Enterprise Server 10 Failsafe Boot Options Mellanox Technologies 231 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Step 21 The Hostname and Domain Name window will pop up Continue config
235. te dia NE I If the output is neither 81 nor 82 card then the card is NOT installed in an x8 PCI Express slot 2 The least significant digit indicates the link speed for PCI Express Gen 1 2 5 GT s 2 for PCI Express Gen 2 5 GT s Note If you are running InfiniBand at QDR 40Gb s 4X IB ports you must run PCI Express Gen 2 5 3 2 InfiniBand Performance Troubleshooting InfiniBand IB performance depends on the health of IB link s and on the IB card type IB link speed 10Gb s or SDR 20Gb s or DDR 40Gb s or QDR also affects performance 4 A latency sensitive application should take into account that each switch on the path adds 200nsec at SDR and 150nsec for DDR ha 1 To check the IB link speed enter ibstat Check the value indicated after the Rate string 10 indicates SDR 20 indicates DDR and 40 indicates QDR 2 Check that the link has NO symbol errors since these errors result in the re transmission of packets and therefore in bandwidth loss This check should be conducted for each port after the driver is loaded To check for symbol errors enter ee SME eless mune mie lt clowske 7 jootamcy SST ES HIE EE TE Mellanox Technologies 107 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Performance The command above is performed on Port 1 of the device lt device gt The output value should be 0 if no symbol errors were recorded 3 Bandwidth is expected to vary between systems
236. that you need to supply You can also apply a manual configuration that persists only until the next reboot or driver restart Section 3 7 3 3 84 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 7 3 1 IPolB Configuration Based on DHCP Setting an IPoIB interface configuration based on DHCP is performed similarly to the configura tion of Ethernet interfaces In other words you need to make sure that IPoIB configuration files include the following line For RedHat BOOTPROTO dhep For SLES BOOTPROTO dehp If IPoIB configuration files are included ifcfg ib lt n gt files will be installed under 4 etc sysconfig network scripts on a RedHat machine hai etc sysconfig network on a SuSE machine 7 4 A patch for DHCP is required for supporting IPoIB For further information please see the REAME which is available under the docs dhcp directory Standard DHCP fields holding MAC addresses are not large enough to contain an IPoIB hardware address To overcome this problem DHCP over InfiniBand messages convey a client identifier field used to identify the DHCP session This client identifier field can be used to associate an IP address with a client identifier value such that the DHCP server will grant the same IP address to any client that conveys this client identifier The length of the client identifier field is not fixed in the specification
237. the available BridgeX s from the host side e To discover the available BridgeXs run o AS IS e To receive the full vNic information of eth10 run A A O e To receive a shorter information report on eth10 run ee ros Mee AO e To get help and usage information run A Ie pa Ole ES 3 6 3 2 ethtool ethtool application is another method to retrieve interface information and change its configura tion EoIB interfaces support ethtool similarly to hardware Ethernet interfaces The supported Ethtool options include the following options e show and update interrupt coalesce options gt Query RX TX ring parameters k K Show end DHOOL SE S prono o lito loas SE Show driver information 5 show adapter statistics For more information on ethtool run ethtool h 3 6 3 3 Link State An EoIB interface can report two different link states e The physical link state of the interface that is made up of the actual HCA port link state and the status of the vNics connection with the BridgeX f the HCA port link state is down or the EoIB connection with the BridgeX has failed the link will be reported as down because without the connection to the BridgeX the EoIB protocol cannot work and no data can be sent on the wire The mlx4_vnic driver can also report the status of the external BridgeX port status by using the mlx4 vnic info script If the eport state enforce module parameter is set then the external port state will b
238. tin eG UMS he te oo e aia ets DR POSTERO hd L HEHE R Onis e 96 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 4 Working With VPI VPI allows ConnectX ports to be independently configured as either IB or Eth Ifa ConnectX port is configured as Eth it may also function as a Fibre Channel HBA 4 1 Port Type Management ConnectX ports can be individually configured to work as InfiniBand or Ethernet or Fibre Channel over Ethernet ports By default both ConnectX ports are initialized as InfiniBand ports If you wish to change the port type use the connectx port config script after the driver is loaded Running sbin connectx port config s will show current port configuration for all ConnectX devices Port configuration is saved in the file etc infiniband connectx conf This saved configuration is restored at driver restart only if restarting via etc init d openibd restart Possible port types are e eth Ethernet e ib Infiniband e auto Link sensing mode Detect port type based on the attached network type If no link is detected the driver retries link sensing every few seconds Table 4 lists the ConnectX port configurations supported by VPI Table 4 Supported ConnectX Port Configurations Port 1 Configuration Port 2 Configuration i ib eth Note that the configuration Port eth and Port2 ib is not supported
239. tination s directed path LID or GUID lid guid gt Optional Destination s port number lt op gt lt value gt Optional Define the allowed port operations enable disable reset speed and query In case of multiple channel adapters CAs or multiple ports without a CA port being specified a port is chosen by the utility according to the following criteria I The first ACTIVE port that is found 2 If not found the first port that is UP physical link state is LinkUp Examples I Query the status of Port 1 of CA mlx4 0 using ibstatus and use its output the LID 3 in this case to obtain additional link information using ibportstate es alo a Mis ne sevice ae pe elet det FesUs 00000000 OOO 0000 0000 9289 33905 base lid 0x3 SME 0x3 Spades T TE phys state cc qUe rate 20 Gb sec 4X DDR Mellanox Technologies 177 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities 2 Query the status of two channel adapters using directed paths 178 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 Change the speed of a port Mellanox Technologies 179 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 BARNER UPPOO nE E ti Rea eee IX or dx Rec Me dee ID Oona 24 6 ERWE EDA eee femmes ccm a AX Bunk o DS Sato EE ZON NS EO BEE Mis GE H iii 5 0 Gbps IBA extension
240. tion 113 TDM OPENS SVAN A dd Bees Ad 113 iad Environment Varables yaa ees n ala LERNIA nad bake kn bets 123 12 97 Sienalibri iena iaia NE E oat ea ae a ee ss e 123 24 RUNNING DEN SI sac lipidi ilaria 123 7 2 4 1 Running OpenSM As Daemon 123 7 3 osmtest Description 124 ESSI E A NOS E 124 SD ARAS OSM ds ados 127 7 4 Partitions 127 idol Pierna oeren A ATAR AA sa 128 7 5 Routing Algorithms 130 Sk Etfect of Tepolosy Chanscs sissiseo ode ai nad thant add nee REG dee eae 131 7 52 Min OPA LOLI cieli ee eli la Dyk renee se Sst Se ee 132 55 WPDN A sont 2432 fase he do at thats O 132 Pook WPDN Alconthim Wsaee civic teh cat rag a Beit ae e llas 133 75 4 Fat tree Routine Alsornihni stelle een oe be eek eee ee as 133 7 5 4 1 Routing between non CN Nodes 000 cece eee eee 134 7 5 4 2 Activation through OpenSMy 4 4 al sue tdabesee tes de ea 135 r LASH Routine 9 e errar Soe eee eR eso aes 135 130 DOR Route ALSO ili Se haw ee os wk eG a ere ota ed 136 19 TOn 2 QoS Routine Aleonthims pts eee heat eae behest aes ee Ls 136 Toe Umes 22 IO f rt ren Cr te ee ak tet dol Onde sole tee ii ni 137 iS MulieasEROUtno al a ele ee eed lo hate Re pela 139 7 5 7 3 Torus Topology Discove
241. tion Ceneda Aan ST Central and South America Central e Perform Installation Russia Pagine Configuration Asia East Indiana a Hostname Australia Hawaii Root Password Africa Indiana Starke Network Pacific Michigan Customer Center Global Mountain Online Update Etc Pacific a Service Samoa Users Clean Up e e Hardware Clock Set To Time and Date UTE 07 52 06 24 03 2008 Change Help Abot Finish Step 10 In the Installation Settings window click Partitioning to get the Suggested Partitioning window Preparation Language Installation Settings w License Agreement Disk Activation i ni n els Click any headline to make changes or use the Change menu below w Time Zone Overview Expert Installation Installation Summary Keyboard Layout Perf Installati e Perform Installation English US Configuration e Hostname Partitioning X Window System GNOME Desktop Environment for Server Server Base System Novell AppArmor Frint Server Size of Packages to Install 1 3 GB Release Notes Hardware Configuration SASSI Create boot partition dew sdal 70 5 MB with ext e Network Create swap partition dew sda2 502 0 MB e Customer Center Create root partition dev sda3 7 4 GB with reiserfs Online Update e Service Software e Users e Clean Up SUSE Linux Enterprise Server 10 LJ LJ Language Primary Language English US
242. to deadlock So in the example above with failed switch T the location of the illegal turn at I in the path from S to D requires that any credit loop caused by that turn must encircle the failed switch at T Thus the second and later hops after the illegal turn at I 1 e hop r D cannot contribute to a credit loop because they cannot be used to construct a loop encircling T The hop I r uses a separate VL so it cannot contribute to a credit loop encircling T Extending this argument shows that in addition to being capable of routing around a single switch failure without introducing deadlock torus 2QoS can also route around 138 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 multiple failed switches on the condition they are adjacent in the last dimension routed by DOR For example consider the following case on a 6x6 2D torus 5 Ho Ho Ho Ho I I I I I I 4 Ho D Ho I I I I I I 3 1 I u Ho I I I I I I 2 Ho q R Ho I I I I I I 1 m_ ___ S n _ T _ o o_ I I I I I I y O AZ Ho Ho Ho Ho I I I I I I x 0 1 2 3 4 5 Suppose switches T and R have failed and consider the path from S to D Torus 2QoS will gener ate the path S n q I u D with an illegal turn at switch I and with hop I u using a VL with bit I set As a further example co
243. trical Fat Tree of various types not just a K ary N Tree non constant K not fully staffed and for any CBB ratio Similar to UPDN Fat Tree routing is con strained to ranking rules 4 LASH Routing Algorithm Uses InfiniBand virtual layers SL to provide deadlock free shortest path routing while also dis tributing the paths between layers LASH is an alternative deadlock free topology agnostic rout ing algorithm to the non minimal UPDN algorithm It avoids the use of a potentially congested root node 5 DOR Routing Algorithm Based on the Min Hop algorithm but avoids port equalization except for redundant links between the same two switches This provides deadlock free routes for hypercubes when the fab ric is cabled as a hypercube and for meshes when cabled as a mesh 6 Torus 2QoS Routing Algorithm Based on the DOR Unicast routing algorithm specialized for 2D 3D torus topologies Torus 2005 provides deadlock free routing while supporting two quality of service QoS levels Additionally it can route around multiple failed fabric links or a single failed fabric switch without introducing deadlocks and without changing path SLvalues granted before the failure OpenSM provides an optional unicast routing cache enabled by A or ucast cache options When enabled unicast routing cache prevents routing recalculation which is a heavy task in a large cluster when there was no topology change detected during th
244. ture e g Cisco Nexus Once a vHBA is instantiated on an Ethernet interface it immediately attempts to log into the FC fabric Provided that the FC fabric and FC targets are well configured LUNs will map to SCSI disk devices dev sdXXX vHBAs instantiated automatically by the debxd daemon are created on a VLAN 0 interface with VLAN priority set to the value negotiated with the switch This takes advantage of PFC which allows pausing FCoE traffic when needed without pausing the entire Ethernet link Also with proper configuration of the FCoE switch the link s maximum bandwidth can be divided as needed between FCoE and regular Ethernet traffic Instantiating vHBAs manually allows creating them on VLAN interfaces with any arbitrary VLAN id and priority as well as on the regular without VLAN Ethernet interfaces Using the reg ular interface means that PFC cannot be used In this case it is highly recommended that both the FCoE switch and the m1x4 en driver be con figured to use link pause regular flow control Otherwise any FCoE packet drop will trigger SCSI errors and timeouts 3 2 2 1 FCoE Configuration After installation please edit the file etc mlxfc mlxfc conf and set the following vari ables e FC SPEC set to T11 or pre T11 as supported by your FCoE switch S Only pre T11 format is offloaded in hardware di e DCBX IFS provide a space separated list of Ethernet devices to monitor the use of the DCBX
245. ual for more detailed instructions on how to enable use the HA feature The following is an example of an SRP Target setup file K KK srpt sh KKKKKKKKKKKKKKKKKKKKKKKKKKKKKEKK bin sh H ss St elas cols MO cito ses Ome sh obs eel 100 Scho pen es idee LORO RIO proc cesso veda are nidi i des dE LIO peo see als dise Seno Newer dt a de sde ELO CIO peo se diede noO Neon dls o os co CTO prece sese ets ls Ads e Sono uo O ee sio gio lOs Decre IE I Seo Mello subido rie RON ann cche deri 7 poe Seo leg quo Doral es Sc ss Se SE dere MOCOLODe seme ep colo detroit pe Mesa cele den grido e peo ee ei cche dele nie er eee eo Ases cope en K End srpt sh KRK KK KK KK KK KK KK KRK KA B 3 How to Unload Shutdown 1 Unload ib srpt Mino dpeoocea So e 2 Unload scst and its dev_handlers first MOC ORO Oem a hes Sc Es Grats 236 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 Unload ofed S E 2G d op n Da stop Mellanox Technologies 237 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Appendix C mlx4 Module Parameters In order to set m1x4 parameters add the following line s to etc modpobe conf options and or Opt tons and or OPS and or options IHS OC dei mlx4 ib parameter lt value gt uo Sia parameter lt value gt ax eee parameter lt value gt The following sections list the available m
246. uids No commands Force clear the Flash semaphore on the device No command is allowed clear semaphor allowed when this switch is used e Warning May result in system instability or Flash corruption if the device or another application is currently using the Flash 1 mage burn verify Binary image file lt image gt burn query Run a quick query When specified mstflint will not perform full image integrity checks during the query operation This may shorten execution time when running over slow interfaces e g I2C MTUSB 1 nofs Burn image in a non failsafe manner Allow burning the firmware image without updating the invariant sector This is to ensure failsafe burning even when an invariant sector difference is detected Mellanox Technologies Two MACs must be specified here The specified MACs are assigned to portl and port2 repectively Note This switch is applicable only for Mellanox Technologies Ethernet products Burn the image with blank GUIDs and MACs where applicable These val ues can be set later using the sg command see Table 22 below guids burn s 4 GUIDs must be specified here The specified GUIDs are assigned the fol lt GUIDs gt lowing values repectively node portl port2 and system image GUID Note Port2 guid must be specified even for a single port HCA the HCA Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 21
247. ule requests to connect to them as well Operation When a path from portl to a target fails the ib sm module starts an error recovery process If this process gets to the reset host stage and there is no path to the target from this port ib srp will remove this scsi host After the scsi host is removed multipath switches to another path to this target from another port HCA When the failed path recovers it will be detected by the SRP daemon The SRP daemon will then request ib_srp to connect to this target Once the connection is up there will be a new scsi host for Mellanox Technologies 71 J Mellanox Technologies Confidential Rev 1 5 2 2 1 0 Driver Features this target Multipath will be executed on the devices of this host returning to the original state prior to the failed path Prerequisites Installation for RHEL4 5 Execute once e Verify that the standard device mapper multipath rpm is installed If not install it from the RHEL distribution Installation for SLES10 Execute once e Verify that multipath is installed If not take it from the installation you may use yast e Update udev Execute once for manual activation of High Availability only e Add a file to etc udev rules d you can call it 91 srp rules This file should have one line ACTION add KERNEL sd 0 9 RUN sbin multipath M m ity below this file is created upon each boot of the driver and is deleted w
248. unters of port l only per fouet yr ere R 0x20 ht rese eeen de d per Eor man Ce teo lies OE por e Orly perfguery R a 32 mese per amane CoOunkers Or a H pOr parl guey R 374 OxOrrr ereo e ON a rr Oe counters Or ponte perrquery R 32 240 F000 He POSS rh Only nOr Cer aC Oe D soos 1 Read local port s performance counters gt perfquery MSPORT tO OE ROCE o NG AA 1 So iS eee en em ren eae eee 0x1000 THI 2 A AI e a 0 AS A AI SIA 0 E A ona ses Y RO UCI 0 PEV Mierke ieee O 0 REY Remote E ora io 0 Per WREDI Er ON OtS Hae rane yn eA meneame Ome ara 0 lt br ai E 0 MOE OS Rakai O ae nia a 0 T EL TO ren 0 LENAT ESOT E VCO PICO 0 Oido T TATO 0 A o een 0 Mellanox Technologies 189 Mellanox Technologies Confidential Rev 1 5 2 2 1 0 InfiniBand Fabric Diagnostic Utilities 2 Read performance counters from LID 2 all ports 3 Read then reset performance counters from LID 2 port 1 190 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 EMO see eee oe E A A i 0 Events Enya ZO 0 RevowReloyEtto Stelio 0 RIESI IRR DAI T nr a eee 5 MES OS trad ibe be TOE ER 0 BREV CET STIG PE IS TO Seneca enes Asea 0 noire coeva 0 ExCBurone Fe TR o rag aa 0 VER T e an 0 HETE TE SAS A e E ain da 0 Redattore 0 gt GUZZI ASTE ZI E o FIR 0 BERE Sti Re o INNI ae 0 8 14 ibcheckerrs Applicable Hardware All InfmiBand devices Description Validates an I
249. uring your machine until the operating system is up then you can start running the machine in normal operation mode Step 22 Optional If you wish to have the second instance of connecting to the iSCSI Target go through the IB driver copy the initrd file under boot to a new location add the IB driver into it after the load commands of the iSCSI Initiator modules and continue as described in Section A 7 on page 210 Pay extra care when changing initrd as any mistake may prevent the client j machine from booting It is recommended to have a back up iSCSI Initiator on a i machine other than the client you are working with to allow for debug in case ini trd gets corrupted In addition edit the init file that is in the initrd zip and look for the following string a WOTSCOTRTAREETETPIDDR 2 then sie sail CILE RESP Ei Now add before the string the following line TEES E CETE DDE TEREA a On SLC ST gie Example iSCSI TARGET IPADDR 11 4 3 7 A 10 WinPE Mellanox FlexBoot enables WinPE boot via TFTP For instructions on preparing a WinPE image please see http etherboot org wiki winpe 232 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Appendix B SRP Target Driver The SRP Target driver is designed to work directly on top of OpenFabrics OFED software stacks http www openfabrics org or InfiniBand drivers in Linux kernel tree kernel org
250. us it can transparently replace the TCP socket family with SDP socket calls The library also implements a user level socket switch Using a configuration file the system administrator can set up the policy that selects the type of socket to be used 1ibsdp so also has the option to allow server sockets to listen on both SDP and TCP interfaces The various configu rations with SDP TCP sockets are explained inside the etc libsdp conf file 3 4 3 Configuring SDP To load SDP upon boot edit the file etc infiniband openib conf and set SDP LOAD yes S For the changes to take effect run etc init d openibd restart ha SDP can work over IPoIB interfaces or RoCE interfaces In case of IPoIB SDP uses the same IP addresses and interface names as IPoIB see IPoIB configuration in Section 9 3 3 and Section 9 3 3 3 In case of RoCE SDP use the same IP addresses and interface names of the corresponding mlx4_ en interfaces see mlx4_en configuration in Section 4 3 and Section 4 3 4 3 4 3 1 How to Know SDP Is Working Since SDP is a transparent TCP replacement it can sometimes be difficult to know that it is work ing correctly To check whether traffic is passing through SDP or TCP monitor the file proc net sdpstats and see which counters are running Alternative Method Using the sdpnetstat Program The sdpnetstat program can be used to verify both that SDP is loaded and is being used The following command shows all active SDP soc
251. v mapper 4 It is possible that regular not SRP LUNs may also be present the SRP LUNs may be identified by their name hai e Itis possible to see the output of the SRP daemon in var log srp daemon log 3 5 2 7 Shutting Down SRP SRP can be shutdown by using rmmod ib srp or by stopping the OFED driver etc init d openibd stop or as a by product of a complete system shutdown Prior to shutting down SRP remove all references to it The actions you need to take depend on the way SRP was loaded There are three cases I Without High Availability When working without High Availability you should unmount the SRP partitions that were mounted prior to shutting down SRP 2 After Manual Activation of High Availability If you manually activated SRP High Availability perform the following steps a Unmount all SRP partitions that were mounted b Kill the SRP daemon instances c Make sure there are no multipath instances running If there are multiple instances wait for them to end or kill them d Run multipath F 3 After Automatic Activation of High Availability If SRP High Availability was automatically activated SRP shutdown must be part of the driver shutdown etc init d openibd stop which performs Steps 2 4 of case b above However you still have to unmount all SRP partitions that were mounted before driver shutdown Mellanox Technologies 13 Mellanox Technologies Confidential Rev 1 5
252. v4 Traffic Performance 103 5 2 2 Tuning the Network Adapter for Improved IPv6 Traffic Performance 103 5223 iInterrupiNioderanofiz esteri Ri r nd und ee oa ilari bh es 104 324 niet ipo Ansa tot vet tai 105 5 2 4 1 Example Script for Setting Interrupt Affinity o ooooooooooooo 105 5 2 5 Preserving Your Performance Settings After A Reboot 0 0 0 0 cee eee 106 5 3 Performance Troubleshooting 106 5 3 1 PCI Express Performance Troubleshooting 0 00 ccc eens 106 5 3 2 InfiniBand Performance Troubleshooting LL 107 5 3 3 System Performance Troubleshooting nnna annann annann eanna 108 Chapter 6 MPI Message Passing Interface ccc cc ce cece cee romo roo 109 6 1 Overview 109 Mellanox Technologies 5 I Mellanox Technologies Confidential Rev 1 5 2 2 1 0 6 2 Prerequisites for Running MPI 109 6221 SoA On E 15T e tisi leleine Sele tao 109 6 3 MPI Selector Which MPI Runs 111 6 4 Compiling MPI Applications 111 Chapter 7 OpenSM Subnet Manager cc ccc ccc ccc cece cece rece eee eeees 113 7 1 Overview 113 7 2 opensm Descrip
253. work parameters that are set by the operating system in order to improve IPv4 and IPv6 traffic performance Note however that changing the network parameters may yield different results on different systems The results are significantly dependent on the CPU and chipset efficiency 102 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 5 2 1 Tuning the Network Adapter for Improved IPv4 Traffic Performance The following changes are recommended for improving IPv4 traffic performance e Disable the TCP timestamps option for better CPU utilization STEGET S E ABE elites E N E e Disable the TCP selective acks option for better CPU utilization Si e OW EE D e Increase the maximum length of processor input queues SVcCCEl W Mee cOLe Nekevaomax back log 2a0U000 e Increase the TCP maximum and default buffer sizes using setsockopt seed Se peo Toe ey sc delie eee ace ese cea e T ys Ine OT CANNES S TOTTA Se Al Oso O pS H MOS e Increase memory thresholds to prevent packet dropping Ss CU e te Ma EE Mel On NG O OOO e Increase Linux s auto tuning of TCP buffer limits The minimum default and maxi mum number of bytes to use are SUS o ESE e HRES So sysctl w net 1pv4 tcp wmem 4096 65536 16777216 5 2 2 Tuning the Network Adapter for Improved IPv6 Traffic Performance The following changes are recommended for improving IPv6 traffic performan
254. y Subnet management attributes such as node info node description switch info and port info Synopsys SMO se A AS AA cia E Cane et ie ue al node name map lt node name map gt copi IS ole jorenelat lol SiO Boa Table 18 lists the various flags of the command Table 18 smpquery Flags and Options Default If Not Description Specified d ebug Optional Raise the IB debug level May be used several times for higher debug levels ddd or d d d Optional Show send and receive errors timeouts and others v erbose Optional Increase verbosity level May be used several times for additional verbosity vvv or v v v D irect Optional Use directed path address arguments The path is a comma separated list of out ports Examples 0 self port 0 1 2 1 4 out via port 1 then 2 G uid Optional Use GUID address argument In most cases 1t is the Port GUID Example 0x08 1040023 ESTO Oni sen ema SSA Pr Omir O Semo ene Onion eterea ee P lt ca por gt lt ca P lt ca por gt Optional Use the specified port 2 0 Use Use the specified port specified port Optional Override the default timeout for the solicited MADs iaia ms gt msec Optional Mandatory Mellanox Technologies Mellanox Technologies Confidential InfiniBand Fabric Diagnostic Utilities Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 Table 18 smpquery Flags and Options
255. y must be set in the BridgeX first For further information please refer to BridgeX documentation 3 6 2 4 EolB Multicast Configuration Configuring Multicast for EoIB interfaces is identical to multicast configuration for native Ether net interfaces EoIB maps Ethernet multicast addresses to InfiniBand MGIDs Multicast GID It 4 ensures that different vHubs use mutually exclusive MGIDs Thus preventing vNics on af different vHubs from communicating with one another 78 Mellanox Technologies Mellanox Technologies Confidential Mellanox OFED for Linux User s Manual Rev 1 5 2 2 1 0 3 6 2 5 EolB and Quality of Service EoIB enables the use of InfiniBand service levels The configuration of the SL is performed through the BridgeX and lets you set different data control service level values per BridgeX box For further information on the use of non default service levels please refer to BridgeX documen tation 3 6 2 6 IP Configuration Based on DHCP Setting an EoIB interface configuration based on DHCP v3 1 2 which is available via www isc org is performed similarly to the configuration of Ethernet interfaces When setting the EoIB configuration files verify that it includes following lines e For RedHat BOOTPROTO dhcp e For SLES BOOTPROTO dchp If EoIB configuration files are included ifcfg eth lt n gt files will be installed under etc A sysconfig network scripts on a RedHat machine and under etc sy

Mellanox OFED Linux User`s Manual

Contents

Download Pdf Manuals

Related Search

Related Contents