The Enterprise NSP system is deployed as cluster of one or more VMs in the Kubernetes container environment. The NSP system consists of a deployer host, which holds the container image and Helm repositories and deploys the containerization environment for NSP clusters, and the NSP cluster VMs, which host the main NSP functions and load balance as needed. Within NSP cluster VMs, the NSP cluster host performs configuration operations.

Kubernetes is the orchestration system that hosts the NSP VM clusters and is included in the NSP software bundle. For more information about the NSP components described here, see the NSP Installation and Upgrade Guide.

Enterprise NSP requires the base Platform feature package as a minimum.

A typical NSP installation contains UI elements for a wide variety of functions. Enterprise NSP has a focused UI that only contains the relevant elements for the use-case type. In order to display the UI for the desired Enterprise NSP use-case, before installing NSP you must edit the nsp-config.yml configuration file as follows:

nsp:

   deployment:

       type:standard

       mode:enterprise-utilities

User access and permissions in the Enterprise UI

Admin users have full access and read/write/execute permissions for all options in the NSP menu tree. All other user types have their access defined according to Role Based Access Control, or RBAC. Enterprise NSP Admin users are required to use RBAC when configuring other user accounts to ensure that they have the permission levels that their duties require.

User configuration is described in the NSP System Administrator Guide.

Artifacts and adaptors are resource files that define network node characteristics and allow for management support in NSP by providing the mapping between node attributes and NSP attributes. Intent types, which define service characteristics, are also considered artifacts and can be installed using the NSP UI. These files typically come in the form of zip bundles that you obtain from the NSP software download site and import using NSP.

You will have the option to install NSP artifacts as part of the onboarding process. After onboarding, if you need to import additional artifacts later, use the procedures in the NSP Network Automation Guide rather than the onboarding wizard. To discover and manage Nokia 7210 SAS and 7705 SAR nodes in an NSP Enterprise deployment that does not include the NFM-P component, artifact bundles are available for download from the NSP software download site and described in the NSP Nokia Enterprise Artifact Guide.

To view the SAS/SAR artifacts bundle, see the NSP Nokia Enterprise Artifact Guide.

Caution: Do not install the SAS/SAR artifact bundle if NFM-P is present in the deployment. The SAS/SAR adaptor artifacts are intended for use only when basic inventory and alarms are required, and provisioning is not required.

To install an intent type, see How do I import an intent type from my computer? in the Network Automation Guide.