Last updated on MAY 08, 2015
Applies to:Oracle Exalogic Elastic Cloud Software - Version 184.108.40.206.0 to 220.127.116.11.0
You have an installation of Exalogic Virtual running on Exalogic Elastic Cloud Software (EECS) version 18.104.22.168.0 where you have previously created an untagged external network, which is not tagged by a vLAN, and have been using this network successfully with guest vServers. However you have encountered a problem immediately after applying the Exalogic January 2015 Patchset Update (PSU), where any Guest vServer you restart via EM OpsCenter (EMOC) is created without a valid network environment for the untagged network. In the case of any new vServer created you will find that it works initially, immediately after creation, but also fails once it has been restarted by EMOC.
When you encounter this issue the Hardware (MAC) address for the interface corresponding to the untagged network is shown as all zeros in the output from ifconfig on the impacted vServer:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms