CISCO SR-MPLS, SRv6 Crosswork tīkla kontrolieris

Informācija par produktu

Specifikācijas

• Produkta nosaukums: Cisco Crosswork tīkla kontrolieris
• Atbalstītās funkcijas: SR-MPLS un SRv6 politikas pārvaldība
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Produkta lietošanas instrukcijas

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view kartē.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Kolonā Darbības izvēlieties > View informācija par vienu no SR-MPLS vai SRv6 politikām.
• View the policy details, including segment lists and path computation constraints.
• Visus datus var eksportēt CSV failā file no šī view.
• Kopējiet URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS un 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 un SRv6 politikas topoloģijas kartē

• 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 kartē.
• You can select up to 10 policies that will appear as separate colored links.

remarka Nē.	Apraksts
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: Ja abi A un 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	Šī loga saturs ir atkarīgs no atlasītā vai filtrētā satura. Šajā piemērāample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 cilnes uz view attiecīgais SR-TE politikas saraksts.

remarka Nē.	Apraksts
7	Eksports visi data into a CSV fileJūs nevarat eksportēt atlasītos vai filtrētos datus.
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 pašlaik listed in the SR Policy table.
9	Šī opcija ļauj izvēlēties, kā grupas filtrs (kad tas tiek lietots) jāpielieto tabulas datiem. Piemēram,ampja, ja 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 SR-MPLS un SRv6 politikas informācija

• View SR-MPLS vai SRv6 TE politikas līmeņa informācija, kā arī segmentu saraksti un visi ceļa aprēķināšanas ierobežojumi, kas konfigurēti katram kandidāta ceļam atsevišķi.

Procedūra

1. darbība

• From the Actions column, choose > View informācija par vienu no SR-MPLS vai SRv6 politikām.

2. darbība

• View SR-MPLS vai SRv6 politikas informācija. No pārlūkprogrammas varat kopēt URL un dalīties ar citiem.

Piezīme

• 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 pēdējo reizi, kad vērtība tika atjaunināta.

Vizualizējiet IGP ceļu un metrikas

• View fiziskais ceļš un metrikas starp atlasīto SR-MPLS politiku galapunktiem.

Procedūra

• 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 metrika par iesaistītajām saitēm.
• 3. darbība: noklikšķiniet > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Piezīme
You must check the Show IGP Path check box to view metriku.

Atrast vairākus kandidātu ceļus (MCP)

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

Svarīgas piezīmes

• 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’.
• Jūs varat view aktīvi tiešie ceļi, bet ne neaktīvi kandidātu tiešie ceļi lietotāja saskarnē.

Pirms sākat
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 SR-TE politika, kas ir iezīmēta topoloģijas kartē.
• Šajā bijušajāampPiemēram, jūs redzat, ka aktīvais ceļš ir šāds: cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.

3. darbība: View kandidātu ceļu saraksts.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View informācija. SR politikas informācijas logā tiek parādīts potenciālo ceļu saraksts kopā ar politikas informāciju. Zaļā A zem Stāvokļa kolonnas norāda aktīvo ceļu.

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

Piezīme
You will not be able to select or view skaidri kandidātu ceļi.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Šajā bijušajāampPiemēram, jūs redzat, ka alternatīvais ceļš ved tieši no cw-xrv53 > cw-xrv60.

Vizualizējiet pamatā esošos ceļus, kas saistīti ar definētu saistījuma segmenta ID (B-SID) etiķeti

• Crosswork tīkla kontrolleris ļauj vizualizēt B-SID lēciena pamatā esošo ceļu, ko esat manuāli konfigurējis ierīcē vai konfigurējis, izmantojot Crosswork tīkla kontrolleri. Šajā piemērāample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• Uz view Lai noteiktu SR-MPLS vai SRv6 politikas B-SID pamatā esošo ceļu, veiciet tālāk norādītās darbības.

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.
Šajā bijušajāampPiemēram, jūs redzat, ka B-SID ceļš ved no cw-xrv51 uz cw-xrv52.

Step 3: From the SR policy details page, click > View detaļas.

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

• Šajā bijušajāampPiemēram, pamatā esošais ceļš faktiski ved no cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.

Vizualizēt vietējos SR ceļus

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

Ierīces priekšnosacījumi

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:
     Piezīme
     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:

Vizualizēt vietējos ceļus

• Lai izveidotu ceļa vaicājumu, veiciet šīs darbības.

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

Piezīme
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View iepriekšējos vaicājumus, lai atgrieztos ceļa vaicājumu informācijas panelī. Ja sarakstā jau bija ceļa vaicājumi, varat view esošo informāciju, kamēr jaunais vaicājums turpina darboties fonā, ko norāda zilā ikona “Darbojas” kolonnā “Vaicājuma statuss”. Kad jaunā vaicājuma statuss kļūst zaļš un ir pabeigts, to var viewed.

4. darbība: Noklikšķiniet View rezultātus, kad tas kļūst pieejams uznirstošajā logā “Aktivējošā vaicājuma ID”. Tiek parādīts logs “Ceļa informācija” ar atbilstošo pieejamo ceļu informāciju, savukārt topoloģijas kartē kreisajā pusē tiek parādīti pieejamie Native SR IGP ceļi.

TE saišu afinitāšu konfigurēšana Crosswork tīkla kontrollerī

• 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 (piemēram,ample, 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 apraksti un atbalstītās konfigurācijas komandas (piemēram,ample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Nākamais exampattēlā redzama SR-TE afinitātes konfigurācija (afinitātes karte) ierīcē:

• 1. darbība: 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.
• 2. darbība: Click + Create to add a new affinity mapping.
• 3. darbība: Enter the name and the bit it will be assigned. For example (izmantojot iepriekš minēto konfigurāciju):

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

Piezīme
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.

Politikas ieviešanas apsvērumi

Pirms nodrošināšanas politiku izstrādes apsveriet šīs iespējas.

• 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 konfigurācijas.

Izveidojiet skaidras SR-MPLS politikas

• Šis uzdevums izveido SR-MPLS politikas, izmantojot skaidru (fiksētu) ceļu, kas sastāv no prefiksu vai blakus esošo segmentu ID saraksta (SID saraksta), katrs no kuriem attēlo mezglu vai saiti ceļā. Veiciet šīs darbības, lai izveidotu skaidras SR-MPLS politikas.

Pirms sākat

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

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

Piezīme
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).

3. darbība: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view lauka apraksts.
Padoms
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.

• 4. darbība: Under Policy path, click Explicit path and enter a path name.
• 5. darbība: Add segments that will be part of the SR-MPLS policy path.
• 6. darbība: Noklikšķiniet uz Iepriekšview and confirm that the policy you created matches your intent.
• 7. darbība: If you want to commit the policy path, click Provision to activate the policy on the network or exit to abort the configuration process.
• 8. darbība: 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.

Piezīme
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 un apstipriniet jaunās SR-MPLS politikas informāciju. Satiksmes inženierijas tabulā noklikšķiniet uz un atlasiet View detaļas.

Piezīme

• Iestatījumos ar lielu mezglu, politiku vai saskarņu skaitu politikas izvietošanas laikā var rasties taimauts. Lai konfigurētu taimauta opcijas, skatiet sadaļu TE taimauta iestatījumu konfigurēšana.

Izveidojiet dinamiskas SR-MPLS politikas, pamatojoties uz optimizācijas nolūku
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.

• 1. darbība: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• 2. darbība: 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).
• 3. darbība: Sadaļā Politikas informācija ievadiet vai atlasiet nepieciešamās SR-MPLS politikas vērtības. Novietojiet peles kursoru virs view katra lauka apraksts.

Padoms

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

Afinitātes apsvērumi

• 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.
• 7. darbība: Under Segments, select whether or not protected segments should be used when available.
• 8. darbība: 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.

SID informācija

• 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.
• 9. darbība: Noklikšķiniet uz Iepriekšview. The path is highlighted on the map.
• 10. darbība: To commit the policy path, click Provision.
• 11. darbība: 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.

Piezīme

• 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 un apstipriniet jaunās SR-MPLS politikas informāciju. Satiksmes inženierijas tabulā noklikšķiniet uz un atlasiet View detaļas.

Izveidot SR-TE politikas (PCC iniciētas)

• Šis uzdevums izveido tiešas vai dinamiskas SR-MPLS vai SRv6 politikas, izmantojot Cisco Network Services Orchestrator (NSO) un Crosswork lietotāja saskarni.

Pirms sākat
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.

1. darbība: Galvenajā izvēlnē izvēlieties Pakalpojumi un datplūsmas inženierija > Nodrošināšana (NSO).
2. darbība: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Piezīme

• You may also click lai importētu esošu SR-TE politiku.
• 3. darbība: Enter the policy constraints and required values.
• You must populate the following options:

1. tabula: SR-TE politikas konfigurācija

Izvērst šis:	To specify this:
nosaukums	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.
krāsa	Enter a color. For examptālr .: 200.
ceļš	a.      Noklikšķiniet and enter a preference value. For examptālr .: 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.
• Ja vēlaties konfigurēt pakalpojumu, kura prasības neatbilst šajā piemērā aprakstītajāmampsazinieties ar Cisco klientu apkalpošanas dienestu.
• Step 5: When you are ready to activate the policy, click Commit Changes.

SR-MPLS politikas modificēšana

• Varat modificēt vai dzēst tikai tās SR-MPLS politikas, kas ir izveidotas, izmantojot Crosswork Network Controller API vai lietotāja saskarni. Veiciet šīs darbības, lai view, modificēt vai dzēst SR-MPLS politiku.
• 1. darbība: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• 2. darbība: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• 3. darbība: Izvēlieties View informāciju vai rediģēt/dzēst. Pēc SR-MPLS politikas informācijas atjaunināšanas varat iepriekšview izmaiņas kartē pirms to saglabāšanas.

FAQ

J: Cik politikas var attēlot topoloģijas kartē?

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

J: Vai varu eksportēt atlasītos datus no politikas informācijas? view?

A: Nē, visus datus var eksportēt tikai CSV failā. file from the policy details view.

Dokumenti / Resursi

CISCO SR-MPLS, SRv6 Crosswork tīkla kontrolieris [pdfLietotāja rokasgrāmata SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork tīkla kontrolieris, SR-MPLS SRv6, Crosswork tīkla kontrolieris, Tīkla kontrolieris, Kontrolieris

Atsauces

• Lietotāja rokasgrāmata