User Manual

Rev 2.2-1.0.1

Mellanox Technologies

If you manually activated SRP High Availability, perform the following steps:

a. Unmount all SRP partitions that were mounted.

b. Stop service srpd (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.

4.2 iSCSI Extensions for RDMA (iSER)

4.2.1 Overview

iSCSI Extensions for RDMA (iSER) extends the iSCSI protocol to RDMA. It permits data to be

transferred directly into and out of SCSI buffers without intermediate data copies.

4.2.2 iSER Initiator

Setting the iSER target is out of scope of this manual. For guidelines of how to do so,

please refer to the relevant target documentation (e.g. stgt, clitarget).

The iSER initiator is controlled through the iSCSI interface available from the iscsi-initiator-utils

package.

Make sure iSCSI is enabled and properly configured on your system before proceeding with

iSER. Additionally

, make sure you have RDMA connectivity between the initiator and the target.

rping -s [-vVd] [-S size] [-C count] [-a addr] [-p port]

Targets settings such as timeouts and retries are set the same as any other iSCSI targets.

If targets are set to auto connect on boot, and targets are unreachable, it may take a long

time to continue the boot process if timeouts and max retries are set too high.

Example for discovering and connecting targets over iSER:

iscsiadm -m discovery -o new -o old -t st -I iser -p <ip:port> -l

iSER also supports RoCE without any additional configuration required. To bond the RoCE

interfaces, set the

fail_over_mac option in the bonding driver (see Section 4.4.6, “Bonding

IPoIB”, on page 82).

4.3 Ethernet over IB (EoIB) 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