Note:
The X2-4, X3-4, X4-4, X5-4, and X6-4 Exalytics Machines are certified with Oracle VM 3.3.3.
This section includes the following topics:
Parent topic: Configuring Exalytics Machine for Virtualization
Before you virtualize an Exalytics Machine, review the following sections:
As you prepare to virtualize an Exalytics Machine, do the following:
Review the Oracle VM Release Notes, to ensure that you understand the differences between Oracle Virtual Machine and its documented functionality, and any other issues that apply to the current release.
Review Oracle VM Installation and Upgrade Guide for Release 3.2 and Oracle VM User's Guide for Release 3.2 to ensure that you understand how to install and configure Oracle Virtual Machine Server, set up networking, and create virtual machines.
Review Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4, X4-4, X5-4, and X6-4 to ensure that you have properly configured and commissioned the Exalytics Machine in your data center.
The following prerequisites must be met before you can virtualize an Exalytics Machine:
The Exalytics Machine has been racked and mounted in a data center.
Oracle Integrated Lights Out Manager (ILOM) 3.1.2.24 or later, is configured to be accessible from the network using the web interface.
All networking information such as host name, IP address, subnet, gateway, and DNS are available.
Spare, unassigned IP addresses are available for the server pool and for each virtual machine deployed on the Exalytics Machine.
A Linux environment is available to install Oracle VM Manager.
You have access to the internet from a computer (not necessarily the Exalytics Machine) to download required software.
If required, remove the existing partition on /dev/sdb which is mounted to /u01 from the Exalytics Machine. You cannot create a repository on a Oracle Virtual Machine disk which contains a partition.
Note:
Before removing the existing partition, remember to back up all data on sdb1. If you are removing the existing partition on a new machine, you do not need to back up your data.
To remove existing partitions:
This section consists of the following topics.
The X2-4 Exalytics Machine comprises six hard drives, each having a capacity of 600 GB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 457 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X2-4 Exalytics Machine:
The X3-4 Exalytics Machine comprises 6 hard drives, each having a capacity of 900 GB.Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 657 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X3-4 Exalytics Machine:
The X4-4 Exalytics Machine comprises six hard drives, each having a capacity of 1.2 TB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 1000 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X4-4 Exalytics Machine:
The X5-4 Exalytics Machine comprises six hard drives, each having a capacity of 1.2 TB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X6-4 and X5-4 Exalytics Machine:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
At the prompt, Press Ctrl><R> for WebBIOS... , press Ctrl+Y to access the LSI MegaRAID utility as the Exalytics Machine is restarting.
Note:
Observe the screen carefully as the Press Ctrl><R> for WebBIOS... .message displays for a very short time. This avoids restarting the machine again.
The Virtual Drive Management screen is displayed.
Delete the existing RAID configuration, by performing the following actions:
Select the first virtual drive and Press F2.
Select Delete VD.
At the prompt, Press Yes.
Repeat the above steps (a to c) to delete the second virtual drive.
Create a RAID1 partition of two virtual drive, by performing the following actions:
On the Virtual Drive Management screen, Press F2.
Select Create Virtual Drive.
The Create New VD screen is displayed.
In the RAID Level drop down field, select RAID1.
Under Basic Settings, in the Size field, enter 100.
Select Advanced.
The Create Virtual Drive-Advanced screen is displayed.
Select Initialize, and then select OK.
The "Initialization complete on VD 0" message is displayed.
Select OK.
The Virtual Drive Management screen displays the 100 GB virtual disk created.
To create the second virtual drive, select Drive Group: 0, RAID1, press F2, and then select Add New VD.
In the RAID Level drop down field, select RAID1.
Under Basic Settings, in the Size field, accept the default value, and select Advanced.
Select Initialize, and then select OK.
The "Initialization complete on VD 1" message is displayed.
Select OK.
The Virtual Drive Management screen displays the RAID1 partition created of two virtual drives.
Create a RAID5 partition with the remaining drives, by performing the following actions:
On the Virtual Drive Management screen, select LSI MegaRAID, press F2, and then select Create Virtual Drive.
The Create New VD screen is displayed.
In the RAID Level drop down field, select RAID5.
Select the four virtual drives (02, 03, 04, 05).
Note:
For each virtual drive, accept the default size of the drive.
Select Advanced.
Select Initialize, and then select OK.
The "Initialization complete on VD 2" message is displayed.
Select OK.
The Virtual Drive Management screen displays the RAID5 partition created of four four virtual drives.
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
This section includes the following topics:
This section includes the following topics:
To install Oracle VM Server 3.3.3:
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Exalytics Software 2.0.0.1.0.
Select Release 2.1 related to the download queue.
Click Continue.
Choose the required part number in the available list of softwares.
Download and unzip the Oracle Exalytics Base Image 2.2.0.1.0 for Exalytics Oracle VM x86-64 (Part number V789434-01) to a local directory.
The zip file contains the Exalytics_2.2.0.0.0_X4-4_OVS3.3.3_751_<DATE>.iso file. Use this iso file to install the Oracle VM Server 3.3.3 on an X2-4, X3-4, X4-4 or X5-4 Exalytics Machine.
On the Exalytics Machine, connect and log on to Oracle Integrated Lights Out Manager (ILOM).
Note:
If you are installing Oracle VM Server 3.2.9 on an X2-4 or X3-4 Exalytics Machine, you must use ILOM 3.1.2.24.d or later version. If you are installing Oracle VM Server 3.3.3 on an X4-4, X5-4 or X6-4 Exalytics Machine, you must use ILOM 3.2.4.18 or later version.
For the latest Exalytics certified ILOM versions, see the Oracle Exalytics Certification Matrix. The Oracle Exalytics Certification Matrix is located at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
On the Summary Information screen, under Actions, click Launch to launch the Remote Console.
The ILOM remote console is displayed.
For X2-4, X3-4, X4-4, X5-4, or X6-4 machines, from the menu bar, select KVMS, then Storage.
Click Add to link to the Oracle VM Server 3.3.3 image (Exalytics_2.2.0.0.0_X4-4_OVS3.3.3_751_<DATE>.iso) as a remote virtual CD-ROM in ILOM.
Click Connect.
In the left pane of the ILOM, expand Host Management, then select Host Control. In the Next Boot Device list, select CDROM, then click Save.
Restart the machine by expanding in the left pane of the ILOM, Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts and displays the Oracle VM Server screen.
Press Enter to install Oracle VM Server.
The Oracle VM Server is installed on the Exalytics Machine. After Oracle VM Server is installed, the Exalytics Machine restarts automatically.
To install Oracle VM Server 3.3.3:
Navigate to My Oracle Support (MOS) and download the patch number 22546910.
Download the package and unzip to a local directory.
The downloaded zip file contains Exalytics_2.2.0.0.0_X6-4_OVS3.3.3_<DATE>.iso and a patch file p20431965_20001_Linux-x86-64.zip.
On the Exalytics Machine, connect and log on to Oracle Integrated Lights Out Manager (ILOM).
Note:
For the latest Exalytics certified ILOM versions, see the Oracle Exalytics Certification Matrix. The Oracle Exalytics Certification Matrix is located at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
On the Summary Information screen, under Actions, click Launch to launch the Remote Console.
The ILOM remote console is displayed.
From the menu bar, select KVMS, then Storage. Click Add to link to the Oracle VM Server 3.3.3 image for X6-4 machine (Exalytics_2.2.0.0.0_X6-4_OVS3.3.3<DATE>.iso) as a remote virtual CD-ROM in ILOM. Click Connect.
In the left pane of the ILOM, expand Host Management, then select Host Control. In the Next Boot Device list, select CDROM, then click Save.
Restart the machine by expanding in the left pane of the ILOM, Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts and displays the Oracle VM Server screen.
Press Enter to install Oracle VM Server.
The Oracle VM Server is installed on the Exalytics Machine. After Oracle VM Server is installed, the Exalytics Machine restarts automatically.
Perform the following postinstallation steps to configure the network on Oracle VM Server.
Editing the /etc/sysconfig/network File
You edit the /etc/sysconfig/network file to add the hostname of the machine and gateway and netmask for the network.
To edit the /etc/sysconfig/network file:
Navigate to and open the /etc/sysconfig/network file in a text editor.
Change the HOSTNAME to the name of the machine.
Enter the GATEWAY and NETMASK for the network.
For example:
NETWORKING=yes
NETWORKING_IPV6=no
GATEWAY=xx.xxx.xxx.x
NETMASK=xxx.xxx.xxx.x
HOSTNAME=<name of the machine>
Save the file.
Configuring bond0
You configure bond0 by editing the ifcfg-bond0 file.
To edit the ifcfg-bond0 file:
Navigate to and open the /etc/sysconfig/network-scripts/ifcfg-bond0 file in a text editor.
Change the BOOTPROTO to static.
For example:
BOOTPROTO=static
Add the IP Address of the machine.
For example:
IPADDR=xx.xxx.xx.xxx
Editing the hosts File
To edit the hosts file:
Navigate to and open the /etc/hosts file in a text editor.
Add the IP Address, host name, and alias for the host.
For example:
xx.xxx.xx.xxx exalyticsHost1.mycompany.com.exalytics Host1
Note:
Ensure the IP Address of the host is the same as the IP Address you entered in the ifcfg-bond0 file.
Editing the resolv.conf File
To edit the resolve.conf file:
Navigate to and open the /etc/resolve.conf file in a text editor.
Enter the DNS Server name and the Search base.
For example:
nameserver xxx.xxx.xxx.xxx
search xxx.mycompany.com
Note:
You can create additional bonded ports from Oracle VM Manager after the server is registered. See Creating a New Network Channel for Virtual Machines
Restarting the Exalytics Machine
To restart the Exalytics Machine:
In the left pane of the ILOM, expand Host Management, then select Power Control.
In the Select Action list, select Power Cycle, then click Save.
You upgrade the Exalytics Base Image for Oracle VM 2.2.0.1.0 by applying the patch on Oracle VM Server. The patch upgrades the Base Image to 2.2.0.1.0, installs Flash drivers and utilities.
To upgrade Oracle Exalytics Base Image for Oracle VM to 2.2.0.1.0:
Use the appropriate patch for the machines:
For X6-4 machine using Oracle VM Server 3.3.3, use the patch file p20431965_20001_Linux-x86-64.zip downloaded in Installing Oracle VM Server 3.3.3 on X6-4 and X5-4 Machines.
For X5-4 machine using Oracle VM Server 3.3.3, use the patch file p20431965_20001_Linux-x86-64.zip downloaded in Installing Oracle VM Server 3.3.3 on X6-4 and X5-4 Machines.
For X4-4 and earlier machines, navigate to My Oracle Support and download patch number 20431965: Patchset Upgrade Utility for Exalytics Base Image 2.2.0.1.0 Oracle VM for Linux x86-64. The patch contains the p2.6.39-400.248.3.el6uek x86_64.zip file. The zipped file contains Flash drivers and Flash configurator scripts.
Log on to the Exalytics Machine as the root user.
Extract the contents of the file into an appropriate directory on the Exalytics Machine.
Unzip the file into a temporary (/tmp) directory.
The following directory is created:
exalytics_ovs_server_base_image_upgrade_to_2.2.0.1.0.
Navigate to the directory by entering the following command:
# cd exalytics_ovs_server_base_image_upgrade_to_2.2.0.1.0
To upgrade the Base Image to 2.2.0.1.0 and to install Flash, enter the following command:
# ./update.sh
The output looks similar to the following:
current_kernel_version=2.6.39-400.215.9.el6uek
minimum_kernel_version=2.6.39-400.215.9.el6uek
OS Version check passed..
Update to 2.2.0.1.0.ovs-3.2.9 starting at DAY-DD-MM-YYYY HR:MIN:SEC
Removing unnecessary packages...
Skipping removing rpm kernel-ib-devel as it doesn't exist...
Skipping removing rpm kernel-ib as it doesn't exist...
Skipping removing rpm ibvf-config as it doesn't exist...
Removing RPM OpenIPMI-tools ...
Done
Running new install steps...
Preparing... ################################################## [100%]
exalogic.tools ################################################## [100%]
--------------------------------------------------------
Successfully installed exalogic.tools
--------------------------------------------------------
.....[exalogic.tools] := Post Transaction called...............
Running update...
Applying libibumad
Preparing... ################################################## [100%]
libibumad ################################################## [100%]
Preparing... ################################################## [100%]
libibmad ################################################## [100%]
Preparing... ################################################## [100%]
openib ################################################## [100%]
Preparing... ################################################## [100%]
opensm-libs ################################################## [100%]
opensm ################################################## [100%]
error: Failed dependencies:
infiniband-diags is needed by ovsvf-config-1.0-10.noarch
Preparing... ################################################## [100%]
infiniband-diags ################################################## [100%]
Preparing... ################################################## [100%]
exalytics-flash ################################################## [100%]
postInstall (exalytics-flash) 1 ...
[EXALYTICS_INFO:GENERAL] Updating exalytics-flash-config file to set FLASH_INSTALL_TYPE=OVS ...
postInstall (exalytics-flash) 1; done
Preparing... ################################################## [100%]
Installing....
Lib_Utils ################################################## [100%]
MegaCli ################################################## [100%]
Preparing... ################################################## [100%]
hesiod ################################################## [100%]
autofs ################################################## [100%]
sas_snmp ################################################## [100%]
Starting snmpd
Starting snmpd: [ OK ]
Registering Service lsi_mrdsnmpd
Starting LSI SNMP Agent
Starting LSI SNMP Agent:LSI MegaRAID SNMP Agent Ver 3.18.0.2 (Oct 30th, 2012) Started
[ OK ]
Preparing... ################################################## [100%]
policycoreutils-1.33.12-14.8.el6
oracle-hmp-libs ################################################## [100%]
oracle-hmp-hwmgmt ################################################## [100%]
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
ipmiflash ################################################## [100%]
ipmitool ################################################## [100%]
mstflint ################################################## [100%]
oracle-hmp-snmp ################################################## [100%]
oracle-hmp-tools ################################################## [100%]
oracle-hmp-tools-biosconfig############################################# [100%]
oracle-hmp-tools
ubiosconfig ################################################## [100%]
QConvergeConsoleCLI ################################################## [100%]
Preparing... ################################################## [100%]
package glibc-common-2.5-123.0.1.el6_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el6_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el6_11.1.i686 is already installed
package nscd-2.5-123.0.1.el6_11.1.x86_64 is already installed
Removing bm flash scripts...
Running post install script...
Running post patch script
Setting SET_IPOIB_CM=yes
file /etc/sysconfig/network-scripts/ifcfg-bondib0 not found
/usr/lib/init-exalogic-node/init-ipoib.sh not exist in /etc/rc.local , nothing to delete
Completed post patch script
Enabling services...
Updating dom0 memory to 16G..
Copying Exa* files...
Updating imageinfo...
Image name in imageinfo is already uptodate
finished; DAY-DD-MM-YYYY HR:MIN:SEC
finished; DAY-DD-MM-YYYY HR:MIN:SEC
To verify that the upgrade was successful, enter the following command:
# imageinfo
The output looks similar to the following:
Exalytics 2.2.0.1.0.ovs-3.3.3 (build:r20151215.1) Image version : 2.2.0.1.0.ovs-3.3.3 Image build version : 20151215.1 Creation timestamp : 2016-09-19_21-25-14 Kernel version : 3.8.13-68.3.3.el6uek.x86_64 Image activated : 2016-09-19_21-25-14 Image status : SUCCESS
To verify that Flash is installed and the number of Flash cards installed, enter the following command:
# ddcli
For an X2-4 or X3-4 configuration, six Flash cards are displayed. The output looks similar to the following:
**************************************************************************** LSI Corporation WarpDrive Management Utility Version 107.00.00.04 (2012.06.05) Copyright (c) 2011 LSI Corporation. All Rights Reserved. **************************************************************************** ID WarpDrive Package Version PCI Address -- --------- --------------- ----------- 1 ELP-4x100-4d-n 08.05.01.00 00:11:00:00 2 ELP-4x100-4d-n 08.05.01.00 00:21:00:00 3 ELP-4x100-4d-n 08.05.01.00 00:31:00:00 4 ELP-4x100-4d-n 08.05.01.00 00:a1:00:00 5 ELP-4x100-4d-n 08.05.01.00 00:c1:00:00 6 ELP-4x100-4d-n 08.05.01.00 00:d1:00:00 Select the WarpDrive [1-6 or 0:Quit]: 0
Note:
For an X4-4, X5-4, and X6-4 configuration, three Flash cards are displayed.
You install and configure Oracle VM Manager, as described in the following sections:
Oracle recommends that you install Oracle VM Manager on a separate machine than the Exalytics Machine, preferably colocated geographically within Oracle VM Server.
To install Oracle VM Manager 3.2.9:
Oracle recommends that you install Oracle VM Manager on a separate machine than the Exalytics machine, preferably colocated geographically within Oracle VM Server. OVM Manager 3.3.3 is supported with X6-4 and X5-4 servers due to NVMe hardware incompatibility in OVM Manager 3.2.9.
To install Oracle VM Manager 3.3.3:
Download the Oracle VM Manager from the following link:
https://edelivery.oracle.com/osdc/faces/SearchSoftware
In the Oracle Software Delivery Cloud home page, select the checkbox
Linux/OVM/VMs
Search by entering Oracle VM Manager 3.3.3 in the search box.
Select Releases in the drop down.
Click Continue. It will prompt to download
V77113-01.iso
Unzip the downloaded file. It should contain the installer ISO file.
Mount the ISO file to a directory as the root user with the following command:
#mkdir /OVMCD
#mount –o loop ovmm-3.3.3-installer-OracleLinux-b1085.iso /OVMCD
Run the Oracle VM Manager installer using the following commands:
#cd /OVMCD
#./ createOracle.sh
#./runInstaller.sh
Install Oracle VM Manager 3.3.3. For instructions, see "Installing Oracle VM Manager" in Oracle VM Installation and Upgrade Guide for Release 3.2. The guide is located at:
Adding Oracle VM Servers to your Oracle VM Manager environment is known as discovering Oracle VM Servers. Discovering servers is the first step to configuring the virtualization environment.
To discover Oracle VM Servers:
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, right-click Server Pools, and then select Discover Servers.
The Discover Dialog box is displayed.
Enter the following information for the server:
Oracle VM Agent Port. The default port number is 8899.
Oracle VM Agent Password. The default password is "oracle".
IP Address.
Click OK.
Oracle VM Server and its details, including number of processors, IP address, processor speed, RAM, networking ports and configuration are discovered and added to the Unassigned Servers folder.
For more information, see "Chapter 6, Managing Server Pools and Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
A Virtual Network Interface Controller (VNIC) is used by virtual machines as network cards. You create virtual network interfaces by defining a range of MAC addresses to use for each VNIC. Each MAC address corresponds with a single virtual Network Interface Controller (NIC), which is used by a virtual machine.
To create Virtual Network Interface Controllers:
For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
A server pool consists of at least one Oracle VM Server. If you find a server pool does not have sufficient resources, such as CPU or memory, to run the virtual machines, you can expand the server pool by adding more Oracle VM Servers.
Before creating a server pool, you must have:
An IP address for the server pool
An IP address for each virtual machine
The password to access the Oracle VM Agent installed on Oracle VM Server
For information on creating server pools and adding servers, see "Chapter 6, Managing Server Pools and Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
Note:
When creating a server pool, you must deselect the Activate Cluster option.
A repository stores Oracle VM resources, such as virtual machines, templates for creating virtual machines, virtual machine assemblies, and so on.
Note:
Oracle recommends that you create a repository on each physical disk available. Use the smaller repository to store Oracle VM templates and cloned virtual machines and the larger repository to store virtual drives that are assigned to the virtual machines.
You use Oracle VM Manager to create and configure Exalytics repositories, and to present the repositories to Oracle VM Servers.
To create an Exalytics repository:
Log on to Oracle VM Manager.
Select the Repositories tab.
In the toolbar, click Create New Repository to display the Create a Data Repository dialog.
Perform the following actions:
In the Repository Name field, enter the name for the repository.
For Repository Location, select Physical Disk and click Search.
From the drop-down list, select a local storage array and select the smaller of the two storage drives.
Click OK.
Select the server pool for the repository.
Click Next.
The new repository is available to be presented to Oracle VM Server. To enable your Oracle VM Server to use the repository, you must present the repository to Oracle VM Server.
Select and move Oracle VM Server from the Servers field to the Present to Server(s) field and click Finish.
The repository is listed in the Repository tab.
For more information, see "Chapter 4, Managing Storage" in Oracle VM User's Guide for Release 3.2.
You create a VM Network channel in Oracle VM Manager to enable Oracle VM Guests in the server pool to communicate with each other and also to communicate with external networks. The VM Network channel instructs Oracle VM Servers to create a Xen bridge that controls network traffic to and from Oracle VM Guests.
A Server Management Network channel that enables communication between Oracle VM Manager and Oracle VM Servers is automatically created by Oracle VM Manager. You can use this existing Server Management Network channel to communicate with virtual machines, or create a new network channel.
Note:
Oracle recommends that you create a new network channel for the virtual machines.
To create a VM Network Channel, follow the procedures described in one of the following topics:
Using the Existing Server Management Network Channel for Virtual Machines
For simple network deployments, you can use the default Server Management Network channel to communicate with virtual machines.
To use the Existing Server Management Network channel for Virtual Machines:
Log on to Oracle VM Manager.
Select the Networking tab.
Select the Server Management Network channel address.
Note:
The Server Management Network channel address is similar to the Gateway address you entered except the trailing digit at the end of the address is a zero. For example, if you entered 10.244.138.1 as the Gateway address, the Server Management Network channel address is displayed as 10.244.138.0.
Click the Edit icon.
The Edit Network screen in displayed.
To enable the virtual machine to connect the Server Management Network channel, select Virtual Machine.
Click Next.
Accept the default server settings, and click Next.
Accept the default port settings, and click Next.
Click Finish.
The Virtual Machine column against the Server Management Network channel address displays a check mark indicating that the virtual machine is connected to the network.
Creating a New Network Channel for Virtual Machines
Before you can create a new network channel you must connect additional Ethernet cable to the Gigabit Ethernet connector ports and create a new bonded port through the Oracle VM Manager user interface.
Note:
The following procedure describes how to create and use a bonded port for the network channel. If you need to, you can use a single ethernet port for the channel instead of a bond. Oracle recommends using a bonded port.
To create a new bonded port and network channel:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
To create a new bonded port, perform the following tasks:
In the left pane, expand Server Pools, and then select the Exalytics Machine on which the Oracle VM Server is running.
In the Perspective list, select Bond Ports.
Click Create Bond Port.
The Create Bond Port page is displayed.
In the Addressing list, select IP Address.
In the IP Address field, enter an IP address for the bond.
In the Mask field, enter a Netmask for the bond.
Leave the MTU field at the default number.
Enter a description for the bond.
In the Available Ports section, select the connected ports and move it to the Selected Ports section.
Click OK.
To create a new network channel, perform the following tasks:
Select the Networking tab.
Click Create New Network.
The Create Network page is displayed.
Select Create a network with bond/ports only, and click Next.
In the Name field, enter a name for the network.
Enter a description.
Select Virtual Machine, and then click Next.
In the Available Servers section, select the server on which the Oracle VM Manager is running, move it to the Selected Servers section, and then click Next.
In the Available Ports section, select the bonded port you created in Step 3, move it to the Selected Ports section, and then click Next.
The Ports page is displayed.
Confirm the settings on the Ports page and then click Finish.
For more information, see "Chapter 5, Managing Networks" in Oracle VM User's Guide for Release 3.2.
New customers must upgrade to Oracle Exalytics Release 2.1 (2.0.0.1.0) on the virtualized environment. For instructions, see Upgrading to Oracle Exalytics Release 2.1 (2.2.0.0.0.ovs-3.3.3) on Virtual Deployments
You use virtual templates to create virtual machines. The process of creating a virtual machine from a template is known as cloning. Before you create virtual machines, ensure that you have the following resources available:
A server pool
An Oracle VM Server
VM templates
The process of creating virtual machines from templates consists of the following steps:
To download VM templates:
Download and save the Exalytics Oracle Release 2 VM Template (2.2.0.0.0) for Exalytics Oracle VM x86-64, by performing the following steps:
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Business Intelligence.
In the Platform list, select Linux X86-64.
Click Go.
Select Oracle Exalytics Software Media Pack for Linux x86-64 Release: 2.0.0.0.
Click Continue.
To install VM template on a Linux 6 operating system, download the Oracle Exalytics Oracle VM Template 2.2.0.0.0.el6, Part Number:V76309-01.
Save the template on a web server.
After downloading the templates, you import them into Oracle VM Manager.
To import VM templates into Oracle VM Manager:
After importing the template in Oracle VM Manager, you use the template to create a virtual machine.
Note:
Oracle recommends that you use Oracle VM Manager to create virtual drives of the sizes required for your system on the larger repository. Associate these virtual drives with the virtual machines deployed on your system. These virtual drives provide enough storage for installing the Exalytics software and the various files associated with the Exalytics Machine.
Before you create virtual machines, keep the following guidelines in mind:
Ensure that Hyperthreading is disabled on Oracle VM Server and in order to disable the hyperthreading, update the vCPUs value to 10 in the grub.conf file.
Note:
Oracle recommends that Hyperthreading be disabled when creating new virtual machines.
Maximum number of virtual machines you can create for a non-InfiniBand configuration on an X2-4, X3-4, X4-4, X5-4, and X6-4 Exalytics Machine is ten.
Total virtual processors (vCPUs) you can assign on Oracle VM Server for an X2-4, X3-4, X4-4, X5-4, and X6-4 Exalytics Machine is ten.
Total memory you can allocate on Oracle VM Server for an X2-4, X3-4, X4-4, X5-4, and X6-4 Exalytics Machine is 16 GB.
Review Table 5-1 for the total vCPUs and memory you can allocate on all virtual machines and the maximum vCPUs and memory you can allocate to each virtual machine.
Table 5-1 Total and Maximum vCPUs and Memory Allowed For Virtual Machines
| System | Total vCPUs for all Virtual Machines | Maximum vCPUs for each Virtual Machine | Total RAM for all Virtual Machines | Maximum RAM for each Virtual Machine |
|---|---|---|---|---|
|
X2-4 |
40 |
28 |
984 GB |
800 GB |
|
X3-4 |
40 |
28 |
984 GB |
800 GB |
|
X4-4 |
60 |
28 |
1984 GB |
800 GB |
|
X5-4 |
72 |
28 |
1984 GB |
800 GB |
|
X6-4 |
72 |
28 |
1984 GB |
800 GB |
Note:
For the X2-4 and X3-4 Exalytics Machine, total memory on Oracle VM Server (16 GB) and all virtual machines (984 GB) cannot exceed 1000 GB. For the X4-4, X5-4, and X6-4 Exalytics Machine, total memory on Oracle VM Server (16 GB) and all virtual machines (1984 GB) cannot exceed 2000 GB.
To create virtual machines from a VM template:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane toolbar, click Create Virtual Machine.
The Create Virtual Machine dialog is displayed.
Select Clone from an existing VM Template.
Perform the following actions:
In the Clone Count list, select the number of machines you want to clone.
In the Repository list, select a repository for the machine.
In the VM Template list, select the VM template from which you want to create the virtual machine.
Enter a name for the virtual machine.
In the Server Pool list, select a server pool.
Enter a description for the virtual machine.
Click Finish.
The virtual machine is created and is ready to be configured.
To configure and start a virtual machine, configure a network on a virtual machine, and configure SWAP on a virtual machine, see Maintaining Virtual Machines.
For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.