The following tables present key dimension details for an NSP deployment with LSP management. These scale numbers apply to all functions of NSP unless otherwise specified.

Table 5-1: Scale limits for an NSP deployment with LSP management

The following table presents key dimension details for an NSP deployment with path control.

Table 5-2: Scale limits for an NSP deployment with path control

The following table presents key dimension details for an NSP deployment with path simulation.

Table 5-3: Scale limits for an NSP deployment with path simulation

NSP supports up to 64 asynchronous tasks. When the limit is exceeded, additional tasks are queued and will get executed as any of the executing workflows completes.

NSP supports up to 15 synchronous workflows. Synchronous workflows consume more resources and must be limited in parallel executions.

The following table presents scaling dimensions of stored executions for deployment of the NSP's Workflows function.

Table 5-4: Scale limits for Workflows deployment

The following tables present scaling dimensions for Model Driven Mediation application.

Table 5-5: Scaling dimensions – Model Driven Mediation application

Note: The nim module is used to identify and stitch MDM link endpoints. The above limit applies to any LLDP link with at least one MDM endpoint.

Table 5-6: MDM Authentication Session limits with NEs

The following table presents scaling dimensions for IGP Topology.

Table 5-7: Scaling dimensions – IGP Topology

The following table presents scaling dimensions for intent-based device configuration in the Device Management views.

Table 5-8: Scaling dimensions – intent-based device configuration

Note: Customers should use caution when invoking bulk actions at the template level with many thousands of configuration instances as this may take many hours to complete. Bulk operations will be optimized in a future NSP release.

NSP provides a wide variety of artifact bundles, some of which contain intent type artifacts. It is recommended that artifact bundles are installed selectively to ensure that no more than 200 intent type artifacts are deployed on a single NSP system.

If your NSP system requires more than 200 intent type artifacts, or if you have unknowingly exceeded 200 intent type artifacts and your pod won't come back up after a restart, please contact Nokia support.

The following table presents key dimension details for NSP's IP/optical coordination function in an NSP classic and model-driven IP + optical deployment as described in the NSP Installation and Upgrade Guide.

Table 5-9: Scale limits for IP/optical coordination in an NSP classic and model-driven IP + optical deployment

The NSP SNMP adapter artifacts, which provide SNMP adaptation for standard SNMP devices, can manage up to 50,000 devices in a large-scale NSP deployment. Devices are discovered at /24 subnet (250NEs at once), however, multiple discovery rules can be initiated in sequence. For large deployments, the user should stagger the discovery rule execution to limit the impact on the system. SNMP adapters utilize the MDM framework to manage basic functions such as discovery, fault management, and port inventory.

Note: The above figures represent the discovery of 7705 SAR NEs with minimal configurations, and do not account for more complex configurations such as services.

The supported maximum rate for granting REST tokens is one token every 2.5 seconds.