Prerequisites

Network configuration prerequisites

Before enhanced path control can be configured in NSP, the network configuration prerequisites must be met. The following table describes the requirements that can apply to similar use cases, and indicates whether each prerequisite is required for this use case.

Where an NSP intent type is not available, CLI or MD-CLI must be used to perform configuration on the device.

Prerequisite

Documentation reference

Notes

Mandatory for LSP Enhanced Path Control

GRPC configuration

  1. Generate security certificates

  2. Configure security and enable GRPC on all devices

  3. Apply security certificates on all devices

See SR TLS information here in the SR OS 24.3 R1 documentation: TLS

—

Netconf/SNMP provisioning: enable NETCONF and SNMP protocols on all devices

For more information about SNMP and NETCONF with SR OS, see SNMP and NETCONF in the SR OS 24.3 R1 System Management Guide.

—

NSP installation

Pathway for NSP system installation in the NSP Installation and Upgrade Guide

How do I enable TLS for telemetry and gNMI on_change support? in the NSP System Administrator Guide.

Include the following in your deployment:

  • Feature packs:

    • platform-baseServices

    • platform-pluggableNetworkAdaptation

    • platform-loggingMonitoring

    • networkInfrastructureManagement-basicManagement

    • networkInfrastructureManagement-deviceConfig

    • enhancedOptimization

  • Adaptor suites:

    • sros-common

    • sros-oc-logical-inventory

    • sros-23-7-r1

  • Additional required components:

    • VSR-NRC NE

Download the required artifact bundles from the NSP software delivery site:

  • NSP predefined set for ICM (device configuration)

  • vendor agnostic custom resources to support telemetry collection.

How do I install an artifact bundle? in the NSP Network Automation Guide

The vendor agnostic custom resources bundle is found on the NSP software delivery site, in the Adaptors folder along with your NE adaptor suite, for example, NSP → 23.11 → Adaptors → Nokia_SROS. Choose the zip file with va and cr in the filename, for example, nsp-telemetry-cr-va-sros-1.0.0-rel.10.zip.

Device discovery

Pathway for device discovery in the NSP Classic Management User Guide

How do I discover devices? in the NSP Device Management Guide

Nokia Developer Portal for information about FTP mediation policy creation using API.

—

Cards and MDAs provisioning

ICM process in the NSP Device Management Guide for more information about using the Device Configuration views, and the other procedures in the NSP Device Management Guide for further detail.

See the NSP ICM Intent Type Catalog for information about this and other device configuration intent types developed by Nokia.

The intent type required for this configuration is icm-equipment-card-mda.

Connectors and Ports provisioning

The intent types required for this configuration are:

  • icm-equipment-port-connector

  • icm-equipment-port-ethernet

OSPF/ISIS

CLI Reference Guides for SR OS

—

LDPs, MPLS and RSVP configuration

CLI Reference Guides for SR OS

For LDP to be operational, the IPv4 and IPv6 bindings must be configured manually using CLI.

Interfaces Provisioning

How do I create a physical configuration deployment? in the NSP Device Management Guide.

The intent type required for this configuration is icm-router-network-interface

PCEP configuration

CLI Reference Guides for VSR-NRC

Most of the connections required for PCEP are established during previous configuration steps.

For this use case, the VSR-NRC component must be correctly integrated with the setup. PCEP sessions between the routers in the network and the VSR-NRC component (VSR-I NE) must be established. 

Optional

Optional items to include in your NSP deployment

Pathway for NSP system installation in the NSP Installation and Upgrade Guide

SR OS Router Configuration Guide for information about configuring Cflowd sampling on NEs.

  • Optional feature packs:

    • An AuxDB

    • serviceActivationAndConfiguration-intentBasedServiceFulfillment 

To force incoming traffic to use a particular LSP path, the easiest way is to configure a service between the edge routers. The service can be provisioned using CLI, but if the user wishes to use NSP, the serviceActivationAndConfiguration-intentBasedServiceFulfillment feature pack must be included. The service fulfillment artifact bundle is also required for this option.

If you choose to provision a service via NSP, a customer will also have to be provisioned via NSP's Device Management, Device Configuration views. 

  • A Flow Collector (FC) and Flow Collector Controller (FCC)

    FC and FCC components are required if the older generation of 7250 IXRs are part of the Nokia SR OS network. For such devices, there is no gNMI telemetry support for collecting LSP/path statistics. Therefore, Cflowd sampling was used to collect interface/MPLS statistics.

    Cflowd sampling can be used for other NE types if preferred, however, this document assumes that gNMI telemetry will be used whenever possible.

    Older generation 7250 IXRs:

    • 7250 IXR-S 

    • 7250 IXR-6 

    • 7250 IXR-R6 

    • 7250 IXR-10 

    • 7250 IXR-e 

  • An NFM-P instance

    NFM-P is required if classically managed NEs are part of the network

Download the following artifact bundle from the NSP software delivery site:

  • NSP product artifact bundle for Service Fulfillment

How do I install an artifact bundle? in the NSP Network Automation Guide

—

BGP/EVPN

How do I create a logical configuration deployment? in the NSP Device Management Guide.

The intent type required for this configuration is icm-router-bgp_group

Segment Routing

CLI Reference Guides for SR OS

The examples in this use case use RSVP/MPLS LSPs. If SR-TE LSPs are used instead, segment routing configuration is mandatory.

Scheduler QoS Policies

How do I create a logical configuration deployment? in the NSP Device Management Guide.

The intent types required for this configuration are:

  • icm-qos-schedulerpolicy-srqos

  • icm-qos-network-srqos

  • icm-qos-sapingress-srqos

  • icm-qos-sapegress-srqos

Network QoS Policies configuration

LAGs and MC-LAG creation

How do I create a logical configuration deployment? in the NSP Device Management Guide.

The intent types required for this configuration are:

  • icm-logical-lag-access

  • icm-logical-mc_lag-access