SD-WAN Nokia-Nuage Networks Collector Installation Guide

1. SSH into the SevOne NMS or the system on which the collector/flow augmenter needs to be deployed.
2. If the installation is on an NMS appliance, and docker is not enabled and/or started, execute the following commands.

   $ systemctl enable docker
   
   $ systemctl start docker

3. If the installation is on a non-NMS appliance, ensure that docker is enabled and started.

1. Using ssh, login to NMS appliance as root.

   $ ssh root@<NMS appliance>

   Example

   $ ssh root@10.128.10.226

2. Download the following (latest) files from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support for the latest files. You must place these files in /root directory of SevOne NMS appliance.
   1. sdwan-nuage-installation-v6.7.0-build.245233.tgz
   2. sdwan-nuage-installation-v6.7.0-build.245233.tgz.sha256.txt
   3. signature-tools-latest-version-build.<###>.tgz. For example, signature-tools-2.0.1-build.1.tgz
   4. signature-tools-latest-version-build.<###>.tgz.sha256.txt. For example, signature-tools-2.0.1-build.1.tgz.sha256.txt
3. Execute the following commands to verify the checksum of the code signing tool before extracting it.

   $ (cat $(ls -Art signature-tools-*.tgz.sha256.txt | \
   tail -n 1) | sha256sum --check)
   
   $ sudo tar xvfz $(ls -Art signature-tools-*.tgz | \
   tail -n 1) -C /

4. Extract the .tgz file.

   $ mkdir -p /opt/SevOne/upgrade/ansible/playbooks
   
   $ cp sdwan-nuage-installation-v6.7.0-build* /opt/SevOne/upgrade
   
   $ cd /opt/SevOne/upgrade && tar xvzf /opt/SevOne/upgrade/sdwan-nuage-installation*.tgz -C /opt/SevOne/upgrade/ansible/playbooks/

   Note: You will find sample_config.yaml file in /opt/SevOne/upgrade/ansible/playbooks/config directory.
5. Add a tenant by configuring sample_config.yaml file to create <tenant>_config.yaml file for each tenant created.
6. Make a directory and copy this config file to it.

   Example: Default path, /opt/nuage_ansible/config, for config files

   $ mkdir -p /opt/nuage_ansible/config
   $ cp -f /opt/SevOne/upgrade/ansible/playbooks/config/* /opt/nuage_ansible/config

7. You are now ready to install the Nuage Networks Collector. Run the setup script.

   Run the setup script

   Example: Default config directory

   $ cd /opt/SevOne/upgrade/ansible/playbooks/
   
   $ sh setup_ssu.sh

   Example: The command returns the following

   ******************************************************************************
   
   SEVONE GUI INSTALLER
   
   Please open https://10.128.10.226:3000 in your web browser to access the GUI Installer.
   
   Your credentials are:
   - Username: admin
   - Password: DNH{wR|q-k
   
   If you ever lose your credentials, they are stored in:
   /etc/sevone-guii/creds
   
   ******************************************************************************

   You are now ready to install using the Graphical User Interface Installer.

8. Using a web browser of your choice, enter the URL the setup script has returned. For example, https://10.128.10.226:3000.
   
   Note: You will also need the credentials (Username and Password) that the setup script returns. These credentials are also stored in /etc/sevone-guii/creds file.

   Example

   $ 
   cat /etc/sevone-guii/creds | jq
   {
   "password": "DNH{wR|q-k",
   "tokenSecret": "BIRfudiUiILoISEAfKHOITmlkbNHZmXg",
   "username": "admin"
   }

9. Click Update Cluster to install SD-WAN Nuage Collector.
10. Enter the credentials returned to perform the Self-Service Upgrade. For example, Username: admin and Password: DNH{wR|q-k
    
    Note: To use the Graphical User Interface installer in dark theme, click next to SevOne logo.
    For help on what each upgrade step does, click button in the upper-right corner.
    Important: IMPORTANT
    All the screenshots below are based on the example being used to write this document. Your total number of tasks passed (ok) , skipped, failed, ignored, unreachable, or unexecuted will vary based on your setup. The tasks failed must be addressed as ansible has not ignored them.
11. Enter username & password and then click Login. The graphical user interface installer checks the Current Version and allows you to proceed with the installation.
    
    Important: Example
    Current Version is on SD-WAN Nuage Collector 6.7.0+239379.
    
    You can proceed with redeploy/install.
    Important: During the Self-Service Upgrade, if you experience network connectivity issue or the upgrade has been halted for any reason, the self-service upgrade will resume from the step where it left off after the issue is resolved. However, if you are at the Deploy step and the self-service upgrade has been halted for any reason, self-service upgrade will show a message requesting you to contact IBM SevOne Support.
    
    To resume with the Self-Service Upgrade, using a web browser of your choice, re-enter the URL the setup script has returned. For example, https://10.128.10.226:3000.
12. Click the Continue to Configure button to configure SD-WAN Nokia Nuage solution.
    
    1. From Configuration drop-down, choose a configuration file from the list. The default configuration file is solutions-sdwan-nuage_custom_guii.yaml. Provide inputs for all mandatory fields.
       Important: Once you provide inputs for all mandatory fields, error messages will no longer appear.
       
    2. Configure
       • NMS/PAS IP - The IP address of the SevOne NMS Appliance.
       • NMS/PAS GUI Username - GUI username of the NMS / PAS.
       • NMS/PAS GUI password - GUI password of the NMS / PAS.
       • DNC/NMS IP address - The IP address of the NMS / DNC, where the augmented flow must be sent.
       • DNC/NMS Flows Port - Port of DNC, where the flows are sent.
       • VSD Host IP or DNS name - The IP address or DNC of targeted Virtualized Services Directory (VSD).
       • VSD username - The username for the VSD.
       • VSD password - The password for the VSD.
       • Nuage organization - The organization for the VSD.
       • Elasticsearch host IP - The elasticsearch host IP.
       • Elasticsearch host Port - The elasticsearch host port.
       • Collect Data from ElasticSearch - Collect data from elasticsearch.
       • ActiveMQ username - The username of the Messaging Service (ActiveMQ) broker. The format must be %40. For example, sevone%40csp, where sevone is the username and csp is the organization.
       • ActiveMQ password - The password of the Messaging Service (ActiveMQ) broker.
       • ActiveMQ Topic name - Topic to subscribe to the Messaging Service (ActiveMQ) broker. The format must be topic/<topic_name>. For example, topic/CNAAlarms, where CNAAlarms is the topic name.
       • ActiveMQ Port - Port of the Messaging Service (ActiveMQ) broker. The default port is 5672.
       • ActiveMQ IP - The IP address of the Messaging Service (ActiveMQ) broker.
       • Collector installation on remote/local - The mode of installation for the collector. local installs the collector on the same NMS where the script is running.
       • Collector IP - The IP address of the Virtual Machine where collector needs to be installed.
       • Collector ssh username - The SSH username of the VM for collector installation.
       • Collector ssh password - The SSH password of the VM for collector installation.
       • Upgrade Collector - Flag to upgrade the collector.
       • Collector Log Level - Defines the log-level for the collector. Value can be info or debug or error. The default value is info.
       • Enable flow data collection - Flag to enable flow data collection.
       • Flow Augmenter installation on remote/local - The mode of installation for Flow Augmenter.
       • List of Flow VMs - List of Details of VMs where Flow Augmenter needs to be installed.

       • Augmenter Log Level - Defines the log-level for the augmenter. Value can be info or debug or error. The default value is info.

       • Upgrade Flow Augmenter - Flag to upgrade the augmenter.
       • MSP Name - The Managed Service Provider name to which the configured tenant level Orchestrator belongs to. The MSP name can be of your choice.
       • Tenant Name - The tenant name is the Enterprise name that matches with the tenant/enterprise name available in VSD, for the data that needs to be collected.
       • Self monitoring device name - Device name for self monitoring of the Nuage collector.
       • Distribute data across all NMS peers - The flag if set to true, will distribute the devices across the cluster on its own on all the peers. However, if set to false, it will send data to local peer or given list of peers (if provided). The default value is false.
       • Distribution Peers list - The flag expects a list of peers to distribute data. This flag is ignored if Distribute data across all NMS peers flag is true. It is empty by default.
       • q<#>_name- Allows you to change the names of the interface queues as per the user requirements. During installation, if the interface queue names are changed, the same names must be retained during the upgrade or else, new interface queue objects will be created with the new names set during the upgrade. The default interface queue names are q1, q2, q3, q4, and q10.
       • Nuage API version - API version that is compatible with VSD.
       • Create custom site group using device metadata - Flag for creating a custom site group using device metadata. If two devices have the same name (matching of name is case insensitive), it will create the site with the name from the REST-API response. The default value is false.
       • Unique device hostname per MSP - When all the device hostnames are unique across all the tenants, set it to true. This flag is to avoid suffixing the tenant name to the device name. The default value is false.
       • Enable FlowView creation - If the default Nuage Flow View is created at the time of deployment, set the value to true.
       • Update VSD Lat Long value - For latitude, set the flag to the default value, true. Longitude value is updated in device/site metadata by the collector. If an update is required by some external system in NMS, set the flag to false.
       • Enable Self Monitoring - Flag to enable self monitoring. It will create Objects and Indicators for a selfmon device and is set to true. The default value is false.
       • Enable Flow object mapper - Flag to run the flow object mapper. It maps the flow interfaces to the interface objects. The default value is true.
       • Create Devices - Flag to determine devices to be created. If set to true, it will create all devices. If set to false, devices with no data will not be created. The default value is true.
       • Enable Tunnel stat Runner - Flag to run the tunnel stats runner in a separate container for better performance. The default value is true.
       • Enable Interface stat Runner - Flag to run the interface stats runner in a separate container for better performance. The default value is true.

       • Enable Device Summary Runner - Flag to run the device summary runner in a separate container for better performance. The default value is true.

       • Enable Interface Queue stat Runner - Flag to run the queue interfaces runner in a separate container for better performance. The default value is true.
       • Enable Events Runner - Flag to run the events runner in a separate container for better performance. The default value is true.
       • Enable Alarms Runner - Flag to run the alarms runner in a separate container for better performance. The default value is true.
       • Enable vport Poller - Flag to run the vport & aggregation runner in a separate container for better performance. It creates raw vport objects. The default value is true.
       • Enable Lan Aggregation Poller - Flag to run the vport & aggregation runner in a separate container for better performance. It creates the aggregated vport objects at the subnet and domain level. The default value is true.
       • Enable APM probe stat Runner - Flag to run the APM probe runner in a separate container for better performance. The default value is true.
       • Enable SLA stat Runner - Flag to run the SLA runner in a separate container for better performance. The default value is true.
       • Enable Tunnel description Runner - Flag to run the Tunnel description runner in a separate container for better performance.
       • Enable Flow Interface speed runner - Flag to run the flow interface speed runner. It updates the interface speed for the flow interfaces. The default value is true.
       • Enable flow interface rename runner - Flag to run the flow interface rename runner. It renames the flow interfaces to show the interface name instead of ifIndex. The default value is true.
       • Enable Octet Indicators - Flag to enable octet indicators.
       • Enable Packet Indicators - Flag to enable packet indicatos.
       • Enable LTE Interface Poller - Flag to enable / disable LTE data collection. The default value is true.
       • Enable Device Description Runner - Flag to run the device description runner in a separate container for better performance. The default value is true.
       • SevOne API read Timeout - The read timeout for the SevOne REST API connection. The default value is 30 seconds.
       • Collection Offset - Represents the number of seconds the collector runs in delay from the current time. Set to 0 for regular poll interval collection. Provide the number of seconds for the offset from the current time. For example, if the value is set to 300 (in seconds), the collector collects the data until 5 minutes before the collector's run time. The default value is 0.
       • Create Devices Runner Interval - Interval set in minutes to run the runner. Recommended value is 30 minutes.
       • Tunnel stat Runner Interval - Interval set in minutes to run the tunnel stat runner. Recommended value is 5 minutes.
       • Interface stat Runner Interval - Interval set in minutes to run the interface stat runner. Recommended value is 5 minutes.
       • Device Summary Runner Interval - Interval set in minutes to run the device summary runner. Recommended value is 5 minutes.
       • Interface Queue stat Runner Interval - Interval set in minutes to run the interface queue stat runner. Recommended value is 5 minutes.
       • Events Runner Interval - Interval set in minutes to run the events runner. Recommended value is 5 minutes.
       • vport & aggregation Runner Interval - Interval set in minutes to run the vport & aggregation runner. Recommended value is 5 minutes.
       • APM probe stat Runner Interval - Interval set in minutes to run the APM probe runner. Recommended value is 5 minutes.
       • SLA stat Runner Interval - Interval set in minutes to run the SLA runner. Recommended value is 5 minutes.
       • Custom Site Group Runner Interval - The interval set in hours for the custom site group creation. Recommended value is 1 hour.
       • Device Description Runner Interval - The interval set in minutes to update the device description to apply the device group rules on it. Recommended value is 15 minutes.
       • Installer Interval - Interval value of installer. Recommended value is 24 hours.
       • Flow Object Mapper Interval - The interval set in hours for the flow object mapper Recommended value is 24 hour.
       • device_summary_runner_aggregation_interval - Aggregation interval set in minutes to run the device summary runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • interface_stat_runner_aggregation_interval- Aggregation interval set in minutes to run the interface stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • interface_queue_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the interface queue stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • tunnel_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the tunnel stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • lan_aggregation_and_vport_poller_aggregation_interval - Aggregation interval set in minutes to run the vport & lan aggregation runner. Only aggregated data is pushed. Recommended value is 5 minutes. If the interval value is set to 0 then it will not push any data.
       • apm_probe_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the APM probe stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • Redis Password - The install script sets the password for the redis.
       • Fetch Tunnel Page Size - Size of the page to fetch the data from elastic search index for probes. The default value 5000.
       • fetch_tunnel_workers - Number of parallel probe fetchers per tunnel runner instance. The default value is 4.
       • send_tunnel_workers - Number of parallel tunnel data senders towards NMS. The default value is 4.
       • ES Session Timeout - Elastic search session timeout value. The default value is 30 seconds.
       • tunnel_count_bucket_size - Tunnel count bucket size for sending towards NMS per device. The default value is 700.
       • Filtered Indicator List - Comma separated list of indicators that will be filtered/enabled.
       • Enable Dry run - Flag to enable/disable the dry-run mode. The default value is false.
       • Dry run Interval - Duration for running Nokia collector in dry-run mode. The default value is 0 seconds.
       • Total Tunnel Runner - Flag to set the total tunnel runner instances required for fetching data points. Recommended value is 1 instance. For example, 1 tunnel instance fetches around 500k probe data points. Based on the incoming rate, increase the instance count. NOTE: Please do not change the default instant count value if you want to use the aggregation for the tunnel data.
       • Total APM probe Runner - Flag to set the total APM probe runner instances required for fetching data points. Recommended value is 1 instance.
       • SLA Alert Cleanup Interval - Time to keep the violation alerts in NMS as active. Violation alerts get deleted when violation alert timestamp and sla_alert_cleanup_interval are <= current timestamp. The default value is 300 seconds.
       • SLA fetch pagesize - Flag to configure the SLA fetch page size. The default value is 100.
       • Tunnel Description Runner Interval - The interval set in hours to update the tunnel description when site names are changed by custom site group runner. Recommended value is 1 hour.
       • LTE Interface Poller Interval - Interval set in minutes to for LTE data collection. The default value is 5 minutes.
       • LTE Interface Poller Page Size - Flag to configure elastic search page size for LTE data collection. The default value is 5000.
       • LTE interface runner Interval - Interval set in hours to run the LTE interface runner. The default value is 24 hours. It creates object groups, rules, and object metadata. LTE interface runner is enabled / disabled based on the Enable LTE Interface Poller flag.
       • LTE interface runner NMS buffer size - Flag for updating the buffer size for object metadata in bulk. The default value is 500.
       • Enable IKE tunnel Poller - Flag to enable / disable data collection for IKE tunnel objects. The default value is true.
       • IKE Tunnel Poller Interval - Interval set in minutes to run the IKE tunnel runner. The default value is 5 minutes.
       • Enable IKE Probe Poller - Flag to enable / disable data collection for IKE probe objects. The default value is true.
       • IKE Probe Poller Interval - Interval set in minutes to run the IKE probe runner. The default value is 5 minutes.
       • IKE Tunnel Poller page size - Flag to configure elastic search page size for the data collection of IKE tunnel objects. The default value is 5000.
       • IKE Probe Poller page size - Flag to configure elastic search page size for the data collection of IKE probe objects. The default value is 5000.
       • IKE Object Runner NMS buffer size - Flag for updating the buffer size for object metadata related to IKE tunnels and probes in bulk. The default value is 500.
       • IKE Object Group update interval - Interval set in hours to update the object groups related to IKE tunnel and IKE probe. The default value is 24 hours. The value must be set only when Enable IKE tunnel Poller and Enable IKE Probe Poller are set to true.
       • template_send_frequency - The frequency at which the IPFIX data template is sent at DNC.
       • flominer_receiver_read_buffer - The flowminer receiver buffer size.
       • flow_collection_interval - The interval in seconds at which flow collection must happen. The default value is 300 seconds.
       • flow_fetch_workers - The number of parallel fetching threads the elastic search receives to fetch the flows. The default value is 2.
       • flow_send_workers - The number of parallel processing threads that process the flow data points and send to rabbitmq for decoder. The default value is 4.
       • flow_fetch_pagesize - The page size to fetch by the elasticsearch query for the flows. The default value is 5000.
13. Click Save. Configuration is saved in /opt/nuage_ansible/config/solutions-sdwan-nuage_custom_guii.yaml.
    Important: Once the configuration is saved, click Continue button to Deploy.
14. Click Continue button to Deploy.
    
15. Click the Run Deploy button to run the deployment. This can take a few minutes to run.
    
    Note: To view the logs for a task, click for the task you need the details for. The pop-up has Copy to clipboard button which allows you to copy all the contents in the pop-up and paste it into a file.

    SD-WAN Nuage Collector installation has now completed.

    Note: The task list can be long. Search tasks capability is available to search for text you are looking for in the task list.
16. Click the Continue button.
    

Execute the following steps to upgrade SD-WAN Nokia-Nuage Collector using Graphical User Interface (GUI).

1. Using ssh, login to NMS appliance as root.

   $ ssh root@<NMS appliance>

   Example: Currently on SD-WAN Nokia-Nuage Collector 6.6 and to be upgraded to SD-WAN Nokia-Nuage Collector 6.7

   $ ssh root@10.128.9.13

2. Make a directory.

   $ mkdir -p /opt/SevOne/upgrade/ansible/playbooks

3. Download the following (latest) files from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support for the latest files. You must place these files in /root directory.
   1. sdwan-nuage-installation-v6.7.0-build.245233.tgz
   2. sdwan-nuage-installation-v6.7.0-build.245233.tgz.sha256.txt
   3. signature-tools-latest-version-build.<###>.tgz. For example, signature-tools-2.0.1-build.1.tgz
   4. signature-tools-latest-version-build.<###>.tgz.sha256.txt. For example, signature-tools-2.0.1-build.1.tgz.sha256.txt
4. Execute the following commands to verify the checksum of the code signing tool before extracting it.

   $ (cat $(ls -Art signature-tools-*.tgz.sha256.txt | \
   tail -n 1) | sha256sum --check)
   
   $ sudo tar xvfz $(ls -Art signature-tools-*.tgz | \
   tail -n 1) -C /

5. Extract the .tgz file.

   $ cp sdwan-nuage-installation-v6.7.0-build* /opt/SevOne/upgrade
   
   $ cd /opt/SevOne/upgrade && tar xvzf /opt/SevOne/upgrade/sdwan-nuage-installation*.tgz -C /opt/SevOne/upgrade/ansible/playbooks/

6. Change directory to /opt/SevOne/upgrade/ansible/playbooks/.

   $ cd /opt/SevOne/upgrade/ansible/playbooks/

7. Run the migration script to move the existing configuration from the main.yml file to the tenant configuration file.
   Important: You must perform this step when upgrading from SD-WAN <=6.5 to SD-WAN 6.7.

   $ ./migrate_config -src /root/<Previous Installation Folder Name>/nuage/defaults/main.yml -dest /opt/nuage_ansible/config/<tenant name.yaml>

   Example

   $ ./migrate_config -src /root/sdwan-nuage-installation-6.5.0/nuage/defaults/main.yml -dest /opt/nuage_ansible/config/enterprise_sevone_config.yaml

   Important: It is important to have a single .yaml file in /opt/nuage_ansible/config directory. If multiple files are present, the installer will interpret it as a multi-tenant deployment. In such cases, it is recommended to use the CLI method for upgrading the collector.
8. Install the GUI.

   $ sh setup_ssu.sh

   Example: The command returns the following

   ******************************************************************************
   
   SEVONE GUI INSTALLER
   
   Please open https://10.128.9.13:3000 in your web browser to access the GUI Installer.
   
   Your credentials are:
   - Username: admin
   - Password: dvU;Gwhoja
   
   If you ever lose your credentials, they are stored in:
   /etc/sevone-guii/creds
   
   ******************************************************************************

   You are now ready to install using the Graphical User Interface Installer .

9. Using a web browser of your choice, enter the URL the setup script has returned. For example, https://10.128.9.13:3000.
   
   Note: You will also need the credentials (Username and Password) that the setup script returns. These credentials are also stored in /etc/sevone-guii/creds file.

   $ cat /etc/sevone-guii/creds | jq   
   
   {
       "password": "dvU;Gwhoja",
       "tokenSecret": "HPoqiCgpbaHOBkCwtcTooDphrrpPkSIX",
       "username": "admin"
   }

10. Click Update Cluster to update SD-WAN Nuage Collector. For example, upgrade from SD-WAN Nuage Collector 6.6.0+234822 to SD-WAN Nuage Collector 6.7.0+243695.
11. Enter the credentials returned to perform the Self-Service Upgrade. For example, Username: admin and Password: dvU;Gwhoja
    
    Note: To use the Graphical User Interface installer in dark theme, click next to SevOne.
    
    For help on what each upgrade step does, click button in the upper-right corner.
    Important: All the screenshots below are based on the example being used to write this document. Your total number of tasks passed (ok) , skipped , failed , ignored , unreachable , or unexecuted will vary based on your setup. The tasks failed must be addressed as ansible has not ignored them.
12. The graphical user interface installer checks the Current Version and the Upgrade Available version. If the current version is older than the upgrade version available, you are now ready to continue to Configure.
    
    Important: EXAMPLE
    Current Version is on SD-WAN Nuage Collector 6.6.0+234822.
    Upgrade Available version is SD-WAN Nuage Collector 6.7.0+243695.
    Important: During the Self-Service Upgrade, if you experience network connectivity issue or the upgrade has been halted for any reason, the self-service upgrade will resume from the step where it left off after the issue is resolved. However, if you are at the Upgrade step and the self-service upgrade has been halted for any reason, self-service upgrade will show a message requesting you to contact IBM SevOne Support.
    
    To resume with the Self-Service Upgrade, using a web browser of your choice, re-enter the URL the setup script has returned. For example, https://10.128.9.13:3000.
13. Click the Continue to Configure button to configure SD-WAN Nuage chart values, if required.
    Important: If you do not want to configure the chart values, click Continue button to start the upgrade.
    
    1. From Configuration drop-down, choose a configuration file from the list. For example, the primary configuration file is solutions-sdwan-nuage_custom_guii.yaml. If SD-WAN Nuage collector has already been configured, you can select that configuration from the drop-down list to edit it. If multiple configuration files are present for the same tenant, the files will be applied in the alphabetical order.
       Important: Please ignore warnings related to the runner intervals. These configurations will be automatically migrated to the cron configuration from existing cron jobs.
       
    2. Configure
       • NMS/PAS IP - The IP address of the SevOne NMS Appliance.
       • NMS/PAS GUI Username - GUI username of the NMS / PAS.
       • NMS/PAS GUI password - GUI password of the NMS / PAS.
       • DNC/NMS IP address - The IP address of the NMS / DNC, where the augmented flow must be sent.
       • DNC/NMS Flows Port - Port of DNC, where the flows are sent.
       • VSD Host IP or DNS name - The IP address or DNC of targeted Virtualized Services Directory (VSD).
       • VSD username - The username for the VSD.
       • VSD password - The password for the VSD.
       • Nuage organization - The organization for the VSD.
       • Elasticsearch host IP - The elasticsearch host IP.
       • Elasticsearch host Port - The elasticsearch host port.
       • Collect Data from ElasticSearch - Collect data from elasticsearch.
       • ActiveMQ username - The username of the Messaging Service (ActiveMQ) broker. The format must be %40. For example, sevone%40csp, where sevone is the username and csp is the organization.
       • ActiveMQ password - The password of the Messaging Service (ActiveMQ) broker.

       • ActiveMQ Topic name - Topic to subscribe to the Messaging Service (ActiveMQ) broker. The format must be topic/<topic_name>. For example, topic/CNAAlarms, where CNAAlarms is the topic name.

       • ActiveMQ Port - Port of the Messaging Service (ActiveMQ) broker. The default port is 5672.
       • ActiveMQ IP - The IP address of the Messaging Service (ActiveMQ) broker.
       • Collector installation on remote/local - The mode of installation for the collector. local installs the collector on the same NMS where the script is running.
       • Collector IP - The IP address of the Virtual Machine where collector needs to be installed.
       • Collector ssh username - The SSH username of the VM for collector installation.
       • Collector ssh password - The SSH password of the VM for collector installation.
       • Upgrade Collector - Flag to upgrade the collector.
       • Collector Log Level - Defines the log-level for the collector. Value can be info or debug or error. The default value is info.
       • Enable flow data collection - Flag to enable flow data collection.
       • Flow Augmenter installation on remote/local - The mode of installation for Flow Augmenter.
       • List of Flow VMs - List of Details of VMs where Flow Augmenter needs to be installed.
       • Augmenter Log Level - Defines the log-level for the augmenter. Value can be info or debug or error. The default value is info.
       • Upgrade Flow Augmenter - Flag to upgrade the augmenter.
       • MSP Name - The Managed Service Provider name to which the configured tenant level Orchestrator belongs to. The MSP name can be of your choice.
       • Tenant Name - The tenant name is the Enterprise name that matches with the tenant/enterprise name available in VSD, for the data that needs to be collected.
       • Self monitoring device name - Device name for self monitoring of the Nuage collector.
       • Distribute data across all NMS peers - The flag if set to true, will distribute the devices across the cluster on its own on all the peers. However, if set to false, it will send data to local peer or given list of peers (if provided). The default value is false.
       • Distribution Peers list - The flag expects a list of peers to distribute data. This flag is ignored if Distribute data across all NMS peers flag is true. It is empty by default.
       • q<#>_name- Allows you to change the names of the interface queues as per the user requirements. During installation, if the interface queue names are changed, the same names must be retained during the upgrade or else, new interface queue objects will be created with the new names set during the upgrade. The default interface queue names are q1, q2, q3, q4, and q10.
       • Nuage API version - API version that is compatible with VSD.
       • Create custom site group using device metadata - Flag for creating a custom site group using device metadata. If two devices have the same name (matching of name is case insensitive), it will create the site with the name from the REST-API response. The default value is false.
       • Unique device hostname per MSP - When all the device hostnames are unique across all the tenants, set it to true. This flag is to avoid suffixing the tenant name to the device name. The default value is false.
       • Enable FlowView creation - If the default Nuage Flow View is created at the time of deployment, set the value to true.
       • Update VSD Lat Long value - For latitude, set the flag to the default value, true. Longitude value is updated in device/site metadata by the collector. If an update is required by some external system in NMS, set the flag to false.
       • Enable Self Monitoring - Flag to enable self monitoring. It will create Objects and Indicators for a selfmon device and is set to true. The default value is false.
       • Enable Flow object mapper - Flag to run the flow object mapper. It maps the flow interfaces to the interface objects. The default value is true.
       • Create Devices - Flag to determine devices to be created. If set to true, it will create all devices. If set to false, devices with no data will not be created. The default value is true.
       • Enable Tunnel stat Runner - Flag to run the tunnel stats runner in a separate container for better performance. The default value is true.
       • Enable Interface stat Runner - Flag to run the interface stats runner in a separate container for better performance. The default value is true.
       • Enable Device Summary Runner - Flag to run the device summary runner in a separate container for better performance. The default value is true.
       • Enable Interface Queue stat Runner - Flag to run the queue interfaces runner in a separate container for better performance. The default value is true.
       • Enable Events Runner - Flag to run the events runner in a separate container for better performance. The default value is true.
       • Enable Alarms Runner - Flag to run the alarms runner in a separate container for better performance. The default value is true.
       • Enable vport Poller - Flag to run the vport & aggregation runner in a separate container for better performance. It creates raw vport objects. The default value is true.
       • Enable Lan Aggregation Poller - Flag to run the vport & aggregation runner in a separate container for better performance. It creates the aggregated vport objects at the subnet and domain level. The default value is true.
       • Enable APM probe stat Runner - Flag to run the APM probe runner in a separate container for better performance. The default value is true.
       • Enable SLA stat Runner - Flag to run the SLA runner in a separate container for better performance. The default value is true.
       • Enable Tunnel description Runner - Flag to run the Tunnel description runner in a separate container for better performance.
       • Enable Flow Interface speed runner - Flag to run the flow interface speed runner. It updates the interface speed for the flow interfaces. The default value is true.
       • Enable flow interface rename runner - Flag to run the flow interface rename runner. It renames the flow interfaces to show the interface name instead of ifIndex. The default value is true.
       • Enable Octet Indicators - Flag to enable octet indicators.
       • Enable Packet Indicators - Flag to enable packet indicatos.
       • Enable LTE Interface Poller - Flag to enable / disable LTE data collection. The default value is true.
       • Enable Device Description Runner - Flag to run the device description runner in a separate container for better performance. The default value is true.
       • SevOne API read Timeout - The read timeout for the SevOne REST API connection. The default value is 30 seconds.
       • Collection Offset - Represents the number of seconds the collector runs in delay from the current time. Set to 0 for regular poll interval collection. Provide the number of seconds for the offset from the current time. For example, if the value is set to 300 (in seconds), the collector collects the data until 5 minutes before the collector's run time. The default value is 0.
       • Create Devices Runner Interval - Interval set in minutes to run the runner. Recommended value is 30 minutes.
       • Tunnel stat Runner Interval - Interval set in minutes to run the tunnel stat runner. Recommended value is 5 minutes.
       • Interface stat Runner Interval - Interval set in minutes to run the interface stat runner. Recommended value is 5 minutes.
       • Device Summary Runner Interval - Interval set in minutes to run the device summary runner. Recommended value is 5 minutes.
       • Interface Queue stat Runner Interval - Interval set in minutes to run the interface queue stat runner. Recommended value is 5 minutes.
       • Events Runner Interval - Interval set in minutes to run the events runner. Recommended value is 5 minutes.
       • vport & aggregation Runner Interval - Interval set in minutes to run the vport & aggregation runner. Recommended value is 5 minutes.
       • APM probe stat Runner Interval - Interval set in minutes to run the APM probe runner. Recommended value is 5 minutes.
       • SLA stat Runner Interval - Interval set in minutes to run the SLA runner. Recommended value is 5 minutes.
       • Custom Site Group Runner Interval - The interval set in hours for the custom site group creation. Recommended value is 1 hour.
       • Device Description Runner Interval - The interval set in minutes to update the device description to apply the device group rules on it. Recommended value is 15 minutes.
       • Installer Interval - Interval value of installer. Recommended value is 24 hours.
       • Flow Object Mapper Interval - The interval set in hours for the flow object mapper Recommended value is 24 hour.
       • device_summary_runner_aggregation_interval - Aggregation interval set in minutes to run the device summary runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • interface_stat_runner_aggregation_interval- Aggregation interval set in minutes to run the interface stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • interface_queue_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the interface queue stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • tunnel_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the tunnel stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • lan_aggregation_and_vport_poller_aggregation_interval - Aggregation interval set in minutes to run the vport & lan aggregation runner. Only aggregated data is pushed. Recommended value is 5 minutes. If the interval value is set to 0 then it will not push any data.
       • apm_probe_stat_runner_aggregation_interval - Aggregation interval set in minutes to run the APM probe stat runner. Recommended value is 5 minutes. If the interval value is set to 0 then it will push non-aggregated data.
       • Redis Password - The install script sets the password for the redis.
       • Redis Port - Default Redis port is port 6381.
       • Fetch Tunnel Page Size - Size of the page to fetch the data from elastic search index for probes. The default value 5000.
       • fetch_tunnel_workers - Number of parallel probe fetchers per tunnel runner instance. The default value is 4.
       • send_tunnel_workers - Number of parallel tunnel data senders towards NMS. The default value is 4.
       • ES Session Timeout - Elastic search session timeout value. The default value is 30 seconds.
       • tunnel_count_bucket_size - Tunnel count bucket size for sending towards NMS per device. The default value is 700.
       • Filtered Indicator List - Comma separated list of indicators that will be filtered/enabled.
       • Enable Dry run - Flag to enable/disable the dry-run mode. The default value is false.
       • Dry run Interval - Duration for running Nokia collector in dry-run mode. The default value is 0 seconds.
       • Total Tunnel Runner - Flag to set the total tunnel runner instances required for fetching data points. Recommended value is 1 instance. For example, 1 tunnel instance fetches around 500k probe data points. Based on the incoming rate, increase the instance count. NOTE: Please do not change the default instant count value if you want to use the aggregation for the tunnel data.
       • Total APM probe Runner - Flag to set the total APM probe runner instances required for fetching data points. Recommended value is 1 instance.
       • SLA Alert Cleanup Interval - Time to keep the violation alerts in NMS as active. Violation alerts get deleted when violation alert timestamp and sla_alert_cleanup_interval are <= current timestamp. The default value is 300 seconds.
       • SLA fetch pagesize - Flag to configure the SLA fetch page size. The default value is 100.
       • Tunnel Description Runner Interval - The interval set in hours to update the tunnel description when site names are changed by custom site group runner. Recommended value is 1 hour.
       • LTE Interface Poller Interval - Interval set in minutes to for LTE data collection. The default value is 5 minutes.
       • LTE Interface Poller Page Size - Flag to configure elastic search page size for LTE data collection. The default value is 5000.
       • LTE interface runner Interval - Interval set in hours to run the LTE interface runner. The default value is 24 hours. It creates object groups, rules, and object metadata. LTE interface runner is enabled / disabled based on the Enable LTE Interface Poller flag.
       • LTE interface runner NMS buffer size - Flag for updating the buffer size for object metadata in bulk. The default value is 500.
       • Enable IKE tunnel Poller - Flag to enable / disable data collection for IKE tunnel objects. The default value is true.
       • IKE Tunnel Poller Interval - Interval set in minutes to run the IKE tunnel runner. The default value is 5 minutes.
       • Enable IKE Probe Poller - Flag to enable / disable data collection for IKE probe objects. The default value is true.
       • IKE Probe Poller Interval - Interval set in minutes to run the IKE probe runner. The default value is 5 minutes.
       • IKE Tunnel Poller page size - Flag to configure elastic search page size for the data collection of IKE tunnel objects. The default value is 5000.
       • IKE Probe Poller page size - Flag to configure elastic search page size for the data collection of IKE probe objects. The default value is 5000.
       • IKE Object Runner NMS buffer size - Flag for updating the buffer size for object metadata related to IKE tunnels and probes in bulk. The default value is 500.
       • IKE Object Group update interval - Interval set in hours to update the object groups related to IKE tunnel and IKE probe. The default value is 24 hours. The value must be set only when Enable IKE tunnel Poller and Enable IKE Probe Poller are set to true.
       • template_send_frequency - The frequency at which the IPFIX data template is sent at DNC.
       • flominer_receiver_read_buffer - The flowminer receiver buffer size.
       • flow_collection_interval - The interval in seconds at which flow collection must happen. The default value is 300 seconds.
       • flow_fetch_workers - The number of parallel fetching threads the elastic search receives to fetch the flows. The default value is 2.
       • flow_send_workers - The number of parallel processing threads that process the flow data points and send to rabbitmq for decoder. The default value is 4.
       • flow_fetch_pagesize - The page size to fetch by the elasticsearch query for the flows. The default value is 5000.
14. Click Save. Configuration is saved in /opt/nuage_ansible/config/enterprise_sevone_config.yaml.
    Important: Once the configuration is saved, click Continue button to Upgrade.
15. Click Continue button to Upgrade.
    
16. Click the Run Upgrade button to run the upgrade. This can take a few minutes to run.
    
    Note: To view the logs for a task, click for the task you need the details for. The pop-up has Copy to clipboard button which allows you to copy all the contents in the pop-up and paste it into a file.

    SD-WAN Nuage Collector upgrade has now completed.

    Note: The task list can be long. Search tasks capability is available to search for text you are looking for in the task list.
17. Click the Continue button.
    
    Important: This indicates that the upgrade has completed successfully.
    Important: If there was a kernel upgrade for this release, it is recommended to reboot the cluster after the deployment to install the right kernel version.
18. You may now click the link Click Here.
19. Link Click Here will launch SevOne Data Insight, where you can view the data collected by the collector.

Important: Example: Upgrade not required
If you are already on the version you are trying to upgrade to, you will get the You can proceed with redeploy/install message. This allows you to upgrade to a later version, if available.

1. Using ssh, login to NMS appliance as root.

   $ ssh root@<NMS appliance>

2. Backup the existing config files to use as a reference.

   $ export NUAGE_BACKUP_DATE=$(date +%s) && mkdir -p /opt/SevOne/upgrade/sdwan-nuage-config-backup-$NUAGE_BACKUP_DATE && cp /opt/nuage_ansible/config/* /opt/SevOne/upgrade/sdwan-nuage-config-backup-$NUAGE_BACKUP_DATE

3. Make a directory.

   $ mkdir -p /opt/SevOne/upgrade/ansible/playbooks

4. Download the following (latest) files from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support for the latest files. You must place these files in /root directory of SevOne NMS appliance.
   1. sdwan-nuage-installation-v6.7.0-build.245233.tgz
   2. sdwan-nuage-installation-v6.7.0-build.245233.tgz.sha256.txt
   3. signature-tools-latest-version-build.<###>.tgz. For example, signature-tools-2.0.1-build.1.tgz
   4. signature-tools-latest-version-build.<###>.tgz.sha256.txt. For example, signature-tools-2.0.1-build.1.tgz.sha256.txt
5. Execute the following commands to verify the checksum of the code signing tool before extracting it.

   $ (cat $(ls -Art signature-tools-*.tgz.sha256.txt | \
   tail -n 1) | sha256sum --check)
   
   $ sudo tar xvfz $(ls -Art signature-tools-*.tgz | \
   tail -n 1) -C /

6. Extract the .tar.gz file.

   $ cp sdwan-nuage-installation-v6.7.0-build* /opt/SevOne/upgrade
   
   $ cd /opt/SevOne/upgrade && tar xvzf /opt/SevOne/upgrade/sdwan-nuage-installation-*.tgz -C /opt/SevOne/upgrade/ansible/playbooks/

   Note: You will find sample_config.yaml file in /opt/SevOne/upgrade/ansible/playbooks/config directory.
7. Change directory to /opt/SevOne/upgrade/ansible/playbooks/.

   $ cd /opt/SevOne/upgrade/ansible/playbooks/

8. Run the migration script to move the existing configuration from the main.yml file to the tenant configuration file. You can use the migrated configuration file as a reference for the next step.
   Important: You must perform this step when upgrading from SD-WAN <=6.5 to SD-WAN 6.7.

   $ ./migrate_config -src /root/<Previous Installation Folder Name>/nuage/defaults/main.yml -dest /opt/nuage_ansible/config/<tenant name.yaml>

   Example

   $ ./migrate_config -src /root/sdwan-nuage-installation-6.5.0/nuage/defaults/main.yml -dest /opt/nuage_ansible/config/enterprise_sevone_config.yaml

9. Using the text editor of your choice, configure sample_config.yaml file for each tenant based on the current config values present in the default file /opt/nuage_ansible/config.
   Important: IMPORTANTMake sure to set the following variables to true for each tenant config file.

   • collector_upgrade: 'true'
   • flowaugmenter_upgrade: 'true'
   1. Copy the config file to the config directory and navigate to it.
      Important: This step will overwrite the existing config files with the new ones received in the package. This is necessary as new configurations have been added in SD-WAN 2.13. Please ensure that existing config files have been backed up.

      $ cp -f /opt/SevOne/upgrade/ansible/playbooks/config/* /opt/nuage_ansible/config

10. You are now ready to upgrade the Nuage Networks Collector. Run nuage deployment script.

    $ sh deploy_nuage.sh

11. To ensure that upgrade has completed successfully, perform the steps in Check Installation.

The Object Mapping page enables you to map the indicators on the objects that plugins poll to a flow interface. This enables you to display a FlowFalcon report of the flow data that is related to the poll data from an indicator that appears in an Instant Graph.

Users can generate FlowFalcon report for Object Group on the basis of Object mapping. As of SDWAN Nokia-Nuage 2.13 release, the solution will create Object mappings by default for SD-WAN Interface Objects. For any other objects, users will have to manually add the Object mappings. Steps required to manually add an object mapping can be found in SevOne NMS System Administration Guide > section Map Flow Objects.

Important: The device interface object indicator should be mapped to the appropriate direction Incoming/Outgoing.

Mapping a device interface object

After adding the object mapping, the user is now able to quick chain the performance metrics report to the FlowFalcon report for the indicator. Follow the steps below to see the flows report for the mapped object and the indicator.

• Navigate to Reports > Create Report. Select Performance Metrics.
• Select appropriate Resources the same as the mapped object and the indicator.
• Create the Performace Metrics report by clicking on Finish. A Performance Metrics report will be generated.
• Click on the Setting icon on the top-right corner of the report. Select Chain > Quick Chain.
  

  Performance Metrics Report

  

• This will automatically create the chained FlowFalcon for the selected object and the indicator as shown in the image below.

  Quick Chain Report

  

Execute the following steps to configure custom sites for the Nokia-Nuage collector.

1. To access the SevOne NMS login page, navigate to the appropriate URL in your browser.
2. From the navigation bar, click on Devices menu and select Device Manager.
3. Select the device and click on under the Actions column to display the Edit Metadata pop-up to manage the values for the metadata attributes you want to associate with the device.
4. Scroll-down to SDWAN_GENERIC.
   
5. Place your cursor on the Site Name you want to provide a custom name to and click on icon.
6. Enter the Site Name in the text field available and click on the Update button. For example, nokiaNuageSN.
   Note: > Site Name does not support the following characters
   

   • forward-slash - /
   • back-slash - \\
   • double-colon - ::
   • double-quotes - "
   • less-than - <
   • greater-than - >
   • pipe - |
   • tab
   • new-line
   
7. Click on Save button to save the custom Site Name.
   
   Important: Since the cronjobs run every 1 hour, it can take at most 1 hour for the update to take effect.

• You are not required to stop the collector to add a new tenant. To add a new tenant, follow the steps in Add Tenant.
• After the tenant has been added, follow the steps in Run Deployment Script.
• To see cronjobs for a tenant, follow the steps in under Check Cronjobs.

To stop collecting data from a tenant, follow the steps below.

1. Execute the following command to manually remove the cronjobs. This will stop collecting the data for a specific tenant.

   Remove Tenant

   $ rm /etc/cron.d/nuage_<tenant_name>
   
   $ rm /etc/cron.d/nuage_<tenant_name>_flow_collector
   
   $ rm /etc/cron.d/nuage_* # check for other files with nuage prefix , if they have tenant specific cronjob then remove it
   
   $ rm /opt/nuage_ansible/config/<tenant_name>_config.yaml
   
   $ rm /opt/sdwan-nuage/<tenant-name>/*
   
   $ docker stop nuage_alarm_runner_<tenant_name>
   
   $ docker rm nuage_alarm_runner_<tenant_name>

   Note: Default location for config directory is /opt/nuage_ansible/config. If config files are in a different location, remove the <tenant>_config.yaml file from that location.
2. After stopping the collection of data for the tenant, manually cleanup to remove the tenant specific data from the NMS. To purge the flow data, from the navigation bar, go to Administration, select Flow Configuration, and then select Flow Interface Manager. Select the devices from the list specific to the tenant, click on the icon and Purge Device Flows.
3. To finally delete the data, select the devices specific to the tenant from the list on the Flow Interface Manager, click on the Delete Device Rules button.
4. To delete the tenant device group, from the navigation bar, go to Devices, select Grouping, and then select Device Groups. Hover over the tenant device group and click on  icon. Click on OK to confirm.
5. To delete the tenant object group, from the navigation bar, go to Devices, select Grouping, and then select Object Groups. Hover over the tenant object group and click on  icon. Click on OK to confirm.
6. To delete the devices from this tenant, from the navigation bar, go to Devices and then select Device Manager. Select the devices for this tenant and click on Delete Selected. Then click on OK to confirm.

Download SevOne NMS / SD-WAN Virtual Appliance images for AWS from IBM Passport Advantage ( https://www.ibm.com/software/passportadvantage/pao_download_software.html ) via Passport Advantage Online . However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support .

Please refer to SevOne Data Platform Deployment on Amazon Web Services guide for details on how to perform the deployment.

Download SevOne NMS / SD-WAN Virtual Appliance images for AWS from IBM Passport Advantage ( https://www.ibm.com/software/passportadvantage/pao_download_software.html ) via Passport Advantage Online . However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support .

Please refer to SevOne Data Platform Deployment on Microsoft Azure guide for details on how to perform the deployment.

Please refer to SD-WAN Nokia-Nuage Networks Collector Installation Guide for details to access the new instance via SSH.

Execute the following commands to cleanup old containers, Nuage Networks Collector image, and any other images.

$ docker rmi docker.sevone.com/sc/collectors/nuage:<collector-release-tag>
 
$ docker images -qf "dangling=true" -q | xargs -r docker rmi
 
$ docker volume ls -qf dangling=true | xargs -r docker volume rm

The total number of aggregated flow views present in SevOne NMS must be less than 10. If the aggregated flow views are greater than 10, then delete the unwanted flow views and trigger the deployment script again.

By default, the Nuage collector creates log rotation rules in /etc/logrotate.d/nuage-collector for the files stored in the log directory /var/log/sdwan-nuage/<tenant_name>/.

Nuage Collector log rotate rules created in /etc/logrotate.d/nuage-collector

/var/log/sdwan-nuage/*.log {
    daily
    size 100M
    missingok
    rotate 5
    compress
    delaycompress
    notifempty
    dateext
    dateformat %s
}

Sometimes, by the time Nuage Flow View creation happens, fields are still in the process of being inserted in the database. Due to this, the new fields do not end up in the Nuage Flow View. In such cases, delete the partially created view SDWAN:Nuage:AugmentedFlow from the User Interface. SSH to your NMS and execute the following command from the installation directory.

Example

$ ssh root@<NMS appliance>
 
$ cd sdwan-nuage-installation
 
$ php nuage/templates/flow_view_creator_nuage.php.j2

To stop the collector, manually remove the cronjobs.

$ rm /etc/cron.d/nuage_<tenant_name>
 
$ rm /etc/cron.d/nuage_<tenant_name>_flow_collector

For any support tickets, please obtain the following details.

Execute the following steps to start the collector.

1. Using ssh, login to NMS appliance as root.

   $ ssh root@<NMS appliance>

   Example

   $ ssh root@10.128.10.226

2. Change directory to /opt/SevOne/upgrade/ansible/playbooks.

   $ cd /opt/SevOne/upgrade/ansible/playbooks

3. Start the collector by executing the following command.

   $ sh deploy_nuage.sh start_collector -f <tenant file path>

Execute the following steps to stop the collector.

1. Using ssh, login to NMS appliance as root.

   $ ssh root@<NMS appliance>

   Example

   $ ssh root@10.128.10.226

2. Change directory to /opt/SevOne/upgrade/ansible/playbooks.

   $ cd /opt/SevOne/upgrade/ansible/playbooks

3. Stop the collector by executing the following command.

   $ sh deploy_nuage.sh stop_collector -f <tenant file path>