Lync Server 2013 中的热门故障报告Top Failures Report in Lync Server 2013

 

上次修改的主题: 2012-10-01Topic Last Modified: 2012-10-01

主要故障报告说明了最常报告的故障及其在一段时间内的趋势。故障基于以下两项指标的组合:The Top Failures Report provides a look at the most-commonly reported failures and their trends over time. Failures are based on a combination of the following two metrics:

  • 诊断 ID。附加到 SIP 消息的唯一标识符(采用 ms-diagnostics 标头的形式)。诊断 ID 提供的信息在解决与呼叫相关的问题时很有用。Diagnostic ID. Unique identifier (in the form of an ms-diagnostics header) that is attached to a SIP message. Diagnostic IDs provide information useful in troubleshooting call-related problems.

  • 响应代码Response code. 响应代码在 SIP 通信会话中用来响应 SIP 请求。Response codes are used in SIP communication sessions to respond to SIP requests. 例如,假定 Ken 将 INVITE 请求发送给 Pilar Ackerman(即,假定 Ken Myer 呼叫 Pilar Ackerman)。For example, suppose Ken sends the INVITE request to Pilar Ackerman (that is, suppose Ken Myer calls Pilar Ackerman). 如果 Pilar 应答,则她的电话将发送响应代码 200(确定),以便让 Ken 的电话获知 Pilar 已应答。If Pilar answers, her phone will send the response code 200 (OK), letting Ken's phone know that Pilar has answered. 顶级故障报告仅包括在响应呼叫失败时发送的响应代码。Lync Server 不会跟踪在呼叫过程中发出的所有响应代码。The Top Failures Report only includes response codes that were sent in response to a call failure; Lync Server does not keep track of all the response codes issued during the course of a call.

不仅将报告与出现故障的会话的总数相关的信息,而且还将报告与受故障影响的用户总数相关的信息。Information is reported not only for the total number of sessions where a failure occurred but also for the total number of users who were impacted by the failure.

访问主要故障报告Accessing the Top Failures Report

可从监控报告主页访问主要故障报告。The Top Failures Report is accessed from the Monitoring Reports home page. 单击报告的会话指标将转到 Lync Server 2013 中的故障分布报告Clicking the Reported sessions metric will take you to the Failure Distribution Report in Lync Server 2013.

最充分地利用主要故障报告Making the Best Use of the Top Failures Report

主要故障报告有一个与众不同的方面:它允许您一次性对最多 5 个诊断 ID 进行筛选。(通常,您一次只能筛选一项 - 例如,一个用户 SIP 地址。)若要对多个诊断 ID 进行筛选,只需在诊断 ID 框中输入每个 ID,并使用逗号分隔这些 ID。(如果需要,您可以在每个逗号后面保留一个空格。)例如:The Top Failures Report is unusual in one regard: it allows you to filter on as many as 5 diagnostic IDs at once. (Typically you can only filter on one item – such as one user SIP address – at a time.) To filter on multiple diagnostic IDs, simply enter each ID in the Diagnostic IDs box, separating the IDs by using commas. (If you want to, you can leave a blank space after each comma.) For example:

1011, 2412, 1033, 52116, 10081011, 2412, 1033, 52116, 1008

这样一来,将仅显示报告了这五个诊断 ID 中的至少一个 ID 的失败呼叫。Do that, and only failed calls that reported at least one of those five diagnostic IDs will be displayed.

如果您将鼠标指针悬停在响应代码的上方,则将显示一个工具提示,告知您有问题的响应代码的含义。例如,如果您将鼠标指针悬停在响应代码 486 的上方,则将显示以下消息:If you hold your mouse over a Response code you'll see a tooltip that tells you what the Response code in question means. For example, if you hold the mouse over the Response code 486 you'll see this message:

此处忙碌。Busy Here.

筛选器Filters

利用筛选器,您可以返回一组针对性更强的数据或通过不同的方式查看返回的数据。例如,主要故障报告允许您基于活动类型(点对点会话还是会议会话)或失败会话附带的 SIP 响应代码等条件筛选返回的数据。您还可以选择数据的分组方式。在此示例中,将按小时、日、周或月对使用情况进行分组。Filters provide a way for you to return a more finely-targeted set of data or to view the returned data in different ways. For example, the Top Failures Report enables you to filter the returned data based on such things as the activity type (peer-to-peer session or conferencing session) or by the SIP response code that accompanied the failed session. You can also choose how data should be grouped. In this case, usages are grouped by hour, day, week, or month.

下表列出了可用于主要故障报告的筛选器。The following table lists the filters that you can use with the Top Failures Report.

主要故障报告筛选器Top Failures Report Filters

名称Name 说明Description

FromFrom

时间范围的开始日期/时间。若要按小时查看数据,请输入开始日期和时间,如下所示:Start date/time for the time range. To view data by hours, enter both the start date and time as follows:

7/7/2012 1:00 PM7/7/2012 1:00 PM

如果您未输入开始时间,该报告会自动将某个特定日的上午 12:00 作为开始时间。若要按日查看数据,请只输入日期:If you do not enter a start time, the report automatically begins at 12:00 AM on the specified day. To view data by day, enter just the date:

7/7/20127/7/2012

若要按周或按月查看,请输入您要查看的周或月中的任一日期(您不必输入周或月的第一天):To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month):

7/3/20127/3/2012

一周始终是从星期日开始至星期六结束。Weeks always run from Sunday through Saturday.

ToTo

时间范围的结束日期/时间。若要按小时查看数据,请输入结束日期和时间,如下所示:End date/time for the time range. To view data by hours, enter both the end date and time as follows:

7/7/2012 1:00 PM7/7/2012 1:00 PM

如果您未输入结束时间,该报告会自动将某个特定日的上午 12:00 作为结束时间。若要按日查看数据,请只输入日期:If you do not enter an end time, the report automatically ends at 12:00 AM on the specified day. To view data by day, enter just the date:

7/7/20127/7/2012

若要按周或按月查看,请输入您要查看的周或月中的任一日期(您不必输入周或月的第一天):To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month):

7/3/20127/3/2012

一周始终是从星期日开始至星期六结束。Weeks always run from Sunday through Saturday.

活动类型Activity type

活动的类型。选择下列选项之一:Type of activity. Select one of the following:

  • 各种[All]

  • 对等Peer-to-peer

  • ConferenceConference

模态Modality

在这里,只能选择“[所有]”选项。At this time the only option available is [All].

PoolPool

注册器池或边缘服务器的完全限定域名 (FQDN)。可以选择单个池,也可以单击“[所有]”查看所有池的数据。系统根据数据库中的记录自动为您填充该下拉列表。Fully qualified domain name (FQDN) of the Registrar pool or Edge Server. You can either select an individual pool or click [All] to view data for all the pools. This drop-down list is automatically populated for you based on the records in the database.

类别Category

遇到的故障的类型。选择下列选项之一:Type of failure experienced. Select one of the following:

  • 预期失败和意外失败Both expected and unexpected failure

  • 意外失败Unexpected failure

"预期故障 " 是预期发生的故障。An "expected failure" is a failure that is expected to happen. 例如,如果用户将其状态设置为“请勿打扰”,那么向该用户发出的任何呼叫应该都会失败。For example, if a user has set his or her status to Do Not Disturb you would expect any call to that user to fail. "意外故障 " 是指看起来好像是以其他正常运行的系统出现的故障。An "unexpected failure" is a failure that occurs in what would appear to be an otherwise healthy system. 例如,如果呼叫者处于呼叫等待状态,则不应该终止呼叫。For example, a call should not be terminated if the caller is placed on hold. 如果终止,则会被标记为意外失败。If that occurs, that would be flagged as an unexpected failure.

响应代码Response code

会议失败时发送的 SIP 响应代码。请输入完整的响应代码。例如:SIP response code sent when the conference failed. Enter the entire response code For example:

400400

诊断 IDDiagnostic ID

附加到 SIP 消息的唯一标识符(采用 ms-diagnostics 标头的形式),提供的信息在排查错误时通常很有帮助。诊断标头是可选的(SIP 会话可以不包含这些标头),并且只对遇到此类问题的会话报告诊断 ID。Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors. Diagnostics headers are optional (it is possible to have SIP sessions that do not include these headers), and diagnostic IDs are reported only for sessions that experienced problems of some kind.

指标Metrics

下表列出了主要故障报告中提供的信息。The following table lists the information provided in the Top Failures Report.

主要故障报告指标Top Failures Report Metrics

名称Name 是否可按此项排序?Can you sort on this item? 说明Description

RankRank

Yes

基于报告的会话数确定的相对等级。Relative rank based on the number of reported sessions.

报告的会话Reported sessions

Yes

基于诊断 ID 和 SIP 响应代码确定的失败会话总数。Total number of failed sessions based on diagnostic ID and SIP response code.

影响的用户Users impacted

Yes

失败会话影响的用户总数。Total number of users affected by the failed session.

故障信息Failure information

No

有关故障的详细信息,包括诊断 ID、SIP 响应代码和有关会话失败原因的说明。Detailed information about the failure, including diagnostic ID, SIP response code, and description of why the session failed.

过去的趋势Trend in the past

No

以图形的形式显示失败会话在一段时间内的趋势。Graphs failed sessions over time.