Cisco 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:

• Error Messages--These messages indicate PfR operational failures and communication problems that can impact normal PfR operation.
• Debug Messages--These messages are used to monitor detailed PfR operations to diagnose operational or software problems.
• Notification Messages--These messages indicate that PfR is performing a normal operation.
• Warning Messages--These messages indicate that PfR is functioning properly but an event outside of PfR may be impacting normal PfR operation.

Note	With CSCtx06699, PfR syslog levels are added to minimize the number of messages displayed, and a syslog notice is added to display when 30 percent of the traffic classes are out-of-policy.

Note

With CSCts74631, PfR syslog levels are added to minimize the number of messages displayed, a syslog notice is added to display when 30 percent of the traffic classes are out-of-policy, and new syslog alerts are added for a PfR version mismatch, an MC-BR authentication error, and when minimum PfR requirements are not met and the master controller is disabled because there are less than two operational external interfaces.

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.

Although 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:

• Periodic--A traceroute probe is triggered for each new probe cycle. The probe is sourced from the current exit of the traffic class when the option to probe only one exit is selected. If the option to probe all exits is selected, the traceroute probe is sourced from all available exits.
• Policy based--A traceroute probe is triggered automatically when a traffic class goes into an out-of-policy state. Traceroute reporting can be enabled for all traffic classes specified in the match clause of an PfR map. Policy based traceroute reporting stops when the traffic class returns to an in-policy state.
• On demand--A trace route probe can be triggered on an on demand basis when periodic traceroute reporting is not required, or the per-hop statistics are not required for all paths. Using optional keywords and arguments of the show pfr master prefix command, you can start traceroute reporting for a specific traffic class on a specific path, or all paths.

1.    enable


2.    configure terminal


3.    pfr master


4.    traceroute probe-delay milliseconds


5.    exit


6.    pfr-map map-name sequence-number


7.    match pfr learn {delay | throughput}


8.    set traceroute reporting [policy {delay | loss | unreachable}]


9.    end


10.    show pfr master prefix [detail | learned [delay | throughput] | prefix [detail | policy | traceroute [exit-id | border-address | current] [now]]]

Router> enable

Router# configure terminal

Router(config)# pfr master 

Router(config-pfr-mc)# traceroute probe-delay 500 

Router(config-pfr-mc)# exit 

Router(config)# pfr-map TRACEROUTE 10

Router(config-pfr-map)# match pfr learn delay 

Router(config-pfr-map)# set traceroute reporting 

Router(config-pfr-map)# end 

Router# show pfr master prefix 10.5.5.5 traceroute now