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.
Chapter 6<br />
<strong>Medianet</strong> Management and Visibility Design Considerations<br />
<strong>Cisco</strong> Network Analysis Module<br />
bandwidth percent 4<br />
dbl<br />
class SCAVENGER-QUEUE<br />
bandwidth percent 1<br />
class class-default<br />
bandwidth percent 25<br />
dbl<br />
!<br />
~<br />
!<br />
interface GigabitEthernet3/1<br />
description CONNECTION TO ME-WESTDIST-3 GIG1/13<br />
no switchport<br />
ip address 10.17.100.38 255.255.255.252<br />
ip pim sparse-mode<br />
load-interval 30<br />
service-policy output 1P7Q1T-GIG3/1<br />
!<br />
~<br />
!<br />
interface GigabitEthernet3/3<br />
description CONNECTION TO ME-WESTDIST-4 GIG1/2<br />
no switchport<br />
ip address 10.17.100.41 255.255.255.252<br />
ip pim sparse-mode<br />
load-interval 30<br />
service-policy output 1P7Q1T-GIG3/3<br />
!<br />
~<br />
Notice that the class-map definitions shown at the top of the configuration example are shared between<br />
the policy maps. However, a unique policy map name is applied to each of the GigabitEthernet uplink<br />
interfaces.<br />
Referring back to Example 6-20, when a policer is applied to a queue, the bit rates of the data that<br />
conform, exceed, and violate the policer committed information rate (CIR) are also displayed within the<br />
show policy-map interface command. This information can provide a view of how much traffic is<br />
currently being handled by a policed queue, and whether sufficient bandwidth has been provisioned on<br />
the policer for the service classes handled by the queue. The final two highlighted sections in<br />
Example 6-20 provide an aggregate byte count of the packets handled by the particular queue, as well as<br />
the number of packets dropped because of insufficient buffer space on the queue. This holds for either<br />
the priority queue defined via the priority command, or a class-based weighted fair queueing (CBWFQ)<br />
defined via the bandwidth command. You can get an estimate of the overall data rate through a particular<br />
queue by running the show policy-map interface command several times over fixed time intervals and<br />
dividing the difference in byte count by the time interval.<br />
<strong>Cisco</strong> Catalyst 3750G/3750E Series Commands<br />
When QoS is enabled on the <strong>Cisco</strong> Catalyst 3750G/3750E Series switches with the mls qos global<br />
command, egress queueing consists of four queues; one of which can be a priority queue, each with three<br />
thresholds (1P3Q3T). The third threshold on each queue is pre-defined for the queue-full state (100<br />
percent). Queue settings such as buffer allocation ratios and drop threshold minimum and maximum<br />
settings are defined based on queue-sets applied across a range of interfaces; not defined per interface.<br />
The <strong>Cisco</strong> Catalyst 3750G/3750E Series switches support two queue sets. Ports are mapped to one of the<br />
two queue-sets. By default, ports are mapped to queue-set 1. The show platform port-asic stats drop<br />
command allows you to view interface drops per queue on the switch port. Example 6-22 shows the<br />
output from a NME-XD-24ES-1S-P switch module within a <strong>Cisco</strong> 3845 ISR, which runs the same code<br />
base as the <strong>Cisco</strong> Catalyst 3750G.<br />
OL-22201-01<br />
<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />
6-57