Cisco InfiniBand 4x User's Guide Page 158

  • Download
  • Add to my manuals
  • Print
  • Page
    / 174
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 157
144 Implementing Cisco InfiniBand on IBM BladeCenter
a time) and make sure pings continue to work, regardless of if we have either cable
plugged in, or both cables plugged in.
In Example 7-11, we lost a total of three pings while pulling and adding cables. Ping
packet 9 was lost when we pulled the first cable, ping packets 21 and 22 were lost when
we reinserted the first cable and pulled the second cable.
Example 7-11 InfiniBand host pinging the default gateway while cables being pulled and re-added
[root@localhost ~]# ping 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.290 ms
64 bytes from 172.16.225.250: icmp_seq=2 ttl=255 time=0.270 ms
64 bytes from 172.16.225.250: icmp_seq=3 ttl=255 time=0.277 ms
64 bytes from 172.16.225.250: icmp_seq=4 ttl=255 time=0.301 ms
64 bytes from 172.16.225.250: icmp_seq=5 ttl=255 time=0.269 ms
64 bytes from 172.16.225.250: icmp_seq=6 ttl=255 time=0.331 ms
64 bytes from 172.16.225.250: icmp_seq=7 ttl=255 time=0.271 ms
64 bytes from 172.16.225.250: icmp_seq=8 ttl=255 time=0.291 ms
64 bytes from 172.16.225.250: icmp_seq=10 ttl=255 time=0.344 ms
64 bytes from 172.16.225.250: icmp_seq=11 ttl=255 time=0.359 ms
64 bytes from 172.16.225.250: icmp_seq=12 ttl=255 time=0.253 ms
64 bytes from 172.16.225.250: icmp_seq=13 ttl=255 time=0.263 ms
64 bytes from 172.16.225.250: icmp_seq=14 ttl=255 time=0.273 ms
64 bytes from 172.16.225.250: icmp_seq=15 ttl=255 time=0.338 ms
64 bytes from 172.16.225.250: icmp_seq=16 ttl=255 time=0.326 ms
64 bytes from 172.16.225.250: icmp_seq=17 ttl=255 time=0.340 ms
64 bytes from 172.16.225.250: icmp_seq=18 ttl=255 time=0.337 ms
64 bytes from 172.16.225.250: icmp_seq=19 ttl=255 time=0.726 ms
64 bytes from 172.16.225.250: icmp_seq=20 ttl=255 time=0.322 ms
64 bytes from 172.16.225.250: icmp_seq=23 ttl=255 time=0.292 ms
64 bytes from 172.16.225.250: icmp_seq=24 ttl=255 time=0.323 ms
64 bytes from 172.16.225.250: icmp_seq=25 ttl=255 time=0.339 ms
64 bytes from 172.16.225.250: icmp_seq=26 ttl=255 time=0.333 ms
64 bytes from 172.16.225.250: icmp_seq=27 ttl=255 time=0.302 ms
64 bytes from 172.16.225.250: icmp_seq=28 ttl=255 time=0.329 ms
64 bytes from 172.16.225.250: icmp_seq=29 ttl=255 time=0.264 ms
--- 172.16.225.250 ping statistics ---
29 packets transmitted, 26 received, 10% packet loss, time 28004ms
rtt min/avg/max/mdev = 0.253/0.321/0.726/0.088 ms
[root@localhost ~]#
7.5.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 TG1, 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 only include the commands that effect the area of the device we configured. We
do not include the entire device configuration.
Page view 157
1 2 ... 153 154 155 156 157 158 159 160 161 162 163 ... 173 174

Comments to this Manuals

No comments