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:
-
Remove the leading # character from each parameter that you need to configure.
-
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-1, 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-1: 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 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 | ||
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 |