Share via

Troubleshooting: Replication Among Lync Server Standard and Edge Server

  • Article

Introduction

We have the following set topology, 

http://3.bp.blogspot.com/-CDX8ZYslWEY/TynFpp8sQLI/AAAAAAAAC7Q/ch2c18S9wwo/s640/topologia.jpg 
 

The Edge Server is configured and policies established publishing the Standard Pool.
The steps of the settings are on the Article Instalação do Lync Edge Server em DMZ Double Hop (pt-BR)

Sintoma

The connections policies and changes are not applied in the Edge Pool, and the connections of users are denied access outside. Using the cmdlet Get-CsManagementStoreReplicationStatus shows the replication server with status Edge UpToDate: False

Get-CsManagementStoreReplicationStatus

http://3.bp.blogspot.com/-UKNW1sib7GU/Ty6Kal-0kxI/AAAAAAAADDI/5pDhyzCKsIE/s320/ErrEg02.png 

Cause

This problem usually is related to the network settings of the structure Lync Server.
To begin identifying the problem access the Topology Builder and display settings Edge Pools

http://3.bp.blogspot.com/-2l6xvB5_Etw/Ty6KaDmnbuI/AAAAAAAADDA/H34bsVqkuDg/s320/ErrEg01.png 

Solution 1°

The networks between the Standard Pool and Edge Pool must be routed, and the internal servers should be able to resolve the name Fqdn Edge server.
Create a firewall rule allowing ICMP packets from the internal network and has set the FQDN of the drip Edge Server.
In this case:

Internal Server FQDN: HmEdge.home.intranet
Internal IP address: 172.16.0.200

http://4.bp.blogspot.com/-IOMwxuicv1c/Ty6KbDRJzAI/AAAAAAAADDQ/48cuZNBB2CM/s320/ErrEg03.png 

If name resolution fails manually create a record in the DNS server's Active Directory Domain to host the *Edge Server *

http://3.bp.blogspot.com/-Tq0KskoJp-4/TyWXFu02j_I/AAAAAAAAC0k/LmhhiVhuuD4/s320/edge01.png 

And check the network configuration of the Edge Server, the IP address of the internal card must be configured with the same ip Topolog Builder Internal IP address: 172.16.0.200. And the configured routes must have an entry for the internal network.

http://3.bp.blogspot.com/-qbl33_XKKjE/Ty6RF81E-tI/AAAAAAAADDo/mfwhSLkrCz4/s320/ErrEg06.png 

Solution 2°

The port configuration Internal Configuration Replication Port (HTTPS) should be allow from the origin server for the ip Back End of inner network adapter of the Edge Server.
The default port for replication is 4443/TCP.
To check this setting run in the Back End cmdlet to force replication of servers.
*
*To check this setting run in the Back End cmdlet to force replication of servers

Invoke-CsConfigurationStoreReplication

http://2.bp.blogspot.com/-OCxtEpdnFdk/TysoH7CeCHI/AAAAAAAADCY/AxGiTA_sp2c/s640/edge108.png 

Verify on the firewall that separates the Back End and Edge Server

http://3.bp.blogspot.com/-QpTQ1hBxBzM/Ty6KbkPAsbI/AAAAAAAADDY/KOJo_vRoLtw/s320/ErrEg04.png 

Create a rule allowing the port 4443/TCP with origin the Back End and destination to inner network card of the Edge Server. The firewall log should show the connection successfully established.

http://4.bp.blogspot.com/-Yxcnwq4O7_E/Ty6KcG4myLI/AAAAAAAADDg/qNZWuikbxj0/s320/ErrEg05.png 

Solution 3°

The service responsible for keeping the connection must be initiated replication in the Edge Server. Start the Management Console on the Edge Server service and verify that the service Lync Replica Replicator Server Agent is started and configured to run as Network Service

http://2.bp.blogspot.com/-5bGGToXYzDY/Ty6YeCHxyUI/AAAAAAAADDw/Y0l3ErAqFZo/s320/ErrEg07.png

Other Languages

This article is also available in the following languages:

This article was originally written by: 
Fernando Lugão Veltem
**blog: **http://flugaoveltem.blogspot.com 
**twitter: **@flugaoveltem