4.6.4 Task 4: Verify the 10 GbE Interfaces

The following procedure describes how to verify the 10 GbE interfaces:

1. Log in as the root user.
2. Use the cat command to review the /proc/net/bonding/bondeth0 file. The following is an example of the command and output from the command:

   # cat /proc/net/bonding/bondeth0
   
   Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)
    
   Bonding Mode: fault-tolerance (active-backup)
   Primary Slave: None
   Currently Active Slave: eth9
   MII Status: up
   MII Polling Interval (ms): 100
   Up Delay (ms): 5000
   Down Delay (ms): 5000
    
   Slave Interface: eth9
   MII Status: up
   Link Failure Count: 0
   Permanent HW addr: 00:1b:21:66:4b:c0
    
   Slave Interface: eth15
   MII Status: up
   Link Failure Count: 0
   Permanent HW addr: 00:1b:21:66:4b:c1
   

   In the output, verify the slave interfaces are correct, and the MII statuses for the slave interface are up.

3. Use the netstat -nr command to check the routing table. The routing table should not have changed. The following is an example of the command and output:

   # netstat -nr
   
   Kernel IP routing table
   Destination   Gateway      Genmask         Flags   MSS Window  irtt Iface
   scan_subnet 0.0.0.0        255.255.255.0   U         0 0          0 bondeth0
   192.168.80.0  0.0.0.0      255.255.254.0   U         0 0          0 bondib0
   192.168.80.0  0.0.0.0      255.255.254.0   U         0 0          0 bondib1
   192.168.80.0  0.0.0.0      255.255.254.0   U         0 0          0 bondib2
   192.168.80.0  0.0.0.0      255.255.254.0   U         0 0          0 bondib3
   mgmt_subnet 0.0.0.0        255.255.254.0   U         0 0          0 eth0
   0.0.0.0       scan_gw      0.0.0.0         UG        0 0          0 bondeth0
   

4. Use the following commands to check the default gateway. The gateway is the SCAN network gateway, and should use bondeth0 on the 10 GbE interfaces.

   # grep GATEWAY /etc/sysconfig/network
   GATEWAY=gw_address
   GATEWAYDEV=bondeth0 
   
   # ping -c 2 gw_address
   PING gw_address (gw_address) 56(84) bytes of data.
   64 bytes from gw_address: icmp_seq=1 ttl=57 time=1.12 ms
   64 bytes from gw_address: icmp_seq=2 ttl=57 time=1.05 ms
   
   --- gw_address ping statistics ---
   2 packets transmitted, 2 received, 0% packet loss, time 1002ms
   rtt min/avg/max/mdev = 1.054/1.087/1.120/0.033 ms
   

   In the preceding commands and output, gw_address is the IP address of the default gateway.

5. If the name servers were responding to the ping command in "Task 1: Verify ping Functionality", then use the following commands to check the name servers. Similar commands can be used to check other servers that connect to Oracle Exadata Database Machine.

   # grep "^nameserver" /etc/resolv.conf
   nameserver ip_address_1
   nameserver ip_address_2
   
   # ping -c 2 ip_address_1
   PING ip_address_1 (ip_address_1) 56(84) bytes of data.
   64 bytes from ip_address_1: icmp_seq=1 ttl=57 time=1.12 ms
   64 bytes from ip_address_1: icmp_seq=2 ttl=57 time=1.05 ms
    
   --- ip_address_1 ping statistics ---
   2 packets transmitted, 2 received, 0% packet loss, time 1002ms
   rtt min/avg/max/mdev = 1.054/1.087/1.120/0.033 ms