1. 3 | Analyzing Server, Network, and Client Health

2. Indicators for Server Health
20335B
Indicators for Server Health
04: Analyzing Server, Network, and Client Health
Common server key health indicators (KHIs):
System
Back-End servers
Multipoint Conferencing Unit (MCU)
Edge
Conferencing
Mediation server
Web components
Front-End servers
Mobile
 Key Health Indicators (KHI) are Performance Counters with recommended thresholds aimed at revealing problems that can impact the user experience

3. Indicators for Network Health
20335B
Indicators for Network Health
04: Analyzing Server, Network, and Client Health
Network device KHIs:
CPU usage
Packet drops
Queue length
Errors
Skype for Business Server call network metrics:
Packet Loss: A percentage of packets that are lost in a given window
Jitter: The average change in delay between successive packets in a VoIP call
Latency: Stack latency and network propagation delay
Use the following lists below to add value to the list on the slide.
Packet loss and Jitter:
On managed networks, there should be almost 0 loss and very little jitter.
The media stack has state of the art technology to recover from loss and jitter, so values outside optimal range may not be noticeable. But, if you address these issues anyway, you will still improve quality (with lower bandwidth).
On unmanaged networks, there is nothing the user can do other than to avoid making calls with a bad connection. Use user education and policy to prevent bad calls.
Latency:
There are two types: one-way and round trip (RTT); the latter is easier to measure and therefore used in the most places.
Typically, discussion revolves around what latency levels are acceptable.
Instead let us focus on sources of latency.
Stack latency (capture/framing/codec) – there is not much the admin can control here.
Jitter buffering latency – amount proportional to amount of packet loss and jitter; good network end- to-end equals low latency.
Network propagation latency (sum of latency across each hop) – huge latencies are often caused by one bad network leg:
This is a sign that a real problem exists.
Have the expectation of latency, such as speed of light x distance + minimal overhead.

4. Indicators of Client Health
20335B
Indicators of Client Health
04: Analyzing Server, Network, and Client Health
Use client data, such as device performance reports or Wi-Fi call quality reports, to improve call quality
These include:
IP-PSTN Gateway
Wi-Fi subnet quality reports

5. Sample Output for Wi-Fi Subnet Quality Reports
04: Analyzing Server, Network, and Client Health
ReportDate
Subnet
AllStreams
BadStreams
BadStreams Ratio
1/1/2015
1,456 6
0.00
322 13
0.04
1/2/2015
1,390
250 10
Review the sample outputs in the table.

6. Audio/Video Bandwidth Usage
04: Analyzing Server, Network, and Client Health
Required bandwidth is determined by:
Codec choice
Network performance:
Poor network performance results in redundant encoding of audio content (Forward Error Correction)
Voice activity and video content
Media endpoints actively manage distribution of bandwidth across UC modalities by:
Prioritizing Audio first and distributing remaining bandwidth to App Sharing, Video, and File Transfer as required
Choosing the best-quality audio codec and video resolution for available bandwidth  Unique to Skype
May dynamically change codec choices during a session  Unique to Skype

7. Managing Configuration Audits
20335B
Managing Configuration Audits
04: Analyzing Server, Network, and Client Health
Types of drift to manage can include:
IP-PSTN gateway configuration drift
Skype for Business Server configuration drift
Network configuration drift

8. Usage Trend Monitoring Reports
20335B
Usage Trend Monitoring Reports
04: Analyzing Server, Network, and Client Health
These can include:
Overall usage
Scenarios-based usage
Conferencing
Peer-to-peer (P2P)
PSTN
Video
Others (for example, Microsoft Exchange Unified Messaging)
Location-based usage
Bandwidth usage
Wired versus Wireless
Internal versus External
VPN
Federation

9. Skype for Business Server Features that Provide Monitoring Data
04: Analyzing Server, Network, and Client Health
These include:
System Center Operations Manager (SCOM) alerts
Event logs
Synthetic transactions
Performance counters
Call detail recording (CDR)
Call Quality Dashboard (CQD)

10. Using the Message Analyzer
20335B
Using the Message Analyzer
04: Analyzing Server, Network, and Client Health
Monitoring performance statistics using the Message Analyzer allows you to:
Capture and conduct protocol analysis of network traffic
Capture text files, event logs, and system event traces

11. Third-Party Monitoring Solutions
20335B
Third-Party Monitoring Solutions
04: Analyzing Server, Network, and Client Health
These can include:
AppNeta
SMART
NetIQ
Ixia
Give a brief overview of each third-party option and how they are used for monitoring.

12. Common Audio Problems 20337B 10: Monitoring
This is just a discussion slide. Use the slide content to discuss factors that contribute to users’ perception.