Lync Server 2013: Best Practice: Active Monitoring with Operations Manager
•Als PPT, PDF herunterladen•
3 gefällt mir•6,634 views
•Monitoring Scenarios •Demo of how it looks in OpsMgr •Watcher Nodes •20 minutes demo of how Watcher Nodes work •How to deploy for success
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
Lync Server 2013: Best Practice: Active Monitoring with Operations Manager
- 1. Ståle Hansen Lync Server 2013 Best Practice: Active Monitoring with Operations Manager
- 2. Objective Understand how you can actively monitor Lync Server 2013 • Monitoring Scenarios • Let’s take a look • Watcher Nodes • How to deploy for success
- 3. Ståle Hansen Technical Evangelist @ Atea V-TSP @ Microsoft Blog @ msunified.net Company blog @ LyncAtea.no Co-Author Lync Master Class @ LyncLab.no Contributor @ TheUCArchitects PodCast
- 6. Component health alerts • Event Logs • Performance Counters
- 7. Dependency health monitoring • External dependencies • Internet Information Services (IIS) availability • CPU and memory usage of Lync Servers and processes • Disk metrics
- 8. Call reliability alerts (CDR) • Directly from the Monitoring database • Tells you • Why a call terminated • Why a user failed to connect a call • Gives you the Diagnostics Header
- 9. Media quality alerts (QoE) • Directly from the monitoring database • Quality of Experience • Based on key metrics • Jitter • Packet Loss • Latency
- 10. Synthetic Transactions • Test actual functionality with real users • Using test cmdlets • Run from Watcher Nodes
- 11. Let’s take a look Demo
- 12. Watcher Nodes are computers that periodically run Lync Server synthetic transactions
- 13. More control in Lync 2013 • Run from various geographic locations • We got a cmdlet to choose scenarios • New-CsWatcherNodeConfiguration • Three types of scenarios • Default • Non-Default • Extended
- 14. Default Scenarios • Test-CsAddressBookService (ABS) • Test-CsAddressBookWebQuery (ABWQ) • Test-CsAVConference (AvConference) • Test-CsGroupIM (IM Conferencing) • Test-CsIM (P2P IM) • Test-CsP2PAV (P2PAV) • Test-CsPresence (Presence) • Test-CsRegistration
- 15. Non-default scenarios • Test-CsPstnPeerToPeerCall (PSTN) • Test-CsAVEdgeConnectivity • Test-CsDataConference (DataConference) • Test-CsExumConnectivity (ExumConnectivity) • Test-CsGroupIM –TestJoinLauncher (JoinLauncher) • Test-CsMCXP2PIM (MCXP2PIM) • Test-CsPersistentChatMessage (PersistentChatMessage) • Test-CsUnifiedContactStore (UnifiedContactStore) • Test-CsXmppIM (XmppIM)
- 16. Extended Scenarios • Test-CsPstnPeerToPeerCall (PSTN) • Can be run multiple times during each pass • Multiple voice routes
- 17. Test User Accounts • Do not need to represent actual people • Must be valid Active Directory accounts • Must be enabled for Lync Server 2013 • Have valid SIP addresses • Should be enabled for Enterprise Voice
- 18. Configuring Synthetic Transactions for Watcher Nodes Demo
- 19. How to deploy for success? • Do one thing at a time • Implement Management Pack (MP) for Lync • Tune it till it’s green • Create a MP for overrides and customization • Tune your synthetic transactions
- 20. Key Takeaways • Monitoring Scenarios – Lync health at a glance • Watcher Nodes – Runs actual tests periodically • How to deploy for success? - Do one thing at a time
- 21. Questions?
Hinweis der Redaktion
- Did anyone attend last years lync troubleshooting session here on NIC Then you may remember that there where a lot of tools and things to check for
- as services not running, certificates expiring high failure rates, high message latency, or connectivity issues
- Lync Server can fail for a variety of external reasons. The Management Pack now monitors and collects data for critical external dependencies that can indicate severe issues
- These queries produce alerts that indicate when a high number of users experience connectivity issues for peer-to-peer calls or basic conferencing functionality What is the diagnostics header you may say Shows a diagnostic header, it tells you why the call failed No response No media connectivity Possible source of fault, returncode
- pinpoint scenarios where users are most likely to experience compromised media quality
- run from various geographic locations, to test and help ensure high availability of scenarios such as sign in, presence, IM, and conferencing for users.
- synthetic transactions can use a large amount of computer memory and processor time. Because of this, we recommend that you use a dedicated computer as a watcher node. For example, you should not configure a Lync Server Front End Server to act as a watcher node Can not be collocated with a 2010 watcher node because of the 2013 binaries