User guide

Chapter 7. Configuring the Cisco 3012 InfiniBand to Ethernet gateway 133
7.4.1 Some comments on VLANs and the Ethernet gateway module
When discussing VLANs and the Ethernet gateway module, remember:
򐂰 Each Ethernet gateway module supports up to 32 VLANs
򐂰 Ethernet bridge module ports can be tagged or untagged
򐂰 Standard 802.1Q VLANs are supported
򐂰 Static port based VLANs are supported
򐂰 A full range of VLAN IDs are supported
򐂰 One VLAN is mapped to one InfiniBand partition (unique p_key)
򐂰 Separate multicast groups are created per InfiniBand partition (for multiple VLANs)
Figure 7-11 represents the configuration that we use to demonstrate using VLAN tagging on
the uplink. Note that by creating multiple bridge groups, each using a different p_key on the
InfiniBand side, and different VLAN tagging on the Ethernet side, and then associating them
to the same uplink or uplinks, it is possible to carry multiple VLANs on the same link or links
between the gateway module and the upstream switch. (We do not demonstrate this in this
section.)
Figure 7-11 Example for using tagged VLAN88
Assuming previous configurations have been removed, we can begin the configuration for
this section.
ib0
BladeServer10
ib1
Cisco BCH 4X
IB Switch
Cisco 3012
Cisco 4948
Ethernet
Switch
Gi1/16
Trunk
Native VLAN 1
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
Eth int 4/1
IB int 4/1
BG1
BladeCenter H
Ethernet Network
InfiniBand Network
VLAN 88 tagged