NSP can be deployed in three configurations providing different levels of IP-optical integration. Each configuration reflects how closely NSP and the optical environment are integrated for user access and network automation.

A Direct IP Management configuration is an NSP-only deployment and no subtending optical controllers are required. Consult Nokia Professional Services for information involving intent configuration.

In a Limited Cross Domain Management configuration, you install NSP and WS-NOC/RC as an integrated deployment. Operators use the NSP SSO framework for a common UI and sign-in. In this mode, alarm correlation, and optical equipment inventory are available. Limited Cross Domain Management does not include deploying the WaveSuite T-API artifact, as multi-layer visualization and discovery along with control and coordination feature packages are not supported.

In a Cross Domain Controller Management configuration, you still get the common UI and SSO as in Limited Cross Domain Management, but you also install the WS-NOC/RC T-API artifact such that the multi-layer visualization and discovery along with control and coordination feature packages can be made available.

Note: Cross Domain Controller Management configurations:

• do not support multiple network interface controllers (NICs) to segregate traffic for client, internal, and mediation communication

• do not support IPv6

See the NSP Release Notice for version compatibility between NSP, the NSP/WaveSuite T-API artifact, and the WaveSuite controller.

Table 1-1: IP-optical configuration types

Nokia's Model-Driven Mediation (MDM) platform is required in order to enable IP/Optical Coordination functionality, as are adaptors that correspond to the supported controller types.

The following installation options would be typical for a Cross Domain Controller Management configuration:

• serviceActivationAndConfiguration-intentBasedServiceFulfillment

• networkInfrastructureManagement-deviceConfig

• platformSdn

• platform-pluggableNetworkAdaptation

• platform-certificateManager

• platform-loggingMonitoring

• pathControlAndOptimization

• multilayerControlCoordination

• networkInfrastructureManagement-basicManagement

• serviceActivationAndConfiguration-originalServiceFulfillment

• platformMdm

• platform-baseServices

• intentBasedNetworkingFramework

• networkInfrastructureManagement-igpTopology

• networkInfrastructureManagement-gnmiTelemetry

• multilayerDiscoveryAndVisualization

• intentBasedNetworkingFramework

• platformMdm

• multilayerControlCoordination

• platformSdn

• networkInfrastructureManagement-deviceConfig

• serviceActivationAndConfiguration-intentBasedServiceFullfillment

When NSP and WS-NOC/RC are deployed in a Cross Domain Controller Management configuration, the following switchover behaviors will be observed:

• NSP DR switchover — after the standby NSP becomes the active NSP, it will automatically connect to the WS-NOC/RC, and no manual intervention is required for the T-API controller addition.

• WS-NOC/RC switchover — the T-API controller page will automatically point to the new standby WS-NOC/RC server, and no manual intervention is required. Switchover to the standby WSNOC/RC server typically takes 5-10 minutes. All the parameters in the T-API form will point to the new active WS-NOC/RC server, however, the cross launch URL must be manually updated to point to it.

• NSP DR switchover and WS-NOC/RC switchover — once NSP switchover occurs, the controller addition page will automatically point to the standby WS-NOC/RC. No manual intervention is required. The cross launch URL must be manually updated to the new active WS-NOC/RC server.

Note: Certificates are copied to both WS-NOC/RC servers during integration and, therefore, it is not necessary to manually copy any certificates for T-API. However, you must ensure that T-API artifacts are installed on both sites during NSP installation.