Purpose
Command or Action
Enters flow record configuration mode.
flow record flow_record_name
Example:
Step 2
Device(config)#
flow record
flow-record-1
(Optional) Creates a description for the flow record.
description description
Example:
Step 3
Device(config-flow-record)#
description
flow-record-1
Specifies a match to the IP version from the IPv4 header.
match ipv4 version
Example:
Step 4
Device(config-flow-record)#
match ipv4 version
Specifies a match to the IPv4 protocol.
match ipv4 protocol
Example:
Step 5
Device(config-flow-record)#
match ipv4 protocol
Specifies a match to the application name.
match application name
Step 6
Example:
This action is mandatory for AVC support, as
this allows the flow to be matched against the
application.
Note
Device(config-flow-record)#
match application name
Specifies a match to the IPv4 address of the client (flow
initiator).
match connection client ipv4 address
Example:
Step 7
Device(config-flow-record)#
match connection
client ipv4 address
Specifies a match to the IPv4 address of the server (flow
responder).
match connection server ipv4 address
Example:
Step 8
Device(config-flow-record)#
match connection
server ipv4 address
Specifies a match to the transport port of the server.
match connection server transport port
Example:
Step 9
Device(config-flow-record)#
match connection
server transport port
Specifies a match to the observation point ID for flow
observation metrics.
match flow observation point
Example:
Step 10
Device(config-flow-record)#
match flow observation
point
Specifies to collect the direction — Ingress or Egress —
of the relevant side — Initiator or Responder — of the
collect flow direction
Example:
Step 11
bi-directional flow that is specified by the
initiator
Device(config-flow-record)#
collect flow direction
keyword in the
collect connection initiator
command in
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
120
Configuring Application Visibility and Control in a Wired Network
Creating a Flow Record
