NetFlow Traffic Analyzer 4.0 Release Notes

Release date: December 5, 2013

These release notes describe the new features, improvements, and fixed issues in NetFlow Traffic Analyzer 4.0. They also provide information about upgrades and describe workarounds for known issues.

If you are looking for previous release notes for NetFlow Traffic Analyzer, see Previous Version documentation.

New features and improvements in NTA 4.0

Return to top

NTA 4.0 offers new features and improvements compared to previous releases of NTA.

NTA Flow Storage database

  • New no-SQL column-oriented database for storing flow data.
  • Improved NTA performance - better load times of NTA resources and reports, ability to process more flows per second.
  • One-minute data granularity during the whole retention period.
  • Flexible deployment options - NTA Flow Storage Database is separate from Orion SQL, allowing for installation on any computer in your network.
    • If you are using NTA primarily for viewing CBQoS data and receive few or no flows, you do not need to set up an extra server for the NTA Flow Storage Database; you can install it locally.
    • For NTA evaluations using MS SQL Express database, installing NTA Flow Storage Database on a remote server is not natively supported. However, it is possible. For more details, see the KB article Installing NTA 4.0 Evaluation with Remote NTA Flow Storage Database.

New Web-Based Reporting

For more information, see NetFlow Traffic Analyzer Reports.

  • Create and edit reports from within the Orion Web Console.
  • Include custom tables to apply data and layout you need in your reports.
  • Use 7 CBQoS legacy reports and 14 new web-based reports.

Improved CBQoS Granularity

CBQoS data can be viewed with one-minute granularity during whole retention period.

Behavior changes

  • Historically, host and domain names are stored in flows. If endpoint hostnames are updated, the new names are reflected only in new incoming flows, not in the historical data.
  • Endpoint, transmitter and receiver resources group data by the hostname instead of by the IP address. Multiple IP addresses resolved to the same hostname are now grouped into one row in the resource.
  • Updates to the IP Groups, Applications and NetFlow sources (disabling interface) settings do not appear immediately in resources, because stored data have to be updated with the new information. The update operation can take minutes to complete.

Fixed issues

Return to top

NTA 4.0 fixes the following issues.

Issue Case Numbers
Performance Problems
SQL performance - high CPU 467265
NTA 3.8 upgrade problems 267321
NTA 3.9 upgrade problems 503209
Query in NTA resource running slowly 322310
Unable to modify IP address groups 202141
Performance issues after migration 540447
CBQoS Policies Issues
CBQoS not working for some policies 484360
CBQoS Issue:Cannot find parent class for policy 482798, 534199
Not all CBQoS classes displayed on a device 505123
CBQoS polling issue 528796
CBQoS policy used in more classes not displaying correct data 329367
CBQoS information not displayed 290241
Class-default missing in CBQoS data 506458
Orion Web Console Improvements
Better integration with Orion charts due to improved data granularity 266290
Orion subviews support added -

Known issues

Return to top

Issue Case Number

Performance Impact

Flow data are saved in more detail in the NTA Flow Storage Database. Displaying reports and graphs in NTA resources on summary views requires handling increased amount of data. In case of viewing data for longer time periods, such as 12 hours or more, rendering and processing the data can be slower.
-
Conversations are grouped by IP addresses (not by hostnames as endpoint resources). Multiple IP addresses resolved to the same hostname are now grouped into one row in the resource. -
Endpoint hostnames must comply with the RFC 952 standard; endpoint names containing other than the following characters A-Z, a-z, 0-9, .- will not display correctly. -

End of life

Return to top

Version EoL Annoucement EoE Effective Date EoL Effective Date
3.9

December 10, 2013:

End-of-Life (EoL) announcement – Customers on SolarWinds NetFlow Traffic Analyzer version 3.9 or older should begin transitioning to SolarWinds NetFlow Traffic Analyzer version 4.0.

March 10, 2014:

End-of-Engineering (EoE) – Service releases, bug fixes, workaround, and service packs for SolarWinds NetFlow Traffic Analyzer version 3.9 or older will no longer actively be supported by SolarWinds.

March 10, 2015:

End-of-Life– SolarWinds will no longer provide technical support for SolarWinds NetFlow Traffic Analyzer version 3.9 or older.

See the End of Life Policy for information about SolarWinds product lifecycle phases. For supported versions and EoL announcements for all SolarWinds products, see Currently supported software versions.


Legal notices

Return to top

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.