Tune the NNM iSPI Performance for Traffic

This topic includes the following sections:

• Enhance the Performance of the Master Collector and the Leaf Collector
• Modify the JVM Parameters
• Tune the Retention Period
• Enhance NPS Performance

Micro Focus recommends that after installation, you configure the NNM iSPI Performance for Traffic to optimize its performance in small, medium, and large tier environment by tuning a set of parameters. Micro Focus also recommends that you configure the report data retention period for the flow data generated by Master Collector.

Enhance the Performance of the Master Collector and the Leaf Collector

The NNM iSPI Performance for Traffic provides you with a set of parameters that you can configure for the optimum performance of the iSPI in a large-scale environment. These tuning parameters are available in the following files:

• On the Master Collector system

  On Windows

  %NnmDataDir%\nmsas\traffic-master\conf\%NnmDataDir%\shared\traffic-master\conf\nmstraffic-master.address.properties or %TrafficDataDir%\nmsas\trafficmaster\conf\%TrafficDataDir%\shared\traffic-master\conf\nms-trafficmaster.address.properties

  On Linux

  /var/opt/OV/nmsas/traffic-master/conf//var/opt/OV/shared/traffic-master/conf/nmstraffic-master.address.properties

• On the Leaf Collector system

  On Windows

  %NnmDataDir%\nmsas\traffic-leaf\conf\%NnmDataDir%\shared\traffic-leaf\conf\nmstraffic-leaf.address.properties or %TrafficDataDir%\nmsas\trafficleaf\conf\%TrafficDataDir%\shared\traffic-leaf\conf\nms-trafficleaf.address.properties

  On Linux

  /var/opt/OV/nmsas/traffic-leaf/conf//var/opt/OV/shared/traffic-leaf/conf/nms-trafficleaf.address.properties

The NNMi Ultimate Support Matrix defines the following types of environments:

• Entry
• Small
• Medium
• Large

To configure the tuning parameters of the NNM iSPI Performance for Traffic after installation:

1. Identify the type of your environment—entry, small, medium, or large (see NNM iSPI Performance for Traffic Support Matrix). To determine the rate of flow records in your network, run the nmstrafficflowanalysistool.ovpl command. For more information, see Reference pages for this tool.
2. Note down the recommended values for the tuning parameters from the Leaf Collector table in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic.

3. Follow these steps on each Leaf Collector system:

   1. Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.

   2. Open the nms-traffic-leaf.address.properties file with a text editor.

      Micro Focus recommends that you do not modify the following properties in the nms-trafficleaf.address.properties file available on the Leaf Collector system:

      • Collector Name.flowrecord.pool.size
      • Collector Name.topn.flowrecord.pool.size

      In this instance, Collector Name is the name of the Leaf Collector instance.

   3. Set the flowrecord.pool.size property to the value recommended for FlowRecord for your environment in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic. Micro Focus recommends that you set this property to the recommended value only once.

      • If you have multiple Leaf Collector instances on the same Leaf Collector system, you must divide the required pool size among the Leaf Collector instances. You can then set the flowrecord.pool.size and topn.flowrecord.pool.size properties for each Leaf Collector instance in the nms-traffic-leaf.address.properties file accordingly. For example, if the object pool size required for FlowRecord of a Leaf Collector system is 100K and you have two Leaf Collector instances, you must set the flowrecord.pool.size property to 50K.

      • Increase in FlowRecord pool size requires additional memory. For every 100K increase in FlowRecord pool size, you must provide additional 200 MB memory. For example, if you increase FlowRecord pool size by 200K, you must add additional 400MB to the Xmx value for Leaf Collector.

   4. Set the topn.flowrecord.pool.size property to the value recommended for TopN Flowrecord for your environment in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic. Micro Focus recommends that you set this property to the recommended value only once.

      Increase in TopN FlowRecord pool size requires additional memory. For every 100K increase in TopN FlowRecord pool size, you must provide additional 200 MB memory. For example, if you increase TopN FlowRecord pool size by 500K, you must add additional 1GB to the Xmx value for Leaf Collector.

   5. In a large tier environment, if the NNM iSPI Performance for Traffic monitors at least 4000 interfaces with at least 20 thresholds, you must set the thresold.objectpool.size property to at least 1000000.
   6. Save the file.

   7. Restart the Leaf Collector by running the following command:

      On Windows

      %NnmInstallDir%\traffic-leaf\bin\%NnmInstallDir%\nonOV\trafficleaf\bin\%TrafficInstallDir%\nonOV\traffic-leaf\bin\nmstrafficleafstart.ovpl

      On Linux

      /opt/OV/traffic-leaf/bin//opt/OV/nonOV/traffic-leaf/bin/nmstrafficleafstart.ovpl

      During the operation, the NNM iSPI Performance for Traffic automatically updates the values of these parameters. With every automatic update of tuning parameters, the NNM iSPI Performance for Traffic creates a new entry in the Flow Processing Status view in the NNMi console.

4. Follow these steps on the Master Collector system:

   1. Log on to the Master Collector system as an administrator on Windows and as root on Linux.

   2. Open the nms-traffic-master.address.properties file with a text editor.

   3. Set the nms.traffic-master.maxflowrecord.inqueue property to the value recommended for Master Queue Size for your environment in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic.
   4. Save the file.

   5. Restart the Master Collector by running the following command:

      On Windows

      %NnmInstallDir%\traffic-master\bin\%NnmInstallDir%\nonOV\trafficmaster\bin\nmstrafficmasterstart.ovpl or %TrafficInstallDir%\trafficmaster\bin\%TrafficInstallDir%\nonOV\trafficmaster\bin\nmstrafficmasterstart.ovpl

      On Linux

      /opt/OV/traffic-master/bin//opt/OV/nonOV/trafficmaster/bin/nmstrafficmasterstart.ovpl

Additional Tuning Parameters

The NNM iSPI Performance for Traffic is unable to write files on the NNMi system when sufficient disk space is not available or there are large number of pending files for each type of report to be written to the NNMi system.

The NNM iSPI Performance for Traffic writes files to the NNMi system in the %NnmDataDir%\shared\perfSpi\datafiles directory on Windows and /var/opt/OV/shared/perfSpi/datafiles directory on Linux.

To ensure that the NNM iSPI Performance for Traffic writes files successfully to the NNMi system, the NNM iSPI Performance for Traffic detects the amount of disk space available on the NNMi system and number of pending files of each type to be written to the NNMi system. Before writing files to the NNMi system, the NNM iSPI Performance for Traffic reads these values from the Master Collector configuration. By default, minimum amount of disk space required on the NNMi system for the Master Collector to write files to the NNMi system is 1 GB and maximum number of pending files of each type that can be queued when writing files to the NNMi system is 100.

To modify the default values set in the NNM iSPI Performance for Traffic, follow these steps on the Master Collector system:

1. Log on to the Master Collector system as an administrator on Windows and as root on Linux.

2. Stop the Master Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl or

   %TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl

   On Linux

   /opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

3. Open the nms-traffic-master.address.properties file with a text editor.

4. Set the following properties depending on your requirements:

   1. nnm.shared.drive.size: Defines the minimum amount of disk space required on the NNMi system for the Master Collector to write files to the NNMi system.

   2. nps.max.pending.files: Defines the maximum number of pending files of each type that can be queued when writing files to the NNMi system.
5. Save the file.

6. Start the Master Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl or

   %TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl

   On Linux

   /opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl

Disable Object Pool Tuning

The NNM iSPI Performance for Traffic automatically tunes the pool size of the Leaf Collector based on the values that you set for pool sizes in your environment. You can disable this feature if you do not want variable memory usage.

To disable the automatic tuning of the pool size for a Leaf Collector instance:

1. Log on to the Leaf Collector system.

2. Stop the Leaf Collector processes by running the following commands:

   On Windows

   %NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl or

   %TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl

   On Linux

   /opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl

3. Navigate to the following directory:

   On Windows

   %NnmDataDir%\nmsas\traffic-leaf\conf\nms-traffic-leaf.address.properties or

   %TrafficDataDir%\nmsas\traffic-leaf\conf\nms-traffic-leaf.address.properties

   On Linux

   /var/opt/OV/nmsas/traffic-leaf/conf/nms-traffic-leaf.address.properties

4. Open the nms-traffic-leaf.address.properties file with a text editor.

5. Add the following property:

   leaf.collector.object.pool.tuner.disable=true

   Adding the above property disables automatic tuning of pool sizes for all instances.

6. Save and close the file.

7. Start the Leaf Collector processes by running the following commands:

   On Windows

   %NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl or

   %TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl

   On Linux

   /opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl

Modify the JVM Parameters

You can modify the JVM parameters for the Master Collector and Leaf Collector to change the Initial Java Heap size (-Xms) and the Maximum Java Heap size (-Xmx).

To change the Initial Java Heap size (-Xms) and the Maximum Java Heap size (-Xmx) for Master Collector:

1. Log on to the Master Collector system as an administrator on Windows and as root on Linux.

2. Stop the Master Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl or

   %TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl

   On Linux

   /opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl

3. Navigate to the following directory:

   On Windows

   %NnmDataDir%\nmsas\traffic-master\conf

   or

   %TrafficDataDir%\nmsas\traffic-master\conf

   On Linux

   /var/opt/OV/nmsas/traffic-master/conf

4. Open the nms-traffic-master.jvm.properties file using a text editor.
5. Set the -Xms property to the value recommended for the Initial Java Heap size (-Xms) for your environment in the Master Collector Size table in NNMi Ultimate Support Matrix. By default, Initial Java Heap size is set to 128 MB.
6. Set the -Xmx property to the value recommended for the Maximum Java Heap size (-Xmx) for your environment in the Master Collector Size table in NNMi Ultimate Support Matrix. By default, Maximum Java Heap size is set to 4096 MB.
7. Save and close the file.

8. Start the Master Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl or

   %TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl

   On Linux

   /opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl

To change the Initial Java Heap size (-Xms) and the Maximum Java Heap size (-Xmx) for Leaf Collector:

1. Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.

2. Stop the Leaf Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl or

   %TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl

   On Linux

   /opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl

3. Navigate to the following directory:

   On Windows

   %NnmDataDir%\nmsas\traffic-leaf\conf

   or

   %TrafficDataDir%\nmsas\traffic-leaf\conf

   On Linux

   /var/opt/OV/nmsas/traffic-leaf/conf

4. Open the nms-traffic-leaf.jvm.properties file using a text editor.

5. Set the -Xms property to the recommended value for the Initial Java Heap size (-Xms) for your environment in the Leaf Collector Size table in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic. By default, Initial Java Heap size is set to 128 MB.

6. Set the -Xmx property to the recommended value for the Maximum Java Heap size (-Xmx) for you environment in the Leaf Collector Size table in Performance and Sizing Recommendations for the NNM iSPI Performance for Traffic. By default, Maximum Java Heap size is set to 4096 MB.
7. Save and close the file.

8. Start the Leaf Collector by running the following command:

   On Windows

   %NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl or

   %TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl

   On Linux

   /opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl

Tune the Retention Period

The retention period is the time for which the detailed and summarized data generated by the Master Collector is stored on the NPS system for reporting purposes. The stored data contributes to the NPS system disk usage. On the NPS system, after the database occupies a portion of the disk, you cannot reduce the database (*.db) files and reuse that disk space for operating system. To reduce the disk usage you can modify the retention periods for the extension pack provided by NPS or individual extension packs provided by NNM iSPI Performance for Traffic. The retention period value set for the extension packs provided by NNM iSPI Performance for Traffic overrides the retention period value set for the extension pack provided by NPS. For information on changing retention periods for NPS, see the Micro Focus Network Node Manager iSPI Performance for Metrics Installation Guide.

Each extension pack provided by the NNM iSPI Performance for Traffic is installed with different retention periods for the detailed and summarized data. Following parameters define these retention periods:

• PRSPI_DataRetention_Raw: Number of days for which the detailed data is stored. The detailed data for NNM iSPI Performance for Traffic is stored in raw tables only. Therefore, to change the retention period, you must modify PRSPI_DataRetention_Raw parameter. The NNM iSPI Performance for Traffic extension packs provide the default retention periods listed in the following table:

Retention Period Default Values

Extension Pack	Default Value
Interface_Traffic	3
Interface_Traffic_1_minute	30
Interface_Traffic _Aggregated	400

The Interface Traffic_1_min reports are disabled by default. For information on how to enable these reports, see the Configuring Master Collectors section in the Network Node Manager iSPI Performance for Traffic Software Online Help.

• PRSPI_DataRetention_Hour: Number of days for which the data summarized every hour is stored.

NNM iSPI Performance for Traffic does not store data in summary tables. Modifying this parameter will not change the retention period.

• PRSPI_DataRetention_Day: Number of days for which the data summarized every day is stored.

NNM iSPI Performance for Traffic does not store data in summary tables. Modifying this parameter will not change the retention period.

• PRSPI_SUMMARY_Policy: Summarization policy for the extension pack. Micro Focus recommends that you do not set this parameter for any extension pack of NNM iSPI Performance for Traffic.

To change the default retention period for individual extension pack:

1. Log on to the NPS system.
2. Stop the ETL process.

3. Open customConfig.cfg file with a text editor:

   On Windows

   <NPS_Data_Dir>\NNMPerformanceSPI\rconfig\<extensionpack_name>\customConfig.cfg

   In this instance, <NPS_Data_Dir> is the directory where NPS configuration and data files are stored after you install NPS.

   On Linux

   /var/opt/OV/NNMPerformanceSPI/rconfig/<extensionpack_name>/customConfig.cfg

4. Transfer the contents of the customConfig.cfg file into a new userConfig.cfg file and save the new file in the same location.

5. In the new userConfig.cfg file, set the parameter PRSPI_DataRetention_Raw to modify the number of days for which the detailed data is stored.

   Modifying the retention period can have significant impact on the disk usage.

6. Save and close customConfig.cfg file.

7. Restart the ETL process.

Enhance NPS Performance

NPS processes the NNM iSPI Performance for Traffic files slowly that results in increasing the number of pending files for each type of report to be written to the NNMi system. You can increase the performance of the NPS system by tuning the ETL. For more information, see "Tuning the ETL for NPS" below.

You can also enhance the performance of NPS by tuning the hardware. Optimize the disk and file system when large amount of data processing is required to reduce the disk latency and I/O wait for optimized record processing and reporting. For more information, see "Disk Usage Recommendations" on the next page.

Tune the ETL for NPS

To tune the ETL for NPS:

1. Log on to the NPS system.
2. Stop the ETL process.

3. Open customConfig.cfg file with a text editor:

   On Windows

   <NPS_Data_Dir>\NNMPerformanceSPI\rconfig\<extensionpack_name>\customConfig.cfg

   In this instance, <NPS_Data_Dir> is the directory where NPS configuration and data files are stored after you install NPS.

   On Linux

   /var/opt/OV/NNMPerformanceSPI/rconfig/<extensionpack_name>/customConfig.cfg

4. Create a new userConfig.cfg file in the same location and transfer the contents of the customConfig.cfg file into the new userConfig.cfg file.

5. In the new userConfig.cfg file, set the following parameters for each extension pack to tune the ETL for NPS:

   Increasing the tuning parameters for ETL process of NPS to values listed in tables below will result in significant increase in CPU utilization. Make sure that there is sufficient CPU bandwidth available before increasing these parameters.

   In this instance, <NPS_Data_Dir> is the directory where NPS configuration and data files are stored after you install NPS.

   The number of child processes for the ETL process of NPS for medium and large tiers of traffic data based on different extension packs (ETL_MaxChildProcs):

   Approximate managed environment tier	Interface_Traffic	Interface_Traffic_1_Minute	Interface_Traffic_ Aggregated
   Medium	5	10	10
   Large	10	50	20

   The maximum number of records per child process for the ETL process of NPS for medium and large tiers of traffic data based on different Extension Packs (ETL_MaxRecordsPerChild):

   Approximate managed environment tier	Interface_Traffic	Interface_Traffic_1_Minute	Interface_Traffic_ Aggregated
   Medium	100k	100k	100k
   Large	100k	200k	200k

   The number of files per batch for the ETL process of NPS for medium and large tiers of traffic data based on different Extension Packs (ETL_MaxMetricsFilesPerBatch):

   Approximate managed environment tier	Interface_Traffic	Interface_Traffic_1_Minute	Interface_Traffic_ Aggregated
   Medium	20	25	20
   Large	30	50	30

6. Save and close userConfig.cfg file.

7. Restart the ETL process.

Disk Usage Recommendations

To reduce the disk latency and I/O wait, follow these recommendations:

• Create the storage locations /var/opt/OV, IQ_SYSTEM_TEMP, and USER_MAIN on different disks on SAN.

  Run the following command to set the location and size of these storage locations:

  For Windows

  <NPS_Install_Dir>\NNMPerformanceSPI\bin\dbsize.ovpl

  For Linux

  /opt/OV/NNMPerformanceSPI/bin/dbsize.ovpl

  • Set IQ_SYSTEM_TEMP to a minimum value of 100 GB.
  • Set the disk cache ratios to 50/50 read/write
  • Use raw disks for storage locations

  For more information, contact your Storage Area Network administrator.