Microwave backhaul service creation using NSP Intent-Based Service Fulfillment

Intent-Based Service Fulfillment

You can use the NSP intent manager and service fulfillment functions to create L2 microwave backhaul services for Wavence equipment. The NSP automates service creation through specialized workflows, which must be installed and configured before they can be triggered. This section describes the high-level steps required to install the Wavence backhaul service intent and workflow files, create a service template, and create a service. For more information about using the NSP, see the NSP Network Automation Guide.

Before using intent-based service fulfillment, ensure the following have been performed:

the physical links are configured (except for single-site service)
Ethernet rings are configured, if you are creating a service that includes one or more rings
the Wavence backhaul service intent package was downloaded from the Nokia Support Portal
in the NFM-P, the administrator user account has the OSS Management role configured in its Scope of Command

Before starting this process, it will be useful to have the NSP Network Automation Guide documentation open or easily available.

Stages

In Network Intents, import the wavencebackhaul intent file. See the NSP Network Automation Guide for information about installing intent files.

In the Workflows, import the following workflows included with the Wavence backhaul service intent package:

Separate_Topology
Wavence_Backhaul_Service_Connect
Wavence_Backhaul_Service_Deploy

After the workflows are imported, ensure the Service Life Cycle State is set to Published. See the NSP Network Automation Guide for information about importing workflows and setting life cycle states.

In Workflows, create a kafka trigger for the Wavence_Backhaul_Service_Connect workflow for when a service is created, using the following parameter values:

Parameter	Value
Kafka Topic	nsp-db-fm
Trigger Name	create_alarm
Trigger Rule	$[?(@.alarmName == ‘connectNotAttemptedOnService’ \|\| @.alarmName == ‘serviceModified’ )]
Kafka Event	CREATE

See the NSP Network Automation Guide for information about managing kafka triggers.

Create a second kafka trigger for the same workflow for when a service is updated, with the following values:

Parameter	Value
Kafka Topic	nsp-db-fm
Trigger Name	update_alarm
Trigger Rule	$[?(@.alarmName == ‘connectNotAttemptedOnService’ \|\| @.alarmName == ‘serviceModified’ )]
Kafka Event	UPDATE

In the NSP application, import the wavencebackhaul intent you installed using the intent manager previously. See the NSP Network Automation Guide for information about importing intents.

Create a service template, then configure the Service Intent Type to use the wavencebackhaul intent and add the Wavence_Backhaul_Service_Deploy workflow as an assigned workflow. See the NSP Network Automation Guide for information about creating service templates.

In the Inventory tab, configure Customers as required. See the NSP Network Automation Guide for information about customer configuration.

In the Services tab, create a service using the Wavence_Backhaul service template. Configure the service as required according to your network. See the NSP Network Automation Guide for information about service configuration.

Monitoring created services

After creating the service, the Deploy and Connect workflows are automatically launched as required to configure the specified Wavence devices.

You can monitor the progress of the workflows using Workflows, the status of the devices using Device Management, the status of the newly-created service and watch for alarms or faults using the Network Map and Health dashboard. Additionally, Wavence backhaul service status can be monitored using the Network Map and Health dashboard; see To display Wavence backhaul service status information on the NSP Network Map and Health dashboard.

Separating a service

After creating a service, you can separate the service using a workflow. Select the service you need to separate, and perform the Execute Workflow action, then choose the Separate_Topology workflow. See the NSP Network Automation Guide for more information about executing workflows on a service.