Forum Discussion

Muhammad_Omair_'s avatar
Icon for Nimbostratus rankNimbostratus
Oct 05, 2011

Does GTM is Mandatory for Lync? How many LTM?




I am working on a scenario where customer need Lync solution. I understand that in normal circumstances i need one pair of LTM for lync servers and one pair for Edge Servers. The customer however cannot go for such investement. I believe we can achieve the same with one pair of LTM, Can you guys confirm.



Secondly if few of my servers in DC1 and few DR site. Can i achieve the loadbalancing without using GTM. If yes, what i functionality i will miss.







4 Replies

  • Ryan_Korock_46's avatar
    Historic F5 Account



    Normally I recommend a pair of BIG-IP LTMs for the Edge Servers, and a pair for the Front Ends (just as you described), however as this is not an option, we have to look at alternatives.....



    There is nothing technically stopping you from using the same pair of BIG-IPs for the Edge Servers and the Front Ends. Most customers do not do this because of network architecture and the security concerns around a single network device spanning multiple legs of a network. But it does work to reuse the same BIG-IPs, and it is up to you and your customer if this is a solution you can support.



    GTM provides health monitoring and more precision in load distribution; things you will not have when not using GTM for the wide area. Without GTM, there isn't awareness of the health and availability of the servers, and there is little control over where users are sent to.





  • Hi Ryan,



    but in general GTM is not mandatory if the Lync environment is spread over two regional datacecenter?



  • Ryan_Korock_46's avatar
    Historic F5 Account
    Hey RoK,



    I wouldn't go as far as saying they are 'mandatory', but would highly recommend it. GTM provides dynamic load balancing and health monitoring that other static DNS & global methods can't provide.



    If it helps at all, Microsoft chose to use GTM for their Site Resiliency solution -> Planning for Metropolitan Site Resiliency