Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Loopback-based performance monitoring for IPv6 endpoints

Want to summarize with AI?

Log in

Explains how hardware-offloaded loopback probes measure IPv6 endpoint latency, loss, liveness, and ECMP paths without remote monitoring support or PTP clock synchronization.


A loopback-based performance monitoring mechanism for IPv6 endpoints is an SRv6 network monitoring capability that

  • measures round-trip latency, packet loss, and liveness for IPv6 endpoints

  • uses a loopback mechanism to remove the need for performance monitoring or STAMP support on the destination endpoint, and

  • operates without Precision Time Protocol (PTP) synchronization between the sender and destination endpoints.

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

Loopback-based performance monitoring for IPv6 endpoints

Release 26.3.1

Introduced in this release on: Fixed Systems (8200 [ASIC: Q200, P100], 8700 [ASIC: P100, K100], 8010 [ASIC: A100]); Centralized Systems (8600 [ASIC: Q200]); Modular Systems (8800 [LC ASIC: Q200, P100])

You can now simplify IPv6 endpoint performance monitoring by eliminating the need to configure remote devices, enable IPM or STAMP support on those endpoints, or synchronize clocks with PTP. IPM loopback mode uses hardware-offloaded SRv6 probes to measure latency, packet loss, and liveness, and uses flow-label spraying to validate available Equal-Cost Multipath (ECMP) paths. The feature provides high-precision performance metrics through hardware-based timestamping and exports real-time results through telemetry and syslog alerts.

Network  visibility gaps in IPv6 endpoint monitoring

Traditional one-way Integrated Performance Measurement (IPM) deployments require the destination endpoint to participate in measurement processing and often require PTP synchronization between the source and destination. These requirements can limit performance monitoring for legacy devices, third-party endpoints, or endpoints that cannot run active measurement software.

In an ECMP environment, standard connectivity checks may validate only one network path, which can hide degradation on other ECMP paths. Loopback mode helps address this gap by using sender-hosted probes that can be distributed across ECMP paths without requiring remote endpoint configuration or clock synchronization.

The sender node hosts the IPM loopback session and offloads probe generation, timestamping, and metric calculation to the NPU. Only liveness is calculated in real time. Latency and packet loss are calculated after each alternate-marking interval.

Benefits  of loopback-based performance monitoring for IPv6 endpoints

Loopback-based performance monitoring offers these benefits:

  • Simplified deployment: Monitors legacy or third-party IPv6 endpoints without requiring IPM, STAMP, endpoint configuration, or PTP synchronization on the destination.

  • Comprehensive path coverage: Uses flow-label spraying to distribute probes across ECMP paths and detect path-specific degradation.

  • High-scale performance: Offloads probe generation, timestamping, and metric calculation to the NPU to preserve system processor resources.

  • High-precision metrics: Uses hardware timestamping at NPU ingress and egress points to calculate latency and packet-loss metrics.

  • Seamless observability: Exports real-time performance data through telemetry and syslog alerts for existing monitoring systems.

IPM loopback and IPM one-way comparison

Table 2. IPM loopback and IPM one-way comparison

Feature

IPM loopback

IPM one-way

Peer requirement

The destination endpoint does not need to support IPM or STAMP.

The destination endpoint must be an active IPM-capable receiver.

PTP synchronization

PTP synchronization is not required between the sender and destination endpoint.

PTP synchronization is required between the sender and destination endpoint.

Processing location

Latency, loss, and liveness calculations occur on the sender node. The receiver does not perform measurement processing.

The sender and receiver participate in timestamping and processing.

Scalability

Sessions can be hosted for endpoints that do not support active receiver capability, because the destination endpoint only needs to return the probes through the configured reverse path.

Scale is limited by the requirement for active receiver capability at the destination endpoint.

Measurement scope

Measures aggregate round-trip performance across the forward and reverse paths.

Measured in one direction only.


How loopback-based performance monitoring for IPv6 endpoints works

Summary

The key components involved in the process are:

  • Sender node: Hosts the performance monitoring session, generates probes, and calculates measurement metrics.

  • Destination endpoint: Receives probes, decapsulates them, and returns probes via the configured reverse path using labels.

  • Network infrastructure: Forwards probes along the selected ECMP path to reach the destination endpoint.

The SRv6 performance measurement workflow involves the sender node generating hardware-level probes with SRv6 routing information and sending them across ECMP paths to the destination. The destination decapsulates and returns the probes using reverse labels. The sender calculates latency, packet loss, and liveness metrics by offloading probe handling to the NPU. Liveness is calculated in real time, while latency and packet loss are computed after intervals. The sender exports this data for monitoring, and no processing is required at the destination

Workflow

These are the stages of loopback-based performance monitoring for IPv6 endpoints works.

  1. The sender node generates performance measurement probes at the hardware level.

  2. The sender node encapsulates the probes with SRv6 routing information.

  3. The network forwards the probes across the selected ECMP path toward the IPv6 destination endpoint.

  4. The destination endpoint receives the probes, decapsulates them, and uses the configured reverse labels to return the probes to the sender node.

  5. The sender node receives the returning probes and calculates round-trip latency, packet loss, and liveness metrics. No timestamping or measurement processing occurs on the destination endpoint.

  6. The system exports the calculated performance metrics to external monitoring systems for analysis and alerting.


Restrictions for loopback-based performance monitoring for IPv6 endpoints

  • For the endpoint address type, if only endpoint addresses are configured without a segment-list, the endpoint must support SRv6 encapsulation for loopback mode. Native IPv6 endpoints do not work in loopback mode. For IPM one-way mode, both configurations are supported.

  • Do not mix IPM one-way mode and IPM loopback mode under the same endpoint.

  • Do not use IPM loopback mode for IPv4 endpoints, Segment Routing over MPLS (SR-MPLS) encapsulation, or VXLAN.

  • Use IPM loopback mode for round-trip metrics only. The system cannot derive per-direction latency and packet-loss metrics from loopback sessions.


Configure IPM loopback mode for IPv6 endpoints

Use this task to configure IPM loopback mode for IPv6 endpoint monitoring.

Procedure

  1. Configure the global IPM alternate-marking interval on the target node.

    This configuration is optional. The valid range is 60 to 600 seconds, and the default value is 60 seconds.

    Example:

    Router# configure 
    Router(config)# performance-measurement 
    Router(config-perf-meas)# ipm 
    Router(config-perf-meas-ipm)# alternate-marking interval 60 
    Router(config-perf-meas-ipm)# commit 
  2. Configure the IPM profile for loopback mode.

    Example:

    Router(config-perf-meas)# ipm-profile name profile-loopback 
    Router(config-pm-ipm-profile)# ipm-mode loopback 
    Router(config-pm-ipm-profile)# ipm-sender 
    Router(config-pm-ipm-sender)# probe-interval 999 
    Router(config-pm-ipm-sender)# dscp 48 
    Router(config-pm-ipm-sender)# flow-label spray 
    Router(config-pm-ipm-sender)# commit 

    Use the transmit-disabled option under the IPM sender profile to stop probe transmission on a node and make the node operate as a receiver-only node. The transmit-disabled is not supported on IPM loopback. All other profile configurations are the same as in one-way mode.

    Do not configure the expected-probe-interval in the receiver profile when using loopback mode.

  3. Configure the IPM session on the target node.

    Example:

    Router(config-perf-meas)# endpoint ipv6 2020::2 
    Router(config-pm-ep)# source-address ipv6 2020::1 
    Router(config-pm-ep)# ip-measurement 
    Router(config-pm-ep-ipm)# session-id 49153 
    Router(config-pm-ep-ipm-sid)# ipm-profile profile-loopback 
    Router(config-pm-ep-ipm-sid)# segment-routing traffic-eng segment-list FWD-LIST-SRV6 
    Router(config-pm-ep-ipm-sid)# commit 

    The reverse path segment list is optional in loopback mode. You can configure the reverse path in one of these ways:

    • Under the IPM session: segment-routing traffic-eng reverse-path segment-list rev_sl

    • Under the endpoint: segment-routing traffic-eng explicit reverse-path segment-list name

    By default, all IPM loopback sessions use the endpoint-level reverse path, unless a specific reverse path is configured for an individual session.

  4. Verify the IPM configuration and session status.

    Example:

    
    Router# show performance-measurement endpoint ipm sender brief 
            
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    0/RP0/CPU0
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    SSID  Endpoint Name                                     FL    Tx (Block 0)    Tx (Block 1)   Status  
    ------------------------------------------------------------------------------------------------------------------------------- 
    1100  IPv6-2::1-vrf-default                              Spray 4148673         4103012        Run     
    1200  IPv6-2::1-vrf-default                              Spray 4153494         4103008         Run     
    1300  IPv6-2::1-vrf-default                              Spray 4108296         4103003         Run     
    100   IPv6-3::1-vrf-default                              Spray 4117516         4102998         Run     
    500   IPv6-3::1-vrf-default                              Spray 4152            4099            Run     
    1400  IPv6-3::1-vrf-default                              Spray 4148672         4102988         Run     
    1600  IPv6-3::1-vrf-default                              Spray 4152944         4102973         Run     
    1700  IPv6-3::1-vrf-default                              Spray 4138762         4102969         Run     
    400   IPv6-fccc:cc00:1:fe10::-vrf-default                Spray 4108125         4102965         Run     
    700   IPv6-fccc:cc00:1:fe10::-vrf-default                Spray 4153995         4102964         Run     
    600   IPv6-fccc:cc00:1:fea0::-vrf-default                Spray 4128992         4102961         Run     
    200   IPv6-fccc:cc00:3::-vrf-default                     Spray 4157804         4102958         Run     
    1500  IPv6-fccc:cc00:3::1-vrf-default                    Spray 4142822         4102943         Run     
    800   IPv6-fccc:cc00:fe10:fed0::-vrf-default             Spray 4123229         4102940         Run     
    1000  IPv6-fccc:cc00:fe10:fed0:fe11:3::-vrf-default      Spray 4143724         4102937         Run     
    900   IPv6-fccc:cc00:fe10:fed0:fe11::-vrf-default        Spray 4113458         4102934         Run     
    300   IPv6-fccc:cc01:3::-vrf-default                     Spray 4143623         4102932         Run 
    Router#show performance-measurement endpoint ipm receiver brief      
    
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    0/RP0/CPU0
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Session ID  Rx (Block 0)  Rx (Block 1)  Liveness  EMA Loss  Min/Max/EMA Latency             
    --------------------------------------------------------------------------------------------- 
    1100        0             0             Down      -         -/-/-                           
    1200        0             0             Down      -         -/-/-                           
    1300        0             65065         Up        0         0/8/4                           
    100         0             65065         Up        0         0/8/4                           
    500         0             0             Down      -         -/-/-                           
    1400        0             65065         Up        0         0/8/4                           
    1600        0             0             Down      -         -/-/-                           
    1700        0             0             Down      -         -/-/-                           
    400         0             0             Down      -         -/-/-                           
    700         0             0             Down      -         -/-/-                           
    600         0             0             Down      -         -/-/-                           
    200         0             65065         Up        0         0/8/4                           
    1500        0             0             Down      -         -/-/-                           
    800         0             0             Down      -         -/-/-                           
    1000        0             0             Down      -         -/-/-                           
    900         0             0             Down      -         -/-/-                           
    300         0             65065         Up        0         0/8/4
    Router#show performance-measurement ipm sessions 1300 detail private           
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    0/RP0/CPU0
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Endpoint name: IPv6-2::1-vrf-default
      Description                 : Not set
      Endpoint                    : 2::1
      VRF name                    : default
      Source address              : 1::1
      VRF ID                      : 0x60000000
      Routing table ID            : 0xe0800000
    
      Session ID                  : 1300
        Profile name              : Default
        Destination port          : 15104
        Source port               : 15104
        Flow-label                : Spray
        DSCP                      : 48
        Internal label            : 26075
        Internal label context    : 3556769795
        Segment-list              : sl-mix-uA-uN
            fccc:cc00:1:fe30::/64
              Format: f3216
            fccc:cc00:3::/48
              Format: f3216
        NPU information
          NPU number              : 0
          NPU session state       : Session created
          Retry count             : 0
        Sender information:
          Status                  : Created
          Alternate marking interval (seconds): 65
          Total TX packets counter:
            Alternate marking bit 0: 4173377
            Alternate marking bit 1: 4168068
        Receiver information:
          Status                  : Created
          Alternate marking information:
            Receiving bit: 1 (May 08 2026 14:21:37.759)
            Notifications from NPU:
              Redundant: 0
              Out of order: 0
          Liveness information:
            Status: Up (since May 08 2026 12:04:08.019)
          Last interval loss information:
            Alternate marking bit: 0 (May 08 2026 14:21:37.759)
            RX packets:
              Estimate expected: 65065
              Actual: 65065
              Loss: 0
            EMA loss ratio(%): 0
            Current marking change timestamp (ns): 1778250097759322000
            Previous marking change timestamp (ns): 1778250032757790000
          Last interval latency information (uSec):
            Min: 0
            Max: 8 (May 08 2026 14:21:37.762)
            Estimated median: 4
            Estimated average: 4
            EMA latency: 4