For this configuration, your Exalogic hardware is pre-installed with Oracle Enterprise Manager Ops Center to manage your hardware components. Oracle Enterprise Manager Cloud Control provides many of the monitoring features used by system administrators.
The steps below provide the prerequisites and instructions to discover an Exalogic target in Enterprise Manager Cloud Control:
Installing Management Agent for Oracle VM Manager and Ops Center
Once you have completed the discovery of your Exalogic Machine in Enterprise Manager, follow the steps outlined in Post-Discovery Configuration and Verification.
Before proceeding with discovery, you must verify that your Exalogic hardware meets the following minimal software requirements:
Oracle Exalogic Elastic Cloud Software (EECS): version 2.0.6.0.0 or later.
For Exalogic Machine in the virtual configuration (installed with EECS version 2.0.6.0.0), Oracle Enterprise Manager Ops Center is pre-installed. If Ops Center is not installed already on your Exalogic Machine, then submit a service request to Oracle Support.
For the Management Agents installed in the Installing Management Agent for Oracle VM Manager and Ops Center section, support is provided for Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3.0) or later and Enterprise Manager Cloud Control 13c Release 1 (13.1.0.1.0) and Release 2 (13.2.1.0) or later. Verify that the instance of Cloud Control you choose for monitoring is at 12.1.0.3.0 or later.
Note:
The Exalogic Infrastructure plug-in is not required for discovery of a Virtual Exalogic system.
Note:
Exalogic configurations supporting virtualization must each have Oracle Virtual Machine (VM) Manager properly configured for read-only access by Enterprise Manager Cloud Control as a mandatory requirement as described in the following procedure. Failure to configure the Oracle VM Manager for read-only access by Enterprise Manager Cloud Control will result in an unsupported configuration. Operations performed in this unsupported configuration may result in software outages and necessitate the re-installation of the Exalogic Control software.
If the Oracle VM Manager Has NOT Been Discovered
If you have not yet performed discovery of the Oracle VM Manager in Cloud Control, then skip this section and proceed to Installing Management Agent for Oracle VM Manager and Ops Center and install the Management Agent for Oracle VM Manager and the Management Agent for Exalogic Hardware.
If the Oracle VM Manager HAS Been Discovered
This section only applies if you have an Enterprise Manager instance and have already discovered the Oracle VM Manager within the Exalogic Control stack VM. You must perform the following steps as a prerequisite in order to discover the Oracle VM Manager in read-only configuration.
As part of the original discovery of the Oracle VM Manager, the Management Agent for Oracle VM Manager is already installed. Once you have completed the steps outlined below, proceed to the Discovering Targets section.
Note:
If Oracle VM Manager was registered with Enterprise Manager Cloud Control prior to performing the read-only configuration procedure below, then you must perform Synchronize Operation from the Oracle VM Manager Target menu in Enterprise Manager to re-register it in read-only mode. Confirm that the Oracle VM Manager target is in read-only configuration.
The Oracle VM Manager is part of the Exalogic Control Stack configured as part of the Exalogic installation process. If you have used an instance of Enterprise Manager to discover this target within the Exalogic Control Stack, then this process needs to take place to avoid an unsupported configuration.
You can validate the configuration following these steps by observing that several menus for the manager/pool/server/guest vm target are disabled. Specifically, you can validate that Oracle VM Manager is in read-only mode by right-clicking the registered Oracle VM manager under Infrastructure Cloud.
All the active operation menu items in the second and third tier of the list, such as Create Zone, Create Virtual Server Pool, and Manage Network, are disabled (grayed out) and are not available for selection. Conversely, if you choose an item from the pull-down menus that are displayed when you click either the VM Manager or VM Guest menu option, the same menu items may not be grayed out. However, if you select one of the active management options, Enterprise Manager displays an error message stating that the action cannot be performed, thus indicating that the Oracle VM Manager is in read-only mode.
The Management Agent is necessary to establish a connection between Enterprise Manager and Oracle VM Manager and Ops Center. This connection will allow you to manage your Exalogic Machine through Enterprise Manager Cloud Control. Install the Management Agent before proceeding to the discovery process:
Follow the steps below to install the Management Agent:
Ensure that you have downloaded and applied the latest version of Oracle Enterprise Manager Agent software for Oracle Linux 64-bit platforms.
In Enterprise Manager Cloud Control, do one of the following:
From the Setup menu, select Add Target, then select Auto Discovery Results. On the Auto Discovery Results page, click the Host and Oracle VM Manager tab and select a host that you want to monitor from the displayed list. Click Promote.
From the Setup menu, select Add Target, then select Add Targets Manually. On the Add Targets Manually page, select Add Host Targets and click Add Host.
On the Host and Platform page, do the following:
Accept the default name assigned for this session or enter a unique name of your choice. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name. For example, add_host_operation_1
.
A unique deployment activity name enables you to save the installation details specified in this deployment session and reuse them in the future without having to enter all the details all over again in the new session.
Click Add to enter the fully qualified name and select the platform of the host on which you want to install the Management Agent.
Note:
The host should be the VM where both Ops Center and Oracle VM Manager are installed.
The platform should be Oracle Linux 5 or later. At this time, Solaris is not supported.
Click Next.
At this point, the Management Agent is to be installed, which is a separate process. For details about installing the agent, see the "Installing Oracle Management Agent" chapter of the Oracle® Enterprise Manager Cloud Control Basic Installation Guide:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/install_agent.htm
To configure the agent for an Exalogic machine, follow the steps below on the Installation Details page:
In the Deployment Type section, select Fresh Agent Install.
From the table, select the first row that indicates the hosts grouped by their common platform name.
In the Installation Details section, provide the installation details common to the hosts selected in Step b. For Installation Base Directory, enter the absolute path to the agent base directory where you want the software binaries, security files, and inventory files of the Management Agent to be copied.
For Instance Directory, accept the default instance directory location or enter the absolute path to a directory of your choice where all Management Agent-related configuration files can be stored.
From Named Credential list, select an appropriate profile whose credentials can be used for setting up the SSH connectivity between the OMS and the remote hosts, and for installing a Management Agent on each of the remote hosts.
For Privileged Delegation Setting, validate the Privilege Delegation setting to be used for running the root scripts. By default, it is set to the Privilege Delegation setting configured in Enterprise Manager Cloud Control.
For Port, accept the default port (3872) that is assigned for the Management Agent to communicate, or enter a port of your choice.
Repeat for every other row you have in the table in step b.
Click Next.
If you want to deploy Management Agents on the selected hosts in a rolling manner, such that the deployment proceeds continuously from one deployment phase to another, ignoring the failed hosts in each deployment phase, specify the following in the $OMS_HOME/sysman/prov/agentpush/agentpush.properties
file:
oracle.sysman.prov.agentpush.continueIgnoringFailedHost=true
On the Review page if you are satisfied with the details, then click Deploy Agent to install the Management Agent. You are automatically taken to the Add Host Status page that enables you to monitor the progress of the deployment session.
Note:
The host described in this section is the VM where both Ops Center and Oracle VM Manager are installed.
As you are integrating an Exalogic machine in a virtual configuration with EECS 2.0.6.0.0 or later with the Enterprise Manager Cloud Control 12c (Release 12.1.0.3) or later, a certificate is needed to be imported to the agent because of a hardening in the communication channel of the Oracle VM Manager.
Now that you have installed the Management Agent onto the Control VM where the Oracle VM Manager is hosted, it is possible to use a tcp://
connection instead of a tcps://
connection as the access method for Oracle VM Manager discovery. Oracle recommends that you use a tcps://
connection as it is a more secure access method.
To import the Oracle VM Manager certificate into the agent:
Note:
The host described in this section is the VM where both Ops Center and Oracle VM Manager are installed.
This section provides step-by-step instructions about how to export the certificate from the Enterprise Manager Ops Center keystore and how to import the certificate into the Enterprise Manager agent keystore. These steps are a prerequisite for Exalogic Elastic Cloud discovery in Enterprise Manager Cloud Control.
Use these steps to export the Oracle Enterprise Manager Ops Center Enterprise Controller trust certificate and import it to the Enterprise Manager Cloud Control Management Agent:
Once you have installed Enterprise Manager Cloud Control 12c and the associated Manager Agent, you can now discover the targets to be monitored by Cloud Control. Follow the discovery steps below:
On an Exalogic machine in a virtual configuration, Oracle VM Manager is pre-installed as part of the Exalogic Control stack.
To install the latest release of the Enterprise Manager Oracle Virtualization plug-in on the Enterprise Manager Cloud Control Server and the agent:
To install the latest release of the Enterprise Manager Oracle Virtualization plug-in on the Management Server:
For more information about plug-ins, see the "Plug-in Manager" chapter in the Oracle® Enterprise Manager Cloud Control Administrator's Guide:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm
To deploy the plug-in to the Management Agent:
For more information, see the "Deploying Plug-Ins on Oracle Management Agent" section in the Oracle® Enterprise Manager Cloud Control Administrator's Guide:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CJGBIAGJ
The Oracle VM Manager provides the user interface that allows you to create and manage zones, virtual server pools, virtual servers, and guest virtual machines. Before you use the Oracle VM Manager to manage virtualization targets in Enterprise Manager, you must register an existing installation of the Oracle VM Manager.
Note:
The Oracle VM Manager that you register with Enterprise Manager must be at least version 3.0.2 or later.
The Oracle VM Manager must be associated with only one Enterprise Manager installation.
If you are registering Oracle VM Manager 3.3, you must ensure that the Enterprise Manager for Oracle Virtualization (Oracle Virtualization) plug-in 12.1.0.7 or a later version has been deployed on the Oracle Management Service and the Management Agent.
To register the Oracle VM Manager, you must first add it as an Enterprise Manager target. To do so, follow these steps:
For further details, see the "Registering the Oracle VM Manager" section of the Oracle® Enterprise Manager Cloud Administration Guide:
http://docs.oracle.com/cd/E24628_01/doc.121/e28814/cloud_iaas_setup.htm#CEGICIFE
When EECS 2.0.4.0.0 is upgraded to EECS 2.0.6.0.0, the following steps must be taken to re-register the upgraded Oracle VM Manager in Enterprise Manager:
Note:
If Exalogic with EECS 2.0.6.0.0 or later is used, then the Oracle VM Manager certificate needs to be imported to agent keystore.
Note:
Register the Oracle VM Manager with Enterprise Manager Cloud Control
Use the Enterprise Manager Cloud Control Agent deployed on the same Exalogic Control VM as the Oracle VM Manager. If an Enterprise Manager Cloud Control Agent is not present on the Exalogic Control VM please deploy one using the following documentation:
http://docs.oracle.com/cd/E24628_01/install.121/e24089/part_installing_agent.htm
In order to see Exalogic Control VMs in the Enterprise Manager Cloud Control 12c Exalogic navigation tree, you must register the Oracle VM Manager with Enterprise Manager Cloud Control.
The Oracle Exalogic Elastic Cloud machine includes two Oracle ZFS Storage Appliances. Follow the steps below to view and manage the Oracle ZFS Storage Appliances in Oracle Enterprise Manager Cloud Control 12c:
Configuring Oracle ZFS Storage Appliance for Oracle Enterprise Manager Monitoring
Adding Oracle ZFS Storage Appliance Instances for Monitoring
Viewing metrics and accessing reports
The two primary ways to gather information about monitored instances of an Oracle ZFS Storage appliance are viewing metrics and accessing reports:
Install the latest release of the Enterprise Manager Oracle ZFS Storage Appliance plug-in on the Enterprise Manager Cloud Control agent. To deploy the plug-in:
Figure 2-2 Deploy Plug-in
For more information about plug-ins, see the "Plug-in Manager" chapter in the Oracle® Enterprise Manager Cloud Control Administrator's Guide:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm
Note:
Follow the instructions listed in this section for both Oracle ZFS Storage Appliances in your Exalogic Rack.
To set up each appliance for monitoring from Cloud Control, enter the Oracle ZFS Storage Appliance Browser User Interface (BUI) as root
or another user with the proper role to create worksheets, enable datasets, and create users and user roles on the appliance:
Log in to the BUI and go to the Maintenance/Workflows tab.
Run the Configure for Oracle Enterprise Manager Monitoring workflow, entering and recording the password for the oracle_agent
user. You can rerun the workflow later to reset the worksheet, re-enable data sets, or recreate the user. The following occurs when the workflow is run:
A restricted role user named oracle_user
is created for use by the monitoring agent. The restricted access role associated with the oracle_agent
user is also named oracle_agent
.
An analytics worksheet is automatically created to ensure smooth communication between the Cloud Control administrator and the storage administrator tasked with administering the target Oracle ZFS Storage Appliance.
Communicate the oracle_agent
password to the Cloud Control Administrator along with the following information:
IP address for the network interface that you want Cloud Control to use to access management information (this interface must allow administration).
Full DNS name that is used to locate the system and corresponds to the IP address.
Port that is used by the BUI (typically 215 unless your company has a requirement to change management ports)
Note:
If the Oracle ZFS Storage Appliance plug-in is version 12.1.0.4 or later, then you must carry out the following additional steps:
Click to edit the “Oracle Agent" User name field.
Uncheck “Kiosk user" if it is checked.
Note:
Follow the instructions listed in this section for both Oracle ZFS Storage Appliances in your Exalogic Rack.
To add the Oracle ZFS Storage Appliance target to Oracle Enterprise Manager, complete the steps below:
As a rule, more "point in time" information is available in raw metric information than in reports. Reports are focused on information that administrators can use to analyze database performance and storage capacity.
To view the raw information collected from an Oracle ZFS Storage Appliance:
View the categories and information collected from the last collection interval.
To view reports for an Oracle ZFS Storage Appliance:
The Exalogic Elastic Cloud Discovery process identifies the targets present in the Exalogic Elastic Cloud and maps them to Enterprise Manager targets, then adds Enterprise Manager targets as Exalogic Elastic Cloud system members. The system members are represented in the schematic diagram (as shown in Figure 2-5) within Cloud Control.
Figure 2-5 Oracle Exalogic Elastic Cloud Schematic
You can use the Exalogic Elastic Cloud Discovery wizard to discover and monitor an Exalogic target in Enterprise Manager. Follow these steps:
The following monitoring tasks are only available for the Exalogic Machine in a virtual configuration:
Note:
For monitoring and management tasks common to both physical and virtual Exalogic configurations, see Monitoring and Managing Exalogic and Monitoring Hosts and Applications.
The Exalogic Elastic Cloud Software control software stack can be monitored by selecting Control Stack in the left hand navigation tree of the Exalogic target. Enterprise Manager Cloud Control displays a master-detail page of Exalogic Elastic Cloud Software virtual machines, corresponding hosts and control software element. Selecting each row master element results in a change in the detail of the page and corresponding key performance indicator charts. This page provides a unified view of incidents related to the Exalogic Elastic Cloud Software control software stack.
This section describes how to configure Enterprise Manager Cloud Control in order to consolidate alarms/incidents from Oracle Enterprise Manager Ops Center and consequently view all the issues from both systems in a single console. Furthermore, this configuration enables you to use the existing integration between Enterprise Manager Cloud Control and the ticketing system to manage the Oracle Enterprise Manager Ops Center incidents. Please note that once you start to manage Oracle Enterprise Manager Ops Center incidents within Enterprise Manager Cloud Control, if for any reason you alter incidents in Oracle Enterprise Manager Ops Center, those changes will not be reflected in Cloud Control.
The functionality of viewing Oracle Enterprise Manager Ops Center alarms in Oracle Enterprise Manager Cloud Control is disabled by default. You can enable this functionality to view Oracle Enterprise Manager Ops Center alarms in Oracle Enterprise Manager Cloud Control by performing the following steps:
From the Exalogic System target menu, select Monitoring and then choose Metric and Collection Settings.
Enable the Collection Schedule for the Oracle Enterprise Manager Ops Center Alarms metric by clicking Collection Schedule.
To view incidents and status changes created for an Exalogic system in Oracle Enterprise Manager Ops Center as incidents in Oracle Enterprise Manager Cloud Control, follow these steps:
The following management tasks are only available for the Exalogic Machine in a virtual configuration:
Note:
For monitoring and management tasks common to both physical and virtual Exalogic configurations, see Monitoring and Managing Exalogic and Monitoring Hosts and Applications.
The Exalogic Guest Base Template is an OS image in a certain format that can be used to create an Exalogic Control VM. By default, a server template is bound to a specific account. You can register a server template for public use within any account inside the Exalogic Virtual Data Center (vDC). All virtual servers created in the Exalogic vDC use a Server Template.
Before you configure the Exalogic Guest Base Template, ensure that the following prerequisites are met:
A configured virtualized Exalogic Elastic Cloud Software (EECS) installation must be present.
Enterprise Manager Cloud Control 12c installation must be present.
All Exalogic Control VMs are expected to have a public IP; so, the Enterprise Manager agent can be pushed.
Root privileges required to mount and edit the Exalogic Guest Base Template.
Oracle user account must have been defined on the Exalogic Guest Base Template.
Configuring the Exalogic Guest Base Template involves the following steps:
The disk size of the Exalogic Guest Base Template needs to be expanded to accommodate the Management Agent. To expand the disk size of the Exalogic Guest Base Template, follow these steps:
sudo
to Deploy the Management AgentTo enable sudo
, log in as user with root privileges and follow the instructions as shown in the example below:
This procedure lists the steps required to copy the Exalogic Identifier to the Exalogic Base Image Template. It must be performed for each Exalogic on a separate fabric. The Exalogic Identifier (present in the em-context.info
file) is specific to each Exalogic Fabric. The resulting Exalogic Server Templates must be used with the same rack from which the corresponding em-context.info
file was copied.
Upload and register the configured Exalogic Guest Base Template to the Exalogic Control by following the steps listed in:
http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABFFDDA
After the modified Exalogic Guest Base Template has been uploaded, follow instructions in Configuring the Exalogic Network to configure the Exalogic network. After the network has been configured, create an Exalogic Control VM using the above template within Exalogic Control. See Creating an Exalogic Control VM for details.
For Enterprise Manager to be able to map a Guest Virtual Machine on Exalogic to the corresponding host target, the host's serial number must be obtained. The GenerateSlNo.sh
script is available to obtain the host's serial number. This script should be run on the operating system of all the Guest Virtual Machines which need to be associated with their Host targets. If your EECS does not include this script, follow the instructions below to create one and run it.
Note:
This script must be run on each and every Exalogic Control VM that would potentially be monitored via an Enterprise Manager "Exalogic Elastic Cloud" system type.
Check to see if the /var/log/cellos/SerialNumbers
file exists:
If it does exist, check the content and see if it contains any serial number data. If the file is empty of serial numbers, then delete the SerialNumbers
file before you run the script as described below; otherwise, the script will exit out.
As the root
user, create a new text file in the /etc
directory. Name the file GenerateSlNo.sh
.
Add the following content to the text file:
serialCode=`dmidecode |grep Serial|grep -v Not|cut -d ":" -f2|cut -d " " -f2` if [ -f /var/log/cellos/SerialNumbers ]; then echo "File /var/log/cellos/SerialNumbers already exists." else mkdir -p /var/log/cellos echo "====START SERIAL NUMBERS====" > /var/log/cellos/SerialNumbers echo "==Motherboard, from dmidecode==" >> /var/log/cellos/SerialNumbers echo "--System serial--" >> /var/log/cellos/SerialNumbers echo "$serialCode" >> /var/log/cellos/SerialNumbers echo "--Chassis serial--" >> /var/log/cellos/SerialNumbers echo "$serialCode" >> /var/log/cellos/SerialNumbers fi
Save the file and close it.
Edit the permissions of the file to make it executable:
# chmod 700 GenerateSlNo.sh
This permissions setting allows only the root
user to run the script.
Note:
It is recommended that the EM Agent install user also have read permissions for the /var/log/cellos/SerialNumbers
file.
Run the GenerateSlNo.sh
script:
# /etc/GenerateSlNo.sh
After this script is run manually, you can either wait for the agent to re-read it (every 24 hours) or read it now and therefore populate the fields. To read it now, from the host target menu, select Configuration, then Last Collected, and finally select Refresh.
Create the Exalogic Control VM with an interface on the configured Enterprise Manager external network by following steps listed in http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#CHDIHDEI
.
Note:
The IP address for the network is assigned when the Exalogic Control VM is created. Once the Exalogic Control VM is created, a new interface cannot be assigned.
After the IP address has been created, do the following:
Configure the DNS by editing the /etc/resolv.conf
file.
Log into the running Exalogic Control VM as user with root
privileges, set the password for the Oracle user account and follow the instructions to deploy the Management Agent.
After you have uploaded and registered the configured Exalogic Guest Base Template, you need to configure the Exalogic Network and create a new Virtual Local Area Network (VLAN).
Prerequisites
All Exalogic Control VMs must be a part of the VLAN that is to be used for communication between Oracle Management Service (OMS) and the Management Agent.
The OMS must have access to the VLAN being used for communication between OMS and the Management Agent.
All Exalogic Control VMs must have publicly available host names (and corresponding IPs) that are accessible from the OMS.
To configure the Exalogic network, follow these steps:
The following steps are typically performed by a network administrator:
Identify all the available IPs on the external network with which the Guest virtual machines will be configured.
Identify the VLAN to be used for communication between the OMS and the Management Agent. If it is a tagged network then get the VLAN ID as well. The VLAN ID is added in Step 3 below.
Create external Ethernet over InfiniBand (EoIB) networks to isolate public traffic for different Accounts in the Exalogic Control. Follow the instructions in:
http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABHHEGG
Assign external EoIB networks to the Account. This step makes the external networks available to users belonging to the selected Account. To perform this step, you must identify the Account(s) for which the external EoIB networks are to be assigned. Follow the instructions listed in:
http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BEJBAIGF