DX Infrastructure Management

Tech tips: NFA 9.2.1 New Device Based Licensing Display 

10-24-2014 11:28 AM

NFA 9.2.1 introduces a new License Monitoring view in the "About" screen which is based off of the Device based licensing model as opposed to the old interface based model.


The information is displayed next to the following labels:

■ Licensed Devices in Use

■ License Utilization




You can review this information to see whether you are close to using all of your licenses.

The calculation for license utilization is based on the Licensed Devices value on the Application Settings page.

This new setting is used only for this calculation.

The License Utilization percentage is accurate only if the Licensed Devices value is accurate. Changing the Licensed Devices value does not increase or decrease the number of available licenses.




Note: To calculate the number of licenses that each device uses, you can use the following formula. Divide the number of active* interfaces by 5 and round up to the next whole number. See the following examples:

■ 1 device that has 5 active interfaces consumes 1 license

■ 1 device that has 6 active interfaces consumes 2 licenses

■ 2 devices that each have 1 active interface consume 2 licenses between them

If you need help determining the number of licenses you have, consult your CA representative.

* In this context, an active interface is one that has exported data to the product and the data is still stored. If an interface has exported data, its records continue to be stored unless you delete it permanently from the Available Interfaces page. Active interfaces are shown on the Available Interfaces page with a License value of 'Yes.'


This has also been published on Support.ca.com as a Tech Doc http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1404305.aspx

0 Favorited
0 Files

Tags and Keywords


10-27-2014 12:43 PM

Np. It was an option in the old system and I hadn't noticed that it wasn't

an option in the new system.


On Mon, Oct 27, 2014 at 11:41 AM, Melanie_Giuliani <

10-27-2014 12:41 PM

Hi Stuart,


Unfortunately we don't have the capability to convert document comments into discussion threads or split them off. I would encourage Eugene Khodus /Christopher Walsh to open a discussion thread for this conversation, though, as it may be helpful for other users as well, and it will be easier for others to find it in discussion form.




10-27-2014 12:34 PM

Hello Stuart,


I don’t know how I can do it.

I’m sorry ☹


If you or Melanie can help me, I will be very grateful.



10-27-2014 12:28 PM

Christopher, thanks a lot for your help!


The version 9.2.1 worked from evening of Friday (10/24/2014) to morning of Monday (10/27/2014). And I didn't see any data in NFA since evening of Friday.

The version 9.2.0 is working fine with same devices.

I was confused strange percentage utilization of licenses.

Tomorrow I will try repeat upgrade to 9.2.1 using your recomendations.


Thank you very much.

10-27-2014 12:08 PM

Melanie_Giuliani, please split this into a separate thread.

10-27-2014 12:01 PM

This should probably be spun off on a new thread.


There are many possible causes of a device not being licensed on a new installation.

You should make sure that your devices are receiving over 50kb's of data over a 15 minute period of time in order to display data.


You can use the NASTv13 tool described here Tech Tips: NASTv13.exe available for NFA 9.1.3 and NFA 9.2 to see how much data is coming in.


An interface will not enter a "licensed" state until it receives 50kb's of valid NetFlow over 15 minutes.


You can verify if you are receiving valid NetFlow by using Wireshark described here Tech Tips: How to determine if a NetFlow enabled device is sending the correct fields


If all of that checks out okay, make sure all services are up and running on your Console, Harvester, and DSA(If a 3 tier).


Check to see if you are seeing .nfa files greater than 1kb in the \NetFlow\datafiles\harvesterarchive directory on the Harvester.

Check to see if there are any files not getting processed in one of the following directories, \NetFlow\datafiles\HarvesterWork, \NetFlow\datafiles\ReaperWork, and \NetFlow\datafiles\ReaperInput, these directories should have files moving in and out of them. If you see lots of older files, it means they are not being processed.


You can check some of the logs on the Harvester under \Netflow\logs and the logs on the NFA Console server under \Reporter\logs.


If you do not see anything obvious, open an issue with support and include run the  RemoteEngineer tool on the Console and Harvester and upload them to the issue, you can find more details on that here Tech Tip: CA Remote Engineer updated for NFA

10-27-2014 11:49 AM

Christopher, thank you very much.


But, then I have a problem: I just upgraded NFA from version 9.2.0 to 9.2.1. The process of upgrade finished fine, but the page of license showed me that "License Utilization: 2546%" and all interfaces switched off with "No License". I didn't see any information from my interfaces after upgrade.


Could you help me, where is my mistake?


Thank you.

10-27-2014 11:33 AM

NFA 9.2.1 doesn't actually require a license file.

Licensing/Entitlement is controlled by what you can download from the Support.ca.com Download Center and monitored by your CA Account team.


The "Gold Key" works with ReporterAnalyzer 9.0, which still requires a license file.

10-27-2014 11:25 AM



Can I use a "Gold key" license file with NFA 9.2.1?

I've the "Gold key" license file for 9.2.0 version and it is working fine.


Thank you.

10-27-2014 09:25 AM

FYI, this query will give you the license consumption and device count:


select 'Legal Licenses Consumed' as Type, sum(a.license_count) as Count
from (select ceil(count(*)/5) as license_count from reporter.agents_all_view group by routername) as a
select 'Number of Devices', count(distinct(RouterName))
from reporter.agents_all_view;


For example, this shows that we use an average of 1.4 device licenses per device (1251 device licenses / 898 devices).

Related Entries and Links

No Related Resource entered.