CISCO SR-MPLS, SRv6 Crosswork Network Controller
Product Information
fepetra arahana
- Anaran'ny vokatra: Cisco Crosswork Network Controller
- Endri-javatra tohana: SR-MPLS sy SRv6 fitantanana politika
- Maximum Policies Displayed: Up to 10 policies with separate colored links
Torolàlana momba ny fampiasana vokatra
- Navigate to Services & Traffic Engineering > Traffic Engineering.
- In the Traffic Engineering table, select the checkbox of each SR-MPLS or SRv6 policy to view eo amin'ny sarintany.
- You can select up to 10 policies that will appear as separate colored links on the map.
- Avy amin'ny tsanganana Actions, fidio > View antsipiriany momba ny iray amin'ireo politika SR-MPLS na SRv6.
- View the policy details, including segment lists and path computation constraints.
- Azonao atao ny manondrana ny angona rehetra ao anaty CSV file avy amin'ity view.
- Kopia ny URL from the browser to share SR-MPLS or SRv6 policy details with others.
SR-MPLS sy 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 Politika SR-MPLS sy SRv6 amin'ny sarintany topolojia
- 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 eo amin'ny sarintany.
- You can select up to 10 policies that will appear as separate colored links.
| Miantso mafy Tsia. | Description |
| 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: Raha samy A SY 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 | Ny votoatin'ity varavarankely ity dia miankina amin'izay nofantenana na voasivana. Amin'ity example, the SR-MPLS tab is selected, and the SR Policy table is displayed. |
| 6 | Click on either the SR-MPLS or SRv6 tabs ho view Ny lisitry ny politika SR-TE tsirairay avy. |
).| Miantso mafy Tsia. | Description |
| 7 | fanondranana rEHETRA data into a CSV file. Tsy afaka manondrana angona voafantina na voasivana ianao. |
| 8 | ny 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 amin'izao fotoana izao listed in the SR Policy table. |
| 9 | Ity safidy ity dia ahafahanao misafidy ny fomba hampiharana ny sivana vondrona (rehefa ampiasaina) amin'ny angona latabatra. Ho an'ny example, raha 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 Ny antsipirian'ny politika SR-MPLS sy SRv6
- View SR-MPLS na SRv6 TE antsipirihan'ny haavon'ny politika ary koa ny lisitry ny fizarana sy ny teritery momba ny kajy ny lalana izay namboarina amin'ny alàlan'ny lalana isaky ny kandidà.
fitsarana
Dingana 1
- From the Actions column, choose
> View antsipiriany momba ny iray amin'ireo politika SR-MPLS na SRv6.
Dingana 2
- View Ny antsipirian'ny politika SR-MPLS na SRv6. Avy amin'ny navigateur, azonao atao ny mandika ny URL ary zarao amin'ny hafa.
Fanamarihana
- 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 ny fotoana farany nanavaozana ny sandany.
Alaivo sary an-tsaina ny lalana sy metrika IGP
- View ny lalana ara-batana sy ny metrika eo anelanelan'ny teboka faran'ny politika SR-MPLS voafantina.
fitsarana
- 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 metrika amin'ny rohy mandray anjara.
- Dingana 3: Tsindrio
> Metrics tab. - Step 4: Toggle applicable metrics to ON.
Fanamarihana
You must check the Show IGP Path check box to view metrika.
Mitadiava lalana kandida maro (MCPs)
- 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.
Fanamarihana manan-danja
- 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’.
- Ianao dia afaka view lalana mivaingana mavitrika fa tsy lalana mibaribary kandida tsy mavitrika ao amin'ny UI.
Alohan'ny hanombohanao
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 ny politikan'ny SR-TE izay asongadina amin'ny sarintany topologie.
- Amin'ity example, hitanao fa ny lalana mavitrika dia avy amin'ny cw-xrv53 > cw-xrv57 > cw-xrv58 > cw-xrv59 > cw-xrv60.
Dingana 3: View ny lisitry ny lalana kandida.
- From the SR-MPLS or SRv6 Policy table Actions column, click
> View antsipiriany. Misy lisitry ny lalan'ny kandidà miseho miaraka amin'ny antsipirian'ny politika ao amin'ny varavarankelin'ny antsipirian'ny politika SR. Ny maitso A eo ambanin'ny tsanganana Fanjakana dia manondro ny lalana mavitrika.
- 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.
Fanamarihana
You will not be able to select or view lalana kandida mazava.
- From the Candidate path area, hover your mouse over the candidate path name. The candidate path is highlighted on the topology map.
- Amin'ity example, hitanao fa mandeha mivantana avy amin'ny cw-xrv53 > cw-xrv60 ny lalana mifandimby.
Alaivo sary an-tsaina ny lalana fototra mifandray amin'ny marika ID (B-SID) voafaritra voafaritra
- Ny Crosswork Network Controller dia ahafahanao maka sary an-tsaina ny lalana fototra amin'ny hop B-SID izay namboarinao tamin'ny fitaovana iray na namboarinao tamin'ny alàlan'ny Crosswork Network Controller. Amin'ity example, we have assigned 15700 as a B-SID label on an SR-MPLS policy hop.
- ny view ny lalana fototra B-SID ho an'ny politika SR-MPLS na SRv6, ataovy izao manaraka izao:
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.
Amin'ity example, hitanao fa ny lalana B-SID dia avy amin'ny cw-xrv51 mankany cw-xrv52.
Step 3: From the SR policy details page, click > View antsipiriany.
Step 4: Expand the active path and click the B-Sid Label ID to see the underlying path.
- Amin'ity exampNy lalana fototra dia avy amin'ny cw-xrv51 > cw-xrv54 > cw-xrv53 > cw-xrv52.
Alaivo sary an-tsaina ny lalana SR teratany
- 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.
Fepetra takiana amin'ny fitaovana
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:
Fanamarihana
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:
Alaivo sary an-tsaina ny lalan-tany
- Araho ireto dingana ireto mba hamoronana fanontaniana momba ny lalana.
Dingana 1: From the main menu, choose Services & Traffic Engineering > Path Query.The Path Query dashboard appears.
Dingana 2: Click New query.
Dingana 3: Enter the device information in the required fields to find available Native SR IGP Paths and click Get paths.
Fanamarihana
Path queries may take a moment to complete. When the Running Query ID pop-up appears, you can also select View fanontaniana taloha mba hiverina any amin'ny Dashboard Query lalana. Raha efa manana fanontaniana momba ny lalana ao amin'ny lisitra ianao dia azonao atao view antsipirian-javatra efa misy satria mitohy mandeha any ambadika ilay fanontaniana vaovao, izay asehon'ny kisary manga Running ao amin'ny tsanganana Query State. Rehefa lasa maitso ny toetry ny fangatahana vaovao, ary vita dia mety ho izany viewed.
Dingana 4: tsindrio View vokatra rehefa hita eo amin'ny pop-up Running Query ID. Ny varavarankelin'ny Path Details dia miseho miaraka amin'ny antsipirian'ny lalana mifanandrify amin'izany raha ny sarintany topologie kosa dia mampiseho ny lalana Native SR IGP misy eo ankavia.
Ampifanaraho ny fifandraisan'ny rohy TE ao amin'ny 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 (ho an'ny 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 famaritana sy baiko fanamafisana tohanana (ohatraample, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
- Ny manaraka example dia mampiseho SR-TE affinity configuration (affinity-map) amin'ny fitaovana iray:
- Dingana 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.
- Dingana 2: Click + Create to add a new affinity mapping.
- Dingana 3: Enter the name and the bit it will be assigned. For example (mampiasa ny fanamafisana etsy ambony):
- Dingana 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
Fanamarihana
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.
Fandinihana ny fametrahana politika
Alohan'ny hanaovana politika, diniho ireto safidy ireto.
- 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 configurations.
Mamorona politika SR-MPLS mazava
- Ity asa ity dia mamorona politikan'ny SR-MPLS amin'ny alàlan'ny lalana mibaribary (fixed) misy lisitr'ireo kaomandin'ny fizarana mialoha na mifanakaiky (lisitra SID), izay samy maneho node na rohy eo amin'ny lalana. Araho ireto dingana ireto mba hamoronana polisy SR-MPLS mazava.
Alohan'ny hanombohanao
- 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.
Dingana 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
Dingana 2: Click Create > PCE Init.
Fanamarihana
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).
Dingana 3: Under Policy details, enter or select the required SR-MPLS policy values. Hover the mouse pointer over the to view famaritana ny saha.
Soso-kevitra
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.
- Dingana 4: Under Policy path, click Explicit path and enter a path name.
- Dingana 5: Add segments that will be part of the SR-MPLS policy path.
- Dingana 6: Tsindrio ny Preview and confirm that the policy you created matches your intent.
- Dingana 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.
- Dingana 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.
Fanamarihana
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 ary hamafiso ny antsipirian'ny politika SR-MPLS vaovao. Avy amin'ny tabilao Traffic engineering, tsindrio ny ary safidio View antsipiriany.
Fanamarihana
- Amin'ny setup miaraka amin'ny fanisana node, politika, na interface tsara, dia mety hitranga ny fe-potoana mandritra ny fametrahana politika. Raha te handrindra ny safidin'ny fotoana lany dia jereo ny tenifototra TE fe-potoana.
Mamorona politika SR-MPLS mavitrika mifototra amin'ny fikasana fanatsarana
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.
- Dingana 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS.
- Dingana 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).
- Dingana 3: Ao amin'ny antsipirian'ny politika, ampidiro na safidio ny soatoavina politika SR-MPLS ilaina. Atsipazo ny fanondroan'ny totozy mankany view famaritana ny saha tsirairay.
Soso-kevitra
- 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.
- Dingana 4: Under Policy path, click Dynamic path and enter a path name.
- Dingana 5: Under Optimization objective, select the metric you want to minimize.
- Dingana 6: Define any applicable constraints and disjointness.
Fandinihana ny fifandraisana
- 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.
- Dingana 7: Under Segments, select whether or not protected segments should be used when available.
- Dingana 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.
Fampahalalana momba ny orinasa 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.
- Dingana 9: Tsindrio ny Preview. The path is highlighted on the map.
- Dingana 10: To commit the policy path, click Provision.
- Dingana 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.
Fanamarihana
- 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 ary hamafiso ny antsipirian'ny politika SR-MPLS vaovao. Avy amin'ny tabilao Traffic engineering, tsindrio ary mifidiana View antsipiriany.
Mamorona politika SR-TE (natomboky ny PCC)
- Ity asa ity dia mamorona politika SR-MPLS na SRv6 mazava na mavitrika amin'ny alàlan'ny Cisco Network Services Orchestrator (NSO) amin'ny alàlan'ny Crosswork UI.
Alohan'ny hanombohanao
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.
Dingana 1: Avy amin'ny menio lehibe, safidio ny Services & Traffic Engineering > Provisioning (NSO).
Dingana 2: From SR-TE > Policy, click
. Crosswork displays the Create SR-TE > Policy window.
Fanamarihana
- You may also click
hanafatra politika SR-TE efa misy. - Dingana 3: Enter the policy constraints and required values.
- You must populate the following options:
Tabilao 1: Fanamboarana Politika SR-TE
| hanitatra ity: | To specify this: |
| anarana | 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. |
| loko | Enter a color. For exampny: 200. |
| LALANA | a. tsindrio and enter a preference value. For exampny: 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.
- Raha te-hanamboatra serivisy manana fepetra tsy mifanaraka amin'ireo voalazanay amin'ity ex ity ianaoample, mifandraisa amin'ny Cisco Customer Experience.
- Step 5: When you are ready to activate the policy, click Commit Changes.
Manova ny politikan'ny SR-MPLS
- Azonao atao ny manova na mamafa ny politika SR-MPLS izay noforonina amin'ny alàlan'ny Crosswork Network Controller API na UI. Araho ireto dingana ireto mba view, manova, na mamafa politika SR-MPLS.
- Dingana 1: Choose Services & Traffic Engineering > Traffic Engineering > SR-MPLS tab.
- Dingana 2: From the Traffic engineering table, locate the SR-MPLS policy you are interested in and click.
- Dingana 3: Fidio View pitsopitsony na Ahitsio/Fafao. Aorian'ny fanavaozana ny antsipirian'ny politikan'ny SR-MPLS dia azonao atao mialohaview ny fanovana eo amin'ny sari-tany alohan'ny hitehirizana azy.
FAQ
F: Firy ny politika azo aseho amin'ny sarintany topologie?
A: Up to 10 policies can be selected and displayed as separate colored links on the map.
F: Afaka manondrana angona voafantina avy amin'ny antsipirian'ny politika ve aho view?
A: Tsia, azonao atao ny manondrana ny angona rehetra ao anaty CSV ihany file from the policy details view.
Documents / Loharano
 |
CISCO SR-MPLS, SRv6 Crosswork Network Controller [pdf] Torolàlana ho an'ny mpampiasa SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork Network Controller, SR-MPLS SRv6, Crosswork Network Controller, Network Controller, Controller |