1 / 52

Microsoft Communications Server “14” Monitoring and Reporting

Required Slide. SESSION CODE: UNC316. Microsoft Communications Server “14” Monitoring and Reporting. Jared Zhang Program Manager Arish Alreja Program Manager Microsoft Corporation. Blank Background option for use with content that extends over Purple line art .

christmas
Download Presentation

Microsoft Communications Server “14” Monitoring and Reporting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Required Slide SESSION CODE: UNC316 Microsoft Communications Server “14” Monitoring and Reporting Jared Zhang Program Manager Arish Alreja Program Manager Microsoft Corporation

  2. Blank Background optionfor use with content that extends over Purple line art Session Objectives and Takeaways Objectives: • Describe CS “14” health monitoring • Walk 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

  3. Blank Background optionfor use with content that extends over Purple line art Agenda • CS “14” health monitoring with SCOM • Service, component and voice quality monitoring • Demo: CS “14” health monitoring with synthetic transactions and SCOM • CS “14” reporting with the Monitoring Server role • Usage, call reliability and media quality data collection • Reporting of usage, call reliability and media quality • Demo: CS “14” Monitoring Server reports • Summary

  4. CS “14” Health Monitoring

  5. Blank Background optionfor use with content that extends over Purple line art CS “14” Health Monitoring Goals • Accurate alerts • Filter out transient conditions to reduce noise • Distinguish alerts based on the impact to the system • Track the current state of alerts (active or resolved) • Actionable alerts • Cause and recommended actions • Relevant information to identify and isolate problems • Guidance for troubleshooting

  6. Blank Background optionfor use with content that extends over Purple line art CS “14” Health Monitoring • Health monitoring for CS “14” • Service monitoring • End-to-end verification of availability of CS services • Component monitoring • Monitoring components running on individual CS servers • Voice Quality monitoring • Monitoring end-user call reliability and media quality experience • CS “14” MP for SCOM 2007 R2 • Monitoring and alerting on services, components and voice quality • Central discovery of monitored objects from CS “14” Central Management Store (CMS)

  7. Blank Background optionfor use with content that extends over Purple line art Service Monitoring with Synthetic Transactions • Synthetic transactions (STs) • End-to-end scenario view • PowerShell cmdlets starting with the Test verb • Example: Test-CsIM • Run with configured test accounts or real user credentials • Provide a success/failure response • SCOM alerting • Core set of STs are run periodically to verify service availability • ST failures result in high priorityalerts • Alerts are auto-resolved if STs succeed in the next run

  8. Synthetic Transactions

  9. Run Synthetic Transactions as PowerShell CommandLets Failure making a PSTN outbound call: PS C:\> Test-CsPstnOutboundCall -TargetFqdn pool0.vdomain.com -TargetPstnPhoneNumber +15551234567 TargetFqdn: pool0.vdomain.com Result     : Failure Latency    : 00:00:00.2409772 Error      : 504, Server time-out Diagnosis  : 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.com Result     : Success Latency    : 00:00:04.0974690 Error      : Diagnosis  :

  10. Blank Background optionfor use with content that extends over Purple line art SCOM Alert Created by Synthetic Transaction Failures

  11. Component Monitoring • Health modeling for CS “14” components • Key health indicator (KHI) and non-KHIs • Events and performance counters are categorized as service impacting aspects (KHIs) and non-service impacting aspects (non-KHIs) • KHI indicates a service impacting condition • SCOM alerting • KHIs result in medium priority alerts • KHI alerts are auto-resolved if the component returns to healthy • Non-KHIs result in informational alerts that need manual resolving

  12. Blank Background optionfor use with content that extends over Purple line art SCOM Alert Created by Component KHIs

  13. Call Reliability Monitoring • Call reliability data are stored as Call Detail Records (CDR) data • Failures are classified as “Expected” and “Unexpected”, based on the ms-diagnostic ID • Example: 52031 indicates media connectivity failure • SCOM alerting • Categories for call reliability alerting: • Peer-to-peer audio/video calls • Audio/video conference calls • Alerts are raised for higher than expected failure rates • Each alert contains a CDR report link for troubleshooting

  14. Call Reliability Alert Details

  15. Blank Background optionfor use with content that extends over Purple line art Media Quality Monitoring • Media quality data are stored as Quality of Experience (QoE) data • Calls are classified as good/poor quality, based on a set of key QoE metrics • Network degradation, RTT, package loss, jitter,healer metrics • SCOM alerting • Categories for media quality alerting: • A/V Conferencing Servers, Mediation Servers, Gateways • Network locations (subnets/sites/regions) • Alerts are raised for higher than expected poor quality call rates • Each alert contains a QoEreport link for troubleshooting

  16. CS “14” Health Monitoring with Synthetic Transactions and SCOM Jared ZhangProgram ManagerMicrosoft Corporation DEMO

  17. CS “14” Reporting with the Monitoring Server role Arish Alreja Program ManagerMicrosoft

  18. Blank Background optionfor use with content that extends over Purple line art Improvements for the CS “14” Monitoring Server role • Call Detail Records (CDR) data collection • Improved diagnostic information for all modalities in CS “14” • Registration diagnostic data • IP phone inventory data • Quality of Experience (QoE) data collection • Richer endpoint data (OS, MAC address, CPU) • Richer audio metrics (User facing diagnostics, audio healer metrics) • Coverage on Media Bypass, Mediation Server – multiple gateways

  19. Improvements for the CS “14” Monitoring Server Role • Reporting improvements • Dashboard view of key system usage and troubleshooting information • For return-on-investment (ROI) analysis and asset management • Usage reports for visibility into the deployment • IP phone devices used in the deployment • For operational monitoring and diagnostics • Call reliability/media quality reports for troubleshooting • For Helpdesk responding to end-user complaints • User activity report • Reports can be subscribed for periodic email delivery • Reports are accessible from CS “14” Control Panel UI

  20. Access Monitoring Server Reports from CS Control Panel

  21. Monitoring Server Dashboard

  22. Blank Background optionfor use with content that extends over Purple line art Monitoring Server Report Homepage

  23. Reporting for CS “14” with Monitoring Server Arish Alreja Program ManagerMicrosoft DEMO

  24. Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Summary and Key Takeaways • Use CS “14” Management Pack for SCOM 2007 R2: • System health monitoring • Call reliability and media quality monitoring • Use CS “14” Monitoring Server dashboard and reports: • Managers: return-on-investment (ROI) analysis • IT pros: call reliability and media quality troubleshooting • Helpdesk: end-user troubleshooting

  25. Related Breakout Sessions You are here

  26. Questions?

  27. Unified Communications Track Call to Action! Learn More! • View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online • Visit microsoft.com/communicationsserver for more Communications Server “14” product information • Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter • Check out Microsoft TechNet resources for Communications Server and Exchange Server • Visit additional Exchange 2010 IT Professional-focused content • Partner LinkorCustomer Link (Name: ExProPword: EHLO!world) Try It Out! • Exchange 2010 SP1 Beta downloadis now available from the download center!

  28. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

  29. Required Slide Complete an evaluation on CommNet and enter to win!

  30. 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

  31. © 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.

  32. Blank Background optionfor use with content that extends over Purple line art Appendix

  33. Blank Background optionfor use with content that extends over Purple line art Synthetic Transaction to Verify IM Conferencing

  34. Blank Background optionfor use with content that extends over Purple line art Synthetic Transaction to Verify PSTN Outbound Call

  35. Blank Background optionfor use with content that extends over Purple line art Alert Views in SCOM

  36. Blank Background optionfor use with content that extends over Purple line art ST Alerting in SCOM

  37. Blank Background optionfor use with content that extends over Purple line art Component Alerting in SCOM

  38. Blank Background optionfor use with content that extends over Purple line art Call Reliability Alerting in SCOM

  39. Blank Background optionfor use with content that extends over Purple line art Monitoring Server Dashboard

  40. Blank Background optionfor use with content that extends over Purple line art Monitoring Server Report Homepage

  41. Conference Summary Report

  42. Conference Usage Trend

  43. Peer-to-Peer Activity Reliability Report

  44. Failure Distribution Report

  45. Peer-to-Peer Activity Reliability Report – Call List

  46. Location-based Media Quality Report

  47. Location-based Media Quality Report - Drilldown

  48. Location-based Media Quality Report – Trend

  49. Call List - Poor Quality Calls are Highlighted

  50. User Activity Report – Full List of User Activities

More Related