Microsoft Communications Server “14” Monitoring and Reporting

Jared ZhangProgram Manager

Arish AlrejaProgram ManagerMicrosoft Corporation

SESSION CODE: UNC316

Session Objectives and TakeawaysObjectives:

Describe CS “14” health monitoringWalk through CS “14” reporting with the Monitoring Server role

Takeaways:Use the CS Management Pack (MP) for System Center Operations Manager (SCOM) to monitor the health of CS “14”Use the CS “14” Monitoring Server role for reporting of usage, call reliability and media quality

AgendaCS “14” health monitoring with SCOM

Service, component and voice quality monitoringDemo: CS “14” health monitoring with synthetic transactions and SCOM

CS “14” reporting with the Monitoring Server roleUsage, call reliability and media quality data collectionReporting of usage, call reliability and media qualityDemo: CS “14” Monitoring Server reports

Summary

CS “14” Health Monitoring

CS “14” Health Monitoring GoalsAccurate alerts

Filter out transient conditions to reduce noiseDistinguish alerts based on the impact to the systemTrack the current state of alerts (active or resolved)

Actionable alertsCause and recommended actionsRelevant information to identify and isolate problemsGuidance for troubleshooting

CS “14” Health MonitoringHealth monitoring for CS “14”

Service monitoringEnd-to-end verification of availability of CS services

Component monitoringMonitoring components running on individual CS servers

Voice Quality monitoringMonitoring end-user call reliability and media quality experience

CS “14” MP for SCOM 2007 R2Monitoring and alerting on services, components and voice qualityCentral discovery of monitored objects from CS “14” Central Management Store (CMS)

Service Monitoring with Synthetic TransactionsSynthetic transactions (STs)

End-to-end scenario viewPowerShell cmdlets starting with the Test verb

Example: Test-CsIMRun with configured test accounts or real user credentialsProvide a success/failure response

SCOM alertingCore set of STs are run periodically to verify service availabilityST failures result in high priority alertsAlerts are auto-resolved if STs succeed in the next run

Synthetic TransactionsSynthetic Transaction Purpose Running in SCOM?

Test-CsRegistration Tests client registration Y

Test-CsIM Tests peer-to-peer IM Y

Test-CsP2PAV Tests peer-to-peer AV Y

Test-CsAVConference Tests AV conferencing Y

Test-CsGroupIM Tests IM conferencing Y

Test-CsPresence Tests presence updates Y

Test-CsDialInConferencing Tests PSTN conferencing attendant (CAA) Y

Test-CsGroupExpansion Tests group expansion

Test-CsAddressBookServiceTest-CSAddressBookWebQuery Tests address book download and query

Test-CsPstnOutboundCallTest-CsPstnPeerToPeerCall Tests PSTN outbound and P2P

Test-CsFederatedPartner Tests connection to a federated domain

Run Synthetic Transactions as PowerShell CommandLetsFailure making a PSTN outbound call:

PS C:\> Test-CsPstnOutboundCall -TargetFqdn pool0.vdomain.com -TargetPstnPhoneNumber +15551234567

TargetFqdn : pool0.vdomain.comResult     : FailureLatency    : 00:00:00.2409772Error      : 504, Server time-outDiagnosis  : ErrorCode=1005,Source=accessproxy.vdomain.com,Reason=Cannot route to

destination domain Microsoft.Rtc.Signaling.DiagnosticHeader

Success making a PSTN outbound call:PS C:\> Test-CsPstnOutboundCall -TargetFqdn pool0.vdomain.com -TargetPstnPhoneNumber

+15551234567

TargetFqdn : pool0.vdomain.comResult     : SuccessLatency    : 00:00:04.0974690Error      : Diagnosis  :

SCOM Alert Created by Synthetic Transaction Failures

Component MonitoringHealth modeling for CS “14” components

Key health indicator (KHI) and non-KHIsEvents and performance counters are categorized as service impacting aspects (KHIs) and non-service impacting aspects (non-KHIs)KHI indicates a service impacting condition

SCOM alertingKHIs result in medium priority alertsKHI alerts are auto-resolved if the component returns to healthyNon-KHIs result in informational alerts that need manual resolving

SCOM Alert Created by Component KHIs

Call Reliability MonitoringCall reliability data are stored as Call Detail Records (CDR) dataFailures are classified as “Expected” and “Unexpected”, based on the ms-diagnostic ID

Example: 52031 indicates media connectivity failureSCOM alerting

Categories for call reliability alerting:Peer-to-peer audio/video callsAudio/video conference calls

Alerts are raised for higher than expected failure ratesEach alert contains a CDR report link for troubleshooting

Call Reliability Alert Details

Media Quality MonitoringMedia quality data are stored as Quality of Experience (QoE) dataCalls are classified as good/poor quality, based on a set of key QoE metrics

Network degradation, RTT, package loss, jitter, healer metricsSCOM alerting

Categories for media quality alerting:A/V Conferencing Servers, Mediation Servers, GatewaysNetwork locations (subnets/sites/regions)

Alerts are raised for higher than expected poor quality call ratesEach alert contains a QoE report link for troubleshooting

CS “14” Health Monitoring with Synthetic Transactions and SCOMJared ZhangProgram ManagerMicrosoft Corporation

DEMO

CS “14” Reporting with the Monitoring Server roleArish AlrejaProgram ManagerMicrosoft

Improvements for the CS “14” Monitoring Server roleCall Detail Records (CDR) data collection

Improved diagnostic information for all modalities in CS “14”Registration diagnostic dataIP phone inventory data

Quality of Experience (QoE) data collectionRicher endpoint data (OS, MAC address, CPU)Richer audio metrics (User facing diagnostics, audio healer metrics)Coverage on Media Bypass, Mediation Server – multiple gateways

Improvements for the CS “14” Monitoring Server RoleReporting improvements

Dashboard view of key system usage and troubleshooting informationFor return-on-investment (ROI) analysis and asset management

Usage reports for visibility into the deploymentIP phone devices used in the deployment

For operational monitoring and diagnosticsCall reliability/media quality reports for troubleshooting

For Helpdesk responding to end-user complaintsUser activity report

Reports can be subscribed for periodic email deliveryReports are accessible from CS “14” Control Panel UI

Access Monitoring Server Reports from CS Control Panel

Monitoring Server Dashboard

Monitoring Server Report Homepage

Reporting for CS “14” with Monitoring ServerArish AlrejaProgram ManagerMicrosoft

DEMO

Summary and Key TakeawaysUse CS “14” Management Pack for SCOM 2007 R2:

System health monitoringCall reliability and media quality monitoring

Use CS “14” Monitoring Server dashboard and reports:Managers: return-on-investment (ROI) analysisIT pros: call reliability and media quality troubleshootingHelpdesk: end-user troubleshooting

Related Breakout SessionsMonday 4:30PM UNC320 CS “14”: What's New in Communicator “14” Experience & Backend Amit Gupta

Tuesday

9:45AM UNC311 CS “14”: Architecture Mahendra Sekaran

1:30PM UNC313 CS “14”: Voice Architecture and Planning for High Availability Jamie Stark

3:15PM UNC312 CS “14”: Network Considerations Neil Deason

9:45AM UNC317 CS “14”: What’s new in Manageability Anand & Cezar

5:00PM UNC314 CS “14”: Voice Deployment Jamie Stark

Wednesday

8:00AM UNC318 CS “14”: What's New in Conferencing Experience & Backend Cameron & Tim

9:45AM UNC317 CS “14”: What’s new in Manageability Anand & Cezar

11:45AM UNC321 CS “14”: Interoperability: Voice, Video, Conferencing, IM, & Presence Francois Doremieux

1:30PM UNC316 CS “14”: Monitoring and Reporting Jared & Arish

5:00PM UNC315 CS “14”: Setup and Deployment Peter Schmatz

Thursday 9:45AM UNC208 CS “14”: What's New in Devices Avi & Sachin

You are here

Questions?

Unified Communications Track Call to Action!

Learn More!View Related Unified Communications (UNC) Content at TechEd/after at TechEd OnlineVisit microsoft.com/communicationsserver for more Communications Server “14” product informationFind additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on TwitterCheck out Microsoft TechNet resources for Communications Server and Exchange ServerVisit additional Exchange 2010 IT Professional-focused content

Partner Link or Customer Link (Name: ExPro Pword: EHLO!world)

Try It Out!Exchange 2010 SP1 Beta download is now available from the download center!

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

Complete an evaluation on CommNet and enter to win!

Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st

http://northamerica.msteched.com/registration

You can also register at the

North America 2011 kiosk located at registrationJoin us in Atlanta next year

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

Appendix

Synthetic Transaction to Verify IM Conferencing

Synthetic Transaction to Verify PSTN Outbound Call

Alert Views in SCOM

ST Alerting in SCOM

Component Alerting in SCOM

Call Reliability Alerting in SCOM

Monitoring Server Dashboard

Monitoring Server Report Homepage

Conference Summary Report

Conference Usage Trend

Peer-to-Peer Activity Reliability Report

Failure Distribution Report

Peer-to-Peer Activity Reliability Report – Call List

Location-based Media Quality Report

Location-based Media Quality Report - Drilldown

Location-based Media Quality Report – Trend

Call List - Poor Quality Calls are Highlighted

User Activity Report – Full List of User Activities

Call Detail Report – Details of a Particular Call

JUNE 7-10, 2010 | NEW ORLEANS, LA