Exchange 2010 System Template Question. http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=4955972 2013-05-24T18:16:31Z 2013-05-24T18:16:31Z Russ Whitear http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=4960408 2012-01-05T15:19:25Z 2012-01-05T15:19:25Z

Great. Thanks for the clarification Jason. I may have a try at modifying the system template to add the option to set IP Sticky for the RPC connections. Would make a great demonstration of the flexibility of templating. Many thanks Russ.

Russ Whitear 2012-01-05T15:19:25Z Jason Notari http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=4957071 2012-01-04T20:31:44Z 2012-01-04T20:31:44Z

Russ We will look at an update on the ANM side of this to make this more clear. While working with the CVD team to develop this template there was quite a bit of concern about the IP sticky behavior when a large percentage of the clients were routing through a super proxy. The Exchange would work for the RPC connections without any session persistence (although with slight additional latency and CPU usage on the rservers). At that time the developer of the CVD felt that it was easy to add IP sticky to the deployed vserver after the fact. The risk of certain cases having unbalanced server usage (with IP sticky) was thought to be more difficult to troubleshoot and debug. So we made the decision to pull it from the template. Unfortunately that wasn't clearly communicated. We should at least provide an on-screen note to indicate what we are doing. We could also provide the option to set IP Sticky with the appropriate caveat. Ideally the CVD would be updated with a note about super-proxies as well. Jason

Jason Notari 2012-01-04T20:31:44Z Russ Whitear http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=4955971 2012-01-04T13:07:56Z 2012-01-04T13:07:56Z

I'm trying to ratify an Exchange 2010 ACE configuration generated with the ANM system template against the Cisco Validated Design for load balancing Exchange 2010.    ANM creates the following configuration for MAPI-RPC traffic:    rserver host 192.168.11.58   ip address 192.168.11.58   inservice rserver host 192.168.11.59   ip address 192.168.11.59   inservice rserver host 192.168.11.60   ip address 192.168.11.60   inservice   serverfarm host msExchange02-others   failaction purge   predictor leastconns   rserver 192.168.11.58     inservice   rserver 192.168.11.59     inservice   rserver 192.168.11.60     inservice   class-map match-all msExchange02_other   2 match virtual-address 192.168.10.105 any   policy-map type loadbalance first-match msExchange02_other-l7slb   class class-default     serverfarm msExchange02-others policy-map multi-match int10   class msExchange02_other     loadbalance vip inservice     loadbalance policy msExchange02_other-l7slb     nat dynamic 1 vlan 11   As can be seen, no session persistence is configured by ANM. The CVD on the other hand declares that SRC-IP stickiness is required for MAPI-RPC connections in an Exchange 2010 environment.    I'm looking for confirmation whether the error is with ANM or the CVD.   Many thanks   Russ.

Russ Whitear 2012-01-04T13:07:56Z