Troubleshooting
Problem
TSAMP Support recommends that you implement a schedule to reboot your Windows based TSAMP cluster nodes every so often to avoid a Microsoft SUA performance problem that manifests as slow response or hang conditions for services/commands with the SUA environment.
Symptom
Logging into a TSAMP shell is either unresponsive or all TSAMP based commands appear to hang indefinitely.
SUA CLI OS commands are slow to respond or can hang.
Cause
http://support.microsoft.com/kb/2639164
http://support.microsoft.com/kb/978048
http://support.microsoft.com/kb/2300085
Diagnosing The Problem
Even if the efix for the above listed KB articles are installed, Microsoft's SUA has shown to be unstable over long periods without a restart of the server. The symptoms shown above are not all inclusive ... other erratic behavior can be observed.
Resolving The Problem
TSAMP Support recommends that you schedule maintenance periods where you can reboot your Windows nodes every so often. Unfortunately we cannot recommend a particular reboot frequency because we've found that the SUA performance degradation becomes a problem at different rates for different customer environments.
Microsoft have not offered a complete resolution to their SUA performance problem to date. Microsoft have also discontinued SUA for future Windows Server editions. As a result, IBM will no longer offer TSAMP on the Windows platform as of TSAMP v4.1. We recommend the Linux platform as an alternative.
Was this topic helpful?
Document Information
Modified date:
24 June 2019
UID
swg21670461