Onboarding a service into NSP

Purpose

This process shows you how to use the NSP to create a service and to monitor service health, service components’ health, and service performance.

See the NSP Network and Service Assurance Guide for detailed procedures.

Create a service using service management

Note: This process assumes that intent types for service creation have already been imported into Network Intents.


1	In NSP's service management views, create an Epipe service template, and use the template to create an Epipe service. See the service creation procedure in the NSP Service Management Guide.
2	View the service in Service Management, Services. Green icons indicate that the service was created and deployed successfully and is aligned with the template used to create it.
3	Select the service. In the More menu, there are multiple options for more information. Choose Open in Object Troubleshooting to view the service in the Object Troubleshooting dashboard.
4	The Object Troubleshooting dashboard displays summaries of alarm, site, endpoint, and tunnel binding health, and if event recording has been enabled, an event timeline summary. From the view drop-down, you can navigate to the event timeline or to the Current Alarms page. From the More menu () at the top of the page, you can add the service to the watchlist or open other detailed views. Adding the service to the watchlist allows you to easily navigate directly to it in the future. Scroll down in the view to see the Service map and Service inventory summaries.
5	Click Expand size () on the Service Endpoint summary dashlet to see detailed information about the port associated with the endpoint. Select an endpoint and choose Open in NE Inventory from the table row actions menu (). In the NE Inventory view, click on the port to see port details in the Info panel.

Initiate OAM tests from the service in the Object Troubleshooting dashboard

Returning to the Object Troubleshooting dashboard, create OAM tests to verify that the new service was provisioned and activated properly. On-demand testing verifies that traffic is flowing. After we have confirmed traffic, we can run proactive tests.


1	From the Object Troubleshooting dashboard, choose Create OAM Test Suite().
2	In the form that opens, configure the test parameters: Choose the test type and select both service endpoints. Choose an on-demand template from the Template drop-down. Enter a name for the group of tests. Choose a name that will make the tests easy to tell apart from others in a test results page. Click GENERATE & EXECUTE. The tests are executed.
3	When test generation is completed, choose View OAM test results from the More menu () in the Object Troubleshooting dashboard. The Data Collection and Analysis Management, Tests page opens, filtered to show the tests on the service. Select an on-demand test and choose View Results from the table row actions menu (). The on-demand test has passed, verifying that traffic is flowing.

View port details and utilization data in real time

From the NE inventory view, you can launch a utilization chart to view raw utilization data and verify that traffic is moving between service endpoints. This request creates a temporary telemetry subscription, which is deleted when the utilization chart is closed.


1	Identify the service endpoints: Open the Object Troubleshooting dashboard for the service and navigate to Service Endpoints. Select an endpoint and choose Open in NE Inventory from the table row actions menu (). The NE Inventory view for the endpoint NE opens.
2	In the NE Inventory view, click on a port. The port properties display in the Info panel. From the More menu for the port (), choose Plot utilization statistics.
3	Data Collection and Analysis, Visualizations opens, showing the chart of the pre-configured utilization counters.
4	The creation of the chart creates a temporary subscription for the utilization counters. The subscription is automatically deleted when you close the chart. Tip: The description of the temporary subscription is Created by telemetry data subscription.
5	While the chart is open, you can: Review the details of the pre-configured subscription by clicking Configure. Tip: From the New Chart , Configuration form, copy the Object Filter string. You can use this string to create a permanent subscription. Edit the chart configuration, for example, to show different counters. Save the chart to make the chart available from Data Collection and Analysis, Visualizations in the future.

Create permanent telemetry subscriptions for the service endpoints

Creating a telemetry subscription is an optional step, used for monitoring performance over time. A telemetry subscription allows you to configure statistics collection, for example, utilization statistics for a service, and to run the collection at any time, for example, for use in SLA management. Statistics can also be used to generate Analytics reports. To learn how to create a subscription, and for information about aggregation and retention for use in reporting, see the NSP Data Collection and Analysis Guide.

Perform the subscription creation procedure to create subscriptions for the service SAPs. See the NSP Data Collection and Analysis Guide for more information.

Use the object filter string you copied from the temporary subscription in Stage 5.

View utilization statistics from the Network Map and Health dashboard


1	In the Network Map and Health dashboard, navigate to the network map. Choose Enabled from the Utilization drop-down.
2	Hover over a link in the network map to show utilization information. A subscription is automatically created for the ports associated with the endpoints for NEs present on the Network Map and Health dashboard utilization map.
3	Open Data Collection and Analysis, Management. Edit the temporary subscription as needed. To chart a subscription, select the subscription and choose Open in Data Collection and Analysis Visualizations from the table row actions menu () Note: Two subscriptions are automatically generated, for two telemetry types: `base/classic-utilization/utilization` and `base/interfaces/utilization`. The interfaces telemetry type must be used for charting. Tip: The name of each subscription starts with `netsup-`.