Chat now with support
Chat with Support

Unified Communications Diagnostics 8.5 - User Guide

About Unified Communications Diagnostics Getting Started Using the Management Console Introducing Management Console health tests Health tests available from the Exchange organization node
About the Exchange-based health tests Exchange Server Health Test Prerequisites for Exchange Delivery Health Tests Exchange Internal Server Delivery Health Test Exchange Internal Mailbox Delivery Health Test Exchange External Message Delivery Health Test Exchange Modern Message Delivery Health Test Exchange Storage Health Test Exchange Queue Health Test Internal Outlook Web Access (OWA) Availability Health Test External Outlook Web Access (OWA) Availability Health Test Exchange Replication Health Test Exchange System Health Test Active Directory Account Lockout Health Test Exchange Online Connectivity Health Test Exchange Online Mailbox Logon Health Test Exchange Online Message Delivery Health Test Office 365 Subscription Health Test BlackBerry Server Health Test BlackBerry Message Delivery Health Test Creating test mailboxes for Exchange Adding health sets for Exchange System health tests Configuring Exchange impersonation for the Modern Message Delivery health test
Health tests available from the Lync/Skype for Business Environment Resolving Problems with Native Tools Launching the Diagnostic Console from the Management Console Launching UC Analytics from the Management Console Diagnosing Problems using the Diagnostic Console UC Diagnostics: Exchange 2007 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2010 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2013 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2016 Diagnostic Console (Plug In) UC Diagnostics: BlackBerry Diagnostic Console (Plug In) UC Diagnostics: OCS Diagnostic Console (Plug In) UC Diagnostics: Lync 2013 or Skype for Business 2015 Diagnostic Console (Plug In) Reporting Using Web Reports Counters with Non-Zero Alarm Values

BlackBerry Drilldowns

Each drilldown page contains displays that provide you with specific information about the components of your system. Drilldowns mainly use two different types of displays – tables and charts. Drilldowns have the following features:

•
They can be configured to show all or some of the metrics associated with components.
•
You can access further information about displays in drilldowns by moving the mouse over the displays, or by clicking or right-clicking them.
•
You can copy the data shown in drilldowns to other applications or save it to a file.
•
You can view a brief description of a drilldown by hovering your mouse over a component, such as a button, dataflow, status ball, or Toolbar button.
To view a drilldown

Right-click a component in a panel and select Show Details.

 
Table 8. BlackBerry drilldowns.
Drilldown
Associated Charts/Tabs

Service Health
•
BlackBerry Attachment Service
•
BlackBerry Dispatcher Service
•
BlackBerry Messaging Agents Service
•
BlackBerry Policy Service
•
BlackBerry Router Service
•
BlackBerry Synchronization Service

For a description of these charts, For more information, see BlackBerry Service Health Panel.

SRP
•
SRP Status – indicates whether or not the BlackBerry Server is connected to RIM's Server Relay Protocol (SRP) server using port 3101

For a description on the other charts, For more information, see BlackBerry SRP Panel.

Server
•
Message and Users – Shows messages and user information. Message charts includes: Pending, Expired, Error, MORE, Global Filtered, and User Filtered. User charts include: OTAC, WER, and Failed Initializations.
•
Licenses and Connections – Shows license and connection information. License charts include information on licenses currently in use. Connection charts include: Message Agents, Service Connections, and Device Connections.

For a description on these charts, For more information, see BlackBerry Server Panel.

Users
•
User Configuration – shows configuration data for the users hosted by this BlackBerry Server
•
User Devices – shows users' handheld device information on this BlackBerry Server
•
User Statistics – shows statistical information related to the users on this BlackBerry Server

OS/Subsystem
•
CPU Usage
•
System Disk
•
Network Bytes per Sec
•
System Memory
•
Network Output Queue
•
Processor Queue Length

For a description of these charts, For more information, see BlackBerry OS/ Subsystem Panel.

Processes
•
Process Name
•
CPU Usage
•
Physical Memory
•
Virtual Memory

Metrics

A metric is an individual piece of information that UC Diagnostics has collected about the performance of a system, such as perfmon counters. The information may be a numeric value (a number or percentage), a string of text, or some other piece of data.

To view the perfmon counters
•
Right-click a component and select Metrics.

The perfmon counter is visible in the Metric help section in the General tab.

Every time that the UC Diagnostics window is refreshed, UC Diagnostics retrieves the latest value of the metric, which can then be displayed in a drilldown or on the home page.

The Metric editor allows you to view and edit the properties of UC Diagnostics metrics, including their thresholds and severities. You can open the Metric editor for a component or a drilldown by right-clicking on the component and choosing Metrics from the invoked shortcut menu.

When you open the Metric editor, the General tab is open by default. Several metrics contain data source descriptions for the metric. The data source descriptions use the following list of functions.

 
Table 9. Server metrics.
function
Description

max(x)

the maximum of a set of values in list x

max(x,y)

the maximum of x and y

min(x)

the minimum of a set of values in list x

count(x)

the number of values in list x

sum(x)

the sum of a set of values in list x

if(x,y,z)

if x is true, then return y, otherwise, return z

snull(x)

if x could not be collected, then return true

avg(x)

the average of values in list x

 

UC Diagnostics: OCS Diagnostic Console (Plug In)

UC Diagnostics: OCS Diagnostic Console (Plug In)
•
Introducing the OCS Diagnostic Console
•
Understanding the OCS Diagnostic Console
•
Panels
•
OCS Message Flows
•
OCS Drilldowns
•
Metrics

Introducing the OCS Diagnostic Console

Introducing the OCS Diagnostic Console

The Diagnostic Console provides you with a real-time representation of the messaging system processes and components within OCS (Office Communications Server). The Diagnostic Console can perform real-time monitoring on Front-End and Conferencing servers only.

The Diagnostic Console retrieves a large amount of data from a server frequently, which can place excessive stress on a server, affecting the server's performance. Also, using the Diagnostic Console for an extended period of time can consume critical system resources, affecting the stability of UC Diagnostics. It is recommended that the Diagnostic Console view a maximum of 10 servers at any one time.

The Diagnostic Console contains the following:

•
Home pages that highlight targeted areas of the OCS server activity.
•
Graphical flows that illustrate the rate at which data is moving between server components. Colorful buttons, gauges, queues, spinners, and containers display the value of key statistics and metrics.
•
Visual warnings if the performance metrics exceed acceptable thresholds, which you can adjust. The buttons, gauges, queues, and other visual objects, collectively referred to as components, change color to show you the source of the problem.
•
Warning messages that are displayed well before the traffic levels of a server become critical.
•
A range of reports and graphs that provide you with detailed information about a server. You can view this information on the screen or you can print it.

If you are using the Diagnostic Console as a monitoring tool, you must disconnect from, then reconnect to the Diagnostic Console daily. Though the Management Console can run tests when it is closed, the Diagnostic Console cannot perform any actions when it is closed.

For information about software prerequisites and the permissions required to run the diagnostic console on OCS, see the Unified Communications Diagnostics Deployment Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating