62-2
Software Configuration Guide—Release IOS XE 3.3.0SG and IOS 15.1(1)SG
OL-25340-01
Chapter 62 Configuring Flexible NetFlow
match ipv4 source address
match ipv4 destination address
collect counter bytes long
collect counter packets long
collect timestamp sys-uptime first
collect timestamp sys-uptime last
!
flow monitor m1
! monitor refers record configuration and optionally exporter
! configuration. It specifies the cache size i.e. how many unique flow
! records to collect
record r1
exporter e1
cache timeout active 60
cache timeout inactive 30
cache entries 1000
!interface GigabitEthernet 3/1
! layer2-switched allows collection of flow records even when the packet is
! bridged
ip flow monitor m1 layer2-switched input
!
interface GigabitEthernet 3/2
ip flow monitor m1 input
!
3. Flow collection is supported on multiple targets (Port, VLAN, per-port per-VLAN (FNF can be
enabled on a specific VLAN on a given port)) and on a port-channel (FNF is configured on the
port-channel interface, rather than individual member ports).
4. 64 unique flow record configurations are supported.
5. Flow QoS/UBRL and FNF cannot be configured on the same target. (For information on Flow-based
QoS, see the section Flow-based QoS, page 40-10.)
6. 14,000 unique IPv6 addresses can be monitored.
7. On a given target, one monitor per traffic type is allowed. However, you can configure multiple
monitors on the same target for different traffic types.
For example, the following configuration is allowed:
! vlan config 10
ip flow monitor <name> input
ipv6 flow monitor <name> input
!
The following configuration is not allowed:
!
interface GigabitEthernet 3/1
ip flow monitor m1 input
ip flow monitor m2 input
8. On a given target monitoring Layer 2 and Layer 3, simultaneous traffic is not supported:
interface channel-group 1
datalink flow monitor m1 input
ip flow monitor m2 input
!
9. Selection of Layer 2 and Layer 3 packet fields in a single flow record definition is not allowed.
However, ingress 802.1Q VLAN Id of packet and Layer 3 packet field selection is allowed.
10. In order to attach a monitor to port or port-vlan targets, a flow record matching on ingress 802.1Q
VLAN Id as key field, must match on input interface also as key field.