Controlador de xarxa CISCO SR-MPLS, SRv6 Crosswork
Informació del producte
Especificacions
- Nom del producte: Controlador de xarxa Cisco Crosswork
- Funcions compatibles: Gestió de polítiques SR-MPLS i SRv6
- Maximum Policies Displayed: Up to 10 policies with separate colored links
Instruccions d'ús del producte
- Navigate to Services & Traffic Engineering > Traffic Engineering.
- In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view al mapa.
- You can select up to 10 policies that will appear as separate colored links on the map.
- A la columna Accions, trieu > View detalls d'una de les polítiques SR-MPLS o SRv6.
- View the policy details, including segment lists and path computation constraints.
- Podeu exportar totes les dades a un CSV file a partir d'això view.
- Copia el URL from the browser to share SR-MPLS or SRv6 policy details with others.
SR-MPLS i 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 Polítiques SR-MPLS i SRv6 al mapa de topologia
- 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 al mapa.
- You can select up to 10 policies that will appear as separate colored links.
| Cridar No. | Descripció |
| 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: Si tots dos A i 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 | El contingut d'aquesta finestra depèn del que s'hagi seleccionat o filtrat. En aquest exempleample, the SR-MPLS tab is selected, and the SR Policy table is displayed. |
| 6 | Click on either the SR-MPLS or SRv6 pestanyes a view la llista respectiva de polítiques SR-TE. |
).| Cridar No. | Descripció |
| 7 | Exportacions tots data into a CSV fileNo podeu exportar dades seleccionades o filtrades. |
| 8 | El 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 actualment listed in the SR Policy table. |
| 9 | Aquesta opció us permet triar com s'ha d'aplicar el filtre de grup (quan s'utilitza) a les dades de la taula. Per exempleample, si 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 Detalls de les polítiques SR-MPLS i SRv6
- View Detalls del nivell de política SR-MPLS o SRv6 TE, així com llistes de segments i qualsevol restricció de càlcul de ruta configurada per ruta candidata.
Procediment
Pas 1
- From the Actions column, choose
> View detalls d'una de les polítiques SR-MPLS o SRv6.
Pas 2
- View Detalls de la política SR-MPLS o SRv6. Des del navegador, podeu copiar el URL i compartir amb els altres.
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 l'última vegada que es va actualitzar el valor.
Visualitzar la ruta i les mètriques IGP
- View la ruta física i les mètriques entre els punts finals de les polítiques SR-MPLS seleccionades.
Procediment
- 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ètriques sobre els enllaços participants.
- Pas 3: Feu clic
> Metrics tab. - Step 4: Toggle applicable metrics to ON.
Nota
You must check the Show IGP Path check box to view mètriques.
Trobar múltiples camins candidats (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.
Notes importants
- 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’.
- Tu pots view camins explícits actius però no camins explícits candidats inactius a la interfície d'usuari.
Abans de començar
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 la política SR-TE que està ressaltada al mapa topològic.
- En aquest exampés a dir, veieu que la ruta activa va de cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.
Pas 3: View la llista de camins candidats.
- From the SR-MPLS or SRv6 Policy table Actions column, click
> View detalls. A la finestra de detalls de la política SR apareix una llista de camins candidats juntament amb els detalls de la política. La A verda sota la columna Estat indica el camí actiu.
- 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 camins candidats explícits.
- From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
- En aquest exampés a dir, veieu que la ruta alternativa va directament de cw-xrv53 > cw-xrv60.
Visualitzar els camins subjacents associats amb una etiqueta d'ID de segment d'enllaç (B-SID) definida
- El controlador de xarxa Crosswork us permet visualitzar la ruta subjacent d'un salt B-SID que heu configurat manualment en un dispositiu o que heu configurat mitjançant el controlador de xarxa Crosswork. En aquest exempleample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
- A view la ruta subjacent B-SID per a una política SR-MPLS o SRv6, feu el següent:
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.
En aquest exampÉs a dir, veieu que la ruta B-SID va de cw-xrv51 a cw-xrv52.
Step 3: From the SR policy details page, click > View detalls.
Step 4: Expand the active path and click the B-Sid Label ID to see the underlying path.
- En aquest exampés a dir, la ruta subjacent en realitat va de cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.
Visualitza les rutes SR natives
- 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.
Requisits previs del dispositiu
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 exampLI:
Visualitza els camins nadius
- Segueix aquests passos per crear una consulta de ruta.
Pas 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Pas 2: Click New query.
Pas 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 consultes anteriors per tornar al tauler de consultes de ruta. Si ja teníeu consultes de ruta a la llista, podeu view detalls existents a mesura que la nova consulta continua executant-se en segon pla, cosa que s'indica amb la icona blava En execució a la columna Estat de la consulta. Quan el nou estat de la consulta es torna verd i s'ha completat, es pot viewed.
Pas 4: Feu clic View resultats quan estigui disponible a la finestra emergent Running Query ID. Apareix la finestra Path Details amb els detalls dels camins disponibles corresponents, mentre que el mapa de topologia mostra els camins IGP SR natius disponibles a l'esquerra.
Configurar les afinitats d'enllaç TE al controlador de xarxa 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 (per 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 descripcions i ordres de configuració compatibles (per exemple,ampel, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
- El següent example mostra una configuració d'afinitat SR-TE (mapa d'afinitat) en un dispositiu:
- Pas 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.
- Pas 2: Click + Create to add a new affinity mapping.
- Pas 3: Enter the name and the bit it will be assigned. For example (utilitzant la configuració anterior):
- Pas 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.
Consideracions sobre el desplegament de polítiques
Abans de definir polítiques, tingueu en compte aquestes opcions.
- 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 samples configuracions.
Crea polítiques SR-MPLS explícites
- Aquesta tasca crea polítiques SR-MPLS utilitzant una ruta explícita (fixa) que consisteix en una llista d'ID de segment de prefix o adjacència (llista SID), cadascun dels quals representa un node o enllaç al llarg de la ruta. Segueix aquests passos per crear polítiques SR-MPLS explícites.
Abans de començar
- 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.
Pas 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Pas 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).
Pas 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view una descripció del camp.
Consell
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.
- Pas 4: Under Policy path, click Explicit path and enter a path name.
- Pas 5: Add segments that will be part of the SR-MPLS policy path.
- Pas 6: Feu clic a Preview and confirm that the policy you created matches your intent.
- Pas 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.
- Pas 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 i confirmeu els detalls de la nova política SR-MPLS. A la taula Enginyeria de trànsit, feu clic a i seleccioneu View detalls.
Nota
- En una configuració amb un nombre elevat de nodes, polítiques o interfícies, es pot produir un temps d'espera durant la implementació de polítiques. Per configurar les opcions de temps d'espera, consulteu Configuració dels paràmetres de temps d'espera de TE.
Crea polítiques SR-MPLS dinàmiques basades en la intenció d'optimització
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.
- Pas 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
- Pas 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).
- Pas 3: A Detalls de la política, introduïu o seleccioneu els valors de la política SR-MPLS necessaris. Passeu el punter del ratolí per sobre de view una descripció de cada camp.
Consell
- 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.
- Pas 4: Under Policy path, click Dynamic path and enter a path name.
- Pas 5: Under Optimization objective, select the metric you want to minimize.
- Pas 6: Define any applicable constraints and disjointness.
Consideracions d'afinitat
- 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.
- Pas 7: Under Segments, select whether or not protected segments should be used when available.
- Pas 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.
Informació del 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.
- Pas 9: Feu clic a Preview. The path is highlighted on the map.
- Pas 10: To commit the policy path, click Provision.
- Pas 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 i confirmeu els detalls de la nova política SR-MPLS. A la taula Enginyeria de trànsit, feu clic i seleccioneu View detalls.
Crea polítiques SR-TE (iniciades pel PCC)
- Aquesta tasca crea polítiques SR-MPLS o SRv6 explícites o dinàmiques mitjançant Cisco Network Services Orchestrator (NSO) a través de la interfície d'usuari de Crosswork.
Abans de començar
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.
Pas 1: Al menú principal, trieu Serveis i enginyeria de trànsit > Aprovisionament (NSO).
Pas 2: From SR-TE > Policy, click
. Crosswork displays the Create SR-TE > Policy window.
Nota
- You may also click
per importar una política SR-TE existent. - Pas 3: Enter the policy constraints and required values.
- You must populate the following options:
Taula 1: Configuració de la política SR-TE
| Expandir això: | To specify this: |
| nom | 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. |
| color | Enter a color. For exampel: 200. |
| camí | a. Feu clic and enter a preference value. For exampel: 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.
- Si voleu configurar un servei que té requisits que no coincideixen amb els que descrivim en aquest exempleampés a dir, poseu-vos en contacte amb Cisco Customer Experience.
- Step 5: When you are ready to activate the policy, click Commit Changes.
Modificar les polítiques SR-MPLS
- Només podeu modificar o suprimir polítiques SR-MPLS que s'hagin creat mitjançant l'API o la interfície d'usuari del controlador de xarxa Crosswork. Seguiu aquests passos per a view, modificar o suprimir una política SR-MPLS.
- Pas 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
- Pas 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
- Pas 3: Tria View detalls o Edita/Suprimeix. Després d'actualitzar els detalls de la política SR-MPLS, podeu pre-view els canvis al mapa abans de desar-lo.
Preguntes freqüents
P: Quantes polítiques es poden mostrar al mapa topològic?
A: Up to 10 policies can be selected and displayed as separate colored links on the map.
P: Puc exportar les dades seleccionades dels detalls de la pòlissa? view?
A: No, només podeu exportar totes les dades a un CSV file from the policy details view.
Documents/Recursos
 |
Controlador de xarxa CISCO SR-MPLS, SRv6 Crosswork [pdfGuia de l'usuari SR-MPLS, SRv6, SR-MPLS SRv6 Controlador de xarxa Crosswork, SR-MPLS SRv6, Controlador de xarxa Crosswork, Controlador de xarxa, Controlador |