Table of Contents Previous Next



C:\Users\susan\Desktop\pem-architecture.png
After installing the PEM agent, the agent must be registered on each node that will be monitored by the PEM server. The steps that follow detail registering the PEM agent with the server, and configuring the server to monitor the agent.
modify the pg_hba.conf file on the node hosting the PEM server to allow connections from any monitored node.
modify the pg_hba.conf file on any monitored node, allowing connections from the PEM server.
Please note: when a cluster node is stopped (for example, when scaling down), or if a cluster is deleted, the Monitoring tab of the PEM web interface will alert you that the agent on that node is down (see Figure 4.22).
C:\Users\susan\Desktop\Screen Shot 2018-01-15 at 12.18.09 PM.png
If the cluster has been deleted (and the agent will not resume monitoring), you can use the PEM Browser tree control to remove the agent definition from the PEM server. Expand the PEM Agents node of the tree control, and right-click on the name of the deleted agent; then, select Delete/Drop from the context menu.
Navigate to the Clusters tab, and create a new cluster that is provisioned using an engine definition that includes the pem-agent RPM package in the list of required RPM packages.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\5175f7dd\Screen Shot 2017-05-08 at 2.32.35 PM.png
For detailed information about creating a new server cluster, please see the EDB Ark Getting Started Guide, available through the EDB Ark Dashboard tab.
Before a PEM agent that resides on an Ark cluster can communicate with the PEM server, you must modify the pg_hba.conf file (see Figure 4.24) of the PostgreSQL database that stores PEM statistics to allow connections from any monitored servers as well as the PEM client.
Screenshot-#%pg_hba
With your choice of editor, modify the pg_hba.conf file of the PEM Server backing database, adding entries for the IP address of the EDB Ark cluster. The connection properties should allow connections that use cert and md5 authentication.
For detailed information about modifying the pg_hba.conf file, please see the PostgreSQL documentation, available from the EnterpriseDB website at:
After modifying the pg_hba.conf file for the PostgreSQL installation that stores statistical information for PEM, you must restart the PEM backing database server to apply the changes. The name of the PEM service is:
Where x specifies the version. For example:
Use the Download SSH Key icon on the Clusters tab to download the SSH key for your cluster. When you download the key, a popup will open, informing you of the steps required to connect to the master node of your cluster (see Figure 4.25).
Screen Shot 2016-03-02 at 6
Use your choice of editor to modify the pg_hba.conf file on the Ark node. By default, the pg_hba.conf file is located in /var/lib/ppas/9.5/data.
Add entries to the pg_hba.conf file that allow connections from the PEM server (see Figure 4.26).
Screen Shot 2016-03-02 at 6
After modifying the pg_hba.conf file, you must restart the server to apply the changes. The name of the service is Arkdb. Use the platform and version specific command for your cluster to restart the Arkdb service.
PGPASSWORD=password ./pemagent --register-agent --pem-server x.x.x.x --pem-port port --pem-user user_name
x.x.x.x specifies the IP address of the PEM server.
port specifies the port on which the server is listening for connections
user_name specifies the name of the PEM user.
Screen Shot 2016-03-01 at 2


Table of Contents Previous Next