Workflow for new NSP system deployment

Purpose

The following is the sequence of high-level actions that you must perform in order to install a standalone or DR NSP system.

Stages
 

Submit an NSP Platform Sizing Request to Nokia; if the NSP deployer host and cluster VMs are to be deployed on one station, ensure that you include the deployer host resources in your request.


If using physical hosts for the VMs, perform To provision the network bridge for NSP VMs on each physical host to create a network bridge for KVM access to the guest VMs.


Commission the required stations for the NSP VMs according to the specifications in the response to your Platform Sizing Request.


Ensure that the RHEL chronyd time-synchronization service is running on each component, and that chronyd is actively tracking a central time source. See the RHEL documentation for information about using the chronyc command to view the chronyd synchronization status.

Note: NSP deployment is blocked if the chronyd service is not active.


Contact Nokia to obtain the required license for your deployment.


If you are using a custom TLS certificate for the deployment, perform To generate custom TLS certificate files for the NSP to generate the required TLS files.


Install the NSP in the standalone or primary data center; perform To install the NSP.


In a DR deployment, install the NSP in the standby data center; perform To install the NSP.


If you are using NSP artifacts, see “How do I install adaptor artifacts that are not supported in the Artifacts view?” or “How do I install an artifact bundle?” to download and install the artifacts.


10 

If you are adding an existing independent NFM-P system to the NSP deployment, perform To add an independent NFM-P to an existing NSP deployment.