Microsoft UC User GroupNorway (MUCUGN)

Troubleshooting Lync 2013Get-help *CsClsLogging*• Lasse Nordvik Wedø• Senior Architect – Unified

Communications• Datametrix AS

Agena• The problem

• The Lync 2010 «solution»

• The Lync 2013 solution

• Start-CsClsLogging

• Update-CsClsLogging

• Stop-CsClsLogging

• Sync-CsClsLogging

• Search-CsClsLogging

• Common errors

• Snooper tool

• Resources

• ???

The problem• User reports an error• No conclusive error messages• Large deployments may be hard to

troubleshoot

• Lync logging tool• Installed with system• Run one instance on each server• Many switches to turn on/off• Textfiles hard to read out of the box

• Resource Kit Tools• Includes Snooper tool, excellent to read

sip messages

• Monitor reports

The Lync 2010 «solution»

• One ClsController to rule them all• ClsAgent will run on all Lync servers• 50001• 50002• 50003

• Gather logs from one central server• One file to analyze• «Easier» to log right action, based on

scenarios

The Lync 2013 solution

• Commands to configure the environment• Get-CsClsScenario• Set-CsClsScenario• Get-CsClsConfiguration• Set-CsClsConfiguration

• Can see or alter scenarios• Change folders• Control file sizes

Get/Set-CsCls*

• Can be started from any server in your farm• Must reach all members on the 5000X port• Must be run with administrative rights• Can not be run in ISE (Will start, but no

output)

• Start-csclslogging• Scenario• Pools • Duration (NA for alwayson)

Start-CsClsLogging

• Used to update duration

• Update-CsClsLogging• Duration• Pool

Update-CsClsLogging

• Unless «Duration» is set, remember to stop logging

• Always remember to stop «alwayson»• Not uncommon with a «wpp error»• Retry stop-CsClsLogging after a couple of minutes

• Stop-CsClsLogging• Scenario• Pool

Stop-CsClsLogging

• Used to flush the cache• Make sure you get all the gathered

information

• Sync-CsClsLogging• Pools

Sync-CsClsLogging

• Dump logs to file• Selective or all

• Search-CsClsLogging• Pools• Loglevel• Starttime («8/31/2013 8:00AM»)• EndTime («8/31/2013 11:00AM»)• URI (sip:lasse.nordvik.wedo@datametrix.no)• Matchall• Matchany• Outputfilepath

Search-CsClsLogging

• Get-Command Get-cscls*• Use Get-help• Stop/start –cswindowsservice rtcclsagt• Start-csclslogging –pool poolname –scenario cls• Read eventviewer• Check region setting (wrong start/end-time)• %temp%\tracing = C:\Windows\ServiceProfiles\

NetworkService\AppData\Local\Temp\Tracing (not your user %temp%)

Troubleshoot-CsClsLogging

• 2013 = New and improved• All features from 2010 +• Call flow chart• Merge flow items• Group flow item

Snooper tool

• Lync 2010 Resourse kit tools download: • http://www.microsoft.com/en-us/download/details.aspx?id=21165

• Lync 2013 Resourse kit tools download: • http://www.microsoft.com/en-us/download/details.aspx?id=36821

• Microsoft Lync Server 2013 Debugging Tools• http://www.microsoft.com/en-us/download/details.aspx?id=35453

• Microsoft Technet Library CsClsLogging• CMDLETS: http://technet.microsoft.com/en-us/library/jj205064.aspx• Using the Centralized Logging Service• http://technet.microsoft.com/en-us/library/jj688101.aspx

Resources

Q&A

• $provider1 = New-CsClsProvider -Flags All -Level All -Name SipStack -Type WPP

• $provider2 = New-CsClsProvider -Flags All -Level All -Name ExUmRouting -Type WPP

• $provider3 = New-CsClsProvider -Flags All -Level All -Name InboundRouting -Type WPP

• New-CsClsScenario -Identity global/VoicemailVerbose -Provider @{Add=$provider1,$provider2,$provider3}

Get/Set-CsCls*