Advanced Troubleshooting Scott Stubberfield

OFC-B411

Goals for today’s sessionReview applicable troubleshooting toolsDiscuss a systematic approach to troubleshootingDiagnose and resolve some common problems

Tools

Snooper

“The” tool that you will use to help diagnose and troubleshoot Lync client and server issuesReleased in Lync 2013 as part of the “Debugging Tools”Can be used to read server or client side logs

Snooper

http://www.microsoft.com/en-us/download/details.aspx?id=35453

Tools

Centralized Logging Service

New in Lync Server 2013Improves log file collection over the Lync Server Logging ToolEnables IT admin to manage logging and search logs across all Lync Servers in a deployment centrally

Start, stop, and flush trace logging for any/all machines in a deployment from one placeStart/stop logging based on scenariosSee what logging is turned on per pool/machine for the entire deploymentSearch trace logs based on specified parameters from a centralized place

Centralized Logging Service (CLS)

CLSAgentRuns on every Lync ServerControls logging based on commands from CLSControllerManages log files to ensure drive space is not consumed, moves old logs to fileshare

CLSControllerSends Start, Stop, Flush, and Search commands to all the CLSAgents in the deploymentAggregates search results from CLSAgentsAvailable on every Lync Server in “C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent”

CLS Architecture

CLSControllerFE

CLSAgent

FE

CLSAgent

FE

CLSAgent

Start, Stop, Search commands

Start, Stop, Search commands

Start, Stop, Search comm

ands

Search results

Search results

Search results

Logging is based on scenariosBuilt in scenarios specify a group of components and log levels to be started and stopped together

Scenarios

ACPMCUAddressBookAlwaysOnApplicationSharingAudioVideoConferencingIssueCAACLSCPSDeviceUpdate

HostedMigrationHybridVoiceIMAndPresenceIncomingAndOutgoingCallLILRLegacyLILRLYSSLYSSAndUCSMediaConnectivity

MeetingJoinMonitoringAndArchivingPowershellRGSSPUserReplicatorVoiceMailWACXMPP

Scenario details can be discovered with theGet-CsClsScenario cmdlet

Components Logged by ScenariosEg. for scenario:IncomingAndOutgoingCallName Level Flags

MediationServer Info All

S4 Info All

Sipstack Info All

TranslationApplication Info All

OutboundRouting Info All

InboundRouting Info All

UserServices Verbose

TF_Component,TF_CM,TF_Protocol

Get-CsClsScenario global/<ScenarioName> |Select -ExpandProperty Provider |Format-Table Name,Level,Flags -a

The “AlwaysOn” ScenarioThe special scenario “AlwaysOn” can be on all the time. It logs INFO level for many common componentsWhen an issue occurs there may be enough info in the AlwaysOn component logs to debug the issueThis avoids having to turn on logging and repro the issue, which was always required in Lync Server 2010If the logs from AlwaysOn are not sufficient, turn on the specific scenario relevant to your issue, repro the issue, and get a higher level of loggingAt any given time, you can have one extra scenario enabled along with AlwaysOn

Custom ScenariosIf the default scenarios are not enough or the logging level is not high enough for you, then you can create your own custom scenario

$a = New-CsClsProvider -Name "Sipstack" -Type "WPP" -Level "Verbose" -Flags "All"New-CsClsScenario -Identity "Global/CustomVerbose3" - provider $a$b = New-CsClsProvider -Name “OutboundRouting" -Type "WPP" -Level "Verbose" -Flags "All"$c = New-CsClsProvider -Name "InboundRouting" -Type "WPP" -Level "Verbose" -Flags "All"$d = New-CsClsProvider -Name "S4" -Type "WPP" -Level "Verbose" -Flags "All"Set-CsClsScenario -Identity "global/CustomVerbose3" -Provider @{Add=$b,$c,$d}

It make take a short period of time for the new custom scenario to be available for starting/stoppingNote: There is a known bug when specify “All” for the level, therefore use Verbose

Start AlwaysOn logging for entire deploymentstart-csclslogging -scenario AlwaysOn

Start another scenario for a specific poolstart-csclslogging -scenario IncomingAndOutgoingCall -pools pool1.contoso.com

Start another scenario for a specific serverstart-csclslogging -scenario IncomingAndOutgoingCall –computers fe1.contoso.com

Stop loggingstop-csclslogging -scenario IncomingAndOutgoingCall

Starting and Stopping Logging

Get the current Sipstack log for a specific poolsearch-csclslogging -components Sipstack -pools pool1.contoso.com –outputfilepath c:\logs\sip.log –loglevel Verbose

The “sip.log” text file can be opened in any text editor or in SnooperLeave out the “pools” parameter to aggregate all Sipstack logs or use the “computers” parameter to pull the log from one computerNote: If you have created a custom scenario and changed the default log level you must specify which level you would like to search for by using the “loglevel” switch otherwise the higher level results will not be included in your search

Searching Logging

14

The logs are stored in %temp%\Tracing for the Network Service account profile

Trace File Location

There are some great resources out there that you can use to learn more about CLShttp://technet.microsoft.com/en-us/library/jj688101.aspx http://www.mylynclab.com/2013/04/lync-2013-centralised-logging-deep-dive.htmlhttp://blogs.technet.com/b/jenstr/archive/2012/08/01/using-centralized-logging-service-in-lync-server-2013-preview.aspx

Additional Resources

Demo

Problem Identification and Resolution

Support IncidentA user has reported that he is unable to call a co-worker. The co-worker uses a PBX phone and can be reached at 1-425-555-1002. The user would typically dial 1002 and the call would complete however today that is not working. The support ticket indicated he was working from home at the time.

External Client

PBX Phone14255551002

Lync

Our ApproachPerform investigations using relevant log files and using systematic troubleshooting techniques, isolate and fix these problems one at a time.

Note: You spoke with the Telephony administrator that is responsible for routing the call destined to 1-425-555-1002 and that system has been verified to have no issues.

Resources

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

msdn

Resources for Developers

http://microsoft.com/msdn

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Sessions on Demand

http://channel9.msdn.com/Events/TechEd

Complete an evaluation and enter to win!

Evaluate this session

Scan this QR code to evaluate this session.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.