- Monitoring an Oracle Private Cloud Appliance
- Discover the Private Cloud Appliance
- Installing the Management Agent on Private Cloud Appliance
Installing the Management Agent on Private Cloud Appliance
Before discovering the Oracle Private Cloud Appliance in Enterprise Manager, you must first prepare the appliance and install a Management Agent. Follow the steps below to properly configure your Oracle Private Cloud Appliance:
- Using the
root
account change theoracle
user password to a known password on both management nodes of the Oracle Private Cloud Appliance Rack:passwd oracle
- Verify the VIP and public Enterprise Manager IP are in the
/etc/hosts
file on both management nodes and on the Enterprise Manager host:YOUR.VIP vip-host1.example.com vca1-vip-vip YOUR.EMIP em-host1.example.com em01
- On the active management node, using the
root
user, create an agent directory on the shared NFS directory. The sharednfs
directory is required for both availability and failover purposes.mkdir /nfs/shared_storage/oemagent chown oracle:dba /nfs/shared_storage/oemagent
Note:
- By default, the Enterprise Manager agent port 3872 is pre-populated by Oracle Private Cloud Appliance software. If you use this default Enterprise Manager agent port 3872 for pushing the agent, then this step is not needed. If a non-default port is used for the Enterprise Manager agent, the steps do need to be executed on standby management node.
- If the agent port is different from the default port (3872), you must configure the firewall for that particular port, as 3872 is set by default in the Oracle Private Cloud Appliance management node setup.
- Open an Enterprise Manager agent port in the firewall using the
root
user by running the following command. Make sure you choose the same port while pushing the agent in step 5:For Oracle Private Cloud Appliance 2.4.4 and above:firewall-cmd --add-port <agent_port>/tcp --permanent firewall-cmd --reload
For Oracle Private Cloud Appliance 2.4.3 and below:
Whereiptables -I INPUT <line_num> -m state --state NEW -m tcp -p tcp --dport <agent_port> -j ACCEPT
line_num
is any line number before the rule to block all traffic. To obtain theline_num
value tun the following commands using theroot
user:service iptables save service iptables reload
- Push the Management Agent from the Oracle Management Server (OMS). From Enterprise Manager Cloud Control:
- From the Setup menu, select Add Target, then select Add Targets Manually.
- In the Add Host Targets area of the Add Targets Manually page, click Install Agent on Host. The Add Host wizard will begin.
- Add a Host and Platform. On this page, click Add and select
Manually. Enter a host name (fully qualified) in the Host
field. This name should be the fully qualified virtual IP host name of
the Oracle Private Cloud Appliance rack for
deploying the agent. Select Linux x86-64 from the Platform
menu. Click Next.
- On the Installation Details page, enter the
following information:
- Installation Base Directory:
/nfs/shared_storage/oemagent
- Instance Directory:
/nfs/shared_storage/oemagent/agent_inst
(This value is automatically completed based on the Installation Base Directory input.) - Named Credential:
<agent_username>
Note:
If this is the first time you are adding a credential, an add icon () appears. Click this icon for a dialogue box that prompts for the credentials of the agent user (
oracle
/password for example).Create a Named Credential for the
oracle
user with the password you set in step 1 above.Once created, that credential and any other credentials that have already been added to Enterprise Manager will be available for selection. For an existing installation of an Enterprise Manager, a user may already have the necessary credentials available for selection for Oracle Private Cloud Appliance discovery.
This root privileges field is located in between Name credential and Privileged Delegation Setting in Enterprise Manager 13.5.
- Privileged Delegation Setting: Leave the
default. By default, this field is populated with
/usr/bin/sudo -u %RUNAS% %COMMAND%
- Port: By default, this field is populated
with
3872
. If you've not used the default port3872
, then ensure to specify the port number. - Preinstallation Script: Leave this field blank.
- Postinstallation Script: Leave this field blank.
- Additional Parameters: Leave this field blank.
Once the fields are complete, click Next.
- Installation Base Directory:
- On the Review page, review the details of the host information. Click Deploy Agent.
Note:
During the agent install as a non privileged user, the user interface will display a warning and state that privilege scripts need to be run manually as the root user. Select Continue All Hosts and once the agent install has completed, run the following privileged scripts as theroot
user on the Oracle Private Cloud Appliance active management node:/nfs/shared_storage/oemagent/agent_13.5.0.0.0/root.sh
/u01/app/oraInventory/orainstRoot.sh
For more information, see Meeting the Generic Prerequisites for Installing Standalone Management Agents Using Add Host Targets Wizard or EM CLI
- On the active management node, set the emd property
AgentListenOnAllNICs
to false by running following command with theoracle
user:/nfs/shared_storage/oemagent/agent_inst/bin/emctl setproperty agent -name "AgentListenOnAllNICs" -value "false"
- On the active management node, run the following command with the
oracle
user:/nfs/shared_storage/oemagent/agent_inst/bin/emctl setproperty agent -allow_new -name _disableLoadDPFromCache -value true
- On the active management node, run the following command with the
oracle
user:/nfs/shared_storage/oemagent/agent_inst/bin/emctl setproperty agent -name preferIPv6Addresses -value false
- Using the
root
account copy the following agent installation files to the passive management node (ovcamn06r1
is passive in this example):scp /etc/init.d/gcstartup root@ovcamn06r1:/etc/init.d/ rsync -og /etc/oragchomelist root@ovcamn06r1:/etc/oragchomelist rsync -rog /u01/app/oraInventory/ oracle@ovcamn06r1:/u01/app/oraInventory/
- On the active management node using the
root
account remove allgc rc.d
links (no startup of agent on startup):for x in `find /etc/rc.*/rc* | grep gcstart`; do rm $x; done
- Restart the Enterprise Manager agent on the active management node as
oracle
from the agent's emctl command:/nfs/shared_storage/oemagent/agent_inst/bin/emctl stop agent /nfs/shared_storage/oemagent/agent_inst/bin/emctl start agent