Forum Discussion
2funky_105078
Cirrus
CirrusSmartprobe 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 the TCP port still up?
These CAS servers provide RPC service to all outlook clients that connect to. IN LTM there is no smart probe for RPC.
Do you know of any application probe already developed?
Do you know of any iControl rule integrated in some server Microsoft monitoring tool that, in case of server unavailbility, will instruct the LTM to bring a possible failing server out of service?
If the server has the TCP port UP and the server is not responsing, this might cause an outage...
5 Replies
2funky_105078we were thinking to use RPC probe, but not sure how to configure it for CAS service....- 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 - 2funky_105078Thanks for the answer but.....
So you dont have any RPC application probe to suggest, only TCP?
We are not targetting EWS (where we use HTTPS probe), but RPC/RPC-MAPI - 2funky_105078Regarding the possible RPC probe...
I see that the configurable parameters in the RPC probe are Program and Version Number.
From the trace of my Outlook client connecting to Exchnage via the LTM we see Version number 5 but not sure on Program number… - We don't have a custom probe for RPC. My suggestion is to use an EAV monitor to check mailbox availability through EWS, and make the RPC pool status dependent on that monitor.
