CISCO SR-MPLS,SRv6 Crosswork Network Controller

ຂໍ້ມູນຜະລິດຕະພັນ

ຂໍ້ມູນຈໍາເພາະ

• ຊື່ຜະລິດຕະພັນ: Cisco Crosswork Network Controller
• ຄຸນສົມບັດທີ່ຮອງຮັບ: ການຄຸ້ມຄອງນະໂຍບາຍ 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 ໃນແຜນທີ່ topology

• 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	ເນື້ອໃນຂອງປ່ອງຢ້ຽມນີ້ແມ່ນຂຶ້ນກັບສິ່ງທີ່ໄດ້ຖືກເລືອກຫຼືການກັ່ນຕອງ. ໃນນີ້ example, 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	ຕົວເລືອກນີ້ອະນຸຍາດໃຫ້ທ່ານເລືອກວິທີການກັ່ນຕອງກຸ່ມ (ໃນເວລາທີ່ໃຊ້) ຄວນຖືກນໍາໃຊ້ໃນຂໍ້ມູນຕາຕະລາງ. ຕົວຢ່າງample, ຖ້າ 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 metrics ກ່ຽວກັບການເຊື່ອມຕໍ່ທີ່ເຂົ້າຮ່ວມ.
• ຂັ້ນຕອນທີ 3: ກົດ > Metrics tab.
• Step 4: Toggle applicable metrics to ON.

ໝາຍເຫດ
You must check the Show IGP Path check box to view metrics.

ຊອກຫາເສັ້ນທາງຜູ້ສະໝັກຫຼາຍອັນ (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.

ຫມາຍເຫດທີ່ສໍາຄັນ

• 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 ທີ່ຖືກເນັ້ນໃສ່ໃນແຜນທີ່ topology.
• ໃນນີ້ example, ເຈົ້າເຫັນວ່າເສັ້ນທາງທີ່ເຄື່ອນໄຫວແມ່ນໄປຈາກ 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.
• ໃນນີ້ example, ເຈົ້າເຫັນວ່າເສັ້ນທາງສະຫຼັບໄປໂດຍກົງຈາກ cw-xrv53 > cw-xrv60.

ເບິ່ງເຫັນເສັ້ນທາງທີ່ຕິດພັນກັບປ້າຍກຳກັບ Binding-Segment ID (B-SID)

• Crosswork Network Controller ຊ່ວຍໃຫ້ທ່ານສາມາດເບິ່ງເຫັນເສັ້ນທາງພື້ນຖານຂອງ B-SID hop ທີ່ທ່ານໄດ້ຕັ້ງຄ່າດ້ວຍຕົນເອງໃນອຸປະກອນຫຼື configured ໂດຍໃຊ້ Crosswork Network Controller. ໃນນີ້ example, 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.
ໃນນີ້ example, ທ່ານເຫັນວ່າເສັ້ນທາງ 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.

• ໃນນີ້ exampແທ້ຈິງແລ້ວ, ເສັ້ນທາງພື້ນຖານແມ່ນມາຈາກ 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 example:

ເບິ່ງເຫັນເສັ້ນທາງພື້ນເມືອງ

• ປະຕິບັດຕາມຂັ້ນຕອນເຫຼົ່ານີ້ເພື່ອສ້າງການສອບຖາມເສັ້ນທາງ.

ຂັ້ນຕອນທີ 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 ຄໍາຖາມທີ່ຜ່ານມາເພື່ອກັບຄືນໄປຫາ Path Query Dashboard. ຖ້າທ່ານມີຄໍາຖາມເສັ້ນທາງຢູ່ໃນບັນຊີລາຍຊື່ແລ້ວ, ທ່ານສາມາດເຮັດໄດ້ view ລາຍ​ລະ​ອຽດ​ທີ່​ມີ​ຢູ່​ໃນ​ຂະ​ນະ​ທີ່​ການ​ສອບ​ຖາມ​ໃຫມ່​ສືບ​ຕໍ່​ດໍາ​ເນີນ​ການ​ຢູ່​ໃນ​ພື້ນ​ຖານ​, ເຊິ່ງ​ຊີ້​ໃຫ້​ເຫັນ​ໂດຍ icon ການ​ແລ່ນ​ສີ​ຟ້າ​ໃນ​ຖັນ Query State​. ເມື່ອສະຖານະການສອບຖາມໃຫມ່ປ່ຽນເປັນສີຂຽວ, ແລະສໍາເລັດ, ມັນສາມາດເປັນ viewed.

ຂັ້ນຕອນທີ 4: ກົດ View ຜົນໄດ້ຮັບເມື່ອມັນມີໃຫ້ຢູ່ໃນປັອບອັບຂອງ Running Query ID. ປ່ອງຢ້ຽມລາຍລະອຽດເສັ້ນທາງຈະປາກົດພ້ອມກັບລາຍລະອຽດເສັ້ນທາງທີ່ມີຢູ່ທີ່ສອດຄ້ອງກັນໃນຂະນະທີ່ແຜນທີ່ topology ສະແດງເສັ້ນທາງ 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 (ສໍາ​ລັບ​ການ 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 ຄໍາ​ອະ​ທິ​ບາຍ​ແລະ​ຄໍາ​ສັ່ງ​ການ​ຕັ້ງ​ຄ່າ​ສະ​ຫນັບ​ສະ​ຫນູນ (ສໍາ​ລັບ​ການ exampເລ, Segment Routing Configuration Guide for Cisco ASR 9000 Series Router)
• ຕໍ່ໄປນີ້ example ສະ​ແດງ​ການ​ຕັ້ງ​ຄ່າ SR-TE affinity (affinity-map) ໃນ​ອຸ​ປະ​ກອນ​:

• ຂັ້ນຕອນທີ 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 ໂດຍໃຊ້ເສັ້ນທາງທີ່ຊັດເຈນ (ຄົງທີ່) ປະກອບດ້ວຍບັນຊີລາຍຊື່ຂອງຄໍານໍາຫນ້າຫຼື adjacency Segment IDs (SID list), ແຕ່ລະຄົນເປັນຕົວແທນຂອງ node ຫຼືການເຊື່ອມຕໍ່ຕາມເສັ້ນທາງ. ປະຕິບັດຕາມຂັ້ນຕອນເຫຼົ່ານີ້ເພື່ອສ້າງຕໍາຫຼວດ 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: ກົດກ່ອນview 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 ລາຍລະອຽດ.

ໝາຍເຫດ

• ໃນ​ການ​ຕັ້ງ​ຄ່າ​ທີ່​ມີ node ສູງ​, ນະ​ໂຍ​ບາຍ​, ຫຼື​ການ​ໂຕ້​ຕອບ​ນັບ​, ການ​ຫມົດ​ເວ​ລາ​ອາດ​ຈະ​ເກີດ​ຂຶ້ນ​ໃນ​ລະ​ຫວ່າງ​ການ​ນໍາ​ໃຊ້​ນະ​ໂຍ​ບາຍ​. ເພື່ອກຳນົດຄ່າຕົວເລືອກການໝົດເວລາ, ເບິ່ງການຕັ້ງຄ່າການໝົດເວລາຂອງ 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: ກົດກ່ອນview. 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 example: 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.
• ຖ້າທ່ານຕ້ອງການປັບຄ່າບໍລິການທີ່ມີຄວາມຕ້ອງການທີ່ບໍ່ກົງກັບສິ່ງທີ່ພວກເຮົາອະທິບາຍໃນຕົວຢ່າງນີ້ample, ຕິດຕໍ່ປະສົບການລູກຄ້າ Cisco.
• Step 5: When you are ready to activate the policy, click Commit Changes.

ແກ້ໄຂນະໂຍບາຍ SR-MPLS

• ທ່ານສາມາດແກ້ໄຂ ຫຼືລຶບນະໂຍບາຍ SR-MPLS ທີ່ໄດ້ສ້າງຂຶ້ນໂດຍໃຊ້ Crosswork Network Controller API ຫຼື UI ເທົ່ານັ້ນ . ປະຕິບັດຕາມຂັ້ນຕອນເຫຼົ່ານີ້ເພື່ອ 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, ທ່ານສາມາດ preview ການປ່ຽນແປງໃນແຜນທີ່ກ່ອນທີ່ຈະບັນທຶກມັນ.

FAQ

ຖາມ: ມີນະໂຍບາຍຫຼາຍປານໃດທີ່ສາມາດສະແດງຢູ່ໃນແຜນທີ່ topology?

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 Network Controller [pdf] ຄູ່ມືຜູ້ໃຊ້ SR-MPLS, SRv6, SR-MPLS SRv6 Crosswork Network Controller, SR-MPLS SRv6, Crosswork Network Controller, Network Controller, Controller

ເອກະສານອ້າງອີງ

• ຄູ່ມືຜູ້ໃຊ້