Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Adding performance counters

You can include additional performance counters that you want to monitor for the specific server health test that you want to run.

You can add more than one instance of the same performance counter if you want to monitor for different conditions. For example, two instances of the counter "MSExchangeTransport Queues\Retry Mailbox Delivery Queue Length (_Total)" are pre-defined.

•
The first instance is set to detect a large value of the counter (a value greater than 100 generates a warning, and a notification is sent the second consecutive time it happens).
•
The second instance is set to detect several consecutive small values of the counter (a value of 1 generates a warning, 2 or more generates an alarm, but notifications are sent only when this happens 4 times in a row).
To add performance counters
1
Click <Add Performance Counters> located under the Performance Counters section in the listview of the server health test that you select.
2
Enter the name of the server you want to monitor, the performance object and counter you want to add, and select the instances, if applicable, you want to monitor in the Performance Counters dialog box and click OK.
3
Configure the thresholds you want to monitor for the new performance counter you have added.
 
* 
TIP: The Network Interface(*)\Bytes Total/sec counter indicates the rate at which the network adapter is processing data bytes.
•
If you are using a 100-MBps network adapter, set the counter to less than 6000000 - 7000000 bytes.
•
If you are using a 1000-MBps network adapter set the counter to less than 60000000 - 70000000 bytes.

Exchange health tests with preconfigured counters use the threshold value for 1000-MBps network adapter, which is 73400320 bytes. If you are using a 100-Mbps network adapter, you may modify the counter to 7340032 bytes.

For more information on counters, see Counters with Non-Zero Alarm Values .

Adding event log entries

You can include additional Event Log Entries that you want to monitor for the specific server health test that you want to run.

To add event log entries
1
Click Add Event Log Entries located under the Event Log section in the listview for the server health test you selected.
2
Enter the event log name for the log file in the Event Log field.
3
Enter the event provider name in the Source field.
* 
IMPORTANT: If you view the Windows event log properties in the Event Viewer, the event source is not the Source that appears in the General tab. The source that you specify when adding event log entries is the Provider Name that appears under the Details tab.

You can also enter a wild card character ( * ) at the end of the source string. For example, BlackBerry* would match the BlackBerry Policy Service, BlackBerry Router, etc.

4
Enter the event IDs you want to add in the Event IDs. For more information, see Options for specifying event IDs .
5
Click OK.
6
Configure the metrics you want to monitor for the new event log entry you have added.
Options for specifying event IDs

You can monitor specific event logs by filtering by event IDs or by text in the event ID descriptions. You can specify the following:

•
a specific event ID, such as 1000
•
multiple event IDs separated by commas
•
ranges, such as 1000-2000 (no spaces)
•
“ * “ to monitor all event IDs
•
an event ID or range of event IDs with text separated by a colon, as in the following examples:
•
1000:Error to monitor events with event ID 1000 and containing the word ’Error’
•
1000–2000:Error to monitor events within the range of event IDs 1000 to 2000 and containing the word ’Error’
•
1004:!Error to monitor events with the event ID 1004 and not containing the word ’Error’
•
1004–1005:!Succeeded to monitor events within the range of event IDs 1004 to 1005 and not containing the word ’Succeeded’
•
1000–2000:Error,1010:!Warning to monitor all events between event ID 1000 and 2000 that contains the word ’Error’, except those with event ID 1010 that contains the word ’Warning’
•
1000:Long Phrase to monitor events with the event ID 1000 that contains the specified long phrase. It cannot contain a comma.
•
1000:Error, 1000:Warning to monitor all events with the event ID 1000 and contains the word ’Error’ or ’Warning’

The following rules apply:

•
If you have both an inclusive filter and an exclusive filter for the same ID, the exclusion filter takes precedence.
•
If you want to look for multiple words that are not a phrase, you must add them separately.
Event log entries for Exchange crimson channels

The Exchange Applications and Services event logs store the events from a single application or component instead of events that have system-wide impact. This category of event logs is known as an application's crimson channel.

When creating a server health test for Exchange 2013 and Exchange 2016 mailbox servers, you will see the Microsoft-Exchange-HighAvailability/Monitoring log entry is set by default in the event log list.

For other crimson channel log entries or for earlier versions of Exchange, Lync or Skype for Business, or Blackberry, you can manually add an log entry for an Applications and Services event log.

To manually add an log event entry for an Applications and Services event log
1
In the Microsoft Windows Event Viewer, navigate to the event log that you want,
2
Right-click on the event log.
3
Click Properties and copy the name that appears in the Full Name field.
4
In the UC Diagnostics Management Console, when creating the server health test, click Add Event Log Entries located under the Event Log section.
5
Enter the full log name that you copied from the log properties page to the Log Name field.
6
Specify * as the Source.
7
Enter the event IDs you want to add in the Event IDs.
8
Click OK.
9
Configure the metrics you want to monitor for the new event log entry you have added.

Deleting services, performance counters, and event log entries

To delete services, performance counters, and event log entries
•
Right-click the description of a service, performance counter, or event log entry, and select Delete.

You can select multiple services, performance counters, or event log entries to delete them at the same time.

Editing counters while creating a health test

For many counters, you can change the following fields in the New Health Test wizard:

•
description
•
role
•
condition
•
warning and error thresholds (numerical counters only). In addition to specifying default thresholds (for all servers), you can create server-specific thresholds, which override default values.
•
alarms to skip before sending notification

Some of these fields do not exist for some counters. In some counters, certain fields cannot be changed. If you cannot perform the following procedures, this is an indication that the field in the current counter cannot be changed.

To edit a description
1
Right-click somewhere on the counter, and click Edit Counter Name.
2
Change the description in place.
If you enter invalid characters, the description does not change.
To edit a role
1
Click the current Role value.
2
In the dialog that appears, click one or more check boxes to select or deselect the roles for this counter. To select all roles, select All.
3
Click Close to remove the dialog.
To edit a condition
1
Click the current Condition value.
2
In the drop-down list, select the new value for the condition.
Changing the condition may cause current threshold values to become invalid. You must correct the thresholds or restore the condition value before leaving the wizard. Values that must be corrected are red.
To edit default warning or error thresholds for all servers
1
Click on the current value and enter a new value in place.
You cannot edit a warning threshold or error threshold if the value in the Condition column is set to Informational or Disabled. If you leave a threshold field with an invalid value, the previous value is restored.
To add or edit warning or error thresholds for individual servers
1
Right-click somewhere on the counter and click Edit Server Thresholds.
2
If the target server is listed, select it and click Edit, or double-click the target server.
If the target server is not listed, click Add. In the Server Thresholds dialog, click Browse. In the Select Servers dialog, check the boxes for one or more servers, or group. Click OK.
You can add several servers and apply server-specific thresholds to them together. But once listed, you can only select one server to edit. To modify multiple servers that are listed, click Add, reselect them, and specify new thresholds.
3
In the Server Thresholds dialog, enter values for the Error threshold and/or Warning threshold.
Warning thresholds may need to be higher or lower than Error thresholds, depending on the current condition. Violations are indicated by a red warning bullet. You cannot leave this dialog with invalid threshold values.
4
Click OK to accept changes and exit the Server Thresholds dialog.
5
Click OK to return to the Health Test wizard.
Notice that servers with server-specific thresholds are listed in the Overrides column for the counter. Position the cursor over this field to see an expanded list of servers (up to 5) that have server-specific thresholds. Right-click and select Edit Server Thresholds to view all servers with server-specific thresholds.
To edit the alarms to skip before sending notification
1
Click on the current value and enter a new value in place.
By skipping the specified number of alarms before a notification is sent you can avoid notifications on occasional spikes in the counter values. See Creating a health testCreating a health test for more information.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation