SR-TE Policy Configuration Sources
SR-TE policies discovered and reported by Crosswork Optimization Engine may have been configured from the following sources:
-
PCC initiated—Policies configured on a PCC (see PCC-Initiated SR-TE Policy Example). This policy type displays as Unknown in the UI.
-
PCE initiated—Policies configured on a PCE or created dynamically by Crosswork Optimization Engine. SR-MPLS explicit or dynamic policies that are configured using the UI are the only types of SR-TE policies that you can modify or delete in Crosswork Optimization Engine. PCE Initiated policy types can be one of the following:
-
Dynamic
-
Explicit
-
Bandwidth on Demand
-
Bandwidth Optimization
-
Local Congestion Mitigation
-
PCC-Initiated SR-TE Policy Example
The following example shows a configuration of an SR-TE policy at the headend router. The policy has a dynamic path with affinity constraints computed by the headend router. See SR configuration documentation for your specific device to view descriptions and supported configuration commands (for example: Segment Routing Configuration Guide for Cisco ASR 9000 Series Routers).
segment-routing
traffic-eng
policy foo
color 100 end-point ipv4 1.1.1.2
candidate-paths
preference 100
dynamic
metric
type te
!
!
constraints
affinity
exclude-any
name RED
!
!
!
!
!