Showing posts with label Oracle VM Manager. Show all posts
Showing posts with label Oracle VM Manager. Show all posts

Monday, March 2, 2020

How To Access Guest Console In OVM 3 Using VNC Without Using OVM Manager


Earlier releases of OVM (2.x) documented manual configuration to enable access to virtual machine consoles through VNC without using the OVM 2.x manager:

E.3 Guest Console Access
However, such configuration is not possible with Oracle VM 3.


With OVM3 this is achieved by redirecting the remote port to a local port using the ssh(1) command.
To do this, first find the id of the vm (this can be done in the Manager UI by expanding the entry for the vm, or using the "list vm" command in the CLI).

Then on the OVM Server ("ovs", aka "dom0") the vm is running on, issue the xm list command to find its ID, e.g.:
# xm list

Name                             ID Mem VCPUs State  Time(s)
0004fb00000600005454e1ab286913be 2  4096    2 -b---- 424.6
Domain-0                         0  840     8 r----- 478278.2

In this example the ID is 2.

Then find the port the vm console is listening on:
# xm list -l 2 | grep 59
(uuid 3c787270-abad-9595-8258-d27f03fd928d)
(location 127.0.0.1:5900)

In this example the vnc port for the vm is 5900.

On the system where you wish to display the console, open an ssh session to the ovm server and redirect the port to it, e.g.:
$ ssh -L 12345:localhost:5900 root@olvm-ovs00009

The "5900" port on the ovs will be redirected to port "12345" of your local desktop.

Leave this session open for the duration of the vnc session.

Then vncviewer can be used to open the vm console, e.g. from another terminal issue:
$ vncviewer localhost:12345

 On a Windows system, you can use some other SSH client, e.g. PuTTY for the re-direct.


at No comments:
Labels: ,

How To Regenerate The Oracle VM Manager 3.3.x/3.4.x DB



To regenerate the Oracle VM database you'll need to have access to the /u01/app/oracle/ovm-manager-3/.configfile.  This file has the parameters of your database that will be used for the regeneration. 

For Oracle VM 3.4. x release, please consider restoring a valid backup before regenerating the database.

The process for Regenerating your database should be:
  1.      Stop the ovm services
  2.      Delete the Manager Data Base   The ovm_upgrade.sh command is used to delete the current Oracle VM database.
  3.      Generate new certificates.
  4.      Start the services
  5.      Restart the ovm service for the certificate to be applied
  6.      Repopulate the DB by discovering and refreshing the repositories
  7.      To restore the simple names  Use KM article: Restore OVM Manager "Simple Names" After a Rebuild/Reinstall (Doc ID 2129616.1)
Note: Anything in <> should be replaced with the value appropriate to your environment or filename.
1. The Oracle VM manager services need to be shutdown, to delete the OVM manager database.
#service ovmm stop

2. Delete the current OVM database.  

(Use the dbuser and password, not the ovm admin user/passowrd.)
Using ovm_upgrade.sh from /u01/app/oracle/ovm-manager-3/ovm_upgrade/binand the values from the /u01/app/oracle/ovm-manager-3/.configfile, delete the bad database
Command syntax:
# sh ovm_upgrade.sh --deletedb --dbuser=<user> --dbpass=<password> --dbhost=localhost --dbport=<database-port> --dbsid=<your sid>

Obtain the values to substitute from the /u01/app/oracle/ovm-manager-3/.config on a management node:
# cat /u01/app/oracle/ovm-manager-3/.config
DBTYPE=MySQL
DBHOST=localhost
SID=ovs             < --dbsid
LSNR=1521           < --dbport
OVSSCHEMA=ovs       < --dbuser
APEX=8080
WLSADMIN=weblogic
OVSADMIN=admin
COREPORT=54321
UUID=0004fb00000100009bfa6a96c1303e32
BUILDID=3.2.11.775
default "--dbpass" is "Welcome1" - use appropriate value for your system.
 Sample delete command based on the above sample .config file: 
#sh /u01/app/oracle/ovm-manager-3/ovm_upgrade/bin/ovm_upgrade.sh --deletedb --dbuser=ovs --dbpass=Welcome1
--dbhost=localhost --dbport=1521 --dbsid=ovs 

  3. Start the OVM services and Generate  the replacement certificate

#service ovmm start
#export MW_HOME=/u01/app/oracle/Middleware
#/u01/app/oracle/ovm-manager-3/ovm_upgrade/bin/ovmkeytool.sh setupWebLogic

4. Activate the new certificate.


#sh /u01/app/oracle/ovm-manager-3/bin/configure_client_cert_login.sh

Stop then start the OVM service apply the new certificate.

#service ovmm stop
#service ovmm start

5. Repopulate the database

1) Login, the UI should be EMPTY of  any data. The OVM servers and VMs are still up and running, the poolFS and repos already exist

 2) Repopulate the database by Rediscovering the environment using the Oracle OVM Manager UI.
The OVM database is rebuilt from the existing servers in the pool, so the relationships will already be established.  The Servers and VMs are up and running, the pool filesystem the storage repositories are on the servers.
a. Discover Server(s) -> Pool/OVM Server(s) will be visible again
        If your storage is network based, validate that your servers are listed under the storage tab.
        If not "Discover server" and enter the name and IP of the storage array.

 b. Refresh Repository (right click each storage, and choose refresh

 c. Rediscover Server(s) -> VM's will reappear under the OVM Server(s). Non running VM's can be found under "Unassigned Virtual Machines"
Note: NFS  and iSCSI repositories need to be re-discovered independently after "re-discover Oracle VM Servers" and "refresh-all on Server Pools",
because occasionally NFS repositories can not be re-discovered, and the regeneration does not recover iSCSI storage.

d. if one need more VNICS, Run VNIC Manager to recreate a range of MAC addresses, because only the MAC addresses in use will have been rediscovered

 6.  Restore the simple names
This Database will be populated, but you will be missing items such as friendly disk names, display names for Vdisk, Vnics etc. (meta data)

 Please refer to KM article: Restore OVM Manager "Simple Names" After a Rebuild/Reinstall (Doc ID 2129616.1)   to restore the friendly names. 

 After the friendly names have been restored,  
Logout, and close the browser.
Open a browser, and login.

 The data base should be up and working with the friendly names (meta data) 


at No comments:
Labels: ,

Configure Secure TCP for Oracle VM Manager




The configuration of the TCPS service requires a certain amount of understanding about keystores and certificates. It is similar to the HTTPS configuration of Weblogic, so if you are involved in setting up overall Oracle VM security, this will be straightforward.

It's preferred to use the bundled scripts to create keystore and enable TCPS service for Oracle VM Manager.

Using Bundled Scripts
When you perform a fresh install of Oracle VM Manager 3.1.1, 3.2.x or 3.3.x, scripts are provided under /u01/app/oracle/ovm-manager-3/bin of the Oracle VM Manager server
·         secureOvmmTcpGenKeyStore.sh: create the keystore
·         secureOvmmTcp.sh: use the generated keystore to enable the TCPS service for Oracle VM Manager

For Oracle VM Manager 3.2.x and 3.3.x, the scripts are included as part of the default installation.
For detailed instructions how to use the scripts, please refer to the documentation:
After you follow the instructions to create keystore and enable TCPS service for Oracle VM Manager. Once Oracle VM Manager is restarted, you can verify the status to confirm that Oracle VM Manager is now listening for TCPS requests on port 54322 by default.

# netstat -a | grep  54322
tcp       0     0*:54322                    *:*                         LISTEN
Additional Resources
For more information, see the following links:



at No comments:
Labels: ,

How to Create Virtual Disk without Oracle VM Manager




In some situations, it may be necessary to know how to create a Virtual Disk on OVM 2.2 without using OVM Manager, and attach it to a Virtual Machine.

This can be done in OVM 2.2 via the following process:

1. Log into the Oracle VM server where the VM is running.

2. Change the directory at which the repository is mounted, e.g.:
# cd /to/path/to/repo

3. Create the raw format .img disk image, e.g. initiating 4 GB Virtual Disk:
# dd if=/dev/zero of=newdisk.img bs=1M count=4096

4. Then add new disk image to disk = [ ] section of vm.cfg file of a Virtual Machine. Format:
disk = [ 'file:/mnt/el4u5_64_hvm//system.img,hda,w' ]

Note: Making any change to vm.cfg file effective requires a domain re-creation which is Virtual Machine shutdown then start (NOT restart.)

5. If an outage on the Virtual Machine is not possible, then hot plug read/write as /dev/xvdX by:
# xm block-attach [domain ID] /path/to/image /dev/xvdX w


at No comments:
Labels: , ,

To increase Virtual Machine Memory in the OVM Manager GUI ?




To increase Virtual Machine Memory in the OVM Manager GUI, Please follow the following steps 


1. Using Oracle VM Manager GUI:

2. Login to Oracle VM Manager (GUI).

3. Select the VM and click on edit.

4. Check the assigned "Max. Memory (MB):" and "Memory (MB):".

5. If the "Max. Memory (MB):" is the same as "Memory (MB):", then you have to shut down the VM to increase the "Max. Memory (MB):" and "Memory (MB):".

6. If the "Max. Memory (MB):" is higher than the "Memory (MB):", then you can increase the "Memory (MB):" till "Max. Memory (MB):".

7. Ensure the "Memory (MB):" should not be higher than "Max. Memory (MB):"

8. Click on Save.

Login to the VM and verify allocated memory. 

Memory allocated to the VM can be check by Oracle VM Manager either by going to the Server and 
VM tab or by going to Health tab in GUI  then selecting Server and VM statistics. 

at No comments:
Labels: ,

Friday, June 28, 2019

Installing Oracle VM Manager


It takes approximately 8-15 minutes to complete the installation of Oracle VM Manager, depending on the performance of the Oracle VM Manager host, and the installation type you choose.
Before you begin the installation, download the Oracle VM Manager software from:
http://edelivery.oracle.com/oraclevm
This section describes the Oracle VM Manager installation process.
Note
If you want to install Oracle VM Manager in a virtualized environment, do not install it on Oracle VM Server (dom0) directly; install it into a virtual machine running on an Oracle VM Server.

Mounting the Oracle VM Manager Installation Media
Before you can run the Oracle VM Manager installer, you must mount the installation media. You can either burn the installation media to a CD and mount the CD, or mount the ISO file directly from the hard drive. Which ever way you choose to mount the installation media, you should perform this as the root user on the computer on which you want to install Oracle VM Manager.
  • To install Oracle VM Manager from a CD, burn the Oracle VM Manager ISO file to a CD. Insert and mount the Oracle VM Manager CD using the following commands:
·         # mkdir mount-point
# mount /dev/cdrom mount-point
Where mount-pointrefers to the directory on which you mount the ISO file.
  • To install Oracle VM Manager from a hard drive, locate the folder that contains the ISO file. Mount the ISO file to an existing directory using the following commands:
·         # mkdir mount-point
# mount -o loop OracleVM-Manager-version.iso mount-point
Where mount-pointrefers to the directory on which you mount the ISO file. For example:
# mkdir /OVMCD
# mount -o loop OracleVM-Manager-3.x.x.iso /OVMCD
You can find all the mounted files under the directory /OVMCD.
Note
The location of the mounted Oracle VM Manager ISO file should be accessible by the oracle user.

Running the Oracle VM Manager Installer
To install Oracle VM Manager, enter the mount point you created in above step for example, /OVMCD and start the installation with the runInstaller script as the root user:
# cd /OVMCD
# ./runInstaller.sh
A set of installer options are displayed:
Please select an installation type:
   1: Simple (includes database if necessary)
   2: Custom (using existing Oracle database)
   3: Uninstall
   4: Help
At the command prompt, enter 1 to perform a Simple installation or 2 to perform a Custom installation. If you already have Oracle VM Manager installed and want to uninstall it, select 3 to Uninstall.

Simple Installation (includes database if necessary)
The Simple installation option should be used if you do not have an existing Oracle Database installed or if you would like to keep Oracle VM Manager running independently of any existing Oracle Database.
The Simple installation option installs MySQL Enterprise Edition, MySQL Enterprise Edition Backup, Oracle WebLogic Server, Oracle Application Development Framework (ADF), Java, and Oracle VM Manager on the local system. The following example shows the Simple installation process.
Note
If you have an existing MySQL installation on the system where you intend to install Oracle VM Manager you should backup your databases and uninstall it. Oracle VM Manager requires exclusive use of MySQL due to the specific tuning parameters that it applies to the configuration. Oracle VM Manager uses MySQL Enterprise Edition on a non-standard port. The licensing of the MySQL Enterprise Edition provided with Oracle VM Manager grants exclusive use to Oracle VM. You must not use the MySQL server provided for any other purpose. If MySQL is installed as a result of a previous installation of Oracle VM Manager the installation prompts you to provide the hostname, root password and port number that was used in the previous installation.
Example 4.1. Simple Installation
# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer

Oracle VM Manager Installer log file:
  /tmp/filename.log

Please select an installation type:
1: Simple (includes database if necessary)
2: Custom (using existing Oracle database)
3: Uninstall
4: Help

   Select Number (1-4): 1
The installation process starts, and the following is displayed:
Starting production with local database installation ...

Verifying installation prerequisites ...

One password is used for all users created and used during the installation.
Enter a password for all logins used during the installation:
Enter a password for all logins used during the installation (confirm):
Enter a system-wide password that can be used when creating accounts for all of the components within the Oracle VM Manager installation. This password will be used for your MySQL install, WebLogic and Oracle VM Manager itself. You will need to confirm your password after you have entered it.
Verifying configuration ...
Warnings may occur if not all recommendations are met.
The installer provides a final option to continue or to abort the installation process. Enter 1 to continue. Progress of the installation is output on your screen step by step, as shown below:
Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database Software...
Installing Database Software...
Retrieving MySQL Database 5.5 ...
Unzipping MySQL RPM File ...
Installing MySQL 5.5 RPM package ...
Configuring MySQL Database 5.5 ....

Step 2 of 9 : Java ...
Installing Java ...

Step 3 of 9 : Database schema ...
Creating database 'ovs' ...
Creating user 'ovs' for database 'ovs'...

Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...
Installing Oracle ADF Patch...

Step 6 of 9 : Oracle VM  ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Granting ovm-admin role to user 'admin' ...
Set Log Rotation ...
Disabling HTTP and enabling HTTPS...
Configuring Https Identity and Trust...

Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...

Retrieving Oracle VM Manager CLI tool ...
Extracting Oracle VM Manager CLI tool...
Installing Oracle VM Manager CLI tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Shutting down Oracle VM Manager instance ...
Restarting Oracle VM Manager instance ...
Waiting for the application to initialize ...
Oracle VM Manager is running ...
Oracle VM Manager installed.

Please wait while WebLogic configures the applications... This can take up to 5 minutes.
When the installation is complete a summary similar to the following is displayed:
Installation Summary
--------------------
Database configuration:
  Database type               : MySQL
  Database host name          : localhost
  Database name               : ovs
  Database listener port      : 49500
  Oracle VM Manager schema    : ovs

Weblogic Server configuration:
  Administration username     : weblogic

Oracle VM Manager configuration:
  Username                    : admin
  Core management port        : 54321
  UUID                        : 0004fb00000100008e2c477634f634c9


Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM Manager,
Database, and Oracle WebLogic Server have been set by you during this installation. In
the case of a default install, all passwords are the same.

Oracle VM Manager UI:
  https:/hostname:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual
machine's console.

For more information about Oracle Virtualization, please visit:
  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important
Make sure you delete the temporary configuration file created during the installation:
/tmp/ovm_configid
This file is useful for debugging installation issues, but does contain some sensitive information that may present a security issue if left in place.
Warning
Some performance degradation may be noted when installing onto an Oracle Linux system using an EXT4 formatted filesystem. This is the result of the default mount parameters for EXT4 on an Oracle Linux installation. In order to ensure that your installation performs optimally, the /etc/fstab must be edited to provide alternate mount options for the mount point where Oracle VM Manager is installed. Mount options for an EXT4 filesystem should be specified as: rw,noatime,data=writeback,barrier=0,nobh.

Custom Installation (using existing Oracle database)
The Custominstallation option allows you to use an existing local or remote Oracle Database as the Oracle VM Manager database repository. During the Custominstallation process, you need to set the users and passwords to use in order to connect to the database, the SID that should be used within the Oracle Database to load the Oracle VM Manager schema, the username and password to be used for the Oracle WebLogic Server, and the password for the admin user account in Oracle VM Manager. The following example shows the Custominstallation process.
Example 4.2. Custom Installation
# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer

Oracle VM Manager Installer log file:
  /tmp/ovm-manager-3-install-date-id.log


Please select an installation type:
1: Simple (includes database)
2: Custom (using existing Oracle database)
3: Uninstall
4: Help


   Select Number (1-4): 2
The installation process starts, and the following is displayed:
Starting production installation ...

Verifying installation prerequisites ...

Oracle Database Repository
==========================
Use an existing Oracle database 
When prompted, enter the following information
Enter the Oracle Database hostname [localhost]:
Enter the Oracle Database System ID (SID) [ORCL]:
Enter the Oracle Database SYSTEM password:
Enter the Oracle Database listener port [1521]: 
Enter the Oracle VM Manager database schema [ovs]:
Enter the Oracle VM Manager database schema password:
Enter the Oracle VM Manager database schema password (confirm):

Oracle Weblogic Server 11g
==========================
Enter the Oracle WebLogic Server 11g user [weblogic]:
Enter the Oracle WebLogic Server 11g user password:
Enter the Oracle WebLogic Server 11g user password (confirm):

Oracle VM Manager application
=============================
Enter the username for the Oracle VM Manager administration user [admin]:
Enter the admin user password:
Enter the admin user password (confirm):

Verifying configuration ...

Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1
You have the option to continue or abort the installation. Enter 1 to continue. You may be prompted again to either abort or continue the installation in case certain components are already present on your system. Progress of the installation is output on your screen step by step, as shown below:
Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database ...
Installing Database ...
Database installation skipped ...

Step 2 of 9 : Java ...
Installing Java ...
If an existing Oracle VM Manager database schema is found in the database, the following is displayed:
Step 3 of 9 : Database Schema ...
An existing OVM database was found.  How should the install proceed?
   1: Use the existing OVM database
   2: Remove the existing OVM database and create a new OVM database
   3: Abort

   Select Number (1-3): 1
Enter 1 - 3, depending on your requirements. In this example, the existing schema is retained.
Alternatively, if no existing Oracle VM Manager database schema is found in the database, the schema is created.
Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...

Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...

Step 6 of 9 : Oracle VM  ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Granting ovm-admin role to user 'admin' ...
Set Log Rotation ...
Disabling HTTP and enabling HTTPS...
Configuring Https Identity and Trust...

Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Shutting down Oracle VM Manager instance ...
Restarting Oracle VM Manager instance ...
Waiting 15 seconds for the application to initialize ...
Oracle VM Manager is running ...
Oracle VM Manager installed.

Please wait while WebLogic configures the applications... This can take up to 5 minutes.
When the installation is complete a summary similar to the following is displayed:
Installation Summary
--------------------
Database configuration:
  Database host name          : localhost
  Database instance name (SID): MYDB
  Database listener port      : 1521
  Application Express port    : 8080
  Oracle VM Manager schema    : ovs

Weblogic Server configuration:
  Administration username     : weblogic

Oracle VM Manager configuration:
  Username                    : admin
  Core management port        : 54321
  UUID                        : 0004fb0000010000cc1b57e39ff77ea9

Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM
Manager, Database, and Oracle WebLogic Server have been set by you
during this installation. In the case of a demo install, all passwords are the
same.

Oracle VM Manager UI:
  https://myserver.example.com:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual
machine's console.

For more information about Oracle Virtualization, please visit:
  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important
Make sure you delete the temporary configuration file created during the installation:
/tmp/ovm_configid

Performing a Silent Install
The Oracle VM Manager installer can be installed silently, without any intervention. An installation configuration script can be used to provide the installation options, and a set of command line options are available for the installation parameters. The configuration script is written in YAML. Structure is shown through indentation (one or more spaces). Sequence items are denoted by a dash, and key value pairs within a map are separated by a colon. Structure is shown through indentation (one or more spaces) and key value pairs within a map are separated by a colon.
The following example silently performs a Custom install.
Warning
Always provide the absolute path to the configuration file. The installer cannot process a relative path and will simply terminate the installation process.
Example 4.3. Silent install using configuration file
The command to run the silent production installation using a configuration file is:
./runInstaller.sh --config=/path/config.yml --installtype=Custom --assumeyes
The configuration file used in this installation example (config.yml) installs a local MySQL database. Replace the password entry with your own password.
db:
      install       : Yes
      host          : localhost
      sys_password  : password
      port          : 49500
      sid           : ovs
      mgmt_port     : 8080
      user          : ovs
      password      : password

webLogic:
      install       : Yes
      user          : weblogic
      password      : password

java:
      install       : Yes

ADF:
      install       : Yes

OVMCore:
      install        : Yes
      user           : admin
      password       : password

OVMConsole:
      install       : Yes

OVMShell:
      install       : Yes

onFailure:
      cleanup       : No

OVMUpgrade:
      install       : Yes

Configuring the NTP Service
When an Oracle VM Server is discovered in Oracle VM Manager, NTP (Network Time Protocol) is automatically configured and enabled to ensure time synchronization. Oracle VM automatically configures the Oracle VM Manager host computer as the NTP source for all Oracle VM Servers under its control, unless other NTP servers are configured in the user interface or CLI.
If you do not set up your own list of NTP servers, and want to use the Oracle VM Manager host computer to provide NTP time synchronization services, NTP must first be installed and configured on the Oracle VM Manager host server. Make sure that your Oracle VM Manager host is either registered with the Unbreakable Linux Network (ULN) or configured to use Oracle's public YUM service.
To configure NTP on the Oracle VM Manager host:
  1. Install the NTP package.
# yum install ntp
When NTP is installed, configure it to both synchronize with upstream servers and provide time services to the local network, where the Oracle VM Servers reside.
  1. Enable upstream synchronization by defining the upstream time servers in the ntp.conf file.
Oracle Linux uses three public NTP servers as upstream time sources by default. Check with your network administrator if time services are provided on the corporate network and, if necessary, replace the default entries with the names or IP addresses of your NTP servers.
Use your favorite text editor to modify /etc/ntp.conf. Search for these entries:
# vi /etc/ntp.conf

server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
  1. Configure downstream access for the Oracle VM Servers in your local network. To do so, disable the default "noquery" option for the Oracle VM Server management network.
Again in the /etc/ntp.conffile, search for this entry:
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
Remove the # character at the start of the line to uncomment this entry. Replace 192.168.1.0 with the network address of your Oracle VM Server management network. You may also need to adjust the netmask (255.255.255.0). Once you have finished editing, save the /etc/ntp.conffile.
  1. Start the NTP service and set it to launch automatically upon boot.
5.  # service ntpd start
# chkconfig ntpd on
  1. When NTP is running, check upstream synchronization. The ntpq command should output something similar to this example:
7.  # ntpq -p
8.   
9.       remote           refid      st t when poll reach   delay   offset  jitter
10.==============================================================================
11.lists2.luv.asn. 203.161.12.165  16 u   25   64    3    3.495   -3043.1   0.678
12.ns2.novatelbg.n 130.95.179.80   16 u   27   64    3   26.633   -3016.1   0.797
 sp1.mycdn.fr    130.234.255.83  16 u   24   64    3    4.314   -3036.3   1.039
  1. Test downstream synchronization from another server in the management network to ensure that NTP services are working. Note that it may take several minutes before your NTP server is able to provide time services to downstream clients. Begin by checking the stratum level of your server:
14.# ntpq -c rv
15. 
16.assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
17.version="ntpd 4.2.4p8@1.1612-o Tue Jul  6 21:50:26 UTC 2010 (1)",
18.processor="x86_64", system="Linux/2.6.32-200.19.1.el6uek.x86_64",
19.leap=11,  stratum=16 , precision=-20, rootdelay=0.000,
20.rootdispersion=1.020, peer=0, refid=INIT,
21.reftime=00000000.00000000  Thu, Feb  7 2036 17:28:16.000, poll=6,
22.clock=d21d4a96.a26c5962  Fri, Sep 16 2011 14:09:58.634, state=0,
23.offset=0.000, frequency=0.000, jitter=0.001, noise=0.001,
stability=0.000, tai=0  
If the server is showing stratum=16, wait a few minutes and try again. It may take up to 15 minutes for an NTP server to stabilize sufficiently to lower its stratum level.
Downstream clients will not synchronize with a server at stratum level 16. Once the stratum level has dropped, log in to an available Linux host in your management network, not running Oracle VM Manager, and issue the following command:
# ntpdate -d manager.hostname
[...]
16 Sep 13:58:25 ntpdate[1603]: step time server 192.168.1.1 offset 3.009257 sec
This command runs ntpdate in debug mode, in which case the availability of the remote time server is checked. If the debug run ends in a line similar to the one in this example, the test is successful. In case the stratum level is still too high, the error message "Server dropped: strata too high" is displayed.
When you have confirmed with these tests that NTP is working properly for your environment, you should not need to check this again.
Caution
NTP communicates over UDP port 123. Ensure that no firewall is blocking this traffic.

Installing and Configuring Virtual Machine Console Utilities
There are two types of virtual machine consoles in Oracle VM Manager: the VNC console used to connect virtual machines in x86-based server pools, and the serial console used to connect to virtual machines in both x86-based and SPARC-based server pools. This section discusses installing the prerequisite software and any configuration required to use both console types.

Oracle VM Server VNC Console for x86
Oracle VM Manager uses a secure tunnel to protect the virtual machine console (remote connection utility) data across the network. Oracle VM Manager does not communicate directly with the VNC client, but rather connects via an SSH-encrypted tunnel on port 69xx (where xx is based on the guest to which it is connecting).
Any firewall between the client and Oracle VM Manager needs port 15901 to be open. Any firewall between the Oracle VM Manager and the Oracle VM Servers needs ports 6900 and above open; one port for each virtual machine on an Oracle VM Server. For example, if you have 100 virtual machines on an Oracle VM Server, you should open ports 6900-6999 (100 ports) on any firewall between the Oracle VM Server and Oracle VM Manager.
To connect to a virtual machine's VNC console in Oracle VM Manager, you should have a VNC viewer installed somewhere in your environment, either:
  • On the Oracle VM Manager host computer
  • On the client computer
  • On both the Oracle VM Manager host computer and the client computer
The virtual machine VNC console feature uses the client instance of a VNC viewer, if one exists, to connect to a virtual machine's console. If a VNC viewer is not found on the client computer, a request is sent to the Oracle VM Manager host computer to display the VNC viewer.
It is preferred that you install TightVNC on the Oracle VM Manager host computer. You can get the latest TightVNC package from:
http://oss.oracle.com/oraclevm/manager/RPMS/
Install TightVNC with the command:
# rpm -ivh tightvnc-java-version.noarch.rpm
Packages are also available at Oracle's public YUM repository:
On the client computer you use to connect to Oracle VM Manager it is recommended that you install RealVNC. Oracle recommends RealVNC on the client computer as it renders quickly, has better keyboard support, and has less mouse control issues compared to other VNC clients. The RAS proxy applet used to view the screen or console of a virtual machine looks for RealVNC by default. If you have multiple VNC viewers on your client computer, you can configure which one is used from the virtual machine console in Oracle VM Manager. See Connecting to a Virtual Machine for more information on using and configuring the VNC client.
If you are using a Linux-based operating system on your client computer, you can also install TightVNC as above on your client computer and it is automatically discovered when you connect to a virtual machine using the console feature in Oracle VM Manager.
Oracle VM Server Serial Console for x86 and SPARC
You cannot use the standard VNC console to connect to virtual machines on a SPARC-based server pool. Instead, use the serial console. The serial console can also be used to connect to virtual machines running on x86-based server pools. The serial console behaves differently to the VNC-based x86 console, and the console must be displayed using the Java Telnet Application (JTA2) package installed on the Oracle VM Manager host computer. You can get the latest JTA2 package from:
http://oss.oracle.com/oraclevm/manager/RPMS/
Install JTA2 with the command:
# rpm -ivh jta-version.noarch.rpm
Packages are also available at Oracle's public yum server:
See Connecting to a Virtual Machine for more information on using the serial console to connect to virtual machines in SPARC-based server pools.
Installation Logs
If any errors occur during installation, check the Oracle VM Manager installation log file:
/tmp/ovmm-installer.selfextract_id/ovm-manager-3-install-date.log
When the installation is complete, the installation log is copied to:
/tmp/ovm-manager-3-install-date.log
Installation Directories
The locations of the Oracle VM Manager components are listed below.

Component
Location
MySQL
/u01/app/oracle/mysql/data
MySQL Enterprise Backup
/opt/mysql/meb-3.8/
Backups stored in: /u01/app/oracle/mysql/dbbackup
Java
/u01/app/oracle/java
Oracle WebLogic Server 11g
/u01/app/oracle/Middleware/
Oracle ADF
/u01/app/oracle/Middleware/
Oracle VM Manager application
/u01/app/oracle/ovm-manager-3/
Oracle WebLogic Server domain
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain 


at No comments:
Labels: ,
Subscribe to: Posts (Atom)

Question 8 Explanation

Compartments are the primary building blocks you use to organize your cloud resources. You use compartments to organize and isolate your res...