HP 376227-B21 Dual-port 4x Fabric Adapter User Guide - Page 79

IPoIB Setup, About IPoIB, Configuring IPoIB

Get HP 376227-B21 - ProLiant InfiniBand 4x Fabric Copper Switch PDF manuals and user guides
UPC - 829160632193
View all HP 376227-B21 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 79 highlights

67 IPoIB Setup About IPoIB IPoIB (IP over InfiniBand) is simply that: IP packets running over the IB fabric. This protocol is useful for testing connectivity into the fabric between two hosts, and also for taking advantage of the high speed fabric for "legacy" applications that are written to communicate over IP. Configuring IPoIB Configuration of IPoIB is similar to configuring Ethernet interfaces under Linux except the interfaces are called ibx (in othe words, ib0, ib1, etc) instead of ethx (for example, eth0, eth1, etc). To test the IPoIB interfaces, choose a subnet that is currently not routed in your network environment. For this test, we'll choose 192.168.0.0 with a netmask of 255.255.255.0 and assign "Server 1" the address 192.168.0.1 and "Server 2" 192.168.0.2. 1. On Server 1, use ifconfig to configure ib0. Example # ifconfig ib0 192.168.0.1 netmask 255.255.255.0 2. Verify that the interface was configured properly. Example # ifconfig ib0 ib0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST MTU:2044 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:128 RX bytes:0 (0.0 b) TX bytes:126 (126.0 b) 3. Repeat the process on Server 2 by configuring ib0 to 192.168.0.2. If the system failed to configure the interface properly, you may not have successfully installed the HCA drivers on the OS. If the drivers did not install, it is likely due to a version mismatch between the driver suite and the installed kernel. 4. To test connectivity, attempt to ping Server 2 from Server 1, using the ping command. Example # ping -c 1 192.168.0.2 PING 192.168.0.2 (192.168.0.2) from 192.168.0.1 : 56(84) bytes of data. 64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=154 usec --- 192.168.0.2 ping statistics --1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/mdev = 0.154/0.154/0.154/0.000 ms If you do not receive a response from the other server, check cable connectivity. Be sure the IB cable is plugged into the correct port for ib0 on the HCA (top port on the PCI adapter card). Also, check the LEDs on both the HCA and the IB switch. Refer to "Interpreting HCA LEDs" on page 61.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
67
IPoIB Setup
About IPoIB
IPoIB (IP over InfiniBand) is simply that: IP packets running over the IB fabric. This protocol is useful
for testing connectivity into the fabric between two hosts, and also for taking advantage of the high
speed fabric for “legacy” applications that are written to communicate over IP.
Configuring IPoIB
Configuration of IPoIB is similar to configuring Ethernet interfaces under Linux except the interfaces
are called ib
x
(in othe words, ib0, ib1, etc) instead of eth
x
(for example, eth0, eth1, etc).
To test the IPoIB interfaces, choose a subnet that is currently not routed in your network environment.
For this test, we'll choose 192.168.0.0 with a netmask of 255.255.255.0 and assign “Server 1” the
address 192.168.0.1 and “Server 2” 192.168.0.2.
1.
On
Server 1
, use
ifconfig
to configure ib0.
Example
2.
Verify that the interface was configured properly.
Example
3.
Repeat the process on
Server 2
by configuring ib0 to 192.168.0.2.
If the system failed to configure the interface properly, you may not have successfully installed the
HCA drivers on the OS. If the drivers did not install, it is likely due to a version mismatch between
the driver suite and the installed kernel.
4.
To test connectivity, attempt to ping
Server 2
from
Server 1
, using the
ping
command.
Example
If you do not receive a response from the other server, check cable connectivity. Be sure the IB
cable is plugged into the correct port for ib0 on the HCA (top port on the PCI adapter card). Also,
check the LEDs on both the HCA and the IB switch. Refer to
“Interpreting HCA LEDs” on
page 61
.
#
ifconfig ib0 192.168.0.1 netmask 255.255.255.0
#
ifconfig ib0
ib0
Link encap:Ethernet
HWaddr 00:00:00:00:00:00
inet addr:192.168.0.1
Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST
MTU:2044
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:128
RX bytes:0 (0.0 b)
TX bytes:126 (126.0 b)
#
ping -c 1 192.168.0.2
PING 192.168.0.2 (192.168.0.2) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=154 usec
--- 192.168.0.2 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.154/0.154/0.154/0.000 ms