What is device configuration in NSP?

NSP Device Configuration

Device Configuration helps to define and deploy infrastructure configurations to an NSP managed network. With Device Configuration, the network engineer can easily define reusable configuration templates covering such areas as card, port, QoS, security, and routing policy configurations. Device Configuration is found in Device Management, in the Configuration views, if Network Infrastructure Management - Device Config is included in the deployment.

RESTCONF APIs are also available; see the API documentation on the Network Developer Portal.

Greenfield configuration of third-party equipment is supported and has been tested for Juniper card configuration. Brownfield configuration of third-party equipment has not been tested.

Intent types

NSP uses intent types to build configuration templates, which are then used to build configurations. 

The intent type defines the parameters that will be set when the configuration template is deployed. The configuration form can provide a parameter value or leave the value blank, to be set during deployment. If a parameter is not included in the configuration form, deploying the configuration template will not set that parameter on the target.

Users can create custom intent types in NSP or download predefined intent types from the Artifacts directory on the NSP software download site. Nokia recommends using predefined intent types where applicable.

Predefined intent types are delivered to the software download site outside the NSP release cycle. The intent types are delivered in zip files, which include a readme file for each intent type. See the NSP Device Configuration Intent Type Catalogue document in the Artifacts directory for the list and descriptions of the intent types in the collection.

Configuration templates

Operators use the configuration templates to deploy the configurations to the network either in bulk or on an individual target basis (NE or card/port). Device Configuration provides full feedback on the success (aligned) or failure (misaligned) of the deployment request, so that the operator is aware if the defined configuration is present and running in the network. The operator can audit and monitor for configuration drift that may occur over time and realign the network configuration back to the intended and defined configuration.

Templates can be defined with fixed or flexible attribute definitions. Certain attributes can be set with a fixed value (for example, MTU = 1500) that cannot be changed by the operator, or can be set with a default value that can be modified in the deployment phase.