CISCO SR-MPLS, SRv6 Crosswork Network Controller

Zambiri Zamalonda

Zofotokozera

• Dzina lazogulitsa: Cisco Crosswork Network Controller
• Zothandizira: SR-MPLS ndi kasamalidwe ka mfundo za SRv6
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Malangizo Ogwiritsira Ntchito Zogulitsa

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view pa mapu.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Kuchokera pagawo la Zochita, sankhani > View zambiri za imodzi mwa mfundo za SR-MPLS kapena SRv6.
• View the policy details, including segment lists and path computation constraints.
• Mutha kutumiza deta yonse ku CSV file kuchokera izi view.
• Koperani URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS ndi SRv6

• This section describes the SR-MPLS and SRv6 policy features that Crosswork supports.
• For a list of known limitations and important notes, see the Cisco Crosswork Network Controller Release Notes.

View SR-MPLS ndi SRv6 mfundo pamapu a topology

• To get to the Traffic Engineering topology map, choose Services & Traffic Engineering > Traffic Engineering.
• From the Traffic engineering table, click the checkbox of each SR-MPLS or SRv6 policy you want to view pa mapu.
• You can select up to 10 policies that will appear as separate colored links.

Imbani kunja Ayi.	Kufotokozera
1	Click the appropriate check box to enable the following options: •  Show: IGP path—Displays the IGP path for the selected SR-TE policy. •  Show: Participating only—Displays only links that belong to the selected SR-TE policy. All other links and devices disappear.
2	A device with an orange () 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 ().
4	SR-MPLS and SRv6 policy origin and destination: Ngati onse A ndi Z are displayed in a device cluster, at least one node in the cluster is a source, and another is a destination. The A+ denotes that there is more than one SR-TE policy that originates from a node. The Z+ denotes that the node is a destination for more than one SR policy.
5	Zomwe zili pawindo ili zimadalira zomwe zasankhidwa kapena zosefedwa. Mu example, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 tabo ku view mndandanda wa ndondomeko za SR-TE.

Imbani kunja Ayi.	Kufotokozera
7	Zogulitsa kunja zonse data into a CSV file. Simungathe kutumiza deta yosankhidwa kapena yosefedwa.
8	The Mini dashboard provides a summary of the operational SR-MPLS or SRv6 policy status. If filters are applied, the Mini dashboard is updated to reflect what is displayed in the SR Policy and SRv6 Policy tables. In addition to the policy status, the SR-MPLS mini dashboard table displays the number of PCC and PCE-initiated tunnels that are panopa listed in the SR Policy table.
9	Njirayi imakupatsani mwayi wosankha momwe fyuluta yamagulu (pamene ikugwiritsidwa ntchito) iyenera kugwiritsidwa ntchito pa data ya tebulo. Za example, ngati Headend only was selected, then it would only display policies where the headend device of the policy is in the selected group. This filter allows you to see specific configurations and is useful when you have a large network. 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.

View Tsatanetsatane wa mfundo za SR-MPLS ndi SRv6

• View Tsatanetsatane wa mfundo za SR-MPLS kapena SRv6 TE komanso mindandanda yamagawo ndi zovuta zilizonse zapanjira zokhazikitsidwa panjira ya munthu aliyense.

Ndondomeko

Gawo 1

• From the Actions column, choose > View zambiri za imodzi mwa mfundo za SR-MPLS kapena SRv6.

Gawo 2

• View Tsatanetsatane wa mfundo za SR-MPLS kapena SRv6. Kuchokera pa osatsegula, mukhoza kukopera URL ndi kugawana ndi ena.

Zindikirani

• The Delay value is calculated for all policies every 10 minutes. Hover your mouse over the “i” icon (next to the Delay value) to view nthawi yomaliza mtengowo unasinthidwa.

Onani njira ya IGP ndi ma metric

• View njira yakuthupi ndi ma metrics pakati pa malekezero a mfundo zosankhidwa za SR-MPLS.

Ndondomeko

• Step 1: From the SR Policy table, check the check box next to the SR-TE (SR-MPLS and SRv6) policies you are interested in.
• Step 2: Check the Show IGP Path check box. The IGP paths for the selected SR-MPLS policies are displayed as straight lines instead of the segment hops. In a dual-stack topology, the Participating only checkbox must also be checked to view ma metric pa maulalo omwe akutenga nawo mbali.
• Gawo 3: Dinani > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Zindikirani
You must check the Show IGP Path check box to view metrics.

Pezani Njira Zambiri (MCPs)

• Visualizing MCPs gives you insight into which paths might be a better alternative to the currently active ones.
• If you determine to do so, you can then manually configure the device and change which path becomes active.

Mfundo Zofunika

• Only PCC-initialized SR-TE policies with MCPs are supported.
• Crosswork does not distinguish dynamic paths from explicit paths. The Policy Type field value displays as ‘Unknown’.
• Mutha view njira zachidziwitso koma osati njira zachidziwitso zachidziwitso zomwe zimagwira ntchito mu UI.

Musanayambe
A policy must be configured with MCPs on devices before they can be visualized on the Traffic Engineering topology map. This configuration can be done manually or within the Crosswork Network Controller.

• Step 1: From the main menu, choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS or SRv6 tab.
• Step :2 Navigate to the active SR-TE policy that has MCPs configured and view it on the topology map.
• Check the check box next to the SR-TE policy that has MCPs configured.
• View ndondomeko ya SR-TE yomwe yawonetsedwa pamapu a topology.
• Mu example, mukuwona kuti njira yogwira ikupita ku cw-xrv53> cw-xrv57> cw-xrv58> cw-xrv59> cw-xrv60.

Gawo 3: View mndandanda wa njira zosankhidwa.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View zambiri. Mndandanda wa njira zosankhidwa umawonekera pamodzi ndi ndondomeko pawindo la ndondomeko ya SR. Wobiriwira A pansi pa gawo la State akuwonetsa njira yogwira.

• Step 4: You can expand individual paths or click Expand all to view details of each path.
• Step 5: Visualize the candidate path on the topology map.
• Check the check box next to any candidate path.

Zindikirani
You will not be able to select or view njira zoyeserera zowunikira.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Mu example, mukuwona kuti njira ina imachokera ku cw-xrv53> cw-xrv60.

Onani m'maganizo mwanu njira zomwe zimagwirizanitsidwa ndi chizindikiro cha Binding-Segment ID (B-SID)

• Crosswork Network Controller imakulolani kuti muwone njira yomwe ili pansi pa B-SID hop yomwe mwaikonza pamanja pa chipangizo kapena kusinthidwa pogwiritsa ntchito Crosswork Network Controller. Mu example, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• Ku view B-SID yoyambira njira ya SR-MPLS kapena SRv6, chitani izi:

Step 1: Choose Services & Traffic Engineering > Traffic Engineering.
Step :2 From the SR Policy table, check the check box next to the policy that has a hop assigned with a B-SID label. Hover your mouse over any part of the SR-MPLS row to see the B-SID name. The B-SID path is highlighted in orange on the topology map.
Mu example, mukuwona kuti njira ya B-SID ikupita ku cw-xrv51 kupita ku cw-xrv52.

Step 3: From the SR policy details page, click > View zambiri.

Step 4: Expand the active path and click the B-Sid Label ID to see the underlying path.

• Mu example, njira yoyambira imachokera ku cw-xrv51> cw-xrv54> cw-xrv53> cw-xrv52.

Onani njira zakubadwa za SR

• Visualizing the native path will help you in OAM (Operations, Administration, and Maintenance) activities to monitor label-switched paths (LSPs) and quickly isolate forwarding problems to assist with fault detection and troubleshooting in the network.
• Since this feature uses multipaths, all ECMP paths are shown between the source and destination. You can visualize only native SR IGP paths.

Zofunikira pa chipangizo

Confirm the following device software and configurations are met prior to visualizing native paths.

1. Devices should be running Cisco IOS XR 7.3.2 or higher. Run show version command to verify it.
2. Devices should have GRPC enabled. For information on enabling gRPC on PCE, see Requirements for adding SR-PCE providers in the Cisco Crosswork Network Controller 7.1 Administration guide.
   • Run show run grpc to confirm GRPC configuration. You should see something similar to this:
     Zindikirani
     Address family is only required in an IPv4 topology.
   • To enable GRPC with a secure connection, you must upload security certificates to connect to the device.
3. Devices should have GNMI capability enabled and configured.
   • From Device Management > Network Devices, click the IP address for the device you are interested in.
   • Confirm that GNMI is listed under Connectivity details.
     Based on the type of devices, these device encoding type are available. The appropriate encoding type is determined by the device’s capabilities, the data model it supports, and how the data is expected to be transmitted between the device and Crosswork Network Controller.
   • JSON: Human-readable and widely supported by most devices.
   • BYTES: Encodes data in binary format for efficient transmission.
   • PROTO: A compact, efficient binary format used with gRPC.
   • ASCII: A plain-text format that is human-readable but less commonly used compared to JSON.
   • JSON IETF: A standardized variant of JSON that adheres to IETF YANG specifications.
4. Devices should have the CDG router static address. Static route should be added from the device to the southbound CDG IP address. For exampLe:

Onani m'maganizo mwathu njira zachikale

• Tsatirani izi kuti mupange funso lanjira.

Gawo 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Gawo 2: Click New query.
Gawo 3: Enter the device information in the required fields to find available Native SR IGP Paths and click Get paths.

Zindikirani
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View mafunso am'mbuyomu kuti abwerere ku Path Query Dashboard. Ngati muli ndi mafunso a njira pamndandanda, mutha view zomwe zilipo pomwe funso latsopanoli likupitilira kumbuyo, zomwe zikuwonetsedwa ndi chithunzi cha blue Running mugawo la Query State. Pamene funso latsopanolo likutembenukira kubiriwira, ndikumalizidwa, likhoza kukhala viewed.

Gawo 4: Dinani View zotsatira zikapezeka pa Running Query ID pop-up. Zenera la Path Details likuwoneka ndi tsatanetsatane wa njira zomwe zilipo pomwe mapu a topology akuwonetsa njira za Native SR IGP kumanzere.

Konzani maulalo a TE mu Crosswork Network Controller

• If you have any affinities you wish to account for when provisioning an SR policy, Tree-SID, or RSVP-TE tunnel, then you can optionally define affinity mapping on the Crosswork Network Controller UI for consistency with affinity names in device configurations. Crosswork Network Controller will only send bit information to SR-PCE during provisioning. If an affinity mapping is not defined in the UI, then the affinity name is displayed as “UNKNOWN”. If you want to configure affinity mappings in Crosswork Network Controller for visualization purposes, you should collect affinities on the device, then define affinity mapping in Crosswork Network Controller with the same name and bits that are used on the device.
• The affinity configuration on interfaces simply turns on some bits. It is a 32-bit value, with each bit position (0–31) representing a link attribute. Affinity mappings can be colors representing a certain type of service profile (kwa example, low delay, high bandwidth, and so on). This makes it easier to refer to link attributes.
• See SR, Tree-SID, or RSVP-TE configuration documentation for your specific device to view mafotokozedwe ndi malamulo othandizira kasinthidwe (mwachitsanzoample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Example akuwonetsa SR-TE affinity kasinthidwe (affinity-mapu) pa chipangizo:

• Gawo 1: Choose Administration > Settings > System settings > Traffic engineering > Affinity > TE link affinities. Alternatively, you can define affinities while provisioning an SR-TE policy, Tree-SID, or RSVP-TE tunnel by clicking Manage mapping under the Constraints > Affinity field.
• Gawo 2: Click + Create to add a new affinity mapping.
• Gawo 3: Enter the name and the bit it will be assigned. For example (pogwiritsa ntchito kasinthidwe pamwambapa):

• Gawo 4: Click Save to save the mapping. To create another mapping, you must click + Create and save the entry. Affinity removal and orphan TE tunnels

Zindikirani
You should remove the TE tunnel before removing the affinity to avoid orphan TE tunnels. If you have removed an affinity associated with a TE tunnel, the affinity is shown as “UNKNOWN” in the SR policy / RSVP-TE tunnel details window.

Malingaliro a kutumizidwa kwa ndondomeko

Musanapereke ndondomeko, ganizirani izi.

• On a scaled setup with high node, policy, or interface counts, a timeout may occur during policy deployment. To configure timeout options, see Configure TE timeout settings.
• For visualization purposes, you can optionally collect affinity information from your devices and then map them in Cisco Crosswork before provisioning an SR policy, Tree-SID, or RSVP-TE tunnel. See Affinity map configurations for sample masanjidwe.

Pangani malamulo omveka bwino a SR-MPLS

• Ntchitoyi imapanga mfundo za SR-MPLS pogwiritsa ntchito njira yodziwika bwino (yokhazikika) yomwe ili ndi mndandanda wa ma ID a gawo kapena adjacency Segment (mndandanda wa SID), iliyonse ikuyimira mfundo kapena ulalo panjira. Tsatirani izi kuti mupange malamulo omveka bwino a SR-MPLS.

Musanayambe

• Collect affinity information from your devices, and then map them in the Crosswork Network Controller UI before creating an explicit SR-MPLS policy. See Configure TE link affinities in Crosswork Network Controller.

Gawo 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Gawo 2: Click Create > PCE Init.

Zindikirani
If you would like to provision a PCC-initiated policy using Cisco Network Services Orchestrator (NSO) via the Crosswork UI, see Create SR-TE policies (PCC-initiated).

Gawo 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view kufotokoza za munda.
Langizo
If you have set up device groups, you can select the device group from the Device Groups drop-down list. Then navigate and zoom in on the topology map to click the device for headend or endpoint selection.

• Gawo 4: Under Policy path, click Explicit path and enter a path name.
• Gawo 5: Add segments that will be part of the SR-MPLS policy path.
• Gawo 6: Dinani Preview and confirm that the policy you created matches your intent.
• Gawo 7: If you want to commit the policy path, click Provision to activate the policy on the network or exit to abort the configuration process.
• Gawo 8: Validate the SR-MPLS policy creation:
• Confirm that the new SR-MPLS policy appears in the Traffic Engineering table. You can also click the check box next to the policy to see it highlighted in the map.

Zindikirani
The newly provisioned SR-TE policy may take some time, depending on the network size and performance, to appear in the table. The Traffic engineering table is refreshed every 30 seconds.

• View ndikutsimikizira mfundo zatsopano za SR-MPLS. Kuchokera pa tebulo laukadaulo wa Magalimoto, dinani ndikusankha View zambiri.

Zindikirani

• Pakukhazikitsa kokhala ndi ma node apamwamba, ndondomeko, kapena mawonekedwe, nthawi imatha kuchitika panthawi yotumiza. Kuti mukonze zosankha zakutha, onani Konzani TE zochunira nthawi yotha.

Pangani malamulo amphamvu a SR-MPLS potengera kukhathamiritsa
SR-PCE computes a path for the policy based on metrics and path constraints (affinities or disjointness) defined by the user. A user can select from three available metrics to minimize in-path computation: IGP, TE, or latency. The SR-PCE will automatically re-optimize the path as necessary based on topology changes. If a link or interface fails, the network will find an alternate path that meets all the criteria specified in the policy and raise an alarm. If no path is found, an alarm is raised, and the packets are dropped.
Follow these steps to create SR-MPLS policies with a dynamic path.

• Gawo 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Gawo 2: Click Create > PCE Init. If you would like to provision a PCC-initiated policy using Cisco Network Services Orchestrator (NSO) via the Crosswork UI, see Create SR-TE policies (PCC-initiated).
• Gawo 3: Pansi pa Tsatanetsatane wa Ndondomeko, lowetsani kapena sankhani mfundo zofunika za SR-MPLS. Yendetsani cholozera cha mbewa mpaka view kufotokoza kwa gawo lililonse.

Langizo

• If you have set up device groups, you can select the device group from the Device Groups drop-down menu. Then navigate and zoom in on the topology map to click the device for headend or endpoint selection.
• Gawo 4: Under Policy path, click Dynamic path and enter a path name.
• Gawo 5: Under Optimization objective, select the metric you want to minimize.
• Gawo 6: Define any applicable constraints and disjointness.

Malingaliro ogwirizana

• Affinity constraints and disjointness cannot be configured on the same SR-MPLS policy. Also, there cannot be more than two SR-MPLS policies in the same disjoint group or subgroup. The configuration will not be allowed during Preview.
• If there are existing SR-MPLS policies belonging to a disjoint group that you define here, all SR-MPLS policies that belong to that same disjoint group are shown during Preview.
• Gawo 7: Under Segments, select whether or not protected segments should be used when available.
• Gawo 8: Enter any applicable SID constraint. Crosswork Network Controller will try to find a path with this SID. If a path with the SID constraint cannot be found, the provisioned policy will remain operationally down until the conditions are met.

Zambiri za SID

• Flexible Algorithm—The values correspond to the Flexible Algorithm that are defined on the device and the 128-255 range is enforced by Cisco IOS XR.
• Algorithm 0—This is a Shortest Path First (SPF) algorithm based on link metric. This shortest path algorithm is computed by the Interior Gateway Protocol (IGP).
• Algorithm 1—This is a Strict Shortest Path First (SSPF) algorithm based on link metric. Algorithm 1 is identical to Algorithm 0 but requires that all nodes along the path honor the SPF routing decision. Local policy does not alter the forwarding decision. For example, a packet is not forwarded through a locally engineered path.
• Gawo 9: Dinani Preview. The path is highlighted on the map.
• Gawo 10: To commit the policy path, click Provision.
• Gawo 11: Validate the SR-MPLS policy creation.
• Confirm that the new SR-MPLS policy appears in the SR Policy table. You can also click the check box next to the policy to see it highlighted in the map.

Zindikirani

• The newly provisioned SR-MPLS policy may take some time, depending on the network size and performance, to appear in the Traffic Engineering table. The table is refreshed every 30 seconds.
• View ndikutsimikizira mfundo zatsopano za SR-MPLS. Kuchokera pa tebulo laukadaulo wa Magalimoto, dinani ndikusankha View zambiri.

Pangani malamulo a SR-TE (PCC-initiated)

• Ntchitoyi imapanga mfundo zomveka bwino kapena zamphamvu za SR-MPLS kapena SRv6 pogwiritsa ntchito Cisco Network Services Orchestrator (NSO) kudzera pa Crosswork UI.

Musanayambe
If you want to create explicit PCC-initiated SR-MPLS or SRv6 policies, you must create a Segment IDs list (Services & Traffic Engineering > Provisioning (NSO) > SR-TE > SID-List). An explicit (fixed) path consists of a list of prefix or adjacency Segment IDs, each representing a node or link along on the path.

Gawo 1: Kuchokera ku menyu yayikulu, sankhani Services & Traffic Engineering> Provisioning (NSO).
Gawo 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Zindikirani

• You may also click kuitanitsa ndondomeko yomwe ilipo ya SR-TE.
• Gawo 3: Enter the policy constraints and required values.
• You must populate the following options:

Table 1: SR-TE Policy Configuration

Wonjezerani izi:	To specify this:
dzina	Enter a name for this SR-TE policy.
head-end	•  You can click to select a node or manually enter the node name.
tail-end	Manually enter the node name.
mtundu	Enter a color. For exampndi: 200.
njira	a.      Dinani and enter a preference value. For exampndi: 123 b.     Select one of the following and toggle the switch to enable: •  explicit-path—Click to add previously configured SID lists. •  dynamic-path—Select the metric you want to minimize and define any applicable constraints and disjointness.
srv6	If you are creating an SRv6 policy, toggle Enable SRv6.

• Step 4: When you are finished, click Dry Run to validate your changes and save them. Crosswork will display your changes in a pop-up window.
• Ngati mukufuna kukonza ntchito yomwe ili ndi zofunikira zomwe sizikugwirizana ndi zomwe tafotokoza kaleample, kulumikizana ndi Cisco Customer Experience.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Sinthani ndondomeko za SR-MPLS

• Mutha kungosintha kapena kufufuta mfundo za SR-MPLS zomwe zidapangidwa pogwiritsa ntchito Crosswork Network Controller API kapena UI. Tsatirani izi kuti view, sintha, kapena kufufuta mfundo za SR-MPLS.
• Gawo 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Gawo 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Gawo 3: Sankhani View zambiri kapena Sinthani/Chotsani. Mukasintha zambiri za mfundo za SR-MPLS, mutha kutsataview zosintha pamapu musanazisunge.

FAQ

Q: Ndi mfundo zingati zomwe zitha kuwonetsedwa pamapu a topology?

A: Up to 10 policies can be selected and displayed as separate colored links on the map.

Q: Kodi ndingathe kutumiza deta yosankhidwa kuchokera ku ndondomeko ya ndondomeko view?

A: Ayi, mutha kutumiza deta yonse mu CSV file from the policy details view.

Zolemba / Zothandizira

CISCO SR-MPLS, SRv6 Crosswork Network Controller [pdf] Buku Logwiritsa Ntchito SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork Network Controller, SR-MPLS SRv6, Crosswork Network Controller, Network Controller, Controller

Maumboni

• Buku Logwiritsa Ntchito