Securing oracle agents

These are the days of Oracle Grid.
Recently i had to install Oracle agents on my new RAC nodes to manage them using the Grid Control.
I installed Oracle Agent 10.2.0.1 on my new nodes to talk to my 10.2.0.2 OMS.
Though the agent was supposed to talk to the OMS by itself after the installation, it did not.
I could not see the details of the nodes in the Grid Control.

Below is how i figured what had gone wrong and how it was fixed.

From the Agent_Home/bin:

myjpsuolicdbt01 [SHCL1DR1]$ ./emctl upload
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
—————————————————————
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..
myjpsuolicdbt01 [SHCL1DR1]$

Seems like the agent could not talk to the OMS.
Since i had installed the Agent in Unsecure mode, thought of checking whether the OMS is secured or not.

From the Agent_Home/bin:
myjpsuolicdbt01 [SHCL1DR1]$ ./emctl status agent -secure
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
Checking the security status of the Agent at location set in /u01/app/oracle/product/agent10g/Done.
Agent is unsecure at HTTP Port 3872.
Checking the security status of the OMS at
http://myjpsufuchdbd01:4889/em/upload/…  Done.
OMS is secure on HTTPS Port 1159
myjpsuolicdbt01 [SHCL1DR1]$

Voila!!!! OMS is Secure and my Agent is not secured and that was the reason Agent could not talk to the OMS.

So i secured the Agent by

myjpsuolicdbt01 [SHCL1DR1]$ cd /u01/app/oracle/product/agent10g/bin
myjpsuolicdbt01 [SHCL1DR1]$ ./emctl stop agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
Agent is Not Running
myjpsuolicdbt01 [SHCL1DR1]$
myjpsuolicdbt01 [SHCL1DR1]$
myjpsuolicdbt01 [SHCL1DR1]$ ./emctl secure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
Enter Agent Registration password :
Agent is already stopped…   Done.
Securing agent…   Started.
Requesting an HTTPS Upload URL from the OMS…   Done.
Requesting an Oracle Wallet and Agent Key from the OMS…   Done.
Check if HTTPS Upload URL is accessible from the agent…   Done.
Configuring Agent for HTTPS in CENTRAL_AGENT mode…   Done.
EMD_URL set in /u01/app/oracle/product/agent10g/myjpsuolicdbt01/sysman/config/em
Securing agent…   Successful.
myjpsuolicdbt01 [SHCL1DR1]$

The above asks for the password that was used while setting up the OMS. Since i didn’t remember the password i follwed Metalink Note:433828.1 and added a new password in  Setup->Registration Passwords

myjpsuolicdbt01 [SHCL1DR1]$ ./emctl status agent -secure
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
Checking the security status of the Agent at location set in /u01/app/oracle/pro              Done.
Agent is secure at HTTPS Port 3872.
Checking the security status of the OMS at
http://myjpsufuchdbd01:4889/em/upload
OMS is secure on HTTPS Port 1159
myjpsuolicdbt01 [SHCL1DR1]$

 

Advertisements

5 thoughts on “Securing oracle agents

  1. Did you install them in unsecure mode in the first place intentionally or not?

    What is the installation default? I need to check my systems tomorrow when I get to work

    Good write up.

    That is what I like to see in a blog. A small problem and a well-documented solution.

    John

  2. Pingback: Index « My confrontations with oracle

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s