Troubleshooting highly available SMS Gateway deployments

A highly available environment might include an eXtreme Scale Liberty Deployment (XSLD) caching server and SMS Gateway in IBM Cloud Private. If you run into problems, the information in the following sections can help guide you through troubleshooting and redeploying. (As of Version 1.0.6.0, the XSLD caching server is deprecated in favor of the Redis caching server.)

Tip: If you're unable to successfully deploy the XSLD caching server using the deploy-sms-xsld-kubernetes.sh deployment script, you can run each piece of the script individually to help pinpoint the problem. For more information, see Deployment scripts for XSLD in the sample.voice.gateway repository.

• Verifying your highly available SMS Gateway deployment

  After you deploy, run kubectl commands to see which pods are running.

• Cleaning up your environment before you redeploy

  If your XSLD caching server or SMS Gateway deployment was not completely successful, you need to clean up the existing deployment before you redeploy.

• Viewing XSLD information

  After the XSLD caching server is deployed, you can view information from each of the cache members. For example, you can download logging and trace files, or view SMS session entries in the data cache.