Feedback
Table Of Contents
Cisco Performance Monitor Commands
action (policy react and policy inline react)
alarm severity (policy react and policy inline react)
alarm type (policy react and policy inline react)
collect transport event packet-loss counter
description (Performance Monitor)
flow monitor type performance-monitor
flow record type performance-monitor
match mpls experimental topmost
match packet length (class-map)
match transport destination-port
policy-map type performance-monitor
service-policy type performance-monitor
show performance monitor cache
show performance monitor clock rate
show performance monitor clients
show performance monitor history
show performance monitor status
show policy-map type performance-monitor
threshold value (policy react and policy inline react)
Cisco Performance Monitor Commands
action (policy react and policy inline react)
To configure which applications which will receive an alarm or notification, use the action command in policy react configuration mode and policy inline react configuration mode. To disable the sending alarms or notifications, use the no form of this command.
action {syslog | snmp}
no action {syslog | snmp}
Syntax Description
syslog
Sends an alarm or notification to the syslog.
snmp
Sends an alarm or notification to the SNMP MIB variables.
Command Default
Information is saved to syslog.
Command Modes
Policy react configuration (config-pmap-c-react)
Policy inline react configuration (config-spolicy-inline-react)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You can configure multiple action commands to allow more than one recipients to receive an alarm or notification.
Examples
The following example shows how to specify that SNMP MIB variables will receive an alarm or notification, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# react 2000 rtp-jitter-averageRouter(config-pmap-c-react)# action snmpThe following example shows how to specify that SNMP MIB variables will receive an alarm or notification, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# react 2000 rtp-jitter-averageRouter(config-spolicy-inline-react)# action snmpRelated Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
alarm severity (policy react and policy inline react)
To configure the severity of alarms sent for a Performance Monitor policy, use the alarm severity command in policy react configuration mode and policy inline react configuration mode. To return to the default and send all alarms, use the no form of this command.
alarm severity {alert | critical | emergency | error | info}
no alarm severity {alert | critical | emergency | error | info}
Syntax Description
alert
Sends only alerts.
critical
Sends only critical alarms.
emergency
Sends only emergency alarms.
error
Sends only errors.
info
Sends only informational messages.
Command Default
Alarm severity is set to info.
Command Modes
Policy react configuration (config-pmap-c-react)
Policy inline react configuration (config-spolicy-inline-react)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The definition of the alarms types are listed below in order of severity:
•
Emergency—System unusable
•
•
•
Examples
The following example shows how to specify that only emergency alarms will be sent, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# react 2000 rtp-jitter-averageRouter(config-pmap-c-react)# alarm severity emergencyThe following example shows how to specify that only emergency alarms will be sent, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# react 2000 rtp-jitter-averageRouter(config-spolicy-inline-react)# alarm severity emergencyRelated Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
alarm type (policy react and policy inline react)
To configure the types of alarms sent for a Performance Monitor policy, use the alarm type command in policy react configuration mode and policy inline react configuration mode. To return to the default and send all alarms, use the no form of this command.
alarm type {discrete | grouped {count number | percent number}
no alarm type {discrete | grouped {count number | percent number}
Syntax Description
Command Default
Alarm type is set to discrete.
Command Modes
Policy react configuration (config-pmap-c-react)
Policy inline react configuration (config-spolicy-inline-react)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The monitored event is specified by the react command. You can group alarms by whether they exceed a specified percentage or count.
Examples
The following example shows how to specify that only percentage type alarms will be sent, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# react 2000 rtp-jitter-averageRouter(config-pmap-c-react)# alarm type percent 80The following example shows how to specify that only percentage type alarms will be sent, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# react 2000 rtp-jitter-averageRouter(config-spolicy-inline-react)# alarm type percent 80Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
class-map
To create a class map to be used for matching packets to a specified class, use the class-map command in global configuration mode. To remove an existing class map from the router, use the no form of this command. The class-map command enters class-map configuration mode in which you can enter one of the match commands to configure the match criteria for this class.
Cisco 2600, 3660, 3845, 6500, 7200, 7401, and 7500 Series Routers
class-map [type {stack | access-control | port-filter | queue-threshold | logging log-class}] [match-all | match-any] class-map-name
no class-map [type {stack | access-control | port-filter | queue-threshold | logging log-class}] [match-all | match-any] class-map-name
Cisco 7600 Series Routers
class-map class-map-name [match-all | match-any]
no class-map class-map-name [match-all | match-any]
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
class-map class-map-name
no class-map class-map-name
Syntax Description
Command Default
No class map is configured by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
Only the class-map-name argument is available.
Cisco 2600, 3660, 3845, 6500, 7200, 7401, 7500, and ASR 1000 Series Routers
Use the class-map command to specify the class that you will create or modify to meet the class-map match criteria. This command enters class-map configuration mode in which you can enter one of the match commands to configure the match criteria for this class. Packets that arrive at either the input interface or the output interface (determined by how the service-policy command is configured) are checked against the match criteria configured for a class map to determine if the packets belong to that class.
When configuring a class map, you can use one or more match commands to specify match criteria. For example, you can use the match access-group command, the match protocol command, or the match input-interface command. The match commands vary according to the Cisco IOS release. For more information about match criteria and match commands, see the "Modular Quality of Service Command-Line Interface (CLI) (MQC)" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.
Cisco 7600 Series Routers
You apply the class-map command and its commands on a per-interface basis to define packet classification, marking, aggregate, and flow policing as part of a globally named service policy.
You can attach a service policy to an EtherChannel. Do not attach a service policy to a port that is a member of an EtherChannel.
After the router is in class-map configuration mode, the following configuration commands are available:
•
•
•
–
–
The following commands appear in the CLI help but are not supported on LAN interfaces or WAN interfaces on the Optical Service Modules (OSMs):
•
•
•
•
OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
Policy Feature Card (PFC) QoS does not support the following commands:
•
•
•
•
•
If you enter these commands, PFC QoS does not detect the unsupported keywords until you attach a policy map to an interface. When you try to attach the policy map to an interface, you get an error message. For additional information, see the Cisco 7600 Series Router Cisco IOS Software Configuration Guide and the Cisco IOS command references.
After you have configured the class-map name and are in class-map configuration mode, you can enter the match access-group and match ip dscp commands. The syntax for these commands is as follows:
match [[access-group {acl-index | acl-name}] | [ip {dscp | precedence} value]]
See Table 8 for a syntax description of the match commands.
Examples
The following example specifies class101 as the name of a class, and it defines a class map for this class. The class named class101 specifies policy for traffic that matches access control list 101.
Router(config)# class-map class101Router(config-cmap)# match access-group 101The following example shows how to define FPM traffic classes for slammer and UDP packets. The match criteria defined within the class maps are for slammer and UDP packets with an IP length not to exceed 404 bytes, UDP port 1434, and pattern 0x4011010 at 224 bytes from the start of the IP header.
Router(config)# load protocol disk2:ip.phdfRouter(config)# load protocol disk2:udp.phdfRouter(config)# class-map type stack match-all ip-udpRouter(config-cmap)# description "match UDP over IP packets"Router(config-cmap)# match field ip protocol eq 0x11 next udpRouter(config)# class-map type access-control match-all slammerRouter(config-cmap)# description "match on slammer packets"Router(config-cmap)# match field udp dest-port eq 0x59ARouter(config-cmap)# match field ip length eq 0x194Router(config-cmap)# match start 13-start offset 224 size 4 eq 0x4011010The following example shows how to configure a port-filter policy to drop all traffic that is destined to closed or "nonlistened" ports except SNMP.
Router(config)# class-map type port-filter pf-classRouter(config-cmap)# match not port udp 123Router(config-cmap)# match closed-portsRouter(config-cmap)# exitRouter(config)# policy-map type port-filter pf-policyRouter(config-pmap)# class pf-classRouter(config-pmap-c)# dropRouter(config-pmap-c)# endThe following example shows how to configure a class map named ipp5, and enter a match statement for IP precedence 5:
Router(config)# class-map ipp5Router(config-cmap)# match ip precedence 5Related Commands
clock-rate (policy RTP)
To configure the rate for the RTP packet time-stamp clock, use the clock-rate command in policy RTP configuration mode. To remove the configuration, use the no form of this command.
clock-rate {type-number | type-name} rate
no clock-rate
Syntax Description
Command Default
Clock rate is 90000.
Command Modes
policy RTP configuration (config-pmap-c-mrtp)
policy inline RTP configuration (config-spolicy-inline-mrtp)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
For more information about how the clock rate for RTP packet time-stamp clock is used to calculate the packet arrival latency, see RFC 3550, RTP, A Transport Protocol for Real-Time Applications. The clock rate has to be synchronized with the routers along the path of the flow. Because the clock rate can vary depending on the payload codec type, a keyword is provided to set the expected clock rate.
The available values for type-name and type-number are celb (25), cn (13), dvi4 (5) (8000 Hz as described in RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control), dvi4-2 (6) (8000 Hz as described in RFC 3551), dvi4-3 (16) (DVI4 Dipol 11025 Hz), dvi4-4 (17) DVI4 Dipol 22050 Hz), g722 (9), g723 (4), g728 (15), g729 (18), gsm (3), h261 (31), h263 (34), jpeg (26), l16 (11) (L16 channel 1), l16-2 (10) (L16 channel 2), lpc (7), mp2t (33), mpa (14), mpv (32), nv (28), pcma (8), pcmu (0), qcelp (12).
Examples
The following example shows how to set the rate for the RTP packet time-stamp clock,while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpRouter(config-pmap-c-mrtp)# clock-rate 8 9600The following example shows how to set the rate for the RTP packet time-stamp clock, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRouter(config-spolicy-inline-mrtp)# clock-rate 8 9600Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
collect application media
To configure one of the application media fields as a nonkey field for a flow record, use the collect application media command in flow record configuration mode. To disable the use of one of the application media field as a nonkey field for a flow record, use the no form of this command.
collect application media {bytes {rate | counter [long]} | packets {rate [variation] | counter [long]}| events}
no collect application media {bytes | packets | events}
Syntax Description
Command Default
The application media field is not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures application media packet field as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect application media packetsRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect counter
To configure one of the counter fields as a nonkey field for a flow record, use the collect counter command in flow record configuration mode. To disable the use of one of the counter fields as a nonkey field for a flow record, use the no form of this command.
collect counter {bytes [long | rate] | packets [dropped [long] | long]}
no collect counter {bytes [long | rate] | packets [dropped [long] | long]}
Syntax Description
Command Default
The counter fields are not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures the dropped packet counter field as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect counter packets droppedRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect flow
To configure the flow direction, the flow sampler ID number, or reason why the flow ended as a nonkey field for a flow record, use the collect flow command in flow record configuration mode. To disable the use of the flow direction and the flow sampler ID number as a nonkey field for a flow record, use the no form of this command.
collect flow {direction | sampler}
no collect flow {direction | sampler}
Cisco IOS Release 15.1(4)M1
collect flow direction
no collect flow direction
Syntax Description
Command Default
The flow direction and the flow sampler ID number are not configured as nonkey fields.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
collect flow direction
This field indicates the direction of the flow. This is of most use when a single flow monitor is configured for input and output flows. It can be used to find and eliminate flows that are being monitored twice, once on input and once on output. This field may also be used to match up pairs of flows in the exported data when the two flows are flowing in opposite directions.
collect flow sampler
This field contains the ID of the flow sampler used to monitor the flow. This is useful when more than one flow sampler is being used with different sampling rates. The flow exporter option sampler-table command exports options records with mappings of the flow sampler ID to sampling rate so the collector can calculate the scaled counters for each flow.
Examples
The following example configures the ID of the flow sampler that is assigned to the flow as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect flow samplerCisco Performance Monitor in Cisco IOS Release 15.1(4)M1
The following example configures the direction in which the flow was monitored as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect flow directionRelated Commands
collect interface
To configure the input and output interface as a nonkey field for a flow record, use the collect interface command in flow record configuration mode. To disable the use of the input and output interface as a nonkey field for a flow record, use the no form of this command.
collect interface {input | output}
no collect interface {input | output}
Syntax Description
Command Default
The input and output interface is not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the flow record type performance-monitor command.
Examples
The following example configures the input interface as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect interface inpuThe following example configures the output interface as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect interface outputCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the input interface as a nonkey field:
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect interface inputRelated Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect ipv4
To configure one or more of the IPv4 fields as a nonkey field for a flow record, use the collect ipv4 command in flow record configuration mode. To disable the use of one or more of the IPv4 fields as a nonkey field for a flow record, use the no form of this command.
collect ipv4 {dscp | header-length | id | option map | precedence | protocol | tos | version}
no collect ipv4 {dscp | header-length | id | option map | precedence | protocol | tos | version}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
collect ipv4 dscp
no collect ipv4 dscp
Syntax Description
Command Default
The IPv4 fields are not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Note
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
Only the the dscp keyword is available. You must first enter the flow record type performance-monitor command.
Examples
The following example configures the DSCP field as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect ipv4 dscpCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the DSCP field as a nonkey field:
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect ipv4 dscpRelated Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect ipv4 destination
To configure the IPv4 destination address as a nonkey field for a flow record, use the collect ipv4 destination command in flow record configuration mode. To disable the use of an IPv4 destination address field as a nonkey field for a flow record, use the no form of this command.
collect ipv4 destination {address | {mask | prefix} [minimum-mask mask]}
no collect ipv4 destination {address | {mask | prefix} [minimum-mask mask]}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
collect ipv4 destination mask [minimum-mask mask]}
no collect ipv4 destination mask [minimum-mask mask]}
Syntax Description
Command Default
The IPv4 destination address is not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
Only the mask and minimum-mask keywords are available. You must first enter the flow record type performance-monitor command.
Examples
The following example configures the IPv4 destination address prefix from the flows that have a prefix of 16 bits as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect ipv4 destination prefix minimum-mask 16Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the IPv4 destination address prefix from the flows that have a prefix of 16 bits as a nonkey field:
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect ipv4 destination prefix minimum-mask 16Related Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect ipv4 source
To configure the IPv4 source address as a nonkey field for a flow record, use the collect ipv4 source command in flow record configuration mode. To disable the use of the IPv4 source address field as a nonkey field for a flow record, use the no form of this command.
collect ipv4 source {address | {mask | prefix} [minimum-mask mask]}
no collect ipv4 source {address | {mask | prefix} [minimum-mask mask]}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
collect ipv4 source mask [minimum-mask mask]}
no collect ipv4 source mask [minimum-mask mask]}
Syntax Description
Command Default
The IPv4 source address is not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
Only the mask and minimum-mask keywords are available. You must first enter the flow record type performance-monitor command.
collect ipv4 source prefix minimum-mask
The source address prefix is the network part of an IPv4 source address. The optional minimum mask allows more information to be gathered about large networks.
collect ipv4 source mask minimum-mask
The source address mask is the number of bits that make up the network part of the source address. The optional minimum mask allows a minimum value to be configured. This command is useful when there is a minimum mask configured for the source prefix field and the mask is to be used with the prefix. In this case, the values configured for the minimum mask should be the same for the prefix and mask fields.
Alternatively, if the collector is aware of the minimum mask configuration of the prefix field, the mask field can be configured without a minimum mask so that the true mask and prefix can be calculated.
Examples
The following example configures the IPv4 source address prefix from the flows that have a prefix of 16 bits as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect ipv4 source prefix minimum-mask 16Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the IPv4 source address prefix from the flows that have a prefix of 16 bits as a nonkey field:
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect ipv4 source prefix minimum-mask 16Related Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect ipv4 ttl
To configure the IPv4 time-to-live (TTL) field as a nonkey field for a flow record, use the collect ipv4 ttl command in flow record configuration mode. To disable the use of the IPv4 TTL field as a nonkey field for a flow record, use the no form of this command.
collect ipv4 ttl [maximum | minimum]
no collect ipv4 ttl [maximum | minimum]
Syntax Description
Command Default
The IPv4 time-to-live (TTL) field is not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the flow record type performance-monitor command.
collect ipv4 ttl [minimum | maximum]
This command is used to collect the lowest and highest IPv4 TTL values seen in the lifetime of the flow. Configuring this command results in more processing than is needed to simply collect the first TTL value seen using the collect ipv4 ttl command.
Examples
The following example configures the largest value for IPv4 TTL seen in the flows as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect ipv4 ttl maximumThe following example configures the smallest value for IPv4 TTL seen in the flows as a nonkey field
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect ipv4 ttl minimumCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the smallest value for IPv4 TTL seen in the flows as a nonkey field
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect ipv4 ttl minimumRelated Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect monitor event
To configure the monitor event field as a nonkey field for a flow record, use the collect monitor event command in flow record configuration mode. To disable the use of a monitor event field as a nonkey field for a flow record, use the no form of this command.
collect monitor event
no collect monitor event
Syntax Description
This command has no arguments or keywords.
Command Default
The monitor event field is not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
Monitor events are recorded using two bits. Bit 1 is not used. Bit 2 indicates that no media application packets were seen, in other words, a Media Stop Event occured.
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures the monitor event field as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect monitor eventRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect routing
To configure one or more of the routing attributes as a nonkey field for a flow record, use the collect routing command in flow record configuration mode. To disable the use of one or more of the routing attributes as a nonkey field for a flow record, use the no form of this command.
collect routing {{destination | source} {as [4-octet] [peer [4-octet]] | traffic-index} | forwarding-status | next-hop address {ipv4 | ipv6} [bgp] | vrf input}
no collect routing {{destination | source} {as [4-octet] [peer [4-octet]] | traffic-index} | forwarding-status | next-hop address {ipv4 | ipv6} [bgp] | vrf input}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
collect routing forwarding-status [reason]
no collect routing forwarding-status [reason]
Syntax Description
Command Default
The routing attributes are not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command, however the mode prompt is the same for both products. For Flexible NetFlow, the mode is also known as Flexible NetFlow flow record configuration mode. For Performance Monitor, the mode is also known as Performance Monitor flow record configuration mode. Here we refer to them both as flow record configuration mode.
The Flexible NetFlow and Performance Monitor collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The reason keywordwas added and only the forwarding-status keyword is available. You must first enter the flow record type performance-monitor command.
collect routing source as [peer]
This command collects the 16-bit autonomous system number based on a lookup of the router's routing table using the source IP address. The optional peer keyword provides the expected next network, as opposed to the originating network.
collect routing source as 4-octet [peer 4-octet]
This command collects the 32-bit autonomous system number based on a lookup of the router's routing table using the source IP address. The optional peer keyword provides the expected next network, as opposed to the originating network.
collect routing destination as [peer]
This command collects the 16-bit autonomous system number based on a lookup of the router's routing table using the destination IP address. The optional peer keyword provides the expected next network as opposed to the destination network.
collect routing destination as 4-octet [peer 4-octet]
This command collects the 32-bit autonomous system number based on a lookup of the router's routing table using the destination IP address. The peer keyword will provide the expected next network as opposed to the destination network.
collect routing destination traffic-index
This command collects the traffic-index field based on the destination autonomous system for this flow. The traffic-index field is a value propagated through BGP.
This command is not supported for IPv6.
collect routing source traffic-index
This command collects the traffic-index field based on the source autonomous system for this flow. The traffic-index field is a value propagated through BGP.
This command is not supported for IPv6.
collect routing forwarding-status
This command collects a field to indicate if the packets were successfully forwarded. The field is in two parts and may be up to 4 bytes in length. For the releases specified in the Command History table, only the status field is used:
+-+-+-+-+-+-+-+-+| S | Reason || t | codes || a | or || t | flags || u | || s | |+-+-+-+-+-+-+-+-+0 1 2 3 4 5 6 7Status:00b=Unknown, 01b = Forwarded, 10b = Dropped, 11b = Consumedcollect routing vrf input
This command collects the VRF ID from incoming packets on a router. In the case where VRFs are associated with an interface via methods such as VRF Selection Using Policy Based Routing/Source IP Address, a VRF ID of 0 will be recorded. If a packet arrives on an interface that does not belong to a VRF, a VRF ID of 0 is recorded.
Examples
The following example configures the 16-bit autonomous system number based on a lookup of the router's routing table using the source IP address as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect routing source asThe following example configures the 16-bit autonomous system number based on a lookup of the router's routing table using the destination IP address as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect routing destination asThe following example configures the value in the traffic-index field based on the source autonomous system for a flow as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect routing source traffic-indexThe following example configures the forwarding status as a nonkey field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect routing forwarding-statusThe following example configures the VRF ID for incoming packets as a nonkey field for a Flexible NetFlow flow record:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# collect routing vrf inputCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the forwarding status as a nonkey field for a Performance Monitor flow record:
Router(config)# flow record type performance-monitor RECORD-1Router(config-flow-record)# collect routing forwarding-status reasonRelated Commands
flow record
Creates a flow record, and enters Flexible NetFlow flow record configuration mode.
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect timestamp interval
To configure the start time of the monitoring interval as a nonkey field for a flow record, use the collect timestamp interval command in flow record configuration mode. To disable the use of the start time of the monitoring interval as a nonkey field for a flow record, use the no form of this command.
collect timestamp interval
no collect timestamp interval
Syntax Description
This command has no arguments or keywords.
Command Default
The start time of the monitoring interval is not configured as a nonkey field.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures the start time of the monitoring interval as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect timestamp intervalRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect transport event packet-loss counter
To configure the event packet-loss counter field as a nonkey field for a flow record, use the collect transport event packet-loss counter command in flow record configuration mode. To disable the use of the event packet-loss counter field as a nonkey field for a flow record, use the no form of this command.
collect transport event packet-loss counter
no collect transport event packet-loss counter
Syntax Description
This command has no arguments or keywords.
Command Default
The event packet-loss counter field is not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The event packet-loss counter is incremented when a lost RTP packet is detected. However, the counter is also incremented when a reorder occurs, in other words, when packets are received out of order.
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures event packet-loss counter field as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect transport event packet-loss counterRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect transport packets
To configure various packet fields as a nonkey field for a flow record, use the collect transport packets command in flow record configuration mode. To disable the use of a packet field as a nonkey field for a flow record, use the no form of this command.
collect transport packets{lost counter | lost rate | expected counter | round-trip-time}
no collect transport packets {lost counter | lost rate | expected counter | round-trip-time}
Syntax Description
Command Default
The packet fields are not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You can retrieve different transport packet counters for RTP and TCP. The following transport packet counters as available:
•
•
•
•
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures the field that counts the number of lost packets as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect transport packets lost counterRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
collect transport rtp jitter
To configure one of the RTP jitter fields as a nonkey field for a flow record, use the collect transport rtp jitter command in flow record configuration mode. To disable the use of a jitter field as a nonkey field for a flow record, use the no form of this command.
collect transport rtp jitter {mean | maximum | minimum}
no collect transport rtp jitter {mean | maximum | minimum}
Syntax Description
Command Default
The RTP jitter field is not configured as a nonkey field for a user-defined flow record.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The collect commands are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases the values for nonkey fields are taken from only the first packet in the flow.
Examples
The following example configures the RTP jitter field as a nonkey field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# collect transport rtp jitterRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
debug performance monitor
To enable debugging for performance monitor, use the debug performance monitor command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug performance monitor {database | dynamic | event | export | flow-monitor | metering | provision | sibling | snmp | tca | timer}
no debug performance monitor {database | dynamic | event | export | flow-monitor | metering | provision | sibling | snmp | tca | timer}
Syntax Description
Command Default
Debugging for performance monitor is disabled.
Command Modes
Privileged EXEC
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to enable debugging for dynamic monitoring:
Router# debug performance monitor dynamicRelated Commands
flow exporter
Creates a flow exporter.
flow monitor type performance-monitor
Creates a flow monitor.
description (Performance Monitor)
To configure a description for a flow exporter, flow record, flow monitor, or policy map use the description command in the appropriate configuration mode. To remove the description, use the no form of this command.
description description
no description
Syntax Description
Command Default
No description is configured.
Command Modes
Flow exporter configuration (config-flow-exporter)
Flow record configuration (config-flow-record)
Flow monitor configuration (config-flow-monitor)
Policy configuration (config-pmap)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember information about the flow exporter, flow record, flow monitor, or policy map, such as which packets are included within the policy map.
Examples
The following example shows how to configuration a description for a flow record:
Router(config)# flow record type performance-monitorRouter(config-flow-record)# description collect the number of IPV4 packet droppedRouter(config-flow-record)# match ipv4 protocolRouter(config-flow-record)# collect counter packets droppedRelated Commands
destination
To configure an export destination for a flow exporter, use the destination command in flow exporter configuration mode. To remove an export destination for a flow exporter, use the no form of this command.
destination {{ip-address | hostname} | vrf vrf-name}
no destination
Syntax Description
Command Default
An export destination is not configured.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
Each flow exporter can have only one destination address or hostname.
When you configure a hostname instead of the IP address for the device, the hostname is resolved immediately and the IP address is stored in the running configuration. If the hostname-to-IP-address mapping that was used for the original domain name system (DNS) name resolution changes dynamically on the DNS server, the router does not detect this, and the exported data continues to be sent to the original IP address, resulting in a loss of data. Resolving the hostname immediately is a prerequisite of the export protocol, to ensure that the templates and options arrive before the data
Examples
The following example shows how to configure the networking device to export the Flexible NetFlow cache entry to a destination system:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# destination 10.0.0.4The following example shows how to configure the networking device to export the Flexible NetFlow cache entry to a destination system using a VRF named VRF-1:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# destination 172.16.10.2 vrf VRF-1Related Commands
dscp (Flexible NetFlow)
To configure a differentiated services code point (DSCP) value for flow exporter datagrams, use the dscp command in flow exporter configuration mode. To remove a DSCP value for flow exporter datagrams, use the no form of this command.
dscp dscp
no dscp
Syntax Description
Command Default
The differentiated services code point (DSCP) value is 0.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Examples
The following example sets 22 as the value of the DSCP field in exported datagrams:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# dscp 22Related Commands
export-protocol
To configure the export protocol for a flow exporter, use the export-protocol command in flow exporter configuration mode. To restore the use of the default export protocol for a flow exporter, use the no form of this command.
export-protocol {netflow-v5 | netflow-v9}
no export-protocol
Syntax Description
netflow-v5
Configures NetFlow Version 5 export as the export protocol.
netflow-v9
Configures NetFlow Version 9 export as the export protocol.
Command Default
NetFlow Version 9 export is used as the export protocol for a flow exporter.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
The NetFlow Version 5 export protocol is supported only for flow monitors that use the Flexible NetFlow predefined records.
Examples
The following example configures NetFlow Version 5 export as the export protocol for a Flexible NetFlow or Performance Monitor flow exporter:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# export-protocol netflow-v5Related Commands
exporter
To configure a flow exporter for a flow monitor, use the exporter command in the appropriate configuration mode. To remove a flow exporter for a flow monitor, use the no form of this command.
exporter exporter-name
no exporter exporter-name
Syntax Description
Command Default
An exporter is not configured.
Command Modes
flow monitor configuration (config-flow-monitor)
Policy configuration (config-pmap-c)
Policy monitor configuration (config-pmap-c-flowmon)Command History
Usage Guidelines
You must have already created a flow exporter by using the flow exporter command before you can apply the flow exporter to a flow monitor with the exporter command.
For Performance Monitor, you can associate a flow exporter with a flow monitor while configuring either a flow monitor, policy map, or service policy.
Examples
The following example configures an exporter for a flow monitor:
Router(config)# flow monitor FLOW-MONITOR-1Router(config-flow-monitor)# exporter EXPORTER-1The following example shows one of the ways to configure a flow exporter for Performance Monitor:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class class-4Router(config-pmap-c)# flow monitor monitor-4Router(config-pmap-c-flowmon)# exporter exporter-4Related Commands
flow monitor type performance-monitor
To configure a flow monitor for Performance Monitor, use the flow monitor type performance-monitor command in global configuration mode. To remove flow monitor, use the no form of this command.
flow monitor type performance-monitor monitor-name
no flow monitor type performance-monitor monitor-name
Syntax Description
Command Modes
Global configuration (config)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
.Before you configure flow monitor, you should first configure a flow record and an optional flow exporter.
Examples
The following example shows how to configure a flow monitor:
Router(config)# flow monitor type performance-monitor PM-MONITOR-4Related Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
flow record type performance-monitor
To configure a flow record for Performance Monitor, use the flow record type performance-monitor command in global configuration mode. To remove the flow record, use the no form of this command.
flow record type performance-monitor record-name
no flow record type performance-monitor record-name
Syntax Description
Command Modes
Global configuration (config)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the collect command.
Examples
The following example shows how to configure a flow record:
Router(config)# flow record type performance-monitor PM-RECORD-4Related Commands
flows
To configure the maximum number of flows for each Performance Monitor cache, use the flows command in monitor parameters configuration mode. To remove the configuration, use the no form of this command.
flows number
no flows number
Syntax Description
Command Default
Number of flows to collect is 8000.
Command Modes
Monitor parameters configuration (config-pmap-c-mparam)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the number of flows to collect for a Performance Monitor policy to four:
Router(config)# policy-map type performance-monitor PM-POLICY-4Router(config-pamp)# class class-6Router(config-pmap-c)# monitor parametersRouter(config-pmap-c-mparam)# flows 4Related Commands
history (monitor parameters)
To configure the number of historical collections to keep for a Performance Monitor policy, use the history command in monitor parameters configuration mode. To remove the configuration, use the no form of this command.
history number
no history
Syntax Description
Command Default
Number of historical collections to keep is 10.
Command Modes
Monitor parameters configuration (config-pmap-c-mparam)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the number of historical collections to keep for a Performance Monitor policy to four:
Router(config)# policy-map type performance-monitor PM-POLICY-4Router(config-pamp)# class class-6Router(config-pmap-c)# monitor parametersRouter(config-pmap-c-mparam)# history 4Related Commands
interval duration
To configure the duration of the collection interval for a Performance Monitor policy, use the interval duration command in monitor parameters configuration mode. To remove the configuration, use the no form of this command.
interval duration duration
no interval duration
Syntax Description
Command Default
Duration of the collection interval is 30 seconds.
Command Modes
Monitor parameters configuration (config-pmap-c-mparam)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the collection interval for a Performance Monitor policy to twenty:
Router(config)# policy-map type performance-monitor PM-POLICY-4Router(config-pamp)# class class-6Router(config-pmap-c)# monitor parametersRouter(config-pmap-c-mparam)# interval duration 20Related Commands
match access-group
To configure the match criteria for a class map on the basis of the specified access control list (ACL), use the match access-group command in class-map configuration or policy inline configuration mode. To remove ACL match criteria from a class map, use the no form of this command.
match access-group {access-group | name access-group-name}
no match access-group access-group
Syntax Description
Command Default
No match criteria are configured.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including ACLs, protocols, input interfaces, quality of service (QoS) labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
Note
The match access-group command specifies a numbered or named ACL whose contents are used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
When packets are matched to an access group, a traffic rate is generated for these packets. In a zone-based firewall policy, only the first packet that creates a session matches the policy. Subsequent packets in this flow do not match the filters in the configured policy, but instead match the session directly. The statistics related to subsequent packets are shown as part of the inspect action.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Supported Platforms Other than Cisco 10000 Series Routers
To use the match access-group command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
•
Note
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Note
Cisco 10000 Series Routers
To use the match access-group command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish.
Note
Examples
The following example specifies a class map named acl144 and configures the ACL numbered 144 to be used as the match criterion for that class:
Router(config)# class-map acl144Router(config-cmap)# match access-group 144The following example pertains to Zone-Based Policy Firewall. The example defines a class map named c1 and configures the ACL numbered 144 to be used as the match criterion for that class.Router(config)# class-map type inspect match-all c1Router(config-cmap)# match access-group 144Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria specified the ACL numbered 144 will be monitored based on the parameters specified in the flow monitor configuration named fm-2
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-cmap)# match access-group 144Related Commands
match any
To configure the match criteria for a class map to be successful match criteria for all packets, use the match any command in class-map configuration or policy inline configuration mode. To remove all criteria as successful match criteria, use the no form of this command.
match any
no match any
Syntax Description
This command has no arguments or keywords.
Command Default
No match criteria are specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
In the following configuration, all packets traversing Ethernet interface 1/1 will be policed based on the parameters specified in policy-map class configuration mode:
Router(config)# class-map matchanyRouter(config-cmap)# match anyRouter(config-cmap)# exitRouter(config)# policy-map policy1Router(config-pmap)# class class4Router(config-pmap-c)# police 8100 1500 2504 conform-action transmit exceed-action set-qos-transmit 4Router(config-pmap-c)# exitRouter(config)# interface ethernet1/1Router(config-if)# service-policy output policy1Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that all packets traversing Ethernet interface 0/0 will be matched and monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match anyRouter(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match cos
To match a packet on the basis of a Layer 2 class of service (CoS)/Inter-Switch Link (ISL) marking, use the match cos command in class-map configuration or policy inline configuration mode. To remove a specific Layer 2 CoS/ISL marking as a match criterion, use the no form of this command.
match cos cos-value [cos-value [cos-value [cos-value]]]
no match cos cos-value [cos-value [cos-value [cos-value]]]
Syntax Description
Command Default
Packets are not matched on the basis of a Layer 2 CoS/ISL marking.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
In the following example, the CoS values of 1, 2, and 3 are successful match criteria for the interface that contains the classification policy named cos:
Router(config)# class-map cosRouter(config-cmap)# match cos 1 2 3In the following example, classes named voice and video-n-data are created to classify traffic based on the CoS values. QoS treatment is then given to the appropriate packets in the CoS-based-treatment policy map (in this case, the QoS treatment is priority 64 and bandwidth 512). The service policy configured in this example is attached to all packets leaving Fast Ethernet interface 0/0.1. The service policy can be attached to any interface that supports service policies.
Router(config)# class-map voiceRouter(config-cmap)# match cos 7Router(config)# class-map video-n-dataRouter(config-cmap)# match cos 5Router(config)# policy-map cos-based-treatmentRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority 64Router(config-pmap-c)# exitRouter(config-pmap)# class video-n-dataRouter(config-pmap-c)# bandwidth 512Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet0/0.1Router(config-if)# service-policy output cos-based-treatmentCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a CoS value of 2 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match cos 2Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match destination-address mac
To use the destination MAC address as a match criterion, use the match destination-address mac command in class-map configuration or policy inline configuration mode. To remove a previously specified destination MAC address as a match criterion, use the no form of this command.
match destination-address mac address
no match destination-address mac address
Syntax Description
Command Default
No destination MAC address is specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example specifies a class map named macaddress and specifies the destination MAC address to be used as the match criterion for this class:
Router(config)# class-map macaddressRouter(config-cmap)# match destination-address mac 00:00:00:00:00:00Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the specified destination MAC address will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match destination-address mac 00:00:00:00:00:00Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match discard-class
To specify a discard class as a match criterion, use the match discard-class command in class-map configuration or policy inline configuration mode. To remove a previously specified discard class as a match criterion, use the no form of this command.
match discard-class class-number
no match discard-class class-number
Syntax Description
Command Default
Packets will not be classified as expected.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
A discard-class value has no mathematical significance. For example, the discard-class value 2 is not greater than 1. The value simply indicates that a packet marked with discard-class 2 should be treated differently than a packet marked with discard-class 1.
Packets that match the specified discard-class value are treated differently from packets marked with other discard-class values. The discard-class is a matching criterion only, used in defining per hop behavior (PHB) for dropping traffic.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example shows that packets in discard class 2 are matched:
Router(config)# class-map d-class-2Router(config-cmap)# match discard-class 2Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria specified by discard-class 2 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match discard-class 2Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match dscp
To identify one or more differentiated service code point (DSCP), Assured Forwarding (AF), and Certificate Server (CS) values as a match criterion, use the match dscp command in class-map configuration or policy inline configuration mode. To remove a specific DSCP value from a class map, use the no form of this command.
match [ip] dscp dscp-value [dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value]
no match [ip] dscp dscp-value
Syntax Description
Command Default
No match criteria are configured.
If you do not enter the ip keyword, matching occurs on both IPv4 and IPv6 packets.Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
DSCP Values
You must enter one or more differentiated service code point (DSCP) values. The command may include any combination of the following:
•
•
•
•
•
For example, if you wanted the DCSP values of 0, 1, 2, 3, 4, 5, 6, or 7 (note that only one of the IP DSCP values must be a successful match criterion, not all of the specified DSCP values), enter the match dscp 0 1 2 3 4 5 6 7 command.
This command is used by the class map to identify a specific DSCP value marking on a packet. In this context, dscp-value arguments are used as markings only and have no mathematical significance. For instance, the dscp-value of 2 is not greater than 1. The value simply indicates that a packet marked with the dscp-value of 2 is different than a packet marked with the dscp-value of 1. The treatment of these marked packets is defined by the user through the setting of Quality of Service (QoS) policies in policy-map class configuration mode.
Match Packets on DSCP Values
To match DSCP values for IPv6 packets only, the match protocol ipv6 command must also be used. Without that command, the DSCP match defaults to match both IPv4 and IPv6 packets.
To match DSCP values for IPv4 packets only, use the ip keyword. Without the ip keyword the match occurs on both IPv4 and IPv6 packets. Alternatively, the match protocol ip command may be used with match dscp to classify only IPv4 packets.
After the DSCP bit is set, other QoS features can then operate on the bit settings.
The network can give priority (or some type of expedited handling) to marked traffic. Typically, you set the precedence value at the edge of the network (or administrative domain); data is then queued according to the precedence. Weighted fair queueing (WFQ) can speed up handling for high-precedence traffic at congestion points. Weighted Random Early Detection (WRED) can ensure that high-precedence traffic has lower loss rates than other traffic during times of congestion.
Cisco 10000 Series Routers
The Cisco 10000 series routers support DSCP matching of IPv4 packets only. You must include the ip keyword when specifying the DSCP values to use as match criterion.
You cannot use the set ip dscp command with the set ip precedence command to mark the same packet. DSCP and precedence values are mutually exclusive. A packet can have one value or the other, but not both.
Examples
The following example shows how to set multiple match criteria. In this case, two IP DSCP value and one AF value.
Router(config)# class-map map1Router(config-cmap)# match dscp 1 2 af11Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria specified by DSCP value 2 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match dscp 2Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match flow
To configure the flow direction and the flow sampler ID number as key fields for a flow record, use the match flow command in flow record configuration or policy inline configuration mode. To disable the use of the flow direction and the flow sampler ID number as key fields for a flow record, use the no form of this command.
match flow {direction | sampler}
no match flow {direction | sampler}
Syntax Description
direction
Configures the direction in which the flow was monitored as a key field.
sampler
Configures the flow sampler ID as a key field.
Command Default
The use of the flow direction and the flow sampler ID number as key fields for a user-defined flow record is not enabled by default.
Command Modes
flow record configuration (config-flow-record)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
match flow direction
This field indicates the direction of the flow. This is of most use when a single flow monitor is configured for input and output flows. It can be used to find and eliminate flows that are being monitored twice, once on input and once on output. This field may also be used to match up pairs of flows in the exported data when the two flows are flowing in opposite directions.
match flow sampler
This field contains the ID of the flow sampler used to monitor the flow. This is useful when more than one flow sampler is being used with different sampling rates. The flow exporter option sampler-table command will export options records with mappings of the flow sampler ID to the sampling rate so the collector can calculate the scaled counters for each flow.
Examples
The following example configures the direction the flow was monitored in as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match flow directionThe following example configures the flow sampler ID as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match flow samplerCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the flow sampler ID will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match flow samplerRouter(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match fr-de
To match packets on the basis of the Frame Relay discard eligibility (DE) bit setting, use the match fr-de command in class-map configuration or policy inline configuration mode. To remove the match criteria, use the no form of this command.
match fr-de
no match fr-de
Syntax Description
This command has no arguments or keywords.
Command Default
Packets are not matched on the basis of the Frame Relay DE bit setting.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example creates a class named match-fr-de and matches packets on the basis of the Frame Relay DE bit setting.
Router(config)# class-map match-fr-deRouter(config-cmap)# match fr-deCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the Frame Relay DE bit setting will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match fr-deRouter(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match fr-dlci
To specify the Frame Relay data-link connection identifier (DLCI) number as a match criterion in a class map, use the match fr-dlci command in class-map configuration or policy inline configuration mode. To remove a previously specified DLCI number as a match criterion, use the no form of this command.
match fr-dlci dlci-number
no match fr-dlci dlci-number
Syntax Description
Command Default
No DLCI number is specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
This match criterion can be used in main interfaces and point-to-multipoint subinterfaces in Frame Relay networks, and it can also be used in hierarchical policy maps.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
In the following example a class map named "class1" has been created and the Frame Relay DLCI number of 500 has been specified as a match criterion. Packets matching this criterion are placed in class1.
Router(config)# class-map class1Router(config-cmap)# match fr-dlci 500Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the Frame Relay DLCI number of 500 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match fr-dlci 500Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match input-interface
To configure a class map to use the specified input interface as a match criterion, use the match input-interface command in class-map configuration or policy inline configuration mode. To remove the input interface match criterion from a class map, use the no form of this command.
match input-interface interface-name
no match input-interface interface-name
Syntax Description
Command Default
No match criteria are specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Supported Platforms Other Than Cisco 10000 Series Routers
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including input interfaces, access control lists (ACLs), protocols, quality of service (QoS) labels, and experimental (EXP) field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match input-interface command specifies the name of an input interface to be used as the match criterion against which packets are checked to determine if they belong to the class specified by the class map.
To use the match input-interface command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Cisco 10000 Series Routers
For CBWFQ, you define traffic classes based on match criteria including input interfaces, ACLs, protocols, QoS labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
To use the match input-interface command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish.
Examples
The following example specifies a class map named ethernet1 and configures the input interface named ethernet1 to be used as the match criterion for this class:
Router(config)# class-map ethernet1Router(config-cmap)# match input-interface ethernet1Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of the input interface named ethernet1 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match input-interface ethernet 1Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match ip dscp
The match ip dscp command is replaced by the match dscp command. See the match dscp command for more information.
match ip precedence
The match ip precedence command is replaced by the match precedence command. See the match precedence command for more information.
match ip rtp
To configure a class map to use the Real-Time Protocol (RTP) port as the match criterion, use the match ip rtp command in class-map configuration or policy inline configuration mode. To remove the RTP port match criterion, use the no form of this command.
match ip rtp starting-port-number port-range
no match ip rtp
Syntax Description
starting-port-number
The starting RTP port number. Values range from 2000 to 65535.
port-range
The RTP port number range. Values range from 0 to 16383.
Command Default
No match criteria are specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
This command is used to match IP RTP packets that fall within the specified port range. It matches packets destined to all even User Datagram Port (UDP) port numbers in the range from the starting port number argument to the starting port number plus the port range argument.
Use of an RTP port range as the match criterion is particularly effective for applications that use RTP, such as voice or video.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example specifies a class map named ethernet1 and configures the RTP port number 2024 and range 1000 to be used as the match criteria for this class:
Router(config)# class-map ethernet1Router(config-cmap)# match ip rtp 2024 1000Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of RTP port number 2024 and range 1000 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match ip rtp 2024 1000Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match ipv4
To configure one or more of the IPv4 fields as a key field for a flow record, use the match ipv4 command in flow record configuration mode. To disable the use of one or more of the IPv4 fields as a key field for a flow record, use the no form of this command.
match ipv4 {dscp | header-length | id | option map | precedence | protocol | tos | version}
no match ipv4 {dscp | header-length | id | option map | precedence | protocol | tos | version}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
match ipv4 protocol
no match ipv4 protocol
Syntax Description
Command Default
The use of one or more of the IPv4 fields as a key field for a user-defined flow record is not enabled by default.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Note
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
Only the protocol keyword is available. You must first enter the flow record type performance-monitor command.
Examples
The following example configures the IPv4 DSCP field as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match ipv4 dscpCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example configures the IPv4 DSCP field as a key field for Cisco Performance Monitor:
Router(config)# flow record type performance-monitor FLOW-RECORD-1Router(config-flow-record)# match ipv4 dscpRelated Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Cisco Performance Monitor.
match ipv4 destination
To configure the IPv4 destination address as a key field for a flow record, use the match ipv4 destination command in flow record configuration mode. To disable the IPv4 destination address as a key field for a flow record, use the no form of this command.
match ipv4 destination {address | {{mask | prefix} [minimum-mask mask]}
no match ipv4 destination {address | {{mask | prefix} [minimum-mask mask]}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
match ipv4 destination {address | prefix [minimum-mask mask]}
no match ipv4 destination {address | prefix [minimum-mask mask]}
Syntax Description
Command Default
The IPv4 destination address is not configured as a key field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The mask keyword is not available. You must first enter the flow record type performance-monitor command.
Examples
The following example configures a 16-bit IPv4 destination address prefix as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match ipv4 destination prefix minimum-mask 16The following example specifies a 16-bit IPv4 destination address mask as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match ipv4 destination mask minimum-mask 16Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example specifies a 16-bit IPv4 destination address mask as a key field for Cisco Performance Monitor:
Router(config)# flow record type performance-monitor FLOW-RECORD-1Router(config-flow-record)# match ipv4 destination mask minimum-mask 16Related Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Cisco Performance Monitor.
match ipv4 source
To configure the IPv4 source address as a key field for a flow record, use the match ipv4 source command in flow record configuration mode. To disable the use of the IPv4 source address as a key field for a flow record, use the no form of this command.
match ipv4 source {address | {{mask | prefix} [minimum-mask mask]}
no match ipv4 source {address | {{mask | prefix} [minimum-mask mask]}
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
match ipv4 source {address | prefix [minimum-mask mask]}
no match ipv4 source {address | prefix [minimum-mask mask]}
Syntax Description
Command Default
The IPv4 source address is not configured as a key field.
Command Modes
flow record configuration (config-flow-record)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The mask keyword is not available. You must first enter the flow record type performance-monitor command.
match ipv4 source prefix minimum-mask
The source address prefix field is the network part of the source address. The optional minimum mask allows a more information to be gathered about large networks.
match ipv4 source mask minimum-mask
The source address mask is the number of bits that make up the network part of the source address. The optional minimum mask allows a minimum value to be configured. This command is useful when there is a minimum mask configured for the source prefix field and the mask is to be used with the prefix. In this case, the values configured for the minimum mask should be the same for the prefix and mask fields.
Alternatively, if the collector knows the minimum mask configuration of the prefix field, the mask field can be configured without a minimum mask so that the true mask and prefix can be calculated.
Examples
The following example configures a 16-bit IPv4 source address prefix as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match ipv4 source prefix minimum-mask 16The following example specifies a 16-bit IPv4 source address mask as a key field:
Router(config)# flow record FLOW-RECORD-1Router(config-flow-record)# match ipv4 source mask minimum-mask 16Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example specifies a 16-bit IPv4 source address mask as a key field for Cisco Performance Monitor:
Router(config)# flow record type performance-monitor FLOW-RECORD-1Router(config-flow-record)# match ipv4 source mask minimum-mask 16Related Commands
flow record
Creates a flow record for Flexible NetFlow.
flow record type performance-monitor
Creates a flow record for Cisco Performance Monitor.
match mpls experimental topmost
To match the experimental (EXP) value in the topmost label header, use the match mpls experimental topmost command in class-map configuration or policy inline configuration mode. To remove the EXP match criterion, use the no form of this command.
match mpls experimental topmost number
no match mpls experimental topmost number
Syntax Description
number
Multiprotocol Label Switching (MPLS) EXP field in the topmost label header. Valid values are 0 to 7.
Command Default
No EXP match criterion is configured for the topmost label header.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
You can enter this command on the input interfaces and the output interfaces. It will match only on MPLS packets.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example shows that the EXP value 3 in the topmost label header is matched:
Router(config)# class-map mpls expRouter(config-cmap)# match mpls experimental topmost 3Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a EXP value of 3 in the topmost label header will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match mpls experimental topmost 3Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match not
To specify the single match criterion value to use as an unsuccessful match criterion, use the match not command in class-map configuration or policy inline configuration mode. To remove a previously specified source value to not use as a match criterion, use the no form of this command.
match not match-criterion
no match not match-criterion
Syntax Description
match-criterion
The match criterion value that is an unsuccessful match criterion. All other values of the specified match criterion will be considered successful match criteria.
Command Default
No unsuccessful match criterion is configured.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
The match not command is used to specify a quality of service (QoS) policy value that is not used as a match criterion. When the match not command is used, all other values of that QoS policy become successful match criteria.
For instance, if the match not qos-group 4 command is issued in QoS class-map configuration mode, the specified class will accept all QoS group values except 4 as successful match criteria.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
In the following traffic class, all protocols except IP are considered successful match criteria:
Router(config)# class-map noipRouter(config-cmap)# match not protocol ipCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 for all protocols except IP will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match not protocol ipRouter(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match packet length (class-map)
To specify the Layer 3 packet length in the IP header as a match criterion in a class map, use the match packet length command in class-map configuration or policy inline configuration mode. To remove a previously specified Layer 3 packet length as a match criterion, use the no form of this command.
match packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]}
no match packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]}
Syntax Description
Command Default
The Layer 3 packet length in the IP header is not used as a match criterion.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
This command considers only the Layer 3 packet length in the IP header. It does not consider the Layer 2 packet length in the IP header.
When using this command, you must at least specify the maximum or minimum value. However, you do have the option of entering both values.
If only the minimum value is specified, a packet with a Layer 3 length greater than the minimum is viewed as matching the criterion.
If only the maximum value is specified, a packet with a Layer 3 length less than the maximum is viewed as matching the criterion.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
In the following example a class map named "class 1" has been created, and the Layer 3 packet length has been specified as a match criterion. In this example, packets with a minimum Layer 3 packet length of 100 bytes and a maximum Layer 3 packet length of 300 bytes are viewed as meeting the match criteria.
Router(config)# class-map match-all class1Router(config-cmap)# match packet length min 100 max 300Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a minimum Layer 3 packet length of 100 bytes and a maximum Layer 3 packet length of 300 bytes will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match packet length min 100 max 300Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match precedence
To identify IP precedence values to use as the match criterion, use the match precedence command in class-map configuration or policy inline configuration mode. To remove IP precedence values from a class map, use the no form of this command.
match [ip] precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4}
no match [ip] precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4}
Syntax Description
Command Default
No match criterion is configured.
If you do not enter the ip keyword, matching occurs on both IPv4 and IPv6 packets.Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
You can enter up to four matching criteria, as number abbreviation (0 to 7) or criteria names (critical, flash, and so on), in a single match statement. For example, if you wanted the precedence values of 0, 1, 2, or 3 (note that only one of the precedence values must be a successful match criterion, not all of the specified precedence values), enter the match ip precedence 0 1 2 3 command. The precedence-criteria numbers are not mathematically significant; that is, the precedence-criteria of 2 is not greater than 1. The way that these different packets are treated depends upon quality of service (QoS) policies, set in the policy-map configuration mode.
You can configure a QoS policy to include IP precedence marking for packets entering the network. Devices within your network can then use the newly marked IP precedence values to determine how to treat the packets. For example, class-based weighted random early detection (WRED) uses IP precedence values to determine the probability that a packet is dropped. You can also mark voice packets with a particular precedence. You can then configure low-latency queueing (LLQ) to place all packets of that precedence into the priority queue.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Matching Precedence for IPv6 and IPv4 Packets on the Cisco 10000 and 7600 Series Routers
On the Cisco 7600 series and 10000 series routers, you set matching criteria based on precedence values for only IPv6 packets using the match protocol command with the ipv6 keyword. Without that keyword, the precedence match defaults to match both IPv4 and IPv6 packets. You set matching criteria based on precedence values for IPv4 packets only, use the ip keyword. Without the ip keyword the match occurs on both IPv4 and IPv6 packets.
Precedence Values and Names
The following table lists all criteria conditions by value, name, binary value, and recommended use. You may enter up to four criteria, each separated by a space. Only one of the precedence values must be a successful match criterion. Table 9 lists the IP precedence values.
Do not use IP precedence 6 or 7 to mark packets, unless you are marking control packets.
Examples
IPv4-Specific Traffic Match
The following example shows how to configure the service policy named priority50 and attach service policy priority50 to an interface, matching for IPv4 traffic only. In a network where both IPv4 and IPv6 are running, you might find it necessary to distinguish between the protocols for matching and traffic segregation. In this example, the class map named ipprec5 will evaluate all IPv4 packets entering Fast Ethernet interface 1/0/0 for a precedence value of 5. If the incoming IPv4 packet has been marked with the precedence value of 5, the packet will be treated as priority traffic and will be allocated with bandwidth of 50 kbps.
Router(config)# class-map ipprec5Router(config-cmap)# match ip precedence 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class ipprec5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fa1/0/0Router(config-if)# service-policy input priority50IPv6-Specific Traffic Match
The following example shows the same service policy matching on precedence for IPv6 traffic only. Notice that the match protocol command with the ipv6 keyword precedes the match precedence command. The match protocol command is required to perform matches on IPv6 traffic alone.
Router(config)# class-map ipprec5Router(config-cmap)# match protocol ipv6Router(config-cmap)# match precedence 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class ipprec5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fa1/0/0Router(config-if)# service-policy input priority50Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a match precedence of 4 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match precedence 4Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match protocol
To configure the match criterion for a class map on the basis of a specified protocol, use the match protocol command in class-map configuration or policy inline configuration mode. To remove the protocol-based match criterion from the class map, use the no form of this command.
match protocol protocol-name
no match protocol protocol-name
Syntax Description
protocol-name
Name of the protocol (for example, bgp) used as a matching criterion. See the "Usage Guidelines" for a list of protocols supported by most routers.
Command Default
No match criterion is configured.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Supported Platforms Other Than Cisco 7600 Routers and Cisco 10000 Series Routers
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria protocols, access control lists (ACLs), input interfaces, quality of service (QoS) labels, and Experimental (EXP) field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
The match protocol ipx command matches packets in the output direction only.
To use the match protocol command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
To configure NBAR to match protocol types that are supported by NBAR traffic, use the match protocol (NBAR) command.
Cisco 7600 Series Routers
The match protocol command in QoS class-map configuration configures NBAR and sends all traffic on the port, both ingress and egress, to be processed in the software on the Multilayer Switch Feature Card 2 (MSFC2).
For CBWFQ, you define traffic classes based on match criteria like protocols, ACLs, input interfaces, QoS labels, and Multiprotocol Label Switching (MPLS) EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
If you want to use the match protocol command, you must first enter the class-map command to specify the name of the class to which you want to establish the match criteria.
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
This command can be used to match protocols that are known to the NBAR feature. For a list of protocols supported by NBAR, see the "Classification" part of the Cisco IOS Quality of Service Solutions Configuration Guide.
Cisco 10000 Series Routers
For CBWFQ, you define traffic classes based on match criteria including protocols, ACLs, input interfaces, QoS labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
The match protocol ipx command matches packets in the output direction only.
To use the match protocol command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish.
If you are matching NBAR protocols, use the match protocol (NBAR) command.
Match Protocol Command Restrictions (Catalyst 6500 Series Switches Only)
Policy maps contain traffic classes. Traffic classes contain one or more match commands that can be used to match packets (and organize them into groups) on the basis of a protocol type or application. You can create as many traffic classes as needed.
Cisco IOS Release 12.2(18)ZY includes software intended for use on the Catalyst 6500 series switch that is equipped with a Supervisor 32/PISA engine. For this release and platform, note the following restrictions for using policy maps and match protocol commands:
•
•
Supported Protocols
Table 10 lists the protocols supported by most routers. Some routers support a few additional protocols. For example, the Cisco 7600 router supports the AARP and DECnet protocols, while the Cisco 7200 router supports the directconnect and PPPOE protocols. For a complete list of supported protocols, see the online help for the match protocol command on the router that you are using.
* This protocol is not supported on the Catalyst 6500 series switch that is equipped with a Supervisor 32/PISA engine.Examples
The following example specifies a class map named ftp and configures the FTP protocol as a match criterion:
Router(config)# class-map ftpRouter(config-cmap)# match protocol ftpCisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 for the IP protocol will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match protocol ipRouter(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match qos-group
To identify a specific quality of service (QoS) group value as a match criterion, use the match qos-group command in class-map configuration or policy inline configuration mode. To remove a specific QoS group value from a class map, use the no form of this command.
match qos-group qos-group-value
no match qos-group qos-group-value
Syntax Description
Command Default
No match criterion is specified.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
The match qos-group command is used by the class map to identify a specific QoS group value marking on a packet. This command can also be used to convey the received Multiprotocol Label Switching (MPLS) experimental (EXP) field value to the output interface.
The qos-group-value argument is used as a marking only. The QoS group values have no mathematical significance. For instance, the qos-group-value of 2 is not greater than 1. The value simply indicates that a packet marked with the qos-group-value of 2 is different than a packet marked with the qos-group-value of 1. The treatment of these packets is defined by the user through the setting of QoS policies in QoS policy-map class configuration mode.
The QoS group value is local to the router, meaning that the QoS group value that is marked on a packet does not leave the router when the packet leaves the router. If you need a marking that resides in the packet, use IP precedence setting, IP differentiated services code point (DSCP) setting, or another method of packet marking.
This command can be used with the random-detect discard-class-based command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example shows how to configure the service policy named priority50 and attach service policy priority50 to an interface. In this example, the class map named qosgroup5 will evaluate all packets entering Fast Ethernet interface 1/0/0 for a QoS group value of 5. If the incoming packet has been marked with the QoS group value of 5, the packet will be treated with a priority level of 50.
Router(config)# class-map qosgroup5Router(config-cmap)# match qos-group 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class qosgroup5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet1/0/0Router(config-if)# service-policy output priority50Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a QoS value of 4 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match qosgroup 4Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match source-address mac
To use the source MAC address as a match criterion, use the match source-address mac command in class-map configuration or policy inline configuration mode. To remove a previously specified source MAC address as a match criterion, use the no form of this command.
match source-address mac address-source
no match source-address mac address-source
Syntax Description
Command Default
No match criterion is configured.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
This command can be used only on an input interface with a MAC address; for example, Fast Ethernet and Ethernet interfaces.
This command cannot be used on output interfaces with no MAC address, such as serial and ATM interfaces.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example uses the MAC address mac 0.0.0 as a match criterion:
Router(config)# class-map matchsrcmacRouter(config-cmap)# match source-address mac 0.0.0Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the specified MAC source address will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match source-address mac 0.0.0Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
match transport destination-port
To configure the destination port as a key field for a flow record, use the match transport destination-port command in flow record configuration mode. To disable the use of the destination port as a key field for a flow record, use the no form of this command.
match transport destination-port
no match transport destination-port
Syntax Description
This command has no arguments or keywords.
Command Default
The use of the destination port as a key field for a user-defined flow record is not enabled by default.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Examples
The following example configures the destination port as a key field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# match transport destination-portRelated CommandsC
flow record type performance-monitor
Creates a flow record for Performance Monitor.
match transport rtp ssrc
To configure the SSRC field in RTP packet header as a key field for a flow record, use the match transport rtp ssrc command in flow record configuration mode. To disable the use of the SSRC field as a key field for a flow record, use the no form of this command.
match transport rtp ssrc
no match transport rtp ssrc
Syntax Description
This command has no arguments or keywords.
Command Default
The use of the SSRC field in RTP packet header as a key field for a user-defined flow record is not enabled by default.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
The SSRC field in RTP packet header is used to identify a different stream source which is using the same protocol and source and destination IP address and port.
Examples
The following example configures the SSRC field in RTP packet header as a key field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# match transport rtp ssrcRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
match transport source-port
To configure the source port as a key field for a flow record, use the match transport source-port command in flow record configuration mode. To disable the use of the source port as a key field for a flow record, use the no form of this command.
match transport source-port
no match transport source-port
Syntax Description
This command has no arguments or keywords.
Command Default
The use of the source port as a key field for a user-defined flow record is not enabled by default.
Command Modes
flow record configuration (config-flow-record)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
A flow record requires at least one key field before it can be used in a flow monitor. The key fields differentiate flows, with each flow having a unique set of values for the key fields. The key fields are defined using the match command.
Examples
The following example configures the source port as a key field:
Router(config)# flow record type performance-monitor PM-RECORD-4Router(config-flow-record)# match transport source-portRelated Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
match vlan
To define the VLAN match criteria, use the match vlan command in class-map configuration or policy inline configuration mode. To remove the match criteria, use the no form of this command.
match vlan {vlan-id | vlan-range | vlan-combination}
no match vlan
Syntax Description
Command Default
No match criterion is configured.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Use the match vlan command to specify which fields in the incoming packets are examined to classify the packets. Only the IP access group or the MAC access group matching the Ether Type/Len field are supported.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inline command.
Examples
The following example uses the VLAN ID as a match criterion:
Router(config)# class-map matchsrcmacRouter(config-cmap)# match vlan 2Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the criteria of a VLAN ID of 2 will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# match vlan 2Router(config-if-spolicy-inline)# flow monitor fm-2
Router(config-if-spolicy-inline)# exitRelated Commands
max-dropout (policy RTP)
To configure the maximum dropout metric for a Performance Monitor policy, use the max-dropout command in policy RTP configuration mode. To remove the configuration, use the no form of this command.
max-dropout number
no max-dropout number
Syntax Description
number
Specifies the maximum number of packets to ignore ahead of the current packet in terms of sequence number.
Command Default
Maximum number of dropouts is 5.
Command Modes
policy RTP configuration (config-pmap-c-mrtp)
policy inline RTP configuration (config-spolicy-inline-mrtp)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the maximum RTP dropout, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpRouter(config-pmap-c-mrtp)# max-dropout 20The following example shows how to set the maximum RTP dropout, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRouter(config-spolicy-inline-mrtp)# max-dropout 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
max-reorder (policy RTP)
To configure the maximum reorder metric for a Performance Monitor policy, use the max-reorder command in policy RTP configuration mode. To remove the configuration, use the no form of this command.
max-reorder number
no max-reorder number
Syntax Description
number
Specifies the maximum number of packets to ignore ahead of the current packet in terms of sequence number.
Command Default
Maximum number of reorders is 5.
Command Modes
policy RTP configuration (config-pmap-c-mrtp)
policy inline RTP configuration (config-spolicy-inline-mrtp)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the maximum RTP reorder, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpRouter(config-pmap-c-mrtp)# max-reorder 20The following example shows how to set the maximum RTP reorder, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRouter(config-spolicy-inline-mrtp)# max-reorder 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
min-sequential (policy RTP)
To configure the mimimum number of packets in a sequence used to classify an RTP flow, use the min-sequential command in policy RTP configuration mode. To remove the configuration, use the no form of this command.
min-sequential number
no min-sequential number
Syntax Description
number
Specifies the mimimum number of sequental packets required to identify a stream as being an RTP flow.
Command Default
min-sequential is 5.
Command Modes
policy RTP configuration (config-pmap-c-mrtp)
policy inline RTP configuration (config-spolicy-inline-mrtp)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the mimimum number of packets in a sequence used to classify an RTP flow, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpRouter(config-pmap-c-mrtp)# min-sequential 20The following example shows how to set the mimimum number of packets in a sequence used to classify an RTP flow, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRouter(config-spolicy-inline-mrtp)# min-sequential 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
monitor metric ip-cbr
To configure IP-CBR monitor metrics for a Performance Monitor policy, use the monitor metric ip-cbr command in policy configuration mode. To remove the configuration, use the no form of this command.
monitor metric ip-cbr
no monitor metric ip-cbr
Syntax Description
This command has no arguments or keywords.
Command Modes
policy RTP configuration (config-pmap-c)
policy inline RTP configuration (config-if-spolicy-inline)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the layer 3 transmission rate to 10 gbps, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric ip-cbrRouter(config-pmap-c-mipcbr)# rate layer3 10 gbpsThe following example shows how to set the layer 3 transmission rate to 10 gbps, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric ip-cbrRouter(config-spolicy-inline-mipcbr)# rate layer3 10 gbpsRelated Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
monitor metric rtp
To configure RTP monitor metrics for a Performance Monitor policy, use the monitor metric rtp command in policy configuration mode. To remove the configuration, use the no form of this command.
monitor metric rtp
no monitor metric rtp
Syntax Description
This command has no arguments or keywords.
Command Modes
policy configuration (config-pmap-c)
policy inline configuration (config-if-spolicy-inline)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the RTP monitor metrics, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpThe following example shows how to set the RTP monitor metrics, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRelated Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
monitor parameters
To configure monitor parameters for a Performance Monitor policy, use the monitor parameters command in policy configuration mode. To remove the configuration, use the no form of this command.
monitor parameters
no monitor parameters
Syntax Description
This command has no arguments or keywords.
Command Modes
Policy configuration (config-pmap-c)
Policy inline configuration (config-if-spolicy-inline))Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the amount of time wait for a response when collecting data to 20 seconds, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor parametersRouter(config-pmap-c-mparam)# timeout 20The following example shows how to set the amount of time wait for a response when collecting data to 20 seconds, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor parametersRouter(config-spolicy-inline-mparam)# timeout 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
option (Flexible NetFlow)
To configure options data parameters for a flow exporter for Flexible NetFlow or Performance Monitor, use the option command in flow exporter configuration mode. To remove options for a flow exporter, use the no form of this command.
option {application-table | exporter-stats | interface-table | sampler-table | vrf-table} [timeout seconds]
no option {application-table | exporter-stats | interface-table | sampler-table | vrf-table}
Syntax Description
Command Default
The timeout is 600 seconds. All other options data parameters are not configured.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
option application-table
This command causes the periodic sending of an options table, which will allow the collector to map the Network Based Application Recognition (NBAR) application IDs provided in the flow records to application names. The optional timeout can alter the frequency at which the reports are sent.
option exporter-stats
This command causes the periodic sending of the exporter statistics, including the number of records, bytes, and packets sent. This command allows your collector to estimate packet loss for the export records it is receiving. The optional timeout alters the frequency at which the reports are sent.
option interface-table
This command causes the periodic sending of an options table, which will allow the collector to map the interface SNMP indexes provided in the flow records to interface names. The optional timeout can alter the frequency at which the reports are sent.
option sampler-table
This command causes the periodic sending of an options table, which details the configuration of each sampler and allows the collector to map the sampler ID provided in any flow record to a configuration that it can use to scale up the flow statistics. The optional timeout can alter the frequency at which the reports are sent.
option vrf-table
This command causes the periodic sending of an options table, which will allow the collector to map the VRF IDs provided in the flow records to VRF names. The optional timeout can alter the frequency at which the reports are sent.
Examples
The following example causes the periodic sending of the exporter statistics, including the number of records, bytes, and packets sent:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# option exporter-statsThe following example causes the periodic sending of an options table, which allows the collector to map the interface SNMP indexes provided in the flow records to interface names:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# option interface-tableThe following example causes the periodic sending of an options table, which details the configuration of each sampler and allows the collector to map the sampler ID provided in any flow record to a configuration that it can use to scale up the flow statistics:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# option sampler-tableThe following example causes the periodic sending of an options table, which allows the collector to map the NBAR application IDs provided in the flow records to application names:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# option application-tableThe following example causes the periodic sending of an options table, which allows the collector to map the VRF IDs provided in the flow records to VRF names:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# option vrf-tableRelated Commands
output-features
To enable sending export packets for Flexible NetFlow or Performance Monitor using quality of service (QoS) or encryption, use the output-features command in flow exporter configuration mode. To disable sending export packets using QoS or encryption, use the no form of this command.
output-features
no output-features
Syntax Description
This command has no arguments or keywords.
Command Default
If QoS or encryption is configured on the router, neither QoS or encryption is run on Flexible NetFlow or Performance Monitor export packets.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
If the router has the output feature quality of service (QoS) or encryption configured, the output-features command causes the output features to be run on Flexible NetFlow or Performance Monitor export packets.
Examples
The following example configures the use of QoS or encryption on Flexible NetFlow or Performance Monitor export packets:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# output-featuresRelated Commands
policy-map type performance-monitor
To configure a policy for Performance Monitor, use the policy-map type performance-monitor command in global configuration mode. To remove the policy, use the no form of this command.
policy-map type performance-monitor policy-name
no policy-map type performance-monitor policy-name
Syntax Description
Command Modes
Global configuration (config)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
If you do not have an existing flow monitor, you can still configure a flow policy by using the flow monitor inline command to create a new flow monitor.
Examples
The following example shows how to configure a Performance Monitor policy.
Router(config)# policy-map type performance-monitor PM-POLICY-4Related Commands
rate layer3
To configure a Layer 3 transmission rate for a Performance Monitor policy, use the rate layer3 command in policy IP-CBR configuration mode. To remove the configuration, use the no form of this command.
rate layer3 {rate-byte {bps | kbps | mbps | gbps} | packet}
no rate layer3 {rate-byte {bps | kbps | mbps | gbps} | packet}
Syntax Description
Command Default
The Layer 3 transmission rate is 100 mbps.
Command Modes
Policy IP-CBR configuration (config-pmap-c-mipcbr)
Policy inline IP-CBR configuration (config-spolicy-inline-mipcbr)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the Layer 3 transmission rate to 10 gbps, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric ip-cbrRouter(config-pmap-c-mipcbr)# rate layer3 10 gbpsThe following example shows how to set the Layer 3 transmission rate to 10 gbps, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric ip-cbrRouter(config-spolicy-inline-mipcbr)# rate layer3 10 gbpsRelated CommandsR
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
react (policy)
To configure threshold parameters for a Performance Monitor policy, use the react command in policy configuration mode. To disable all threshold monitoring or to disable individual monitored elements, use the no form of this command.
react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate}
no react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate}
Syntax Description
Command Default
Service policy threshold monitoring is disabled.
Command Modes
policy configuration (config-pmap-c)
policy inline configuration (config-if-spolicy-inline)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You can configure multiple react commands for a Performance Monitor policy.
Examples
The following example shows how to specify that SNMP MIB variables will receive an alarm or notification, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# react 2000 rtp-jitter-averageRouter(config-pmap-c-react)# action snmpThe following example shows how to specify that SNMP MIB variables will receive an alarm or notification, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# react 2000 rtp-jitter-averageRouter(config-spolicy-inline-react)# action snmpRelated Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
record (Performance Monitor)
To associate a flow record with a flow monitor for Performance Monitor, use the record command in the appropriate Performance Monitor configuration mode. To remove the association, use the no form of this command.
record {record-name | default-rtp | default-tcp}
no record {record-name | default-rtp | default-tcp}
Syntax Description
Command Modes
Flow monitor configuration (config-flow-monitor)
Monitor configuration (config-pmap)
Policy monitor configuration (config-pmap-c-flowmon)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You can associate a flow record with a flow monitor for Performance Monitor while configuring either a flow monitor, policy map, or service policy.
Examples
The following example shows how to configure a flow record:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class class-4Router(config-pmap-c)# flow monitor inlineRouter(config-pmap-c-flowmon)# record record-4Related Commands
rename (policy)
To rename a policy for Performance Monitor, use the rename command in the policy configuration mode.
rename policy-name
Syntax Description
Command Modes
Policy configuration (config-pmap)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to rename a policy:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# rename policy-20Related Commands
service-policy type performance-monitor
To configure the association of a Performance Monitor policy to an interface, use the service-policy type performance-monitor command in interface configuration mode. To remove the association, use the no form of this command.
service-policy type performance-monitor {{input | output} policy-name | inline {input | output}}
no service-policy type performance-monitor {{input | output} policy-name | inline {input | output}}
Syntax Description
Command Modes
interface configuration (config-if)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
If you do not have an existing flow policy, you can still association a flow policy to an interface by using the inline option to create a new flow policy.
Examples
The following example shows how to configure an association of a Performance Monitor policy to an interface for the input direction.
Router(config)# interface ethernet 0/0
Router(config-if)# service-policy type performance-monitor input PM-POLICY-4Related Commands
flow record type performance-monitor
Creates a flow record for Performance Monitor.
show performance monitor cache
To display the contnet of the cache for Performance Monitor, use the show performance monitor cache command in privileged EXEC mode.
show performance monitor cache [policy policy map name class class map name] [interface interface name]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
If no flow policy or interface is specified, all for all flow policies and interfaces are shown.
Examples
The following example shows the output for this command:
Router # show performance monitor cacheMMON Metering Layer Stats:static pkt cnt: 3049static cce sb cnt: 57dynamic pkt cnt: 0Cache type: PermanentCache size: 2000Current entries: 8High Watermark: 9Flows added: 9Updates sent ( 1800 secs) 0IPV4 SRC ADDR IPV4 DST ADDR IP PROT TRNS SRC PORT TRNS DST PORTipv4 ttl ipv4 ttl min ipv4 ttl max ipv4 dscp bytes long perm pktslong perm user space vm==========================================================================================10.1.1.1 10.1.2.3 17 4000 19670 0 0 0x00 801 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 17 6000 19670 0 0 0x00 801 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 17 4000 20000 0 0 0x00 441 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 6 6000 30000 0 0 0x00 842 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 17 1967 60010 0 0 0x00 361 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 17 1967 40010 0 0 0x00 361 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 6 3001 60010 0 0 0x00 1243 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x0000000010.1.1.1 10.1.2.3 17 2001 40010 0 0 0x00 441 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x000000000x00000000Table 11 describes the significant fields shown in the display.
Related CommandsR
show performance monitor historical
Displays historical sets of statistics collected by Performance Monitor.
show performance monitor clock rate
To display information about clock rates for performance monitor classes, use the show performance monitor clock rate command in privileged EXEC mode.
show performance monitor clock rate [policy policy map name class class map name]
Syntax Description
policy policy map name
Show statistics only for the specified policy.
class class map name
Show statistics only for the specified class.
Command Modes
privileged EXEC
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You must have at least one active session before clock information can be displayed.
Examples
The following example displays performance monitor clock rate information:
Router# show performance monitor clock rateLoad for five secs: 6%/2%; one minute: 5%; five minutes: 5% Time source is NTP, 17:41:35.508 EST Wed Feb 16 2011RTP clock rate for Policy: all-apps-w-mask, Class: IPTVPayload type Clock rate(Hz)pcmu (0 ) 8000gsm (3 ) 8000g723 (4 ) 8000dvi4 (5 ) 8000dvi4-2 (6 ) 16000lpc (7 ) 8000pcma (8 ) 8000g722 (9 ) 8000l16-2 (10 ) 44100l16 (11 ) 44100qcelp (12 ) 8000cn (13 ) 8000mpa (14 ) 90000g728 (15 ) 8000dvi4-3 (16 ) 11025dvi4-4 (17 ) 22050g729 (18 ) 8000celb (25 ) 90000jpeg (26 ) 90000nv (28 ) 90000h261 (31 ) 90000mpv (32 ) 90000mp2t (33 ) 90000h263 (34 ) 90000default 90000RTP clock rate for Policy: all-apps, Class: telepresence-CS4Payload type Clock rate(Hz)pcmu (0 ) 8000gsm (3 ) 8000g723 (4 ) 8000dvi4 (5 ) 8000dvi4-2 (6 ) 16000lpc (7 ) 8000pcma (8 ) 8000g722 (9 ) 8000l16-2 (10 ) 44100l16 (11 ) 44100qcelp (12 ) 8000cn (13 ) 8000mpa (14 ) 90000g728 (15 ) 8000dvi4-3 (16 ) 11025dvi4-4 (17 ) 22050g729 (18 ) 8000celb (25 ) 90000jpeg (26 ) 90000nv (28 ) 90000h261 (31 ) 90000mpv (32 ) 90000mp2t (33 ) 90000h263 (34 ) 90000(96 ) 48000(112) 90000default 90000RTP clock rate for Policy: all-apps, Class: IPVS-traffic-rtpPayload type Clock rate(Hz)pcmu (0 ) 8000gsm (3 ) 8000g723 (4 ) 8000dvi4 (5 ) 8000dvi4-2 (6 ) 16000lpc (7 ) 8000pcma (8 ) 8000g722 (9 ) 8000l16-2 (10 ) 44100l16 (11 ) 44100qcelp (12 ) 8000cn (13 ) 8000mpa (14 ) 90000g728 (15 ) 8000dvi4-3 (16 ) 11025dvi4-4 (17 ) 22050g729 (18 ) 8000celb (25 ) 90000jpeg (26 ) 90000nv (28 ) 90000h261 (31 ) 90000mpv (32 ) 90000mp2t (33 ) 90000h263 (34 ) 90000(96 ) 30000default 90000Table 12 describes the significant fields shown in the display.
Related Commands
show performance monitor clients
To display information about clients for performance monitor, use the show performance monitor clients command in privileged EXEC mode.
show performance monitor clients {detail {client-ID | all} | list}
Syntax Description
detail client-ID
Show detailed information for the specified clients.
detail all
Show detailed information for all clients.
list
Show a list of clients.
Command Modes
privileged EXEC
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You must have Cisco Mediatrace configured and at least one active session before client information can be displayed.
Examples
The following example displays a list of performance monitor clients:
Router# show performance monitor clients listDynamic Video Monitor Client database list:Total number of active clients: 1ID name age(secs) flow(src,dst,src-port, dst-port)1 Mediatrace-158244661 7498 10.10.10.1 1000 10.10.12.2 2000 17Table 13 describes the significant fields shown in the display.
The following example displays details for all performance monitor clients:
Router# show performance monitor clients detail allClient name for ID 1 : Mediatrace-131419052Type: MediatraceAge: 443 secondsMonitor Object: _MMON_DYN_-class-map-69Flow spec: (dvmc-acl#47) 10.10.130.2 1000 10.10.132.2 2000 17monitor parametersinterval duration 60timeout 2history 1flows 100monitor metric rtpmin-sequential 10max-dropout 5max-reorder 5clock-rate 112 90000clock-rate default 90000ssrc maximum 20monitor metric ip-cbrrate layer3 packet 20Flow record: dvmc_fnf_fdef_47Key fields:ipv4 source addressipv4 destination addresstransport source-porttransport destination-portip protocolNon-key fields:monitor eventapplication media eventrouting forwarding-statusip dscpip ttlcounter bytes rateapplication media bytes ratetransport rtp jitter meantransport packets lost countertransport packets expected countertransport event packet-loss countertransport packets lost ratetimestamp intervalcounter packets droppedcounter bytescounter packetsapplication media bytes counterapplication media packets counterMonitor point: _MMON_DYN_-policy-map-70 GigabitEthernet0/3 outputClassification Statistic:matched packet: 545790matched byte: 64403220Table 14 describes the significant fields shown in the display.
Related Commands
show performance monitor historical
Displays historical sets of statistics collected by Performance Monitor.
show performance monitor history
To display the statistics collected by Performance Monitor during the current or past intervals, use the flow performance monitor history command in privileged EXEC mode.
show performance monitor history [interval {all | number [start number]} | interface interface name [filter] | policy policy map name class class map name [filter]} | filter ]
where filter = {ip {source-addr source-prefix | any} {dst-addr dst-prefix | any} | {tcp | udp} {source-addr source-prefix | any} {[eq | lt | gt number | range min max | ssrc {ssrc-number | any} | {{dst-addr dst-prefix | any} eq | lt | gt number | range min max | ssrc {ssrc-number | any}}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
You can display the statistics collected by Performance Monitor during any or all intervals, including the current one. The duration of collection intervals is specified by the interval duration command.
If no flow policy or interface is specified, statistics for all flow policies and interfaces are shown.
Examples
The following example shows the output for this command:
Router # show performance monitor historyCodes: * - field is not configurable under flow recordNA - field is not applicable for configured parametersMatch: ipv4 src addr = 1.1.1.1, ipv4 dst addr = 7.7.7.2, ipv4 prot = udp, trns src port = 20001, trns dst port = 10000, SSRC = 4294967291Policy: RTP_POL, Class: RTP_CLASS, Interface: GigabitEthernet0/4, Direction: inputstart time 14:57:34============*history bucket number : 1*counter flow : 1counter bytes : 0counter bytes rate (Bps) : NA*counter bytes rate per flow (Bps) : NA*counter bytes rate per flow min (Bps) : NA*counter bytes rate per flow max (Bps) : NAcounter packets : 0*counter packets rate per flow : 0counter packets dropped : 0routing forwarding-status reason : Unknowninterface input : NAinterface output : NAmonitor event : trueipv4 dscp : 0ipv4 ttl : 57application media bytes counter : 0application media packets counter : 0application media bytes rate (Bps) : NA*application media bytes rate per flow (Bps) : NA*application media bytes rate per flow min (Bps) : NA*application media bytes rate per flow max (Bps) : NAapplication media packets rate (pps) : 0application media event : Stop*transport rtp flow count : 0transport rtp jitter mean (usec) : NAtransport rtp jitter minimum (usec) : NAtransport rtp jitter maximum (usec) : NA*transport rtp payload type : 0transport event packet-loss counter : NA*transport event packet-loss counter min : NA*transport event packet-loss counter max : NAtransport packets expected counter : NAtransport packets lost counter : NA*transport packets lost counter minimum : NA*transport packets lost counter maximum : NAtransport packets lost rate ( % ) : NA*transport packets lost rate min ( % ) : NA*transport packets lost rate max ( % ) : NA*transport tcp flow count : 1*transport round-trip-time sum (msec) : 32*transport round-trip-time samples : 1transport round-trip-time (msec) : 32*transport round-trip-time min (msec) : 32*transport round-trip-time max (msec) : 32Table 15 describes the significant fields shown in the display.
Related Commands
show performance monitor status
Displays statistics collected by Performance Monitor.
show performance monitor status
To display the cumulative statistics collected by Performance Monitor during the specified number of most recent intervals, use the show performance monitor status command in privileged EXEC mode.
show performance monitor status [interface interface name [filter] | policy policy map name class class map name [filter]} | filter | sort {bitrate-max | loss-event | rtt-max}]
where filter = {ip {source-addr source-prefix | any} {dst-addr dst-prefix | any} | {tcp | udp} {source-addr source-prefix | any} {[eq | lt | gt number | range min max | ssrc {ssrc-number | any} | {{dst-addr dst-prefix | any} eq | lt | gt number | range min max | ssrc {ssrc-number | any}}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
This command displays the cumulative statistics for the specified number of most recent intervals. The number of intervals is configured using the history command. The default settings for this commands is 10 of the most recent collection intervals. The duration of collection intervals is specified by the interval duration command.
If no flow policy or interface is specified, statistics for all flow policies and interfaces are shown.
Examples
The following example shows the output for this command:
Router # show performance monitor statusCodes: * - field is not configurable under flow recordNA - field is not applicable for configured parametersMatch: ipv4 src addr = 1.1.1.1, ipv4 dst addr = 7.7.7.2, ipv4 prot = udp, trns src port = 20001, trns dst port = 10000, SSRC = 4294967291Policy: RTP_POL, Class: RTP_CLASS, Interface: GigabitEthernet0/4, Direction: input*counter flow : 7counter bytes : 43560counter bytes rate (Bps) : 311*counter bytes rate per flow (Bps) : 44*counter bytes rate per flow min (Bps) : 0*counter bytes rate per flow max (Bps) : 442counter packets : 990*counter packets rate per flow : 1counter packets dropped : 0routing forwarding-status reason : NAinterface input : NAinterface output : NAmonitor event : NAipv4 dscp : NAipv4 ttl : NAapplication media bytes counter : 0application media packets counter : 0application media bytes rate (Bps) : 169*application media bytes rate per flow (Bps) : 24*application media bytes rate per flow min (Bps) : 0*application media bytes rate per flow max (Bps) : 241application media packets rate (pps) : 7application media event : Stop*transport rtp flow count : 6transport rtp jitter mean (usec) : 457transport rtp jitter minimum (usec) : 3transport rtp jitter maximum (usec) : 2031*transport rtp payload type : 31transport event packet-loss counter : 0*transport event packet-loss counter min : 0*transport event packet-loss counter max : 0transport packets expected counter : 990transport packets lost counter : 0*transport packets lost counter minimum : 0*transport packets lost counter maximum : 0transport packets lost rate ( % ) : 0.00*transport packets lost rate min ( % ) : 0.00*transport packets lost rate max ( % ) : 0.00*transport tcp flow count : 1*transport round-trip-time sum (msec) : 32*transport round-trip-time samples : 1transport round-trip-time (msec) : 32*transport round-trip-time min (msec) : 32*transport round-trip-time max (msec) : 32Table 16 describes the significant fields shown in the display.
Related Commands
show performance monitor history
Displays historical sets of statistics collected by Performance Monitor.
show policy-map type performance-monitor
To display policy-map statistics for Performance Monitor, use the show policy-map type performance-monitor command in privileged EXEC mode.
show policy-map type performance-monitor[interface interface-name] [class class-name] [input | output]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
If no interface or class is specified, statistics for all interfaces and classes associated with a performance-monitor policy-map are shown.
Examples
The following example shows the output for this command for one Flow Policy::
Router # show policy-map type performance-monitorPolicy Map type performance-monitor PM-POLICY-4Class PM-CLASS-4flow monitor PM-MONITOR-4record PM-RECORD-4exporter PM-EXPORTER-4monitor parametersinterval duration 30timeout 10history 10flows 8000monitor metric rtpmin-sequential 5max-dropout 5max-reorder 5clock-rate default 90000ssrc maximum 5Table 17 describes the significant fields shown in the display.
Related Commands
source (Flexible NetFlow)
To configure the source IP address interface for all of the packets sent by a flow exporter for Flexible NetFlow or Performance Monitor, use the source command in flow exporter configuration mode. To remove the source IP address interface for all of the packets sent by a flow exporter, use the no form of this command.
source interface-type interface-number
no source
Syntax Description
Command Default
The IP address of the interface over which the Flexible NetFlow or Performance Monitor datagram is transmitted is used as the source IP address.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
The benefits of using a consistent IP source address for the datagrams that NetFlow sends include the following:
•
•
Caution
Tip
Examples
The following example shows how to configure Flexible NetFlow or Performance Monitor to use a loopback interface as the source interface for NetFlow traffic:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# source loopback 0Related Commands
ssrc maximum
To configure the SSRC maximum metrics for a Performance Monitor policy, use the ssrc maximum command in policy RTP configuration mode. To remove the configuration, use the no form of this command.
ssrc maximum number
no monitor ssrc maximum number
Syntax Description
number
Specifies the maximum number of SSRCs that can be monitored within same flow (as defined by the protocol, source/destination address, source/destination port). The range is from 1 to 50.
Command Default
Maximum number of SSRC sessions is 10.
Command Modes
Policy RTP configuration (config-pmap-c-mrtp)
Policy inline RTP configuration (config-spolicy-inline-mrtp)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Usage Guidelines
It is not recommended that you limit the maximum number of SSRCs that can be monitored within same flow by using the ssrc maximum keyword. The flow engine will not learn new SSRC sessions once the maximum number is meet until a discovered flow is removed. Setting the value high will help to avoid the unexpected denial-of-service attacks.
Examples
The following example shows how to set the SSRC maximum, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor metric rtpRouter(config-pmap-c-mrtp)# ssrc maximum 40The following example shows how to set the SSRC maximum, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor metric rtpRouter(config-spolicy-inline-mrtp)# ssrc maximum 40Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
template data timeout
To configure the template resend timeout for a flow exporter, use the template data timeout command in flow exporter configuration mode. To remove the template resend timeout for a flow exporter, use the no form of this command.
template data timeout seconds
no template data timeout
Syntax Description
seconds
Configures resending of templates based on the timeout value in seconds, that you enter. Range: 1 to 86400. Default 600.
Command Default
The default template resend timeout for a flow exporter is 600 seconds.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
Examples
The following example configures resending templates based on a timeout of 1000 seconds:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# template data timeout 1000Related Commands
threshold value (policy react and policy inline react)
To configure the threshold that determines whether alarms are sent for a Performance Monitor policy, use the threshold value command in policy configuration mode and policy inline react configuration mode. To remove the threshold setting, use the no form of this command.
threshold value {ge number | gt number | le number | lt number | range rng-start rng-end}
no threshold value {ge number | gt number | le number | lt number | range rng-start rng-end}
Syntax Description
Command Default
no thresholds are set.
Command Modes
Policy react configuration (config-pmap-c-react)
Policy inline react configuration (config-spolicy-inline-react)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to specify that alarms are sent if a value exceeds a threshold of 20, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# react 2000 rtp-jitter-averageRouter(config-pmap-c-react)# threshold gt 20The following example shows how to specify that alarms are sent if a value exceeds a threshold of 20, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# react 2000 rtp-jitter-averageRouter(config-spolicy-inline-react)# threshold gt 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
service-policy type performance-monitor
Associates a policy with an interface.
timeout (monitor parameters)
To configure the amount of time to wait before a stopped flow is removed from the Performance Monitor database, use the monitor parameters command in monitor parameters configuration mode. To remove the configuration, use the no form of this command.
timeout number
no timeout
Syntax Description
timeout number
Specifies the number of intervals before a stopped flow is removed from the database.
Command Default
Timeout is 10 intervals.
Command Modes
Monitor parameters configuration (config-pmap-c-mparam)
Inline monitor parameters configuration (config-spolicy-inline-mparam)Command History
15.1(3)T
This command was introduced.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE.
Examples
The following example shows how to set the amount of time wait for a response when collecting data to 20 intervals, while configuring a policy-map:
Router(config)# policy-map type performance-monitor policy-4Router(config-pmap)# class PM-CLASS-4Router(config-pmap-c)# monitor parametersRouter(config-pmap-c-mparam)# timeout 20The following example shows how to set the amount of time wait for a response when collecting data to 20 intervals, while associating a service-policy with an interface:
Router(config)# interface ethernet 0/0Router(config-if)# service-policy type performance-monitor inline inputRouter(config-if-spolicy-inline)# monitor parametersRouter(config-spolicy-inline-mparam)# timeout 20Related Commands
policy-map type performance-monitor
Creates a policy for Performance Monitor.
policy-map type performance-monitor
Creates a policy for Performance Monitor.
transport (Flexible NetFlow)
To configure the transport protocol for a flow exporter for Flexible NetFlow or Performance Monitor, use the transport command in flow exporter configuration mode. To remove the transport protocol for a flow exporter, use the no form of this command.
transport udp udp-port
no transport
Syntax Description
udp udp-port
Specifies User Datagram Protocol (UDP) as the transport protocol and the UDP port number.
Command Default
Flow exporters use UDP on port 9995.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
Examples
The following example configures UDP as the transport protocol and a UDP port number of 250:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# transport udp 250Related Commands
ttl (Flexible NetFlow)
To configure the time-to-live (TTL) value for a flow exporter for Flexible NetFlow or Performance Monitor, use the ttl command in flow exporter configuration mode. To remove the TTL value for a flow exporter, use the no form of this command.
ttl ttl
no ttl
Syntax Description
Command Default
Flow exporters use a TTL of 255.
Command Modes
flow exporter configuration (config-flow-exporter)
Command History
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor.
Examples
The following example specifies a TTL of 15:
Router(config)# flow exporter FLOW-EXPORTER-1Router(config-flow-exporter)# ttl 15Related Commands
