Exchange RPC Timeouts when using Citrix NetScaler


Updated 9 June 2016

Environment


Exchange 2010

Citrix NetScaler 10.x/11.x

Issue


  • Users creating a new email and clicking on To: to browse the Global Address List would receive an Exchange timeout error message.
  • Accepting meeting invites puts the appointment in the recpients calendar but not the organisers and no email gets sent to the organiser of the appectance. Takes clicking the Accept button multiple times before it processes the acceptance.

Resolutions


Create a new TCP Profile

GUI:

  • System
  • Profiles
  • Add
  • Name: RPC_Profile
  • MSS: 1460
  • Keep-Alive Probes – Enable
  • Connection idle time before sending probe (secs) – 30
  • Keep-alive probe interval (secs) – 20
  • Everything else defaults

Bind this profile to the RPC Load Balanced VIP

  • Traffic Management
  • Load Balancing
  • Virtual Servers
  • <Exchange RPC LB VIP Name>
  • Profiles > Add
  • TCP Profile – Select RPC_Profile
  • Ok
  • Done

CLI:

add ns tcpProfile RPC_Profile_RPC -mss 1460 -KA ENABLED -KAconnIdleTime 30 -KAprobeInterval 20

add lb vserver <Exchange RPC LB VIP Name> TCP <IP_Address> * -persistenceType SOURCEIP -timeout 150 -cltTimeout 180 -tcpProfileName RPC_Profile

 

Additional Timeout customization recommendations

  • Add ‘Thresholds & Timeouts node to the RPC ServiceGroup
    • Configure ‘Client Idle Time-out’ setting to: 28800
  • Disable AppFlow on the RPC VIP and ServiceGroup
  • Ensure ‘Surge Protection’ is disabled on the RPC ServiceGroup

 

Advertisements

6 Responses to Exchange RPC Timeouts when using Citrix NetScaler

  1. MasterXen says:

    Our only symptom was a timeout on the Global Address Book, once we implemented this TCP Profile the issue went away. It is now a documented solution by Citrix.
    We have only tested and implemented this on NS 10.x

    • Mike Crowley says:

      ok thanks. This isn’t my space, can you provide the citrix link?

      • MasterXen says:

        http://support.citrix.com/article/CTX200901

      • Mike Crowley says:

        much obliged

  2. Mike says:

    Will this solution work/apply to Exchange 2013? We are also facing similar issue.

    • MasterXen says:

      Should apply to any NS/Exchange implementation

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: