CISCO SR-MPLS、SRv6 Crosswork 網路控制器使用者指南

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 UI 中的活動明確路徑，但不是非活動的候選顯式路徑。

開始之前
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。

步驟一： 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.
在這個前ample，您會看到替代路徑直接從 cw-xrv53 > cw-xrv60。

視覺化與定義的綁定段 ID (B-SID) 標籤關聯的底層路徑

Crosswork 網路控制器可讓您視覺化在裝置上手動配置或使用 Crosswork 網路控制器配置的 B-SID 躍點的底層路徑。在本例中ample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
到 view SR-MPLS 或 SRv6 策略的 B-SID 底層路徑，請執行下列操作：

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.

在這個前ample，底層路徑其實是從 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.

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:
  筆記
  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.
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 examp樂：

可視化原生路徑

請依照以下步驟建立路徑查詢。

步驟1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
步驟2: Click New query.
步驟一： 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 新查詢將繼續在背景運行，其詳細資訊將保留在現有查詢中，這由「查詢狀態」列中的藍色「正在運行」圖示指示。當新查詢狀態變為綠色且已完成時，可以 view編輯。

步驟一： 點選 View 當結果在「執行查詢 ID」彈出視窗中可用時，將顯示「路徑詳細資訊」窗口，其中包含相應的可用路徑詳細信息，而拓撲圖左側將顯示可用的原生 SR IGP 路徑。

在 Crosswork 網路控制器中設定 TE 鏈路親和性

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 親和性配置（親和性圖）：

步驟一： 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 策略，該路徑由前綴或鄰接 Segment ID（SID 清單）清單組成，每個 ID 代表路徑上的節點或連結。請依照以下步驟建立明確 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.

步驟一： Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
步驟一： 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.
步驟一： Add segments that will be part of the SR-MPLS policy path.
步驟一： 點擊前view and confirm that the policy you created matches your intent.

步驟一： 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.

步驟一： Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
步驟一： 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).
步驟一： 在「策略詳情」下，輸入或選擇所需的 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.
步驟一： Under Policy path, click Dynamic path and enter a path name.
步驟一： Under Optimization objective, select the metric you want to minimize.

步驟一： 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.
步驟一： Under Segments, select whether or not protected segments should be used when available.

步驟一： 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.
步驟一： 點擊前view. The path is highlighted on the map.
步驟一： To commit the policy path, click Provision.
步驟一： 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 發起）

此任務透過 Crosswork UI 使用 Cisco 網路服務協調器 (NSO) 建立明確或動態 SR-MPLS 或 SRv6 策略。

開始之前
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.

步驟一： 從主選單中，選擇服務和流量工程 > 配置（NSO）。
步驟一： From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

筆記

You may also click 導入現有的 SR-TE 策略。

步驟一： 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例如，聯絡思科客戶體驗。
Step 5: When you are ready to activate the policy, click Commit Changes.

修改SR-MPLS策略

您只能修改或刪除使用 Crosswork Network Controller API 或 UI 建立的 SR-MPLS 策略。請依照以下步驟操作 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 儲存地圖之前請檢查地圖上的變更。

常問問題

Q：拓樸圖上可以顯示多少條策略？

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

Q：我可以從保單詳情中匯出選定的資料嗎？ view?

答：不可以，您只能將所有資料匯出為 CSV 文件 file from the policy details view.

文件/資源

CISCO SR-MPLS、SRv6 交叉工作網路控制器 [pdf] 使用者指南
SR-MPLS、SRv6、SR-MPLS SRv6 Crosswork 網路控制器、SR-MPLS SRv6、Crosswork 網路控制器、網路控制器、控制器

參考

使用者手冊

CISCO SR-MPLS、SRv6 交叉工作網路控制器

產品資訊

產品使用說明