Krish,
I'm not sure about TServer 8, however, up to v 7.6 the following options were configurable on TServer app:
ts-tp-enabled
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
Enables or disables the T-Server side tunnel protocol of the Heartbeat feature.
When the option is set to true and T-Server is in High-Availability mode,
tunnel protocol heartbeat messages are sent for both primary and backup
T-Servers.
ts-tp-heartbeat-timer
Default Value: 25
Valid Values: 5–60
Changes Take Effect: Immediately
Specifies the time interval (in seconds) that T-Server waits for link activity,
before it sends a side tunnel protocol heartbeat message to the link.
ts-tp-heartbeat-timout
Default Value: 10
Valid Values: 5–60
Changes Take Effect: Immediately
Specifies the time interval (in seconds) that T-Server waits for link activity
after sending a side tunnel protocol heartbeat, before it closes the link and
restarts.
You should be able to see the polling messages in the logs and identify at exactly what time the disconnections occurred, so that you can then verify whether anything happened on AES at that istant.
In regards to your questions, how can you be sure TServer did not disconnect? After a disconnection, TServer automatically tries to reconnect to AES, therefore you may see the EventLinkConnected multiple times.
Fra