add a NTP server for the rsyslog time of TSSC to be synced with external NTP

When I logged in to TSSC on one of our devices I noticed that the syslog had printed that I had logged in 19 minutes before I actually had...

After raising this with IBM they told me the following:

The 3957 TSSC that we use to log in and out of the 3957 VTS do not run on NTP time server but they can be changed manually and yes as they are just a linux they have there times set and they can drift but I don't expect by much. 

I had to connect to each TSSC / cluster individually I compared it to the VTS time whic is UTC time.
TSSC on cluster 0 is 10 min 38 seconds behind the VTS time which is UTC time .....
TSSC on cluster 1 is 56 seconds ahead
TSSC on cluster 2 is 19 Minutes 56 seconds ahead
TSSC on cluster 3 is 1 Minutes 2 seconds 56 ahead

I am not aware that there is an option in current code to add a NTP server to keep the TSSC in sync. 

This causes our shop great issues as all activity is monitored and subject to change conditions. We are now seeing that we are being flagged for non compliance, doing change outside of change windows which we have to defend ourselves from and waste time and effort proving our innocence.. I can not be subjecting our staff to logging and monitoring events where the time is drifting and is not true.

This needs to be resolved as soon as possible as it will not only be our shop that experiences these issues when audit and regulators make people log and monitor their systems.