We've heard from many customers who are trying the new Oracle Enterprise Manager App in the Oracle Cloud Marketplace that they would like more information on how to set up the networking between their newly-installed, cloud-hosted EM and their on-premises assets. This blog post will use an example explain how to set up the networking and to ensure the connection is efficient and secure.
Let's use an example: Reference Architecture
First off, let's define a simple example. Let's say you have an OCI tenant called eminfra, and it is deployed in the OCI-Phoenix region. In that tenant you've installed an Enterprise Manager instance, either manually in a Virtual Machine you've configured yourself or using the EM marketplace app. That VM probably has a Internet Gateway so that you can access your EM instance from over the Internet.
Now you want to manage some targets in another data center. It could be perhaps in your own on-premises data center, or another IaaS provider, or even something deployed in a different OCI region. For the purposes of this example, we will call this the "Target Data Center" and we will be standing up an OCI VM with a single-instance Database in the OCI-Ashburn region, and the instance name is oradbclouducm.
You can see both of these environments in the image below. The "left" host is the EM-in-OCI network, and the "right" host is the Target network.
Figure 1. Architecture for our sample application, featuring an OCI-hosted EM in the OCI-Phoenix data center (the "Left/EM-side", and "on-premises" database in a different data center (the "Right/Target-side" -- in this case, we are using OCI-Ashburn, but you would possibly be using your own data center).
Our goal is to establish secure, reliable networking connectivity between eminfra and oradbclouducm so that an EM agent installed on the Database in oradbclouducm can talk to the EM OMS installed on eminfra. There are two options to do this.
The first, and simplest option is to make use of Oracle Cloud FastConnect, which provides a dedicated, secure VPN connection between your site and Oracle Cloud. If you are making use of FastConnect, no additional work is needed as these two hosts can communicate with each other just like they are in your local network, so we won't go into that option any further here (note that subscribing to FastConnect carries an additional cost).
The second option is to make use of a secure and encrypted site-to-site IPSec VPN that you set up on your own using an Open Source IPSec client such as LibreSwan. This setup requires a bit more work on your end, but carries no additional cost. We'll show you the steps required to do this on both the EM and Target sides.
The image below shows the end state -- the same reference architecture with the IPSec VPN networking enabled.
Figure 2. The same reference architecture shown above, with the end-state IPSec networking also shown.
For the purposes of this example, we are going to assume that you have already have an on-premises "Target Data Center" network and it has a connection to the Internet.
IMPORTANT note about the Right/Target-Side networking: Our example is using a different OCI Data Center for our "Right/Target-side Data Center," but that is just an example...if your Right/Target-side is your traditional on-premises network, then some the networking actions/terminology we discuss in this section might be different for you. For example, in an on-premises network, you might be dealing with the administrators of your network's DMZ, bastion hosts and firewall rules instead of (in our example) OCI's Internet Gateways, Ingress Rules and similar. However, the basic information you'll need to gather from the Right/Target-side network to use in the Left/EM-side still apply, so hopefully this information will help you understand what you would need from your on-premises network as well.
In our example where the Database Target is in OCI-Ashburn, let's assume you already set up an OCI Compartment called EnterpriseManager inside the (OCI-Ashburn) oradbclouducm OCI instance, and that EnterpriseManager Compartment has a VCN called EM-Demo with the CIDR 10.0.0.0/24 and a Subnet called em with the CIDR 10.0.0.0/27 that has an Internet Gateway enabled (if you don't know what any of this means, visit the OCI Networking site to learn more).
You then need to spin up a new VM in the em Subnet of the EM-Demo VCN into which you will install Libreswan. We are going to call this VM instance-libreswan, and it will use a VM.Standard.2.1 Shape.
Figures 3 and 3A. Setting up a new host for your Libreswan IPSec installation.
Note the Private IP address of the instance-libreswan VM, which in this example is 10.0.0.4 .
Note the Public IP address of the instance-libreswan VM, which in this example is 184.108.40.206 .
Once the instance-libreswan VM is up, navigate to the new instance in OCI Console, choose the Attached VNIC setting, edit it and Disable the Source/Destination check on the network (since Libreswan is going to be taking care of that for us).
Figure 4. Disabling the host-level Source/Destination check on your soon-to-be-Libreswan host.
Then add Ingress Rules to the VM to open up ports 500, 4500, UDP and TCP ports.
Figure 5. Adding Ingress Rules to allow outside connectivity to your soon-to-be-Libreswan host.
Then add a route rule to the Route Table in the EM-Demo network to send all incoming traffic to the instance-libreswan machine, using the Private IP address you noted above (in our case, 10.0.0.4).
Figure 6. Adding a Route Table to send all incoming traffic through the soon-to-be-Libreswan host.
Then, as root user in the instance-libreswan VM, install the Libreswan package by running the command
We now need to create a VCN on the Enterprise Manager side of the equation that will allow the EM instance to communicate with our Libreswan IPsec endpoint.
In our eminfra OCI instance, create a Compartment called EM-MP and in that compartment create a VCN called hybrid_con with CIDR 220.127.116.11/16.
Figure 8. Creating a VCN called "hybrid_con" in for your OCI-hosted Enterprise Manager to use to communicate through the IPSec channel to your on-premises Targets.
Then create a Subnet in the EM-MP Compartment called hybrid_sn with CIDR 18.104.22.168/27 .
Figure 9. Creating a Subnet called "hybrid_sn" in the EM-MP Compartment.
Add an Internet Gateway called hybrid_ig to the hybrid_con VCN.
Figure 10. Adding an Internet Gateway called "hybrid_ig" to the EM-MP Compartment.
Now we need to add a Dynamic Routing Gateway (we'll call it hybrid_drg) and attach to the hybrid_con VCN. This will allow us to instantiate a (you guessed it!) IPSec connection to Customer-Premise Equipment (like the LibreSwan instance we configured above).
Figure 11. Adding a Dynamic Routing Gateway called "hybrid_drg" to our VCN.
Create a Customer Premise Equipment with the Public IP address of the Libreswan host. (In this example, 22.214.171.124). We will call this hybrid_cpe .
Figures 12 and 13. Creating Customer Premise Equipment with the Public IP address of the Libreswan host.
Create a new IPSec Connection to the the CIDR from the Target-Side VCN EM-Demo (in this example, 10.0.0.0/24). You will have to select the name of your Dynamic Routing Gateway (hybrid_drg), and your Customer Premises Equipment (hybrid_cpe) and make sure that the CPE IP Address is the Public IP address of the Libreswan VPN Machine. (In this example, 126.96.36.199).
Figure 14. Creating a new IPSec Connection from our OCI-Phoenix VCN to our "on-premises" Target network.
Add a Route Rule to ensure traffic goes through the Dynamic Routing Gateway, using the destination of the CIDR from the Target-Side VCN EM-Demo (in this example, 10.0.0.0/24).
Figure 15. Adding a Route Rule to ensure traffic goes through the Dynamic Routing Gateway.
As you did on the Right/Target/Libreswan side, update the Left/EM-side hybrid_con VCN's Ingress Rules to open ports 500 and 4500 - TCP & UDP.
Figure 16. Adding Ingress Rules to the Left/EM-side VCN.
Copy the IP Address and Shared Secret from the IPSec connection. You're going to need these in a minute back on the Right/Target/Libreswan side.
Figure 17. Getting the IP Address and Shared Secret from the Left/EM-side IPSec Connection.
First, on the Libreswan host VM (instance-libreswan), add the following config into the file /etc/sysctl.conf
Then populate the config with command
On the same host, add the following entries into the file /etc/ipsec.conf
On the same host, create a file under /etc/ipsec.d/oci.conf with the following info (using the public IP addresses and VCN CIDRs from earlier steps):
On the same host, create a new secret file on /etc/ipsec.d/oci.secret, in which you place the Shared Secret from the EM host you noted down earlier.
On the same host, disable the Linux firewall & Disable the SELinux so there are no conflicts with the IPSec networking.
Verify and Start the IPSec connection.
And finally, verify the connection by the following the command
Congratulations! You've now created an IPSec VPN tunnel between your OCI-hosted EM instance on the "left" side and your on-premises/other IaaS data center on the "right" side. You can make sure the IPSec connection is up by checking to see if one of the IPSec connections shows as "Up" in the hybrid_ipsec host console.
Figure 18. Verifying the IPSec Connection is up-and-running.
Now that we have the IPSec Connection, we can connect to a database installed on a host that is reachable from the Libreswan host (in the same VCN Subnet in OCI, or on the same LAN if your Libreswan host is in a physical data center). You're going to manually install an EM Agent via SSH, then discover the Database and associated components normally.
Let's say your Database is on a host called dbonpremise. First, generate SSH keys on both the EM host and the Database host, with the command:
Make sure you save the key values to a text file so you can paste them in later.
Now, add the DB machine's public key to the EM machine's authorized_keys and vise versa (code example below shows adding the EM key to the DB machine's key store).
Now, from Enterprise Manager, use the standard "Add target" workflow to manually install an EM Agent on the DB System. You'll need to enter the DB machine's private key in the "SSH Credentials" field.
Figures 19, 20 and 21. Using the IPSec Connection, manually adding the Database Target from the Right/Target/Libreswan-side to the Left/EM-side Enterprise Manager, followed by Installing the EM Agent on the Right/Target/Libreswan-side Target.
You'll also want to make sure the Ingress Rules on both hosts allow for open ports 1521,1830 and 4903.
Figure 22. Verifying the host Ingress Rules allow for EM OMS-Agent Communication.
From this point, you can use standard EM Database Discovery workflows to discover the Database system and all its components. You should use the IP address of the Database host where the workflow asks you for the Database "Listener Machine Name" since only the IP address is visible over the IPSec network connection.
Figures 23, 24, 25 and 26. Discovering the Database/Listener using standard EM processes.
Congratulations! Your Database target and Listener should now appear in the EM "All Targets" page.