CISCO SR-MPLS,SRv6 Crosswork Network Controller
Impormasyon sa Produkto
Mga detalye
- Ngalan sa Produkto: Cisco Crosswork Network Controller
- Gisuportahan nga mga Feature: SR-MPLS ug SRv6 nga pagdumala sa palisiya
- Maximum Policies Displayed: Up to 10 policies with separate colored links
Mga Instruksyon sa Paggamit sa Produkto
- Navigate to Services & Traffic Engineering > Traffic Engineering.
- In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view sa mapa.
- You can select up to 10 policies that will appear as separate colored links on the map.
- Gikan sa kolum nga Mga Aksyon, pilia ang > View mga detalye para sa usa sa mga polisiya sa SR-MPLS o SRv6.
- View the policy details, including segment lists and path computation constraints.
- Mahimo nimong i-export ang tanan nga datos sa usa ka CSV file gikan niini view.
- Kopyaha ang URL from the browser to share SR-MPLS or SRv6 policy details with others.
SR-MPLS ug 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 ug SRv6 nga mga palisiya sa topology nga mapa
- 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 sa mapa.
- You can select up to 10 policies that will appear as separate colored links.
| Callout Dili. | Deskripsyon |
| 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: Kung pareho A ug 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 | Ang sulod niini nga bintana nagdepende sa gipili o nasala. Niining example, the SR-MPLS tab is selected, and the SR Policy table is displayed. |
| 6 | Click on either the SR-MPLS or SRv6 tabs sa view ang tagsa-tagsa nga listahan sa mga polisiya sa SR-TE. |
).| Callout Dili. | Deskripsyon |
| 7 | Mga eksport tanan data into a CSV file. Dili nimo ma-export ang pinili o nasala nga datos. |
| 8 | Ang 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 sa pagkakaron listed in the SR Policy table. |
| 9 | Kini nga kapilian nagtugot kanimo sa pagpili kung giunsa ang pagsala sa grupo (kung gigamit) kinahanglan gamiton sa datos sa lamesa. Kay example, kung 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 Mga detalye sa palisiya sa SR-MPLS ug SRv6
- View Ang mga detalye sa lebel sa palisiya sa SR-MPLS o SRv6 TE ingon man ang mga lista sa bahin ug bisan unsang mga limitasyon sa pag-compute sa agianan nga gi-configure sa usa ka basehanan sa matag kandidato.
Pamaagi
Lakang 1
- From the Actions column, choose
> View mga detalye para sa usa sa mga polisiya sa SR-MPLS o SRv6.
Lakang 2
- View Mga detalye sa palisiya sa SR-MPLS o SRv6. Gikan sa browser, mahimo nimong kopyahon ang URL ug ipaambit sa uban.
Nota
- 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 ang katapusang higayon nga gi-update ang kantidad.
I-visualize ang IGP path ug metrics
- View ang pisikal nga agianan ug sukdanan tali sa mga endpoint sa pinili nga SR-MPLS nga mga palisiya.
Pamaagi
- 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 metrics sa mga partisipanteng link.
- Lakang 3: Pag-klik
> Metrics tab. - Step 4: Toggle applicable metrics to ON.
Nota
You must check the Show IGP Path check box to view metrics.
Pangitag Daghang Dalan sa Kandidato (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.
Importante nga mga Nota
- 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’.
- Mahimo nimo view aktibo nga klaro nga mga agianan apan dili dili aktibo nga kandidato nga klaro nga mga agianan sa UI.
Sa dili ka pa magsugod
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 ang palisiya sa SR-TE nga gipasiugda sa mapa sa topolohiya.
- Niining exampLe, nakita nimo nga ang aktibo nga agianan gikan sa cw-xrv53> cw-xrv57> cw-xrv58> cw-xrv59> cw-xrv60.
Lakang 3: View ang listahan sa mga dalan sa kandidato.
- From the SR-MPLS or SRv6 Policy table Actions column, click
> View mga detalye. Ang usa ka lista sa mga agianan sa kandidato makita kauban ang mga detalye sa palisiya sa bintana sa mga detalye sa palisiya sa SR. Ang berdeng A ubos sa kolum sa Estado nagpakita sa aktibong dalan.
- 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.
Nota
You will not be able to select or view klaro nga mga agianan sa kandidato.
- From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
- Niining example, nakita nimo nga ang alternatibong agianan diretso gikan sa cw-xrv53> cw-xrv60.
Tan-awa ang nagpahiping mga agianan nga may kalabotan sa usa ka gipiho nga Binding-Segment ID (B-SID) nga label
- Gitugotan ka sa Crosswork Network Controller nga mahanduraw ang nagpahiping agianan sa usa ka B-SID hop nga imong gi-configure nga mano-mano sa usa ka aparato o gi-configure gamit ang Crosswork Network Controller. Niining example, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
- Sa view ang B-SID nga nagpahiping dalan alang sa usa ka polisiya sa SR-MPLS o SRv6, buhata ang mosunod:
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.
Niining exampLe, nakita nimo nga ang B-SID nga agianan gikan sa cw-xrv51 hangtod sa cw-xrv52.
Step 3: From the SR policy details page, click > View mga detalye.
Step 4: Expand the active path and click the B-Sid Label ID to see the underlying path.
- Niining exampOo, ang nagpahiping agianan sa tinuud gikan sa cw-xrv51> cw-xrv54> cw-xrv53> cw-xrv52.
Tan-awa ang lumad nga SR nga mga agianan
- 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.
Mga kinahanglanon sa aparato
Confirm the following device software and configurations are met prior to visualizing native paths.
- Devices should be running Cisco IOS XR 7.3.2 or higher. Run show version command to verify it.
- 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:
Nota
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.
- Run show run grpc to confirm GRPC configuration. You should see something similar to this:
- 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.
- Devices should have the CDG router static address. Static route should be added from the device to the southbound CDG IP address. For example:
Handurawa ang lumad nga mga agianan
- Sunda kini nga mga lakang aron makahimo usa ka pangutana sa agianan.
Lakang 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Lakang 2: Click New query.
Lakang 3: Enter the device information in the required fields to find available Native SR IGP Paths and click Get paths.
Nota
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View nangaging mga pangutana aron mobalik sa Path Query Dashboard. Kung naa na kay mga pangutana sa dalan sa lista, mahimo nimo view kasamtangan nga mga detalye samtang ang bag-ong pangutana nagpadayon sa pagdagan sa background, nga gipakita sa asul nga Running icon sa Query State column. Kung ang bag-ong kahimtang sa pangutana mahimong berde, ug nahuman na, mahimo kini viewed.
Lakang 4: Pag-klik View resulta kon kini magamit sa Running Query ID pop-up. Ang Path Details nga bintana makita uban sa katugbang nga anaa nga mga detalye sa mga agianan samtang ang topology nga mapa nagpakita sa anaa nga Native SR IGP nga mga agianan sa wala.
I-configure ang TE link affinities sa 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 (alang sa 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 mga paghubit ug gisuportahan nga mga sugo sa pag-configure (alang sa example, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
- Ang mosunod nga example nagpakita ug SR-TE affinity configuration (affinity-map) sa usa ka device:
- Lakang 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.
- Lakang 2: Click + Create to add a new affinity mapping.
- Lakang 3: Enter the name and the bit it will be assigned. For example (gamit ang configuration sa ibabaw):
- Lakang 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
Nota
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.
Mga konsiderasyon sa pagdeploy sa palisiya
Sa wala pa ang mga palisiya sa paghatag, hunahunaa kini nga mga kapilian.
- 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 sampmga pagsalig.
Paghimo og klaro nga mga palisiya sa SR-MPLS
- Kini nga buluhaton nagmugna sa mga palisiya sa SR-MPLS gamit ang usa ka klaro (fixed) nga agianan nga naglangkob sa usa ka lista sa prefix o adjacency Segment IDs (listahan sa SID), ang matag usa nagrepresentar sa usa ka node o link sa agianan. Sunda kini nga mga lakang aron makahimo og klaro nga mga polisiya sa SR-MPLS.
Sa dili ka pa magsugod
- 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.
Lakang 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Lakang 2: Click Create > PCE Init.
Nota
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).
Lakang 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view usa ka paghulagway sa kapatagan.
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.
- Lakang 4: Under Policy path, click Explicit path and enter a path name.
- Lakang 5: Add segments that will be part of the SR-MPLS policy path.
- Lakang 6: Pag-klik Preview and confirm that the policy you created matches your intent.
- Lakang 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.
- Lakang 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.
Nota
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 ug kumpirmahi ang bag-ong mga detalye sa palisiya sa SR-MPLS. Gikan sa lamesa sa Traffic engineering, i-klik ang ug pilia View mga detalye.
Nota
- Sa usa ka setup nga adunay taas nga node, polisiya, o mga ihap sa interface, ang usa ka timeout mahimong mahitabo sa panahon sa pagdeploy sa palisiya. Aron ma-configure ang mga opsyon sa timeout, tan-awa ang I-configure ang TE timeout settings.
Paghimo dinamikong mga palisiya sa SR-MPLS base sa katuyoan sa pag-optimize
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.
- Lakang 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
- Lakang 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).
- Lakang 3: Ubos sa mga detalye sa polisiya, isulod o pilia ang gikinahanglan nga SR-MPLS policy values. I-hover ang mouse pointer sa ibabaw view usa ka paghulagway sa matag field.
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.
- Lakang 4: Under Policy path, click Dynamic path and enter a path name.
- Lakang 5: Under Optimization objective, select the metric you want to minimize.
- Lakang 6: Define any applicable constraints and disjointness.
Mga konsiderasyon sa affinity
- 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.
- Lakang 7: Under Segments, select whether or not protected segments should be used when available.
- Lakang 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.
Impormasyon sa 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.
- Lakang 9: Pag-klik Preview. The path is highlighted on the map.
- Lakang 10: To commit the policy path, click Provision.
- Lakang 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.
Nota
- 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 ug kumpirmahi ang bag-ong mga detalye sa palisiya sa SR-MPLS. Gikan sa lamesa sa Traffic engineering, i-klik ug pilia View mga detalye.
Paghimo og SR-TE nga mga palisiya (PCC-gisugdan)
- Kini nga buluhaton nagmugna og klaro o dinamikong SR-MPLS o SRv6 nga mga palisiya gamit ang Cisco Network Services Orchestrator (NSO) pinaagi sa Crosswork UI.
Sa dili ka pa magsugod
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.
Lakang 1: Gikan sa main menu, pilia ang Services & Traffic Engineering > Provisioning (NSO).
Lakang 2: From SR-TE > Policy, click
. Crosswork displays the Create SR-TE > Policy window.
Nota
- You may also click
sa pag-import sa usa ka kasamtangan nga SR-TE nga palisiya. - Lakang 3: Enter the policy constraints and required values.
- You must populate the following options:
Talaan 1: SR-TE Policy Configuration
| Pagpalapad kini: | To specify this: |
| ngalan | 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. |
| kolor | Enter a color. For exampug: 200. |
| dalan | a. Pag-klik and enter a preference value. For exampug: 123
b. Select one of the following and toggle the switch to enable: • explicit-path—Click • 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.
- Kung gusto nimo i-configure ang usa ka serbisyo nga adunay mga kinahanglanon nga dili katumbas sa among gihulagway sa kini nga example, kontaka ang Cisco Customer Experience.
- Step 5: When you are ready to activate the policy, click Commit Changes.
Usba ang mga palisiya sa SR-MPLS
- Mahimo ra nimo usbon o papason ang mga palisiya sa SR-MPLS nga gihimo gamit ang Crosswork Network Controller API o UI. Sunda kini nga mga lakang sa view, pag-usab, o pagtangtang sa usa ka polisiya sa SR-MPLS.
- Lakang 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
- Lakang 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
- Lakang 3: Pilia View mga detalye o Edit/Delete. Human sa pag-update sa mga detalye sa polisiya sa SR-MPLS, mahimo nimong preview ang mga kausaban sa mapa sa dili pa kini i-save.
FAQ
P: Pila ka polisiya ang mapakita sa topology map?
A: Up to 10 policies can be selected and displayed as separate colored links on the map.
P: Mahimo ba nako i-export ang pinili nga datos gikan sa mga detalye sa palisiya view?
A: Dili, mahimo ra nimo ma-export ang tanan nga datos sa usa ka CSV file from the policy details view.
Mga Dokumento / Mga Kapanguhaan
 |
CISCO SR-MPLS,SRv6 Crosswork Network Controller [pdf] Giya sa Gumagamit SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork Network Controller, SR-MPLS SRv6, Crosswork Network Controller, Network Controller, Controller |