F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Victor_129910's avatar
Victor_129910
Icon for Nimbostratus rankNimbostratus
Dec 19, 2013

CAS exchange tcp 60001 expires before source persistence timeout

Hi,

 

we are loadbalancing CAS Exchange services (135, 60000, 60001, 443, 25) using source address persistence timeout 7200 seconds (LTM 11.2.1)

 

Nevertheless, our Exchange workmates say most connections ends before that time.

 

We are wondering if maybe we should also modify tcp idle timeout profile (300 seconds by default)

 

Best Regards

 

3 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Victor,

     

    The Exchange iApp does indeed set a TCP idle timeout of 7200secs so I would recommend you do change it from the default.

     

    Rgds

     

    N

     

  • Hi,

     

    sorry, we are not using Exchange iApp, we are using our own config, but for your answer I guess we should modify TCP idle timeout also to 7200.

     

    Many thanks.

     

    • nathe's avatar
      nathe
      Icon for Cirrocumulus rankCirrocumulus
      I was using the iApp as the recommended config. Hopefully changing this will sort your issue.