References > Template Reference > Microsoft Lync > Microsoft Lync Server (Edge Role)

Microsoft Lync Server (Edge Role)

This template assesses the status and overall health of services as well as the performance of the Edge Microsoft Lync Server.

Prerequisites

WMI access to the target server.

Credentials

Windows Administrator on the target server.

Monitored Components

For details on monitors, see SAM Component Monitor Types.

You need to set thresholds for these counters according to your environment. It is recommended to monitor these counters for some period of time to understand potential value ranges and then set the thresholds accordingly.

Service: Lync Server Replica Replicator Agent

This component monitor returns the CPU and memory usage of the Lync Server Replica Replicator Agent. This service is used by the File Transfer Agent for replication configuration settings.

SIP Peers: Connections Active

This component monitor returns the number of established connections that are currently active. A connection is considered established when peer credentials are verified (e.g. via MTLS), or the peer receives a 2xx response. You will need to baseline this counter by testing and monitoring the user load. This returned value should be less than 15,000 connections per Front-End.

SIP Peers: TLS Connections Active

This component monitor returns the number of established TLS connections that are currently active. A TLS connection is considered established when the peer certificate, and possibly the host name, are verified for a trust relationship. You will need to baseline this counter by testing and monitoring the user load.

SIP Peers: Average Outgoing Queue Delay

This component monitor returns the average time, in seconds, that messages have been delayed in outgoing queues. Check the Outgoing Queue Delay for delays in sending messages to other servers or clients that could be causing messages to be accumulated in the server. The server will drop client connections if it is in a throttle state and messages stay in the outgoing queue for more than 32 seconds.

SIP Peers: Incoming Requests/sec

This component monitor returns the rate of received requests, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Protocol: Incoming Messages/sec

This component monitor returns the rate of received messages, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Load Management: Average Holding Time For Incoming Messages

This component monitor returns the average time that the server held the incoming messages currently being processed. This should usually be less than one second, on average, but it is normal to see short spikes of up to three seconds. The server will throttle new incoming messages after going above the high benchmark and until the number of messages falls below the low benchmark. The server starts rejecting new connections when the average holding time is greater than overload time of 15 seconds.

SIP Access Edge Server: External Messages/sec With Internally Supported Domain

This component monitor returns the per-second rate of messages received at the external edge with an internally supported domain.

SIP Access Edge Server: External Messages/sec Received With Allowed Partner Server Domain

This component monitor returns the per-second rate of messages received at the external edge with an allowed partner server domain.

SIP Access Edge Server: External Messages/sec Received With a Configured Allowed Domain

This component monitor returns the per-second rate of messages received at the external edge with a configured allowed domain.

A/V Edge UDP: Active Relay Sessions – Authenticated

This component monitor returns the number of active relay sessions over UDP.

A/V Edge UDP: Active Relay Sessions – Allocated Port

This component monitor returns the number of active relay sessions with a UDP port allocation.

A/V Edge UDP: Active Relay Sessions – Data

This component monitor returns the number of active relay data sessions over UDP.

A/V Edge UDP: Allocated Port Pool Count

This component monitor returns the number of UDP ports available in the Allocated Port Pool. This monitor should be more than zero. If it reaches zero there is a resource issue.

A/V Edge UDP: Allocate Requests/sec

This component monitor returns the per-second rate of Allocate Requests over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Authentication Failures/sec

This component monitor returns the per-second rate of failed attempts to authenticate with the relay over UDP. The returned value should be as low as possible.

A/V Edge UDP: Allocate Requests Exceeding Port Limit

This component monitor returns the number of allocate requests over UDP that exceeded the port limit. If the value is greater than zero, this could indicate an attempt to misuse the port.

A/V Edge UDP: Packets Received/sec

This component monitor returns the number of packets, received per second, by the relay over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Packets Sent/sec

This component monitor returns the number of packets sent per second by the relay over UDP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge UDP: Average Data Packet Latency (milliseconds)

This component monitor returns the average latency for a valid data request over UDP in milliseconds. The returned value should be as low as possible.

A/V Edge UDP: Packets Dropped/sec

This component monitor returns the per-second rate of packets over UDP dropped by the relay. The returned value should be as low as possible.

This error occurs when an unexpectedly high rate of User Datagram Protocol (UDP) packets is received at the Media Relay (A/V Edge server)  causing some packets to be discarded. This could be the result of system overload or an indication of an attempt to misuse the MR.

To resolve this, check that the profile of network traffic to the MR is in line with expected usage. If the traffic exceeds 250 Mbps per interface, increase the Receive and Transmit buffer size on the associated network adapter network adapters to three times the default values.

If the cause is a general system overload, increase the capacity of the deployed MR function. A network level trace can be used to determine if there is an unusual amount of traffic originating from a single source. If the situation persists, enable tracing to check the network source of sessions exceeding the bandwidth limits to allow further troubleshooting of the cause.

A/V Edge TCP: Active Relay Sessions – Authenticated

This component monitor returns the number of active relay sessions over TCP.

A/V Edge TCP: Active Relay Sessions – Allocated Port

This component monitor returns the number of active relay sessions with a TCP port allocation.

A/V Edge TCP: Active Relay Sessions – Data

This component monitor returns the number of active relay data sessions over TCP.

A/V Edge TCP: Allocated Port Pool Count

This component monitor returns the number of TCP ports available in the Allocated Port Pool. This monitor should be greater than zero. If zero is reached, a resource issue exists.

A/V Edge TCP: Allocate Requests/sec

This component monitor returns the per-second rate of Allocate Requests over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Authentication Failures/sec

This component monitor returns the per-second rate of failed attempts to authenticate with the relay over TCP. The returned value should be as low as possible.

A/V Edge TCP: Allocate Requests Exceeding Port Limit

This component monitor returns the number of allocate requests over TCP that exceeded the port limit. If the value is greater than zero, this could indicate an attempt to misuse the port.

A/V Edge TCP: Packets Received/sec

This component monitor returns the number of packets received per second by the relay over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Packets Sent/sec

This component monitor returns the number of packets sent per second by the relay over TCP. You will need to baseline this counter by testing and monitoring the user load.

A/V Edge TCP: Average Data Packet Latency (milliseconds)

This component monitor returns the average latency for a valid data request over TCP in milliseconds. The returned value should be as low as possible.

A/V Edge TCP: Packets Dropped/sec

This component monitor returns the per-second rate of packets over TCP dropped by the relay. The returned value should be as low as possible.

This error occurs when an unexpectedly high rate of User Datagram Protocol (UDP) packets is received at the Media Relay (A/V Edge server)  causing some packets to be discarded. This could be the result of system overload or an indication of an attempt to misuse the MR.

To resolve this, check that the profile of network traffic to the MR is in line with expected usage. If the traffic exceeds 250 Mbps per interface, increase the Receive and Transmit buffer size on the associated network adapter network adapters to three times the default values.

If the cause is a general system overload, increase capacity of the deployed MR function. A network level trace can be used to determine if there is an unusual amount of traffic originating from a single source. If the situation persists, enable tracing to check the network source of sessions