Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide 11g Release 1 (11.1.0.1.0) Part Number E16847-10 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can use the nfsagentinstall
script to install Oracle Management Agents (Management Agent) with the help of a central, shared Oracle home of an existing Management Agent. In particular, this section covers the following:
If you want to install additional Management Agents on hosts that share a mounted drive where a Management Agent is already installed, then the best option is to use the software binaries of the shared Oracle home from the mounted drive and configure the remote hosts to be managed by that Management Agent, thus capitalizing on the NFS visibility and saving hard disk space on the remote hosts. You can achieve this in GUI as well as in silent mode.
While the Shared Agent Deployment Wizard helps you install such Management Agents in GUI mode, the nfsagentinstall
script helps you install in silent mode.
Much like the Shared Agent Deployment Wizard, the nfsagentinstall uses the software binaries from the shared Oracle home, and configures an EMSTATE
directory on each of the remote destination hosts for storing configuration files such as emd.properties
, targets.xml
, log files
, and so on. For more information about the EMSTATE
directory, see What Is EMSTATE Directory?.
The Management Agent that shares its software binaries, in this context, is called the Master Agent, and the one that is configured with an EMSTATE
directory on the remote host is called the Shared Agents or NFS Agents. Technically, the nfsagentinstall
script does not install a Management Agent; it only uses the software binaries from the shared Oracle home and configures an EMSTATE
directory on each of the remote hosts.
However, unlike the Shared Agent Deployment Wizard, the nfsagentinstall
script must be run only from a destination host, and at a given time, only one Management Agent can be installed at a given time. Therefore, if you want to install only a few Management Agents, then use The nfsagentinstall script.
Before you begin, keep in mind the points described in Before You Begin.
Before installing the Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 15-1 Prerequisites for Installing Oracle Management Agent Using nfsagentinstall Script
Requirement | Description | Yes/No |
---|---|---|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements as described in Appendix A, "Meeting Hardware Requirements". |
|
Operating System Requirements |
Ensure that you install the Management Agent only on certified operating systems as mentioned in My Oracle Support note 412431.1. |
|
User and Operating System Group Requirement |
Ensure that the destination host where you want to install the Management Agent has the appropriate users and operating system groups created. For information about creating operating system groups and users, see Appendix C, "Creating Operating System Groups and Users Requirements". |
|
Temporary Directory Space Requirements |
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. For example, |
|
Central Inventory Requirements |
Ensure that you allocate 100 MB of space for the central inventory directory. Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1. |
|
EMSTATE Directory Requirements |
Ensure that the installation base directory you specify is empty and has write permission. |
|
Existing Management Agent Software Requirements |
Ensure that you install a Management Agent (Master Agent) on the shared, mounted location. To install a Management Agent on the shared, mounted location, you can use any of the other Management Agent Deployment methods described in this guide. |
|
Existing Management Agent Status Requirements |
Ensure that the existing Management Agent (Master Agent) on the shared, mounted location is shut down always and not used for monitoring any targets. This installation is purely for sharing the software binaries with the Shared Agents. |
|
|
If the shared Management Agent is not the first Oracle product installation but its Oracle home is shared, then ensure that you verify the If
|
|
Software Availability Requirements |
Although the installation actually is done using a shared Oracle home of an installed Management Agent that might be running on a different host, the By default, the software for Oracle Management Agent 11g Release 1 is available on the host where Oracle Management Service 11g Release 1 is running. Note that this Management Agent software is for the platform on which the OMS is running. Therefore, if you want to install Oracle Management Agent 11g Release 1 on a platform that is the same as the one on which the OMS is running, then you already meet this prerequisite; you do not have to take any action. However, if you want to install Oracle Management Agent 11g Release 1 on a platform that is different from the one on which the OMS is running, then ensure that you download the Management Agent software for that platform. For more information about downloading the Management Agent software, see Procuring Oracle Management Agent Software. |
|
Shared, Mounted Location Requirements |
Ensure that the shared, mounted location is accessible from all destination hosts where you want to install additional Management Agents. |
|
Destination Host Credentials Requirements |
Ensure that the destination hosts have the same operating system credentials and file system structure, including the following:
|
|
|
If the destination host and the host on which OMS is running belong to different network domains, then ensure that you update the For example, if the fully-qualified host name is
|
|
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is user1, and user installing the Management Agent is user2, then ensure that user1 and user2 belong to the same group, and they have read and write access to the inventory. |
|
Permission Requirements |
|
|
Oracle Inventory Location Requirements |
Ensure that the Oracle Inventory ( |
|
SUDO Privilege Requirement |
Ensure that you have SUDO privileges to run To verify whether you have SUDO privileges to run these files, access the
|
|
SUDOERS File Configuration Requirements |
Ensure that you configure /etc/sudoers file so that while running a command using SUDO, you are always prompted for a password. If /etc/sudoers file is configured in such a way that SUDO never prompts for a password, then a directory with the host password as the title gets created in the invoking users home directory. |
|
Default SSH Port Requirements |
Ensure that the SSH daemon is running on the default port (that is, 22) on all the destination hosts. If the port is a non-default port, that is, any port other than 22, then update the SSH_PORT property in the following file present in the OMS Instance Base:
|
|
PubkeyAuthentication Parameter Requirements |
Ensure that the To verify the value of this parameter, run the following command:
For example, grep PubkeyAuthentication /etc/ssh/sshd_config The result of this command must be Yes. If the result is No, then edit the |
To install a Management Agent using the nfsagentinstall
script, follow these steps:
On one of the destination hosts, navigate to the following directory (the shared Oracle home that is visible on this destination host):
<ORACLE_HOME>/sysman/install/
Run the following command:
./nfsagentinstall -s <absolute_path_to_EMSTATE_directory_location> [ -p <customized_port_number>] [ -i <invPtrLoc> inventory_pointer_location] [-t Skip discovery]
Note:
In this command,-p
, -i
, and -t
are optional arguments.If AGENT_INSTALL_PASSWORD
parameter is not set in the nfsagentinstall
script, then you are prompted to specify the agent registration password to secure the Management Agent.
(Only for UNIX Operating Systems) If this Management Agent installation is the first Oracle product installation on this host, then the nfsagentinstall
script prompts you to run the following scripts manually:
If this is the first Oracle product you just installed on the host, then run the oraInstRoot.sh
script from the inventory location specified in the oraInst.loc file that is available in the Oracle home of the Management Agent.
For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:
$HOME/oraInventory/oraInstRoot.sh
If you are not a root user, then use SUDO to change to a root user. For example, run the following command:
/usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh
Run the root.sh script from the Oracle home of the Management Agent:
<Oracle_Home>/root.sh
If you are not a root user, then use SUDO to change to a root user. For example, run the following command:
/usr/local/bin/sudo /scratch/OracleHomes/agent11g/root.sh
Repeat Step (1) to Step (3) on the remaining hosts where you want to install the Management Agent.
Note:
If the installation fails, then review the log files described in Appendix L, "Installation and Configuration Log Files".After you install the Management Agent, follow these steps outlined in After You Install.