Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

PDF

Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

SR-TE policy PCC and PCE configuration sources

Want to summarize with AI?

Log in

Distinguishes between policies configured directly on a client and those managed by a controller. While client-initiated policies are often labelled as unknown, the system recognizes specific types like bandwidth on demand, allowing for modification or deletion based on the configuration source.


SR-TE policies that are configured using the UI or API are the only types of policies that you can modify or delete in Crosswork Network Controller. SR-TE policies discovered and reported by Crosswork Network Controller may have been configured from these sources:

  • Path Computation Client (PCC) initiated: Policies configured directly on a PCC (refer to PCC-initiated SR-TE policy example). These policies display as Unknown in the UI because they are not provisioned or managed by Crosswork Network Controller. However, Bandwidth on Demand (BWoD) and Circuit Style (CS) policies are exceptions. These are not labeled as Unknown because Crosswork Network Controller recognizes and categorizes them based on their attributes and purpose, even if they are PCC-initiated.

    Note

    Circuit Style policies are always PCC-initiated.

  • Path Computation Element (PCE) initiated: Policies configured on a PCE or created dynamically by Crosswork Network Controller. Examples of PCE-initiated policy types include:

    • Dynamic

    • Explicit