CISCO SR-MPLS, SRv6 Crosswork Network Controller

Ozi ngwaahịa

Nkọwapụta

• Aha ngwaahịa: Cisco Crosswork Network Controller
• Atụmatụ akwadoro: SR-MPLS na njikwa amụma SRv6
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Ntuziaka ojiji ngwaahịa

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view na map.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Site na kọlụm omume, họrọ > View nkọwa maka otu iwu SR-MPLS ma ọ bụ SRv6.
• View the policy details, including segment lists and path computation constraints.
• Ị nwere ike mbupụ data niile na CSV file site na nke a view.
• Detuo ya URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS na 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 Amụma SR-MPLS na SRv6 na map 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 na map.
• You can select up to 10 policies that will appear as separate colored links.

Kpọpụta oku Mba.	Nkọwa
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: Ọ bụrụ na ha abụọ A na 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	Ọdịnaya nke mpio a dabere n'ihe ahọpụtara ma ọ bụ yochaa. Na nke a example, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 taabụ na view ndepụta nke usoro iwu SR-TE.

Kpọpụta oku Mba.	Nkọwa
7	Mbupụ niile data into a CSV file. Ị nweghị ike mbupụ data ahọpụtara ma ọ bụ nke akọrọ.
8	Nke 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 ugbu a listed in the SR Policy table.
9	Nhọrọ a na-enye gị ohere ịhọrọ otu esi etinye nzacha otu (mgbe a na-eji ya) na data tebụl. Maka example, ọ bụrụ 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 Nkọwa amụma SR-MPLS na SRv6

• View Nkọwa ọkwa ọkwa amụma SR-MPLS ma ọ bụ SRv6 TE yana ndepụta ngalaba yana mgbochi ngụkọ ụzọ ọ bụla ahaziri n'ụzọ onye ọ bụla.

Usoro

Nzọụkwụ 1

• From the Actions column, choose > View nkọwa maka otu iwu SR-MPLS ma ọ bụ SRv6.

Nzọụkwụ 2

• View Nkọwa amụma SR-MPLS ma ọ bụ SRv6. Site na ihe nchọgharị, ị nwere ike iṅomi ya URL ma soro ndị ọzọ kerịta.

Rịba ama

• 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 oge ikpeazụ emelitere uru.

Jiri anya nke uche hụ ụzọ IGP na metrik

• View ụzọ anụ ahụ na metrik n'etiti njedebe nke amụma SR-MPLS ahọpụtara.

Usoro

• 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 metrik na njikọ ndị na-ekere òkè.
• Nzọụkwụ 3: Pịa > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Rịba ama
You must check the Show IGP Path check box to view metrik.

Chọta ọtụtụ ụzọ ndị ntuli aka (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.

Ihe ndetu dị mkpa

• 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’.
• Ị nwere ike view Ụzọ doro anya na-arụ ọrụ mana ọ bụghị onye na-achọ ọrụ na-adịghị arụ ọrụ ụzọ doro anya na UI.

Tupu ịmalite
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 amụma SR-TE nke e mere ka ọ pụta ìhè na map topology.
• Na nke a example, ị na-ahụ na-arụsi ọrụ ike ụzọ si na cw-xrv53> cw-xrv57> cw-xrv58> cw-xrv59> cw-xrv60.

Nzọụkwụ 3: View ndepụta nke ụzọ ntuli aka.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View nkọwa. Ndepụta nke ụzọ nwa akwukwo na-apụta yana nkọwa amụma na windo nkọwa amụma SR. Akwụkwọ ndụ akwụkwọ ndụ A n'okpuru kọlụm steeti na-egosi ụzọ na-arụ ọrụ.

• 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.

Rịba ama
You will not be able to select or view ụzọ ndị ndoro-ndoro anya.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Na nke a examplee, ị na-ahụ na ụzọ ọzọ na-aga kpọmkwem site na cw-xrv53> cw-xrv60.

Chee echiche nke ọma ụzọ ndị dị n'okpuru jikọtara ya na akara njirimara Binding-Segment ID (B-SID)

• Crosswork Network Controller na-enye gị ohere iji anya nke uche hụ ụzọ dị n'okpuru nke hop B-SID nke ị jiri aka hazie na ngwaọrụ ma ọ bụ hazie site na iji Crosswork Network Controller. Na nke a example, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• Iji view Ụzọ n'okpuru B-SID maka amụma SR-MPLS ma ọ bụ SRv6, mee ihe ndị a:

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.
Na nke a examplee, ị na-ahụ na ụzọ B-SID na-esi na cw-xrv51 gaa cw-xrv52.

Step 3: From the SR policy details page, click > View nkọwa.

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

• Na nke a example, ụzọ dị n'okpuru na-esi na cw-xrv51> cw-xrv54> cw-xrv53> cw-xrv52.

Jiri anya nke uche hụ ụzọ SR nke ala

• 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.

Ihe achọrọ ngwaọrụ

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:
     Rịba ama
     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:

Jiri anya nke uche hụ ụzọ obodo

• Soro usoro ndị a ka ịmepụta ajụjụ ụzọ.

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

Rịba ama
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View Ajuju gara aga ịlaghachi na dashboard ajụjụ ụzọ. Ọ bụrụ na ịnweelarị ajụjụ ụzọ na ndepụta ahụ, ị nwere ike view nkọwa dị ka ajụjụ ọhụrụ ahụ na-aga n'ihu n'azụ, nke gosipụtara na akara ngosi na-agba ọsọ na-acha anụnụ anụnụ na kọlụm State Query State. Mgbe steeti ajụjụ ọhụrụ ahụ ghọrọ akwụkwọ ndụ akwụkwọ ndụ, ma mechaa, ọ nwere ike ịbụ viewed.

Nzọụkwụ 4: Pịa View nsonaazụ mgbe ọ dị na mgbapụta NJ ajụjụ na-agba ọsọ. Window nkọwa nke ụzọ na-egosi na nkọwa ụzọ dabara adaba dị ebe map topology na-egosiputa ụzọ Native SR IGP dị n'aka ekpe.

Hazie njikọ njikọ TE na 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 (maka 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 nkọwa na iwu nhazi akwadoro (maka example, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Ndị na-esonụ example na-egosi nhazi mmekọ SR-TE (map affinity) na ngwaọrụ:

• Nzọụkwụ 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.
• Nzọụkwụ 2: Click + Create to add a new affinity mapping.
• Nzọụkwụ 3: Enter the name and the bit it will be assigned. For example (iji nhazi nke dị n'elu):

• Nzọụkwụ 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

Rịba ama
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.

Atụmatụ mbugharị amụma

Tupu ịnye usoro iwu, tụlee nhọrọ ndị a.

• 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 nhazi.

Mepụta amụma SR-MPLS doro anya

• Ọrụ a na-emepụta amụma SR-MPLS site na iji ụzọ doro anya (edobere) nke nwere ndepụta prefix ma ọ bụ n'akụkụ NJ ngalaba (ndepụta SID), nke ọ bụla na-anọchi anya ọnụ ma ọ bụ njikọ n'akụkụ ụzọ ahụ. Soro usoro ndị a ka imepụta uwe ojii SR-MPLS doro anya.

Tupu ịmalite

• 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.

Nzọụkwụ 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Nzọụkwụ 2: Click Create > PCE Init.

Rịba ama
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).

Nzọụkwụ 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view nkọwa nke ubi.
Ndụmọdụ
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.

• Nzọụkwụ 4: Under Policy path, click Explicit path and enter a path name.
• Nzọụkwụ 5: Add segments that will be part of the SR-MPLS policy path.
• Nzọụkwụ 6: Pịa Preview and confirm that the policy you created matches your intent.
• Nzọụkwụ 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.
• Nzọụkwụ 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.

Rịba ama
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 ma kwado nkọwapụta amụma SR-MPLS ọhụrụ. Site na tebụl injinia okporo ụzọ, pịa wee họrọ View nkọwa.

Rịba ama

• Na ntọlite nke nwere ọnụ ọnụ elu, amụma, ma ọ bụ interface, oge nkwụsị nwere ike ime n'oge mbugharị amụma. Iji hazie nhọrọ nkwụsị oge, hụ Hazie ntọala TE.

Mepụta atumatu SR-MPLS siri ike dabere na ebumnuche nkwalite
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.

• Nzọụkwụ 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Nzọụkwụ 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).
• Nzọụkwụ 3: N'okpuru nkọwa amụma, tinye ma ọ bụ họrọ ụkpụrụ iwu SR-MPLS achọrọ. Nyefee ntụaka òké n'akụkụ view nkọwa nke ubi ọ bụla.

Ndụmọdụ

• 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.
• Nzọụkwụ 4: Under Policy path, click Dynamic path and enter a path name.
• Nzọụkwụ 5: Under Optimization objective, select the metric you want to minimize.
• Nzọụkwụ 6: Define any applicable constraints and disjointness.

Echiche mmekọrịta

• 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.
• Nzọụkwụ 7: Under Segments, select whether or not protected segments should be used when available.
• Nzọụkwụ 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.

Ozi 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.
• Nzọụkwụ 9: Pịa Preview. The path is highlighted on the map.
• Nzọụkwụ 10: To commit the policy path, click Provision.
• Nzọụkwụ 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.

Rịba ama

• 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 ma kwado nkọwapụta amụma SR-MPLS ọhụrụ. Site na tebụl injinia okporo ụzọ, pịa wee họrọ View nkọwa.

Mepụta atumatu SR-TE (PCC malitere)

• Ọrụ a na-emepụta amụma SR-MPLS ma ọ bụ SRv6 doro anya ma ọ bụ dị ike site na iji Cisco Network Services Orchestrator (NSO) site na Crosswork UI.

Tupu ịmalite
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.

Nzọụkwụ 1: Site na isi menu, họrọ Ọrụ & Okporo ụzọ Injinịa> Nnyefe (NSO).
Nzọụkwụ 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Rịba ama

• You may also click ibubata amụma SR-TE dị adị.
• Nzọụkwụ 3: Enter the policy constraints and required values.
• You must populate the following options:

Tebụl 1: Nhazi amụma SR-TE

Gbasaa nke a:	To specify this:
aha	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.
agba	Enter a color. For exampnke: 200.
uzo	a.      Pịa and enter a preference value. For exampihe: 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.
• Ọ bụrụ na ịchọrọ ịhazi ọrụ nwere ihe achọrọ na-adabaghị ndị anyị kọwara na mbụ aample, kpọtụrụ Cisco Ahịa Ahụmahụ.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Megharịa amụma SR-MPLS

• Ị nwere ike gbanwee ma ọ bụ hichapụ atumatu SR-MPLS nke emebere site na iji Crosswork Network Controller API ma ọ bụ UI . Soro usoro ndị a ka view, gbanwee, ma ọ bụ hichapụ amụma SR-MPLS.
• Nzọụkwụ 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Nzọụkwụ 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Nzọụkwụ 3: Họrọ View nkọwa ma ọ bụ Dezie/Hichapụ. Mgbe emelitechara nkọwapụta amụma SR-MPLS, ị nwere ike ibu ụzọview mgbanwe na maapụ ahụ tupu ịchekwa ya.

FAQ

Ajụjụ: Iwu ole ka enwere ike igosipụta na maapụ topology?

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

Ajụjụ: Enwere m ike mbupụ data ahọpụtara site na nkọwa amụma view?

A: Mba, naanị ị nwere ike mbupụ data niile n'ime CSV file from the policy details view.

Akwụkwọ / akụrụngwa

CISCO SR-MPLS, SRv6 Crosswork Network Controller [pdf] Ntuziaka onye ọrụ SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork Network Controller, SR-MPLS SRv6, Crosswork Network Controller, Network Controller, Controller.

Ntụaka

• Akwụkwọ ntuziaka onye ọrụ