Dell Integrated Systems for Oracle Database - Oracle Enterprise Manager Integration Guide v1.
Revisions Date Description September 2015 Document initial release version 1.0 THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc.
Contents 1 About this Guide ........................................................................................................................................................................ 4 2 Introduction ................................................................................................................................................................................ 5 3 Installation overview...........................................................................................
1 About this Guide This is a supplementary guide to the Dell Integrated Systems for Oracle Database (DISOD) Owner’s Guide that is available on Dell Support site. This guide describes the installation, configuration, and integration of Dell infrastructure management software (Open Manage Essentials) with Oracle Enterprise Manager in order to manage and monitor the DISOD hardware components along with the Oracle databases from a single management console.
2 Introduction DISOD solution rack ships with a pre-integrated hardware infrastructure that is dedicated for the management and monitoring of its hardware components. Using the DISOD management infrastructure, customers and Dell Services or Support can manage and monitor any of the hardware components—either locally or remotely. The DISOD management infrastructure consists of the following dedicated hardware: Management Switch: Dell Networking 1 GbE switch is used as the dedicated management switch.
Figure 1 shows the architectural overview of the DISOD management solution. Customer Environment Oracle Middleware Server OMS OEM Console DAAD OEM Plugin Dell OME Plugin Oracle Enterprise Manager 12c Cloud Control Public Network DISOD Rack Mgmt.
3 Installation overview This section provides an overview of The Management Server OS configuration Management software installation flow, and The network prerequisites The DISOD solution is managed primarily by using two different software components: Oracle Enterprise Manager and Dell OpenManage Essentials software application. 3.1 Management Server OS configuration overview This section provides the OS configuration overview on the management server (R320) before it ships out to the customer.
Dell Acceleration Appliance for Databases (DAAD) plug-in for OEM Existing OEM environment Start Monitor DISOD from OEM Console No Yes Install Software on WinVM Install OpenManage Essentials Perform DAAD discovery on OEM Install OEM on LinVM Deploy the DAAD OEM plugin onto DAAD 2.0 Configure SNMP Enable OEM discovery on DAAD 2.
3.3 Network prerequisites The following are the network prerequisites that must be configured before installing DISOD management software. Switch prerequisites: - Ensure that the customer’s public network is connected to the public network port(s) that are pre-defined1 on the top-of-rack (ToR) S6000 switch(es). Management server prerequisites: a. Configure public IP address for the public network adapter dMan-pub on the Management Server’s base Windows Server 2012 operating system. b.
Database nodes prerequisites: a. Create bonding (bond0) by using the public network ports on each of the database nodes and configure public IP address to ensure that the database nodes can be reached from the customer’s public network. NOTE: In the R730-based database nodes, eth4 and eth6 are the public network ports, and in the R930-based database nodes, eth2 and eth4 are the public network ports. b. Assign hostnames to each of the database nodes. c.
h. Move the cursor to Name Server 1 and add the appropriate DNS server IP address. NOTE: The DNS IP address is either the customer’s existing DNS server IP address or the new one set up in WinVM. i. Press ALT + u to change the Routing (customer’s network gateway) IP address of the DAAD Node j. Press ALT + o to ensure the configuration changes done in previous steps are accepted and to close the dialogue box. k. At the CLI, enter setup cluster to view the Setup dialog box for cluster configuration. l.
4 Installing OEM 12c on LinVM (optional) Oracle Enterprise Manager (OEM, 12c Cloud Control) is an integrated management suite that allows the database administrator to manage and monitor the health of both Oracle and non-Oracle IT infrastructure from applications to storage. In this section, installation and configuration of OEM 12c is described.
5 Installing Dell OME on WinVM This section describes the installation and configuration instructions for the Dell OpenManage Essentials (OME). Dell OpenManage Essentials is an easy-to-install, intuitive, and simple-to-use, systems management console solution from Dell, optimized for monitoring and managing Dell servers, switches, and storage. 5.1 Prerequisites To provide network connectivity from one server to another, you have to manually update the hosts file on each server.
5.4 Discover DISOD Components in Dell OpenManage Essentials This section provides steps to discover the DISOD components in Dell OME. After successful Dell OME installation, proceed to discover by using the following information: To Discover the DISOD database nodes, refer to this wiki article. To Discover Dell Force10 Switches, refer to this wiki article. To Discover DAAD nodes, refer to this wiki article.
6 Install Oracle Management Agent (OMA) on WinVM This section describes the installation and configuration of Oracle Management Agent for Windows platform on WinVM. The Oracle Management Agent is used to convert an unmanaged host to a managed host in the Enterprise Manager System, which uses the Oracle Management Agent to monitor targets running on the managed host. 6.
If your environment doesn’t have a Windows-based system that can connect to both OMS and WinVM, you can use the DISODs management server (R320) for this purpose. NOTE: This staging Windows host should not be the same as WinVM and also should have connectivity to WinVM. For the process of installing OMA on Windows host by using PsExec tools, see the Oracle enterprise manager release documentation by clicking link.
7 Dell OpenManage Plug-in installation steps This section describes the installation, configuration, and deployment of Dell OpenManage essentials plugin that pairs the OEM with the WinVM on which the OpenManage Essentials software is installed. Download the Dell OpenManage Plug-in for Oracle Enterprise Manager from this link.
3. Log in to Enterprise Manager and navigate to Setup → Extensibility → Self Update. Selecting the appropriate menu to check the uploaded plug-in 4. Click the Plug-in Folder and make sure that Dell OpenManage Plug-in for OEM has been successfully uploaded to the Software Repository. 7.2 Deploying the plug-in on OMS 1. Log in to an Oracle Enterprise Manager Cloud Control web console with administrative privileges. 2. From the Enterprise Manager Web console, navigate to Setup → Extensibility → Plug-ins. 3.
Screenshot for deploying DELL OME plug-in on OMS 7. In the Deploy Plug-in on Management Servers dialog box, type the Repository SYS Password, and then click Continue. 8. Review the results of the pre-requisite check and click Next. 9. If the details in the review page are correct, click Deploy to begin the plug-in deployment. Note: The Review page displays the management servers on which the plug-in is being deployed, the version of any previously deployed Dell plug-ins, and the status of the OMS. 10.
7.3 Deploying the Dell OpenManage plug-in on OMA (WinVM) 1. Log in to Oracle Enterprise Manager Cloud Control web console with administrative privileges. 2. From the Enterprise Manager Web console, click Setup → Extensibility → Plugins. 3. On the Plug-ins page, select the Dell OpenManage Essentials row under the Servers, Storage and Network folder. Successful upload of Plug-in 4. Right-click Dell OpenManage Essentials, pause the pointer over Deploy On, and then click Management Agent.
Management agent status 6. After selecting the appropriate OMA, click Continue in the Deploy Plug-in on Management Agent window. 7. Review the results of the pre-requisite check and click Next. 8. If the details in the review page are correct, click the Deploy button to begin the plug-in deployment job. Final deploy screen Note: The Review page displays the management servers on which the plug-in is being deployed, the version of any previously deployed Dell plug-ins, and the status of the OMA. 9.
10. The Management Agent with Plug-in field, for the plug-in, contains the number of OpenManage Essentials plug-ins that were deployed to OMAs. To view this field, navigate back to the Plug-ins page (Setup → Extensibility → Plug-ins). Successful deployment shows a value in Management agents with Plug-in column 7.4 Manually adding the Dell OME target 1. Log in to an Oracle Enterprise Manager Cloud Control web console with administrative privileges. 2.
Selection of Windows based target 6. After selecting the OMA to use, click the Add Manually button to continue to the plug-in configuration page. Select Add Manually 7. On the configuration page, set the values for customizing the plug-in connection to the OpenManage Essentials system. a. Target Name (required): An instance name required for the OpenManage Essentials Plug-in target. This name is used to reference this specifically configured target and sub-targets inside of OEM. b.
must be the same host name that is used when connecting the OpenManage Essentials web console. c. Dell OpenManage Essentials Port: The port that Dell OpenManage Essentials is running on. This value is optional, if it is not provided, the plug-in will use port 2607 by default. d. Password (required): A valid password in combination with the associated username is required to connect to the Dell OpenManage Essentials web services. The account used should have at least OME Users privileges. e.
OEM – OME host connection status 9. If the test connection result is successful, click OK to finalize the target configuration. Target added as managed host based on target monitoring properties 10. To view the Dell OpenManage Essentials target that was just created, navigate to the All Targets view (Targets → All Target) and view the table of targets for the instance name that was used during configuration. Note: It may take up to 20 minutes for completion of the first collection interval for the target.
to collect device data from an OpenManage Essentials environment. Sub-target discovery and promotion is described in the “Discovering device sub-targets” section of this guide. 7.5 Discovering device sub-targets The discovery process will find all targets related to a Dell OpenManage Essentials target. This includes servers, chassis controllers, storage, and switches. 1. Log in to an Oracle Enterprise Manager Cloud Control web console with administrative privileges. 2.
Selection of appropriate agents for auto-discovery 5. Clear all options except the Dell OME Discovery Module to disable the discovery of other targets unrelated to this plug-in. Select OME specific targets 6. Click OK. 7. Select the same host selected in step 4 and click Run Discovery Now. Dell Integrated Systems for Oracle Database - Oracle Enterprise Manager Integration Guide v1.
Run first-time discovery procedure 7.6 Promoting Discovered device sub-targets 1. After the discovery process is complete, view the discovery results to see the targets that have been discovered. You can view this by clicking Add Target Auto Discover Results. Check the discovered sub-targets 2. On the Discovery results page, select agent based targets. Select all targets in this list from where you want to collect data, and then click Promote.
Sample discovered targets 3. Navigate back to OpenManage Essentials target to view that the data is now being collected. OME specific target monitoring window Note: The time between the target being promoted and data for the target returning is dependent on the configured metric collection interval of the OMA. Dell Integrated Systems for Oracle Database - Oracle Enterprise Manager Integration Guide v1.
8 Installing and Configuring the Dell Acceleration Appliance for Databases (DAAD) Plug-in on OEM The Dell Acceleration Appliance for Databases (DAAD) plug-in for OEM enables OEM to display information and statistics such as volume and link performance, directly from the storage array. Version 12.1.0.1 of the plug-in is compatible with the following: DAAD plug-in version 12.1.0.1 release 2.3.0.1. Oracle Management Server (OMS) versions 12.1.0.1, 12.1.0.2, 12.1.0.3, and 12.1.0.4 8.
After successful execution of the command the command, the following message is displayed: Agent deployment successful, The Agent is configured successfully.Finished product -specific root actions. Note: Repeat the step on the other DAAD node and view the results. If it is successful, go to the next step. Else, check connections between the nodes and continue. After successful installation on DAAD nodes, go to the OEM console and see the DAAD nodes under the All Targets tab.
NOTE: This process will take a while. To get the status of the process, run the following command: $./emcli get_plugin_deployment_status – plugin_id=fusionio.ion.ion1 7. Step 5 will be executed for the other DAAD node by using the command: $./emcli deploy_plug_on_agent -agent_names=t***.b****.com:3872 -plugin=fusionio.ion.ion1 NOTE: This process will take a while. To get the status of the process, run the following command: $./emcli get_plugin_deployment_status – plugin_id=fusionio.ion.
8.4 Opening the DAAD target in OEM: 1. Log in to the OEM console. 2. Select the All Targets tab from the target menu which is located in the toolbar. 3. Select the ION Accelerator target from the all targets or search for the target name from the Search tab located in the upper-right corner to open the ION Accelerator plug-in home page.
