Does this mean my tcp probe needs tweaking and what should I tweak to? We use a different internal port for ssh and its 22022
This means the SFTP process was trying to enable keep-alives on the connection it received from the loadbalancer, but the loadbalancer is resetting the TCP connection before the SFTP daemon has a chance to write back data to the port on the loadbalancer -- SFTP is likely getting a "connection refused" message from the loadbalancer, since the loadbalancer has already destroyed the connection and no longer has that TCP port open.
Cisco Workload Optimization Manager (CWOM)
Continuously Assure Application Performance at Any Scale
Webinar: Wednesday, October 23rd at 11am ET
Today’s applications utilize traditional virtualization platforms as well as newer DevOps meth...
To participate in this event, please use the button to ask your questions
This special event - formerly known as Ask the Expert- is open only to Cisco Customers and Partners.
Many pages in the Cisco Community are acce...