CISCO SR-MPLS, SRv6 Crosswork мрежен контролер

Информации за производот

Спецификации

• Име на производ: Cisco Crosswork мрежен контролер
• Поддржани функции: Управување со политики SR-MPLS и SRv6
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Упатство за употреба на производот

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view на картата.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Од колоната Дејства, изберете > View детали за една од SR-MPLS или SRv6 политиките.
• View the policy details, including segment lists and path computation constraints.
• Можете да ги извезете сите податоци во CSV file од ова view.
• Копирајте го URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS и 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 и SRv6 политики на тополошката мапа

• 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 на картата.
• You can select up to 10 policies that will appear as separate colored links.

Отповика бр.	Опис
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: Ако и двете 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	Содржината на овој прозорец зависи од тоа што е избрано или филтрирано. Во овој случајample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 јазичиња до view соодветната листа на полиси на SR-TE.

Отповика бр.	Опис
7	Извозот сите data into a CSV fileНе можете да извезете избрани или филтрирани податоци.
8	На 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 моментално listed in the SR Policy table.
9	Оваа опција ви овозможува да изберете како треба да се примени групен филтер (кога е во употреба) врз податоците од табелата. На пр.ampако, ако 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 Детали за политиката SR-MPLS и SRv6

• View Детали за нивото на политиката SR-MPLS или SRv6 TE, како и листи на сегменти и сите ограничувања за пресметка на патеки конфигурирани врз основа на патека за секој кандидат.

Постапка

Чекор 1

• From the Actions column, choose > View детали за една од SR-MPLS или SRv6 политиките.

Чекор 2

• View Детали за политиката SR-MPLS или SRv6. Од прелистувачот, можете да го копирате URL и споделувајте со другите.

Забелешка

• 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 последниот пат кога вредноста беше ажурирана.

Визуелизирајте ја IGP патеката и метриките

• View физичката патека и метриките помеѓу крајните точки на избраните SR-MPLS политики.

Постапка

• 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 метрики на линковите што учествуваат.
• Чекор 3: Кликнете > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Забелешка
You must check the Show IGP Path check box to view метрика.

Пронајди повеќекратни патеки на кандидати (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.

Важни забелешки

• 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’.
• Можеш view активни експлицитни патеки, но не и неактивни експлицитни патеки-кандидати во корисничкиот интерфејс.

Пред да започнете
A policy must be configured with MCPs on devices before they can be visualized on the Traffic Engineering topology map. This configuration can be done manually or within the Crosswork Network Controller.

• Step 1: From the main menu, choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS or SRv6 tab.
• Step :2 Navigate to the active SR-TE policy that has MCPs configured and view it on the topology map.
• Check the check box next to the SR-TE policy that has MCPs configured.
• View политиката SR-TE што е означена на тополошката мапа.
• Во овој ексampт.е., гледате дека активната патека оди од cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.

Чекор 3: View листата на кандидатски патеки.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View детали. Список на патеки-кандидати се појавува заедно со детали за политиката во прозорецот со детали за политиката SR. Зеленото A под колоната Состојба ја означува активната патека.

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

Забелешка
You will not be able to select or view експлицитни патеки на кандидати.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Во овој ексampт.е., гледате дека алтернативната патека оди директно од cw-xrv53 > cw-xrv60.

Визуелизирајте ги основните патеки поврзани со дефинирана етикета за ID на врзувачки сегмент (B-SID)

• Контролерот на мрежата Crosswork ви овозможува да ја визуелизирате основната патека на B-SID скок што сте го конфигурирале рачно на уред или сте го конфигурирале со помош на контролерот на мрежата Crosswork. На пример,ample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• На view основната патека B-SID за SR-MPLS или SRv6 политика, направете го следново:

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.
Во овој ексampт.е. гледате дека патеката B-SID оди од cw-xrv51 до cw-xrv52.

Step 3: From the SR policy details page, click > View детали.

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

• Во овој ексampт.е. основната патека всушност оди од cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.

Визуелизирајте ги нативните SR патеки

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

Предуслови за уредот

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:
     Забелешка
     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 exampле:

Визуелизирајте матични патеки

• Следете ги овие чекори за да креирате барање за патека.

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

Забелешка
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View претходни барања за да се вратите на контролната табла за барања за патеки. Ако веќе сте имале барања за патеки во листата, можете view постоечките детали додека новото барање продолжува да се извршува во позадина, што е означено со сината икона Running во колоната Query State. Кога новата состојба на барањето ќе стане зелена и ќе биде завршена, може да се viewед.

Чекор 4: Кликнете View резултатите кога ќе станат достапни во појавниот прозорец Running Query ID. Прозорецот Path Details се појавува со соодветни детали за достапните патеки, додека тополошката мапа ги прикажува достапните Native SR IGP патеки од левата страна.

Конфигурирајте ги афинитетите на TE врските во 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 (на прample, 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 описи и поддржани команди за конфигурација (на пр.ampле, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Следниве прample покажува конфигурација на афинитет SR-TE (мапа на афинитет) на уред:

• Чекор 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.
• Чекор 2: Click + Create to add a new affinity mapping.
• Чекор 3: Enter the name and the bit it will be assigned. For example (користејќи ја горенаведената конфигурација):

• Чекор 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

Забелешка
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.

Размислувања за имплементација на политиката

Пред политиките за обезбедување, разгледајте ги овие опции.

• 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 sampле конфигурации.

Креирај експлицитни SR-MPLS политики

• Оваа задача креира SR-MPLS политики користејќи експлицитна (фиксна) патека што се состои од листа на префиксни или соседни сегментни идентификатори (SID листа), при што секој претставува јазол или врска по патеката. Следете ги овие чекори за да креирате експлицитни SR-MPLS политики.

Пред да започнете

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

Чекор 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Чекор 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).

Чекор 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view опис на полето.
Совет
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.

• Чекор 4: Under Policy path, click Explicit path and enter a path name.
• Чекор 5: Add segments that will be part of the SR-MPLS policy path.
• Чекор 6: Кликнете Preview and confirm that the policy you created matches your intent.
• Чекор 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.
• Чекор 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.

Забелешка
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 и потврдете ги деталите за новата политика SR-MPLS. Од табелата Сообраќајно инженерство, кликнете на и изберете View детали.

Забелешка

• На поставување со висок број на јазли, политики или интерфејси, може да се појави истекување на времето за време на распоредувањето на политиката. За да ги конфигурирате опциите за истекување на времето, видете Конфигурирајте ги поставките за истекување на времето на TE.

Креирајте динамички SR-MPLS политики врз основа на намерата за оптимизација
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.

• Чекор 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Чекор 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).
• Чекор 3: Под Детали за политиката, внесете или изберете ги потребните вредности на политиката SR-MPLS. Поместете го покажувачот на глувчето над view опис на секое поле.

Совет

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

Размислувања за афинитет

• 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.
• Чекор 7: Under Segments, select whether or not protected segments should be used when available.
• Чекор 8: Enter any applicable SID constraint. Crosswork Network Controller will try to find a path with this SID. If a path with the SID constraint cannot be found, the provisioned policy will remain operationally down until the conditions are met.

Информации за SID

• 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.
• Чекор 9: Кликнете Preview. The path is highlighted on the map.
• Чекор 10: To commit the policy path, click Provision.
• Чекор 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.

Забелешка

• 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 и потврдете ги деталите за новата политика SR-MPLS. Од табелата Сообраќајно инженерство, кликнете и изберете View детали.

Креирај SR-TE политики (иницирано од PCC)

• Оваа задача креира експлицитни или динамички SR-MPLS или SRv6 политики користејќи го Cisco Network Services Orchestrator (NSO) преку Crosswork UI.

Пред да започнете
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.

Чекор 1: Од главното мени, изберете Услуги и сообраќајно инженерство > Обезбедување (NSO).
Чекор 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Забелешка

• You may also click за увоз на постоечка SR-TE политика.
• Чекор 3: Enter the policy constraints and required values.
• You must populate the following options:

Табела 1: Конфигурација на политиката SR-TE

Прошири ова:	To specify this:
име	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.
боја	Enter a color. For exampле: 200.
патека	a.      Кликнете and enter a preference value. For exampЛе: 123 b.     Select one of the following and toggle the switch to enable: •  explicit-path—Click to add previously configured SID lists. •  dynamic-path—Select the metric you want to minimize and define any applicable constraints and disjointness.
srv6	If you are creating an SRv6 policy, toggle Enable SRv6.

• Step 4: When you are finished, click Dry Run to validate your changes and save them. Crosswork will display your changes in a pop-up window.
• Ако сакате да конфигурирате услуга што има барања што не се совпаѓаат со оние што ги опишуваме во овој примерampле, контактирајте го Cisco Customer Experience.
• Step 5: When you are ready to activate the policy, click Commit Changes.

Измени ги политиките на SR-MPLS

• Можете да менувате или бришете само SR-MPLS политики што се креирани со користење на API или кориснички интерфејс на Crosswork Network Controller. Следете ги овие чекори за да view, измени или избриши политика на SR-MPLS.
• Чекор 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Чекор 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Чекор 3: Изберете View детали или Уреди/Избриши. По ажурирањето на деталите за политиката SR-MPLS, можете да ги пре-view промените на мапата пред да ја зачувате.

Најчесто поставувани прашања

П: Колку политики можат да бидат прикажани на тополошката мапа?

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

П: Може ли да ги извезам избраните податоци од деталите за полисата? view?

A: Не, можете да ги извезете сите податоци само во CSV-датотека file from the policy details view.

Документи / ресурси

CISCO SR-MPLS, SRv6 Crosswork мрежен контролер [pdf] Упатство за корисникот SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork мрежен контролер, SR-MPLS SRv6, Crosswork мрежен контролер, мрежен контролер, контролер

Референци

• Упатство за употреба