•10g em grid control mass deployment using agent push method.doc

7/29/2019 10g EM Grid Control Mass Deployment using Agent Push Method.doc

1/17

INSTALLATION OF MASS DEPLOYMENT AGENT

Once GRID CONTROL is installed on a machine it is possible to deploy the Grid controlagent onto various machines you want added to the GRID.

In this example the agent is deployed from the GRID CONTROL machine to DEVU007 boxfrom 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 istarget machine where agent will be deployed using oracle unix login.

The following envrionment would be usedORACLE_HOME = /u01/oracle/product/10.2.0/grid/oms10gJAR_LOC = /u01/oracle/product/10.2.0/grid/oms10g/oui/jlibSSH_LOC = /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/agentpush/jlibOUI_LOC = /u01/oracle/product/10.2.0/grid/oms10g/ouiPROP_LOC = /u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resourcesJAVAHOME = /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 copyfiles between the local host and the remote hosts. You may be prompted forthe password during the execution of the script.AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORYAND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TOTHESEdirectories.

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. Thecurrent private key may or may not have a passphrase associated with it. In case you rememberthe passphrase and do not want to re-run ssh-keygen, type 'no'. If you type 'yes', the script willremove the old private/public key files and, any previous SSH user setups would be reset.Enter 'yes', 'no'yes

Enter the password: - oracle passwordEnter the passphrase: - Just enterLogfile Location :


2/17

/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts/SSHSetupDoing 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 sshto 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 ASKFORPASSWORDS. If you see any output other than date or are prompted for thepassword, ssh is not setup correctly and you will need to resolve theissue 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 sshfor 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 ormay 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 theadditional text to the /sysman/prov/resources/ignoreMessages.txt file.--------------------------------------------------------------------------devu007.bankwest.com:--Running /usr/bin/ssh -x -l oracle devu007.bankwest.com date to verify SSH connectivity has beensetup from local host to devu007.bankwest.com.IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IFYOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN

SUCCESSFUL. Please note that being prompted for a passphrase may be OK but beingprompted for a password is ERROR.Tue Jul 22 08:48:11 WAUST 2008------------------------------------------------------------------------SSH verification complete.rcatp:/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts>

Check with following commands

rcatp:/u01/oracle/product/10.2.0/grid/oms10g/sysman/prov/resources/scripts> ssh devu007 dateTue 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


3/17

/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% /u04rcatp:/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 theOracle 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_configThis should return "yes"

If it returns "no", Edit File /etc/ssh/sshd_config and changeFrom: PubkeyAuthentication no

To: PubkeyAuthentication yesThen restart the sshd Deamon.

If this PubkeyAuthentication is disabled then ssh will not be able to connect to theremote machine from OMS box .

As ssh make use of public key authentication to log into machine, SSH configurationwill 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 createdsshd_config :

oms:/etc/ssh> grep PubkeyAuthentication /etc/ssh/sshd_config.bak#PubkeyAuthentication yesoms:/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


4/17

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.propertiesfile to match the path on the target machine.

Then start agent installation .


5/17


6/17

CLICK ON INSTALL AGENT


7/17


8/17

Click on Fresh install


9/17


10/17

Enter Host name- devu007 in Provide Host List


11/17


12/17

Leave Port blankAdditional parameters enter -z Australia/PerthEnter 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 PRDU010machine.

Click on CONTINUE.


13/17


14/17

ACCEPT and continue.


15/17


16/17

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


17/17

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 agentOracle 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.0OMS Version : 10.2.0.4.0Protocol Version : 10.2.0.4.0Agent Home : /u01/oracle/agent10gAgent binaries : /u01/oracle/agent10gAgent Process ID : 2056316Parent Process ID : 1785856Agent URL : https://devu007.bankwest.com:3872/emd/main/Repository URL : https://prdu010.bankwest.com:1159/em/uploadStarted at : 2008-09-08 11:20:48Started by user : oracleLast Reload : 2008-09-08 11:28:48Last successful upload : 2008-09-08 11:45:58

Total Megabytes of XML files uploaded so far : 11.27Number of XML files pending upload : 1Size 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 Readydevu007 $

•10g em grid control mass deployment using agent push method.doc

Documents