For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Arun_Kumar_1295's avatar
Arun_Kumar_1295
Icon for Nimbostratus rankNimbostratus
Aug 13, 2013

Lync Edge server integraion :Public IP

Hi,

 

I am doing Lync implemantation with the F5.

 

My WAN link will be terminate on the Fortigate firewall, and doing nating with the private IP. i.e if we have three public ip we will nat one to one with the 3 private ip.

 

But as per F5 and Microsoft documentation, we require 9 public ip for the Edge server. I have attached my topology design for F5 implementation. Need your advice for the same.

 

“Each Lync Edge server should have a unique publicly routable IP address for each of the three Edge services (Access, A/V, and Web Conferencing) in addition to one unique public IP address for each service’s BIG-IP virtual server. If you are deploying two Edge servers, you would need 9 publicly routable IP addresses”

 

Excerpt from Microsoft Edge Server deployment guide :

 

Lync Server 2010 Scaled Consolidated Edge (hardware load balanced) Requires three public IP address for load balancer virtual IP addresses (one time requirement that does not increment as more Edge Servers are added to the pool) plus three public IP addresses per Edge Server in a pool.

 

availability
deployment
design
devops
iApps
microsoft

4 Replies

  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Aug 14, 2013
    i don't see anything attached and i don't really see a question, what is your exact question?
  • marvn_58503's avatar
    marvn_58503
    Icon for Nimbostratus rankNimbostratus
    Aug 14, 2013
    There's no question here, but as someone who extensively uses LTM with Lync 2010 / 2013 I'll give you some info. The reason you need to use real public IP addresses is the SIP traffic that Lync sends/receives. Lync hardcodes the real IP address within the SIP packets so if you use any kind of NAT on it, it ceases to work. You must use three public IPs for your Edge pools - one each for AV / Webconf / Access - and each Edge server has one IP for each. So if you have two Edge servers you need 9 public IPs, if you have three Edge servers you need 12, and so on. This is per pool as well, so if you've got another pool you'll need 3 more public IPs. Hopefully this will help explain why, please say if you need to ask more.