Cisco Crosswork Network Controller 7.2 Network Bandwidth Management

PDF

Configure circuit-style SR policies

Updated: January 30, 2026

Want to summarize with AI?

Log in

Overview

Use this procedure to manually configure a circuit-style SR policy and a PM profile on a device.

A circuit-style SR policy configuration must include the destination endpoint, the amount of requested bandwidth, and the bidirectional attribute (see Important considerations for circuit-style SR-TE policies for additional requirements or notable constraints). The configuration should also include a Performance Measurement Liveness (PM) profile. A PM profile enables proper detection of candidate path liveness and effective path protection. PCCs do not validate past the first SID, so without PM, the path protection will not occur if the failure in the circuit-style SR policy candidate path is not the first hop in the segment list. For more information, see Configuring SR Policy Liveness Monitoring.

Procedure

1.

If applicable, enable the hardware module on the device for PM configuration.

Example:

hw-module profile offload 4
reload location all
2.

Configure the PM profile.

Example:

performance-measurement
  liveness-profile sr-policy name CS-active-path
    probe
      tx-interval 3300
    !
    npu-offload enable   !! Required for hardware Offload only
    !
  !
  liveness-profile sr-policy name CS-protect-path
    probe
      tx-interval 3300
    !
    npu-offload enable   !! Required for hardware Offload only
    !
  !
!
3.

Configure the Circuit Style SR policy with the PM profile. All configurations shown in the example are required in order for CSM to manage the circuit-style SR-TE policy. Entries that are defined by the user are italicized. See Important considerations for circuit-style SR-TE policies for additional requirements or notable constraints.

Example:


segment-routing
  traffic-eng
    policy cs1-cs4
      performance-measurement
        liveness-detection
          liveness-profile backup name CS-protect  !! Name must match liveness profile defined for Protect path
          liveness-profile name CS-active  !! Name must match liveness profile defined for Active path
      !
      !
      bandwidth 10000
      color 1000
      end-point ipv4 192.168.20.4
      path-protection
      !
      candidate-paths
        preference 10
          dynamic
            pcep
          !
            metric
             type igp
            !
           !
          backup-ineligible
          !
          constraints
            segments
              protection unprotected-only
              adjacency-sid-only
            !
          !
          bidirectional
            co-routed
            association-id 1010
            !
          !
        preference 50
          dynamic
            pcep
            !
            metric
              type igp
              !
            !
          constraints
            segments
              protection unprotected-only
              adjacency-sid-only
              !
            disjoint-path group-id 3
            type node, srlg, or link
            !
            bidirectional
              co-routed
              association-id 1050
              !
             !
        preference 100
          dynamic
            pcep
           !
          metric
           type igp
           !
          !
          constraints
            segments
              protection unprotected-only
              adjacency-sid-only
             !
            disjoint-path group-id 3
            type node, srlg, or link
            !
            bidirectional
              co-routed
              association-id 1100
              !
            !
          !
        !
      !
    !