Operational dependencies in Lync Server 2013

Lync Server 2013
 

Letztes Änderungsdatum des Themas: 2015-05-15

The Reference Architecture discussed in this document will help ensure that you have a Lync Server 2013 deployment that not only scales to the organization’s requirements but is architected as per Microsoft best practices. Be that as it may the Lync Server 2013 implementation is a dynamic service and like any other service in the enterprise still requires monitoring and proactive management to maintain high level of service availability and service quality to the business.

As Lync Server 2013 becomes deeply ingrained in the organization’s everyday business it is important that the service be managed by accurate and tangible service level management. The Lync system architecture can become complex and very integrated and in order to maintain effective service level management and establish SLAs for Lync Server 2013 it becomes critical to understand the system’s dependencies on other platforms and servers. Equally important is to note which business services, such as voice and UC integrated applications, become dependent on Lync.

Lync Server 2013 must be established noting all the said dependencies. The service map will allow you to formulate a SLA between Lync and its dependent service and provide a starting place for SLA negotiation.

The following table lists the typical dependency services for a Lync infrastructure. Each of these technologies should have its own proactive monitoring.

Typical dependency services

Dependency Service

Operating systems

Server Hardware

Active Directory

Public Key Infrastructure

Domain Naming Service

Database Services

Storage Services

System Management – Monitoring and distribution

Security Services - Antivirus

Network Infrastructure - Internet

Network Infrastructure – Internal (LAN/WAN)

Telephony Infrastructure – IP-PBX and Gateways

Cloud Services

It is assumed that the organization is operationally mature in exercising basic service level management functions such as change, incident and release management as prescribed by the MOF. The Lync solution should be adopted by these functions and become subject to the same operational management processes.

Building on the information obtained above we now have a greater understanding of what can impact the Lync service in the enterprise. To help ensure Lync Server 2013 service availability and quality, the following monitoring tools must accompany the reference architecture deployment:

Monitoring tools

Component Description Applicable Site

Lync Server 2013 Monitoring Server

Deploy at least one Lync Server 2013 Monitoring Server role per Central site and configure Quality of Experience (QoE) Reporting Pack.

Refer to the Lync Server 2013 Deployment documentation for further details:

Bereitstellen des Monitoring Servers

Central sites

Tether each pool to its nearest instance of the Monitoring Server role.

Central sites

Branch sites

System Center Operations Manager 2012

System Center Operations Manager 2012 with the Microsoft Lync Server 2013 Management Pack (MP) imported.

The Management Pack implements traditional Event Log and Performance counter based instrumentation is utilized as well as enabling newly available instrumentation in Lync Server 2013.

Central sites

Make sure that Central Discovery to discovery of roles and components that need to be monitored are automatically completed based on a central discovery script that reads the topology document published in Central Management Database.

Central Site

Branch Site

Edge Site

Deploy System Centre Operations Manager 2007 agents to all deployed servers running Lync Server.

Central Site

Branch Site

Edge Site

Make sure Prioritized Alerts are configured for notification:

High Priority Alerts

Medium Priority Alerts

Other Alerts.

Central Site

Branch Site

Edge Site

Configure Port monitoring for your deployment.

Central Site

Branch Site

Edge Site

Configure URL monitoring for your deployment

Central Site

Lync and System Center Operations Manager integration

Deploy Call Reliability and Media Quality MonitoringCall reliability and media quality monitoring use the Monitoring-Server computer as their watcher node to monitor call reliability and media quality of Lync Server. Both of these features query the Monitoring-Server databases to do analysis.

Central Site

Branch Site

Ensure Media Quality warning thresholds are accurately configured. The following table indicates the maximum Network Mean Opinion Scores by Codec. In production these scores should be monitored for a set period and acceptable thresholds must be established based on the organization specific NMOS scores.

Central Site

Branch Site

Lync Server 2013 Synthetic Transaction Watcher

Deploy a dedicated Lync Server to be a synthetic transaction watcher.

Synthetic transactions are Lync Server 2013 Windows PowerShell cmdlets that are automatically triggered by the management pack on a predefined interval. These are executed on a synthetic transaction watcher node which is an administrator designated server responsible for discovery and execution of STs for each pool.

We do not recommend that you use an existing Microsoft Lync Server 2013 server as a synthetic transaction watcher node. This is due to the high CPU/memory usage requirements for running STs. Use a new server computer (or a virtual server) for the synthetic transaction watcher node.

Central Site

Deploying synthetic transactions watcher node.

Refer to the MonitoringCS_withSCOM.docx document from UCTAP connect documentation.

Central Site

Maximum Network MOS scores per codec

Scenario Codec Max NMOS

UC-UC call

RTAudio WB

4.10

UC-UC call

RTAudio NB

2.95

Conference call

Siren

3.72

UC-PSTN call

RTAudio NB

2.95

UC-PSTN call

G-711

3.61

Over and above the previous pro-active monitoring activities, maintenance tasks should be executed for Central, Edge and Branch sites on a recurring daily, weekly and monthly basis as defined in the Lync RA Operations Guide.

 
Anzeigen: