In releases prior to 3.3, if VLAN port group names have one or more commas in them, they may not be parsed correctly when Oracle VM Manager is doing a re-discover of an Oracle VM Server after Oracle VM Manager has just been upgraded to 3.3. In the case of an untagged VLAN interface, this can lead to the VLAN interfaces or the underlying port not being associated with a network in Oracle VM Manager. However, the Oracle VM Server is still configured correctly.

Performing a re-discover of the Oracle VM Server after the upgrade to 3.3 corrects the view that Oracle VM Manager has of the network configuration. In version 3.3, VLAN port groups have been removed. Therefore, once the system is upgraded to version 3.3 and a re-discover is done, the issue is resolved.

Bug 18758922