Configuring Cisco Performance Monitor

Cisco Performance Monitor enables you to monitor the flow of packets in your network and become aware of any issues that might impact the flow before it starts to significantly impact the performance of the application in question. Performance monitoring is especially important for video traffic because high quality interactive video traffic is highly sensitive to network issues. Even minor issues that may not affect other applications can have dramatic effects on video quality.

Because Cisco Performance Monitor uses similar software components and commands as Cisco NetFlow and Cisco Flexible NetFlow, familiarity with these products will help you to understand how to configure Cisco Performance Monitor. These products provide statistics on packets flowing through a router and are the standard for acquiring IP operational data from IP networks. They provide data to support network and security monitoring, network planning, traffic analysis, and IP accounting. For more information about Cisco NetFlow and Cisco Flexible NetFlow, see the documents listed in the Additional References section.

For more information about the design, configuration, and troubleshooting of Performance Monitor and other Cisco Medianet products, including a Quick Start Guide and Deployment Guide, see the Cisco Medianet Knowledge Base Portal, located at http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html.

The following prerequisites must be met before you can configure Cisco Performance Monitor:

To configure Cisco Performance Monitor, configure many of the same basic elements that you normally configure for Flexible NetFlow:

• Interface
• Policy
• Class
• Flow monitor
• Flow record
• Flow exporter

The figure below shows how these elements are related to each other. The elements at the bottom of the figure are configured first.

As shown above, a policy includes one or more classes. Each class has a flow monitor associated with it, and each flow monitor has a flow record and an optional flow exporter associated with it. These elements are configured in the following order:

1. Configure a flow record to specify the key and non-key fields that you want to monitor. This is configured using match and collect commands. You can also optimally configure a flow exporter to specify the export destination. For Cisco Performance Monitor, you must configure a performance-monitor type flow record.
2. Configure a flow monitor that includes the flow record and flow exporter. For Cisco Performance Monitor, you must configure a performance-monitor type flow monitor.
3. Configure a class to specify the filtering criteria using the class-map command.
4. Configure a policy to include one or more classes and one or more performance-monitor type flow monitors using the policy-map command. For Cisco Performance Monitor, you must configure performance-monitor type policies.
5. Associate a performance-monitor type policy to the appropriate interface using the service-policy type performance-monitor command.

You can monitor the following information by configuring a flow record with collect or match commands for the corresponding non-key fields:

Tip	For more information about these statistics, see the show performance monitor statuscommand in theCisco Media Monitoring Command Reference.

• IP Packet Count
• IP TTL
• IP TTL minimum
• IP TTL maximum
• Flow to Interface Mapping
• IP Flow destination address and port, source address and port, and protocol
• RTP Synchronization Source (SSRC)
• IP Octets Count
• Media Stream Packet Count
• Media Stream Octect Count
• Media Byte Rate
• Media Byte Count
• Media Packet Rate
• Media Packet Loss Count
• Media Packet Loss Rate
• Packets Expected Count
• Measured Rate
• Media Loss Event Count
• Round Trip Time (RTT)
• Interarrival Jitter (RFC3550) max
• Interarrival Jitter (RFC3550) min 2
• Interarrival Jitter (RFC3550) mean
• Media Rate Variation
• Monitor Event
• Media Error
• Media Stop
• IP Byte Count
• IP Byte Rate
• IP Source Mask
• IP Destination Mask
• Epoch of A Monitoring Interval
• Packet Forwarding Status
• Packet Drops
• DSCP and IPv6 Traffic Class
• TCP: Maximum Segment Size
• TCP: Window Size Maximum
• TCP: Window Size Maximum
• TCP: Window Size Average
• Out Of Order Bytes
• Out Of Order Packets

Cisco Performance Monitor provides support for the use of the industry-standard Simple Network Management Protocol (SNMP) to monitor media streams. This support is implemented with the addition of the following Cisco proprietary SNMP Management Information Base (MIB) modules:

• CISCO-FLOW-MONITOR-TC-MIB--Defines the textual conventions common to the following MIB modules.
• CISCO-FLOW-MONITOR-MIB--Defines the framework that describes the flow monitors supported by a system, the flows that it has learned, and the flow metrics collected for those flows.
• CISCO-RTP-METRICS-MIB--Defines objects that describe the quality metrics collected for RTP streams, similar to those described by an RTCP Receiver Report packet (RFC 3550).
• CISCO-IP-CBR-METRICS-MIB--Defines objects that describe the quality metrics collected for IP streams that have a Constant Bit Rate (CBR).

For detailed information about these MIBs, and to locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at http://www.cisco.com/go/mibs .

This feature also includes two new command-line interface (CLI) commands and one modified CLI command. The commands are as follows:

• snmp-server host--Enables the delivery of flow monitoring SNMP notifications to a recipient.
• snmp-server enable traps flowmon--Enables flow monitoring SNMP notifications. By default, flow monitoring SNMP notifications are disabled.
• snmp mib flowmon alarm history--Sets the maximum number of entries maintained by the flow monitor alarm history log.

For more information about these commands, see the Cisco IOS Master Command List .

Cisco Performance Monitor has the following limitations on the Catalyst 6000 platform:

• There are some limitations on which types of interfaces can be monitored. The next two tables list which types of interfaces are supported for ingress and egress monitoring on the Catalyst 6500 platform.

• Performance monitoring on VRFs is not supported.
• Performance Monitoring of multicast flows is not supported.

• Routed traffic from a trunk port on a VLAN interface cannot not be monitored because it is not possible to identify the source VLAN interface for the traffic. You will see the following syslog message: "Routed traffic from trunk ports will not be monitored by ingress policy on VLAN interface."

  For a workaround, you can configure a performance monitoring policy on a trunk interface. This monitoring will result in additional CPU usage.

• You cannot use match all type Class maps. Only match any type of lookups are supported. If you configure performance monitoring to use match-all type class maps, it will result in the cloning of packet to the CPU. Packets will then again be classified in the CPU when match-all classes are properly applied and packet are dropped if required. This causes higher than expected CPU usage.
• Performance monitoring policy on the egress of a VLAN interface will not monitor traffic getting bridged within the VLAN. This is due to hardware limitation. Workaround is to apply the policy at the ingress of VLAN interface as well as egress. Policy on the ingress of the VLAN interface will monitor bridged packets.
• Cloned packets from Egress policies can only be software rate-limited. No hardware-based protection is available for these packets. Therefore, you might see high interrupt CPU usage during scenarios when many flows are being monitored.
• Egress performance monitoring makes use of a recirculation mechanism on the Catalyst 6500 platform. This introduces several microseconds of additional latency to the frame switching.
• Performance monitoring is not supported for the packets switched using the Fast (CEF) Path.
• Lawful intercept and performance monitoring makes use of the same mechanism for cloning the packets. The Lawful Intercept feature takes precedence over performance monitoring. Therefore, performance monitoring does not function when the Lawful Intercept feature is enabled. When this occurs, a syslog message is created.
• Performance monitoring makes use of same mechanism as other features, such as Optimized ACL logging, VACL Capture, IPv6 Copy, and so on. The feature that is enabled first takes precedence. The other features are blocked from being configured and a syslog message is created.

Support for IPv6 with Performance Monitor has the following limitations:

• The following topologies are supported with IPv6: Non-MPLS, DMVPN (on most platforms), and dual stack.
• The following topologies are not supported with IPv6: MPLS/VRF (6PE and 6VPE), GETVPN and IPV6 over IPV4 tunnel.
• Mediatrace does not support IPv6.
• Exporting data to a IPv6 address is not supported on the ASR1K platform.
• Flexible NetFlow does not support IPv6 multicast.
• DMVPN is not supported with IPv6 on the ASR1K platform.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    flow exporter exporter-name

4.    description description

5.    destination {ip-address | hostname} [vrf vrf-name]

6.    export-protocol {netflow-v5 | netflow-v9 | ipfix }

7.    dscp dscp

8.    source interface-type interface-number

9.    option {application-attributes | application table | exporter-stats | interface-table | metadata-table | sampler-table | vrf-table} [timeout seconds]

10.    output-features

11.    template data timeout seconds

12.    transport udp udp-port

13.    ttl seconds

14.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	flow exporter exporter-name Example: Device(config)# flow exporter EXPORTER-1	Creates the flow exporter and enters Flexible NetFlow flow exporter configuration mode. This command also allows you to modify an existing flow exporter.
Step 4	description description Example: Device(config-flow-exporter)# description Exports to the datacenter	(Optional) Configures a description to the exporter that will appear in the configuration and the display of the show flow exporter command.
Step 5	destination {ip-address | hostname} [vrf vrf-name] Example: Device(config-flow-exporter)# destination 172.16.10.2	Specifies the IP address or hostname of the system to which the exporter sends data. Note    You can export to a destination using either an IPv4 or IPv6 address.
Step 6	export-protocol {netflow-v5 | netflow-v9 | ipfix } Example: Device(config-flow-exporter)# export-protocol netflow-v9	Specifies the protocol used by the exporter. Note    The export of extracted fields from NBAR is only supported over IPFIX.
Step 7	dscp dscp Example: Device(config-flow-exporter)# dscp 63	(Optional) Configures differentiated services code point (DSCP) parameters for datagrams sent by the exporter. The range for the dscp argument is from 0 to 63. Default: 0.
Step 8	source interface-type interface-number Example: Device(config-flow-exporter)# source ethernet 0/0	(Optional) Specifies the local interface from which the exporter will use the IP address as the source IP address for exported datagrams.
Step 9	option {application-attributes | application table | exporter-stats | interface-table | metadata-table | sampler-table | vrf-table} [timeout seconds] Example: Device(config-flow-exporter)# option exporter-stats timeout 120	(Optional) Enables the use of option tables to decrease the amount of data exported. These tables allow the exporter to just export an ID that represents the complete value of the metadata and is mapped to the value by the option table. For example, the interface table maps the SNMP index to the interface name and the VRF table maps the VRF ID to the name. You can enable the use of any combination of option tables concurrently. The range for the seconds argument is 1 to 86,400. Default: 600.
Step 10	output-features Example: Device(config-flow-exporter)# output-features	(Optional) Enables sending export packets using quality of service (QoS) and encryption.
Step 11	template data timeout seconds Example: Device(config-flow-exporter)# template data timeout 120	(Optional) Configure the resending of templates based on a timeout. The range for the seconds argument is 1 to 86400 (86400 seconds = 24 hours).
Step 12	transport udp udp-port Example: Device(config-flow-exporter)# transport udp 650	Configures UDP as the transport protocol and specifies the UDP port on which the destination system is listening for exported datagrams. The range for the udp-port argument is from 1 to 65536.
Step 13	ttl seconds Example: Device(config-flow-exporter)# ttl 15	(Optional) Configures the time-to-live (TTL) value for datagrams sent by the exporter. The range for the seconds argument is from 1 to 255.
Step 14	end Example: Device(config-flow-exporter)# end	Exits flow exporter configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    flow record type performance-monitor record-name

4.    match application {name [account-on-resolution] | vendor | version}

5.    match connection transaction-id

6.    match flow {direction | sampler}

7.    match interface {input | output}

8.    match ipv4 {destination{address | prefix [minimum-mask mask]} | protocol | source {address | prefix [minimum-mask mask]}

9.    match ipv4 fragmentation {flags |offset}

10.    match ipv4 {section {header size header-size | payload size payload-size}

11.    match ipv4 total-length

12.    match ipv4 ttl

13.    match ipv6 {dscp | flow-label | next-header | payload-length | precedence | protocol | traffic-class | version}

14.    match ipv6 destination {address | {mask | prefix} [minimum-mask mask]}

15.    match ipv6 extension map

16.    match ipv6 fragmentation {flags | id | offset}

17.    match ipv6 hop-limit

18.    match ipv6 length {header | payload | total}

19.    match ipv6 {section {header size header-size | payload size payload-size}

20.    match ipv6 source {address | {mask | prefix} [minimum-mask mask]}

21.    match metadata {global-session-id | multi-party-session-id}

22.    match routing {destination | source}

23.    match routing is-multicast

24.    match routing multicast replication-factor

25.    match transport {destination-port | igmp | rtp [ssrc] | source-port}

26.    match transport icmp ipv4 {code | type}

27.    match transport icmp ipv6 {code | type}

28.   match transport tcp {acknowledgement-number | destination-port | flags {[ack] | [cwr] | [ece] | [fin] | [psh] | [syn] | [urg]} | header-length | maximum-segment-size | sequence-number | urgent-pointer | window-size | window-size-maximum | window-size-minimum | window-size-average}

29.   match transport udp {destination-port | message-length | source-port}

30.    collect application media {bytes{rate | counter}| packets {rate|counter} | events}

31.    collect application {name [account-on-resolution ]| description | http host | nntp group-name | pop3 server | rstp host-name | sip {destination | source} | smtp {sender | server} | vendor | version}

32.    collect connection

33.    collect counter {bytes [long | rate] |packets[dropped [long] | long]}

34.    collect datalink mac source address {input | output}

35.    collect flow direction

36.    collect interface {input | output}

37.    collect ipv4 {destination mask [minimum-mask mask]} | dscp | source mask [minimum-mask mask] | ttl [minimum | maximum]}

38.    collect ipv4 fragmentation {flags | offset}

39.    collect ipv4 {section {header size header-size | prefix[payload size payload-size}

40.    collect ipv4 total-length [maximum | minimum]

41.    collect ipv6 {dscp | flow-label | next-header | payload-length | precedence | protocol | traffic-class | version}

42.    collect ipv6 destination {address {mask | prefix} [minimum-mask mask]}

43.    collect ipv6 extension-map

44.    collect ipv6 fragmentation {flags | offset}

45.    collect ipv6 hop-limit [maximum] [minimum]

46.    collect ipv6 length{header | payload | total [maximum] [minimum] }

47.    collect ipv6 {section {header size header-size | prefix [payload size payload-size}

48.    collect ipv6 source {address {mask | prefix} [minimum-mask mask]}

49.    collect metadata {global-session-id | multi-party-session-id}

50.    collect monitor event

51.    collect routing forwarding-status [reason]

52.    collect routing is-multicast

53.    collect routing multicast replication-factor

54.    collect timestamp internal

55.    collect timestamp sys-uptime {first | last}

56.    collect transport {destination-port | igmp type | source-port | event packet-loss counter | packets {expected counter | lost {counter | rate} | out-of-order} | round-trip-time | rtp jitter {minimum | mean | maximum}}

57.    collect transport icmp ipv4

58.    collect transport icmp ipv6

59.   collect transport tcp {acknowledgement-number | destination-port | flags {[ack] | [cwr] | [ece] | [fin] | [psh] | [syn] | [urg]} | header-length | maximum-segment-size | sequence-number | urgent-pointer | window-size | window-size-maximum | window-size-minimum | window-size-average}

60.    collect transport udp {destination-port | message-length | source-port}

61.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	flow record type performance-monitor record-name Example: Device(config)# flow record type performance-monitor record-8	Creates a flow record and enters flow record configuration mode. This command also allows you to modify an existing flow record.
Step 4	match application {name [account-on-resolution] | vendor | version} Example: Device(config-flow-record)# match application name	Specifies that the application name, vendor, or version will be used as a key field.
Step 5	match connection transaction-id Example: Device(config-flow-record)# match connection transaction-id	Specifies that the application name will be used as a key field.
Step 6	match flow {direction | sampler} Example: Device(config-flow-record)# match flow direction	Specifies that the flow direction field will be used as a key field.
Step 7	match interface {input | output} Example: Device(config-flow-record)# match flow direction	Specifies that the input interface field will be used as a key field.
Step 8	match ipv4 {destination{address | prefix [minimum-mask mask]} | protocol | source {address | prefix [minimum-mask mask]} Example: Device(config-flow-record)# match ipv4 destination address	Specifies that one or more of the IPv4 fields will be used as a key field.
Step 9	match ipv4 fragmentation {flags |offset} Example: Device(config-flow-record)# match ipv4 fragmentation flags	Specifies that one or more of the IPv4 fields will be used as a key field.
Step 10	match ipv4 {section {header size header-size | payload size payload-size} Example: Device(config-flow-record)# match ipv4 section header size 8	Specifies that one or more of the IPv4 fields will be used as a key field.
Step 11	match ipv4 total-length Example: Device(config-flow-record)# match ipv4 total-length	Specifies that the IPv4 total length field will be used as a key field.
Step 12	match ipv4 ttl Example: Device(config-flow-record)# match ipv4 ttl	Specifies that the IPv4 ttl field will be used as a key field.
Step 13	match ipv6 {dscp | flow-label | next-header | payload-length | precedence | protocol | traffic-class | version} Example: Device(config-flow-record)# match ipv6 dscp	Specifies that the IPv6 DSCP field will be used as a key field.
Step 14	match ipv6 destination {address | {mask | prefix} [minimum-mask mask]} Example: Device(config-flow-record)# match ipv4 destination address	Specifies that the IPv6 destination address field will be used as a key field.
Step 15	match ipv6 extension map Example: Device(config-flow-record)# match ipv6 extension map	Specifies that the IPv6 extension map field will be used as a key field.
Step 16	match ipv6 fragmentation {flags | id | offset} Example: Device(config-flow-record)# match ipv6 fragmentation flags	Specifies that the IPv6 fragmentation flags field will be used as a key field.
Step 17	match ipv6 hop-limit Example: Device(config-flow-record)# match ipv6 hop-limit	Specifies that the IPv6 hop limit field will be used as a key field.
Step 18	match ipv6 length {header | payload | total} Example: Device(config-flow-record)# match ipv6 length total	Specifies that the IPv6 total length field will be used as a key field.
Step 19	match ipv6 {section {header size header-size | payload size payload-size} Example: Device(config-flow-record)# match ipv6 section header size 8	Specifies that the IPv6 section header size field will be used as a key field.
Step 20	match ipv6 source {address | {mask | prefix} [minimum-mask mask]} Example: Device(config-flow-record)# match ipv6 source address	Specifies that the IPv6 source address field will be used as a key field.
Step 21	match metadata {global-session-id | multi-party-session-id} Example: Device(config-flow-record)# match metadata global-session-id	Specifies that a metadata session ID field will be used as a key field.
Step 22	match routing {destination | source} Example: Device(config-flow-record)# match routing source	Specifies that the routing source flag field will be used as a key field.
Step 23	match routing is-multicast Example: Device(config-flow-record)# match routing is-multicast	Specifies that the routing is-multicast flag field will be used as a key field.
Step 24	match routing multicast replication-factor Example: Device(config-flow-record)# match routing multicast replication-factor	Specifies that the routing multicast replication-factor flag field will be used as a key field.
Step 25	match transport {destination-port | igmp | rtp [ssrc] | source-port} Example: Device(config-flow-record)# match transport destination-port	Specifies that one or more of the transport layer fields will be used as a key field, including the Synchronization Source (SSRC) field in the Real-Time Transport Protocol (RTP) packet header.
Step 26	match transport icmp ipv4 {code | type} Example: Device(config-flow-record)# match transport icmp ipv4 code	Specifies that the IPv4 ICMP transport code field will be used as a key field.
Step 27	match transport icmp ipv6 {code | type} Example: Device(config-flow-record)# match transport icmp ipv6 code	Specifies that the IPv6 ICMP transport code field will be used as a key field.
Step 28	match transport tcp {acknowledgement-number | destination-port | flags {[ack] | [cwr] | [ece] | [fin] | [psh] | [syn] | [urg]} | header-length | maximum-segment-size | sequence-number | urgent-pointer | window-size | window-size-maximum | window-size-minimum | window-size-average} Example: Device(config-flow-record)# match transport tcp destination-port	Specifies that the IPv6 TCP transport destination port field will be used as a key field.
Step 29	match transport udp {destination-port | message-length | source-port} Example: Device(config-flow-record)# match transport udp destination-port	Specifies that the IPv6 UDP transport destination port field will be used as a key field.
Step 30	collect application media {bytes{rate | counter}| packets {rate|counter} | events} Example: Device(config-flow-record)# collect application media events	Specifies that the application media bytes, packets, or events will be used as a nonkey field. An application event occurs when either one of the thresholds specified by a react statement for the flow was crossed at least once in the monitoring interval or no media packets were seen.
Step 31	collect application {name [account-on-resolution ]| description | http host | nntp group-name | pop3 server | rstp host-name | sip {destination | source} | smtp {sender | server} | vendor | version} Example: Device(config-flow-record)# collect application name	Specifies that the application name will be used as a nonkey field.
Step 32	collect connection Example: Device(config-flow-record)# collect connection initiator	Specifies that the connection initiator will be used as a nonkey field.
Step 33	collect counter {bytes [long | rate] |packets[dropped [long] | long]} Example: Device(config-flow-record)# collect counter bytes long	Specifies the number of bytes or packets that will be used as a nonkey field.
Step 34	collect datalink mac source address {input | output} Example: Device(config-flow-record)# collect flow direction	Specifies that the flow direction field will be used as a nonkey field.
Step 35	collect flow direction Example: Device(config-flow-record)# collect flow direction	Specifies that the flow direction field will be used as a nonkey field.
Step 36	collect interface {input | output} Example: Device(config-flow-record)# collect interface input	Specifies that the input or output interface will be used as a nonkey field.
Step 37	collect ipv4 {destination mask [minimum-mask mask]} | dscp | source mask [minimum-mask mask] | ttl [minimum | maximum]} Example: Device(config-flow-record)# collect ipv4 dscp	Specifies that the IPv4 DSCP field will be used as a nonkey field.
Step 38	collect ipv4 fragmentation {flags | offset} Example: Device(config-flow-record)# collect ipv4 fragmentation flags	Specifies that the IPv4 fragmentation flags field will be used as a nonkey field.
Step 39	collect ipv4 {section {header size header-size | prefix[payload size payload-size} Example: Device(config-flow-record)# collect ipv4 section header size 8	Specifies that the IPv4 section header size field will be used as a nonkey field.
Step 40	collect ipv4 total-length [maximum | minimum] Example: Device(config-flow-record)# collect ipv4 total-length	Specifies that the IPv4 total-length field will be used as a nonkey field.
Step 41	collect ipv6 {dscp | flow-label | next-header | payload-length | precedence | protocol | traffic-class | version} Example: Device(config-flow-record)# collect ipv6 dscp	Specifies that the IPv6 DSCP field will be used as a nonkey field.
Step 42	collect ipv6 destination {address {mask | prefix} [minimum-mask mask]} Example: Device(config-flow-record)# collect ipv6 destination mask	Specifies that the IPv6 destination mask field will be used as a nonkey field.
Step 43	collect ipv6 extension-map Example: Device(config-flow-record)# collect ipv6 extension-map	Specifies that the IPv6 extension-map field will be used as a nonkey field.
Step 44	collect ipv6 fragmentation {flags | offset} Example: Device(config-flow-record)# collect ipv6 fragmentation flags	Specifies that the IPv6 fragmentation flags field will be used as a nonkey field.
Step 45	collect ipv6 hop-limit [maximum] [minimum] Example: Device(config-flow-record)# collect ipv6 hop-limit	Specifies that the IPv6 hop-limit field will be used as a nonkey field.
Step 46	collect ipv6 length{header | payload | total [maximum] [minimum] } Example: Device(config-flow-record)# collect ipv6 length total	Specifies that the IPv6 total length field will be used as a nonkey field.
Step 47	collect ipv6 {section {header size header-size | prefix [payload size payload-size} Example: Device(config-flow-record)# collect ipv6 section header size 8	Specifies that the IPv6 section header size field will be used as a nonkey field.
Step 48	collect ipv6 source {address {mask | prefix} [minimum-mask mask]} Example: Device(config-flow-record)# collect ipv6 source mask	Specifies that the IPv6 source mask field will be used as a nonkey field.
Step 49	collect metadata {global-session-id | multi-party-session-id} Example: Device(config-flow-record)# collect meatdata global-session-id	Specifies that a metadata session ID field will be used as a nonkey field.
Step 50	collect monitor event Example: Device(config-flow-record)# collect monitor event	Specifies that the monitor event field will be used as a nonkey field. A monitor event occurs when no media application packets were seen
Step 51	collect routing forwarding-status [reason] Example: Device(config-flow-record)# collect routing forwarding-status	Specifies that the one or more of the routing attributes will be used as a nonkey field.
Step 52	collect routing is-multicast Example: Device(config-flow-record)# collect routing is-multicast	Specifies that the routing is-multicast field will be used as a nonkey field.
Step 53	collect routing multicast replication-factor Example: Device(config-flow-record)# collect routing multicast replication-factor	Specifies that the routing multicast replication-factor field will be used as a nonkey field.
Step 54	collect timestamp internal Example: Device(config-flow-record)# collect timestamp internal	Specifies that the system timestamp of the first seen or last seen packet in a flow will be used as a nonkey field.
Step 55	collect timestamp sys-uptime {first | last} Example: Device(config-flow-record)# collect timestamp sys-uptime	Specifies that the system timestamp of the sys-uptime will be used as a nonkey field.
Step 56	collect transport {destination-port | igmp type | source-port | event packet-loss counter | packets {expected counter | lost {counter | rate} | out-of-order} | round-trip-time | rtp jitter {minimum | mean | maximum}} Example: Device(config-flow-record)# collect transport packets expected counter	Specifies that one or more of the transport layer fields will be used as a nonkey field. These fields include metrics for: Packet-loss counter Expected packets counter Jitter
Step 57	collect transport icmp ipv4 Example: Device(config-flow-record)# collect transport icmp ipv4	Specifies that the transport ICMP IPv4 field will be used as a nonkey field.
Step 58	collect transport icmp ipv6 Example: Device(config-flow-record)# collect transport icmp ipv6	Specifies that the transport ICMP IPv6 field will be used as a nonkey field.
Step 59	collect transport tcp {acknowledgement-number | destination-port | flags {[ack] | [cwr] | [ece] | [fin] | [psh] | [syn] | [urg]} | header-length | maximum-segment-size | sequence-number | urgent-pointer | window-size | window-size-maximum | window-size-minimum | window-size-average} Example: Device(config-flow-record)# collect transport tcp destination-port
Step 60	collect transport udp {destination-port | message-length | source-port} Example: Device(config-flow-record)# collect transport udp destination-port	Specifies that the transport UDP destination port field will be used as a nonkey field.
Step 61	end Example: Device(config-flow-record)# end	Exits flow record configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    flow record flow-record-name

4.    match interface input

5.    match flow direction

6.    match connection client {ipv4 | ipv6} address

7.    match connection client transport port

8.    match connection server {ipv4 | ipv6} address

9.    match connection server transport port

10.    match ipv4 {initiator | responder} address

11.    match ipv6 {initiator | responder} address

12.    match transport {initiator | responder} port

13.    match routing vrf {input | output}

14.    match datalink {destination-vlan-id | source-vlan-id}

15.    match datalink vlan {input | output}

16.    match datalink mac {destination | source} address {input | output}

17.    match flow {class | qos-class}

18.    match policy performance-monitor classification hierarchy

19.    match services waas segment

20.    collect interface output

21.    collect flow direction

22.    collect timestamp sys-uptime first

23.    collect timestamp sys-uptime last

24.    collect counter bytes long

25.    collect counter packets

26.    collect connection client {ipv4 | ipv6} address

27.    collect connection client counter {bytes long | packets long | packets retransmitted}

28.    collect connection client transport port

29.    collect connection new-connections

30.    collect connection sum-duration

31.    collect routing vrf {input | output}

32.    collect connection delay application {sum | min | max}

33.    collect connection delay network {client-to-server | to-server [histogram { bucket1 | bucket2 | bucket3 | bucket4 | bucket5 | bucket6 | bucket7}] {sum | min | max}

34.    collect connection delay response {client-to-server | to-client | to-server} {sum | min | max}

35.    collect connection performance application-delay {sum | min | max}

36.    collect connection performance initiator bytes long

37.    collect connection performance initiator count re-transmitted-packets

38.    collect connection performance initiator network-delay {sum | min | max}

39.    collect connection performance initiator packets long

40.    collect connection performance network-delay {sum | min | max}

41.    collect connection performance new-transaction-time

42.    collect connection performance total-transaction-time {sum | min | max}

43.    collect connection performance total-transaction-time {sum | min | max}

44.    collect connection performance responder bytes long

45.    collect connection performance responder response-time {sum | min | max}

46.    collect connection performance responder network-delay {sum | min | max}

47.    collect connection performance responder count {histogram { bucket1 | bucket2 | bucket3 | bucket4 | bucket5 | bucket6 | bucket7} | late-responses | responses}

48.    collect connection performance responder packets long

49.    collect connection performance total-delay {sum | min | max}

50.    collect connection performance total-transaction-time {sum | min | max}

51.    collect connection server {ipv4 | ipv6} address

52.    collect connection server counter {bytes long | packets long | packets retransmitted}

53.    collect connection server transport port

54.    collect connection transaction {counter complete | duration {sum | min | max}}

55.    collect datalink {destination-vlan-id | source-vlan-id}

56.    collect datalink mac {destination | source} address {input | output}

57.    collect datalink vlan {input | output}

58.    collect policy performance-monitor classification hierarchy

59.    collect services waas {passthrough-reason | segment}

60.    collect timestamp absolute {first | last}

61.    collect transport tcp {option map | window-size {sum | minimum | maximum} | maximum-segment-size}

62.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	flow record flow-record-name Example: Router(config)# flow record my-input-usage-monitor	Creates a flow record and enters flow record configuration mode.
Step 4	match interface input Example: Router(config-flow-record)# match interface input	Configures the input interface for the packet as a key field for the flow record. input--Traffic arrives on the Cisco router's input interface.
Step 5	match flow direction Example: Router(config-flow-record)# match flow direction	Configures the direction of the flow record as a key field. The direction is either input or output.
Step 6	match connection client {ipv4 | ipv6} address Example: Router(config-flow-record)# match connection client ipv6 address	Configures the Ipv6 address of the client as a key field for a flow record.
Step 7	match connection client transport port Example: Router(config-flow-record)# match connection client transport port	Configures the connection port of the client as a key field for a flow record.
Step 8	match connection server {ipv4 | ipv6} address Example: Router(config-flow-record)# match connection server ipv6 address	Configures the Ipv6 address of the server as a key field for a flow record.
Step 9	match connection server transport port Example: Router(config-flow-record)# match connection server transport port	Configures the connection port of the server as a key field for a flow record.
Step 10	match ipv4 {initiator | responder} address Example: Router(config-flow-record)# match ipv4 initiator address	(Optional) For IPv4 networks, configures the IPv4 address of the initiator or responder as a key field. The direction is either input or output.
Step 11	match ipv6 {initiator | responder} address Example: Router(config-flow-record)# match ipv6 initiator address	(Optional) For IPv6 networks, configures the IPv6 address of the initiator or responder as a key field. The direction is either input or output.
Step 12	match transport {initiator | responder} port Example: Router(config-flow-record)# match transport initiator port	(Optional) Configures the transport port of the initiator or responder as a key field.
Step 13	match routing vrf {input | output} Example: Router(config-flow-record)# match routing vrf input	(Optional) Configures the virtual routing and forwarding (VRF) ID for incoming or outgoing packets as a key field.
Step 14	match datalink {destination-vlan-id | source-vlan-id} Example: Router(config-flow-record)# match datalink destination-vlan-id	(Optional) Configures the destination VLAN ID as a key field.
Step 15	match datalink vlan {input | output} Example: Router(config-flow-record)# match datalink vlan input	(Optional) Configures the VLAN ID for incoming or outgoing packets as a key field.
Step 16	match datalink mac {destination | source} address {input | output} Example: Router(config-flow-record)# match datalink mac destination address output	(Optional) Configures the destination MAC address as a key field.
Step 17	match flow {class | qos-class} Example: Router(config-flow-record)# match flow class	Configures the use of the class ID as a key field for a flow record.
Step 18	match policy performance-monitor classification hierarchy Example: Router(config-flow-record)# match policy performance-monitor classification hierarchy	Configures the use of the Performance Monitor policy classification hierarchy as a key field for a flow record.
Step 19	match services waas segment Example: Router(config-flow-record)# match services waas segment	Configures the use of the WAAS segment as a key field for a flow record.
Step 20	collect interface output Example: Router(config-flow-record)# collect interface output	Configures the output interface as a non-key field for a flow record and enables collecting the output interface fields from the flows for the flow record.
Step 21	collect flow direction Example: Router(config-flow-record)# collect flow direction	Configures the flow direction as a non-key field for a flow record.
Step 22	collect timestamp sys-uptime first Example: Router(config-flow-record)# collect timestamp sys-uptime first	Configures the system uptime of the first seen packet in a flow as a nonkey field for a flow record. first--Configures the system uptime for the time the first packet was seen from the flows as a nonkey field and enables collecting time stamps based on the system uptime for the time the first packet was seen from the flows.
Step 23	collect timestamp sys-uptime last Example: Router(config-flow-record)# collect timestamp sys-uptime last	Configures the system uptime of the last seen packet in a flow as a nonkey field for a flow record. last--Configures the system uptime for the time the last packet was seen from the flows as a nonkey field and enables collecting time stamps based on the system uptime for the time the most recent packet was seen from the flows.
Step 24	collect counter bytes long Example: Router(config-flow-record)# collect counter bytes long	Configures the number of bytes in a flow as a nonkey field for a flow record. bytes--Configures the number of bytes seen in a flow as a nonkey field and enables collecting the total number of bytes from the flow. long--Enables collecting the total number of bytes or packets from the flow by using a 64-bit counter rather than a 32-bit counter.
Step 25	collect counter packets Example: Router(config-flow-record)# collect counter packets	Configures the number of packets in a flow as a nonkey field for a flow record. packets--Configures the number of packets seen in a flow as a nonkey field and enables collecting the total number of packets from the flow.
Step 26	collect connection client {ipv4 | ipv6} address Example: Router(config-flow-record)# collect connection client ipv6 address	Configures the Ipv6 address of the client as a nonkey field for a flow record.
Step 27	collect connection client counter {bytes long | packets long | packets retransmitted} Example: Router(config-flow-record)# collect connection client counter packets retransmitted	Configures the number of the client packets retransmitted as a nonkey field for a flow record.
Step 28	collect connection client transport port Example: Router(config-flow-record)# collect connection client transport port	Configures the client connection port as a nonkey field for a flow record.
Step 29	collect connection new-connections Example: Router(config-flow-record)# collect connection new-connections	Counts the number of TCP or UDP connections which were opened during the observation period. The observation period may be specified by the flow start and end timestamps.
Step 30	collect connection sum-duration Example: Router(config-flow-record)# collect connection sum-duration	Aggregates the total time, in seconds, for all the TCP or UDP connections, which were in use during the observation period. For example, if there are five concurrent connections each for 10 seconds, the value would be 50 seconds.
Step 31	collect routing vrf {input | output} Example: Router(config-flow-record)# collect routing vrf output	Configures the virtual routing and forwarding (VRF) ID for incoming or outgoing packets output as a nonkey field for a flow record.
Step 32	collect connection delay application {sum | min | max} Example: Router(config-flow-record)# collect connection delay application sum	Configures the total amount of application delay as a nonkey field for a flow record.
Step 33	collect connection delay network {client-to-server | to-server [histogram { bucket1 | bucket2 | bucket3 | bucket4 | bucket5 | bucket6 | bucket7}] {sum | min | max} Example: Router(config-flow-record)# collect connection delay network client-to-server sum	Configures the total amount of network delay between the client and the server as a nonkey field for a flow record.
Step 34	collect connection delay response {client-to-server | to-client | to-server} {sum | min | max} Example: Router(config-flow-record)# collect connection delay response client-to-server sum	Configures the total amount of response delay between the client and the server as a nonkey field for a flow record.
Step 35	collect connection performance application-delay {sum | min | max} Example: Router(config-flow-record)# collect connection performance application-delay sum	Configures the total application delay as a nonkey field for a flow record.
Step 36	collect connection performance initiator bytes long Example: Router(config-flow-record)# collect connection performance initiator bytes long	Configures the number of long bytes for the Mediatrace initiator as a nonkey field for a flow record.
Step 37	collect connection performance initiator count re-transmitted-packets Example: Router(config-flow-record)# collect connection performance initiator count re-transmitted-packets	Configures the number of retrransmitted packets for the Mediatrace initiator as a nonkey field for a flow record.
Step 38	collect connection performance initiator network-delay {sum | min | max} Example: Router(config-flow-record)# collect connection performance initiator network-delay sum	Configures the total network delay for the Mediatrace initiator as a nonkey field for a flow record.
Step 39	collect connection performance initiator packets long Example: Router(config-flow-record)# collect connection performance initiator packets long	Configures the number of long packets for the Mediatrace initiator as a nonkey field for a flow record.
Step 40	collect connection performance network-delay {sum | min | max} Example: Router(config-flow-record)# collect connection performance network-delay sum	Configures the total network delay as a nonkey field for a flow record.
Step 41	collect connection performance new-transaction-time Example: Router(config-flow-record)# collect connection performance new-transaction	Configures the new transaction field as a nonkey field for a flow record.
Step 42	collect connection performance total-transaction-time {sum | min | max} Example: Router(config-flow-record)# collect connection performance total-transaction-time sum	Configures the total transaction time as a nonkey field for a flow record.
Step 43	collect connection performance total-transaction-time {sum | min | max} Example: Router(config-flow-record)# collect connection performance total-transaction-time sum	Configures the total transaction time as a nonkey field for a flow record.
Step 44	collect connection performance responder bytes long Example: Router(config-flow-record)# collect connection performance responder bytes long	Configures the number of long bytes for the Mediatrace responder as a nonkey field for a flow record.
Step 45	collect connection performance responder response-time {sum | min | max} Example: Router(config-flow-record)# collect connection performance responder response-time sum	Configures the total response time for the Mediatrace responder as a nonkey field for a flow record.
Step 46	collect connection performance responder network-delay {sum | min | max} Example: Router(config-flow-record)# collect connection performance responder network-delay sum	Configures the total network delay for the Mediatrace responder as a nonkey field for a flow record.
Step 47	collect connection performance responder count {histogram { bucket1 | bucket2 | bucket3 | bucket4 | bucket5 | bucket6 | bucket7} | late-responses | responses} Example: Router(config-flow-record)# collect connection performance responder count late-responses	Configures the number of late responses for the Mediatrace responder as a nonkey field for a flow record.
Step 48	collect connection performance responder packets long Example: Router(config-flow-record)# collect connection performance responder packets long	Configures the number of long packets for the Mediatrace responder as a nonkey field for a flow record.
Step 49	collect connection performance total-delay {sum | min | max} Example: Router(config-flow-record)# collect connection performance total-delay sum	Configures the total connection delay as a nonkey field for a flow record.
Step 50	collect connection performance total-transaction-time {sum | min | max} Example: Router(config-flow-record)# collect connection performance total-transaction-time sum	Configures the total transaction time as a nonkey field for a flow record.
Step 51	collect connection server {ipv4 | ipv6} address Example: Router(config-flow-record)# collect connection server ipv6 address	Configures the IPv6 address of the server as a nonkey field for a flow record.
Step 52	collect connection server counter {bytes long | packets long | packets retransmitted} Example: Router(config-flow-record)# collect connection server counter packets retransmitted	Configures the number of the server packets retransmitted as a nonkey field for a flow record.
Step 53	collect connection server transport port Example: Router(config-flow-record)# collect connection server transport port	Configures the server connection port as a nonkey field for a flow record.
Step 54	collect connection transaction {counter complete | duration {sum | min | max}} Example: Router(config-flow-record)# collect connection transaction duration sum	Configures the total duration of the transaction as a nonkey field for a flow record.
Step 55	collect datalink {destination-vlan-id | source-vlan-id} Example: Router(config-flow-record)# collect datalink destination-vlan-id	(Optional) Configures the destination VLAN ID as a nonkey field.
Step 56	collect datalink mac {destination | source} address {input | output} Example: Router(config-flow-record)# collect datalink mac destination address input	(Optional) Configures the destination MAC address as a nonkey field.
Step 57	collect datalink vlan {input | output} Example: Router(config-flow-record)# collect datalink vlan input	(Optional) Configures the VLAN ID for incoming or outgoing packets as a nonkey field.
Step 58	collect policy performance-monitor classification hierarchy Example: Router(config-flow-record)# collect policy performance-monitor classification hierarchy	Configures the use of the Performance Monitor policy classification hierarchy as a nonkey field for a flow record.
Step 59	collect services waas {passthrough-reason | segment} Example: Router(config-flow-record)# collect services waas segment	Configures the use of the WAAS segment as a nonkey field for a flow record.
Step 60	collect timestamp absolute {first | last} Example: Router(config-flow-record)# collect timestamp absolute first	Configures the use of the first timestamp as a nonkey field for a flow record.
Step 61	collect transport tcp {option map | window-size {sum | minimum | maximum} | maximum-segment-size} Example: Router(config-flow-record)# collect connection performance initiator network-delay sum	Configures the total network delay for the Mediatrace initiator as a nonkey field for a flow record.
Step 62	end Example: Router(config-flow-record)# end	Exits flow record configuration mode and returns to privileged EXEC mode.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    flow monitor type performance-monitor monitor-name

4.    description description

5.    cache {entries| timeout| type}

6.    statistics {packet}

7.    exporter exporter-name

8.    record {record-name| default-rtp| default-tcp|netflow ipv4 original-input}

9.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	flow monitor type performance-monitor monitor-name Example: Device(config)# flow monitor type performance-monitor FLOW-MONITOR-2	Creates a flow monitor and enters flow monitor configuration mode. This command also allows you to modify an existing flow monitor.
Step 4	description description Example: Device(config-flow-monitor)# description Used for monitoring IPv4 traffic	(Optional) Creates a description for the flow monitor.
Step 5	cache {entries| timeout| type} Example: Device(config-flow-monitor)# cache timeout 20	(Optional) Creates a cache for the flow monitor.
Step 6	statistics {packet} Example: Device(config-flow-monitor)# statistics	(Optional) specifies whether statistics are collected for the flow monitor.
Step 7	exporter exporter-name Example: Device(config-flow-monitor)# exporter export-4	Specifies the flow exporter for the flow monitor.
Step 8	record {record-name| default-rtp| default-tcp|netflow ipv4 original-input} Example: Device(config-flow-monitor)# record default-rtp	Specifies the flow record for the flow monitor.
Step 9	end Example: Device(config-flow-monitor)# end	Exits flow monitor configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    class-map class-name

4.    description description

5.    match {access-group {access-group | name access-group-name} | any | class-map class-map-name | cos cos-value | destination-address mac address | discard-class class-number | dscp dscp-value | flow {direction | sampler} | fr-de | fr-dlci dlci-number | input-interface interface-name | ip {rtp starting-port-number port-range | precedence | dscp} | mpls experimental topmost number | not match-criterion| packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]} | precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4} | protocol protocol-name | qos-group qos-group-value | source-address mac address-destination| vlan {vlan-id | vlan-range | vlan-combination}}

6.    rename class-name

7.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	class-map class-name Example: Device(config)# class-map class-4	Specifies a class to include in the policy. Repeat this command for each class that you want to include in the policy.
Step 4	description description Example: Device(config-cmap)# description match any packets	(Optional) Creates a description for the flow class.
Step 5	match {access-group {access-group | name access-group-name} | any | class-map class-map-name | cos cos-value | destination-address mac address | discard-class class-number | dscp dscp-value | flow {direction | sampler} | fr-de | fr-dlci dlci-number | input-interface interface-name | ip {rtp starting-port-number port-range | precedence | dscp} | mpls experimental topmost number | not match-criterion| packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]} | precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4} | protocol protocol-name | qos-group qos-group-value | source-address mac address-destination| vlan {vlan-id | vlan-range | vlan-combination}} Example: Device(config-cmap)# match any	Specifies the classification criteria. For more information and examples, see the Cisco Media Monitoring Command Reference.
Step 6	rename class-name Example: Device(config-cmap)# rename class-4	Specifies a new name for the flow class.
Step 7	end Example: Device(config-cmap)# end	Exits the current configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    policy-map type performance-monitor policy-name

4.    parameter-map type performance-monitor system-default-aor

5.    class {class-name | class-default}

6.    flow monitor monitor-name

7.    monitor metric ip-cbr

8.    rate layer3 {byte-rate {bps | kbps | mbps | gbps} | packet}

9.    exit

10.    monitor metric rtp

11.    clock-rate {type-number | type-name | default} rate

12.    max-dropout number

13.    max-reorder number

14.    min-sequential number

15.    ssrc maximum number

16.    exit

17.    monitor parameters

18.    flows number

19.    interval duration number

20.    history number

21.    timeout number

22.    exit

23.    react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate}

24.    action {snmp | syslog}

25.    alarm severity {alert | critical | emergency | error | info}

26.    alarm type {discrete | grouped {count number | percent number}

27.    threshold value {ge number | gt number | le number | lt number | range rng-start rng-end}

28.    description description

29.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	policy-map type performance-monitor policy-name Example: Device(config)# policy-map type performance-monitor FLOW-MONITOR-4	Creates a policy and enters policy configuration mode. This command also allows you to modify an existing policy.
Step 4	parameter-map type performance-monitor system-default-aor Example: Device(config-pmap)# parameter-map type performance-monitor system-default-aor	Creates a parameter map for Performance Monitor. The only map available is the system-default -aor map
Step 5	class {class-name | class-default} Example: Device(config-pmap)# class class-4	Specifies a class to include in the policy. Repeat this command for each class that you want to include in the policy.
Step 6	flow monitor monitor-name Example: Device(config-pmap-c)# flow monitor FLOW-MONITOR-4	Enters flow monitor configuration mode. If you do not want to use an existing flow monitor, you can use the inline option to configure a new one, as described in the Configuring a Flow Policy for Cisco Performance Monitor Without Using an Existing Flow Monitor.
Step 7	monitor metric ip-cbr Example: Device(config-pmap-c)# monitor metric ip-cbr	(Optional) Enters IP-CBR monitor metric configuration mode.
Step 8	rate layer3 {byte-rate {bps | kbps | mbps | gbps} | packet} Example: Device(config-pmap-c-mipcbr)# rate layer3 248 mbps	(Optional) Specifies the rate for monitoring the metrics. byte-rate --Data rate in Bps, kBps, mBps, or gBps. The range is 1 to 65535. packet --Packet rate in packets per second.
Step 9	exit Example: Device(config-pmap-c-mipcbr)# exit	Returns to policy class configuration mode.
Step 10	monitor metric rtp Example: Device(config-pmap-c)# monitor metric rtp	Enters RTP monitor metric configuration mode.
Step 11	clock-rate {type-number | type-name | default} rate Example: Device(config-pmap-c-mrtp)# clock-rate 8 9600	Specifies the clock rate used to sample RTP video-monitoring metrics. For more information about the clock-type numbers and names, see the Cisco Media Monitoring Command Reference. The range for rate is 1 kHz to 192 kHz.
Step 12	max-dropout number Example: Device(config-pmap-c-mrtp)# max-dropout 2	Specifies the maximum number of dropouts allowed when sampling RTP video-monitoring metrics.
Step 13	max-reorder number Example: Device(config-pmap-c-mrtp)# max-reorder 4	Specifies the maximum number of reorders allowed when sampling RTP video-monitoring metrics.
Step 14	min-sequential number Example: Device(config-pmap-c-mrtp)# min-sequential 2	Specifies the minimum number of sequential packets required to identify a stream as being an RTP flow.
Step 15	ssrc maximum number Example: Device(config-pmap-c-mrtp)# ssrc maximum 20	Specifies the maximum number of SSRCs that can be monitored within the same flow. A flow is defined by the protocol, source/destination address, and source/destination port).
Step 16	exit Example: Device(config-pmap-c-mrtp)# exit	Returns to policy class configuration mode.
Step 17	monitor parameters Example: Device(config-pmap-c)# monitor parameters	Enters monitor parameters configuration mode.
Step 18	flows number Example: Device(config-pmap-c-mparam)# flows 40	Specifies the maximum number of flows for each monitor cache.
Step 19	interval duration number Example: Device(config-pmap-c-mparam)# interval duration 40	Specifies the interval, in seconds, between samples taken of video-monitoring metrics.
Step 20	history number Example: Device(config-pmap-c-mparam)# history 4	Specifies the number of historical buckets of collected video-monitoring metrics.
Step 21	timeout number Example: Device(config-pmap-c-mparam)# timeout 20	Specifies the number of intervals before a stopped flow is removed from the database.
Step 22	exit Example: Device(config-pmap-c-mparam)# exit	Returns to policy class configuration mode.
Step 23	react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate} Example: Device(config-pmap-c)# react 41 rtp-jitter-average	Enters a mode where you can specify what reaction occurs when a threshold is violated for the following metrics: ID-- ID for react configuration. Range is 1 to 65535. media-stop --No traffic is found for the flow. mrv --Ratio calculated by dividing the difference between the actual rate and the expected rate, by the expected rate. rtp-jitter-average --Average jitter. transport-packets-lost-rate --Ratio calculated by dividing the number of lost packets by the expected packet count.
Step 24	action {snmp | syslog} Example: Device(config-pmap-c-react)# action syslog	Specifies how violations of the thresholds with be reported.
Step 25	alarm severity {alert | critical | emergency | error | info} Example: Device(config-pmap-c-react)# alarm severity critical	Specifies which level of alarm will be reported. The default setting is info.
Step 26	alarm type {discrete | grouped {count number | percent number} Example: Device(config-pmap-c-react)# alarm type discrete	Specifies which types of levels are considered alarms that require reporting. The default setting is discrete.
Step 27	threshold value {ge number | gt number | le number | lt number | range rng-start rng-end} Example: Device(config-pmap-c-react)# threshold value ge 20	Specifies which types of threshold values are considered alarms that require reporting. If no value is set but the application name is configured as a key field, then the system uses the value for the threshold that it finds in the default map. If no value is set and the application name is not configured as a key field, then the default value is used for the threshold. If more than one react command is configured for the same policy and class but only one of the react configurations has threshold values set, then the values of the configured react take precedence and the rest of the threshold values are ignored. If more than one react command is configured for the same policy and none of them have the threshold value configured, then the default threshold value is applied for the configuration with the lowest react ID.
Step 28	description description Example: Device(config-cmap-c-react)# description rtp-jitter-average above 40	(Optional) Creates a description for the reaction.
Step 29	end Example: Device(config-pmap-c-react)# end	Exits the current configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    policy-map type performance-monitor policy-name class class-name

4.    parameter-map type performance-monitor system-default-aor

5.    class {class-name | class-default}

6.    flow monitor inline

7.    record {record-name | default-rtp | default-tcp}

8.    exporter exporter-name

9.    exit

10.    monitor metric ip-cbr

11.    rate layer3 {byte-rate {bps | kbps | mbps | gbps} | packet}

12.    exit

13.    monitor metric rtp

14.    clock-rate {type-number| type-name} rate

15.    max-dropout number

16.    max-reorder number

17.    min-sequential number

18.    ssrc maximum number

19.    exit

20.    monitor parameters

21.    flows number

22.    interval duration number

23.    history number

24.    timeout number

25.    exit

26.    react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate}

27.    action {snmp | syslog}

28.    alarm severity {alert | critical | emergency | error | info}

29.    alarm type {discrete | grouped {count number | percent number}

30.    threshold value {ge number | gt number | le number | lt number | range rng-start rng-end

31.    description description

32.    end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	policy-map type performance-monitor policy-name class class-name Example: Device(config)# policy-map type performance-monitor FLOW-MONITOR-4	Creates a policy and enters policy configuration mode. This command also allows you to modify an existing policy.
Step 4	parameter-map type performance-monitor system-default-aor Example: Device(config-pmap)# parameter-map type performance-monitor system-default-aor	Creates a parameter map for Performance Monitor. The only map available is the system-default -aor map
Step 5	class {class-name | class-default} Example: Device(config-pmap)# class class-4	Specifies a class to include in the policy. Repeat this command for each class that you want to include in the policy.
Step 6	flow monitor inline Example: Device(config-pmap-c)# flow monitor inline	Enters inline mode and enables you to configure a new flow monitor.
Step 7	record {record-name | default-rtp | default-tcp} Example: Device(config-pmap-c-flowmon)# record default-tcp	Specifies a flow record to associate with the flow monitor.
Step 8	exporter exporter-name Example: Device(config-pmap-c-flowmon)# exporter exporter-4	Specifies a flow record to associate with the flow exporter.
Step 9	exit Example: Device(config-pmap-c-flowmon)# exit	Returns to policy class configuration mode.
Step 10	monitor metric ip-cbr Example: Device(config-pmap-c)# monitor metric ip-cbr	(Optional) Enters IP-CBR monitor metric configuration mode.
Step 11	rate layer3 {byte-rate {bps | kbps | mbps | gbps} | packet} Example: Device(config-pmap-c-mipcbr)# rate layer3 248 mbps	(Optional) Specifies the rate for monitoring the metrics. byte-rate--Data rate in Bps, kBps, mBps, or gBps. The range is 1 to 65535. packet--Packet rate in packets per second.
Step 12	exit Example: Device(config-pmap-c-mipcbr)# exit	Returns to policy class configuration mode.
Step 13	monitor metric rtp Example: Device(config-pmap-c)# monitor metric rtp	Enters RTP monitor metric configuration mode.
Step 14	clock-rate {type-number| type-name} rate Example: Device(config-pmap-c-mrtp)# clock-rate 8 9600	Specifies the clock rate used to sample RTP video-monitoring metrics. For more information about the clock-type numbers and names, see the Cisco Media Monitoring Command Reference. The range for rate is 1 kHz to 192 kHz.
Step 15	max-dropout number Example: Device(config-pmap-c-mrtp)# max-dropout 2	Specifies the maximum number of dropouts allowed when sampling RTP video-monitoring metrics.
Step 16	max-reorder number Example: Device(config-pmap-c-mrtp)# max-reorder 4	Specifies the maximum number of reorders allowed when sampling RTP video-monitoring metrics.
Step 17	min-sequential number Example: Device(config-pmap-c-mrtp)# min-sequential 2	Specifies the minimum number of sequential packets required to identify a stream as being an RTP flow.
Step 18	ssrc maximum number Example: Device(config-pmap-c-mrtp)# ssrc maximum 20	Specifies the maximum number of SSRCs that can be monitored within the same flow. A flow is defined by the protocol, source/destination address, and source/destination port).
Step 19	exit Example: Device(config-pmap-c-mrtp)# exit	Returns to policy class configuration mode.
Step 20	monitor parameters Example: Device(config-pmap-c)# monitor parameters	Enters monitor parameters configuration mode.
Step 21	flows number Example: Device(config-pmap-c-mparam)# flows 40	Specifies the maximum number of flows for each monitor cache.
Step 22	interval duration number Example: Device(config-pmap-c-mparam)# interval duration 40	Specifies the duration of the intervals, in seconds, for collecting monitoring metrics.
Step 23	history number Example: Device(config-pmap-c-mparam)# history 4	Specifies the number of historical intervals of collected monitoring metrics to display.
Step 24	timeout number Example: Device(config-pmap-c-mparam)# timeout 20	Specifies the number intervals before a stopped flow is removed from the database.
Step 25	exit Example: Device(config-pmap-c-mparam)# exit	Returns to policy class configuration mode.
Step 26	react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate} Example: Device(config-pmap-c)# react 41 rtp-jitter-average	Enters a mode where you can specify what reaction occurs when a threshold is violated for the following metrics: ID--ID for react configuration. Range is 1 to 65535. media-stop--No traffic is found for the flow. mrv--Ratio calculated by dividing the difference between the actual rate and the expected rate, by the expected rate. rtp-jitter-average--Average jitter. transport-packets-lost-rate--Ratio calculated by dividing the number of lost packets by the expected packet count.
Step 27	action {snmp | syslog} Example: Device(config-pmap-c-react)# action syslog	Specifies how violations of the thresholds with be reported.
Step 28	alarm severity {alert | critical | emergency | error | info} Example: Device(config-pmap-c-react)# alarm severity critical	Specifies which level of alarm will be reported.The default setting is info.
Step 29	alarm type {discrete | grouped {count number | percent number} Example: Device(config-pmap-c-react)# alarm severity critical	Specifies which types of levels are considered alarms that require reporting. The default setting is discrete.
Step 30	threshold value {ge number | gt number | le number | lt number | range rng-start rng-end Example: Device(config-pmap-c-react)# threshold value ge 20	Specifies which types of threshold values are considered alarms that require reporting. If no value is set but the application name is configured as a key field, then the system uses the value for the threshold that it finds in the default map. If no value is set and the application name is not configured as a key field, then the default value is used for the threshold. If more than one react command is configured for the same policy and class but only one of the react configurations has threshold values set, then the values of the configured react take precedence and the rest of the threshold values are ignored. If more than one react command is configured for the same policy and none of them have the threshold value configured, then the default threshold value is applied for the configuration with the lowest react ID.
Step 31	description description Example: Device(config-cmap-c-react)# description rtp-jitter-average above 40	(Optional) Creates a description for the reaction.
Step 32	end Example: Device(config-pmap-c-react)# end	Exits the current configuration mode and returns to privileged EXEC mode.

• Troubleshooting Tips