Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

PDF

Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

Create static Tree-SID policies

Updated: August 4, 2025

Want to summarize with AI?

Log in

This section provides Tree-SID policy configuration examples and steps to create a static Tree-SID policy.

Before you begin

If you plan to use affinities, collect affinity information from your devices. Map the affinities in Cisco Crosswork Network Controller before creating a static Tree-SID policy. For more information, see Configure TE link affinities.

To create a static Tree-SID policy that represents a leaf or a root node, complete these steps:

Procedure

1.

From the main menu, choose Services & Traffic Engineering > Traffic Engineering > Tree-SID and click Create.

2.

Enter or select the required Tree-SID policy values. To view a description of a field, hover the mouse pointer over the Field Help icon icon.

Note

You can only add PCC nodes with a PCEP session to PCE as root nodes.

Figure 1. Create static tree-SID policy

Create static Tree-SID policy
3.

To commit the policy, click Provision.

4.

Validate the Tree-SID policy creation.

  1. Confirm that the new Tree-SID policy appears in the Traffic engineering table. To highlight the policy on the map, select the check box next to the policy.

    Note

    Depending on the network size and performance, the newly provisioned Tree-SID policy may take some time to appear in the Traffic engineering table. The table refreshes every 30 seconds.

    Figure 2. Newly added tree-SID policy on topology map

    Newly added tree-SID policy on topology map

  2. View and confirm the new Tree-SID policy details. From the Actions column, click More icon and select View details.

    Figure 3. Tree-SID policy details

    Tree-SID policy details

Static Tree-SID policy configuration

The following output shows a static Tree-SID policy configured from the Crosswork Network Controller UI on the compute SR-PCE.

RP/0/RP0/CPU0:cw-xrv56#sh pce lsp p2mp                                                                
      
Tree: 50-52-54, Root: 3.3.3.50 
  PCC: 3.3.3.50
  Label:   505254
  Operational: up  Admin: up  Compute: Yes
  Local LFA FRR: Disabled
  Metric Type: IGP
  Transition count: 1
  Uptime: 00:01:45 (since Thu Apr 27 10:54:49 PDT 2023)
  Destinations: 3.3.3.52, 3.3.3.54
  Nodes:
    Node[0]: 3.3.3.50 (cw-xrv50)
      Delegation: PCC
      PLSP-ID: 205
      Role: Ingress
      Hops:
        Incoming: 505254 CC-ID: 1
        Outgoing: 505254 CC-ID: 1 (11.1.28.54) [cw-xrv54]
        Outgoing: 505254 CC-ID: 1 (11.1.1.51) [cw-xrv51]
    Node[1]: 3.3.3.54 (cw-xrv54)
      Delegation: PCC
      PLSP-ID: 148
      Role: Egress
      Hops:
        Incoming: 505254 CC-ID: 2
    Node[2]: 3.3.3.51 (cw-xrv51)
      Delegation: PCC
      PLSP-ID: 187
      Role: Transit
      Hops:
        Incoming: 505254 CC-ID: 3
        Outgoing: 505254 CC-ID: 3 (11.1.2.52) [cw-xrv52]
    Node[3]: 3.3.3.52 (cw-xrv52)
      Delegation: PCC
      PLSP-ID: 247
      Role: Egress
      Hops:
        Incoming: 505254 CC-ID: 4

The below output shows the same static Tree-SID policy as viewed on the High Availability (HA) peer SR-PCE.

RP/0/RP0/CPU0:cw-xrv63#sh pce lsp p2mp
      
Tree: 50-52-54, Root: 3.3.3.50 
  PCC: 3.3.3.50
  Label:   505254
  Operational: standby  Admin: up  Compute: No
  Local LFA FRR: Disabled
  Metric Type: IGP
  Transition count: 0
  Destinations: 3.3.3.52, 3.3.3.54
  Nodes:
    Node[0]: 3.3.3.54 (cw-xrv54)
      Delegation: PCE (3.3.3.56)
      PLSP-ID: 148
      Role: Egress
      Hops:
        Incoming: 505254 CC-ID: 2
    Node[1]: 3.3.3.52 (cw-xrv52)
      Delegation: PCE (3.3.3.56)
      PLSP-ID: 247
      Role: Egress
      Hops:
        Incoming: 505254 CC-ID: 4
    Node[2]: 3.3.3.51 (cw-xrv51)
      Delegation: PCE (3.3.3.56)
      PLSP-ID: 187
      Role: Transit
      Hops:
        Incoming: 505254 CC-ID: 3
        Outgoing: 505254 CC-ID: 3 (11.1.2.52)
    Node[3]: 3.3.3.50 (cw-xrv50)
      Delegation: PCE (3.3.3.56)
      PLSP-ID: 205
      Role: Ingress
      Hops:
        Incoming: 505254 CC-ID: 1
        Outgoing: 505254 CC-ID: 1 (11.1.28.54)
        Outgoing: 505254 CC-ID: 1 (11.1.1.51)