Cisco InfiniBand 4x User's Guide Page 138

  • Download
  • Add to my manuals
  • Print
  • Page
    / 174
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 137
124 Implementing Cisco InfiniBand on IBM BladeCenter
Cisco 4948 Ethernet Switch, the 4948 will put any untagged packet on to VLAN 88 inside the
4948).
Assuming the client and other components are already configured, all we have to do is create
a bridge group with the desired options in the gateway module, to permit packets to flow.
Note that a bridge group is a logical entity that allows the gateway to pass InfiniBand frames
to the Ethernet network.
7.3.2 Some comments on bridge groups
When creating a bridge group, remember:
򐂰 A bridge group is an entity that runs on the Ethernet gateway module and enables the
bridging of one IPoIB partition to one VLAN.
򐂰 The Ethernet gateway acts like a Layer 2 bridge between InfiniBand and Ethernet. Each
Ethernet gateway must be configured for Layer 2 bridging (with or without link aggregation
and redundancy groups).
򐂰 Configuring a bridge group enables the system to learn everything it needs to know about
the location of nodes on the network with very little input from the administrator.
򐂰 The bridge group only bridges the IP protocol and drops all other traffic.
򐂰 Attributes of the bridge port must be created or deleted with the bridge group. For
example, the physical port attribute is assigned at the time the bridge group is created,
and cannot be changed without deleting the bridge group.
򐂰 The parameters that you define for the bridge group determine the way the traffic is
handled between the InfiniBand network and the Ethernet network. The bridge port has
certain attributes that are always attached to the bridge port entity, and certain attributes
that are optional to the bridge port.
򐂰 Some mandatory items:
You must select a p_key (default is ff:ff). If you use a non default p_key on the gateway
module, you will need to configure the InfiniBand clients and InfiniBand fabric to use
this p_key.
You must select a physical Ethernet port number(s) or aggregation/trunk interface.
򐂰 Some optional items:
Non-default p_key (not covered in this chapter)
VLAN tagging
Aggregation/trunking
For our example, we demonstrate creating the bridge group using the Element Manager.
Then we show what the CLI looks like after this configuration is applied.
7.3.3 Summary of steps to implement a simple bridge group design
Here, we provide a summary of the steps that we describe in the remainder of this section to
implement the simple bridge group design:
1. In the 3012 Element Manager, open the Bridging window (step 1 on page 125).
2. Open the Add Bridge Group window and complete the information in the Groups tab (step
2 on page 126).
3. Complete the Forwarding and Subnet tabs in the Add Bridge Group window (step 3 on
page 128).
Page view 137
1 2 ... 133 134 135 136 137 138 139 140 141 142 143 ... 173 174

Comments to this Manuals

No comments