Pengawal Rangkaian Silang Kerja CISCO SR-MPLS,SRv6
Maklumat Produk
Spesifikasi
- Nama Produk: Pengawal Rangkaian Cisco Crosswork
- Ciri yang Disokong: Pengurusan dasar SR-MPLS dan SRv6
- Maximum Policies Displayed: Up to 10 policies with separate colored links
Arahan Penggunaan Produk
- Navigate to Services & Traffic Engineering > Traffic Engineering.
- In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view pada peta.
- You can select up to 10 policies that will appear as separate colored links on the map.
- Daripada lajur Tindakan, pilih > View butiran untuk salah satu dasar SR-MPLS atau SRv6.
- View the policy details, including segment lists and path computation constraints.
- Anda boleh mengeksport semua data ke dalam CSV file daripada ini view.
- Salin URL from the browser to share SR-MPLS or SRv6 policy details with others.
SR-MPLS dan 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 Dasar SR-MPLS dan SRv6 pada peta topologi
- 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 pada peta.
- You can select up to 10 policies that will appear as separate colored links.
| petak bual Tidak. | Penerangan |
| 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: Jika kedua-duanya A dan 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 | Kandungan tetingkap ini bergantung pada apa yang telah dipilih atau ditapis. Dalam bekas iniample, the SR-MPLS tab is selected, and the SR Policy table is displayed. |
| 6 | Click on either the SR-MPLS or SRv6 tab ke view senarai dasar SR-TE masing-masing. |
).| petak bual Tidak. | Penerangan |
| 7 | Eksport semua data into a CSV file. Anda tidak boleh mengeksport data yang dipilih atau ditapis. |
| 8 | The 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 pada masa ini listed in the SR Policy table. |
| 9 | Pilihan ini membolehkan anda memilih cara penapis kumpulan (semasa digunakan) harus digunakan pada data jadual. Untuk example, jika 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 Butiran dasar SR-MPLS dan SRv6
- View Butiran tahap dasar SR-MPLS atau SRv6 TE serta senarai segmen dan sebarang kekangan pengiraan laluan yang dikonfigurasikan berdasarkan laluan setiap calon.
Prosedur
Langkah 1
- From the Actions column, choose
> View butiran untuk salah satu dasar SR-MPLS atau SRv6.
Langkah 2
- View Butiran dasar SR-MPLS atau SRv6. Dari penyemak imbas, anda boleh menyalin URL dan berkongsi dengan orang lain.
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 kali terakhir nilai dikemas kini.
Visualisasikan laluan dan metrik IGP
- View laluan fizikal dan metrik antara titik akhir dasar SR-MPLS yang dipilih.
Prosedur
- 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 metrik pada pautan yang mengambil bahagian.
- Langkah 3: Klik
> Metrics tab. - Step 4: Toggle applicable metrics to ON.
Nota
You must check the Show IGP Path check box to view metrik.
Cari Laluan Calon Berbilang (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.
Nota Penting
- 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’.
- awak boleh view laluan eksplisit aktif tetapi bukan laluan eksplisit calon tidak aktif dalam UI.
Sebelum anda bermula
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 dasar SR-TE yang diserlahkan pada peta topologi.
- Dalam bekas iniampOleh itu, anda melihat bahawa laluan aktif pergi dari cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.
Langkah 3: View senarai laluan calon.
- From the SR-MPLS or SRv6 Policy table Actions column, click
> View butiran. Senarai laluan calon muncul bersama dengan butiran dasar dalam tetingkap butiran dasar SR. A hijau di bawah lajur Negeri menunjukkan laluan aktif.
- 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 laluan calon yang jelas.
- From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
- Dalam bekas iniampOleh itu, anda melihat bahawa laluan alternatif pergi terus dari cw-xrv53 > cw-xrv60.
Visualisasikan laluan asas yang dikaitkan dengan label ID Segmen Binding (B-SID) yang ditentukan
- Pengawal Rangkaian Crosswork membolehkan anda menggambarkan laluan asas lompatan B-SID yang telah anda konfigurasikan secara manual pada peranti atau konfigurasikan menggunakan Pengawal Rangkaian Crosswork. Dalam bekas iniample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
- Kepada view laluan asas B-SID untuk dasar SR-MPLS atau SRv6, lakukan perkara berikut:
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.
Dalam bekas iniampOleh itu, anda melihat bahawa laluan B-SID adalah dari cw-xrv51 ke cw-xrv52.
Step 3: From the SR policy details page, click > View butiran.
Step 4: Expand the active path and click the B-Sid Label ID to see the underlying path.
- Dalam bekas iniampJadi, laluan asas sebenarnya pergi daripada cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.
Visualisasikan laluan SR asli
- 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.
Prasyarat peranti
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:
Visualisasikan laluan asli
- Ikuti langkah ini untuk membuat pertanyaan laluan.
Langkah 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Langkah 2: Click New query.
Langkah 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 pertanyaan lalu untuk kembali ke Papan Pemuka Pertanyaan Laluan. Jika anda sudah mempunyai pertanyaan laluan dalam senarai, anda boleh view butiran sedia ada kerana pertanyaan baharu terus berjalan di latar belakang, yang ditunjukkan oleh ikon Berlari biru dalam lajur Keadaan Pertanyaan. Apabila keadaan pertanyaan baharu bertukar hijau dan selesai, ia boleh jadi viewed.
Langkah 4: klik View terhasil apabila ia tersedia pada pop timbul ID Pertanyaan Menjalankan. Tetingkap Butiran Laluan muncul dengan butiran laluan tersedia yang sepadan manakala peta topologi memaparkan laluan IGP SR Asli yang tersedia di sebelah kiri.
Konfigurasikan pertalian pautan TE dalam Pengawal Rangkaian Silang Kerja
- 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 (untuk 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 penerangan dan arahan konfigurasi yang disokong (contohnyaample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
- Ex berikutample menunjukkan konfigurasi perkaitan SR-TE (peta perkaitan) pada peranti:
- Langkah 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.
- Langkah 2: Click + Create to add a new affinity mapping.
- Langkah 3: Enter the name and the bit it will be assigned. For example (menggunakan konfigurasi di atas):
- Langkah 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.
Pertimbangan penggunaan dasar
Sebelum dasar peruntukan, pertimbangkan pilihan ini.
- 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 konfigurasi.
Buat dasar SR-MPLS yang jelas
- Tugas ini mencipta dasar SR-MPLS menggunakan laluan eksplisit (tetap) yang terdiri daripada senarai awalan atau ID Segmen bersebelahan (senarai SID), setiap satu mewakili nod atau pautan di sepanjang laluan. Ikut langkah ini untuk membuat dasar SR-MPLS yang jelas.
Sebelum anda bermula
- 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.
Langkah 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Langkah 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).
Langkah 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view penerangan tentang bidang tersebut.
Petua
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.
- Langkah 4: Under Policy path, click Explicit path and enter a path name.
- Langkah 5: Add segments that will be part of the SR-MPLS policy path.
- Langkah 6: Klik Praview and confirm that the policy you created matches your intent.
- Langkah 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.
- Langkah 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 dan sahkan butiran dasar SR-MPLS baharu. Daripada jadual Kejuruteraan Trafik, klik dan pilih View butiran.
Nota
- Pada persediaan dengan kiraan nod, dasar atau antara muka yang tinggi, tamat masa mungkin berlaku semasa penggunaan dasar. Untuk mengkonfigurasi pilihan tamat masa, lihat Konfigurasi tetapan tamat masa TE.
Buat dasar SR-MPLS dinamik berdasarkan niat pengoptimuman
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.
- Langkah 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
- Langkah 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).
- Langkah 3: Di bawah Butiran dasar, masukkan atau pilih nilai dasar SR-MPLS yang diperlukan. Tuding penunjuk tetikus ke atas view penerangan bagi setiap bidang.
Petua
- 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.
- Langkah 4: Under Policy path, click Dynamic path and enter a path name.
- Langkah 5: Under Optimization objective, select the metric you want to minimize.
- Langkah 6: Define any applicable constraints and disjointness.
Pertimbangan pertalian
- 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.
- Langkah 7: Under Segments, select whether or not protected segments should be used when available.
- Langkah 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.
maklumat 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.
- Langkah 9: Klik Praview. The path is highlighted on the map.
- Langkah 10: To commit the policy path, click Provision.
- Langkah 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 dan sahkan butiran dasar SR-MPLS baharu. Daripada jadual Kejuruteraan Trafik, klik dan pilih View butiran.
Buat dasar SR-TE (dimulakan PCC)
- Tugas ini mencipta dasar SR-MPLS atau SRv6 yang eksplisit atau dinamik menggunakan Cisco Network Services Orchestrator (NSO) melalui UI Crosswork.
Sebelum anda bermula
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.
Langkah 1: Daripada menu utama, pilih Perkhidmatan & Kejuruteraan Trafik > Peruntukan (NSO).
Langkah 2: From SR-TE > Policy, click
. Crosswork displays the Create SR-TE > Policy window.
Nota
- You may also click
untuk mengimport dasar SR-TE sedia ada. - Langkah 3: Enter the policy constraints and required values.
- You must populate the following options:
Jadual 1: Konfigurasi Dasar SR-TE
| Kembangkan ini: | To specify this: |
| nama | 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. |
| warna | Enter a color. For example: 200. |
| laluan | a. klik and enter a preference value. For example: 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.
- Jika anda ingin mengkonfigurasi perkhidmatan yang mempunyai keperluan yang tidak sepadan dengan yang kami terangkan dalam ex iniample, hubungi Pengalaman Pelanggan Cisco.
- Step 5: When you are ready to activate the policy, click Commit Changes.
Ubah suai dasar SR-MPLS
- Anda hanya boleh mengubah suai atau memadam dasar SR-MPLS yang telah dibuat menggunakan API atau UI Pengawal Rangkaian Silang Kerja. Ikuti langkah ini untuk view, ubah suai atau padamkan dasar SR-MPLS.
- Langkah 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
- Langkah 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
- Langkah 3: Pilih View butiran atau Edit/Padam. Selepas mengemas kini butiran dasar SR-MPLS, anda boleh membuat praview perubahan pada peta sebelum menyimpannya.
Soalan Lazim
S: Berapa banyak dasar yang boleh dipaparkan pada peta topologi?
A: Up to 10 policies can be selected and displayed as separate colored links on the map.
S: Bolehkah saya mengeksport data terpilih daripada butiran dasar view?
J: Tidak, anda hanya boleh mengeksport semua data ke dalam CSV file from the policy details view.
Dokumen / Sumber
 |
Pengawal Rangkaian Silang Kerja CISCO SR-MPLS,SRv6 [pdf] Panduan Pengguna SR-MPLS, SRv6, SR-MPLS SRv6 Pengawal Rangkaian Silang, SR-MPLS SRv6, Pengawal Rangkaian Silang, Pengawal Rangkaian, Pengawal |