Configure Performance Measurement

Table 1. Feature History

Feature Name

Release Information

Description
Segment Routing Performance Measurement Delay Measurement Using RFC 5357 (TWAMP Light)

Cisco IOS XE Bengaluru 17.4

This feature enables hardware timestamping. The Performance Measurement (PM) for link delay uses the light version of Two-Way Active Measurement Protocol (TWAMP) over IP and UDP defined in Appendix I of RFC 5357. TWAMP provides an alternative for interoperability when RFC 6374 is not used.

Segment Routing Absolute One-Way Link Loss Measurement for GRE-IPSec Tunnel

Cisco IOS XE Dublin 17.10.1a

This feature provides a mechanism for link loss measurement for point-to-point GRE-IPSec tunnel, in order to identify paths that meet specified loss criteria.

Network performance metrics such as packet loss, delay, delay variation, and bandwidth utilization are a critical measure for traffic engineering (TE) in service provider networks. These metrics provide network operators with information about characteristics of their networks for performance evaluation and helps to ensure compliance with service level agreements. The service-level agreements (SLAs) of service providers depend on the ability to measure and monitor these network performance metrics. Network operators can use the performance measurement (PM) feature to monitor the network metrics for links as well as end-to-end TE label switched paths (LSPs).

The following table explains the functionalities supported by the performance measurement feature for measuring delay for links or SR policies.

Table 2. Performance Measurement Functionalities

Functionality

Details

Probe and burst scheduling

Schedule probes and configure metric advertisement parameters for delay measurement.

Metric advertisements

 Advertise measured metrics periodically using configured thresholds. Also supports accelerated advertisements using configured thresholds.

Measurement history and counters

Maintain packet delay and loss measurement history and also session counters and packet advertisement counters.

Link Delay Measurement

The PM for link delay uses the light version of Two-Way Active Measurement Protocol (TWAMP) over IP and UDP defined in Appendix I of RFC 5357. Hence, only TWAMP test sessions are implemented and not the TWAMP control protocol. TWAMP provides an alternative for interoperability when RFC 6374 is not used. TWAMP packets are carried over IP and UDP. Thus, the dependency on MPLS dataplane is eliminated.

The following figure explains the PM query and response for link delay.

Figure 1. Performance Measurement for Link Delay

The PM query and response for link delay can be described in the following steps:

  1. The local-end router sends PM query packets periodically to the remote side once the egress line card on the router applies timestamps on packets.

  2. Ingress line card on the remote-end router applies time-stamps on packets as soon as they are received.

  3. The remote-end router sends the PM packets containing time-stamps back to the local-end router. The remote-end router time-stamps the packet just before sending it for two-way measurement.

Restrictions and Usage Guidelines for PM for Link Delay

The following restrictions and guidelines apply for the PM for link delay feature for different links.

  • For broadcast links, only point-to-point (P2P) links are supported. P2P configuration on IGP is required for flooding the value.

  • As ASR 1000 platforms do not support PTP 1588v2 clock, it can not use the (T2-T1) to calculate the One-way delay value. Therefore, Two-way Delay value is divided by 2 to calculate the One-way delay value.

    • Two-Way Delay = (T2 – T1) + (T4 – T3)

    • One-Way Delay = ((T2 – T1) + (T4 – T3))/2

PM Link Delay: Default Values for Different Parameters

The default values for the different parameters in the PM for link delay is given as follows:

  • probe: The default mode for probe is two-way delay measurement.

  • interval: The default probe interval is 30 seconds. The range is from 30 to 3600 seconds.

  • burst count: The default value is 10 and range is from 1 to 30.

  • burst interval: The default value is 3000 milliseconds and the range is from 30 to 15000 milliseconds.

  • periodic advertisement: Periodic advertisement is enabled by default.

  • periodic-advertisement interval: The default value is 120 seconds and the interval range is from 30 to 3600 seconds.

  • periodic-advertisement threshold: The default value of periodic advertisement threshold is 10 percent.

  • periodic-advertisement minimum: The default value is 1000 microseconds (usec) and the range is from 0 to 100000 microseconds.

  • accelerated advertisement: Accelerated advertisement is disabled by default.

  • accelerated-advertisement threshold: The default value is 20 percent and the range is from 0 to 100 percent.

  • accelerated-advertisement minimum: The default value is 1000 microseconds and the range is from 1 to 100000 microseconds.

Configuration Example: PM for Link Delay

This example shows how to configure performance-measurement functionalities for link delay as a global default profile. 


R1(config)#performance-measurement
R1(config-perf-meas)# delay-profile interfaces

R1(config-pm-dm-intf)#advertisement
R1(config-pm-dm-intf-adv)# accelerated // Default: Disabled
R1(config-pm-dm-intf-adv-acc)#threshold 40 //Default 20%
R1(config-pm-dm-intf-adv-acc)#minimum-change 1000 //Default 1000uSec
R1(config-pm-dm-intf-adv)#periodic
R1(config-pm-dm-intf-adv-per)#interval 100 //Default 120seconds
R1(config-pm-dm-intf-adv-per)#threshold 40 //Default 10%
R1(config-pm-dm-intf-adv-per)#minimum-change 1000 //Default 1000 uSec
R1(config-pm-dm-intf)#probe

R1(config-pm-dm-intf-probe)#computation-interval 40 // Def: 30s
R1(config-pm-dm-intf-probe)#burst-interval 40 // Def: 3000 mSec
R1(config-perf-meas)#delay-profile sr-policy
R1(config-pm-dm-srpol)#advertisement
R1(config-pm-dm-sr-adv)#accelerated // Default: Disabled
R1(config-pm-dm-sr-adv-acc)#threshold 40 //Default 40%
R1(config-pm-dm-sr-adv-acc)#minimum-change 4000 // Def: 500 uSec
R1(config-pm-dm-sr-adv)#periodic

R1(config-pm-dm-srpol-adv-per)#interval 100 // Def: 120 sec
R1(config-pm-dm-srpol-adv-per)#threshold 40 // Def: 10%
R1(config-pm-dm-srpol-adv-per)#minimum-change 2000 // Def: 500 uSec
R1(config-pm-dm-srpol)#probe
R1(config-pm-dm-srpol-probe)#computation-interval 40 // Def: 30s
R1(config-pm-dm-srpol-probe)#burst-interval 40 // Def: 3000 mSec
R1(config-pm-dm-srpol-probe)#exit

R1(config-pm-dm-srpol)#exit

R1(config-pm-dm-srpol-adv-per)#exit
R1 R1(config-pm-dm-intf-probe)#exit
R1(config-pm-dm-intf-adv)#exit

R1(config-pm-dm-intf)#exit

R1(config-perf-meas)#exit

This example shows how to enable PM for link delay over an interface.

R1(config)#performance-measurement 
R1(config-perf-meas)#interface GigabitEthernet 0/0/1
R1(config-pm-intf)#delay-measurement 
R1(config-pm-intf-dm)#exit
R1(config-pm-intf-dm)#next-hop ipv4 10.50.62.1
R1(config-pm-intf)#exit

Verification: PM Link Delay Configuration

This example shows how to use the show performance-measurement summary [detail] command to verify the PM for link-delay configuration. 


R1#show performance-measurement summary detail 
Total interfaces                              : 3
Maximum PPS                                   : 100 pkts/sec

Interface Delay-Measurement:
  Total sessions                              : 3
  Profile configuration:
    Measurement Type                          : Two-Way
    Computation interval                      : 30 seconds
    Burst interval                            : 3000 mSec
    Burst count                               : 10 packets
    Protocol                                  : TWAMP-Lite Unauth
    HW Timestamp Supported                    : No
    Periodic advertisement                    : Enabled
      Interval                                : 30 (effective: 30) sec
      Threshold                               : 100%
      Minimum-Change                          : 100000 uSec
    Accelerated advertisement                 : Enabled
      Threshold                               : 100%
      Minimum-Change                          : 100000 uSec
    Threshold crossing check                  : Minimum-delay
  Counters:
    Packets:
      Total sent                              : 293020
      Total received                          : 293016
    Errors:
        TX:
          Total interface down                : 0
          Total no MPLS caps                  : 0
          Total no IP address                 : 0
          Total other                         : 19
        RX:
          Total negative delay                : 144
          Total delay threshold exceeded      : 0
          Total missing TX timestamp          : 0
          Total missing RX timestamp          : 0
          Total probe full                    : 0
          Total probe not started             : 0
          Total control code error            : 0
          Total control code notif            : 0
    Probes:
      Total started                           : 29306
      Total completed                         : 29155
      Total incomplete                        : 148
      Total advertisements                    : 3

Global Delay Counters:
  Total packets sent                          : 293020
  Total query packets received                : 293016
  Total invalid session id                    : 0
  Total no session                            : 0

HW Support for MPLS-GAL [RFC6374] timestamp   : No
HW Support for TWAMP [RF5357] timestamp       : No
HW Support for 64 bit timestamp               : No
HW Support for IPv4 UDP Cheksum               : No

This example shows how to use the show performance-measurement interfaces [interface-name] [detail] command to verify the PM for link-delay configuration. 

R1#show performance-measurement interfaces detail 
Interface Name: GigabitEthernet0/2/3 (ifh: 0xA)
  Delay-Measurement           : Enabled
  Local IPV4 Address          : 10.50.62.2
  Local IPV6 Address          : ::
  State                       : Up

  Delay Measurement session:
    Session ID                : 1

    Last advertisement:
      Advertised at: 09:21:08  12 2019 (439879 seconds ago)
      Advertised reason: Advertise delay config
      Advertised delays (uSec): avg: 2000, min: 2000, max: 2000, variance: 0

    Next advertisement:
      Check scheduled at the end of the current probe (roughly every 30 seconds)
      No probes completed
      Rolling average (uSec): 3146

    Current Probe:
      Started at 11:32:17  17 2019 (10 seconds ago)
      Packets Sent: 4, received: 4
      Measured delays (uSec): avg: 1999, min: 1500, max: 2499, variance: 499
      Probe samples:
              Packet Rx Timestamp Measured Delay
                11:32:17  17 2019 1999999       
                11:32:20  17 2019 1500000       
                11:32:23  17 2019 2499999       
                11:32:26  17 2019 1999999       
      Next probe scheduled at 11:32:46  17 2019 (in 19 seconds)
      Next burst packet will be sent in 1 seconds
R1#

You can also use the following commands for verifying the PM for link delay on the local-end router.

Command

Description

show performance-measurement history interfaces [nameinterface-name] probe

Displays the PM link-delay probe history for interfaces.

show performance-measurement history interfaces [nameinterface-name] aggr

Displays the PM link-delay aggregated history for interfaces.

show performance-measurement counters interface [nameinterface-name] [detail]

Displays the PM link-delay session counters.

show performance-measurement responder interfaces [nameinterface-name]

Displays PM for link-delay for interfaces on the remote-end router.

show performance-measurement responder counters interface [nameinterface-name]

Displays the PM link-delay session counters on the remote-end router.

End-to-End Delay Measurement

Table 3. Feature History

Feature Name

Release Information

Description
Segment Routing Performance Measurement End-to-End Delay Measurement

Cisco IOS XE Bengaluru 17.4

This feature allows to monitor the end-to-end delay experienced by the traffic sent over a Segment Routing policy. This feature ensures the delay does not exceed the specified threshold value and violate the SLAs. Use this feature to apply extended TE link delay metric (minimum delay value) to compute paths for Segment Routing policies as an optimization metric or as an accumulated delay bound.

Starting from Cisco IOS XE Release 17.4.1, end-to-end delay measurement feature is introduced for Segment Routing Performance Management. Use this feature to monitor the end-to-end delay experienced by the traffic sent over a Segment Routing policy. This feature ensures the delay does not exceed the specified threshold value and violate the SLAs. You can verify the end-to-end delay values before activating the candidate-path or the segment-list of the Segment Routing policy in the forwarding table. You can also use the end-to-end delay values to deactivate the active candidate-path or the segment-list of the Segment Routing Policy in the forwarding table. Use this feature to apply extended TE link delay metric (minimum delay value) to compute paths for Segment Routing policies as an optimization metric or as an accumulated delay bound.

The following figure explains the PM query and response for end-to-end delay measurement.

Figure 2. Performance Measurement for End-to-End Delay Measurement

The PM query and response for end-to-end delay measurement can be described in the following steps:

  1. The querier router sends PM query packets periodically to the responder router once the egress line card on the router applies timestamps on packets.

  2. Ingress line card on the responder router applies time-stamps on packets when they are received.

  3. The end-to-end delay value of an SR Policy is different than the path computation result (the sum of TE link delay metrics) due to several factors like queuing delay within the routers.

  4. The remote-end router sends the PM packets containing time-stamps back to the local-end router. The remote-end router time-stamps the packet just before sending it for two-way measurement.

  5. The local-end router time-stamps the packet as soon as the packet is received for two-way measurement.

Configuration Example: PM for End-to-End Delay Management

These examples show how to configure on-demand segment routing policy for end-to-end delay management. 
#show running-config | s on-demand color 800
on-demand color 800 --------------------------------------------------------> SR ODN Policy
authorize
performance-measurement -------------------------------------------------> SR PM CLI
delay-measurement -----------------------------------------------------------> SR PM CLI
candidate-paths
preference 1
constraints
segments
dataplane mpls
!
!
dynamic
pcep
metric
type delay
!
!
!
#

#show segment-routing traffic-eng policy name *10.216.216.216|800

Name: *10.216.216.216|800 (Color: 800 End-point: 10.216.216.216)
Owners : BGP
Status:
Admin: up, Operational: up for 01:27:24 (since 11-29 04:41:36.053)
Candidate-paths:
Preference 1 (BGP):
Dynamic (pce 10.12.12.12) (active)
Weight: 0, Metric Type: DELAY
Metric Type: DELAY, Path Accumulated Metric: 330
16011 [Prefix-SID, 10.205.205.205]
1133 [Adjacency-SID, 10.50.72.1 - 10.50.72.2]
16009 [Prefix-SID, 10.216.216.216]
Attributes:
Binding SID: 1218
Allocation mode: dynamic
State: Programmed
IPv6 caps enabled
#

This example shows how to configure performance-measurement functionalities for end-to-end delay management as a global default profile. 


R1(config)#performance-measurement
R1(config-perf-meas)#delay-profile sr-policy

R1(config-pm-dm-srpol)#probe
R1(config-pm-dm-srpol-probe)#computation-interval 40

R1(config-pm-dm-srpol-probe)#burst-interval 40

R1(config-pm-dm-srpol-probe)#protocol twamp-light
R1(config-pm-dm-srpol-probe-protocol)#exit

R1(config-pm-dm-srpol-probe)#exit
R1(config-pm-dm-srpol)#advertisement periodic

R1(config-pm-dm-srpol-adv-per)#interval 100
R1(config-pm-dm-srpol-adv-per)#threshold 20

R1(config-pm-dm-srpol-adv-per)#minimum-change 500

R1(config-pm-dm-srpol-adv-per)#exit

R1(config-pm-dm-sr-adv)#exit

R1(config-pm-dm-srpol)#advertisement accelerated

R1(config-pm-dm-sr-adv-acc)#threshold 40

R1(config-pm-dm-sr-adv-acc)#minimum-change 1000

R1(config-pm-dm-sr-adv-acc)#exit
R1(config-pm-dm-sr-adv)#exit

R1(config-pm-dm-srpol)#exit

R1(config-perf-meas)#exit

Verification: PM End-to-End Delay Management Configuration

This example shows how to use the show performance-measurement summary command to verify the PM for end-to-end delay management configuration. 


R1#show performance-measurement summary 
Total interfaces                              : 6
Total SR Policies                             : 1
Maximum PPS                                   : 1000 pkts/sec
  
SR Policy Delay-Measurement:
  Total sessions                              : 1
  Profile configuration:
    Measurement Type                          : Two-Way
    Computation interval                      : 30 seconds
    Burst interval                            : 3000 mSec
    Burst count                               : 10
    Protocol                                  : TWAMP-Lite Unauth
    HW Timestamp Supported                    : Yes
    Periodic advertisement                    : Enabled
      Interval                                : 30 (effective: 30) sec
      Threshold                               : 15%
      Minimum-Change                          : 600 uSec
    Accelerated advertisement                 : Enabled
      Threshold                               : 25%
      Minimum-Change                          : 900 uSec
    Threshold crossing check                  : Minimum-delay
  Counters:
    Packets:
      Total sent                              : 334
      Total received                          : 0
    Errors:
      Total sent errors                       : 0
      Total received errors                   : 0
    Probes:
      Total started                           : 33
      Total completed                         : 0
      Total incomplete                        : 33
      Total advertisements                    : 0
 
Global Delay Counters:
  Total packets sent                          : 1251
  Total query packets received                : 917
  Total invalid session id                    : 0
  Total no session                            : 0
         
HW Support for MPLS-GAL [RFC6374] timestamp   : No
HW Support for TWAMP [RF5357] timestamp       : Yes
HW Support for 64 bit timestamp               : Yes
HW Support for IPv4 UDP Cheksum               : No
R1#

Sample show Commands

R1#show performance-measurement interfaces detail
Interface Name: GigabitEthernet2 (ifh: 0x8)
Delay-Measurement : Enabled
Local IPV4 Address : 10.0.0.74
Local IPV6 Address : ::
State : Up
Delay Measurement session:
Session ID : 2
Last advertisement:
Advertised at: 06:45:50 02 2020 (214 seconds ago)
Advertised reason: First advertisement
Advertised delays (uSec): avg: 227, min: 198, max: 263, variance: 29
Next advertisement:
Check scheduled in 1 more probe (roughly every 160 seconds)
Aggregated delays (uSec): avg: 250, min: 208, max: 301, variance: 38
Rolling average (uSec): 254
Current Probe:
Started at 06:49:14 02 2020 (10 seconds ago)
Packets Sent: 3, received: 3
Measured delays (uSec): avg: 243, min: 230, max: 265, variance: 13
Probe samples:
Packet Rx Timestamp Measured Delay
06:49:22 02 2020 265500
06:49:18 02 2020 230000
06:49:14 02 2020 233500
Next probe scheduled at 06:49:54 02 2020 (in 30 seconds)
Next burst packet will be sent in 2 seconds
R1#show performance-measurement history interfaces name Gi2 probe
Interface Name: GigabitEthernet2 (ifh: 0x8)
  Delay-Measurement history (uSec):
        Probe Start Timestamp Pkt(TX/RX) Average   Min       Max      
            06:48:34  02 2020 10/10      254       216       301      
            06:47:54  02 2020 10/10      246       208       282      
            06:47:14  02 2020 10/10      262       182       380      
            06:46:34  02 2020 10/10      278       201       360      
            06:45:54  02 2020 10/10      274       202       364      
            06:45:14  02 2020 10/10      227       198       263

R1#show performance-measurement history interfaces name Gi2 aggr
Interface Name: GigabitEthernet2 (ifh: 0x8)
  Delay-Measurement history (uSec):
        Aggregation Timestamp Average   Min       Max       Action       
            06:47:50  02 2020 259       182       380       NONE


R1#show performance-measurement counters interface name Gi2 detail
Interface Name: GigabitEthernet2 (ifh: 0x8)
  Delay-Measurement:
    Packets:
      Total sent                              : 67
      Total received                          : 67
    Errors:
        TX:
          Total interface down                : 0
          Total no MPLS caps                  : 0
          Total no IP address                 : 0
          Total other                         : 0
        RX:
          Total negative delay                : 0
          Total delay threshold exceeded      : 0
          Total missing TX timestamp          : 0
          Total missing RX timestamp          : 0
          Total probe full                    : 0
          Total probe not started             : 0
          Total control code error            : 0
          Total control code notif            : 0
    Probes:
      Total started                           : 6
      Total completed                         : 6
      Total incomplete                        : 0
      Total advertisements                    : 1


R1#show segment-routing traffic-eng policy all
Name: *10.2.2.2|100 (Color: 100 End-point: 10.2.2.2)
  Owners : BGP
  Status:
    Admin: up, Operational: up for 03:14:11 (since 12-02 03:36:05.290)
  Candidate-paths:
    Preference 100 (BGP):
      Dynamic (active)
        Metric Type: TE, Path Accumulated Metric: 30
          16002 [Prefix-SID, 10.2.2.2]
  Attributes:
    Binding SID: 40
      Allocation mode: dynamic
      State: Programmed
  IPv6 caps enabled


R1#show performance-measurement sr-policy name *10.2.2.2|100 detail
SR Policy name: *10.2.2.2|100
  Color                           : 100
  Endpoint                        : 10.2.2.2
  Source                          : 10.9.9.9
  Number of candidate-paths       : 1
 
  Candidate-Path:
    Preference                    : 100
    Protocol-origin               : BGP
    Discriminator                 : 0
    Active:                       : Yes
    Number of segment-lists       : 1
    Number of atomic paths        : 1
    Max Pkts per Burst            : 4000
    Max Pkts per Probe            : 40000
    AP Min Run per Probe          : 3
    Round-robin bursts            : 1
    Round-robin probes            : 1
    Last advertisement:
      Advertised at: 06:45:52  02 2020 (271 seconds ago)
      Advertised delays (uSec): avg: 860, min: 740, max: 946, variance: 120
    Next advertisement:
      Check scheduled in 1 more probe (roughly every 160 seconds)
      Aggregated delays (uSec): avg: 935, min: 795, max: 1146, variance: 140
    Last probe:
      Packets Sent: 10, received: 10
      Measured delays (uSec): avg: 910, min: 844, max: 1013, variance: 66
    Current Probe:
      Packets Sent: 8, received: 8
      Measured delays (uSec): avg: 949, min: 851, max: 1065, variance: 98
 
    Segment-List:
      Name                        : SegmentList0
      Number of atomic paths      : 1
      Last advertisement:
        Advertised at: 06:45:52  02 2020 (271 seconds ago)
        Advertised delays (uSec): avg: 860, min: 740, max: 946, variance: 120
      Next advertisement:
        Aggregated delays (uSec): avg: 935, min: 795, max: 1146, variance: 140
      Last probe:
        Packets Sent: 10, received: 10
        Measured delays (uSec): avg: 910, min: 844, max: 1013, variance: 66
      Current probe:
        Packets Sent: 8, received: 8
        Measured delays (uSec): avg: 949, min: 851, max: 1065, variance: 98


R1#show performance-measurement sr-policy name *10.2.2.2|100 private
SR Policy name: *10.2.2.2|100
  Color                           : 100
  Endpoint                        : 10.2.2.2
  Source                          : 10.9.9.9
  Number of candidate-paths       : 1
 
  Candidate-Path:
    Preference                    : 100
    Protocol-origin               : BGP
    Discriminator                 : 0
    Active:                       : Yes
    Number of segment-lists       : 1
    Number of atomic paths        : 1
    Max Pkts per Burst            : 4000
    Max Pkts per Probe            : 40000
    AP Min Run per Probe          : 3
    Round-robin bursts            : 1
    Round-robin probes            : 1
    Last advertisement:
      Advertised at: 06:45:52  02 2020 (284 seconds ago)
      Advertised delays (uSec): avg: 860, min: 740, max: 946, variance: 120
    Next advertisement:
      Check scheduled in 4 more probes (roughly every 160 seconds)
      Aggregated delays (uSec): avg: 935, min: 795, max: 1146, variance: 140
    Last probe:
      Packets Sent: 10, received: 10
      Measured delays (uSec): avg: 963, min: 851, max: 1083, variance: 112
    Current Probe:
      Packets Sent: 1, received: 1
      Measured delays (uSec): avg: 925, min: 925, max: 925, variance: 0

R1#show performance-measurement sr-policy name *10.2.2.2|100 verbose
SR Policy name: *10.2.2.2|100
  Color                           : 100
  Endpoint                        : 10.2.2.2
  Source                          : 10.9.9.9
  Number of candidate-paths       : 1
 
  Candidate-Path:
    Preference                    : 100
    Protocol-origin               : BGP
    Discriminator                 : 0
    Active:                       : Yes
    Number of segment-lists       : 1
    Number of atomic paths        : 1
    Max Pkts per Burst            : 4000
    Max Pkts per Probe            : 40000
    AP Min Run per Probe          : 3
    Round-robin bursts            : 1
    Round-robin probes            : 1
    Last advertisement:
      Advertised at: 06:45:52  02 2020 (290 seconds ago)
      Advertised delays (uSec): avg: 860, min: 740, max: 946, variance: 120
    Next advertisement:
      Check scheduled in 4 more probes (roughly every 160 seconds)
      Aggregated delays (uSec): avg: 935, min: 795, max: 1146, variance: 140
    Last probe:
      Packets Sent: 10, received: 10
      Measured delays (uSec): avg: 963, min: 851, max: 1083, variance: 112
    Current Probe:
      Packets Sent: 3, received: 3
      Measured delays (uSec): avg: 911, min: 882, max: 925, variance: 29
 
PE3#show performance-measurement history sr-policy name *10.2.2.2|100  probe
SR Policy name: *10.2.2.2|100
  Candidate-Path:
    Preference                : 100
    Protocol-origin           : BGP
    Discriminator             : 0
    Active                    : Yes
        Probe Start Timestamp Pkt(TX/RX) Average   Min       Max      
            06:49:54  02 2020 10/10      963       851       1083     
            06:49:14  02 2020 10/10      910       844       1013     
            06:48:34  02 2020 10/10      896       795       1019     
            06:47:54  02 2020 10/10      1000      882       1146     
            06:47:14  02 2020 10/10      990       909       1135     
            06:46:34  02 2020 10/10      931       735       1080     
            06:45:54  02 2020 10/10      911       768       1087     
            06:45:14  02 2020 10/10      860       740       946      
    Segment-list:
      Name                    : SegmentList0
          Probe Start Timestamp Pkt(TX/RX) Average   Min       Max      
              06:49:54  02 2020 10/10      963       851       1083     
              06:49:14  02 2020 10/10      910       844       1013     
              06:48:34  02 2020 10/10      896       795       1019     
              06:47:54  02 2020 10/10      1000      882       1146     
              06:47:14  02 2020 10/10      990       909       1135     
              06:46:34  02 2020 10/10      931       735       1080     
              06:45:54  02 2020 10/10      911       768       1087     
              06:45:14  02 2020 10/10      860       740       946      
      Atomic path:
        Hops                  : 10.2.2.2
        Labels                : 16002
        Outgoing Interface    : GigabitEthernet2
        Next Hop              : 10.0.0.73
        Destination           : 10.2.2.2
        Session ID            : 1
            Probe Start Timestamp Pkt(TX/RX) Average   Min       Max      
                06:49:54  02 2020 10/10      963       851       1083     
                06:49:14  02 2020 10/10      910       844       1013     
                06:48:34  02 2020 10/10      896       795       1019     
                06:47:54  02 2020 10/10      1000      882       1146     
                06:47:14  02 2020 10/10      990       909       1135     
                06:46:34  02 2020 10/10      931       735       1080     
                06:45:54  02 2020 10/10      911       768       1087     
                06:45:14  02 2020 10/10      860       740       946


R1#show performance-measurement history sr-policy name *10.2.2.2|100  aggr
SR Policy name: *10.2.2.2|100
  Candidate-Path:
    Preference                : 100
    Protocol-origin           : BGP
    Discriminator             : 0
    Active                    : Yes
        Aggregation Timestamp Average   Min       Max       Action       
            06:50:32  02 2020 942       795       1146      NONE         
            06:47:52  02 2020 922       735       1135      NONE         
    Segment-list:
      Name                    : SegmentList0
          Aggregation Timestamp Average   Min       Max       Action       
              06:50:32  02 2020 942       795       1146      NONE         
              06:47:52  02 2020 922       735       1135      NONE         
      Atomic path:
        Hops                  : 10.2.2.2
        Labels                : 16002
        Outgoing Interface    : GigabitEthernet2
        Next Hop              : 10.0.0.73
        Destination           : 10.2.2.2
        Session ID            : 1
            Aggregation Timestamp Average   Min       Max       Action       
                06:50:32  02 2020 942       795       1146      NONE         
                06:47:52  02 2020 922       735       1135      NONE