290 likes | 463 Views
SERV302-R. Getting the Most out of Lync Server Monitoring Service Data. Nick Smith Principal Program Manager Microsoft Corporation. Can you fix it before you diagnose it?. Session Objectives And Takeaways. Session Objectives Describe the fundamentals of the Monitoring service
E N D
SERV302-R Getting the Most out of Lync Server Monitoring Service Data Nick Smith Principal Program Manager Microsoft Corporation
Session Objectives And Takeaways Session Objectives Describe the fundamentals of the Monitoring service What intelligence can you gather from the Monitoring server data How can you use this data to answer deployment questions How can you use the data to assist in troubleshooting your environment What other tools can you leverage beyond the built-in reports Takeaways Why is the Monitoring service a required component in every Lync Deployment Learn how to interpret the data in the monitoring server reports Learn how to turn the monitoring server into a powerful troubleshooting tool
Monitoring Service Components Clients All endpoints collect and report call quality data Call quality is reported based on data shared between endpoints during the call Server The server collects the call quality reports and call detail reports and submits into the monitoring databases Databases LcsCDR – Call Detail Records QoEMetrics – Quality of Experience Data Call Leg
How do Call Detail Reports get Collected? Front end servers relay all SIP traffic The agent evaluates SIP messages for: Registrations Response codes Diagnostic codes Meeting events This data is then sent to the LcsCDR database for collection To view this process enable Component logging of the UdcAgentcomponent
How is Call Quality data Collected? All media endpoints collect Quality of Experience (QoE) data At the end of the call, each endpoint reports its QoE data Call stream data is reported into the QoEMetrics database Look for ‘VQReport’ in SIP logs
QoEMetrics and LcsCDR Databases QoEMetricsand LcsCDRdatabase schemas are documented on TechNet Needed to write custom SQL queries This is a good reference for understanding metrics and associated thresholds Most in-box reports are based on pre-defined SQL Views • Key CDR Views • Conferences • ConferenceSessionDetails • Registration • SessionDetails • VoIPDetails • Key QoEViews • AudioStreamDetail • MediaLine • QoEReportsCallDetail • Session • VideoStreamDetail
Characteristics of a Poor Audio Call RatioConcealedSamplesAvg > 7% (0.07) The ratio of auto-generated audio data over real speech data, i.e. audio data is delayed or missed, due to network connectivity issues. PacketLossRate > 10% (0.1) Average packet loss rate during the call JitterInterArrival > 30ms Maximum network jitter during the call RoundTrip > 500ms Round trip time from RTCP statistics DegradationAvg > 1.0 The amount the Network MOS was reduced because of jitter and packet loss
Diagnostic logs “Thanks for reporting your issue – do you have logs with that?” Both diagnostic codes and media quality are collected and reported Correlate the user’s reported issue with the associated session reported via CDR/QoE Provides an objective view of the experience
Trend analysis Understand how to determine the scope of the issue Who else is impacted? How often does this happen? Why is it happening?
Proactive Operations Understanding Deployment Health Reviewing reports should be part of our daily operations Gives you a snapshot of usage, quality trending, worst performing servers, and top failures SCOM management pack can monitor the QoE database to identify locations preforming badly
Scenario review Report - Peer to peer audio call report
Scenario review Report - Conference call report
The Lync Call Quality Methodology • Voice Quality Framework • Uses Network Telemetry in QoE • Prescriptive approach for measured improvements • Service Management end state
Health Analysis Tool • Allows you to focus on the most frequent diagnostic codes affecting service reliability • Download as part of the RASK http://aka.ms/LyncRASK
Adoption Dashboard • Designed to enhance the tracking of your adoption rates • Complements the ‘in-box’ usage reports • Provides: • Registered Users • Active Users • Usage Charts by modality • P2P Sessions • Conferences • Dial-in Conferences • Total Session Minutes • Will be released publically soon via the RASK
In Review: Session Objectives And Takeaways Session objectives Describe the fundamentals of the Monitoring service What intelligence can you gather from the Monitoring server data How can you use this data to answer deployment questions How can you use the data to assist in troubleshooting your environment What other tools can you leverage beyond the built-in reports Takeaways Why is the Monitoring service a required component in every Lync Deployment Learn how to interpret the data in the monitoring server reports Learn how to turn the monitoring server into a powerful troubleshooting tool
Common Questions From Users What was wrong with this call? Why did I see a User Facing Diagnostic (UFD)? I was just on a call and it dropped mid stream. Why? From Administrators How do I read the in-box reports? How can I determine what the value of X in a particular report means? Where do I start?
Scenario review Overview - Where do I start
Scenario review Report - Peer to peer audio call report
Scenario review Report - Conference call report
Scenario review Report - Top failures