Friday Aug 02, 2013

Friday Tips #39

Happy Friday! Our tip this week is on a little quirk of using Oracle VM 3 with templates developed in Oracle VM 2.

Question:
Why do I see new Oracle VM 3 networks named xenbr0 and xenbr1 after importing an Oracle VM Template?

Answer by Gregory King, Principal Best Practices Consultant, Oracle VM Product Management:
Some legacy Oracle VM Templates as well as some newer templates are designed to come pre-configured with network interfaces for Oracle VM 2 environments. Oracle VM 3 doesn’t really know what to do with the pre-configured network devices during the import process of an Oracle VM Template, so the product errors on the side of caution by creating place holders for networks. 

This means Oracle VM 3 automatically creates superfluous or false networks using the name of xenbr0, xenbr1, etc. when you import an Oracle VM Template that uses the Oracle VM 2 naming convention for bridges. So you are left with new networks named xenbr0 or xenbr1 that are useless since they are not associated with any servers, network ports or bonds. This can be quite confusing.

The problem is very easy to fix. Simply edit the newly imported Oracle VM Template, replace the networks named xenbr0 and xenbr1 with your real networks, then switch to the Network tab, highlight the networks named xenbr0 and xenbr1 and then delete them. 

Here is a step-by-step example... 

The screen shot below shows Oracle VM networks before a template is imported:

The next screen shot shows the superfluous networks after the new template has been imported:

The networks named xenbr0 and xenbr1 can safely be removed after they are no longer being used by the newly imported Oracle VM Template. Simply switch to the Repositories tab, find and edit the newly imported template as show in the screenshot below:

Now move xenbr0 and xenbr1 to the left hand box while moving the correct network or networks to the right hand box as shown in the screen shot below:

Finally, switch to the Networking tab, highlight and then delete the networks named xenbr0 and xenbr1 as shown in the screenshot below: 

...and now your Oracle VM networks should look just like they did before importing the template :-)


Thanks Greg!

We'll see you all next week with another tip!

-Chris 

Just Released – Two New Templates for Oracle Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3)

The new template continues to build on the integration of Oracle VM and Oracle Enterprise Manager to further automate the deployment of Oracle VM servers. This template can be used to provision new guest virtual machines running Oracle Enterprise Manager Cloud Control 12c Release 3 Oracle Management Service (OMS), Oracle Management Agent and Repository Database.

Note: This VirtualBox image is strictly for test Enterprise Manager setup or proof of concepts (POC), this should not be used for Enterprise Manager production site setup.
The Oracle VM VirtualBox Template for Oracle Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3) can be used to provision new guest virtual machines running Oracle Enterprise Manager Cloud Control 12c Release 3 Oracle Management Service (OMS), Oracle Management Agent and Repository Database. 

For a list of Oracle VM Templates,  please visit:

Oracle VM Templates on Oracle Technical Network 

For more Oracle VM VirtualBox Templates, please visit:

Oracle VM VirtualBox Templates on Oracle Technical Network 

For more information on Oracle Enterprise Manager 12c:

About

Get the latest scoop on products, strategy, events, news, and more, from Oracle's virtualization experts

Twitter

Facebook

Search

Archives
« August 2013 »
SunMonTueWedThuFriSat
    
3
4
5
6
8
10
11
15
17
18
24
25
26
28
29
31
       
Today