7–RoCE Configuration
Configuring RoCE on the Adapter for Linux
153
BC0154501-00 P
Verifying RoCE v2
Run over the same subnet and use the RoCE v2 GID Index.
Server#
ib_send_bw -d qedr0 -F -x 1
Client#
ib_send_bw -d qedr0 -F -x 1 192.168.100.3
Verifying RoCE v2 Through Different Subnets
To verify RoCE v2 through different subnets:
1.
Set the route configuration for the server and client using the DCBX-PFC
configuration.
System Settings:
Server VLAN IP
: 192.168.100.3 and
Gateway :
192.168.100.1
Client VLAN IP
:
192.168.101.3 and
Gateway :
192.168.101.1
Server Configuration:
#
/sbin/ip link add link p4p1 name p4p1.100 type vlan id 100
#
ifconfig p4p1.100 192.168.100.3/24 up
#
ip route add 192.168.101.0/24 via 192.168.100.1 dev p4p1.100
Client Configuration:
#
/sbin/ip link add link p4p1 name p4p1.101 type vlan id 101
#
ifconfig p4p1.101 192.168.101.3/24 up
#
ip route add 192.168.100.0/24 via 192.168.101.1 dev p4p1.101
2.
Set the switch settings using the following procedure.
Use any flow control method (Pause, DCBX-CEE, or DCBX-IEEE),
and enable IP routing for RoCE v2. See
for RoCE v2 configuration, or refer to the vendor
switch documents.
NOTE
If you are running through a switch PFC configuration, use vLAN GIDs for
RoCE v1 or v2 through the same subnet.
NOTE
You must first configure the route settings for the switch and servers. On the
adapter, set the RoCE priority and DCBX mode using either the HII, UEFI
user interface, or one of the Cavium management utilities (see
).
