Understanding SSH Connection Caching Duration in MID ServersIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } The following information helps to clarify how SSH connections are cached by the MID servers, a topic that has not been covered in our documentation. This caching mechanism is crucial for optimizing the performance of MID servers, as it allows them to store and reuse SSH connection information, reducing the need for repeated authentication and connection establishment. By understanding how this caching works, users can better manage their MID servers and troubleshoot any issues that may arise. For more information on MID servers and their configuration, please refer to the MID Server documentation. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All Release Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } 1) What is the duration of the connection caches and how it related to the max connection on host ssh property. -Answer: Right now Max connection on host ssh property is set top 3. 2) Please provide details example of how this would work for a sample server. Multiple patterns are invoked. When will the connection be terminated. Answered: ssh Connection Details during Discovery:* If mid.connection_cache is true:* The maximum connections per host will be 1.* The maximum channels per connection will be set to the value of mid.ssh_connections_per_host. If this property is not defined, the default value will be 7.* If mid.connection_cache is false:* The maximum connections per host will be 3. Connection Cache Timeout:* Any connection that remains idle for more than the value set in mid.ssh.session_timeout (default is 5 minutes) will be cleared or closed within the next 1 minute ideally but depending on number of total host used in discovery it can vary, regardless of the value of mid.connection_cache. 3) If 'mid.connection_cache' is true and 'mid.ssh_connections_per_host' is 3 how many connection will be there? Answered: Single connection will be there .