HP InfiniBand Solution for Oracle RAC Environments white paper

6. Verify that the ib device started successfully by examining the output of the command ifconfig.
Output from the command should contain something similar to the following:
ib0 Link encap:Ethernet HWaddr DD:8B:86:C8:4D:0B
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1
RX packets:967 errors:0 dropped:0 overruns:0 frame:0
TX packets:1264 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:128
RX bytes:65612 (64.0 Kb) TX bytes:1052848 (1.0 Mb)
7. Once the virtual InfiniBand NIC has been configured on each node, ensure that the nodes can
communicate through the ib devices.
8. If the Cluster Verification Utility (CVU) packaged with the HP PDC scripts is run after the IB device
has been configured, some versions of the CVU will report a failure during the Private Network
test of the Network Configuration section:
# Network Configuration
+ Number of network interfaces 2 >= 2
pass
+ Number of network interfaces 2 >= 2
pass
E Private Network
disabled enabled fail
+ Public Network enabled enabled
pass
+ Local Host Loop Back
OK == pass
+
Local Host Loop Back OK == pass
+
topspin1san Host Ping topspin1san
== ping
OK
pass
+ topspin1san IP Ping 192.168.0.1
== ping
OK
pass
+ topspin2san Host Ping topspin2san
== ping
OK
pass
+ topspin2san IP Ping 192.168.0.2
== ping
OK
pass
+
topspin1 Host Ping topspin1
== ping
OK
pass
+ topspin1 Host Ping topspin1
== ping
OK
pass
+
topspin1 IP Ping 15.13.183.67
== ping
OK
pass
+
topspin2 Host Ping topspin2
== ping
OK
pass
+
topspin2 IP Ping 15.13.183.68
== ping
OK
pass
9. The CVU will report this failure because it is unable to detect the IB device. This failure can safely
be ignored. All of the other tests in the Network configuration section should pass, and any other
failures should be investigated before continuing.
10