Cisco InfiniBand 4x User's Guide Page 162

  • Download
  • Add to my manuals
  • Print
  • Page
    / 174
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 161
148 Implementing Cisco InfiniBand on IBM BladeCenter
6. Create the redundancy group using the two previously created bridge groups (step 6 on
page 151).
7. Save the 3012 config to NVRAM (step 7 on page 152).
8. Configure the upstream 4948 to match the Ethernet Gateway configuration (step 8 on
page 152).
9. Re-attach or bring up the links between the 3012 and the 4948 (step 9 on page 153).
10.Test the configurations by pinging from the InfiniBand client to the default gateway on the
4948 and remove links from the gateway modules one at a time to ensure trunk is working
(step 10 on page 153).
7.6.3 Detailed steps to implement a redundant gateway design
To implement a redundant gateway design, follow these detailed steps:
1. Make sure the cables between the module and the upstream switch are either unplugged
or logically shut down. This is to ensure that we do not introduce any temporary spanning
tree loops that could disrupt network communications.
2. Prior to configuring, delete any trunk group and/or bridge group that might have existed
from previous examples (note that you can instead choose to just modify existing groups,
but this example does not do this).
3. After you have a clean configuration, you can start configuring the 3012. The first step for
configuring the 3012 is to add a management InfiniBand interface and give it an IP
address.
During the creation of this document, the only way found to set the IP address on the
mgmt-ib interface and bring it up was through the CLI. To perform this step, telnet to the
management IP address of the 3012, log in (a user ID and password of super/super is the
default) and then run the commands as show in Example 7-14 on page 148.
Example 7-14 Adding an ib management interface for redundancy
conf t
interface mgmt-ib
ip address 192.168.0.1 255.255.255.0
no shutdown
exit
exit
copy running startup
The IP address that we used in this example is on a subnet not in use elsewhere on the
network, and if you want to use separate 3012 chassis for the gateway redundancy, these
addresses need to be on the same IP subnet on each 3012.
Tip: If you do not have an IP address on the mgmt-ib interface, and do not bring it up,
redundancy will not pass packets. If individual bridge groups pass traffic just fine, but
fail to pass traffic when placed in a redundancy group, check to make sure the mgmt-ip
interface is configured with an IP address and in a no shutdown state.
Tip: Do not put a default gateway on the mgmt-ib interface. There might be rare cases
when this is desired, but in those cases, make sure there is not a default gateway also
on the mgmt-ethernet interface. Having more than one default gateway can confuse
management traffic flows and lead to unexpected operation.
Page view 161
1 2 ... 157 158 159 160 161 162 163 164 165 166 167 ... 173 174

Comments to this Manuals

No comments