Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
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.
Prerequisites for Configuring Cisco Performance Monitor
The following prerequisites must be met before you can configure Cisco Performance Monitor:
IPv4 Traffic
The networking device must be configured for IPv4 routing.
One of the following must be enabled on your router and on any interfaces on which you want to enable Cisco Performance Monitor: Cisco Express Forwarding or distributed Cisco Express Forwarding.
Configuration Components of 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.
Figure 1
Cisco Performance Monitor Components
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:
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-monitortype flow record.
Configure a flow monitor that includes the flow record and flow exporter. For Cisco Performance Monitor, you must configure a
performance-monitortype flow monitor.
Configure a class to specify the filtering criteria using the
class-map command.
Configure a policy to include one or more classes and one or more
performance-monitortype flow monitors using thepolicy-map command. For Cisco Performance Monitor, you must configure
performance-monitortype policies.
Associate a
performance-monitortype policy to the appropriate interface using the
service-policytypeperformance-monitorcommand.
Data That You Can Monitor Using Cisco Performance Monitor
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
showperformancemonitorstatuscommand 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
SNMP MIB Support for Cisco Performance Monitor
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-serverhost--Enables the delivery of flow monitoring SNMP notifications to a recipient.
snmp-serverenabletrapsflowmon--Enables flow monitoring SNMP notifications. By default, flow monitoring SNMP notifications are disabled.
snmpmibflowmonalarmhistory--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
.
Limitations for the Catalyst 6500 Platform
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.
Table 1
Support for Ingress Interfaces
Interface Type
Support
Layer 3 Routed Port
Yes
Layer 3 Sub-interface (a)
No
Layer 3 port channels
Yes
Layer 3 port-channel sub-interface (a)
No
Layer 3 SVI (b)
Partial (see the third bullet below)
L3 Tunnels
No
Layer 2 Physical (Switched) Ports
Yes
Layer 2 Port-channels
Yes
Layer 2 Vlans
Yes
Table 2
Support for Egress Interfaces
Interface Type
Support
Layer 3 Routed Port
Yes
Layer 3 Sub-interface (a)
Yes
Layer 3 port channels
Yes
Layer 3 port-channel sub-interface (a)
Yes
Layer 3 SVI (b)
Yes
L3 Tunnels
No
Layer 2 Physical (Switched) Ports
No
Layer 2 Port-channels
No
Layer 2 Vlans
Yes
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.
How to Configure Troubleshoot and Maintain Cisco Performance Monitor
Note
Many of the Flexible NetFlow commands, keywords, and arguments used in used in these tasks are available in previous releases. For more information about these existing Flexible NetFlow commands, keywords, and arguments, refer to the
Cisco IOS Flexible NetFlow Command Reference.
Configuring a Flow Exporter for Cisco Performance Monitor
Flow exporters are used to send the data that you collect with Cisco Performance Monitor to a remote system such as a NetFlow Collection Engine. Flow exporters use user datagram protocol (UDP) as the transport protocol and use the Version 9 export format.
To configure a flow exporter for the flow monitor, in order to export the data that is collected by Cisco Performance Monitor to a remote system for further analysis and storage, perform the following optional task. For Cisco Performance Monitor, flow exporters are configured the same way as they are configured for Cisco IOS Flexible NetFlow. For more information. see
Configuring Data Export for Cisco IOS Flexible NetFlow with Flow Exporters.
Note
Each flow exporter supports only one destination. If you want to export the data to multiple destinations, you must configure multiple flow exporters and assign them to the flow monitor.
To check the configuration and status of your flow exporter, use the
showflowexportercommand.
Configuring a Flow Record for Cisco Performance Monitor
The basic concepts and techniques for configuring a flow record for Cisco Performance Monitor are the same as flow records for Flexible NetFlow. The flow record specifies how the data collected data is aggregated and presented. The only significant difference is that, for Cisco Performance Monitor, the command includestypeperformance-monitor.
Router(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.
Router(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.
To check the configuration and status of your flow record, use the
showflowrecordtypeperformance-monitorcommand.
Configuring a Flow Monitor for Cisco Performance Monitor
The basic concepts for configuring a flow monitor for Cisco Performance Monitor are the same as flow monitors for Flexible NetFlow. Each flow monitor has a separate cache assigned to it and requires a record to define the contents and layout of its cache entries.
When you configure a flow monitor, you must use either:
An existing flow record that you configured
One of the following default predefined records:
The default RTP record (default-rtp)
The default TCP record (default-tcp)
Flexible NetFlow's "NetFlow IPv4 original input"
Note
To modify a flow record, you must remove it from all flow monitors it is associated with.
To check the configuration and status of your flow monitor, use the
showflowmonitortypeperformance-monitor command and the
showrunning-configflowmonitor command.
Configuring a Flow Class for Cisco Performance Monitor
The basic concepts and techniques for configuring a class for Cisco Performance Monitor are the same as for any other type of class. The class specifies the filter that determines which flow traffic to monitor. The filter is configured using various match commands in class-map mode.
If you do not already have a flow monitor configured, you can either:
Note
Nested class maps are not supported. In other words, you cannot use the
class-map command while in class-map configuration mode (config-cmap).
To check the configuration and status of your flow class, use the
showpolicy-maptypeperformance-monitororshowclass-mpacommand.
Configuring a Flow Policy for Cisco Performance Monitor Using an Existing Flow Monitor
The basic concepts and techniques for configuring a class for Cisco Performance Monitor are the same as for any other type of class. The class specifies which flow monitor is included. The only significant difference is that, for Cisco Performance Monitor, the
policy-mapcommand includestypeperformance-monitor.
If you do not already have a flow monitor configured or do not want to use any of your existing flow monitors for a new class, you can configure it using the flow monitor inline option and specifying which flow record and flow exporter are included.
(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 8
exit
Example:
Router(config-pmap-c-mipcbr)# exit
Returns to policy class configuration mode.
Step 9
monitormetricrtp
Example:
Router(config-pmap-c)# monitor metric rtp
Enters RTP monitor metric configuration mode.
Step 10
clock-rate{type-number|type-name |
default}rate
Example:
Router(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 11
max-dropoutnumber
Example:
Router(config-pmap-c-mrtp)# max-dropout 2
Specifies the maximum number of dropouts allowed when sampling RTP video-monitoring metrics.
Step 12
max-reordernumber
Example:
Router(config-pmap-c-mrtp)# max-reorder 4
Specifies the maximum number of reorders allowed when sampling RTP video-monitoring metrics.
Step 13
min-sequentialnumber
Example:
Router(config-pmap-c-mrtp)# min-sequential 2
Specifies the minimum number of sequental packets required to identify a stream as being an RTP flow.
Step 14
ssrcmaximumnumber
Example:
Router(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 15
exit
Example:
Router(config-pmap-c-mrtp)# exit
Returns to policy class configuration mode.
Step 16
monitorparameters
Example:
Router(config-pmap-c)# monitor parameters
Enters monitor parameters configuration mode.
Step 17
flowsnumber
Example:
Router(config-pmap-c-mparam)# flows 40
Specifies the maximum number of flows for each monitor cache.
To check the configuration and status of your flow policy, use the
showpolicy-maptypeperformance-monitorcommand.
Configuring a Flow Policy for Cisco Performance Monitor Without Using an Existing Flow Monitor
The basic concepts and techniques for configuring a class for Cisco Performance Monitor are the same as for any other type of class. The class specifies which flow monitor is included. The only significant difference is that, for Cisco Performance Monitor, the
policy-mapcommand includestypeperformance-monitor.
If you do not already have a flow monitor configured or do not want to use any of your existing flow monitors for a new class, you can configure it under the class configuration mode, by specifying which flow record and flow exporter are included.
(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 11
exit
Example:
Router(config-pmap-c-mipcbr)# exit
Returns to policy class configuration mode.
Step 12
monitormetricrtp
Example:
Router(config-pmap-c)# monitor metric rtp
Enters RTP monitor metric configuration mode.
Step 13
clock-rate{type-number|
type-name}
rate
Example:
Router(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 14
max-dropoutnumber
Example:
Router(config-pmap-c-mrtp)# max-dropout 2
Specifies the maximum number of dropouts allowed when sampling RTP video-monitoring metrics.
Step 15
max-reordernumber
Example:
Router(config-pmap-c-mrtp)# max-reorder 4
Specifies the maximum number of reorders allowed when sampling RTP video-monitoring metrics.
Step 16
min-sequentialnumber
Example:
Router(config-pmap-c-mrtp)# min-sequential 2
Specifies the minimum number of sequental packets required to identify a stream as being an RTP flow.
Step 17
ssrcmaximumnumber
Example:
Router(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 18
exit
Example:
Router(config-pmap-c-mrtp)# exit
Returns to policy class configuration mode.
Step 19
monitorparameters
Example:
Router(config-pmap-c)# monitor parameters
Enters monitor parameters configuration mode.
Step 20
flowsnumber
Example:
Router(config-pmap-c-mparam)# flows 40
Specifies the maximum number of flows for each monitor cache.
To check the configuration and status of your flow policy, use the
showpolicy-maptypeperformance-monitorcommand.
Applying a Cisco Performance Monitor Policy to an Interface Using an Existing Flow Policy
Before it can be activated, a Cisco Performance Monitor policy must be applied to at least one interface. To activate a Cisco Performance Monitor policy, perform the following required task.
Router(config-if)# service-policy type performance-monitor input mypolicy-map-4
Example:
Attaches a policy map to an input interface or virtual circuit (VC), or an output interface or VC, to be used as the service policy for that interface or VC.
input--Attaches the specified policy map to the input interface or input VC.
output--Attaches the specified policy map to the output interface or output VC.
policy-name--name of a service policy map (created by the policy-map command) to be attached. The name can be a maximum of 40 alphanumeric characters.
Step 5
end
Example:
Router(config-if)# end
Exits the current configuration mode and returns to privileged EXEC mode.
To check the configuration and status of your service policy, use the follwoign comands:
showperformancemonitorhistory
showperformancemonitorstatus
showpolicy-mapypreperformance-monitorinterface
Applying a Cisco Performance Monitor Policy to an Interface Without Using an Existing Flow Policy
Before it can be activated, a Cisco Performance Monitor policy must be applied to at least one interface. To activate a Cisco Performance Monitor policy, perform the following required task.
Router(config-if)# service-policy type performance-monitor inline input
Attaches a policy map to an input interface or virtual circuit (VC), or an output interface or VC, to be used as the service policy for that interface or VC.
input--Attaches the specified policy map to the input interface or input VC.
output--Attaches the specified policy map to the output interface or output VC.
Specifies an existing flow monitor to associate with a flow policy. If you do not want to use an existing flow monitor, you can use the
inline option to configure a new one.
If needed, you can also use the
inline option to specify a flow record and flow exporter.
Step 7
record{record-name|default-rtp|default-tcp}
Example:
Router(config-spolicy-inline-flowmon)# record default-tcp
(Optional) If you do not want to use an existing flow monitor, and instead used the
inline option, use this command to configure a flow record.
Specifies the minimum number of sequental packets required to identify a stream as being an RTP flow.
Step 18
ssrcmaximumnumber
Example:
Router(config-spolicy-inline-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:
Router(config-spolicy-inline-mrtp)# exit
Returns to service-policy inline configuration mode.
Router(config-spolicy-inline-react)# threshold value ge
Specifies which types of levels values are considered alarms that require reporting.
Step 31
end
Example:
Router(config-spolicy-inline-react)# end
Exits the current configuration mode and returns to privileged EXEC mode.
What to Do Next
To check the configuration and status of your service policy, use the
showperformancemonitorstatuscommand and
showperformancemonitorhistorycommand.
Verifying That Cisco Performance Monitor Is Collecting Data
To verify that Cisco Performance Monitor is collecting data, perform the following optional task.
If no data is being collected, complete the remaining tasks in this section.
Before You Begin
The interface to which you applied the input flow monitor must be receiving traffic that meets the criteria defined by the original flow record before you can display the flows in the flow monitor cache.
For a description of the fields displayed by this command, see
Cisco Media Monitoring Command Reference.
The following example shows the output for one flow policy:
Example:
Policy Map type performance-monitor PM-POLICY-4
Class PM-CLASS-4
flow monitor PM-MONITOR-4
record PM-RECORD-4
exporter PM-EXPORTER-4
monitor parameters
interval duration 30
timeout 10
history 10
flows 8000
monitor metric rtp
min-sequential 5
max-dropout 5
max-reorder 5
clock-rate default 90000
ssrc maximum 5
Table 3
show policy-map type performance-monitor Field Descriptions
Field
Description
Policy Map type performance-monitor
Name of the Cisco Performance Monitor flow policy.
flow monitor
Name of the Cisco Performance Monitor flow monitor.
record
Name of the Cisco Performance Monitor flow record.
exporter
Name of the Cisco Performance Monitor flow exporter.
monitor parameter
Parameters for the flow policy.
interval duration
The configured duration of the collection interval for the policy.
timeout
The configured amount of time wait for a response when collecting data for the policy.
history
The configured number of historical collections to keep for the policy.
flows
The configured number of flows to collect for the policy.
monitor metric rtp
RTP metrics for the flow policy.
min-sequential
The configured mimimum number of packets in a sequence used to classify an RTP flow.
max-dropout
The configured maximum number of packets to ignore ahead of the current packet in terms of sequence number.
max-reorder
The configured maximum number of packets to ignore behind the current packet in terms of sequence number.
clock-rate default
The configured clock rate for the RTP packet timestamp clock that is used to calculate the packet arrival latency.
ssrc maximum
The configured 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. The range is from 1 to 50.
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 theintervaldurationcommand.
To view statistics for other intervals, use the
showperformancemonitorhistory command as described in the next step. For more information about these commands, see the
Cisco Media Monitoring Command Reference
This command displays the statistics collected by Cisco Performance Monitor during any or all intervals, including the current one. The duration of collection intervals is specified by theintervaldurationcommand.
For more information about this command, see the
Cisco Media Monitoring Command Reference.
The following example shows the output for the
showperformancemonitorhistorycommand:
Example:
Codes: * - field is not configurable under flow record
NA - field is not applicable for configured parameters
Match: 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 = 4294967291
Policy: RTP_POL, Class: RTP_CLASS, Interface: GigabitEthernet0/4, Direction: input
start time 14:57:34
============
*history bucket number : 1
*counter flow : 1
counter bytes : 0
counter 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) : NA
counter packets : 0
*counter packets rate per flow : 0
counter packets dropped : 0
routing forwarding-status reason : Unknown
interface input : NA
interface output : NA
monitmeters : true
ipv4 dscp : 0
ipv4 ttl : 57
application media bytes counter : 0
application media packets counter : 0
application 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) : NA
application media packets rate (pps) : 0
application media event : Stop
*transport rtp flow count : 0
transport rtp jitter mean (usec) : NA
transport rtp jitter minimum (usec) : NA
transport rtp jitter maximum (usec) : NA
*transport rtp payload type : 0
transport event packet-loss counter : NA
*transport event packet-loss counter min : NA
*transport event packet-loss counter max : NA
transport packets expected counter : NA
transport packets lost counter : NA
*transport packets lost counter minimum : NA
*transport packets lost rate ( % ) : NA
*transport packets lost rate min ( % ) : NA
*transport packets lost rate max ( % ) : NA
*transport packets lost rate max ( % ) : 0.00
*transport tcp flow count : 1
*transport round-trip-time sum (msec) : 32
*transport round-trip-time samples : 1
transport round-trip-time (msec) : 32
*transport round-trip-time min (msec) : 32
*transport round-trip-time max (msec) : 32
Table 4
show performance monitor status and show performance-monitor history Field Descriptions
Field
Description
history bucket number
Number of the bucket of historical data collected.
counter flow
Number of flows collected.
counter bytes
Total number of bytes collected for all flows.
counter bytes rate
Average number of bytes processed by the monitoring system per second during the monitoring interval for all flows.
counter bytes rate per flow
Average number of bytes processed by the monitoring system per second during the monitoring interval for each flow.
counter bytes rate per flow min
Minimum for the average number of bytes processed per second for each flow.
counter bytes rate per flow max
Maximum threshold for the average number of packets or bits processed per second for each flow.
counter packets
Total number of IP packets processsed for all flows.
counter packets rate per flow
Avrage number of IP packets processed by the monitoring system per second during the monitoring interval for each flow.
counter packets dropped
IP packet drops by monitoring system for this flow.
routing forwarding-status reason
Forwarding status is encoded using eight bits with the two most significant bits giving the status and the six remaining bits giving the reason code.
Status is either unknown (00), Forwarded (10), Dropped (10) or Consumed (11).
The following list shows the forwarding status values for each status category.
Unknown
0
Forwarded
Forward 64
Forwarded Fragmented 65
Forwarded not Fragmented 66
Dropped
Unknown 128
Drop ACL Deny 129
Drop ACL drop 130
Drop Unroutable 131
Drop Adjacency 132
Drop Fragmentation & DF set 133
Drop Bad header checksum 134
Drop Bad total Length 135
Drop Bad Header Length 136
Drop bad TTL 137
Drop Policer 138
Drop WRED 139
Drop RPF 140
Drop For us 141
Drop Bad output interface 142
Drop Hardware 143
Consumed
Unknown 192
Terminate Punt Adjacency 193
Terminate Incomplete Adjacency 194
Terminate For us 195
interface output
Outgoing interface name.
interface input
Incoming interface name.
monitor event
Bit 1 indicates that one of the thresholds specified by a react statement for the flow was crossed at least once in the monitoring interval. Bit 2 indicates that there was a loss-of-confidence in measurement.
ipv4 dscp
IPv4 differentiated services code point (DCSP).
ipv4 ttl
IPv4 time-to-live (TTL).
application media bytes counter
Number of IP bytes from media applications processed for a specific media stream.
application media packets counter
Number of IP packets from media applications processed for a specific media stream.
application media bytes rate
Average media byte rate (Bps) for all flows during the monitoring interval.
application media bytes rate per flow
Average media byte rate (Bps) for each flow during the monitoring interval.
application media bytes rate per flow min
Minimum rate of application media bytes, in Bps, collected per flow.
application media bytes rate per flow max
Maximum rate of application media bytes, in Bps, collected per flow.
application media event
Bit 1 is not used. Bit 2 indicates that no media application packets were seen, in other words, a Media Stop Event occured.
transport rtp flow count
Number of RTP flows collected.
transport rtp jitter mean
Mean deviation of the difference in packet spacing at the receiver compared to the sender for a pair of packets.
transport rtp jitter minimum
Minimum deviation of the difference in packet spacing at the receiver compared to the sender for a pair of packets.
transport rtp jitter maximum
Maximum deviation of the difference in packet spacing at the receiver compared to the sender for a pair of packets.
transport rtp payload type
Code for the payload format. Payload type codes can be defined dynamically or codes for default audio and video format can be used as defined in RFC 3551. An RTP source can change the payload type during a session, but a receiver MUST ignore packets with payload types that it does not understand. Therefore, some measurements taken during monitoring may not be accurate.
transport event packet-loss counter
Number of loss events (number of contiguous sets of lost packets).
transport event packet-loss counter min
Minimum number of packet loss events.
transport event packet-loss counter max
Maximum number of packet loss events.
transport packets expected counter
Number of packets expected.
transport packets lost counter
Number of packets lost.
transport packets lost counter minimum
Minimum threshold for the number of packets lost.
transport packets lost counter maximum
Maximum threshold for the number of packets lost.
transport packets lost rate
Rate of packets lost, in percent .
transport packets lost rate min
Minimum threshold for the percent of packets lost.
transport packets lost rate max
Maximum threshold for the percent of packets lost.
Displaying Information Specific to the Catalyst 6500 Platform
To display or clear information for the Feature Manager and other functionality specific to the Catalyst 6500 platform, perform the following optional task.
This command displays information about dynamic and static policies for a specific host.
Example:
Router# show platform software feature-manager tcam dynamic performance-monitor handle ip 10.1.1.0
-----------------------------------------------------------------------------
HANDLE Feature ID No of entries MD5
-----------------------------------------------------------------------------
10.1.1.0 VM Ingress L3 2
To display the current status of a flow monitor, perform the following optional task.
Before You Begin
The interface to which you applied the input flow monitor must be receiving traffic that meets the criteria defined by the original flow record before you can display the flows in the flow monitor cache.
SUMMARY STEPS
1.enable
2.showflowmonitortypeperformance-monitor
DETAILED STEPS
Step 1
enable
The enablecommand enters privileged EXEC mode (enter the password if prompted).
Example:
Router> enable
Router#
Step 2
showflowmonitortypeperformance-monitor
The showflowmonitortypeperformance-monitorcommand shows the current status of the flow monitor that you specify.
Example:
Router# show flow monitor type performance-monitor
Flow Monitor type performance-monitor monitor-4:
Description: User defined
Flow Record: record-4
Flow Exporter: exporter-4
No. of Inactive Users: 0
No. of Active Users: 0
Verifying the Flow Monitor Configuration
To verify the configuration commands that you entered, perform the following optional task.
Before You Begin
The interface to which you applied the input flow monitor must be receiving traffic that meets the criteria defined by the original flow record before you can display the flows in the flow monitor cache.
SUMMARY STEPS
1.enable
2.showrunning-configflowmonitor
DETAILED STEPS
Step 1
enable
The enablecommand enters privileged EXEC mode (enter the password if prompted).
Example:
Router> enable
Router#
Step 2
showrunning-configflowmonitor
The showrunning-configflowmonitor command shows the configuration commands of the flow monitor that you specify.
Example:
Router# show running-config flow monitor
Current configuration:
!
flow monitor FLOW-MONITOR-1
description Used for basic IPv4 traffic analysis
record netflow ipv4 original-input
!
!
flow monitor FLOW-MONITOR-2
description Used for basic IPv6 traffic analysis
record netflow ipv6 original-input
!
Verifying That Cisco IOS Flexible NetFlow and Cisco Performance Monitor Is Enabled on an Interface
To verify that Flexible NetFlow and Cisco Performance Monitor is enabled on an interface, perform the following optional task.
SUMMARY STEPS
1.enable
2.showflowinterfacetypenumber
DETAILED STEPS
Step 1
enable
The enablecommand enters privileged EXEC mode (enter the password if prompted).
Example:
Router> enable
Router#
Step 2
showflowinterfacetypenumber
The showflowinterfacecommand verifies that Flexible NetFlow and Cisco Performance Monitor is enabled on an interface.
Example:
Router# show flow interface ethernet 0/0
Interface Ethernet0/0
FNF: monitor: FLOW-MONITOR-1
direction: Input
traffic(ip): on
FNF: monitor: FLOW-MONITOR-2
direction: Input
traffic(ipv6): on
Displaying the Flow Monitor Cache
To display the data in the flow monitor cache, perform the following optional task.
Before You Begin
The interface to which you applied the input flow monitor must be receiving traffic that meets the criteria defined by the original flow record before you can display the flow data in the flow monitor cache.
The enablecommand enters privileged EXEC mode (enter the password if prompted).
Example:
Router> enable
Router#
Step 2
showflowmonitornamemonitor-namecacheformatrecord
The showflowmonitornamemonitor-namecacheformatrecord command string displays the status, statistics, and the flow data in the cache for a flow monitor.
Example Monitor for Lost RTP Packets and RTP Jitter
This example show a configuration that monitors the number of lost RTP packets, the amount of RTP jitter, and other basic statistics for the gig1 interface. In this example, Cisco Performance Monitor is also configured to make an entry in the sylog when the any of the following events occur on the interface:
The percentage of lost RTP packets is between 5 percent and 9 percent.
The percentage of lost RTP packets is greater than 10 percent.
A media stop event has occurred.
! Set the filter spec for the flows to monitor.
access-list 101 ip permit host 10.10.2.20 any
! Use the flow record to define the flow keys and metric to collect.
flow record type performance-monitor video-monitor-record
match ipv4 source
match ipv4 destination
match transport source-port
match transport destination-port
match rtp ssrc
collect timestamp
collect counter byte
collect counter packet
collect mse
collect media-error
collect counter rtp interval-jitter
collect counter rtp packet lost
collect counter rtp lost event
! Set the exporting server. The export message format is based on FNFv.9.
flow export video-nms-server
export-protocol netflow-v9
destination cisco-video-management
transport udp 32001
! Set the flow filter in the class-map.
class-map match-all video-class
access-group ipv4 101
! Set the policy map with the type performance-monitor for video monitor.
policy-map type performance-monitor video-monitor
! Set the video monitor actions.
class video-class
! Specify where the metric data is being exported to.
export flow video-nms-server
flow monitor inline
record video-monitor-record
! Set the monitoring modeling parameters.
monitor parameters
! Set the measurement timeout to 10 secs.
interval duration 10
! Set the timeout to 10 minutes.
timeout 10
! Specify that 30 flow intervals can be kept in performance database.
history 30
priority 7
! Set rtp flow verification criteria.
monitor metric rtp
! Configure a RTP flow criteria: at least 10 packets in sequence.
min-sequential 10
! Ignore packets that are more than 5 packet ahead in terms of seq number. max-dropout 5
! Ignore packets that are more than 5 packets behind in terms of seq number.
max-reorder 5
! Set the clock rate frequency for rtp packet timestamp clock.
clock-rate 89000
! Set the maximum number of ssrc sllowed within this class.
ssrc maximum 100
! Set TCA for alarm.
react 100 transport-packets-lost-rate
description critical TCA
! Set the threshold to greater than 10%.
threshold gt 10
! Set the threshold to the average number based on the last five intervals.
threshold type average 5
action syslog
alarm severity critical
react 110 transport-packets-lost-rate
description medium TCA
! Set the threshold to between 5% and 9% of packet lost.
threshold range gt 5 le 9
threshold type average 10
action syslog
alarm type grouped percent 30
react 3000 media-stop
action syslog
alarm severity critical
alarm type grouped percent 30
interface gig1
service-policy type performance-monitor video-mon in
Where to Go Next
For more information about configuring the products in the Medianet product family, see the other chapter in this guide or see the
Cisco Media Monitoring Configuration Guide.
Additional References
Related Documents
Related Topic
Document Title
Design, configuration, and troubleshooting resources for 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
IP addressing commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 5
Feature Information for Cisco Performance Monitor
Feature Name
Releases
Feature Information
Cisco Performance Monitor 1.0
15.1(3)T
12.2(58)SE
15.1(4)M1
15.0(1)SY
This feature 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 your applications' performance.
The following commands were introduced or modified by this feature:
action(policy react and policy inline react),
alarmseverity (policy react and policy inline react),alarmtype(policy react and policy inline react),class-map,clock-rate(policy RTP),collectapplicationmedia,clearfmperformance-monitorcounters,collectcounter,collectflowdirection,collectinterface,collectipv4,collectipv4destination,collectipv4source,collectipv4ttl,collectmonitorevent,collectrouting,collecttimestampinterval,collecttransporteventpacket-losscounter,collecttransportpackets,collecttransportrtpjitter,debugfmperformance-monitorcounters,
debugperformance-monitorcounters,description (Performance Monitor),
destination,dscp (Flexible NetFlow),
export-protocol,exporter,flowmonitortypeperformance-monitor,flowrecordtypeperformance-monitor,flows,history (monitor parameters),
intervalduration,matchaccess-group,matchany,matchclass-map,matchcos,matchdestination-addressmac,matchdiscard-class,matchdscp,matchflow,matchfr-de,matchfr-dlci,matchinput-interface,matchipdscp,matchipprecedence,matchiprtp,matchipv4,matchipv4destination,matchipv4source,matchmplsexperimentaltopmost,matchnot,matchpacketlength (class-map),
matchprecedence,matchprotocol,matchqos-group,matchsource-addressmac,matchtransportdestination-port,matchtransportrtpssrc,matchtransportsource-port,matchvlan,max-dropout (policy RTP),
max-reorder (policy RTP),
min-sequential (policy RTP),
monitormetricip-cbr,monitormetricrtp,monitorparameters,option (Flexible NetFlow),
output-features,platformperformance-monitorrate-limit,
policy-maptypeperformance-monitor,ratelayer3,react (policy),record (Performance Monitor),
rename (policy),
service-policytypeperformance-monitor,showperformancemonitorhistory,showperformancemonitorstatus,showplatformhardwareaclentryinterface,showplatformsoftwareccm,showplatformsoftwarefeature-managerperformance-monitor,showplatformsoftwarefeature-managertcam,showpolicy-maptypeperformance-monitor,
snmp-serverhost,
snmp-serverenabletrapsflowmon,
snmpmibflowmonalarmhistory,source (Flexible NetFlow),
ssrcmaximum,templatedatatimeout,thresholdvalue (policy react and policy inline react),
timeout (monitor parameters),
transport (Flexible NetFlow), and
ttl (Flexible NetFlow).
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.