2 Exadata Database Machine Discovery

This chapter provides instructions for discovery of the Oracle Exadata Database Machine through Enterprise Manager Cloud Control 12c.

2.1 Prerequisites for Guided Discovery

Before you begin the discovery process, there are several checks you should perform to ensure a smooth discovery. A discovery precheck script is available to automatically verify many of the common problem areas prior to discovery. You should perform the steps outlined in the following sections before proceeding with Automatic Discovery Process.

Discovery Precheck Script
Manual Verification

2.1.1 Discovery Precheck Script

Some Exadata discoveries in Oracle Enterprise Manager 12c may run into issues because of various configuration mismatches in software setup. A discovery precheck script has been developed to resolve the most common configuration problems. Run the script before all Database Machine discovery and examine the output thoroughly before proceeding with Automatic Discovery Process.

Download the Script

You can obtain the script in one of the following ways

Download the script from Prerequisite script for Exadata Discovery in Oracle Enterprise Manager Cloud Control 12c (Doc ID 1473912.1) in My Oracle Support:
```
https://support.oracle.com
```
Access the script as part of the Oracle Enterprise Manager Cloud Control 12c Setup Automation kit (Exakit) 12.1.0.1.3. See Doc ID 1440951.1 in My Oracle Support for more information on the kit:
```
https://support.oracle.com
```

Access the script as part of Exadata plug-in 12.1.0.3 after the plug-in is deployed to the agent:

<agent installation directory>/plugins/oracle.sysman.xa.discovery.plugin_12.1.0.3.0/discover/dbmPreReqCheck/exadataDiscoveryPreCheck.pl

Run the Discovery Precheck Script

To run the script:

cd $ORACLE_HOME/perl/bin/perl
./exadataDiscoveryPreCheck.pl

As the script runs, you will be prompted for various inputs. It will execute all the built-in checks and will display all messages on standard output along with an execution log.

The discovery precheck script checks for the following information:

Verifies that the user who is running the Enterprise Manager agent has read and execute permissions on at least one of the 11.2 (or later) Database Oracle home directory <ORACLE_HOME>/bin/kfod binaries.
Verifies the management server and cell server is up and running on the Exadata cell. You can verify the status by running:
```
cellcli -e 'list cell detail'
```
Verifies log in credentials. These credentials are required to complete the discovery process. Make sure you have the information of the following credentials before starting the discovery process:
- Agent host credentials: the username and password of the user running the agents on the compute nodes
- Monitoring credentials:
  - Cell Root Password
  - InfiniBand Switch Nm2user Password
  - ILOM username and password
- InfiniBand Switch root credentials: Username and Password
Verifies the Database Machine schematic file requirements for Exadata Release 11.2.3.1 and earlier, including:
- That the schematic file should exist on the agent host selected for discovering the Exadata Database Machine at:
```
/opt/oracle.SupportTools/onecommand/databasemachine.xml
```
- That the schematic file has the world-readable privilege so that it is readable by the agent user.
- That the version is 503 or later. The schematic file version is in the header of the file.
- That the values of <ADMINNAME> and <ADMINIP> in the schematic file should be the current host names and management IP addresses of the compute nodes, Exadata cells, InfiniBand switches, KVM, PDU, and Cisco switch.
Notes:
- If you are using Exadata Release 11.2.3.2 and later, see Manual Verification for the file requirements.
- If the Database Machine schematic file does not exist or its version does not meet the requirement, open a Service Request with Oracle Support to get the latest version of the schematic file.

2.1.2 Manual Verification

After running the discovery precheck script, you will still need to perform the following checks manually:

Use the 11.2 (or later) Database Oracle home directory when prompted for in Automatic Discovery Process.
Pre-requirements for platform and Database Machine version.
Compute node needs to be first discovered as Enterprise Manager host targets by installing the Enterprise Manager agents on these hosts.
- The Enterprise Manager agent must be deployed to all compute nodes of the Exadata Database Machine. The host target name of the compute node must be the fully qualified host name (for example, dbm1db01.mydomain.com). Non-fully qualified hostnames (for example, dbm1db01) or IP addresses must not be used for the host target name of the compute node.
- If you are using Exadata plug-in Release 12.1.0.1 or 12.1.0.2, the target name of the compute node host target should be the host name in the management network, not the client network.
- If you are using Exadata plug-in Release 12.1.0.3, the target name of the compute node host target can be the host name in the management network or the client network.
Verify the Database Machine schematic file requirements for Exadata Release 11.2.3.2 and later:
- Verify that the schematic file exists on the agent host selected for discovering the Exadata Database Machine at:
```
/opt/oracle.SupportTools/onecommand/catalog.xml
```
- Verify that the schematic file has the world-readable privilege so that it is readable by the agent user.
- Verify that the schematic file version is 868 or later. The schematic file version is in the header of the file.
- In addition, the values of <ADMINNAME> and <ADMINIP> in the schematic file should be the current host names and management IP addresses of the compute nodes, Exadata cells, InfiniBand switches, KVM, PDU, and Cisco switch.
  
  Client network naming is only supported in Exadata plug-in Release 12.1.0.3, but not in Releases 12.1.0.1 and 12.1.0.2.
Notes:
- If you are using Exadata Storage Server Software Release 11.2.3.1 and earlier, see Discovery Precheck Script for the Database Machine schematic file requirements.
- If the Database Machine schematic file does not exist or its version does not meet the requirement, open a Service Request with Oracle Support to get the latest version of the schematic file.
For users of Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 or if the installed version has been upgraded to Release 12.1.0.2.0 from 12.1.0.1.0 of the plug-in, you must manually push the Exadata plug-in to the agent.

2.2 Automatic Discovery Process

To automatically discover a Database Machine target, follow these steps:

From the Enterprise Manager home page, select the Setup menu (upper right corner), Add Targets, and then Add Targets Manually. Figure 2-1 shows the Add Targets Manually page.

Figure 2-1 Add Target Manually
Select the Add Non-Host Targets Using Guided Process (Also Adds Related Targets) option. From the Target Types drop-down, select Oracle Exadata Database Machine. Click Add Using Guided Discovery.

Enterprise Manager displays the Oracle Exadata Database Machine Discovery page. From here you can add the hardware components such as Exadata Storage Servers and InfiniBand Switches in the Oracle Exadata Database Machine as managed targets. You can choose to discover a new Database Machine and its hardware components as targets or instead discover newly added hardware components in an existing Database Machine as targets.
On the Oracle Exadata Database Machine Discovery page, select the Discover a new Database Machine and its hardware components as targets option. Click Discover Targets.

Enterprise Manger displays the Database Machine Discovery wizard that steps you through the process of discovering the Database Machine. The first page of the wizard, the Discovery Inputs page, appears.
Select an agent on one of the compute nodes that has the schematic file.

Click the search icon . In the Search and Select pop-up, enter the name of a target you have deployed (see "Install Enterprise Manager Agent Using the Push Method") and click Search. Select a Target Name from the results list and click Select.

Note:
If this is a partitioned Exadata Machine, be sure to pick one of the compute nodes that is part of the partition you wanted to be represented by this Database Machine target.
On the Discovery Agent section of the Discovery Inputs page, enter the following information:
- Agent URL: The Agent deployed on compute node
- Database Oracle Home: The Database Oracle home directory on compute node
  
  Note:
  The Agent user needs execute privileges on the $ORACLE_HOME/bin/kfod binary of the Oracle home specified. (Oracle Database should be Release 11.2 or later.)
Click Next.
On the InfiniBand Discovery page, enter the following information:
- IB Switch Host Name: The InfiniBand switch host name (such as, exa01sw-ib2.mycompany.com)
- Nm2user Password: The password for the InfiniBand switch
On the Prerequisite page, Enterprise Manager automatically peforms the following checks:
- Whether KFOD can be executed by the agent.
- Whether the schematic file is present.
- Whether the schematic file is readable by the agent.
On the Components page, the components below are pre-selected. You can deselect any unwanted component.
- Compute Node: select the hosts that are compute nodes in the Oracle Exadata Database Machine.
- Oracle Exadata Storage Server
- InfiniBand Switch: select the InfiniBand Switches that are part of the Oracle Exadata Database Machine. These also will be added as managed targets.
- Ethernet Switch: select the Ethernet switches that are part of the Oracle Exadata Database Machine. The Ethernet switches will be added as managed targets.
- Compute Node ILOM: select the Integrated Lights Out Managers (ILOM) of the compute nodes that are part of this Oracle Exadata Database Machine. Theses Integrated Lights Out Managers will be added as managed targets.
- KVM: select the KVM switches that are part of the Oracle Exadata Database Machine. The KVM switches will be added as managed targets.
Note:
A partitioned rack can list other components that should be deselected manually (for example, compute nodes).

Click Next to display the Monitoring Agents page.
On the Monitoring Agents page, select an agent from the drop-down selection box or click Reset to reassign. Click Next to display the Agent Credential page

Note:
The best practice is to use the Manually select the agents option on the Monitoring Agents page (instead of the Automatically select the agents option) and to use the Agent on compute node 1 for the Monitoring Agent and the Agent on compute node 2 for the Backup Monitoring Agent for all targets.
This configuration is to ensure that you know which Agents to use when configuring SNMP for Exadata Storage Cell and InfiniBand switch targets (see Configure Storage Cell SNMP for Enterprise Manager Monitoring and Configure and Verify SNMP for InfiniBand Switch Targets).
On the Agent Credential page, specify whether the agent host users and passwords are the same for all agents. The agent users and passwords are required to set up password-less SSH between the agents and the cells monitored by the agents.

If the users and passwords are the same, choose Same for all agents and enter the user and password combination. If they are not the same for each agent, choose Different for all agents and enter each combination for each agent.

Click Next to display the Monitoring Credential page.
On the Monitoring Credential page, configure the credentials for:
- Oracle Exadata Storage Server: select the Same for all cells option. Enter the Cell Root Password.
- Infiniband Switch: select the Same for all Infiniband switches option. Enter the Infiniband Switch Nm2user Password.
- ILOM: select the Same for all ILOM option. Enter the ILOM password.
Note:
In all cases you can choose to enter the same user/password combinations for all components or you can enter the credentials separately for each occurrence.

Click Next to display the SNMP Subscription page.
On the SNMP Subscription page, automatically set up an SNMP subscription on the cell and InfiniBand Switch targets. Figure 2-2 shows an example of the SNMP subscription options.

Figure 2-2 SNMP Subscription

Click Next to display the Component Properties page.
On the Component Properties page, specify the target properties of the different components. For each component, enter the required information.

Click Next to display the Review page.
On the Review page, verify each section is correct. Figure 2-3 shows an example of an accurate review.

Figure 2-3 Database Machine Discovery Review Page
If the information is correct, click Submit.
On the Target Creation Summary page, click OK.

Enterprise Manager displays the Target Promotion Summary page that displays the targets that are now managed targets.

The discovery of the Oracle Exadata Database Machine is complete.