Rheolwr Rhwydwaith Trawsweithiol CISCO SR-MPLS, SRv6

Gwybodaeth Cynnyrch

Manylebau

• Enw Cynnyrch: Rheolydd Rhwydwaith Cisco Crosswork
• Nodweddion â Chymorth: rheoli polisïau SR-MPLS a SRv6
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Cyfarwyddiadau Defnydd Cynnyrch

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view ar y map.
• You can select up to 10 policies that will appear as separate colored links on the map.
• O'r golofn Camau Gweithredu, dewiswch > View manylion ar gyfer un o'r polisïau SR-MPLS neu SRv6.
• View the policy details, including segment lists and path computation constraints.
• Gallwch allforio'r holl ddata i mewn i ffeil CSV file o hyn view.
• Copïwch y URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS a 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 Polisïau SR-MPLS a SRv6 ar y map topoleg

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

Galw allan Nac ydw.	Disgrifiad
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: Os y ddau A a 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	Mae cynnwys y ffenestr hon yn dibynnu ar yr hyn sydd wedi'i ddewis neu ei hidlo. Yn yr enghraifft honample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 tabiau i view y rhestr berthnasol o bolisïau SR-TE.

Galw allan Nac ydw.	Disgrifiad
7	Allforion i gyd data into a CSV fileNi allwch allforio data a ddewiswyd na data wedi'i hidlo.
8	Mae'r 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 ar hyn o bryd listed in the SR Policy table.
9	Mae'r opsiwn hwn yn caniatáu ichi ddewis sut y dylid cymhwyso'r hidlydd grŵp (pan gaiff ei ddefnyddio) ar ddata'r tabl. Er enghraifft.ample, os 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 Manylion polisi SR-MPLS a SRv6

• View Manylion lefel polisi SR-MPLS neu SRv6 TE yn ogystal â rhestrau segment ac unrhyw gyfyngiadau cyfrifo llwybr a ffurfweddwyd fesul llwybr ymgeisydd.

Gweithdrefn

Cam 1

• From the Actions column, choose > View manylion ar gyfer un o'r polisïau SR-MPLS neu SRv6.

Cam 2

• View Manylion polisi SR-MPLS neu SRv6. O'r porwr, gallwch gopïo'r URL a rhannu gydag eraill.

Nodyn

• 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 y tro diwethaf i'r gwerth gael ei ddiweddaru.

Delweddu llwybr a metrigau IGP

• View y llwybr ffisegol a'r metrigau rhwng pwyntiau terfyn y polisïau SR-MPLS a ddewiswyd.

Gweithdrefn

• 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 metrigau ar ddolenni sy'n cymryd rhan.
• Cam 3: Cliciwch > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Nodyn
You must check the Show IGP Path check box to view metrigau.

Dod o Hyd i Lwybrau Ymgeisydd Lluosog (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.

Nodiadau Pwysig

• 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’.
• Gallwch chi view llwybrau penodol gweithredol ond nid llwybrau penodol ymgeiswyr anweithredol yn y rhyngwyneb defnyddiwr.

Cyn i chi ddechrau
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 y polisi SR-TE sydd wedi'i amlygu ar y map topoleg.
• Yn y cynample, rydych chi'n gweld bod y llwybr gweithredol yn mynd o cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.

Cam 3: View rhestr y llwybrau ymgeiswyr.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View manylion. Mae rhestr o lwybrau posibl yn ymddangos ynghyd â manylion polisi yn ffenestr manylion polisi SR. Mae'r A gwyrdd o dan y golofn State yn nodi'r llwybr gweithredol.

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

Nodyn
You will not be able to select or view llwybrau ymgeiswyr penodol.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Yn y cynample, rydych chi'n gweld bod y llwybr arall yn mynd yn uniongyrchol o cw-xrv53 > cw-xrv60.

Delweddu llwybrau sylfaenol sy'n gysylltiedig â label ID Segment-Rhwymo (B-SID) wedi'i ddiffinio

• Mae Rheolydd Rhwydwaith Crosswork yn caniatáu ichi ddelweddu llwybr sylfaenol hop B-SID rydych chi wedi'i ffurfweddu â llaw ar ddyfais neu wedi'i ffurfweddu gan ddefnyddio Rheolydd Rhwydwaith Crosswork. Yn yr enghraifft honample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• I view y llwybr sylfaenol B-SID ar gyfer polisi SR-MPLS neu SRv6, gwnewch y canlynol:

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.
Yn y cynample, rydych chi'n gweld bod y llwybr B-SID yn mynd o cw-xrv51 i cw-xrv52.

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

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

• Yn y cynample, mae'r llwybr sylfaenol mewn gwirionedd yn mynd o cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.

Delweddu llwybrau SR brodorol

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

Rhagofynion dyfais

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:
     Nodyn
     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:

Delweddu llwybrau brodorol

• Dilynwch y camau hyn i greu ymholiad llwybr.

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

Nodyn
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View ymholiadau blaenorol i ddychwelyd i'r Dangosfwrdd Ymholiadau Llwybr. Os oedd gennych ymholiadau llwybr yn y rhestr eisoes, gallwch view manylion presennol wrth i'r ymholiad newydd barhau i redeg yn y cefndir, a nodir gan yr eicon Rhedeg glas yn y golofn Cyflwr yr Ymholiad. Pan fydd cyflwr yr ymholiad newydd yn troi'n wyrdd, ac wedi'i gwblhau, gellir ei viewgol.

Cam 4: Cliciwch View canlyniadau pan fydd ar gael ar y naidlen ID Ymholiad Rhedeg. Mae'r ffenestr Manylion Llwybr yn ymddangos gyda manylion llwybrau cyfatebol sydd ar gael tra bod y map topoleg yn dangos y llwybrau IGP SR Brodorol sydd ar gael ar y chwith.

Ffurfweddu perthnasau cyswllt TE yn Rheolydd Rhwydwaith Crosswork

• 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 (ar gyfer 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 disgrifiadau a gorchmynion ffurfweddu â chymorth (er enghraifftample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Mae'r cynampMae le yn dangos cyfluniad affinedd SR-TE (map affinedd) ar ddyfais:

• Cam 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.
• Cam 2: Click + Create to add a new affinity mapping.
• Cam 3: Enter the name and the bit it will be assigned. For example (gan ddefnyddio'r ffurfweddiad uchod):

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

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

Ystyriaethau defnyddio polisïau

Cyn darparu polisïau, ystyriwch yr opsiynau hyn.

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

Creu polisïau SR-MPLS penodol

• Mae'r dasg hon yn creu polisïau SR-MPLS gan ddefnyddio llwybr penodol (sefydlog) sy'n cynnwys rhestr o IDau rhagddodiad neu Segment cyfagos (rhestr SID), pob un yn cynrychioli nod neu ddolen ar hyd y llwybr. Dilynwch y camau hyn i greu polisïau SR-MPLS penodol.

Cyn i chi ddechrau

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

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

Nodyn
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).

Cam 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view disgrifiad o'r maes.
Tip
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.

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

Nodyn
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 a chadarnhau manylion polisi SR-MPLS newydd. O'r tabl peirianneg traffig, cliciwch ar a dewiswch View manylion.

Nodyn

• Ar osodiad gyda chyfrif uchel o nodau, polisïau neu ryngwynebau, gall terfyn amser ddigwydd yn ystod y defnydd o bolisïau. I ffurfweddu opsiynau terfyn amser, gweler Ffurfweddu gosodiadau terfyn amser TE.

Creu polisïau SR-MPLS deinamig yn seiliedig ar fwriad optimeiddio
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.

• Cam 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Cam 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).
• Cam 3: O dan fanylion polisi, nodwch neu dewiswch y gwerthoedd polisi SR-MPLS gofynnol. Hofrannwch y pwyntydd llygoden drosodd i view disgrifiad o bob maes.

Tip

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

Ystyriaethau perthnasedd

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

Gwybodaeth 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.
• Cam 9: Cliciwch Cynview. The path is highlighted on the map.
• Cam 10: To commit the policy path, click Provision.
• Cam 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.

Nodyn

• 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 a chadarnhau manylion polisi SR-MPLS newydd. O'r tabl Peirianneg traffig, cliciwch a dewiswch View manylion.

Creu polisïau SR-TE (a gychwynnwyd gan y PCC)

• Mae'r dasg hon yn creu polisïau SR-MPLS neu SRv6 penodol neu ddeinamig gan ddefnyddio Cisco Network Services Orchestrator (NSO) trwy UI Crosswork.

Cyn i chi ddechrau
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.

Cam 1: O'r brif ddewislen, dewiswch Wasanaethau a Pheirianneg Traffig > Darpariaeth (NSO).
Cam 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Nodyn

• You may also click i fewnforio polisi SR-TE sy'n bodoli eisoes.
• Cam 3: Enter the policy constraints and required values.
• You must populate the following options:

Tabl 1: Ffurfweddiad Polisi SR-TE

Ehangu hwn:	To specify this:
enw	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.
lliw	Enter a color. For exampcyf: 200.
llwybr	a.      Cliciwch and enter a preference value. For exampLe: 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.
• Os ydych chi eisiau ffurfweddu gwasanaeth sydd â gofynion nad ydynt yn cyd-fynd â'r rhai a ddisgrifir gennym yn yr enghraifft honample, cysylltwch â Phrofiad Cwsmeriaid Cisco.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Addasu polisïau SR-MPLS

• Dim ond polisïau SR-MPLS sydd wedi'u creu gan ddefnyddio API neu UI Rheolwr Rhwydwaith Crosswork y gallwch eu haddasu neu eu dileu. Dilynwch y camau hyn i view, addasu, neu ddileu polisi SR-MPLS.
• Cam 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Cam 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Cam 3: dewis View manylion neu Golygu/Dileu. Ar ôl diweddaru manylion polisi SR-MPLS, gallwch chi rag-drefnuview y newidiadau ar y map cyn ei gadw.

FAQ

C: Faint o bolisïau y gellir eu harddangos ar y map topoleg?

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

C: A allaf allforio data a ddewiswyd o fanylion y polisi view?

A: Na, dim ond i CSV y gallwch allforio'r holl ddata file from the policy details view.

Dogfennau / Adnoddau

Rheolwr Rhwydwaith Trawsweithiol CISCO SR-MPLS, SRv6 [pdfCanllaw Defnyddiwr SR-MPLS, SRv6, Rheolydd Rhwydwaith Croeswaith SR-MPLS SRv6, SR-MPLS SRv6, Rheolydd Rhwydwaith Croeswaith, Rheolydd Rhwydwaith, Rheolydd

Cyfeiriadau

• Llawlyfr Defnyddiwr