INSTALLATION OF MASS DEPLOYMENT AGENT –
Once GRID CONTROL is installed on a machine – it is possible to deploy the Grid control agent onto various machines you want added to the GRID.
In this example the agent is deployed from the GRID CONTROL machine to DEVU007 box from PRDU010 box where GRID CONTROL OMS/DATABASE RESIDE.
Space required for only agent home- 1.6 gb
Pre-reqs : cd $OMS_HOME/sysman/prov/resources/scripts > cd /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts
./sshConnectivity.sh -hosts "devu007.bankwest.com" -user oracle - Here DEVU007 is target machine where agent will be deployed using oracle unix login.
The following envrionment would be used ORACLE_HOME = /u01/oracle/product/10.2.0/grid/oms10g JAR_LOC = /u01/oracle/product/10.2.0/grid/oms10g/oui/jlib SSH_LOC = /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/agentpush/jlib OUI_LOC = /u01/oracle/product/10.2.0/grid/oms10g/oui PROP_LOC = /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources JAVAHOME = /u01/oracle/product/10.2.0/grid/oms10g/jdk
Checking if the remote hosts are reachable. Remote host reachability check succeeded. All hosts are reachable. Proceeding further...
NOTE : As part of the setup procedure, this script will use ssh and scp to copy files between the local host and the remote hosts. You may be prompted for the password during the execution of the script. AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE directories.
Do you want to continue and let the script make the above mentioned changes (yes/no)? yes
If The files containing the client public and private keys already exist on the local host. The current private key may or may not have a passphrase associated with it. In case you remember the passphrase and do not want to re-run ssh-keygen, type 'no'. If you type 'yes', the script will remove the old private/public key files and, any previous SSH user setups would be reset. Enter 'yes', 'no' yes
Enter the password: - oracle password Enter the passphrase: - Just enter Logfile Location : /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts/SSHSetup Doing SSHSetup... Please be patient, this operation might take sometime...Dont press Ctrl+C...
Local Platform:- AIX
------Verifying SSH setup ======The script will now run the date command on the remote nodes using ssh to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP, THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR PASSWORDS. If you see any output other than date or are prompted for the password, ssh is not setup correctly and you will need to resolve the issue and set up ssh again. The possible causes for failure could be: 1. The server settings in /etc/ssh/sshd_config file do not allow ssh for user oracle. 2. The server may have disabled public key based authentication. 3. The client public key on the server may be outdated. 4. /u01/oracle or /u01/oracle/.ssh on the remote host may not be owned by oracle. 5. User may not have passed -shared option for shared remote users or may be passing the -shared option for non-shared remote users. 6. If there is output in addition to the date, but no password is asked, it may be a security alert shown as part of company policy. Append the additional text to the
Check with following commands – rcatp:/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts> ssh devu007 date Tue Jul 22 08:49:17 WAUST 2008 rcatp:/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts> ssh devu007 df -k Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 1023884 3% 2098 1% / /dev/hd2 2097152 1194088 44% 26471 9% /usr /dev/hd9var 4194304 4175300 1% 393 1% /var /dev/hd3 2097152 2096452 1% 22 1% /tmp /dev/hd1 2097152 1855316 12% 138 1% /home /proc - - - - - /proc /dev/hd10opt 1048576 980716 7% 1186 1% /opt /dev/bmclv 1048576 734596 30% 4019 3% /opt/bmc /dev/mksysb_lv 4194304 3084832 27% 6 1% /mksysb_images /dev/jp1pc_lv 524288 523880 1% 4 1% /opt/jp1pc /dev/u01_lv 20971520 7363676 65% 78639 5% /u01 /dev/u02_lv 41943040 29646092 30% 77 1% /u02 /dev/u03_lv 20971520 18870044 11% 43 1% /u03 /dev/u04_lv 5242880 4944184 6% 537 1% /u04 rcatp:/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts>
Before running stuff below make sure of following :
This content is intended for administrators who are responsible for installing the Oracle Management Agent on target servers.
How to Deploy the Agent Using the Agent Push Installation Method
10g R2 Agent Push Steps :
1. Make sure PubkeyAuthentication is enabled. grep PubkeyAuthentication /etc/ssh/sshd_config This should return "yes"
If it returns "no", Edit File /etc/ssh/sshd_config and change From: PubkeyAuthentication no To: PubkeyAuthentication yes Then restart the sshd Deamon.
If this PubkeyAuthentication is disabled then ssh will not be able to connect to the remote machine from OMS box .
As ssh make use of public key authentication to log into machine, SSH configuration will not succeed. After pushing your Agent you can revert back the changes.
If under /etc/ssh only sshd_config.bak exists then ask the root owner to
Copy this file as sshd_config and also unhash this line in the newly created sshd_config : oms:/etc/ssh> grep PubkeyAuthentication /etc/ssh/sshd_config.bak #PubkeyAuthentication yes oms:/etc/ssh>
Check the zip path in the target –
Ex on DEVU007
Which zip
/usr/bin/zip
Now on PRDU010 -
Go to OMS_HOME/sysman/agent_download/10.2.0.4.0/aix/agentdeploy ie - /u01/oracle/product/10.2.0/grid/oms10g/sysman/agent_download/10.2.0.4.0/aix/agentdeploy vi sPaths.properties
Search for ZIP path and change it to /usr/bin/zip
If the ZIP path is different on target – then make sure it is changed here in the sPaths.properties file to match the path on the target machine.
Then start agent installation .
CLICK ON INSTALL AGENT
Click on Fresh install
Enter Host name- devu007 in Provide Host List
Leave Port blank Additional parameters enter -z Australia/Perth
Enter oracle user and password- both user and password should be same on source and target.
Enter OMS password – the password when you set up GRID CONTROL on the PRDU010 machine.
Click on CONTINUE.
ACCEPT and continue.
If installation fails after creation of agent10g directory – troubleshoot the issue : cd $AGENT_HOME/sysman/config vi emd.properties
Make sure EMD_URL points to an available port- usually 3872 .
Check with netstat – a |grep 3872 to make sure it is not in use….
EMD_URL=https://devu007.bankwest.com:3872/emd/main/
Make sure entry for time Zone exists at bottom – this has to be added usually – agentTZRegion=Australia/Perth – Use region as per your region.
Then start agent cd $AGENT_HOME/bin - ./emctl start agent.
If agent still does not start or if it starts and does not upload files -
Stop agent - cd /u01/oracle/agent10g/bin
./emctl stop agent cd /u01/oracle/agent10g/sysman/emd rm agntstmp.txt rm lastupld.xml cp -fR /u01/oracle/agent10g/sysman/emd/upload /u01/oracle/agent10g/sysman/emd/upload.bak cp -fR /u01/orahbosa/agent10g/sysman/emd/upload /u01/orahbosa/agent10g/sysman/emd/upload.bak cd /u01/oracle/agent10g/sysman/emd/upload rm * cd /u01/oracle/agent10g/bin
./emctl start agent
./emct status agent devu007 $ ./emctl status agent Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0. Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. ------Agent Version : 10.2.0.4.0 OMS Version : 10.2.0.4.0 Protocol Version : 10.2.0.4.0 Agent Home : /u01/oracle/agent10g Agent binaries : /u01/oracle/agent10g Agent Process ID : 2056316 Parent Process ID : 1785856 Agent URL : https://devu007.bankwest.com:3872/emd/main/ Repository URL : https://prdu010.bankwest.com:1159/em/upload Started at : 2008-09-08 11:20:48 Started by user : oracle Last Reload : 2008-09-08 11:28:48 Last successful upload : 2008-09-08 11:45:58 Total Megabytes of XML files uploaded so far : 11.27 Number of XML files pending upload : 1 Size of XML files pending upload(MB) : 0.00 Available disk space on upload filesystem : 9.99% Last successful heartbeat to OMS : 2008-09-08 11:46:02 ------Agent is Running and Ready devu007 $