Workflow to deploy model-driven and classic management

Description

The following is the sequence of high-level actions required to deploy classic IP and model-driven management.

Note: Before you attempt to deploy an NSP component, you must review and comply with the deployment requirements and restrictions in the NSP Planning Guide.

Note: Some components of an NSP system can be at different releases; see the NSP Release Notice for component release compatibility information.

Note: User group properties are component-specific. When a user of a specific NSP component requires authorization to access an additional component, the user group must be re-created in the new component in order for them to access the functions associated with the new component. Instructions for creating a user group are in the component documentation.

Stages

1	Install an NSP cluster; perform To install the NSP. NOTE: For a deployment of this type, the Service Activation and Configuration feature package is required, as well as the Classic Management installation option.
2	Install the NFM-P, as described in NFM-P installation; configure the NFM-P to use the PKI server for TLS.
3	If you are adding an existing NFM-P system to the NSP cluster, add the servers to the NFM-P system; perform To add an independent NFM-P to an existing NSP deployment.
4	Perform To install the NSP templates for NSP service management on the NFM-P to install the NSP templates on the NFM-P.
5	Install the VSR-NRC; see VSR-NRC installation overview.
6	In a deployment of this type, the NSP uses the VSR-NRC to obtain IGP topology data by default. To configure the NSP to receive IGP topology from the CPAA instead, perform To change the IGP topology data source.