NSP RPM-based configuration file

Using the config.yml file

The config.yml file specifies the deployment criteria for RPM-based NSP components. Based on your requirements, you must edit the config.yml sections that apply to your deployment; an example configuration file is in the following directory:

NSP_installer_directory/NSD_NRC_R_r/examples

Note: It is strongly recommended that you use a modified copy of the example configuration file for your deployment.

Configuring parameters

To enable a section and the required parameters in the section, you must do the following:

1. Remove the leading # character from the section label.

2. Remove the leading # character from each parameter that you need to configure.

3. Enter the required value for each parameter, as described in the comment lines above the section label.

Note: It is recommended that you remove parameter lines that you do not require from the configuration file. Also, failing to provide a parameter value may have undesired consequences.

Note: In the event of a discrepancy between information in a configuration file and the NSP documentation, or if the documentation fails to adequately describe a specific configuration, the configuration file information is to be followed and considered correct. Also, the NSP Release Notice describes configuration updates and corrections that are not captured in the core documentation.

RPM-based deployment parameters

Table 13-2, config.yml parameters lists and describes the config.yml file sections and parameters that are specific to the RPM-based components of an NSP deployment.

Table 13-2: config.yml parameters

Section and parameters		Description
nfmp — NFM-P integration parameters
primary_ip		IP address of primary NFM-P main server Default: none
standby_ip		IP address of standby NFM-P main server Default: none
tls_enabled		Whether TLS communication with NFM-P is enabled You can set the parameter to true only when the NSP system is not integrated with the WS-NOC. Default: true
cert_provided		Whether custom TLS certificate is to be used for communication with NFM-P Default: false
resync_augmentation_scripts_path		Path to the scripts that augment NFM-P re-synchronization in IPRC server
nfmt — WS-NOC integration parameters
primary_ip		IP address of primary WS-NOC server Default: none
standby_ip		IP address of standby WS-NOC server Default: none
cert_provided		Whether custom TLS certificate is to be used for communication with WS-NOC Default: false
nrct — WS-RC integration parameters
primary_ip		IP address of primary WS-RC server Default: none
standby_ip		IP address of standby WS-RC server Default: none
remote		Specifies that the WS-RC is in a remote authentication space, relative to the CDRC server
username		User name to be used when authenticating to an WS-RC in a remote authentication space
password		Password to be used with the supplied user name
sros — required when integrating NSP with an SROS VM
enabled		Whether path computation using SROS VM is enabled Default: false Note: When set to true, the SROS block of the hosts file must be configured.
openflow		Whether OpenFlow is enabled Default: false
pcep		Whether PCEP is enabled Default: false
bgpls		Whether BGP LS is enabled Default: false
vms	ip	IP address of SROS VM
	router_id	SROS VM router ID
	v_id	SROS VM virtual ID; must be an integer value NOTE: The value must be the same for redundant VMs.
	openflow	Whether OpenFlow is enabled Default: false
	pcep	Whether PCEP is enabled Default: false
	bgpls	Whether BGP LS is enabled Default: false
ean — EAN customization parameters
max_subscribers		Maximum number of clients that can subscribe for EAN
remote_syslog_for_nsp_activity_logs — remote syslog server parameters
enabled		Whether NSP activity-log forwarding to a remote syslog server is enabled Default: false
remote_syslog_ip_address		Remote syslog server IP address
remote_syslog_port		Remote server TCP port
remote_syslog_ca_cert_path		Absolute local path of TLS certificate copied from remote server

Manual WS-NOC deployment

If the install parameter in the nfmt section of the configuration file is set to false, the NSP cannot integrate with the WS-NOC, and you must use the oms-server.conf file instead. The file is populated as follows:

oms {

    OMSServers=[ {

        id="WS-NOC_ID"

        OMSMain={

            host="primary_address"

            host2="standby_address"

            username="username"

            password="password"

        }

    } ]

    tls-enabled="value"

    tls-directory="TLS_dir"

}

where

WS-NOC is the unique WS-NOC system identifier

primary_address is the IP address of the standalone WS-NOC server, or the primary WS-NOC server in a redundant deployment

standby_address is the IP address of standby WS-NOC server in a redundant deployment

username is the username required for WS-NOC login

password is the password required for WS-NOC login

value specifies whether TLS is enabled on the WS-NOC, and is true or false

TLS_dir specifies the directory that contains the TLS certificates, if TLS is enabled