| Asset ID: |
1-79-1437434.1 |
| Update Date: | 2012-04-24 |
| Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
1437434.1
:
Prerequisite steps before discovering Exadata DB machine within Oracle Enterprise Manager 12c
| Related Items |
- Exadata Database Machine X2-2 Hardware
- Enterprise Manager for Exadata
|
| Related Categories |
- PLA-Support>Database Technology>Enterprise Manager>EM: Management and Monitoring>EM: Cloud-Host-VM Plugin
- .Old GCS Categories>ST>Server>Engineered Systems>Exadata>Administration and Configuration
- .Old GCS Categories>ST>EM>Managing Hosts>Discovery
|
Applies to:
Exadata Database Machine X2-2 Hardware - Version Not Applicable to Not Applicable [Release N/A]
Enterprise Manager for Exadata - Version 12.1.0.1.0 to 12.1.0.2.0 [Release 12.1]
Information in this document applies to any platform.
Purpose
This document lists a set of prerequisites that you would need to ensure before you can discover your Exadata Database Machine in Oracle Enterprise Manager Cloud Control 12c. Please make sure to go through the entire document before starting the discovery process.
Details
he prerequisite steps are listed below:
1. Create a Database Server ILOM Service Processor User
1. Log in to the Service Processor as root:
ssh root@[Service Processor IP]
Password:
2. Change to the users directory:
cd /SP/users
3. Create the oemuser user and password:
create oemuser
Creating user...
Enter new password: ********
Enter new password again: ********
Created /SP/users/oemuser
4. Change to the new user's directory and set the role:
cd oemuser
/SP/users/oemuser
set role='aucro'
Set 'role' to 'aucro'
5. Test the ILOM user ID created in step 3 by listing the last 10 system events:
ipmitool -I lan -H <ilom_hostname> -U oemuser -P oempasswd -L USER sel list
last 10
6. Repeat steps 1 through 5 for the rest of the compute node ILOM service processors
in your Oracle Database Machine.
2. Verify the versions
Note: The versions reported here are the minimum versions supported. Depending on the version of the Exadata Compute nodes or the Exadata Storage Server software you may need to be on a specific version on one or more components. Please check support note 888828.1 for certified configurations.
| | | |
|---|
| Exadata Storage Server Software |
Run command
Cellcli -e 'list cell detail' as root, cellladmin or cellmonitor |
11.2.2.3 onwards |
| ILOM ipmitool |
For Oracle Linux: as root on the first database server in the cluster, run:
dcli -g ~/dbs_group -l root ipmitool - V
or just ipmitool -V on each compute Node
For Oracle Solaris: as root on the first database server in the cluster, run:
/opt/ipmitool/bin/ipmitool -V |
Linux: 1.8.10.3 or later
Solaris: 1.8.10.4 or later
|
| InfiniBand Switch |
Log on to the management interface for the InfiniBand Switch (using ssh) and execute
nm2version
|
Sun DCS 36p version: 1.1.3-2
|
| PDU Firmware |
The current version can be obtained by logging into the web interface of the PDU. On the left side of the screen, click Module Info to view the PDU firmware version.
Software updates for PDU are available at
https://updates.oracle.com/Orion/PatchDetails/process_form?patch_num=12871297 |
1.02 later |
| KVM Application |
The current version can be obtained by logging into the web interface of the KVM. On the left side of the screen under Unit View, Appliance, Appliance Settings, click Versions to view the Application software version.
Software updates are available at
http://www.avocent.com/Support_Firmware/MergePoint_Unity/MergePoint_Unity_Switch.aspx |
1.2.8 or later |
3. Verify permissions :
User running agent should have read and execute permission on $ORACLE_HOME/bin/kfod binaries
4. Exadata machines delivered to customers before and early parts of 2011 do not have or have unsupported versions of the schematic files required for the successful discovery of the Exadata database machine within Oracle Enterprise Manager 12c.
Action: To make sure you have the correct file please follow the steps outlined below
1. Login to your first (primary) Compute Node as root
2. Change directory to /opt/oracle.SupportTools/onecommand
3. Execute grep -i version databasemachine.xml|grep -v xml
You should see an output similar to the one below:
[ComputeNode onecommand]$ grep -i version databasemachine.xml|grep -v xml
<ORACLE_CLUSTER version="502" timestamp="14-June-2011 9:23:17 AM">
Do not proceed if the version is less than 502.
Please raise a support request with the version mismatch and get the appropriate databasemachine.xml from Oracle support.
5. 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.
6. Other Prerequisites for discovery
Download and install Latest OneCommand Patch
Required credentials list:
- Agent host credentials: the username and password of the user running the agents on the compute nodes
Monitoring credentials:
- Cell Root Password
- Nm2user password of each InfiniBand switch
- ILOM username and password
- InfiniBand Switch root credentials: Username and Password
Attachments
This solution has no attachment
