Flexible NetFlow—MPLS Support Overview
This feature enables collecting MPLS label IDs by applying a flow monitor having a flow record that collects the MPLS label IDs as key or nonkey fields.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Flexible NetFlow - MPLS Support feature supports the monitoring of the following MPLS-related fields:
Information About Flexible NetFlow MPLS Support
This feature enables collecting MPLS label IDs by applying a flow monitor having a flow record that collects the MPLS label IDs as key or nonkey fields.
How to Configure Flexible NetFlow MPLS Support
Perform this optional task to configure a flow exporter for the flow monitor in order to export the data that is collected by Flexible NetFlow to a remote system for further analysis and storage.
Flow exporters are used to send the data that you collect with Flexible NetFlow to a remote system such as a NetFlow Collection Engine. Exporters use UDP as the transport protocol and use the Version 9 export format.
Note |
Each flow exporter supports only one destination. If you want to export the data to multiple destinations, you must configure multiple flow exporters and assign them to the flow monitor. You can export to a destination using either an IPv4 or IPv6 address. |
Note |
When you configure an exporter, configure the exporter in such a way that the source interface is defined as a WAN interface. This configuration helps you prevent any unpredictable behavior because the NAT is not applied on the packets. |
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
||
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
||
Step 3 |
flow exporter exporter-name Example:
|
Creates a flow exporter and enters Flexible NetFlow flow exporter configuration mode.
|
||
Step 4 |
description description Example:
|
(Optional) Creates a description for the flow exporter. |
||
Step 5 |
destination {hostname | ip-address } [vrf vrf-name ] Example:
|
Specifies the hostname or IP address of the system to which the exporter sends data.
|
||
Step 6 |
export-protocol {netflow-v5 | netflow-v9 | ipfix } Example:
|
Specifies the version of the NetFlow export protocol used by the exporter.
|
||
Step 7 |
transport udp udp-port Example:
|
Configures UDP as the transport protocol and specifies the UDP port on which the destination system is listening for exported Flexible NetFlow traffic. |
||
Step 8 |
exit Example:
|
Exits Flexible NetFlow flow exporter configuration mode and returns to global configuration mode. |
||
Step 9 |
flow monitor flow-monitor-name Example:
|
Enters Flexible NetFlow flow monitor configuration mode for the flow monitor that you created previously. |
||
Step 10 |
exporter exporter-name Example:
|
Specifies the name of an exporter that you created previously. |
||
Step 11 |
end Example:
|
Exits Flexible NetFlow flow monitor configuration mode and returns to privileged EXEC mode. |
||
Step 12 |
show flow exporter exporter-name Example:
|
(Optional) Displays the current status of the specified flow exporter. |
||
Step 13 |
show running-config flow exporter exporter-name Example:
|
(Optional) Displays the configuration of the specified flow exporter. |
Perform this required task to create 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. These record formats can be a user-defined format. An advanced user can create a customized format using the flow record command.
If you want to use a customized record, 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 no ip flow monitor 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. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
flow monitor monitor-name Example:
|
Creates a flow monitor and enters Flexible NetFlow flow monitor configuration mode.
|
Step 4 |
description description Example:
|
(Optional) Creates a description for the flow monitor. |
Step 5 |
record {record-name } Example:
|
Specifies the record for the flow monitor. |
Step 6 |
cache {timeout {active } seconds | { normal } Example: |
|
Step 7 |
Repeat Step 6 as required to finish modifying the cache parameters for this flow monitor. |
— |
Step 8 |
exporter exporter-name Example:
|
(Optional) Specifies the name of an exporter that was created previously. |
Step 9 |
end Example:
|
Exits Flexible NetFlow flow monitor configuration mode and returns to privileged EXEC mode. |
Step 10 |
show flow monitor [[name ] monitor-name [cache [format {csv | record | table } ]] ] Example:
|
(Optional) Displays the status for a Flexible NetFlow flow monitor. |
Step 11 |
show running-config flow monitor monitor-name Example:
|
(Optional) Displays the configuration of the specified flow monitor. |
Before it can be activated, a flow monitor must be applied to at least one interface. Perform this required task to activate a flow monitor.
While running the ip flow monitor command for the first interface to enable FNF monitor, you may see the following warning message displaying a GLOBAL memory allocation failure. This log is triggered by enabling FNF monitoring with a large cache size.
Jul 4 01:45:00.255: %CPPEXMEM-3-NOMEM: F0/0: cpp_cp_svr: QFP: 0, GLOBAL memory allocation of 90120448 bytes by FNF failed
Jul 4 01:45:00.258: %CPPEXMEM-3-TOPUSER: F0/0: cpp_cp_svr: QFP: 0, Top User: CPR STILE EXMEM GRAPH, Allocations: 877, Type: GLOBAL
Jul 4 01:45:00.258: %CPPEXMEM-3-TOPUSER: F0/0: cpp_cp_svr: QFP: 0, Top User: SBC, Bytes Allocated: 53850112, Type: GLOBAL
The warning message does not necessarily indicate a flow monitor application failure. The warning message can indicate internal steps that FNF uses for applying memory from the EXMEM infrastructure.
To ensure that the FNF monitor is enabled successfully, use the show flow monitor monitor-name command to check Status (allocated or not allocated) of a flow monitor. For more information, see Displaying the Current Status of a Flow Monitor.
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
interface type number Example:
|
Specifies an interface and enters interface configuration mode. |
Step 4 |
{ip | ipv6 } flow monitor monitor-name {input | output } Example:
|
Activates a flow monitor that was created previously by assigning it to the interface to analyze traffic. |
Step 5 |
Repeat Steps 3 and 4 to activate a flow monitor on any other interfaces in the device over which you want to monitor traffic. |
— |
Step 6 |
end Example:
|
Exits interface configuration mode and returns to privileged EXEC mode. |
Step 7 |
show flow interface type number Example:
|
Displays the status of Flexible NetFlow (enabled or disabled) on the specified interface. |
Step 8 |
show flow monitor name monitor-name cache format record Example:
|
Displays the status, statistics, and flow data in the cache for the specified flow monitor. |
Configuration Examples for Flexible NetFlow MPLS Support
The following example shows how to configure a flow monitor using the Flexible NetFlow "BGP ToS next-hop" predefined record to monitor IPv4 traffic.
This sample starts in global configuration mode:
Router(config)#flow record mpls_1
Router(config-flow-record)#match mpls label 1 details
Router(config-flow-record)#match mpls label 1 exp
Router(config-flow-record)#match mpls label 1 ttl
Router(config-flow-record)#match mpls label 2 details
Router(config-flow-record)#match mpls label 3 details
Router(config-flow-record)#collect mpls label 4 details
Router(config-flow-record)#collect mpls label 5 details
!
flow monitor mpls_1
record mpls_1
!
interface Ethernet 0/0
mpls flow monitor mpls_1 input
mpls flow monitor mpls_1 output
!
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
Flexible NetFlow conceptual information and configuration tasks |
Flexible NetFlow Configuration Guide |
Flexible NetFlow commands |
Cisco IOS Flexible NetFlow Command Reference |
Standard |
Title |
---|---|
No new or modified standards/RFCs are supported by this feature. |
— |
MIB |
MIBs Link |
---|---|
None |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
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. |
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.
Feature Name |
Releases |
Feature Information |
---|---|---|
Flexible NetFlow: MPLS Support |
Cisco IOS XE Release 3.9S |
Enables collecting MPLS label IDs by applying a flow monitor having a flow record that collects the MPLS label IDs as key or nonkey fields. The following commands were introduced or modified: collect mplslabel, match mplslabel, mpls flow monitor. |