Troubleshooting › CPU Usage Spikes in server nodes with Secured Simplified Communication and F5 Load Balancer

CPU Usage Spikes in server nodes with Secured Simplified Communication and F5 Load Balancer

Symptom:

When a clustered Orchestrator is configured to use secure (HTTPS) communication and agents are configured to use simplified communication with an F5 load balancer, CPU usage spikes can occur in server nodes when the orchestrator is restarted while multiple agents are active.

Solution:

Note: This is not a recommended approach. Use the following approach only for the above problem.

To fix the problem, configure the clustered Orchestrator to use non-secure (HTTP) communication between load balancer and orchestrator as follows:

1. Add the following properties in the OasisConfig.properties file for all orchestrator nodes:
   • pam.transport.unsecured.connector.flag: Set the value to true.
   • pam.transport.unsecured.connector.port: Specify an integer value. Default value is 80.
2. Add the following pools for each CA Process Automation cluster and use the non-secure server port (by default, 80) and http protocol for each member:
   • NODE_1 with the member PAM Domain node1
   • NODE_2 with the member PAM Domain node2

   Note: For more information on how to create two F5 pools for each CA Process Automation cluster, see the Create Two F5 Pools for Each CA Process Automation Cluster in the CA Process Automation Installation Guide.

3. Modify the iRule Definition as follows:
   • Add the entries NODE_1 and NODE_2 to the following lines:
     • set NODE1 "NODE_1"
     • set NODE2 "NODE_2"
   • Remove the line:

     set WSPORT "443"
     

   • Modify the URL mapping for the following URLs as follows:

     "/ws/node1" { SSL::disable serverside
                                    pool $NODE1
     }
     "/ws/node1*" {  SSL::disable serverside
                                     pool $NODE1 
     }
     "/ws/node2" { SSL::disable serverside
                                     pool $NODE2 
     }
     "/ws/node2*" {  SSL::disable serverside
                                     pool $NODE2
     }
     

4. Restart Orchestrator nodes and Load Balancer.