The figure below illustrates a sample deployment scenario for the medianet metadata implementation.
Figure 2. Medianet Metadata Implementation
As illustrated in the figure above, two users from different locations can be in a WebEx, Telepresence, or a Cisco IP phone session.
This example assumes the users to be in a WebEx session. WebEx sessions typically require low latency guarantee from the network. QoS configurations can be used to obtain the required behavior. To achieve the required behavior, the required types of policy maps must be configured on the given interface to match the application ID of WebEx. Once this classification provisioning is done, metadata will also have a copy of this information in its classification database. One end of Webex session (endpoint A) signals the application as the metadata, using explicit signaling from the endpoints. The metadata information can be the application name, application ID, application version, and so on. This metadata information flows through the network along the media path.
Resource Reservation Protocol (RSVP) notifies the metadata framework about any incoming flow and provides the metadata information associated with the flow. A match action is performed between the decoded <Attribute, Value> pair and the WebEx metadata properties. If the match is successful, then the same information is propagated to the data plane. The data plane checks the appropriate classification requirements and takes the required QoS actions.
The following example shows how to configure QoS properties to work with the metadata framework. In the following sample configuration, a class map v1 is created.
! Creates a class-map with metadata-based filters
class-map match-all v1
match application webex-video
Next, a policy map p1 is created and the class v1 is added to it. The packets belonging to class v1 are given priority by giving the entire class a guaranteed bandwidth of 1 Mbps. That is, the aggregate of all the flows that match the <Attribute, Value> pair defined in the class v1 are given a guaranteed bandwidth. Any other QoS solutions such as policing, marking, or queueing can also be applied as a classification criterion.
! Create policy map and apply the classification properties
Then, the policy map is attached to the target interface:
! Attach the policy map to the target interface
interface Ethernet 1/0
service-policy output p1
For more information about QoS network traffic classification and solutions such as policing, marking, or queuing, see the
Quality of Service Solutions Configuration Guide.