Cisco InfiniBand 4x User's Guide Page 150

  • Download
  • Add to my manuals
  • Print
  • Page
    / 174
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 149
136 Implementing Cisco InfiniBand on IBM BladeCenter
After logging into the 4948 with sufficient privileges, execute the commands as shown in
Example 7-6 on the 4948 (items starting with an exclamation mark (!) are for
reference/comments only and will not be executed).
Example 7-6 Configure the 4948 to accept packets tagged with VLAN 88
! Assumes starting from enable mode, enter config mode
conf t
! Change int gi1/16 to support tagging for VLAN 88
int gi1/16
description Connection to 3012 Ethernet Switch Module port 4/1 - VLAN 88
! Tell the port to use 802.1Q tagging encapsalation
switchport trunk encapsulation dot1q
! Force the port to trunk mode to support multiple VLANs and tagging
switchport mode trunk
! Restrict VLANs to this single VLAN (can carry more if desired)
switchport trunk allowed vlan 88
! Change portfast to work in trunk mode
spanning-tree portfast trunk
! Exit config mode
end
! Save config to NVRAM
write
5. When the changes have been made to both the Ethernet gateway module and the 4948,
the InfiniBand client at 172.16.225.10 can successfully ping the VLAN 88 default gateway
IP address (172.16.225.250) on the 4948 as shown in Example 7-7.
Example 7-7 InfiniBand host pinging the default gateway
[root@localhost ~]# ping -c 5 172.16.225.250
PING 172.16.225.250 (172.16.225.250) 56(84) bytes of data.
64 bytes from 172.16.225.250: icmp_seq=1 ttl=255 time=0.303 ms
64 bytes from 172.16.225.250: icmp_seq=2 ttl=255 time=0.267 ms
64 bytes from 172.16.225.250: icmp_seq=3 ttl=255 time=0.289 ms
64 bytes from 172.16.225.250: icmp_seq=4 ttl=255 time=0.335 ms
64 bytes from 172.16.225.250: icmp_seq=5 ttl=255 time=0.291 ms
--- 172.16.225.250 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.267/0.297/0.335/0.022 ms
[root@localhost ~]#
7.4.4 CLI reference for this section
This section includes what the appropriate CLI looks like after the steps were executed in the
GUI to create this bridge group, as well as after the changes made to the 4948. It is a useful
reference for those wanting to understand the CLI better, or for those that simply want to use
the CLI and not the GUI to achieve this task.
Note that we include only the commands that effect the area of the device that we configured.
We do not include the entire device configuration.
Page view 149
1 2 ... 145 146 147 148 149 150 151 152 153 154 155 ... 173 174

Comments to this Manuals

No comments