Oracle Enterprise Manager Cloud Control 12c Setup Automation kit for Exadata

With this post I like to mention the availability of the Enterprise Manager 12c setup automation kit for Exadata. I also like to explain how easy it is to deploy the agent for a complete Exadata rack of any size with all it's components. After the discovery the system can managed by EM, the deployment I did took only 30 minutes for a quarter rack with all components.

You can obtain the "Oracle Enterprise Manager Cloud Control 12c Setup Automation kit for Exadata" from MOS by searching for patch 12960596

The deployment of the agent starts with the Exadata configurator sheet. This is the sheet ACS already used for the Exadata deployment. The sheet now also creates a configuration output file for automatic agent and OMS deployment. The file I am talking about is called em.params. This file can be used as input for the OMS or EM 12c deployment scripts. In this posting I will only discuss the agent deployment.

This em.params file will have the following information:

# This is em.param file
# Written : 26-10-2011
EM_VERSION=1.0

OMS_LOCATION=REMOTE_CORP_GC
EM_BASE=/u01/app/oracle/product/EMbase
OMS_HOST=my-host.us.oracle.com
OMS_PORT=4900

EM_CELLS=(cel12 cel13 cel14)

EM_COMPUTE_ILOM_NAME=(db07-c db08-c)
EM_COMPUTE_ILOM_IP=(a.b.c.d a.b.c.e)

machinemodel="X2-2 Quarter rack"

EM_USER=oracle
EM_PASSWORD=passwd

swikvmname=sw-kvm
swikvmip=a.b.c.f
swiipname=sw-ip
swiipip=a.b.c.g
swiib2name=sw-ib2
swiib2ip=a.b.c.d
swiib3name=sw-ibh
swiib3ip=a.b.c.i
pduaname=pdu1
pduaip=a.b.c.j
pdubname=pdu2
pdubip=a.b.c.k


Of course, the names and ipnumbers are changed in this example to hide any specific information.
When you install the kit the configuration file is expected in /opt/oracle.SupportTools/onecommand, this is where your OneCommand deployment files will be anyway.

During installation some additional checks will be done like:
Trying to ping Oracle Management Server Host my-host.us.oracle.com .
Checking oracle user info
Searching for KVM Switch information by key swikvmname from /opt/oracle.SupportTools/onecommand/em.param
Searching for KVM Switch IP information by key swikvmip from /opt/oracle.SupportTools/onecommand/em.param
Searching for Cisco Switch information by key swiipname from /opt/oracle.SupportTools/onecommand/em.param
Searching for Cisco Switch IP information by key swiipip from /opt/oracle.SupportTools/onecommand/em.param
Searching for IB2 Switch information by key swiib2name from /opt/oracle.SupportTools/onecommand/em.param
Searching for IB2 Switch IP information by key swiib2ip from /opt/oracle.SupportTools/onecommand/em.param
Searching for IB3 Switch information by key swiib3name from /opt/oracle.SupportTools/onecommand/em.param
Searching for IB3 Switch IP information by key swiib3ip from /opt/oracle.SupportTools/onecommand/em.param
Searching for PDUA Name information by key pduaname from /opt/oracle.SupportTools/onecommand/em.param
Searching for PDUA IP information by key pduaip from /opt/oracle.SupportTools/onecommand/em.param
Searching for PDUA Name information by key pdubname from /opt/oracle.SupportTools/onecommand/em.param
Searching for PDUB IP information by key pdubip from /opt/oracle.SupportTools/onecommand/em.param
Searching for ILON Names information by key EM_COMPUTE_ILOM_NAME from /opt/oracle.SupportTools/onecommand/em.param
Searching for ILOM IPS information by key EM_COMPUTE_ILOM_IP from /opt/oracle.SupportTools/onecommand/em.param
Verifying ssh setup..
Verifying SSH setup for root

When the validations are done, the 12.1.0.1.0_AgentCore_226.zip file will be transferred to the compute nodes and the 12c agent will be installed.
Like the 11.1 installation, still no agents will be installed on the storage cells, EM will use the compute nodes as proxy to the cells, it's up to you if you want EM to choose which nodes or choose yourself.

After deployment, there are three easy steps left in the EM GUI:
  • Exadata discovery
  • GI(Cluster) discovery
  • RAC discovery

The discovery steps above are guided by a clear GUI.
All the discovery process needs is access to a compute node, from there all the Exadata components will be discovered automatically.
The file EM needs to be available for that is  /opt/oracle.SupportTools/onecommand/databasemachine.xml

After installation of the kit and discovery in EM 12c, you have a nice overview of the rack with all the components in it, easy to drill down and manage from there. The example below is a quarter rack.

René Kundersma

Oracle MAA Development










Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Blog of Rene Kundersma, Principal Member of Technical Staff at Oracle Development USA. I am designing and evaluating solutions and best practices around database MAA focused on Exadata. This involves HA, backup/recovery, migration and database consolidation and upgrades on Exadata. Opinions are my own and not necessarily those of Oracle Corporation. See http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today