An Oracle White Paper October Oracle Enterprise Manager 12c: Oracle Exadata Discovery Cookbook

Transcription

1 An Oracle White Paper Octber 2012 Oracle Enterprise Manager 12c: Oracle Exadata Discvery Ckbk

2 Intrductin... 2 Befre Yu Begin... 2 Exadata discvery prerequisite check script... 3 Launching Discvery... 9 Installing the Agents n the Cmpute Ndes... 9 Running Guided Discvery Pst Discvery Setups KVM Discvering the Cluster and Oracle Databases Cnclusin... 36

3 Intrductin Oracle Enterprise Manager 12c is Oracle s integrated enterprise IT management prduct line that prvides the industry s first cmplete clud lifecycle management slutin. Oracle Enterprise Manager 12c ffers a hlistic apprach t managing Oracle Exadata Database Machine, with its cmprehensive lifecycle management frm mnitring t management and nging maintenance fr the entire engineered system. One f the first steps t managing Oracle Exadata is t discver the machine in Oracle Enterprise Manager 12c. This whitepaper describes in detail what s required in rder t be successful. Befre Yu Begin The fllwing sectin utlines the steps that yu need t cmplete befre yu launch discvery in Oracle Enterprise Manager 12c. These steps are extremely imprtant and need t be cmpleted in entirety t ensure a successful discvery. A. Create a Database Server ILOM Service Prcessr User Lg in t the Service Prcessr as rt: ssh rt@[service Prcessr IP] Passwrd: Change t the users directry: cd /SP/users Create the emuser user and passwrd: create emuser Creating user... Enter new passwrd: ******** Enter new passwrd again: ******** Created /SP/users/emuser Change t the new user's directry and set the rle: cd emuser /SP/users/emuser set rle='aucr' Set 'rle' t 'aucr' Test the ILOM user ID <emuser> created abve, by listing the last 10 system events: ipmitl -I lan -H slcb06db01-c -U emuser -P empasswd - L USER sel list last 10 2

4 Repeat all the abve steps fr the rest f the cmpute nde ILOM service prcessrs in yur Oracle Database Machine. Exadata discvery prerequisite check script We have created a Perl script that can dwnladed and executed n any cmpute nde befre actually starting the discvery prcess. Yu can run the script befre r after Oracle Enterprise Manager Clud Cntrl 12c has been deplyed n the Exadata Database Machine. Yu can dwnlad the latest cpy f the script frm nte: Checks cvered by the prerequisite script A. Verify the cmpnent versins In this check we verify the versin f the different Oracle Exadata cmpnents. Yu may als use the cmmand listed in the table belw t run it manually. Nte: The versins reprted here are the minimum versins supprted. Depending n the versin f the Exadata Cmpute ndes r the Exadata Strage Server sftware yu may need t be n a specific versin n ne r mre cmpnents. Please check supprt nte fr certified cnfiguratins. Cmpnent Cmmand Versins supprted Oracle Exadata Strage Server Sftware ILOM ipmitl Infiniband Switch Lg int any f the strage servers as rt, cellladmin r cellmnitr and execute cmmand Cellcli e list cell detail Fr Oracle Linux: as rt n the first database server in the cluster, run: dcli -g ~/dbs_grup -l rt ipmitl V r just ipmitl V Fr Oracle Slaris: as rt n the first database server in the cluster, run: /pt/ipmitl/bin/ipmitl -V Lg n t the management interface fr the InfiniBand Switch as nm2user (using ssh) and execute nm2versin nwards Slaris: r later Linux: # nm2versin Sun DCS 36p versin:

5 PDU Firmware KVM Applicatin If Oracle Exadata has a PDU cabled and yu wish t mnitr it prceed with this check. This is nt a mandatry check. The current versin can be btained by lgging int the web interface f the PDU [ IP Address>/] Nte: There is n terminal access t the PDU - there is nly a netwrk cnnectin. Yu can reset the http access by resetting the cntrl panel. On the left side f the screen, click Mdule Inf t view the PDU firmware versin. Sftware updates fr PDU are available at patch_num= If Oracle Exadata has a keybard, vide and muse (KVM) switch and yu wish t mnitr it prceed with this check. This is nt a mandatry check as sme versins f Exadata d nt have a KVM. The current versin can be btained by lgging int the web interface f the KVM. [ IP Address>/]. This check is nt applicable t X2-8 database machines. On the left side f the screen under Unit View, Appliance, Appliance Settings, click Versins t view the Applicatin sftware versin. Sftware updates are available at y/mergepint_unity_switch.aspx 1.04 later r later Figure 1: Image shwing the PDU versin frm the web interface 4

6 Figure 2: Image shwing the KVM versin frm the web interface B. Verify the permissins I. User running agent shuld have read and execute permissin n $ORACLE_HOME/bin/kfd binaries II. User running agent shuld have read permissin n /pt/racle.supprttls/necmmand/catalg.xml OR /pt/racle.supprttls/necmmand/databasemachine.xml Nte: This check is nw integrated with the discvery flw. C. Verify the versin f the catalg.xml Recently the Java based cnfiguratr has been released thrugh OneCmmand patch and has replaced the previusly used cnfiguratin spreadsheet. The Java based cnfiguratr generates a new cnfiguratin file called catalg.xml that (if available) is used by the Enterprise Manager agent during discvery t read cnfiguratin infrmatin. The Exadata prerequisite check script has been updated t verify the existence f this file and the minimum versin (868) supprted. If this file is nt present then the databasemachine.xml is used. Either the catalg.xml r the databasemachine.xml file shuld be present t ensure successful discvery. DO NOT prceed if the versin is less than 868. Please raise a service request with the versin mismatch and get the apprpriate databasemachine.xml frm Oracle Supprt. D. Verify the versin f the databasemachine.xml The databasemachine.xml is the file created by the necmmand prcess during prvisining f Oracle Exadata. Oracle Enterprise Manager 12c uses the cnfiguratin infrmatin in this file during the discvery prcess and als uses the infrmatin t render the schematic diagram in the Exadata hme page. Hwever Oracle Exadata delivered t custmers befre and early parts f 2011 d nt have r have unsupprted versins f the schematic files required fr the successful discvery f Oracle Exadata within Oracle Enterprise Manager 12c. 5

7 T make sure yu have the crrect file please fllw the steps utlined belw A. Lgin t yur first (primary) Cmpute Nde as rt r racle B. Change directry t /pt/racle.supprttls/necmmand C. Execute grep -i versin databasemachine.xml grep -v xml DO NOT prceed if the versin is less than 502. Please raise a service request with the versin mismatch and get the apprpriate databasemachine.xml frm Oracle Supprt. E. Verify ADMINNAME and ADMINIP in databasemachine.xml r catalg.xml If Oracle Exadata was re-ip ed due t a netwrk change and the crrespnding management IP addresses were nt updated in the databasemachine.xml then discvery will fail. The prerequisite script has this check built-in. If yu want t manually verify the ADMINNAME and ADMINIP yu can d a nslkup f a hst and then verify the IP address in the catalg.xml r databasemachine.xml. Repeat this check fr all cmpnents. If yu find such IP address mismatch prblems please lg an SR with Oracle Supprt. F. Make sure rt.sh has been executed 6

8 Yu can run this script after the Oracle Enterprise Manager agent has been installed n the Database Machine. This check ensure that the rt.sh script has been successfully applied after agent installatin. The fllwing files in <agent installatin dir>/sbin shuld be wned by rt and have the s bit set: -rws--x--- 1 rt install Apr 6 14:56 nmb -rws--x--- 1 rt install Apr 6 14:56 nmhs -rws--x--- 1 rt install Apr 5 21:51 nm G. Check fr crrect cipher: Agent push fails with an errr Failed t launch prcess: Algrithm negtiatin fail This script checks the cipher entries and suggests if any changes are required. Yu can fllw instructin is Supprt Nte t crrect any missing entries. H. Check fr setup files cnsistency: This check ensures that em.param and schematic files (catalg.xml / databasemachine.xml) must be cnsistent and cntain the same cell, infiniband, kvm and pdu ndes infrmatin. I. Check ping status fr each cmpnent IP address fund in schematic file: a. All cmpnents fund in schematic file must be alive. b. When using databasemachine.xml schematic file we need t check ADMINIP respnds. c. When using catalg.xml schematic file we need t check IP under ADMIN tree respnds. If the nde is a cmpute nde we shuld als check that IP under CLIENT tree respnds. J. Check dmain name setup: The dmain name btained frm the perl script using Net::Dmain Perl mdule and the dmain name at OS level btained using dmainname cmmand must be the same, and nt be empty r cntain (nne). List f credentials needed fr Discvery Agent hst credentials: the username and passwrd f the user running the agents n the cmpute ndes Mnitring credentials: Cell Rt Passwrd Nm2user passwrd f each InfiniBand switch 7

9 ILOM username and passwrd (see the first pre-requisite step described abve) InfiniBand Switch rt credentials: Username and Passwrd Agent wner shuld be in the same OS grup as the CRS and Database sftware wners 8

10 Launching Discvery This sectin assumes that yu already have a fully functinal Oracle Enterprise Manager 12c envirnment. If nt please refer t supprt nte fr the latest Exakit that yu may use t cnfigure an Oracle Enterprise Manager 12c envirnment. There is als an Oracle Exadata Agent kit available which autmates the agent deplyment prcess n the cmpute ndes. In the fllwing sectins we will describe bth the Agent push methd frm the OMS and the Oracle Exadata Agent Kit methd. This paper used a quarter rack Oracle Exadata machine fr capturing the flw, the same prcess listed belw applies t bth half and full rack machines. Installing the Agents n the Cmpute Ndes Agent Push Methd The first step t discvery is installing the agents n the cmpute ndes. This is a fairly simple prcess and can be dne in parallel n all the cmpute ndes frm the Oracle Enterprise Manager 12c Clud Cntrl cnsle. Frm the setup menu select Add targets Add targets manually This screen leads yu t the Add Hsts screen Select the Add Hst targets radi buttn and click n the Add Hst buttn. 9

11 In the Add Target screen use the ADD buttn t add as many rws yu have. Fr example, fr a full rack yu will need 8 rws fr the 8 cmpute ndes. Yu need t select Same fr All Hsts in the Platfrm bx and Linux x86-64 r Slaris fr the Operating System. Once this infrmatin is added click Next t mve t the installatin details screen. In the installatin details screen input the Installatin Base Directry which autmatically ppulates the Instance Directry. In the Named Credential field either use a previusly created credential r input the username and passwrd f the user that will wn the Agent binaries. Yu may leave the Prt number as is, r change it t a number f yur chice. Click Next t review inputs and deply the agents. 10

12 In the fllwing screen Oracle Enterprise Manager 12c cpies the Agent binaries t all the cmpute ndes, runs several validatin checks and n successful agent deplyment the cmpute ndes are discvered as Hst targets in Oracle Enterprise Manager. Once the agents are successfully deplyed, click n dne t get back t the Add targets screen. Oracle Exadata Agent Kit If yu chse t use the Oracle Exadata Agent kit please refer t supprt nte t dwnlad the latest versin f the kit. The Oracle Exadata Agent kit autmates the steps that we have described in the previus sectin. Once the Agent kit is dwnladed please fllw the instructins in the README carefully t deply the agents. At a high level the steps invlved are 11

13 Lg in as the rt user n the first database server. Create the /tmp/emkit directry n the first database server n Oracle Exadata. Make sure /tmp has at least 2 GB free space. Dwnlad the Oracle Enterprise Manager 12c Agent Setup Autmatin kit X. [This versin must crrespnd t yur OMS versin. Detailed versin related checks are mentined in the README file] Cpy the dwnladed kit t /tmp/emkit. Change t the /tmp/emkit directry. Run the fllwing cmmands: unzip pxxxx_12xxx_linux-x86-64.zip tar xbvpfz CludCntrl_Agent_ X.X_LINUX.X64.tar.Z Change the directry t /tmp/emkit/cmmn. Make sure t edit the /pt/racle.supprttls/necmmand/em.param file and prvide the required infrmatin. Run the setup script using the fllwing cmmand: (sh setupem.sh tee /tmp/setupag.lg) 3>&1 1>&2 2>&3 tee /tmp/setupag.err Once Agents are installed n the Cmpute Ndes prceed t run guided discvery described in the fllwing sectin. 12

14 Running Guided Discvery In the Add targets page select the Add Nn-Hst targets using Guided prcess and chse Oracle Exadata frm the drp dwn and click n Add using Guided Discvery buttn. This will launch the discvery wizard page. In this page yu have the ptin t either discver an Oracle Database Machine as a brand new target r yu can chse t add hardware cmpnents in an existing Database Machine target. Based n yur requirements select the ptin and click n Discver targets. This paper will fcus n the new target additin flw nly. In the Discvery Inputs screen specify the agent that yu wuld want t use fr discvery. Yu can chse any ne f the cmpute ndes but it is recmmended t use the first nde f the cluster. When 13

15 yu chse the agent yu want t use a crrespnding Database Oracle Hme is autmatically picked up. The kfd binaries are lcated in the racle hme which are used by the discvery prcess. In the next step we discver the Infiniband netwrk. Specify ne f the Infiniband switches and prvide the switch credentials. We suggest using the nm2user credentials t verify cnnectivity. Fr any issues related t cnnectivity please refer t the Infiniband dcumentatin. Once cnnectivity is authenticated prceed t the next step. In this step we have intrduced the new prerequisite checks framewrk in EM12c Release 2. In this step we verify whether the KFOD executable are present and the database machine schematic files are present and readable by the EM Agent. These are very basic checks and shuld be successful fr mst installatins. Once satisfied click next t prceed t the next screen. 14

16 After examining the Infiniband Netwrk, the Cell cnfiguratin files and the Database Machine Schematic file (databasemachine.xml) all the Exadata cmpnents are discvered. Once yu have reviewed the IP addresses f each cmpnent discvered please prceed t the next sectin fr Agent assignments. This is als yur chance t deselect any cmpnents that yu may nt chse t mnitr as part f Exadata Discvery. 15

17 In this screen we assign the agents that we have deplyed earlier t mnitr individual cmpnents. We specify a mnitring agent and a backup agent in case the mnitring agent is subjected t a planned r unplanned utage. We can either chse t use the built-in algrithm fr agent assignment r manually verride the assignments. Yu may als chse t simply use a single agent t be the primary fr all cmpnents and anther ne as the backup agent. Once yu are satisfied with the entries prceed t the next step. 16

18 In this step we first prvide the Agent hst credentials. This is the user n the cmpute ndes that wns the Agent binaries. If the hst passwrd is the same then yu shuld use the first ptin r chse t use Different fr all agents in case the Agent wner passwrd is different in different ndes. It is recmmended t use the Test Cnnectin buttn t verify the passwrds yu have entered. Once the credentials are verified, click n Next. 17

19 In the Mnitring Credentials screen we cllect the credentials fr the Strage (Cell) Server rt user, Infiniband Switches and the ILOMs fr creating SSH equivalence. SSH equivalence enables passwrd less lgin int these cmpnents frm the cmpute ndes. Agents lgin t these cmpnents peridically t cllect different metrics fr mnitring. If the Strage servers rt passwrd is different chse the Different fr all cells ptin therwise use the same fr all cells ptin t validate cnnectivity. The Infiniband switch passwrd is prefilled based n the input earlier but if yu have different credentials fr each switch enter them separately. Finally the ILOM credentials are als cllected. We recmmend creating a separate mnitring user fr the ILOMs. The steps are described in the Befre yu begin sectin f this dcument. On validatin f each user accunt prceed t the next step. 18

20 The next screen guides yu thrugh cnfiguratin f SNMP subscriptins fr the Oracle Enterprise Manager 12c agents t receive SNMP traps. T setup this subscriptin rt credentials are needed fr the Infiniband switches (prir t Oracle Enterprise Manager 12c Release 2 yu will be prmpted t prvide rt passwrd fr the strage servers). As recmmended earlier verify the passwrds yu have entered using the Test Cnnectin buttn. Prceed t the next screen t enter the cmpnent prperties. 19

21 In this screen yu shuld see the Strage Server ILOM IP addresses. Make sure the addresses are crrect by manually verifying it against yur cnfiguratin. Yu are als required t enter the SNMP cmmunity string which is cmmnly set t public. It is recmmended t set the SNMP Timeut t 10 secnds. 20

22 Nw that all the infrmatin is cllected the final review screen helps yu t g thrugh them befre submitting the target fr prmtin. Yu als have the ptin t change the target names aut generated by the discvery prcess t a name mre cnvenient t remember. It is als recmmended that yu take a screen sht in case yu want t g back and check the mnitring agent assignments r IP addresses at a later pint in time. Once yu click n submit the target prmtin prcess kicks in. It takes a little while (abut a minute r tw) and n successful target prmtin we get the status screen. 21

23 At this pint yur discvery is cmplete. Yu will ntice a new menu ptin has been added t the targets menu if this is the first Oracle Exadata machine yu are discvering. 22

24 Click n the Oracle Exadata target and yu can g t the Oracle Exadata Schematic page frm the Oracle Exadata page. Pst Discvery Setups Cisc Ethernet Switch Cnfigure Cisc Ethernet Switch SNMP fr Oracle Enterprise Manager 12c Mnitring The Cisc Ethernet Switch needs t be cnfigured t allw the Agents that mnitr it t be able t bth pll the switch fr SNMP data and t receive SNMP traps frm the switch. T allw this, perfrm the fllwing steps (swapping the example switch name edbm01sw-ip with the name f the Cisc Ethernet Switch target being cnfigured) Lgin t the Cisc switch and enter Cnfigure mde: 23

25 # telnet edbm01sw-ip User Access Verificatin Passwrd: dm01sw-ip> enable Passwrd: dm01sw-ip# cnfigure terminal Enter cnfiguratin cmmands, ne per line. End with CNTL/Z. dm01sw-ip(cnfig)# Enable access t allw the Agents mnitring Cisc Switch targets t pll the switch. dm01sw-ip(cnfig)# access-list 1 permit <EMagentIPaddr> Issue the abve cmmand fr each Agent that mnitrs the Cisc switch, substituting the IP address f the Agent fr <EMagentIPaddr> Cnfigure the SNMP cmmunity. The SNMP cmmunity specified must match the value specified in the Oracle Enterprise Manager 12c Mnitring Cnfiguratin page fr the Cisc Switch target: and is generally 'public' dm01sw-ip(cnfig)# snmp-server cmmunity <cmmunity_string> r 1 Set the mnitring Agent as the lcatin where SNMP traps are delivered. Again, the SNMP cmmunity specified must match the value prvided during Oracle Enterprise Manager 12c Cisc Switch Management Plug-In setup: dm01sw-ip(cnfig)# snmp-server hst <EMagentIPaddr> versin 1 <cmmunity string> udp-prt <EMagentRecvltListenPrt> - Where EMagentRecvltListenPrt is the EMD_URL prt f the agent r the value f the prperty SnmpRecvletListenNIC frm the emd.prperties file f the agent, if specified. Issue the abve cmmand fr each Agent that mnitrs the Cisc switch, substituting the IP address f the Agent fr <EMagentIPaddr> Cnfigure the switch t send nly envirnmental mnitr SNMP traps: dm01sw-ip(cnfig)# snmp-server enable traps envmn Verify the settings and save the cnfiguratin: 24

26 dm01sw-ip(cnfig)# end dm01sw-ip# shw running-cnfig dm01sw-ip# cpy running-cnfig startup-cnfig Verify the Cisc Switch SNMP cnfiguratin fr Oracle Enterprise Manager 12c Mnitring T verify that SNMP is cnfigured and running fr the Cisc Ethernet Switch, use the snmpget cmmand line utility r an equivalent tl, as the agent sftware wner, frm the cmpute ndes whse agents are cnfigured t mnitr the Cisc Ethernet Switch. Running the fllwing cmmand shuld fetch and display data frm the Cisc switch: snmpget v 1 c <cmmunity_string> <hstname_f_cisc_switch> Fr example, $ snmpget v 1 c public edbm01sw-ip.us.racle.cm SNMPv2-SMI::enterprises = INTEGER: 14 Nte: If the Timeut message is displayed as a utput fr the abve cmmand, then it means that the Cisc switch is nt yet cnfigured fr SNMP. Pwer Distributin Unit Cnfigure PDU SNMP fr Oracle Enterprise Manager 12c Mnitring T enable Oracle Enterprise Manager t cllect metric data and raise events fr the PDU target, yu must cnfigure the PDU t accept SNMP queries frm the Agents that mnitr the PDU target. Als, apprpriate threshld values fr different Phase values needs t be set n the PDU. This sectin assumes that this is a first time cnfiguratin f the PDU. SNMP must be enabled and the trap sectin cmpleted. Granting SNMP access t a different mnitring Agent IP address is an example where nly the "Trap Hst Setup" sectin needs t be changed. Access the PDU netwrk interface via a brwser using the URL Click Net Cnfiguratin, and then lg in using rt credentials. Scrll dwn until yu reach the SNMP sectin f the frame. If the PDU is nt SNMP-enabled, select the SNMP Enable check bx then click Submit. Scrll t the "NMS" regin f the frame. 25

27 Add the IP address f each Oracle Enterprise Manager agent that mnitrs the PDU in the NMS table: IP: Enter the IP address f the first mnitring Agent Cmmunity: Enter "public" Click Submit. Fr details n cnfiguring the PDU threshlds settings, see Nte PDU Threshld Settings fr Oracle Exadata in My Oracle Supprt. Verify the PDU SNMP cnfiguratin fr Oracle Enterprise Manager 12c Mnitring It is pssible t verify that SNMP requests can be made by the agent sftware wner n the cmpute ndes whse agents are cnfigured t mnitr the PDU using the snmpget cmmand line utility r an equivalent tl. Running the fllwing cmmand shuld fetch and display data frm the PDU: snmpget v 1 c <cmmunity_string> <hstname_f_pdu> Fr example, # snmpget -v 1 -c public scab01-pdu

28 SNMPv2-SMI::enterprises = INTEGER: 255 Nte: If the Timeut message is displayed as a utput fr the abve cmmand, then it means that the PDU is nt yet cnfigured fr SNMP. KVM Cnfigure Keybard Vide and Muse SNMP fr Oracle Enterprise Manager 12c Mnitring The keybard vide and muse (KVM) needs t be cnfigured t send SMNP traps t the Agents that mnitr it. Cnfigure the KVM t send traps t the mnitring agent hst recvlet listening prt. This is nrmally the prt value f EMD_URL prperty frm $ORACLE_HOME/sysman/cnfig/emd.prperties, e.g: 3872 unless verridden by the prperty SnmpRecvletListenNIC in the same file. Lgin t the KVM management cnsle via a brwser using the URL: Click n the SNMP link under Unit View > Appliance > Appliance Settings in the lefthand navigatin bar. Select the Enable SNMP check bx and enter the apprpriate cmmunity name in the "Read" "Write" and "Trap" fields ("public", fr example). Click Save. Click the Destinatins link under Unit View > Appliance > Appliance Settings > Auditing > Destinatins in the left-hand navigatin bar. Enter the IP address f each Agent mnitring the KVM target. Click Save. 27

29 Verify KVM SNMP Cnfiguratin fr Oracle Enterprise Manager 12c Mnitring (Base SNMP Cnfiguratin) The KVM SNMP cnfiguratin can be verified by running snmptrapd within a terminal sessin: Fllw the belw steps n each mnitring Agent hst, lgged in as rt: Run the fllwing cmmand t temprarily stp the snmptrapd service: # service snmptrapd stp Rename the file /etc/snmp/snmptrapd.cnf t be /etc/snmp/snmptrapd.cnf_bk Run the fllwing cmmand t start the snmptrapd prcess in the terminal sessin: # snmptrapd -p 162 Rebt the KVM (t generate SNMP traps) - see next sectin fr details. The terminal where the snmptrapd cmmand was run shuld display the received trap which is generated by the KVM due t the rebt. If the abve step is cnfirmed, the KVM has been cnfigured crrectly. After the test has been perfrmed, rename the back-up file and restart the snmptrapd service: 1. Stp the snmptrapd cmmand that was started in step 3 abve (use Ctrl+c t stp the cmmand). 2. Rename the file /etc/snmp/snmptrapd.cnf_bk t be /etc/snmp/snmptrapd.cnf 3. Run the fllwing cmmand t start the snmptrapd prcess as a service nce again: # service snmptrapd start Verify KVM SNMP Cnfiguratin fr Oracle Enterprise Manager 12c Mnitring (SNMP frwarding t Agent) This sectin prvides the steps t validate that the mnitring Agent can receive SNMP traps that are generated by the KVM and cnvert the received traps t Enterprise Manager events. 1. Lg in t the KVM. 2. On the left side f the screen under Unit View > Appliance, click Overview. 3. Click Rebt. 28

30 4. Cnfirm KVM rebt by clicking OK in the windw that asks if yu want t cntinue. 5. In the Oracle Enterprise Manager 12c cnsle, g t the KVM target page. An Incident shuld be displayed fr the KVM rebt event in the Incidents and Prblems sectin f the page. Discvering the Cluster and Oracle Databases Once Oracle Exadata has been discvered, the next step wuld be t discver the cluster and the databases running n this machine. Navigate t Setup Add targets Add targets manually; select the ptin Add Nn-Hst Targets Using Guided Prcess and click n the Add Using Guided Discvery buttn. 29

31 In the fllwing screen enter the details f the cluster Only the Cluster Name is mandatry but fr the sake f cmpleteness yu shuld input the SCAN Name, SCAN Prt, ONS Prt and als the selected hsts. Since this is a Quarter Rack we have tw cmpute ndes in the cluster. Click n the Add buttn and after a minute the cluster will be added t the list f targets. After the cluster is added it is nw turn f the database targets which include the databases, listeners and the ASM instances. Navigate t Setup Add Targets Add Targets manually and nw select Oracle Database, Listener and Autmatic Strage Management frm the drpdwn. 30

32 Click n Add Using Guided Discvery buttn. In the next screen yu will be prmpted t select ne f the agents n the cmpute ndes. After selecting the agent n the first cmpute nde click n select and then click next. Since this hst is part f a cluster the next screen prvides the ptin f discvering databases either n this hst r n all hsts in the cluster. Select the latter as yu want t discver all databases n Oracle Exadata. 31

33 Click n the Cntinue buttn and nw the agent searches fr all databases running n this cluster. Sn all databases running n Oracle Exadata are discvered. In the next step yu need t prvide the mnitring credentials. This is the database user accunt that will be used t mnitr the databases. Click n the setup icn n the extreme right. 32

34 Prvide the Mnitr passwrd and click n test cnnectin n the right. Ntice yu d nt need t input the passwrd fr each instance individually. The passwrd is accepted at the cluster level. If yu wish t change the name f the database yu can change the name and then click Next. This is the review screen. Once yu have reviewed the infrmatin click OK t prceed t the next step. 33

35 Repeat the abve steps fr all the discvered databases including the ASM instances. Once all the passwrds are prvided, yu can click n the Finish buttn t cmplete the discvery. In the next screen yu will be prmpted t input additinal target prperties. This is an ptinal step and can be skipped if yu have nt decided n these values. 34

36 Click Next. Once discvery is cmplete and the target infrmatin saved in the repsitry yu will get the fllwing cnfirmatin screen. Nw yu can navigate t Targets Databases t check the status f all discvery targets. The All targets page (Targets All targets) will list the status f all the targets discvered in this prcess. 35

37 Cnclusin Discvering Oracle Exadata in Oracle Enterprise Manager 12c is nw mre than 10 times faster frm previus versin f Oracle Enterprise Manager helping administratrs save bth valuable time and effrt. The typically discvery prcess nw takes as little as 15 t 30 minutes if all the prerequisite steps are cmpleted befre yu launch the discvery prcess. T learn mre abut Oracle Exadata manageability, be sure t watch the fllwing: VIDEO: Managing Oracle Exadata with Oracle Enterprise Manager 12c VIDEO: Oracle Enterprise Manager 12c Mnitr an Oracle Exadata Envirnment 36

38 Oracle Exadata Discvery Ckbk June, 2012 Authr: Deba Chatterjee Cntributing Authrs: Faruk Abushaban, Jim Viscusi, Andrew Bullch Cpyright 2012, Oracle and/r its affiliates. All rights reserved. This dcument is prvided fr infrmatin purpses nly and the cntents heref are subject t change withut ntice. This dcument is nt warranted t be errr-free, nr subject t any ther warranties r cnditins, whether expressed rally r implied in law, including implied warranties and cnditins f merchantability r fitness fr a particular purpse. We specifically disclaim any liability with respect t this dcument and n cntractual bligatins are frmed either directly r indirectly by this dcument. This dcument may nt be reprduced r transmitted in any frm r by any means, electrnic r mechanical, fr any purpse, withut ur prir written permissin. Oracle Crpratin Wrld Headquarters 500 Oracle Parkway Redwd Shres, CA U.S.A. Wrldwide Inquiries: Phne: Fax: Oracle and Java are registered trademarks f Oracle and/r its affiliates. Other names may be trademarks f their respective wners. AMD, Optern, the AMD lg, and the AMD Optern lg are trademarks r registered trademarks f Advanced Micr Devices. Intel and Intel Xen are trademarks r registered trademarks f Intel Crpratin. All SPARC trademarks are used under license and are trademarks r registered trademarks f SPARC Internatinal, Inc. UNIX is a registered trademark licensed thrugh X/Open Cmpany, Ltd racle.cm