In this article we will have a look at the Centralized Logging Service (CLS) and csclslogging feature in Lync 2013.
These both logging features will help us to identify any issues in the pool.
These 2 features are available only from Lync 2013
First lets have a look at the Centralized Logging Service (CLS)
This is located in the directory
C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent
Below are the commands that can help you out to identify an issue through clscontroller
ClsController.exe -start –scenario <scenario> –pools <pool fqdn>
ClsController.exe -stop –scenario <scenario> –pools <pool fqdn>
ClsController.exe -flush –pools <pool fqdn>
ClsController.exe -search –pools <pool fqdn> –components <component> –loglevel <loglevel>
Below are the supported scenarios
AlwaysOn, MediaConnectivity, ApplicationSharing, AudioVideoConferencingIssue, HybridVoice, IncomingAndOutgoingCall, VoiceMail, IMAndPresence, AddressBook, DeviceUpdate, LYSSAndUCS, CLS, SP, WAC, UserReplicator, HostedMigration, MonitoringAndArchiving, LILRLegacy, LILRLYSS, MeetingJoin, RGS, CPS, XMPP and CAA.
Note : This ClsController.exe is present only in the RTM release and later microsoft came up with this powershell based control which is CsClsLogging
The Search-CsClsLogging cmdlet provides a command line option for searching the log files generated by the centralized logging service. Lync administrators can analyze the issue with the cmdlet.
You can run run Search-CsClsLogging cmdlet with start time and end time
You can use show-cslogging to check the current status of the centralised logging service
The following inputs are supported
There is a service responsible for this operation which is called Lync Server Centralized Logging Service Agent.
So make sure that this service is running else we will face issues in running these commands.