Discover Oracle Exadata Machine:
Oracle Exadata targets that can be monitored and managed by OEM 12c:
- Oracle Exadata Storage Servers
- Database Server or Compute nodes
- Infiniband Switches
- Cisco Switches
- Power Distribution Units (PDU)
- KVM (Keyboard, Video & Mouse)
In this article, I will describe how to discover an Exadata Database Machine OEM 12c.
Prerequisite of Discover Oracle Exadata Machine
To install Oracle Exadata agent on the target system, we have to fulfill the prerequisite.
Create a Database Server ILOM Service Processors User:
For the Enterprise Manager agent to communicate with an ILOM service processor, there must be a specific user ID established on the ILOM service processor. Adding the specific user ID requires administrator level privilege on the ILOM service processor.
Here this user will create with ILOM CLI.
- Log in to the Service Processor as root:
Shell12# ssh root@[Service Processor IP]# Password:
- Change to the user directory.
Shell1# cd /SP/users
- Create the oemuser user and password:
Shell123456# create oemuserCreating user...Enter new password: ********Enter new password again: ********Created /SP/users/oemuser
- Change to the new user’s directory and set the role:
Shell12345# cd oemuser#pwd/SP/users/oemuser# set role='aucro'
- Repeat steps 1 through 5 for the rest of the compute node and cell node( Storage server) ILOM service processors in your Oracle Database Machine.
Run Prerequisite Script:
Discover oracle Exadata machine, Before install Oracle Exadata management agent, we have to run a prerequisite script which can be download from http://support.oracle.com and Doc ID is ‘1473912.1’
Now we discuss in details what will be checked using this script. If prerequisite check failed due to any information then that information we will fix manually.
- Verify Component Version.
|Oracle Exadata Component Version|
|Oracle Exadata Storage Software||Log into any of the storage servers as root, cellladmin or cellmonitor and execute command Cellcli –e ‘list cell detail’||126.96.36.199 onwords|
|ILOM ipmitool||For Oracle Linux, run the following command as the root user on one of the database servers in the cluster:
dcli -g ~/dbs_group -l root ipmitool –V
or just ipmitool –V
Note: The dbs_group file contains the list of compute node hostnames, one on each line. If the file does not exist, you can create it before running the dcli command.
|Infiniband Switch||Log on to the management interface for the InfiniBand Switch as nm2user (using ssh) and execute nm2version||# nm2version
Output ‘Sun DCS 36p
2.Verify the permissions agent
A) agent user(i.e oemuser) should have read and execute permission on
B) agent user(i.e oemuser) should have read permission on
3. Verify the version of the catalog.xml
This prerequisite script checks the version of catalog.xml. To discover targets Oracle Enterprise Manger use catalog.xml or databasemachine.xml file. If catalog.xml file version is under 868 please do not proceed to discover using this file also contact with Oracle support.Verify the version of the databasemchine.xml
4. Verify the version of the databasemchine.xml
The databasemachine.xml is the file created by the onecommand process during provisioning of Oracle Exadata. Oracle Enterprise Manager 12c uses the configuration information in this file during the discovery process and also uses the information to render the schematic diagram in the Exadata home page
Log in primary database machine as root or oracle user then execute command:
DO NOT proceed if the version is less than 502. Please raise a service request with the version mismatch and get the appropriate databasemachine.xml from Oracle Support.Verify ADMINNAME and ADMINIP in databasemachine.xml or catalog.xml
5. Verify ADMINNAME and ADMINIP in databasemachine.xml or catalog.xml
If Oracle Exadata was re-IP’ed(i.e IP address change) due to a network change and the corresponding management IP addresses were not updated in the databasemachine.xml then discovery will fail. The prerequisite script has this check built-in. If you want to manually verify the ADMINNAME and ADMINIP you can do a nslookup of a host and then verify the IP address in the catalog.xml or databasemachine.xml. Repeat this check for all components.
If you find such IP address mismatch problems, please log an SR with Oracle Support.
6. Make sure root.sh has been executed.
If you see “s” bit have been added in <agent installation dir>/sbin following files and root user own, it proved that root.sh was been executed.
7. Check for correct cipher.
Agent push fails with an error “Failed to launch process: Algorithm negotiation fail” This script checks the cipher entries and suggests if any changes are required. You can follow instruction is Support Note 1437596.1 to correct any missing entries.
8. Check for setup file consistency.
This check ensures that em.param and schematic files (catalog.xml / databasemachine.xml) must be consistent and contain the same cell, infiniband, kvm and pdu nodes information.
9. Check ping status for each component IP address found in schematic file:
- All components present in the schematic file must be alive.
- When using databasemachine.xml schematic file we need to check ADMINIP responds.
- When using catalog.xml schematic file we need to check IP under ADMIN tree responds. If the node is a compute node we should also check that IP under CLIENT tree responds.
Create User and agent installation directory:
To install OEM management agent in the target system, we have to create an installation directory and user.
- Create a user
# useradd –g oinstall oemuser
- Change password for oemagent user
- See uid and gid of oemagent user
- Create a directory
# mkdir –p /u01/app/oracle/product/oemuser
- Change permission to newly created directory
# chowm oemagent:oinstall /u01/app/oracle/product/oemagent
Verify Firewall Configuration:
1. Allow Ping
In many secure network environments, it is normal for the ping service to be disabled. Enterprise Manager uses ping to establish the basic availability and status of the Exadata Database Machine components.
- The compute nodes need to have the ping service and port enabled from the OMS Server(s).
- All other Exadata Database Machine components (ILOM servers, PDU’s, storage cell nodes, InfiniBand switches, and Cisco switch) need to have the ping service and port enabled from the compute nodes (where the agents are running)
2. Open Database Ports:
The database listener ports must be opened for the Enterprise Manager OMS server(s). Note that Exadata Database Machine databases will use SCAN listeners; so, ports will need to be opened for the base compute node, the compute node virtual IP, and scan listeners addresses.
3. Open Enterprise Manager Upload Port
The Enterprise Manager Cloud Control 12c agents require access to the Enterprise Manager Servers upload service, normally configured on port 4889 for HTTP uploads and 4900 for HTTPS. To verify the ports assigned, run the following command on the OMS server command line.
$ emctl status oms -details
4. Open Agent Ports
The OMS server(s) will need to be able to connect to the Enterprise Manager Cloud Control 12c Agent HTTP/HTTPS port on each compute node. The Agent port defaults to 3872. If port 3872 is not available, the next available port starting from port 1830 is used.
To identify the port used:
Run the following command on the compute node command line:
$ emctl status agent
Alternatively, you can look for the value of the EMD_URL property in the emd.properties file the following directory:
5. Open SSH Ports
The Enterprise Manager Cloud Control 12c Agents require ssh access to the Exadata Database Machine components they monitor. As the Agents will run on the compute nodes the ssh ports, 22, on each of the storage cells, ILOMs, PDUs, KVMs, InfiniBand switches, and Cisco switch will need to be opened for each of the compute nodes.
To enable ssh connectivity between agent host and cell host, follow document
when the password is want please ignore this.
6. Allow UDP Traffic (SNMP Ports)
All Exadata Database Machine components need to be able to send SNMP traps to the Agents running on the compute nodes. SNMP uses the UDP protocol so the Agent port and port 162 need to be opened for UDP traffic between the Storage Cells, ILOMs, InfiniBand Switches, Cisco Switch, and the Agent.
Enable SSH Connectivity:
- Log in to the computer where the Enterprise Manager Agent is running, open a terminal, and run the following commands as the Agent user to generate a pair of the SSH private/public keys if they are not present:
- For Release 188.8.131.52.0:
Shell12$ cd <ORACLE_HOME>/.ssh$ ssh-keygen -t dsa -f id_dsa
- For Release 184.108.40.206.0:
Shell12$ cd $HOME/.ssh$ ssh-keygen -t dsa -f id_dsa
- For Release 220.127.116.11.0:
- Copy the public key (id_dsa.pub) to the /tmp directory on the storage cell:
1$ scp id_dsa.pub root@<cell_ipaddress>:/tmp
- Add the contents of the id_dsa.pub file to the authorized_keys file in the .ssh directory within the home directory of the cellmonitor user:
1$ ssh -l root <cell_ipaddress> "cat /tmp/id_dsa.pub >> ~cellmonitor/.ssh/authorized_keys"
If the authorized_keys file does not exist, then create one by copying the id_dsa.pub file to the .ssh directory within the home directory of the user cellmonitor:1$ ssh -l root <cell_ipaddress> "cp /tmp/id_dsa.pub ~cellmonitor/.ssh/authorized_keys; chown cellmonitor:cellmonitor ~cellmonitor/.ssh/authorized_keys"
- Make sure that the .ssh directory and authorized_keys have the right file permission:
12# chmod 700 ~cellmonitor/.ssh# chmod 600 ~cellmonitor/.ssh/authorized_keys