7.13 Returning Oracle VM Server Pool to Operation After Network Services Restart

Warning

This section applies only to systems with an InfiniBand-based network architecture. The use of the bond0 interface described in this section is inherent to the network design based on the use of Oracle Fabric Interconnect F1-15s .

When network services are restarted on the master management node, the connection to the Oracle VM management network ( bond0 ) is lost. By design, the bond0 interface is not brought up automatically on boot, so that the virtual IP of the management cluster can be configured on the correct node, depending on which management node assumes the master role. While the master management node is disconnected from the Oracle VM management network, the Oracle VM Manager user interface reports that the compute nodes in the server pool are offline.

The management node that becomes the master, runs the Oracle VM services necessary to bring up the bond0 interface and configure the virtual IP within a few minutes. It is expected that the compute nodes in the Oracle VM server pool return to their normal online status in the Oracle VM Manager user interface. If the master management node does not reconnect automatically to the Oracle VM management network, bring the bond0 interface up manually from the Oracle Linux shell.

Warning

Execute this procedure ONLY when so instructed by Oracle Support. This should only be necessary in rare situations where the master management node fails to connect automatically. You should never manually disconnect or restart networking on any node.

Manually Reconnecting the Master Management Node to the Oracle VM Management Network

Using SSH and an account with superuser privileges, log into the disconnected master management node on the appliance management network.
```
# ssh root@192.168.4.3
root@192.168.4.3's password:
[root@ovcamn05r1 ~]#
```

Check the configuration of the bond0 interface.

If the interface is down, the console output looks similar to this:

# ifconfig bond0
bond0     Link encap:Ethernet  HWaddr 00:13:97:4E:B0:02  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Bring the bond0 interface up.
```
# ifconfig bond0 up
```

Check the configuration of the bond0 interface again.

When the interface reconnects successfully to the Oracle VM management network, the console output looks similar to this:

# ifconfig bond0
bond0     Link encap:Ethernet  HWaddr 00:13:97:4E:B0:02  
          inet addr:192.168.140.4  Bcast:192.168.140.255  Mask:255.255.255.0
          inet6 addr: fe80::213:97ff:fe4e:b002/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:62191 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9183 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4539474 (4.33 MB)  TX bytes:1853641 (1.77 MB)