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

2funky_105078's avatar
2funky_105078
Icon for Cirrus rankCirrus
Feb 06, 2013

Smartprobe for CAS RPC roles???

  Hello,     We have multiple CAS Exchange 2010 servers which are monitored only on TCP port on the RPC/RPC-MAPI services.   What would happen if the CAS servers would be down but th...
microsoft
partner
mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Feb 06, 2013
Hi 2funky, in general we recommend moving to Outlook Anywhere if possible, since RPC client access is going away in Exchange 2013 and we do a lot more monitor-wise for HTTP-based services. That said, here are our general recommendations for monitoring RPC:

 

 

1. Configure your Exchange servers to use static ports for the MSExchangeRPC and Address Book services

 

2. Create TCP monitors for each of these ports and assign them to their respective pools

 

3. Then, assign both of those static port TCP monitors to the RPC 135 pool, in addition to the TCP 135 monitor, and configure pool's minimum number of up monitors to "All".

 

 

Also, we now have an EAV monitor that performs a real mailbox login against Exchange Web Services (which MAPI clients must still use to do things like free/busy lookups, etc). You could create that monitor and attach it to your port 135 pool in addition to the 3 TCP monitors already assigned, leaving the monitor requirement set to "All".

 

 

Let me know if you are interested in using the EWS EAV monitor. I can PM you with the details.

 

thanks

 

Mike