Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Cisco</strong> Network Analysis Module<br />
Chapter 6<br />
<strong>Medianet</strong> Management and Visibility Design Considerations<br />
Port Rx-No-Pkt-Buff RxPauseFrames TxPauseFrames PauseFramesDrop<br />
Gi1/1 0 0 0 0<br />
Gi1/2 0 0 0 0<br />
...<br />
Gi1/48 0 0 0 0<br />
Port UnsupOpcodePause<br />
Gi1/1 0<br />
Gi1/2 0<br />
...<br />
Gi1/48 0<br />
The first two highlighted sections can provide information regarding how many unicast and multicast<br />
packets have crossed the interface in the inbound or outbound direction. Multicast traffic is often used<br />
to support real-time and VoD broadcasts. The multicast packet count within the switch interface<br />
increments from when the switch was reloaded or the counters were manually cleared. Because of this,<br />
and because the information does not include the byte count, you cannot use the statistics alone to<br />
determine the data rate of multicast traffic across the interface. However, you may be able to gain some<br />
useful information regarding the percentage of multicast traffic on the interface based on the ratio of the<br />
unicast to multicast packets seen.<br />
The third highlighted section provides two additional pieces of information. First, it indicates the number<br />
of queues per interface. Because the output above is from a <strong>Cisco</strong> Catalyst 4948 switch, four transmit<br />
queues per interface are supported. Second, the output indicates the amount of traffic, in bytes, that has<br />
been transmitted per queue per interface. Because this is a summation of bytes since the counters were<br />
last cleared or the switch reloaded, you must run the command multiple times over a time interval to get<br />
a rough estimate of the byte rate over that time period. This can be used to gain an idea of the current<br />
data rate of a particular traffic service class across the switch interface.<br />
The final two highlighted sections indicate the number of packets dropped in the egress direction, per<br />
transmit queue. You can use this information to assist in troubleshooting a video application<br />
performance issue or fault condition caused by packet loss. Note that Dbl-Drops are drops that are the<br />
result of the dynamic buffer limiting (DBL) algorithm, which attempts to fairly allocate buffer usage per<br />
flow through the <strong>Cisco</strong> Catalyst 4500 switch. You have the option of enabling or disabling DBL per<br />
service class on the switch.<br />
To make use of information regarding transmit queues drops shown in Example 6-17, you must<br />
understand which traffic classes are assigned to which transmit queues. For <strong>Cisco</strong> Catalyst 4500 Series<br />
switches with classic supervisors as well as <strong>Cisco</strong> Catalyst 4900 Series switches, the show qos maps<br />
command can be used to display which DSCP values are mapped to which transmit queues on the switch,<br />
as shown in Example 6-18.<br />
Example 6-18<br />
Output from <strong>Cisco</strong> Catalyst 4948 show qos maps Command<br />
tp-c2-4948-1#show qos maps<br />
DSCP-TxQueue Mapping Table (dscp = d1d2) ! Provides mapping of DSCP value to transmit<br />
! queue on the switch<br />
d1 : d2 0 1 2 3 4 5 6 7 8 9<br />
-------------------------------------<br />
0 : 02 01 01 01 01 01 01 01 01 01<br />
1 : 01 01 01 01 01 01 04 02 04 02<br />
2 : 04 02 04 02 04 02 04 02 04 02<br />
3 : 04 02 03 03 04 03 04 03 04 03<br />
4 : 03 03 03 03 03 03 03 03 04 04<br />
5 : 04 04 04 04 04 04 04 04 04 04<br />
6 : 04 04 04 04<br />
Policed DSCP Mapping Table (dscp = d1d2)<br />
d1 : d2 0 1 2 3 4 5 6 7 8 9<br />
6-52<br />
<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />
OL-22201-01