지금 지원 담당자와 채팅
지원 담당자와 채팅

Unified Communications Diagnostics 8.6.3 - 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 Registering UC Diagnostics with the Microsoft Azure portal
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

OS/Subsystem Panel

The OS/Subsystem panel displays information about the amount of CPU being used by all processes. It also indicates the amount of System Memory and System Disk being used, and reports on any errors. This panel includes:

 
Table 5. OCS OS subsystem panel.
Component
Description

CPU Usage

Indicates the amount of CPU used by all processes.

Top CPU Consumer

Indicates the top CPU consumer.

Top Memory Consumer

Indicates the top consumer of memory.

System Memory

Indicates the amount of system memory used by all processes.

Processor Queue

Indicates the number of threads waiting to execute.

System Disk

Indicates the amount of system disk space being used.

Event Log Errors

Indicates the number of OCS-related errors in the Event Log.

Last AB Update

Indicates the date stamp of the most recent file in the Address Book share location.

OCS Message Flows

The OCS Diagnostic Console contains the following message flows that show the amount of information being sent to various components in your OCS environment.

 
Table 6. OCS message flows panel.
Message Flow
Description

Unavailable/Sec

Indicates the amount of errors per second

SIP In/Sec

Indicates the amount of incoming SIP messages/second

SIP Out/Sec

Indicates the amount of outgoing SIP messages/second

Authentications/Sec

Indicates the number of authentications created per second

Authentication Errors/Sec

Indicates the number of authentication errors per second

Com Failures/Sec

Indicates the number of communication failures per second

Req Drop/Sec

Indicates the number of requests dropped per second

Resp Drop/Sec

Indicates the number of responses dropped per second

C3P Rec/Sec

Indicates the number of C3P messages received per second

C3P Sent/Sec

Indicates the number of C3P messages sent per second

Archiving/Sec

Indicates the number of messages sent to the MSMQ per second

User Replication Updates/Sec

Indicates the number of user replicator updates occurring per second

OCS 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 on 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 7. OCS drilldowns.
Drilldown
Associated Charts/Tabs

Clients/Network
•
Network — indicates the number of packets waiting to be sent through the network.
•
TCP/IP — indicates the TCP segments, UDP datagrams, IP Fragments, and IP Datagrams that are transferred.
•
NBT — indicates the computers that have an active connection to the system being diagnosed.
•
Authentication — indicates how many Authentications/sec and Authentication Errors/sec are occurring.
•
AD Search Latency — indicates the average amount of time to perform an LDAP search against the first Global Catalog found in the domain.
•
Outstanding RPC Calls — indicates the number of RPC calls waiting to be sent between Front-End servers.
•
Connected Endpoints — allows you to enter a search filter to limit the number of endpoints returned.

Server Load
•
Flow Controlled — indicates the number of flow controlled connections per connections source, average holding time of connections, how many connections have been dropped, and average delay of connections.
•
SIP — indicates the number of incoming and outgoing SIP messages, messages outstanding, dropped, or held, and memory usage of the SIP Proxy.
•
C3P — indicates the average time to allocate a new conference and the number of C3P transactions being processed.
•
Database — indicates the average amount of time a database request or database stored procedure waits before it is sent to the database.

Server Roles
•
Roles — indicates the amount of CPU usage per Front-End server, and number of allocated conferences by type.
•
IM Conferences — indicates the number of connected users, the number of incoming and outgoing messages, and overall health per IM conference.
•
Telephony (PSTN) Conferences — handles the C3P messages that flow between Focus and the ACP.
•
Web Conferences — indicates the number of participants, number of slides, and number of errors in the Web Conference.
•
A/V Conferences — indicates the number of users, number of audio/video messages being sent and received, the average time it takes to process Audio packets, and the number of buffers sent to users.

OS Subsystem
•
CPU — indicates the CPU usage by all processes.
•
Memory — indicates the amount of memory used by all users.
•
Top CPU/Memory Consumers — indicates the top consumers of CPU and memory.
•
Logical Disk – indicates the number of read and write requests, disk queue, and transfer time.
•
User Replicator/Address Book — indicates the user replicator updates and the contents of the Address Book file share.
•
Archiving — indicates various characteristics of the Archiving server such as CPU and memory usage, database queue latencies, database queue depth, and MSMQ messages.

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.

Each time the UC Diagnostics window is refreshed, UC Diagnostics retrieves the latest value of the metric, which can 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 8. OCS 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

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.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택