CISCO SR-MPLS, SRv6 Crosswork netstýring

Upplýsingar um vöru

Tæknilýsing

• Vöruheiti: Cisco Crosswork netstýring
• Studdir eiginleikar: SR-MPLS og SRv6 stefnustjórnun
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Notkunarleiðbeiningar fyrir vöru

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view á kortinu.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Úr dálknum Aðgerðir skaltu velja > View upplýsingar um eina af SR-MPLS eða SRv6 stefnunum.
• View the policy details, including segment lists and path computation constraints.
• Þú getur flutt öll gögn út í CSV skrá file úr þessu view.
• Afritaðu URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS og 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 og SRv6 stefnur á grannfræðikortinu

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

blaðra Nei.	Lýsing
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: Ef bæði A og 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	Efni þessa glugga fer eftir því hvað hefur verið valið eða síað. Í þessu dæmiample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 flipa til view viðkomandi lista yfir SR-TE stefnur.

blaðra Nei.	Lýsing
7	Útflutningur allt data into a CSV fileÞú getur ekki flutt út valin eða síuð gögn.
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 eins og er listed in the SR Policy table.
9	Þessi valkostur gerir þér kleift að velja hvernig hópsían (þegar hún er í notkun) á að vera notuð á töflugögnin. Til dæmisample, ef 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 Upplýsingar um SR-MPLS og SRv6 stefnu

• View Upplýsingar um stefnustig SR-MPLS eða SRv6 TE, sem og lista yfir hluta og allar útreikningstakmarkanir á leiðum sem eru stilltar fyrir hvern umsækjanda fyrir sig.

Málsmeðferð

Skref 1

• From the Actions column, choose > View upplýsingar um eina af SR-MPLS eða SRv6 stefnunum.

Skref 2

• View Upplýsingar um SR-MPLS eða SRv6 stefnu. Þú getur afritað úr vafranum URL og deila með öðrum.

Athugið

• 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 síðast þegar gildið var uppfært.

Sýna IGP slóð og mælikvarða

• View Efnisleg leið og mælikvarðar milli endapunkta valdra SR-MPLS-stefnu.

Málsmeðferð

• 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 mælikvarðar á þátttökutenglum.
• Skref 3: Smelltu > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Athugið
You must check the Show IGP Path check box to view mælikvarðar.

Finndu margar frambjóðendaleiðir (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.

Mikilvægar athugasemdir

• 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’.
• Þú getur view Virkar, skýrar slóðir en ekki óvirkar, mögulegar, skýrar slóðir í notendaviðmótinu.

Áður en þú byrjar
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 stefnan sem er auðkennd á grannfræðikortinu.
• Í þessu frvampÞú sérð að virka leiðin fer frá cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.

Skref 3: View listinn yfir leiðir sem eru í boði.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View upplýsingar. Listi yfir mögulegar leiðir birtist ásamt upplýsingum um stefnu í glugganum fyrir upplýsingar um SR-stefnu. Græna A-ið undir dálknum „Staða“ gefur til kynna virka leiðina.

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

Athugið
You will not be able to select or view skýrar leiðir frambjóðenda.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Í þessu frvampÞú sérð að önnur leið liggur beint frá cw-xrv53 > cw-xrv60.

Sýnið undirliggjandi slóðir sem tengjast skilgreindu B-SID merki (Binding-Segment ID)

• Crosswork Network Controller gerir þér kleift að sjá undirliggjandi slóð B-SID hopps sem þú hefur stillt handvirkt á tæki eða stillt með Crosswork Network Controller. Í þessu dæmiample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• Til view Undirliggjandi B-SID slóðin fyrir SR-MPLS eða SRv6 stefnu skaltu gera eftirfarandi:

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.
Í þessu frvampÞú sérð að B-SID slóðin fer frá cw-xrv51 til cw-xrv52.

Step 3: From the SR policy details page, click > View smáatriði.

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

• Í þessu frvampLeiðin sem liggur að baki er í raun og veru frá cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.

Sýna innfæddar SR-slóðir

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

Kröfur um tæki

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:
     Athugið
     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:

Sýna innfæddar slóðir

• Fylgdu þessum skrefum til að búa til slóðarfyrirspurn.

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

Athugið
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View fyrri fyrirspurnir til að fara aftur á leiðarfyrirspurnarmælaborðið. Ef þú varst þegar með leiðarfyrirspurnir á listanum geturðu view fyrirliggjandi upplýsingar á meðan nýja fyrirspurnin heldur áfram að keyra í bakgrunni, sem er gefið til kynna með bláa „Keyrslu“ tákninu í dálknum „Fyrirspurnarstaða“. Þegar nýja fyrirspurnarstaðan verður græn og henni er lokið er hægt að viewútg.

Skref 4: Smelltu View niðurstöður þegar þær verða tiltækar í sprettiglugganum „Keyrandi fyrirspurnarauðkenni“. Glugginn „Slóðarupplýsingar“ birtist með upplýsingum um samsvarandi tiltækar slóðir á meðan kortið yfir staðsetningu sýnir tiltækar Native SR IGP slóðir vinstra megin.

Stilla TE tengiskyldu í 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 (tdample, 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 lýsingar og studdar stillingarskipanir (til dæmisample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Eftirfarandi frvampLe sýnir SR-TE sæknistillingu (affinity-map) á tæki:

• Skref 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.
• Skref 2: Click + Create to add a new affinity mapping.
• Skref 3: Enter the name and the bit it will be assigned. For example (með ofangreindri stillingu):

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

Athugið
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.

Íhugunaratriði varðandi innleiðingu stefnu

Áður en úthlutunarreglur eru settar upp skaltu íhuga þessa valkosti.

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

Búa til skýrar SR-MPLS stefnur

• Þetta verkefni býr til SR-MPLS stefnur með því að nota skýra (fasta) slóð sem samanstendur af lista af forskeytum eða aðliggjandi hlutaauðkennum (SID lista), þar sem hvert táknar hnút eða tengil á slóðinni. Fylgdu þessum skrefum til að búa til skýrar SR-MPLS stefnur.

Áður en þú byrjar

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

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

Athugið
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).

Skref 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view lýsingu á reitnum.
Ábending
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.

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

Athugið
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 og staðfesta nýju upplýsingarnar um SR-MPLS stefnuna. Í töflunni um umferðarverkfræði, smelltu á og veldu View smáatriði.

Athugið

• Í uppsetningu með miklum fjölda hnúta, stefnu eða viðmóta getur tímamörk komið upp við uppsetningu stefnu. Til að stilla tímamörk, sjá Stilla tímamörk fyrir TE.

Búa til kraftmiklar SR-MPLS stefnur byggðar á hagræðingaráformum
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.

• Skref 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Skref 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).
• Skref 3: Undir Upplýsingar um stefnu, sláðu inn eða veldu nauðsynleg gildi fyrir SR-MPLS stefnu. Færðu músarbendlinn yfir view lýsingu á hverju sviði.

Ábending

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

Skyldleikaatriði

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

SID upplýsingar

• 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.
• Skref 9: Smelltu á Preview. The path is highlighted on the map.
• Skref 10: To commit the policy path, click Provision.
• Skref 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.

Athugið

• 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 og staðfesta nýju upplýsingarnar um SR-MPLS stefnuna. Smelltu á og veldu í töflunni Umferðarverkfræði. View smáatriði.

Búa til SR-TE stefnur (PCC-frumkvæði)

• Þetta verkefni býr til skýrar eða breytilegar SR-MPLS eða SRv6 stefnur með því að nota Cisco Network Services Orchestrator (NSO) í gegnum Crosswork notendaviðmótið.

Áður en þú byrjar
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.

Skref 1: Í aðalvalmyndinni skaltu velja Þjónusta og umferðarverkfræði > Útvegun (NSO).
Skref 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Athugið

• You may also click til að flytja inn núverandi SR-TE stefnu.
• Skref 3: Enter the policy constraints and required values.
• You must populate the following options:

Tafla 1: Stillingar SR-TE stefnu

Stækkaðu þetta:	To specify this:
nafn	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.
lit	Enter a color. For exampl: 200.
leið	a.      Smelltu and enter a preference value. For exampá: 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.
• Ef þú vilt stilla upp þjónustu sem hefur kröfur sem passa ekki við þær sem við lýsum í þessu dæmiampHafðu samband við viðskiptavinaþjónustu Cisco.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Breyta SR-MPLS stefnum

• Þú getur aðeins breytt eða eytt SR-MPLS stefnum sem hafa verið búnar til með Crosswork Network Controller API eða UI. Fylgdu þessum skrefum til að view, breyta eða eyða SR-MPLS stefnu.
• Skref 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Skref 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Skref 3: Veldu View upplýsingar eða Breyta/Eyða. Eftir að þú hefur uppfært upplýsingar um SR-MPLS stefnuna geturðu forstilltview breytingarnar á kortinu áður en það er vistað.

Algengar spurningar

Sp.: Hversu margar stefnur er hægt að birta á kortinu yfir svæði?

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

Sp.: Get ég flutt út valin gögn úr upplýsingum um stefnuna? view?

A: Nei, þú getur aðeins flutt öll gögn út í CSV skrá file from the policy details view.

Skjöl / auðlindir

CISCO SR-MPLS, SRv6 Crosswork netstýring [pdfNotendahandbók SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork netstýring, SR-MPLS SRv6, Crosswork netstýring, netstýring, stýring

Heimildir

• Notendahandbók