用于隔离网络损坏的Mediatrace

下载选项

PDF (234.0 KB)
在各种设备上使用 Adobe Reader 查看
ePub (102.7 KB)
在 iPhone、iPad、Android、Sony Reader 或 Windows Phone 上使用各种应用查看
Mobi (Kindle) (91.6 KB)
在 Kindle 设备上查看或在多个设备上使用 Kindle 应用查看

已更新: 2013 年 4 月 12 日

文档 ID:116033

非歧视性语言

此产品的文档集力求使用非歧视性语言。在本文档集中，非歧视性语言是指不隐含针对年龄、残障、性别、种族身份、族群身份、性取向、社会经济地位和交叉性的歧视的语言。由于产品软件的用户界面中使用的硬编码语言、基于 RFP 文档使用的语言或引用的第三方产品使用的语言，文档中可能无法确保完全使用非歧视性语言。深入了解思科如何使用包容性语言。

关于此翻译

思科采用人工翻译与机器翻译相结合的方式将此文档翻译成不同语言，希望全球的用户都能通过各自的语言得到支持性的内容。请注意：即使是最好的机器翻译，其准确度也不及专业翻译人员的水平。 Cisco Systems, Inc. 对于翻译的准确性不承担任何责任，并建议您总是参考英文原始文档（已提供链接）。

简介

本文档介绍如何使用Mediatrace功能快速隔离影响语音和视频质量的网络损害，如丢包和抖动。

先决条件

要求

本文档没有任何特定的要求。

使用的组件

本文档中的信息基于以下软件和硬件版本：

思科集成多业务路由器(ISR)和ISRG2平台上的Mediatrace功能 — Cisco IOS® 15.1(3)T版或更高版本
Cisco 3750平台上的Mediatrace功能 — Cisco IOS版本12.2(58)SE或更高版本
思科网真EX90 — 思科网真软件版本TE 6.0或更高版本上的Mediatrace功能

本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始（默认）配置。如果您使用的是真实网络，请确保您已经了解所有命令的潜在影响。

规则

有关文档约定的更多信息，请参考 Cisco 技术提示约定。

网络拓扑

在本示例中，解释了在两个EX90终端之间发生丢包的视频呼叫的配置。网络拓扑如下所示：

配置

配置Mediatrace发起方和响应方的过程非常简单。有关配置，请参阅以下示例。

中心 — 软件

interface Vlan201
 ip address 10.2.3.70 255.255.255.0

ip rsvp snooping

mediatrace responder
mediatrace initiator source-ip 10.2.3.70 max-sessions 100

中心广域网

interface GigabitEthernet0/0
 description "CE router connected to MPLS PE router"
 ip address 10.16.1.2 255.255.255.252
 ip rsvp source address 10.2.3.65
!
interface GigabitEthernet0/1
 description "Connected to Central-SW"
 ip address 10.2.3.65 255.255.255.0

mediatrace responder
mediatrace initiator source-ip 10.2.3.65 max-sessions 100

BR-WAN

interface GigabitEthernet0/0
 description "CE router connected to MPLS PE router"
 ip address 10.16.2.2 255.255.255.252
 ip rsvp source address 10.2.4.65
!
interface GigabitEthernet0/1
 description "Connected to BR3-SW"
 ip address 10.2.4.65 255.255.255.0

mediatrace responder
mediatrace initiator source-ip 10.2.4.65 max-sessions 100

BR-SW

interface Vlan202
 ip address 10.2.4.70 255.255.255.0

ip rsvp snooping

mediatrace responder
mediatrace initiator source-ip 10.2.4.70 max-sessions 100

故障排除方法

思科建议您在企业网络中所有适用节点上启用Mediatrace。在3750和ISR-G2等常见交换和路由平台中支持此功能。

第 1 步

确定所关注音频或视频路由表协议(RTP)流的源和目标IP地址/端口号。

EX90

xstatus MediaChannels
*s MediaChannels Call 9 IncomingAudioChannel 115 Encryption Status: Off
*s MediaChannels Call 9 IncomingAudioChannel 115 Audio Protocol: AACLD
*s MediaChannels Call 9 IncomingAudioChannel 115 Audio Mute: False
*s MediaChannels Call 9 IncomingAudioChannel 115 Audio Channels: 1
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTP Local IpAddress: 
   "10.2.3.41"
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTP Local Port: 16454
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTP Remote IpAddress: 
   "10.2.4.5"
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTP Remote Port: 16444
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTCP Local IpAddress: 
   "10.2.3.41"
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTCP Local Port: 16455
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTCP Remote IpAddress: 
"10.2.4.5"
*s MediaChannels Call 9 IncomingAudioChannel 115 Transport RTCP Remote Port: 16445
*s MediaChannels Call 9 IncomingVideoChannel 118 Encryption Status: Off
*s MediaChannels Call 9 IncomingVideoChannel 118 ChannelRole: Main
*s MediaChannels Call 9 IncomingVideoChannel 118 Video Protocol: H264
*s MediaChannels Call 9 IncomingVideoChannel 118 Video FrameRate: 30
*s MediaChannels Call 9 IncomingVideoChannel 118 Video ResolutionX: 640
*s MediaChannels Call 9 IncomingVideoChannel 118 Video ResolutionY: 360
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTP Local IpAddress: 
   "10.2.3.41"
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTP Local Port: 16456
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTP Remote IpAddress: 
"10.2.4.5"
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTP Remote Port: 16446
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTCP Local IpAddress: 
"10.2.3.41"
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTCP Local Port: 16457
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTCP Remote IpAddress: 
"10.2.4.5"
*s MediaChannels Call 9 IncomingVideoChannel 118 Transport RTCP Remote Port: 16447
*s MediaChannels Call 9 IncomingVideoChannel 121 Encryption Status: Off

步骤 2

确定始发端点所连接的交换机。此交换机可以使用Cisco发现协议(CDP)show命令。

EX90

xstatus Network
*s Network 1 Ethernet MacAddress: "FF:FF:FF:70:E6:B6"
*s Network 1 Ethernet Speed: 100full
*s Network 1 IPv4 Address: "10.2.3.41"
*s Network 1 IPv4 SubnetMask: "255.255.255.0"
*s Network 1 IPv4 Gateway: "10.2.3.65"
*s Network 1 IPv4 DNS Domain Name: ""
*s Network 1 IPv4 DNS Server 1 Address: ""
*s Network 1 IPv4 DNS Server 2 Address: ""
*s Network 1 IPv4 DNS Server 3 Address: ""
*s Network 1 IPv4 DNS Server 4 Address: ""
*s Network 1 IPv4 DNS Server 5 Address: ""
*s Network 1 IPv6 Address: ""
*s Network 1 IPv6 Gateway: ""
*s Network 1 MTU: 1500
*s Network 1 VLAN Voice VlanId: "201"
*s Network 1 VLAN Native VlanId: "202"
*s Network 1 CDP Platform: "cisco WS-C3750V2-24TS"
*s Network 1 CDP Version: "Cisco IOS Software, C3750 Software 
   (C3750-IPSERVICESK9-M), Version 12.2(58)SE2, RELEASE SOFTWARE (fc1)
   *Technical Support: http://www.cisco.com/techsupport*Copyright (c) 
   1986-2011 by Cisco Systems, Inc.*Compiled Thu 21-Jul-11 01:53 by 
   prod_rel_team"
*s Network 1 CDP Capabilities: "0x0028"
*s Network 1 CDP DeviceID: "Central-SW"
*s Network 1 CDP PortID: "FastEthernet1/0/23"
*s Network 1 CDP Duplex: "Full"
*s Network 1 CDP VTPMgmtDomain: ""
*s Network 1 CDP Address: "10.2.3.70"
*s Network 1 CDP PrimaryMgmtAddress: "10.2.3.70"
*s Network 1 CDP SysName: ""
*s Network 1 CDP SysObjectID: ""
*s Network 1 CDP VoIPApplianceVlanID: "201"
** end

步骤 3

登录到第一跳交换机并配置流说明符以唯一标识RTP流。此流说明符用于mediatrace poll命令中。

mediatrace flow-specifier RTP
 source-ip 10.2.3.41 source-port 16456
 dest-ip 10.2.4.5 dest-port 16446

步骤 4

输入mediatrace poll命令。

源值 — 源UC终端的IP地址
目标值 — 目标UC终端的IP地址
流说明符 — 包含4值元组以标识RTP流的流说明符的名称

#mediatrace poll path-specifier source 10.2.3.41 destination 10.2.4.5
   perf-monitor flow-specifier RTP
Started the data fetch operation.
Waiting for data from hops.
This may take several seconds to complete...
Data received for hop 1
Data received for hop 2
Data received for hop 3
Data received for hop 4
Data fetch complete.
Results:
Data Collection Summary:
  Request Timestamp: 11:00:54.302 EST Sun Mar 10 2013
  Request Status: Completed
  Number of hops responded (includes success/error/no-record): 4
  Number of hops with valid data report: 4
  Number of hops with error report: 0
  Number of hops with no data record: 0
Detailed Report of collected data&colon;
    Number of Mediatrace hops in the path: 4

    Mediatrace Hop Number: 1 (host=Central-Wan, ttl=254)
      Metrics Collection Status: Success
      Reachability Address: 10.2.3.65
      Ingress Interface: Gi0/1
      Egress Interface: Gi0/0
      Metrics Collected:
        Flow Sampling Start Timestamp: 10:26:48
        Loss of measurement confidence: FALSE
        Media Stop Event Occurred: FALSE
        IP Packet Drop Count (pkts): 0
        IP Byte Count (Bytes): 191965
        IP Packet Count (pkts): 402
        IP Byte Rate (Bps): 15996
        Packet Drop Reason: 64
        IP DSCP: 32
        IP TTL: 63
        IP Protocol: 0
        Media Byte Rate Average (Bps): 15058
        Media Byte Count (Bytes): 180709
        Media Packet Count (pkts): 402
        RTP Interarrival Jitter Average (usec): 155
        RTP Packets Lost (pkts): 0
        RTP Packets Expected (pkts): 397
        RTP Packet Lost Event Count: 0
        RTP Loss Percent (%): 0.00

    Mediatrace Hop Number: 2 (host=BR-Wan, ttl=251)
      Metrics Collection Status: Success
      Reachability Address: 10.16.2.2
      Ingress Interface: Gi0/0
      Egress Interface: Gi0/1
      Metrics Collected:
        Flow Sampling Start Timestamp: 09:58:40
        Loss of measurement confidence: FALSE
        Media Stop Event Occurred: FALSE
        IP Packet Drop Count (pkts): 0
        IP Byte Count (Bytes): 331523
        IP Packet Count (pkts): 694
        IP Byte Rate (Bps): 16576
        Packet Drop Reason: 64
        IP DSCP: 32
        IP TTL: 60
        IP Protocol: 0
        Media Byte Rate Average (Bps): 15604
        Media Byte Count (Bytes): 312091
        Media Packet Count (pkts): 694
        RTP Interarrival Jitter Average (usec): 1648
        RTP Packets Lost (pkts): 14
        RTP Packets Expected (pkts): 708
        RTP Packet Lost Event Count: 13
        RTP Loss Percent (%): 1.97

    Mediatrace Hop Number: 3 (host=BR-SW, ttl=251)
      Metrics Collection Status: Success
      Reachability Address: 10.2.4.70
      Ingress Interface: Fa1/0/22
      Egress Interface: Fa1/0/24
      Metrics Collected:
        Flow Sampling Start Timestamp: 22:50:37
        Loss of measurement confidence: FALSE
        Media Stop Event Occurred: FALSE
        IP Packet Drop Count (pkts): 0
        IP Byte Count (Bytes): 505526
        IP Packet Count (pkts): 1059
        IP Byte Rate (Bps): 16850
        Packet Drop Reason: 0
        IP DSCP: 32
        IP TTL: 60
        IP Protocol: 17
        Media Byte Rate Average (Bps): 16144
        Media Byte Count (Bytes): 484346
        Media Packet Count (pkts): 1059
        RTP Interarrival Jitter Average (usec): 1511
        RTP Packets Lost (pkts): 22
        RTP Packets Expected (pkts): 1075
        RTP Packet Lost Event Count: 21
        RTP Loss Percent (%): 2.04

    Mediatrace Hop Number: 4 (host=BR-EX90, ttl=251)
      Metrics Collection Status: Success
      Reachability Address: 10.2.4.5
      Ingress Interface: eth0
      Egress Interface: None
      Metrics Collected:
        Flow Sampling Start Timestamp: 11:02:00
        Loss of measurement confidence: FALSE
        Media Stop Event Occurred: FALSE
        IP Packet Drop Count (pkts): 0
        IP Byte Count (Bytes): 0
        IP Packet Count (pkts): 0
        IP Byte Rate (Bps): 0
        Packet Drop Reason: 0
        IP DSCP: 0
        IP TTL: 0
        IP Protocol: 17
        Media Byte Rate Average (Bps): 16000
        Media Byte Count (Bytes): 478219
        Media Packet Count (pkts): 1056
        RTP Interarrival Jitter Average (usec): 4953
        RTP Packets Lost (pkts): 17
        RTP Packets Expected (pkts): 1073
        RTP Packet Lost Event Count: 6
        RTP Loss Percent (%): 0.04

Central-SW#

数据分析

这些观察可以从mediatrace poll命令输出中得出：

RTP流的网络路径包含4个Central-SW中支持Mediatrace的设备：

中心广域网
BR-WAN
BR-SW
BR-EX90

中心WAN路由器上未发现丢包现象。
在BR-WAN、BR-SW和BR-EX90上观察到数据包丢失。
结论是，在中心WAN和BR-WAN之间会引入丢包。

常见问题

导致数据包丢失的典型因素包括：

差分服务代码点(DSCP)值不正确。
服务提供商网络中的监察器，以限制带宽利用率。
第2层错误，例如双工不匹配和控制器错误。

常见问题

问：Mediatrace是否与网络管理或监控系统集成？

答：是的，Cisco Prime协作使管理员只需单击一次即可使用Mediatrace对视频呼叫进行故障排除，并以图形格式显示结果。

问：我是否需要为Mediatrace功能启用资源预留协议(RSVP)?

答：否，Mediatrace使用RSVP-TP，在配置Mediatrace发起方或响应方时自动启用。无需输入ip rsvp bandwidth命令。

用于隔离网络损坏的Mediatrace

下载选项

非歧视性语言

关于此翻译

目录

简介

先决条件

要求

使用的组件

规则

网络拓扑

配置

中心 — 软件

中心广域网

BR-WAN

BR-SW

故障排除方法

第 1 步

步骤 2

步骤 3

步骤 4

数据分析

常见问题

常见问题

问：Mediatrace是否与网络管理或监控系统集成？

问：我是否需要为Mediatrace功能启用资源预留协议(RSVP)?

相关信息

修订历史记录

由思科工程师提供

此文档是否有帮助?

联系我们