Controlador de rede cruzada CISCO SR-MPLS,SRv6

Información do produto

Especificacións

• Nome do produto: Controlador de rede Cisco Crosswork
• Funcionalidades compatibles: xestión de políticas SR-MPLS e SRv6
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Instrucións de uso do produto

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view no mapa.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Na columna Accións, escolla > View detalles para unha das políticas SR-MPLS ou SRv6.
• View the policy details, including segment lists and path computation constraints.
• Podes exportar todos os datos a un CSV file dende isto view.
• Copia o URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS e 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íticas SR-MPLS e SRv6 no mapa topolóxico

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

callout Non.	Descrición
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: Se os dous A e 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	O contido desta xanela depende do que se seleccionou ou filtrou. Neste exemploample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 pestanas para view a lista respectiva de políticas SR-TE.

callout Non.	Descrición
7	Exportacións todos data into a CSV fileNon podes exportar datos seleccionados ou filtrados.
8	O 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 actualmente listed in the SR Policy table.
9	Esta opción permíteche escoller como se debe aplicar o filtro de grupo (cando estea en uso) aos datos da táboa. Por exemploample, se 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 Detalles da política SR-MPLS e SRv6

• View Detalles a nivel de política de SR-MPLS ou SRv6 TE, así como listas de segmentos e calquera restrición de cálculo de ruta configurada para cada ruta candidata.

Procedemento

Paso 1

• From the Actions column, choose > View detalles para unha das políticas SR-MPLS ou SRv6.

Paso 2

• View Detalles da política SR-MPLS ou SRv6. Desde o navegador, podes copiar o URL e compartir con outras persoas.

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 a última vez que se actualizou o valor.

Visualizar a ruta e as métricas de IGP

• View a ruta física e as métricas entre os puntos finais das políticas SR-MPLS seleccionadas.

Procedemento

• 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étricas sobre as ligazóns participantes.
• Paso 3: Fai clic > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Nota
You must check the Show IGP Path check box to view métricas.

Atopar varias rutas candidatas (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.

Notas importantes

• 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’.
• Podes view rutas explícitas activas pero non rutas explícitas candidatas inactivas na interface de usuario.

Antes de comezar
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 a política SR-TE que está resaltada no mapa topolóxico.
• Neste exampé dicir, ves que a ruta activa vai de cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.

Paso 3: View a lista de camiños candidatos.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View detalles. Aparecerá unha lista de rutas candidatas xunto cos detalles da política na xanela de detalles da política SR. O A verde baixo a columna Estado indica a ruta activa.

• 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 rutas candidatas explícitas.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Neste exampé dicir, ves que a ruta alternativa vai directamente de cw-xrv53 > cw-xrv60.

Visualizar as rutas subxacentes asociadas a unha etiqueta de ID de segmento de vinculación (B-SID) definida

• O Controlador de rede Crosswork permíteche visualizar a ruta subxacente dun salto B-SID que configuraches manualmente nun dispositivo ou que configuraches mediante o Controlador de rede Crosswork. Neste exemploample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• Para view a ruta subxacente B-SID para unha política SR-MPLS ou SRv6, faga o seguinte:

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.
Neste exampé dicir, ves que a ruta B-SID vai de cw-xrv51 a cw-xrv52.

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

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

• Neste exampé dicir, a ruta subxacente vai en realidade de cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.

Visualizar rutas SR nativas

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

Requisitos previos do dispositivo

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

Visualizar rutas nativas

• Siga estes pasos para crear unha consulta de ruta.

Paso 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Paso 2: Click New query.
Paso 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 consultas pasadas para volver ao panel de consultas de ruta. Se xa tiñas consultas de ruta na lista, podes view detalles existentes mentres a nova consulta continúa a executarse en segundo plano, o que se indica coa icona azul En execución na columna Estado da consulta. Cando o novo estado da consulta se torna verde e se completa, pódese viewed.

Paso 4: Fai clic View resultados cando estea dispoñible na ventá emerxente ID da consulta en execución. Aparece a xanela Detalles da ruta cos detalles das rutas dispoñibles correspondentes, mentres que o mapa de topoloxía mostra as rutas IGP SR nativas dispoñibles á esquerda.

Configurar as afinidades de enlace de TE en 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 (por 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 descricións e comandos de configuración compatibles (por exemplo,ample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Os seguintes exampmostra unha configuración de afinidade SR-TE (mapa de afinidade) nun dispositivo:

• Paso 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.
• Paso 2: Click + Create to add a new affinity mapping.
• Paso 3: Enter the name and the bit it will be assigned. For example (usando a configuración anterior):

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

Consideracións sobre a implementación de políticas

Antes de aprovisionar políticas, considere estas opcións.

• 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 configuracións.

Crear políticas SR-MPLS explícitas

• Esta tarefa crea políticas SR-MPLS usando unha ruta explícita (fixa) que consiste nunha lista de ID de segmento de prefixo ou adxacencia (lista SID), cada un representando un nodo ou ligazón ao longo da ruta. Siga estes pasos para crear políticas SR-MPLS explícitas.

Antes de comezar

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

Paso 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Paso 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).

Paso 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view unha descrición do campo.
Consello
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.

• Paso 4: Under Policy path, click Explicit path and enter a path name.
• Paso 5: Add segments that will be part of the SR-MPLS policy path.
• Paso 6: Fai clic en Preview and confirm that the policy you created matches your intent.
• Paso 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.
• Paso 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 e confirme os detalles da nova política SR-MPLS. Na táboa Enxeñaría de tráfico, faga clic en e seleccione View detalles.

Nota

• Nunha configuración con moitos nodos, políticas ou interfaces, pode producirse un tempo de espera durante a implementación de políticas. Para configurar as opcións de tempo de espera, consulte Configurar os axustes de tempo de espera de TE.

Crear políticas SR-MPLS dinámicas baseadas na intención de optimización
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.

• Paso 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Paso 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).
• Paso 3: En Detalles da política, introduza ou seleccione os valores da política SR-MPLS requiridos. Pase o punteiro do rato por riba de view unha descrición de cada campo.

Consello

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

Consideracións de afinidade

• 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.
• Paso 7: Under Segments, select whether or not protected segments should be used when available.
• Paso 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ón do 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.
• Paso 9: Fai clic en Preview. The path is highlighted on the map.
• Paso 10: To commit the policy path, click Provision.
• Paso 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 e confirme os detalles da nova política SR-MPLS. Na táboa Enxeñaría de tráfico, faga clic e seleccione View detalles.

Crear políticas SR-TE (iniciadas por PCC)

• Esta tarefa crea políticas SR-MPLS ou SRv6 explícitas ou dinámicas usando Cisco Network Services Orchestrator (NSO) a través da interface de usuario de Crosswork.

Antes de comezar
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.

Paso 1: No menú principal, escolla Servizos e enxeñaría de tráfico > Aprovisionamento (NSO).
Paso 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Nota

• You may also click para importar unha política SR-TE existente.
• Paso 3: Enter the policy constraints and required values.
• You must populate the following options:

Táboa 1: Configuración da política SR-TE

Expandir isto:	To specify this:
nome	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.
cor	Enter a color. For exampLe: 200.
camiño	a.      Fai clic and enter a preference value. For exampnúmero: 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.
• Se queres configurar un servizo que teña requisitos que non coincidan cos que describimos neste exemploampé dicir, póñase en contacto co departamento de Experiencia do cliente de Cisco.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Modificar as políticas de SR-MPLS

• Só podes modificar ou eliminar políticas SR-MPLS que se crearon mediante a API ou a interface de usuario de Crosswork Network Controller. Sigue estes pasos para view, modificar ou eliminar unha política SR-MPLS.
• Paso 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Paso 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Paso 3: Escolle View detalles ou Editar/Eliminar. Despois de actualizar os detalles da política SR-MPLS, pode predefinirview os cambios no mapa antes de gardalo.

FAQ

P: Cantas políticas se poden mostrar no mapa topolóxico?

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

P: Podo exportar os datos seleccionados dos detalles da póliza? view?

R: Non, só podes exportar todos os datos a un ficheiro CSV file from the policy details view.

Documentos/Recursos

Controlador de rede cruzada CISCO SR-MPLS,SRv6 [pdfGuía do usuario SR-MPLS, SRv6, SR-MPLS SRv6 Controlador de rede Crosswork, SR-MPLS SRv6, Controlador de rede Crosswork, Controlador de rede, Controlador

Referencias

• Manual de usuario