Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > SR-TE > ODN-Template.

Step 2

Click to create a new template and give it a unique name. In this case, the name is L3VPN_NM-SRTE-ODN_72-a. Click Continue.

You may also browse for an existing template on your system to import the file. The information from the imported file is populated into the form.

Step 3

Choose the head-end device, PE-A, and specify the color 72.

Step 4

Under dynamic, select latency as the metric type. This is the SLA objective on which we are optimizing.

Step 5

Select the pce check box to specify that the path should be computed by the SR-PCE, not by the Path Computation Client (PCC).

Step 6

Define the required constraints. In this case, we want the computed paths to be disjointed because they must not share a link.

Under disjoint-path, choose link as the type, and specify a numeric group ID, in this case, 16, as the group-id.

Note	You may choose the group ID. All paths requested with the same group-id will be disjointed.

Note	Optionally, you may configure Flex-Algo as a constraint.

Step 7

Commit your changes or click Dry run to check what will be configured on the devices before you commit.

Step 8

Check that the new ODN template appears in the table and its provisioning state is Success. Click in the Actions column and choose Config view to see the Yang model-based service intent data that details the ODN template you created.

Step 9

Create the other ODN templates listed above in the same manner.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > Routing Policy Tag.

Step 2

Click to create a new routing policy tag and type the name of the tag set: COLOR_70. Click Continue.

Step 3

Under Tag-value, click + and type the tag-value: 70.

The tag value may be a number between 1 – 4294967295 and should match to a color value.

Step 4

Click Continue. The new routing policy tag name with the new tag value is visible. Click Commit changes.

Step 5

Now, create the routing policy destination prefixes. From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > Routing Policy Destination Prefix.

Step 6

Click to create a new routing policy destination prefix and type the name DEST_PREFIX_SET_70.

Step 7

For Mode, select ipv4.

Step 8

Expand prefixes and click to add the ip-prefix to the prefix-list. Type 70.70.70.0/30 and click Continue.

Step 9

Create the other two routing policy destination prefixes (DEST_PREFIX_SET_71 and DEST_PREFIX_SET_72) by following the same steps.

Step 10

Now, we are ready to create the first route policy - L3VPN_NM-SRTE-RP-PE-A-7. The other route policies can be created using the same procedure. From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3vpn > Routing Policy.

Step 11

Click to create a new route policy and type a unique name for the top-level policy definition: L3VPN_NM-SRTE-RP-PE-A-7. Click Continue. The statements section appears.

Step 12

Expand statements, click to add the name of the policy statement (such as stmt1) and click Continue. The statement{stmt1} panel appears, showing conditions and actions sections.

Step 13

Expand conditions and then expand match-dest-prefix-set. In the prefix-set list, select or type the following: DEST_PREFIX_SET_70. This is what references a defined prefix set.

Step 14

Expand actions and then expand bgp-actions.

Step 15

For bgp-actions, slide the Enable bgp-actions toggle to the on position. Toggling on bgp-actions defines the top-level container for BGP-specific actions.

Step 16

Now expand set-ext-community. Slide the Enable-set-ext-community toggle to the on position. Toggling on set-ext-community sets the extended community attributes.

Step 17

For Method and reference, select the Ext-community-set-ref list and select COLOR_70. The Ext-community-set-ref references a defined extended community set by name.

Step 18

Click X in the top-right corner to close the statement{stmnt1} panel and click Commit changes.

Step 19

Create the other route policies (L3VPN_NM-SRTE-RP-PE-B-7 and L3VPN_NM-SRTE-RP-PE-C-7) in the same manner.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > VPN Profiles.

Step 2

Click to create a VPN profile to be referenced in the VPN service.

Step 3

Select the Id list and select L3VPN_NM-SRTE-RP-PE-A-7.

Step 4

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3vpn > L3vpn-Service.

Step 5

Click to create a new service and type a new vpn-id: L3VPN_NM-SRTE-ODN-70. Click Continue.

Step 6

Create vpn-instance-profile, which is a container that defines the route distinguisher (RD), route targets, and the export/import route policy. We will create vpn-instance-profiles for each endpoint, as follows:

Step 7

Define each VPN endpoint: PE-A, PE-B, and PE-C.

1. Expand vpn-nodes and click to select the relevant device from the list: PE-A. Click Continue.

2. Enter the local-as number for network identification: 200.

3. Expand active-vpn-instance-profiles and click to select the profile-id you created in the previously: L3VPN_NM-SRTE-RP-PE-A-7. Click Continue.

4. Define the network access parameters for communication from the PE to the CE:

   • Under vpn-network-accesses, click to create a new set of VPN access parameters and provide a unique ID. Click Continue.

   • In the Interface-id field, type Loopback70. This is the identifier for the physical or logical interface. The identification of the sub-interface is provided at the connection level and/or the IP connection level.

   • Expand ip-connection > ipv4 and enter a local-address (70.70.70.1) and then prefix-length (30).

   • For routing protocols, click to create a unique id, set the type to bgp-routing, and then expand bgp to set the peer-as number (70), and the address-family (ipv4). In addition, set the bgp neighbor (70.70.70.2) and the multihop number (for example, 11) that indicates the number of hops allowed between the bgp neighbor and the PE device.

     

   • Click X in the top-right corner until you are back on the Create L3VPN screen.

   • Similarly, create the other VPN nodes: PE-B and PE-C.

Step 8

Commit your changes or click Dry run to check what will be configured on the devices before you commit.

Step 9

Check that the new L3VPN service appears in the table and its provisioning state is Success.

Step 1

From the main menu, choose Services & Traffic Engineering > VPN Services. The map opens on the left side of the page, and the table opens on the right side.

Step 2

Select the newly created, unmonitored service, which will have a gray health indicator.

Step 3

In the Actions column for that service, click and select Start monitoring.

Note	The Health column color coding indicates the health of the service: Blue = Initiated Green = Good Orange = Degraded Red = Down Gray = Not Monitoring

Step 4

In the Monitor Service dialog box, select the Monitoring Level. For help with selecting the appropriate monitoring level for your needs, see chapter Reference – Basic Monitoring and Advanced Monitoring in the Cisco Crosswork Network Controller 7.1 Service Health Monitoring guide.

Step 5

Click Start Monitoring.

Note	Once you have started monitoring the health of the service, in the Actions column, click to view additional Service Health options, such as: Stop monitoring, Pause monitoring, Edit monitoring settings, and Assurance graph.

Step 6

Repeat these steps for each service that you wish to start health monitoring.

Step 1

In the L3VPN Service table, click on the service name or click in the Actions column and choose View details from the menu.

The map opens, and the service details are shown to the right of the map.

or

From the main menu, choose Services & Traffic Engineering > VPN Services.

The map opens, and a table of VPN services is displayed to the right of the map.

Click on the VPN in the Services table. If there are many services in the table, you can filter by name, type, or provisioning state to help locate the VPN.

In the map, the VPN is an overlay on the topology. It shows a representation of the three endpoints and a dashed line indicating that it is a virtual path.

Select the Show: Participating only check box to see only the devices involved in the selected VPN.

Step 2

click in the Actions column and choose View details from the menu to drill down to a detailed view of the VPN service, including the device configurations and the computed transport paths.

Step 3

To see the computed paths for this VPN, click on the Transport tab in the Service details panel. All the dynamically created SR-TE policies are listed in the Transport tab. Select one or more SR-TE policies to see the path from endpoint to endpoint on the map.

In this example, we examine the disjoint paths computed from PE-A to PE-B and from PE-A to PE-C.

Step 4

To see the physical path between the endpoints, select the Show: IGP path check box in the top-left corner of the map. Hover with your mouse over a selected policy in the table to highlight the path in the map and show prefix SID and routing information.

Step 5

To filter the topology to a specific Flex-Algo constraint and visualize nodes and links you have configured manually in your network, click the button at the top right of the map and do the following:

1. Click the Flex Algo tab.

2. From the drop-down list, choose up to 2 Flex-Algo IDs.

3. View the Flex-Algo Types and confirm that the selection is correct. Also, note the color assignments for each Flex-Algo ID.

4. (Optional) Check the Show selected Flex Algo topology only check box to isolate the Flex-Algo IDs on the topology map. When this option is enabled, SR policy selection is disabled.

5. Check the Show Flex Algo A+B links only to show only those links and nodes that participate in both Flex-Algos.

   Suppose a selected Flexible Algorithm is defined with a criteria, but there are no links and node combinations that match it (for example, a defined affinity to include all nodes or links with the color blue). In that case, the topology map will be blank. If a selected Flexible Algorithm is not configured on a node or link, the default blue link or node color appears.

6. Click Apply. You must click Apply for any additional changes to your Flex-Algo selections to see the update on the topology map.

7. (Optional) Click Save view to save the topology view and Flexible Algorithm selections.

Step 1

Observe the automatic network optimization.

Step 2

The SR-PCE constantly monitors the network and automatically optimizes the traffic path based on the defined SLA. For illustration purposes, let’s look at what happens when one of the links goes down, in this case, the link between P-BOTTOMLEFT and P-BOTTOMRIGHT. This means the previous path from PE-A to PE-C is no longer viable. Therefore, the SR-PCE computes an alternative path, from PE-A to PE-C and from PE-A to PE-B, to compensate for the down link and maintain the disjoint paths.

Recomputed paths:

Source and destination	Old path	New path
PE-A > PE-C	PE-A > P-BOTTOMLEFT > P‑BOTTOMRIGHT > PE-C	PE-A > P-TOPLEFT > P‑BOTTOMRIGHT > PE-C
PE-A > PE-B	PE-A > P-TOPLEFT > P‑TOPRIGHT > PE‑B	PE-A > P-BOTTOMLEFT > P‑TOPRIGHT > PE-B

Step 1

From the main menu, choose Services & Traffic Engineering > VPN Services. The map opens on the left side of the page, and the table opens on the right side.

Step 2

Select the required service and in the Actions column, click and choose View details. The Service details panel appears on the right side.

Step 3

Select the Health tab and click the Active symptoms tab. The Active symptoms table displays Active symptoms and Monitoring errors by default. To filter the table to show only the Active symptoms, either click the Symptoms tab in the mini dashboard above the table or select Symptoms from the filter box under the Type. The table now shows a filtered list containing only the Active symptoms.

Step 4

Click on a root cause to view the Symptom details and the Failed subexpressions & metrics information. As required, you can expand or collapse all of the symptoms listed in the tree. In addition, use the Show only failed toggle to focus only on the failed expression values.

Step 5

Click the Transport and Configuration tabs and review the details provided.

Step 6

Click X in the top-right corner to return to the VPN Services list.

Step 7

In the Actions column, click for the required degraded service and click Assurance graph. The topology map of services and subservices appear with the Service details panel showing Service key, Status, Monitoring status, Monitoring settings, Sub services, and Active symptoms details.

Step 8

By default, the Assurance Graph displays a concise view with only the service and the top level subservices (aggregator nodes). Click the icon in the nodes to expand the graph and to view the dependent details. To expand all the nodes at once, click the Sub services: Expand all check box at the top.

Step 9

Select a degraded subservice in the Assurance Graph. The Subservice details panel appears with subservice metrics, and subservice-specific Active symptoms and Impacted services details.

Step 10

Inspect the Active symptoms and Impacted services information and the root causes associated with the degraded service to determine what issues need to be addressed to maintain a healthy setup.

Step 11

From the main menu, choose Administration > Collection Jobs.

Step 12

Click the Parameterized jobs tab.

Step 13

Review the Parameterized jobs list to identify the devices that may have service health degradation issues. By reviewing Parameterized jobs, you can identify and focus on gNMI, SNMP, and CLI-based jobs by their Context ID (protocol) for further troubleshooting purposes.

Step 14

In the Job Details panel, select the collection job you want to export and click to download the status of collection jobs for further examination. The information provided is collected in a .csv file when the export is initiated.

Step 15

Click Export.

Step 16

To check the status of the exported collection job data, click View export status at the top right of the Job details panel. The Export status jobs panel appears, providing the status of the export request.

Step 17

Review the exported .csv file for collection job details and the possible cause of the degraded device.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > SR-TE > ODN-Template.

Step 2

Click to create a new template and give it a unique name.

In this case, the name is L3VPN_NM-SRTE-ODN_72-a. Click Continue.

Step 3

Choose the headend device, PE-A, and specify the color 72.

Step 4

Under srv6, select the Enable srv6 toggle.

Step 5

Under locator, enter the required SRv6 locator-name.

The locator name should match what is configured on the router.

Step 6

Under dynamic, select latency as the metric type. This is the SLA objective on which we are optimizing.

Step 7

Select the pce check box to specify that the path should be computed by the SR-PCE, not by the Path Computation Client (PCC).

Step 8

Define the required constraints. In this case, we want the computed paths to be disjoint in that they must not share a link.

Step 9

Check that the new ODN template appears in the table and its provisioning state is Success. Click in the Actions column and choose Config view to see the Yang model-based service intent data that details the ODN template you created.

Step 10

Create the other ODN templates listed above in the same manner.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > Routing Policy Tag.

Step 2

Click to create a new routing policy tag and type the name of the tag set: COLOR_70. Click Continue.

Step 3

Under tag-value, click and type the Tag-value: 70.

Step 4

Click Continue. The new routing policy tag name with the new tag value is visible. Click Commit changes.

Step 5

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > Routing Policy Destination Prefix.

Step 6

Click to create a new routing policy destination prefix and type the name DEST_PREFIX_SET_70.

Step 7

For Mode, select ipv6.

Step 8

Expand prefixes and click + to add the ip-prefix to the prefix-list.

Step 9

For Ip-prefix, type 70:70:70::0/64 and click Continue.

Now, we are ready to create the first route policy, L3VPN_NM-SRTE-RP-PE-A-7. The other route policies can be created using the same procedure.

Step 10

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > Routing Policy.

Step 11

Click to create a new route policy and type a unique name for the top-level policy definition: L3VPN_NM-SRTE-RP-PE-A-7. Click Continue. The statements section appears.

Step 12

Expand statements, click to add the name of the policy statement (such as stmt1), and click Continue. The statement{stmt1} panel appears, showing conditions and actions sections.

Step 13

Expand conditions and then expand match-dest-prefix-set before selecting the prefix-set list and select DEST_PREFIX_SET_70. This is what references a defined prefix set.

Step 14

Expand actions and then expand bgp-actions.

Step 15

For bgp-actions, slide the Enable bgp-actions toggle to the on position. By toggling bgp-actions on, it defines the top-level container for BGP-specific actions.

Step 16

Now expand set-ext-community. Slide the enable-set-ext-community toggle to the on position. Toggling on set-ext-community sets the extended community attributes.

Step 17

For Method and reference, select the ext-community-set-ref list and select COLOR_70. The Ext-community-set-ref references a defined extended community set by name.

Step 18

Click X in the top-right corner to close the statement{stmnt1} panel and click Commit changes.

Step 19

Create the other route policies (L3VPN_NM-SRTE-RP-PE-B-7 and L3VPN_NM-SRTE-RP-PE-C-7) in the same manner.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3VPN > VPN Profiles.

Step 2

Click to create a valid VPN profile to be referenced in the VPN service.

Step 3

Select the Id list and select L3VPN_NM-SRTE-RP-PE-A-7.

Step 4

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L3vpn > L3vpn-Service.

Step 5

Click to create a new service and type a new vpn-id: L3VPN_NM-SRTE-ODN-70.

Step 6

Click Continue.

Step 7

Create vpn-instance-profiles, which is a container that defines the route distinguisher (RD), route targets, and the export/import route policy. We will create vpn-instance-profiles for each endpoint, as follows:

Step 8

Define each VPN endpoint individually: PE-A, PE-B, and PE-C.

1. Expand vpn-nodes and click to select the relevant device from the list: PE-A. Click Continue.

2. Enter the local autonomous system number for network identification: 200.

3. Expand active-vpn-instance-profiles and click to select the Profile-id you created in the previously: L3VPN_NM-SRTE-RP-PE-A-7. Click Continue.

4. Define the network access parameters for communication from the PE to the CE:

   • Under vpn-network-accesses, click to create a new set of VPN access parameters and provide a unique ID. Click Continue.

   • In the Interface-id field, type Loopback70. This is the identifier for the physical or logical interface. The identification of the sub-interface is provided at the connection level and/or the IP connection level.

   • Expand ip-connection > ipv6 and enter a Local-address (70:70:70::1) and the Prefix-length (64).

   • Expand routing-protocols and click before typing a unique identifier for the routing protocol: EBGP. Click Continue.

   • From the routing protocol Type list, select bgp-routing.

   • Expand bgp and for Peer-as, type 70. This information indicates the customer’s ASN when the customer requests BGP routing.

   • From the Address-family list, select ipv6.

   • Under neighbor, click to create a neighbor IP address and type 70:70:70::2. Click Continue.

   • Type the Multihop number 11. This describes the number of IP hops allowed between a given BGP neighbor and the PE.

   • For redistribute-connected, click and select ipv6 from the Address-family list. Click Continue.

   • Click X in the top-right corner until you are back on the Create L3VPN screen.

   • Similarly, create the other VPN nodes: PE-B and PE-C.

Step 9

Commit your changes or click Dry run to check what will be configured on the devices before you commit.

Step 10

Check that the new L3VPN service appears in the table and its provisioning state is Success.

Step 1

In the L3VPN Service table, click on the service name or click in the Actions column and choose View details.

1. From the main menu, choose Services & Traffic Engineering > VPN Services.

   The map opens, and a table of VPN services is displayed to the right of the map.

2. Click on the VPN in the Services table. If there are many services in the table, you can filter by name, type, or provisioning state to help locate the VPN.

   In the map, you will see the VPN as an overlay on the topology. It shows a representation of the three endpoints and a dashed line that indicates that it is a virtual path.

   

   Select the Show participating only check box to see only the devices involved in the selected VPN.

   Note

   When the Provisioning state is Failed, an information icon appears. Click on the icon to see details of the failure. This is true whether you are on the VPN services, Service details, and many of the Provisioning screens that show a table of services and their Provisioning status. If you select the icon, Error Message details appear describing the failure. You can also click the Show error details link to view the Component errors screen and take action to fix the error. Each failed source provides further error message details and recommendations. For example, in the Action column for the failed source on the component Errors screen, you may click for different options (such as Check-sync, Sync-to, Sync-from, Compare-config, View job status) that will assist in fixing the error. Service level actions are also available for additional options (such as Re-deploy, Reactive-re-deploy, Re-deploy reconcile, Clean-up, etc.) that will assist in fixing the service level error. Use the information icons next to these options for further details on fixing the issue.

   

   

   

   

Step 2

In the Actions column, click to drill down to a detailed view of the VPN service, including the device configurations and the computed transport paths.

Step 3

To see the computed paths for this VPN, click on the Transport tab in the Service details panel. All the dynamically created SR-TE policies are listed in the Transport tab. Select one or more SR-TE policies to see the path from endpoint to endpoint on the map.

Step 4

To see the physical path between the endpoints, select the Show: IGP path check box in the top-left corner of the map. Hover with your mouse over a selected policy in the table to highlight the path in the map and show prefix SID and routing information.

Step 1

Observe the automatic network optimization.

Step 2

The SR-PCE constantly monitors the network and automatically optimizes the traffic path based on the defined SLA. For illustration purposes, let’s look at what happens when one of the links goes down, in this case, the link between P-BOTTOMLEFT and P-BOTTOMRIGHT. This means the previous path from PE-A to PE-C is no longer viable. Therefore, the SR-PCE computes an alternative path, both from PE-A to PE-C and from PE-A to PE-B, to compensate for the link that is down and maintain the disjoint paths.

Recomputed paths:

Source and destination	Old path	New path
PE-A > PE-C	PE-A > BOTTOM-LEFT > BOTTOM-RIGHT > PE-C	PE-A > TOP-LEFT > BOTTOM-RIGHT > PE-C
PE-A > PE-B	PE-A > TOP-LEFT > TOP-RIGHT > PE‑B	PE-A > BOTTOM-LEFT > TOP-RIGHT > PE-B

Step 1

Prepare the input required to produce the SID list for the path from endpoint to endpoint. You will need the router ID of each endpoint, as follows:

{
  "input": {
    "head-end": "100.100.100.7",
    "end-point": "100.100.100.5",
    "sr-policy-path": {
      "path-optimization-objective": "igp-metric"
    }
  }
}'

Step 2

Invoke the API on Crosswork Network Controller server by using the input prepared in the previous step. For example:

curl --location --request POST 
'https://10.194.63.198:30603/crosswork/nbi/optima/v1/restconf/operations/cisco-crosswork-
optimization-engine-sr-policy-operations:sr-policy-dryrun' \
--header 'Content-Type: application/yang-data+json' \
--header 'Accept: application/yang-data+json' \
--header 'Authorization: Bearer 
eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJhZG1pbiIsImlzRnJvbU5ld0xvZ2luIjoidHJ1ZSIsInBvbGljeV9pZCI6ImFkb
WluIiwiYXV0aGVudGljYXRpb25EYXRlIjoiMjAyMS0wMy0yMlQxNjozODozNy43NDY2MTZaW0dNVF0iLCJzdWNjZXNzZnV
sQXV0aGVudGljYXRpb25IYW5kbGVycyI6IlF1ZXJ5RGF0YWJhc2VBdXRoZW50aWNhdGlvbkhhbmRsZXIiLCJpc3MiOiJod
HRwOlwvXC9sb2NhbGhvc3Q6NTQ4OVwvU1NPIiwibGFzdF9uYW1lIjoic21pdGgiLCJjcmVkZW50aWFsVHlwZSI6IlVzZXJ
uYW1lUGFzc3dvcmRDcmVkZW50aWFsIiwiYXVkIjoiaHR0cHM6XC9cLzEwLjE5NC42My4xOTg6MzA2MDNcL2FwcC1kYXNoY
m9hcmQiLCJhdXRoZW50aWNhdGlvbk1ldGhvZCI6IlF1ZXJ5RGF0YWJhc2VBdXRoZW50aWNhdGlvbkhhbmRsZXIiLCJsb25
nVGVybUF1dGhlbnRpY2F0aW9uUmVxdWVzdFRva2VuVXNlZCI6ImZhbHNlIiwiY2hhbmdlX3B3ZCI6ImZhbHNlIiwiZXhwI
joxNjE2NDU5OTIwLCJpYXQiOjE2MTY0MzExMjAsImZpcnN0X25hbWUiOiJqb2huIiwianRpIjoiU1QtODQtOFVlWXMybEt
3R2d1Z3RIYjl4MzVmTFlNTGVVRlp6OURyNGpoeFcxakhsV01VYXdXSWgxbUdTd01aRC1tOEk1S2Z0amI2ZmlWTUhlYnBYY
jBMMFZqRFc2WVppUFVUbHRpNFVpZnNUeG9aQ284WWpPWEc2VlFjS0Mwb29lWjJhc3BWanMzYnA3bHo5VkhySlBCTzl5TDN
GcFRIWXRPeWJtVi1jYXMtMSJ9.Vi4k0w8KsOv5M_O8zBqWochT3k9V9Pn2NjSn5ES9c5Pf-
4ds0o4kk6xuZx5_cggauiEICuUMnzmRzneST-oAuA' \
--data-raw '{
  "input": {
    "head-end": "100.100.100.5",
    "end-point": "100.100.100.7",
    "sr-policy-path": {
      "path-optimization-objective": "igp-metric" 
    }
  }
}'

Step 3

Note the SID list ID in the API response. You will use this when creating the SID list in the next step. For example:

{
  "cisco-crosswork-optimization-engine-sr-policy-operations:output": {
    "segment-list-hops": [
      {
        "step": 0,
        "sid": 23002,
        "ip-address": "100.100.100.7",
        "type": "node-ipv4"
      }
    ],
    "igp-route": [
      {
        "node": "PE-A",
        "interface": "GigabitEthernet0/0/0/0"
      },
      {
        "node": "P-TOPLEFT",
        "interface": "GigabitEthernet0/0/0/2"
      },
      {
        "node": "P-BOTTOMRIGHT",
        "interface": "GigabitEthernet0/0/0/3"
      }
    ],
    "state": "success",
    "message": ""
  }
}

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > SR-TE > SID-List.

Step 2

Click to create a new SID list and give it a unique name. For this example, the SID list name is L2VPN_NM-P2P-SRTE-PE-C-240. Click Continue.

Step 3

Under Sid, click to create a new SID index and give it a numeric value. Click Continue.

Step 4

Under mpls, enter the SID ID that was received in the API response in Step 1.

Step 5

Click X in the top-right corner to return to the SID list. Your new SID appears in the index table.

Step 6

Repeat these steps to create additional SID indexes, as required.

Step 7

Commit your changes.

Step 8

Check that the new SID list appears in the table.

Step 9

Create another SID list for the traffic from PE-A to PE-C. For this example, the SID list name is L2VPN_NM-P2P-SRTE-PE-A-240.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > SR-TE > Policy.

Step 2

Click to import.

Step 3

Download the sample .json or .xml file, which will serve as a template for the required configuration. In the Import Service dialog, click the Download sample .json and .xml files (.zip) link.

Step 4

Unzip the downloaded file and open sr-Policy.xml in an XML editor.

Step 5

Edit the xml file as required. Provide a name for the SR-TE policy, and specify the SID list to be associated with this policy. Save the xml file.

Step 6

In the Import Service dialog, select Policy as the type of file to import, browse to the edited xml file, and click . If there are any errors in the file, you will receive a notification. If there are no errors, the file will be imported, and the policy and the devices will be configured accordingly.

Step 7

Check whether the new SR-TE policy appears in the Policy table and whether its Provisioning State is Success.

Step 8

Click in the Actions column and choose Config view to see the Yang model-based service intent data that details the SR-TE policy you created. You can also check the devices themselves to ensure they were provisioned correctly.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L2vpn > L2vpn-Service.

Step 2

Click to import.

Step 3

If you did not download the sample .json or .xml files in Step 3, do so now.

Step 4

Open l2vpn-service.xml in an XML editor.

Step 5

Edit the xml file as required. Provide a name for the L2VPN, configure each endpoint, and define the VPN parameters.

This is the configuration for PE-A in our example:

Step 6

Save the xml file.

Step 7

In the Import Service dialog, select l2vpn service as the type of file to import, browse to the edited xml file, and click . If there are any errors in the file, you will receive a notification. If there are no errors, the file will be imported, and the policy and the devices will be configured accordingly.

Step 8

Check that the new L2VPN service appears in the L2VPN Service table and its Provisioning State is Success.

Step 9

Click in the Actions column and choose Config view to see the Yang model-based service intent data that details the VPN service you created. You can also check the devices themselves to ensure that they were provisioned correctly.

Step 1

Locate the L2VPN in the VPN Service table.

Step 2

Click in the Actions column and choose Edit.

Step 3

Under vpn-nodes, select PE-A and click the Edit button above the table.

Step 4

In the pane that opens on the right, open the te-service-mapping > te-mapping section.

Step 5

In the sr-policy tab, you can find the list of configured SR policies in the policy-type drop-down list. Choose the policy created for PE-A: L2VPN_NM-P2P-SRTE-PE-A-240 from the list or enter the name of the SR-TE policy in the policy field.

Step 6

Click X in the top-right corner to close the PE-A pane.

Step 7

Repeat the above steps for PE-C and attach the SR-TE policy: L2VPN_NM-P2P-SRTE-PE-C-240.

Step 8

Click Commit changes.

Step 1

From the main menu, choose Services & Traffic Engineering > VPN Services. The map opens on the left side of the page, and the table opens on the right side.

Step 2

Select the newly created, unmonitored service, which will have a gray health indicator.

Step 3

In the Actions column for that service, click and select Start monitoring.

Note	The Health column color coding indicates the health of the service: Blue = Initiated Green = Good Orange = Degraded Red = Down Gray = Not Monitoring

Step 4

In the Monitor service dialog box, select the Monitoring level. For help choosing the appropriate monitoring level for your needs, see Crosswork Network Controller 7.1 Service Health Guide reference chapter, Basic Monitoring and Advanced Monitoring rules.

Step 5

Click Start monitoring.

Note	Once you have started monitoring the health of this service, select the Actions column and click to view additional Service Health options. You will see Stop monitoring, Pause monitoring, Edit monitoring settings, and Assurance graph options.

Step 6

Repeat these steps for each service for which you wish to start health monitoring.

Step 7

Click X in the top-right corner when you are done.

Step 1

In the L2VPN Service table, in the Actions column for the new VPN, click and choose View details from the menu. The map opens, and the service details are shown to the right of the map.

1. Click on the VPN in the Services table. If there are many services in the table, you can filter by name, type, or provisioning state to help locate the VPN.

2. In the map, you will see the VPN as an overlay on the topology. It shows a representation of the endpoints and a solid line that indicates that it is a virtual path.

3. Select the Show: Participating only check box if you do not want to see the devices that are not involved in the selected VPN.

   

Step 2

Under the Actions column, click and choose View details to drill down to a detailed view of the VPN service, including the device configurations, the computed transport paths, and the health status for transport paths.

Step 3

In the Transport tab, select one or more SR-TE policies to see the path from endpoint to endpoint on the map. The image below shows the path from PE-C to PE-A. The Show: IGP path check box in the top left corner of the map is selected so the physical path is shown. The dashed line indicates that this link is being used to transport multiple services.

Step 1

Return to the VPN Services list.

Step 2

In the Actions column, click for the degraded service and click Assurance graph. The topology map of services and subservices appear with the Service details panel showing Service key, Status, Monitoring status, Monitoring settings, Sub services, and Active symptoms details.

Step 3

At the top of the page, click the Show History toggle. The Assurance Graph's historical timeline appears. This timeline shows different ranges of historical health service monitoring details from one day (the Last Day) up to the Last 60 Days.

Step 4

Review the root cause information by clicking a particular event. The Service details panel reloads, showing the active symptoms and the root causes associated with the event. Columns can be resized using your mouse or you can select the gear icon to deselect or select columns you want to appear.

Step 5

To further isolate the possible issues and to utilize the last 24Hr metrics, perform the following steps:

1. In the historical timeline, use your mouse to select the range of historical health service monitoring details from one day (the Last Day) up to the Last 60 Days.

   Note

   At the top-right of the historical timeline, select the appropriate icons to either zoom in or out, horizontally scroll through the date ranges, or refresh the graph to go back to the most recent event, for example. You can also use your mouse to draw a rectangle over events to further zoom in on the degraded devices. Events that are consecutive may appear as a line of white space.

2. Click on a degraded event in the historical timeline. The Service details panel reloads, showing any active symptoms and the root causes to be inspected. Expand the table and information as necessary for further details.

   

Step 6

Check the Down & degraded only check box at the top-left corner of the Assurance Graph to show only the subservices which are degraded, along with other dependent but healthy subservices. Inspect the Service details panel showing the active symptoms and their root cause. Uncheck the Down & degraded only check box and check the Soft dependencies check box in the top-left corner of the Assurance Graph. Soft dependencies implies that a child subservice’s health has a weak correlation to its parent’s health. As a result, the degraded health of the child will not result in the parent’s health degradation.

Step 7

Select the degraded subservice in the map to show the subservice details.

Step 8

Click the Symptoms tab to show any root causes for the service health details, and then click the Impacted services tab to view the impacted services.

Step 9

Click X in the top-right corner to return to the VPN Services list. In the Actions column, click for the degraded service and click Assurance graph to show the Service details panel.

Step 10

Again, select the Show History toggle in the top-right corner of the Service details panel before selecting the blue metrics icon in one of the Root cause rows. The Symptoms metrics – Last 24 Hr bar chart appears. This chart provides details of the metric patterns, different sessions states (such as active, idle, failed if applicable) for individual root cause symptoms with Status, Session, Start Time, and Duration information to assist in troubleshooting prevailing issues. Use your mouse to hover over the chart to view the different details.

Step 11

From the main menu, choose Administration > Collection Jobs.

Step 12

Click the Parameterized jobs tab.

Step 13

Review the Parameterized jobs list to identify devices with service health degradation issues. By reviewing Parameterized jobs, you can identify and focus on gNMI, SNMP, and CLI-based jobs by their Context id (protocol) for further troubleshooting purposes.

Step 14

In the Job details panel, select the collection job you want to export and click . This process exports the collection job status at the time the export is initiated. The information you provide is collected in a .csv file for export.

Step 15

Click Export.

Step 16

To check the status of the exported collection job data, click View export status at the top right of the Job details panel. The Export status jobs panel appears, providing the status of the export request.

Step 17

Review the exported .csv file for collection job details and the possible cause of the degraded device.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > RSVP-TE > Tunnel.

Step 2

Click to create a new RSVP-TE tunnel and give it a unique name. Click Continue.

Step 3

In the identifier field, enter a numeric identifier for the tunnel. You will use this identifier to associate this RSVP-TE tunnel with the L2VPN service. For this example, the identifier is 2220.

Step 4

In the source and destination fields, enter the loopback0 IP address of the source (PE-A) and the destination (PE-B) devices. This is the TE router ID. To find the TE router ID, go to Topology and click on a device in the map or the list of devices. The Device details pane opens, and the TE router ID is shown in the routing section.

Step 5

Define the endpoints:

1. Under head-end, select the headend device from the dropdown list.

2. Under tail-end, select the tailend device from the dropdown list.

Step 6

Reserve bandwidth on the link. Under te-bandwidth > generic, enter the bandwidth threshold for the link.

Step 7

Define the path of the RSVP-TE tunnel.

1. Under Primary-paths, click to create a new path.

2. Provide a path name in the pane that appears on the right.

3. Select the path computation method – path-locally-computed.

4. Specify a numeric preference for the path. The lower the number, the higher the preference.

5. Define the optimization metric, in this case, igp.

   

Step 8

Click Commit changes.

Step 9

Verify that the RSVP-TE tunnel appears in the list of tunnels and that its provisioning state is Success.

Step 10

Click on the tunnel name to visualize the tunnel on the map and to see the tunnel details.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > L2VPN > L2vpn Service.

Step 2

Click to create a new service and give it a unique name. Click Continue.

Step 3

Choose the vpn-type field.

Step 4

Define each VPN endpoint individually – PE-A and PE-B.

1. Under vpn-nodes, click .

2. Select the relevant device from the vpn-node-id and ned-id dropdown lists and click Continue.

Step 5

Define the LDP signaling options by creating one or more pseudowires. In this case, specify the TE router ID of the peer device (PE-B), and provide a unique numeric label to identify the pseudowire.

Step 6

Attach the RSVP tunnel to the service:

1. Under te-service-mapping > te-mapping, click the te-tunnel-list tab.

2. Click the te-tunnel-id tab.

3. If you have an RSVP-TE tunnel on the device that was configured externally to Crosswork Network Controller, you can provide that tunnel ID under this tab. Use the toggle button next to the Select existing te-tunnel-id field to choose the RSVP-TE tunnel from a list of configured tunnels or manually enter the tunnel ID.

   

4. If you want to specify the IETF-TE service name from which te-tunnel-id will be extracted, click the ietf-te-service tab and specify the service name. The tunnel ID will be extracted from the tunnel configuration.

Step 7

Define the VPN network access. In this case, we are using dot1q encapsulation and we have specified the physical interface (GigabitEthernet0/0/0/2) and the VLAN ID (2220).

Step 8

Follow the above steps for PE-B as well.

Step 9

Click Commit Changes. Verify that the L2VPN appears in the list of VPN services and that its Provisioning state is Success.

Step 1

In the L2VPN Service table, click on the service name. The map opens, and the service details are shown to the right of the map.

1. From the main menu, choose Services & Traffic Engineering > VPN Services.

   The map opens, and a table of VPN services is displayed to the right of the map.

2. Click on the VPN in the Services table. When there are many services in the table, you can filter by name, type, or provisioning state to help locate the VPN.

   In the map, the VPN is an overlay on the topology. It shows a representation of the three endpoints and a dashed line indicating that it is a virtual path. Use the buttons at the top right of the map to toggle between the logical and geographical maps.

Step 2

To see the hops in the route between PCC7_56 and PCC5_81, click the Transport tab and select one or more of the underlying TE tunnels to see the path from endpoint to endpoint on the map.

Step 3

As the RSVP-TE tunnels are configured with a reserved bandwidth, if the bandwidth utilization across the link exceeds the specified bandwidth, the path would be rerouted.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO) > SR-TE > Policy.

Step 2

Click to create a new SR-TE policy and give it a unique name. Click Continue.

Step 3

Define the endpoints:

1. Under head-end, click and select the headend device from the dropdown list and click Continue. Click X to close the Headend pane.

2. Enter the IP address of the tail-end device.

3. Enter a color to identify the traffic.

Step 4

Define the parameters on which the path will be computed:

1. Under path, click .

2. Enter a path preference and click Continue.

3. In the dynamic-path tab, select te in the metric-type dropdown list as the optimization objective.

4. Select the pce check box to have the SR-PCE compute the paths for this policy.

   

5. Click X to close the path pane.

Step 5

In the Bandwidth field enter the requested bandwidth in Kbps. In this case, we are requesting 250 Mbps or 250,000 Kbps.

Step 6

Click Commit changes. The new policy is created and appears in the list of SR-TE policies. The provisioning state should be Success.

Step 7

Verify the new policy by viewing its details and its representation on the map:

1. Click in the Actions column and choose View.

2. The map opens with the SR-TE policy details displayed to the right of the map.

   Note	The policy's operational state is down because the SR-PCE alone cannot address bandwidth computations before the BWoD functionality within Crosswork Network Controller is enabled.

Step 1

From the main menu, choose Services & Traffic Engineering > Bandwidth on Demand.

Step 2

Toggle the Enable switch to True, and enter 80 to set the utilization threshold percentage. To find descriptions of other options, hover the mouse over.

Step 3

Click Commit changes.

Step 1

From the main menu, choose Services & Traffic Engineering > Provisioning (NSO).

Step 2

In the Policy table, locate and select the path computed for the endpoints.

Step 3

The path is shown as an overlay on the map. Select the IGP path check box to see the physical path between the endpoints.