IP network automation (Network Services Platform)
IP network automation (Network Services Platform)
This domain covers Nokia Network Services Platform (NSP) as the automation and management layer for IP and optical networks: NFM-P, model-driven mediation (MDM), service fulfillment, assurance, and OSS integration via REST, NETCONF, and gNMI.
Core rules
- NSP discovers network elements and synchronizes their models. MDM manages SR OS MD-CLI and SR Linux; NFM-P manages classic CLI devices.
- Configuration changes use YANG models over NETCONF or gNMI. MD-CLI supports candidate configuration, commit, compare, and rollback.
- NSP Service Fulfillment uses templates and workflows to provision services such as VPRN, Epipe, VPLS, and EVPN; NSP Assurance collects telemetry and fault data.
- gNMI telemetry provides streaming state such as counters and operational status rather than polling.
Worked example
Provision a new Epipe between two PEs. In NSP, create a service template with SAP and SDP parameters, bind it to the discovered NEs, validate against YANG, and commit. NSP pushes NETCONF edit-config to each PE, then reads back operational state. If the commit fails on one PE, the workflow must roll back the other PE to avoid a half-built service.
Traps
- Treating NSP as a CLI replacement; it is a model-driven orchestrator.
- Mismatched YANG versions break templates and device adapters.
- Ignoring confirmed-commit timers can leave a configuration uncommitted.
- Assuming telemetry replaces SNMP for all fault data.