Troubleshooting Handshake Failed Server State in Siebel Management Console

If you see a Handshake failed server state in the Management screen in Siebel Management Console (SMC), then you cannot perform management runtime activities from SMC. This topic is part of Troubleshooting a Siebel Cloud Manager Instance or Requested Environment.

After all lift and shift activities are completed for a Siebel CRM deployment on OCI, and you navigate to the Servers view in the Management screen in SMC, you might see a State value of Handshake failed for one or more servers. This happens when the Siebel Gateway (CGW) instantiates the Server Manager sessions before all servers are in the running state.

To correct this state and restore the SMC management functionality, you must restart all of the siebelcgw pods. To do this, first connect to the SCM container and set the profile for your OCI environment, as follows:

sudo podman exec -it cloudmanager bash

source /home/opc/siebel/<env_id>/k8sprofile

Next, restart all of the CGW pods using the following command:

kubectl rollout restart sts siebelcgw -n <env_name>

Now you can log in to SMC again and verify the server states from the Management screen.