How to troubleshoot SSL handshake errors between Control-M/Enterprise Manager and Control-M/Server using plc_client and plc_server tools?

- For Control-M/Enterprise Manager , Control-M/Server, and Control-M/Agent, we have SSL utilities to simulate SSL connection.
- These utilities will be helpful to simulate issues occur outside of Control-M and provide more details about the connection failure.

1.  To executes the secured connection simulation, start separate command prompt from the Control-M/Enterprise Manager machine (client) and on the Control-M/Server machine (server).  
2.  In the Control-M Server host, navigates to Control-M Server's installation "exe"  sub-directory and run:
  
    “plc_server -h <server listen host name> -p 5555 -S <site.plc full path> -P <co.plc full path>”

For example,
UNIX       : plc_server -h ctmserver -p 5555 -S $HOME/ctm_server/data/SSL/cert/site.plc -P $HOME/ctm_server/data/SSL/cert/co.plc
WIndows : plc_server -h ctmserver -p 5555 -S Control-M/Server\SecurityPolicy\site -P Control-M/Server\SecurityPolicy\CO

"ctmserver" is the host name where plc_server is running.

3. A plc_server process will be started and listening for incoming client connection.

4.  In the Control-M/Enterprise Manager host, navigates to the Control-M/Enterprise Manager's installation "bin" sub-directory and run:

     "plc_client -h <server listen host name> -p 5555 -S <site.plc full path> -P <gtw.plc full path>"

For example:
Unix        : plc_client -h ctmserver -p 5555 -S $HOME/ctm_em/etc/site/resource/ssl/cert/site.plc -P $HOME/ctm_em/etc/site/resource/ssl/cert/gtw.plc
Windows : plc_client -h ctmserver -p 5555 -S "Control-M\Control-M/Enterprise Manager\9.0.X\Default\SecurityPolicy\site" -P "Control-M\Control-M/Enterprise Manager\9.0.X\Default\SecurityPolicy\GTW"

5. At this point, the connection should be established with SSL communication between Control-M/Enterprise Manager and Control-M Server.

6. If the secured connection failed or any errors displayed, please contact BMC customer support and provide the output of the above test for assistance.

Note: The same test can also be executed between Control-M/Server and Control-M/Agent refer to this KA 000379171
Note: On Windows machines, policy tables are located in Windows registry and not on physical files

The following video demonstrates this solution:

 


Additional Information:
Customers viewing this solution may find value in the following self-help Connect with Control-M video.