Forum Discussion

techieanalyst_1's avatar
techieanalyst_1
Icon for Nimbostratus rankNimbostratus
Jul 11, 2014

Lync 2013 iApp Help

Looking for a quick have on getting the iApp working properly, so far I haven't been having a lot of luck, example contacts and groups won't show up for people externally. My settings in Lync are:

 

Lync 2013 Topology Settings

 

FQDN: lync.domain.com Edge Pool: lynce.domain.com Lync External Web Services: lyncext.domain.com

 

Edge Pool Settings

 

Access Edge Service: access.domain.com Web Conf: Webconf.domain.com AV: av.domain.com

 

F5 Settings

 

I only have the Edge Reverse Proxy Component setup right now, as I don't think I need any other component:

 

What IP address do you want to use for the port 443 reverse proxy virtual server? External IP What is the port 4443 virtual server IP address that forwards traffic to the Front End Servers? Internal IP What is the FQDN of your Lync Front End web services pool? lync.domain.com What is the simple URL for meetings? meet.domain.com What is the simple URL for phone access? dialin.domain.com What is the FQDN for external Lync Mobility access? sip.domain.com

 

I know that my web services URL is wrong, however when I change it the iApp stays down, change it back and it works, so confused there, also the lync mobility should be set to what?

 

APM
application delivery
deployment
devops
iApps
LTM
security

7 Replies

Sort By
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jul 11, 2014

    Hi techieanalyst, I'm fairly sure that Microsoft recommends using the same load balancing method for both reverse proxy and edge services. So, you should deploy the access, A/V, and web conferencing services on your external LTM as well.

     

    In all of my deployments, the front end pool FQDN and web services FQDN are the same. However, your web services FQDN should most likely be lyncext.domain.com (and we may need to reword the question a bit).

     

    Mike

     

  • techieanalyst_1's avatar
    techieanalyst_1
    Icon for Nimbostratus rankNimbostratus
    Jul 11, 2014

    so deploy the two and not just the one? Reverse Proxy and Edge via the F5? I have an edge with public IPs so I didn't think it would be needed

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jul 11, 2014

    Yes, you do need either DNS or hardware load balancing for edge services. In this case you are using HLB for reverse proxy, so you should also use it for edge.

     

    The Lync deployment guide has more information: https://f5.com/solutions/deployment-guides/tag/microsoft

     

    Also, here's a blog post that explains it more in depth: https://devcentral.f5.com/articles/the-hopefully-definitive-guide-to-load-balancing-lync-edge-servers-with-a-hardware-load-balancer

     

  • techieanalyst_1's avatar
    techieanalyst_1
    Icon for Nimbostratus rankNimbostratus
    Jul 11, 2014

    Been through them more than once, but as I said FQDNs and IP's don't seem to come online etc

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jul 11, 2014

    You might try running the BPA for Lync 2013 to make sure everything's good on that side: http://technet.microsoft.com/en-us/library/gg558584.aspx

     

    The iApp uses a base https monitor for the web services pools, so you should be able to use cURL from the BIG-IP command line to make sure that you are getting the respose that the monitor expects.

     

  • techieanalyst_1's avatar
    techieanalyst_1
    Icon for Nimbostratus rankNimbostratus
    Jul 11, 2014

    If my edge already has external IP addresses why would I need the Big IP to do this part for me?, I prefer staying away from NAT situations where they are not needed

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jul 11, 2014

    The recommended configuration is to have LTM load balance client connections to the edge servers' public IPs. The initial connection goes through the VIP and then the edge servers set up direct connections to external clients. In addition to the reasons given in the blog post, we can monitor the services on the edge servers, and there's an option to bring the edge VIPs down if internal SIP isn't responding.