Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 106 / 2086

1-26
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 1 Product Overview
Management Features
For information on configuring this feature, refer to the following documents:
http://www.cisco.com/en/US/docs/ios-xml/ios/msp/configuration/15-1sg/med-ser-prxy.html
http://www.cisco.com/en/US/docs/ios-xml/ios/msp/configuration/xe-3sg/med-ser-prxy-xe.html
Cisco Medianet AutoQoS
Cisco Medianet AutoQoS provides a default configuration to ease the process of enabling QoS on
switches. This process can be difficult given the functional/behavioral differences in QoS across
different platforms. This functionality extend AutoQoS functionality for the Catalyst 4500 to support
video traffic as well as other kinds of traffic.
The goal of AutoQos is to simplify the work customers have to undertake while configuring their
networks to support QoS. This is done by automating QoS configurations to handle various classes of
traffic. AutoQos for Medianet provides commands, which act as macros that call existing CLI commands
to implement desired configurations. You are required to specify the type of device (PC, another switch,
ip camera, etc.) connected to a given interface. AutoQos for Medianet applies a default QoS
configuration to that interface, which you can later fine-tune as needed.
For details, refer to Chapter 44, “Configuring Quality of Service.”
Cisco Medianet Flow Metadata
Flow Metadata is the data that qualifies other data. Flow Metadata aids in supporting an intelligent
network by making the network aware about the type, nature, and characteristics of the media stream
that flows in the network. Flow Metadata also allows for the network to apply policies on the media
streams. Across the Medianet system, Flow Metadata is produced, transported, stored, retrieved, and
acted on consistently by a wide variety of Medianet services.
The Flow Metadata infrastructure provides a framework that allows data from one component be
available to another component on the same network element as well as across network elements.
Flow Metadata is supported on releases prior to Cisco IOS Release 15.1(1)SG. Flow metadata is the data
that describes a flow in the network. This Flow Metadata describes the five tuple flow along with the
attributes. Network elements can take action based on the Flow Metadata generated by the endpoints.
The Flow Metadata infrastructure consists of two major components: producers and consumers.
•
Flow Metadata producer is any source of Flow Metadata. The producer propagates all the attributes
of a given flow. Producers can be anywhere in the network: endpoint, proxy agents, or intermediate
nodes. Currently, Flow Metadata generated by the endpoints is supported. Producers use a specific
transport protocol, such as RSVP for signalling the Flow Metadata attributes and store the
information in a database, referred to as the control plane database, which can then be used by the
consumers.
• Flow Metadata consumer is any network element that uses the flow tuple and Flow Metadata
provided by the producers. The flow tuple and Flow Metadata can also be propagated along the
media path to consumers in different network elements via a transport infrastructure.
For configuration details, refer to the following URLs:
http://www.cisco.com/en/US/docs/ios-xml/ios/mdata/configuration/xe-3sg/metadata-framework.html
http://www.cisco.com/en/US/docs/ios-xml/ios/mdata/configuration/15-1sg/metadata-framework.html
For details on the Flow Metadata commands, refer to the following URL:
http://www.cisco.com/en/US/docs/ios-xml/ios/qos/command/qos-cr-book.html