In this post I want to share the required steps to discover ExaCC or ExaCS in Oracle Enterprise Manager (EM). I’ll provide as much detail as possible.
- Make sure your EM is at least on 13.5 RU 16. If not, please apply RU 16 to EM. Follow this link if you want to know how to patch EM. HERE!
- You need to designate a “monitoring” agent for the discovery. Is recommended that this agent sits outside your Exadata rack and has access to the OCI REST APIs. More information HERE!
- Make sure this agent has both the Database and the Exadata plugins deployed and is patched to the same RU level as the OMS. HERE!
- The agent must be able to reach the OCI REST APIs. There are 3 ways to achieve this.
a) You can use a Proxy
b) You can use the OCI Management Gateway
c) You can have direct network connection
Below is a list of APIs that you will need access to:
Either grant access to (*.oci.oraclecloud.com) or individual URLS:
https://query.<oci_region>.oci.oraclecloud.com
https://identity.<oci_region>.oci.oraclecloud.com
https://database.<oci_region>.oci.oraclecloud.com
https://wss.exacc.<oci_region>.oci.oraclecloud.com
https://management-agent.<oci_region>.oci.oraclecloud.com
https://certificatesmanagement.<oci_region>.oci.oraclecloud.com
https://certificates.<oci_region>.oci.oraclecloud.com
https://telemetry-ingestion.<oci_region>.oci.oraclecloud.com
https://auth.<oci_region>.oci.oraclecloud.com
https://objectstorage.<oci_region>.oci.oraclecloud.com
You may also test that connectivity by executing:
$ curl -v https://query.<oci_region>.oci.oraclecloud.com - Create or use an OCI account that has access to read your Exadata racks. These are the policies I have used:
allow group <domain/group name> to read database-family in compartment <compartment name>
You can find more information about the required policies HERE! - Setup API Keys for authentication. Please follow instructions in the MOS note below:
EM13.5: Manage OCI Connectivity Named Credentials Test Failed with Invalid Private Key. (Doc ID 2792126.1) - Create an EM Named Credential using the API Keys created on the previous step. More details HERE!
- You also need the proper Storage Server credentials. If you don specify them during the discovery process, Storage Server targets will not be discovered. Instructions on how to retrieve this credential can be found HERE!
If you can’t retrieve these credentials, please open a Service Request with support. - Discover your Exadata Infrastructure following the discovery wizard. More information HERE!
After finishing the discovery, you should have your Exadata Cloud target in EM. Please wait between 15 to 20 minutes for the target information to be populated.
If your network setup does not allow direct connectivity to the OCI REST APIs then you will have to use an internal Proxy or use the OCI Management Gateway. More information about the OCI Management Gateway can be found HERE!
There’s also a very good post from Simone about setting up the Management Gateway for the EM agents.
https://blogs.oracle.com/observability/post/setup-oem-agents-cloud-mgmt-gw
Update:
You will also have to modify 2 parameters. One at the OMS level and one at the agent level. Please follow below MOS notes:
OEM 13c : SSH Key Credential Test On a Host Target Fails With “Remote operation timed out.” (Doc ID 2415262.1)
EM 13.2: Agent Patching From EM Console Fails With Error “concurrent job tasks limit (50) has been reached” (Doc ID 2476803.1)
Thanks,
Alfredo