Configuring Exchange on GTM setup

In one paragraph...

Setup your GTM on a separate subdomain (e.g. wip.domain.com). Delegate that sip.domain.com to your GTM. Setup your GTM pool containing the LTM VS's as poolmembers. Create a WIP. Place the GTM pool in the WIP. Test. Then change the service name to be a CNAME record with the value being the WIP.

Note that 1 paragraph hides a bit of configuration around data centres, servers, big3d and gtmd comms etc...

H

How about the internal network users? Currently the internal DNS takes care of the resolution of the traffic for them, so even in the internal DNS I will change the A record and replace it with the CNAME and it will be forwarded to GTM to manage it over GTM Pool?

Well... There lies the devil in the detail... You need to plan this out, and try to be consistent in everything (Special cases will kill you).

Some questions you ned to ask yourself... Do the internal users connect to the same VS as external users? Do you run split DNS? NAT'ing? Are you using APM? Or just LB'ing your CAS servers? Are you silo'ing everything? Or are you spreading your cluster horizontally?

Sorry to be asking you so many questions, but without you knowing all the answers, you can't plan successfully...

H

We've setup GTM as described and only for internal, external users need to VPN in for email. More detail on the cNAME; it's a cNAME on an A record in the internal.domain.com and the A record we chose was the IP address of the service VIP on the LTM in the primary data center. The cName data points to the wip.domain.com. Our GTM is setup for manual failover of exchange records, to prevent any false positives. The WIP has 2 pools and is setup for global availability. The pools are setup with an IPv4 fallback IP to ensure the pool always available until we manually disable it to initiate failover. As stated in previous thread, there are a TON more details and it will depend on your requirements. Hope this helps.

We've setup GTM as described and only for internal, external users need to VPN in for email. More detail on the cNAME; it's a cNAME on an A record in the internal.domain.com and the A record we chose was the IP address of the service VIP on the LTM in the primary data center. The cName data points to the wip.domain.com. Our GTM is setup for manual failover of exchange records, to prevent any false positives. The WIP has 2 pools and is setup for global availability. The pools are setup with an IPv4 fallback IP to ensure the pool always available until we manually disable it to initiate failover. As stated in previous thread, there are a TON more details and it will depend on your requirements. Hope this helps.

In my situation I have 2 sites, each site has 2 CAS servers and under the current setup the users of a particular site are forwarded to their site NLB, now NLB will get replaced with LTM and for the high avaliability we will configure GTM as well, what we want is that the users of each site should get forwarded to their respective CAS aray until that site's CAS array faces any problem the users should not be forwarded to the CAS array of the other site. we are considering automatic fail over no static...

In my situation I have 2 sites, each site has 2 CAS servers and under the current setup the users of a particular site are forwarded to their site NLB, now NLB will get replaced with LTM and for the high avaliability we will configure GTM as well, what we want is that the users of each site should get forwarded to their respective CAS aray until that site's CAS array faces any problem the users should not be forwarded to the CAS array of the other site. we are considering automatic fail over no static...

Hi Guys, Anyone answer pls.... waiting for some input....

Regards,