Reverse Flow Metadata Support
The Reverse Flow Metadata Support feature creates reverse metadata flow sessions to act as proxy and signal metadata, and support QoS for the reverse session. The reverse sessions are created using the attributes of the forward session.
- Finding Feature Information
- Information About Reverse Flow Metadata Support
- How to Configure Reverse Flow Metadata Support
- How to Configure Reverse Flow Metadata Support
- Additional References
- Feature Information for Reverse Flow Metadata Support
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Reverse Flow Metadata Support
Metadata Reverse Flows
End devices provisioned with metadata producers such as Media Services Interface (MSI), Media Services Proxy (MSP), and Network Based Application Recognition (NBAR) add flows to metadata database. When an end device cannot signal metadata, a reverse metadata flow session is created to act as a proxy and signal metadata, and support QoS for the reverse session. The reverse sessions are created using the attributes of a forward session. The reverse flow session is enabled only on the device, which is connected to the endpoint and cannot signal metadata. That is when the device is not provisioned with a metadata producer such as MSP, MSI or NBAR.
How to Configure Reverse Flow Metadata Support
Configuring Reverse Flow Metadata Support
1.
enable
2.
configure
terminal
3.
metadata
flow
4.
metadata
flow
reverse
transmit
5.
exit
DETAILED STEPS
How to Configure Reverse Flow Metadata Support
Example: Configuring Reverse Flow Metadata Support
The following example shows how to enable reverse flow of metadata information in Global configuration mode:
Device> enable Device# configure terminal Device(config)# metadata flow Device(config)# metadata flow reverse transmit Device(config)# exit
The following example shows how to enable reverse flow of metadata information in Interface configuration mode:
Device> enable Device# configure terminal Device(config)# metadata flow Device(config)# interface Ethernet 0/1 Device(config-if)# metadata flow reverse transmit Device(config)# exit
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
Metadata commands |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Reverse Flow Metadata Support
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to . An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Information |
---|---|---|
Reverse Flow Metadata Support |
15.4(1)T 15.4(1)S 15.2(1)SY |
Reverse metadata flow sessions are created to act as a proxy and signal metadata, and support QoS for the reverse session. The reverse sessions are created using the attributes of the forward session. The following commands were introduced or modified: metadata flow reverse transmit . |