Exalogic Virtual: "ifcfg-xenbr0" Gets Deleted Upon Deleting a Compute Node From OVM Manager In Oct 2020 PSU and 184.108.40.206.X Racks Upgraded using Upgrade Kit
(Doc ID 2794096.1)
Last updated on FEBRUARY 11, 2022
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.201020 to 18.104.22.168.210420
Oracle Virtual Server x86-64
Exalogic Virtual Releases 22.214.171.124.X Virtual racks which were upgraded from 126.96.36.199.X (using Upgrade Kit).
This issue occurs in Oct 2020 PSU and 188.8.131.52.x racks that has been upgraded from Oct 2020 PSU using the Upgrade Kit
ifcfg-xenbr0 file inside /etc/sysconfig/network-scripts directory gets deleted upon deleting a Compute Node (DOM0) from OVM Manager BUI console. This issue is observed after performing the steps in the following MOS note to delete and rediscover the compute node from the OVM Manager BUI console.
xenbr0 is the management network used to connect to the compute node from outside the Exalogic rack. With ifcfg-xenbr0 deleted the compute node cannot be accessed from outside the rack. In addition, the Xen Bridge is non-functional.
Before deleting the Compute node from OVM Manager, ifcfg-xenbr0 and other Management network bond files ifcfg-bond0, ifcfg-eth0 are present as shown below:
This issue can occur in 2 scenarios:
- After upgrading to Oct 2020 PSU
- In 184.108.40.206.x racks that has been upgraded from Oct 2020 PSU using the Upgrade Kit
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