03.02.2014 Views

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Cisco</strong> Network Analysis Module<br />

Chapter 6<br />

<strong>Medianet</strong> Management and Visibility Design Considerations<br />

control and therefore the protection of service classes. When multiple service classes are mapped to a<br />

single queue, separate drop thresholds can be implemented (on platforms that support them) to provide<br />

differentiation of service classes within the queue. The implementation of queueing and drop thresholds<br />

is viewed as necessary to provide the correct per-hop treatment of the video application traffic to meet<br />

the overall desired service levels of latency, jitter, and packet loss across the medianet infrastructure. An<br />

example of the mapping of service classes to egress queueing on a <strong>Cisco</strong> Catalyst 6500<br />

WS-X6704-10GE line card, which has a 1P7Q8T egress queueing structure, as shown in Figure 6-22.<br />

Note that the percentage of bandwidth allocated per queue depends on the customer environment;<br />

Figure 6-22 shows only an example.<br />

Figure 6-22 Example Mapping of Service Classes to Egress Queueing on a <strong>Cisco</strong> Catalyst 6500<br />

Line Card with 1P7Q8T Structure<br />

Application<br />

DSCP<br />

1P7Q4T<br />

Network Control<br />

(CS7)<br />

EF<br />

Q8 (PQ)<br />

Internetwork Control<br />

Voice<br />

Multimedia Conferencing<br />

TelePresence<br />

Multimedia Streaming<br />

Call Signaling<br />

CS6<br />

EF<br />

AF4<br />

CS4<br />

AF3<br />

CS3<br />

CS4<br />

CS7<br />

CS6<br />

CS3<br />

CS2<br />

AF4<br />

Q7 (10%)<br />

Q6 (10%)<br />

Q5 (10%)<br />

Q6T4<br />

Q6T3<br />

Q6T2<br />

Q6T1<br />

Transactional Data<br />

AF2<br />

AF3<br />

Q4 (10%)<br />

Network Management<br />

CS2<br />

AF2<br />

Q3 (10%)<br />

Bulk Data<br />

Best Scavenger Effort<br />

Best Effort<br />

AF1<br />

CS1 DF<br />

DF<br />

DF/0<br />

AF1<br />

CS1<br />

Q2 (25%)<br />

Q1 (5%)<br />

Q1T2<br />

Q1T1<br />

228433<br />

This QoS methodology can also provide enhanced visibility into the amount of traffic from individual<br />

video application types crossing points within the medianet infrastructure. The more granular the<br />

mapping of individual video applications to service classes that are then mapped to ingress and egress<br />

queues, the more granular the visibility into the amount of traffic generated by particular video<br />

applications. You can also gain additional visibility into troubleshooting video quality issues caused by<br />

drops within individual queues on router and switch platforms.<br />

The following high-level methodology can be useful for troubleshooting video performance issues using<br />

the router and switch CLI. As with anything, this methodology is not perfect. Some of the shortcomings<br />

of the methodology are discussed in the sections that cover the individual CLI commands. However, it<br />

can often be used to quickly identify the point within the network infrastructure where video quality<br />

issues are occurring. The steps are as follows:<br />

1. Determine the Layer 3 hop-by-hop path of the particular video application across the medianet<br />

infrastructure from end-to-end, starting from the Layer 3 device closest to one end of the video<br />

session. The traceroute CLI utility can be used for this function.<br />

6-36<br />

<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />

OL-22201-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!