Forum Discussion

jwashburn_48359's avatar
jwashburn_48359
Icon for Nimbostratus rankNimbostratus
Nov 13, 2013

Lync 2013 using iApp - Reverse Proxy Issues

Using iApp f5.microsoft_lync_server_2010_2013.v1.2.0 with a new Lync 2013 deployment.   Having some problems getting internal mobile clients working. We are currently testing with the Microsoft L...
deployment
devops
iApps
lync 2013
reverse proxy
mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Nov 13, 2013

Hi, there is a typo in the template. The iApp should create pool members at port 4443 for those IPs. We'll get that fixed ASAP, sorry.

 

Is the "_new_edge_external_ip_reverse_proxy_front_end_4443_pool" pool up? Are you seeing tcp requests to those pool members when the Lync Analyzer tries to connect?

 

thanks Mike

 

  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    OK good that at least means I am not crazy. All the pools are up on both sides except for a few on the internal side that we don't use such as 448, 5068, 5080.
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    Its almost as the traffic is getting black holed on the f5. Running a tcpdump, I see the traffic coming in from a client, but it never forwards it on to the next destination
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Nov 13, 2013
    Can you post your _secure_reverse_proxy iRule here? I'm curious if traffic is even getting by that.
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    when HTTP_REQUEST { switch -glob [string tolower [HTTP::host]] { csweb.domain.corp* { pool Lync2013_External_edge_external_ip_reverse_proxy_front_end_4443_pool } cswebdir.domain.corp* { pool Lync2013_External_edge_external_ip_reverse_proxy_director_4443_pool } meet.domain.corp* { pool Lync2013_External_edge_external_ip_reverse_proxy_director_4443_pool } dialin.domain.corp* { pool Lync2013_External_edge_external_ip_reverse_proxy_director_4443_pool } lyncdiscover.domain.corp* { pool Lync2013_External_edge_external_ip_reverse_proxy_director_4443_pool } } }
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    Looking at the rule I noticed a problem with a typo for the meet domain. I updated it and tested again. No change. Here is the current rule
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    In your lab does the _edge_internal_ip_reverse_proxy_front_end_4443 show as Available? Both that one and _edge_internal_ip_reverse_proxy_director_4443 are showing as Unknown, but when I expand it, they show Green and available under it?
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Nov 13, 2013
    Yes, they are both available. Is the virtual server displaying Unknown, but the pool members are green?
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    Correct.
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Nov 13, 2013
    That doesn't sound right. Under the Resources tab for the _new_edge_internal_ip_reverse_proxy_front_end_4443 and _new_edge_internal_ip_reverse_proxy_director_4443 virtual servers, is the correct pool assigned as the default pool?
  • jwashburn_48359's avatar
    jwashburn_48359
    Icon for Nimbostratus rankNimbostratus
    Nov 13, 2013
    Lync2013_Internal_edge_internal_ip_reverse_proxy_director_4443 Unknown Virtual Server Lync2013_Internal_edge_internal_ip_reverse_proxy_director_4443_pool Available Pool Lync2013_Internal_edge_internal_reverse_proxy_director_https_monitor Monitor Lync2013_Internal_edge_internal_reverse_proxy_director_tcp_5061_monitor Monitor x.x.x.43:4443 Available Pool Member x.x.x.43 Unknown Node x.x.x.44:4443 Available Pool Member x.x.x.44 Unknown Node