Flexible Netflow—Egress VRF Support

The Flexible Netflow—Egress VRF Support feature enables collecting the virtual routing and forwarding (VRF) ID from outgoing packets on a router by applying an output flow monitor having a flow record that collects the VRF ID as a key or a nonkey field.

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 at the end of this module.

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 Flexible Netflow Egress VRF Support

Flexible Netflow—Egress VRF Support Overview

The Flexible Netflow—Egress VRF Support feature enables collecting the virtual routing and forwarding (VRF) ID from outgoing packets on a router by applying an output flow monitor having a flow record that collects the VRF ID as a key or a nonkey field.

How to Configure Flexible Netflow Egress VRF Support

Configuring a Customized Flow Record

Perform this task to configure a customized flow record.

Customized flow records are used to analyze traffic data for a specific purpose. A customized flow record must have at least one match criterion for use as the key field and typically has at least one collect criterion for use as a nonkey field.

There are hundreds of possible permutations of customized flow records. This task shows the steps that are used to create one of the possible permutations. Modify the steps in this task as appropriate to create a customized flow record for your requirements.

This example configures the IPv4 destination address as a key field for the record. For information about the other key fields available for the matchipv4 command, and the other match commands that are available to configure key fields, refer to the Cisco IOS Flexible NetFlow Command Reference .

Step 6

Repeat Step 5 as required to configure additional key fields for the record.

—

Step 7

collectinterface {input | output}

Example:

Device(config-flow-record)# collect interface input

Configures the input interface as a nonkey field for the record.

Note

This example configures the input interface as a nonkey field for the record. For information on the other collect commands that are available to configure nonkey fields, refer to the Cisco IOS Flexible NetFlow Command Reference.

Step 8

Repeat Step 7 as required to configure additional nonkey fields for the record.

Creating a Customized Flow Monitor

Each flow monitor has a separate cache assigned to it. Each flow monitor requires a record to define the contents and layout of its cache entries.

Before You Begin

If you want to use a customized record instead of using one of the Flexible NetFlow predefined records, you must create the customized record before you can perform this task.

If you want to add a flow exporter to the flow monitor for data export, you must create the exporter before you can complete this task.

Note

You must use the noipflowmonitor command to remove a flow monitor from all of the interfaces to which you have applied it before you can modify the parameters for the record command on the flow monitor. For information about the ipflowmonitor command, refer to the Cisco IOS Flexible NetFlow Command Reference.

Displays the status of Flexible NetFlow (enabled or disabled) on the specified interface.

Step 8

showflowmonitornamemonitor-namecacheformatrecord

Example:

Device# show flow monitor name FLOW_MONITOR-1 cache format record

Displays the status, statistics, and flow data in the cache for the specified flow monitor.

Configuration Examples for Flexible Netflow Egress VRF Support

Example Configuring Flexible NetFlow for Egress VRF Support

The following example configures the collection of the virtual routing and forwarding (VRF) ID from outgoing packets on a router by applying an output flow monitor having a flow record that collects the VRF ID as a key field.

MIBs

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 Flexible NetFlow—Egress VRF 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 www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Table 1 Feature Information for Flexible NetFlow—Egress VRF Support

Feature Name

Releases

Feature Information

Flexible NetFlow—Egress VRF Support

Cisco IOS XE Release 3.8S

Enables collecting the virtual routing and forwarding (VRF) ID from outgoing packets on a router by applying an output flow monitor having a flow record that collects the VRF ID as a key or a nonkey field.

The following commands were introduced or modified: collectrouting, matchrouting, option(FlexibleNetFlow, showflowmonitor.