Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

PDF

Cisco Crosswork Network Controller 7.2 Traffic Engineering and Optimization

SR-MPLS and SRv6 policies on the topology map

Want to summarize with AI?

Log in

This section provides an overview of the Traffic Engineering user interface in Crosswork Network Controller, and how it enables viewing and managing SR-MPLS and SRv6 policies on the topology map.


The Traffic Engineering (TE) topology map in Crosswork Network Controller is a powerful visualization tool designed to empower network operators with deep insights into their network’s structure and active TE policies. By providing a clear and intuitive graphical representation of Segment Routing Traffic Engineering (SR-TE) policies and RSVP-TE tunnels, it significantly reduces the complexity of provisioning and managing these traffic engineering mechanisms. This visualization enhances operators’ understanding of traffic flows, resource utilization, and overall network performance, enabling more effective traffic management, optimization, and troubleshooting.

To open the Traffic Engineering topology map, choose Services & Traffic Engineering > Traffic Engineering.

From the Traffic engineering table, select the SR-MPLS or SRv6 policy you want to view on the map. You can select up to 10 policies that will appear as separate colored links.

Figure 1. Traffic engineering UI: SR-MPLS and SRv6 policies


The table describes the callouts for the Traffic Engineering topology map for SR-MPLS and SRv6 policies.

Callout no. Description

1

Select the appropriate check box to enable these options:

  • Show IGP path: Displays the IGP path for the selected SR-TE policy.

  • Show Participating only: Displays only links that belong to selected SR-TE policy. All other links and devices are hidden.

2

Device outlines: A device with an orange (Node SID) outline indicates there is a node SID associated with that device or a device in the cluster.

3

When SR-TE policies are selected in the SR-MPLS or SRv6 tables, they show as colored directional lines on the map indicating source and destination.

An adjacency segment ID (SID) is shown as an orange circle on a link along the path ( Adjacency SID ).

4

SR-MPLS and SRv6 policy origin and destination: If both A and Z are displayed in a device cluster, at least one node in the cluster is a source, and another is a destination.

  • A+ denotes multiple SR-TE policies originating from a node.

  • Z+ denotes multiple SR-TE policies terminating at a node.

5

Window content: The window content depends on the selected or filtered items. In this example, the SR-MPLS tab shows SR Policy table. Depending on the map selection, you can create, modify, or view policies.

6

Tabs: Click the SR-MPLS or SRv6 tab to view the corresponding list of SR-TE policies.

7

Export function: Exports all data into a CSV file. You cannot export selected or filtered data.

8

Mini dashlets: Summarizes the operational SR-MPLS or SRv6 policy status and displays the number of PCC and PCE-initiated tunnels listed in the SR Policy table. When you select a dashlet, filters are applied and the policy table updates to display data corresponding to the filtered dashlet.

9

Group filter: Controls how group filters apply to table data. For example, if Headend only is selected, the table only displays policies where the policy’s headend device is in the selected group. This filter helps you efficiently manage policies in large networks.

Filter options:

  • Headend or Endpoint: Show policies with either the headend or endpoint device in the selected group.

  • Headend and Endpoint: Show policies if both the headend and endpoint are in the group.

  • Headend only: Show policies if the headend device of the policy is in the selected group.

  • Endpoint only: Show policies if the endpoint device of the policy is in the selected group.