Oracle VM Server Got Evicted from Cluster During Network Outage
(Doc ID 2424899.1)
Last updated on JUNE 15, 2020
Applies to:
Oracle VM - Version 3.3.4 to 3.4.5 [Release OVM33 to OVM34]Oracle Cloud Infrastructure - Version N/A and later
Linux x86
Linux x86-64
Symptoms
During network outage where Switch A lost access to the Gateway while Switch B was still active, Oracle VM Servers got evicted from the cluster due to reaching the Network Heartbeat timeout.
On one of the node, below error is visible before reboot:
Jul 8 14:43:02 serv1 kernel: [346223.040811] o2net: Connection to node 1 (num 1) at 127.0.0.2:7777 has been idle for 90.112 secs.
Jul 8 14:43:02 serv1 kernel: [346223.296828] o2net: Connection to node 2 (num 2) at 127.0.0.3:7777 has been idle for 90.112 secs.
Jul 8 14:43:02 serv1 kernel: [346223.296828] o2net: Connection to node 3 (num 3) at 127.0.0.4:7777 has been idle for 90.112 secs.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |