03.02.2014 Views

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Summary<br />

Chapter 6<br />

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

Summary<br />

This design chapter has focused on functionality that can be used to provide increased visibility and<br />

management of video flows within an enterprise medianet. From a high-level perspective, the<br />

functionality can be separated into two broad categories: application-specific management functionality<br />

and network-embedded management functionality. Application-specific management refers to<br />

functionality within the components of a particular video solution: <strong>Cisco</strong> TelePresence, <strong>Cisco</strong> IP Video<br />

Surveillance, <strong>Cisco</strong> Digital Media Systems, and <strong>Cisco</strong> Desktop Video Collaboration.<br />

Network-embedded management refers to functionality embedded within the medianet infrastructure<br />

itself, which allows both visibility and management of video flows. These include specific embedded<br />

software features such as NetFlow and IPSLA, the <strong>Cisco</strong> router and <strong>Cisco</strong> Catalyst switch CLI itself, and<br />

also hardware modules such as the <strong>Cisco</strong> NAM embedded within <strong>Cisco</strong> Catalyst 6500 Series Switches.<br />

By implementing a QoS model that separates the various video applications into different service<br />

classes, which are then mapped to separate queues and drop thresholds within <strong>Cisco</strong> router and switch<br />

platforms, you can gain additional visibility into the video applications themselves by collecting flow<br />

information based on DSCP aggregation, as well as monitoring the router and switch queues. Typically,<br />

the more granular the QoS model (that is, up to 12 service classes) and the more queues and drop<br />

thresholds deployed throughout medianet infrastructure devices, the greater the visibility and ability to<br />

manage the flows.<br />

6-82<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!