Lync Centralized Logging

Lync Server 2013 introduced Centralized Logging. Each Lync Server runs a service that can receive commands from any other Lync Server to enable logging for troubleshooting scenarios. For Edge Servers, you must make sure that port 50001 to 50003 TCP is open from your Front End Servers to each server in the Edge Server Pool. These ports are used to communicate centralized logging commands. Windows Firewall is modified as part of the installation; however, these ports must be considered for any other firewalls in the environment. The following example uses centralized logging to collect data on an Edge Server Pool:

1. Open the Lync Server Management Shell.

2. Navigate to the CLS directory, which by default is C:Program FilesCommon FilesMicrosoft Lync Server 2013ClsAgent.

3. Type the following command to enable logging for the Instant Messaging and Presence scenario:

Clscontroller.exe –start –scenario im –pools edgepool.companyabc.com

4. After the logging is enabled, reproduce the issue you are trying to troubleshoot.

5. From the same command prompt, run the following command to stop logging on the Edge Server Pool:

Clscontroller.exe –stop –scenario –im –pools edgepool.companyabc.com

6. The next two commands must be executed to search and export any logs from the Edge Server Pool. If required, you can filter by specific components; however, this example will simply export data for all tracing components.

Click here to view code image

Clscontroller.exe –flush –pools edgepool.companyabc.com
Clscontroller.exe –search –pools edgepool.companyabc.com –loglevel verbose > c:EdgeLog.TXT

7. If you do not pipe the command to a text file, the log results will simply display in the command prompt. However, given the large amount of data in these log files, it is recommended to pipe to a text file.

8. At this point, you now have a readable log file from the Edge Server Pool. This file can be opened in Notepad or in Snooper.exe for viewing.