User guide

Chapter 7. Configuring the Cisco 3012 InfiniBand to Ethernet gateway 123
After you have configured these two clients and they can ping each other, you can proceed to
configuring the Ethernet gateway module, examples of which can be found in the following
sections.
7.3 Implementing a simple bridge group connection to an
upstream Ethernet network
In this section, we demonstrate the ability to ping from an InfiniBand server to an IP address
on the upstream Ethernet switch, using a single Ethernet connection out of the gateway
module. This is the simplest design but offers no redundancy and no specific VLAN support.
7.3.1 The design
Figure 7-4 shows the basic layout of our test environment for this connection.
Figure 7-4 Simple connectivity from InfiniBand client to Ethernet network
The IP address of server 10, 172.16.225.10, is on the ib0 interface for this server. It is
assumed that this IP address is already configured and tested at this point.
On the gateway module, we use Ethernet port 4/1 and InfiniBand port 4/1 in this example and
create and configure bridge group 1 (BG1).
This example uses VLAN 88 on the Ethernet switch port connecting to interface Ethernet port
4/1 on the Ethernet gateway. Since this port will be configured as Access mode on the
upstream switch, only untagged packets will be sent and received. This means the Ethernet
gateway port should be configured as
untagged (when the untagged packet reaches the
ib0
BladeServer10
ib1
Cisco BCH 4X
IB Switch
Cisco 3012
Cisco 4948
Ethernet
Switch
Gi1/16
Access
VLAN 88
12 port IB – slot 15
12 port IB – slot 16
EGW
EGW = Ethernet Gateway Module
BG1 = Bridge Group 1
Blue = InfiniBand
Green = Ethernet
Using default p_key – ff:ff
Ib0 = 172.16.225.10
Int VLAN 88
172.16.225.250
On 4948
Untagged traffic
Eth int 4/1
IB int 4/1
BG1
BladeCenter H
Ethernet Network
InfiniBand Network