Move remote NetOps Portal MySql server host to a new host

Products

• Network Observability
• CA Performance Management

Issue/Introduction

When using a remote MySql server host for a DX NetOps Portal UI web server the network connection stability between servers is critical to the environments success and stability.

While the throughput and bandwidth are important factors, the connection stability is the most important.

Often things like firewalls between the servers can impact the connection stability by closing connections that need to remain open. Once closed the tool gets in an error loop trying to reconnect through a connection it expects to still be open.

Environment

All supported DX NetOps Performance Management releases

Cause

Network connectivity instability causes Portal web server UI functionality problems.

Resolution

Move the remote MySql database server host to a server located where network stability can be maintained. For example moving it to the same network subnet or ESXi host, or to a location without a firewall between the servers.

To successfully move the MySql database server host follow these steps.

1. Before starting the change:
   • Shut down Portal services (stop Console/PC->DM->EM->SSO)
   • Generate a new MySql backup after stopping services.
2. Ensure DNS is correct to support the change.
3. Ensure the /etc/hosts files on Portal and MySql hosts are update as needed to support the change.
4. Configure IP Tables on the servers.
   • Limit access to the remote mysql server host over port 3306.
   • Needs to be accessible from the Portal UI host, and any other hosts used to connect to the server.
5. Post move ensure the MySql service starts
6. If hostname for the MySql server host is changed:
   • Ensure the db.url value in these Portal web server files is updated to the correct name.
   • Make a back up copy of the files before editing them.
     • cp <fileName>.properties <fileName>.properties.<date>
     • Example: cp sso.properties sso.properties.Dec2024
   • File locations and names showing using default paths.
     • /opt/CA/PerformanceCenter/sso/webapps/sso/WEB-INF/sso.properties
     • /opt/CA/PerformanceCenter/EM/webapps/EventManager/WEB-INF/em.properties
     • /opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF/dm.properties
     • /opt/CA/PerformanceCenter/PC/webapps/pc/WEB-INF/cfg/portal.console.properties
7. Start the Portal services (SSO->EM->DM->wait 30 seconds->Console/PC).