CISCO SR-MPLS, SRv6 Çapraz Ağ Denetleyicisi

Ürün Bilgileri

Özellikler

• Ürün Adı: Cisco Crosswork Ağ Denetleyicisi
• Desteklenen Özellikler: SR-MPLS ve SRv6 politika yönetimi
• Maximum Policies Displayed: Up to 10 policies with separate colored links

Ürün Kullanım Talimatları

• Navigate to Services & Traffic Engineering > Traffic Engineering.
• In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view Haritada.
• You can select up to 10 policies that will appear as separate colored links on the map.
• Eylemler sütunundan > öğesini seçin View SR-MPLS veya SRv6 politikalarından birine ilişkin ayrıntılar.
• View the policy details, including segment lists and path computation constraints.
• Tüm verileri bir CSV dosyasına aktarabilirsiniz file bundan view.
• Kopyala URL from the browser to share SR-MPLS or SRv6 policy details with others.

SR-MPLS ve 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 Topoloji haritasında SR-MPLS ve SRv6 politikaları

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

Beyanat HAYIR.	Tanım
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: Eğer ikisi de A Ve 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	Bu pencerenin içeriği, neyin seçildiğine veya filtrelendiğine bağlıdır. Bu örnekteample, the SR-MPLS tab is selected, and the SR Policy table is displayed.
6	Click on either the SR-MPLS or SRv6 sekmeler view SR-TE politikalarının ilgili listesi.

Beyanat HAYIR.	Tanım
7	İhracat Tümü data into a CSV fileSeçili veya filtrelenmiş verileri dışa aktaramazsınız.
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 şu anda listed in the SR Policy table.
9	Bu seçenek, grup filtresinin (kullanım sırasında) tablo verilerine nasıl uygulanacağını seçmenize olanak tanır. Örneğin:ample, eğer 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 ve SRv6 politika ayrıntıları

• View SR-MPLS veya SRv6 TE politika düzeyi ayrıntıları, segment listeleri ve aday yol bazında yapılandırılmış tüm yol hesaplama kısıtlamaları.

Prosedür

Adım 1

• From the Actions column, choose > View SR-MPLS veya SRv6 politikalarından birine ilişkin ayrıntılar.

Adım 2

• View SR-MPLS veya SRv6 politika ayrıntıları. Tarayıcıdan, URL ve başkalarıyla paylaşın.

Not

• 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 değerin son güncellendiği zaman.

IGP yolunu ve ölçümlerini görselleştirin

• View seçili SR-MPLS politikalarının uç noktaları arasındaki fiziksel yol ve ölçümler.

Prosedür

• 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 katılımcı bağlantılara ilişkin metrikler.
• Adım 3: Tıklayın > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

Not
You must check the Show IGP Path check box to view Metrikler.

Birden Fazla Aday Yol (MCP) Bulun

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

Önemli Notlar

• 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’.
• Yapabilirsiniz view Kullanıcı arayüzünde etkin açık yollar var ancak etkin olmayan aday açık yollar yok.

Başlamadan önce
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 Topoloji haritasında vurgulanan SR-TE politikası.
• Bu eskiample, etkin yolun cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60 şeklinde gittiğini görüyorsunuz.

Adım 3: View Aday yolların listesi.

• From the SR-MPLS or SRv6 Policy table Actions column, click > View Ayrıntılar. SR politika ayrıntıları penceresinde, politika ayrıntılarıyla birlikte aday yolların bir listesi görünür. Durum sütununun altındaki yeşil A, etkin yolu gösterir.

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

Not
You will not be able to select or view Açık aday yollar.

• From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
• Bu eskiample, alternatif yolun doğrudan cw-xrv53 > cw-xrv60'a gittiğini görüyorsunuz.

Tanımlı bir Bağlayıcı Segment Kimliği (B-SID) etiketiyle ilişkili temel yolları görselleştirin

• Crosswork Network Controller, bir cihazda manuel olarak yapılandırdığınız veya Crosswork Network Controller kullanılarak yapılandırdığınız bir B-SID atlayışının temel yolunu görselleştirmenize olanak tanır. Bu örnekteample, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
• İle view SR-MPLS veya SRv6 politikası için B-SID temel yolunu oluşturmak için aşağıdakileri yapın:

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.
Bu eskiample, B-SID yolunun cw-xrv51'den cw-xrv52'ye gittiğini görüyorsunuz.

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

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

• Bu eskiampYani, altta yatan yol aslında cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52 şeklindedir.

Yerel SR yollarını görselleştirin

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

Cihaz ön koşulları

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:
     Not
     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 examptarih:

Yerel yolları görselleştirin

• Bir yol sorgusu oluşturmak için şu adımları izleyin.

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

Not
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View Geçmiş sorguları kullanarak Yol Sorgusu Panosuna geri dönebilirsiniz. Listede zaten yol sorgularınız varsa, view Yeni sorgu arka planda çalışmaya devam ederken, mevcut ayrıntılar görüntülenir; bu durum Sorgu Durumu sütunundaki mavi Çalışan simgesiyle gösterilir. Yeni sorgu durumu yeşile döndüğünde ve tamamlandığında, viewed.

Adım 4: Tıklamak View Çalışan Sorgu Kimliği açılır penceresinde kullanılabilir olduğunda sonuçlar görüntülenir. Yol Ayrıntıları penceresi, ilgili kullanılabilir yol ayrıntılarıyla birlikte görüntülenirken, topoloji haritası sol tarafta kullanılabilir Yerel SR IGP yollarını görüntüler.

Crosswork Network Controller'da TE bağlantı yakınlıklarını yapılandırın

• 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 (örneğinample, 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 açıklamalar ve desteklenen yapılandırma komutları (örneğinampley, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• Aşağıdaki örnekample, bir cihazda SR-TE yakınlık yapılandırmasını (yakınlık haritası) gösterir:

• Adım 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.
• Adım 2: Click + Create to add a new affinity mapping.
• Adım 3: Enter the name and the bit it will be assigned. For example (yukarıdaki yapılandırmayı kullanarak):

• Adım 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

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

Politika dağıtım hususları

Politikaları sağlamadan önce bu seçenekleri göz önünde bulundurun.

• 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 yapılandırmaları.

Açık SR-MPLS politikaları oluşturun

• Bu görev, her biri yol üzerindeki bir düğümü veya bağlantıyı temsil eden bir önek veya bitişiklik Segment Kimlikleri (SID listesi) listesinden oluşan açık (sabit) bir yol kullanarak SR-MPLS politikaları oluşturur. Açık SR-MPLS politikaları oluşturmak için aşağıdaki adımları izleyin.

Başlamadan önce

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

Adım 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Adım 2: Click Create > PCE Init.

Not
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).

Adım 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view alanın tanımı.
Uç
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.

• Adım 4: Under Policy path, click Explicit path and enter a path name.
• Adım 5: Add segments that will be part of the SR-MPLS policy path.
• Adım 6: Ön'e tıklayınview and confirm that the policy you created matches your intent.
• Adım 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.
• Adım 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.

Not
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 ve yeni SR-MPLS politika ayrıntılarını onaylayın. Trafik mühendisliği tablosundan, öğesine tıklayın ve seçin. View detaylar.

Not

• Yüksek düğüm, politika veya arayüz sayısına sahip bir kurulumda, politika dağıtımı sırasında zaman aşımı meydana gelebilir. Zaman aşımı seçeneklerini yapılandırmak için TE zaman aşımı ayarlarını yapılandırma bölümüne bakın.

Optimizasyon amacına dayalı dinamik SR-MPLS politikaları oluşturun
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.

• Adım 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
• Adım 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).
• Adım 3: Politika ayrıntıları altında, gerekli SR-MPLS politika değerlerini girin veya seçin. Fare işaretçisini şuraya getirin: view her alanın açıklaması.

Uç

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

Yakınlık hususları

• 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.
• Adım 7: Under Segments, select whether or not protected segments should be used when available.
• Adım 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 bilgisi

• 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.
• Adım 9: Ön'e tıklayınview. The path is highlighted on the map.
• Adım 10: To commit the policy path, click Provision.
• Adım 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.

Not

• 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 ve yeni SR-MPLS politika ayrıntılarını onaylayın. Trafik mühendisliği tablosundan tıklayın ve seçin. View detaylar.

SR-TE politikaları oluşturun (PCC tarafından başlatılan)

• Bu görev, Cisco Network Services Orchestrator'ı (NSO) kullanarak Crosswork UI üzerinden açık veya dinamik SR-MPLS veya SRv6 politikaları oluşturur.

Başlamadan önce
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.

Adım 1: Ana menüden Hizmetler ve Trafik Mühendisliği > Sağlama (NSO) seçeneğini belirleyin.
Adım 2: From SR-TE > Policy, click. Crosswork displays the Create SR-TE > Policy window.

Not

• You may also click Mevcut bir SR-TE politikasını içe aktarmak için.
• Adım 3: Enter the policy constraints and required values.
• You must populate the following options:

Tablo 1: SR-TE Politika Yapılandırması

Genişletmek Bu:	To specify this:
isim	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.
renk	Enter a color. For exampdosya: 200.
yol	a.      Tıklamak and enter a preference value. For exampben: 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.
• Bu örnekte açıkladığımız gereksinimlerle eşleşmeyen gereksinimlere sahip bir hizmeti yapılandırmak istiyorsanızampCisco Müşteri Deneyimi ile iletişime geçin.
• Step 5: When you are ready to activate the policy, click Commit Changes.

SR-MPLS politikalarını değiştirin

• Yalnızca Crosswork Network Controller API veya kullanıcı arayüzü kullanılarak oluşturulan SR-MPLS politikalarını değiştirebilir veya silebilirsiniz. Aşağıdaki adımları izleyin: viewSR-MPLS politikasını değiştirin veya silin.
• Adım 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
• Adım 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
• Adım 3: Seçmek View Ayrıntıları veya Düzenle/Sil'i seçin. SR-MPLS politika ayrıntılarını güncelledikten sonra,view Haritayı kaydetmeden önce değişiklikleri yapın.

SSS

S: Topoloji haritasında kaç tane politika görüntülenebilir?

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

S: Poliçe ayrıntılarından seçili verileri dışa aktarabilir miyim? view?

A: Hayır, tüm verileri yalnızca CSV'ye aktarabilirsiniz file from the policy details view.

Belgeler / Kaynaklar

CISCO SR-MPLS, SRv6 Çapraz Ağ Denetleyicisi [pdf] Kullanıcı Kılavuzu SR-MPLS, SRv6, SR-MPLS SRv6 Çapraz Ağ Denetleyicisi, SR-MPLS SRv6, Çapraz Ağ Denetleyicisi, Ağ Denetleyicisi, Denetleyici

Referanslar

• Kullanıcı Kılavuzu