Performance Routing Traceroute Reporting
|
|||||||||||||||||||||||||||
Contents
Performance Routing Traceroute ReportingLast Updated: November 11, 2011
Performance Routing (PfR) support for traceroute reporting allows you to monitor prefix performance on a hop-by-hop basis. Delay, loss, and reachability measurements are gathered for each hop from the probe source (border router) to the target prefix.
Finding Feature InformationYour 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. Information About Performance Routing Traceroute ReportingPfR Logging and ReportingCisco IOS PfR supports standard syslog functions. The notice level of syslog is enabled by default. System logging is enabled and configured in Cisco IOS software under global configuration mode. The logging(PfR) command in PfR master controller or PfR border router configuration mode is used only to enable or disable system logging under PfR. PfR system logging supports the following message types:
To modify system, terminal, destination, and other system global logging parameters, use the logging commands in global configuration mode. For more information about global system logging configuration, see to the "Troubleshooting, Logging, and Fault Management" section of the Cisco IOS Network Management Configuration Guide . PfR Troubleshooting Using Traceroute ReportingAlthough PfR provides the ability to diagnose issues using syslog and debug command-line interface (CLI) commands, support for traceroute reporting was introduced in the OER Support for Cost-Based Optimization and Traceoute Reporting feature. Using traceroute reporting, PfR reports traffic class performance by determining the delay on a hop-by-hop basis using traceroute probes. Prior to traceroute reporting there was no method for measuring the delay per hop for situations such as an unexpected round trip delay value being reported for a traffic class on an exit link. PfR uses UDP traceroutes to collect per-hop delay statistics. A traceroute is defined as tracing the route to the device with the given IP address or the hostname and is useful in detecting the location of a problem that exists in the path to the device. Although traditional UDP-based traceroutes are used by default, PfR can be configured to send TCP SYN packets to specific ports that may be permitted through a firewall. Traceroute reporting is configured on the master controller. Traceroute probes are sourced from the border router exit. This feature allows you to monitor traffic class performance on a hop-by-hop basis. When traceroute reporting is enabled, the autonomous system number, the IP address, and delay measurements are gathered for each hop from the probe source to the target prefix. By default, traceroute probes are sent only when the traffic class goes OOP. TCP-based traceroutes can be configured manually and the time interval between traceroute probes can be modified. By default, per-hop delay reporting is not enabled. Traceroute probes are configured using the following methods:
How to Configure Performance Routing Traceroute ReportingConfiguring PfR Traceroute ReportingPerform this task at the master controller to configure traceroute reporting. When using a PfR active probe there are situations when a host address does not respond to the PfR probe message. The reason for no response to the probe message may be due to a firewall or other network issue but PfR assumes the host address to be unreachable and releases control of the prefix. Prior to traceroute reporting there was no method for measuring the delay per hop for situations such as an unexpected round trip delay value being reported for a traffic class on an exit link. The solution for both the non-responding target address and the lack of per-hop delay information involves using UDP, and optionally TCP, traceroutes. Traceroute reporting is configured on a master controller, but the traceroute probes are sourced from the border router exits. In this task, the three methods of configuring traceroute probes are used. Periodic and policy-based traceroute reporting are configured with the set traceroute reporting (PfR) command using a PfR map. On-demand traceroute probes are triggered by entering the show pfr master prefix command with certain parameters. This task also shows to modify the time interval between traceroute probes using the traceroute probe-delay (PfR) command. When traceroute reporting is enabled, the default time interval between traceroute probes is 1000 milliseconds. DETAILED STEPS Configuration Examples for Performance Routing Traceroute ReportingExample Configuring PfR Traceroute ReportingThe following example, starting in global configuration mode, configures continuous traceroute reporting for traffic classes learned on the basis of delay: Router(config)# pfr master Router(config-pfr-mc)# traceroute probe-delay 10000 Router(config-pfr-mc)# exit Router(config)# pfr-map TRACE 10 Router(config-pfr-map)# match pfr learn delay Router(config-pfr-map)# set traceroute reporting Router(config-pfr-map)# end The following example, starting in privileged EXEC mode, initiates an on-demand traceroute probe for the 10.5.5.5 prefix:
Router# show pfr master prefix 10.5.5.55 traceroute current now
Path for Prefix: 10.5.5.0/24 Target: 10.5.5.5
Exit ID: 2, Border: 10.1.1.3 External Interface: Et1/0
Status: DONE, How Recent: 00:00:08 minutes old
Hop Host Time(ms) BGP
1 10.1.4.2 8 0
2 10.1.3.2 8 300
3 10.5.5.5 20 50
Where to Go NextFor information about other Performance Routing features or general conceptual material, see the documents in the "Related Documents" section. Additional ReferencesRelated Documents
Technical Assistance
Feature Information for Performance Routing Traceroute ReportingThe 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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2010-2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||