Hello. Welcome to this presentation that shows how to check the tinyproxy configuration on
the Oracle Private Cloud Appliance management nodes, supporting Oracle Enterprise Manager
Cloud Control.
Under some circumstances, a request to deploy a server through the Oracle Enterprise Manager
Cloud Control Self Service Portal can fail because the particular port used in the process
is closed. Tinyproxy, which is a lightweight proxy server, can be configured to avoid this
failure.
It is a good practice to check the tinyproxy configuration when setting up Oracle Enterprise
Manager. First, you determine the connection port used on the server running Oracle Enterprise
Manager. Then make sure the port is configured for communication on both Oracle Private Cloud
Appliance management nodes.
Let's see how to take care of this task of internal network configuration.
I'm logged into the Oracle Enterprise Manager host server as the user oracle. We want to
see the HTTPS Upload Port configured for the Oracle Management System. To do this, enter
an emctl command line interface - or CLI - command.
The location of emctl might be different for your installation, depending on where the
Oracle Enterprise Manager was installed. However, for this installation, I'll enter the full
path to emctl.
/u01/app/EM/Middleware/bin/, the command emctl status oms, -details -sysman_pwd and the sysman
user's password. And pipe the output to grep "HTTPS Upload Port".
The result shows the HTTPS Upload Port is 4903.
The next part of this procedure takes place on both management nodes, although, you see
only one management node in this demonstration.
The terminal now shows an ssh session, started as root, to the active management node on
the Oracle Private Cloud Appliance. The session connection was made using the virtual IP address
for the management node cluster. The active cluster master is ovcamn05r1.
To check the connection ports in the tinyproxy configuration on the management node, check
the configuration file.
Enter the command grep 4903 /etc/tinyproxy/tinyproxy.conf.
The result shows that port 4903 has been configured as a connection port. However, if port 4903
is not present in the configuration, then use an editor to add a ConnectPort directive
for port 4903.
This slide shows a few ConnectPort directives, as they appear in the tinyproxy.conf file.
If you make a change to the tinyproxy.conf file, you must restart the tinyproxy process
for the change to take effect.
Also, be sure to check the tinyproxy.conf file on the other management node.
Finally, on each management node, check iptables to make sure the ConnectPort - in this configuration,
4903 - is open. Enter the command service iptables status and pipe to grep 4903.
The iptables status result shows that port 4903 is configured to accept any connection.
However, if there is no rule for the port, then you must create one. Issue the command
service iptables status. The rule for port 4903 is one of 21 rules configured.
The new rule should be added to the list of rules already in place, so determine the next
available record in the INPUT chain. To add a rule for the connection port, use
the commands shown in this slide. After entering the rule, save and reload iptables so it can
take effect. Be sure to complete this review and configuration, as needed, on the other
management node.
You have seen how to determine the HTTPS upload port for Oracle Enterprise Manager, and you
have seen how to make sure the tinyproxy configuration on each management node is set up to use the
specified upload port. And you saw how to check iptables.
This ends the demonstration. Thank you for watching.