How do I get all Custom Application Mapping or NBAR2 names to display in NFA reports when I have multiple Domains.

Document ID : KB000016570
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

When creating Application Definitions, each definition is only created under the domain you specify upon creation.  When importing NBAR2 definitions, it creates them all in the default domain, when logged in with a custom domain you will not see names by default, unless you edit each Protocol Name for each custom port while selecting the specific domain you want this name to show up in.  This can be very tedious if you have many application definitions.

Question:

How do I get all Custom Application Mapping or NBAR2 names to display in NFA reports when I have multiple Domains?

Environment:
NFA 9.3 and later.
Answer:

1. Backup your reporter database or at least the reporter.protocol_domains table before updating the database by running the command below from a cmd prompt:

mysqldump reporter protocol_domains > Protocol_domains.sql

 

2. Open a new cmd prompt on the NFA console server and type:

mysql reporter

 

3. Find your domain ID's from the reporter.domains table by running:

select * from harvesters;

 

4. Use those ID values in the mysql statements below.  Each domain will need to have its own command.  Below are examples of applying this to domain ID's 2,3, and 4.

Note that the where clause "where DomainID=" will always use 1 as it is the default domain ID.

 

replace into protocol_domains (protocolId, domainId, name, description)  select protocolid, 2, name, description from protocol_domains where domainid=1;

 

Then use the next domain ID in the next command, 3 in this case:

replace into protocol_domains (protocolId, domainId, name, description)  select protocolid, 3, name, description from protocol_domains where domainid=1;

 

Then do the same for the next domain id…

replace into protocol_domains (protocolId, domainId, name, description)  select protocolid, 4, name, description from protocol_domains where domainid=1;

 

5. If you have more domains continue on using the same format as above.

 

6. Once completed, check your interface reports to see if the Custom Applications/nbar2 protocol names are now shwoing up.