Hi Phillip,
Thank you for the link sir! Being that we are on a custom hub (7.80-jh2), which was to address hub tunnel disconnects, and worked beautifully for nearly a year...making changes to the hub config first needs to go through some red tape.
Your suggestions per the link have been discussed with Rito and Jason (CA Support). Being that it is a Friday, we will likely not implement the changes today being that we are on the eve of a weekend. Once final approval is received, I will get this config's implemented...likely Monday.
Email chain with CA Support that may be useful for some:
I asked Rito the following:
-----------------------------------------------------------------------------------------------
Hi Rito,
Out of those 6 hub cfg settings within " tec000004536", we have 5 of them in our hubs. Here are the current settings within our hubs:
postroute_interval = 30
postroute_reply_timeout = 60
postroute_passive_timeout = 30
hub_request_timeout = 30
tunnel_hang_timeout = 300
Would you be able to explain why we would need to switch those settings and how each could possibly help?
And if we need to add back in "tunnel_hang_retries = 3", why was it removed and why should we add it back?
-----------------------------------------------------------------------------------------------
Response:
-----------------------------------------------------------------------------------------------
These timeouts collectively control the hub's behavior when it encounters slow responses from queues and other hubs. Specifically the postroute_* timeouts have to do with queues. hub_request_timeout has to do with other hub-to-hub requests. Increasing these will help in a busy environment as the hubs will be allowed more time to respond to each other.
tunnel_hang_retries is not present by default, and when not present, defaults to 1. This controls how many times a tunnel connection will be re-tried when unresponsive before the hub simply restarts itself entirely to attempt to self-heal. Setting this higher will allow the hub to internally retry the connection a couple more times before restarting.
-----------------------------------------------------------------------------------------------